[Question] Ready to replace Flink SQL?

Very glad to see arroyo like project that using native language to rewrite and redesign streaming computation engine.
We are finding high performance streaming computation engine and we can contribute code to such project.
Please tell me what's the progress of feature to replace Flink SQL.
Thanks a lot.

Thanks for checking out Arroyo! Arroyo is able to replace Flink SQL for many use cases. Compared to Flink, arroyo is much faster (5-10x depending on the query), easier to develop against (better error messages, better UI, some simpler SQL semantics) and easier to run (no JVM, designed for fast rescaling/recovery and to run in the cloud and kubernetes).
However, today Flink SQL has more features (for example, we don't currently support all of the joins that Flink does, more connectors, and a much bigger community. I'd take a look our SQL docs and see if the features you need are there. Feel free to open up issues for any features that you need and we can see how difficult they would be and where they fit into our prioritization.


Add basic documentation to open and close overlays

Found a bug, not ready for review yet.

Approved


windows-arm lacks bash AND pwsh, as well as git itself.

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Current runner version: '2.319.1'
Runner name: 'windows-11-arm-32gb_442e95740f94'
Runner group name: 'Imageflow'
Machine name: 'runner'
VM Image
OS: Windows (arm64)
Source: Marketplace
Publisher: MicrosoftWindowsDesktop
Offer: windows11preview-arm64
Plan: win11-23h2-ent
Version: 22631.4037.240811
Is it regression?
na
Expected behavior
it should have git/bash/pwsh
Actual behavior
it lacks basic tools
Repro steps
Create a large runner in the org, selecting windows arm

Hi @lilith  ,Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

Hi there - right now the only option we have available for windows on arm is the base image, and you are correct that there are no tools installed on it. We have a windows image coming soon that will be provided by Arm, that will have tools installed. That image will be managed out of the partner-runner-images repository, as it will be a partner image.

This is not @ you, but at the powers that be that decided windows-arm support should be third-party, and feel free to quote me:
Hot take, but if Microsoft wants our free weekend labor to port tens of thousands of essential open-source packages to support Windows/ARM and avoid a repeated flop, they could put in a token effort themselves and perhaps not charge us for the privilege.  This should not be a fake partner feature we're paying Github for. It should have launched before the Copilot+ marketing push.
Microsoft's buggy dev toolchains for ARM already take 10x more of our valuable time and effort, and without functional free CI, why is it worth our time? It's completely valid for maintainers to make a no-windows-arm support policy when the situation is this uniquely bad, and it's easy to spend more time keeping that platform supported than everything else combined. Mac support is easier and that's saying something, given their hostile T&C on the apple SDKs.


Publishing Fails Due to Missing metadata.json

Hello
I'm encountering an error when attempting to publish. The error message received is: "No metadata.json found. Was it included in the zip?" This error results in a BadRequest with a status code of 400. I would like to understand when this error typically occurs and what might be causing it.
I confirm that the zip file is there as well as the metadata.json.
I have consulted with my company's devOps team member, but they were unable to determine the cause of this error.
Can you provide any guidance on how to resolve it?
Thank you in advance!

The issue appears to arise form upload.js

maybe you can add a console.log of e.message to actually get the reason behind the error?
sorry for the late reply, I am not actively maintaining this project at the moment


Canvas is cutted of on A4

Hello! I am using chart.js for graphics on my web page.
The problem:
On pdf view one of them is cutted for A4 view.
My config:
const openPdfInNewWindow = (pdf) => {
const blob = pdf.output('blob');
window.open(window.URL.createObjectURL(blob));
};
    html2pdf(input, { // my selector
        margin: 0,
        filename: name, // some name
        image: { type: 'jpeg', quality: 1 },
        html2canvas: { scale: 2, logging: true },
        jsPDF: { unit: 'pt', format: 'a4', orientation: 'l' },
        pdfCallback: openPdfInNewWindow,
    });

Could you please take a look and tell what's my bad?
Thanks in advance!

Hey @notfffMe, sorry about the delayed response. Take a look at #44, I believe it's related.
Currently html2pdf creates a clone of the contents and resizes it to your page width, so that everything reflows to fit (like shrinking your browser window).  As discussed in the linked issue, I'll work on a "fit-to-width" option in the future.


CLI option does not handle dynamic meta data

I am using option C to send results to Slack. I started with example configuration like this:
{
  "sendResults": "always",
  "slackLogLevel": "error",
  "sendUsingBot": {
    "channels": ["demo"]
  },
  "showInThread": true,
  "meta": [
    { "key": "build", "value" : "{__ENV_BUILD_ID}"},
    { "key": "branch", "value" : "{__ENV_BRANCH_NAME}"},
    { "key": "commit", "value" : "{__ENV_COMMIT_ID}"},
    { "key": "results", "value" : "https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_272x92dp.png"}
  ],
  "maxNumberOfFailures": 4,
  "disableUnfurl": true
}

But what I get in Slack is this:

It looks like it does not process these environment variables. According to documentation it shouldn't let me sent it because I don't have these variables defined. It should output an error... Is there something I am doing wrong? Or is it just broken?

@saulius-skarulskis think theres a bug in the doco, can you try without the curly branches?
e.g.
  "meta": [
    { "key": "build", "value" : "__ENV_BUILD_ID"},
    { "key": "branch", "value" : "__ENV_BRANCH_NAME"},
    { "key": "commit", "value" : "__ENV_COMMIT_ID"},
    { "key": "results", "value" : "https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_272x92dp.png"}
  ],

It works! So its just documentation bug. Thanks 👍


Is it possible to use interactive React components as Items & Groups

From the vis documentation shows that React components can be used as templates for Items and Groups. However, I can't seem to get anything to send data out - ie clicking an item to trigger a Redux action. Is the React component only able to function as normal when used as an Item by specifying the template function like in the examples:
 template: function (item, element) {
      if (!item) { return }
      ReactDOM.unmountComponentAtNode(element);
      return ReactDOM.render(<Item item={item} />, element);
  },

Item looks like this
class Item extends React.Component {
  constructor(props) {
    super(props);
    this.onClick = this.onClick.bind(this);
  }

  onClick(event) {
    console.log("click");
    // this.props.dispatch()
  }

  render() {

    return (
      <div style={{width:'20px', height:'20px'}}>
        <button style={{width:'70px', height:'50px'}} onClick={this.onClick} type="button">Click</button>
      </div>
    );
  }
}

The strange thing is, the onClick handler never executes when clicking on the button, but does trigger when the item is dragged on the timeline

I'm struggling too with this sort of interaction with an item. It feels akward to use the vis built in handler, when using React.
Did you get an answer?

+1

+1

+1

This isn't something we need ourselves so would someone else would need to submit a PR. I leave the issue open if anyone is interested

+1


refactor: replace usage of ThreadManagerSubsystem with reactor Scheduler

This replaces the ThreadManagerSubsystem with Scheduler provided by rxjava. pretty straightforward  since this subsystem is only ever used in the core engine and not to an extent that would make sense. the threads allocated are mostly unused and sit idle.
toTest:

verify that game previews are saved
verify that a screen shot could be taken with F12
game startup is dependent on some of this threading.

Contributes to https://github.com/MovingBlocks/Terasology/issues/4798

Learning lots of things about micrometer! This looks promising.
There's one part where I'm not connecting the dots.
* `saveScreenshot` used ThreadManager. ThreadManager used ThreadMonitor.

* This PR replaced ThreadManager with Reactor schedulers.

  * keturn complained that meant `saveScreenshot` was no longer reporting to ThreadMonitor.

* [`27e8b0e` (#4799)](https://github.com/MovingBlocks/Terasology/pull/4799/commits/27e8b0ec43284bc01d5917a8b80a86136872b8c0) made changes to ThreadMonitor (in SingleThreadMonitorImpl) so that ThreadMonitor reports to micrometer.

* and changed RunningThreadsMode to report only from micrometer, not directly from ThreadMonitor.

* but `saveScreenshot` (and anything else that formerly used ThreadManager) still doesn't use ThreadMonitor,

  * and I don't see any other MetricsMode for the DebugOverlay that reports on tasks that lack ThreadMonitor integration?

I was testing this was Pathfinding. just need to add a name and a tag with metrics(). probably want to do something custom with the list :https://projectreactor.io/docs/core/release/reference/#metrics

Reporting on In-Progress Tasks
The use case we're looking to address is: How do I know if there is a long-running (or indefinitely stuck) task currently being processed?
A task that has not finished will not be represented in a snapshot of a Timer.
Possible Approaches
ExecutorService metrics
ExecutorServices (such as those backing Reactor's schedulers) are instrumented with meters. They include executor.active and executor.queued gauges.
These should be sufficient to let us know if there are active tasks, though it is not enough to distinguish short tasks from long ones, nor will it let us see which tasks they are.
Long Task Timers
If we have certain operations that are known to take a long time, we can wrap them in a long task timer.
(I'm not sure we have an annotation processor that handles the @Timed(longTask=true) annotation, we might have to use the MeterRegistry API instead.)
GameScheduler API
GameScheduler provides a central interface. We could change from returning direct Scheduler references like this
GameScheduler.boundedElastic().schedule(() -> saveScreenshotTask(buffer, width, height));

to providing a schedule method more like the old ThreadManager.submitTask:
GameScheduler.schedule("Write Screenshot", () -> saveScreenshotTask(buffer, width, height));

which would give us a chance to wrap the Runnable in something like our ThreadMonitor#startThreadActivity.

thats why those tasks are wrapped in a Mono, does the same thing.

Reporting on In-Progress Tasks
The use case we're looking to address is: How do I know if there is a long-running (or indefinitely stuck) task currently being processed?
A task that has not finished will not be represented in a snapshot of a Timer.
Possible Approaches
ExecutorService metrics
ExecutorServices (such as those backing Reactor's schedulers) are instrumented with meters. They include executor.active and executor.queued gauges.
These should be sufficient to let us know if there are active tasks, though it is not enough to distinguish short tasks from long ones, nor will it let us see which tasks they are.
Long Task Timers
If we have certain operations that are known to take a long time, we can wrap them in a long task timer.
(I'm not sure we have an annotation processor that handles the @Timed(longTask=true) annotation, we might have to use the MeterRegistry API instead.)
GameScheduler API
GameScheduler provides a central interface. We could change from returning direct Scheduler references like this
GameScheduler.boundedElastic().schedule(() -> saveScreenshotTask(buffer, width, height));

to providing a schedule method more like the old ThreadManager.submitTask:
GameScheduler.schedule("Write Screenshot", () -> saveScreenshotTask(buffer, width, height));

which would give us a chance to wrap the Runnable in something like our ThreadMonitor#startThreadActivity.

Security
GameScheduler

GameScheduler is marked @API. gameMain() provides access to scheduling on GameThread, which is not @API.
What is requiring the AccessController.doPrivileged to get the schedulers?

Is engine code requiring it, or only modules?
Is it for something that reactor…Schedulers does only on the first call (e.g. because it makes a new thread pool), or always?
If it is for new threads, does immediate need it? Immediate doesn't involve new threads.

ExternalApiWhitelist

Packages

reactor.core.scheduler — probs don't want modules having direct access to Schedulers; replace this PACKAGES entry with a few CLASSES?

Document
GameScheduler

Link to Reactor Reference Guide on Schedulers for general info on what "boundedElastic" is and how it differs from "parallel."
When programming for Terasology, when should we use each?

Is the answer always "parallel"?

a boundedElastic scheduler will create threads to fit the needs of the tasks getting submitted to the scheduler. if you can keep all threads busy with 3 threads then elastic scheduler will use three and will split the load. it will expand the number of threads to match the rate of submitted tasks I believe. parallel scheduler is capped to the number of threads the processor supports. difference between IO and CPU bounds tasks.

The way the thread monitor works is not how I want to fit this into this micrometer scheme. I would ideally like to build a facade over micrometer. so we can just stub it out for release candidates.

GameScheduler is marked @API. gameMain() provides access to scheduling on GameThread, which is not @API.

I brought this up in today's meeting, and it wasn't clear to any of us if/when modules need access to this.
skaldarnar's proposal was to leave this implemented, but at a permission level modules wouldn't be able to actually use, with a comment along the lines of "change this if we have a documented use case for it" or something like that.
(I don't think we can implement it exactly as proposed, because I don't think the @API system gives us per-method control, but we can make it package-private or something.)

GameScheduler is marked @API. gameMain() provides access to scheduling on GameThread, which is not @API.

I brought this up in today's meeting, and it wasn't clear to any of us if/when modules need access to this.
skaldarnar's proposal was to leave this implemented, but at a permission level modules wouldn't be able to actually use, with a comment along the lines of "change this if we have a documented use case for it" or something like that.
(I don't think we can implement it exactly as proposed, because I don't think the @API system gives us per-method control, but we can make it package-private or something.)

how do you propose letting a module schedule something back on the main thread?

Try to take screenshot:
17:48:07.881 [main] ERROR o.t.engine.core.TerasologyEngine - Uncaught exception, attempting clean game shutdown
java.lang.ExceptionInInitializerError: null
	at reactor.core.scheduler.Schedulers.newParallel(Schedulers.java:545)
	at reactor.core.scheduler.Schedulers.lambda$static$4(Schedulers.java:1135)
	at reactor.core.scheduler.Schedulers.cache(Schedulers.java:1168)
	at reactor.core.scheduler.Schedulers.parallel(Schedulers.java:238)
	at org.terasology.engine.core.GameScheduler.scheduleParallel(GameScheduler.java:69)
	at org.terasology.engine.rendering.opengl.ScreenGrabber.saveScreenshot(ScreenGrabber.java:112)
	at org.terasology.corerendering.rendering.dag.nodes.FinalPostProcessingNode.process(FinalPostProcessingNode.java:173)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.terasology.engine.rendering.world.WorldRendererImpl.render(WorldRendererImpl.java:350)
	at org.terasology.engine.core.modes.StateIngame.render(StateIngame.java:214)
	at org.terasology.engine.core.subsystem.lwjgl.LwjglGraphics.postUpdate(LwjglGraphics.java:76)
	at org.terasology.engine.core.TerasologyEngine.tick(TerasologyEngine.java:509)
	at org.terasology.engine.core.TerasologyEngine.mainLoop(TerasologyEngine.java:460)
	at org.terasology.engine.core.TerasologyEngine.runMain(TerasologyEngine.java:436)
	at org.terasology.engine.core.TerasologyEngine.run(TerasologyEngine.java:402)
	at org.terasology.engine.Terasology.call(Terasology.java:183)
	at org.terasology.engine.Terasology.call(Terasology.java:67)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1933)
	at picocli.CommandLine.access$1200(CommandLine.java:145)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2332)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2326)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2291)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2159)
	at picocli.CommandLine.execute(CommandLine.java:2058)
	at org.terasology.engine.Terasology.main(Terasology.java:115)
Caused by: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "modifyThread")
	at java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
	at java.base/java.security.AccessController.checkPermission(AccessController.java:897)
	at java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)
	at org.terasology.gestalt.module.sandbox.ModuleSecurityManager.checkPermission(ModuleSecurityManager.java:48)
	at java.base/java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:748)
	at java.base/java.util.concurrent.ThreadPoolExecutor.shutdownNow(ThreadPoolExecutor.java:1405)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.shutdownNow(ScheduledThreadPoolExecutor.java:870)
	at java.base/java.util.concurrent.Executors$DelegatedExecutorService.shutdownNow(Executors.java:693)
	at reactor.core.scheduler.ParallelScheduler.<clinit>(ParallelScheduler.java:57)
	... 25 common frames omitted

Need to initialize schedulers eager. Or add warp this place with doPrivilegeAction
This is first call to scheduler and it fail because called from CoreRendering module

GameScheduler is marked @API. gameMain() provides access to scheduling on GameThread, which is not @API.

I brought this up in today's meeting, and it wasn't clear to any of us if/when modules need access to this.

Some discussion convinced me we do have a use case that requires this:
We want to allow modules to make OpenGL calls, so we must give them a way to run things on the thread that owns the OpenGL Context. (OpenGL works by pushing things on to a command queue, and you don't want to be mixing that up by doing that from multiple threads.)
While we don't currently have module code that makes use of GameThread for OpenGL this way, it's not much of a stretch for me to see that we might. Especially as we use Reactor to move more work off the main thread.

@keturn
OpenGL thread at my way currently.
CoreRendering is using opengl from modules.
It runs at main thread currently.

Try to take screenshot:

Oh, this is my fault! When I wrote the method that takes the task name, I didn't run it through the other method with the AccessController wrapping.
I'll try the eager initialization.

Try to take screenshot:

Oh, this is my fault! When I wrote the method that takes the task name, I didn't run it through the other method with the AccessController wrapping.
I'll try the eager initialization.

Eager works nice.
In graphics scheduler PR - parallel using for interval flux. For splashscreen render loop.

If you make changes to the suppression of alerts in a pull request, please note that theses changes will only be effective once that pull request is merged.

eh? that's weird, LGTM-bot.

Okay, I think the permission-modifying code is isolated enough and adequately commented now.
As for the matter of why we never had to add PermissionProperties before, I think it's a combination:
1. The old ThreadManager seems to have been running code outside the security context, so it's possible things were sneaking by, but mostly

2. There aren't that many things called from the module sandbox that require reading system properties.

I'm totally stumped on why wildcards don't work for PermissionProperties, but I am not worried enough about the maintenance cost of that list to put more importance on it for the time being.

I already tried wildcards :P


App.run() does not automatically exit / quit

Hi, thanks for this amazing jupylet.
Installed and now trying the examples to understand how to use jupylet.
On Windows 10, using Python 3.6, I can't close all examples started from IDLE.
The same goes for all examples run on jupyter. When I close the jupyter's browser tabs, all jupylet examples are still running.
The only way to close the examples are thru Task Managers.
Is there any flag to set so that App.run() can automatically exit / quit when its window / display is closed ?
Or maybe "exit/quit event" that needs to be handled ?
Thank you

Hi, when you close a jupyter tab the python kernel keeps running. This is expected behaviour. To shut it down you need to shutdown the kernel explicitly from the top menu.
I'll check out behaviour with idle.
Thank you for this report.

Do you mean that when running in IDLE if you click the top-right red [X] close button of the running game window, it stops but does not close?

Yes, in IDLE it won't stop.
And it would be great if it can stop in JUPYTER too, when tab is closed or with whatever command / event handler.
Thanks

Probably not quite related, but I found after some googling that in  pygame, I have to call pygame.display.quit() to exit the application cleanly, i.e. closing its main window.

indeed, this is what I tried and it works for me in IDLE.
if __name__ == '__main__':
    app.run(1/30)
    app.window.close()
    print("* DONE") # to verify that app has terminated


pre-push hook fails in v1.5.5 but works in v1.5.4 for some cases

:wrench: Summary
pre-push hook fails in v1.5.5 but works in v1.5.4 for some cases
Lefthook version
1.5.5 9b072e6622857ceb8d40a173ba39ae97afb35957
Steps to reproduce
I have tried the latest version of lefthook in https://github.com/hustcer/setup-nu repo:

The output of 1.5.5 does't look like 1.5.4, notice that this part is missing:
refs/heads/main e7fd469233d16703a7060d7b14feae806720659b refs/heads/main 26a18e5e4802a087f12cfcd83b832db8c2b1d07a
Pushing to remote...
----------------------------------

Expected results
1.5.5 should work the same as 1.5.4
Actual results

Possible Solution

Logs / Screenshots

LEFTHOOK_VERBOSE=true git ...

You are right. There was a change introduced in 1.5.5 - https://github.com/evilmartians/lefthook/pull/590. Lefthook doesn't implicitly pass STDIN to subcommands/scripts. To fix this please use use_stdin: true option explicitly.
I forgot that this might be a breaking change. Do you have problems after this change?

That works for me, thanks.


Global Path Service

Description

Resolves #49 Mock Global Path (Local Pathfinding)

I implemented a Global Path Service message.
The request is a Path type and the response is a bool type. Given how infrequently the global path is expected to change, the choice was made to switch global path from a topic to a service. This way, nodes such as MockGlobalPath and LocalTransceiver  (which have access to the global path) can send a "request" message containing the new global path to Navigate. Then Navigate can respond with True to acknowledge receipt of the message.
Verification
To verify my changes, I first ran the command "ros2 interface show custom_interfaces/srv/GlobalPath" and received the response:
Path global_path
HelperLatLon[] waypoints
float32 latitude
float32 longitude
bool response
So the service was built properly.
I then launched the local pathfinding package and the mock global path node (which will use this service) ran as expected, along with the navigate node.
Resources

Tutorial 2
Tutorial 1

Looks good, nice work Sean!


Add SCSS workaround for iOS issue in viewport-units

The viewport-units page links to a workaround by Patrick Burtchaell for iOS issues.
I've created SCSS mixins based on his idea, that include a comprehensive list of iOS devices.
This basically allow you to support iOS 7 devices by just replacing:
height: 50vh;

with:
@include vh(50);

I thought it could be useful to link it on caniuse!

Thanks!


Exporting all charts

Anyone has been able to figure out how would I be able to have an external handler for exporting all charts given array like in this example? http://jsfiddle.net/highcharts/gd7bB/
I have an array of configurations and would like to perform exactly the same action, but unable to successfully convert these 2 methods so they would suit for the angular directive.
Thanks.

@Vaelyr you would need to add the functions there and also the exporting dependency, it should work then, i tried my self and worked just as in the example.


Icicle/Flame view doesn't capture the right canvas height on some machine

I found the same view has incorrect height on my laptop while it is okay showing on a dell monitor.
Also - the main color for icicle/flame is too dark (dark red), not good for this visual, should do some adjustment on it.

This is correct on a dell monitor:

This is incorrect on my laptop:

this should be fixed by latest PR #23


Add DynamicPPL integration tests

This PR adds the Turing/DynamicPPL integration tests (from the test/turing folder in DynamicPPL) to this repository instead.
The main motivation behind this PR is to ensure that the tests added here are always run whenever a new version of Turing is released, thus making it impossible to release a version of Turing that contains a buggy version of DynamicPPL. See https://github.com/TuringLang/DynamicPPL.jl/issues/703 for more thorough explanation.
Some implementation details:

I made each test file its own module. This mimics the structure of the other tests in Turing.jl.
I had to add AbstractPPL and BangBang as explicit test depedencies (previously they were transitive deps).
Because the DynamicPPL integration tests run very quickly, it's probably OK for to run them under the 'everything else' bucket in the CI setup. Hence this PR makes no change to the CI.
I fixed a couple of deprecation warnings (specifically link!(vi, sampler) -> link!!(vi, sampler, model); the same with invlink!; and AutoReverseDiff(false) -> AutoReverseDiff(; compile=false)).

Otherwise, this is a straight copy paste.

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

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.5%) to 78.075%

Files with Coverage Reduction
New Missed Lines
%

src/mcmc/particle_mcmc.jl
2
93.24%

src/mcmc/gibbs.jl
6
77.38%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.5%

Covered Lines:
1225

Relevant Lines:
1569

💛  - Coveralls

Should be mergeable, I think, then I'll get rid of them from DynamicPPL.

In line with the above, I'm going to close this PR and open a new one


chore(master): release 0.33.0

:robot: I have created a release beep boop
0.33.0 (2024-07-12)
Features

add appspace region + tda token (9617574)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.33.0
:sunflower:


Allow hiding menubar

It should be possible to hide the menubar. Afterwards, pressing the Alt key should reveal it (just like Firefox and the RocketChat Electron app).
Franz is silently ignoring this feature request for a long time.
References

https://github.com/meetfranz/franz/issues/833 -- Unable to hide menubar

This seems to be the code portion in the Rocket-Chat Electron client that implements the autohiding:
mainWindow.setAutoHideMenuBar(!showMenuBar);
mainWindow.setMenuBarVisibility(!!showMenuBar);

... with the mainWindow being created in mainWindow/index.js.

User @khamer mentioned in https://github.com/meetfranz/franz/issues/833#issuecomment-514627530 that the following code works for hiding the menu bar, when run via the Developer Tools:
require('electron').remote.getCurrentWindow().setAutoHideMenuBar(true)

It's been a bit busy lately, but I'll allocate some time to address some of the open issues over the week-end 🙏

Hello,
I've just implemented this feature, similar to how RocketChat handles it:
The menubar is shown by default. In the menubar there is a new checkbox, "Auto-hide menu bar". Enabling this will set remote.getCurrentWindow().setAutoHideMenuBar(true), as suggested by you. This setting will persist between restarts as the value is stored in the app settings.

@vantezzen I like the idea of a release candidate (rc) pre-release that includes bug fixes / improvements until next official release version in sync with Franz. WDYT?

@kytwb Good idea, I would follow the naming scheme of Franz pre-releases (v5.X.X-beta.X). This way the pre-releases should be able to Ferdi's "Include beta versions" feature.

How do we know what the beta version is going to be? patch up? minor up?

Best is is to patch up, Franz won't minor up too often.
I also think we could release new patch versions of Ferdi without Franz having that version yet (e.g. 5.3.3) if we want to release new features for Ferdi. But I do still think that we should keep minor and major version numbers in sync with Franz.

LGTM! Will go with that 👍

Available in v5.3.3-beta.1.

The menubar is shown by default. In the menubar there is a new checkbox, "Auto-hide menu bar".

@vantezzen I can't find this option anywhere in the menu bar. (Note that I'm running Ferdi on Ubuntu Bionic using the GNOME desktop.) Where is this meant to be? Can you maybe post a screenshot here?
It would be weird if this feature were not platform independent. I don't think it has to be.

Same here... I can not find the option in the menu bar. Latest build on Arch Linux.

Reading commit e9746cbfe61819 I fear the implementation is totally macOS specific. The menu you have added the new menu item to does not exist on other platforms (guessing for Windows and other platforms here).
To make this platform independent I'd suggest to put the new item into the "View" menu. TBO, I don't know if that menu is shown on a Mac; maybe you can check where the "Enter Full Screen" and "Toggle Developer Tools" items are placed, and simply add the new item to that very same menu.

@bittner Thank you for your help, that was the exact problem. c6356d5 should have fixed the problem, hope you can check if it is fixed in the next beta build.

Hey. Menu item on Windows 10 isn't hiding menu, only when fullscreen (F11).

@pztrn I think this is a regression that has been adressed directly in Electron via https://github.com/electron/electron/pull/21449. The regression should be fixed in the next beta as we updated Electron to include its latest fixes in https://github.com/getferdi/ferdi/commit/06b26716fc90297b4227668c2d6a48e771e02ba7.

Has this been addressed yet? I'm on version 5.5.0 for Ubuntu 18.04 and I can't seem to find this option.

Sure, there's the "Auto-hide menu bar" option in the "View" menu, for quite some time. Works on GNU/Linux (Ubuntu Bionic).

On Windows the "Auto-hide menu bar" option is not working for me. I can't toggle it with the option under "View" even though the option itself displays properly, and pressing alt does not hide the sidebar. Can someone help with this?

On Windows the "Auto-hide menu bar" option is not working for me. I can't toggle it with the option under "View" even though the option itself displays properly, and pressing alt does not hide the sidebar. Can someone help with this?

I'm also having this issue. Is there some manual toggle fot it, once it's enabled, maybe? Or some other kind of trigger?

Still doesnt work on windows latest version.

The "auto-hide" doesn't work on latest but that's likely because for windows the menu is part of the title bar?
Don't know if that's the case for other OS's. But would explain why auto-hide doesn't work?
Normally the menu would be below it?

Yep, still not works, Would really love it to work


fix: move rn-svg also to peer deps

In my project using expo-dev-client we are using a different version of react-native-svg.
Thus we were getting the following error:
Invariant Violation: Tried to register two views with the same name RNSVGSvgView, js engine: hermes

by moving react-native-svg to peer deps everything is working as expected.

Same issue, I wish this PR to be merged soon.

Would love this to be merged too

Thanks for this PR 👍


[QHC-697] Adding Calibration checkpoints

TODOs of PR:

[x] Implement the main idea of the checkpoints algorithm
[x] Implement Comparison of fidelity in output dictionary and values in node.check_value
[ ] Test this, with concrete mock notebooks
[x] Write quick docstrings
[ ] Cover functionality with tests
[ ] Write better docstrings

Also some other checks:

[x] Make sure is backwards compatible, if no checkpoints are passed
[ ] Make sure weird cases indeed work correctly, like green checkpoints after red ones...

Remember to add a test of the diagnose method as I believe is not covered rn

After careful review, testing it with edge cases, hand to hand with @GuillermoAbadLopez, I believe it is good to go.
Leaving my aprove but adding software testing is needed to pass codecov and also test it on HW when available.


Add Sepolia color tokens to light and dark color libraries in Figma

Description
Add Sepolia to network colors section in light and dark.
Technical Details

Already in develop branch just need to pull and update via Figma tokens
Add documentation and swatch
Publish library
Release notification on appropriate Slack channels

Acceptance Criteria

networks/sepolia/default is available in Figma
networks/sepolia/inverse is available in Figma

References

Code equavalent PR https://github.com/MetaMask/design-tokens/pull/243
Storybook for reference https://metamask.github.io/design-tokens/?path=/story/colors-themecolors--light-theme-colors

Duplicate https://github.com/MetaMask/design-tokens/issues/252

Hey team! Please add your planning poker estimate with Zenhub @Akatori-Design @brianacnguyen @garrettbear @georgewrmarshall

Added these new colors in doc & figma style.
sepolia.default
sepolia.inverse
@georgewrmarshall Requested review for Light Theme & Dark Theme library branches.
Brand : Figma

Light Theme : Figma

Dark Theme : Figma


How to add STM32f412ZGT6 board in the Arduino IDE board manager?

I want to use Arduino IDE for STM32f412ZG for driving a led strip. I tried installing STM32 core in Arduino IDE but STM32f412ZGT6 is not available there. Can anybody help me with this issue? I want to have STM32f142ZGT6 as an option in the board manager.

Hi @vviicckkyy55
They are several way to do this:
https://github.com/stm32duino/wiki/wiki/Add-a-new-variant-(board)
or
https://github.com/stm32duino/wiki/wiki/Custom-board-based-on-a-core
You can have a look at the Generic_F412Rx variant which I guess should be closed to the ZG.
For questions please do not open an issue. You used the forum and this is the best way to get support.
https://www.stm32duino.com/viewtopic.php?f=12&t=618


cranelift-icache fuzzbug: "internal error: entered unreachable code: Invalid OperandSize: 16"

thread '<unnamed>' panicked at 'internal error: entered unreachable code: Invalid OperandSize: 16', [wasmtime/cranelift/codegen/src/isa/x64/inst/args.rs:1802](https://github.com/bytecodealliance/wasmtime/blob/d620705a323e3da59bd90473b4e627c8502b1255/cranelift/codegen/src/isa/x64/inst/args.rs#L1802):18

Discovered on oss-fuzz (https://oss-fuzz.com/testcase-detail/6676165556830208)
base64 -d to decode input:
I/0g////AAD/ARQE

cc @bnjbvr

According to cargo fuzz fmt cranelift-icache, this is the function being tested:
SingleFunction(
    function u0:1(i128 sext) system_v {
    block0(v0: i128):
        v1 = iconst.i128 0
        v2 = iconst.i64 0
        v3 = iconst.i32 0
        v4 = iconst.i16 0
        v5 = iconst.i8 0
        v6 = udiv v0, v0
        return
    }
    ,
)

Yep, this is an internal panic (not even an error propagated up to callers), and I'm afraid that the icache fuzz target, as it directly generates CLIF code (as opposed to other fuzz targets which generate wasm code translated to CLIF) will keep on hitting those things that haven't been implemented because they weren't useful for wasm. (I guess that's the same situation cg_clif would be facing if it was being fuzzed.)
The overall solution I can think of is to make all those Result and propagate up errors, but that might add lots of error checking in many places in the code base, so I wonder if it's worth doing. Do other people have other ideas that come to mind?

I guess that's the same situation cg_clif would be facing if it was being fuzzed.

Yeah, I think so too.

Do other people have other ideas that come to mind?

What first came to mind was implementing the i128 div/rem ops, but another solution is to prevent the function generator from building i128 ops. We've disabled ops in the past where the x64 backend isn't ready to deal with them yet.
Although if we do disable those ops, we shouldn't commit that PR just yet, for the same reasons as https://github.com/bytecodealliance/wasmtime/pull/4752#issuecomment-1224326672 It will mark all issues as fixed in OSS Fuzz and then probably create dups in the future.
This would solve this immediate issue, but not the overall solution of not panicking during compilation (which I think is a great idea, but probably not for now!)

Yes, the ideal answer here is that the verifier is the one gate that determines/defines what is valid CLIF; and if valid, then a correct backend can compile it. Anything less than that is in theory a temporary situation, a place where we either want to eventually fill out the backend or reduce the scope of valid CLIF at the verifier level (by changing the definitions in the meta crate).
I don't necessarily think introducing Results all the way up is the right answer here if the semantics we eventually want are that the verifier is the single source of acceptability; but what we can and should do probably soon is to try to close the gap between the verifier and backends' ideas of "acceptable".
If we don't expect to actually use i128.div or i128.rem anywhere, I'm ok with deleting this case by modifying the instruction definitions accordingly. It feels a little non-orthogonal, but then, maintaining actually-unused code is not a great feeling (or good use of time) either.

Based on the discussion in #4771, I think it's better to keep the 128-bit versions of division operators: cg_clif needs them and is currently working around their absence by generating function calls to compiler-builtins implementations. I like Afonso's suggestion of having Cranelift implement these instructions as libcalls, although it sounds like there are some potential issues there.


Added an article about Operating Systems

NOTE:

Please fill out the template below

Did you read the instructions in the README?

Y

Have you read the instructions in CONTRIBUTING?

Y

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?

Yes, I've written this article myself. I used the book Operating System Concepts by Silberschatz, Galvin, Gagne for reference, but wrote the article in my own words.

Merging it


Build Your First FAQ Chatbot

Tutorial URL: https://developers.sap.com/tutorials/conversational-ai-faq-chatbot-beginner.html
Please specify the step you are referring to Step 7. Test feature is not working and result in Cannot make request error

I just did the entire tutorial and it works OK.

Can you provide more information? Perhaps click on Debug in the Chat Preview or copy and past the JSON for more information.

Hi,
I'm getting the below error.

Thanks and Regards,
Saravana Kumar V

What action did you take immediately before getting this error? Just opening the test panel?

I just typed and sent Hi message

If the bot works, feel free to close the issue

Thank you so much for the immediate help !


AprsIsConnection should save which APRS-IS server it is connected to

Description
The AprsIsConnection object is used to connect to, authenticate with, and receive from APRS-IS servers. Given that we often use a rotating address, the actual connected server is often not known to the user. The server does identify itself in the auth response message, however.
This issue is to add parsing to AprsIsConnection to save that server name so that it can be exposed to the user and/or logged.
Acceptance Criteria

[ ] New nullable string property on AprsIsConnection for the name of the connected server
[ ] New logic to parse the authentication response message for the server name
[ ] Add a log command (likely LogInformation level) to log the name of the connected server
[ ] Add tests for parsing the server responses

I would like to contribute with this enhancement.  Please assign to me if you would like me to give it a go.  Thanks.

I would like to contribute with this enhancement.  Please assign to me if you would like me to give it a go.  Thanks.

@martelro Great, it's yours! Always happy to have help. 😊 Let me know and I'm happy to provide examples of server messages or discuss the change!

Thank you, @CBielstein for the assignment!
Yes, I'd be happy to see any examples of server messages.
Also, do you have any preference/convention on what the property should be named?  Would ConnectedServer or ConnectedServerName work?

@martelro Great! Here are some details!
Most of APRS Internet Service servers (to which this project connects) use the aprsc server software, so we can code to that. aprsc sends a response to a login request by a client with the following pattern: # logresp <clientCallsign> <verified|unverified>, server <serverName> (where anything in pointy brackets is replaced with an actual value)
I just ran several tests around the world to ensure this looked right and got the following response strings that you can use for examples and tests. (I used "N0CALL" string as a callsign (user ID) for connection. Consider it like "example.com" in that it points to nothing.)
Here are the result strings:

# logresp N0CALL unverified, server T2ONTARIO
# logresp N0CALL unverified, server T2PERTH
# logresp N0CALL unverified, server T2BRAZIL
# logresp N0CALL unverified, server T2NANJING
# logresp N0CALL unverified, server T2KA

With the server names from these being T2ONTARIO, T2PERTH, T2BRAZIL, T2NANJING, and T2KA, respectively.
You'll see that the AprsIsClient is already reading for login responses from the server (albeit a bit primitively with startsWith and contains checks, but it gets the job done 😅): src/AprsIsClient/AprsIsClient.cs#135 to set the connection state. You should be able to piggy back on that and parse out the server name.
One request is that should the parsing fail, we shouldn't throw an exception or fail. Given the distributed nature and tinkerer culture of amateur radio operators, I think we're better off with flexibility than rigidity in this project.
For testing, we have an appropriately mocked out test of server response here: test/AprsIsClientUnitTests/ReceiveUnitTests.cs#57. You can either follow that pattern to write a new test or (and this might be easier) update the test to be a [Theory] and use [InlineData] and pass in various logresp and expected server values. Let me know if you're unfamiliar with xUnit theories and I'm happy to point to some examples. 😃
As far as property name, I think either of what you suggested sound just fine. I'll leave it to your choice!
Thanks again for the help here! Again, please let me know if you have any questions!

@CBielstein Thank you for the helpful information!


1.1.0 Planning

High level plans for the next minor update.

Azure App Service integration

WebHostBuilder.UseAzureAppService()

Logging provider (aspnet/Logging#466)
Key Vault configuration provider (aspnet/Configuration#487)
Auto-enable IIS integration

Blob storage DataProtection key storage provider (aspnet/DataProtection#92)
B2C integration (Identity & Authn/z)
Kudu publish time improvements

WebListener server (for Service Fabric & public-facing ready self-host without reverse proxy and Windows 10 IoT/UWP support)
Startup time improvements

MVC startup time
MVC view pre-compilation
DI startup time (aspnet/DependencyInjection#372)
Reduction of JIT cost from startup via multi-core JIT and/or first-class CrossGen story

Runtime performance

Improving all TechEmpower scenarios (beyond Plaintext)
Standard middleware overhead improvements

Security middleware
Buffering middleware
Static files middleware

Dev experience improvements

Meta-packages & publish trimming (reduce dependencies version burden)
Improve developer experience compile & startup time
Templates improvement (dotnet new, etc.)
Improve Razor tooling design, e.g. not require a build to get Tag Helper IntelliSense to work

Re-enabling missing features & scenarios

Dependency Injection adjustments for better alignment with 3rd party DI containers
SignalR for ASP.NET Core (may target a preview in 1.1 timeframe)
Page-based development model on MVC (aspnet/mvc#494)
MVC view pre-compilation
MVC View Component Tag Helpers
Response caching middleware (aspnet/ResponseCaching#10)
WebSockets middleware
URL rewriting middleware (with mod_rewrite & URL Rewrite import) (aspnet/BasicMiddleware#43)

.NET Standard 2.0 alignment
DataProtection key ring storage provider (e.g. Redis) (aspnet/DataProtection#169)

@DamianEdwards Will you consider taking one off of "Future" and giving it some kind of reasonable milestone? ... "Future" is probably the "Black Hole" milestone. :smile:
Access to Service Control Manager / System.ServiceProcess.ServiceController
I need ServiceBase ported to Core to create a Windows Services app for Nano Server. Unless I get other/better guidance, I'm implementing my app as a GPO startup script hooking ...
[DllImport("Kernel32")]
private static extern bool SetConsoleCtrlHandler(EventHandler handler, bool add);

... which may work but is kind'a blah yuckola.

@GuardRex Your issue sounds like a .NET Core request and not an ASP.NET Core one and these plans seem to be ASP.NET specific.

Yes, it's CoreFX, but they won't answer. I'll withdraw the request for information here; however, I asked @DamianEdwards on the Standup if he would check on it, and he said he would ask since they won't respond on that issue.

Thank you for infos.
What about EntityFramework 1.1.0 planning ?

@ikourfaln take a look at https://blogs.msdn.microsoft.com/dotnet/2016/07/29/entity-framework-core-1-1-plans/

@rowanmiller thank you for sharing

I'm really curious about the

WebListener server ... Windows 10 IoT/UWP support

Is there more info to share about this topic?

@tomkuijsten any particular question? It's currently preview. We're working on releasing an RTM version. This is a Windows-only web server that sits on top of http.sys.

@muratg well I'm working on a custom webserver for our win10iot project. But it feels like wasted time if you will support these kind of features out of the box any time soon.

@tomkuijsten Feel free to check out dev builds (https://dotnet.myget.org/feed/aspnetcore-dev/package/nuget/Microsoft.AspNetCore.Server.WebListener). Related repo will hopefully be OSS soon too.

Thanks @muratg

Hi @DamianEdwards @rowanmiller , thanks a lot for providing more info; Would you include a refreshed Azure Mobile .NET Server SDK for the next release? I am currently building a .Net Core app but had to include the full .Net in order to communicate with the mobile SDK, and the code gets convoluted when mixing up EF Core and EF with ASP.NET Identity Core on top.

https://github.com/aspnet/Home/issues/1776

I really like where ASP.NET Core is going.
will

SignalR for ASP.NET Core

include the SignalR Client as well as the server?

@Genae we started work on updating SignalR, but it's not in 1.1.0.

Adding to @Eilon, there will be SignalR clients in addition to the server whenever we do release SignalR.

@muratg @Eilon any news about the Azure Mobile SDK?

I am not sure why but I was expecting to see an asp.net core 2.0 version to align with .net core/standard 2.0. It looks like it is done in the version 1.2 (so much versions, it is confusing!).
this seems to be the item .NET Standard 2.0 alignment. still expected in Q2? any release in Q3?

@Jonathan34 the next version of ASP.NET Core will be 2.0, and is aligned with all the other "2.0" wave of releases. We just updated all our version numbers yesterday from 1.2 to 2.0, so you should see that in builds later this week.

aaah, that makes more sense. Thanks!

What is the status of UWP support? Any early prototype available?

What is the status of UWP support? Any early prototype available?

Can you specific about what you are asking for?


Proposal: embed ci config in cloudformation template

At present taskcat config must be stored in a separate file, typically located in ci/taskcat.yaml combined with at least one  parameter mapping file ci/my-test.json relative to the project root.
Supporting having this metadata in the template itself would have several benefits:

Single file tests - any cfn template could be tested by taskcat without requiring any tool specific scaffolding. If metadata is not present taskcat just launches using defaults for stack parameters (potentially applying global overrides)
Linting rules to extend cfn-python-lint can be created for taskcat configs and parameters within templates
Cleaner, simpler setup for new users
tools that generate quick start projects have to worry about less
simplify code base, there is a lot of scaffolding to deal with where to find the config file. This assumes that support for standalone config file is dropped, which may not happen for some time.

Potential concerns with this approach:

how to define tests that involve multiple entrypoint templates would probably have to change. Scan folder structure for template files, any files with taskcat metadata get tested.
backwards compatibility with standalone configs introduces additional maintenance burden

Proposed metadata structure:
AWSTemplateFormatVersion: '2010-09-09'
Metadata:
  TaskCat::Config:
    MarketplaceAmi: false # Optional, defaults false
    Owner<EMAIL_ADDRESS># optional
    Name: quickstart-demo-redhat-openshift
    Regions: # optional, if not specified a single region is tested. Mutually exclusive to AllRegions
      - us-east-1
      - us-west-2
    AllRegions: true # reserved for future use, once taskcat can detect supported regions will launch tests in all regions supported by the resources in the template
    Reporting: true # optional defaults true
    Tests: # optional, if not specified a single test will be launched, using all defaults
      MytemplateMytest:
        ParameterInput: myparams # optional, if not specified stack will be launched with defaults
        # template_file not needed, we'll launch the template this metadata is embedded in
        Regions:
          - us-west-2
    ParameterSets: # must be present if ParameterInput is specified in Tests
      myparams:
        KeyName: blah # Use shorthand instead of cfn ParameterKey, ParameterValue
        RemoteAccessCidr: <IP_ADDRESS>/16

The presence of any metadata should not be required if taskcat is pointed to a particular template taskcat ./templates/my-template.yaml should launch 1 test in a predetermined default region (us-east-2 ?) using all defaults for parameters. If taskcat is pointed at a project path taskcat ./my-project/ then all templates found should be scanned for TaskCat::Config metatdata and if found tests defined should be run. A minimal config can be as little as:
AWSTemplateFormatVersion: '2010-09-09'
Metadata:
  TaskCat::Config:
    Name: quickstart-demo-redhat-openshift

cc: @aws-quickstart/aws_quickstart_team

This is a great idea!

If a project has multiple entrypoints we could add a new key to the global section to the metadata like 'stage: 0' 'stage:1' ...
So if a project has 3 templates which have taskcat metadata defined the stage variable can be used to determine the starting point.

This is a nice idea but please ensure a way to provide local override values that would not be part of the template. Also #122 needs per test override and/or a way to have per region input parameters.

@magic7s  - per-region input parameters are forthcoming in the v0.9 branch; For the moment, this issue isn't on our active roadmap, and at minimum is slated for consideration in v0.9.1

implemented in latest release


Live Query API

Stacked on #99
This added a new "Live Query" extension/plugin (our first one).
To use the extension it needs adding to the PGlite instance when creating it:
import { PGlite } from "@electric-sql/pglite";
import { live } from "@electric-sql/pglite/live";

const pg = new PGlite({
  extensions: {
    live,
  },
});

There are three methods on the live namespace:

live.query() for basic live queries. Less machinery in PG so quicker for small results sets and narrow rows.
live.incrementalQuery() for incremental queries. It materialises the full result set on each update in js. Perfect for feeding into React
live.changes() a lower level api that emits the changes (insert/update/delete) that can then be mapped to mutation in a UI or other datastore.

query()
This is very similar to a standard query, but takes an additional callback that receives the results whenever they change:
const ret = pg.live.query("SELECT * FROM test ORDER BY rand;", null, (res) => {
  // res is the same as a standard query result object
});

The returned value from the call is an object with this interface:
https://github.com/electric-sql/pglite/blob/a678da01e34519bbc5bd9545d5b1712f62b24430/packages/pglite/src/live/interface.ts#L49-L53

initialResults is the initial results set (also sent to the callback
unsubscribe allow you to unsubscribe from the live query
refresh allows you to force a refresh of the query

Internally it watches for the tables that the query depends on, and reruns the query whenever they are changes.
incrementalQuery()
Similar to above, but maintains a temp table inside of Postgres of the previous state. When the tables it depends on change the query is re-run and diffed with the last state. Only the changes from the last version of the query are copied from WASM into JS.
It requires an additional key argument, the name of a column (often a PK) to key the diff on.
const ret = pg.live.incrementalQuery(
  "SELECT * FROM test ORDER BY rand;", [], "id",
  (res) => {
   // res is the same as a standard query result object
  }
);

The returned value is of the same type as the query method above.
live.changes()
A lower level API that is the backend for the incrementalQuery, it emits the change that have happed. It again requires a key to key the diff on:
const ret = pg.live.changes(
  "SELECT * FROM test ORDER BY rand;", [], "id",
  (res) => {
   // res is a change result object
  }
);

the returned value from the call is defined by this interface:
https://github.com/electric-sql/pglite/blob/a678da01e34519bbc5bd9545d5b1712f62b24430/packages/pglite/src/live/interface.ts#L55-L60
The results passed to the callback are array of Change objects:
https://github.com/electric-sql/pglite/blob/a678da01e34519bbc5bd9545d5b1712f62b24430/packages/pglite/src/live/interface.ts#L62-L80
Each change has it's new values as part of the object along with:

__changed_columns__ the columns names that were changes
__op__ the operation that is required to update the state (INSERT, UPDATE, DELETE)
__after__ the key of the row that this row should be after, it will be included in __changed_columns__ if it has been changed.

To do:

[ ] Docs
[ ] Tests

any updates for this PR ?

Hey @jueinin
I need to rebase this on top of the new version we are building here #112, it will then get released with it. We are getting there.


57% regression in frame build times in platform_views_scroll_perf_ios__timeline_summary

skia perf: https://flutter-flutter-perf.skia.org/e/?begin=1683950885&end=1684165510&keys=X8a741e7c680a37c03fc977c2c02261c0&selected=commit%3D34816%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DiPhone_11%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253D99th_percentile_frame_build_time_millis%252Ctest%253Dplatform_views_scroll_perf_ios__timeline_summary%252C&xbaroffset=34817
Introduced in: https://github.com/flutter/flutter/pull/126758
Likely culporit: https://github.com/flutter/engine/pull/41463

cc @flar the author of the PR

Here is another regression from the same commit: https://flutter-flutter-perf.skia.org/e/?begin=1683950885&end=1684165510&keys=X34ccaba2b6b7299d719fde038d47d477&num_commits=50&request_type=1&xbaroffset=34817
FWIW it looks like there was some other positive aspects of this pr too like this: https://flutter-flutter-perf.skia.org/e/?begin=1683950885&end=1684165510&keys=Xd337031ff394b281da0d99630ea0ef09&num_commits=50&request_type=1&xbaroffset=34817
But they seem smaller in magnitude.  Here is a link to the whole array: https://flutter-flutter-perf.skia.org/t/?begin=1684066703&end=1684066705&subset=all


2.2.0 breaks 2.6 compatibility

(Original issue 1320 created by jonashaag2 on 2017-01-27T00:40:02.121107+00:00)
https://bitbucket.org/birkenfeld/pygments-main/src/0a472aa2e4daf82aa65d420829308a6bec7f4cca/pygments/lexers/_lua_builtins.py?at=default&fileviewer=file-view-default#_lua_builtins.py-291

(Original issue was assigned to birkenfeld)
(Original issue 1320 last updated on 2017-01-27T06:22:52.807664+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2017-01-27T06:22:52.804492+00:00)
Fixes #1320: restore Py2.6 compatibility
→ <<cset 76b98609a792>>


Add Adreno firmware to the packaged firmware for several boards

Process archives with Adreno firmware (e.g. proprietary.tar.gz) to extract Adreno zap shaders (and GMU for sm8150).

@sbanerjee-quic ping

Will conclude today

Hi @lumag we have tested this today, recipes-bsp/firmware/firmware-qcom-adreno.inc is meeting our needs as well.

Thanks, @sbanerjee-quic !


HTML Output Added

Added HTML output in Report Engine class
LIMIT variable added to methods.

Discussed on call - now part of #124 changes.


Strange power/refresh/paint issues with Ubuntu 15.10

Hey there, I managed to make a Lenovo ThinkVision LT1421 to work with the Displaylink driver on Ubuntu 15.10 on a Lenovo Thinkpad T450s, however I'm still running in issues that make the usage of the display very unreliable. I thought of sharing these findings with you in the hopes you can improve the driver.
I've originally posted some here
http://askubuntu.com/questions/753164/ubuntu-doesnt-look-like-sending-power-to-an-usb-port-used-by-a-device-that-uses
but I will summarize below:

The Displaylink driver will work only if the Intel Linux Graphics Driver is completely removed. Apparently this is due a modified libdrm package which evdi doesn't like. However, I wish this issue could be addressed, as the Intel drivers do in fact improve power management and resolve other issues I had with other programs and hardware acceleration (mainly Chrome).

Once intel drivers are uninstalled, the screen will work, but not properly, as detailed below.

if I start ubuntu, then connect the display with either 1 or 2 usb, it will work (i can see the refresh rate is better with 2) -- note this display comes with a usb Y cable (the kind that splits into 2-male USB plugs to draw more power if necessary, I tried in my tests to work with either one or 2 plugs connected, it doesn't make a difference)

if I disconnect the display, and reconnect it, it won't work. It may turn on and all, but it will refresh very slowly, to the point of being unusable.

if anything related to screen displays refreshes/restarts, such as the displaylink service or for example if I update my software for display calibration (DisplayCal), the screen will flash and will enter in this state where it doesn't paint properly

if I start my laptop with my display connected already (either to 1 or 2 usb) it won't work, it will only function in this bad state - sometimes it will even keep the same appearance as I left it since last reboot (same partially painted areas)

disconnecting and reconnecting again after the screen has entered in this state, no matter what, it will always bring it back in the same unusable mode. I have to restart ubuntu with the screen disconnected, then connect the screen and hope it won't hang

very interestingly, whenever the screen is in this failed state, it will show 2 extra displays in my "Screen" settings - one correctly labelled like Lenovo Thinkvision 14" and the other labeled as FNM 0"

Is this still reproducible with the Ubuntu 1.1.62 release that's just out? Thanks.

thanks! will try out soon and let you know

works like a charm on Ubuntu 16.04 Gnome, with 2 more external displays on a Thinkpad T450s, one on dp/hdmi another on vga
I am not running Intel proprietary drivers (technically not ready for 16.04 although there's a hack to install does from Vivid)... so I'm not sure how this would behave then
probably need to test more if there are power issues or strange things happening like with previous drivers on 15.04
thanks a lot! great job

ps if you need more details just let me know


Fix email link and a couple of typos.

@jasondavies many thanks for fixing these, really appreciate it 👍


[CARBONDATA-4185] Doc Changes for Heterogeneous format segments in carbondata

Why is this PR needed?
Heterogeneous format segments in carbondata documenation.
What changes were proposed in this PR?
Add segment feature background and impact on existed carbondata features
Does this PR introduce any user interface change?

No

Is any new testcase added?

No

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3609/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5354/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5407/

LGTM


NightCry [PCSE00895]

App summary

App name: NightCry
App serial: PCSE00895
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3020
Commit hash: https://github.com/vita3k/vita3k/commit/a4ded14b
CPU backend: Dynarmic
GPU backend: Vulkan/OpenGL

Test environment summary

Tested by: NightK15
OS: Windows 11 Pro Build 222621
CPU: Intel Core i5 12400F
GPU: AMD Radeon RX 6700 XT
RAM: 16 GB

Issues
Game runs flawlessly, scenarios render properly, but characters don't. There are vertex explosions present and character models aren't shown, not in the cutscenes, nor in gameplay (except for main character's model, which has many bugs). I'm guessing it would be Ingame+ or even playable if it weren't because of that. It gets worse when upscaling.
As a sidenote, same issue persists in android version using SD778G/Adreno 642L and Android 13.
Screenshots

Native resolution

2x Upscaled
Log
vita3k.log
Recommended labels
Ingame -

as of https://github.com/Vita3K/Vita3K/commit/c01996ec909f2332fe21f6209d25cf9bd8f48281, the character displays properly. Cant test it further.
Screenshots

Log
vita3k.log
Recommended Labels

Ingame +/Playable?

I accidently posted in Vita3k instead of compatibility, sorry about that. So, at Chapter 2 Scene 3, when you are suppose to go into the airduct, the game will show the loading screen and try to fade in the airduct but will crash. Here is the room with the airduct and a log. Can't progress any further in-game at this time.

vita3k log.zip


Add hub for realtime multiplayer

Initial logic pass. Doesn't yet have an actual client implementation (so serialization has not been tested sufficiently yet).
Potentially will be split out into its own project eventually, but made too much sense to keep it here while we can.

[ ] Depends on https://github.com/ppy/osu/pull/11127 (use local game reference to test)

Awesome feedback @bdach, thanks!


Fix for browser undefined in Chromium

I tried to launch the extension on a Chromium based browser and it failed with an error about "browser" being undefined, this fixes it.
If you know a better way to do this, or if I just did not build it correctly please tell me.

Yeah, I forgot about Chromium while adding this but fixed it locally already. As a heads up: it's enough to use chrome object in Firefox (at least for now), it exposes compatibility mode with callback based methods while browser exposes promise based methods


Introduce Hare-round clock

Motivation
Round timing in the Hare was based on timers and tickers integrated in the flow. This has two main downsides:

Round timing depends on the time it takes to run the code before the timer is set (this is mitigated by running most code in goroutines, reducing the time and variability of time before setting timers, but in environments with tight resources this could still be an issue).
It's practically impossible to mock/patch the timing mechanism for accelerated or tightly controlled tests.

Changes
This PR introduces a Hare-round clock that calculates when a round ends based on the time the layer starts and then sets precise timers internally based on those calculations. Each "consensus process" (Hare for a particular layer) has its own clock instance which is generated by a clock factory that can be easily mocked and patched in test code to achieve desired behaviors.
Test Plan

New unit tests for the new clock.
Hare unit tests now take advantage of the ability to patch the clock.
Existing Hare and general system tests.

TODO

[ ] Test changes and document test plan

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors try

bors try

bors try

bors try

bors try

bors merge


Investigate if we can delegate getClass() to real method

From<EMAIL_ADDRESS>on October 06, 2009 14:22:35
Perhaps using DONT_MOCK_NEXT_CALL
Original issue: http://code.google.com/p/powermock/issues/detail?id=176

From<EMAIL_ADDRESS>on October 06, 2009 12:23:54
Status: WontFix


Fixed Local .jsonl dataset loading

While Trying to load a local .jsonl dataset, It was'nt loading.
It was a simple fix, so here it is.

Had the same issue and resolved it with a similar change. Loading JSON objects separated by lines seems to now be supported by default by the "datasets" library as described in the documentation as with any an ordinary JSON file.

Thank you for the PR! Sorry for the delay.


Added position and zoom level options

Added additional options for positioning the magnify-lens as well as maintaining a zoom level.  Heres what it looks like working:

Thanks, I'll test and merge when time permits...

I just tested the changes and will not be merging for the following reasons:

All lens styling and positioning should be managed in the CSS file to keep the code lean.
The zoom level option fails when there are multiple images (try it on the demo).


Confirm box colored

Experimenting at improving readability of the warnings TerminalGuiDesigner produces.
Top is the current implementation (using MessageBox.Query).  Bottom is the one this PR introduces.  Its not perfect and I think more could maybe be done.  Leaving this as draft for now.

I know why this is happening. As the dialog has focus he uses the focus color to clear. I'm trying to fix that for only the most focused is cleared. But I'm getting problems with the TabView which is calling the base.Redraw which is clearing part of TabRowView. But I'm trying fix it.

Are you talking about a problem with the top image or the bottom one? I deliberately set the background color to black for readability against the yellow but now I look at it again it does look bugged/wierd.
Was just trying to spice up the message box and emphasize the message part.

Sorry, I thought that was the resulting after your hack to workaround for the https://github.com/gui-cs/Terminal.Gui/issues/2094 issue. After the fix the dialog was using it's focus color scheme and was more or less like that :-)

Closing this as I don't think its an improvement

Here is the new revamp based on Norton Commander:


Does "react/state-in-constructor" still make sense?

Does "react/state-in-constructor" still make sense?

It was only added last fall, so of course? It will forever make sense to me. Why do you think it wouldn’t?

Yes, but with https://github.com/yannickcr/eslint-plugin-react/commit/a312b16ea41203fc02054308f590f0e65784e2c3 is active in my projects. So until now it was turned off.
I think the default way should be without constructor anyway. What do you think?

It should not, because class fields isn't part of the language yet - it's stage 3.

Ok. You're right, as always. I'm using babel, so. Thanks anyway. For me we can close.

Even when it's in the language, folks may still have a style preference, so the rule won't stop making sense at any point.


Support enabling/disabling plans and stories

Move 'enabled' to the core attributes (L0 metadata).
Update the specification to cover all metadata levels.
Disable plans needing special setup by default.
Add test coverage for selecting/showing tests/plans/stories.
Use the canonical form for showing boolean (resolves #141).

This is quite an important feature, let's try to squeeze this into 1.4 as well.

/packit test


Bug: Black screen after clicking 'Unable to locate GAME'S_NAME'

Description of Problem or Question
@BenRQ, I've just noticed another bug with the version you shared.
After running Valkyrie app where you choose a game to play, I have a red text 'Unable to locate...' (I don't have Descent game). In the version, the text is a clickable button. When I click it, Valkyrie app minimizes and a Dialog to locate the game's EXE file opens. If I click Cancel and go back to Valkyrie, the app's screen is black and nothing can be done but ALT+F4 to close the app.
2.15 doesn't have this problem; the text is not clickable.

Thank you for spotting this, I will have a look


Refactor Cesium3DTileset traversal types into separate classes

This PR splits Cesium3DTilesetTraversal into two separate classes: Cesium3DTilesetBaseTraversal and Cesium3DTilesetSkipTraversal, which, along with Cesium3DTilesetMostDetailedTraversal, are all implementations of the Cesium3DTilesetTraversal interface. This new structure has the following advantages:

The flow is simpler: branching (based on the tileset.skipLevelOfDetail flag) is done once per frame, instead of several times throughout the traversal
The code is more understandable: each class is easier to read
The new interface is more extensible: to implement new traversal logic, simply add a new class Cesium3DTilesetNewTraversal

The traversal type is now selected in Cesium3DTileset.prototype.getTraversal, instead of being fixed inside Cesium3DTilePass.
The changes in the traversals themselves are probably easiest to understand by comparing Cesium3DTilesetBaseTraversal and Cesium3DTilesetSkipTraversal to the original version of Cesium3DTilesetTraversal—in this view, each new class is a simplified version of the original.

Thanks for the pull request @jjhembd!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks @ggetz for the review! I think I have addressed all your feedback

Looks great! Thanks again @jjhembd!


[BUG] Firefox v113 tabsbar alignment bug

Describe the problem
Tabsbar no longer displays under URLbar.

See https://github.com/vinceliuice/WhiteSur-firefox-theme/issues/23 for more info
Version
1.5.1
OS
Windows 11
Firefox Version
113
Install Options
none
Colour Theme
n/a
Additional info
No response
Please tick the boxes

[X] You are using a current version of the theme. (check the date associated with the version)
[X] You've checked that this issue hasn't already been raised

Have tested on MacOS and Windows, confirmed working on v113

https://github.com/AdamXweb/WhiteSurFirefoxThemeMacOS/releases/tag/v1.5.2 released with support for v113


Make main optional when compiling to WASM

Not sure this is idiomatic. However, I noticed, that when compiling to e.g. a yew app, which has a main, it conflicts with the existing main from kord. The double negation of not("wasm_no_main") is because I didn't want to make this a breaking change, which I guess a feature "wasm_main" would have been. Let me know if you prefer a feature "wasm_main" as part of the default-features perhaps, or something else entirely.

Actually, I think the right thing to do idiomatically is to delete the main entirely.  It probably shouldn't have a main, except for debugging, so maybe that's the best way to cfg it away.

Here's a variant without a main in WASM at all. One could add it for debugging. I have kept set_panic_hook in, however I'd also argue it is up for removal. A library user would do it themselves, so certainly a pub function seems out of place.
Maybe a good compromise would be to simply keep the original fn main but comment it out. No features and no set_panic_hook. This would be a breaking change, however.
What do you think?

Yeah, I think we should remove them altogether.


Invalid URL - sample queries

While doing some testing, I found out that one of the sample queries has an invalid URL.
Do we validate URLs on the GE side or DevX API? What and how do we validate?

We do it on the GE side. It displays this error if there is space within the the url. Spaces are only allowed on the search parameters, leading part of the url ( spacehttps://... ) and trailing part of the url as long as there are no search parameters (https:... (space)).

This particular url is triggering that error message because there is space between 'id', '|' and 'userPrincipalName.

https://github.com/microsoftgraph/microsoft-graph-devx-api/pull/949


Feature: Support for setting folder alias names in the sidebar

What feature or improvement do you think would benefit Files?
I'd like to request the ability to change the display name of pinned sidebar items (without changing the actual file name, like you could back in windows 7), and request a recent files sidebar widget for easier navigation
Requirements

This proposal will improve speed of accessing folders and organization

Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.5073
Comments
No response

Thank you for your feedback


hotfix: add commas in order to fix the editor warning when user copy/paste from doc

Just add extra commas in order to fix this behavior.

oh no! Clumsy me... thank you for. catching this <3


0.71 breaks multi-line TextInput focus accessibility for legacy renderer

Description
With React Native 0.71, multi-line TextInput fields are not announcing "is editing" to assistive devices when the field is activated. This results in assistive keyboards, like braille screen input, from working and renders the text input entirely unusable.
This is verified broken from 0.71.0 - 0.71.4 and is not broken in 0.70.x.
React Native Version
0.71.4
Output of npx react-native info
System:
OS: macOS 13.0
CPU: (8) arm64 Apple M1
Memory: 106.13 MB / 16.00 GB
Shell: 3.6.0 - /opt/homebrew/bin/fish
Binaries:
Node: 19.7.0 - /usr/local/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 9.5.0 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode: 14.1/14B47b - /usr/bin/xcodebuild
Languages:
Java: 11.0.11 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.4 => 0.71.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

Using Expo Go, open an app on a physical iOS device.
Navigate to a TextInput with multiline={true}
Double-tap to activate the field.
Observe that the screen reader does not announce "is editing".

Snack, code example, screenshot, or link to a repository
https://github.com/jgillick/rn-input-multiline-a11y-bug

Is this only an issue with iOS? Is there a reference to documentation of what we should be expecting?

A user of our app reported this on iOS, so I have yet to check Android.  As for reference documentation, I'm not sure, but I know that when the text field is focused and ready for input, VoiceOver is supposed to say something like "TextField, is editing, insertion point at end". I also understand that this prompts assistive keyboards to become enabled for typing -- without this, the assistive keyboards do not function.

Yesterday I was troubleshooting the issue further with the rn-tester app and noticed that when fabric_enabled is true in the Podfile, the text field works as expected and when fabric_enabled is false it's broken.

Yes, that's correct.

Using git bisect and the rn-tester app, I believe I've found the source of the bug.

Commit: https://github.com/facebook/react-native/commit/98d84e571df64b00e1ed3484923a1d8169dcfda1
PR: https://github.com/facebook/react-native/pull/34524

In TextInput.js, setting accessibilityState on RCTTextInputView (RCTMultilineTextInputView) causes the bug. I've tried commenting out individual state properties, but the bug persists even when passing an empty object to the accessibilityState property.
Hopefully, this helps.

Braille Keyboard is not working with Multiline input


Updates for Julia 1.0

hi. fixed at darwin room.

yahhh, I'm going to fix the LayerDicts.jl for 1.0

oh, rebased totally wrong...

Note that your scripts are failing because of package management deprecations.  You can see an example of some updated after_success lines here.

@wookay are you interested in fixing those or shall I?

@ExpandingMan , @iamed2 thanks. please fix anytime that you want. and It failed on LayerDicts.jl in Julia 1.0.

LayerDicts seems fixed, any chance we can merge that and re-run this?  It would be a shame to have to use forks of LibPQ, it seems in pretty good shape.

That's my to-do to-day

It's been taking a while to get tagged versions of dependencies but I think we're nearly there.


[sublime] cmd+d/ctrl+d should stop moving the main selection after it's added all instances

repro:

open https://codemirror.net/demo/sublime.html
put cursor on any of the instances of `Shift'
press cmd+d repeatedly

expected:
all the instances of Shift will be selected, and then the viewport will stop moving. this is the behavior of sublime (as well as VSCode & IntelliJ). not sure if it always was, but that is the behavior now.
actual:
all instances of Shift do get selected, but then the viewport keeps moving, because very time the command gets executed, the primary cursor moves.

There was code trying to implement this, but it was broken. Attached patch should help.


Upgrade to guid causes problems for people with the Upn claim in their cookies

We need to somehow flush people's cookies when they upgrade to the GUID version, because otherwise they may have a Upn claim which is not a GUID, it's a username.  That then causes a problem in UserExtensions when it tries to parse into a GUID.
See #407

Or perhaps we just need to change UserExtensions.Id to use TryParse

I guess we can check it the beginning of authentication if the Upn contains a valid GUID. If not reset the cookie and forward to login.
Here is how to remove the cookie:
http://stackoverflow.com/questions/5122404/how-do-you-clear-cookies-using-asp-net-mvc-3-and-c/5122611#5122611

We probably don't need to remove the cookie ourselves - if we just refuse to Authenticate at that point, then I suspect the framework will deal with it - it will do a redirect-to-login, which will then give us a decent cookie.

I'm closing this, because I think #488 fixes/avoids it


Formatting amendments

Hi,
I have made minor formatting amendements to make the tutorial more consistent. I think improves readability as well. Let me know your thoughts :-)
Poornima

Nice improvements @poornimanayar. I made one change if you want to view my commit
I'm doing the same thing in #21576, which is the Razor Pages version. It has alot of improvements, best practices, etc. I hope to have that published next week.

Hi @Rick-Anderson ,
Thank you, happy to help and I quite enjoy making docs contributions! I am working through that tutorial so I am making amends as I work through them. So what is the best way to make sure your PR and mine don’t clash? And you don’t have to keep updating yours as well?
Regards,
Poornima

If you're going through Razor Pages with Entity Framework Core I would hold off for another week until I merge and publish #21576

Nope, I am going through the MVC one!

In that case there are no conflicts, keep going. I highly recommend you go through the RP version when it publishes.

I will most certainly be doing that! Already had bookmarked it in my head :-)


hubble-relay: add Dockerfile and make target to build hubble-relay image

Coverage decreased (-0.003%) to 44.637% when pulling 1b6326d9cc2f60eb8914c6837874a24bd38534f2 on pr/rolinh/hubble-relay-docker into a4867b8af39085220aa2ecda3ced6573b9a43c72 on master.

test-me-please

Please update the release process documentation
@aanm Done, thanks for pointing out.

test-me-please


contiguous boundaries to multipolygons

Some attendance boundaries like Hirsch are noncontiguous. Let's represent these a multipolygons.
https://data.thefoiabakery.org/geography-63ff7a7/boundary?_sort=rowid&Name__exact=HIRSCH+HS

addressed.


org.xml.sax.SAXParseException

Getting org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 840; cvc-elt.1: Cannot find the declaration of element 'DespatchAdvice' on saxparser

Fixed in release 1.1.3


SEO HTML Head not being set in generated static files

Version
v2.12.2
Reproduction link
https://github.com/tunecino/nuxt-seo
Steps to reproduce

Create a new project
Go inside /pages/index.vue
Add head() { return { title: "xyz"} } inside page local settings as mentioned in docs.
Run yarn generate

What is expected ?
I expected to find <title>xyz</title> inside the generated file (/dist/index.html)
What is actually happening?
Found <title>example</title> instead. Which is my project name.
Additional comments?
The web page works fine in a browser, as far as javascript is enabled as it replaces the title tag correctly at certain point.
But if you disable javascript and reload the page, local settings are omitted and it shows the wrong title.
Even Lighthouse extension, which shows a great SEO score, if reports are expanded, you'll notice it parsed the wrong title.
I thought static pages won't require search engine bots to run any javascript. Is it a bug or did I miss something?
Thanks.

This bug report is available on Nuxt community (#c10508)

Because you are using mode: 'spa' (instead of 'universal')
https://github.com/tunecino/nuxt-seo/blob/master/nuxt.config.js#L3

Oh! My bad. That was what I did miss. Thank you @manniL


Colorized cli output is impossible to read

The dotnet ef cli tool colourizes output to make it easier to read. In some cases, it actually becomes impossible to read.
Here is what I see when I run dotnet ef migrations list on my machine:

I would expect the output to be always be readable, no matter the colorscheme in my terminal. In fact, I would rather have colourless output than something unreadable.
Steps to reproduce

Use a recent version of GNOME Terminal on Linux with the Solarized Dark colorscheme.
dotnet new web
Add the following to the csproj file:

    <PackageReference Include="Microsoft.EntityFrameworkCore.SQLite" Version="2.0.0" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0" />

Create a Model.cs file. Use https://docs.microsoft.com/en-us/ef/core/get-started/netcore/new-db-sqlite#create-the-model but introduce a typo.
dotnet ef migrations list
dotnet ef migrations list --verbose

Further technical details
EF Core version:
    <PackageReference Include="Microsoft.EntityFrameworkCore.SQLite" Version="2.0.0" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0" />

Database Provider: Microsoft.EntityFrameworkCore.SQLite
Operating system:
$ uname -a
Linux trull 4.12.9-300.fc26.x86_64 #1 SMP Fri Aug 25 13:09:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME=Fedora
VERSION="26 (Workstation Edition)"
ID=fedora
VERSION_ID=26
PRETTY_NAME="Fedora 26 (Workstation Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:26"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=26
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=26
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
VARIANT="Workstation Edition"
VARIANT_ID=workstation

IDE: cli:
$ dotnet --info
.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     fedora
 OS Version:  26
 OS Platform: Linux
 RID:         fedora.26-x64
 Base Path:   /usr/lib64/dotnet/sdk/2.0.0/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : N/A

Do you have bold disabled?
Try the following, and if some of the colors look the same, you may want to file a new issue on dotnet/corefx.
Console.ForegroundColor = ConsoleColor.Black;
Console.WriteLine("Black");
Console.ForegroundColor = ConsoleColor.DarkGray;
Console.WriteLine("DarkGray");
Console.ForegroundColor = ConsoleColor.Gray;
Console.WriteLine("Gray");
Console.ForegroundColor = ConsoleColor.White;
Console.WriteLine("White");

It should look the same as doing this in the terminal.
echo -e "\e[30mBlack\e[0m"
echo -e "\e[30;1mDarkGray\e[0m"
echo -e "\e[37mGray\e[0m"
echo -e "\e[37;1mWhite\e[0m"

We print verbose messages using DarkGray. It may also be the case that this is conflicting with your current theme.
Workaround
You can always workaround coloring issues by using --no-color. Output semantics can be preserved by also adding --prefix-output

Do you have bold disabled?

I dont think so.

Try the following

Here is what I see:

You can always workaround coloring issues by using --no-color

That works, even if it is a little cumbersome. Thanks.

Would it be possible to keep this issue open? There is a workaround, sure. But the underlying issue is still a bug and makes it harder for me to use the EF cli tooling.

We believe this is an issue with the theme: Dark gray (a.k.a. bold black) isn't visible.
Other utilities (like MSBuild) also output verbose messages in this color, so it seems external to EF. If there's a well-established pattern to ensure applications never output to color that would be invisible in the current theme, we're certainly open to taking a PR for this. Last I checked, however, .NET Core didn't implement the Console.BackgroundColor getter in a way that would be useful in this scenario, so we might need an issue in dotnet/corefx to unblock this work.

Why not do what the Console logger does? https://github.com/aspnet/Logging/blob/671af986ec3b46dc81e28e4a6c37a9d0ee283c65/src/Microsoft.Extensions.Logging.Console/ConsoleLogger.cs#L234