RTD build fail

I observed the same error on a bunch of different repo on the past two hours.

I just tested and it looks like docs are building fine for me (using these instructions). I did see an NPM error while building but it wasn't fatal:
><EMAIL_ADDRESS>build:src /Users/grant/Sites/jupyter/ipywidgets/jupyter-js-widgets
> tsc --project src

node_modules/@types/jquery/index.d.ts(3246,5): error TS2300: Duplicate identifier 'export='.
node_modules/@types/mathjax/index.d.ts(581,9): error TS2687: All declarations of 'CommonHTML' must have identical modifiers.
node_modules/@types/requirejs/index.d.ts(416,13): error TS2403: Subsequent variable declarations must have the same type.  Variable 'require' must be of type '{ <T>(path: string): T; (paths: string[], callback: (...modules: any[]) => void): void; ensure: (...', but here has type 'Require'.
node_modules/@types/semver/index.d.ts(108,11): error TS2300: Duplicate identifier 'SemVerBase'.
node_modules/@types/semver/index.d.ts(116,11): error TS2300: Duplicate identifier 'SemVer'.
node_modules/@types/semver/index.d.ts(132,11): error TS2300: Duplicate identifier 'Comparator'.
node_modules/@types/semver/index.d.ts(142,11): error TS2300: Duplicate identifier 'Range'.
node_modules/@types/semver/index.d.ts(185,5): error TS2300: Duplicate identifier 'export='.
typings/jquery/jquery.d.ts(615,5): error TS2374: Duplicate string index signature.
typings/jquery/jquery.d.ts(2833,5): error TS2374: Duplicate string index signature.
typings/jquery/jquery.d.ts(2834,5): error TS2375: Duplicate number index signature.
typings/jquery/jquery.d.ts(3207,5): error TS2300: Duplicate identifier 'export='.
typings/mathjax/mathjax.d.ts(581,9): error TS2687: All declarations of 'CommonHTML' must have identical modifiers.
typings/semver/semver.d.ts(31,11): error TS2300: Duplicate identifier 'SemVerBase'.
typings/semver/semver.d.ts(39,11): error TS2300: Duplicate identifier 'SemVer'.
typings/semver/semver.d.ts(55,11): error TS2300: Duplicate identifier 'Comparator'.
typings/semver/semver.d.ts(65,11): error TS2300: Duplicate identifier 'Range'.
typings/semver/semver.d.ts(74,1): error TS2300: Duplicate identifier 'export='.

npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "run" "build:src"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build:src: `tsc --project src`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build:src script 'tsc --project src'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the jupyter-js-widgets package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc --project src
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jupyter-js-widgets
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls jupyter-js-widgets
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/grant/Sites/jupyter/ipywidgets/jupyter-js-widgets/npm-debug.log

npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: `npm run build:src && npm run build:css && webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'npm run build:src && npm run build:css && webpack'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the jupyter-js-widgets package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build:src && npm run build:css && webpack
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jupyter-js-widgets
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls jupyter-js-widgets
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/grant/Sites/jupyter/ipywidgets/jupyter-js-widgets/npm-debug.log

npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "install"
npm ERR! node v6.7.0
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the jupyter-js-widgets package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jupyter-js-widgets
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls jupyter-js-widgets
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/grant/Sites/jupyter/ipywidgets/jupyter-js-widgets/npm-debug.log

I'm going to close. Re-open if the you're still having issues.


new notebook can not be created with new environment use after  new environment is created and activated in terminal

new notebook can not be created with new environment use after  new environment is created and activated in terminal

in any case how to make new environment visible to use for new notebook

new environment is not visible

it is not like example, since new environment is not visible
https://github.com/aws/studio-lab-examples/blob/main/custom-environments/custom_environment.ipynb

may i need to activate new environment through console - console environment is not changed after activating in terminal
but how to   activate new environment through console?

conda init bash is not working neither
kernel restart is not helping

ok I found answer in
https://docs.aws.amazon.com/sagemaker/latest/dg/studio-lab-use-manage.html
then your explanatoin in https://github.com/aws/studio-lab-examples/blob/main/custom-environments/custom_environment.ipynb
is wrong
since
conda install ipykernel
missed

and

and

We close this issue. ipykernel is included to environment.yml.


TextField Password has strange issue on Dialog when autofilled in by Chrome

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component
Component name
MudTextField
What happened?
The MainLayout of my app has an AuthorizeView - when the user is NOT authourised it renders a component called Login.razor
Login.razor on AfterRenderAsync - opens up the following Dialog by use of the DialogService
<MudDialog DefaultFocus="DefaultFocus.FirstChild">
     <DialogContent>
        <MudForm @ref="@form">
            <MudStack Spacing="3">
                <MudStack Row="false">
                    <MudStack Row="true" Spacing="1" AlignItems="MudBlazor.AlignItems.Center" Justify="Justify.Center">
                        <MudImage Src="/_content/BJP.TestApp.WebUI.Razor.Shared/images/saalogo.jpg" />
                    </MudStack>
                </MudStack>
                <MudStack Spacing="2" Justify="Justify.SpaceEvenly">
                    <MudTextField ShrinkLabel T="string" Label="Email:" Variant="MudBlazor.Variant.Filled"
<EMAIL_ADDRESS>                                  Required="true" RequiredError="Email is required" Validation="@(new EmailAddressAttribute() {ErrorMessage = "The email address is invalid"})" />
                    <MudTextField ShrinkLabel T="string" Label="Password:" Variant="MudBlazor.Variant.Filled"
<EMAIL_ADDRESS>InputType="InputType.Password"
                                  Required="true" RequiredError="Password is required" For="() => model.Password" KeyDownPreventDefault="true" />
                    <MudCheckBox<EMAIL_ADDRESS>Color="Color.Primary" Label="RememberLogin" Style="margin-left: -5px;" />
                </MudStack>
                <MudStack Row="true" Spacing="1" AlignItems="MudBlazor.AlignItems.Center" Justify="Justify.Center" Style="margin-bottom: 10px;">
                    <MudButton ButtonType="MudBlazor.ButtonType.Button" Variant="MudBlazor.Variant.Filled" Style="width: 360px; background-color: #e53935;color: white" OnClick="(() => OnSubmit())">Sign In</MudButton>
                </MudStack>
            </MudStack>
        </MudForm>
    </DialogContent>
</MudDialog>

If I set the Second Text Field to by just Text then the dialog loads albeit with just the username filled in - if I then type in a password and click submit then I log in just fine and from then on I am authourized - all good.
If I set the second text field to Password - Chrome autofills in the password so my screen looks like this

So far so good - however the moment I try to click the EMAIL text field, the PASSWORD text field, the Checkbox OR the Sign In button I get the following Javascript error from MUDBLAZOR.MIN.JS

onKeyDown(args){var self=this.mudKeyInterceptor;var key=args.key.toLowerCase();
args.key is undefined - but I have not tried to type anything - I just clicked the sign in button.....
If I 'f5' pass the JS errors and then click the signin button again it signs me in as before and all is well - but it's bugging me this JS error....
Can anyone recommend what I might be doing incorrectly, or if they can think of what might be causing this and how I might be able to code around it
Expected behavior
I want to set the text field as password - chrome will autofill it if it's recognised and I can change it, or sign in etc with NO javascript error
Reproduction link
N/A
Reproduction steps

...
Relevant log output
Message=
  Source=
  StackTrace:
  at HTMLDivElement.onKeyDown (https://localhost:5177/_content/MudBlazor/MudBlazor.min.js:39:66)

Version (bug)
7.1.15
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think it's the same issue as this: https://github.com/MudBlazor/MudBlazor/issues/9107
@ScarletKuro made a fix, but I don't think it's released yet. At least not for v7?

I think it's the same issue as this: #9107
@ScarletKuro made a fix, but I don't think it's released yet. At least not for v7?

Ay yes - looks like you are correct - I guess it's a known issue then and not me being totally stoopid - not sure if that's better or worse :)

Closed as duplicate of #9107


[Question]: Combine AND and OR statements in MetadataFilters

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I have some documents saved in postgresql table using llama-index. When creating a query_engine I'm trying to add AND filter between my metadata fields and an OR filter between a list of filters so I would get exactly the data I need from database. So far I've seen the way to apply filters using
from llama_index.vector_stores import ExactMatchFilter, FilterCondition, MetadataFilters

all_filters = [ .... ] # defining some ExactMatchFilter
filters = MetadataFilters(
      filters=all_filters,
      condition=FilterCondition.OR
)

Is there a way to define FilterCondition.AND between multiple filters of all_filters list (a nested list of filters) and have the for example OR condition between the whole all_filters?

The bot's answer is not related to Postgresql database. In PGVectorStore, it is using the MetadataFilters which they seems not support multiple nested conditions.

I think this is very related to having no other filters than ExactMatchFilter.

@juleskuehn Thanks for your response. For now, I just did all the retrieval task manually so I could have the combination of filters. I would encourage you to open a PR as more people might have the same problem (I don't have the time myself to do it).

@logan-markewich Do you agree with my proposal? If so, I can start on a PR.

@juleskuehn if you want to make a pr, go for it 👍 but would need to make sure this doesn't break other vector stores too I think

I had the similar issue with Neo4jPGStore = Neo4jPropertyGraphStore. I got inspired by this post but due to lack of time, I ended up overriding the vector_query method to accept a string.
I am simply passing the filters as a partial cypher query after creating it programmatically per query. This also helps overcome another limitation I have discovered. The existing filters do not allow comparing two arrays to identify if all elements are equal.
Since the filters can get very complicated, it may be a good option to allow passing filters as a string.


Fixes #46: remove simple line breaks for GH style

Fixes #46
Before a line break in the md file would generate a line break in the pdf file but to match the way GH renders Markdown it should be rendered in the same line in the pdf file. This PR fixes this.
Here is a before and after of this text:
Hi,
how
are
you?

Before:

After:

@BlueHatbRit sorry for using the handler to get your attention, but it would be wonderful if You could merge this changes. They fixes the #46.
Thank you!

Sorry for the delay on this, I really don't use mdpdf much these days so find it hard to make time for updates. I've merged this in with a few tweaks 01f2e38e1e85b0839de3c89d0d24c18b20aae5fa. I'll close this PR but it's in master and I'm preparing a release of 3.0.2.


Provide a default result grid height

Fixes https://github.com/microsoft/azuredatastudio/issues/5705.
Here's an example of a default split with this change.

Whats wrong with the 50/50, pretty sure thats what sms does?

Yeah that seems pretty large - does it cut off the query if that's larger than the current viewing area? While I could see something like this if we actually measured how much text was in the window and had the results grid be max between 50% and the bottom of the query text I personally would lean towards a little smaller if the logic is just a static value.

This is restoring the behavior from the June release.  I don't recall any design discussions to change it.  Please schedule a meeting to discuss UX changes to the query editor and we can see if there is a better proportion.

Where are you seeing this being the previous behaviour? can you link to a code line? I looked and didn't see anything around this behaviour nor does using the product show this behaviour, if anything this seems like the new behaviour...

@anthonydresser sure, here's the where this was previously defined https://github.com/microsoft/azuredatastudio/blob/release/1.7/src/sql/workbench/parts/query/browser/queryResultsView.ts#L134.  We can discuss what we'd like to have happen here in our committer sync this Friday.  For now, let's put it back to its previous behavior until a new design can be reviewed.

Oh, actually now that I recall, this may define the messages and results split.  Not the text editor results split.  I'll put it back to 50\50 and we can discuss on Friday.


Use "timelib.h"

https://github.com/Montecri/GPSTimeServer/blob/5a0cee3bb3972d495a00e4791f701c804b7f2d9c/src/main.cpp#L653
Why don't you let "timelib.h" calculate it for you?
timestamp = now() + seventyYears;
so you don't need all the code for the time calculation.

Hi @mmarkin !
Believe you replaced:
 timestamp = numberOfSecondsSince1900Epoch(year(t), month(t), day(t), hour(t), minute(t), second(t));
with:
timestamp = CalculateNTP(year(t), month(t), day(t), hour(t), minute(t), second(t));
On Dual Display tree.
@cheise above is proposing what appears to be a more concise and elegant solution.
I've updated the main tree with the suggestion, tested and appear to work ok.
Would like to implement that on the Dual Display tree?
Thank you!

Hi Cristiano
Thanks for the suggestions. Yes, I should have realized timelib already has
the timestamp. There was no need to calculate it again either by using
ziggy's function or the longer version of it that I wrote. All that has to
be done is to convert timelib's timestamp from UNIX to NTP by adding 70
years.
Also there was no need for the > 3000 age check when syncing with GPS.
I made the changes to my server and it's still working properly. I also
updated the Dual OLED post on GitHub.
Cheers,
Mitch Markin
On Mon, Feb 6, 2023 at 1:05 PM Cristiano Monteiro @.***>
wrote:

Hi @mmarkin https://github.com/mmarkin !
Believe you replaced:
timestamp = numberOfSecondsSince1900Epoch(year(t), month(t), day(t),
hour(t), minute(t), second(t));
with:
timestamp = CalculateNTP(year(t), month(t), day(t), hour(t), minute(t),
second(t));
On Dual Display tree.
@cheise https://github.com/cheise above is proposing what appears to be
a more concise and elegant solution.
I've updated the main tree with the suggestion, tested and appear to work
ok.
Would like to implement that on the Dual Display tree?
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/Montecri/GPSTimeServer/issues/7#issuecomment-1419754201,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHVRWOKZXONDV2ETW7HONNTWWFRQTANCNFSM6AAAAAAUSSLAAM
.
You are receiving this because you were mentioned.Message ID:
@.***>

In Germany we say: "You can't see the tree for the trees"
or "why make it complicated when it's easy" I hope the translation is correct. Best Regards

In Canada the saying is "you can't see the forest for the trees."  I didn't
write most of the code for this project but I did go through it trying to
make it more efficient. I fixed the bug in the timestamp calculations. But
even though I am very familiar with timelib and  have used it numerous
times for clock projects, it never occurred to me that timelib already has
the timestamp.
Sometimes you get so focused on one solution the obvious easier
solution gets overlooked.
Mitch Markin
On Mon, Feb 6, 2023 at 5:07 PM cheise @.***> wrote:

In Germany we say: "You can't see the tree for the trees"
or "why make it complicated when it's easy" I hope the translation is
correct. Best Regards
—
Reply to this email directly, view it on GitHub
https://github.com/Montecri/GPSTimeServer/issues/7#issuecomment-1420022459,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHVRWOK356IHOY7MLBOLS6LWWGN6PANCNFSM6AAAAAAUSSLAAM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi guys!
I remember I added >3000 to debug a specific situation (for which, of course, I don't recall) and forgot to remove it.
Went over the code so many times to make it work with my hardware and specific needs that, at some point, it kind of becomes fuzzy. Unless it's a code-breaking bug you don't see the opportunities anymore. But I was certain that people online would find these and help fix them.
Like my ugly display code, fixed by @mmarkin, and these fixed by @cheise
Thank you all!

Cristiano

Fixed as of today.

I ported the code to RP2040 Raspberry Pico, the non wifi varriant. That's when I noticed the problems. I have built a lightweight network based GPS NTP device, not WiFi based. Your code helped me a lot to understand many things. Gread work from you :)

Very nice!
Have you posted your port on Github or something?
If you want we can created a RP2040 branch for it, like I did for Mitch Dual Display and PIR version, so he can maintain it.
Regards,

Cristiano

Under https://github.com/cheise/PICO_GPS_TimeServer_PLUS you can see my newest public code. Now it has support for the newer TinyGPSPlus libary  ;) This Version is for the i2c Display what you use, too. Functionaly the same, without the "reset / WiFi" Button, i use the "run" pin on RPI Pico for resetting the board with a Button.


discussion: cloudflare workers

@iefserge I hope it's ok to continue dropping some discussion topics here.
I was doing  a bit more research into v8 Isolates and Contexts and stumbled across an explanation of Cloudflare's new Workers platform and can't help but draw some parallels with runtimejs or at least what runtime was when it was supported multiple isolates.
from the article:
What we ended up settling on was a technology built by the Google
Chrome team to power the Javascript engine in that browser, V8: Isolates.

Isolates are lightweight contexts that group variables with the code allowed
to mutate them. Most importantly, a single process can run hundreds or
thousands of Isolates, seamlessly switching between them. They make it
possible to run untrusted code from many different customers within a single
operating system process. They’re designed to start very quickly (several
had to start in your web browser just for you to load this web page), and to
not allow one Isolate to access the memory of another.

Is this where runtime was headed? what might it take to allow runtimejs to operate "hundreds" of isolates on the runtimejs kernel. Reading through the issues, it looks like there needs to be some refactoring/rewriting to make isolates a stable part of runtime, but what parts would those be?
cc: @facekapow @piranna

Interesting comment :-) I don't know about the internals or runtimejs, but definitely seems something to follow on :-)


Add thenewboston

Playlists:

https://www.youtube.com/playlist?list=PLFE2CE09D83EE3E28
https://www.youtube.com/playlist?list=PL27BCE863B6A864E3

Old, but there's tons of short videos that go in order (follows up from each previous video) which may help :)

Could probably add him to other languages as well


auto detect template subscriptions?

The fast render docs say that automatic subscription detection works for:
Subscriptions defined in the route's waitOn function.
Subscriptions defined in the route controller's waitOn function.
Subscriptions defined in the route controller's subscriptions method.
However, Kadira academy states that it is not advisable to define subscriptions on the route level, but rather define them in the templates. So this seems to contradict the fast-render implementation

See #115


taking a lineout by clicking and dragging in lineout mode corrupts currently displayed plot

Marc Durant reported this. A picture showing corruption is attached. Just reporting a bug I'm encountering on Windows. It's only an annoyance, but I've had several users in the company comment on it, so I need to pass it on. The bug concerns the "Lineout" mode on windows. When in lineout mode, the underlying plot isn't refreshed between when I click the mouse button to start the lineout, and when I release the button to end the lineout. If I move the mouse around, I can generate a large white area with no plot. As soon as I release the mouse button, the plot will redraw instantly (i.e. from video memory, not regenerated by VisIt) and the lineout will also appear properly. Attached is an image of the graphic corruption. Let me know if you need any more information.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 795
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: taking a lineout by clicking and dragging in lineout mode corrupts currently displayed plot
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 07/26/2011
Due date:
% Done: 0%
Estimated time:
Created: 07/26/2011 11:40 am
Updated: 08/05/2011 07:33 pm
Likelihood: 3 - Occasional
Severity: 3 - Major Irritation
Found in version: 2.3.0
Impact:
Expected Use:
OS: Windows
Support Group: Any
Description:
Marc Durant reported this. A picture showing corruption is attached. Just reporting a bug I'm encountering on Windows. It's only an annoyance, but I've had several users in the company comment on it, so I need to pass it on. The bug concerns the "Lineout" mode on windows. When in lineout mode, the underlying plot isn't refreshed between when I click the mouse button to start the lineout, and when I release the button to end the lineout. If I move the mouse around, I can generate a large white area with no plot. As soon as I release the mouse button, the plot will redraw instantly (i.e. from video memory, not regenerated by VisIt) and the lineout will also appear properly. Attached is an image of the graphic corruption. Let me know if you need any more information.
Comments:
From a follow-up email from Marc. Test with XP, both 32 bit and 64 bit, does not reproduce.Test with Win7 64 bit, does not reproduce.So, for whatever reason, this only occurs on Win7, 32 bit.


⚠ TiendaEnLinea has degraded performance

In cb6bb8d, TiendaEnLinea (https://www.fahorro.com/) experienced degraded performance:

HTTP code: 200
Response time: 5787 ms

Resolved: TiendaEnLinea performance has improved in d2cb7dc.


Don't add a space betweenn spans (Royalroad)

Leech seems to be adding spaces beween span tags which breaks Delve (https://www.royalroad.com/fiction/25225/delve' chapter 164 and probably others) since delve for some reason has the start of a word and the rest of the word in seperate tags. So Rain (MC) sometimes ends up as R ain, and other errors like that.

Honestly, beautifulsoup doing this in a "prettify" operation is a pretty good argument for just removing all usage of prettify from the code. Such things really shouldn't semantically change the output.
An alternative might be to use something like @annedo's prettierfier. But I think my main reason for prettifying when I added it back-in-the-day was to make debugging easier, so just removing it from the output entirely seems fair to start. 🤔


vectorSegmentedAddUniformToRight4 in vector_kernel needs indices argument clarified

In vector_kernel, the function vectorSegmentedAddUniformToRight4 has an
argument "d_minIndices" but the documentation for that argument refers to
an "array of maximum indices". Please make the documentation and argument
name match the functionality.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 17 Jun 2009 at 10:48

Assigning to Shubho since this is his function.

Original comment by<EMAIL_ADDRESS>on 17 Jun 2009 at 11:30

John to verify.

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 4:57

Shubho, can you clarify the way this argument works? Is this greater-than or
greater-than-or-equal-to? If it's as described, I don't see how it would be
possible
to specify a minimum index that is just to the right of 0, since 0 seems to be
special-cased according to the description.

Also, there's a reference to d_maxindex in the kernel description, but there's
no
d_maxindex argument. It looks like the kernel description was copied from the
previous kernel.

Also, there's a FIXME comment in this kernel.

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 1:12

Changed state: Started

Original comment by<EMAIL_ADDRESS>on 23 Jun 2009 at 2:10

Added labels: Milestone-Release1.1

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 4:50

Changed state: Fixed

That clarification - why it's one-based - is worth adding. It would make it much
easier for those who modify/use your code to understand it.

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 5:52

Added clarification

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 9:49

Changed state: Fixed

It is in line 293 - and also in segmented_scan_cta.cu where they are generated.

There is a reason why it is 1 - if the first element of a CTA has a flag - the
index would be 0 - but 0 also means
the absence of a flag. Hence a 1-based index to prevent overloading of what 0
means.

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 5:27

Can you clarify the 1-based thing in the comments? It seems to me that
greater-than-with-1-index is equivalent to the simpler
greater-than-or-equal-to-with-0-index, but I just want it described completely;
I
didn't write the code. But "1-index" is not mentioned in the documentation at
all and
it seems like it should be.

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 5:19

It is greater than. If it is 0 then it is added to the whole CTA. if it is 1
you have a minimum index which is just to
the right of 0 (the minimum index is 1-based)

changed d_maxIndex to d_minIndex

FIXME is unrelated to this issue - can open a new one to fix that

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 5:10

That's helpful, thanks.

Original comment by<EMAIL_ADDRESS>on 25 Jun 2009 at 9:55

Changed state: Verified


snap migration of lxd fails if btrfs volume is a mounted one

I tried to migrate lxd 2.21 (ubuntu 17.10, btrfs)  to snap package on 2 systems:

one with /var/lix/lxd btrfs subvolume in-place

one with btrfs subvolume mounted on  /var/lix/lxd (with mount UUID etc ..)

the migration on the system with btrfs in-place worked fine

the migration on the system with btrfs mounted on /var/lib/lxd failed (didn't stopped).

I think the second case is not taken in account in the migration process.
Regards.

i don't remember  the error message, and i can't replay the migration script.
i think the lxd database is corrupted since i have lost all containers.

Hmm, LXD wouldn't start if your database had been corrupted, so it's more likely it's looking at the wrong database. So we should be able to figure that out easily enough.
Can you paste:

cat /proc/self/mountinfo
ls -lh /var/snap/lxd/common/lxd
ls -lh /var/snap/lxd/current/lxd/

gaetanquentin-perso@gquentin-ssd-t3:~$ cat /proc/self/mountinfo
22 28 0:21 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw
23 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:13 - proc proc rw
24 28 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs udev rw,size=8143368k,nr_inodes=2035842,mode=755
25 24 0:22 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts rw,gid=5,mode=620,ptmxmode=000
26 28 0:23 / /run rw,nosuid,noexec,relatime shared:5 - tmpfs tmpfs rw,size=1634952k,mode=755
28 0 0:25 /@ / rw,noatime shared:1 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=257,subvol=/@
29 22 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - securityfs securityfs rw
30 24 0:28 / /dev/shm rw,nosuid,nodev shared:4 - tmpfs tmpfs rw
31 26 0:29 / /run/lock rw,nosuid,nodev,noexec,relatime shared:6 - tmpfs tmpfs rw,size=5120k
32 22 0:30 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:9 - tmpfs tmpfs ro,mode=755
33 32 0:31 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:10 - cgroup2 cgroup rw
34 32 0:32 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:11 - cgroup cgroup rw,xattr,name=systemd
35 22 0:33 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:12 - pstore pstore rw
36 32 0:34 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:14 - cgroup cgroup rw,cpu,cpuacct
37 32 0:35 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,perf_event
38 32 0:36 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:16 - cgroup cgroup rw,hugetlb
39 32 0:37 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:17 - cgroup cgroup rw,pids
40 32 0:38 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:18 - cgroup cgroup rw,cpuset,clone_children
41 32 0:39 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:19 - cgroup cgroup rw,memory
42 32 0:40 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:20 - cgroup cgroup rw,devices
43 32 0:41 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime shared:21 - cgroup cgroup rw,net_cls,net_prio
44 32 0:42 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:22 - cgroup cgroup rw,freezer
45 32 0:43 / /sys/fs/cgroup/rdma rw,nosuid,nodev,noexec,relatime shared:23 - cgroup cgroup rw,rdma
46 32 0:44 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:24 - cgroup cgroup rw,blkio
47 23 0:45 / /proc/sys/fs/binfmt_misc rw,relatime shared:25 - autofs systemd-1 rw,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16562
50 24 0:19 / /dev/mqueue rw,relatime shared:26 - mqueue mqueue rw
49 22 0:8 / /sys/kernel/debug rw,relatime shared:27 - debugfs debugfs rw
48 24 0:46 / /dev/hugepages rw,relatime shared:28 - hugetlbfs hugetlbfs rw,pagesize=2M
80 22 0:20 / /sys/kernel/config rw,relatime shared:29 - configfs configfs rw
82 22 0:47 / /sys/fs/fuse/connections rw,relatime shared:30 - fusectl fusectl rw
84 28 7:0 / /snap/core/3748 ro,nodev,relatime shared:31 - squashfs /dev/loop0 ro
86 28 7:1 / /snap/blender/12 ro,nodev,relatime shared:32 - squashfs /dev/loop1 ro
88 28 7:2 / /snap/core/3887 ro,nodev,relatime shared:33 - squashfs /dev/loop2 ro
90 28 7:3 / /snap/core/3604 ro,nodev,relatime shared:34 - squashfs /dev/loop3 ro
93 28 8:33 / /efi rw,relatime shared:35 - vfat /dev/sdc1 rw,gid=46,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
92 28 0:25 / /mnt/ROOT rw,noatime shared:36 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=5,subvol=/
100 28 0:25 /@lxd /var/lib/lxd rw,noatime shared:37 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=498,subvol=/@lxd
94 28 0:25 /@cache /cache rw,noatime shared:38 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=451,subvol=/@cache
96 28 0:25 /@home2 /home rw,noatime shared:39 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=500,subvol=/@home2
98 28 0:25 /@appli /appli rw,noatime shared:40 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=463,subvol=/@appli
102 28 0:25 /@data /data rw,noatime shared:41 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=464,subvol=/@data
104 28 0:25 /@opt /opt rw,noatime shared:42 - btrfs /dev/sdc3 rw,compress=lzo,ssd,space_cache,subvolid=440,subvol=/@opt
105 47 0:56 / /proc/sys/fs/binfmt_misc rw,relatime shared:43 - binfmt_misc binfmt_misc rw
388 28 0:59 / /var/lib/lxcfs rw,nosuid,nodev,relatime shared:257 - fuse.lxcfs lxcfs rw,user_id=0,group_id=0,allow_other
127 28 0:49 / /mnt/BACKUP rw,noatime shared:368 - btrfs /dev/sde1 rw,compress=lzo,space_cache,subvolid=5,subvol=/
472 100 0:63 / /var/lib/lxd/shmounts rw,relatime shared:383 - tmpfs tmpfs rw,size=100k,mode=711
480 100 0:64 / /var/lib/lxd/devlxd rw,relatime shared:390 - tmpfs tmpfs rw,size=100k,mode=755
458 26 0:62 / /run/user/130 rw,nosuid,nodev,relatime shared:262 - tmpfs tmpfs rw,size=1634948k,mode=700,uid=130,gid=137
667 26 0:67 / /run/user/1003 rw,nosuid,nodev,relatime shared:573 - tmpfs tmpfs rw,size=1634948k,mode=700,uid=1003,gid=1003
679 96 0:68 / /home/gaetanquentin-perso rw,nosuid,nodev,relatime shared:584 - ecryptfs /home/gaetanquentin-perso/.Private rw,ecryptfs_fnek_sig=1c3d846bedc670f4,ecryptfs_sig=8f85385bf3c6e37b,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs
685 679 0:69 / /home/gaetanquentin-perso/Cache rw,nosuid,nodev,relatime shared:589 - ecryptfs /cache/gaetanquentin-perso rw,ecryptfs_fnek_sig=1c3d846bedc670f4,ecryptfs_sig=8f85385bf3c6e37b,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs
691 667 0:70 / /run/user/1003/gvfs rw,nosuid,nodev,relatime shared:594 - fuse.gvfsd-fuse gvfsd-fuse rw,user_id=1003,group_id=1003
gaetanquentin-perso@gquentin-ssd-t3:~$ ls -lh /var/snap/lxd/common/lxd
ls: impossible d'accéder à '/var/snap/lxd/common/lxd': Aucun fichier ou dossier de ce type
-> no such file or directory
gaetanquentin-perso@gquentin-ssd-t3:~$ ls -lh /var/snap/lxd/current/lxd/
ls: impossible d'accéder à '/var/snap/lxd/current/lxd/': Aucun fichier ou dossier de ce type
-> no such file or directory

Hmm, did you remove the lxd snap? Looks like it's not installed anymore on that system.

yes i think i removed it. i did  that a few weeks ago so i d'ont remember exactly what happened. I remember only that the migration script never ended. And after that, containers disapperared.
since i have a new system to migrate to snap, and which has a mounted btrfs subvolume too in /var/lib/lxd, how should i do it?
you said a few days ago:
"You'd need to stop LXD, unmount the path, run the migration, then update your fstab to mount it at the new location and mount things again, then restart the snap."
but how can the tool script  migrate things if i unmount the /var/lib/lxd subvolume?
Content won't be here anymore.

Ok, so one issue that you might have run into is the weird way we store our database, it's something I intend to fix in the next couple of days, so I'd suggest you wait for that fix, then I'll let you know the migration steps at that point.

The database issue has been fixed so everything is now self-contained inside /var/snap/lxd/common/lxd, making it easier to transition such a system. I'll look into how lxd.migrate interacts with this and what can be done to improve.

I've made lxd.migrate aware of this and the new workflow looks like:
root@vm08:~# lxd.migrate
=> Connecting to source server
=> Connecting to destination server
=> Running sanity checks

=== Source server
LXD version: 2.0.11
LXD PID: 2695
Resources:
  Containers: 1
  Images: 1

=== Destination server
LXD version: 2.21
LXD PID: 3243
Resources:
  Containers: 0
  Images: 0
  Networks: 0
  Storage pools: 0

The migration process will shut down all your containers then move your data to the destination LXD.
Once the data is moved, the destination LXD will start and apply any needed updates.
And finally your containers will be brought back to their previous state, completing the migration.

WARNING: /var/lib/lxd is a mountpoint. You will need to update your /etc/fstab after the migration.

Are you ready to proceed (yes/no) [default=no]? yes
=> Shutting down the source LXD
=> Stopping the source LXD units
=> Stopping the destination LXD unit
=> Unmounting source LXD paths
=> Unmounting destination LXD paths
=> Wiping destination LXD clean
=> Moving the /var/lib/lxd mountpoint
=> Moving the database
=> Backing up the database
=> Opening the database
=> Updating the storage backends
=> Starting the destination LXD
=> Waiting for LXD to come online
=> Converting the network configuration

=== Destination server
LXD version: 2.21
LXD PID: 3493
Resources:
  Containers: 1
  Images: 1
  Networks: 0
  Storage pools: 1

WARNING: Make sure to update /etc/fstab to mount the right path on top of /var/snap/lxd/common/lxd

The migration is now complete and your containers should be back online.
Do you want to uninstall the old LXD (yes/no) [default=no]? yes

All done. You may need to close your current shell and open a new one to have the "lxc" command work.

Note that it may be a couple of days before this new code hits stable (it's currently in edge). I also need to do the same trick for those using a zfs dataset (slightly different variant of the same issue).


Discrepancies between tests

Describe the bug
The results of combinedTestReport and parallelCombinedTestReport don't match. In addition integrationTestReport does not produce a report. The combinedTestReport runs 10252 tests (with 274 failures) while the parallelCombinedTestReport runs only 9802 tests (with 103 failures). They also fail different tests:

Test
combinedTestReport
parallelCombinedTestReport

docking.widgets.filechooser
Failed
Passed

docking.widgets.table.threaded
Passed
Failed

ghidra.app.plugin.core.compositeeditor
Passed
Failed

ghidra.app.plugin.core.data
Passed
Failed

ghidra.app.plugin.core.datamgr.editor
Passed
Failed

ghidra.app.plugin.core.functiongraph
Passed
Failed

ghidra.app.plugin.core.functionwindow
Passed
Failed

ghidra.app.plugin.core.memory
Passed
Failed

ghidra.app.plugin.core.navigation
Passed
Failed

ghidra.app.plugin.core.progmgr
Passed
Failed

ghidra.app.plugin.core.script
Failed
Passed

ghidra.app.plugin.core.symboltree
Passed
Failed

ghidra.feature.vt.api
Failed
Missing

ghidra.feature.vt.api.correlator.address
Failed
Missing

ghidra.feature.vt.api.markupitem
Failed
Passed

ghidra.feature.vt.gui.provider
Failed
Missing

ghidra.feature.vt.gui.provider.functionassociation
Failed
Missing

ghidra.framework.main.datatree
Passed
Failed

ghidra.framework.plugintool.dialog
Passed
Failed

ghidra.framework.project.tool
Failed 2
Failed 1

ghidra.graph.viewer.edge
Failed
Passed

Note that in this table are only tests that failed in one of the runs, if a test passed in one and is missing in the other it is not in this table.
If tests where only failing extra on the parallel side, this could be blamed on running in parallel (and might still be for some tests). But this is not what is happening.
To Reproduce
Steps to reproduce the behavior:

gradle unitTestReport -PreportDir=../../unitTest
gradle integrationTest -PreportDir=../../integrationTest
gradle combinedTestReport -PreportDir=../../combinedTest
gradle parallelCombinedTestReport -PreportDir=../../parallelTest
Compare results of combinedTest and parallelCombinedTest
See that the integrationTest does not even produce a report

Expected behavior
Have the same amount of tests run and fail. Also have a test report from the integrationTest
Attachments
I've attached the test reports for unitTest, combinedTest and parallelCombinedTest
combinedTestReport.zip
parallelTestReport.zip
unitTestReport.zip
Environment (please complete the following information):

OS: Arch Linux (kernel 5.7.9)
Java Version: 11.0.8
Ghidra Version: Master (ac0a4c9)

Additional context

Test
Tests
Failures
Ignored
Duration
Percentage

unitTest
3735
0
0
12m18.58s
100%

combinedTest
10252
274
0
1h42m22.61s
97%

parallelCombinedTest
9802
103
0
4h52m57.23s
98%

Please note that the duration given is inaccurate, unitTest takes about 20m, combinedTest 2h45m, parallelCombinedTest not sure

For now, the parallel tests are considered to be a work-in-progress.     Running the tests in parallel exposes latent timing issues that do not often appear in the serial tests.
I am closing this ticket for now, as the work to fix this is ongoing, is low priority and will be a long-term project.


Es6modules only

It's really basic implementation. It only checks if AST of imported file contains one of these nodes types
[
'ExportDefaultDeclaration',
'ExportNamedDeclaration',
'ExportAllDeclaration',
'ExportSpecifier',
]

Coverage decreased (-0.06%) to 96.033% when pulling 69e939e969b80346bc8d013c6ab98810c8506ddb on dominiktilp:es6modules-only into e0403c6b836d812d650c1dfe85b4b2cd9004535a on benmosher:master.

Coverage decreased (-0.06%) to 96.033% when pulling 69e939e969b80346bc8d013c6ab98810c8506ddb on dominiktilp:es6modules-only into e0403c6b836d812d650c1dfe85b4b2cd9004535a on benmosher:master.

Coverage decreased (-0.06%) to 96.033% when pulling 69e939e969b80346bc8d013c6ab98810c8506ddb on dominiktilp:es6modules-only into e0403c6b836d812d650c1dfe85b4b2cd9004535a on benmosher:master.

Coverage decreased (-0.06%) to 96.033% when pulling 69e939e969b80346bc8d013c6ab98810c8506ddb on dominiktilp:es6modules-only into e0403c6b836d812d650c1dfe85b4b2cd9004535a on benmosher:master.

Of course, the situation about es6 modules is not ideal. But from my point of view, there is a lot of packages which is not used directly in node or browsers. And at the end, you are always traspiling at least your code to be sure that it will work in your target environment.

It’s never safe to transpile code you didn’t write. If a package ships “not ES5 CJS”in “main”, it’s a bug.

It’s never safe to transpile code you didn’t write. If a package ships “not ES5 CJS”in “main”, it’s a bug.

@ljharb Sorry for OT question but could you share a link/explanation of how/why it's unsafe?  thank you!

@coreyfarrell quite simply, transpilation is not 1:1; it can change hw the code behaves for certain edge cases (for example, arrow functions aren’t supposed to be constructible, but the default “loose” setting for them in babel allows them to be). You can’t know if the author was relying on all those caveats or not - you can only know that about your own code.


Use model alias?

Since January 2024, there is an alias gpt-4-turbo-preview for the last released gpt4 turbo model. We should consider using it if it turns out that repeaded updated models worked reliably. This might in particular become important once the turbo-vision model comes out, which is mentioned here: https://openai.com/blog/new-embedding-models-and-api-updates
Quote:

... one argument against: If we use the alias, it would be harder to document which model was actually used under the hood.

Closing this for the sake of reproducibilty.


Link to /data from each city

From the city view screen, in addition to the existing menu items, there should be a link that points to the Data screen. The label could be "Data". The URL should be something like /data?city=buenos_aires#city. The hash (#city) refers to the last section of the page, where there is a select control to choose the city, which should be the city passed in the city param from the query.
Things to consider:

The implementation of the hash can be similar to the one in the Terms component.
All the new text has to be i18nized. New entries have to be added to the files in api/config/locales.

@BrunoSalerno Just to clear some terminology up here, does this Issue refer to adding a new link on each City page which links to the Data page with a pre-selected option in the "Data by city" dropdown?

@christaylor19 yes, exactly!


SetProperties value is often '?' in node and the wrong type in form

See attached. The Value property doesn't appear to serialize correctly. Schema mismatch?

Note:
Today we currently remove any empty object and empty arrays in sanitizeDialogData. We could update that function to also look at the schema to determine whether or not we want to do that.
Another option is to have default serializers in the form that do the sanitization work which can be overridden on a per-property basis.

The schema is outdated:

Two more related problems:

The logic is wrong if the value is set to false or 0. in SetProperty, it should be ?? instead of ||
The content displayed inside SetProperty and SetProperties are not consistent.

I will create a PR for fixing that, focusing on optimize the node content of SetProperty(s)

Some other problems I found in Form side

when the value type is set to 'object' or 'array', action.value equals undefined rather than the displayed value in JSON editor;
when the value type is set to 'array', JSON editor displays {} which should be []

addressed Visual Editor part in #2936

Thanks @yeze322, merged. I will try to address the other issue in the coming week.


bluetooth: hci: spi: 0xFF is a valid payload length

A payload size of 0xFF is valid and should not be a reason to keep looping for more headers. The complete reqiurement is now:
header_slave[STATUS_HEADER_READY] == READY_NOW &&
header_slave[STATUS_HEADER_TOREAD] > 0

This fixes events being dropped when the payload size is 255.

@JordanYates did you figure out why there was a check for 0xff?
I'm wondering if it is related to this
(void)memset(&txmsg, 0xFF, SPI_MAX_MSG_LEN);

@JordanYates did you figure out why there was a check for 0xff?
I'm wondering if it is related to this
(void)memset(&txmsg, 0xFF, SPI_MAX_MSG_LEN);

It's been there since the driver was added 7 years ago, so I'll take my best guess.
The purpose of the check if to validate that the controller is ready to send the payload, and if not, check again.
If the controller is not ready, the line state, and hence the received data, will be 0x00 or 0xFF, depending on the controller SPI slave implementation.
The original condition did not include header_slave[STATUS_HEADER_READY] == READY_NOW.
The original check was probably trying to check against the idle line state, but missed the simplest solution of checking header_slave[STATUS_HEADER_READY] == READY_NOW.


npm versions higher than 6.1.0 cannot be installed

actually, the hpm repository changed.
Error is:
Error: Failed to read response from https://codeload.github.com/npm/npm/tar.gz/v6.4.1
    at Request.<anonymous> (C:\ws\nodist\lib\build.js:110:25)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at Request.onRequestResponse (C:\ws\nodist\node_modules\request\request.js:954:10)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:473:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
    at TLSSocket.socketOnData (_http_client.js:362:20)
    at emitOne (events.js:96:13)
    at TLSSocket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at TLSSocket.Readable.push (_stream_readable.js:134:10)
    at TLSWrap.onread (net.js:551:20)

because the correct URL now is:
https://codeload.github.com/npm/cli/tar.gz/v6.4.1

instead of
https://codeload.github.com/npm/npm/tar.gz/v6.4.1

hmm. fixed also by #217. How about merging it?

A new version is coming out today that merged #222 to fix this issue.


update docs folder links

Q
A

Is bugfix?
✔/❌

New feature?
✔/❌

Breaks BC?
✔/❌

Fixed issues

👍🏻


"No Provider For ViewContainerRef" in NotificationService

Detailed description
Using the latest carbon-components-angular v5.14.11 with Angular v14.3.0.
When using the NotificationService (i.e. referring to showNotification() method), the UI fails to load. It shows the stacktrace referenced below.
This did not occur in 5.1.0.
Additional information
Unhandled Promise rejection: NullInjectorError: No provider for ViewContainerRef! ; Zone: <root> ; Task: Promise.then ; Value: NullInjectorError: NullInjectorError: No provider for ViewContainerRef!
    at NullInjector.get (core.mjs:8191:27)
    at R3Injector.get (core.mjs:8618:33)
    at R3Injector.get (core.mjs:8618:33)
    at R3Injector.get (core.mjs:8618:33)
    at injectInjectorOnly (core.mjs:4782:33)
    at Module.ɵɵinject (core.mjs:4786:12)
    at Object.NotificationService_Factory [as factory] (carbon-components-angular-notification.mjs:856:1)
    at R3Injector.hydrate (core.mjs:8719:35)
    at R3Injector.get (core.mjs:8607:33)
    at injectInjectorOnly (core.mjs:4782:33) NullInjectorError: NullInjectorError: No provider for ViewContainerRef!
    at NullInjector.get (http://dev.local/vendor.js:484509:21)
    at R3Injector.get (http://dev.local/vendor.js:485012:27)
    at R3Injector.get (http://dev.local/vendor.js:485012:27)
    at R3Injector.get (http://dev.local/vendor.js:485012:27)
    at injectInjectorOnly (http://dev.local/vendor.js:480533:29)
    at Module.ɵɵinject (http://dev.local/vendor.js:480538:59)
    at Object.NotificationService_Factory [as factory] (http://dev.local/vendor.js:562600:204)
    at R3Injector.hydrate (http://dev.local/vendor.js:485126:29)
    at R3Injector.get (http://dev.local/vendor.js:485002:23)
    at injectInjectorOnly (http://dev.local/vendor.js:480533:29)

Is there any update for this issue. I am also facing same error.

No update yet. If i find anything, i'll make sure to let you know.


Deployment fail on precompile -> compilation step. Possible memory leak?

Important: GitHub issues are for feature requests or bug reports. The Capistrano team recommends you use Stack Overflow for general questions. For more details, please see our contribution policy.

Steps to reproduce
rspec pipeline testing with same command succeeds and local bundle exec rake assets:precompile also succeeds with no issues. But when I try and deploy, I get the following error. From researching, my speculation is that it may be a memory leak issue. My confusion comes from where I did not change anything that is related to deployment since last deployment, but I am getting this error all of the sudden.
00:10 deploy:assets:precompile
      01 /usr/local/rvm/bin/rvm default do bundle exec rake assets:precompile

      01
      01 yarn install v1.22.5

      01
      01 [1/4] Resolving packages...
      01
      01
log writing failed. "\xE2" from ASCII-8BIT to UTF-8
      01 ⠁
      01

[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.

info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.

      01
      01 [3/4] Linking dependencies...
      01

      01
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
      01

      01
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
      01

      01
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>      01

      01
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 15.x.x || 16.x.x".
      01

      01
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 15.x.x || 16.x.x".
      01

      01
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ~0.14.x || ^15.0.0 || ^16.0.0".
      01

      01
      01 warning "react-router-dom > react-router ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>||…
      01

      01
      01 [4/4] Building fresh packages...
      01

      01
      01 Done in 10.49s.
      01 Compiling...
      01 Compilation failed:
      01 events.js:174
      01       throw er; // Unhandled 'error' event
      01       ^
      01
      01 Error: write EPIPE
      01     at ChildProcess.target._send (internal/child_process.js:762:20)
      01     at ChildProcess.target.send (internal/child_process.js:634:19)
      01     at ChildProcessWorker.send (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/w…
      01     at WorkerPool.send (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/WorkerPoo…
      01     at Farm._process (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/Farm.js:129…
      01     at Farm._enqueue (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/Farm.js:152…
      01     at Farm._push (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/Farm.js:159:12)
      01     at Promise (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/Farm.js:90:14)
      01     at new Promise (<anonymous>)
      01     at Farm.doWork (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worker/build/Farm.js:56:12)
      01     at JestWorker._callFunctionWithArgs (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/jest-worke…
      01     at TaskRunner.runTask (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/@rails/webpacker/node_mo…
      01     at enqueue (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/@rails/webpacker/node_modules/terse…
      01     at cache.get.then (/var/www/vhosts/admired-leadership/releases/20230125154033/node_modules/@rails/webpacker/node_module…
      01 Emitted 'error' event at:
      01     at process.nextTick (internal/child_process.js:766:39)
      01     at process._tickCallback (internal/process/next_tick.js:61:11)
      01
#<Thread:0x000000011aaff850@/Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
	13: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
	12: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:31:in `run'
	11: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:31:in `instance_exec'
	10: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/capistrano-rails-1.4.0/lib/capistrano/tasks/assets.rake:67:in `block (4 levels) in <top (required)>'
	 9: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:92:in `within'
	 8: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/capistrano-rails-1.4.0/lib/capistrano/tasks/assets.rake:68:in `block (5 levels) in <top (required)>'
	 7: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:100:in `with'
	 6: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/capistrano-rails-1.4.0/lib/capistrano/tasks/assets.rake:69:in `block (6 levels) in <top (required)>'
	 5: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:80:in `execute'
	 4: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:148:in `create_command_and_execute'
	 3: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:148:in `tap'
	 2: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:148:in `block in create_command_and_execute'
	 1: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/netssh.rb:169:in `execute_command'
/Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/command.rb:97:in `exit_status=': rake exit status: 1 (SSHKit::Command::Failed)

Expected behavior
Deploys with successful compilation
Actual behavior
Fails with the error mentioned above.

EPIPE usually indicates that something like foo | bar (i.e piping output of foo into bar), which can also happen when a parent child spawns a child process and uses a "pipe" to connect the stdout, or some other stream from the parent into the stdin (or some other stream) in the child.
Your intuition is probably correct, it for sure means that a process you were writing to in the parent died, probably the bundler, and possibly because of OOM.
Depending heavily on your OS, configuration, and the hosting platform you use, there could be a number of ways to find out. I suggest you look for ways to see the kernel logs, systemd journal, or at least the "OOM killer" logs (which may be in the kernel logs, or systemd journal)
Sorry we can't help more, but to confirm your suspiscion that it's a system-specific issue you are facing due to your OS configuration or machine sizing.

Thank you for your response. Regarding your point about confirming my suspicion on a system-specific level, I'm assuming the remote system I'm deploying to would be the issue and not locally correct?
To trail off that point, I've updated the node version on the remote system and the error I'm receiving is a bit different. Wondering if this changes your speculation
00:11 deploy:assets:precompile
      01 /usr/local/rvm/bin/rvm default do bundle exec rake assets:precompile

      01
      01 yarn install v1.22.5
      01

      01
      01 [1/4] Resolving packages...
      01
      01
log writing failed. "\xE2" from ASCII-8BIT to UTF-8
      01 ⠁
      01
log writing failed. "\xE2" from ASCII-8BIT to UTF-8
⠂<EMAIL_ADDRESS>log writing failed. "\xE2" from ASCII-8BIT to UTF-8
⠄<EMAIL_ADDRESS>
      01
[2/4] Fetching packages...
      01

info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.

info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...

      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".

      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".

      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>
      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 15.x.x || 16.x.x".

      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 15.x.x || 16.x.x".

      01 warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ~0.14.x || ^15.0.0 || ^16.0.0".
      01
warning "react-router-dom > react-router ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17…
[4/4] Building fresh packages...

      01 Done in 11.78s.
      01 Compiling...
      01 Compilation failed:
      01
#<Thread:0x000000014748b5a0@/Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
        13: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
        12: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:31:in `run'
        11: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:31:in `instance_exec'
        10: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/capistrano-rails-1.4.0/lib/capistrano/tasks/assets.rake:67:in `block (4 levels) in <top (required)>'
         9: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:92:in `within'
         8: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/capistrano-rails-1.4.0/lib/capistrano/tasks/assets.rake:68:in `block (5 levels) in <top (required)>'
         7: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:100:in `with'
         6: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/capistrano-rails-1.4.0/lib/capistrano/tasks/assets.rake:69:in `block (6 levels) in <top (required)>'
         5: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:80:in `execute'
         4: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:148:in `create_command_and_execute'
         3: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:148:in `tap'
         2: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/abstract.rb:148:in `block in create_command_and_execute'
         1: from /Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/backends/netssh.rb:169:in `execute_command'
/Users/jaepark/.rvm/gems/ruby-2.6.6/gems/sshkit-1.19.1/lib/sshkit/command.rb:97:in `exit_status=': rake exit status: 1 (SSHKit::Command::Failed)
yarn install v1.22.5

I have removed node_modules and ran yarn and also ran bundle install. May be related to sshkit? I guess that leads to my question of what could've changed with sshkit that is causing this if this is the culprit. I've compared sshkit versions across different commits and it's constant.
Thanks for your time

Lack of memory space in remote system was the issue. Issue resolved by expanded memory by adding swap space. Thank you @leehambley for your time.


Improve downloader

Code refactoring and thread refactoring.

Coverage increased (+0.1%) to 0.763% when pulling c054e6bbd4fc86a7d4130d85c11ab2abf091acb0 on improve-downloader into e46c0d16573ab354a6af327c9fcd6540a65c0212 on develop.


androidx.work.impl.utils.ForceStopRunnable in setAlarm$13462e - java.lang.SecurityException

Stack Trace
java.lang.SecurityException: get application info: Neither user 1110087 nor current process has android.permission.INTERACT_ACROSS_USERS.
at android.os.Parcel.readException(Parcel.java:1599)
at android.os.Parcel.readException(Parcel.java:1552)
at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:225)
at android.app.AlarmManager.setImpl(AlarmManager.java:469)
at android.app.AlarmManager.setExact(AlarmManager.java:407)
at androidx.work.impl.utils.ForceStopRunnable.setAlarm$13462e(ForceStopRunnable.java:133)
at androidx.work.impl.utils.ForceStopRunnable.isForceStopped(ForceStopRunnable.java:89)
.run(ForceStopRunnable.java:72)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)

Thanks for reporting this.
I'm closing this issue because I cannot reproduce it in this codelab.
If you think that this is a problem of the WorkManager library, please open a bug on the WorkManager public issue tracker: https://issuetracker.google.com/issues/new?component=409906&template=1094197
Please reopen if you still think this is an issue with the codelab.


add totalCount to edges and node

There's a decent amount of build up that goes into getting the arrayLength of the connectionFromArraySlice (and the sliceStart for that matter) when dealing with large collections.
Instead of swallowing them up, it'd be useful to expose arrayLength as totalCount right next to the edges and pageInfo?
Just a general idea. What do you think?
Addendum: http://stackoverflow.com/a/38308189/381285

Continued in https://github.com/graphql/graphql-relay-js/pull/109.


Dev search v108

Test server : http://gofullstack.me:3001/

#464 Some improvement in styles in report view
#515 Timeline can is live:

If there is new tweets, it will show a small notice like search

There is a background process that update your timeline after 20s, then 31s, 42s, 53, .... you can use a timer to track the log in console with the msg (Getting newer tweets), or just feel it :+1:
The "age" of tweet (2m in the picture below) is updated every 10secs

works for me. nice!


Added auto-population of address field when user selects location from map

Thank you Arman @mdarman1124 for this.
The no. of fields the user has to type is reduced to just one now.


feat: Misc. (#9)

feat: BSRandom.

feat: Inline function as it should be.

feat: More misc. RE'ing.

feat: AimModel RE.

feat: Update IDs.

feat: Missing import

I'm confused as to how it's compiling, but that BSRandom function isn't calling func

And now with func in place, it fails to build?

Remove the extra closing bracket

Good catch! Should all be good to go.


Camera selection

Browsers like Chrome on Desktop/Android don't expose the sourceInfo.facing property, thus setting the facing config value of Quagga to "environment" or "user" doesn't work. Another way to select the camera is by index and this is implemented in the PR. Feel free to adapt/improve as you like, since it's a pretty simple solution.
Btw: sooner or later a switch should be done away from MediaStreamTrack: https://www.chromestatus.com/feature/4765305641369600... perhaps I'll fix it in an upcoming commit.

Hi @JauernigIT, I've been working on moving towards the new MediaDevices API and already created a branch for that. This feature also includes the ability to select the camera via deviceId. You can check out the feature in feature/#93. I'll add some tests and merge it to master ASAP.

This facingMode thing is currently not working for me in Chrome 49 on desktop. This was why I needed an alternative function how to choose the camera... for me it was/is best by index. deviceId is also fine for me, but then Quagga should expose a method which returns the available devices with the corresponding device IDs.

Well, that's the reason why I implemented a fix for chrome which still uses the old API to query the devices. With this, and some normalization, it works in Chrome, as well as in Firefox and Edge. Have you tested it yet? I hope to get the documentation ready in the next two days, because I want to publish a new release ASAP.

Yes, I have tested it, but it didn't work with feature/#97 on desktop Chrome 49. The sourceInfo.facing property in applyCameraFacing() is empty string. Don't know if it depends on the hardware, too (didn't think it would). I've tested it on a Surface Pro 4 (has front and rear camera).
On the other hand, it seems to work in Chrome on Android...

Thanks a lot for testing. I don't have a windows device with front/back-facing camera. Well, that's a pitty then, because the new property facingMode which can be set in the constraints (Chrome 49), is taken into consideration on the desktop, but not on mobile (not implemented yet). That's the reason why I implemented the workaround through MediaStreamTrack.getSources().
But since this branch includes the adapter.js polyfill, you can use enumerateDevices to query your devices. Does this help?

Yeah, I thought of testing it with the adapter.js polyfill and using mediaDevices.enumerateDevices(). I'll test it today evening and give you a feedback.

Ok, mediaDevices.enumerateDevices() returns all devices as array of MediaDeviceInfo for all common browsers (Chrome, Firefox, Edge). Unfortunately, the spec doesn't expose a facing property, thus we can't get the camera facing out of this API. So it seems to be worthless for our aim.

Is the facing info really such important for barcode scanning? I think it is much more important to select the camera with the best resolution/quality for best scanning results. The user usually should be able to point the object with the barcode to each camera (front or back).
Btw, in nearly all devices the facing camera has a lower resolution than the camera pointing to the environment. So, if You can analyze the camera resolution, You also can estimate which one is facing.

How would you analyze the camera resolution? Using the constraints and check whether it throws an error or not? I think  it's quite important to select the user's camera up-front. Firefox makes it easier due to the select-box which shows up upon requesting the camera. In Chrome, this must be implemented by the site-owner.
However, this issue should now be resolved with the latest release. See 0.10.0 Release

@sascha-hendel Perhaps you are mistaken by naming. facing doesn't mean the camera that is oriented to your face. By setting facing to "environment" or "user", you are able to choose the camera explicitly and since the default in most cases is the front-facing camera ("user"), you have to be able to choose the back-facing one ("environment").


Support kafka transactional topics (#5404)

update kafka version to latest v2.0.0
Remove the skipOffsetGaps option since it's not used or required anymore
Adjust kafka consumer to use transactional semantics
Update tests
Update docs

@surekhasaharan There's an unused import that is tripping the CI:
[ERROR] /home/travis/build/apache/incubator-druid/extensions-core/kafka-indexing-service/src/test/java/org/apache/druid/indexing/kafka/KafkaIndexTaskTest.java:187:8: Unused import - java.util.concurrent.atomic.AtomicInteger. [UnusedImports]

Meant to fix #5404. (Just commenting here so it shows up in the PR links. @surekhasaharan - FYI - I see you included it in the title but GitHub doesn't automatically create links out of the title. It should be in the description or commit message.)

Meant to fix #5404. (Just commenting here so it shows up in the PR links. @surekhasaharan - FYI - I see you included it in the title but GitHub doesn't automatically create links out of the title. It should be in the description.)

ok thanks, good to know.

thanks @gianm , IT test failure looks legit, I will take a look.


Update Weather-App.md

Weather App by Flutter
This Weather App is a Flutter-based mobile application that provides real-time weather information for any location around the world. The app is designed to offer a simple and user-friendly interface for users to access current weather conditions, forecasts, and other relevant weather data.
Features
1. Real-Time Weather Data: Get the current weather conditions including temperature, humidity, wind speed, and more.
2. Search Functionality:  Users can search for weather information for any location by entering a city name or using GPS to find their current location.
3. Weather Forecast: Provides a 7-day weather forecast with detailed information about daily weather conditions.
4. Dynamic UI: The app adjusts its UI dynamically based on weather conditions, displaying relevant icons, animations, and background images for different weather scenarios (e.g., sunny, rainy, cloudy, etc.).
5. Location-Based Weather: Automatically fetches the weather data based on the user’s current GPS location.
6. Unit Conversion: Supports temperature conversion between Celsius and Fahrenheit.
7. Clean UI/UX: A visually appealing and intuitive interface for easy navigation and interaction.
8. Error Handling: Graceful error handling for cases like network issues, invalid city names, or permission denial for location access.
Below is the link of the App from by github repo.
[https://github.com/akshit397a/FlutterDev/tree/main/MainApp/WeatherApp/lib]

hey, @florinpop17 @jrubins @jdmedlock @chevcast @ideabrian @diogomoreira @gualexfer @twhite96
Kindly tell be if it could be merged.

Uhh, why am I tagged in this?


Start work on the architectural refactor

So, it's finally time:  I've gotten around to starting work on the big refactor that got more and more inevitable from issues like #114, #94, and #117.
Right now, the state is just barely enough to blink an LED on Arduino Uno.  I wanted to get this out as quickly as possible to initiate discussions on the design.  As this work will take a while to complete, we will go about it like this:  master stays with the current architecture for now until the new design reaches feature-parity.  Until then, we will use the next branch to get it there.  Thus, this PR will be merged into next instead of master.
TODO

[x] Re-write documentation for the port module.
[x] Test integration with the already refactored USART.
[x] Add basic Arduino Leonardo support to see how that works out.

As a short breakdown for anyone interested:

mcu/atmega-hal/ is the new unified HAL for ATmega MCUs
arduino-hal/ is the unified board support crate for Arduino boards
examples/arduino-uno/ is the new place for examples (for Arduino Uno)

I.e. the POC example is now examples/arduino-uno/src/bin/uno-blink.rs and you can run it by
cd examples/arduino-uno
cargo run --bin uno-blink

Added support for basic USART, to see how it works out... I ran into one issue which popped up due to the new pins architecture: The current USART code was running into the orphan rule because UsartOps is implemented in avr-hal-generic and USART0 is from avr-device (and the Pin is now from avr-hal-generic while it was previously part of the HAL crate).
I've mitigated this by wrapping the "raw peripheral" from the PAC in a RawPeripheral wrapper.

All basic features for two boards are there now, looking okay so far.  One big thing I am still unsure about:  Right now I have each HAL and board-crate redefine the Peripherals struct.  This is super-convenient but has one big drawback:
Either, only peripherals with a HAL implementation are available or we'd have to explicitly name all not-yet-supported peripherals for each supported MCU individually.  I think option 1 would make the HAL pretty much unusable, but option 2 is a lot of manual code-writing...
Anyone has ideas for an alternative solution?

@explicite, if you want to work on Arduino Mega2560 support, these commits can probably serve as a good basis:

356090d155e2 ("atmega-hal: Add support for ATmega32U4")
5304fd0d923c ("arduino-hal: Add support for Arduino Leonardo")
8f6928cbfd26 ("Add example crate for Arduino Leonardo")


Client crash searching ores in JEI serch with AE mod?

AE2 version: RV6-Stable-3
Mystical World Version: 1.12.2-1.0.1
Forge Version: 1.12.2-<IP_ADDRESS>72
When searching for tin or bronze metals in JEI the client will crash to desktop. I tried disabling the metals/ores in the mystical world config but still get the same result. The crash log states its a facade but unsure why.
If you remove/disable the Mystical World mod and do the search again the game is fine. Not sure what is causing this is it a metals conflict possibly or a AE2 problem? Thanks for your help and work reviving this mod btw the mobs are great.
Basically this:
Ingredient Mod: Applied Energistics 2
Ingredient Info: 1xitem.appliedenergistics2.facade@0 appliedenergistics2:facade nbt:{damage:0,item:"mysticalworld:copper_block"}
crash-2018-11-06_21.58.48-client.txt
crash-2018-11-05_23.09.13-client.txt

Can you post this on the ae2 issue tracker too? I believe this is an issue with how code chicken lib and mystical lib interact...

ok sure no problem, thanks for checking into this, Question if ores are enable/disabled in the mystical world.cfg how will that effect ore gen in worlds that have immersive engineering ore gen enabled. we implemented this in our pack but I didn't disable the ores in the mystical world.cfg. Will we have to turn on IE retro ore gen if disabling the ores in mystical worlds mod? Thanks

It's reported now at https://github.com/AppliedEnergistics/Applied-Energistics-2/issues/3810

Thanks for you help in checking on this.


Fix Travis build

The build is currently failing on Travis. I believe this is unrelated to #338.

Using git bisect it seems 69a2d1d410220a688ad169366d0d20e138e264f6 broke ms_transform_SUITE.

It looks like lfe_ms:is_ms_func/3 fails for the records tests and also lfe_ms:expr/2 doesn't have a function clause for, e.g.
expr([[rec,[object]]], #ms{dc=1,bs=[],where=guard}).

/cc @rvirding

I think one problem is that the new testing of the record in the record macros is done using a let to ensure that the record argument is only evaluated once. This is not a problem in the body but lets are not allowed in the guard. This will mean some more study of how erlang does it.

I now see that lets are allowed in guards but only in a restricted way. Still testing though. With a bit of luck we can have testing in the record macros.

The problem is accessing record keys in the guard and body. I will look at fixing that.
However I saw that there was another Travis problem which also occurred before I made my fix. When testing with R16 and 17 versions there is a problem compiling proper. It worked when building v1.2.1 so I am guessing it is a recent version. Any suggestions welcome. Can rebar3 handle having different dependencies for for different OSs?


Jodit does not work in popout windows

I'm using Jodit in my main app as well as a popout window. I'm passing in ownerDocument and ownerWindow for the document and window of the popout.
Jodit works nicely in the main app, and displays ok in the popout, but as soon as you attempt to do something like drop an image, you get an error at:
if (!Dom.isNode(node, this.win)) {
    throw new Error('Parameter node most be instance of Node');
}

in insertNode, Selection.ts:481
this.win refers to the window of the popout (good), but the node has been created via the document of the main window. insertNode in this case was being called from insertImage, which uses this.jodit.create.inside.element('img'). this.jodit is a Jodit object and it inherits create from Panel.ts. The main issue is that Panel is expecting a jodit object so that it can obtain the ownerDocument and ownerWindow, which is not possible since we cannot pass ourselves "this" from Jodit constructor all the way up to Panel.ts.
Jodit Version:  3.2.28
Expected behavior:
Jodit should work in a popout
Actual behavior:
Errors since the ownerDocument and ownerWindow do not reference the correct window in the Create instance.

As a hack, I've added
this.create = new Create(
    this.ownerDocument,
    this.editorDocument
);

to Jodit.constructor which fixes the above issue, but there are other problems in the popout that are not present when in the main document. I'm investigating those now.

Fixed in 3.2.42


Hyper-V and fat and ntfs and locking

[Enter feedback here]

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

ID: 96887ea3-60f9-4e2f-c719-0abd6759b8fe
Version Independent ID: cc4e8521-9821-9bbb-ff13-bc1c54de6c44
Content: Get-VM (Hyper-V)
Content Source: docset/winserver2022-ps/hyper-v/Get-VM.md
Product: w10
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Add support for host-created EmptyDir

Is your feature request related to a problem? Please describe.
Kubernetes EmptyDirs are sometimes used as a way to share data from the host to a guest. The work done in #1485 drastically improved performance for most use-cases, but broke host->guest sharing of files.
Describe the solution you'd like
A flag in the configuration that disables guest-created EmptyDirs, allowing users to fall back to slower, host-created ones.
Describe alternatives you've considered
Unfortunately, there aren't really any other good solutions to the problem my org is using EmptyDir to solve. There are multi-tenancy issues with host volumes, and our use-case relies on linking container logs on the host to a logging container in a pod.
Additional context
I've already implemented this and my org is running a fork with a disable_guest_empty_dir flag, but I'd like to gauge upstream's interest in this. It's a very small changeset (+42 -11) and would allow folks to use EmptyDir with Kata in this way again.
Before raising this feature request
Have you looked at the limitations document?
Yes.

Please assign this to me.

done, thanks

cc @awprice

I suspect we should discuss if we want this to be a pod annotation rather than another config file option - we are trying to reduce/move away from/limit our config file bloat. And, this feels more like a per-pod choice than a whole stack choice? /cc @amshinde

👍 This change seems reasonable to me.

If we were to add this, I think we need to support this as an annotation in addition to the config option to allow configuring this on a per pod basis.
@evanfoster Do volumes based on hostPath not fit your requirements?

Unfortunately not. We evaluated hostPath, but it's not really compatible with how we run our clusters (for example, hostPath breaks multi-tenancy).
I'm absolutely not opposed to adding an annotation as well. Being able to set the default to host-created or guest-created emptyDirs and then allowing users to selectively override per pod would be really nice.

We actually have a perfect use-case for that annotation. Since the config option is disable_guest_empty_dir and is under the runtime section, would the appropriate annotation be io.katacontainers.config.runtime.disable_guest_empty_dir ?

We actually have a perfect use-case for that annotation. Since the config option is disable_guest_empty_dir and is under the runtime section, would the appropriate annotation be io.katacontainers.config.runtime.disable_guest_empty_dir ?

Yes, sounds right.

Running into a snag with this. The annotation needs to be applied at container creation time, but it's only being passed to the runtime during sandbox creation time. Is there a decent way to persist the annotation from sandbox to container creation? I've been digging, but I haven't found anyone else doing so yet.

I've been keeping the config-only version of this up to date in my fork, and I'd love to see it upstreamed if possible. I'm still not sure if I'd be able to support annotations, however.

@evanfoster - can you create an RFC PR for us to look at and comment on?
/cc @egernst for thoughts too.


fix: update readme to give more context to how the game works

This gives a better explanation to how the app is working, and what's needed to run the app with cloud connection.

)
Closes #22

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


viewing the model

I've used this pacakge a few months, ago, and I remember I was able to do $head model, and to see the model weights.
It seems that the model is now encoded somehow (binarized?) am I correct? is there a way to see the model as before?

Yes, we store binary format now because the text format is too slow. We will provide a tool to view the model in the next major release, but for now there is no way to view the model. If you have such need, please use the previous version (v114).


Modeling 'Therapeutic Intervention' (as a Domain Entity)

We need to model an object for type/class-level representations of Therapeutic Interventions (as opposed to specific instances that occur on specific occasions toward particular patients).  The driving use case for this is the descriptor/object in Therapeutic Response Annotations, as described in #31.  A few initial thoughts are below:

A therapeutic intervention is a process in which some form of treatment is administered to a patient - be it chemical (e.g. a drug), physical (e.g. acupuncture, radiation), behavioral, etc.
The model will have to support simple interventions comprised of a single type of drug exposure, and combination treatments that include multiple exposures/interventions as part (e.g. multiple drugs).
It may also need to support modeling of temporal aspects of interventions - including things like sequence in which interventions are applied, intervals between interventions, dosage or duration of treatments, etc.
It may have to include representations of specific drugs (e.g. erlotinib) as well as drug categories (e.g. EGFR inhibitors)

Once we have clearly defined requirements and a straw man proposal, we should reach out to other GA4GH groups that may have need for a similar object (e.g. ClinPheno), and also consider if/how we might leverage SchemaBlocks here.

For now (for v0) we have defined the very simple and naive model here, which will support initial testing, but ultimately be replaced by a richer model developed in collaboration with other groups.


Bug with TagAssign

In out CI pipeline we do
opslevel create service tag rails_webapp minimum-test-threshold ${TESTS_RAN} --assign

But we end up with 2 tags on the service
Key: minimum-test-threshold
Value: 15415

Somewhere between v2022.9.19 and 2023.7.19 is a bug that breaks TagAssign calls because the API receives
tags"=>[{"key"=>"Key", "value"=>"minimum-test-threshold"}, {"key"=>"Value", "value"=>"15415"}

but should actually be
tags"=>[{"key"=>"minimum-test-threshold", "value"=>"15415"}

It seems in https://github.com/OpsLevel/cli/commit/25703267b32cd7c61b44d6b9ce8ce6129c31977b we changed the signature of opslevel-go AssignTags function and this is likely the culprit but we will need to investigate whats causing the problem, ensure we have proper and correct tests, and ensure we fix the problem in the CLI (we might want to double check Terraform too)

https://github.com/OpsLevel/cli/pull/150


Suggestion: date() type

Love the work done with V1. Type inference is so much better and more useful.
However having dates properly typed as Date on the FormattedItem is still a little tricky.
I am suggesting the date() type as quality of life feature:
startAt: date().required()
Since dynamo does not have a Date type the toolbox would convert the date to a string (ISO) or a number (epoch)  before saving and convert it back when retrieving.
The same logic could be applied to timestamps fields to have them properly typed as dates as well.
I know that this can already be achieved with a little extra code, but having a native toolbox implementation would be a great QOL improvement.

Good idea ! Will include it in the roadmap, but there are some other work in progress with higher prios right now, so probably in a few months

@lucas-subli Would you like it to resolve to a Date object ? Or a string/number would do the trick ?

Ideally I would like to resolve to a Date in the FormattedItem and also be able to pass in a date for create / update operations.


futil not found when running outside of calyx/ dir

I've built Calyx inside a Docker image with the following:
RUN cargo build --manifest-path ./calyx/Cargo.toml \
  && cargo install runt \
  && FLIT_ROOT_INSTALL=1 flit -f ./calyx/fud/pyproject.toml install -s --deps production \
  && mkdir /root/.config \
  && fud config global.futil_directory /root/calyx

When I then run:
docker run -it my-image bash -c 'fud config global.futil_directory /root/calyx && fud e calyx/examples/tutorial/language-tutorial-iterate.futil \
  -s verilog.data calyx/examples/tutorial/data.json \
  --to dat --through verilog -v'

I get:
✖ futil.run_futil
[fud] ERROR: `./target/debug/futil -l /root/calyx -b verilog' failed:
=====STDERR=====
/bin/sh: 1: ./target/debug/futil: not found

=====STDOUT=====

Things work if I cd first, though:
docker run -it my-image bash -c 'cd calyx && fud config global.futil_directory /root/calyx && fud e examples/tutorial/language-tutorial-iterate.futil \
  -s verilog.data examples/tutorial/data.json \
  --to dat --through verilog -v'
✔ futil.run_futil
✔ transform
✔ verilog.mktmp
✔ verilog.json_to_dat
✔ verilog.compile_with_verilator
✔ verilog.simulate
✔ verilog.output_json
✔ verilog.cleanup
{
  "cycles": 85,
  "memories": {
    "mem": [
      42
    ]
  }
}

Does fud have to use a relative directory for futil? I would expect to be able to use fud from anywhere.

Hmm; that's odd! My best guess is that your cargo build command is building the library only, not the executable. There's a Cargo.toml at the root that is for the compiler executable, as well as in the calyx subdirectory (which it currently looks like you're building) that is just for the core library.
Barring that, can you do us a quick favor and run a plain ol fud config inside the container to see if that fud config global.futil_directory /root/calyx command took hold correctly?

Actually, that doesn't explain why it would work when you cd to the right place. So my best guess is now the configuration thing…

[global]
futil_directory = "/root/calyx"

[stages.futil]
exec = "./target/debug/futil"
file_extensions = [ ".futil",]

[stages.interpreter]
exec = "./target/debug/interp"
round_float_to_fixed = true

[stages.debugger]

[stages.dahlia]
exec = "dahlia"
file_extensions = [ ".fuse", ".dahlia",]

[stages.verilog]
exec = "verilator"
file_extensions = [ ".v", ".sv",]
cycle_limit = 500000000
top_module = "main"
round_float_to_fixed = true

[stages.vcd]
exec = "vcdump"
file_extensions = [ ".vcd",]

[stages.vcd_json]
file_extensions = [ ".json",]

[stages.jq]
exec = "jq"

[stages.dat]
file_extensions = [ ".dat",]

[stages.relay]
file_extensions = [ ".relay",]

[stages.systolic]
file_extensions = [ ".systolic",]

[stages.synth-verilog]
exec = "vivado"
ssh_host = ""
ssh_username = ""

[stages.vivado-hls]
exec = "vivado_hls"
ssh_host = ""
ssh_username = ""

[stages.xclbin]
mode = "hw_emu"
device = "xilinx_u50_gen3x16_xdma_201920_3"
temp_location = "/tmp"
ssh_host = ""
ssh_username = ""

[stages.wdb]
mode = "hw_emu"
ssh_host = ""
ssh_username = ""
xilinx_location = "/scratch/opt/Xilinx/Vitis/2020.2"
xrt_location = "/opt/xilinx/xrt"

[stages.fpga]

thanks for the quick reply adrian :)

Cool; thanks! Maybe give this a shot?
fud config stages.futil.exec /root/calyx/target/debug/futil

(I'm ever so slightly confused because I vaguely remember this working without fixing a path for this separately from the root directory, but I don't now see how that could have been possible, and it's possible I hallucinated that. Anyway, seems like something we could make a little easier somehow?)

Nope, you need to provide the full path to fud before it starts working outside of the calyx directory. “Fud check” will warn you about this problem. The fix is using the “fud c” command Adrian mentioned

The futil_directory stuff is used for different things and is not used to make calls to compiler work globally

Works! Thanks!