text:
Bold Text Support

Went through all the files and added all the stuff needed for bold text, it probably won't work, this is my first time coding in JavaScript or using Github, was just trying to get a feel for GitHub and thought this would be a cool feature for atom-clock.

Even if this won't get accepted can you guys just look and see If I did it correctly or what I messed up?

Most of what you've done seems correct however there is a syntax error in atom-clock.js here  which prevents any of the tests from passing.
Your code is this:
if(this.showBoldText)
  this.element.appendChild(this.timeElement.bold())
}
else{
  this.element.appendChild(this.timeElement)
}

The syntax error is caused by a missing { on the first line, it should be this:
if(this.showBoldText) {
  this.element.appendChild(this.timeElement.bold())
} else {
  this.element.appendChild(this.timeElement)
}

Oh I should've noticed that, however im pretty sure you meant to say atom-clock-vew.js as that is where that code is. Another question, is it fine If I do the "bolding" in atom-clock-view.js or should I do it where the others seem to have done it in atom-clock-view-spec.js?

I've looked through your code a bit more and it seems you've written a few pieces of code but they aren't 'joined up'. For example you've made an entry in the menu bar but there is no function to respond to it being clicked, and you add the .atom-clock-bold class yet there is no style using it so it has no effect.
Also, you seem to be trying to make the text bold in two different ways which are incompatible with each other. Using .bold() in drawElement() tries to make the text bold with HTML but .atom-clock-bold would use CSS/LESS.
I understand you may have made a lot of effort with this feature and it may be your first contribution however I don't think the feature you are proposing would really be needed. Users can make the text bold themselves using their styles.less file and the .atom-clock-time selector.

Oh okay, well I guess there is no point in trying to fix the issues then, thanks for all the help though. I really appreciate it a lot.

Thank you for the effort you put in the request. Happy to help in your first GitHub experience!
As @frasertmay pointed out, the first step before even getting down to the code should be checking whether the feature you're aiming to code isn't there already. In this particular case, the CSS selectors exposed by the class allow you to edit the clock exactly the way you wanted.
Beside the technical issues with the code itself, that @frasertmay already explained, another minor issue would be to conform your code with the style and formatting that is already in place. Also, you can run the specs locally, so obvious mistakes like a missing bracket will be easily spotted.
Hope this helps, and thank you for the PR!

If you are interested in how you could've made this work, please see my commit here.
I just tidied up your code and added a couple of bits to tie it all together so it now toggles the .atom-clock-bold class. Currently there is no style associated with that selector so whilst it does not make the text appear in bold it wouldn't be a difficult task to add that.
The main missing part was not adding a callback for the command triggered by the menu item which is done like this:
this.subscriptions.add(atom.commands.add('atom-workspace', {
  'atom-clock:toggle': () => this.toggle(),
  'atom-clock:utc-mode': () => atom.config.set('atom-clock.showUTC', !this.showUTC),
  'atom-clock:boldText': () => atom.config.set('atom-clock.showBoldText', !this.showBoldText)
}))

This listens for the command and sets the config value to the opposite of its current value (i.e. toggling it)
The other important part was setting the bold text class in the initialize() function which is pretty much what you were trying to achieve in drawElement() before.
With respect to your question about whether or not to do the "bolding" in atom-clock-view.js or atom-clock-view-spec.js: the files in the spec folder are all tests, they aren't part of the plugin itself, so any functionality would be done in atom-clock-view.js and you would test that it works in atom-clock-view-spec.js.
If you have any other questions please don't hesitate to ask!

Oh okay, this won't be my last time, I will learn more about javascript and atom and I will add something actually useful to atom-clock, thanks for all the help guys!

I look forward to it! 👍

authors: b3by conorpo frasertmay


text:
Use commentstring  as fallback

This way users don't need to set the comment by hand cause most of the time it's defined in a plugin for language.

I actually just went ahead and applied the changes myself, I'll test this out now and if it works I'll merge.

I actually just went ahead and applied the changes myself, I'll test this out now and if it works I'll merge.

Merged! 🎉
Thanks again for this PR, it saved me a lot of time.

Merged! 🎉
Thanks again for this PR, it saved me a lot of time.

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
add an unsupported status for gitmoji-cli

Here is the tool https://github.com/carloscuesta/gitmoji-cli
and the current status https://github.com/carloscuesta/gitmoji-cli/issues/893

Thanks!


text:
Villages can generate floating.

Village buildings, and other structures that are spread over a wide area, can often generate floating.
Vanilla Minecraft generates padding using a pre-calculated noise table, but it seems like this was written for current vanilla world gen in mind, and simply adapting it for Beta world gen will not work, not without obvious artifacts.  Not sure how to go about fixing it..

Partially resolved for a little while now, padding is just generated underneath structures.  Clunky, but it works.

source: gharchive/issue


text:
为什么我部署了之后就可以直接聊天了？我的apikey都还没添加呢。

Additional context
我按照README中的Vercel部署了之后，打开Vercel提供的链接，直接就可以聊天成功了。 可是代码中没有任何的apikey呀，所以这个成功聊天用的是哪个apikey？有点不理解。有人可以给解释下吗？感谢。

盗号了?

authors: GreysonHYH whengu

repo: babaohuang/GeminiProChat


text:
Fix to convert hash token.

Fixed #752
This pull request makes the hash token of the class private field to be converted to the token specification of ESLint.

looks good, does it cause issues with specific rules with this change? I assume we will have further changes

@hzoo Thank you for quickly merging this PR!

authors: hzoo ota-meshi

repo: babel/babel-eslint

license: mit

license_source: bigquery


text:
add babel-jscs

https://github.com/babel/babel-library-boilerplate/issues/172
Need to temporarily disable validateQuoteMarks until https://github.com/jscs-dev/babel-jscs/issues/1 is fixed. (Or should we wait till I try to fix that?, although the .eslintrc has the quotes rule covered as well.)
Didn't add any other rules.

@hzoo, thanks for this PR, and I'm sorry I haven't looked into this sooner! I still want to compare ESlint and JSCS and see if I still want to include both in the repo.

Actually, @hzoo, it looks like as of 2.0.0, JSCS uses this by default when esnext is true? I just updated this library to use JSCS 2.0, so I'm gonna close 'cause it seems like that's the case.
Lmk if I'm wrong and I'll reopen.

Yeah your good then :+1:
On Thu, Jul 30, 2015, 2:50 AM James Smith notifications@github.com wrote:

Actually, @hzoo https://github.com/hzoo, it looks like as of 2.0.0,
JSCS uses this by default when esnext is true? I just updated this
library to use JSCS 2.0, so I'm gonna close 'cause it seems like that's the
case.
Lmk if I'm wrong and I'll reopen.
—
Reply to this email directly or view it on GitHub
https://github.com/babel/babel-library-boilerplate/pull/177#issuecomment-126203883
.

authors: hzoo jmeas

repo: babel/babel-library-boilerplate


text:
Add Blog post: Babel <3 React

I quickly wrote up this blog post to post tomorrow. @sebmck thoughts?

:+1:

Releasing

authors: sebmck thejameskyle


text:
Update README.md reference for AoA pred

Manuscript for AoA prediction was accepted to Cognitive Science, updating reference accordingly.

Congrats on the acceptance! Merged. :)

authors: aaronmueller evaportelance

repo: babylm/evaluation-pipeline


text:
Closes almost all of the open tabs after a crush during search

Always when i'm typing "oned", exactly when I type 'd', it closes lots of tabs (from 5 to 10) and the counter of opened tabs gets crazy (from 30 jumps to 4) while there still remain more than 4 tabs opened. Its very dissapointing as some times they cannot be opened again with Ctrl-shift-T and finding them in the history is very difficult sometimes.

That's strange, is it possible that the "Close all displayed tabs shortcut" keyboard shortcut option has been mapped to 'd' rather than ctrl + shift + d?

I thought unchecking all checkboxes will disable it :facepalm . Thx, I think that unchecking them AND deleting the 'd' will do the job.

I think there is a bug here. I have them all unchecked, and whenever I search in the box it closes all tabs.

authors: babyman juliancrg vjpr

repo: babyman/quick-tabs-chrome-extension


text:
Nodes Manager

The Problem
Today we don't have a dedicated component in the Requester node that manages the compute nodes in the network. We only have a transient NodeInfoStore that discovers compute nodes through gossiping, and evict nodes that stop heartbeating for over 10 minutes. This state is transient, will be lost when the Requester node is restarted, and not possible for operators to interact with, such as draining or manually  marking a node as unhealthy.
In addition to that, we don't have a mechanism today to schedule daemon jobs on newly joined compute nodes that match the job selection criteria of existing daemon jobs, or when a compute node changes its labels to match or no longer match existing daemon jobs.
Requirements

As an operator, I want to have the power to manually approve compute nodes before they join the network, ensuring better control and security.
As an operator, I need a feature that allows for the auto-joining of pre-authorized compute nodes, eliminating the need for manual intervention.
As an operator, I want to mark certain nodes as ineligible for new job placements, while existing jobs on these nodes can continue to run uninterrupted.
As an operator, I want to drain nodes when necessary and have Bacalhau re-schedule the jobs to other nodes.
As an operator, I want the ability to add labels to nodes from the control plane and override any labels that the compute nodes have set themselves.
As an operator, I need to set the criteria for timeouts and missed heartbeats that will determine when a node is considered in 'unknown' state.
As an operator, I need to set the criteria for timeouts and missed heartbeats that will determine when a node is considered 'unhealthy'.
As an operator, I want the flexibility to set these timeout and heartbeat thresholds at individual node levels, for groups of nodes, or as default settings for any nodes not specified.
As a user, I expect Bacalhau to automatically reschedule 'batch' and 'service' jobs if their nodes are marked as unhealthy.
As a user, I want Bacalhau to mark the execution of 'ops' jobs as failed if their nodes are flagged as unhealthy.
As a user, I want Bacalhau to schedule daemon jobs on new compute nodes that join the network and match selection criteria of existing jobs
As a user, I want Bacalhau to evict daemon jobs on existing compute nodes if their labels are updated to no longer match existing jobs

The Proposal

The proposal is to have a dedicated NodeManger component inside the Requester node that persists the state of compute nodes, managers their lifecycle, and expose APIs to allow operators to query and mutate the nodes.
The NodeManager will also be responsible for queueing new evaluations for daemon jobs if new nodes join, or their labels are updated.
The NodeManager shall persist stable info about compute nodes, such as their state, labels and supported engines, and store in-memory always changing metadata, such as available resources

Open Questions

Evaluate the need for an explicit RegisterNode API that compute nodes shall call when they start up and want to register with a requester node, instead of just always publishing their info.

Reference: #355

Duplicate of https://github.com/bacalhau-project/bacalhau/issues/3945

repo: bacalhau-project/bacalhau


text:
🛑 SM Service is down

In f494df6, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in a78889a.

repo: bachmannschumacher/upptime


text:
🛑 SM Service is down

In 39434af, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 44666d2 after 14 minutes.


text:
🛑 SM Service is down

In 110bc55, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 5102193.


text:
🛑 SM Service is down

In 889f9ea, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 40d941d.


text:
Restrict backstage access to only specified memebers from a Github

Discussed in https://github.com/backstage/backstage/discussions/12719

Originally posted by prasoon-pxc July 19, 2022
I have setup Github App auth providers in backstage for authentication purpose but now I want to restrict only users to access backstage which is members of my github organizations? How it can be done

I would suggest that right now backstage is not mature enough to handle authentication but for the workaround , if you have setup Github Auth providers then use sign in identities and resolvers:
Here is the Detailed Steps:
Import Your Github Organizations user data in Backstage
-- First import your Github organizational Data from GitHub on your Backstage identity  , link for the ref GitHub Organization Data
-- If you are unable to do above steps than specify your users list manually in Backstage:
cd projectrepo
touch /examples/org.yaml

-- Create User like that in above org.yaml file(keep in mind that user should be matched with Github user identity)
apiVersion: backstage.io/v1alpha1
kind: User
metadata:
name: guests
spec:
memberOf: [guests]
apiVersion: backstage.io/v1alpha1
kind: User
metadata:
name: githubuser1
spec:
memberOf: [guests]
apiVersion: backstage.io/v1alpha1
kind: User
metadata:
name: githubuser2
spec:
memberOf: [guests]
apiVersion: backstage.io/v1alpha1
kind: Group
metadata:
name: guests
spec:
type: team
children: []

After that You need to change auth.ts file to enable github auth resolver:(packages/backend/src/plugins/auth.ts)
 github: providers.github.create({
        signIn: {
         - /* resolver(_, ctx) {
          -  const userRef = 'user:default/guest'; // Must be a full entity reference
          -  return ctx.issueToken({
             - claims: {
             -   sub: userRef, // The user's own identity
              -  ent: [userRef], // A list of identities that the user claims ownership through
              -},
            -});
          -},*/
          // Uncomment Below Line to enable Resolver(It matches github user name with local backstage user identity and then generate the token for it)
           + resolver: providers.github.resolvers.usernameMatchingUserEntityName(),
        },
      }),

This Should enable basic authentication but I would suggest to choose something external for authentication

repo: backstage/backstage


text:
🐛 Bug Report: Slowness with Azure Authetification

📜 Description
After X page refresh or during the first login, Azure authentication can take up to 30 seconds to complete the query GET /api/auth/microsoft/refresh?optional&env=azure.  This behavior does not apply to all requests but after like 5? requests.
Our authentication setup closely follows the guidelines provided in the documentation: docs/auth/microsoft/provider.md.
Additionally, we have implemented this middleware as described in the following tutorial: contrib/docs/tutorials/authenticate-api-requests.md.
👍 Expected behavior
It should refresh the token/session faster and redirect user to desired route path.In the browser's network tool, we can see that the API takes up to 30 seconds:

👎 Actual Behavior with Screenshots
The user is waiting on a loading page.
👟 Reproduction steps

Clear browser cache or in incognito mode

2a. First login can be slow
or
2b. Refresh a Backstage page several times
📃 Provide the context for the Bug.
[1] 2023-11-03T15:31:48.039Z auth info Issuing token for user:default/user, with entities user:default/user,group:default/cloud_admin_azure,group:default/user_group, type=plugin component=token-factory
[1] 2023-11-03T15:31:48.040Z backstage info ::1 - - [03/Nov/2023:15:31:48 +0000] "GET /api/auth/microsoft/refresh?optional&env=azure HTTP/1.1" 200 - "http://localhost:3000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 Edg/118.0.2088.76" type=incomingRequest

🖥 Your Environment
Database container image: bitnami/postgresql:16.0.0-debian-11-r14

OS:   Linux 5.15.90.1-microsoft-standard-WSL2 - linux/x64
node: v20.9.0
yarn: 4.0.1
cli:  0.23.1 (installed)
backstage:  1.19.6

Dependencies:
  @backstage/app-defaults                                          1.4.4
  @backstage/backend-app-api                                       0.5.7
  @backstage/backend-common                                        0.19.8
  @backstage/backend-dev-utils                                     0.1.2
  @backstage/backend-openapi-utils                                 0.0.5
  @backstage/backend-plugin-api                                    0.6.6
  @backstage/backend-tasks                                         0.5.11
  @backstage/catalog-client                                        1.4.5
  @backstage/catalog-model                                         1.4.3
  @backstage/cli-common                                            0.1.13
  @backstage/cli-node                                              0.1.5
  @backstage/cli                                                   0.23.1
  @backstage/config-loader                                         1.5.2
  @backstage/config                                                1.1.1
  @backstage/core-app-api                                          1.11.0
  @backstage/core-components                                       0.13.7
  @backstage/core-plugin-api                                       1.7.0
  @backstage/dev-utils                                             1.0.22
  @backstage/errors                                                1.2.3
  @backstage/eslint-plugin                                         0.1.3
  @backstage/frontend-app-api                                      0.2.0
  @backstage/frontend-plugin-api                                   0.2.0
  @backstage/integration-aws-node                                  0.1.7
  @backstage/integration-react                                     1.1.20
  @backstage/integration                                           1.7.1
  @backstage/plugin-api-docs                                       0.9.12
  @backstage/plugin-app-backend                                    0.3.54
  @backstage/plugin-app-node                                       0.1.6
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.0
  @backstage/plugin-auth-backend-module-github-provider            0.1.3
  @backstage/plugin-auth-backend-module-gitlab-provider            0.1.3
  @backstage/plugin-auth-backend-module-google-provider            0.1.3
  @backstage/plugin-auth-backend-module-oauth2-provider            0.1.3
  @backstage/plugin-auth-backend                                   0.19.4
  @backstage/plugin-auth-node                                      0.4.0
  @backstage/plugin-catalog-backend-module-ldap                    0.5.21
  @backstage/plugin-catalog-backend-module-msgraph                 0.5.13
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.3
  @backstage/plugin-catalog-backend                                1.14.0
  @backstage/plugin-catalog-common                                 1.0.17
  @backstage/plugin-catalog-graph                                  0.2.37
  @backstage/plugin-catalog-import                                 0.10.1
  @backstage/plugin-catalog-node                                   1.4.7
  @backstage/plugin-catalog-react                                  1.8.5
  @backstage/plugin-catalog                                        1.14.0
  @backstage/plugin-cost-insights-common                           0.1.2
  @backstage/plugin-cost-insights                                  0.12.14
  @backstage/plugin-events-node                                    0.2.15
  @backstage/plugin-github-actions                                 0.6.6
  @backstage/plugin-graphiql                                       0.2.55
  @backstage/plugin-home-react                                     0.1.4
  @backstage/plugin-home                                           0.5.9
  @backstage/plugin-kubernetes-backend                             0.13.0
  @backstage/plugin-kubernetes-common                              0.7.0
  @backstage/plugin-kubernetes-node                                0.1.0
  @backstage/plugin-kubernetes-react                               0.1.0
  @backstage/plugin-kubernetes                                     0.11.0
  @backstage/plugin-org                                            0.6.15
  @backstage/plugin-permission-backend                             0.5.29
  @backstage/plugin-permission-common                              0.7.9
  @backstage/plugin-permission-node                                0.7.17
  @backstage/plugin-permission-react                               0.4.16
  @backstage/plugin-proxy-backend                                  0.4.4
  @backstage/plugin-scaffolder-backend                             1.18.1
  @backstage/plugin-scaffolder-common                              1.4.2
  @backstage/plugin-scaffolder-node                                0.2.7
  @backstage/plugin-scaffolder-react                               1.5.6
  @backstage/plugin-scaffolder                                     1.15.1
  @backstage/plugin-search-backend-module-catalog                  0.1.10
  @backstage/plugin-search-backend-module-pg                       0.5.15
  @backstage/plugin-search-backend-module-techdocs                 0.1.10
  @backstage/plugin-search-backend-node                            1.2.10
  @backstage/plugin-search-backend                                 1.4.6
  @backstage/plugin-search-common                                  1.2.7
  @backstage/plugin-search-react                                   1.7.1
  @backstage/plugin-search                                         1.4.1
  @backstage/plugin-tech-radar                                     0.6.9
  @backstage/plugin-techdocs-backend                               1.8.0
  @backstage/plugin-techdocs-module-addons-contrib                 1.1.1
  @backstage/plugin-techdocs-node                                  1.9.0
  @backstage/plugin-techdocs-react                                 1.1.12
  @backstage/plugin-techdocs                                       1.8.0
  @backstage/plugin-user-settings                                  0.7.11
  @backstage/release-manifests                                     0.0.10
  @backstage/test-utils                                            1.4.4
  @backstage/theme                                                 0.4.3
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.6

👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

After digging a bit a find these similar issues/discussions:
https://github.com/backstage/backstage/issues/18163
https://github.com/backstage/backstage/discussions/17849
https://github.com/backstage/backstage/issues/18380

Hi @gaelgoth 👏
thank you for gathering all the issues/discussions together.  #96c4f54 has been included in the last next release so it's worth trying

Hello @vinzscam,
I did try to run the next release locally using the following command (yarn backstage-cli versions:bump --release next). Unfortunately, I still experienced a wait time of approximately 30 seconds on the following endpoint: /api/auth/microsoft/refresh?optional&env=azure
Here's a screenshot of the issue for reference with release version of #96c4f54:

I also did tried to benchmark via curl and got same result:
$ curl -w "@curl-format.txt" -o /dev/null -s 'http://localhost:7007/api/auth/microsoft/refresh?optional&scope=openid%20offline_access%20profile%20email%20User.Read&env=azure' \
  -H 'Accept: */*' \
  -H 'Accept-Language: en,fr-CH;q=0.9,fr;q=0.8,en-US;q=0.7' \
  -H 'Connection: keep-alive' \
  -H 'Cookie: microsoft-refresh-token='MY_AZURE_TOKEN' \
  -H 'DNT: 1' \
  -H 'If-None-Match: W/".."' \
  -H 'Origin: http://localhost:3000' \
  -H 'Referer: http://localhost:3000/' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \

  --compressed

     time_namelookup:  0.000020s
        time_connect:  0.000105s
     time_appconnect:  0.000000s
    time_pretransfer:  0.000155s
       time_redirect:  0.000000s
  time_starttransfer:  30.394398s
                     ----------
          time_total:  30.394613s

Network on our side is OK. I don't know if it's maybe on the Azure side that we have an issue.
Do you know if there is a way to reduce this token refresh ?
Thanks 😃

Are you able to work out where the delay is coming from?  If you can reproduce this locally, try running with debugging enabled for http to see the outgoing http calls from /api/auth/microsoft/refresh - is the time being spent on any of these
NODE_DEBUG=http,http2 yarn dev

Note, this will log response requests & bodies (including secrets!), so only do this if you're able to reproduce locally.
When tracing locally, I see 3 calls being made

A call to refresh the token https://login.microsoftonline.com/e8e97cab-f602-4278-8421-9d6657dede55/oauth2/v2.0/token
A call to get the user's avatar https://graph.microsoft.com/v1.0/me/photos/48x48/$value
A call to get the user from the catalog from the sign in resolver.  (This call may vary depending on the sign in resolver you have configured)
http://localhost:7007/api/catalog/entities?filter=kind=user,metadata.annotations.microsoft.com%2Femail=REDACTED

Hello @afscrome,
Thanks a lot! It helps to find where the issue is.
I did enable NODE_DEBUG. I found out that graph.microsoft.com was slow. Then, I searched which endpoint is particularly slow.

OK POST https://login.microsoftonline.com
OK GET https://graph.microsoft.com/v1.0/me
NOK GET https://graph.microsoft.com/v1.0/me/photos/48x48/$value

I did a test with Curl, but I got the same result with MS Graph explorer, which took approximately 30 seconds to return my user photo or end up with a 504 time error.
The issue is definitely on our Azure Tenant with the Microsoft Graph service. However, we are still impacted by getUserPhoto during a new Auth and token refresh
To reduce the impact on my Backstage Developers, I did a quick and dirty fix that patches node_modules/@backstage/plugin-auth-backend/dist/index.cjs.js in my CI to remove this slow call.
I'll continue my research at Microsoft Graph side.
What do you think about adding a flag (or another mechanism) to enable or disable the user photo in the Microsoft provider?
Thank you again for your help! 👍🏾

A slightly less hacky workaround could be to roll @backstage/plugin-auth-backend back to 0.19.2.  1.19.3 was released to fix a a couple of bugs, #20699 and #20677 .  If the first isn't a problem for you, the second sounds like a feature, so 0.19.2 may get you what you need in the short term.
Sounds like we have 3 bugs

The timeout error should have been logged to the console in some way so you could debug the problem without needing to use NODE_DEBUG
We should probably add a tighter timeout onto the avatar call request - I doubt anyone wants to wait 30 seconds for an avatar call to fail
Given the other issues you linked to, this 504 issue seems wider so we should probably add a flat to disable retrieving a user photos.

There has been some refactoring around getting the avatar in #20706 so it's worth giving tomorrow's release / master branch a go to see if it's any better, although I'm not sure I'd see anything obvious.

Another short term mitigation to skip the user profile call with backstage 1.20.0 would be to remove the User.Read scope from your app.  If this is missing from the access token, backstage should skip the user profile check.
https://github.com/backstage/backstage/blob/5afec2736d4b0c8f3e2a195054a1537325d0b2ac/plugins/auth-backend-module-microsoft-provider/src/strategy.ts#L67
Think we still need to add an option to not load user profiles as based on your scenario there are times we may want the user.read permission, but not to load user avatars.

I rolled back @backstage/plugin-auth-backend to 0.19.3 as advised. We are no longer affected by the API call slowness. Since we ingest users from LDAP in the catalog, only user settings are impacted, with the default avatar placeholder. As you said, I will check on today release about this.
  "dependencies": {
    "@backstage/backend-common": "^0.19.8",
    "@backstage/backend-tasks": "^0.5.11",
    "@backstage/catalog-client": "^1.4.5",
    "@backstage/catalog-model": "^1.4.3",
    "@backstage/cli-common": "^0.1.13",
    "@backstage/config": "^1.1.1",
    "@backstage/plugin-app-backend": "^0.3.54",
-  "@backstage/plugin-auth-backend": "0.19.4",
+ "@backstage/plugin-auth-backend": "0.19.3",
...
}

A slightly less hacky workaround could be to roll @backstage/plugin-auth-backend back to 0.19.2. 1.19.3 was released to fix a a couple of bugs, #20699 and #20677 . If the first isn't a problem for you, the second sounds like a feature, so 0.19.2 may get you what you need in the short term.
Sounds like we have 3 issues to fix

The timeout error should have been logged to the console in some way so you could debug the problem without needing to use NODE_DEBUG
We should probably add a tighter timeout onto the avatar call request - I doubt anyone wants to wait 30 seconds for an avatar call to fail
Given the other issues you linked to, this 504 issue seems wider so we should probably add a flag to disable retrieving a user photos.

There has been some refactoring around getting the avatar in #20706 so it's worth giving tomorrow's release / master branch a go to see if it's any better, although I'm not sure I'd see anything obvious.

Hello 👋🏽,
For the follow-up, I tried Backstage v1.20.2 and it didn't improve much. If feasible, I think the best solution for this is to fetch the user's avatar in the background and not include this API call in the auth/refresh token process.

I wonder if it's worth reaching out to Azure side and asking what's going on with these response times for the images. Definitely doesn't feel normal that it takes 30 seconds to return a profile picture or 504. Can someone do this?

I opened a ticket with Microsoft Azure and did not receive a clear response regarding why this Microsoft Graph request was slow. It's been 3 weeks since we noticed any slowness on this request https://graph.microsoft.com/v1.0/me

@gaelgoth To clarify - do you mean that you no longer see any slowness on that endpoint? That would be good news! Can anyone else confirm?

Hello @freben,
Yes, from my side, I confirm that we no longer see any slowness.

Nice! Gonna close this issue

authors: Rugvip afscrome benjdlambert freben gaelgoth vinzscam


text:
🐛 Bug Report: Unable to Hide Only Scaffolder Task List using Task Permissions

📜 Description
I'm trying to hide just the Task List on the Demo site as part of rolling out an example Software Template. There was new permissions for Task introduce in a previous version and I thought these would allow me to do this but it does not seem possible.
To be clear I want Users to be able to run a Software Template end to end but not be able to see the Task List. In a more real world scenario you might only want an Admin Groups to be able to see the Task List.
Documentation used: https://backstage.io/docs/features/software-templates/authorizing-scaffolder-template-details#authorizing-scaffolder-tasks
👍 Expected behavior
We should be able to hide only the Scaffolder Task List view
👎 Actual Behavior with Screenshots
Currently it seems we are not able to do this with the available Task Permissions.
👟 Reproduction steps
To keep things simple you can use this branch of the Demo site from my fork: https://github.com/awanlin/demo/tree/topic/scaffolder-permissions
📃 Provide the context for the Bug.
For the Demo site we'd like to prevent re-running templates as we use the Guest user. This is an unsual setup but I can see this need for this in cases where you might only want and Admin Group to have access to this.
🖥 Your Environment
OS:   Darwin 23.5.0 - darwin/arm64
node: v18.18.2
yarn: 3.5.0
cli:  0.26.11-next.1 (installed)
backstage:  1.29.0-next.2

Dependencies:
  @backstage/app-defaults                                          1.5.8-next.2
  @backstage/backend-app-api                                       0.7.8, 0.7.10-next.1
  @backstage/backend-common                                        0.21.7, 0.23.1, 0.23.3-next.1
  @backstage/backend-defaults                                      0.3.4-next.1
  @backstage/backend-dev-utils                                     0.1.4
  @backstage/backend-openapi-utils                                 0.1.13, 0.1.15-next.1
  @backstage/backend-plugin-api                                    0.6.20, 0.6.22-next.1
  @backstage/backend-tasks                                         0.5.25, 0.5.27-next.1
  @backstage/catalog-client                                        1.6.5
  @backstage/catalog-model                                         1.5.0
  @backstage/cli-common                                            0.1.14
  @backstage/cli-node                                              0.2.6
  @backstage/cli                                                   0.26.11-next.1
  @backstage/config-loader                                         1.8.1
  @backstage/config                                                1.2.0
  @backstage/core-app-api                                          1.13.1-next.1
  @backstage/core-compat-api                                       0.2.6, 0.2.7-next.1
  @backstage/core-components                                       0.14.8, 0.14.9-next.1
  @backstage/core-plugin-api                                       1.9.3
  @backstage/e2e-test-utils                                        0.1.1
  @backstage/errors                                                1.2.4
  @backstage/eslint-plugin                                         0.1.8
  @backstage/frontend-plugin-api                                   0.6.6, 0.6.7-next.1
  @backstage/integration-aws-node                                  0.1.12
  @backstage/integration-react                                     1.1.28, 1.1.29-next.0
  @backstage/integration                                           1.12.0, 1.13.0-next.0
  @backstage/plugin-api-docs                                       0.11.7-next.2
  @backstage/plugin-app-backend                                    0.3.71-next.1
  @backstage/plugin-app-node                                       0.1.22-next.1
  @backstage/plugin-auth-backend-module-atlassian-provider         0.2.3-next.1
  @backstage/plugin-auth-backend-module-aws-alb-provider           0.1.14-next.1
  @backstage/plugin-auth-backend-module-azure-easyauth-provider    0.1.5-next.1
  @backstage/plugin-auth-backend-module-bitbucket-provider         0.1.5-next.1
  @backstage/plugin-auth-backend-module-cloudflare-access-provider 0.1.5-next.1
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.17-next.1
  @backstage/plugin-auth-backend-module-github-provider            0.1.19-next.1
  @backstage/plugin-auth-backend-module-gitlab-provider            0.1.19-next.1
  @backstage/plugin-auth-backend-module-google-provider            0.1.19-next.1
  @backstage/plugin-auth-backend-module-guest-provider             0.1.8-next.1
  @backstage/plugin-auth-backend-module-microsoft-provider         0.1.17-next.1
  @backstage/plugin-auth-backend-module-oauth2-provider            0.2.3-next.1
  @backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.15-next.1
  @backstage/plugin-auth-backend-module-oidc-provider              0.2.3-next.1
  @backstage/plugin-auth-backend-module-okta-provider              0.0.15-next.1
  @backstage/plugin-auth-backend-module-onelogin-provider          0.1.3-next.1
  @backstage/plugin-auth-backend                                   0.22.9-next.1
  @backstage/plugin-auth-node                                      0.4.15, 0.4.17-next.1
  @backstage/plugin-auth-react                                     0.1.4-next.1
  @backstage/plugin-bitbucket-cloud-common                         0.2.21-next.0
  @backstage/plugin-catalog-backend-module-logs                    0.0.1-next.1
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.20-next.1
  @backstage/plugin-catalog-backend                                1.24.0-next.1
  @backstage/plugin-catalog-common                                 1.0.24
  @backstage/plugin-catalog-graph                                  0.4.7-next.2
  @backstage/plugin-catalog-node                                   1.12.2, 1.12.4-next.1
  @backstage/plugin-catalog-react                                  1.12.1, 1.12.2-next.2
  @backstage/plugin-catalog                                        1.21.1-next.2
  @backstage/plugin-events-node                                    0.3.8-next.1
  @backstage/plugin-home-react                                     0.1.15-next.2
  @backstage/plugin-home                                           0.7.7-next.2
  @backstage/plugin-kubernetes-backend                             0.18.3-next.1
  @backstage/plugin-kubernetes-common                              0.8.0
  @backstage/plugin-kubernetes-node                                0.1.16-next.1
  @backstage/plugin-kubernetes-react                               0.4.1-next.1
  @backstage/plugin-kubernetes                                     0.11.12-next.2
  @backstage/plugin-org                                            0.6.27-next.2
  @backstage/plugin-permission-backend                             0.5.46-next.1
  @backstage/plugin-permission-common                              0.7.14
  @backstage/plugin-permission-node                                0.7.31, 0.7.33-next.1
  @backstage/plugin-permission-react                               0.4.23
  @backstage/plugin-proxy-backend                                  0.5.3-next.1
  @backstage/plugin-scaffolder-backend-module-azure                0.1.14-next.1
  @backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.1.12-next.1
  @backstage/plugin-scaffolder-backend-module-bitbucket-server     0.1.12-next.1
  @backstage/plugin-scaffolder-backend-module-bitbucket            0.2.12-next.1
  @backstage/plugin-scaffolder-backend-module-gerrit               0.1.14-next.1
  @backstage/plugin-scaffolder-backend-module-gitea                0.1.12-next.1
  @backstage/plugin-scaffolder-backend-module-github               0.4.0-next.1
  @backstage/plugin-scaffolder-backend-module-gitlab               0.4.4-next.1
  @backstage/plugin-scaffolder-backend                             1.23.0-next.2
  @backstage/plugin-scaffolder-common                              1.5.3
  @backstage/plugin-scaffolder-node                                0.4.8-next.1
  @backstage/plugin-scaffolder-react                               1.10.0-next.2
  @backstage/plugin-scaffolder                                     1.22.1-next.2
  @backstage/plugin-search-backend-module-catalog                  0.1.28-next.1
  @backstage/plugin-search-backend-module-explore                  0.1.26, 0.1.28-next.1
  @backstage/plugin-search-backend-module-techdocs                 0.1.27-next.1
  @backstage/plugin-search-backend-node                            1.2.25, 1.2.27-next.1
  @backstage/plugin-search-backend                                 1.5.14-next.1
  @backstage/plugin-search-common                                  1.2.12
  @backstage/plugin-search-react                                   1.7.12, 1.7.13-next.1
  @backstage/plugin-search                                         1.4.14-next.2
  @backstage/plugin-signals-react                                  0.0.4
  @backstage/plugin-techdocs-backend                               1.10.9-next.1
  @backstage/plugin-techdocs-node                                  1.12.8-next.1
  @backstage/plugin-techdocs-react                                 1.2.6-next.1
  @backstage/plugin-techdocs                                       1.10.7-next.2
  @backstage/plugin-user-settings-common                           0.0.1
  @backstage/plugin-user-settings                                  0.8.9-next.2
  @backstage/release-manifests                                     0.0.11
  @backstage/theme                                                 0.5.6
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.8

👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

PR that added the Scaffolder Task permissions for reference: https://github.com/backstage/backstage/pull/24518

Hi @Zaperex, any chance you can give me your thoughts on this? My gut tells me it's not possible with the current permissions but maybe you have an idea that I'm missing.

Currently the scaffolder.task.read permissions aren't granular enough to allow that.
So based on what I'm seeing, we want users to not be able to see the entire list. However, for an E2E scenario, users would need read permissions for the specific task they're running. Specifically for the /tasks/:taskId and /tasks/:taskId/eventstream endpoints.
We can potentially have a permission solely for viewing the task list as well if they don't want the task list to appear for users at all?
Alternatively, we can allow the configuring of a permission rule to only allow reading of tasks owned by the user? If we still want users to be able to view the task list for tasks THEY generated/own, we can potentially add some permissions/rules when trying to view All Tasks?

https://github.com/backstage/backstage/blob/5442edda318637e7b40a4991bf9b60e3b412b9b5/plugins/scaffolder-backend/src/service/router.ts#L590-L592
What do you think?

I'm taking a look at this, can you assign me?

Thanks @Zaperex, I've assigned it to you 👍

I do like the idea of having it work so you can only view your own tasks but also having something to globally hide the task lists (and the option for it in the context menu).

Unstale, please

I do like the idea of having it work so you can only view your own tasks but also having something to globally hide the task lists (and the option for it in the context menu).

I would go with a frontend config that hides the list completely

Tbh I think the way to go with this one is to override the task endpoint to always return []

authors: Rugvip Zaperex awanlin ltdonner-bah vinzscam


text:
chore(gitlab-mr-action): remove deprecation of projectid for template…

projectid is now passed through the query parameter project in the repoUrl. It still allows people to not use the projectid and use the repoUrl with the owner and repo query parameters instead. This makes it easier to publish to repositories instead of writing the full path to the project.
Changed the parseUrl function so it uses a switch-case statement which makes the function more readable than having several if-else statements.
Created an auxiliary function called checkRequiredParams. The function checks if the required parameters (given as arguments) are present in the URL.
The function parseUrl uses checkRequiredParams to verify that all the required query parameters are present in the repo's URL. This replaces the if-else mess with a switch statement for better readability.

Signed-off-by: Borja González borja.gonzalez@sinch.com
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hello @jhaals ! I thought of providing some test cases and the outcome of those in order to hopefully proof to you that the frontend is passing the projectid through query parameters.

Successfully creating MR with projectID:
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>?project=<some_gitlabID>'
The output of the template action is:

Successfully creating MR with projectPath (owner and repo as query parameters):
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>?owner=<some_owner>&repo=test01'
The output of the template action is:

Unsuccessfully creating MR without query prameters:
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>'
The output of the template action is that the owner is missing, as expected:

Unsuccessfully creating MR with owner stated as a query parameter, but not repo:
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>?owner=<some_owner>'
The output of the template action is that the repo is missing, as expected:

Hope that this is enough to satisfy your first question :)

@satrox28 can you take a look at this PR and see if this makes sense? I'm a little lost on this one to be honest, and I don't have much knowledge on Gitlab

Hello @benjdlambert ! I can give you a little bit of context:
Maybe you remember this PR where the projectID for publishing GitLab MRs was deprecated because of redundancy between the projectID and the projectPath: https://github.com/backstage/backstage/pull/11946
The inconvenience that this brought to us, is that we couldn't use the projectID for GitLab projects at all and were forced to pass owner and repo as query parameters in order to specify the location of the GitLab project we wanted to publish a MR into, which we don't really like.
Because of this, we wanted to bring the functionality of using the projectID back, and at the same time, allow users to use the RepoUrlPicker if they want (i.e. passing owner and repo as query parameters), but to simplify things, we decided to pass the GitLab Project ID to the project query parameter... otherwise we would have to pass the projectID field into the parseUrl function, which would have involved more changes in all the places that call that function.
Hopefully this gave a little bit more of insight of the changes that I made :)

Also @jhaals I am confused with the changeset thing, because in one of your first comments, you suggested me to remove it, but now you ask for a changeset with minor changes, and that is what I had in the beginning 🙊.

Also @jhaals I am confused with the changeset thing, because in one of your first comments, you suggested me to remove it, but now you ask for a changeset with minor changes, and that is what I had in the beginning 🙊.

Sorry if I was unclear. The changeset is still needed and is what end up in the CHANGELOG.md for this individual package. It's good to keep that text short and sweat and only mention what's necessary for the user of the package to know.
If I try to summarise this for end users I would suggest something like:

Removed deprecation of projectid from the publish:gitlab:merge-request action as this field is still used.

What happened internally in the utils with the switch refactor is too detailed information for the consumers of this package :)

Hello @jhaals! Regarding your comment here: https://github.com/backstage/backstage/pull/14019#discussion_r1004142770, it is the second option. The INPUT FIELD projectID would be deprecated, BUT it will be passed via the repoURL input field :)

Thank you very much for your help @jhaals ! :)

Thank you for contributing during Hacktoberfest 🍂! You can claim the Backstage Hacktoberfest Holopin at https://bck.st/hacktoberfest-holopin 🙌🏻

authors: Borchies benjdlambert jhaals suuus


text:
Fixed typo in 05-extension-overrides.md

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

oh it wants you to run prettier on the file first - it looks good but maybe something had slipped in from a previous PR? I'll enable automerge for now, but it does need a prettier run

oh it wants you to run prettier on the file first - it looks good but maybe something had slipped in from a previous PR? I'll enable automerge for now, but it does need a prettier run

I've actually fixed a few other things in the docs which might need review.

authors: freben marleypowell


text:
Fix readme to give correct command

You cant use env() safely outside of the config files. As soon as you run config:cache() - this causes all env() commands to return null.
Therefore env() shouldnt be used here at all - it'll just trip people up.
This PR fixes the example to make it suitable and safer for all situations.

Thanks =)

authors: ShawnMcCool laurencei

repo: backup-manager/laravel


text:
Extend configuration to ban matching of ts files

Description
I am researching different ways to run step definition files written with typescript and I would like to propose the following feature:
Proposal
Instead of tsifying files in plugins file let's allow the user to compile .ts files to .js with tsc and run cypress afterward.
Pros
Right now step definitions are being compiled on every run. This produces some problems:

Delay before tests start (it's really annoying)
Any compilation errors are shown inside cypress log, without details.

If we would compile ts files with tsc and just exclude them from files matching step definitions (we already have their's compiled version) then we will solve both of the stated problems.
Possible solution
Let's introduce new boolean param matchTypeScriptStepDefinitions with default value set to true.
I am ready to prepare PR and an example of usage if you would agree to add this feature to the project.

Got same issue.
I was using a package.json command that first ran ""tsc" then "cypress run/open", The problem with that approach is you need to manually re-run tsc each time you modify your code when using cypress open.
Though for performance and CI execution, it is much better to simply use "tsc" then "cypress run" and use the compile js file, rather than compiling the "ts" files using browserify for every test suites (in this case, *.features)

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far.
Read more about the transfer of ownership here.
The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.

authors: FrancisBourgault badeball ghost

repo: badeball/cypress-cucumber-preprocessor


text:
fix [waffle] labels badge

update URL and parsing code to use /columns endpoint
add error handling for 'not found' case
add missing test cases
update home page example

Closes #1731
Refs https://github.com/waffleio/waffle.io/issues/3559

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @chris48s!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS

Updated based on comments - cheers.

repo: badges/shields


text:
Add Gitlab logo

Resubmission of #1539 with requested minification.
See also #541 for discussion of Gitlab CI support.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @alerque!

:book:

:art: Thanks for submitting a logo. Please ensure your contribution follows our guidance for logo submissions.

  Generated by :no_entry_sign: dangerJS

@PyvesB Yes I saw there was work going on to support the Gitlab API. I had actually started hacking on it myself and kludged together a couple things, but am looking forward to seeing a proper set of badges.

authors: alerque shields-ci


text:
ReadableStream - Post 2.0

Standard Module Implementation for readable_stream.ts

[ ] Add file block comment at top of file describing the adt/structure.
[ ] Check for any missing combinators/derivations that could be implemented.
[ ] Modify all combinator variable names to be readable (use style guide).
[ ] Add documentation to every export (and // comment local tools).
[ ] Check that every function and line is covered by tests in the testing directory.

Style Guide

Use A -> I, B -> J, C -> K, D -> L for inner types.
Use ua, va to match URI, VRI, etc in generic positions.
Implement algebraic structure types (type classes) out to length 4.
Use functions over const arrow functions for root exports.
Document all type exports.
Order file exports by group and then alphabetically. Groups are Types, Constructors, Combinators, Type Class Instances, Type Class Constructors, and Derived Combinators.

Documentation Guide

Start with at least one full sentence describing the use case for the export.
Include a @since tag (default to 2.0.0)
Include an @example tag with a simple example

Imports should be relative for functional stuff and otherwise full urls with versions
Example should end with at least one assert from the deno std lib

Moved to code.null.pub.

repo: baetheus/fun


text:
Cannot get Demo to run

Describe the bug
The simple slider demo just displays boxes, no slides
To Reproduce
vue-cli 3.3.0
vue create slider
cd slider
npm install hooper
edit HelloWorld.vue and replace most of the template with
   <hooper>
      <slide>
        1
      </slide>
     <slide>
        2
      </slide>
     <slide>
        3
      </slide>
     <slide>
        4
      </slide>
    </hooper>

(and add the import and component stuff for Hooper and Slide)
Expected behavior
I would expect to see one "slide" with one number and that I could then scroll through the rest of the slides.
Screenshots

Desktop (please complete the following information):

OS: macOS 10.14.2
Browser Chrome
Version 71

Additional context
I've tried the demo, too, but same behaviour. Don't know what I'm missing...

Appears to be still an issue, looks like the css its not getting loaded properly.
Describe the bug
No styling (colors, shapes) on elements
To reproduce
I tried to use it on a project of mine and didn't work, so I created a virgin project with vue-cli create and replaced App.vue with the example in the documentation and the issue is still there.
Expected behavior
I expect to see some sort of styling but there appears to be none, or maybe not all of it.
Screenshots
Page with two slide elements as in the doc example. Opening the page shows slide 1 spanning through the entire width of the view.

Scrolling/dragging brings slide 2, however no styiling

Desktop:
OS: Ubuntu 18.04
Browser: Chrome
Version: 85.0.4183.102
Additional context
Scrolls and mouse drags are working fine and without importing the css all I see is a list so I would guess something is happening but not properly.
This is my project configuration:
{
  "name": "test-hooper",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build"
  },
  "dependencies": {
    "core-js": "^3.6.5",
    "hooper": "^0.3.1",
    "vue": "^2.6.11",
    "vue-router": "^3.2.0",
    "vuex": "^3.4.0"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "~4.5.0",
    "@vue/cli-plugin-router": "~4.5.0",
    "@vue/cli-plugin-vuex": "~4.5.0",
    "@vue/cli-service": "~4.5.0",
    "vue-template-compiler": "^2.6.11"
  }
}

I've also tried with version 0.3.4 which is the one that gets installed by npm install hooper, however github lists 0.3.1 as latest release so I also gave a try to that one.
Is this the expected behavior? I was expecting to have some styling as shown in the examples page

authors: lupodellasleppa mccare

repo: baianat/hooper


text:
Since data-vv-id is random, it is making Jest snapshots fail

Versions:

VueJs: 2.5.3
Vee-Validate: 2.0.0-rc.23

Description:
vee-validate generates a random ID for each field that it's applied to when they're rendered. This means that if you're using Jest snapshots, or any other test framework that supports snapshots, they have to be regenerated every test, thus rendering them useless.
Is there a way to mock this random ID function to make it return something static/predictable?
Steps To Reproduce:
Store a snapshot of the rendered HTML in Jest.

I don't think it can be overridden at the moment because its being used by the field constructor directly. However it uses Math.random for generation, you could globally patch that to produce predictable results.
I believe the random id can be replaced by an increasing integer which should maintain uniqueness like how Vue does it for its components.

@logaretm thanks for the reply. I will try and mock Math.random.
Also, do you know how to make the IDs incremental?

I meant that as a possible enhancement for vee-validate so its not on your side.

Ah right I see!
It would be nice to be able to override the I'd generator with a custom
function, to help with testing.
On Thu, 23 Nov 2017, 20:26 Abdelrahman Awad, notifications@github.com
wrote:

I meant that as a possible enhancement for vee-validate so its not on
your side.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/baianat/vee-validate/issues/1000#issuecomment-346693386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYBhVlLlVrEKu6rXsL6Y-qGSRJhTjTYks5s5dUIgaJpZM4Qow8R
.

authors: logaretm ymhr

repo: baianat/vee-validate


text:
Custom validation rules seems to ignore immediate:false flag set in extendOptions object

Versions

vee-validate: 2.1.7
vue: 2.5.16

Describe the bug
Setting the immediate flag to false in the extendOptions object when extending the Validator with a custom rule, it gets ignored and the rule triggers immediately on page-load.
non-immediate-rules
To reproduce
Steps to reproduce the behavior:

Make a custom async validation rule
Extend the Validator with the above rule and set the immediate flag to false in the extendOptions object
The rule triggers on page load

Expected behavior
The rule should not have been triggered until after the user has changed the field.
Desktop (please complete the following information):

OS: macOs Mojave
Browser chrome
Version 74

Additional context
import axios from "axios";

export const isEmailUniqueIgnoreSelf = (email, {userId, refId}) => {

    let data = {
        email : email,
        userId: userId,
        refId : refId
    };

    return axios({
        data  : data,
        url   : `/validate/email`,
        method: "post"
    }).then((response) => {
        return {
            valid: response.data.valid,
            data : {
                message: response.data.message
            }
        };
    });
};

let paramNames = ["userId", "refId"];

Validator.extend("self-email", {
        getMessage: (field, params, data) => data.message,
        validate  : isEmailUniqueIgnoreSelf
}, {paramNames, immediate: false});

    <ValidationProvider
            :debounce="debounce"
            :events="validateOn"
            :name="name"
            :rules="rules"
            :vid="vId">
        <VTextField
                :auto-focus="autofocus"
                :class="classes"
                :disabled="disabled"
                :error="!valid && validated"
                :error-messages="errors"
                :full-width="full"
                :hide-details="hide"
                :label="label"
                :placeholder="placeholder"
                :ref="reference"
                :success="valid && validated"
                :type="fieldType"
                :validateOnBlur="validateOn==='blur'"
                slot-scope="{ errors, valid, validated }"
                v-model="innerValue"
        />
    </ValidationProvider>

<VTextFieldWithValidation
       :error-messages="errors"
       :rules="`email|self-email:${user.id},${user.ref}`"
       label="Email"
       name="email"
       placeholder="Enter email"
       v-model="user.email"
       vId="email"
       validateOn="blur"
/>

I'm facing the same result (rule triggers on page load), but with synchronous validation which is "require-like".
Validator.extend(
  'bool-question-required',
  value => {
    const valid = value === true || value === false;
    return {
      valid,
      data: {
        required: true,
      },
    };
  },
  {
    computesRequired: true,
    immediate: false,
  }
);

Not sure if it is related though.

Sorry about not being able to respond to this sooner, I have tested this behavior and I cannot reproduce it, furthermore, the tests are passing for it. So it must be related to something specific that your sample does not cover.
If you guys can provide a demo at codesandbox I will happily take a look. I will re-open once you do, thanks!

authors: logaretm ngrampsas veselj43


text:
如何在一定的并发和PPS基础上，加大流量

目标：在固定的并发下，测试出来被测目标能承受pps和bps的最大值。
操作：所以根据以上条件，CC固定的不能变；通过keepalive将pps也调到了稳定值，所以keepalive也固定了，现在需要在这基础上继续加大流量，但是增加packet_size后pps就降下来了，这个应该怎么设置呢？

增加CPU个数

authors: alongpan pengjianzhang

repo: baidu/dperf


text:
v0.6.0 not honoring configuration file settings

What happened?
After the upgrade to 0.6.0, the application started throwing TLS errors even though I have insecureSkipVerify set to true in the configuration. It was working properly until the container image was updated.
After some playing around, I noticed there are several options in my configuration file that are not being honored (or not represented in PRINT_CONFIG_ONLY mode), but some are. Some settings are being honored, just not all of them.  I've checked the documentation and update notes for 0.6.0 and feel like I have everything right but maybe I missed something.
If I set properties like insecureSkipVerify with environment variables, the application works as expected. If I revert to the configuration file only, the new version does not work correctly.
AdguardHome-Sync Version
v0.6.0
AdguardHome Version
v0.107.43
Configuration
Using docker-compose on Debian 11 Bullesys / Raspberry Pi 4 hardware (stock Debian docker / compose packages), here is the compose file.

docker-compose YAML

---
version: "3.7"
services:
  adguardhome-sync:
    image: ghcr.io/bakito/adguardhome-sync
    container_name: adguardhome-sync
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Chicago
      - CONFIGFILE=/config/adguardhome-sync.yaml #optional
      - PRINT_CONFIG_ONLY=true
    volumes:
      - /home/whadmin/Code/container-configurations/docker/compose/adguardhome-sync/config:/config
    restart: always

AdGuardHome-Sync configuration file
# cron expression to run in daemon mode. (default; "" = runs only once)
cron: "*/15 * * * *"

# runs the synchronisation on startup
runOnStart: true

origin:
  # url of the origin instance
  url: https://originhostname:443
  # apiPath: define an api path if other than "/control"
  insecureSkipVerify: true # disable tls check
  username: whadmin
  password: *********

# replica instance (optional, if only one)
replica:
  # url of the replica instance
  url: https://replicahostname:443
  # apiPath: define an api path if other than "/control"
  insecureSkipVerify: true # disable tls check
  username: whadmin
  password: *********

# Configure the sync API server, disabled if api port is 0
api:
  # Port, default 8080
  port: 0
  # if username and password are defined, basic auth is applied to the sync API
  #username: admin
  #password:

# Configure sync features; by default all features are enabled.
features:
  generalSettings: true
  queryLogConfig: true
  statsConfig: true
  clientSettings: true
  services: true
  filters: true
  dhcp:
    serverConfig: false
    staticLeases: false
  dns:
    serverConfig: true
    accessLists: true
    rewrites: true

Output from running in PRINT_CONFIG_ONLY mode. It doesn't seem to honor the insecureSkipVerify, runOnStart, nor the DHCP config replication settings.
Creating network "adguardhome-sync_default" with the default driver
Creating adguardhome-sync ... done
Attaching to adguardhome-sync
adguardhome-sync    | 2024-01-12T10:53:45.621-0600      INFO    root    cmd/root.go:119 Using config file:/config/adguardhome-sync.yaml
adguardhome-sync    | 2024-01-12T10:53:45.627-0600      INFO    run     cmd/run.go:35   Printing adguardhome-sync config (THE APPLICATION WILL NOT START IN THIS MODE):
adguardhome-sync    | origin:
adguardhome-sync    |     url: https://originhostname:443
adguardhome-sync    |     webURL: https://originhostname:443
adguardhome-sync    |     apiPath: /control
adguardhome-sync    |     username: whadmin
adguardhome-sync    |     password: *********
adguardhome-sync    |     insecureSkipVerify: false
adguardhome-sync    |     autoSetup: false
adguardhome-sync    | replica:
adguardhome-sync    |     url: https://replicahostname:443
adguardhome-sync    |     webURL: ""
adguardhome-sync    |     apiPath: /control
adguardhome-sync    |     username: whadmin
adguardhome-sync    |     password: *********
adguardhome-sync    |     insecureSkipVerify: false
adguardhome-sync    |     autoSetup: false
adguardhome-sync    | cron: '*/15 * * * *'
adguardhome-sync    | runOnStart: true
adguardhome-sync    | printConfigOnly: true
adguardhome-sync    | features:
adguardhome-sync    |     dns:
adguardhome-sync    |         accessLists: true
adguardhome-sync    |         serverConfig: true
adguardhome-sync    |         rewrites: true
adguardhome-sync    |     dhcp:
adguardhome-sync    |         serverConfig: true
adguardhome-sync    |         staticLeases: true
adguardhome-sync    |     generalSettings: true
adguardhome-sync    |     queryLogConfig: true
adguardhome-sync    |     statsConfig: true
adguardhome-sync    |     clientSettings: true
adguardhome-sync    |     services: true
adguardhome-sync    |     filters: true
adguardhome-sync    |

### Relevant log output

```shell
adguardhome-sync    | 2024-01-12T11:08:55.530-0600      INFO    root    cmd/root.go:119 Using config file:/config/adguardhome-sync.yaml
adguardhome-sync    | 2024-01-12T11:08:55.543-0600      INFO    sync    sync/sync.go:38 AdGuardHome sync        {"version": "v0.6.0", "build": "2024-01-10T18:53:37Z", "os": "linux", "arch": "arm64"}
adguardhome-sync    | 2024-01-12T11:08:55.544-0600      DEBUG   sync    types/types.go:73       Using config    {"config": {"origin":{"url":"https://originhostname:443","webURL":"https://originhostname:443","apiPath":"/control","username":"w***n","password":"g****","insecureSkipVerify":false,"autoSetup":false},"replica":{"url":"https://replicahostname:443","webURL":"","apiPath":"/control","username":"w***n","password":"g****","insecureSkipVerify":false,"autoSetup":false},"cron":"*/15 * * * *","runOnStart":true,"api":{},"features":{"dns":{"accessLists":true,"serverConfig":true,"rewrites":true},"dhcp":{"serverConfig":true,"staticLeases":true},"generalSettings":true,"queryLogConfig":true,"statsConfig":true,"clientSettings":true,"services":true,"filters":true}}}
adguardhome-sync    | 2024-01-12T11:08:55.545-0600      INFO    sync    sync/sync.go:65 Setup cronjob   {"cron": "*/15 * * * *", "next-execution": "2024-01-12T11:15:00.000-0600"}
adguardhome-sync    | 2024-01-12T11:15:00.000-0600      DEBUG   client  client/client-methods.go:17     do get  {"host": "originhostname:443", "method": "GET", "path": "status", "username": "whadmin"}
adguardhome-sync    | 2024-01-12T11:15:00.152-0600      DEBUG   client  client/client-methods.go:27     error in do get {"host": "originhostname:443", "method": "GET", "path": "status", "username": "whadmin", "status": 0, "body": "", "error": "Get \"https://originhostname:443/control/status\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}
adguardhome-sync    | 2024-01-12T11:15:00.152-0600      ERROR   sync    sync/sync.go:163        Error getting origin status     {"from": "originhostname:443", "error": ": Get \"https://originhostname:443/control/status\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}
adguardhome-sync    | github.com/bakito/adguardhome-sync/pkg/sync.(*worker).sync
adguardhome-sync    |   /go/src/app/pkg/sync/sync.go:163
adguardhome-sync    | github.com/bakito/adguardhome-sync/pkg/sync.Sync.func2
adguardhome-sync    |   /go/src/app/pkg/sync/sync.go:59
adguardhome-sync    | github.com/robfig/cron/v3.FuncJob.Run
adguardhome-sync    |   /go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:136
adguardhome-sync    | github.com/robfig/cron/v3.(*Cron).startJob.func1
adguardhome-sync    |   /go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:312

Anything else?
No response

released in https://github.com/bakito/adguardhome-sync/releases/tag/v0.6.1

released in https://github.com/bakito/adguardhome-sync/releases/tag/v0.6.1

Thank you! Updated my config as per the new documentation and it's working great.

authors: bakito ekrunch

repo: bakito/adguardhome-sync


text:
channel.close never happens

Hi.
After opening a channel I cannot close it. Please, have a look at the code, and the console output below.
Thank you!
THE CODE
require("babel-polyfill");

const series = require('async').series;
const nextTick = require('async').nextTick;

class Infra {

  constructor(connection, settings) {
    this.connection = connection;
    this.settings = settings;
    this.handle = this.connection.handle;
    this.channel_num = 2;
  };

  * channel_number() {
    yield this.channel_num++;
  };

  open_channel() {
    return new Promise((resolve, reject) => {
      const cn = this.channel_number().next().value;
      this.handle.channel.open(cn);

      this.handle.once(`${cn}:channel.close`, () => {
        console.log(`channel.close: ${cn}`);

        this.handle.channel['close-ok'](cn, () => {
          console.log(`[${cn}]close-ok:`);
        });

      });

      this.handle.once(`${cn}:channel.flow`, (channel, method, data) => {
        console.log(`${cn}:channel.flow:`, channel, method, data);
        this.handle.channel['flow-ok'](cn, data.active, () => {
          console.log(`[${cn}]flow-ok:`, data);
        });
      });

      this.handle.once(`${cn}:channel.open-ok`, () => {
        console.log(`${cn}:channel.open-ok`);
        resolve(cn);
      });

    });
  };

  * object_names(className) {
    for(let object_name of this.settings[className]) {
      yield object_name;
    };
  };

  declare_exchange(channel_number, object_config) {
    return new Promise((resolve, reject) => {
      const nowait = false;

      this.handle.exchange.declare(
        channel_number,
        object_config.name,
        object_config.exchange_type,
        object_config.passive,
        object_config.durable,
        object_config.auto_delete,
        object_config.internal,
        nowait,
        object_config.arguments,
        (error) => {
          if(error) {
            console.error(error);
            reject(error);
          };
        }
      );
      this.handle.on(
        `${channel_number}:exchange.declare-ok`, (channel, method, data) => {
          console.log(`${channel_number}:exchange.declare-ok: ${object_config.name}`);
          resolve();
        }
      );
    });
  };

  create_exchanges() {
    return new Promise((resolve, reject) => {
      const obj_names_gen = this.object_names('exchanges');

      for(let next_name of obj_names_gen) {
        const object_config = this.settings[next_name];

        this.open_channel()
          .then((channel_number) => {

            this.declare_exchange(channel_number, object_config)
              .then(() => {
                console.log(`BEFORE: this.handle.channel.close(${channel_number})`);
                this.handle.channel.close(channel_number, 200, 'object declared OK');
              })
              .catch((error) => {
                reject(error);
              });

          })
          .catch((error) => {
            reject(error);
          });
      };
    });
  };

  create_queues() {
    return new Promise((resolve, reject) => {
      resolve();
    });
  };

  create_bindings() {
    return new Promise((resolve, reject) => {
      resolve();
    });
  };

  create() {

    return new Promise((resolve, reject) => {

      series([

        (callback) => {
          this.create_exchanges()
            .then(() => {
              nextTick(callback);
            })
            .catch((error) => {
              callback(error);
            });
        },

        (callback) => {
          this.create_queues()
            .then(() => {
              nextTick(callback);
            })
            .catch((error) => {
              callback(error);
            });
        },

        (callback) => {
          this.create_bindings()
            .then(() => {
              nextTick(callback);
            })
            .catch((error) => {
              callback(error);
            });
        },

      ], (error, result) => {
        if(error) {
          console.error(error);
          reject(error);
        }
        resolve();
      });

    });
  };

};

module.exports = Infra;

THE CONSOLE OUTPUT
2:channel.open-ok
3:channel.open-ok
4:channel.open-ok
5:channel.open-ok
6:channel.open-ok
3:exchange.declare-ok: x-dlx
7:channel.open-ok
2:exchange.declare-ok: x-ae
4:exchange.declare-ok: x-fci
5:exchange.declare-ok: x-rci
BEFORE: this.handle.channel.close(3)
BEFORE: this.handle.channel.close(2)
BEFORE: this.handle.channel.close(4)
BEFORE: this.handle.channel.close(5)
6:exchange.declare-ok: x-idx
7:exchange.declare-ok: x-cmd
BEFORE: this.handle.channel.close(6)
BEFORE: this.handle.channel.close(7)

Hi
Just before looking in depth at this, could you add your environment (npm version) and the connection and settings used to create this?

From an initial look at the code, the create_exchanges promise is not being resolved.  I would add a resolve using this.handle.once(`${channel_number}:channel.close-ok`)
With some quick testing on a portion of this code, I can open and close channels fine.  The channels are there in the management console and disappear when I close them.

authors: Dmitry-N-Medvedev bakkerthehacker

repo: bakkerthehacker/bramqp


text:
SRS Review: "BeamBending" in Abbreviations and Acronyms section

Not only is "BeamBending" neither an abbreviation nor an acronym, but, if included here, its description is not particularly informative.

In Dr. Smith's review, he mentioned I should add "Program" to the end of the description, which I think makes it more informative. I'll try to think of a better abbreviation for BeamBending -- I've been thinking about renaming it for a while, I just haven't come up with a better name.

repo: balacij/Drasil


text:
sails.config.blueprints.populate setting not obeyed by "create" endpoint

Sails version: 12.0
Node version: 7.1.0
NPM version: 4.0.2
Operating system: 10.12

When using blueprints and setting populate to true on associations are not populated. I'm not sure why this is happening.
This issue is always reproducible and has been reported before by #3375

@remzr7 thanks for posting.  To clarify, is this re: the "create" blueprint action?

To follow up:  it was confirmed that the behavior for the create blueprint is in Sails v0.12.x is inconsistent with that of the other blueprints in that it doesn't automatically populate the response.  This is fixed in 1.0, but decided not to back-port to v0.12 b/c it could be considered a breaking change.

🎉This was incorporated into the official 1.0 release.

repo: balderdashy/sails


text:
sails-mysql username cannot accept special characters

Sails version: 1.0.2
Node version: 8.11.2
NPM version: 5.6.0
DB adapter name: sails-mysql
DB adapter version: 1.0.0
Operating system: macOS High Sierra 10.13.5
I am deploying the sailsjs code to a production environment where the username has a special character. For example, user@sitename
mysql://user@site1:myPassWord@localhost:3306/awesomedbname
If we have "@" for the username, the site1 becomes the host.
Any fix for this?

@sshhawwnn -  Perhaps there's a way to inject the ASCII code (64) for "@" with String.fromCharCode(64) to get around this limitation. Ultimately and if possible / acceptable, removing the special "@" symbol from the actual login name and keeping to 0-9/a-z/A-Z standard would make the database more platform-agnostic. Hope this helps, I'm curious to see other responses too!


text:
[OpenGL] Crash when separable shader program cannot be created

In my case, it was when I had a Tessellation Evaluation Shader without gl_PerVertex being redeclared. In application, the set of shaders is linked in a single program object, and worked without any warnings or errors, but RenderDoc crashed without a word when I went to a drawcall using the program.
So I built Profile config locally and before the crash I hit an error in MakeSeparableShaderProgram(), with "error C7592: ARB_separate_shader_objects requires built-in block gl_PerVertex to be redeclared before accesing its members". Sure enough, shader didn't redeclare it.
Continuing through a couple more related errors, this led to GLReplay::SavePipelineState giving a null ShaderReflection* to GetBindpointMapping, and crash.
Was able to fix on my end by adding gl_PerVertex to the shader, but probably be nice to not crash if that happens :)

Oh how I despise that stupid redeclaration requirement...
I agree that it shouldn't crash regardless, I'll check to see what's going on there and make sure there's some kind of graceful fallback (although RenderDoc won't be able to operate correctly without that separable prorgam).
However, in MakeSeparableShaderProgram I attempt to add a redeclaration of gl_PerVertex if it doesn't already exist, for this exact reason - can you see if it thinks the block is already declared, or is the compilation failing even with the block added?
If you're able to send me a capture or even just the shaders, I'll try and reproduce and investigate more myself.

aha! it doesn't get added to this particular shader! our preprocessor apparently turns #version 450 core into # version 450 core. with a space in there. So MakeSeparableShaderProgram doesn't find #version and doesn't do the insertion

Ahhh, of course, I need to allow for whitespace between # and version. That should be easy enough to do. Thanks :).

Sorry that took a little while for something easy enough, been busy on side-branches :). This should fix the issue of having whitespace in preprocessor directives messing with my shader patching.

That seems to have done it, thanks!

authors: SirTimothy baldurk

repo: baldurk/renderdoc


text:
Crash during replay

Description
renderdoc crashes when trying to replay a dump.
Steps to reproduce
Capture: http://ipfs.io/ipfs/QmeU6BahJ2a41Jv1rRdLwyXUS3ctyJ7D4jkYgdtBzB3ypp
(Rename it to .tar.xz. File is ~400M, please let me know if there's download problems.)
Environment

RenderDoc version: 0d4194afc57fa8498a6cde3df5ece2b21c744a83
Operating System: Arch Linux
Graphics API: Vulkan, RADV

Could also be capture generated an invalid file.

RenderDoc is only intended for capturing your own programs. Capturing copyrighted programs that you do not have the rights to is not endorsed and I will provide absolutely no support for it.


text:
aufs bug creates unstoppable zombies

Odroid-C1+ devices with an old kernel (3.10)
puppeteer leaving orphaned chromium processes
systemd not properly reaping the zombie because of the old kernel

Suggested solution: backport the following kernel patch from Ben Hutchings, message 47:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812207#47
Also, backport the aufs utils patch.
See also:

https://github.com/moby/moby/issues/18180#issuecomment-193708192
https://github.com/moby/moby/issues/19166

Copied from https://github.com/balena-os/meta-balena/issues/1344
 Front conversations

@ZubairLK we can close this now right?

authors: ZubairLK shaunmulligan

repo: balena-os/balena-odroid


text:
Update balena-yocto-scripts digest to fe6beaf

This PR contains the following updates:

Package
Update
Change

balena-yocto-scripts
digest
56bb055 -> fe6beaf

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Can one of the admins verify this patch?

authors: balena-ci resin-jenkins

repo: balena-os/balena-up-board


text:
code auto completion is not working.....(in vs code)

The user name of my machine has  a space. I think this is the issue for auto completion is not working. Also i can not use any libraries in my code.

@VJFernandez123 this will be fixed in the next immediate release

Hi @VJFernandez123,
Thanks for reporting this issue. We tried to reproduce the issue in Windows 10; using username "James Clark". Then saved a new ballerina file test.bal under the path C:\Users\James Clark\Documents path. Still, we could retrieve all code completions.
Please note that untitled files in VSCode will not provide any code completions due to fact that Ballerina VSCode plugin is only activated for the files with .bal extension. Thus, in order to receive code completions,  you need to save it somewhere first.
If the above is not the case, can you please try it on a latest Ballerina version such as 0.981.1 and let us know the results.
Used Ballerina Version: 0.981.1
Used VSCode Ballerina Plugin Version: 0.981.1
Note: I am closing the ticket as it is working with the latest. Please  re-open if you encounter the same issue with the latest release.

authors: VJFernandez123 nadeeshaan rasika

repo: ballerina-platform/ballerina-lang


text:
Stream is not returning custom error type when using next()

Description:
My iterator returns 'public function next() returns record{| record{} value; |}| sql:Error?', but when I do stream.next(), it's not returning my custom error - 'Error', and it's returning generic 'error' type. And hence I couldn't do,
record{| NumericInvalidColumn value; |}|sql:Error? data =  streamData.next();

And I can only do.
record{| NumericInvalidColumn value; |}|error? data =  streamData.next();

Compilation error:
    ERROR: .::query-test.bal:71:64:: incompatible types: expected '(record {| NumericInvalidColumn value; |}|ballerina/sql:DatabaseError|ballerina/sql:ApplicationError)?', found '(record {| NumericInvalidColumn value; |}|error)?'
        at org.ballerinalang.test.util.BRunUtil.getInvokedFunction(BRunUtil.java:1143)
        at org.ballerinalang.test.util.BRunUtil.invokeFunction(BRunUtil.java:1162)
        at org.ballerinalang.jdbc.query.NumericTypesQueryTest.testQueryNumericTypeRecord(NumericTypesQueryTest.java:83)

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/21524 ...

authors: mohanvive sinthuja


text:
VSCode Plugin Not Detecting Home Directory

Description:
When there is a space in a user's home directory (for example, mine was "SamWeeras 1"), the VSCode plugin doesn't automatically detect Ballerina home. Output can be seen in the below image:

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

As per the output log, this seems to be a CLI issue when executing ballerina home command.

Closing along with #27

authors: NipunaRanasinghe Samallama


text:
Update the snakeyaml version

Purpose
$subject
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

shall we include this for beta3-dev branch?


text:
Add parser changes to allow annotations for each member in a tuple

Purpose

Allow annotations to be added to each member in a tuple

Fixes #36390
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@ushirask, please fix the PR title to be similar to the commit messages. See https://github.com/ballerina-platform/ballerina-lang/pull/30227#issuecomment-829996231.

We also need to add a path for the optional annotation in tuple members in the BallerinaParserErrorhandler

Sorry I missed this before.

We also need to change,
https://github.com/ballerina-platform/ballerina-lang/blob/56e03dd7b2938ef06557f46baf457c965f83ed13/compiler/ballerina-parser/src/main/java/io/ballerina/compiler/internal/parser/BallerinaParserErrorHandler.java#L5037-L5038 to

if (isInTypeDescContext()) {
    startContext(ParserRuleContext.TUPLE_MEMBERS);
    return ParserRuleContext.TUPLE_MEMBER;
}

Because we added ANNOTATIONS under TUPLE_MEMEBERS ctx we need to add an entry in getNextRuleForAnnotationEnd() for that ctx.

Shall we also add a recovery test for tuple annotations?

@lochana-chathura the alterenatives for TUPLE_MEMBER should be
private static final ParserRuleContext[] TUPLE_MEMBER =
            { ParserRuleContext.ANNOTATIONS, ParserRuleContext.TYPE_DESCRIPTOR };

right? not ANNOTATIONS & TYPE_DESC_IN_TUPLE

@lochana-chathura the alterenatives for TUPLE_MEMBER should be
private static final ParserRuleContext[] TUPLE_MEMBER =
            { ParserRuleContext.ANNOTATIONS, ParserRuleContext.TYPE_DESCRIPTOR };

right? not ANNOTATIONS & TYPE_DESC_IN_TUPLE

Nope. it has to be TYPE_DESC_IN_TUPLE. will explain you offline.

authors: MaryamZi lochana-chathura ushirask


text:
Add verbose for push and pull commands

Purpose

$Title

Fixes https://github.com/ballerina-platform/ballerina-lang/issues/8885

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

How we can test this kind of functionality?

How we can test this kind of functionality?

We are going to add tests for this in ballerina-distribution.

@azinneera I have removed the stale lable assuming this work is not needed anymore. Then it won't get added to the [Stale PR] Ballerina Stale PR Details mail in the future.

authors: anupama-pathirage hasithaa pramodya1994


text:
Improvements to generated code with gRPC clients

Description:
Consider the following protobuf definition.
syntax = "proto3";

import "google/protobuf/wrappers.proto";

service Validator {
	rpc validate(stream google.protobuf.StringValue)
			returns (google.protobuf.BoolValue);
}

Describe your problem(s)/solution(s)

in the ValidateStreamingClient generated for this the name of the send string method is sendstring. Shouldn't this be sendString?
In the generated main function (--mode client), the main function has a rest param. Shouldn't we generate the main function with no params instead?
Some union types have parentheses around them (e.g.,  validate in ValidatorClient). We don't need them, right? This doesn't seem to happen with all unions though,

The new lines added between different constructs (e.g., between two type definitions, between two methods of a class) also seem to be inconsistent.

This is fixed in the latest SL release. We are now using the Ballerina syntax tree to generate the code.

authors: MaryamZi daneshk


text:
Ballerina 2201.2.1 RC1

Description:

Need to work on $Subject

Closing as this is completed.


text:
Tarea gradle para generar reporte cobertura con jacoco

Hola!, seria interesante que el scaffold de clean architecture venga ya configurado con la tarea jacoco de gradle para generar el reporte de cobertura de pruebas con todo el consolidado de los módulos del proyecto.
`task jacocoRootReport(type: JacocoReport){
dependsOn = subprojects.test
additionalSourceDirs.setFrom files(subprojects.sourceSets.main.allSource.srcDirs)
sourceDirectories.setFrom files(subprojects.sourceSets.main.allSource.srcDirs)
classDirectories.setFrom files(subprojects.sourceSets.main.output)
executionData.setFrom project.fileTree(dir: '.', include: '**/build/jacoco/test.exec')

reports {
    html.enabled = true
    html.destination = file("${buildDir}/jacoco")
    xml.enabled = true
    xml.destination = file("${buildDir}/jacoco/report.xml")
    csv.enabled = false
}

}`

Hi @CarlosM4rtinez , you can use jacoco or cobertura in your project. You need generated the scaffold with the option coverage = <jacoco | cobertura> if you dont specify the coverage tool, the default value is jacoco.
Maybe is usefull generate the pipeline too  with the task gradle generatePipeline --type=[pipelineType] that use the report of the coverage tool and publish with sonarQube.

repo: bancolombia/scaffold-clean-architecture


text:
Warning! Error encountered during contract execution [execution reverted]

Hello,
i  m using the bot with default settings and got 6 : Warning! Error encountered during contract execution [execution reverted] .
The gas fee are taken but transaction is aborted.
Example: tx hash 0x9d172dd0413be135a18fabff76d8b150f756786305e3f7e016fc64c65e7af0fe
is there a way to avoid that?

Hi, thanks for submitting your question.
What happened is that the pool values changed from when you calculated the arbitrage, so the minimum return specified from the first trade was not received, causing the transaction to fail. This is actually a good thing in that it failed early in the process, saving you some ETH gas costs.
This could have happened due to a trade on the pool in the block before your arbitrage trade, causing your arbitrage transaction to no longer be valid.
This has generally become less frequent over time, but it does still happen on occasion. If you want to continue the discussion on how to improve your bot, or have any followup questions, feel free to start a conversation on the Bancor Developer's Telegram group:

repo: bancorprotocol/fastlane-bot


text:
vault rekey and rotate - is it supported?

Is your feature request related to a problem? Please describe.
vault rekey and rotate operations are part of vault operator commands. Though this can be done manually but it requires the human to actually fetch the keys from s3 and decrypt it using kms key and use it to rekey.
Describe the solution you'd like
I think the above exposes the keys to a human and ideally should be able to trigger this say via vault CR in an automated way.
Describe alternatives you've considered
none
Additional context
https://www.vaultproject.io/docs/internals/rotation.html

No this is not yet supported but could be a valuable addition, but it is not trivial to implement, so we need to think about it first how to do this correctly.

@bonifaido rotate is pretty straightforward as it doesn't require the shared keys. It will just rotate the backend key used for encryption. rekey requires all the shares to be present and might require some work. Can you share your concerns when you say it is not trivial so that we can take the discussion forward. I think it is a good addition as most organization might have a key rotation policy.

My concerns are basically time-related only, namely that we don't have time currently to implement this, but I still think this a valid and valuable feature.

thanks @bonifaido fair enough

Closing this as not relevant anymore. Please reopen if still needed.

authors: bonifaido ramizpolic raoofm

repo: bank-vaults/bank-vaults


text:
Fix github actions tags

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
fixes github actions tags

License
Apache 2.0

What's in this PR?
Fix github actions tags to trigger pipeline from correct tags
Why?
Github actions tags were not set correctly for CI, Docker and Helm pipelines
Checklist

[x] Code meets the Developer Guide
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

Thanks @tiswanso @hi-im-aren for approving but not able to merge yet

repo: banzaicloud/imps


text:
与shiro集成报错

`public class DynamicDataSourceAutoConfiguration {
@Autowired
private DynamicDataSourceProperties properties;
。。。
@Bean
@ConditionalOnMissingBean
public DynamicDataSourceCreator dynamicDataSourceCreator() {
DynamicDataSourceCreator dynamicDataSourceCreator = new DynamicDataSourceCreator();
dynamicDataSourceCreator.setDruidGlobalConfig(properties.getDruid());
`
properties 报空指针，无法注入。
shiro 在非DynamicDataSource 环境运行正常；
DynamicDataSource在非shiro环境运行正常；
不知道您那有集成shiro成功的工程或者样例没有？

`public class DynamicDataSourceAutoConfiguration {
@Autowired
private DynamicDataSourceProperties properties;
。。。
@bean
@ConditionalOnMissingBean
public DynamicDataSourceCreator dynamicDataSourceCreator() {
DynamicDataSourceCreator dynamicDataSourceCreator = new DynamicDataSourceCreator();
dynamicDataSourceCreator.setDruidGlobalConfig(properties.getDruid());
`
properties 报空指针，无法注入。
shiro 在非DynamicDataSource 环境运行正常；
DynamicDataSource在非shiro环境运行正常；
不知道您那有集成shiro成功的工程或者样例没有？

我也遇到了这个问题，你解决了没有

应该是配置有冲突，我在启动类上加了这个就可以， 具体原因不明
@SpringBootApplication(exclude = {ShiroAnnotationProcessorAutoConfiguration.class, DruidDataSourceAutoConfigure.class})
🤣

這倆個無關，不會影響。

我也遇到了这个问题，还没解决，有没有人会解决呀？？？？

相关问题查看文档， 楼上问题新版会解决。

authors: huayanYu neozo xxyben ynp zhaogituser


text:
条件ne  查询问题

当前使用版本(必须填写清楚，否则不予处理)
3.2.0
该问题是怎么引起的？(最新版上已修复的会直接close掉)
条件ne  查询问题
ne()  如果传入null的话 查询结果不对
原因 数据库 <> null 的话是有问题的   必须用 is null
希望改善下这个条件   上游传入了null   查询结果就会差强人意了
重现步骤
报错信息
无

@miemieYaho 大老看下啦

自己判断处理

哈哈哈  那有空pr下

pr也不会接的

authors: miemieYaho purgeyao

repo: baomidou/mybatis-plus


text:
newline ending

Hello. Does it possible for logger macroc (info! error! etc) to be aware of plaform with newline? On linux all is fine, but when run on windows it seems newline is only \n, without \r.  May be i can configure it somehow ?

Oh, may be it's bug. I will try to solve it later.

repo: baoyachi/simple-log