Fix scheduled job

Purpose
Scheduled job is failing to assume a role because the script to identify the account number fails.
#!/bin/bash -eo pipefail
export ACCOUNT_ID=$(~/project/scripts/pipeline/identify_account_id.sh demo)
temp_role=$(aws sts assume-role --role-arn arn:aws:iam::$ACCOUNT_ID:role/opg-use-an-lpa-ci --role-session-name ci)
export AWS_ACCESS_KEY_ID=$(echo $temp_role | jq .Credentials.AccessKeyId | xargs)
export AWS_SECRET_ACCESS_KEY=$(echo $temp_role | jq .Credentials.SecretAccessKey | xargs)
export AWS_SESSION_TOKEN=$(echo $temp_role | jq .Credentials.SessionToken | xargs)
aws ecs update-service --cluster demo-use-an-lpa --force-new-deployment --service api --region eu-west-1
aws ecs update-service --cluster demo-use-an-lpa --force-new-deployment --service pdf --region eu-west-1
aws ecs update-service --cluster demo-use-an-lpa --force-new-deployment --service actor --region eu-west-1
aws ecs update-service --cluster demo-use-an-lpa --force-new-deployment --service viewer --region eu-west-1
/bin/bash: /home/circleci/project/scripts/pipeline/identify_account_id.sh: Permission denied
An error occurred (AccessDenied) when calling the AssumeRole operation: User: arn:aws:iam::631181914621:user/opg-use-an-lpa-ci is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam:::role/opg-use-an-lpa-ci
Exited with code exit status 255
CircleCI received exit code 255
Approach
chmod +x the script file
Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about the Refunds service
Checklist

[ ] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Redeploy job finished successfully

Coverage remained the same at 80.468% when pulling 599e8b95f1308409e7cbd49da1d6be4fbda62f3d on fix-scheduled-job into df0d68c4dd3599c7b8dbed030f115d2f0bcfad74 on master.

Today's scheduled update has been run


How to train on NWPU-Crowd dataset? Can you provide data preprocessing script? thank you

How to train on NWPU-Crowd dataset? Can you provide data preprocessing script? thank you

Check their other repo called CLTR


80 and/or 443?

Which one of these two quotes is correct? Is only 443 required, or both 80 and 443?
"To obtain updates from Microsoft Update, the WSUS server uses port 443 for HTTPS protocol."
"Although the connection between Microsoft Update and WSUS requires ports 80 and 443 to be open, you can configure multiple WSUS servers to synchronize with a custom port."

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

ID: 85eb6a21-2659-019a-71ab-66f2e3a7f474
Version Independent ID: ee2ab576-3c19-15a5-8c41-29a00275614b
Content: Step 2 - Configure WSUS
Content Source: WindowsServerDocs/administration/windows-server-update-services/deploy/2-configure-wsus.md
Product: windows-server
Technology: manage-wsus
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Thanks for the feedback. This has been clarified that it's both port 80 and 443. The change should be visible later today.
#please-close


Validation: forbid __schema outside of the root type

According to @IvanGoncharov , __schema should not be used outside of the root type: https://github.com/apollographql/router/pull/5255#discussion_r1699109946
Do we check this somewhere?

In a typical schema, non-root types don’t have a __schema field so converting AST to an ExecutableDocument would fail with a BuildError::UndefinedField. In code, meta-fields like __schema are not present in the Rust struct ObjecType.fields but are returned if you instead call schema.type_field(type_name, field_name).
Defining a schema like type Something { __schema: Int } is disallowed per spec but we don’t yet implement that validation rule: https://github.com/apollographql/apollo-rs/issues/743

Closing as duplicate of https://github.com/apollographql/apollo-rs/issues/743


Update README.md

i would like to update the readme file section of virtual environment for Linux/MAC users.
can you assign it to me. i am a gssoc participant

Yess, @avishmehta68710 you can go with this but make sure you don't make any changes for the windows section.
Thank you


[nstool] Release 1.7.0 fails to run on ubuntu 20.04

The latest release will not run on unbutu 20.04 receive errors:
cclansman@plexServer:~/repos/zelda3/platform/switch$ unzip nstool-v1.7.0-ubuntu_x86_64.zip
Archive:  nstool-v1.7.0-ubuntu_x86_64.zip
  inflating: nstool
cclansman@plexServer:~/repos/zelda3/platform/switch$ chmod +x nstool
cclansman@plexServer:~/repos/zelda3/platform/switch$ ./nstool
./nstool: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./nstool)
./nstool: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./nstool)
./nstool: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./nstool)

Version 1.6.6 is working fine

Seems like you should update your ubuntu, or build NSTool locally.
Some searching shows this is an issue with your environment.
https://askubuntu.com/questions/1345342/how-to-install-glibc-2-32-when-i-already-have-glibc2-31


Comment thumbnails

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Adds comment thumbnails
Issue Number: #3107
What is the current behavior?
No thumbnails on comments
What is the new behavior?
Thumbnails on comments & ChannelThumbnail allows for default, anonymous thumbnails now if nothing is passed in.
Other information

@osilkin98 Have you noticed any slowness issues with resolving a lot of channels when a file has a lot of comments?
Could you try batching all the resolves to see how that affects things? You could call resolve from CommentList and pass all the uris to that.

Currently, the styling is as it should be for the most part. It appears that the length of the comment list will cause slowdown issues by FilePage re-rendering on scroll. The two possible solutions it seems are to either implement FilePage.shouldComponentUpdate, or by converting either FilePage or CommentList into inheriting from PureComponent

Another solution could be to virtualize the comment using react-window or a similar library.

Sorry I missed your comment @osilkin98
What component is causing that?

The CollapseableText component seems to be redrawing itself frequently,
though I don't know if that's the sole cause.
On Mon, Nov 25, 2019 at 12:48 PM Sean Yesmunt<EMAIL_ADDRESS>wrote:

Sorry I missed your comment @osilkin98 https://github.com/osilkin98
What component is causing that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-desktop/pull/3108?email_source=notifications&email_token=AEAH2RYVF23TVXSVZORWQIDQVQFWFA5CNFSM4JD45IH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFDHN4Q#issuecomment-558266098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAH2R33IASKXCPW66LFNB3QVQFWFANCNFSM4JD45IHQ
.


Notify is broken

The example code for notify does not work in the latest version. I have as of now not been successful in figuring out why it fails.
code:
from pprint import pprint
from bitshares.notify import Notify
from bitshares.market import Market
from bitshares import BitShares

notify = Notify(
    markets=["TEST:GOLD"],
    accounts=["xeroc"],
    on_market=print,
    on_account=print,
    on_block=print,
    on_tx=print,
)
notify.listen()

error message:
File "\site-packages\bitshares\notify.py", line 88, in __init__
    urls=self.blockchain.rpc.urls,

File "\site-packages\events\events.py", line 58, in __getattr__
    raise EventsException("Event '%s' is not declared" % name)
events.events.EventsException: Event 'blockchain' is not declared

That was an easy fix :D


When decoration fails, show original class

Description
Thanks for the work on Draper to all the maintainers 👍
This provides a fix for #819
When decorating an object without decorator, then the last class which was checked for a decorator is contained in the error message. In case of Rails this is most often ActiveRecord::Base.
This is a bit misleading and it would be better if the class which was actually tried to decorate is shown in the error message.
This is caused by the recursive nature of the decorate method which moves up  the hierarchy when no decorator class found. And raises when it can not move further up.
Before:
Something::Bar.decorate
Draper::UninferrableDecoratorError: Could not infer a decorator for ActiveRecord::Base.

After:
Something::Bar.decorate
Draper::UninferrableDecoratorError: Could not infer a decorator for Something::Bar.

Testing
Outline steps to test your changes.

Run the specs, tests have been added

Alternatively:

on a subclass of AR, which does not have a decorator, call #decorate
Check that the name of the subclass is contained in the error message and not ActiveRecord::Base

(The fix is not restricted to AR)
References

https://github.com/drapergem/draper/issues/819

@codebycliff  sorry for messing up the rebase (thought I can easily do this while eating, watching a movie and solve some SQL stuff I'm working on. Looks like I'm not as smart as I thought ;-) ). Will clean this up when you decide to merge the recursive solution instead of the iterative solution at https://github.com/drapergem/draper/pull/823

@pascalbetz I think we'll go with the recursive solution for now. It's much simpler to read and understand. Plus, decorator_class isn't truly public API as it's not documented. I might want to re-visit the iterative solution at some point, but let's move forward with this for now. If you can clean up the commit history we can get this merged.

@codebycliff PR should be cleaner now.
Here is the iterative solution for documentation purpose:
def decorator_class
        current = self
        decorator_name_constant = nil

        while !decorator_name_constant && current do
          prefix = current.respond_to?(:model_name) ? current.model_name : current.name
          decorator_name = "#{prefix}Decorator"
          decorator_name_constant = decorator_name.safe_constantize
          if !decorator_name_constant && current.superclass.respond_to?(:decorator_class)
            current = current.superclass
          else
            current = nil
          end
        end

        if !decorator_name_constant
          raise Draper::UninferrableDecoratorError.new(self)
        end

        decorator_name_constant
end

@pascalbetz Thanks again! Sorry it took me so long to get it merged.

No problem at all. Thanks for your work on Draper. I use it in various projects.


feat: added a button to close react notifications modal

https://app.clickup.com/t/30901592/TASK-1032

Task linked: TASK-1032 Habilitar botão de "fechar todos" na popup de criação de campanha

I have read the CLA Document and I hereby sign the CLA


Transition Skills 'Performed Skills' vue-table-2 table to use bootstrap-vue table

Transition Skills 'Performed Skills' vue-table-2 table to use bootstrap-vue table
write cypress tests

PR: https://github.com/NationalSecurityAgency/skills-service/pull/290

PR: https://github.com/NationalSecurityAgency/skills-service/pull/290


feat: support callback function in eval

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary

Other information
This a draft for resolving issue #474. The API should expose to external after most of major platforms are implemented.

Callback closure in evaluate_script should be like | val: String | { ... }. We will serialized the return value from eval and pass to it the callback.
Error from the execution result will not pass to the callback closure due to varying formats returned by each platform. I think this is a minor issue, we can deal with this later.

[ ] TODO:

[x] macOS
[x] Unix
[x] Windows
[ ] Android

Issues

I think we can expose another method called evaluate_script_with_callback or something.
We can leave Android unimplemented and open an issue for it later.


Unable to increase Flea Market Standing

Versions

SPT-AKI Server version: 3.5.3
SPT-AKI Profile Editor version: 2.6.1
List of installed mods: None

Describe the bug
I am unable to increase the standing with ragfair. I can up the number but upon clicking Save Profile, it does not save, and reverts back to 0.2. This does not happen with the other traders. I have also tried this on a completely fresh profile, same issue. If you could tell me how I can manually edit it i'm happy to do so.
Additional context
SPT-AKI Profile file:
8966f3b48bb79cc5a8c2c218.zip

Manual path is "characters" - "pmc" - "RagfairInfo" - "rating"

Fixed in 70ec49c


fix ALLOWED_DTYPES to include complex dtypes

This adds support to handle complex dtypes for complex64 complex128

What is the use case for this? Basically none of the Keras APIs support complex dtypes.

@fchollet Thanks for your question! In my Ph.D. research on Physics-informed Machine Learning, I integrate complex coherence equations from InSAR with trainable layers to predict certain physical model assumptions. Complex dtype support is essential for accurately processing this complex coherence data within the machine learning framework. If you have any more questions or suggestions, feel free to ask. Your feedback is valuable!
Here is a simple graph of the model:

My main concern here is that virtually all Keras ops have no support for complex dtypes, so you can't do much with them. Instead, if you try to use them, they will get casted to float, which is not what the user expects and can lead to silent bugs.

Complex dtype support is essential for accurately processing this complex coherence data within the machine learning framework.

Could you simply pass around the real and imaginary parts of your complex tensor as two separate tensors? Your layers would take two inputs, e.g. instead of def call(self, inputs) you'd have def call(self, real, imaginary).

Thank you for sharing your concerns! I've taken them into account by adding support for complex data types in Keras operations and ensuring that corresponding test cases are included.
Regarding your suggestion, I've actually implemented a workaround similar to what you proposed, and it seems to be working alright. However, I believe incorporating direct support for complex data types in Keras would provide a more solid foundation for users who might need it in the future. Appreciate your input!

Regarding your suggestion, I've actually implemented a workaround similar to what you proposed, and it seems to be working alright. However, I believe incorporating direct support for complex data types in Keras would provide a more solid foundation for users who might need it in the future. Appreciate your input!

Adding true complex dtype support in Keras would be a large project -- we'd have to make sure that all relevant ops support these new dtypes. Until that's possible, we believe it would be better to leave these dtypes as unsupported. Adding these dtypes creates expectations that the framework cannot fulfill.


improve draining

After reviewing suggestions and emails for http2 graceful shutdown from @jpeach @mlibbey @maskit @masaori335 , I find some action items to improve drain functionalities even after we got https://github.com/apache/trafficserver/pull/2106 and https://github.com/maskit/trafficserver/pull/1.

Draining traffic without restarting or stopping.
Recovery from draining state.

Any ideas about how to achieve these?
P.S. I notice that sometimes we need to wait for max time or metrics going down thresholds then perform the actions. If we can implement different actions in some uniform style, that would be great.

If this is still an issue please reopen.


Grammatical correction.

we need a migration when we rename skills so I did this manually. Thanks!


resource not found

hello, can you tell me where can I find the 'universal_robot_databag'? Thank you for your help.

I have used rospackage databag  to record the data for test. I will fig this bug in launch file.

OK. I have fixed it and I hope you can git clone it again and build it.

OK, I get it, thanks a lot !


glue-viz

oh dear, I would really love to have a custom data reader for glue-viz.
(btw: somewhat already coupled to yt)

Uh, just works like a charm on HDF5 data sets out of the box :)
What we need now are more plugins, e.g. the histogram is only on spectral intensities if working on a (pre-binned) phase space.


minor

👷 Deploy Preview for crpp-ai-oncology processing.

Name
Link

🔨 Latest commit
b26c5f034a375d24de11450e16a82db2e7cb26d6

🔍 Latest deploy log
https://app.netlify.com/sites/crpp-ai-oncology/deploys/636a7a4187e3290009ffb7d5


Navbar li fixed and buttons aligned properly!

Related Issue

Issue No. #

Changes you made :

Navbar list items positioning fixed.

Describe the changes :

Else hover gonna break your whole page during responsiveness.
Check list :

[x] I have followed code style of this project.
[x] I have read the CONTRIBUTING document.
[x] All the aspects mentioned in the issue are covered.
[x] The website is properly working after my changes.
[x] 🌟 ed the repo

Type of change :

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Output Screenshots :

@Arun9739

@Zack-Dx Thank you for your pull request
But you need to create an issue first in order to make pull request
Please follow the contributing guidelines
Show your love by starring the repo 🌟

@Zack-Dx Thank you for your pull request
But you need to create an issue first in order to make pull request
Please follow the contributing guidelines
Show your love by starring the repo 🌟


Permission problem with using Jammy builder

Expected Behavior

We can run the container without permission trouble in case using React APP (npm start for development).
As a successful example, I will show the case of using bionic based builder.
$ pack build test-bionic --builder paketobuildpacks/builder:base
(snip..)
Successfully built image test-bionic

$ docker run -p 3000:3000 test-bionic:latest
(snip..)
Starting the development server...
(snip..)
Compiled successfully!
(snip..)
webpack compiled successfully
Compiling...
Compiled successfully!
webpack compiled successfully

Current Behavior

Failed to run the container with permission trouble when using Jammy based builder.
$ pack build test-jammy --builder paketobuildpacks/builder-jammy-base
(snip..)
Successfully built image test-jammy

$ docker run -p 3000:3000 test-jammy:latest
(snip..)
Starting the development server...
(snip..)
Failed to compile.

[eslint] EACCES: permission denied, open '/workspace/node_modules/.cache/.eslintcache'
ERROR in [eslint] EACCES: permission denied, open '/workspace/node_modules/.cache/.eslintcache'

webpack compiled with 1 error

I guess #278 may be related.
Possible Solution

I will probably go back to bionic based builder for a while for React development.
However, bionic is not good for a security perspective. So I hope this issue will be fixed.
Steps to Reproduce

Prepare react app

$ npx create-react-app my-app
(snip..)
Happy hacking!
$ cd my-app
$ ls -a
.                 .git              README.md         package-lock.json public
..                .gitignore        node_modules      package.json      src

Just try Expected (or Current) Behavior

Motivations

I think it's a very basic scenario when we develop React App.
If we can't do it, we need to go back dockerfile.

Additional Note
The directory structure of the container at build time is created with uid1001, but the actual user is cnb(uid1002), which seems to cause problems when creating new files or directories such as .eslintcache after startup.
$ docker exec -it 9c925c0c6253 bash
cnb@9c925c0c6253:/workspace$ id
uid=1002(cnb) gid=1000(cnb) groups=1000(cnb)
cnb@9c925c0c6253:/workspace$ ls -al
total 732
drwxrwxrwx 6 1001 cnb    4096 Jan  1  1980 .
drwxr-xr-x 1 root root   4096 Oct 24 15:51 ..
-rw-r--r-- 1 1001 cnb      27 Jan  1  1980 .env
drwxr-xr-x 7 1001 cnb    4096 Jan  1  1980 .git
-rw-r--r-- 1 1001 cnb    2230 Jan  1  1980 .gitignore
-rw-r--r-- 1 1001 cnb    3359 Jan  1  1980 README.md
drwxr-xr-x 3 1001 cnb    4096 Jan  1  1980 build
lrwxrwxrwx 1 1001 cnb      69 Jan  1  1980 node_modules -> /tmp/4d6b8328f31f0ade280f708051b532cf52e67649547d1c558ce7df2ecb94a806
-rw-r--r-- 1 1001 cnb  698792 Jan  1  1980 package-lock.json
-rw-r--r-- 1 1001 cnb     821 Jan  1  1980 package.json
drwxr-xr-x 2 1001 cnb    4096 Jan  1  1980 public
drwxr-xr-x 2 1001 cnb    4096 Jan  1  1980 src
-rw-r--r-- 1 1001 cnb     130 Jan  1  1980 start.sh

@hirosat Thanks for the for the perfect steps to reproduce :)
For bionic, the build und the run user were the same (uid 1000). This changed with jammy and the build (uid 1001) and the run user (uid 1002) are different. Unfortunately, no writable .cache folder exists, so when eslint tries to create it, it fails due to permission.
workaround: You could run the container with the build user, e.g. docker run -u 1001 -p 3000:3000 test-jammy:latest
possible solution: It sounds to me as if a .cache folder should already exist and it should be writable for the group cnb. I will look into this.

@c0d1ngm0nk3y  Thank you for your reply!
Your explanation was very helpful.
However, if the expected run user is cnb (uid 1002), is it possible to change the directory's owner to the last step of the builder process, like the following?:
$ chown -R 1002 /workspace

@hirosat Having the whole workspace writable for the run user would somehow be against the original idea of using different users for build and run in the first place.
Although, the same problem should occur when using a r/o root file system. The question is WHY eslint needs to run at runtime and not only at buildtime. Is it not "only" a linter?
Another question, you can help me with. How/when did you decide to change from bionic to jammy. Because I think the usage of bionic is quite hidden and we could/should help there.

@c0d1ngm0nk3y

Having the whole workspace writable for the run user would somehow be against the original idea of using different users for build and run in the first place.

I think the actual problem is that the runuser is not an expected user ID.
I suggested chown than chmod because where it is writable is not a current issue.

Although, the same problem should occur when using a r/o root file system. The question is WHY eslint needs to run at runtime and not only at buildtime. Is it not "only" a linter?

Usecases for react:
For development, it is likely to use npm start on the local environment to start the Webpack Dev Server and enable real-time debugging. The eslint is used in this case, and a cache is written to re-test based on changes in the source code.
For production, it is likely to use npm build to render static files and copy these files to a web server, such as apache or nginx.
Why:
To share a prototype frontend code with others, it is preferable to be able to build by using a development way, rather than preparing such a web server.
Essentially, eslint is unnecessary in such cases, but it is a pain to consider a workaround for it.
BTW, I'm not sure "only" a linter is need writeble.

Another question, you can help me with. How/when did you decide to change from bionic to jammy. Because I think the usage of bionic is quite hidden and we could/should help there.

I was decided by using pack builder suggest.
Previously bionic(paketobuildpacks/builder:base) was suggested and a few months ago it was changed to jammy.

Thanks for the explanation.

Having the whole workspace writable for the run user would somehow be against the original idea of using different users for build and run in the first place.

I think the actual problem is that the runuser is not an expected user ID. I suggested chown than chmod because where it is writable is not a current issue.

Actually i do think that the run user has the expected user id and the node_modules do not have the permissions to be changed by the run user (only by build user).
The permissions of these symlinks in between might be confusing.
cnb@6242c05f0a37:/workspace$ id
uid=1002(cnb) gid=1000(cnb) groups=1000(cnb)
cnb@6242c05f0a37:/workspace$ ls -la node_modules
lrwxrwxrwx 1 1001 cnb 69 Jan  1  1980 node_modules -> /tmp/4d6b8328f31f0ade280f708051b532cf52e67649547d1c558ce7df2ecb94a806
cnb@6242c05f0a37:/workspace$ ls -la /tmp/4d6b8328f31f0ade280f708051b532cf52e67649547d1c558ce7df2ecb94a806
lrwxrwxrwx 1 cnb cnb 65 Oct 31 08:31 /tmp/4d6b8328f31f0ade280f708051b532cf52e67649547d1c558ce7df2ecb94a806 -> /layers/paketo-buildpacks_npm-install/launch-modules/node_modules
cnb@6242c05f0a37:/workspace$ ls -la /layers/paketo-buildpacks_npm-install/launch-modules
total 52
drwxr-xr-x   5 1001 cnb  4096 Jan  1  1980 .
drwxr-xr-x   3 1001 cnb  4096 Jan  1  1980 ..
drwxr-xr-x   2 1001 cnb  4096 Jan  1  1980 env.launch
drwxr-xr-x   2 1001 cnb  4096 Jan  1  1980 exec.d
drwxr-xr-x 854 1001 cnb 36864 Jan  1  1980 node_modules

Although, the same problem should occur when using a r/o root file system. The question is WHY eslint needs to run at runtime and not only at buildtime. Is it not "only" a linter?

Usecases for react: For development, it is likely to use npm start on the local environment to start the Webpack Dev Server and enable real-time debugging. The eslint is used in this case, and a cache is written to re-test based on changes in the source code. For production, it is likely to use npm build to render static files and copy these files to a web server, such as apache or nginx.
Why: To share a prototype frontend code with others, it is preferable to be able to build by using a development way, rather than preparing such a web server. Essentially, eslint is unnecessary in such cases, but it is a pain to consider a workaround for it. BTW, I'm not sure "only" a linter is need writeble.

Thanks for the explanation. Yes, I agree that this seems not to be specific to eslint. I was just wondering why a linter comes up in this.

Another question, you can help me with. How/when did you decide to change from bionic to jammy. Because I think the usage of bionic is quite hidden and we could/should help there.

I was decided by using pack builder suggest. Previously bionic(paketobuildpacks/builder:base) was suggested and a few months ago it was changed to jammy.

Thanks.

Maybe I was mistaken.
So you are intentionally making node_modules read-only and intentionally mounting them as a different user?
In general, I thought that node_modules is an area that can be managed by the user(cnb), so what is the reason for making it read-only like that?

Got it.
The idea of splitting the run and build user is originated here.
@paketo-buildpacks/nodejs-maintainers Having a group writable node_module folder doesn't sound right to me. Why should the run user want/need to change it. It is an image after all. WDYT?
But the node_nodules/.cache folder is a bit different and seems to be standard to be used. Any concerns in making is group writable?
I guess this use case will just not work with a readonly root filesystem, but I don't see a chance.

Now I understood the background. Thank you for your kindly explanation.
Yes. I would be happy if you could make the group writable for all configurations under the node_nodules/.cache directory, at least in this case.
Thank you in advance.

@c0d1ngm0nk3y
Would you fix it to close this ticket?

@c0d1ngm0nk3y Any updates?

Fixed with the next release of npm-install/nodejs buildpack


fix: Content for Error fetching event (#1366)

Fixes #1366
Changes: new layout file for error on fetching event
Screenshots for the change:

Resolve conflicts

Resolve conflicts

done.

@iamareebjamal @liveHarshit what's wrong with Semantic?

@aman210697 Try adding a space after the colon in title

@liveHarshit please review

Remove snackbar message

Remove snackbar message

What happens when you click favorite or share button?

What happens when you click favorite or share button?

crash 😄

What happens when you click favorite or share button?

crash

Then solve the issue properly.

What happens when you click favorite or share button?

crash

Then solve the issue properly.

looks good?


Add improvements to full game example

Added shot and cooldown display
Rewritten stat scaling so they are more accessible for balancing
Added bullet friction
Added range stat
Adjusted difficulty
Minor UI adjustments

Thanks a ton as always! Really enhances the feel of the game and paves the way for future improvements for it.


Spidermonkey cleanup

Motivation for this change
We keep a lot of spidermonkey versions, one which wasn't used at all. The default version was also very old and was only used three places:

jsawk
plowshare
pyload

~I changed the default to ~60~ 38 which didn't break the build of the above packages, though I didn't tested them in any serious fashion~
Changed default to 38 as some dependencies require a js binary which 52 and 60 doesn't ship with (could link, but eg. fedora and arch doesn't at least).
Things done
Of note:

changed default to 38
removed 17 and then unused 31
upgraded 60.3.0 to 60.4.0 and did some cleanup
In particular I turned on --enable-optimize this made the build a bit slower, but should hopefully be worth i (it turns on -O3). Eg. fedora disabled it a long time ago due to a gcc bug which is no longer with us. I ran up a VM with gnome and tested gnome-maps which uses gjs without problems
upraded 38.2.1.rc0 to last released 38.8.0, changed from random to url to official mozilla url.

Did a nix-review:

34 package were build:
  - adapta-gtk-theme
  - arc-theme
  - buildah
  - chrome-gnome-shell
  - flatpak
  - flatpak-builder
  - gnome-builder
  - gnome3.anjuta
  - gnome3.gjs
  - gnome3.gnome-characters
  - gnome3.gnome-documents
  - gnome3.gnome-flashback
  - gnome3.gnome-maps
  - gnome3.gnome-session
  - gnome3.gnome-shell
  - gnome3.gnome-shell-extensions
  - gnome3.gnome-software
  - gnome3.gnome-sound-recorder
  - gnome3.gnome-terminal
  - gnome3.gnome-tweak-tool
  - gnome3.gnome-weather
  - gnome3.gpaste
  - gnome3.polari
  - gnome3.pomodoro
  - gnome3.sushi
  - gtkpod
  - jsawk
  - minishift
  - ostree
  - plowshare
  - pyload
  - rpm-ostree
  - skopeo
  - spidermonkey

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

The default should probably be 38 as 52 and 60 doesn't include a js binary (only eg. js60). This breaks at least jsawk. Alternatively we could add a symlink, but might be safer to just go with 38.

Could someone trigger a darwin build for spidermonkey_38? I've been putting off getting the permissions :/

@GrahamcOfBorg build spidermonkey_38


RDP Issue

Hi, i have managed to get it working on my pc. No problems with windows 2004 update.
On another pc, running Version 10.0.18363 Build 18363 - version exists in ini file - when i rdp in, the rdp session displays over the local session. So the actual local machine sees or displays the remote session. When signing out, it returns to the normal desktop. Why is this?

So, you have a running session, open and logged in on the local computer. Then when you log in from another computer, you get a new session for the remote computer, but that remote session is displayed on the local monitor - is that right? Can you both operate the computer at the same time?
And then, when you log out of the remote session, it disappears from the screen and the old local session returns?
Weird. The important thing might be the hardware. Some graphics drivers don't play nice with RDP. Could you reply with your graphics setup and graphics driver versions?

Thanks for the reply.
(So, you have a running session, open and logged in on the local computer. Then when you log in from another computer with a different user account, you get a new session for the remote computer, but that remote session is also displayed on the local monitor - is that right?) - That is correct, unfortunately i am not sure if the local pc can control the remote session as i am setting this up remotely via teamviewer - there is no user on site at the moment. You are also correct in the understanding of once you signout/disconnect the remote session, the local desktop returns , still signed in and active.
Currently this is being setup on a Microsoft Surface Pro 7, running hybrid display with Intel and Nvidia - I will try get the driver information of both, but last time i worked on the pc - a week ago, i updated both drivers too the latest version. Should i try force the laptop to use only the Intel driver as a test?

Ok - one thing I do know - Teamviewer and rdp do NOT work well together.
Teamviewer has to guess which session you really want - and it is probably
making the wrong decision.
Wait until there is someone on site before going further - it could be
working just fine. Teamviewer is just selecting the new rdp session to
connect you to, instead of sticking to the local session as you expected.
On Mon, 20 Jul 2020 at 20:45, travismailsa<EMAIL_ADDRESS>wrote:

Thanks for the reply.
(So, you have a running session, open and logged in on the local computer.
Then when you log in from another computer with a different user account,
you get a new session for the remote computer, but that remote session is
also displayed on the local monitor - is that right?) - That is correct,
unfortunately i am not sure if the local pc can control the remote session
as i am setting this up remotely via teamviewer - there is no user on site
at the moment. You are also correct in the understanding of once you
signout/disconnect the remote session, the local desktop returns , still
signed in and active.
Currently this is being setup on a Microsoft Surface Pro 7, running hybrid
display with Intel and Nvidia - I will try get the driver information of
both, but last time i worked on the pc - a week ago, i updated both drivers
too the latest version. Should i try force the laptop to use only the Intel
driver as a test?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stascorp/rdpwrap/issues/1125#issuecomment-660951828,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMCGIRNW6BWTD3A6ON5OX3R4QN4HANCNFSM4PCAZESQ
.

That makes sense, thanks it did cross my mind, but not sure if it would affect mstsc and <IP_ADDRESS>. Will see if i can get someone to assist later and will give feedback.
Thanks so much


ai-gen: Update metadata

Description
Doing some wordsmithing so the extension is easier to find in the store if searching for "GPT-3" or "DALL•E"
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@josephschmitt Love the new wording 👌
Are you still happy with the ai-gen? This applies to the directory (/extensions/ai-gen) and package.name property. Wondering if it's worth changing it to openai-generator. If so, I could handle the renaming internally, so it'll be a seamless change for users.
Let me know what you think.

@peduarte I don't really care, to be honest. It seems like that name doesn't actually show up anywhere users see. I'm fine leaving it as-is unless you feel there's a compelling reason to rename

@josephschmitt I don't mind. It just helps with discoverability within the extensions folder. Typically the folder name will be pretty much the same as the Extension name, so if someone wants to find your extension, they can easily find it.

Integrated these changes into #3471


Make voronoi component automatically infer scales and extent

At long last this PR addresses #355. It enables the voronoi component to automatically pick up the extent and scales for the current XYPlot. It also makes the API mostly conform to the rest of the react-vis style (#821). Finally, and most interestingly, I believe that this PR enables throwing voronois over non-linear scales.
It is backwards compatible with the current usage, so nothing should break!

@benshope thanks for reviewing all these prs.   I'll do that now

@mcnuttandrew bumped to 1.10.7, let me know if I should also update the docs


infinite scroll doesn't work in my demo

Framework7 Version: 2.0.7
Framework7-Vue Version: 2.0.7
Platform and Target: mac

What you did
i write my code just like demo in document,but it does not work
demo like
 <f7-page infinite @infinite="onInfiniteScroll">
   <f7-navbar title="My App"></f7-navbar>

Page content

Page content

Page content

Page content

 < /f7-page>


bosh ssh should not connect successfully when given non-existent job index

Actual Behavior:  If I have only one vm: job_z1/0 and I try to bosh ssh job_z1 99 it will successfully connect to job_z1/0.
Expected Behavior:  I would expect it to fail and yell at me for trying to ssh into vm that doesn't exist.
This can be confusing if I have jobs running across multiple AZs and accidentally increment the index instead of the AZ number.
cc @Amit-PivotalLabs

Looks like it already fixed
https://github.com/cloudfoundry/bosh/blob/master/bosh-director/spec/unit/api/instance_lookup_spec.rb#L58

Closing - thanks, @uzzz, for mentioning this. Confirmed fixed.
$ bo ssh dummy 99
Acting as user 'admin' on deployment 'dummy' on 'director'
Target deployment is 'dummy'

Setting up ssh artifacts

Director task 17
Error 70001: No instances matched {:job=>"dummy", :index=>[99], :deployment_id=>1}

Task 17 error
Failed to set up SSH: see task 17 log for details


bug: Some pin locations displays an object that each character is a new line.

Bug Definition
Some pins displays a JSON object that each characters splitted into new line.
-- Please add discord contact information
** discord username: @tinman#7219 **
## Bug environment
afetharita.com
rc.afetharita.com
Describe how you are producing the bug step by step
Sample urls;
https://afetharita.com/en?id=707631
https://rc.afetharita.com/en?id=707622
https://rc.afetharita.com/en?id=552624
https://rc.afetharita.com/en?id=552626
Expected Behaviour
Should show data, or none.
Screen shots

Desktop Information

Operating System: osx
Browser chrome

Fixed with #927


feat(cli): Added get-version feature

Added the read-only feature "get-version", that will output the latest version, if any.
Closes #222

I'm sorry, it was too late yesterday.. forgot to rerun reformat and tests once again after changing the selected name for the disable-fallback parameter.

Hey @andre161292 I am sorry but #240 has just been merged and there are now some conflicts.
Also you should adapt the get-version command so it accepts a --package flag for monorepos.

Thanks for the update. I'll update this as soon as i have some spare time :+1:

I applied all requested changes, so as soon as there's time, you can do a re-review :)

Regarding the failing codecov/patch check.. Those errors (except from one) are coming from reformattings across the codebase, that i only did, because of a previously failing lint-check at those locations. I see it as a "falsy"-positive kind of failing check.
Should i fix them too in this PR? Doesn't seem like the right place to do it, though..

You probably don't need to worry about the coverage too much, it's advisory for the most part

As soon as the conflict with main is resolved I think this is ready to be merged @andre161292 :)

Check :heavy_check_mark:

Thank you @andre161292 :)


⚠ Fetchers has degraded performance

In 1078736, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 257 ms

Resolved: Fetchers performance has improved in cccb128.


.gif support

This package is incredible. Thanks so much for putting it together.
Is there .gif support? Is that a feature that might be in the works? Is it there and I've missed it?
Thanks.

It's already there for iOS, not for Android

@cpsiaki
Well i have a "good" info. I try something with .gif on Android.
You can get animated gif if you don't resize the image and you do like folowing :
/*
 * Don't use the folowing options :
 * maxWidth - maxHeight
 * angle
 * quality
 */
var options = {
  title: 'Select Avatar',
  cancelButtonTitle: 'Cancel',
  takePhotoButtonTitle: 'Take Photo...',
  chooseFromLibraryButtonTitle: 'Choose from Library...',
  noData: false, // we use response.data to display gif
  allowsEditing: false // make sure we don't edit the gif
};

ImagePickerManager.showImagePicker(options, (response) => {
  const source = {uri: 'data:image/gif;base64,' + response.data};
});

Sorry i know it's not very mutch but animated gif on Android are in a particular Class and it's make it harder to manage


Intermittent 500 errors for some browsers, no errors in log

I have several people reporting 500 errors on our site. For some it's random and only intermittent and for others it's 100% of the time, we can't reproduce it ourselves despite trying different browsers.
The site runs PHP 7, WooCommerce and Polylang Pro. SSL is disabled.
Since we can't reproduce it, I wonder if there could be something client related, ie some cookie limit or similar that could cause this.
Also, how we make Nginx log more errors? Because right now /var/log/nginx/site.com.error.log is completely empty.

[x] lsb_release -a

No LSB modules are available.


Create Migration Script for Version 1.2

The script needs to migrate the changes made in the template attack section so that it's valid (the same) for both NPCs and player characters.

This is now finished and tested. There is a warning dialog box that tells users to back up their data before migrating, as well, just for good measure.


updated to r74

updated threejs library to r74
removed projector from demos and repo
cleaned up raycaster code in DomEvents
updated linkify to work with the new raycaster

thanks for porting it to r74 :)


Make Vmax + other useful params configurable via CAN

As of now, Vcc and Vmax are statically defined in the model. This prevents us from adapting those parameters to the setups/robots w/o re-generating the code.
It'd be thus great to have the possibility to tune the voltage values on the fly via CAN, for example to adapt for cable or battery voltage supply.
We haven't done that yet as the current CAN protocol doesn't foresee this option.
EDIT
We may consider at this stage including other motor-related useful parameters to configure via CAN. For example: the motor resistance and inductance.

Actually, it turns out that Vcc can be read by the board using ADC. This would enable us to automatically adapt wrt. a constantly changing battery voltage. Opening a dedicated issue for this.

cc @marcoaccame @sgiraz @fgarini @valegagge

Hi guys,
I just want to add a note regarding this new feature.
In AMC-BLDC, @ale-git had already implemented two motor parameters:

swapBC: it is a boolean that lets the user simulate the motor cable swap. This is useful in case of wrong cabling.
hall sensor offset

It would be great if these parameters were included in the new CAN protocol.
We are available to discuss together where to insert these parameters.
I suggest only designing the new protocol taking in mind these parameters also, but not making them work: we can do it in a different activity.

Agreed @valegagge 👍🏻
Added them up to the OP.


Cat fastq

Add a process to cat together fastq files from multiple lanes, in the same way as many other pipelines.
fastq files with the same sample metadata will be merged together.
PR checklist

[X] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/fastquorum branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nf-test test main.nf.test -profile test,docker).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@SPPearce thank-you for this, but I would really like to keep this workflow/pipeline as close as possible to the fgbio best-practices description.  I understand it is common to have a sample split across lanes, to increase coverage as well as uniformity, but again, I want to aim this pipeline at having as little extra beyond the core FASTQ->consensus calling steps.  Perhaps this philosophy needs to be stated in the README or contributed docs?

What do you expect people who have got fastq files spread across lanes to do then?
Just cat them together outside of the pipeline? That is not really a satisfactory solution, and really hampers use of the pipeline. They could be merged together as uBams instead of at fastq files.

@SPPearce I could see us having different on-ramps into the pipeline, so sure go ahead and clean up this PR and I'll review it.  I do want to enforce the boundary that this pipeline has a specific purpose, to exemplify the fgbio best-practices.  For example, I am not in favor of adding other umi-grouping or consensus tools at this time, or adding downstream variant calling.  I have seen our clients try to modify and extend other nf-core pipelines with quite a bit of difficulty, do to there being so many options and conditional paths.  This philosophy is meant to combat that.  Thank-you for taking the time to make the PR in advance.

Closing in favor of #38


libnetwork does not transfer network names to the remote plugin API

The struct CreateNetworkRequest has no notion of the network name. We use this as a means to associate a friendly network name with the network. Network IDs are really an internal state tracking thing for us.
In conversations with @mrjana I was surprised to hear there's not any intent to provide this and was hoping we could have a discussion about why.
/cc @jainvipin @mapuri @shykes

I'm happy to provide the code with a little guidance, fwiw.

fwiw, I have asked for the same here:
https://github.com/docker/libnetwork/issues/139

ok, I'll close this one and watch that one, then. Thanks!

@erikh
Please do post your thoughts on why it is a good idea to pass the name too in #139. I think with more compelling use cases, we may get this feature.


how do I view the new permission list

i try this:
cleos set account permission eoswangyilin view '{"threshold":1,"keys":  [{"key": "EOS5SL61GpNqMUJmhrPE3ueq7XG41MujPieMEhaDDCT5F2L4fhyny","weight": 1}] ,"accounts":[]}'
and how to see the  permissions 'view' contains?  i can't found how to see list.

If the above command run successfully, you will see your new permission inside cleos get account eoswangyilin

@andriantolie sorry,i lose put this:cleos set action permission eoswangyilin eosio.token transfer view
i want see view had how many action's permission?
and cleos get account eoswangyilin  only know eoswangyilin has a view permission,but don't know what action can call.

Ah, if that's what you mean, I believe there's no API to retrieve the list of linked actions. I think it will be a useful feature though.
Not exactly the proper way to get it though, but in the current code, I'm aware that if you are trying to delete the permission, it will complain and say which action is currently linked

Ah, if that's what you mean, I believe there's no API to retrieve the list of linked actions. I think it will be a useful feature though.
Not exactly the proper way to get it though, but in the current code, I'm aware that if you are trying to delete the permission, it will complain and say which action is currently linked

Great trick with deleting permission - I needed to verify that the linkauth is set correctly


gesture_overview_enable = false disables workspace swipe

Would expect this to disable only the overview gesture but it disables all 4-fingered gestures instead.

This is explained in the README.
The reason is most touchpads only have three and four finger events available (aside from the standard one or two finger gestures). For scrolling I need the two axes, but overview and workspaces only need one axis each.
It could be clearer and separate the _enable option, but that would also make it less clear that _fingers should  be the same value. I don't really want to add personalized gestures, and people choices for whether to swipe up/down or to the sides. I think the default is quite reasonable. I can add gesture_workspaces_enable, gestures_workspaces_fingers and gesture_workspaces_distance if you think that helps you, but my fear is people will start changing fingers not realizing the reason why they are shared.

The default Hyprland workspace swipe doesn't work with hyprscroller. The explanation is here.
hyprscroller has workspace windows outside of the monitor, while Hyprland doesn't. so when you swipe to change workspace, Hyprland can show a bit of the active workspace and a bit of the next in the animation, because they don't overlap. Instead, if you tried the same with hyprscroller, it would show windows that are outside of the viewport, but have the same coordinates as the ones in the next workspace (coordinate space overlaps).
So basically, workspace swipe cannot work the same way as Hyprland's, because workspaces have overlapping coordinates (they are infinite). No fancy animations, sorry.

Back to the original issue, it is simply the case that gesture_overview_enable misleads. This matters to some users (me) because I'm using fusuma to register a 4-fingered vertical swipe for brightness, and I'd like workspace swipe to keep working.

Yes, I can separate the two.

Impemented in af08f46b8706572d3e3f2e030e6687934aa66fe3


Issue getting status output from Get-AzVM in Graphical Runbook tutorial

The follow Code in the example will not work and will cause the job to fail out with with a null input type
$StatusesJson = $ActivityOutput['Get-AzVM'].StatusesText  $Statuses = ConvertFrom-Json $StatusesJson  $StatusOut =""  foreach ($Status in $Statuses){  if($Status.Code -eq "Powerstate/running"){$StatusOut = "running"}  elseif ($Status.Code -eq "Powerstate/deallocated") {$StatusOut = "stopped"}  }  $StatusOut
from my testing it appears i am not getting any output from the StatusesText from Get-AzVM, after doing some digging around if i made the code the following
$Statuses = $ActivityOutput['Get-AzVM'].Statuses $StatusOut = "" foreach ( $Status in $Statuses) { if($Status.Code -eq "Powerstate/running"){$StatusOut = "running"}  elseif ($Status.Code -eq "Powerstate/deallocated") {$StatusOut = "stopped"}  }  $StatusOut
I am getting the correct power stat from Get-AzVM

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

ID: 4799ebe4-d654-b9d2-e64f-923d025ad7cf
Version Independent ID: f6519afb-bf55-c886-e3c3-d11174da3aea
Content: Create a graphical runbook in Azure Automation
Content Source: articles/automation/learn/automation-tutorial-runbook-graphical.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@paulehr Thanks for your comment. We are actively investigating and will get back to you shortly.

Assigning to content author @MGoedtel for review

I will take a look at this as soon as I can and if the doc is incorrect, I'll create a work item and correct it.  #in-progress.

I confirmed the sample code in the article is logically incorrect and that your proposed code change is producing the expected results. I'm going to update the code in the article and get it published this week. Thank you for bringing this to our attention and sharing the PowerShell code that you invested time to develop and work around the doc issue.  #please-close


update logic for checking if there are any changes on workflow node s…

Summary
Update the logic and add a higher-level wrapper isWorkflowNodeDirty
The potential usage is as follows, create a computed property where WorkflowNode is available: in the operator-node or operator-drilldown for example:
const isDirty = computed(() => isWorkflowNodeDirty(props.node));

...

 <Button
         :disabled="!isDirty"
         label="Run something"
         size="small"
         icon="pi pi-play"
/>

Then, assuming the operator is coded to workflow guideline, this will tell you if there are any unsaved changes on the workflow-node.
Testing
Covered in unit test case
yarn run test workflow

@brittanykondo


Added DEBIAN_FRONTEND=noninteractive to sudo

By default sudo drops all environment variables and executes its commands with a clean environment. This is by design, but for the DEBIAN_FRONTEND environment variable it is not what we want, since it results in installers being interactive. This adds the env_keep instruction to /etc/sudoers to keep DEBIAN_FRONTEND with its noninteractive value, and thus pass it on to commands that care about it. Note that this makes no difference in our builds, because we are running them directly as root. However, for users of our image this is going to make a difference, since they start out as runner and have to use sudo.

@Fleshgrinder Thanks for your contribution!
Just a quick question, but how can I test this?
Should I kubectl-exec into one of my runner pods' runner containers and try running sudo apt-get install whatever and see if it skips the prompt now?
Do you have any other tools in your mind that this change might be useful for?

dpkg (the program underlying apt and apt-get) is by far the most prominent candidate for DEBIAN_FRONTEND, yes. You need to perform an installation that would usually ask questions to see the effect of it. Many users execute with --yes, which already hides various dialogs (and is dangerous). I do not remember any installation routine that kicks in with --yes and no DEBIAN_FRONTEND from the top of my head. Maybe something with locales or time zones. The one were we ran into this problem is https://github.com/ilikenwf/apt-fast, which is also used by GitHub in their VMs. You could try this one if you want.
sudo add-apt-repository ppa:apt-fast/stable
sudo apt-get update
sudo apt-get install apt-fast

That said, to see that it is working sudo env | grep -F DEBIAN_FRONTEND is already sufficient.

@Fleshgrinder Thanks a lot for your explanation! Got it. I'll test it and plan when to merge this. We have a lot of ongoing pull requests waiting for reviews now.

Meanwhile you can add
RUN sudo bash -c "echo DEBIAN_FRONTEND=noninteractive >> /etc/environment"

to set it globally (also available in sudo commands).


React Native support

Problem
A lot of projects want React Native library. We should support this.
Notes
With native modules we should be able to bind the Swift and Kotlin to a basic React Native library.
See https://reactnative.dev/docs/native-modules-intro
Acceptance criteria
Basic React Native library support.

Seems like we need an Obj C bridging header. Something like this:
Swift:
// MoproCircom+ReactNative.swift
import Foundation

extension MoproCircom {
    @objc func generateProofWithCallback(circuitInputs: [String: [String]], callback: @escaping RCTResponseSenderBlock) {
        do {
            let result = try generateProof(circuitInputs: circuitInputs)
            // Convert `GenerateProofResult` to a dictionary or array if necessary
            callback([NSNull(), result.toDictionary()])
        } catch let error {
            callback([error.localizedDescription, NSNull()])
        }
    }

    // Add similar methods for `setup` and `verifyProof`
}

Obj C:
// MoproCircomBridge.m
#import "React/RCTBridgeModule.h"

@interface RCT_EXTERN_MODULE(MoproCircom, NSObject)
RCT_EXTERN_METHOD(generateProofWithCallback:(NSDictionary *)circuitInputs callback:(RCTResponseSenderBlock)callback)
// Add similar extern declarations for `setup` and `verifyProof`
@end

JS:
import { NativeModules } from 'react-native';

const { MoproCircom } = NativeModules;

MoproCircom.generateProofWithCallback(circuitInputs, (error, result) => {
  if (error) {
    console.error(error);
  } else {
    console.log(result);
  }
});

// Add similar calls for `setup` and `verifyProof`

@oskarth I am Assigning this one to me for the moment.
I'm working on an RN library setup, that I'll push in our GitHub org once having something working. Once the specs and objc bridge specs are refined, we could add it to Mopro settings if it's wanted/needed by Mopro.
WDYT?

Sounds great!

Update:
I have a working bridge that you'll be able to find here.
It's a bit tricky but possible.

The objc swift wrapper
The objc bridge

You'll find a working example of the complex-circuit-100k circuit.

Next steps:

Clean the repo
Find ways to automatize this bridging to have a clean workflow with the CLI
Try to run it on device
Try with AA circuits

Awesome!

See https://github.com/anon-aadhaar/anon-aadhaar-react-native/commit/d6443316200cd3e1f17ad2679458cc6e6e9fe1f2 for latest React Native WIP integration

We want to take this RN WIP integration above and:

Add to mopro-cli as platform option
Integrate into example app template
Basic docs about usage

I built this example app https://github.com/zkmopro/react-native-app
Next steps:

write down documentation

how to setup from a new project
how to integrate with existing react native project

try to support snarkjs in browser
benchmark the performance
(cli to init a react native project)


DBZ-2975: Extract offset context from object states to method signatures

See DBZ-2975.
This PR complements https://github.com/debezium/debezium/pull/2283.
TODO:

[x] Run unit and integration tests locally.

Pushed one more commit to adjust to the changes I did in core. Merging now. Thx, @morozov!


0.00 shown when scanning a receipt

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
Email or phone of affected tester (no customers): @puneetlath
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1712101481245059
Action Performed:
NOTE: No idea how to reproduce this issue

Scan a receipt

Expected Result:
Report amount should be the receipts amount total
Actual Result:
the report total is showing as -$0.00
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989


WindowsACI running correctly in local without too many intergration

Having a lot all functions in WindowsACI that works the same as the MacOSACI, and can be running local test within WindowsACI by itself. Tht ipyny files are used to test in first or by person.

Hey @yuhengcai1 , what's the purpose of having the WindowsACI.py and the WindowsOSACI.py? I notice they have different functions, but it seems you tested only 1 of them in the testWindows.py file and notebook.

Hey @yuhengcai1 , is there anything more to add to the PR? Other than that, I think the clean-up + the suggestion earlier in the conversation is all that's left before merging.

I tested the functions with your provided test cases and also the actions that you didn't test. LGTM. 😄
Some minor changes:

unnecessary imports
clean up (remove test file, and notebook; they LGTM!)
"control" -> "ctrl"; not sure about this...is "control" working on your end?


vNext Task: Example script/scene for Navigation Gesture

Overview
There is no example which demonstrates 'Navigation Gesture' for HoloLens. A lot of HoloToolkit customers use Navigation gesture.
Navigation gesture is introduced as an official gesture in HoloLens:
https://docs.microsoft.com/en-us/windows/mixed-reality/holograms-211

Done?


Add AWS CLI in order to ship library artifacts from container

Issue #, if available:
#169
Description of changes:
Because we now build and ship library artifacts from Centos container, we need to manually install the AWS CLI in the container. Verified that this installation works on Centos 7.
Related to test Github action failure: https://github.com/opendistro-for-elasticsearch/k-NN/runs/951599939?check_suite_focus=true
Documentation for installing AWS CLI on linux: https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux.html
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Why do we need AWS cli?

@vamshin we need it because we use it to copy the built artifacts to S3 here. The Centos container used for building the artifacts does not come with it, like the Github Actions Ubuntu runner.


Error: event_base_loop reentrant invocation

Hello.
The following code is causing an error:
 EventBase::loop(): event_base_loop: reentrant invocation.  Only one event_base_loop can run on each event_base at once.
<?php

use React\EventLoop\Loop;
use React\Promise\Deferred;
use function React\Async\await;

require __DIR__  . '/vendor/autoload.php';

Loop::addTimer(0, function () {
	$deferred = new Deferred();
	Loop::addTimer(0, static fn() => $deferred->resolve());
	await($deferred->promise());
});

Tested on ExtEventLoop.

Which version of this package are you using?

@WyriHaximus,
react/async: dev-main (ff11a7aa9eea7104af8f05bafbc85422dac4b8ab)
react/event-loop: v1.2.0
Tested on PHP 8.1.0 and PHP 8.1.1

Here you tried:
<?php

use React\EventLoop\Loop;
use React\Promise\Deferred;
use function React\Async\async;
use function React\Async\await;

require __DIR__  . '/vendor/autoload.php';

Loop::addTimer(0, async(function () {
	$deferred = new Deferred();
	Loop::addTimer(0, static fn() => $deferred->resolve());
	await($deferred->promise());
}));

Or using https://github.com/reactphp/promise-timer#sleep
<?php

use React\EventLoop\Loop;
use React\Promise\Deferred;
use function React\Async\async;
use function React\Async\await;
use React\Promise\Timer\sleep;

require __DIR__  . '/vendor/autoload.php';

Loop::addTimer(0, async(function () {
	await(sleep(0));
}));

Thanks, there is no problem with async().
Does this mean that any function that contains await() should be wrapped with async() ?

Forgotten async() call forces SimpleFiber::suspend() to call Loop::run() https://github.com/reactphp/async/blob/ff11a7aa9eea7104af8f05bafbc85422dac4b8ab/src/SimpleFiber.php#L44
But if Loop::run() is already called before await() is called, then this causes various problems.
Another example
<?php

use React\EventLoop\Loop;
use React\Promise\Deferred;

use function React\Async\await;

require __DIR__  . '/vendor/autoload.php';

Loop::futureTick(/* missed await */ function () {
	$deferred = new Deferred();
	Loop::addTimer(0, static fn() => $deferred->resolve());
	await($deferred->promise());
});

Loop::futureTick((static fn() => 0));

PHP Fatal error:  Uncaught RuntimeException: Can't shift from an empty datastructure in /vendor/react/event-loop/src/Tick/FutureTickQueue.php:46
Stack trace:
#0 /vendor/react/event-loop/src/Tick/FutureTickQueue.php(46): SplQueue->dequeue()
#1 /vendor/react/event-loop/src/ExtEventLoop.php(203): React\EventLoop\Tick\FutureTickQueue->tick()
#2 /vendor/react/event-loop/src/Loop.php(55): React\EventLoop\ExtEventLoop->run()
#3 [internal function]: React\EventLoop\Loop::React\EventLoop\{closure}()
#4 {main}
  thrown in /vendor/react/event-loop/src/Tick/FutureTickQueue.php on line 46

As a result, we do not know the problem file and line. It's very easy to miss async() in future code.
Maybe just throw an exception instead of calling Loop::run() ?

Forgotten async() call forces SimpleFiber::suspend() to call Loop::run()
https://github.com/reactphp/async/blob/ff11a7aa9eea7104af8f05bafbc85422dac4b8ab/src/SimpleFiber.php#L44
But if Loop::run() is already called before await() is called, then this causes various problems.
Another example
<?php

use React\EventLoop\Loop;
use React\Promise\Deferred;

use function React\Async\await;

require __DIR__  . '/vendor/autoload.php';

Loop::futureTick(/* missed await */ function () {
	$deferred = new Deferred();
	Loop::addTimer(0, static fn() => $deferred->resolve());
	await($deferred->promise());
});

Loop::futureTick((static fn() => 0));

PHP Fatal error:  Uncaught RuntimeException: Can't shift from an empty datastructure in /vendor/react/event-loop/src/Tick/FutureTickQueue.php:46
Stack trace:
#0 /vendor/react/event-loop/src/Tick/FutureTickQueue.php(46): SplQueue->dequeue()
#1 /vendor/react/event-loop/src/ExtEventLoop.php(203): React\EventLoop\Tick\FutureTickQueue->tick()
#2 /vendor/react/event-loop/src/Loop.php(55): React\EventLoop\ExtEventLoop->run()
#3 [internal function]: React\EventLoop\Loop::React\EventLoop\{closure}()
#4 {main}
  thrown in /vendor/react/event-loop/src/Tick/FutureTickQueue.php on line 46

As a result, we do not know the problem file and line. It's very easy to miss async() in future code.

We MIGHT always wrap loop handers in an async() call in the future. For now, you have to do this yourself, and yes that means you might miss one.
But I'll also open a PR to test this package against all event loops we support because honestly I only develop and tested it against ext-uv. Also @clue has looked into if we still perse need the future ticks and we might drop them from the implementation. I'll also PR your example as a test, if it's not already in there in a maybe slightly different way.

Maybe just throw an exception instead of calling Loop::run() ?

Because that Fiber constructor argument triggers when the main Fiber starts.

Thanks, there is no problem with async(). Does this mean that any function that contains await() should be wrapped with async() ?

Excellent input! The await() function can indeed be considered "blocking", so if you're using it from an event loop timer, event listener, or promise callback, you should always wrap it in an async() function. I've just filed #26 to add documentation for this behavior.
Technically, we could also wrap this automatically for each callback, but this incurs a significant overhead. This is especially true as we would have to do this for each callback even if it does not use await() internally, because there's no way to tell from the outside.
At the moment, explicitly using async() in these cases instead seems like a reasonable compromise between ease of use and performance. This is still an early development version and I'm curious to see how the ecosystem and performance considerations evolve over time! 👍

@Provoker Which version of ext-event are you running?

@WyriHaximus, Latest stable from pecl
Sockets support => enabled
Debug support => disabled
Extra functionality support including HTTP, DNS, and RPC => enabled
OpenSSL support => enabled
Thread safety support => disabled
Extension version => 3.0.6
libevent2 headers version => 2.0.21-stable


Allow Vines to be harvested like Weeping Vines

When harvesting Weeping Vines, you can break the top vine, you'll receive some or all of the connected vines. Currently, when harvesting Vines, you break the top vine and lose all connected vines, meaning you have to harvest vines one at a time, bottom to top, which is extremely awkward and unfun. As such, think Vines should be harvestable like Weeping Vines. You could then limit how far Vines will naturally grow, similarly to Weeping Vines.

I'm closing this out as something that we won't fix. It could be revisited in the future, but it's not within our capacity to work on right now.


What will dynamic_rnn reuse when set reuse of variable_scope as true

I'm sorry but I havn't found a clear answer in StackOverflow
I wonder what will dynamic_rnn reuse when set reuse of variable_scope as true, only the gate parameters will be share or including the output & status?
The example is that my code wanna process two sequence with different length by one bidirectional LSTM network, and then compare them for further use. Will I set reuse as True when process the second sequence at one step? Do I need to clear the state in this situation?

Short answer is reuse=True only affects the tf.Variable objects.  @ebrevdo on the dynamic_rnn() part.

Depends on if you're using tf 1.1 or the tf nighties.  If you're using tf
1.1 then you need to reuse the variable scope from the first call to
dynamic rnn to ensure you're using the same parameters in the second call.
In the nighties, so long as you use the same cell object in the second
call, your parameters will be shared regardless of the variable scope/
reuse value.
On May 9, 2017 4:17 PM, "Zongheng Yang"<EMAIL_ADDRESS>wrote:

Short answer is reuse=True only affects the tf.Variable objects. @ebrevdo
https://github.com/ebrevdo on the dynamic_rnn() part.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/9798#issuecomment-300328486,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtimzQTplyY9WIYJzFjD9U6RNVHrEG4ks5r4PQPgaJpZM4NVk7U
.

@ebrevdo
Thx for your answer. I've take a quick glimpse at the rnn_ops.py, it seems the dynamic_rnn call will auto clear the cells' state unless I wanna keep them isn't? So I can just set the reuse as True in the second call thus the code can run as I want regardless of the TF version?

That's right. Furthermore, If you want to keep state between two calls to
dynamic_rnn, you'd have to take the final state from the first call and
pass it in as the initial state in the second call. This of very rarely
done in practice.
On May 9, 2017 11:24 PM, "ruiann"<EMAIL_ADDRESS>wrote:

@ebrevdo https://github.com/ebrevdo
Thx for your answer. I've take a quick glimpse at the rnn_ops.py, it seems
the dynamic_rnn call will auto clear the cells' state unless I wanna keep
them isn't? So I can just set the reuse as True in the second call thus the
code can run as I want regardless of the TF version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/9798#issuecomment-300387379,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim7jljxrmp4YzHhsVIBHzjACRNW1Cks5r4VgpgaJpZM4NVk7U
.


Cut images for release

What is the expected behavior?
Currently, we are releasing nightly images for our builds. In addition to the nightlies / latest, we should also have images for each release, i.e. gateway:v0.0.6, gateway:v0.0.5, etc. so that users can have a stable set of images to use / install.

I thought that this action does it.

Looks like it's some but not others...
https://hub.docker.com/r/qiskit/quantum-serverless-gateway/tags
https://hub.docker.com/r/qiskit/quantum-serverless-notebook/tags

(maybe there's no versioned gateway because the gateway wasn't part of the last release...)

yeah, that seems to be it... gateway wasn't added to the CI before the last version was cut


Test PostgreSQL 9.6 and analyze performance impact

Since Nov 11, 2016, Amazon RDS supports PostgreSQL 9.6 [1]. This version provides various performance improvements, including support for parallel queries [2]. It'd be nice to figure out what that means for a Clair usage a scale. Besides, we need to make sure Clair behaves properly on this latest version.

We are now using PostgreSQL 9.6 in production. We've also made multiple performance improvements. Closing for now but it'd still be great to see whether we could profit from new features.


Add Dockerfile

As suggested in #5, the easiest way here would probably to use dockerhub for building the image on a push to master. What do you think @alexarchambault?
We can still add it to the main CI build later instead if that makes more sense at some point.

@alexarchambault could you add the dockerhub repo for this (linked to this repo with a build rule that builds on push to master and tags just latest)? I don't want to merge it before because the git pull in the readme doesn't work without that.

Just adjusted the dockerhub settings. Let's see how it goes.

Sorry for the delay by the way :|

I think you have added it to the main almond docker repo almondsh/almond? I thought it might be better to create a dedicated docker repo almondsh/examples.
Otherwise because people might be confused because they expect  almondsh/almond:latest to contain just the current almond version. I.e. the same as  almondsh/almond:0.4.0 at the moment.
Sorry I probably should have communicated what I meant more clearly.

Ok, I got confused by the fact that the build of the main image used to be done from dockerhub…
The new repo is here, and its build is ongoing.

Thanks. The build is finished now and it seems to works fine. :)
I'll add a line about it to the docker page in the main docs.


Problem with forcing new line in generated documentation.

Look at include/spi.h lines 149-156. They look good in header file however when it is generated to html it is all in one line, it is not clear and hard to read. doxygen supports @n special command that forces new line in generated documentation. I have added it at the beginning of each line however without any effect on generated documentation text.

@dbkinder  can you take a look?

Looks like the command to force a newline/linebreak is \n not @n  (according to https://www.stack.nl/~dimitri/doxygen/manual/commands.html)

@dbkinder Doxygen manual says:

All commands in the documentation start with a backslash (\) or an at-sign (@). If you prefer you can replace all commands starting with a backslash below by their counterparts that start with an at-sign.

I have check both options \n and @n,  none of them works.

Yep... further investigation shows this is a known problem with breathe.  I'm checking out the latest version (4.7.2) to see if we can switch to that.

i have seen some people working around this by adding  in doxygen :-)

using @n or \n or <br/> all generate the same doxygen xml output that's read by sphinx/breathe, and looks like breathe doesn't honor the  xml tag.
So, there is another way to fix this by using @param to identify the struct members being documented, and using 4 leading spaces when you want to create a pre block for the part of the struct documentation that describes the bit field layout (and is using spaces to align stuff).  I'm submitting a PR to tweak spi.h with this change.
But there's another problem here: there are two include files defining the spi interface, spi.h and spi_legacy.h with structs and such with the same names, and doxygen is trying to mash them together.

P.S.  You can use a blank line to force a new paragraph.

Then documentation in header file will look long and weird.

@m-kru I tried to assign you as a reviewer for https://github.com/zephyrproject-rtos/zephyr/pull/1424 but you don't show up.  Take a look.

I found the solution.
If your comment like this, will not work
   /**
   * line1 \n
   * line2 \n
   */

solution:
/**
 line1 \n
 line2 \n
*/

This will work


hikvision-alarmserver has an invalid jsonConfig

hello, i receive this message from the admin adapter. The Logs gives me that info
hikvision-alarmserver has an invalid jsonConfig: [{"instancePath":"/items/sendTab/items/sendXmlInstance","schemaPath":"#/patternProperties/%5E.%2B/allOf/33/then/required","keyword":"required","params":{"missingProperty":"adapter"},"message":"must have required property 'adapter'"},{"instancePath":"/items/sendTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]

@rmp61526
FYI - functionality of the adapter should not be affected
@raintonr
most likely attribute adapter is missing at send XmlINstance:
adapter - name of adapter. With special name _dataSources you can get all adapters with flag common.getHistory.

As an alternative the own adapter could be defaulted and this is not reflected azt schema. Do you have any idea?
If you think schema is incorrect, please open a issue at https://github.com/ioBroker/adapter-react-v5 or drop a note so that I can do it.

@raintonr
Could you take a look at this?

@mcm1957
Yes, the functionality of the adapter is not affected.