ci: fix subtree commands - add remote, fetch, pull

Coverage increased (+0.04%) to 79.016% when pulling 2aea2fb68c7560145626d3d48e38be460f0a843c on rrojo/auto-update into a6bf9a9f3f50e71d5df692619d594288a60bc655 on master.


add chatbot

Title and Issue number

Title : add chatbot
Issue No. : #111
Code Stack : Javascript, css
Close #111

Video/Screenshots (mandatory)

https://github.com/apu52/Travel_Website/assets/110532770/c87fa28b-63a8-4d7d-b6ef-02748e7dee00
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
adjusted go to top button accordingly
Are you contributing under any Open-source programme?

JWoC'24

@apu52 please review.

@PranavBarthwal This PR have merge conflicts . Please sync your branch to the updated version of the website & then submit your PR


@clerk/clerk-sdk-node ClerkAPIResponseError: Unprocessable Entity - getUserOauthAccessToken google

Description

Steps to reproduce:

Authorize user with Google and a gmail.send,gmail.readonly scopes
refresh the browser or wait a few hours
use server-side clerk.users.getUserOauthAccessToken(userId, 'oauth_google');
getting ClerkAPIResponseError: Unprocessable Entity error

When using the method right after the authentication with Google, everything works fine

Expected behavior:

I would expect the code not to throw and be able to get the OAuth token, even when the last token is expired, using the refresh token it fetched in the initial authentication
Actual behavior:
The getUserOauthAccessToken mechanism seems not to handle situation when it needs to refresh the OAuth token

Publishable key
pk_test_cHJvcGVyLXNwYXJyb3ctNDkuY2xlcmsuYWNjb3VudHMuZGV2JA
Environment
System:
    OS: macOS 13.5.2
    CPU: (8) arm64 Apple M1 Pro
    Memory: 70.92 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - ~/.volta/tools/image/node/18.16.0/bin/node
    Yarn: 1.22.18 - ~/.volta/tools/image/yarn/1.22.18/bin/yarn
    npm: 9.5.1 - ~/.volta/tools/image/node/18.16.0/bin/npm
    pnpm: 8.5.0 - ~/Library/pnpm/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 117.0.5938.132
    Safari: 16.6
  npmPackages:
    @clerk/clerk-sdk-node: ^4.12.6 => 4.12.6
    @clerk/nextjs: ^4.24.0 => 4.24.0
    @clerk/themes: ^1.7.6 => 1.7.6

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs

[X] I have searched for existing issues: https://github.com/clerkinc/javascript/issues

[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction / Replay Link
its pretty hard - if there's no other choice ill try to create one

I'm still trying to find a reproduction here, but we noticed Clerk auth acting strangely in our React Native / Expo app starting a week ago, and we haven't updated our app in over two weeks. It might be this. I'll report back.

Hello 👋
We currently close issues after 40 days of inactivity. It's been 30 days since the last update here. If we missed this issue, please reply here. Otherwise, we'll close this issue in 10 days.
As a friendly reminder: The best way to see an issue fixed is to open a pull request. If you're not sure how to do that, please check out our contributing guide.
Thanks for being a part of the Clerk community! 🙏

Hello again 👋
After 40 days of no activity, we'll close this issue. Keep in mind, I'm just a robot, so if I've closed this issue in error, please reply here and my human colleagues will reopen it.
As a friendly reminder: The best way to see an issue fixed is to open a pull request. If you're not sure how to do that, please check out our contributing guide.
Thanks for being a part of the Clerk community! 🙏

@thecrayon
actually eventually, it stopped happening... might be a version or something (I moved to clerk core v2

I've just started running into this issue too. For further context, I'm calling the function inside a cached server action.
I did some optimisations yesterday where I removed a bunch of unnecessary const user = await currentUser() statements, and I wonder whether that could be impacting it. I've added them back in just to see if it reduces the frequency of the problem.
export const getReports = cache(async (propertyId: string, reportId: string): Promise<ReportData> => {
const { userId } = auth();
  if (!userId) {
    throw new Error(`Authentication error`);
  }
  const clerkToken = await clerkClient().users.getUserOauthAccessToken(userId, provider);
})

hey has anyone got an update on this issue? the refresh token is not automatically refreshing the access token (im using google oauth). The code again works if I log out and log in again (probably because the access token resets), however why is the refresh token not automatically refreshing the access token as outlined in the documentation? Is it to do with the fact that im in dev mode still and can it fix in production? for reference: _ClerkAPIResponseError: Unprocessable Entity errors: [     {       code: 'oauth_missing_refresh_token',       message: 'Cannot refresh OAuth access token',       longMessage: "The current access token has expired and we cannot refresh it, because the authorization server hasn't provided us with a refresh token",       meta: [Object]     }   ]

Can we reopen this issue please?
@muratg98 can you advise what Clerk hooks you’re calling prior to requesting the OAuth token?
In my case I was using auth().protect() which I note is experimental and wondered whether that could have any impact.

@muratg98 I actually swapped out Clerk for Next Auth- I never got this to work in Clerk. Using Next Auth, I find managing the access/refresh tokens to be much easier (you can clearly see error messages and you have much more control over the user authentication in general).

@muratg98 I'm also running into this issue. Using Google OAuth like the other's who have experienced this. The token isn't getting refreshed and after an hour calling getUserOauthAccessToken causes throws the following error.
errors: [     {       code: 'oauth_missing_refresh_token',       message: 'Cannot refresh OAuth access token',       longMessage: "The current access token has expired and we cannot refresh it, because the authorization server hasn't provided us with a refresh token",       meta: [Object]     }   ]
Happens both in Dev and Prod environments.

@muratg98 I'm also running into this issue. Using Google OAuth like the other's who have experienced this. The token isn't getting refreshed and after an hour calling getUserOauthAccessToken causes throws the following error.
errors: [ { code: 'oauth_missing_refresh_token', message: 'Cannot refresh OAuth access token', longMessage: "The current access token has expired and we cannot refresh it, because the authorization server hasn't provided us with a refresh token", meta: [Object] } ]
Happens both in Dev and Prod environments.

The problem is due to the same OAuth application being used for Clerk Dev and Prod environments; the refresh token is only provided to whichever Clerk environment authenticates an account first.
The solution is to ensure you use two separate projects in Google Cloud, one for Clerk Dev and one for Clerk Prod.

@muratg98 I'm also running into this issue. Using Google OAuth like the other's who have experienced this. The token isn't getting refreshed and after an hour calling getUserOauthAccessToken causes throws the following error.
errors: [ { code: 'oauth_missing_refresh_token', message: 'Cannot refresh OAuth access token', longMessage: "The current access token has expired and we cannot refresh it, because the authorization server hasn't provided us with a refresh token", meta: [Object] } ]
Happens both in Dev and Prod environments.

The problem is due to the same OAuth application being used for Clerk Dev and Prod environments; the refresh token is only provided to whichever Clerk environment authenticates an account first. The solution is to ensure you use two separate projects in Google Cloud, one for Clerk Dev and one for Clerk Prod.

oh wow, i just got into the same issue
thanks for the hint @jnimmo

This is correct - also we are tracking this specific issue and looking to get a fix implemented internally so this wouldn't be the case anymore, in case that is helpful

just for the record, it happens when using python lib, and clerk api
    print(f'user_id: {user_id}')     print(f'provider: {provider}')     print(f'clerk_api_key: {clerk_api_key}')     url = f"https://api.clerk.com/v1/users/{user_id}/oauth_access_tokens/{provider}"     headers = {"Authorization": f"Bearer {clerk_api_key}"}     response = requests.get(url, headers=headers)     print(f'Response: {response.json()}')
response:
Response: {'errors': [{'message': 'Cannot refresh OAuth access token', 'long_message': "The current access token has expired and we cannot refresh it, because the authorization server hasn't provided us with a refresh token", 'code': 'oauth_missing_refresh_token'}], 'clerk_trace_id': '1b224db015e456bf624e4e2d1b3f2860'}

Hey everyone, I'm a Software Engineer from @clerk SDK team 👋
The refresh_token is only provided by Google during the initial user authorization. Subsequent authorizations, like those made while testing an OAuth2 integration, will not return the refresh_token again, and therefore calls to getUserOauthAccessToken end up failing.
Clerk will handle these cases, so you won't need to manage Identity Provider-specific behaviors. We will soon implement an API change that redirects users to Google for consent again if a refresh token is missing, requiring no action on your part.


Add /apis_ontology.[model]/{id}/ endpoints to Swagger

The following endpoints seem to be missing in the Swagger documentation:

[ ] apis/api/apis_ontology.event/{id}
[ ] apis/api/apis_ontology.function/{id}
[ ] apis/api/apis_ontology.institution/{id}
[ ] apis/api/apis_ontology.person/{id}
[ ] apis/api/apis_ontology.place/{id}
[ ] apis/api/apis_ontology.salary/{id}

Their response should be a single entry with the same fields as in the list view + a list of relations grouped by class.

I've extended the endpoint enumerator to include those endpoints. Can you check if that works for you?

@b1rger if you like you can also re-run the frontend-build yourself to check ;)

a list of relations grouped by class.

this seems to be missing from both the swagger dok as well as the return shape

ah, yeah, I was referring to the endpoints in the swagger documentation. I've created #85 for tracking the detail responses shapes


fix bug in roles for device settings

@MicrosoftGuyJFlo

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


bottom of background not showing again

The issue was fixed until I upgraded to 0.1.8. just wanted to let you know

Have you set background_image: true?

I did not, just changed it and now working. Thanks


video controls progress is not visible on IOS

I add controls={true} but the video controls progress is not visible on IOS,there is nothing on Video.Is anyone knows how to solve this?

@cq920702  how did you solve this? I too added controls={true} but I can't get anything to show up...

@latimesmike There is no video controls progress  and you need to add the custom progress by yourself.


Implement reflection.proto

Complementing the https://github.com/eigr/massa/issues/13

Closed this because already implemented in wip/http-transcoding.
Only waiting for merge but we can close this for now.


Do CollisionObject::_input_event when MOUSE_CAPTURED

[ ] Documentation update
The last known mouse position is used, not necessarily the mouse center.
[ ] Is this consistent with events which go through _unhandled_input?
[ ] Add example where I set the mouse position to the screen center.
[ ] Find existing issues.

Looks like I have time in the two coming week to work on this again. Sorry for the silent delay

@RandomShaper could we talk about this PR to find out what needs to be done to get this in?

Sure, but we'll have to leave it for next week. I'm just too busy these days.


feat: feeds | delete feeds option and add modal window

Fixes Issue
related to issue none

Changes proposed

[x] fix load comments with post, and don't send another view when user viewed
[x] add feed delete functionality
[x] make the modal window to be common component
[x] add edit/delete options in feed options screen and close functionality
[x] add feed option button display

Screenshots
https://github.com/thecyberworld/TheCyberHUB/assets/76536506/8186a2d9-8e46-4263-aff8-515d0b664998

Note to reviewers

still in progress, need to add option to delete reply comments, and to edit feeds and comments

Code of Conduct

[x] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Thecyberworld.
Join the Thecyberworld GitHub Organisation by raising an issue (you will be sent an invitation).

nice good work


Refinement from query code generation

This change extracts refinements from refinement+query expressions for enforcing data validity in code generated Kotlin handles.

@jasonwyatt I thought I had (by running the ./tools/local-presubmit) but it seems not. Thanks
Ktlint doesn't give me any feedback when run on ./src/tools/tests/goldens/*.kt
Am I holding it wrong?


when a share exists its impossible to share a renamed folder

as einstein create folder f1
as einstein create folder f2
as einstein share folder f1 with richard
as einstein rename folder f2 to f2-renamed
as einstein share folder f2-renamed with richard

Folder cannot be shared, but sharing itself still works, because its possible to create a folder called f3 and share that.
Failed sharing response:
<?xml version="1.0" encoding="UTF-8"?>
<ocs><meta><status>error</status><statuscode>996</statuscode><message>grpc create share request failed</message></meta></ocs>

OCIS log output
2020-10-20T11:17:21+05:45 INF unary code=OK end="20/Oct/2020:11:17:21 +0545" from=tcp://<IP_ADDRESS>:46106 pkg=rgrpc service=storage start="20/Oct/2020:11:17:21 +0545" time_ns=88133 traceid=aef75bf10b157ccf7cf6f81c60a1866c uri=/cs3.storage.registry.v1beta1.RegistryAPI/GetStorageProvider user-agent=grpc-go/1.26.0
2020-10-20T11:17:21+05:45 ERR home/artur/go/pkg/mod/github.com/cs3org/reva@v1.2.2-0.20200924071957-e6676516e61e/internal/grpc/services/storageprovider/storageprovider.go:740 > error setting ACL error="ocfs: error resolving reference: error: not found: f25f51e5-2c71-4747-90ee-7d3c67c4c11b" pkg=rgrpc service=storage traceid=aef75bf10b157ccf7cf6f81c60a1866c
2020-10-20T11:17:21+05:45 INF unary code=OK end="20/Oct/2020:11:17:21 +0545" from=tcp://<IP_ADDRESS>:33010 pkg=rgrpc service=storage start="20/Oct/2020:11:17:21 +0545" time_ns=373589 traceid=aef75bf10b157ccf7cf6f81c60a1866c uri=/cs3.storage.provider.v1beta1.ProviderAPI/AddGrant user-agent=grpc-go/1.26.0
2020-10-20T11:17:21+05:45 ERR home/artur/go/pkg/mod/github.com/cs3org/reva@v1.2.2-0.20200924071957-e6676516e61e/internal/grpc/services/gateway/usershareprovider.go:460 > error committing share to storage grant error="gateway: grpc failed with code CODE_INTERNAL" pkg=rgrpc service=storage traceid=aef75bf10b157ccf7cf6f81c60a1866c
2020-10-20T11:17:21+05:45 INF unary code=OK end="20/Oct/2020:11:17:21 +0545" from=tcp://<IP_ADDRESS>:46148 pkg=rgrpc service=storage start="20/Oct/2020:11:17:21 +0545" time_ns=1765773 traceid=aef75bf10b157ccf7cf6f81c60a1866c uri=/cs3.gateway.v1beta1.GatewayAPI/CreateShare user-agent=grpc-go/1.26.0
2020-10-20T11:17:21+05:45 INF http end="20/Oct/2020:11:17:21 +0545" host=<IP_ADDRESS> method=POST pkg=rhttp proto=HTTP/1.1 service=storage size=164 start="20/Oct/2020:11:17:21 +0545" status=200 time_ns=104697473 traceid=aef75bf10b157ccf7cf6f81c60a1866c uri=/ocs/v1.php/apps/files_sharing/api/v1/shares url=/ocs/v1.php/apps/files_sharing/api/v1/shares

the issue even happens if the share of f1 is removed again

not hapening any longer with the latest master

not hapening any longer with the latest master

I will reopen this to add tests (or to check if those tests already exist). Tests will run against owncloud and ocis storage proving if there is an issue in ether of them

[ ]  ToDo QA-team: add API tests for this case

I will reopen this to add tests (or to check if those tests already exist). Tests will run against owncloud and ocis storage proving if there is an issue in ether of them

[ ]  ToDo QA-team: add API tests for this case


Zombie nodes

0.6.0
Build/Run method

[ x] Docker - hass io addon
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

Zwave2Mqtt version: 0.6.0
Openzwave Version: 1.6.974
Describe the bug
I have 3 nodes on my network that do not exist, however they continually persist as dead nodes. The only way I can make them dissappear, temporarily, is to run a request info, then they get flagged as removed. However if I do a neighbor update of certain nodes, they rise again as dead nodes.
Additional context
The best I can determine is that they are marked as failed by the controller, but for some reason a few nodes still have them listed as neighbors so they rise again when a network update is done. The reason I believe they are marked as failed is because if I tell it to send a NIF, neighbor update, has failed, or remove failed node, nothing is logged for those nodes, if I send a request for info, it does attempt, reports the node as sleeping, and them flags it as removed. But, again, they rise when a neighbor update is requested.

Are you speaking about mesh graph?

Daniel - Software Engineer
Support me at:
Github sponsors

On 24 Apr 2020, at 06:34, xannor<EMAIL_ADDRESS>wrote:

Assigned #377 to @robertsLando.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.

not specifically, but it can be used to visualize the links. I am mostly observing this through the debug log. As an example:
2020-04-24T11:11:11.133Z z2m:Zwave controller command {
nodeid: 11,
state: 7,
errcode: 0,
help: 'RequestNodeNeighborUpdate Completed'
}
OpenZWave Detail, Received: 0x01, 0x05, 0x00, 0x48, 0x58, 0x22, 0xc8
OpenZWave Detail,
OpenZWave Info, REQUEST_NEIGHBOR_UPDATE_DONE
OpenZWave Detail, Requesting routing info (neighbor list) for Node 11
OpenZWave Detail, Node011, Queuing (Command) Get Routing Info (Node=11): 0x01, 0x07, 0x00, 0x80, 0x0b, 0x00, 0x00, 0x03, 0x70
OpenZWave Detail, Node011, Notification: RequestNodeNeighborUpdate ControllerCommand - Completed
OpenZWave Detail,
OpenZWave Info, Node011, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=11): 0x01, 0x07, 0x00, 0x80, 0x0b, 0x00, 0x00, 0x03, 0x70
OpenZWave Info, Node011, Encrypted Flag is 0
OpenZWave Detail, Node011, Received: 0x01, 0x20, 0x01, 0x80, 0xf6, 0x1b, 0x78, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xcb
OpenZWave Detail,
OpenZWave Info, Node011, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
OpenZWave Info, Node011, Neighbors of this node are:
OpenZWave Info, Node011, Node 2
OpenZWave Info, Node011, Node 3
OpenZWave Info, Node011, Node 5
OpenZWave Info, Node011, Node 6
OpenZWave Info, Node011, Node 7
OpenZWave Info, Node011, Node 8
OpenZWave Info, Node011, Node 9
OpenZWave Info, Node011, Node 10
OpenZWave Info, Node011, Node 12
OpenZWave Info, Node011, Node 13
OpenZWave Info, Node011, Node 20
OpenZWave Info, Node011, Node 21
OpenZWave Info, Node011, Node 22
OpenZWave Info, Node011, Node 23
OpenZWave Detail, Node011, Expected reply was received
OpenZWave Detail, Node011, Message transaction complete
OpenZWave Detail,
OpenZWave Detail, Node011, Removing current message

This is a neighbor update request to node 11. It seem to report back node 12 and 20 as neighbors, though those nodes do not exist. Node 12 was a NanoMote quad that I had accidentally reset and is now another node (23 I believe), and node 20 was a GE hinge pin sensor that I had but could not remove, this one was also node 19, I had some issues when I first tried to set it up. I stopped using it because it is not compatible with my door frames.

Here is an example of sending a request info to node 20:
OpenZWave Detail, Node020, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
OpenZWave Detail, Node020, ZW_SEND_DATA delivered to Z-Wave stack
OpenZWave Detail, Node020, Received: 0x01, 0x18, 0x00, 0x13, 0x6d, 0x01, 0x03, 0xb1, 0x00, 0x7f, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x01, 0x07, 0x00, 0x00, 0x00, 0x00, 0x02, 0x14, 0x15, 0x16, 0x46
OpenZWave Detail, Node020, ZW_SEND_DATA Request with callback ID 0x6d received (expected 0x6d)
2020-04-24T11:18:02.509Z z2m:Zwave Notification from node 20: Notification - NoOperation (2)
2020-04-24T11:18:02.509Z z2m:Zwave Notification from node 20: Notification - Node Asleep (4)
OpenZWave Detail, Node020, Extended TxStatus: Time: 9450, Hops: 0, Rssi: --- --- --- --- ---, AckChannel: 0, TxChannel: 1, RouteScheme: Explorer Route, Route: 0 0 0 0, RouteSpeed: 40K, RouteTries: 20, FailedLinkFrom: 21, FailedLinkTo: 22
OpenZWave Info, Node020, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
OpenZWave Info, Node020, Node 20 has been marked as asleep
OpenZWave Info, Node020, Node not responding - moving QueryStageComplete command to Wake-Up queue
OpenZWave Detail, Node020, Notification: Notification - NoOperation
OpenZWave Detail, Node020, Notification: Notification - Node Asleep

This is also the only action I can send that shows anything in the log, if I do a NIF or has failed or remove failed, nothing is logged. When I do the request for info, the node get set as removed.

@Fishwaldo

Did you try to send updateNodeNeightbors api?

Against which node? I have done it against node 11, which reports node 12 and 20 as neighbors. Oddly enough this time it finally did not report node 20. I originally thought ti try to fire update neighbors on all nodes that had reported a link to a dead node, but the only flaw in that is that node 19 seems to have no links, but still comes back.

Against node 11

I have since moved to the other zwave package for home assistant, in there I removed the dead nodes.


[Decomp] Fix bitfields in dma-bucket

Pull Request Test Coverage Report for Build 760999454

65 of 109 (59.63%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 69.242%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

decompiler/IR2/AtomicOp.cpp
3
5
60.0%

decompiler/IR2/AtomicOpForm.cpp
0
2
0.0%

decompiler/IR2/bitfields.h
1
6
16.67%

decompiler/IR2/FormExpressionAnalysis.cpp
25
41
60.98%

decompiler/IR2/bitfields.cpp
36
55
65.45%

Totals

Change from base Build 759438937:
-0.04%

Covered Lines:
33592

Relevant Lines:
48514

💛  - Coveralls


Support basic building feature on msbuild v1.

Or only msbuild v2.

Usable information from https://www.nuget.org/packages/Microsoft.Net.Compilers

IL2C now automate executable at 3bd86d5a60d9df9e8aacffcc3a0efdb98b45c0cf

We have to build translated C source code by automated.

First step: support arduino eco system


Use single upload for file less than 20 m

For file size less than 20M, use single upload instead of multi-upload

@usmanismail  Ready for review.


The gif operation requires libvips to have been installed with support for ImageMagick

I am trying to resize a gif file, but keep getting this error: The gif operation requires libvips to have been installed with support for ImageMagick
I am aware that I need to install libvips with *magick, but I'm not sure how to do that.
Is it possible to list this as a dependency so I don't have to install it separately on every single machine that I use?

Please see https://sharp.pixelplumbing.com/install#custom-libvips and #2012

Thanks for the quick reply.
I read the instructions, but I'm still not sure how to compile "libvips with imageMagick support" automatically on running npm install / yarn.
Should I configure package.json somehow to reflect this or set a global flag inside the project somehow?

You'll need to globally install libvips compiled with support for ImageMagick before using npm to install sharp.
https://libvips.github.io/libvips/install.html#building-libvips-from-a-source-tarball

I deleted node_modules and ran:
yarn config set sharp_binary_host "https://npm.taobao.org/mirrors/sharp" yarn config set sharp_libvips_binary_host "https://npm.taobao.org/mirrors/sharp-libvips" yarn install sharp
After doing this, I am getting the same error.

And who does he use Windows for? The guide specifies "The use of a globally-installed libvips is unsupported on Windows." What can I do as an alternative? I gloabally-installed libvips, added to the PATH but is not recognized by Sharp

@DragoSpiro98 If your constraints include Windows and requirements include GIF output then sharp is probably the wrong solution.

@msiric Were you able to make any progress with this by following the instructions at https://libvips.github.io/libvips/install.html#building-libvips-from-a-source-tarball ?

@lovell I haven't made any progress on a Win machine, but judging by your reply above, I assume it isn't possible to install libvips globally with ImageMagick support?

I've also trying to install sharp to configure a GIF file however I couldn't make it work.
OS: Ubuntu 18.04.5 LTS
I followed instructions to install libvips
These are the installation results:
muratcolyaran@MSI:~/microservices-google-cloud$ pkg-config --modversion vips-cpp
8.10.6

And this is the npm installation
sharp: Detected globally-installed libvips v8.10.6
sharp: Building from source via node-gyp
make: Entering directory '/home/muratcolyaran/microservices-google-cloud/node_modules/sharp/build'
  CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
  AR(target) Release/obj.target/../node-addon-api/nothing.a
  COPY Release/nothing.a
  TOUCH Release/obj.target/libvips-cpp.stamp
  CXX(target) Release/obj.target/sharp/src/common.o
  CXX(target) Release/obj.target/sharp/src/metadata.o
  CXX(target) Release/obj.target/sharp/src/stats.o
  CXX(target) Release/obj.target/sharp/src/operations.o
  CXX(target) Release/obj.target/sharp/src/pipeline.o
  CXX(target) Release/obj.target/sharp/src/utilities.o
  CXX(target) Release/obj.target/sharp/src/sharp.o
  SOLINK_MODULE(target) Release/obj.target/sharp.node
  COPY Release/sharp.node
make: Leaving directory '/home/muratcolyaran/microservices-google-cloud/node_modules/sharp/build'

However when I try to make an operation on a GIF file I'm getting this error message
Error: GIF output requires libvips with support for ImageMagick
Do you have any advice? On which step I'm making mistake

I've found an easy solution for this and that is to grab the libvips build for your platform
https://github.com/libvips/libvips/releases and just extract the binaries from the bin folder to node_modules/sharp/build/Release and overwrite all files.
Verified to work (at least for this particular use case) for<EMAIL_ADDRESS>with<EMAIL_ADDRESS>

I recommend just using FFmpeg. its faster than imagemagick by almost several folds and uses far less ram. it shouldn't be this difficult to convert some gifs on lambda! but it is and after weeks of trying I've given up and surprised how well FFmpeg works. I guess when you deal with hours and hours of hd video compression, image ain't nothin

leaving this here... on macOS Big Sur 11.4 I ran into some issues, but resolved it.
haven't tested with Lambda, but GIF output working on macOS now.
NOTE: I also have imagemagick installed, so not sure if that plays into it.
# install global vips, which already includes the --with-magick flag
brew install vips

# next I had issues with OpenEXR and Imath not being in the default pkgconfig paths, so I added some links to the Homebrew Cellar:
sudo ln -s /usr/local/Cellar/openexr/3.0.5/lib/pkgconfig/OpenEXR.pc /usr/local/lib/pkgconfig/OpenEXR.pc;
sudo ln -s /usr/local/Cellar/Imath/3.0.5/lib/pkgconfig/Imath.pc /usr/local/lib/pkgconfig/Imath.pc;

# not sure if required, but I also ensured this was installed globally node-gyp might be required...
npm install -g node-gyp;

# the last issue I encountered with the XCode CLI tools,
# i have s newer version installed, but the path points to the older one,
# i opted to just update the path with this command:
# (other options here: https://github.com/schnerd/d3-scale-cluster/issues/7)
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer;

# last step, your sharp install should be good and it should pickup your global vips without issue.
yarn add sharp;
# npm install sharp;

I fixed this issue by uninstalling vips, since I had it installed globally:
brew uninstall vips

If, like me, you’re arriving here after 2022-02-01, then you should know that starting with v0.30.0 sharp supports GIF with the prebuilt binaries, so you don’t need to bring your own ImageMagick or anything like that.


Fix rebase error with ESM interop

Description

Testing Instructions

Current dependencies on/for this PR:

main

PR #5395

PR #5396   👈

This comment was auto-generated by Graphite.

Sorry. I messed up this one...

Sorry. I messed up this one...


Hack patched

They also added a new menu for key mappings

yes, he is updating it

or not, maybe tomorrow

I'm working on it as of right now... I'm afraid it's more than just a simple deobfuscation procedure. The whole "bind to anything you want" thing has changed everything and there's no longer a "mousePressed" variable. I'm trying my best.
In the meantime, transparency and enemy lines work fine!

k

so no autoaim?

Nope

It will look like it, but you're not actually doing auto aim


JetBrains: security: save our config in a secure way

In particular, the access token can be confidential information that we don't want to store in the file system unencoded.
VS Code has something called "Secret storage" where we store the tokens once they are set in settings.
JetBrains must have something like it—let's use it.

After a quick discussion with @szymonprz:

We'll save the application-level token in JetBrains' PasswordSafe storage, but the project-level ones will remain in the project folder, assuming that it's a safe place, or that security-sensitive users can just avoid using that and use app-level settings.

We should still read the accessToken key from the app-level config for backward-compatibility.


Add BYOH cluster create sequence diagram

Co-authored-by: Anusha Hegde<EMAIL_ADDRESS>What this PR does / why we need it:
This PR adds a sequence diagram for BYOH cluster creation workflow.
Which issue(s) this PR fixes :
Fixes #

Codecov Report

Merging #355 (e5d4629) into main (3069d0c) will increase coverage by 61.92%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           main     #355       +/-   ##
=========================================
+ Coverage      0   61.92%   +61.92%
=========================================
  Files         0       23       +23
  Lines         0     1731     +1731
=========================================
+ Hits          0     1072     +1072
- Misses        0      587      +587
- Partials      0       72       +72

Impacted Files
Coverage Δ

agent/installer/internal/algo/apt_step.go
100.00% <0.00%> (ø)

agent/main.go
21.42% <0.00%> (ø)

.../installer/internal/algo/mock_ubuntu_with_error.go
100.00% <0.00%> (ø)

agent/installer/installer.go
79.22% <0.00%> (ø)

agent/cloudinit/cloudinit.go
76.66% <0.00%> (ø)

agent/installer/os_detector.go
88.67% <0.00%> (ø)

agent/cloudinit/file_writer.go
30.30% <0.00%> (ø)

agent/installer/bundle_downloader.go
68.42% <0.00%> (ø)

...ontrollers/infrastructure/byocluster_controller.go
71.55% <0.00%> (ø)

agent/cloudinit/cmd_runner.go
100.00% <0.00%> (ø)

... and 13 more

Continue to review full report at Codecov.

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

How about adding "Patch BYOH Provider on Management Cluster"?

How about adding "Patch BYOH Provider on Management Cluster"?

@huchen2021 , I do not have strong views on this, but my thoughts were that it's implied that the provider is installed when we say management cluster. I know, currently we have to patch BYOH provider separately but that might not be the case going forward.

How about adding "Patch BYOH Provider on Management Cluster"?

Yes, that's a valid point @huchen2021
We did discuss about this, but for cluster create, we are assuming the provider is already present on the management cluster - this is something as a preparation step and not really part of "Cluster Create" operation. Makes sense?

@dharmjit shall we create an arch.md file where we describe these diagrams and embed the png as well, wdyt?

@dharmjit shall we create an arch.md file where we describe these diagrams and embed the png as well, wdyt?

Yes, referring to these diagrams in other docs is a good idea for discovery.

Yes, referring to these diagrams in other docs is a good idea for discovery.

Let's use https://github.com/vmware-tanzu/cluster-api-provider-bringyourownhost/issues/238 for this.

overall /LGTM
@dharmjit minor nits of arrow types for return messages and wherever possible callout sync/async calls

@dharmjit let me take care of these nits in #238 , we can merge this
LGTM!


ModuleNotFoundError: No module named 'main'

Announcement:
We have identified an issue with a subset of python functions apps which have imported libraries like python-dotenv are seeing an error with functions runtime 4.9.1 and above.
The function apps are failing with the following error:
Microsoft.Azure.WebJobs.Host.FunctionInvocationException : Exception while executing function: Functions.HttpTrigger ---> Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcException : Result: Failure Exception: ModuleNotFoundError: No module named '__main__' Stack: File '/azure-functions-host/workers/python/3.9/LINUX/X64/azure_functions_worker/dispatcher.py', line 448, in _handle__invocation_request call_result = await self._loop.run_in_executor( File '/usr/local/lib/python3.9/concurrent/futures/thread.py', line 58, in run result = self.fn(*self.args, **self.kwargs) File '/azure-functions-host/workers/python/3.9/LINUX/X64/azure_functions_worker/dispatcher.py', line 691, in _run_sync_func return ExtensionManager.get_sync_invocation_wrapper(context, File '/azure-functions-host/workers/python/3.9/LINUX/X64/azure_functions_worker/extension.py', line 215, in _raw_invocation_wrapper result = function(**args) File '/home/site/wwwroot/HttpTrigger/__init__.py', line 8, in main return func.HttpResponse(f'Dotenv: {load_dotenv(find_dotenv())}') File '/home/site/wwwroot/.python_packages/lib/site-packages/dotenv/main.py', line 284, in find_dotenv if usecwd or _is_interactive() or getattr(sys, 'frozen', False): File '/home/site/wwwroot/.python_packages/lib/site-packages/dotenv/main.py', line 281, in _is_interactive main = __import__('__main__', None, None, fromlist=['__file__'])
Mitigation:
Add the app setting PYTHON_ISOLATE_WORKER_DEPENDENCIES to 0 as described in the documentation here
Fix:
The fix for this is currently being rolled out and will be available in runtime versions 1.10.2 and higher.

Still seeing this and really holding us back here on runtime version <IP_ADDRESS>.

I am still seeing this on uk-south premium plan. Combined with #1050 this issue blocks use of Tensorflow and Dill on Azure Functions.

@drewsilcock Have you enabled PYTHON_ISOLATE_WORKER_DEPENDENCIES in your app settings? Also, could you share your requirements.txt?

I am still seeing this on uk-south premium plan. Combined with #1050 this issue blocks use of Tensorflow and Dill on Azure Functions.

@drewsilcock Have you enabled PYTHON_ISOLATE_WORKER_DEPENDENCIES in your app settings? Also, could you share your requirements.txt?

I have PYTHON_ISOLATE_WORKER_DEPENDENCIES set to 1 as a necessary step to fixing issues https://github.com/Azure/azure-functions-python-worker/issues/1217 and https://github.com/Azure/azure-functions-python-worker/issues/1050.
I can since figured out a hacky workaround for this issue that doesn't require setting PYTHON_ISOLATE_WORKER_DEPENDENCIES to 0, which is simply to create the file __main__.py in the folder of my function and then put
import os
import path
sys.path.append(os.path.abspath(os.path.join(os.path.dirname(__file__))))

at the top of the __init__.py for the function - this unblocks me from being able to use these libraries, but obviously isn't an ideal solution.
For reference, requirements.txt:
absl-py==1.4.0 ; python_version >= "3.9" and python_version < "3.10"
aiohttp==3.8.4 ; python_version >= "3.9" and python_version < "3.10"
aiosignal==1.3.1 ; python_version >= "3.9" and python_version < "3.10"
alembic==1.10.4 ; python_version >= "3.9" and python_version < "3.10"
astunparse==1.6.3 ; python_version >= "3.9" and python_version < "3.10"
async-cache==1.1.1 ; python_version >= "3.9" and python_version < "3.10"
async-timeout==4.0.2 ; python_version >= "3.9" and python_version < "3.10"
attrs==23.1.0 ; python_version >= "3.9" and python_version < "3.10"
azure-core==1.26.4 ; python_version >= "3.9" and python_version < "3.10"
azure-cosmos==4.3.1 ; python_version >= "3.9" and python_version < "3.10"
azure-eventhub==5.11.2 ; python_version >= "3.9" and python_version < "3.10"
azure-functions==1.13.3 ; python_version >= "3.9" and python_version < "3.10"
azure-storage-blob==12.16.0 ; python_version >= "3.9" and python_version < "3.10"
binaryornot==0.4.4 ; python_version >= "3.9" and python_version < "3.10"
cachetools==5.3.0 ; python_version >= "3.9" and python_version < "3.10"
certifi==2022.12.7 ; python_version >= "3.9" and python_version < "3.10"
cffi==1.15.1 ; python_version >= "3.9" and python_version < "3.10"
chardet==5.1.0 ; python_version >= "3.9" and python_version < "3.10"
charset-normalizer==3.1.0 ; python_version >= "3.9" and python_version < "3.10"
click==8.1.3 ; python_version >= "3.9" and python_version < "3.10"
cloudpickle==2.2.1 ; python_version >= "3.9" and python_version < "3.10"
colorama==0.4.6 ; python_version >= "3.9" and python_version < "3.10" and platform_system == "Windows"
comtrade==0.0.10 ; python_version >= "3.9" and python_version < "3.10"
contourpy==1.0.7 ; python_version >= "3.9" and python_version < "3.10"
cryptography==40.0.2 ; python_version >= "3.9" and python_version < "3.10"
cycler==0.11.0 ; python_version >= "3.9" and python_version < "3.10"
databricks-cli==0.17.6 ; python_version >= "3.9" and python_version < "3.10"
decorator==5.1.1 ; python_version >= "3.9" and python_version < "3.10"
dill==0.3.4 ; python_version >= "3.9" and python_version < "3.10"
dm-tree==0.1.8 ; python_version >= "3.9" and python_version < "3.10"
docker==6.0.1 ; python_version >= "3.9" and python_version < "3.10"
entrypoints==0.4 ; python_version >= "3.9" and python_version < "3.10"
flask==2.2.3 ; python_version >= "3.9" and python_version < "3.10"
flatbuffers==23.3.3 ; python_version >= "3.9" and python_version < "3.10"
fonttools==4.39.3 ; python_version >= "3.9" and python_version < "3.10"
frozenlist==1.3.3 ; python_version >= "3.9" and python_version < "3.10"
gast==0.4.0 ; python_version >= "3.9" and python_version < "3.10"
gitdb==4.0.10 ; python_version >= "3.9" and python_version < "3.10"
gitpython==3.1.31 ; python_version >= "3.9" and python_version < "3.10"
google-auth-oauthlib==1.0.0 ; python_version >= "3.9" and python_version < "3.10"
google-auth==2.17.3 ; python_version >= "3.9" and python_version < "3.10"
google-pasta==0.2.0 ; python_version >= "3.9" and python_version < "3.10"
greenlet==2.0.2 ; python_version >= "3.9" and platform_machine == "aarch64" and python_version < "3.10" or python_version >= "3.9" and platform_machine == "ppc64le" and python_version < "3.10" or python_version >= "3.9" and platform_machine == "x86_64" and python_version < "3.10" or python_version >= "3.9" and platform_machine == "amd64" and python_version < "3.10" or python_version >= "3.9" and platform_machine == "AMD64" and python_version < "3.10" or python_version >= "3.9" and platform_machine == "win32" and python_version < "3.10" or python_version >= "3.9" and platform_machine == "WIN32" and python_version < "3.10"
grpcio==1.54.0 ; python_version >= "3.9" and python_version < "3.10"
gunicorn==20.1.0 ; python_version >= "3.9" and python_version < "3.10" and platform_system != "Windows"
h5py==3.8.0 ; python_version >= "3.9" and python_version < "3.10"
idna==3.4 ; python_version >= "3.9" and python_version < "3.10"
importlib-metadata==5.2.0 ; python_version >= "3.9" and python_version < "3.10"
importlib-resources==5.12.0 ; python_version >= "3.9" and python_version < "3.10"
isodate==0.6.1 ; python_version >= "3.9" and python_version < "3.10"
itsdangerous==2.1.2 ; python_version >= "3.9" and python_version < "3.10"
jax==0.4.8 ; python_version >= "3.9" and python_version < "3.10"
jinja2==3.1.2 ; python_version >= "3.9" and python_version < "3.10"
joblib==1.2.0 ; python_version >= "3.9" and python_version < "3.10"
keras==2.12.0 ; python_version >= "3.9" and python_version < "3.10"
kiwisolver==1.4.4 ; python_version >= "3.9" and python_version < "3.10"
libclang==16.0.0 ; python_version >= "3.9" and python_version < "3.10"
mako==1.2.4 ; python_version >= "3.9" and python_version < "3.10"
markdown==3.4.3 ; python_version >= "3.9" and python_version < "3.10"
markupsafe==2.1.2 ; python_version >= "3.9" and python_version < "3.10"
matplotlib==3.7.1 ; python_version >= "3.9" and python_version < "3.10"
ml-dtypes==0.1.0 ; python_version >= "3.9" and python_version < "3.10"
mlflow==1.30.1 ; python_version >= "3.9" and python_version < "3.10"
multidict==6.0.4 ; python_version >= "3.9" and python_version < "3.10"
numpy==1.23.5 ; python_version >= "3.9" and python_version < "3.10"
oauthlib==3.2.2 ; python_version >= "3.9" and python_version < "3.10"
opt-einsum==3.3.0 ; python_version >= "3.9" and python_version < "3.10"
packaging==21.3 ; python_version >= "3.9" and python_version < "3.10"
pandas==1.5.3 ; python_version >= "3.9" and python_version < "3.10"
pillow==9.5.0 ; python_version >= "3.9" and python_version < "3.10"
plotly==5.14.1 ; python_version >= "3.9" and python_version < "3.10"
prometheus-client==0.16.0 ; python_version >= "3.9" and python_version < "3.10"
prometheus-flask-exporter==0.22.3 ; python_version >= "3.9" and python_version < "3.10"
protobuf==4.22.3 ; python_version >= "3.9" and python_version < "3.10"
psycopg-binary==3.1.8 ; python_version >= "3.9" and python_version < "3.10"
psycopg-c==3.1.8 ; python_version >= "3.9" and python_version < "3.10"
psycopg-pool==3.1.7 ; python_version >= "3.9" and python_version < "3.10"
psycopg[c,pool]==3.1.8 ; python_version >= "3.9" and python_version < "3.10"
pyasn1-modules==0.3.0 ; python_version >= "3.9" and python_version < "3.10"
pyasn1==0.5.0 ; python_version >= "3.9" and python_version < "3.10"
pycparser==2.21 ; python_version >= "3.9" and python_version < "3.10"
pydantic==1.10.7 ; python_version >= "3.9" and python_version < "3.10"
pydantic[dotenv]==1.10.7 ; python_version >= "3.9" and python_version < "3.10"
pyjwt==2.6.0 ; python_version >= "3.9" and python_version < "3.10"
pyparsing==3.0.9 ; python_version >= "3.9" and python_version < "3.10"
python-dateutil==2.8.2 ; python_version >= "3.9" and python_version < "3.10"
python-dotenv==1.0.0 ; python_version >= "3.9" and python_version < "3.10"
pytz==2022.7.1 ; python_version >= "3.9" and python_version < "3.10"
pywin32==306 ; python_version >= "3.9" and python_version < "3.10" and sys_platform == "win32"
pyyaml==6.0 ; python_version >= "3.9" and python_version < "3.10"
querystring-parser==1.2.4 ; python_version >= "3.9" and python_version < "3.10"
redis==4.5.4 ; python_version >= "3.9" and python_version < "3.10"
requests-oauthlib==1.3.1 ; python_version >= "3.9" and python_version < "3.10"
requests==2.28.2 ; python_version >= "3.9" and python_version < "3.10"
rsa==4.9 ; python_version >= "3.9" and python_version < "3.10"
scikit-learn==1.0.2 ; python_version >= "3.9" and python_version < "3.10"
scipy==1.10.1 ; python_version >= "3.9" and python_version < "3.10"
setuptools==67.7.2 ; python_version >= "3.9" and python_version < "3.10"
six==1.16.0 ; python_version >= "3.9" and python_version < "3.10"
smmap==5.0.0 ; python_version >= "3.9" and python_version < "3.10"
sqlalchemy==1.4.47 ; python_version >= "3.9" and python_version < "3.10"
sqlparse==0.4.4 ; python_version >= "3.9" and python_version < "3.10"
tabulate==0.9.0 ; python_version >= "3.9" and python_version < "3.10"
tenacity==8.2.2 ; python_version >= "3.9" and python_version < "3.10"
tensorboard-data-server==0.7.0 ; python_version >= "3.9" and python_version < "3.10"
tensorboard-plugin-wit==1.8.1 ; python_version >= "3.9" and python_version < "3.10"
tensorboard==2.12.2 ; python_version >= "3.9" and python_version < "3.10"
tensorflow-estimator==2.12.0 ; python_version >= "3.9" and python_version < "3.10"
tensorflow-io-gcs-filesystem==0.32.0 ; python_version >= "3.9" and python_version < "3.10" and platform_machine != "arm64" or python_version >= "3.9" and python_version < "3.10" and platform_system != "Darwin"
tensorflow-probability==0.18.0 ; python_version >= "3.9" and python_version < "3.10"
tensorflow==2.12.0 ; python_version >= "3.9" and python_version < "3.10"
termcolor==2.3.0 ; python_version >= "3.9" and python_version < "3.10"
threadpoolctl==3.1.0 ; python_version >= "3.9" and python_version < "3.10"
tqdm==4.65.0 ; python_version >= "3.9" and python_version < "3.10"
typing-extensions==4.5.0 ; python_version >= "3.9" and python_version < "3.10"
tzdata==2023.3 ; python_version >= "3.9" and python_version < "3.10" and sys_platform == "win32"
urllib3==1.26.15 ; python_version >= "3.9" and python_version < "3.10"
waitress==2.1.2 ; python_version >= "3.9" and python_version < "3.10" and platform_system == "Windows"
websocket-client==1.5.1 ; python_version >= "3.9" and python_version < "3.10"
werkzeug==2.2.3 ; python_version >= "3.9" and python_version < "3.10"
wheel==0.40.0 ; python_version >= "3.9" and python_version < "3.10"
wrapt==1.14.1 ; python_version >= "3.9" and python_version < "3.10"
xarray==0.21.1 ; python_version >= "3.9" and python_version < "3.10"
yarl==1.9.1 ; python_version >= "3.9" and python_version < "3.10"
zipp==3.15.0 ; python_version >= "3.9" and python_version < "3.10"


Please include a big warning about wiping of existing app gateway configuration

We are exploring the Application Gateway Ingress Controller feature and we found out that it actually wipes any existing configuration when it is kicked of.
Can you confirm it works this way?
So actually one will need to set up a dedicated app gateway to connect with Azure Kubernetes Service (AKS) Cluster's Application Gateway Ingress Controller (AGIC) feature.

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

ID: 94bdeded-846e-526c-8ce3-77ee36ffa852
Version Independent ID: 7d768d5c-0318-25f1-38f8-7a2ee15c1c41
Content: Tutorial: Enable Ingress Controller Add-On for existing AKS cluster with existing Azure Application Gateway
Content Source: articles/application-gateway/tutorial-ingress-controller-add-on-existing.md
Service: application-gateway
GitHub Login: @Caya
Microsoft Alias: caya

@cveld , Thanks for reaching out. We will investigate and update this thread.

@cveld , Apologies for the delay in response. when you deploy multiple clusters then it is necessary to enable an option called Shared Application Gateway when AGIC is used for multiple AKS clusters. By default, AGIC assumes full ownership of the Application Gateway it is linked to. AGIC version 0.8.0 and later can share a single Application Gateway with other Azure components. Else, Existing configurations will be overwritten.
I will be assigning this request to the content owner to provide a note on the document accordingly.

I am closing issues that have not been updated in over a year. I will cross reference and research them individually. I am recording each issue and compiling a list of articles to review. If you feel there is an urgent need to address something related to this GitHub issue, please open a new issue and I will reply in the new thread. Please also reference this GitHub issue number in the new issue. Thanks. #please-close


Fixed travis release yaml configuration. Fix for #340

Motivation
There was an extra empty line in travis.yaml that prevented the release binary to be uploaded to github.

@rdhabalia This should fix it for 1.18. Though can you manually upload the binaries for the 1.17.3 tag?

This should fix it for 1.18. Though can you manually upload the binaries for the 1.17.3 tag?
Yes, I will upload them but I don't think it will work with 1.18 because it didn't work with 1.17.3. Travis-build failed earlier for 1.17.3 because we have updated the key. So, I have deleted 1.17.3 tag and cherry-picked key-update-commit and then build passed.

Actually I have tried it in my local-branch when I noticed this extra line but it didn't upload the binary at that time. Not sure if other thing went wrong and it couldn't upload. Also I think yaml allows extra new line.
However, we can try it.

Actually I have tried it before in my local-branch when I noticed this extra line but it didn't upload the binary at that time. Not sure if other thing went wrong and it couldn't upload. Also I think yaml allows extra new line.

The upload is only done on git tags, and only from the yahoo/pulsar repo, not any other fork.

The upload is only done on git tags, and only from the yahoo/pulsar repo, not any other fork.

Yes, in that commit I had tried to create release with name: 1.12.1 and as I have travis-build on my fork so, I thought that travis-build should check in to my fork repo.
But hopefully, we wish this change will work 👍


132 transformer dynamically load as proto dependencies

To test this version, you can:

create a new project using our tooling (npx clear-npx-cache && npx @massalabs/sc-project-initializer@dev init my-sc && cd my-sc)
modify the main.ts file to add a function to export with our decorator. For ex:

@massaExport()
export function Hey(language: string, name: string): string {
  let greetings = 'Hello,' + language;
  return greetings + name + '!';
}

export function test2(): void {}

link your branch with as-transformer (go in package/as-transformer and do npm link then go in your project and do npm link @massalabs/as-transformer) now your project is using the as-transformer version of your branch
find how to configure the compiler to use as-transformer or simply use the command:
npx asc --transform /home/greg/tmp/tmp2/as/packages/as-transformer/dist/index.js  assembly/contracts/main.ts --target release --exportRuntime -t build/sc.wat -o build/sc.wasm
check that their is not error in the console and that the exported function(s) of or SC are in the "export" section int the build/sc.wat file

Ping me if all this is not clear :-)

It works on my side using absolute or relative path:
➜  my-sc npx asc --transform /home/greg/code/as/packages/as-transformer/dist/index.js  assembly/contracts/main.ts --target release --exportRuntime -t build/sc.wat -o build/sc.wasm
compiler mismatch: std/portable included twice
compiler mismatch: std/portable included twice
➜  my-sc npx asc --transform ../../code/as/packages/as-transformer/dist/index.js  assembly/contracts/main.ts --target release --exportRuntime -t build/sc.wat -o build/sc.wasm
compiler mismatch: std/portable included twice
compiler mismatch: std/portable included twice

this is the content of my maint.ts:
➜  my-sc cat assembly/contracts/main.ts
@massaExport()
export function SayHello(language: string, name: string): string {
  let greetings = 'Hello,' + language;
  return greetings + name + '!';
}

this is the content of my package.son:
{
    "name": "my-massa-sc",
    "version": "0.0.1",
    "description": "",
    "main": "index.js",
    "scripts": {
        "test": "asp --summary",
        "build": "npx massa-as-compile",
        "deploy": "npm run build && ts-node src/deploy.ts",
        "prettier": "prettier '**/src/**/*.ts' --check && as-prettier --check assembly",
        "prettier:fix": "prettier '**/src/**/*.ts' --write && as-prettier --write assembly",
        "lint": "eslint .",
        "lint:fix": "eslint . --fix",
        "fmt:check": "npm run prettier && npm run lint",
        "fmt": "npm run prettier:fix && npm run lint:fix"
    },
    "keywords": [],
    "author": "",
    "license": "ISC",
    "devDependencies": {
        "@as-pect/cli": "^8.0.1",
        "@assemblyscript/loader": "^0.25.2",
        "@massalabs/as-transformer": "^0.1.3-dev",
        "@massalabs/as-types": "^0.0.3-dev",
        "@massalabs/eslint-config": "^0.0.9",
        "@massalabs/massa-as-sdk": "^2.0.2-dev",
        "@massalabs/massa-sc-compiler": "^0.0.4-dev",
        "@massalabs/massa-sc-deployer": "^0.0.4-dev",
        "@massalabs/massa-web3": "^1.16.2-dev",
        "@massalabs/prettier-config-as": "^0.0.2",
        "@types/node": "^18.11.10",
        "as-proto": "^1.3.0",
        "as-proto-gen": "^1.3.0",
        "assemblyscript": "^0.25.2",
        "assemblyscript-prettier": "^1.0.7",
        "dotenv": "^16.0.3",
        "prettier": "^2.8.1",
        "ts-node": "^10.9.1",
        "tslib": "^2.4.0",
        "typescript": "^4.8.4"
    },
    "type": "module",
    "prettier": "@massalabs/prettier-config-as",
    "engines": {
        "node": ">=16"
    }
}

@0xSwapFeeder can you fix the CI ?


CLI doesn't handle spaces well

Probably the way we're invoking vim is not right and ignoring quoted arguments or something
requested by @alexwasserman

FYI - there's already #2210, but the app seems to handle spaces in file names ok, but the CLI doesn't

yeah I believe #2210 is from a time when the apps were discouraging spaces in their UX, but as we can't see those fields (encrypted) and people actually do want spaces (@CoreyCole & You?) in their names we're starting to move away from that incorrect assumption

\  doesn't work either


Updating Blog page footer #1185

Related Issue
None
Fixes: #1185
Description
This PR enhances the footer section by improving the layout, spacing, and styling for better readability and responsiveness across different screen sizes. The goal is to make the footer more visually appealing and user-friendly with modern design elements.

Increased Padding and Margin:

Added more space between footer elements to create a cleaner, less cluttered look.
Enhanced padding for overall section breathing room.

Font Adjustments:

Increased font sizes for better readability, especially for headings and links.
Used a secondary color for section headings to create contrast and improve visibility.

Hover Effects:

Added smooth hover transitions for links and social icons, including color changes and slight movements to improve interactivity.

Responsive Design:

Ensured that the footer layout adjusts well on mobile devices by stacking columns vertically and centering the content.
Adjusted the spacing and alignment of elements for smaller screen sizes.

Social Icons:

Increased icon size and added a scale effect on hover for better visual impact and consistency with the rest of the design.

Footer Bottom Section:

Softer border and text colors for a more refined look.
Improved text alignment and readability.

Type of PR

[X] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[X] I have made this change from my own.
[ ] I have taken help from some online resources.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

@PriyaGhosal  please merge this PR which fixed the enhancement of the footer on blog page

@amanreddy77 Your pull request has been successfully merged! Don't stop here—continue contributing by addressing more issues and aiming to become a top contributor. Exclusive swag awaits for those who go the extra mile!
Great contribution ! 🎉


Woff2 and Brotli updates

Woff2 build fails, will fix, please don't merge yet :)

Fixed.

Lets wait for the CI and merge


Support Prism as a Ruby parser

This PR introduces the parser_engine option to ProcessedSource to support Prism, as part of the RuboCop AST side effort towards addressing https://github.com/rubocop/rubocop/issues/12600.
Configuration
By default, analysis is performed using the Parser gem, so the default value for the newly added parser_engine is parser_whitequark:
ProcessedSource.new(@options[:stdin], ruby_version, file, parser_engine: :parser_whitequark)

This code maintains compatibility, meaning the traditional behavior is preserved:
ProcessedSource.new(@options[:stdin], ruby_version, file)

To perform analysis using Prism, specify parser_engine: :parser_prism:
ProcessedSource.new(@options[:stdin], ruby_version, file, parser_engine: :parser_prism)

The parameter name parser_prism reflects the original parser_prism which was the basis for Prism::Translation::Parser (now integrated into Prism): https://github.com/kddnewton/parser-prism
This is an experimental introduction, and some incompatibilities still remain.

[!NOTE]
As initially mentioned in https://github.com/rubocop/rubocop/issues/12600#issuecomment-1933657732,
the plan was to set parser_engine: prism.
However, the parser engine used in this PR is Prism::Translation::Parser, not Prism:
https://github.com/ruby/prism/pull/2419
Prism::Translation::Parser and Prism have different ASTs, so their migration will definitely cause incompatibility.
So, considering the possibility of further replacing Prism::Translation::Parser with Prism in the future,
it has been decided that it might be better not to use ParserEngine: prism for the time being.
ParserEngine: prism is reserved for Prism, not Prism::Translation::Parser.
Therefore, the parameter value has been set to parser_engine: parser_prism specifically for
Prism::Translation::Parser.
This means that the planned way to specify Prism in .rubocop.yml file will be ParserEngine: parser_prism,
not ParserEngine: prism.

Compatibility
The compatibility issues between Prism and the Parser gem have not been resolved. The failing tests will be skipped with broken_on: :prism:

https://github.com/ruby/prism/issues/2454 has been resolved but not yet released.
https://github.com/ruby/prism/issues/2467 is still unresolved.

Issues that will be resolved in several upcoming releases of Prism are being skipped with broken_on: :prism.
Anyway, RuboCop AST can be released independently of the resolution and release of Prism.

[!NOTE]
The hack in Prism::Translation::Parser for ProcessedSource needs to be fixed:
https://github.com/ruby/prism/blob/v0.24.0/lib/prism/translation/parser/rubocop.rb
If the above interface is accepted, a fix will be proposed on the Prism side.

Test
Tests for RuboCop AST with Prism as the backend can be run as follows:
bundle exec rake prism_spec

The above is the shortcut alias for:
PARSER_ENGINE=parser_prism TARGET_RUBY_VERSION=3.3 rake spec

RuboCop AST works on Ruby versions 2.6+, but since Prism only targets analysis for Ruby 3.3+, internal_investigation Rake task will not be executed. This task is only run with the Parser gem, which can analyze Ruby versions 2.0+.

Prism requires Ruby 2.7 or higher at runtime. The most straightforward solution would be to drop Ruby 2.6 from RuboCop AST's runtime support. I plan to open a PR to drop Ruby 2.6 from the runtime. Do you have any thoughts on this?

That's fine by me. Ruby 2.6's usage is quite low already and the upgrade that to 2.7 is trivial.

I like the PR overall - no concerns from me regarding the overall approach and the implementation. @rubocop/rubocop-core please take a look as well, given this is a major development.
@koic Did you get the chance to compare the performance with the new old and the new parser engine?

Did you get the chance to compare the performance with the new old and the new parser engine?

Here is an example of benchmark for my local development:
# bench.rb
require 'bundler/inline'

gemfile(true) do
  source 'https://rubygems.org'

  gem 'benchmark-ips'
  gem 'rubocop-ast', path: '/Users/koic/src/github.com/rubocop/rubocop-ast'
end

require 'rubocop-ast'

source = File.read(__FILE__)

Benchmark.ips do |x|
  x.report('Parser') do
    RuboCop::AST::ProcessedSource.new(source, 3.3, parser_engine: :parser)
  end

  x.report('Prism') do
    RuboCop::AST::ProcessedSource.new(source, 3.3, parser_engine: :parser_prism)
  end

  x.compare!
end

Although results may depending on the code analyzed, it has been observed that Prism tends to be faster:
$ ruby bench.rb
Fetching gem metadata from https://rubygems.org/..
 Great work, @koic! 🔥

Looks very to me 🚀

@bbatsov @marcandre Can you release this feature to move forward with https://github.com/rubocop/rubocop/pull/12724?

Sure, I'll do this right away.


affine versioned pairing supporting for BitVM

Description
This PR propose is to give caller an another more option to choose when do pairing. In current implementation, the coefficients of divisor line function is computed through projective coordinates as it's more efficient (than affine coordinates) when computing pairings, while it's not when verifying pairings (recursive snark). As Andrija and Liam stated in 5.2 section of On Proving Pairings.
So for supporting verifying pairings for BN254 in BitVM, I add one more option method for pairing.
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Wrote unit tests
[x] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the GitHub PR explorer

So this pairing computation results in another target group element?

So this pairing computation results in another target group element?

the test result proves that it's equal with current pairing result (same element of Gt), even so for the sake of consistency with script implementation in BitVM we need to a benchmark, this pairing in arkworks is my benchmark

Eh. Why then we need code that computes the same result in a supposedly slower way?

Eh. Why then we need code that computes the same result in a supposedly slower way?

Okay, let me introduce a naive and toy case to explain why we need that, what the benchmark actually mean.
If I want to implement a division algorithm for two numbers (whatever numbers is okay, even big integer) with javascript language, say a / b. I might need to benchmark to test if the algorithm is right. By now we do not have the same algorithm (a / b) implementation in C++, we only have the equivalence algorithm, say a * 1/b.
If use javascript(a / b) == c++(a * 1/b) in my unit test, someone else may argue that the algorithms are not consistent with each other, c++(a / b) is accurate benchmark, and this is what I want.

Eh. Why then we need code that computes the same result in a supposedly slower way?

PS: Most of the time, you are do computing pairings (in snark verifier), so projective is your option, if you are do verifying pairings, affine is your option. It's the best option for recursive snark.

I think what will happen with this PR is that it would be held off until the R1CS gadget for verifying affine pairing is done. If the value is the same, we do not need this in algebra, and the R1CS witness generation would be in R1CS.


Want to add some documentation

Want to add CODE_OF_CONDUCT.md , Contributing.md and also want to update your README.md

Want to add CODE_OF_CONDUCT.md , Contributing.md and also want to update your README.md

Assigned


Configurable timeout without using Polly

New Feature
Please let configurable timeout without using Polly provider.
Motivation for New Feature
Polly is not always needed.

@Deilan this would be a new feature, I will mark it as such but I do not have time to work on it at the moment.
However I would suggest just using Polly as I won't have time to do it anytime soon, unless you want to have a go yourself!

I know this is an old feature request, but I needed the same functionality. You can do this without having to do your own Ocelot fork/build. Copy and paste the HttpClientBuilder and HttpClientHttpRequester classes from the Github branch you are using into your project and rename the classes (MyHttpClientBuilder and MyHttpClientHttpRequester, for example).
In HttpClientHttpRequester change this line to create your custom HttpClientBuilder:
 var builder = new MyHttpClientBuilder(_factory, _cacheHandlers, _logger);
In your custom HttpClientBuilder, change the timeout to what you need:
 _defaultTimeout = TimeSpan.FromSeconds(600);
In startup.cs, add this AFTER the call to 'AddOcelot':
services.RemoveAll<IHttpRequester>();
Then, somewhere after that, add:
services.TryAddSingleton<IHttpRequester, MyHttpClientHttpRequester>();

@Deilan  Hi Michael!
Will New AddOcelot extensions in PR #1655 help you to overload Polly services in DI and inject your favorite ones?

@Deilan commented on Sep 7, 2018
Please let configurable timeout without using Polly provider.

We welcome you to contribute!
Feel free to reopen in future if you will have intention to contribute.


Error in psycopg2

After getting "[*] Completed initializing core docker", I run sudo ./docker-helper.py -ec "tp-link" "Archer_VR600v1_0.1.0_0.9.1_up_boot\(160217\)_2016-02-17_14.52.21.zip"  but I get the error
Traceback (most recent call last):   File "/home/asd/Desktop/FirmAE/./docker-helper.py", line 9, in <module>     import scripts.util as util   File "/home/asd/Desktop/FirmAE/scripts/util.py", line 4, in <module>     import psycopg2   File "/usr/lib/python3/dist-packages/psycopg2/__init__.py", line 104     connection_factory=None, cursor_factory=None, async=False, **kwargs):                                                   ^ SyntaxError: invalid syntax
The arrow is under "async".

Maybe the async syntax error is fixed on the latest psycopg2 version (please check the issue).
Can you check again by re-initializing the FirmAE docker?


would like to have RawVal to support adding comments as well

I see the ctyHandler be able to handle comment https://github.com/mercari/hcledit/blob/main/internal/handler/cty.go#L20
we'd like RawHandler for RawVal be able to accept comment as well https://github.com/mercari/hcledit/blob/main/internal/handler/raw.go#L21
thanks
i can contribute as well if approved

Sure! Happy to review a pull request for this. Please just request review from me or the other code owners on the PR.

@ryan-ph a quick update here https://github.com/mercari/hcledit/pull/127/files

Thanks for the contribution @piggybankwang!


Read additional module and theme folders from web.config, take 2

updated version of
https://github.com/OrchardCMS/Orchard/pull/5357
Should resolve #5019, #5241, #5354
Additional comma separated lists can be defined in web.config (example included).
Default is added to the list in any case.
Includes trimming, should ignore empty strings and duplicates.

I made some quick tests and it appears to be working very well.
One slightly related problem I noticed that for themes put under ~/OtherThemes Theme.png is not properly retrieved: e.g. http://localhost:30322/OrchardLocal/OtherThemes/Lombiq.PrettyGoodBootstrapBaseTheme/Theme.png will result in a 404 (and the same of course for other themes put there too) while other static files work (e.g. http://localhost:30322/OrchardLocal/OtherThemes/Lombiq.PrettyGoodBootstrapBaseTheme/Styles/site.css). This is because the original Themes folder contains a Web.config that allows to serve specifically these files. This may be something to document (that you need to copy it over if your theme folder is not under ~/Themes).

Thanks for testing,
Indeed a theme that are not under ~/Themes should have its own web.config and I would recommend its own project file too.
It should also be noted that if a project depth in the tree is changed than some of its references may need to be updaed. (for example moving ~/Modules/MyModule to ~/CustomerA/Modules/MyModule)

Updated as per comments from reviewers.

@qt1, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Can you check the merge conflicts?

merged with most recent 1.9.x

I am reluctant to include it in 1.9.2 directly, it can potentially break a whole site if a module is incorrectly loaded, or other modules are loaded where they weren't. We'll talk about it tomorrow during the triage. Otherwise, great work!

Tomorrow I am planning to attend a slightly different version of a triage namely CV2 live so I can't participate in the discussion.
To add confusion please see #5768 for an alternative that can be merged on dev instead.

@qt1 The other PR is closed. Please open the one that you want to have merged and close the other one.

I have prepared two options: This one - base on 1.9.x - which is a bit cleaner (and I am using it internally) and I prefer it - but would effect 1.9.2 so it should be tested more people for possible regressions;
The one base on dev would not effect 1.9.2 but has some extra files that probably got in due to synchronization and changes in dev/1.9.x that where made parallel to the preparation and related conflicts.
At the moment I am leaving the discussion about selecting variants to the orchard gods, and I am going to an infected concert instead :)

So where is the actual PR for dev ?

I'll prepare a new one, hopefully in a couple of days.

updated against current 1.9.x.

Now you can redo it and actually target dev as we discussed a long time ago ;)

Please find yet another a PR against dev #5973
I would recommend to use the current PR # 5604 (this PR) since 1.9.2 is already on a separate branch
and my tests where on the 1.9.x - so it should be better tested.
Please note Dev still has problems compiling (takes several rounds).

Why shouldn't we use the dev one? It can just be better.

My working branch is base on 1.9.x . I already have a few modules arranged in a separate directory using this PR. My personal testing and fixes will be done relative to 1.9.x.
Preparing an additional dev variant is double work for me so naturally I would prefer the PR be integrated to 1.9.x now.
In future will probably also be merged into dev next time 1.9.x is merged into dev.
BTW As far as I can tell PR is not breaking anything, so with 1.9.2 on a separate branch integrating it with 1.9.x seems like a low risk.
Please note the squashed variant is #5982


Error if schedule not set

Deployment fails if schedule is not set for task
serverless.yml
org: timpolyma
app: birdzview
service: birdzview-fargate
frameworkVersion: "3"

provider:
  name: aws
  runtime: python3.9
  region: eu-central-1
  ecr:
    images:
      python:
        path: ./
        file: Dockerfile

  vpc:
    securityGroupIds:
      - birdzview-sg
    subnetIds:
      - birdzview

fargate:
  memory: "4GB"
  cpu: 2048
  logGroupName: fargate-log-group
  tasks:
    test:
      image: python
      # error if not set
      # schedule: "rate(1 day)"

plugins:
  - serverless-fargate

error:
Deploying birdzview-fargate to stage dev (eu-central-1, "default" provider)

✖ Stack birdzview-fargate-dev failed to deploy (30s)
Environment: linux, node 16.11.0, framework 3.21.0, plugin 6.2.2, SDK 4.3.2
Credentials: Serverless Dashboard, "default" provider (https://app.serverless.com/timpolyma/apps/birdzview/birdzview-fargate/dev/eu-central-1/providers)
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues

Error:
CREATE_FAILED: TestService (AWS::ECS::Service)
Resource handler returned message: "Invalid request provided: CreateService error: Error retrieving subnet information for [birdzview]: The subnet ID 'birdzview' does not exist (ErrorCode: InvalidSubnetID.NotFound) (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 63c4ba55-a080-40e8-9ff3-4d5b43465d1c; Proxy: null)" (RequestToken: 236acdc6-f1e7-625c-e8dd-3aff8ae81613, HandlerErrorCode: InvalidRequest)

View the full error: https://eu-central-1.console.aws.amazon.com/cloudformation/home?region=eu-central-1#/stack/detail?stackId=arn%3Aaws%3Acloudformation%3Aeu-central-1%3A028655318971%3Astack%2Fbirdzview-fargate-dev%2F672a9e80-0c40-11ed-8e96-0646e2fbd7f4

Couldn't figure out, why SubnetID is a problem in that case.

birdzview does not look to be a valid subnet id, these should be the subnet-* id that AWS has supplied.

Did you manage to resolve this issue with a valid subnet id?

Yes, I am using the default subnet-id now. It works. Closing. :)


Node stuck and cannot participate (1/8 joiners have not yet joined after 5+ hours)

Detailed description here: https://casperlabs-team.slack.com/archives/C01ULKL8G8J/p1671003062388689
TODO:

make sure we're not overeager with banning
SRE: use refreshed trusted hash
verify restart frequency vs blocklist duration (10 min.?) - no sense in restarting while banned
check the logs of the other nodes to see if they banned the "stuck" node

The reason why this node is not joining is because the trusted hash that it's using to sync eventually becomes stale. Because the node is being restarted with the old trusted hash, it keeps trying to sync and gets rejected sync leaps and stops. It then gets restarted and repeats this behaviour indefinitely.
In order to prevent this from happening, when the node gets restarted, we should provide it with a different, newer trusted hash.
The TL;DR is that:

Node attempts to leap multiple times when first started
It takes a while to get the global state but the metrics show that it's progressing to download the global state
The node keeps leaping until at one point it failed to leap since the sync leap requests timed out
At this point the node shuts down which is normal behaviour
Node does not appear to be banned when this happens and does seem to have sufficient fully connected peers
Node restarts a few times until the trusted hash becomes too old, sync leap is progressing in this case, global state is being downloaded.
Other nodes get restarted as well but manage to catch up before the trusted hash becomes too old.

Aj confirms testing with latest trusted hash


JINR Tape output rules in need of redistribution

Impact of the bug
MSOutput (in partner with the P&R and DM team)
Describe the bug
The DM team reported that there are many output data placement rules - made by MSOutput - for JINR_Tape RSE, which have been stuck for many weeks (or even months). This has, at least, two negative consequences:

workflows cannot get archived (they will remain in announced state until those Tape rules have been satisfied)
and, there is no archival copy of those datasets, increasing chances of data loss

How to reproduce it
None
Expected behavior
What we discussed over slack (P&R, site-info channel) is the following:

the DM team has identified all the problematic containers
the DM team (Fernando?) will create new Tape rules for all those containers
the DM team will hand a list/json of container name and the new rule id over to the WMCore team
the WMCore team will find which workflows (only the original/first workflow) created those containers
the WMCore team will fetch those workflows MSOutput records, update the relevant Tape container rule by swapping it by the new rule id provided by the DM team, and finally updating that record in MongoDB

We better keep that list of workflow/containers/rule ids persisted somewhere, such that we can confirm that those workflows start moving to archived, as Tape rules started getting satisfied.
We might take the opportunity and provide a script to fetch and update those mongodb records. No need to make that too generic, but really more like a baseline for future similar actions.
Additional context and error message
None

I know that @todor-ivanov is following up on this but don't forget to update the issue here to say what specifically we're waiting on before we can move this forward.

Thanks @klannon  I am following this with Fernando and Data Management Team now.

I am uploading here the list of rules  as provided by DataManagement:
JINR_Tape_Relocation_Rules.txt

And here I link the comment from the PR pointing to the operational logs.

Closing this issue out as well. Further information at: https://github.com/dmwm/WMCore/pull/11221
Thanks Todor.


Onagre launch requires working theme

I'm keen to use onagre, because it seems exactly what is needed for wayland,   and it looks like its well conceived and promising.
I had been a long time user of rofi ( and recently LeBonn's version of Rofi for wayland).
I haven't been able to launch it however. I am using the arch package. The README states that onagre will fall back on the default theme if none is provided, but for me, launch fails with the  error message:
Unable to load user theme: Unable to find theme settings file /home/user/.config/onagre/theme.toml
Installing the default theme in ~/user/.config/onagre/theme.toml, I receive the error :
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.11.0/src/backend/direct.rs:204:9
When I provide provide any of the themes given as examples, I receive errors concerning unknown variables 'width' and 'height'.
I am surprised because I understand people are able to use Onagre. Advice that may point me in the right direction to get it up and running would be gratefully received.
I do understand it is early days yet!
Kind Regards,
John

Hey @plum thank you for trying onagre.
I have just updated the AUR package, can you try again and let me know how it goes.
If it still fails can you try to install via cargo :
cargo install --git https://github.com/oknozor/onagre

You will need to install rust to get it.
If this still fail via cargo. This might be a hardware issue and I will have to open an issue in iced.
Let me know how it goes.

Thank you kindly OKnozor, for prompt suggestions in reply.
Having installed via cargo, I receive this error when running theme.toml:
Unable to load user theme: Theme format error : unknown field width, expected one of background, text_color, border_color, border_radius, border_width, padding, lines``
A difference this time is that a terminal window was actually launched, with a white background.
If I am to assume it is a misleading error report, and if whayt you suggst may be true, tha tit is a hardware issue, then for what reason could that be? I cannot imagine.
Set up: Running arch linix-lts 5.10.78-1 (latest version) on a thinkpad T440p
Regards, John

Since onagre is starting, this not a hardware issue.
I guess you took this theme example which is outdated and should be replaced with a correct one.
Can you try with one of the theme from docs/theme_examples ?

Can you try with one of the theme from [docs/theme_examples]

I installed the arc theme and the jetbains mono font for convenience and ran:
$ onagre -t ~/.config/onagre/theme-nord.toml
A terminal was launched with a dark background, and received the following error.
Unable to load theme config : Config format error : unknown field icons, expected modes``
Some more results:
⏎     onagre -t ~/.config/onagre/nord-rounded.toml
Unable to load theme config : Config format error : unknown field `icons`, expected `modes`

onagre -t ~/.config/onagre/simple-theme.toml
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: NotFound', src/style/font.rs:23:67
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

~ ❯❯❯ onagre -t ~/.config/onagre/murz-theme.toml
Unable to load user theme: Theme format error : unknown field `height`, expected one of `background`, `text_color`, `border_color`, `border_radius`, `border_width`, `padding`, `lines`

Regards,
John

@plum looking at the error, it's obvious you are running an older version of onagre.
Can you remove your pacman/aur-helper cache and reinstall from the AUR ?

I uninstalled onagre using cargo, from ~/.cargo.
I ran yay -Sc and,  yay -S onagre-git.
The results below  with specified themes indicate that local cargo installation is interfering. Deleting  ~/.cargo  made no difference, which seems strange. I even cleared my system ram cache, and restarted. Not sure how to proceed now.
~ ❯❯❯ onagre
Unable to load user theme: Theme format error : unknown field `height`, expected one of `background`, `text_color`, `border_color`, `border_radius`, `border_width`, `padding`, `lines`
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/chuee/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.11.0/src/backend/direct.rs:204:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
~ ❯❯❯ onagre -t ~/.config/onagre/nord-rounded.toml
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/chuee/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.11.0/src/backend/direct.rs:204:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
~ ❯❯❯ /usr/bin/onagre -t ~/.config/onagre/murze-theme.toml
Unable to load user theme: expected newline, found an identifier at line 10 column 24 in .config/onagre/murze-theme.toml
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/chuee/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.11.0/src/backend/direct.rs:204:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@plum have just double checked with another laptop and I cannot reproduce your issue.
I guess you have the correct version installed but somehow an old version is still used on your $PATH or some build cache still remains on your system.
Can you uninstall everything again an check there is no onagre bin remaining on your path :
❯ which onagre
onagre not found

Once it's done look for any remaining build cache. I just ran yay -Sc and I can confirm some cached build where still not removed after that. You can locate them with fd or find (i used fd here) :
❯ cd /

/🔒
❯ fd onagre
var/lib/archbuild/extra-x86_64/okno/build/onagre-git
var/lib/archbuild/extra-x86_64/okno/var/lib/pacman/local/onagre-git-0.1.0.r116.g6168926-1
var/lib/archbuild/extra-x86_64/okno/usr/bin/onagre

Then remove them :
sudo rm -rd var/lib/archbuild/extra-x86_64/okno/build/onagre-git
sudo rm -rd var/lib/archbuild/extra-x86_64/okno/var/lib/pacman/local/onagre-git-0.1.0.r116.g6168926-1
sudo rm -rd var/lib/archbuild/extra-x86_64/okno/usr/bin/onagre

Once you are absolutely sure your system has no more cached build you can run yay -S onagre-git.
If you are actually installing the correct version you should see a cargo build during the installation process and It should take
a little longer than the previous cached installation you made :
   Compiling iced v0.3.0 (https://github.com/hecrj/iced#20177e42)
   Compiling onagre v0.1.0 (/home/okno/.cache/yay/onagre-git/src/onagre)
    Finished release [optimized] target(s) in 3m 33s

For the sake of testing make sure you delete everything under $HOME/.config/onagre/, and create an empty config :
rm -rd $HOME/.config/onagre
mkdir $HOME/.config/onagre
touch $HOME/.config/onagre/theme.toml
touch $HOME/.config/onagre/config.toml

Now let's add a working theme :
❯ cat $HOME/.config/onagre/theme.toml
icon_theme = "Papyrus"
font = "JetBrains Mono,JetBrains Mono Medium"
size = [800, 280]
font_size = 18
background = "#2E3440"
border_color = "#00000000"
border_radius = 0.0
border_width = 0.0

[rows.lines.default]
background = "#2E3440"
text_color = "#81A1C1"
padding = 5

[rows.lines.selected]
background = "#2E3440"
text_color = "#EBCB8B"
padding = 5

[scrollable]
scrollbar_width = 0
scroller_width = 0

[search.bar]
background = "#3B4252"
value_color = "#8FBCBB"
placeholder_color = "#8FBCBB"
border_color = "#00ff00ff"
selection_color = "#fcfbfbff"
text_width = "fill"

[search]
background = "#3B4252"
height = 30

Let me know how it goes.

Thanks Oknozor.
I followed your steps. Actually that was a repeat of what I had done previously, and reported in the last post. Nontheless I repeated. There were no build cache remaining, I checked this time.
I'll show what the problem is precisely:
I had previously deleted my ~/cargo directory, but installing onagre-git installs a new ~/.cargo directory:
❯❯❯ onagre
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/chuee/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.11.0/src/backend/direct.rs:204:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

 ls /home/chuee/.cargo/registry/src/
github.com-1ecc6299db9ec823

~ ❯❯❯ sudo rm -R ~/.cargo

~ ❯❯❯ ls home/chuee/.cargo/registry/src/
ls: cannot access 'home/chuee/.cargo/registry/src/': No such file or directory

~ ❯❯❯ onagre
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/chuee/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.11.0/src/backend/direct.rs:204:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

In calling onagre, somehow, contents of the former (now absent) directory ~/.cargo is being referenced.
Restarting and clearing system cache  doesn't remove the problem.
Any ideas on this? I don't myself understand the meaning of 'Error in Surface::configure: invalid surface',

Can you copy the output of RUST_LOG=debug RUST_BACKTRACE=1 onagre ?

Sure I have attached  here in a file:
onagre-rust_log.txt
Thanks,
John

@plum I don't know how to solve this so I created an issue in iced. Let's wait and see.

@plum I don't know how to solve this so I created an issue in iced. Let's wait and see.

Fair enough. Thanks, I'll be patient. We can consider it as an issue raised towards useful progress overall, ironing out any potential problems ahead.
I researched  mesa/intel/linux default set ups, especially concerning i915 vulkan drivers and all  seems to be correct with arch and, likewise on my setup.
Here I found the best overview : [https://www.askwoody.com/forums/topic/mesa-20-arrives-good-news-for-intel-graphics-users-on-linux/] on gpu drivers for intel on wayland.
Regards,
John

@plum Any chance you could try the wgpu examples? If the issue is there, then you should probably open a bug report there.

@plum Any chance you could try the wgpu examples? If the issue is there, then you should probably open a bug report in their repository.

OK hecrj, I'm working on it now. I assume I dont need to run Vulkan's Validation Layers for applicaiton development, an dI shoul drun the wgpu examples only?  Information on the Vulkan's Validation Layers here:
https://github.com/gfx-rs/wgpu/wiki/Getting-Started

Hi,
The (shortened) results are in this file: I believe there is an issue there:
onagre-tests.md

Hello @plum I think you should open an issue in wgpu and maybe link it to this issue.

OK Will do Oknozor.

Good news, I've solved the problem by installing vulkan-intel from the main arch repository.
I am surprised  because nowhere have I found that this should be necessary, and all the indications are that the i915 wayland driver is built in to kernel, and should be sufficient. So I wont be apologising for that! I had no prior such warnings in running wayland for several months.  I have yet to find out what is happening with the drivers.
Running $ RUST_LOG=debug RUST_BACKTRACE=1 onagre &> onagre-rust_log-02.txt
I find the following lines 15- 20 from the  previously found errors before installing vulkan-intel have vanished:
15 [2021-11-26T21:01:51Z INFO  wgpu_hal::vulkan::instance] Unable to find extension:               VK_KHR_surface
  16 [2021-11-26T21:01:51Z INFO  wgpu_hal::vulkan::instance] Unable to find extension:               VK_KHR_xlib_surface
  17 [2021-11-26T21:01:51Z INFO  wgpu_hal::vulkan::instance] Unable to find extension:               VK_KHR_xcb_surface
  18 [2021-11-26T21:01:51Z INFO  wgpu_hal::vulkan::instance] Unable to find extension:               VK_KHR_wayland_surface
  19 [2021-11-26T21:01:51Z INFO  wgpu_hal::vulkan::instance] Unable to find extension:               VK_KHR_get_physical_device_properties2
  20 [2021-11-26T21:01:51Z WARN  wgpu_hal::vulkan::instance] create_instance:                        VkError(ERROR_INCOMPATIBLE_DRIVER)

The same error occurs however when running wpgpu --example conservative-raster (I suspect this is due to incomlpete implementation of Intel, as per waning when running onagre:

| ¦Running target/debug/examples/conservative-raster
thread 'main' panicked at 'Adapter does not support required features for this example:         CONSERVATIVE_RASTERIZATION', wgpu/examples/conservative-raster/../framework.rs:147:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
>> onagre
MESA-INTEL: warning: Haswell Vulkan support is incomplete

Should other find themselves with similar problems, this effort may be useful to them.

Onagre looks nice. Keep up the good work, and good luck!  (:+1:

@plum thanks your patience !

I just installed the AUR package and would say this is still an issue.  The logs say failing to parse the theme file is an ERROR. Not a "warning", not "info", it's an "ERROR" not to have a theme file:

ERROR onagre::app::style: Failed to parse theme "/home/mark/.config/onagre/theme.scss": Failed to open config file

If the theme file does not exist and that's OK, it should not attempt to be parsed and not emit this error. It could still be useful to log:

INFO: "/home/mark/.config/onagre/theme.scss" was not found, falling back to default theme.

@markstos thanks for your input but this is already fixed upstream. the AUR package is outdated and I am not the maintainer. Please wait for a stable release or install onagre from source.


A parenthesis omitted in Seccomp.md

A parenthesis omitted in Seccomp.md

LGTM 🐯
/cc @thaJeztah

LGTM thanks!


Rename worldwide news story sub type

Changes to world-news-story as wide was considered redundant in this context and world-news-story is consistent with the non-world flavour.
Trello

LGTM once 🍏


Update customer-key-tenant-level.md

Correcting information related to DEP behavior and cmdlets.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

Please unsubscribe me from your mailing list
On Wed, Mar 10, 2021 at 5:59 PM KC Cross @.***> wrote:

Merged #4274
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4274 into
public.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4274#event-4439797418,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOGLPBYFDHWQ3NRGYKK6BTDTC7TUVANCNFSM4YKNWVZQ
.


Captcha filenames should be sha1 of timestamp and word

Hi,
Currently, captcha helper uses microtime function output as filename. I think we can find a better approach to this, so there is no logic exposed to users.
One of them, which is this pull request, is to save the captcha filenames as a SHA1 of concatenation between timestamp (and not micro-timestamp - see below) and the word itself.
Based on that, usage of microtime() is no longer needed here; simple ints generated by time() should be enough, as the deletion from this pull request uses filemtime function to generate the file timestamp of creation, and by this way we will know which files are "expired" and can be deleted. Also, let's be honest: microseconds aren't the most realistic approach when talking about captcha files expiration.
This pull request also solves a problem where deletion of old files didn't occur on png files, since there were checked only jpg-ending files, and the captcha can generate png files too, if jpg generation is not available.

I don't see how the current behavior is bad, nor how this is an improvement.

Except for the fix of file deletion (searching for png files too), when exposing a numeric-named file to users, they may try to find other files as well by changing those numbers. Also saving information which is available from machine filesystem, in the filename, is not desired too, I think.
I didn't say the current behavior is bad, but only that there may be a better option to it :)

I'd accept a fix for the png files deletion thing that you've found, but the rest is your personal preference rather than objectively an improvement.

Very well, then.
I will close this pull request and make another one during today evening.
Regards,

Before you do, please go through our styleguide first. Your patch here didn't comply with it.