[C#] Client channel socket leaks unless read stream drained explicitly

This is still happening in v1.0.0, and I suspect has always been there.
I am using bidirectional streaming RPCs to talk to server. The server sends an exactly known number of messages back. Therefore  I am not reading the response stream to EOF, but rather end the call as soon as I get the data on the client.
If the call is disposed by the client without first reading the server stream to EOF, channel will not close its socket on shutdown, and a warning message is reported: W1020 18:40:55.407708 Grpc.Core.Channel Channel shutdown was called but there are still 1 active calls for that channel.
In my debugging case, the server returns exactly one message. I can trace the problem as far as this. The socket handle is locked via a call to ChannelSafeHandle.DangerousAddRef() without a matching release on call end. AsyncCallBase.ReleaseResourcesIfPossible() fails to call ReleaseResources() when called from AsyncCall.HandleFinished(), because the member flag readingDone is never set to true in this scenario.
I do not understand the logic of the code to tell if simply setting readingDone = true before the call to ReleaseResourcesIfPossible() from HandleFinished() is all that is missing. Maybe also creating a streamingReadTcs is required to complete possible pending reads? Is the call actually cancelled (in the gRPC sense) when Dispose() is called?
I work around the bug by calling MoveNext on the calls' reader in a loop until it returns false, which, in my case, it immediately does. But this a less than fantastic workaround.

Do you have a code snippet that replicates this?
What platform are you on? Also, from your description it seems it's about a call on the client side, is that right?
Btw, for testing various orderings in which operation completions can arrive to a call, we have this test:
https://github.com/grpc/grpc/blob/9f4e828343a78a24988e638cf7ac865cf3947cbe/src/csharp/Grpc.Core.Tests/Internal/AsyncCallTest.cs  (it runs the call handling logic against a mocked-out C core API and verifies that the behavior is as expected).
Would you be able to express your scenario as a test case there?

To understand this correctly, you basically read X (a known number) of responses on the client side and then you stop reading because you know that's all the messages that will be sent from the server?
I think if you are expecting X responses, it is a good practice to make sure that's the end of the stream and that there hasn't been an error:
// read X msgs here

GrpcPreconditions.CheckState(! await responseStream.MoveNext());  // check this is end of the stream.

Alternatively, you could use an extensions method from Grpc.Core.Utils and do
var responses = await responseStream.ToList();   // read all the responses
GrpcPreconditions(responses.Count == X); // make sure we got the expected num of responses
```
in which case you don't need to invoke any extra MoveNext() yourself.

Do you have a code snippet that replicates this?

I'll make one tonight, based on one of the examples. Should be easy.

What platform are you on? Also, from your description it seems it's about a call on the client side, is that right?

Client is a 32-bit process on Windows. Yes, the bug I see happens on the client side.

Btw, for testing various orderings in which operation completions can arrive to a call, we have this test

I do not see it verifying that a channel indeed has the call counter of 0 in this test. If possible, that should be tested in the Assert* methods.
Let me see if I can repro in the test.

To understand this correctly, you basically read X (a known number) of responses on the client side and then you stop reading because you know that's all the messages that will be sent from the server?

Oh believe me, this is complex. Both endpoints have the message flow that depends on previous server responses.
Client: I have this data for you.
Server: (1st message) Thanks, but I do not need it.
Client (disposes the call without reading to EOF).

Client: I have this data for you.
Server: (1st message) Please send!
Client: message, message, ..., EOF
Server churns for a while then (2nd message): Here are your results:...
Client (disposes the call without reading to EOF).

The second service has an even more complex protocol, where the server emits messages both in response to a flag in a client's message (at most once per client message, 0 to many per call), and a final response upon the end of client's send stream. This happens in real world time, client messages encapsulate real time data. Upon receiving the next reply from the server, the client can decide it has a good enough response and dispose of the call. The server (C++) sees the call as canceled just fine; but the C# channel has its call count permanently increased after the cancellation.

I reproduced the bug in the MR mentioned above. Simply break out of the while(ReadNext()) loop to have a channel socket to never be released even after channel shutdown. Exactly what I see in our production. I'll try to build a test for it.
Since my setup trims EOL whitespace, it's easier to look at the changes with ?w=1: https://github.com/grpc/grpc/pull/8471/files?w=1

I wrote 2 unit tests that reproduced the problem; the single-line change in AsyncCallBase.cs fixed it and did not break anything else. Please check if the fix makes sense to you, and let's wait for the integration tests to return. Please do not commit yet even if LG, I am going to give the change a run in our QA milieu.

I think this might be still an issue.

I still see this behavior as well. My code is essentially this. Like @kkm000, I currently work around the problem by changing the break to a continue such that the stream is always read to the end. But it would be nice not to have to do that, because this occurs in the context of shutting down an ASP.NET Core server, which is a time-sensitive operation, and at that point, I don't care about any pending messages that might be queued.

I can confirm that the socket leak can still be reproduced in the Route Guide example by breaking out of the loop in the ListFeatures() method before reading all the responses from the server.
I can also confirm that explicitly cancelling the call does mean that the socket is closed correctly - however there still needs to be one MoveNext() call after the cancellation.  Without the MoveNext() there is still a socket leak.  The call to MoveNext() after the cancellation does results in an exception being thrown with StatusCode.Cancelled that needs to be handled.
Here is the altered code in the ListFeatures() client method:
// create a token so that we can later cancel the call
var tokenSource = new CancellationTokenSource();

using (var call = client.ListFeatures(request, new CallOptions(cancellationToken: tokenSource.Token)))
{
	var responseStream = call.ResponseStream;
	StringBuilder responseLog = new StringBuilder("Result: ");

	while (await responseStream.MoveNext())
	{
		Feature feature = responseStream.Current;
		responseLog.Append(feature.ToString());
		//  Break out of loop to reproduce #8451
		Log("Exiting on first iteration to repro bug #8451");

		// Cancel the call
		tokenSource.Cancel();
		// Need to do an explicit MoveNext to get the Cancelled status otherwise
		// the socket is left open
		try
		{
			await responseStream.MoveNext();
		}
		catch (RpcException e) when (e.Status.StatusCode == StatusCode.Cancelled)
		{
			Log("Call cancelled by the client!");
		}

		break;
	}
	Log(responseLog.ToString());
}

It would still be nice if the Dispose() of the call did the cancel if necessary without it having to be explicitly done in the code. It looks like the behaviour would be different in the gRPC for .NET implementation but I've not tried it to confirm it - the Microsoft documentation says:

A gRPC call can be canceled in the client by passing a cancellation token with CallOptions.CancellationToken or calling Dispose on the call.

https://docs.microsoft.com/en-us/aspnet/core/grpc/deadlines-cancellation?view=aspnetcore-6.0

@tonydnewell, I'm just thinking aloud; not sure at all that this is doable. The CancellationTokenSource supports a callback, immediately invoked upon a call to .Cancel of it's "token" (internally, token source and token are a single entity, and the source itself and the token are logical interfaces on it, designed with a separation of concerns in mind). Can we somehow hack into this mechanism to make it perform the final try/catch in your example automagically? I.e. call MoveNext, catch and silently ignore the exception with the same when (e.Status.StatusCode == StatusCode.Cancelled)` clause, while letting other exception codes to fall through?
/cc @jtattermusch

@kkm000 I've investigated moving the cleanup logic to a cancellation callback but it appears the callback is invoked too early in the cancellation process - the exception is never thrown (MoveNext succeeds) and the socket still leaks.

Thanks for checking @tonydnewell! Too bad my wild idea didn't work out... :(

@tonydnewell  The fact that call.MoveNext() is still required after requesting call cancellation (regardless whether it's through cancellationToken or call.Dispose()) seems odd to me. It would be good to investigate a bit more why that is the case - and subsequently fix it.
For calls that don't get cancelled, there is little we can do about not requiring the MoveNext() calls - this is simply a side effect of how the C# API has been designed and of how the C-core native component works.  Requiring the user to drain the response stream for non-cancelled calls makes sense IMHO, but it would be nice if this wasn't strictly required for cancelled calls.
One thing to check:

if you sleep for a few seconds after call.Dispose(), does the call still leak? This could also be a "race" between the call's cancellation taking place and the channel being shutdown.

A delay does not make a difference - it is not a race condition.
The problem is that readingDone is false in AsyncCallBase.ReleaseResourcesIfPossible() therefore the resources are not released (Dispose is not called on the native call).  If I set readingDone to true if cancelRequested is true in ReleaseResourcesIfPossible() then the resources are released and there is no socket leak.  I don't think it is a problem to say reading is done (and maybe loosing some date not yet read) as the client has already decided they are giving up with the call.
However I've not yet determined whether this is the correctly place to set this - maybe it should be in AsyncCall.HandleFinished() instead, or if there are other consequences, or whether other types of call are affected. I will investigate further.
Note: cancelRequested is true for both an explicit cancel and also when Dispose is called on the call in the client - so an explicit cancel is not needed

I think we should double check that the doc-comments are clear about the situations in which it's required to drain the call.responseStream (currently it's "always") and update the docs if not.

we can try to come up with a partial fix where requesting the call cancellation (either through triggering the cancellationToken or call.Dispose()) wouldn't remove the need to drain the call.ResponseStream. This needs to be done carefully since it can break call's behavior in other situations.

@jtattermusch can close - the fix is in release v1.46.5


Adding Adjusment variable to to_hijri.

The hijri dates depends on countries, so it will be great if you added Adjustment parameter that can help us to tune the output.
Example:
hijri_date = Date.today.to_hijri   #equals = Friday 17 Ramadan while it is 16 Ramadan in Egypt.
so needed add would simple be
hijri_date = Date.today.to_hijri(-1)  #equals = Friday 16 Ramadan

the issue has been resolved in v0.6.0


(maint) Merge master to main

       Attempt to assign a value to unknown setting :serverport
     # ./lib/puppet/settings.rb:1483:in `set'
     # ./lib/puppet/settings.rb:179:in `[]='```


b080 STM32G030 breakout

Hey Marie,
good job, I have a few suggestions:

connect pin 15 of the STM to the INT pin of the SPI connector. I believe all pins of the STM32G0 can be configured as ints. Some SPI devices rely on the int pin to signal to the microcontroller that they have new data to read.
Add 10k pull-ups to 3.3V on all reset pins, if downstream devices have the reset connected and we leave it floating it could cause problems.
some designs will want the 32.768kHz clock but others may want a faster clock (48MhZ for example) make sure the footprint you use fits both alternatives.


repo reorg: codify if/when core code can depend on extensions

We likely can never compile out tcp_proxy and hcm. Need to codify this and check in CI.

Ideally we can have check_format validate this via Bazel dep graph analysis.

should we just leave them in core and say they're required plugins, or leave them in extensions and just comment / doc that they're special cased?


Automated Package Upgrade

:tada: This PR is included in version 13.0.64 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cannot get dictionary to change output

See
http://stackoverflow.com/q/33268289/2561126

Does the word 'tor' appear in the word list?
Tesseract will never try to correct a valid word.

We do not provide support for custom training (you need to demonstrate bug with traineddata from google).
You can use tesseract user forum for instead. I would suggest to search that forum before asking question.


C++: Searching

Hackerrank problem link
Provide your hackerrank problem link here.
https://www.hackerrank.com/challenges/sherlock-and-array/problem?isFullScreen=true
Issue Checklist

[x] If you have previously contributed to this repo, you declare that you have not made a pull request for more than one issue in this repo till now.
[x] Your forked repo is up-to-date with the the origin remote.
[x] Have you checked that the hackerrank problem you are raising is not already present in the repo?
[x] Have you checked that the hackerrank problem you are raising is not raised by or assigned to another contributor?

Hacktoberfest Contributor

[x] Are you a Hacktoberfest Contributor?

Any other Changes?
If you are raising an issue with some more changes, please provide the details here.

Please assign this issue to me. @Riddhi9570

Hey, @Csrivastava003  Thanks for raising an issue!
I've assigned you the issue and you may please go ahead!
Happy Coding😃!

The pull request has been made regarding the issue.

@Riddhi9570  Thanks for allowing the contribution for Hacktoberfest.
Would love to contribute in the repo after Hacktoberfest too.

@Riddhi9570 Thanks for allowing the contribution for Hacktoberfest. Would love to contribute in the repo after Hacktoberfest too.

@Csrivastava003 Thanks for your valuable contribution! Would love to see you after hacktoberfest! Happy Coding😃!


#18 chore(Automatic Release): Add automatic release with semantic-release.

This change alters the Travis build process adding a last step that automatically publishes a new
release on NPM following semantic versioning definition.
re #18

Excellent! 👏

:tada: This PR is included in version 4.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question: Change default color-scheme?

Pretty much what the title says.
Personally, I didn't use the default color-scheme for a very long time. The only reason I kept it for so long is because it is more recognizable than other themes on USo. I haven't seen too many people change the colors, so I'm not sure what to do.
This is what it could look like. Colors go in line with my other themes, but I'm open to changing them.

Vote here!

Hello again @vednoc , as promised before, people can customize your nice work with a nice chrome extension, would you mind testing it please?
https://chrome.google.com/webstore/detail/wa-web-plus/ekcgkejcjdcmonfpmnljobemcbpnkamh

Hey @tinyCoder32, please keep to the scope of this and other issues.
I appreciate your work but I cannot test your extension for two reasons:

I don't use proprietary extensions.
I keep the extension list down to the minimum.

Hey @tinyCoder32, please keep to the scope of this and other issues.
I appreciate your work but I cannot test your extension for two reasons:

I don't use proprietary extensions.
I keep the extension list down to the minimum.

Hi @vednoc
I totally understand, i'm sorry.
Thanks for your efforts.

I think it'd be a great idea to do this as some sort of theming switch if that's possible. I really like the original scheme with the blue, I think it's a little less harsh than black and orange.

Since the day i installed this theme, i changed the vars to this black and orange theme (my favorite colors).
As the meme say:

I see this as an absolute win

@richardcane: I think it'd be a great idea to do this as some sort of theming switch if that's possible.

It is, but it's a bit complicated to set up properly and I'd have to do it for every single theme I have. That is exactly why I made the theme switcher and it works great, though it does need more color-schemes. :smiley:

I mean if we're talking userstyles wouldn't it be as simple as having a theme dropdown with different preset:root element values?

I mean if we're talking userstyles wouldn't it be as simple as having a theme dropdown with different preset :root values?

It would be possible to have multiple :root presets, the problem is having too many of them -- the reason why theme switcher exists. Another problem that rises is, for the upcoming rewrite in stylus-lang, I don't know of a good way to accomplish that.

Assuming that dropdown had no given theme selected, defer to theme switcher or default theme (black and orange).

Default theme would be the case. Theme switcher will always override colors IF it's installed after the WhatsApp theme -- if necessary, that could be prevented in many different ways.

Having had a quick look at the theme switcher it looks like each individual option can be modified, but there are no full-suite named themes to choose from? Purely from a UX perspective, for users that just want something that "looks functional", that can be a bit overwhelming.

I agree, the UX sucks, but I don't expect majority of people to be changing colors all the time -- for me it's more of a set it and forget it type of thing. Not sure whether I should group the colors since this way people can mix and match colors from various color-schemes.

I think it's a good idea to align the defaults with your other projects.

It's gonna be alright. I really appreciate the input from the community and I'm fine with whatever is chosen. At the end of the day the theme switcher is doing an awesome job for me personally, and it's super easy to adjust colors for those that want to do it. :smile:


[joy-ui][Input] Typescript "No overload matches this call" on preact

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://stackblitz.com/edit/vitejs-vite-rew1hg?file=src%2Fmain.tsx
Steps:

Create a vite preact project from their default preact template
Install @mui/joy @emotion/react @emotion/styled
Create an Input component
Run a build with npm run build

Current behavior 😯
During a build TypeScript throws TS2769: No overload matches this call.
❯ npm run build

><EMAIL_ADDRESS>build
> tsc && vite build

src/app.tsx:15:10 - error TS2769: No overload matches this call.
  Overload 1 of 2, '(props: { component: React.ElementType; } & Pick<React.InputHTMLAttributes<HTMLInputElement>, "disabled" | "required" | "autoComplete" | "autoFocus" | "onClick" | "onChange" | "onKeyDown" | "onKeyUp" | "onFocus" | ... 7 more ... | "id"> & { ...; } & InputSlotsAndSlotProps & Omit<...>): any', gave the following error.
    Type '{ required: true; autoFocus: true; }' is not assignable to type 'IntrinsicAttributes & { component: React.ElementType; } & Pick<React.InputHTMLAttributes<HTMLInputElement>, "disabled" | "required" | "autoComplete" | "autoFocus" | "onClick" | ... 11 more ... | "id"> & { ...; } & InputSlotsAndSlotProps & Omit<...>'.
      Property 'component' is missing in type '{ required: true; autoFocus: true; }' but required in type '{ component: React.ElementType; }'.
  Overload 2 of 2, '(props: DefaultComponentProps<InputTypeMap<{}, "div">>): any', gave the following error.
    Type '{ required: true; autoFocus: true; }' is not assignable to type 'IntrinsicAttributes & Pick<React.InputHTMLAttributes<HTMLInputElement>, "disabled" | "required" | "autoComplete" | "autoFocus" | "onClick" | "onChange" | "onKeyDown" | ... 9 more ... | "id"> & { ...; } & InputSlotsAndSlotProps & Omit<...>'.
      Type '{ required: true; autoFocus: true; }' is missing the following properties from type 'Pick<React.InputHTMLAttributes<HTMLInputElement>, "disabled" | "required" | "autoComplete" | "autoFocus" | "onClick" | "onChange" | "onKeyDown" | "onKeyUp" | "onFocus" | "onBlur" | ... 6 more ... | "id">': disabled, autoComplete, onClick, onChange, and 11 more.

15         <Input required autoFocus />
            ~~~~~

  node_modules/@mui/types/index.d.ts:105:7
    105       component: C;
              ~~~~~~~~~
    'component' is declared here.

Found 1 error in src/app.tsx:15

Expected behavior 🤔
Project builds
Context 🔦
None- I need to be able to make an input component that builds with preact and vite
Your environment 🌎

npx @mui/envinfo
(stackblitz)
  System:
    OS: Linux 5.0 undefined
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
  Browsers:
    Chromium: 117.0.5938.92 (Official Build) (64-bit)
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.17
    @mui/core-downloads-tracker:  5.14.11
    @mui/joy: ^5.0.0-beta.8 => 5.0.0-beta.8
    @mui/private-theming:  5.14.11
    @mui/styled-engine:  5.14.11
    @mui/system:  5.14.11
    @mui/types:  7.2.4
    @mui/utils:  5.14.11
    react:  18.2.0
    react-dom:  18.2.0
    typescript: ^5.0.2 => 5.2.2

It turns out that all of HTML attributes are required properties:
https://stackblitz.com/edit/vitejs-vite-jvvyqb?file=src%2Fapp.tsx,vite.config.ts
Not sure what's the root cause of this but it's likely because of preact. I am reluctant to fix this with Partial<>.

i do not seem to understand this issue can you explain a bit more @siriwatknp @K3das

Is this issue open to contribute?
siriwatknp already proposed a solution with partial<>


Getting setDecorations on invisible editor warning

Have the following code in an extension, which will set decorations on visible editors every 100ms.
setInterval(() => {
    const decoration = vscode.window.createTextEditorDecorationType({});
    vscode.window.visibleTextEditors.forEach(e => {
        e.setDecorations(decoration, []);
    })
}, 100);

If you click around the explorer and open up different files, you'll see setDecorations on invisible editor warnings in the dev tools. There's no apparent way I could avoid them.

A bit worse:
setInterval(() => {
    const decoration = vscode.window.createTextEditorDecorationType({});
    vscode.window.visibleTextEditors.forEach(e => {
        e.document;
    })
}, 100);

Instead of a warning, there's an NPE error the console:
shell.ts:433 Cannot read property 'document' of undefined: TypeError: Cannot read property 'document' of undefined
    at /Users/joao/.vscode-insiders/extensions/cssho.vscode-svgviewer-1.3.0/out/src/extension.js:92:62
    at e.invoke (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:5:1151)
    at e.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:5:4638)
    at t.$acceptModelChanged (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:11:22027)
    at t.e.handle (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:10:24348)
    at s (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:7:28264)
    at h (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:7:28941)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

@joaomoreno I see the warning but I cannot repo the NPE. Is there some secret step missing?

Ok - I might push another change that we don't explode but make editor.document be undefined when the editor detached.

I have a similar issue in my extension which is related to this issue.
Its hard to reproduce, but it happens when closing files. Very rarely an invalid document will returned by   vscode.window.visibleTextEditors that will have a lineCount of 0. So now my code looks like this:
vscode.window.visibleTextEditors.forEach((editor) => {
            if (editor.document && editor.document.lineCount !== 0 ) {

            }
        });

Maybe related to this issue, maybe I should make a new one?

@CoenraadS steps to repo?

It is very difficult to repo.
I created a branch of my extension stripped to the core as a kind of minimum repo scenario:  https://github.com/CoenraadS/BracketPair/tree/repo
I made a video of it occurring (happens at the end of video): https://youtu.be/IvDztPCKtVw
Basically open and close files until it occurs. But how long this takes is random since I don't know the exact trigger.

I think I found the original cause: https://github.com/Microsoft/vscode/issues/20867

Verified that 'Getting setDecorations on invisible editor warning' is gone. But I see now 'TextEditor disposed' messages.
@jrieken Is that ok?

Yeah, that's part of a larger issue I have scheduled for March


Handle REST power on vs Redfish used to boot the host in IPMI inband path

IPMI inband internally call REST at the moment to boot up the host and then login. This will need fix to handle both REST vs Redfish
Login To OS Host
    [Documentation]  Login to OS Host and return the Login response code.
    [Arguments]  ${os_host}=${OS_HOST}  ${os_username}=${OS_USERNAME}
    ...          ${os_password}=${OS_PASSWORD}

    # Description of arguments:
    # ${os_host} IP address of the OS Host.
    # ${os_username}  OS Host Login user name.
    # ${os_password}  OS Host Login passwrd.

    REST Power On  stack_mode=skip  quiet=1 <----------

    SSHLibrary.Open Connection  ${os_host}
    ${resp}=  SSHLibrary.Login  ${os_username}  ${os_password}
    [Return]  ${resp}

https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-test-automation/+/48846


Bug: [Command] spark routes for routes containing {locale} return unknown filters

PHP Version
8.2
CodeIgniter4 Version
4.4.1
CodeIgniter4 Installation Method
Git
Which operating systems have you tested for this bug?
Linux
Which server did you use?
cli-server (PHP built-in webserver)
What happened?
When using placeholder {locale} in Config/Routes.php and $routes->useSupportedLocalesOnly(true), the spark routes command does not output the required result.
// Home page with locale
$routes->get('{locale}/', 'Home::index', ['as' => 'homepage']);

// Home page without locale
$routes->get('/', 'Home::index', ['as' => 'default_homepage']);

Behavior before (<unknown>):
$ ./spark routes

CodeIgniter v4.4.1 Command Line Tool - Server Time: 2023-10-01 10:52:23 UTC+03:00

+--------+-----------------------------+--------------------+-------------------------------------+----------------+---------------+
| Method | Route                       | Name               | Handler                             | Before Filters | After Filters |
+--------+-----------------------------+--------------------+-------------------------------------+----------------+---------------+
| GET    | {locale}                    | homepage           | \App\Controllers\Home::index        | <unknown>      | <unknown>     |
| GET    | /                           | default_homepage   | \App\Controllers\Home::index        | csrf           |               |
+--------+-----------------------------+--------------------+-------------------------------------+----------------+---------------+

Expected:
$ ./spark routes

CodeIgniter v4.4.1 Command Line Tool - Server Time: 2023-10-01 10:52:23 UTC+03:00

+--------+-----------------------------+--------------------+-------------------------------------+----------------+---------------+
| Method | Route                       | Name               | Handler                             | Before Filters | After Filters |
+--------+-----------------------------+--------------------+-------------------------------------+----------------+---------------+
| GET    | {locale}                    | homepage           | \App\Controllers\Home::index        | csrf           |               |
| GET    | /                           | default_homepage   | \App\Controllers\Home::index        | csrf           |               |
+--------+-----------------------------+--------------------+-------------------------------------+----------------+---------------+

Anything else?
I think the solution should be here
https://github.com/codeigniter4/CodeIgniter4/blob/0cd39937d7a8dbd8074237596024adce0fe3c2af/system/Router/Router.php#L439-L457
https://github.com/codeigniter4/CodeIgniter4/blob/0cd39937d7a8dbd8074237596024adce0fe3c2af/system/Commands/Utilities/Routes.php#L120-L122
During the execution of the command, we get a route. Because {locale} will not be in the allowed
// Route
array(4) {
  'method' =>
  string(3) "get"
  'route' =>
  string(13) "{locale}"
  'name' =>
  string(13) "homepage"
  'handler' =>
  string(28) "\App\Controllers\Home::index"
}

// sample URI
string(8) "{locale}"

This is a known limitation.
If you can fix it, feel free to send a PR.

I have not yet figured out how to separate the command from the working routing. I think it's doable

However, this is not simple.
This is because a route containing a regular expression may not uniquely determine the filters to be applied.
In the case of locales, the locales are determined when excluding unsupported locales. However, if, for example, a global filter excludes only a specific locale, the filters applied will be different only for that locale.
The worst case scenario is that the filters displayed in spark routes may not actually be applied.
I think it is better to show <unknown> than that.

 Especially when ~100 routes have a locale

If the filter excludes /fr/home, but allows /en/home. Can we add details like !csrf !toolbar, if presumably the filter doesn't work for all routes?

It may be a solution. At least, !csrf toolbar is better than <unknown>.

Sorry, I did not understand what is the issue.
$routes->useSupportedLocalesOnly(true) changes the output.
This is a bug.
--- a/app/Config/Routes.php
+++ b/app/Config/Routes.php
@@ -5,4 +5,6 @@ use CodeIgniter\Router\RouteCollection;
 /**
  * @var RouteCollection $routes
  */
-$routes->get('/', 'Home::index');
+$routes->useSupportedLocalesOnly(false);
+$routes->get('/', 'Home::index', ['as' => 'default_homepage']);
+$routes->get('{locale}/', 'Home::index', ['as' => 'homepage']);

$ php spark routes

CodeIgniter v4.4.3 Command Line Tool - Server Time: 2023-11-07 11:23:54 UTC+00:00

+--------+----------+------------------+------------------------------+----------------+---------------+
| Method | Route    | Name             | Handler                      | Before Filters | After Filters |
+--------+----------+------------------+------------------------------+----------------+---------------+
| GET    | /        | default_homepage | \App\Controllers\Home::index |                | toolbar       |
| GET    | {locale} | homepage         | \App\Controllers\Home::index |                | toolbar       |
+--------+----------+------------------+------------------------------+----------------+---------------+

--- a/app/Config/Routes.php
+++ b/app/Config/Routes.php
@@ -5,4 +5,6 @@ use CodeIgniter\Router\RouteCollection;
 /**
  * @var RouteCollection $routes
  */
-$routes->get('/', 'Home::index');
+$routes->useSupportedLocalesOnly(true);
+$routes->get('/', 'Home::index', ['as' => 'default_homepage']);
+$routes->get('{locale}/', 'Home::index', ['as' => 'homepage']);

$ php spark routes

CodeIgniter v4.4.3 Command Line Tool - Server Time: 2023-11-07 11:24:24 UTC+00:00

+--------+----------+------------------+------------------------------+----------------+---------------+
| Method | Route    | Name             | Handler                      | Before Filters | After Filters |
+--------+----------+------------------+------------------------------+----------------+---------------+
| GET    | /        | default_homepage | \App\Controllers\Home::index |                | toolbar       |
| GET    | {locale} | homepage         | \App\Controllers\Home::index | <unknown>      | <unknown>     |
+--------+----------+------------------+------------------------------+----------------+---------------+

I sent a PR #8167 to fix this.


2 - Choice between STS and OpenPAYGO Token

Define the protocol that will be used to analyse the entered token.  Switch statement is currently being considered.


Error handling during seeding/upgrading fails

I was attempting to perform an update to the latest code and ran into an issue with the seeding/updating of the database.
The problem I was having was a misconfiguration in our system but I think I found a bug in the error handling code in models.js
`        self.count().exec(function (err, count) {
        if(err) {
            sails.log.error("Failed to seed " + modelName, error);
            return callback();
        }`

Should this be the following instead?
`        self.count().exec(function (err, count) {
        if(err) {
            sails.log.error("Failed to seed " + modelName, err);
            return callback();
        }`

Yes man! Thanks for the notice! Cheers!

    Message Title

                         pantsel/konga created an issue

                                     Infoview Helpdesk /  DESK-93808

                                      Re: [pantsel/konga] Error handling during seeding/upgrading fails (#133)

                                        Issue Type:

                                      Request

                                        Assignee:

                                         Unassigned

                                        Created:

                                         16-Nov-2017 2:58 PM

                                        Reporter:

                                     pantsel/konga

                                        Yes man! Thanks for the notice! Cheers!
                                        — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

                                                         Helpdesk Contacts

                                                             Phone:

                                                         07 3014 2222

                                                             Fax:

                                                         07 3014 2200

                                                             Website:

                                                         http://infoview.com.au

                            This is an automatic notification from Infoview Central. If you wish to contact the helpdesk regarding this request please reply to this email. Please do not edit or remove the email subject.
                            The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Infoview Technologies Pty Ltd.

    Message Title

                         pantsel/konga created an issue

                                     Infoview Helpdesk /  DESK-93811

                                      Re: [pantsel/konga] Error handling during seeding/upgrading fails (#133)

                                        Issue Type:

                                      Request

                                        Assignee:

                                         Unassigned

                                        Created:

                                         16-Nov-2017 4:40 PM

                                        Reporter:

                                     pantsel/konga

                                        Closed #133 .
                                        — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

                                                         Helpdesk Contacts

                                                             Phone:

                                                         07 3014 2222

                                                             Fax:

                                                         07 3014 2200

                                                             Website:

                                                         http://infoview.com.au

                            This is an automatic notification from Infoview Central. If you wish to contact the helpdesk regarding this request please reply to this email. Please do not edit or remove the email subject.
                            The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Infoview Technologies Pty Ltd.

Glad to help, always nice to try and contribute... also I have turned off notifications from our helpdesk system so it doesn't reply to this (I hope)


docs: rename spreadsheet-blueprints to demo-blueprints

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Docs update

What is the current behavior? (You can also link to an open issue here)

The demo blueprints are mentioned as spreadsheet blueprints.

What is the new behavior (if this is a feature change)?

The blueprints are now explicitly called demo blueprints instead of spreadsheet blueprints.

Other information:

I also added a few more links to the Rundown Editor. There's also some unrelated style and formatting changes caused by the auto formatter.

Codecov Report

Merging #644 (d5222f8) into master (7034ed7) will increase coverage by 32.96%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           master      #644       +/-   ##
============================================
+ Coverage   67.03%   100.00%   +32.96%
============================================
  Files         262         2      -260
  Lines       18059        46    -18013
  Branches     4081        16     -4065
============================================
- Hits        12106        46    -12060
+ Misses       5911         0     -5911
+ Partials       42         0       -42

Impacted Files
Coverage Δ

meteor/server/api/ingest/genericDevice/actions.ts

...teor/server/migration/deprecatedDataTypes/1_0_1.ts

packages/server-core-integration/src/lib/random.ts

meteor/server/api/blueprints/context/index.ts

...r/server/api/blueprints/context/watchedPackages.ts

meteor/server/migration/1_12_0.ts

meteor/lib/collections/BucketAdlibActions.ts

meteor/lib/api/mediaManager.ts

meteor/server/migration/api.ts

meteor/lib/collections/RundownLayouts.ts

... and 250 more

Continue to review full report at Codecov.

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

@nytamin I think documentation-only pull requests that are already relevant should not follow our normal git branching strategy because that could delay updates to documentation significantly. I'll bring this up for internal discussion.

@nytamin I think documentation-only pull requests that are already relevant should not follow our normal git branching strategy because that could delay updates to documentation significantly. I'll bring this up for internal discussion.

Shouldn't we essentially treat it as a bugfix, since well, it's fixing what amounts to a bug in documentation?

@nytamin I think documentation-only pull requests that are already relevant should not follow our normal git branching strategy because that could delay updates to documentation significantly. I'll bring this up for internal discussion.

Shouldn't we essentially treat it as a bugfix, since well, it's fixing what amounts to a bug in documentation?

Agreed, let's do that (and also discuss it internally)


Update supported platforms in README

The list of supported platforms in README.md may be outdated.
Issue initially communicated in: 13dca6e9fe5c2618ae34a5e75d69356b77284642.

We always update the list near next release.

For example, it is claimed that Fedora 30 is supported, but PowerShell LTS (7.0) uses .NET 3.1, which no longer supports this distribution.

You can look https://devblogs.microsoft.com/powershell/announcing-powershell-7-1/ where Fedora 30 was mentioned as supported OS for PowerShell 7.1.
PowerShell release process and support lifecycles are under full control by MSFT team.

You can look https://devblogs.microsoft.com/powershell/announcing-powershell-7-1/ where Fedora 30 was mentioned as supported OS for PowerShell 7.1.
PowerShell release process and support lifecycles are under full control by MSFT team.

That blog post appears to be based on https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/docs-conceptual/PowerShell-Support-Lifecycle.md which states:

"When a platform version reaches end-of-life as defined by the platform owner, PowerShell Core will also cease to support that platform version."

Clearly there are platforms on that list that are end-of-life and should therefore be removed.

I've opened dotnet/core#6431 to clarify .NET support for Fedora 32.

@iSazonov Please could you reopen?

Official support for official MSFT distributives is a completely MSFT team internal process. They will update the documents during the next release.


bower install freeze on boilerplate

Running a fresh install of ng-seed.
After executing npm install, than bower install starts, and than it freezes on boilerplate. Stuck and not progressing.
bower validate      4.3.0 against git://github.com/h5bp/html5-boilerplate.git#~4.3.0

Closing as this is pretty old and there was no response from OP (so hopefully this is not an issue any more). If anyone is still having problems, please open a new issue.


TXT files don't automatically download (like other files)

In the data tab -> data table, when downloading a referenced file, if the file is a TXT then the file will not automatically download. Instead, it will open a new tab. Not sure if this is something we can change, but wanted to check.

Unfortunately, it doesn't appear to be something we can easily change. We definitely looked into this


Button to show .err last lines shows .out instead

In GitLab by @jvegas on Mar 22, 2021, 12:02
Just what the title says, the button to show the last lines of the .err is showing the last lines from the .out instead
I detected it on http://bscesweb04.bsc.es/autosubmitapp/experiment/t0j2 when cheking the output from the failed ESMVALTOOL jobs

In GitLab by @wuruchi on Apr 7, 2021, 12:27
Hello @jvegas
Thank you for reporting it. It's one of those weird bugs that happen when modal ids get mixed together somehow.
The contents of the log are correct though, it is the name of the file that was not being properly updated.
Anyway, it is fixed and will be deployed soon.


Support for pyodide 0.17.0

This PR adds support for Pyodide 0.17.0 released on April 21, 2021.

flare.js generally works a little different than before (it mostly backward compatible)
get-pyodide.py loads pyodide 0.17.0 and minimal package set
Added loading animation assets/css/is-loading.svg
Use is-loading.svg instead of is-loading.gif in style.css
Reformatted style.min.css into style.css
Renamed init.js to flare.js as it is the flare initialization routine

The necessary adjustments for the vi are minimal so far.
There is only one thing that bothers:
Until now I could leave this in the main.html:

In case that was missing, the fallback was used.
the new pyodide.js still tries to resolve via the unavailable path and so throws an error.
Is there any possibility to fix that, so i can use the old behavior, else i have to enforce a local pyodide for the vi.

you're right, I'll take a closer look on this. We could also solve it differently so that flare.js generates the specific include for Pyodide.

already started, use pyodide-0.17 from this repo for further development


How to Build a Nearly Headless WordPress Website

Topic Suggestion
How to Build a Nearly Headless WordPress Website
Proposed article introduction
A static site or a headless web app works just as well as a traditional WordPress theme. WP themes make up the majority of all WordPress-powered web pages on the internet today. Caching layers and dependency optimizations on most of these sites help them operate quickly. However, as web developers, we've figured out how to get better outcomes for our clients' websites than the competition. By using a headless WordPress platform, several sites have seen improvements in their loading times, user interactions, and page transitions.
In this tutorial, we will talk more about how we can build a nearly headless WordPress website.
Key takeaways
Traditional WordPress websites
Headless WordPress websites
Introducing Nearly Headless WordPress
How it works
Keeping parity between how the page renders in PHP and JavaScript.
Detect when a page should run in compatibility mode
Extending the app
Article quality
This will be a detailed, unique, and good guide on building headless WordPress websites. I will use simple language and illustrations for the readers to understand faster and in a better way.
References
N/A

I don't think this article adds much value from what is covered in the official documentation. Feel free to suggest another topic. Thanks


MemPoolErrorException in MempoolValidationContext

(The following didn't hang the node but happened 3 times before clearing itself and continuing - I had to hit continue on the debugger)
Ran the node for 20 mins in debug mode and got the following exception:-
Exception of type 'Stratis.Bitcoin.Features.MemoryPool.MempoolErrorException' was thrown.   at Stratis.Bitcoin.Features.MemoryPool.MempoolValidationState.Throw() in C:\Projects\Stratis\StratisBitcoinFullNode\src\Stratis.Bitcoin.Features.MemoryPool\MempoolValidationContext.cs:line 124
at Stratis.Bitcoin.Features.MemoryPool.MempoolValidator.CheckMempoolCoinView(MempoolValidationContext context) in C:\Projects\Stratis\StratisBitcoinFullNode\src\Stratis.Bitcoin.Features.MemoryPool\MempoolValidator.cs:line 671
at Stratis.Bitcoin.Features.MemoryPool.MempoolValidator.<>c__DisplayClass32_0.b__0() in C:\Projects\Stratis\StratisBitcoinFullNode\src\Stratis.Bitcoin.Features.MemoryPool\MempoolValidator.cs:line 437
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state

Are you talking about just when running in the debugger? Yes the mempool validator does throw exceptions that are eaten (basically invalid transactions that are filtered out). So you will want to turn off breaking on that exception in the debugger in the mempool validator or you will go bonkers hitting F5 😁 - especially on Bitcoin testnet.
Looks like that specific one is a transaction in which not all inputs exist. Can confirm with Dan but I think this is a legit case where you've gotten a transaction before you've received all it's inputs so it has to reject it.

Yes this is legit (perhaps we should have designed it differently) but its not a bug.

I am also having this same issue.. Quite annoying.


How to change home directory when running yarn?

I have a nodejs project and using yarn to build it. For some reasons, the user home directory is read-only. When I run yarn install in my project I get below error:
error An unexpected error occurred: "EACCES: permission denied, mkdir '/home/jenkins/.config'".

it seems that yarn is trying to access user home directory. The environment is setup by CI so I can't change the home folder permission. How can I restrict yarn only use current application directory?
I know for npm I can use below environment varaible but I am not sure about how to do that in yarn.
export npm_config_cache=npm-cache

Not related.


Add jax support!

TFP has a JAX-backed impl that's fairly functional at this point (note, some distributions are still coming together).
If you wanted to add support for running on JAX as well, it might just be a matter of tfp = tfp.experimental.substrates.jax.

Good idea!  I'm thinking I might add JAX as a third backend.  Might not get to it for a while honestly but I've heard lots of good things about JAX so hopefully eventually!


More minimalistic design

The current version of the notebook looks like this:

The design has in my opinion too many bounding boxes and appears still overloaded. The tool buttons attract too much attention and appear misplaced when overlapping the editor field. Therefore I suggest the following more clean and simplistic design:

In summary:

Line numbers are outside the cell and appear only at the selected cell.
Controll icons are on the right and also appear only at the selected cell.
The background for the Python code is dark as in standard Jupyter-Notebooks and white for the output (at aleast for the bright color theme). This is more optimal for plots that normally have white background.
The execution counter (like [2]) is inside and grouped together with the timing information so that it is not confused with a line number.

Or even more puristic:

I think the design simplicity of VS Code is one of the major selling points that makes this project is so succesful. I think people would love to see this also in the notebook.

Well, actually, beeing a purist I have no justification for that round circles around the buttons:

I close this issue since the design is meanwhile improved. The tool box is now more discreet on the right which is less annoying. I would still like to have less elements such as lines or buttons which are neither code nor output.


ci: fix new lints, introduced in 1.78

this new lint was silenced , it introduces 30+ locations to fix:  https://rust-lang.github.io/rust-clippy/master/index.html#/multiple_bound_locations ; it has no automatic fix yet with cargo clippy --fix

Looks perfect.
I would also consider fixing multiple_bound_locations instead of applying #![allow(clippy::multiple_bound_locations)].


Correctly parse process stat data under linux

Hopefully closes #81
Currently I have no access to a linux box to test the patch. Hopefully it will pass the test.

Could you add a CHANELOG entry?

this PR has been extended by additional checks in #86  and won't be merged

@immon Ah, good to know. Should we close this on in favour of #86 then?


Deployment failed.  Correlation ID: bb94429f-7083-0000-4482-d9a6c875955e in Appcat log

Category

[x] Error

My .sppkg works fine in local work bench when I deploy it in my application it shows me Deployment failed.  Correlation ID: bb94429f-7083-0000-4482-d9a6c875955e. Please let me know how to figure out this issue to deploy my webpart.
Curious to know why this webpart works good in work bench, but failed deployment.

Could you please share more details about environment, nodejs version details

Also, please check whether the app catalog & the tenant was created in same language (like English language ).

node --version
v8.17.0
npm --version
6.13.4
And this is React webpart for Microsoft Sharepoint online lastest. Please let me know I you need something else.

I have another webpart which is working fine and that webpart is cloned from git repo, but even fresh new welcome react webpart project after running yo @microsoft/sharepoint (without adding code) throw me same error after deploying it in my app cat log.

Steps I have dove are below:

yo @microsoft/sharepoint
(without adding new codes in my project)
gulp bundle --ship
gulp package-solution --ship

Even tried

yo @microsoft/sharepoint
(without adding new codes in my project)
gulp clean
gulp bundle --ship
gulp package-solution --ship

But still facing the issue in my app cat log

Firstly, I have tried in node version 10. However, issue does not solved by downgrading the node version to 8 too.

as you mentioned that you cloned webpart from git repo, could you please follow the respective repo instruction and check whether any  dependency

I have tried with with same installation steps, and the project cloned from git is different web part, but having issue with simple HelloWorld fresh new webpart.

@piraga
Do you eventually have whitespace or other special characters in the name of the folder where you develop your Webpart? If yo, remove them, use only [a-zA-Z0-9], then repackage and reupload your solution. This may also count for parent folders of your solution (don't know exactly if that's the case).

What version of SPFx?
The template for a new issue had a section about context information you could provide that helps in troubleshooting. We need all that information to help... SPFx version, Node version, environment, browser, SharePoint environment, etc.
Please help us help you...


Show deprecated and since doc metadata on mouse over

Enum.chunkis an example of where the deprecation information could be useful. then is an example for since.

Hi, @josevalim
Is anyone working on this now? If not, I'd like to take a shot on this one.

Pls go ahead!

Closed via #852.


Custom events not sending

If I watch the network console when I fire this code - nothing happens:
'''
this.$gtm.push({ event: 'apply', slug: this.slug })
'''
It looks like push isn't sending data to GTM

Same here, custom events are ignored.
Also i can see the page-tracking fires on first call even though in my understanding it shouldn't as the default for pageTracking is set to false.
However, the logs look fine for custom events.

@cprobert Did you find out the issue?


Questions related to requestedAttributes

I have two questions related to the requestedAttributes (in the sp-settings)

I'm trying to figure you how the requestedAttributes (configuration on the sp-settings) works. I've included it in the sp-configuration, but they only seem to be present in the metadata and not in the generated SAMLRequest. What am I missing?

I would expect that if the requestedAttributes (the ones marked required) on the sp are validated somehow in the processing of the SAMLResponse. Meaning if an attribute that is marked required:true is missing in the attribute statement of the SAMLResponse some sort of error is going to be added to the errorlist. Is this something that is supported and I just can't figured out? If it is not supported would it be a nice improvement?

That is how SAML works, the SP defines in its metadata what attributes it requires so any IdP trusting on this SP can record it and provide such attributes on the SAMLResponse. That why the requestedAttributes attributes appear on the SP XML metadata and not in the AuthNRequest.

See AuthNRequest schema:  http://www.datypic.com/sc/saml2/e-samlp_AuthnRequest.html
Anoher Reference: StackOverflow thread: https://stackoverflow.com/questions/35873526/saml-request-attributes-in-authnrequest

That depends on how the IdP was implemented. IdP could try to satisfy your requirements and in case of not be able to provide them:
a) Cancel the authentication and return a non Status=Success SAMLResponse
b) Return the attributes available and leave the SP to validate them and raise the errors.

I believe b) is the most implemented scenario.
The SAML toolkit has no idea about the Attribute Mapping (the relation between how the IdP names the user attributes and how the SP expects such attribute names), Sometime the Mapping is done on the IdP side, others on the SP sides, so isn't
ideal to implement such validation at the toolkit level and I consider that is something that needs to be handled at the app level, where there is the info about app user accounts
At the end gonna be a matter of extract the attributes with auth.get_attributes() and then apply the Attribute Mapping changes to the array if need to be applied and later validate that the required attributes are in the array returned and contains data.

@pitbulk Thank you for your quick and informative reply.

I had been reading this technical specification from OASIS which is an extension to the standard SAML protocol I now see. This however would then probably not be widely supported and thus not worth including in the SAML toolkit.

I did not take into consideration that the mapping could happen a the idp-side, which in the case of requested attributes which specify the attribute name, would not make much sense to me. I'm relatively new to the SAML protocol and it's implementations so I'm not yet very familiar with it's implementation conventions.

Again thank you for your explanation. It is very much appreciated.


Amend Perun Integration: Remove payment address to allow for fiat payment

As discussed with @semuelle , we would like to amend the proposal to allow for payment in fiat.

Closed for now due to some recent updates.


chore: update poetry.lock using Poetry v1.1.15

I've updated poetry.lock (with poetry lock --no-update, i.e. without resolving the dependencies) using Poetry v1.1.15 which sorts extras and extras dependencies, resulting in a more deterministic lock file and hopefully smaller diffs upon changes. In order to benefit from the improvement in Poetry v1.1.15, only Poetry v1.1.15+ should be used for updating dependencies from now on.

Strange, the PR was merged but there's no commit in master. 🤔

Indeed, the commit in the timeline event links to the "spelling fixes" one 🤔

It looks like the changes were applied though.


Note unary expressions

^, &, | are never mentioned, can maybe combined with #130

This issue was moved to dlang-tour/english#19


Publish Calm CLI to NPM

Feature Request
We currently can't use the CLI without cloning and building the repo.
We should publish the CLI to npm under the finos NPM community.
This will allow users to install it globally to their local system.
Todo:

Setup NPM Token in the architecture-as-code repository secrets
Create GitHub action which publishes to NPM on merge using the token

The CALM CLI has now been published to npm - https://www.npmjs.com/package/@finos/calm-cli


Taking too much time with download and play

I'm using https://github.com/zmxv/react-native-sound to implement audio playing in my app. I also you react-native-fs to download the file from the hosted URL to the file system and then play it locally.
The issue I'm facing right now is the latency. The audio takes more than usual to download and play. For a file that takes normally 15 seconds to download, my app takes around 30 sec.
Have anyone else faced a similar problem?

@SoorajChandran can you provide the code that you are using to download and play?

I find that the app takes a long time to buffer on the network. Is there particular policy we can use to play with a reduced buffer?

yes i am facing same issue..
can any one, please assist me to reduce playing time...


Removes double-version management in the dockerfile

Previously, we always had to update the versions twice in the
Dockerfile. This caused indirection and maintenance as the files
included are relatively static. By squashing this, we get a single
version, and also the ability to add support for things like mem or
elasticsearch more easily.

cc @gena01 @klingerf @abesto

I'm not going to be able to squash this right now, as testing the revised syntax for getting curl is saturation my network. Will finish this up tomorrow.

network gods smiled on me.. current commit is ready to go I think, unless combining the RUN statements is very important

:shipit: Great, thanks for making that update.

okie.. let's see if this  doesn't break https://travis-ci.org/openzipkin/docker-zipkin-java/builds/130981747


Don't have access to clone repo

on git clone git@github.com:builderbook/builderbook.git
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

works fine over HTTPS (just an issue over SSH)

@orpheus Thanks for creating this issue. To follow up on it - the problem is likely that SSH keys were not properly set up for the particular machine you were using. In that case, HTTPS will work.
If you want to use SSH, here is Github's tutorial on generating new SSH keys:
https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/
Then you need to add the keys to your Github account:
https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/


Delete stats panel

I think we should just delete the stats panel entirely for now.
Right now it is providing inaccurate info, nobody understands the way the stats work, and multiple PRs have failed to fix it.

This can hopefully be replaced by a solution that is not based on copy pasted THREE.js stats.

I fixed it. It was a small issue of not calling the info reset at the right place due to which my PR failed.

https://github.com/webaverse/app/pull/2335 was reverted due to bugs.

Will just use this one https://github.com/webaverse/app/issues/2285
as one issue and close this one.


QEMU launch NodeOS failed

Hi,
I'm new to NodeOS.
I'm trying to build NodeOS.
use npm install to get and build NodeOS
But, when i use qemu-system-x86_64 to launch NodeOS
When linux kernel initial, it stay on :
.........................
[   20.437522] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   20.524758] ip_tables: (C) 2000-2006 Netfilter Core Team
[   20.652660] TCP: cubic registered
[   20.751746] Initializing XFRM netlink socket
[   20.815748] NET: Registered protocol family 10
[   20.884425]  sda: unknown partition table
[   21.045296] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   21.092952] sd 0:0:0:0: [sda] Attached SCSI disk
[   21.133849] sit: IPv6 over IPv4 tunneling driver
[   21.184698] NET: Registered protocol family 17
[   21.232982] Key type dns_resolver registered
[   21.351737] registered taskstats version 1
[   21.422624]   Magic number: 15:958:761
[   21.446296] console [netcon0] enabled
[   21.476595] netconsole: network logging started
[   21.642662] ALSA device list:
[   21.653663]   No soundcards found.
[   22.132709] Freeing unused kernel memory: 5948K (ffffffff81a72000 - ffffffff82041000)
[   22.216699] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
It can not launch successfully !!
What can i do !?

It should work out of the box. Could you be able to start only the
barebones layer and check the output?
El 22/01/2015 02:51, "joeking11829"<EMAIL_ADDRESS>escribió:

Hi,
I'm new to NodeOS.
I'm trying to build NodeOS.
use npm install to get and build NodeOS
But, when i use qemu-system-x86_64 to launch NodeOS
When linux kernel initial, it stay on :
.........................
[ 20.437522] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 20.524758] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 20.652660] TCP: cubic registered
[ 20.751746] Initializing XFRM netlink socket
[ 20.815748] NET: Registered protocol family 10
[ 20.884425] sda: unknown partition table
[ 21.045296] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 21.092952] sd 0:0:0:0: [sda] Attached SCSI disk
[ 21.133849] sit: IPv6 over IPv4 tunneling driver
[ 21.184698] NET: Registered protocol family 17
[ 21.232982] Key type dns_resolver registered
[ 21.351737] registered taskstats version 1
[ 21.422624] Magic number: 15:958:761
[ 21.446296] console [netcon0] enabled
[ 21.476595] netconsole: network logging started
[ 21.642662] ALSA device list:
[ 21.653663] No soundcards found.
[ 22.132709] Freeing unused kernel memory: 5948K (ffffffff81a72000 -
ffffffff82041000)
[ 22.216699] input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/serio1/input/input3
It can not launch successfully !!
What can i do !?
—
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/92.

Hi piranna,
I do "npm start" at node-barebones
it look like same prolem.
...................................
[   22.994589] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   23.023719] sit: IPv6 over IPv4 tunneling driver
[   23.074669] NET: Registered protocol family 17
[   23.104734] Key type dns_resolver registered
[   23.230797] registered taskstats version 1
[   23.454525]   Magic number: 15:388:671
[   23.474530] console [netcon0] enabled
[   23.488452] netconsole: network logging started
[   23.516814] ALSA device list:
[   23.537326]   No soundcards found.
[   23.594545] ata2.00: configured for MWDMA2
[   23.799704] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[   23.861341] scsi 1:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     2.0. PQ: 0 ANSI: 5
[   24.016374] sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[   24.042542] cdrom: Uniform CD-ROM driver Revision: 3.20
[   24.096758] sr 1:0:0:0: Attached scsi generic sg0 type 5
[   24.512716] Freeing unused kernel memory: 5948K (ffffffff81a72000 - ffffffff82041000)
I launch it on my Ubuntu VM.
Is that a problem !?

It's really strange what you say... pleasy try with 'PLATFORM=qemu_32 npm
install', if this doesn't work then maybe the VM is giving problems... Also
give me the output of 'uname -a'.
By the way, the timestamp are too high, they should be just 2 seconds, not
20.
El 22/01/2015 07:47, "joeking11829"<EMAIL_ADDRESS>escribió:

Hi piranna,
I do "npm start" at node-barebones
it look like same prolem.
...................................
[ 22.994589] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 23.023719] sit: IPv6 over IPv4 tunneling driver
[ 23.074669] NET: Registered protocol family 17
[ 23.104734] Key type dns_resolver registered
[ 23.230797] registered taskstats version 1
[ 23.454525] Magic number: 15:388:671
[ 23.474530] console [netcon0] enabled
[ 23.488452] netconsole: network logging started
[ 23.516814] ALSA device list:
[ 23.537326] No soundcards found.
[ 23.594545] ata2.00: configured for MWDMA2
[ 23.799704] input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/serio1/input/input3
[ 23.861341] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.0. PQ: 0 ANSI: 5
[ 24.016374] sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 24.042542] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 24.096758] sr 1:0:0:0: Attached scsi generic sg0 type 5
[ 24.512716] Freeing unused kernel memory: 5948K (ffffffff81a72000 -
ffffffff82041000)
I launch it on my Ubuntu VM.
Is that a problem !?
—
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/92#issuecomment-70978566.

I am trying to do "PLATFORM=qemu_32 npm install".
And my result of "uname -a" is:
Linux APPLE 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

And my result of "uname -a" is:
Linux APPLE 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

It's really strange, it should work... Could you give me the full outputs?
Or there's nothing after that?

Same problem on qemu-system-i386
qemu-system-i386 -enable-kvm -nographic --kernel bzImage -append console=ttyS0
full log outputs:
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.18.3 (root@APPLE) (gcc version 4.7.3 (GCC) ) #1 SMP Thu Jan 22 15:24:05 CST 2015
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000007ffdfff] usable
[    0.000000] BIOS-e820: [mem 0x0000000007ffe000-0x0000000007ffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] Notice: NX (Execute Disable) protection missing in CPU!
[    0.000000] SMBIOS 2.4 present.
[    0.000000] e820: last_pfn = 0x7ffe max_arch_pfn = 0x100000
[    0.000000] found SMP MP-table at [mem 0x000f0b70-0x000f0b7f] mapped at [c00f0b70]
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[    0.000000] init_memory_mapping: [mem 0x07800000-0x07bfffff]
[    0.000000] init_memory_mapping: [mem 0x00100000-0x077fffff]
[    0.000000] init_memory_mapping: [mem 0x07c00000-0x07ffdfff]
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x000F09E0 000014 (v00 BOCHS )
[    0.000000] ACPI: RSDT 0x07FFFBC1 000034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
[    0.000000] ACPI: FACP 0x07FFF1C0 000074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)
[    0.000000] ACPI: DSDT 0x07FFE040 001180 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
[    0.000000] ACPI: FACS 0x07FFE000 000040
[    0.000000] ACPI: SSDT 0x07FFF234 0008DD (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)
[    0.000000] ACPI: APIC 0x07FFFB11 000078 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
[    0.000000] ACPI: HPET 0x07FFFB89 000038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)
[    0.000000] 0MB HIGHMEM available.
[    0.000000] 127MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 07ffe000
[    0.000000]   low ram: 0 - 07ffe000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
[    0.000000]   Normal   [mem 0x01000000-0x07ffdfff]
[    0.000000]   HighMem  empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00001000-0x0009efff]
[    0.000000]   node   0: [mem 0x00100000-0x07ffdfff]
[    0.000000] Initmem setup node 0 [mem 0x00001000-0x07ffdfff]
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0xb008
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
[    0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
[    0.000000] e820: [mem 0x08000000-0xfeffbfff] available for PCI devices
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[    0.000000] PERCPU: Embedded 12 pages/cpu @c7eef000 s27136 r0 d22016 u49152
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32412
[    0.000000] Kernel command line: console=ttyS0
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] Initializing HighMem for node 0 (00000000:00000000)
[    0.000000] Memory: 113896K/130672K available (7129K kernel code, 354K rwdata, 2008K rodata, 5416K init, 508K bss, 16776K reserved, 0K highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xfff16000 - 0xfffff000   ( 932 kB)
[    0.000000]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    0.000000]     vmalloc : 0xc87fe000 - 0xff7fe000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc7ffe000   ( 127 MB)
[    0.000000]       .init : 0xc1948000 - 0xc1e92000   (5416 kB)
[    0.000000]       .data : 0xc16f699e - 0xc1946b40   (2368 kB)
[    0.000000]       .text : 0xc1000000 - 0xc16f699e   (7130 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.000000] NR_IRQS:2304 nr_irqs:256 0
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [ttyS0] enabled
[    0.000000] tsc: Fast TSC calibration failed
[    0.000000] tsc: Unable to calibrate against PIT
[    0.000000] tsc: HPET/PMTIMER calibration failed
[    0.000000] tsc: Marking TSC unstable due to could not calculate TSC khz
[    0.012000] Calibrating delay loop... 2297.85 BogoMIPS (lpj=1148928)
[    0.026000] pid_max: default: 32768 minimum: 301
[    0.027000] ACPI: Core revision 20140926
[    0.029000] ACPI: All ACPI Tables successfully acquired
[    0.035000] Security Framework initialized
[    0.036000] SELinux:  Initializing.
[    0.037000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.038000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.039000] Initializing cgroup subsys freezer
[    0.045000] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.045000] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.811000] Freeing SMP alternatives memory: 28K (c1e92000 - c1e99000)
[    0.814000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.918000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.923000] smpboot: CPU0: Intel QEMU Virtual CPU version 2.0.0 (fam: 06, model: 06, stepping: 03)
[    0.929000] Performance Events: Broken PMU hardware detected, using software events only.
[    0.931000] Failed to access perfctr msr (MSR c1 is 0)
[    0.932000] x86: Booted up 1 node, 1 CPUs
[    0.934000] smpboot: Total of 1 processors activated (2297.85 BogoMIPS)
[    0.949000] devtmpfs: initialized
[    0.953000] RTC time:  7:28:43, date: 01/22/15
[    0.954000] NET: Registered protocol family 16
[    0.955000] cpuidle: using governor ladder
[    0.956000] cpuidle: using governor menu
[    0.957000] ACPI: bus type PCI registered
[    0.962000] PCI: PCI BIOS revision 2.10 entry at 0xfd3c2, last bus=0
[    0.964000] PCI: Using configuration type 1 for base access
[    0.969000] ACPI: Added _OSI(Module Device)
[    0.970000] ACPI: Added _OSI(Processor Device)
[    0.972000] ACPI: Added _OSI(3.0 SCP Extensions)
[    0.973000] ACPI: Added OSI(Processor Aggregator Device)
[    0.985000] ACPI: Interpreter enabled
[    0.986000] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [_S1] (20140926/hwxface-580)
[    0.989000] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [_S2] (20140926/hwxface-580)
[    0.992000] ACPI: (supports S0 S3 S4 S5)
[    0.994000] ACPI: Using IOAPIC for interrupt routing
[    0.995000] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    1.003000] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    1.005000] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
[    1.006000] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[    1.008000] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
[    1.009000] PCI host bridge to bus 0000:00
[    1.010000] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.011000] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
[    1.012000] pci_bus 0000:00: root bus resource [io  0x0d00-0xadff]
[    1.013000] pci_bus 0000:00: root bus resource [io  0xae0f-0xaeff]
[    1.014000] pci_bus 0000:00: root bus resource [io  0xaf20-0xafdf]
[    1.015000] pci_bus 0000:00: root bus resource [io  0xafe4-0xffff]
[    1.016000] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[    1.017000] pci_bus 0000:00: root bus resource [mem 0x08000000-0xfebfffff]
[    1.066000] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
[    1.067000] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
[    1.068000] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
[    1.069000] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
[    1.089000] pci 0000:00:01.3: quirk: [io  0xb000-0xb03f] claimed by PIIX4 ACPI
[    1.091000] pci 0000:00:01.3: quirk: [io  0xb100-0xb10f] claimed by PIIX4 SMB
[    1.171000] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[    1.179000] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[    1.188000] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[    1.196000] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[    1.203000] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
[    1.207000] ACPI: Enabled 16 GPEs in block 00 to 0F
[    1.208000] vgaarb: setting as boot device: PCI:0000:00:02.0
[    1.208000] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[    1.209000] vgaarb: loaded
[    1.211000] vgaarb: bridge control possible 0000:00:02.0
[    1.212000] SCSI subsystem initialized
[    1.213000] ACPI: bus type USB registered
[    1.215000] usbcore: registered new interface driver usbfs
[    1.216000] usbcore: registered new interface driver hub
[    1.217000] usbcore: registered new device driver usb
[    1.218000] pps_core: LinuxPPS API ver. 1 registered
[    1.219000] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    1.220000] PTP clock support registered
[    1.221000] Advanced Linux Sound Architecture Driver Initialized.
[    1.222000] PCI: Using ACPI for IRQ routing
[    1.226000] NetLabel: Initializing
[    1.227000] NetLabel:  domain hash size = 128
[    1.228000] NetLabel:  protocols = UNLABELED CIPSOv4
[    1.230000] cfg80211: Calling CRDA to update world regulatory domain
[    1.232000] NetLabel:  unlabeled traffic allowed by default
[    1.234000] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[    1.235000] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    1.240000] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[    1.245544] Switched to clocksource hpet
[    1.291623] pnp: PnP ACPI init
[    1.461697] pnp: PnP ACPI: found 6 devices
[    1.525684] hrtimer: interrupt took 3176610 ns
[    1.633563] NET: Registered protocol family 2
[    1.665585] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    1.734618] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    1.755297] TCP: Hash tables configured (established 1024 bind 1024)
[    1.843561] TCP: reno registered
[    1.854778] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    1.873707] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    1.918573] NET: Registered protocol family 1
[    1.957589] RPC: Registered named UNIX socket transport module.
[    1.977668] RPC: Registered udp transport module.
[    1.993498] RPC: Registered tcp transport module.
[    2.011548] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.074574] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[    2.097557] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[    2.120677] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[    3.856687] microcode: CPU0 sig=0x663, pf=0x1, revision=0x1
[    3.911591] microcode: Microcode Update Driver: v2.00<EMAIL_ADDRESS>Peter Oruba
[    3.985623] Scanning for low memory corruption every 60 seconds
[    4.054595] futex hash table entries: 256 (order: 2, 16384 bytes)
[    4.115554] audit: initializing netlink subsys (disabled)
[    4.158591] audit: type=2000 audit(1421911724.158:1): initialized
[    4.261657] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[    4.384623] VFS: Disk quotas dquot_6.5.2
[    4.423638] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    4.482672] NFS: Registering the id_resolver key type
[    4.533678] Key type id_resolver registered
[    4.574583] Key type id_legacy registered
[    4.613627] fuse init (API version 7.23)
[    4.663547] msgmni has been set to 222
[    4.785606] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    4.856667] io scheduler noop registered
[    4.885667] io scheduler deadline registered
[    4.932596] io scheduler cfq registered (default)
[    4.981608] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    5.030637] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[    5.093605] ACPI: Power Button [PWRF]
[    5.165595] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    5.263689] serial 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    5.387633] Non-volatile memory driver v1.3
[    5.431590] Linux agpgart interface v0.103
[    5.485686] [drm] Initialized drm 1.1.0 20060810
[    5.670612] loop: module loaded
[    5.781615] scsi host0: ata_piix
[    5.864659] scsi host1: ata_piix
[    5.892593] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc040 irq 14
[    5.915747] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc048 irq 15
[    6.027602] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    6.047423] e100: Copyright(c) 1999-2006 Intel Corporation
[    6.069542] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    6.092737] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    6.121925] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[   22.337568] e1000 0000:00:03.0 eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56
[   22.374558] e1000 0000:00:03.0 eth0: Intel(R) PRO/1000 Network Connection
[   22.404904] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[   22.425789] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[   22.470572] sky2: driver version 1.30
[   22.575587] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   22.599521] ehci-pci: EHCI PCI platform driver
[   22.615291] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   22.636371] ohci-pci: OHCI PCI platform driver
[   22.663597] uhci_hcd: USB Universal Host Controller Interface driver
[   22.709621] usbcore: registered new interface driver usblp
[   22.739579] usbcore: registered new interface driver usb-storage
[   22.777717] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[   22.889356] serio: i8042 KBD port at 0x60,0x64 irq 1
[   22.907670] serio: i8042 AUX port at 0x60,0x64 irq 12
[   22.951563] mousedev: PS/2 mouse device common for all mice
[   23.017608] rtc_cmos 00:00: RTC can wake from S4
[   23.052769] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[   23.089773] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram, hpet irqs
[   23.118647] hpet1: lost 1 rtc interrupts
[   23.217591] device-mapper: ioctl: 4.28.0-ioctl (2014-09-17) initialised<EMAIL_ADDRESS>[   23.261671] hidraw: raw HID events driver (C) Jiri Kosina
[   23.328633] usbcore: registered new interface driver usbhid
[   23.347818] usbhid: USB HID core driver
[   23.423648] Netfilter messages via NETLINK v0.30.
[   23.451605] nf_conntrack version 0.5.0 (1780 buckets, 7120 max)
[   23.525648] ctnetlink v0.93: registering with nfnetlink.
[   23.607559] ip_tables: (C) 2000-2006 Netfilter Core Team
[   23.659584] TCP: cubic registered
[   23.670743] Initializing XFRM netlink socket
[   23.725605] NET: Registered protocol family 10
[   23.802575] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   23.823551] sit: IPv6 over IPv4 tunneling driver
[   23.878597] NET: Registered protocol family 17
[   23.910589] Key type dns_resolver registered
[   23.925553] mce: Unable to init device /dev/mcelog (rc: -5)
[   23.985645] Using IPI No-Shortcut mode
[   24.040652] registered taskstats version 1
[   24.099593]   Magic number: 15:288:471
[   24.122596] console [netcon0] enabled
[   24.135481] netconsole: network logging started
[   24.154560] ALSA device list:
[   24.165560]   No soundcards found.
[   24.215605] ata2.00: ATAPI: QEMU DVD-ROM, 2.0.0, max UDMA/100
[   24.275824] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[   24.526717] ata2.00: configured for MWDMA2
[   24.562653] scsi 1:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     2.0. PQ: 0 ANSI: 5
[   24.646780] sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[   24.670574] cdrom: Uniform CD-ROM driver Revision: 3.20
[   24.729641] sr 1:0:0:0: Attached scsi generic sg0 type 5
[   25.018544] Freeing unused kernel memory: 5416K (c1948000 - c1e92000)
[   26.011618] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
...........there's nothing after this

Same problem on qemu-system-i386
qemu-system-i386 -enable-kvm -nographic --kernel bzImage -append console=ttyS0

Then honestly I don't know what could be happening here, sorry :-/
Only last posibility is about you are compiling it on an Ubuntu VM
instead of a native install, but that should not be a problem. Please
upgrade your Ubuntu VM and all its related software and try again. If
this doesn't work, try again with a native install. If this doesn't
work, well... :-/
For reference, I'm using as development platform Ubuntu Mate 14.10
both on a Dell Latitude 500 (Core2 Duo, but using a 32 bits system)
and now on a MacBook Pro 2012 pre-Retina (i5 quad core, 64 bits
system, and the reason of the work on the cross-compiler)
--
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux

Inside a VM I had to remove the -enable-kvm part, although if I remember correctly it gave me a useful error message.

I have been getting some compilation problems with latest master and needed to go back some commits... just to find this same issue! O_O I've gone down to previous ones (up to dda61c4 "x86 64 bits support") The worst thing is that I'm running Linux natively and they are some commits that I compiled from scratch. I've also checked about some installed package like QEmu or Linux kernel, but they are from several days before... Removing -enable-kvm doesn't help :-/
Don't know what's happening here, but seems something serious and don't know what could be happening here... :-(

Ok, I think I've found it! :-D Last Tuesday Node.js got updated to v0.11.15. Since we are using the latest available unstable release, I've hardcoded it to use the v0.11.14 version and has been able to run it :-) Need to test with a fully clean repo, but seems that's the reason why it didn't worked. @joeking11829, could you be able to confirm this? If so, then maybe we should use fixed versions instead of depend in the latest ones available, and maybe configure a bot task to test the new ones, what do you think?

I've open an issue on Node.js regarding to this regression.

Hi
I download the new repo for NodeOS.
And it works.
I can launch NodeOS on QEMU simulator.
But I get another error.
Error log:
[   14.856312] EXT4-fs (sda): couldn't mount as ext3 due to feature incompatibilities
[   14.989441] EXT4-fs (sda): mounting ext2 file system using the ext4 subsystem
[   15.012137] EXT4-fs (sda): warning: mounting unchecked fs, running e2fsck is recommended
[   15.022995] EXT4-fs (sda): mounted filesystem without journal. Opts: errors=remount-ro
Error re-mounting / as read-only
[   15.861363] random: init urandom read with 87 bits of entropy available
[   21.733031] random: nonblocking pool is initialized
[   21.988577] EXT4-fs (sdb): couldn't mount as ext3 due to feature incompatibilities
[   22.005963] EXT4-fs (sdb): mounting ext2 file system using the ext4 subsystem
[   22.022120] EXT4-fs (sdb): warning: mounting unchecked fs, running e2fsck is recommended
[   22.027147] EXT4-fs (sdb): mounted filesystem without journal. Opts:
fs.js:552
//  fs.writeSync(fd, buffer, offset, length[, position]);
^
Error: ENOSPC, no space left on device '/root/.forever/n71b.log'
at Error (native)
at Object.fs.openSync (fs.js:455:18)
at Object.forever.startDaemon (/root/lib/node_modules/forever/lib/forever.js:409:14)
at /root/lib/node_modules/forever/bin/starter:50:13
at Array.forEach (native)
at Object. (/root/lib/node_modules/forever/bin/starter:30:10)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: bin/users-services
fs.js:552
//  fs.writeSync(fd, buffer, offset, length[, position]);
^
Error: ENOSPC, no space left on device '/root/.forever/cANd.log'
at Error (native)
at Object.fs.openSync (fs.js:455:18)
at Object.forever.startDaemon (/root/lib/node_modules/forever/lib/forever.js:409:14)
at /root/lib/node_modules/forever/lib/forever/cli.js:264:13
at /root/lib/node_modules/forever/lib/forever/cli.js:150:5
at /root/lib/node_modules/forever/lib/forever.js:352:11
at Object.oncomplete (fs.js:93:15)
it look like mount root file system failed.
Any idea !?

fs.js:552
// fs.writeSync(fd, buffer, offset, length[, position]);
^
Error: ENOSPC, no space left on device '/root/.forever/cANd.log'
at Error (native)
at Object.fs.openSync (fs.js:455:18)
at Object.forever.startDaemon (/root/lib/node_modules/forever/lib/forever.js:409:14)
at /root/lib/node_modules/forever/lib/forever/cli.js:264:13
at /root/lib/node_modules/forever/lib/forever/cli.js:150:5
at /root/lib/node_modules/forever/lib/forever.js:352:11
at Object.oncomplete (fs.js:93:15)
it look like mount root file system failed.
Any idea !?

Oh, sh*t, my fault. No, both rootfs & usersfs has been mounted (good!
:-D ), but rootfs has filled. Yesterday while trying to make bootable
disk images I've also added a way so it's size is autocalculated (it
was hardcoded to 32MB before), seems we should not use it until we can
be sure rootfs will be read-only. Change this line
https://github.com/NodeOS/NodeOS/blob/cc343181619576fec9105900229f3b178c328000/node_modules/nodeos-rootfs/scripts/install#L89
as set this for the size instead
DISK_SIZE=32 # Size in MB
$((DISK_SIZE*1024))

I'll try to fix it later.
--
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux

Fixed in master

Awesome !!
It works !!

I'm happy you got it working again :-)

I just built the latest master and this error still shows up:
[   16.885384] EXT4-fs (sda): couldn't mount as ext3 due to feature incompatibilities
[   16.911772] EXT4-fs (sda): mounting ext2 file system using the ext4 subsystem
[   16.942064] EXT4-fs warning (device sda): ext4_update_dynamic_rev:698: updating to rev 1 because of new feature flag, running e2fsck is recommended
[   16.955621] EXT4-fs (sda): mounted filesystem without journal. Opts: errors=remount-ro
Error re-mounting / as read-only

And the system is quite slow to boot. I don't remember seeing these warnings the last time I built it.

Those errors are normal, it's only saying that the root filesystem is Ext4 but it's mounting it as Ext2, probably related to the auto filesystem detection (I don't know why, the order in /proc/filesystems that's used as basis is Ext3 Ext2 Ext4 while Ext4 should be the first one since it's the more feature complete...), and the last one is regarding to trying to remount the initramfs as read-only, that seems it's not possible by definition. When we move /root to the usersfs and upgrade to use Linux kernel 3.19 with multilayer read-only OverlayFS we'll make it read-only from start, so this will not be needed anymore. I wouldn't worry about any of the both problems :-)
Regarding to being slower, how much slower? It should fully boot in under 10 seconds... Do you have KVM disabled on QEmu? This would make it to boot up to 30 seconds...

Yes, KVM is disabled, but it was not this slow the last time. It boots up around 20+ seconds, and the most wait time is when the mount warnings show up, so I guess they are related.

auto filesystem detection is implemented by reading /proc/filesystem and trying to mount the partition checking each of the partitions in order, so yes, they could be related since there's some IO sync things (do you remember the sync mount functions? ;-) ). Standard auto filesystem in the mount command do it in the same way.

Yeah, I remember. However my main concern is that we didn't come a long way since I converted the old modules, and the boot time is already about 10 seconds slower. By the way the login is slow too. When I give it the password and press enter several seconds pass until it actually logs in.

I don't remember about having any similar issue, but it's true I'm having a hard time and didn't work on NodeOS since a week ago. I'll try to find some time and test it again paying attention to this.

I m installing NodeOS on Ubuntu 14.04LTS 32-bit.
I m Getting this error:-
configure: error: cannot run /bin/bash /home/saurabh/Downloads/NodeOS-master/node_modules/nodeos-barebones/node_modules/nodeos-cross-toolchain/deps/gcc/config.sub
Error compiling '/home/saurabh/Downloads/NodeOS-master/node_modules/nodeos-barebones/node_modules/nodeos-cross-toolchain/obj/i686/gcc'
npm ERR! Linux 3.13.0-35-generic
npm ERR! argv "node" "/usr/bin/npm" "install"
npm ERR! node v0.10.35
npm ERR! npm  v2.2.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: scripts/install
npm ERR! Exit status 31
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'scripts/install'.
npm ERR! This is most likely a problem with the nodeos-cross-toolchain package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     scripts/install
npm ERR! You can get their info via:
npm ERR!     npm owner ls nodeos-cross-toolchain
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/saurabh/Downloads/NodeOS-master/npm-debug.log
Help me!!!

Did you try installing it using docker?

No, I have problem regarding the docker, in fact i didnt get through docker. So i tried Qemu.

Docker is currently unmaintained, hope we can retake it soon when finish to define the filesystem architecture.