Can't retry passing tests

Today we had a test suddenly start failing. It would be good to be able to rerun past cases of this test (on older commits) to find out if it was something that started because of a commit or something that was always broken / newly broken independent of the commits. Currently, however, there's no way to rerun a test that's passed. You can click rerun, but it doesn't do anything (though it does tell you it will).

The task should be reporting that it failed to re-try the task that's a bug. Preventing from running a succeeded task was intended but we can enable that again.

Historically, we have not supported rerunning previously green tasks because of some unwanted scenarios that can crop up.
For the engine atleast, if retrying tasks that generate artifacts, and a retry is performed on a release commit, it will overwrite the newer artifacts.
Additionally, cocoon does not track task history, only the latest result, so retries on previously green runs could also close the tree.

For the engine atleast, if retrying tasks that generate artifacts, and a retry is performed on a release commit, it will overwrite the newer artifacts.

That does seem like a problem. Is there some way we can flag shards that have side-effects so that they can't be rerun?

Additionally, cocoon does not track task history, only the latest result, so retries on previously green runs could also close the tree.

That's a feature, not a bug. The way we have it now is sort of backwards. A test that sometimes fails and sometimes passes is a failing test, but we mark it as passing. We really should mark flaky tests as failing, not passing. If anything, we should detect that a test has a history of failing, and retry it automatically several times until it fails.

For the engine atleast, if retrying tasks that generate artifacts, and a retry is performed on a release commit, it will overwrite the newer artifacts.

That does seem like a problem. Is there some way we can flag shards that have side-effects so that they can't be rerun?

One example of this problem is:
A given commit is released(any release channel) and someone accidentally retries that build creating new artifacts. Because the new artifacts never went through the release process they never get signed.

Additionally, cocoon does not track task history, only the latest result, so retries on previously green runs could also close the tree.

That's a feature, not a bug. The way we have it now is sort of backwards. A test that sometimes fails and sometimes passes is a failing test, but we mark it as passing. We really should mark flaky tests as failing, not passing. If anything, we should detect that a test has a history of failing, and retry it automatically several times until it fails.

This sounds like functionality that needs to be implemented as a separate service potentially running overnight to avoid impacting the development workflows.

We are going to implement a tool to run overnight and collect and report flakiness.

This was fixed in https://github.com/flutter/flutter/pull/99375

Feel free to open another bug if we're still interested in collecting flakiness metrics in off peak hours


Ability to use HTML in the message

Hi
It will allow to have multiple line snackbar (by using br) + style the message with bold/italic/etc

You can already do it:
<template v-slot:default="{ message }">

</template>

Check the demo at https://codesandbox.io/s/v-snackbars-demo-forked-je27y?file=/src/App.vue:200-305

Hi
I completely forgot about the slots. It makes sense then.
Thank you.


version: handle -stable in tag

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Account for -stable in a version tag by making two rules slightly more specific, allowing the version for wolfSSL to be handled by a later rule. (xref #7088)

Looks good, thanks again @EricFromCanada!


[BUG] deal with \mbox

Describe the bug
It appear that some authors have \mbox{} in their text (they probably have a reason)
Paper identifier
https://arxiv.org/abs/2303.02816
Expected behavior
Let's remove the mbox visibility

mbox is an annoying beast and people are very inconsistent on how to use it.
Current update to arxiv_on_deck_2 is not robust.

This dug up more than mbox.
Fixed in
cecfbce of Arxiv_on_deck_2.


Split terminal windows directories

Issue Type: Bug
In latest version of VSCode, I can no longer have split terminal windows from different working directories like I could previously. I have a workspace set up with multiple directories but can no longer open terminal in the second directory
VS Code version: Code 1.29.0 (5f24c93878bd4bc645a4a17c620e2487b11005f9, 2018-11-12T07:39:38.932Z)
OS version: Darwin x64 17.4.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 2

Memory (System)
16.00GB (0.27GB free)

Process Argv

Screen Reader
no

VM
0%

You should be able to configure this with the setting terminal.integrated.splitCwd

This is configurable using terminal.integrated.splitCwd. The default behavior is what you now see. To be able to select the workspace root, set this new setting to workspaceRoot.


Bugfix, infering scale.range for d3.scaleSequential

I was trying to use the library with a d3.scaleSequential, and it failed because this type of scale doesn't have a .range() function. I modified the library to infer the range using the starting and ending values.
Here is an example code that would break the library
https://jsfiddle.net/duto_guerra/h70x34b1/1/

Thanks for making the pull request and the example. I updated the code a bit and merged. Here is an example on the docs page: http://d3-legend.susielu.com/#color-sequential

Beautiful! :)


Decouple FileFormat from datafusion_data_access

Which issue does this PR close?
Part of #2489
Rationale for this change
The IOx ObjectStore does not have an equivalent notion of ObjectReader, decoupling FileFormat from such notions is therefore a necessary precondition of any migration. I also think it makes the API significantly easier to use
What changes are included in this PR?
Reworks FileFormat to be in terms of FileMeta and ObjectStore, instead of ObjectReader and ObjectReaderStream. These concepts translate cleanly, with FileMeta -> ObjectMeta.
Are there any user-facing changes?
Yes, FileFormat is a public API

Seems reasonable to me

cc @richox


[Advanced Approval Workflows] Update pendingAction/pendingFields when making an action offline

Details
The approach we decided to go with is to grey out workflow when any member from this workflow is affected (member or approver is added/updated/removed).
This means that with only one update there is a chance there are more than just one workflow greyed out, due to the fact that any users can be in multiple workflows at once.
Fixed Issues
$ https://github.com/Expensify/App/issues/47701
PROPOSAL: N/A
Tests
N/A
Offline tests

Open Workflows page (it has to be turned on in More features settings page)
Locally edit canUseWorkflowsAdvancedApproval function to return true (or use canUseWorkflowsAdvancedApproval beta)
Add new approval workflow and update/remove existing workflows

QA Steps
Same as Offline tests
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: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[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 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.
[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 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(theme.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 related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[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 the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[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.

Screenshots/Videos

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/d2204acf-a3b8-4af8-9c05-ca7d314e9317

@blazejkustra What is the final expecteation? Currently, If we have any actions offline, all workflows will be greyed out. I think it is different from the PR description

The approach we decided to go with is to grey out workflow when any member from this workflow is affected (member or approver is added/updated/removed).

@blazejkustra What is the final expectation?

The approach we decided to go with is to grey out workflow when any member from this workflow is affected (member or approver is added/updated/removed).
☝ That's the final expectation

Currently, If we have any actions offline, all workflows will be greyed out. I think it is different from the PR description

I think it's not true 🤔 Try to add more users to the workspace and edit workflows/add new ones

@DylanDylann I think it works as described in the description:
https://github.com/user-attachments/assets/36fb0d87-2a0a-44c3-8b78-1406cd2f3c30

@blazejkustra When add an workflow offline, the default workflow also be greyed out
https://github.com/user-attachments/assets/4d52baa9-d8d2-4cd2-b72d-fb5934ef14c9

Because the default workflow contains every member that includes members in the new workflow.
It happens to me because isDefault is true
https://github.com/Expensify/App/blob/cd5ed20881ba5435ec6beabdf74a7b1d31b10c48/src/libs/WorkflowUtils.ts#L134
so the pendingAction still be applied to the default workflow

@DylanDylann To be clear, what is the expected behaviour in your opinion? When adding a new workflow, the default workflow should also be greyed out because the default workflow members are changed?

@blazejkustra Sorry for back and forth. The current code works well with the new expectation.

I want to confirm this new expectation because I have never seen the same situation in our App. @youssef-lr Could you help verify this expectation?

The approach we decided to go with is to grey out workflow when any member from this workflow is affected (member or approver is added/updated/removed).
This means that with only one update there is a chance there are more than just one workflow greyed out, due to the fact that any users can be in multiple workflows at once.

Note that: Two workflows only be related together if an approver belongs to both workflows. If member O is a member of workflow A and also an approver of workflow B --> workflow A and workflow B have no relation. With the current approach, If there is any update to member O in workflow A, workflow B also be grey out although workflow B isn't related to the change in workflow A
cc @tgolen Tag you because you follow this feature at the beginning, It is perfect to have your opinion on this

@DylanDylann Still missing reviewer checklist, right?

@blazejkustra I want to hear a thought from the internal engineer about https://github.com/Expensify/App/pull/48086#issuecomment-2324344245 before completing the checklist

I want to hear a thought from the internal engineer

@DylanDylann Sure!
I haven't linked this one before here. Here's the missing context:

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] 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

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

: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.

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.0.30-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@blazejkustra How should we perform?

Locally edit canUseWorkflowsAdvancedApproval function to return true (or use canUseWorkflowsAdvancedApproval beta)

On staging you need workflowsAdvancedApproval beta to test this feature @kavimuru


correct install instructions for Ubuntu/Debian

@Jarel1337 I downloaded Ubuntu Mate 18.04 myself and gave it a try, and your instructions were correct. It seems that with Ubuntu 18.04 using just apt is preferred over apt-get, and the svg library was indeed missing. Instead of replacing the existing Ubuntu 16.04 installation instructions I added a new set of instructions here: https://github.com/fourtf/chatterino2#ubuntu-1804
Let me know if those instructions are lacking.


fix(create-cloudflare): add a newline character to the line prepended to wrangler.toml

This PR adds a newline character to the line prepended to wrangler.toml (when name or compatibility_date is missing in the template).
Without this change, the prepended line would cause a syntax error.
example:
original wrangler.toml (in template)
main = "index.js"

prepended wrangler.toml
name = "foo"compatibility_date = "2024-11-06"main = "index.js"

after this PR:
name = "foo"
compatibility_date = "2024-11-06"
main = "index.js"

Tests

[ ] TODO (before merge)
[x] Tests included
[ ] Tests not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[x] Not required because: This PR contains only minor changes.

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Documentation not necessary because: remote-template format is originally undocumented.

@syumai thank you so much for catching this bug and creating this PR to fix it 🎉 🙏 ❤ . I've built on top of your finding and updated all the relevant unit tests to test the output shape overall as opposed to testing just for the presence of specific substrings. Can you please rebase your branch on latest main. I want to make sure that your fix fixes all broken use cases not just the one you've updated the test for 🙏

@CarmenPopoviciu I rebased the PR and fixed tests. Please check later 🙏

@syumai this looks fantastic! you da best! thank you so much! Waiting for the CI to pass and will merge so we can release this today 🎉


ngModel: force running formatters for custom things

Hello,
I am working on the application, where I have input field with ng-model,  inside which I need to show number in different units ata time (like px or %),
From the application point of view it is convenient to keep single unit in the model for calculations (i.e model contains only px values), and show different units in input field with help of parsers and formatters. I also have a toggle button for changing the unit.
The problem is , when I try to change the unit, I need formatters to run and store different viewValue inside input field (like instead of px value, show % value in input, though model still has px value).
I did not find any good way of doing this.
I end up incrementing my px value, and in $timeout decrement again, which runs second digest, and causes unwanted UI behaviour (like if model value is binded to something else, it will increment and decrement in few milliseconds, but you can still notice it).
Can we have an api which will trigger formatters for ngModelController and update view value?

Let's centralize the discussion here: https://github.com/angular/angular.js/issues/3407


Remove Install Class from README.md

The install class is still described inside the README.md file. It was removed so description itself can be removed as well

Fixed missing informations inside README.md


Is there anyone who can implement this project in currently Python 3 and  new  tensorflow？

Can author update this project?thank u

Will put this on the roadmap, some update is coming also.

I wonder if https://github.com/pcgreat/zi2zi can help?

@hongtaoZ and @pcgreat can help us in this case
Also calling for help from @lionem2018 and @dbc148


Very difficult to make work

Have been trying on both windows and Linux to download all reqirements and compile to make it work, but everytime something goes wrong. It seems like it needs to updating. Its a pity cause I would really like to use it

I'm not a dev, but it would help if you included system information and issue logs. I was able to get it working on a google cloud VM running ubuntu 20.04 LTS and running the renders on my laptop running arch linux + opengl.

If you have a particular issue please re-open this issue and post the details. Otherwise I am closing this for now because there is nothing I can do to help from the information you've given.


License of DLR sample code

Hi,
I would like to know under which license the sample code is distributed.
Best regards, Paulo

License for the repository is Apache 2.0.

I am asking because all files in Src have an header with the reference to Apache 2.0. However the sample code does not have it.

I have no idea what the original intent was (omitted intentionally or just because no one ever got around to adding it).


Org user can be created with lower disk quota than maximum import size

Context
Working on community edition of builder.
Steps to Reproduce
Please break down here below all the needed steps to reproduce the issue

Create an organization with owner<EMAIL_ADDRESS>Set max_import_file_size to<PHONE_NUMBER> (1Gb)
Create a user<EMAIL_ADDRESS>within the organization using the GUI using the default quota (100Mb)

Current Result
New user has a smaller quota than max import size
cartodb_production=# select email,quota_in_bytes,max_import_file_size,max_import_table_row_count from users where organization_id = '87be24d2-a643-448f-a739-de927b7da7df';
       email       | quota_in_bytes | max_import_file_size | max_import_table_row_count
-------------------+----------------+----------------------+----------------------------
<EMAIL_ADDRESS>|     104857600 |<PHONE_NUMBER> |                    1000000
<EMAIL_ADDRESS>|<PHONE_NUMBER>776 |<PHONE_NUMBER> |                    1000000
(2 rows)

Expected result
Quota should never be smaller than max import size
Browser and version
Chrome Versión 56.0.2924.87 (64-bit)

This should be checked only on creation, because an organization owner might want to reduce quota to a user but he can't change import limit.


Implement not implemented functions for lazy series

# The following functions are not implemented yet and should raise if used.
funs = [
  memtype: 1,
  fetch!: 2,
  mask: 2,
  from_list: 2,
  sample: 4,
  size: 1,
  slice: 2,
  take_every: 2,
  to_enum: 1,
  to_list: 1,
  transform: 2
]

Functions that should be implemented

[ ] mask/2
[ ] sample/4
[ ] size/1
[ ] slice/2
[ ] take_every/2

Functions that NOT should be implemented

memtype/1
fetch!/2
from_list/2
to_enum/1
to_list/1
transform/2

@josevalim @philss Please check it's correct

We cannot implement fetch! because it requires getting a value from something lazy (which has no value).
We cannot implement transform because it requires Elixir functions, and we cannot convert those to backend operations (such as Rust, SQL queries, etc).
You may be able to implement the others... but not guaranteed.

Thanks!


How to get a list of modules?

Is there any functionality to get all / only enabled / the disabled modules?

you can get the array of enabled modules from your config (if there is one) config("modules.enable")
Besides that you could use Laravels Filesystem and get the directories from your Modules folder Storage::directories(app_path().'/Modules/')


[vcpkg-scripts] Pass native install dir to nmake

What does your PR fix?
Makes vcpkg_build_nmake pass INSTALLDIR as native windows path. CMake paths use / separators which don't work for mkdir, copy etc.

Which triplets are supported/not supported? Have you updated the CI baseline?
windows, no

Does your PR follow the maintainer guide?
yes

TBH I don't even know which port uses the INSTALLDIR macro. Is this a nmake convention? Only few ports use vcpkg_build_nmake at the moment. Those that I touched (related to GIS) need INSTDIR. The next step is to add an option to name the variable...

qmake also generates Makefiles for nmake on windows. vcpkg_build_qmake uses jom instead of nmake.

LGTM.

Thanks for the fix!


Getting "No such file or directory: 'datasets/coco_caption/coco-train-words.p'" when training model with SCST loss optimization

I am training latest Oscar code for SCST optimization as per the instructions given in this section - https://github.com/microsoft/Oscar/blob/master/MODEL_ZOO.md#image-captioning-on-coco. However, I am getting below error:
Traceback (most recent call last):
  File "oscar/run_captioning.py", line 1009, in <module>
    main()
  File "oscar/run_captioning.py", line 984, in main
    last_checkpoint = train(args, train_dataloader, val_dataloader, model, tokenizer)
  File "oscar/run_captioning.py", line 455, in train
    baseline_type=args.sc_baseline_type,
  File "/home/default/ephemeral_drive/work/image_captioning/Oscar_13april/oscar/utils/caption_evaluate.py", line 119, in __init__
    self.CiderD_scorer = CiderD(df=cider_cached_tokens)
  File "/home/default/ephemeral_drive/work/image_captioning/Oscar_13april/oscar/utils/cider/pyciderevalcap/ciderD/ciderD.py", line 28, in __init__
    self.cider_scorer = CiderScorer(n=self._n, df_mode=self._df)
  File "/home/default/ephemeral_drive/work/image_captioning/Oscar_13april/oscar/utils/cider/pyciderevalcap/ciderD/ciderD_scorer.py", line 80, in __init__
    pkl_file = cPickle.load(open(df_mode,'rb'), **(dict(encoding='latin1') if six.PY3 else {}))
FileNotFoundError: [Errno 2] No such file or directory: 'datasets/coco_caption/coco-train-words.p'

I have looked into the files that I should download and I did not find coco-train-words.p present in any of the recommended downloads given in this section - https://github.com/microsoft/Oscar/blob/master/DOWNLOAD.md#datasets. I downloaded coco_caption dataset at this location - https://biglmdiag.blob.core.windows.net/oscar/datasets/coco_caption.zip. However, this the dataset download for coco_caption does not has the file coco-train-words.p. Also, I have been using an older version of Oscar code and I did not have this issue with that version - https://github.com/microsoft/Oscar/tree/9b07b6735267c0eb30fc2efd482d4295d13c7b4f.
Please let me know how I can download the coco-train-words.p file or if anyone has guidelines about how to resolve this issue.

I found coco-train-words.p file by downloading coco_caption from this link - https://github.com/microsoft/Oscar/blob/master/VinVL_DOWNLOAD.md#datasets. However, the new download link did not have train.feature.tsv file, which I copied from the download from this location - https://github.com/microsoft/Oscar/blob/master/DOWNLOAD.md#datasets.


Protect AccountUser Name with only allowed symbols

Seems like this must be compared to a older commit on 0.20 branch because a lot of the commits listed should already be present in 0.20?  Maybe a rebase is required?

Seems like this must be compared to a older commit on 0.20 branch because a lot of the commits listed should already be present in 0.20? Maybe a rebase is required?

I made a merge from 0.20 to remove conflicts


 This could be due to the way the IDE driver calls insw() and outsw(). The ATAPI code had this issue and has been fixed in commit  e520c85 but the issue has not been fixed for the ATA code.
Of course, it is also possible (and very likely) that the FAT driver itself is responsible.

Working on this, starting with commit 97f1b79

The new rework of the FAT driver correctly writes files to the disk, it can even (unlike the previous one) overwrite existing files. The directory is written correctly, with no duplicate or missing filenames (also unlike the previous one). All use cases have been tested.
The only problem that remains currently is writing to a nested directory.

Fixed not writing to sub-directories. Currently, though, there is a problem with reading from a sub-directory.

Reading sub-directories problem is fixed. Now you can read and write however you wish!


Moved appcompat classes out of core

Description
Fixes #56
Check list

[x] I have updated CHANGELOG.md if required.
[x] I have updated documentation if required.

Closing for now as we still need to make a decision as to whether we want this extra module or not.


Spark Packages Release

Hi,
Would you like to make a release to the Spark Packages Repository with this nice library? This will allow users to run your package with ease, simply by adding the flag:
--packages FlytxtRnD/GMM:0.1 to pyspark or spark-submit.
Your package will also be ranked higher on the website for having a distribution.
You may use the spark-package command tool to make a release directly from the command line!
Let me know if you have any difficulties in making this happen!
Best,
Burak

@brkyvz
We are not able to publish the package.Please review the following steps and reply what's wrong.

Created a new folder in system named packages
Move to the packages folder
spark-package init -p -n FlytxtRnD/GMM
spark-package zip -f GMM -n FlytxtRnD/GMM -v 0.1
spark-package publish -c credentials -z GMM-0.1.zip -n "FlytxtRnD/GMM" -v "0.1"

Last command gives an error like please specify the foldeer of the package.Could you please tell where we need to give the github repository URL?

@FlytxtRnD Thanks for letting me know. I'll fix it.
Can you please simply try the following command:
spark-package publish -c credentials -f GMM -z GMM-0.1.zip -n "FlytxtRnD/GMM" -v "0.1"
The github repository url we can derive from the package name, so you don't need to enter it. On thing that you should be careful about is that, we automatically read the "git commit sha" from your local repository (the folder) That's why we still need your folder. I should update the README.
Please make sure that the commit is also pushed to your remote repository.
Thanks,
Burak

Done. Thanks @brkyvz for your help.


Xbox Live component isn't making sensors, but still querying XboxAPI

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version): 0.51.2
Python release (python3 --version): Python 3.4.2
Component/platform: Xbox Live
Description of problem:
Prior to 0.50 (I jumped from 0.49 to 0.50 to 0.51 fairly quickly, so I'm still pinpointing where this might have heppened), the Xbox Live sensors worked for me.  Now, no sensors are created by the component in the entity list.  There are two XboxAPI calls made each time I restart HASS (I have two UIDs configured), but no more.
The component shows that it's being configured in the logs.  The config check shows that the secrets are being read correctly, and this was a working config.
2017-08-16 16:36:52 INFO (MainThread) [homeassistant.loader] Loaded sensor.xbox_live from homeassistant.components.sensor.xbox_live
<snip>
2017-08-16 16:37:05 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.xbox_live

There's nothing in the logs related to the sensor after this, and no errors.
Expected:
Sensors are created for the Xbox Live UIDs configured.
Problem-relevant configuration.yaml entries and steps to reproduce:
- platform: xbox_live
  entity_namespace: xbox
  scan_interval: 300
  api_key: !secret xboxapi_key
  xuid:
    - !secret duckpuppy_uid
    - !secret mithrixz_uid

To eliminate the secrets being the issue, I did edit the files and put the api_key and xuids directly in the config.  No change.

Looking at the code for the component, if XBoxAPI returns something other than success, it'll silently do nothing.  This config was a working config, so I'm not sure what errors it could be returning, but I'll try to write up a quick test script later tonight or tomorrow to see what might be going on there.

OK, the problem was that my XBox Live oauth token had expired on XboxApi.  That should be reported as an error when setting up the sensor.  I'll change the title of the ticket to be more in line with the real problem.

Can we reopen this issue?  I'm still hitting it.


switch readme to nextpnr-himbaechel

I was now thinking of adding more corrections to the readme (starting with removing mention of the long-suffering NS-2/honeycomb, references to which have already been cleared from the documentation of Gowin itself :)), but I very quickly realized that this would have to throw out the examples and move everything from the examples/ directory himbaechel is a level higher, and from here it would be nice to clean out the code, leaving only the Himbaechel part, and from here eliminate legacy gowin - in total, this will wait for now :smile:

Yes I think all of those are good ideas. One step at a time.


settings page responsiveness

correct it

anyone who want to work on it can comment here

Hi @mohityadav0903 I would love to work on this issue. Please assign it to me.

Does this look good?

Also I propose to remove these:

console.log() statements
error

hey @BIKRAM-SAHA u can work on it


RichTextBox with ClearTextButton and Watermark

It seems metro:TextBoxHelper.Watermark and metro:TextBoxHelper.ClearTextButton doesn't not affect RichTextBox.
Is there a way to fix that?

@JobaDiniz That's correct

I'm using RichTextBox only because I need to manipulate text position and ranges, but nothing fancy... my RichTextBox is just like an ordinary TextBox.
In fact, I'm interesting specially in the TextBoxHelper.ButtonCommand, TextBoxHelper.ButtonContent and MetroButtonTextBox style.
I just wanted that my RichTextBox looked like

Is this too hard to implement? Some guidance would be great.


Update appveyor.yml to start testing Ruby 2.3.1 on Windows

This became possible thanks to @Azolo's valiant effort to finally push out a new RubyInstaller with 2.3.1 support, but it's still currently blocked on AppVeyor adding Ruby 2.3.1 support (https://github.com/appveyor/ci/issues/925).

In the mean time, it seems there already is a 2.3.0 version on AppVeyor:
https://www.appveyor.com/docs/installed-software#ruby
I'll give that at try.

I tried it on branch try_appveyor_21_23.
There are some errors: https://ci.appveyor.com/project/eregon/spec/build/318


Style/ClassAndModuleChildren: Use nested module/class definitions instead of compact style.

I think this needs to go the way of the white buffalo.
it enforces this (nested)
class Api
  class V1
    class SomeController
    end
  end
end

instead of this (compact)
class Api::V1::SomeController
end

Vote for one of the following in the comments below.

Disabled (allow either way)
Nested (first example)
Compact (second example)

I vote Disabled. I don't have a strong preference either way.

Done with https://github.com/publicstrategies/rubocop-config/commit/f3fd82ae14a5f97c91764f4142a53a7f5579357e

I vote Disabled.


Moff plushies Extended. Part 1

About the PR

Adding 23 new plush moff variations ported over from the BeeStation build. Of them, 4 really have some features, the others are just variations of textures.
Increased variation of sounds that the plush moff can make.
Adding handheld sprites to all plush moffs.
Adding a cargo option to order a box with plush moffs.
Adding plush moff options to loadouts of any roles.
Adding an option for plush moffs to drop from gifts.
Adding moff plushie to dresser.
Adding moff plushie to toy spawner.

Why part 1? Because there is still an idea to add some more moff plushes or replace the existing ones and also add the ability to wear on the head =)
Why / Balance

More is better? Adding a bunch of variations to the moff toy and improving the existing one.
Technical details

As mentioned earlier. Most of the sprites are taken from the BeeStation build, although some were missing and were finished by another user, Miyugi.
From unique 4 plushies:

moff rainbow plushie - respectively, rainbow. Implemented in the same way as a rainbow carp or bee.
moff musician plushie - musical, able to play sunset.ogg composition, although quite quietly. It has a usage timeout of 10 minutes to prevent spam.
moff bluespace plushie - bluespace, has the ability to "teleport". This is implemented through the RandomWalk system, but with breaks of 30-60 seconds and a speed of 500.
broken moff plushie – broken, all sounds replaced by others and "poisonouns" when eated.

Loadout:

Moff plushie - available to all;
Moff rainbow plushie - available if you have more than 10 hours on passenger;
Moff bartender plushie - available if you have more than 5 hours on bartender.

Media

All moff plushie:
https://github.com/user-attachments/assets/560ca15f-74f8-47c1-94ea-145eff9c8930
Random moff plushie proto:
https://github.com/user-attachments/assets/36aed8fd-c353-470b-b711-4b7960485f47
Moff in hand:
https://github.com/user-attachments/assets/face93f1-3db0-42a5-8f39-9f1aecc57996
Moff sounds:
https://github.com/user-attachments/assets/ea6811af-5bbf-4c55-81a4-5be51dd43ef8
Music moff:
https://github.com/user-attachments/assets/4164312d-488e-4743-b134-baa7025ce55f
Moff in cargo:

Moff in loadout:

Requirements

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

From proto PlushieMoth to proto PlushieMoff. And added migration all PlushieMoth to PlushieMoffRandom.
Changelog

:cl:

add: Adding 23 new moff plushie variants and improvement of the existing one. And of course, adding ways to get them all!


[Feature Request] Support ability to switch between multiple keybindings.json files

Feature Request for multiple keybindings.json files
How it works now
Manually copy/paste desired config into keybindings.json, repeat to switch back
Feature request
Allow multiple keybinding config files to be imported and selected programmatically
Why
As a programmable keyboard user, I have one workflow for when I'm using my external keyboard, and another for when I'm using my laptop.  I would like to be able to define a set of keybindings for each use case separately, and be able to toggle between both from within VSCode.
Example
On my keyboard, I use FN+ j/k/i/l as arrow keys, which outputs the native keycodes for left/down/up/right.  To duplicate this behavior on my laptop keyboard, I have to define the following:
{
    "key": "ctrl+j",
    "command": "cursorLeft",
    "when": "textInputFocus"
},
{
    "key": "ctrl+k",
    "command": "cursorDown",
    "when": "textInputFocus"
},
{
    "key": "ctrl+i",
    "command": "cursorUp",
    "when": "textInputFocus"
},
{
    "key": "ctrl+l",
    "command": "cursorDown",
    "when": "textInputFocus"
}

However, when I switch back, I've got to reset these bindings to the defaults (along with all of the other keyboard-specific shortcuts I've defined).  This would be far easier if I could just select from a pre-existing keybinding config from within the editor.

I don't know if this is the correct place , but with the latest update of vs code my custom key bindings for emmet wrapping is not working anymore. any solutions ? my vs code details:
Version 1.23.0
Commit 7c7da59c2333a1306c41e6e7b68d7f0caa7b3d45
Date 2018-05-03T16:44:55.614Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
[     { "key": "ctrl+shift+g", "command":"editor.emmet.action.wrapWithAbbreviation", "when": "editorTextFocus && !editorReadonly" } ]

@shamseerahammedm Please file a separate issue for your problem. It is not recommended to diverge and track multiple problems in one issue. Sorry for that.


Assign a DOI to each visualization repo release

The visualization repos viz-staging, viz-raster, and viz-workflow have a couple releases each. A DOI should be assigned to each release, and the README of each repo should be updated to have a formal citation and resemble the metacatui README.

Thanks, @julietcohen -- proposed title edits below.
Suggested citations for each release, categorized by repo, are as follows. The specific DOI will need to be inserted at the end of each citation, once it is created.
viz-staging
viz-staging releases
Robyn Thiessen-Bock, Juliet Cohen, Matt Jones, Kastan Day, Lauren Walker. 2023. Viz-staging: vector data tiling for geospatial visualization (version 0.9.0). Arctic Data Center. doi: 10.18739/______

Robyn Thiessen-Bock, Juliet Cohen, Matt Jones, Kastan Day, Lauren Walker. 2023. Viz-staging: vector data tiling for geospatial visualization (version 0.9.1). Arctic Data Center. doi: 10.18739/______
viz-raster
viz-raster releases
Robyn Thiessen-Bock, Juliet Cohen, Matt Jones, Lauren Walker. 2023. Viz-raster: raster data processing for geospatial visualization (version 0.9.0). Arctic Data Center. doi: 10.18739/______

Robyn Thiessen-Bock, Juliet Cohen, Matt Jones, Lauren Walker. 2023. Viz-raster: raster data processing for geospatial visualization (version 0.9.1). Arctic Data Center. doi: 10.18739/______
viz-workflow
viz-workflow releases
Robyn Thiessen-Bock, Juliet Cohen, Matt Jones, Kastan Day, Lauren Walker. 2023. Viz-workflow: the Permafrost Discovery Gateway geospatial data visualization workflow (version 0.9.0). Arctic Data Center. doi: 10.18739/______

Robyn Thiessen-Bock, Juliet Cohen, Matt Jones, Kastan Day, Lauren Walker. 2023. Viz-workflow: the Permafrost Discovery Gateway geospatial data visualization workflow (version 0.9.1). Arctic Data Center. doi: 10.18739/______
orcids
Robyn Thiessen-Bock: 0000-0002-1615-3963
Juliet Cohen: 0000-0001-8217-4028
Matt Jones: 0000-0003-0077-4738
Kastan Day: 0000-0002-1989-3406
Lauren Walker: 0000-0003-2192-431X

DONE.

Object Title
Object Creator
Identifier
ID Owner
ID Date Created
ID Date Last Modified
ID Status

Viz-raster: raster data processing for geospatial visualization (version 0.9.1)
Robyn Thiessen-Bock ; Juliet Cohen ; Matthew B. Jones ; Lauren Walker
doi:10.18739/A27W67732
sb-nceas
2024-02-01 02:48:10 UTC
2024-02-01 02:49:43 UTC
public

Viz-raster: raster data processing for geospatial visualization (version 0.9.0)
Robyn Thiessen-Bock ; Juliet Cohen ; Matthew B. Jones ; Lauren Walker
doi:10.18739/A2CN6Z17T
sb-nceas
2024-02-01 02:41:12 UTC
2024-02-01 02:43:28 UTC
public

Viz-workflow: the Permafrost Discovery Gateway geospatial data visualization workflow (version 0.9.1)
Robyn Thiessen-Bock ; Juliet Cohen ; Matthew B. Jones ; Kastan Day ; Lauren Walker
doi:10.18739/A2HD7NV2N
sb-nceas
2024-02-01 02:26:31 UTC
2024-02-01 02:35:36 UTC
public

Viz-workflow: the Permafrost Discovery Gateway geospatial data visualization workflow (version 0.9.0)
Robyn Thiessen-Bock ; Juliet Cohen ; Matthew B. Jones ; Kastan Day ; Lauren Walker
doi:10.18739/A2N58CN59
sb-nceas
2024-02-01 02:15:21 UTC
2024-02-01 02:33:15 UTC
public

Viz-staging: vector data tiling for geospatial visualization (version 0.9.1)
Robyn Thiessen-Bock ; Juliet Cohen ; Matthew B. Jones ; Kastan Day ; Lauren Walker
doi:10.18739/A2RV0D26C
sb-nceas
2024-02-01 01:46:25 UTC
2024-02-01 02:34:21 UTC
public

Viz-staging: vector data tiling for geospatial visualization (version 0.9.0)
Robyn Thiessen-Bock ; Juliet Cohen ; Matthew B. Jones ; Kastan Day ; Lauren Walker
doi:10.18739/A2WM13V9M
sb-nceas
2024-02-01 01:04:03 UTC
2024-02-01 01:06:09 UTC
public

Thank you, Matt! Very much appreciated. I will go ahead and update the README's for each repo.

In addition to updating the README's for each of the repos, we also need to add a CONTRIBUTING.md doc to each repo so the Google fellows and new employees in the future can seamlessly onboard.

[ ] viz-staging README
[ ] viz-raster README
[ ] viz-workflow README
[ ] viz-staging CONTRIBUTING
[ ] viz-raster CONTRIBUTING
[ ] viz-workflow CONTRIBUTING

I added CONTRIBUTING.md for viz-raster and viz-staging to the develop branch of each, which should make a good template and starting point for any others.

The existing releases have all been assigned a DOI, and all 3 repos now have an updated README and CONTRIBUTING document merged into the develop branch.
This issue may be re-opened if we need to assign DOI's to future releases and discuss aspects of them.


[REVIEW] Artsly (BIG WIP 🚧 )

Project link
https://github.com/Artsly/Artsly
A random prompt generator made with Python, using streamlit, the hosted one is up for now but when heroku goes to the no free hosts the I’ll be moving it (idk where to tho XD)

Maybe add a screenshot of the app


Clear filters apply again previous filters

steps:

navigate to #/search path
open Filters panel
select a filter (filter is automatically applied)
click on Clear filters inside the filter panel (filter are cleared)
click again on Clear filters inside the filter panel

expected result:

filters are still cleared

current result:

previous filter is applied again

https://user-images.githubusercontent.com/19175505/123793961-9e00e780-d8e2-11eb-93af-1e3f13bd072d.mp4

solved in https://github.com/GeoNode/geonode-mapstore-client/pull/337


On software version updates, the settings are erased

Bug Report
App Version: 2.0.2 (and during the update to every previous version)
Platform: Linux and Windows
Installation Method: GitHub Release
Bug Description:
Settings (like "Append creation date...") always get erased when an update is performed. It'd be nice not to have to worry about updates erasing these settings.
It might not have been a priority before, but having a settings migration procedure would be awesome now that there are v2 "stable" releases.
Steps to Reproduce:

Change a setting.
Update.
See that the settings are erased.

Expected Behavior:
Settings not be reset to default.
Actual Behavior:
Settings get reset to default.
Additional Information:
Happens cross-platfrom and on every version update.

With 2.0.1 the migration has been implemented. I just double checked it by downloading 2.0.1 from GitHub, starting and configuring it and then doing the update to 2.0.2. The update is done by just deleting 2.0.1 and downloading 2.0.2. All settings persisted on my end (macOS).
Happens cross-platfrom and on every version update.
Can you please provide more details on how you update. What versions you use and so forth.

Hmm this upgrade was from 2.0.0 to 2.0.2. Do you expect it would've upgraded well? Perhaps I won't have the issue next upgrade.

mmhh, I also tried the jump from 2.0.0 to 2.0.2 just now and it upgraded without loosing the settings.

Hmm, was on Linux Mint, installed via the .deb I believe.
Perhaps we can leave it for now, and I'll provide a better repro if it happens again.
Feel free to close the issue if you'd prefer, and I can re-open one next time. I'm not certain I didn't imagine it happening.

Just upgraded from 2.0.2 to 2.0.3, and did not have this issue. Sorry for the false alarm!

Sorry for the false alarm!

No worries :)


Doesn't work with Node 5.x.

There error is:
TypeError: this.options.ci.includes is not a function
    at writing (/usr/local/lib/node_modules/generator-fountain-webapp/node_modules/generator-fountain-gulp/generators/ci/index.js:8:25)
```

This is probably due to: See https://github.com/nodejs/node/issues/5715 indicating that the `includes` is currently hidden behind a harmony flag

You use a outdated Node v5 IMO

Can you paste your .yo-rc.json ?
And execute in your shell
node -e "var os=require('os');console.log('Node.js ' + process.version + '\n' + os.platform() + ' ' + os.release())"
yo --version
npm --version

Updated node to latest 6.x and it works now. Thanks! I suppose I didn't bother updating node since the instructions indicate that at least 4.x is required (I was on 5.7.1).

Yes, it's an issue, includes is not compatible with Node 4+

We can just close this issue and make a note in the docs on the node version requirement.

Same situation, I use node 4.4.7 and npm 3.10.5
j:\Projects\Elartix\fwapp\p2>yo fountain-angular1
? Which module management do you want? None with Bower and script injection
? Which JS preprocessor do you want? Pure old JavaScript
? Which CSS preprocessor do you want? Less
? Which Continuous Integration platform do you want? (Press <space> to select)
? Do you want a sample app? A working landing page
? Would you like a router? Angular UI Router
? May fountainjs.io anonymously report usage statistics to improve the tool over time? No
events.js:141
      throw er; // Unhandled 'error' event
      ^

TypeError: this.options.ci.includes is not a function
    at writing (C:\Program Files\nodejs\node_modules\generator-fountain-angular1\node_modules\generator-fountain-gulp\generators\ci\index.js:7:25)
    at Object.<anonymous> (C:\Program Files\nodejs\node_modules\generator-fountain-angular1\node_modules\yeoman-generator\lib\base.js:431:23)
    at C:\Program Files\nodejs\node_modules\generator-fountain-angular1\node_modules\run-async\index.js:26:25
    at C:\Program Files\nodejs\node_modules\generator-fountain-angular1\node_modules\run-async\index.js:25:19
    at C:\Program Files\nodejs\node_modules\generator-fountain-angular1\node_modules\yeoman-generator\lib\base.js:432:9
    at processImmediate [as _immediateCallback] (timers.js:383:17)

j:\Projects\Elartix\fwapp\p2>node -v
v4.4.7

j:\Projects\Elartix\fwapp\p2>npm -v
3.10.5

Just released v0.7.1 who fixed your issue


Unable to run fpocket due to missing stdlibc++ libraries

I'm trying to run fpocket on Compute Canada, however when I call:
fpocket -f [pdb]
I get the error:
fpocket: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by fpocket)
fpocket: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by fpocket)
fpocket: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by fpocket)

What do I need to do here?

where did you compile fpocket?


test: add unit test for scalars

Add unit tests for the ID checks

Codecov Report

Merging #124 into master will increase coverage by 0.23%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #124      +/-   ##
============================================
+ Coverage     90.25%   90.49%   +0.23%
- Complexity      155      157       +2
============================================
  Files            47       47
  Lines           503      505       +2
  Branches        114      112       -2
============================================
+ Hits            454      457       +3
  Misses           10       10
+ Partials         39       38       -1

Impacted Files
Coverage Δ
Complexity Δ

...a/graphql/generator/extensions/kClassExtensions.kt
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...ia/graphql/generator/extensions/kTypeExtensions.kt
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...pedia/graphql/generator/types/ScalarTypeBuilder.kt
100% <100%> (+4.76%)
6 <3> (+2)
:arrow_up:

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 5e9418a...040d693. Read the comment docs.


Don't emit StorageImageReadWithoutFormat

The only image read operation performed is OpImageSampleExplicitLod,
so there is no need to declare the StorageImageReadWithoutFormat
capability.
Fixes https://github.com/google/clspv/issues/5

I couldn't work out from the issue - but in theory would we need this again in future if we tried to implement all the OpenCL image builtins?

Yes, if we end up emitting an OpImageRead instruction.  But it should be conditional on the finer-grain test if that specific operation is used.
I haven't reviewed the full list of OpenCL image builtins to know.

Ok cool! Ship it 👍

Thanks for the review.
Passes on Release and Debug builds.

Pushed into master as https://github.com/google/clspv/commit/565571c385801d97f1c68a59ff6d0c58f61eaa50


Make sure error is logged in sync permissions issue

https://github.com/CartoDB/cartodb/blob/master/services/importer/lib/importer/runner.rb#L196

Added https://github.com/CartoDB/cartodb/blob/master/services/importer/lib/importer/runner.rb#L207-L211


Provide a caching GitHubAPI mixin

Using ETag and Last-Modified, a mixin which overrides abc.GitHubAPI._request() could pass in the appropriate headers and catch a 304 status code to return a cached result. This should only be used on GET with no body.

To manage the cache, it could either be total number of bytes or total number of entries. Using an OrderedDict might be the easiest way to balance ejecting older entries by moving accessed keys to the front. That way fast access is still the priority while keeping some priority order on values exists (and since this is I/O, that reordering of keys shouldn't be expensive in the grand scheme of things).

You might consider depending on cachetools for this.

https://pypi.org/project/cachetools/

Some open questions:

Least recently used or least frequently used? (Gut says LRU due to data changes being more of a thing than frequency of the call.)
Since a page of PRs is 500K but a single PR is 24K, should there be a cap on the size of what gets cached knowing that e.g. a page of PRs will more than likely be stale sooner than a single PR? (Seems like a per-server thing, e.g. a 10 MB cache could get blown out by a daily cron job going through all open PRs, but at 200 MB you just don't care.)
Only cache JSON data/urlencoded data, or cache everything regardless of content type? (Leaning towards not caring.)
What should the default cache size be (if there even should be a default cache)? (Leaning towards no default since it's so server-specific.)
Accept a cache: MutableMapping argument to GitHubAPI or simplify things for people and just have them specify cache_size: int and otherwise bake in the cache strategy? One perk to the cache idea is a default cache can be provided which would then span GitHubAPI instances which would increase the caching impact. (Leaning towards a cache: Optional[MutableMapping] for flexibility.)

(1) LRU I think for the reasons you said.
(2) Configurable maybe?
(3) I'd cache everything, ideally you can layer this on at the HTTP level IMO, doing something like the cachecontrol library does for requests. Ideally even caching Etag and Last-Modified requests to do conditional GETs (which will revalidate stale data, and don't count against API limits IIRC).
(4) I'd say no default.
(5) A Cache implementation seems like a good idea rather than a cache_size thing.

@dstufft about (3), I would expect to cache every GET request with no body in GitHubAPI._make_request() and send the appropriate If-None-Match and If-Modified-Since headers down through GitHubAPI._request() and catch the 304 response (as well as cache any results).


Incorrect metapath length validation

Description of issue or feature request:
As per TUF metapath specification, length attribute of metadata is an integer numerical value. However, the current validation states that length has to be greater than zero. So I believe this is a slight inconsistency with the specification?
There are legitimate use-cases where signed metadata is an empty file which length is 0. For example, storing git empty files results in their length being 0.
Current behavior:
Signed metadata with length 0 raises a ValueError('Length must be > 0, got 0')
Expected behavior:
Length can be 0.

Thank you. You are correct. I was referring to targetfile length. Empty files with no content can be seen as useful. They contain a name, and their existence can be an indicator of some event in git history. I agree that zero metapath-length is questionable (and not sure if useful). Although the spec refers to numerical values, I think both are seen as potentially being zero?

Got it. We're in agreement then: zero length target files are potentially useful and allowing zero length in general does not seem harmful.


IKEA tradfri motion Sensor

Hello,
I bought today the IKEA tradfri motion sensor.
Is it possible to pair it with the hue bridge, so that I can see this motion sensor via HomeKit and can create automations with it?

No.

Is it still actually?


Set up redirect from /clues/clues

Hmmm... Not sure why I was getting an error.
Previously, the link (with the exact same code!) had been redirecting /clues/clues to /clues/data/clues/{} for some inexplicable reason. But now I'm not. Perhaps there was some Datasette register_routes cache?
In any case, closing.


scroll to top when navigate to a new page

I don't know if this is a normal behaviour but when navigating around, the scroll bar is as the previous page position.

Yeah we should offer something to automatically scroll at the top (smoothly?)

I thought this should be handled automatically be react-router

Where did you see that?
I don't see why, it's an "opinionated" behavior.

I don't remember where. Anyway, this should be in LayoutContainer right? user can remove it easily

We sould provide this options:

direct scroll at top (true)
smooth scroll at top (integer, ms)
no scroll (false)
custom callback (fn)

Changed status.

This is actually very easy to do. There is a packages desinged for this job.
https://github.com/taion/scroll-behavior/blob/master/README.md

https://github.com/ryanflorence/react-router-restore-scroll
Plan is to integrate this in react-router itself.

Here's what worked for me (thanks @thangngoc89 & @kuzvac):
import React, {Component, PropTypes} from "react";
import {Route} from "react-router";
import PhenomicPageContainer from "phenomic/lib/PageContainer";
import LayoutContainer from "../LayoutContainer";
import * as layouts from '../layouts';

class PageContainer extends Component {
    static propTypes = {
        params: PropTypes.object.isRequired,
    };

    render () {
        const {props} = this;
        return (
            <PhenomicPageContainer
                {...props}
                layouts={layouts}
            />
        );
    }

    componentWillReceiveProps (props) {
        if (props.params.splat !== this.props.params.splat && !window.location.hash) {
            window.scrollTo(0, 0);
        }
    }

    componentDidMount () {
        window.addEventListener('hashchange', this.scrollToAnchor);
        this.scrollToAnchor();
    }

    scrollToAnchor () {
        const hashParts = window.decodeURIComponent(window.location.hash).split('#');
        if (hashParts.length === 2) {
            const hash = hashParts.slice(-1)[0];
            document.querySelector(`[id="${hash}"]`).scrollIntoView();
        }
    }
}

export default (
  <Route component={LayoutContainer}>
    <Route
        path="*"
        component={PageContainer}
    />
  </Route>
);

@ben-eb Why do you need to listen to hashchange event ? Phenomic doesn't overide default behaviour.

Looks like you only need that if you are using the hash history, which Phenomic doesn't do. Nevermind, removed. 👍

So I guess that componentWillReceiveProps  code is only necessary?

@MoOx Yes :+1:

FYI https://twitter.com/MoOx/status/727595667674255360

cc @ryanflorence
As it stands right now, both scroll-behavior and react-router-scroll expose a shouldUpdateScroll callback to control specific behavior, see e.g. https://github.com/taion/react-router-scroll#custom-scroll-behavior.
They do not currently have support for scrollable divs like react-router-restore-scroll, but I think the support for actually scrolling the window in the face of adversity (i.e. browsers) is more battle-tested.
Ideally we combine everything in one library that has the best of both.

Nice solution seems to be implemented in react-boilerplate https://github.com/mxstbr/react-boilerplate/blob/229f39e3cd09a555e16da0e9d21ea4bd3a17b840/app/app.js#L66-L80
Tagging as bug, as it's pretty annoying.

I'm confused by what the check there does. If I'm reading it correctly, it seems to scroll to the top on every page transition, even when that transition is e.g. a POP. I'm not sure why that's correct.

cc @mxstbr

Uhh, I'm not sure about the terminology here, what is a POP transition?

POP = when you hit the back button or something
By default react-router-scroll should scroll you to the top of a page whenever you e.g. click on a link or something, but restore the old scroll position if pathname changes because you hit the back button.

I guess that makes sense, hadn't thought about that at all tbh! The solution we have is only in there because it's annoying when you're editing the footer and HMR kicks in and scrolls back to the top.
Would appreciate an improvement!

No, but it will prevent a jump to [0, 0]. I.e. we want to go to the top of the page when a new one is opened, but do the default stuff when that's not the case.

That's supposed to be what you get if you just do useScroll() without a custom shouldUpdateScroll at all, though, isn't it?

I don't know, you made the library! I don't remember why we put it in, if that's the case I'd love to remove those lines of code!

Okay – when you have a chance, then, could you let me know what happens if you take out that callback? I believe everything should work as you expect without it.

It does indeed, thanks @taion! Fixed in mxstbr/react-boilerplate@15006efb6079194805d0528f9b48f3579fe85ccf, works as expected.

Cool, I will implement this asap then!
Thank you both of you!

Glad to hear that. The idea was that most use cases could be satisfied by just the one-liner.
Unfortunately I've had almost no time to work on front-end lately to work on fleshing out functionality and adding this to the router, but this solution should work for now.

@taion since I implemented this, a <Link to="/"> gives errors SecurityError: The operation is insecure. @thangngoc89 is having the issue as well. Any idea?

Full error message (on Chrome)

Uncaught SecurityError: Failed to execute 'pushState' on 'History': A history state object with URL 'http:' cannot be created in a document with origin 'http://localhost:8080' and URL 'http://localhost:8080/tim-hieu-dinh-dang-mdict/'.

This is specifically a regression from the scroll thing? That's really weird – I don't do anything to affect how push/replace work.

@taion it was fixed here https://github.com/MoOx/phenomic/commit/c6a7164fd083b2f1b1561dd3fe9211556ba5fcc5

Ugh we still have bugs with trailing slash in basename? We should fix those...

That workaround shouldn't be necessary. How can I reproduce the error?

@taion thanks for looking to this.
For reproducing, you can :

Clone this https://github.com/MoOx/phenomic/commit/1e6d472eb1c00fed83f1c2e8431ad274468cf6fa

npm install
npm run docs-start

Navigate to a different page and then click on the Phenomic logo on Header bar (to return to home page)

Also posted full instruction in https://github.com/reactjs/react-router/issues/3184#issuecomment-225448418


PBFT catch up: update the current leader

This is a big issue that makes the system unusable if nodes restart.
Context
The leader rotation works in a round-robin fashion. Starting from node at index 0, each view change will assign the next node as the new leader, following a simple (i+1) mod n formula, where i is the current leader index and n the total number of nodes.
Every node maintains its local index of the current leader. A node will accept a view change only if the new proposed leader corresponds to its next expected leader. It also checks that blocks proposals come from its current leader.
Problem
This leader index i starts at 0 when a node starts, and is not updated in case a node is behind the chain and does a catch up. This is a problem, as the leader may have changed without the catching up node knowing about that. The catching up node will then have an outdated current leader index i = 0 and reject every block proposals.
Even worse, if the catching up node is node 0, this node will think that it is the leader node, and send block proposals to all other nodes.
How to reproduce
Use the scripts that are yet on the manual_tests branch:
cd test
./teststart.sh
# send a first transaction, everything fine
./testlist.sh 1 -1
# => kill node 0
# => use ctrl-B + arrows to navigate to the window
./testlist.sh 2 2
# Now node 1 is the leader, everything fine
# => restart node 0
./testlist.sh 2 3
# node 0 thinks he is the leader, he is sending proposals

Solutions
Update sync block
Update the sync block mechanism to include the current leader. This would mean that the catching up node is trusting the remote node that sends the catch up message to send the correct current leader.
Pros:

Only touches the blockcync part

Cons:

Partially solves the problem, as a bad node could send a wrong leader index

Update the blocks content
Update blocks content to include the leader. This would allow the catching up node to check who is the leader in the last block, and update its current leader accordingly.
Pros:

This is the most explicit way of solving this issue
Adds interesting information to the block

Cons:

Increases the size of blocks
Having the leader in a block is not very relevant
Feels like the simple and dirty solution

Update the consensus mechanism
Even if a node doubts about the current leader, it should be convinced to update its current leader if a threshold of nodes came to a consensus on a block. This could be done in the Finalize step, when the block is committed. This would probably require to update the PBFT state machine to store the "rejected leader" in the prepare step, but then accept it if the Finalize step succeeds.
Note that this doesn't solve the problem in case nodes are performing a view change. Therefore, nodes should store view change proposals, and accept one once it has a threshold of proposals for a same node. Right now any proposals that does not concern the next expected leader is rejected.
Pros:

Only touches the PBFT state machine
Ensures a node always has a correct leader index
Requires minimal changes

Cons:

Adds a new state to the PBFT state machine

FWIW: the cothority/byzcoin implementation used the roster stored in the block to indicate the leader: the first node in the roster list is the leader.
When a node started, even if it was the leader, it first caught up all blocks. Then it used the roster in the last block to check if its the leader or not.

Introduction
This is a more detailed explanation of the solution. I choose the last option "Update the consensus mechanism". It mainly evolves around the principle of leader skepticism. A node will reject a block proposal from an unexpected leader, but keep the right to later accept this leader if the block comes to be accepted.
Explanation
Suppose nodes A, B, C, and D, with B as the current accepted leader.

C restarts. It now assumes that A is the leader, because this the default value when a node starts
C receives a block proposal from B, but rejects it. However, it saves B as a skeptical candidate. It also saves the block ID as the tentativeRound. (in the PBFT state machine, a roundID corresponds to the current block's hash proposal)
A, C, and D will agree on committing the block, and finalize it.
Once the block finalized, C will receive a catchup message with the block. If the block hash is equal to the tentativeRound, then C accepts B as the new leader.

Limitations
A node could try to fool another node into thinking this is the leader. For that to work, the adversary node must:

Send a Prepare message to the victim, making the victim save the adversary node as the skeptical candidate
Prevent the victim from receiving the right Prepare message from the leader, but let it receive the catchup
When the victim receives the catchup message, it will save the adversarial node as its leader
Do 2) and 3) for every new block proposal, otherwise the victim will go back to the right leader

For this adversarial scenario to work, a valid catchup block is necessary. Thus, a 2f + 1 threshold of honest node must remain, which prevents any adversarial from taking the leadership position with a majority. Let's say that f nodes are victimized and convinced about a wrong leader. Convincing another node will require to make this new node not participating into the block creation, which make the total of participating node equal to 2f, which is not enough to create a new block. Therefore, not any new node can be fooled.

Hmm - after reading this, I think the Update the blocks content is still my favorite:

there is no way that any outside node can interfere with the leader proposal
it is always clear who the current leader is, even if all nodes restart

But I think I'm missing some information as to how you can have with B as the current accepted leader. How and why is B currently accepted?
This might also be a good time to go back to the papers :) In cothority/byzcoin I implemented a partial ByzcoinX protocol. Partial, because there was only 1 shard. If you look at Section V-A in the Omniledger paper, you get a short description. From what I understand, the shard policy file has all the information about who is the leader. And I suppose that this shard policy file must result from a consensus. This is why I suppose that it is a good idea to put the leader in the block.
Happy to discuss if you think it helps.

But I think I'm missing some information as to how you can have with B as the current accepted leader. How and why is B currently accepted?

Each node has an in-memory state, in which they keep track of what they think is the current leader. As such, if all nodes were to restart, they would all naturally select node 0 as the leader and things would run normally. A node will update its current leader once it receives a threshold of view change messages for its next expected leader.
In Dela, blocks are super light, which aims to make the blockchain as efficient as possible. This is why the roster is not included (but we include a "ChangeSet" of the roster, if the roster changed from the previous block). Including the roster just for the sake of knowing the leader is overkill in this case.

OK, there is a lot going on then... Do you have some documentation about these decisions? My first questions would be:

do you still use the skipchain structure?
do you need to go through all blocks then to know the current roster?
why don't you just include the ID of the current leader in the block?

Is there a possibility to implement Narwhal/Tusk? Here is a nice blog post about it:
https://decentralizedthoughts.github.io/2022-06-28-DAG-meets-BFT/
And they have a rust implementation that should show all the details.

Is there a possibility to implement Narwhal/Tusk?

Sure, you can implement your own ordering module with your favorite consensus algorithm. If you want to supervise a semester project, be our guest :) (I proposed one to implement Hotstuff, but it sadly didn't went through..)

So Narwhal/Tusk has it's own way to handle the mempool between the nodes. Also, it uses a DAG instead of linearly connected blocks.
Does that mean that you could write a mempool module, a DAG module, and a consensus module relying on these two?

Does that mean that you could write a mempool module, a DAG module, and a consensus module relying on these two?

yes! And then you add on the top the existing modules provided by Dela, such as the network overlay (mino), execution and validation (smart contract), store (db), and txn (transaction).

Sounds like a good idea for a semester-project then! If I find the time, I'll propose it to Bryan and look if there is some student who's interested in it.


[FEATURE] Testcontainers Cloud evaluation

Is your feature request related to a problem? Please describe.
Use Testcontainers Cloud
Describe the solution you'd like
Testcontainers Cloud offers a GHA and can provide more worker to improve running test in parallel and the feedback loop.
Describe alternatives you've considered
N/A
Additional context
N/A

I tried using it but it failed for ollama and localai...

any specific issue you can share about? IIRC, I used Testcontainers Cloud to run project's test with Ollama and LocalAI.

Can't find the log... But here is where I disabled it because it was not working: https://github.com/langchain4j/langchain4j/pull/507/commits/56da23709502202975300d3db926d6a42c310bf6
I see multiple runs in the dashboard, but can't find how to see logs or any details:

Account registered for<EMAIL_ADDRESS>(in case you have access)

I will try to run it again in a few days and provide more details

Hello! We did some testing on the Testcontainers Cloud side with the langchain4j test suite, and found at least one issue preventing both the local-ai and ollama modules from completing successfully consistently.
We've made some adjustments to hopefully help, and with the most recent changes I was able to run all the ITs from both of those modules against TCC -local-ai completed fine; there were some failures within the ollama integration tests, but they don't appear to be environment-specific.
I was also able to run the full suite as currently configured (with -DskipITs) against TCC without issue.
I would love to hear if your experience is any better with these changes!


Can not share URL just like the screenshots

So far my Galaxy can see my Macbook, and has a pin with 4 characters. The Neardrop icon is up the top, but the 2 options are greyed out?

When I share the browser URL from my Galaxy crome to my MacBook it crashes the same way.
It's a great tool, please improve it for an even better product!

Duplicate #3 and #16

Guys, why don't you use Chrome build in share "Send to your devices"?

@venelinn Sharing URLs is not an issue limited to Chrome, maybe I might be using a different browser or a different app needs to share any xyz text.

same error when i try to send file from android 13 to 13.4.1c m1


Events Page Out of Date

Hi Team!
I know that this isn't necessarily a place where you're looking for assistance, but I did notice that the Events page is out of date.

I'm not sure if you have more events looming and would like to update this yourself, but if not I'm happy to make a quick switch with push access. 😄

@hollenberry actually it's most DEFINITELY a place where we could use assistance! Thanks for opening this one up. :tada:


Add a new limiter for the VOS equation

Adds a conservative global limiter for volume fractions that have a physical min/max. Also fixes up and refactors the VOF/VOS code.
/cc @manuel-quezada

I think we should add the implosion tests for the VOS model.

@manuel-quezada sounds good on adding the implosion tests. See @adimako 's question about the old VOF/LS/VOS. It was my understanding that the old approach will still work and continue to be supported.


[Automation API] Pulumi deployment stuck in updating state due to typo in AWS Lambda configuration

What happened?
I'm encountering an issue where Pulumi deployments get stuck in the "updating" state when creating an AWS Lambda function. It seems a typo in the configuration is causing the problem.
Example
Reproduction Steps:
Use the following Pulumi code to create an AWS Lambda function with a typo in the S3Bucket property:
lambdaFunc, err := lambda.NewFunction(ctx, lambdaName, &lambda.FunctionArgs{
    // ... other properties
    S3Bucket: pulumi.StringPtr("example_Buckeet"), // Typo here!
    S3Key: pulumi.StringPtr("example/v0.0.1.zip"),
    // ... other properties
})

Run the Pulumi deployment command.
Observed Behavior:
The deployment gets stuck in the "updating" state indefinitely.
Expected Behavior:
The deployment should either succeed or fail with a clear error message indicating the typo in the configuration.
Troubleshooting Attempts:
It took a considerable amount of time to debug and identify the typo as the root cause.
Questions:
How can I effectively troubleshoot similar issues in future Pulumi deployments, specifically with AWS resources like Lambda functions?
What best practices can be recommended for debugging Pulumi deployments in such scenarios?
Request:
I would appreciate guidance on:
Efficient troubleshooting techniques for these types of deployment issues in Pulumi.
Best practices for debugging Pulumi deployments involving AWS resources.
Thank you for your assistance!
Output of pulumi about
CLI
Version      3.109.0
Go Version   go1.22.0
Go Compiler  gc
Plugins
NAME  VERSION
aws   6.25.0
go    unknown
Host
OS       ubuntu
Version  22.04
Arch     x86_64
This project is written in go: executable='/usr/local/go/bin/go' version='go version go1.22.1 linux/amd64'
Backend
Name         ...
URL            s3://example
User          ...
Organizations ....
Token type     personal
Dependencies:
NAME                                                 VERSION
github.com/aws/aws-lambda-go                         v1.46.0
github.com/aws/aws-sdk-go-v2                         v1.25.3
github.com/aws/aws-sdk-go-v2/config                  v1.27.7
github.com/aws/aws-sdk-go-v2/credentials             v1.17.7
github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs  v1.34.3
github.com/aws/aws-sdk-go-v2/service/kms             v1.29.2
github.com/aws/aws-sdk-go-v2/service/lambda          v1.53.2
github.com/aws/aws-sdk-go-v2/service/s3              v1.51.4
github.com/aws/aws-sdk-go-v2/service/s3control       v1.44.2
github.com/aws/aws-sdk-go-v2/service/sns             v1.29.2
github.com/aws/aws-sdk-go-v2/service/sqs             v1.31.2
github.com/aws/aws-sdk-go-v2/service/sts             v1.28.4
github.com/pulumi/pulumi-aws/sdk/v6                  v6.25.0
github.com/pulumi/pulumi/sdk/v3                      v3.109.0
github.com/sirupsen/logrus                           v1.9.3
gopkg.in/yaml.v3                                     v3.0.1
Additional context
Im using the automation api with this setup:
func PulumiSetup() {
projectName := "testtest"
stackName := "test"
cwd, err := os.Getwd()
if err != nil {
	fmt.Printf("Failed to get working directory: %v\n", err)
	panic(err)
}
opts := []auto.LocalWorkspaceOption{
	auto.Project(workspace.Project{
		Name:    tokens.PackageName(projectName),
		Runtime: workspace.NewProjectRuntimeInfo("go", nil),
		Main:    cwd,
		Backend: &workspace.ProjectBackend{
			URL: "s3://example",
		},
	}),
}

stack, err := auto.UpsertStackInlineSource(context.Background(), stackName, projectName, pulumiMain, opts...)
if err != nil {
	fmt.Printf("Error in UpsertStackInlineSource: %v\n", err)
	panic(err)
}

w := stack.Workspace()

err = w.InstallPlugin(context.Background(), "aws", "v6.25.0")
if err != nil {
	fmt.Printf("Failed to install program plugins: %v\n", err)
	panic(err)
}

stdoutStreamer := optup.ProgressStreams(os.Stdout)
res, err := stack.Up(context.Background(), stdoutStreamer)
if err != nil {
	fmt.Printf("Failed to update stack: %v\n\n", err)
	panic(err)
}

fmt.Println(res)

}
and then run: go run main.go
The deployment gets stuck in the "updating" state indefinitely.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@KaizenLol I'm not able to reproduce this issue. I've tried both using the automation api and not and I always get an immediate failure. Here is a full example program that I have tried.
package main

import (
	"context"
	"fmt"
	"os"

	"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/iam"
	"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/lambda"
	"github.com/pulumi/pulumi/sdk/v3/go/auto"
	"github.com/pulumi/pulumi/sdk/v3/go/auto/optup"
	"github.com/pulumi/pulumi/sdk/v3/go/common/tokens"
	"github.com/pulumi/pulumi/sdk/v3/go/common/workspace"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumiMain := func(ctx *pulumi.Context) error {

		assumeRolePolicy, _ := iam.GetPolicyDocument(ctx, &iam.GetPolicyDocumentArgs{
			Statements: []iam.GetPolicyDocumentStatement{
				{
					Actions:    []string{"sts:AssumeRole"},
					Principals: []iam.GetPolicyDocumentStatementPrincipal{{Type: "Service", Identifiers: []string{"lambda.amazonaws.com"}}},
				},
			},
		})
		role, _ := iam.NewRole(ctx, "myrole", &iam.RoleArgs{
			AssumeRolePolicy: pulumi.String(assumeRolePolicy.Json),
		})
		lambda.NewFunction(ctx, "mylambda", &lambda.FunctionArgs{
			Handler:  pulumi.String("index.handler"),
			Runtime:  pulumi.String("nodejs18.x"),
			Role:     role.Arn,
			S3Bucket: pulumi.String("my-bucket"),
			S3Key:    pulumi.String("my-key"),
		})
		return nil
	}
	projectName := "pulumi-go-app"
	stackName := "dev"

	cwd, err := os.Getwd()
	if err != nil {
		fmt.Printf("Failed to get working directory: %v\n", err)
		panic(err)
	}
	opts := []auto.LocalWorkspaceOption{
		auto.Project(workspace.Project{
			Name:    tokens.PackageName(projectName),
			Runtime: workspace.NewProjectRuntimeInfo("go", nil),
			Main:    cwd,
		}),
	}

	stack, err := auto.UpsertStackInlineSource(context.Background(), stackName, projectName, pulumiMain, opts...)
	if err != nil {
		fmt.Printf("Error in UpsertStackInlineSource: %v\n", err)
		panic(err)
	}

	w := stack.Workspace()

	err = w.InstallPlugin(context.Background(), "aws", "v6.25.0")
	if err != nil {
		fmt.Printf("Failed to install program plugins: %v\n", err)
		panic(err)
	}

	stdoutStreamer := optup.ProgressStreams(os.Stdout)
	res, err := stack.Up(context.Background(), stdoutStreamer)
	if err != nil {
		fmt.Printf("Failed to update stack: %v\n\n", err)
		panic(err)
	}
	fmt.Println(res)
}

@KaizenLol Will you be able to try the example above and see if it works for you? I'd love to either find a reliable repro or to close the issue if it's not relevant anymore.


when training st-gcn the loss will turn into NAN

[02.06.24|21:04:38] Training epoch: 0
[02.06.24|21:13:26] 	Iter 0 Done. | loss: 1.4058 | lr: 0.010000
[02.06.24|21:13:31] 	mean_loss: nan
[02.06.24|21:13:31] Time consumption:
[02.06.24|21:13:31] Done.
[02.06.24|21:13:31] Training epoch: 1
[02.06.24|21:13:40] 	mean_loss: nan
[02.06.24|21:13:40] Time consumption:
[02.06.24|21:13:40] Done.
[02.06.24|21:13:40] The model has been saved as D:/dataset/2024.2.6_result2/epoch2_model.pt.
[02.06.24|21:13:40] Eval epoch: 1
[02.06.24|21:13:47] 	mean_loss: nan
[02.06.24|21:13:47] 	Top1: 25.00%
[02.06.24|21:13:47] 	Top5: 100.00%
[02.06.24|21:13:47] Done.
[02.06.24|21:13:47] Training epoch: 2
[02.06.24|21:13:56] 	mean_loss: nan
[02.06.24|21:13:56] Time consumption:
[02.06.24|21:13:56] Done.
[02.06.24|21:13:56] Training epoch: 3
[02.06.24|21:14:05] 	mean_loss: nan
[02.06.24|21:14:05] Time consumption:
[02.06.24|21:14:05] Done.
[02.06.24|21:14:05] The model has been saved as D:/dataset/2024.2.6_result2/epoch4_model.pt.
[02.06.24|21:14:05] Eval epoch: 3
[02.06.24|21:14:11] 	mean_loss: nan
[02.06.24|21:14:11] 	Top1: 25.00%
[02.06.24|21:14:11] 	Top5: 100.00%
[02.06.24|21:14:11] Done.
[02.06.24|21:14:11] Training epoch: 4

why and how


Emit serialized diagnostics in JSON

Motivation
The vscode-swift extension has been parsing diagnostics from stdout. This is output as a flat list. Whereas when sourcekit-lsp sends diagnostics, it will provide nested diagnostics for related information, and suggest quick fixes. There is the serialized diagnostics emitted to -serialize-diagnostics-path, but this is written in bitstream format which would be harder to deserialize in JS/TS.
Proposed solution
It would be amazing if swift could emit a serialized JSON file that would be a lot easier for us the consume in typescript. Ideally (1) we know the nested structure of diagnostics and (2) it seems like tsc knows about the available fixits so would be great to have those
Alternatives considered
No response
Additional information
No response

@award999 ,to generate a JSON file from Swift diagnostics, I would first emit serialized diagnostics in JSON format from the Swift compiler to make it easier to consume in TypeScript, ideally containing the nested structure of diagnostics and information about available quick fixes; then use a library like swift-json-gen to generate JSON encoders and decoders based on Swift struct definitions, allowing me to parse JSON into immutable Swift structs and encode structs back to JSON; next, I would leverage the Diagnostics framework to easily share diagnostic information with users, supporting logging simple string messages, errors, and generating directory tree reports, while also providing custom insights based on the diagnostics; starting with iOS 15 and macOS 12, I would take advantage of the fact that apps that generate crash reports store the data as JSON in files with an .ips or .ips64 extension, which can be interpreted to diagnose problems; and finally, I would use the Codable protocol in Swift to load and decode specific kinds of data from JSON files, creating extensions on Bundle to load JSON files and decode them into Swift structs.
I would like to work on the issue.


Monaco Grahphql error caused by loss of this

When calling the schema loader the "this" handle gets lost resulting in TypeError: Cannot read properties of undefined (reading '_parser') To fix it you need to bind method on LanguageService.ts:93

Huh! i've never seen this bug. Can you create a codesandbox or stackblitz to re-create it?

Do you see the bug here with the latest version?
https://monaco-graphql.netlify.app/


🐛 Bug Report:  PathNotFoundException: Cannot open file, path = '/etc/lsb-release'

👟 Reproduction steps
Hello.
After update to new version (9.0.0)
After start app, got unhandled exception:
PathNotFoundException (PathNotFoundException: Cannot open file, path = '/etc/lsb-release' (OS Error: Нет такого файла или каталога, errno = 2))
Run on linux fedora 38.
I think problem with device_info_plus: 8.1.0 (maybe update will help).
👍 Expected behavior
No unhandled errors
👎 Actual Behavior
Got PathNotFoundException exception.
🎲 Appwrite version
Version 2.0.x
💻 Operating system
Linux
🧱 Your Environment
Fedora 38
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@romulka Thank you for reporting the problem. Will look into it further.
Regarding the device_info_plus plugin I don't see any error report regarding this error though.
I would appreciate your confirmation, if you could simply make a new Flutter project and test both device_info_plus 8.1.0 and latest in your new project for your system, to make sure it works.

@romulka please provide further information. Also with appwrite 9.0.1 latest release we are using latest version of device_info_plus. Let us know if the issue still persist.

Hello. Sorry, i don't have enough time to check you first answer (((
I updated to 9.0.1 and everything is fine! No unexpected errors. Thanks!


[Deploy] Asana

Service
Asana
Link to your repository
https://github.com/LTKort/Asana-Franz
Additional Information
Integrates Asana into Franz

@LTKort Works perfectly, thanks a lot!


Revert "(OFBIZ-5980) Improvement: PartyRole record(s) expiration/revocation"

Reverts apache/ofbiz-framework#325

I don't even understand how this PR was created :)


Compile error with a type cast using the "as" keyword

TypeScript Version:  2.0.3
Code
This works:
context = ModelHelper.normalizeQuery<IMongoosePoseCollection>(context) as BaseModelQueryContext<IMongoosePoseCollection>;

Now I want to break down the statement between two shorter lines. This works:
context = ModelHelper.normalizeQuery<IMongoosePoseCollection>(context) as
BaseModelQueryContext<IMongoosePoseCollection>;

But this causes a compile error:
context = ModelHelper.normalizeQuery<IMongoosePoseCollection>(context)
as BaseModelQueryContext<IMongoosePoseCollection>;

error TS1005: ';' expected.
error TS1005: '(' expected.

Expected behavior:
I would like to be able to use white spaces as I wish inside a TS statement.
Actual behavior:
New line is treated differently from regular tabs or spaces. In certain cases, new line is accepted inside a statement, in other cases it is not accepted.

See comments on #11760


add servicebuilder gradle template

Sorry Andy but Jesse has already sent a template for servicebuilder here that I will be merging when he resends, thanks https://github.com/gamerson/liferay-blade-tools/pull/15

It's ok !
I was working on servicebuilder project converting so I did it by the way.

Thanks Andy, I appreciate it.
On Fri, Nov 20, 2015 at 1:18 AM, Andy Wu<EMAIL_ADDRESS>wrote:

It's ok !
I was working on servicebuilder project converting so I did it by the way.
—
Reply to this email directly or view it on GitHub
https://github.com/gamerson/liferay-blade-tools/pull/14#issuecomment-158306024
.

--
Greg Amerson
Liferay Developer Tools
Liferay, Inc. www.liferay.com


Add test attempting to align adjacent sprites

Continuing discussion on discord, this is probably something we want to show/be able to do. Currently not so easily possibly due to FP error and inability to perform alignement / snapping to screen pixels.
Current test scene looks like this, but I think we can do better:

Closing in favour of issue


Translate "Working with Database" guide to Bahasa Indonesia

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues

Merged. Thanks!

You're welcome @samdark