Visual Bugs in Payload CMS when Displaying Embedded Images from MongoDB

Link to reproduction
No response
Describe the Bug
I am encountering visual bugs in the Payload CMS when attempting to display images with long embeddings stored in MongoDB. Despite successfully uploading and storing the image data in MongoDB, the CMS exhibits visual discrepancies, especially with images containing lengthy embeddings.
Possible Solution:
One potential approach to address this issue is to implement a mechanism within the Payload CMS to truncate the embedding data if it exceeds a certain character length. By limiting the length of the displayed embedding, we can prevent visual bugs caused by excessively long embeddings.
Is this a good issue? I'm just a junior dev.

To Reproduce

Upload an image to Cloudinary using the provided code.
Extract the image embedding and store it in MongoDB using the provided code.
Access the Payload CMS and attempt to display the embedded image.

Code:
https://pastebin.com/n9Vd04Dt
Image:

Payload Version
1.0
Adapters and Plugins
No response

Storing images in MongoDB is not recommended by Mongo. I would say this is something that we are unlikely to address, especially since Payload has dedicated upload functionality that can be leveraged.

Storing images in MongoDB is not recommended by Mongo. I would say this is something that we are unlikely to address, especially since Payload has dedicated upload functionality that can be leveraged.

I am currently working on a project involving an image similarity search engine. In this project, each image undergoes processing through the SIFT algorithm to obtain its descriptor, represented as an array. Subsequently, the descriptor is converted into a base64 string. The reason behind this conversion is to streamline the storage process in MongoDB, as directly storing the descriptor without conversion results in significantly increased storage requirements. Essentially, this descriptor serves as a compact representation of the image. The actual images are stored in a Cloudinary Content Delivery Network (CDN), while MongoDB stores only the corresponding Cloudinary URL along with the converted string that represents the image. The image search algorithm operates by taking an image descriptor and seeking matches within the database's embeddings. To clarify, the images themselves are hosted on the CDN rather than in MongoDB; MongoDB solely manages the storage of the image embeddings, which are lengthy strings. Any visual anomalies experienced likely stem from attempts to display these lengthy strings.


odd indentation cases

Test case from metabase/analyze/fingerprint/fingerprinters.clj:
(deffingerprinter :type/Text
  ((map str) ; we cast to str to support `field-literal` type overwriting:
             ; `[:field-literal "A_NUMBER" :type/Text]` (which still
             ; returns numbers in the result set)
   (robust-fuse {:percent-json   (stats/share valid-serialized-json?)
                 :percent-url    (stats/share u/url?)
                 :percent-email  (stats/share u/email?)
                 :percent-state  (stats/share u/state?)
                 :average-length ((map count) stats/mean)})))

This is currently formatted to:

(deffingerprinter :type/Text
  ((map str) ; we cast to str to support `field-literal` type overwriting:
             ; `[:field-literal "A_NUMBER" :type/Text]` (which still
             ; returns numbers in the result set)
             (robust-fuse {:percent-json   (stats/share valid-serialized-json?)
                           :percent-url    (stats/share u/url?)
                           :percent-email  (stats/share u/email?)
                           :percent-state  (stats/share u/state?)
                           :average-length ((map count) stats/mean)})))

This seems wrong to me?

Another one from src/metabase/api/automagic_dashboards.clj:
(api/defendpoint GET "/model_index/:model-index-id/primary_key/:pk-id"
  "Return an automagic dashboard for an entity detail specified by `entity`
  with id `id` and a primary key of `indexed-value`."
  [model-index-id pk-id]
  {model-index-id :int
   pk-id          :int}
  (api/let-404 [model-index (t2/select-one ModelIndex model-index-id)
                model (t2/select-one Card (:model_id model-index))
                model-index-value (t2/select-one ModelIndexValue
                                                 :model_index_id model-index-id
                                                 :model_pk pk-id)]
               ;; `->entity` does a read check on the model but this is here as well to be extra sure.
    (api/read-check Card (:model_id model-index))
    (let [linked (linked-entities {:model             model
                                   :model-index       model-index
                                   :model-index-value model-index-value})]
      (create-linked-dashboard {:model             model
                                :linked-tables     linked
                                :model-index       model-index
                                :model-index-value model-index-value}))))

This is currently formatted to:
(api/defendpoint GET "/model_index/:model-index-id/primary_key/:pk-id"
  "Return an automagic dashboard for an entity detail specified by `entity`
  with id `id` and a primary key of `indexed-value`."
  [model-index-id pk-id]
  {model-index-id :int
   pk-id          :int}
  (api/let-404 [model-index (t2/select-one ModelIndex model-index-id)
                model (t2/select-one Card (:model_id model-index))
                model-index-value (t2/select-one ModelIndexValue
                                                 :model_index_id model-index-id
                                                 :model_pk pk-id)]
               ;; `->entity` does a read check on the model but this is here as well to be extra sure.
               (api/read-check Card (:model_id model-index))
               (let [linked (linked-entities {:model             model
                                              :model-index       model-index
                                              :model-index-value model-index-value})]
                 (create-linked-dashboard {:model             model
                                           :linked-tables     linked
                                           :model-index       model-index
                                           :model-index-value model-index-value}))))

In both cases, the ;; comment is causing the odd alignment.
In the first case, not sure how to automatically detect / fix this.
In the second case, arguably the comment should be de-dented.


Bump Fog version for multiple subnet functionality

Specifically we need 1.34.0 for fog/fog#3671 which is needed for VPN tunnels in vcloud-edge-gateway

:+1:

Note that we'll need to bump the version number of vcloud-core (so a new version of vcloud-core is released) then amend our dependencies in each of the vCloud Tools gems to use the new version.
We have to update the version of vcloud-core in all of the vCloud Tools projects at the same time, otherwise the vcloud-tools metagem fails to install.


Note about ws:// ports

I'd just like to note that as ws is based on http it can be used on port 80. Furthermore it's using upgrade request so it's actually possible to create hybrid http+ws server listening on single port, at least using node. Also it implies that ws is routable via nginx so realistically user can use path routing or subdomain routing in nginx for example to set up wstunnel "next to" actual http server without any significant trouble.
All of it creates quite interesting use case for wstunnel apart from punching through firewalls: one can use it for tunneling single service for multiple machines exposed under single public IP for example:
ssh.machine1.hostname.com
ssh.machine2.hostname.com

or if subdomains are not available option then even using path:
hostname.com/machine1/ssh
hostname.com/machine2/ssh

Surprisingly it seems to be the only option I found to actually perform ssh hostname/path based routing using single port and single public IP for multiple machines running the same service - as long as we don't want to create dedicated ssh gateway with accounts for absolutely all users or full blown VPN (which is obviously inconvenient as creating such gateway brings further accounts management overhead and security implications). Paired with stunnel TLS tunneling for high security encryption and certificate based authentication it's interesting options for VNC and other management protocols as well.

Good point: when the server is launched without '-t' option, it exposes a single http[s] endpoint that allows the client to tunnel anywhere (that the server can connect to).  But then you better make sure the http[s] endpoint is protected by SSL and password, otherwise, this leaves a giant security hole in your system.


Implement Rename feature support for language server

Description:
Add support for https://microsoft.github.io/language-server-protocol/specifications/specification-3-14/#textDocument_rename in language server

Closing in-favor of https://github.com/ballerina-platform/ballerina-lang/pull/28382


feat: Improve KYC error handling

Details

https://github.com/Expensify/App/issues/30088
Fixed Issues

$ https://github.com/Expensify/App/issues/30088
PROPOSAL: N/A
Tests

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@allroundexperts Not super sure if that's the issue. I've spun up the ngrok URL again.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

One more thing I noticed, @allroundexperts, if KYC is successful, we don't show the activation success page anymore. Is there a way to show the success page? I believe we're optimistically setting isPendingOnfidoResult to true so that's why?
https://github.com/Expensify/App/assets/12268372/7db84ecf-d3f1-47a0-a9f5-16c6d1b690e6

@allroundexperts That would be better, I think! 👍🏼

Nice, thanks, looks better! The only thing is nothing looks to be happening in the UI when the ActivateWallet API command is processing so it looks like the page is stuck for a few seconds:
https://github.com/Expensify/App/assets/12268372/1b75c691-df13-4010-b22c-7527e29c026e

Yes, I think it would! Do buttons have some sort of loading state, perhaps?

Nice, looks good!
https://github.com/Expensify/App/assets/12268372/983ef6f5-02c0-40d3-b7fd-d4d5c197082e

So I've tested the following scenarios:

When Onfido result is pending and the wallet is not yet activated
When Onfido succeeds and the wallet is activated

Can't think of any other scenario at the moment. In the other issue, we'll handle the case when we receive the successful or unsuccessful Onfido result asynchronously. In the case of success, the isPendingOnfidoResult will be removed from the userWallet. In case of failure, we'll have a different UI / error message.

I am inclined to merge this for now so we can get this deployed.
@Expensify/design if you have any suggestions on the UI here, we can fix them in a follow up PR 🙏🏼

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.3.88-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.88-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Add : Python Fortran Rosetta Stone (Transfer content from fortran90.org  #112)

This PR adds Fortran90 content Python Fortran Rosetta Stone, We are grateful to the original owners (@certik) of the content for opensourcing it . This content has been taken from https://github.com/certik/fortran90.org . This content has been formatted with pandoc and converted to myst markdown for consistency.
NOTE: All the python 2 codes have been refactored to python 3.
This PR Resolves:
Closes #112
Thanks and Regards,
Henil
CC @awvwgk @vmagnin

#build_preview

@henilp105
It's great you have shown we can have syntax coloring for both languages!
(Don't forget the upper case F of Fortran)

#build_preview

Here it is: https://fortran-lang.org/pr/185/en/learn/rosetta_stone/
Beautiful!

@henilp105 thanks for porting it! The page looks great. I left a questions above regarding porting of html -> markdown, but otherwise I think this is done.
Let me know how I can help.

@certik sir, It would be great if you could please verify the output of fortran and numpy codes as at some places maybe there were some differences in output.

Ah I see, yes. Btw, later we'll automatically generate the output, but for now we'll just do it by hand.
Ping me once you port the rest of the md file to markdown from html, and I will carefully review the output to make sure it is good.

@certik sure sir, thanks.

#build_preview

@vmagnin @zmoon @certik I have completed the porting of entire Rosetta stone to myst-markdown . Would like to request review the ported doc.
Thanks and Regards,
Henil

Awesome quick work @henilp105 ! I will read it fully on Monday.
At first sight, my first question concerns esthetic: in each example, should we add blank lines in the tables in order to have exactly the same height for the Python and Fortran tables? I have no definitive opinion, although my feeling is that it is prettier when the height is the same, like in the first examples.

@vmagnin I am not sure about this but, It would be difficult to make similar height for all the 51 pairs of tables (sphinx also trims some empty lines in the end of code blocks) , we would have to do that manually for all of them after counting respective lines.

#build_preview

#build_preview

There might be a way to adjust the sizes of the code blocks in the "ccs style" for the Sphinx to make them look aligned.

sir,  changing the css styles won't be able to change the alignment as the code blocks are not tables but, grids in myst markdown . maybe we  would have to append '\n' at the end of all the python code blocks. It would be great if @awvwgk sir could maybe suggest a way of resolving this.

I think the blocks look good now, they are aligned with their upper edge.
I noticed one last html block that would be great to convert to Markdown, otherwise I think this is ready to merge, the rest we can improve iteratively as we go.

@certik sir, It seems we are good to go.

#build_preview

It's looking very nice. I feel like the outputs would be better as non-highlighted code blocks though.

I have read the preview and have a few minor comments and finally a major one to discuss for the long term.

In the sentence "Compile using gFortran example.f90 and execute using ./a.out (you can of course add compilation options to gFortran, for example to produce the executable with a different name)" at the beginning, I would write gfortran for the command and GFortran for the name of the compiler (see https://gcc.gnu.org/wiki/GFortran).
I would also say that you can use "for example GFortran", which is one compiler among many ones.
I have found a typo in "break and exit statements": speficy instead of specify.

If the tutorial is for Fortran beginners, I think the section "Arrays" should rather be placed in the second half of the document. Maybe after "Math and Complex Numbers" or before "Examples"? When you start reading the page, you may think it is only for people using NumPy. But that is not true. And the Python tables are all legended with "NumPy Python", even when NumPy is not concerned. I think that document is very interesting for people who have learned Python at school (the BASIC of the 21th Century) and now want to learn Fortran. There is no reason to suppose they use NumPy.

When you start reading the page, you may think it is only for people using NumPy.

NumPy is a library for the Python programming language. Thus, inorder to use numpy we would have to use python.

NumPy is a library for the Python programming language. Thus, inorder to use numpy we would have to use python.

Yes, but what I mean is that using Python does not imply using NumPy. A student familiar with Python but not NumPy may not read the whole page. Starting with basic things like modules, reals, complex, loops, functions, etc. may be more attracting and concern a larger audience. Using NumPy should not be a prerequisite for this tutorial.
Of course, I started that discussion for the long term. We can merge the page as it is. And the community will see later if it follows my opinion or not to evolve that tutorial. @certik had his reasons to publish it like it is on Fortran90.org but maybe the orientation of that tutorial should be different on the learn page of Fortran-lang.org.

#build_preview

#build_preview

#build_preview

Probably another typo: three Fortran tables before "Some indexing examples", there is a slash / the end of the table.

@vmagnin thanks for the feedback. One could write a similar tutorial focusing on general Python, not specific to numerics. However this tutorial is meant as an introduction to Fortran to somebody who already knows Python for numerical computing. The NumPy syntax is the standard in the Python world to do numerics, and other libraries like PyTorch, TensorFlow, CudaPy all imitate it. So from my experience is it perfectly safe and natural to assume NumPy on the Python side. Consequently, starting with the arrays makes sense: let's get to the meat right away, show it is the same/similar in Fortran. Then we slowly show that the rest is also the same/similar.

@awvwgk @vmagnin @certik I have added the changes would like to request review .
Thanks and Regards,
Henil

#build_preview

@henilp105 After a rapid review (I have not read every detail), it looks good and ready for merging, in my opinion. Good job!

#build_preview

#build_preview

@awvwgk @certik sir, I would like to request review on the current implementation.
Thanks and Regards,
Henil

#buidd_preview

#build_preview

Is there still any reason to delay that PR?

Hi @vmagnin , I had been waiting for the community members to review the PR , I would be grateful if you could review it, Thanks.

Hi @henilp105,
I will review it in the next days.
Curiously, the link https://fortran-lang.github.io/webpage/pr/185 now gives me an error 404. Maybe it is too old (October).
Let's see if I can regenerate it myself:
#build_preview

#build_preview

I can now see the new preview.

@henilp105, I have read the whole page.
Curiously the problem of indentation pointed by @certik on the 20th October is always present, although you did a commit to fix it (on the Fortran side). On the Fortran side, it is not really a problem, but on the Python side it is a real problem as if we copy/paste the code it won't run, the Python indentation with 4 spaces being compulsory. Is it possible to fix it?

Thanks @henilp105
it is weird, there are still problems in indentation although you edited it. For example the first loop:
for i in range(len(a)):
  if a[i] > 5:

Something interesting: looking at all python snippets, I have noticed that it is always the first indentation that is wrong, the second one (inside the first structure) is good.
For example:
for i in range(1, 9):
 if i>2:
     break
 print(i)

It is wrong inside the for but good inside the if.

@vmagnin It seems to be some problem with sphinx I am not sure about it will try to patch this soon. Thanks.

#build_preview

@vmagnin , It seems that I have found a fix for the indentation issue in the python code , can you please review it again ?

Great @henilp105 ! That was so simple, it was hard to understand and find...
As commented before, there is just one Python snippet with a space to remove in the indentation (there is 5 spaces instead of 4) of a for.
And then it can be merged. Thanks for the work on this page. As soon as it is online, you can post it into the Discourse (in the Tutorials category).

Thanks, @vmagnin for prompt review.

Thanks everyone for reviews , I am merging this.
Thanks,
Henil


Regression in Terminal > Integrated: Mac Option Click Forces Selection

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.82.2
OS Version: macOS 13.5.2

Steps to Reproduce:

Enable the Terminal > Integrated: Mac Option Click Forces Selection setting
Launch an integrated terminal
Launch a tmux session with the option set -g mouse on
Note that performing a click/drag over some text triggers tmux's highlight functionality (not the native platform selection) and does not actually highlight the text for local copying
Hold the option key and click/drag over some text - note that it highlights the text using the platform native text selection system
Release the mouse... the highlight vanishes and the text is no longer selected (REGRESSION: Old versions of VS Code would not clear the selection here!)

The correct behavior is that the selection should remain after releasing the option key. This is what happened in previous versions, and also matches other terminal emulators like iterm2, where the highlighted selection remains after releasing the option key. The new behavior in VS Code prevents selections from being made in this mode.
This behavior was first noted in VS Code 1.82.1 and was also confirmed on the latest 1.82.2.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

... It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2...

Updated and confirmed that 1.82.2 still has the issue.

/duplicate #192518


Any examples of this plugin working with kotlin gradle?

In particular the build.gradle file.
Thanks

I do not use Gradle, but you can try this: https://github.com/OpenAPITools/openapi-generator/issues/6190#issuecomment-663621921


Can't stop the video Angular2+

I have a video on a page :
*html
<VideoPlayer #videoPlayer src="{{ videoSrc }}" controls="true" loop="false" finished="{{ completed }}" autoplay="true" height="200"></VideoPlayer>
*component
registerElement("VideoPlayer", () => require("nativescript-videoplayer").Video);```

When I am navigating between my views and come back to the page with the videoplayer the video plays again and again and again... I want to be able to stop the video (destroy the video).

`"nativescript-videoplayer": "^2.4.0",`

But I can't get a reference to the videoPlayer. I tried it with @ViewChild but no luck.

Any thoughts plz?

This comment might help https://github.com/bradmartin/nativescript-videoplayer/issues/56#issuecomment-279301163-

@bradmartin  jup thanks got me in the right direction.


Added Breakout, Tic-tac-toe, Pokemon generator and Candy crush projects

Issue: #187 #188 #189  #191
Added 4 projects which will help in enhancing skills of beginners in web development.
Project Name : Breakout Game, Tic-Tac-Toe, Pokemon Generator and Candy Crush.
Tech Stack: HTML, CSS, JS

Impressive work !!

Impressive work !!

Thank you so much 😁


Same cluster onClusterPress Unable trigger twice

"react-native-map-clustering": "^3.0.2",
"react-native-maps": "0.25.0",

After press on cluster the first time, it trigger the event.
But after i press the same cluster for second time and above, it DID NOT trigger the event anymore.

Hi @kkusanagi
Hmm that is strange because after clicking cluster it should zoom into it, making it disappear ;/
Can you send me code you are using?

The cluster on both of the location is exact same, just different floor.
So even zoom in, it still combine into cluster.
And oh, sometimes the cluster is missing when press.
The cluster location is around 3~5km far from my location.

Hmm works fine for me ;/ Event triggers every time on cluster, but is not getting declustered because location is the same for two markers.
Can you try below code?
 <MapView
        onClusterPress={(cluster, markers) => console.warn(cluster, markers)}
        initialRegion={{
          latitude: 52.5,
          longitude: 19.2,
          latitudeDelta: 6.5,
          longitudeDelta: 6.5
        }}
        style={{ flex: 1 }}
      >
        <Marker
          coordinate={{
            latitude: 52,
            longitude: 18
          }}
        />
        <Marker
          coordinate={{
            latitude: 52,
            longitude: 18
          }}
        />
</MapView>

Found the bug.
if you notice, i use latitudeDelta and longitudeDelta to 0.01.
Now, zoom out and find the cluster.
Once you press on cluster, it will disappeared or cannot press twice when render out the modal.
here use the code below.
<MapView
preserveClusterPressBehavior
onClusterPress={(cluster, markers) => {
this.setState({isGuideModalVisible:true});
console.warn(cluster, markers);
}}
initialRegion={{
latitude: 52.5,
longitude: 19.2,
latitudeDelta: 0.01,
longitudeDelta: 0.01
}}
style={{ flex: 1 }}
>
<Marker
coordinate={{
latitude: 52,
longitude: 18
}}
/>
<Marker
coordinate={{
latitude: 52,
longitude: 18
}}
/>

<Modal
animationType="fade"
transparent={true}
visible={this.state.isGuideModalVisible}
onRequestClose = {()=> {this.setState({isGuideModalVisible:false})}}
>
<TouchableWithoutFeedback onPress={()=>{this.setState({isGuideModalVisible:false})}}>
<View style={{flex:1,backgroundColor:'rgba(0,0,0,0.5)', alignItems:'center',justifyContent:'center'}}>
<View style={{borderRadius:10,padding:5,alignItems:'center',justifyContent:'center'}}>
          </View>
        </View>
      </TouchableWithoutFeedback>
    </Modal>

Maybe mine is too much Marker and it blows up.

Hmm ok I found a bug :) I will have time to fix it in 4 hours so it should be released in 5.
I will let you know once its done 💪

Thanks. I never thought this bug is so hard to find.

@kkusanagi  I had some free time 🎉
Please update module version to 3.0.4 and let me know if that will fix your problem ;)

Had tested. It is fixed. And strange, it become faster than before. Well, it is a good news too.

Oops, the disappearance is fixed. But the press twice issue is still occur. I need to press and move the map and then press the cluster again to trigger the event.
So still not fixed. But better than disappearance.

Hi, yep I can see this bug. It happens sometimes. Looks like <Marker/> onPress() method is not called sometimes. It is possible that 2 markers overlap each other.
But don't worry, I have easy fix for it. Will release soon.

@kkusanagi   Version 3.0.5 is up.
Let me know if this bug is resolved 👍

You just make it worst. Now press the cluster do not focus to it anymore.

Hmm you tested it on code example above?

Yup. Seems like the preserveClusterPressBehavior is turn on. The press event do not trigger fittocoordinate()

Hmm ok I see, problem occurs on Android and I only tested it on iOS. I will try ti fix it ASAP.

I had tested on IOS and it also occur same issue.

I reverted changes in version 3.0.6. For me it looks like problem with react-native-maps module.
I only pass onPress() prop to marker. I don't have control on when it will call :(

hmmm, i try google it and found this. Not sure is this the same issue.
Marker click event on react native maps not working in react ios

Hmm looks promising will test it.

Hmm never mind  Callout is used for something like this:

Well, I can't find any solution in google and react-native-map coding.
Seems like no problem and minor problem.
Haih...Well, this really need some time and much professional tester to get the bugs.
If really react-native-maps issue, we need to create new issue at their github thread.


Expose service and port under the services section in cloudbreak after installing them in ambari

Hi all,
is it possible to expose the new installed services and the configures port to access the service in the service section of cloudbreak. It would be very convenient it it would be possible.
Thanks
Jakov

Hi,
Currently you can not modify your opened ports after the cluster installed. You have to do it by hand on the provider side.
Thanks for reporting this, I will create an improvement ticket for this issue.


Slow Process vs code

Type: Performance Issue
to open the vs code it took long time than my laptop does, my laptop i3 with gen 9 and my computer i5 gen 12 and the ram of course my computer is bigger 2 times and the speed too, but I don't recognized where's the failure system on my computer so took a long time to open the code, i've check all my computer system was does good ssd, cpu, and ram. but if I open vs code with "code ." in terminal it took 6 second to open, but if my laptop just need 2 second and does to the extension, if I build package or eslint to read my code the error took 5 - 6 second to show the error, unlike my laptop
VS Code version: Code 1.81.0 (6445d93c81ebe42c4cbd7a60712e0b17d9463e97, 2023-08-02T12:37:13.485Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i5-12400F (12 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.84GB (4.21GB free)

Process Argv
--crash-reporter-id 9a31d7c5-44c1-4c99-a097-5abab4bea2c0

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	   100	 17372	code main
    0	    90	  3928	   gpu-process
    0	   143	  7336	window [1] (Welcome - bncc.net-be - Visual Studio Code)
    0	    86	  9512	shared-process
    0	    87	 12480	window [3] (Issue Reporter)
    0	    50	 12940	   utility-network-service
    0	   109	 16312	extensionHost [1]
    0	    78	 18436	fileWatcher [1]
    0	    27	 23612	   crashpad-handler

Workspace Info
|  Window (Welcome - bncc.net-be - Visual Studio Code)
|    Folder (bncc.net-be): 10293 files
|      File types: php(7678) md(274) json(172) stub(89) vue(54) rst(37) js(35)
|                  jsx(28) tsx(28) dist(21)
|      Conf files: dockerfile(7) jsconfig.json(2) makefile(2) tsconfig.json(2)
|                  package.json(1);

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
282f8724:30602487
f6dab269:30613381
2i9eh265:30646982
showlangstatbar:30737416
vsctsb:30748421
03d35959:30757346
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
e537b577:30795824
dsvsc013:30795093
dsvsc014:30804076

Can you attach the startup timer output https://github.com/microsoft/vscode/wiki/Performance-Issues#read-the-startup-timers and logs from https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-starts-up-slowly

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Amazon Linux 2

Add support for Amazon Linux 2.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1644 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1644   +/-   ##
========================================
  Coverage    51.78%   51.78%
========================================
  Files           24       24
  Lines         3924     3924
========================================
  Hits          2032     2032
  Misses        1892     1892

Continue to review full report at Codecov.

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


fix: issue where c type is any

While running nuxt app, I was getting the error c.toUpperCase is not a function, after digging in the vite builds, found out that these functions classify & camelize are the root cause.

[x] This PR fixes the issue (we have c which is of type any & toUpperString() only works on String prototype.

Issue Repro –

Clone – https://github.com/geoql/expenses
npm ci
npm run dev

For context, Nuxi info
------------------------------
- Operating System: Darwin
- Node Version:     v20.4.0
- Nuxt Version:     3.6.5
- Nitro Version:    2.5.2
- Package Manager<EMAIL_ADDRESS>- Builder:          vite
- User Config:      app, components, css, devtools, experimental, vue, ssr, modules, nitro, plugins, routeRules, runtimeConfig, typescript
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

I'm not sure I understand the use case here. Is there a legitimate reason for these functions to accept values that aren't strings? Isn't calling toString() just hiding the problem rather than fixing it? Perhaps it would be better to add a warning somewhere further up the callstack to report the original mistake that led to these values not being strings in the first place?

seems like the same unocss bug like here:
https://github.com/unocss/unocss/issues/3206

I ran into the same problem, more details here:
https://github.com/nuxt/nuxt/issues/23937#issuecomment-1816773445
In my case, it was caused by the kebab case component property convention, which seems to not work anymore.
This does not work anymore / produces the hydration failures
      <PostItem :class="{'shadow-lg hover:-translate-y-1': useGridView}"
                v-for="post in posts"
                :key="post.id"
                :post="post"
                :show-border="!useGridView" />

while this works
      <PostItem :class="{'shadow-lg hover:-translate-y-1': useGridView}"
                v-for="post in posts"
                :key="post.id"
                :post="post"
                :showBorder="!useGridView" />

Not sure what causes this and I assume not everybody is facing this issue, as this would probably go viral.

Based on the UnoCSS bug report linked above, I think this PR should be closed.
UnoCSS is rewriting some of the code in Vue. The original code contains this line:
const camelizeRE = /-(\w)/g

By the time it gets to the browser, it has been changed to this:
var camelizeRE = /-\w/g;

The parentheses have been removed, leading to the replace callback being passed the wrong arguments.
I've checked this myself and confirmed that this is what's happening in the original reproduction. I haven't dug in to confirm that UnoCSS is the root cause, but something is rewriting that RegExp, so there's nothing that needs to be done in Vue to fix it.


Add missing shebang to save-my-commit/setup.sh

setup.sh in save-my-commit/ misses the shebang line. In ZSH this causes a problem.
Added shebang line using /usr/bin/venv.

added pull-request to original repo


Errors with NLB OpenSSL SSL_connect: SSL_ERROR_SYSCALL. With ELB is working

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Hi, we are currently using both internal and public ELBs to publish our EKS services. Now, due to a need to publish a websocket, we need to have a NLB, but when deploying this one (in theory it is deployed correctly and has access to the EKS nodes and traffic arrives to it) we can't get it to work.
The error we get is:
curl https://XXXXXXXXXX -vvv                                                                                35 err
*   Trying XX.XX.XX.XX:443...
* Connected to XXXXXXXXXX (XX.XX.XX.XX) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to XXXXXXXXXX:443
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to XXXXXXXXXX:443

This works perfectly with the ELB. I have deployed a parallel NLB and changed only the gateway to go through the new load balancer. But this is not working.
The certificates are created in the same NS with cert-manager (are the same that are used in the ELBs)
Ingressgateway config:
istio-internal-nlb-ingressgateway:
  name: "istio-internal-nlb-ingressgateway"
  revision: ""
  replicaCount: 1
  kind: Deployment
  rbac:
    enabled: true
  serviceAccount:
    create: true
    annotations: {}
    name: ""
  podAnnotations:
    prometheus.io/port: "15020"
    prometheus.io/scrape: "true"
    prometheus.io/path: "/stats/prometheus"
    inject.istio.io/templates: "gateway"
    sidecar.istio.io/inject: "true"
  securityContext: ~
  containerSecurityContext: ~
  service:
    type: LoadBalancer
    ports:
    - name: status-port
      port: 15021
      protocol: TCP
      targetPort: 15021
    - name: http2
      port: 80
      protocol: TCP
      targetPort: 80
    - name: https
      port: 443
      protocol: TCP
      targetPort: 443
    - name: tls
      port: 15443
      protocol: TCP
      targetPort: 15443
    annotations:
      external-dns.alpha.kubernetes.io/hostname: internal-nlb.dev.XXXX
      service.beta.kubernetes.io/aws-load-balancer-name: "Istio Private NLB"
      service.beta.kubernetes.io/aws-load-balancer-internal: "true"
      service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: '*'
      service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
      service.beta.kubernetes.io/aws-load-balancer-scheme: "internal"
      service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: "ManagedBy=Istio"
    loadBalancerIP: ""
    loadBalancerSourceRanges: []
    externalIPs: []
  resources:
    requests:
      cpu: 100m
      memory: 128Mi
    limits:
      cpu: 2000m
      memory: 1024Mi
  autoscaling:
    enabled: true
    minReplicas: 2
    maxReplicas: 5
    targetCPUUtilizationPercentage: 80
  env:
    ISTIO_META_ROUTER_MODE: standard
  labels:
    app: istio-internal-nlb-ingressgateway
    istio: internal-nlb-ingressgateway
  annotations:
    fluentbit.io/exclude: "true"
  tolerations: []
  affinity:
    podAntiAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        - labelSelector:
            matchExpressions:
            - key: service.istio.io/canonical-name
              operator: In
              values:
                - istio-internal-nlb-ingressgateway
          topologyKey: "kubernetes.io/hostname"
  networkGateway: ""
  imagePullSecrets: []

Gatway:
 - name: private
      selector: internal-nlb-ingressgateway
      servers:
        - port:
            number: 80
            name: http-private-nlb
            protocol: HTTP2
          hosts:
            - "*.XXXXXXXX"
          # tls:
          #   httpsRedirect: true
        - port:
            number: 443
            name: https-private-nlb
            protocol: HTTPS
          tls:
            mode: SIMPLE
            credentialName: wildcard.XXXXXXXXXXX
            minProtocolVersion: TLSV1_2
            maxProtocolVersion: TLSV1_3
          hosts:
            - "*.XXXXXXX"

Envoy filters:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: proxy-protocol-internal-nlb
  namespace: istio-ingress
spec:
  workloadSelector:
    labels:
      istio: internal-nlb-ingressgateway
  configPatches:
  - applyTo: LISTENER
    patch:
      operation: MERGE
      value:
        listener_filters:
        - name: envoy.listener.proxy_protocol
        - name: envoy.listener.tls_inspector

Version
istioctl version
client version: 1.18.0
control plane version: 1.18.0
data plane version: 1.17.0 (32 proxies), 1.18.0 (3 proxies)

Client Version: v1.25.6-eks-48e63af
Kustomize Version: v4.5.7
Server Version: v1.25.10-eks-c12679a

We are using Gateway Helm Chart 1.18.0

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

any update on this issue? seeing the same issue on EKS with NLB.

Hi!
Make sure that you have enabled:
Cross-zone load balancing and  in the target Proxy protocol v2
with this it started working for me

@ichasco-heytrade, trying your suggestion but doesn't seem to help in my environment. I am running into similar issue and previously reported it here  with no response unfortunately. Pretty similar setup with private, internal NLB.
I am just curious if your curl tests are initiated from the same node as where ingress pod is running? For me this is the only way to replicate this condition.


007 – Golden Eye  & 007-The World Is Not Enough & mission :impossible  port

Plase add  port game 007 – Golden Eye  & 007-The World Is Not Enough  & mission :impossible

I can't just port any game I want. It's a complex process and it is currently not possible for those games. Even if it was, this is not the place to ask, because this is only for Perfect Dark related issues.


Adding spaces at specific places removes first characters.

Having spaces and newlines or spaces at the end of the paragraph makes it so first characters are not rendered correctly. Given code like this:
---
import { Markdown } from "astro-remote";

// Working as expected
const c0 = `Most .`;

// 1 space
const c1 = `Most
.`;

// 2 spaces
const c2 = `Most
.`;

// Space at the end
const c3 = `Most . `;

const content = [c0, c1, c2, c3];
---

	{content.map((c) => <Markdown san>{c}</Markdown>)}

Result is

Reproduction
This is not issue with marked since it handles those use cases correctly

Having spaces and newlines or spaces at the end of the paragraph makes it so first characters are not rendered correctly. Given code like this:
---
import { Markdown } from "astro-remote";

// Working as expected
const c0 = `Most .`;

// 1 space
const c1 = `Most
.`;

// 2 spaces
const c2 = `Most
.`;

// Space at the end
const c3 = `Most . `;

const content = [c0, c1, c2, c3];
---

	{content.map((c) => <Markdown san>{c}</Markdown>)}

Result is
Reproduction
This is not issue with marked since it handles those use cases correctly

So the new PR about to be opened from the branch testing-issue-#7 will include resolutions to some of the issues your facing.
BUT this issue is not entirely related to astro-remote... aside from the small fix included above,
To preserve the formatting of your strings when they're rendered as Markdown through astro-remote

, you might need to escape the trailing spaces and newlines. Here's how you could do that using the example from your Reproduction:
---
import { Markdown } from "astro-remote";

// Working as expected
const c0 = `Most .`;

// 1 space
const c1 = `Most \\
.`;

// 2 spaces
const c2 = `Most  \\
.`;

// Space at the end
const c3 = `Most . `;

const content = [c0, c1, c2, c3];
---

    {content.map((c) => <Markdown>{c}</Markdown>)}

The Above resolved the issues after I updated a internal function

Upgrading from 0.2.4 to 0.3.2 we got major performance issue in production, the only change was updating this dependency. It slowed the whole astro node instance, I don't see it in dev/preview mode/


Rebuilding shaders broken on Windows

I'm opening this issue just to notify that rebuilding example shaders on Windows is far from working out of the box. I can get it to work but usually after a bit of time fixing problems (environment is MSYS2). I do a make in the examples folder, maybe this is not the right command ?
Anyway:

echo to a file does not work (for example -@echo extern const uint8_t* $(basename $(<))_pssl;>> $(@)), so the last 2 lines about pssl are never added. For my fork I edit all the files at hand for now...

tons of weird directories are created (example: 13-stencil/.....examplesruntimeshadersdx11, 05-instancing/.....buildshadersspirv, etc...).

the build and final directories are not automatically created (i.e., the dirs target does nothing). Or, more realistically, it does not work as intended and creates the weird folders of the previous bullet point.

the compilation fails for some complex shaders:
 [cs_update.sc]
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Fatal: Work buffer overflow
  from file cs_update.sc, line 83.
 cpp: "../../scripts//../src/bgfx_compute.sh", line 58: Error: Inside #ifdef block at end of input, depth = 3
  from file cs_update.sc, line 83.
 Shader entry point 'void main()' is not found.

A quick fix is to increase the buffer sizes in fcpp (I put 4096 for NBUFF and NWORK)

not all shaders in runtime/shaders/ were touched by the rebuild. Are some shaders obsolete but still present in the repo ? These shaders are:

runtime/shaders/glsl/fs_shadowmaps_color_lighting.bin
runtime/shaders/glsl/fs_shadowmaps_color_lighting_omni.bin
runtime/shaders/glsl/fs_shadowmaps_color_lighting_pfc.bin
runtime/shaders/glsl/fs_shadowmaps_depth.bin

That's all I saw, after that I was able to rebuild shaders completely.

This is happening in your fork or master?

Both my fork and master

I did rebuild last night to check this, deleted all built shaders and no issues: https://github.com/bkaradzic/bgfx/commit/610055fbb04f83b4d1284d46ba8c6abaacf88ba6
Which compiler you're using for building shaderc?

Visual Studio 2015 on Win10. But most of the problems are from the makefile. You rebuilt the shaders on linux ?

I rebuild them on windows because D3DCompiler works only there... Issue you pointed out above is not due to makefile.

Issues 1 and 2 clearly are from the makefile. Issue 3, I don't know why it seems to work properly on your system and not on mine. Note that I just do make rebuild inside the examples directory.

1, 2 are because you have multiple shells in your path. Most common issue is sh that comes from Git. Just remove git/bin from your path and it will find GnuWin32 one.

I do not have the git shell in MSYS.
I found the issue for 1. In the following line -@echo extern const uint8_t* $(basename $(<))_pssl;>> $(@) (in shader-embedded.mk), the ; is interpreted as a command separator, hence the redirection does not apply... Adding a backslash to escape the semicolon solves it.
I also found the issue for 2. In tools.mk, there is CMD_MKDIR=cmd /C "if not exist "$(subst /,\,$(1))" mkdir "$(subst /,\,$(1))"" for Windows. It turns out replacing slash by antislashes ends up escaping characters... Changing $(subst /,\,$(1)) by $(subst /,\\,$(1)) solves the problem.
Btw, compiling shaders for Vulkan outputs a lot of debug info of the form:
[fs_particle.sc]
2401: BgfxSampler2D -1
{
                 m_sampler -1
                 m_texture -1
}
499: $Global -1
{
                 u_viewRect 0
                 u_viewTexel 16
                 u_view 32
                 u_invView 96
                 u_proj 160
                 u_invProj 224
                 u_viewProj 288
                 u_invViewProj 352
                 u_model 416
                 u_modelView 2464
                 u_modelViewProj 2528
                 u_alphaRef4 2592
}

I dont know if this is related, but I cannot run many of the example exe's after building in 2015 either in x64 or win32. Only these examples work: 00, 02, 17, 20, 25 and 29
However, if I run them within the Visual Studio IDE, they all work correctly?

 Read the effin docs. Soz.

Normally you don't have to recompile the shaders. This bug report is for when you have to (for example modification of the binary format).
@bkaradzic in which environment you were running the makefiles ? And which compiler ?

I just hit this same snag with NWORK not being large enough to parse bgfx_compute.sh due to its massive macros. For my work environment (macOS, Xcode) the version of shaderc I built ended up with an NWORK size of 512 due to the way it is defined in cppdef.h. The first define is for 2048, but that doesn't seem to get defined for this build and the default is then 512 (as defined lower in the same file). I altered that value and was able to get things compiling again.


fix: make directory based on output prefix before optimizing files #6

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (dc60a4b) to head (3e40a25).
Report is 6 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##                main        #8   +/-   ##
===========================================
  Coverage     100.00%   100.00%
- Complexity       144       146    +2
===========================================
  Files             17        17
  Lines            441       446    +5
===========================================
+ Hits             441       446    +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add help message for "-h" and "--help"

anew will only return usage instructions when used with no arguments. This adds support for "-h" and "--help".  I am going to close it.


Selectors with bool_exp in one simple syntax

@ivansglazunov how bool_exp syntax should be simplified? Why it is a bug? Are you sure that issue still should be fixed? Does it change public GraphQL API of deeplinks? If so, we might try to finish it before stable 1.0.0 release.


[WIP] Pass transpilation options

[WIP] Pass transpilation options
Fixes #107
Summary
I tested the changes locally. The code is half baked. Need to add test cases. This commit is for initial review.
Here we are covering 4 possible scenarios. PFB the notebook snippets.
import numpy as np
import pennylane as qml
from pennylane_qiskit import *

Case 1: transpile argument passed in QiskitDevice init
dev = AerDevice(wires=2, test_param='dummy_param', optimization_level=3, validate=False)

def init_state(n):
    state = np.random.random([2 ** n]) + np.random.random([2 ** n]) * 1j
    state /= np.linalg.norm(state)
    return state

state = init_state(2)
state

array([0.21517941+0.23902292j, 0.04778645+0.44990237j,
       0.60157048+0.01456144j, 0.57077425+0.06314949j])

Case 2: transpile argument passed using apply
For this run only
dev.apply([qml.QubitStateVector(state,wires=[0,1])], routing_method='stochastic', seed_transpiler=22)

cheking transpile args:  {'optimization_level': 3}
cheking temp transpile args:  {'routing_method': 'stochastic', 'seed_transpiler': 22}
cheking merged transpile args:  {'optimization_level': 3, 'routing_method': 'stochastic', 'seed_transpiler': 22}

Case 3: overriding transpile argument
For this run only
dev.apply([qml.QubitStateVector(state,wires=[0,1])], optimization_level=2

cheking transpile args:  {'optimization_level': 3}
cheking temp transpile args:  {'optimization_level': 2}
cheking merged transpile args:  {'optimization_level': 2}

Case 4: overriding and persist transpile arguments
dev.apply([qml.QubitStateVector(state,wires=[0,1])], optimization_level=2, persist_transpile_options=True)

cheking transpile args:  {'optimization_level': 2}
cheking temp transpile args:  {}
cheking merged transpile args:  {'optimization_level': 2}

Hi @sagarpahwa, the scenarios you are testing in the PR comment look very thorough! They will make good unit tests. When you are ready for someone to take a look/review, let us know in the comments

Hi @sagarpahwa, the scenarios you are testing in the PR comment look very thorough! They will make good unit tests. When you are ready for someone to take a look/review, let us know in the comments

Hi @josh146 , I submitted PR for review.
For testcases, I checked only for BasicAer and Aer devices only. For IBMQ device,  the time taken was increasing significantly and other testcases also seemed lightweight to me.

@josh146 , should I re-trigger the build using an empty commit to make the tests pass?

Hi @sagarpahwa! Some checks (e.g. the black formatter) need some adjustment at the moment. Feel free to ignore them, we'll update them dynamically.

Hi @sagarpahwa, we've merged in an update for the black formatting check and now it should be working fine! That means that the checks should now be good to go.
A couple of small tweaks could help out with passing the currently failing CI checks:
Documentation check / sphinx
One thing to note is that docstrings left in the code need to adhere to the formatting conventions of rst markup (linking the relevant part of the development guide on documentation). This involves fixing up warnings that are raised by sphinx, such as:
/pennylane-qiskit/pennylane_qiskit/qiskit_device.py:docstring of pennylane_qiskit.IBMQDevice.apply:4: WARNING: Unexpected indentation.

You can check the warnings locally by running make docs from the root folder of PennyLane-Qiskit.
Here is a guide on the installation of related packages.
Formatting check / black
It seems that a file needs reformatting as per the CI log (/home/runner/work/pennylane-qiskit/pennylane-qiskit/pennylane_qiskit/qiskit_device.py).
This reformatting could be done by executing the following:
black -l 100 pennylane_qiskit/qiskit_device.py

Note: you'll need to have black installed using pip locally
codecov/project
No worries on this one, if its status remains Expected.

Thanks @antalszava , the formatting issues are resolved.

Hi @antalszava , thanks for the thorough review. I made the amendments.

Hi @sagarpahwa, almost there! :100: Left a couple of small suggestions on the docs. You might have to pull before a new addition.
There is now an updated CHANGELOG.md file, you could add an entry to the Improvements section. The convention there is to have a one-sentence description followed by a hyperlink to the PR on the next line (see examples in the changelog). And don't forget to list yourself as a contributor! :blush:

Hi @antalszava,
Sorry for the delay, my exams are going on. Thanks for such detailed pointers at each step. Those were really helpful in understanding the de facto standards of pennylane and open source frameworks in general.


upgrade supports-color; closes #1304

At least, I think it does.  @plroebuck seems to know more about this.

ref: https://github.com/chalk/supports-color/pull/90


chore: migrate notifications category to amplify-prompter

Description of changes

migrates notifications category to use amplify-prompter library instead of inquirer

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #11401 (96216cf) into dev (6e02691) will decrease coverage by 0.00%.
The diff coverage is 76.66%.

@@            Coverage Diff             @@
##              dev   #11401      +/-   ##
==========================================
- Coverage   49.45%   49.44%   -0.01%
==========================================
  Files         692      692
  Lines       33424    33419       -5
  Branches     6840     6838       -2
==========================================
- Hits        16529    16525       -4
+ Misses      15370    15369       -1
  Partials     1525     1525

Impacted Files
Coverage Δ

...fy-category-notifications/src/validate-filepath.ts
40.00% <25.00%> (+6.66%)
:arrow_up:

.../amplify-category-notifications/src/channel-fcm.ts
66.21% <55.55%> (-5.04%)
:arrow_down:

...ify-category-notifications/src/apns-cert-config.ts
90.00% <100.00%> (+1.11%)
:arrow_up:

...lify-category-notifications/src/apns-key-config.ts
93.33% <100.00%> (+1.66%)
:arrow_up:

...amplify-category-notifications/src/channel-apns.ts
65.34% <100.00%> (+0.29%)
:arrow_up:

...li/src/domain/amplify-usageData/getUsageDataUrl.ts
100.00% <0.00%> (+12.50%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add Support for TCX Programs

This PR adds support for TCX programs using priority-based API for
TCX modeled after the existing TC API.
Both the Linux kernel and Aya use a relative positioning approach for
ordering TCX programs that requires new TCX programs to be positioned
relative to an existing TCX program. To improve the user experience
across multiple independent applications, we’ve retained a TC-like
priority API in bpfman, which internally maps to Aya’s relative
ordering API.
Additional Changes:

A TCX integration test is included.
A go-tcx-counter example was added, and the go-app-counter example has been
updated to include a TCX program.
GitHub Actions are now configured to use ubuntu-24.04 to meet the kernel
version requirement (6.6 or higher) for TCX.

This TCX pr is ready for review.

Both bpfman and other applications can install tcx programs.  We don't currently pay attention to TCX programs installed by other means.  The first bpfman TCX program on a given attach point is placed in first position regardless of whether there are already other programs attached.  Subsequent bpfman TCX programs on the same attach point are positioned relative to existing bpfman programs based on priority without regard to any other TCX programs that may have been attached by other means.  We've talked about some options for cooperating better with non-bpfman loaders, but this is the first step.


Add safekeeper option to patch control file.

https://github.com/neondatabase/neon/issues/6397

You mean feed patch to stdin and get result on stdout? Possible. Or feeding the whole state to stdin? Also possible, but not handy, we sometimes have very big term histories, copypasting them is not handy and I'm not sure which way has higher probability of human error...


Support AndroidX

Feature Request
Seems that most updated plugins support AndroidX.
As far as I understand this is a breaking change in terms of the plugin (meaning you either support the old way or the new way) so I would avoid this change in a minor release.
I'm still not sure what needs to be done in order to support this and what's the status of the other community plugins. If most modern plugins already support this then it should be a high priority for next major release, but if not then it can wait.
I currently don't use AndroidX in my project since I think not all the plugins support this, but I need to check...

Cordova have released Android 10.0.0, which requires AndroidX support.
https://cordova.apache.org/announcements/2021/07/20/cordova-android-10.0.0.html
They cite the cordova-plugin-androidx-adapter as a way of migrating for projects still using the old support libs.

[ ] Investigate what is needed to migrate to AndroidX support

@RaddishIoW Let me know if you want me to help, I'm working extensively on MapLibre-gl these days but if you need me to look at something or help out let me know.
I know that the following plugin had made the change from android to androidX:
https://github.com/darryncampbell/darryncampbell-cordova-plugin-intent#readme
These are the relevant commits, I think:
https://github.com/darryncampbell/darryncampbell-cordova-plugin-intent/commit/ef584403a952b25ea71f0eda984921928322a9cd
https://github.com/darryncampbell/darryncampbell-cordova-plugin-intent/commit/567c0f8ce6ba830d6cc2bd98dfb9030c233524d2
https://github.com/darryncampbell/darryncampbell-cordova-plugin-intent/commit/61ed2cad5a6be7b71ea48d89a11ed691a32c2e6e
The first one might not be needed in case cordova-android is defaulting to androidX, maybe, not sure...
Good luck!

@RaddishIoW did you get around to doing this?
I'm trying to migrate now to cordova-android@10 and this is the main plugin that fails compilation.
Everything I tried that did not require to change the code here does not seem to work.
Let me know what's the status of this.
As a side not, it might be better to move the files a bit in order to have all the files under the same namespace. currently when the build fails it's unclear that the files belong to this plugin as they are scattered around in all kind of namescpaces.
Not entirely related to this issue though...

Opening the android folder in android studio and clicking refactor migrate to androidX seems to do most of the heavy lifting.
I've created a branch called androidX to allow testing this and fixing what needs to be fixed.
I'll report back here after I successfully manage to migrate my project to androidX.

Hi @HarelM, sorry for the late reply - I've been snowed-under in other things for a few weeks, and just haven't had the bandwidth to even look at GitHub.
Glad you managed to get this sorted! I'll update when I get a chance and check it with my app.
This wasn't a major issue for me, as I was using a cordova plugin to convert to AndroidX on-the-fly...
So I think we can close this issue now, yeah?

This plugin didn't work for me, I'm not sure why, but it was a good incentive :-)
Yes, closing...


Create kickoff-post.md

@celestehorgan did I break the blog on the first post? Also what needs to be commented out so we can see it?

@celestehorgan just wanted to follow up can you help get this merged and live on the website? What needs to be changed to make it visible?


Add initial CI

Closes #4.

This PR is in principle ready for a first review. It provides tests for template features (either by running a full build & test, or with smoke tests), and a pre-commit config for linting (when a linter required fixes to existing sources I tried to put that in its own commit). The CI runs in GH which is probably okay since it should finish quickly.
Interesting bits:

CI does not work with zeek-5.0.0 since its packaged zkg does not support the create command which we need for testing the template; provide CI only for latest version for now
since we likely run multiple zkg create operations concurrently, we need to provide a workaround for zeek/package-manager#139.
pylint configuration was moved into a .pylintrc file

I rebased this onto the latest master and rewrote the recently merged Spicy feature tests into btests. Would be great if you could have a look @ckreibich @rsmmr.

While figuring out how to make this work against a nightly Zeek I noticed that the new zkg wrapper introduced additional issue (filed zeek/package-manager#144 and added a workaround; fixed GH execution for zeek/package-manager#145).

The only hiccup is that when I run this locally (with Zeek 5.2.0-dev.51), the features.spicy-packet-analyzer test errors with: ...

I added some Zeek preprocessor branch to the Spicy packet analyzer template which branches on versions before or after 5.2.0, but your dev snapshot seems to be from before that branch. Somewhere on the 5.2 dev branch I bumped a spicy-plugin change from Robin removes double underscores from packet analyzer names, but your snapshot seems to miss that.

Yeah Benjamin it all works now over here too. Thanks!


2nd canonical URL on https://cahier1939ms.github.io/texts/translation/ causes Hypothesis to commit incorrect document equivalence

Bug report form
Steps to reproduce

Go to https://cahier1939ms.github.io/texts/translation/
Create annotation
note target URI (https://cahier1939ms.github.io/texts/translation/)
Open URL in Via
create annotation
note target URI (https://viahtml.hypothes.is/texts/translation/)

Seems to be due to:

Expected behaviour
If possible we should see the canonical URL as https://cahier1939ms.github.io/texts/translation/.
Additional details

https://hypothes-is.slack.com/archives/C2BLQDKHA/p1670592776889249

See also:

https://github.com/hypothesis/viahtml/issues/438

The first one is added by us in viahtml, the second is from the page and just happens to match the style of comments we have.
Of particular interest is fact this is a relative URL, we might have to handle that differently.

Support - can you update the customer that we won't be fixing this. However, if this comes up more we should revisit it.
Advice would be to make the link an absolute url.

Closing per discussion above


Drop rewriters

This will happen in 1.0.0 in favor of Object TransformStreams which we will henceforth refer to as Formatters.

This is fixed in 3.0.0 in favor of a streams based approach.

Turns out this is a duplicate / side-effect of #135.


x64dbg packages not installed

What's the problem?
I recently installed flarevm on a Fresh Windows 10 vm. All of the packages installed successfully. But some of the packages failed to installed. These packages are:
2024/09/30 18:35:16 [x64dbg.vm] vm.common.psm1 [+] ERROR : The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://sourceforge.net/projects/x64dbg/files/snapshots/snapshot_2024-04-11_18-47.zip/download'. Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote server"
At C:\ProgramData\chocolatey\helpers\functions\Get-WebFile.ps1:351 char:13
+             throw "The remote file either doesn't exist, is unauthori ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024/09/30 18:35:26 [x64dbg.plugin.dbgchild.vm] vm.common.psm1 [+] ERROR : Cannot find path 'C:\Tools\x64dbg\release' because it does not exist.
At C:\ProgramData\chocolatey\lib\x64dbg.plugin.dbgchild.vm\tools\chocolateyinstall.ps1:6 char:16
+ ...   $toolDir = Join-Path ${Env:RAW_TOOLS_DIR} 'x64dbg\release' -Resolve
+                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024/09/30 18:35:29 [installer.vm] chocolateyinstall.ps1 [+] INFO : 	x64dbg.plugin.dbgchild.vm has been installed
2024/09/30 18:35:29 [installer.vm] chocolateyinstall.ps1 [+] INFO : Installing: x64dbg.plugin.ollydumpex.vm
2024/09/30 18:38:49 [x64dbg.vm] vm.common.psm1 [+] ERROR : The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://sourceforge.net/projects/x64dbg/files/snapshots/snapshot_2024-04-11_18-47.zip/download'. Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote server"
At C:\ProgramData\chocolatey\helpers\functions\Get-WebFile.ps1:351 char:13
+             throw "The remote file either doesn't exist, is unauthori ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024/09/30 18:39:05 [x64dbg.plugin.ollydumpex.vm] vm.common.psm1 [+] ERROR : Cannot find path 'C:\Tools\x64dbg\release\x32' because it does not exist.
At C:\ProgramData\chocolatey\lib\x64dbg.plugin.ollydumpex.vm\tools\chocolateyinstall.ps1:21 char:17
+ ... oolDstDir = Join-Path ${Env:RAW_TOOLS_DIR} 'x64dbg\release\x32' -Reso ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2024/09/30 19:16:09 [installer.vm] chocolateyinstall.ps1 [+] ERROR : Failed to install: x64dbg.plugin.scyllahide.vm
2024/09/30 19:16:10 [installer.vm] chocolateyinstall.ps1 [+] ERROR : Failed to install: regshot.vm
2024/09/30 19:16:10 [installer.vm] chocolateyinstall.ps1 [+] ERROR : Failed to install: x64dbg.plugin.x64dbgpy.vm
2024/09/30 19:16:10 [installer.vm] chocolateyinstall.ps1 [+] ERROR : Failed to install: x64dbg.plugin.ollydumpex.vm
2024/09/30 19:16:10 [installer.vm] chocolateyinstall.ps1 [+] ERROR : Failed to install: x64dbg.plugin.dbgchild.vm
2024/09/30 19:16:10 [installer.vm] chocolateyinstall.ps1 [+] ERROR : Failed to install: x64dbg.vm

I tried to install the packages using chocolatey package manager but this is the error i got:
Installing the following packages:
x64dbg
By installing, you accept licenses for the packages.
x64dbg not installed. The package was not found with the source(s) listed.
 Source(s): 'C:\Users\malware-victim\Desktop;C:\Users\malware-victim\Desktop;https://www.myget.org/F/vm-packages/api/v2;https://myget.org/F/vm-packages/api/v2;https://community.chocolatey.org/api/v2/'
 NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify `--pre`,
 the package may not be found.
Please see https://docs.chocolatey.org/en-us/troubleshooting for more
 assistance.

I tried the --pre flag but still was not able to install the package.
Steps to Reproduce

Run the install.ps1 script on a fresh Windows 10 Home.
At the end of the install, you will see the message of package not installed

Environment
VM AV Details
AntiVirusProduct classname does not exist...
VM PowerShell Version
5.1.19041.3803
VM CLR Version
4.0.30319.42000
VM Chocolatey Version
2.3.0
VM Boxstarter Version
Boxstarter|3.0.3
Boxstarter.Bootstrapper|3.0.3
Boxstarter.Chocolatey|3.0.3
Boxstarter.Common|3.0.3
Boxstarter.HyperV|3.0.3
Boxstarter.WinConfig|3.0.3
Additional Information
Log file is attached for reference.
log.txt.txt

@syed-ahmad-maaz I have tested this both manually (link) and couple days back with installer (Flare VM) and it worked fine in both cases. Since the SourceForge uses Cloudflare, it's likely that your IP was blocked for some reasons (TOR, VPN, etc).

@wand3rlust Thank you for replying. It turns out that my IP address was blocked. I have manually downloaded and installed the tools. Closing this issue as resolved.


How to commission public artwork (hint: not so big that it requires planning permission)

Also added, and who knew?!?


2020 Toyota Highlander Hybrid Engine fingerprint

Engine Fingerprint from 2020 Toyota Highlander Hybrid Platinum

Please include the dongleID from the device that this firmware was taken from

DongleID: b1927e255a1630fe


Exception occurred while running ABI with different metadata name.

After changing metadata name from agent to something else in all.yaml, ABI execution in not getting complete and throwing error, Kernel not found.

This issue has been resolved. PR https://github.com/IBM/Ansible-OpenShift-Provisioning/pull/292


Vector Screen burst size does not match its rectangular nature at higher levels

The Vector Screen is as written a rectangle and it's heightened version is a 10x10 rectangle (as stated by 10 feet wide) which would be a 5 foot burst however it is coded as a 10 foot burst. I have checked my book and the errata for relevant changes and text validity.

Rereading the spell with a fresh mind. I think the ambiguity of the spell requires a Errata from Paizo... It only says 10 feet wide which is modification to its original area of single square. I assumed this was an odd case of square shaped area but it just isn't clear enough what the heightened version is meant to be. It could be interpreted as a 10ft burst, 2 adjacent squares, or a 5ft burst.

Closing as a whyzo, need them to clarify what they mean here.


F/flutter ( 3850): [FATAL:flutter/runtime/dart_vm.cc(413)] Error while initializing the Dart VM: SSE2 is required.

F/flutter ( 3850): [FATAL:flutter/runtime/dart_vm.cc(413)] Error while initializing the Dart VM: SSE2 is required.
有没有遇到相同问题的朋友啊？
flutter doctor -v
[✓] Flutter (Channel dev, v0.9.4, on Mac OS X 10.13.4 17E199, locale zh-Hans-CN)
    • Flutter version 0.9.4 at /Users/mampod/Documents/product/client/flutter
    • Framework revision f37c235c32 (2 days ago), 2018-09-25 17:45:40 -0400
    • Engine revision 74625aed32
    • Dart version 2.1.0-dev.5.0.flutter-a2eb050044

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/mampod/Documents/product/client/AndroidSDK
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/mampod/Documents/product/client/AndroidSDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4, Build version 9F1027a
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 28.0.2
    • Dart plugin version 181.5616
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] Connected devices (2 available)
    • MuMu     • emulator-5554                        • android-x86 • Android 4.4.4 (API 19)
    • iPhone 8 • EB534312-FC79-44F2-8BAB-E8A3031246A2 • ios         • iOS 11.4 (simulator)

• No issues found!

Why did you create a new issue?
You already commented on #21988.
Do you think they are not the same? Please point out why.

[FATAL:flutter/runtime/dart_vm.cc(411)] Error while initializing the Dart VM: SSE2 is required.
现在错误码变成411了，但是依然不能解决问题

Merging with #21988

$ flutter doctor -v
[√] Flutter (Channel stable, v1.5.4-hotfix.2, on Microsoft Windows [Version 10.0.17134.765], locale zh-CN)
• Flutter version 1.5.4-hotfix.2 at D:\fluttersdk\flutter
• Framework revision 7a4c33425d (4 weeks ago), 2019-04-29 11:05:24 -0700
• Engine revision 52c7a1e849
• Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\Users\wb-zyl537012\AppData\Local\Android\sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
• All Android licenses accepted.
[√] Android Studio (version 3.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 31.3.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[√] VS Code (version 1.34.0)
• VS Code at C:\Users\wb-zyl537012\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.0.2
[√] Connected device (1 available)
• MuMu • <IP_ADDRESS>:7555 • android-x86 • Android 6.0.1 (API 23)
• No issues found!
我也是这个问题，请问有解决了的嘛？

@zhangyanling77 https://github.com/flutter/flutter/issues/21988#issuecomment-536243610


GEODE-8176: Add more checks in a flaky test

Hi @metatype
I have been trying to reproduce the failure reported in the ticket, but I have not been able to do it yet.
I dont know if you have progressed with this issue but just in case I think that we could add these checks to the test case in develop branch to have more information next time it appears.

I have rebased the PR now that LGTM Java Analysis seems working again.

Passing this over to Bill and Bruce, I'm afraid I don't have much context.

@Bill please if you approve it, merge this PR (I dont have permissions). Thanks


mcu-interface: fix blocking, add kill for can_rx task, fix ack

Changes in this PR:

Turns the std::sync::mpsc channels into tokio channels. This allows us to receive messages asynchronously and reduces the number of spots we need to call blocking code from async.
Refactors how the ack ids are created. I suspect previously there were some edge cases that could cause bugs, this new way is simpler and probably more correct.
Adds a oneshot "kill" channel to inform can_rx that it should terminate.
Places a few remaining spots that were blocking in async code behind a tokio::task::spawn_blocking.

Needs testing, will do this on Monday

Tested orb-mcu-util and the log-messages example. both seem to work fine.


Update docs for typo fixes

Fixes typos throughout whole repo.

@ferhatelmas Thank you so much for your contribution! We would like to mention you in our tweets and also send some awesome stickers and a tshirt your way. Will you please email me your twitter handle here<EMAIL_ADDRESS>?


Update schema

Updated with links to updated activities in:
https://raw.githubusercontent.com/ReproNim/reproschema-library/enh/rc4/activities/
The conditional logic of what activities are shown based on age conforms to:
https://nda.nih.gov/nda/nimh-common-data-elements
Demo:
https://ibevers.github.io/reproschema-ui/#/?url=https://raw.githubusercontent.com/ibevers/nimh-minimal/update_schema/nimh_minimal/nimh_minimal_schema

this added the .venv directory

this added the .venv directory

Fixed @satra

also can we update the github workflow checksum, so this protocol renders using the correct ui committish?

also can we update the github workflow checksum, so this protocol renders using the correct ui committish?

Slightly confused by what you mean here. My conclusion from the conversation about the UI before is that the only way to render a protocol with a specific version of the UI is to host that version somewhere. Would you mind explaining a bit more?

My conclusion from the conversation about the UI before is that the only way to render a protocol with a specific version of the UI is to host that version somewhere.

indeed and it would be hosted here in this repo. so updating the checksum in config.env should be all that's needed.

But what should I update the checksum to? The latest checksum for the fix/static branch of reproschema-ui?
https://github.com/ReproNim/reproschema-ui/tree/fix/static

i think that was already merged, so the current checksum should be fine.

sorry it wasn't merged. so yes, you can take the committish of that branch and use it.

sorry it wasn't merged. so yes, you can take the committish of that branch and use it.

Done @satra


Fixes sample domain in image wdt

Align the domain-home-in-image samples with the newest changes to the corresponding docker images. This includes executing commands relative to the directory ${scriptDir}.

does this rely on some change to docker-images repo too, or is it standalone?

@markxnelson The PR is to align the Operator sample script with the latest changes to the docker-images repo - https://github.com/oracle/docker-images/pull/1088 has been merged already.

The changes to docker-images have already been merged to master by Monica.


Change charts in filter inspection to parallel charts

Use https://github.com/sgratzl/chartjs-chart-pcp

Done


Create PDF-documents

Currently, the generation of PDF-documents is in general deactivated.
Every action, which will generate a PDF-document, has to be checked.
Seen actions that create a PDF-document:

[x] Motion-List: (Multiselect) Export as PDF
[x] Motion-Detail: Export as PDF
[x] Agenda-Item-List: Export as PDF
[x] User-List: Export user-list as PDF
[x] Assignment-List: Export as PDF
[x] Assignment-Detail: Export as PDF
[x] User-Detail: Export as PDF
[ ] User-List: Export credentials as PDF

"User-List: Export credentials as PDF" throws the following error:
Uncaught (in promise) Unrecognized document structure: {"style":"userDataValue"}

"User-List: Export credentials as PDF" throws the following error:
Uncaught (in promise) Unrecognized document structure: {"style":"userDataValue"}

Done.


Add scaled water rest implementation (second attempt)

Description
This PR creates RESTTopologyFactoryV3, a class that generates a rest-like system where the energies are scaled according to rest with the following exception: scale rest-water interactions by beta/beta_0 (previously was being scaled by sqrt(beta/beta_0).

Motivation and context

How has this been tested?

Change log

@zhang-ivy is this PR still something we want/need?


Can we render the Textured mesh with the Viewer in Nerfstudio?

Can the Viewer support the Textured mesh input? (e.g., attach texture to the extracted-mesh from the DN-Splatter.)

Closing in favor of https://github.com/nerfstudio-project/viser/issues/219!


chore(main): release 0.29.1

:robot: I have created a release beep boop
0.29.1 (2024-12-09)
Bug Fixes

improve windows support (d3b6e62)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.29.1
:sunflower:


CVE-2020-12265, There is no fixed version for decompress-tar, how to prove there is no issure for decompress-4.2.1?

There is no fixed version for decompress-tar, and how to prove there is no issure for decompress-4.2.1?

@waltbest2 did you find a solution for this?
Thanks!

AWS Inspector reports that decompress-tar is vulnerable (linking to https://nvd.nist.gov/vuln/detail/CVE-2020-12265) — was/is the issue in decompress or in decompress-tar?

There is no fixed version for decompress-tar

decompress-tar is decompress' dependency, it extracts files.
Issue was in paths :

package fails to prevent extraction of files with relative paths, allowing attackers to write to any folder in the system,

— from here

how to prove there is no issure for decompress-4.2.1

There are tests in the PR with fix, didn't dive into them, but checking tests can be the way to start.


Latex in comments

I've been learning about ml in python for a few years now and it's become second nature for me to create the latex markup of the equation I need for a model in the cell above my code in a notebook. I work day to day in typescript, and I really miss this pattern of behavior.
The request: a feature to turn on /off inline (markdown with) Latex in comments (something like double clicking a comment with markdown or latex, or putting the cursor in the comment, would de-render it for editing).
I want this enough to probably contribute some weekends to get that extension. I barely know anything about extension writing though, I contributed exactly one pr to an extension so far. How involved would this be?
I am cognizant of the fact that jsdoc/tsdoc would probably already be much more inline-rendered by default if this wasnt difficult in some way. Why is it difficult?

Closing as out of scope for core VS Code but may be possible with some clever extension api usage


Usability : Docking the 'Metadata' floating window

The 'Metadata' window is fine for viewing EXIF data. But the window is a floating one, "a la GIMP" .
Wouldn't it be nicer to have the medata docked on a side ? The user could choose the size position of this window, and undock (i.e. make it float) at will.
I've just seen that egui_dock crate (https://github.com/Adanos020/egui_dock) that would be perfect. It has 4 nice examples. These have dev-dependencies on the eframe framework, but it is not in dependencies, so using eframe should not be a requirement in another egui app (even if I'm sure that eframe is a great crate, being designed by emilk the creator of egui)
As I said in my other posts on usability I'm not an egui expert so I don't really figure if it requires tons of work... just my 2 cents on how to make simp great.

It is an interesting idea but it is not really a vital feature. Simp already has alot of dependencies and I prefer avoiding unstable dependencies if the feature is not vital.


Check OLP_SDK_ENABLE_ANDROID_CURL for Android only

Make sure that OLP_SDK_ENABLE_ANDROID_CURL doesn't affect other platforms, as it should be possible to turn on this option without additional checks for platform.
Relates-To: OLPSUP-20966
Signed-off-by: Andrey Kashcheev<EMAIL_ADDRESS>

@rustam-gamidov-here Previously, the user was required to check that the platform is actually Android before enabling OLP_SDK_ENABLE_ANDROID_CURL. This is not very obvious and incorrect in my opinion and we have the first issue from that.
And now, the user shouldn't check anything and just enable this flag if needed.


Update index.js

The existing UI of the user guide page does not provide user a good reading experience and does not leave a good impression on user, so i will improve the UI and the functionality. Problem solved .

@vikashmurugesh ,As I can see, you've created a PR without meaningful contributions and with an ambiguous or incorrect description. I kindly request you to avoid submitting spam PRs. If you'd like to contribute, please create a valid issue or work on an existing one, and then submit your PR with real improvements and a clear description.


Can't copy and paste over ssh

I can't copy ctrl+c ctrl+v  text inside a ssh session using gnome terminal or terminator
it works fine on my local machine,  both the local machine and the remote machine has xclip installed

See also xavi-/node-copy-paste#28.

Hi, I had at the beginning the same problem. But instead of using Control+C and Control+V, I started using Control+Shift+C and Control+Shift+V, and it worked.
At the same time, maybe it's also necessary to install xclip:
sudo apt-get install xclip


Fix NullPointer

http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2761225-valkyrien-warfare-airships-physics-subworlds-and?comment=348

Lets hope this fixes things for him


can't select version compiled with specific version of OTP

I'm used to using scoop install<EMAIL_ADDRESS> I don't see the option to specify the OTP version with vfox.

I'm used to using scoop install<EMAIL_ADDRESS>I don't see the option to specify the OTP version with vfox.

Yes, this method is not supported at present. If you are interested, you can summit a pull request.


Added support for http-request to frontend and backend config

Same as pull request #20  but w/ support for adding http-request to frontend or backend config.

Thank you!