Font Face

How to change to a font face I like ?

Ah, you can clone this repo, & make the changes in the .scss files. You'd want to change specifically the font variables at the top of the file called $paragraph-font, $header-font, & $monospace-font, as well as the @font-face rules below that. You then want to follow the Build instructions to build the CSS files and move the .css files and the ursine folder into your theme folders.
You can also just edit the CSS files you have now, though it can be a bit more tedious to find all the places to make the changes (font-faces, font-family properties, etc.)

I can see 4 scss files after I cloned，which one is that?And is there any type distriction about the font, ttf is available?Is that ursine-umbra.scss?I only find font-face in it....
------------------ 原始邮件 ------------------
发件人: "Daniel<EMAIL_ADDRESS>发送时间: 2019年8月31日(星期六) 凌晨0:45
收件人<EMAIL_ADDRESS>抄送: "QQ"651608356<EMAIL_ADDRESS>主题: Re: [aCluelessDanny/typora-theme-ursine] Font Face (#35)
Ah, you can clone this repo, & make the changes in the .scss files. You'd want to change specifically the font variables at the top of the file called $paragraph-font, $header-font, & $monospace-font, as well as the @font-face rules below that. You then want to follow the Build instructions to build the CSS files and move the .css files and the ursine folder into your theme folders.
You can also just edit the CSS files you have now, though it can be a bit more tedious to find all the places to make the changes (font-faces, font-family properties, etc.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I only find the font-face in ursine-umbra.scss,but no in ursine-polar.scss,I don't know whether it will in the polar theme
------------------ 原始邮件 ------------------
发件人: "Daniel<EMAIL_ADDRESS>发送时间: 2019年8月31日(星期六) 凌晨0:45
收件人<EMAIL_ADDRESS>抄送: "QQ"651608356<EMAIL_ADDRESS>主题: Re: [aCluelessDanny/typora-theme-ursine] Font Face (#35)
Ah, you can clone this repo, & make the changes in the .scss files. You'd want to change specifically the font variables at the top of the file called $paragraph-font, $header-font, & $monospace-font, as well as the @font-face rules below that. You then want to follow the Build instructions to build the CSS files and move the .css files and the ursine folder into your theme folders.
You can also just edit the CSS files you have now, though it can be a bit more tedious to find all the places to make the changes (font-faces, font-family properties, etc.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

And also there are 3 items after paragraph-font,header-font,monospace-font,shoud I change them all or what?Sorry about keep asking you questions,cuz I love Bear Note App so much ,I work by it everyday so I love your theme the same.
------------------ 原始邮件 ------------------
发件人: "Daniel<EMAIL_ADDRESS>发送时间: 2019年8月31日(星期六) 凌晨0:45
收件人<EMAIL_ADDRESS>抄送: "QQ"651608356<EMAIL_ADDRESS>主题: Re: [aCluelessDanny/typora-theme-ursine] Font Face (#35)
Ah, you can clone this repo, & make the changes in the .scss files. You'd want to change specifically the font variables at the top of the file called $paragraph-font, $header-font, & $monospace-font, as well as the @font-face rules below that. You then want to follow the Build instructions to build the CSS files and move the .css files and the ursine folder into your theme folders.
You can also just edit the CSS files you have now, though it can be a bit more tedious to find all the places to make the changes (font-faces, font-family properties, etc.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ah it's alright really.
So what you wanna do is solely edit the font-faces and certain variables on the top of the file ursine-umbra.scss. Ursine Polar's file, which is ursine-polar.scss, basically inherits all of Ursine Umbra's styling rules, so whatever you edit in Umbra's file will affect both themes. There are different kind of font types you can use, & they should all work fine without much difference.
Basically, I used 3 different fonts to be used throughout the theme:

$paragraph-font holds the font for the "regular" text you see throughout the theme, like for paragraphs, tables, etc.
$header-font is the font for primarily headers, but also for things like blockquotes and the filename title on the sidebar
And $monospace-font is pretty much used for inline code and code blocks

It's your call to pick which fonts you'd like to change. To change them, simply edit the variable with the font name you want, make sure you have the font-face rules set correctly, & have the font files placed in the right place (the fonts are currently placed within the /ursine folder. The build process will do the rest for ya.
So for example, let's say I wanted to change the font of headers to one I found called [Montserrat](https://fonts.google.com/specimen/Montserrat. After downloading the font (ideally, you'd download 4 variants of that font: one normal, one bold, one italics, & one bold-italic) and placing them in the /ursine folder, I'd change the font-faces to make this font available:
/*
In lines 149-175, where the header font-faces are, I change it from 'Adelle' to 'Montserrat'.
Make sure the "url(...)" part is the correct filepath to your fonts
*/

@font-face {
    font-family: 'Montserrat';
    font-style: normal;
    font-weight: normal;
    src: local('Montserrat'), url('./ursine/Montserrat.ttf') format('ttf');
  }

  @font-face {
    font-family: 'Montserrat';
    font-style: italic;
    font-weight: normal;
    src: local('Montserrat-Italic'), url('./ursine/Montserrat-Italic.ttf') format('ttf');
  }

  @font-face {
    font-family: 'Montserrat';
    font-style: normal;
    font-weight: bold;
    src: local('Montserrat-Bold'), url('./ursine/Montserrat-Bold.ttf') format('ttf');
  }

  @font-face {
    font-family: 'Montserrat';
    font-style: italic;
    font-weight: bold;
    src: local('Montserrat-ItalicBold'), url('./ursine/Montserrat-ItalicBold.ttf') format('ttf');
  }

And then simply change $header-font to use the font:
/*
In Line 6, just change 'Adelle' to 'Montserrat'. The other fonts are just fallbacks just in case
*/

$header-font: "'Montserrat', 'Times New Roman', serif";

After you've done all that, follow the Build instructions, & you'll have the built .css files in the /css folder ready to go. Drag and drop those files (not the /css folder) and the /ursine folder into your theme folder, restart Typora, and you should be good to go

I tried but it donesn't work and I don't know. The font I want is called SourceHanSans.  https://github.com/adobe-fonts/source-han-sans
Can you do it for me please?
------------------ 原始邮件 ------------------
发件人: "Daniel<EMAIL_ADDRESS>发送时间: 2019年9月4日(星期三) 凌晨1:56
收件人<EMAIL_ADDRESS>抄送: "QQ"651608356<EMAIL_ADDRESS>主题: Re: [aCluelessDanny/typora-theme-ursine] Font Face (#35)
Ah it's alright really.
So what you wanna do is solely edit the font-faces and certain variables on the top of the file ursine-umbra.scss. Ursine Polar's file, which is ursine-polar.scss, basically inherits all of Ursine Umbra's styling rules, so whatever you edit in Umbra's file will affect both themes. There are different kind of font types you can use, & they should all work fine without much difference.
Basically, I used 3 different fonts to be used throughout the theme:
$paragraph-font holds the font for the "regular" text you see throughout the theme, like for paragraphs, tables, etc.
$header-font is the font for primarily headers, but also for things like blockquotes and the filename title on the sidebar
And $monospace-font is pretty much used for inline code and code blocks
It's your call to pick which fonts you'd like to change. To change them, simply edit the variable with the font name you want, make sure you have the font-face rules set correctly, & have the font files placed in the right place (the fonts are currently placed within the /ursine folder. The build process will do the rest for ya.
So for example, let's say I wanted to change the font of headers to one I found called [Montserrat](https://fonts.google.com/specimen/Montserrat. After downloading the font (ideally, you'd download 4 variants of that font: one normal, one bold, one italics, & one bold-italic) and placing them in the /ursine folder, I'd change the font-faces to make this font available:
/* In lines 149-175, where the header font-faces are, I change it from 'Adelle' to 'Montserrat'. Make sure the "url(...)" part is the correct filepath to your fonts */ @font-face {     font-family: 'Montserrat';     font-style: normal;     font-weight: normal;     src: local('Montserrat'), url('./ursine/Montserrat.ttf') format('ttf');   }   @font-face {     font-family: 'Montserrat';     font-style: italic;     font-weight: normal;     src: local('Montserrat-Italic'), url('./ursine/Montserrat-Italic.ttf') format('ttf');   }   @font-face {     font-family: 'Montserrat';     font-style: normal;     font-weight: bold;     src: local('Montserrat-Bold'), url('./ursine/Montserrat-Bold.ttf') format('ttf');   }   @font-face {     font-family: 'Montserrat';     font-style: italic;     font-weight: bold;     src: local('Montserrat-ItalicBold'), url('./ursine/Montserrat-ItalicBold.ttf') format('ttf');   }
And then simply change $header-font to use the font:
/* In Line 6, just change 'Adelle' to 'Montserrat'. The other fonts are just fallbacks just in case */ $header-font: "'Montserrat', 'Times New Roman', serif";
After you've done all that, follow the Build instructions, & you'll have the built .css files in the /css folder ready to go. Drag and drop those files (not the /css folder) and the /ursine folder into your theme folder, restart Typora, and you should be good to go
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@danielduyixin Show us your .css file content. Maybe we can help.

Gonna close this since it's been a while since his last response


Crash out of handle_start with Plug.Cowboy

This code in handle_start/4…
    {_, adapter} = conn.adapter
    user_agent = header_or_empty(conn, "User-Agent")
    host = header_or_empty(conn, "Host")
    peer_ip = Map.get(Map.get(adapter, :peer_data), :address)

… can crash out when adapter in the first line has no peer_data, but does have peer: {{127, 0, 0, 1}, 63288}, as seen with Plug.Cowboy 2.2.
11:00:54.719 [error] Handler {OpentelemetryPlug, :plug_tracer_start} has failed and has been detached. Class=:error
Reason={:badmap, nil}
Stacktrace=[
  {Map, :get, [nil, :address, nil],
  [file: 'lib/map.ex', line: 450]},
  {OpentelemetryPlug, :handle_start, 4, [file: 'lib/opentelemetry_plug.ex', line: 78]}

The fix seems to be to use c:Plug.Conn.Adapter.get_peer_data/1:
    {adapter_module, payload} = conn.adapter
    peer_data = adapter_module.get_peer_data(payload)

elixir-plug/plug@d24ba4f … it's been that way since Plug 1.6.0.


set discoveryAddress to be cluster-local by default

Any Envoy trying to connect to a discovery server will either:

have an istiod instance in the same cluster
have an istiod-remote service that forwards traffic to the primary cluster's ingressgateway

In either case, traffic from the proxy to the discovery server should be cluster-local.
This fixes https://github.com/istio/istio/issues/23591

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
a6e2777885cbc8aef82099bfb9cbb6e7d1090606
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@hzxuzhonghu

One question: should we make istio-system all cluster local as kube-system?

Created https://github.com/istio/istio/pull/23642 to see if doing so fails any existing integration tests. Don't see why it would, wondering if there is a case where we would want to route straight to the istiod service via NodePort instead of istiod-remote->ingressgateway. I don't think anyone is doing that in prod but I feel like I've heard it mentioned.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
a6e2777885cbc8aef82099bfb9cbb6e7d1090606
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

I'm going to rebase on https://github.com/istio/istio/pull/23208, the multicluster/remote suite is what helped me discover the bug. Want to make sure that test would pass with this change.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
89020e453dbc2bdc628f4705d75966a30225fce6
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
89020e453dbc2bdc628f4705d75966a30225fce6
link
/test lint_istio

gencheck_istio
89020e453dbc2bdc628f4705d75966a30225fce6
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
8b0d0bb507c4050ec2e23effe11b77a15ac968a3
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
8b0d0bb507c4050ec2e23effe11b77a15ac968a3
link
/test lint_istio

gencheck_istio
8b0d0bb507c4050ec2e23effe11b77a15ac968a3
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

In response to a cherrypick label: #23625 failed to apply on top of branch "release-1.6":
Applying: fallback to default proxyconfig
Applying: organize imports
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pilot/pkg/model/context.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/model/context.go
CONFLICT (content): Merge conflict in pilot/pkg/model/context.go
Patch failed at 0003 organize imports

In response to a cherrypick label: new issue created for failed cherrypick: #23714

I'm not sure this is correct - it may be an option that some users may want, but there are plenty of cases where you want envoys to pick control plane from remote clusters even if a local control plane is running.  The point of having control plane in multiple clusters is to allow workloads to load balance and survive failure of any of the control planes.

@costinm

I'm not sure this is correct - it may be an option that some users may want, but there are plenty of cases where you want envoys to pick control plane from remote clusters even if a local control plane is running. The point of having control plane in multiple clusters is to allow workloads to load balance and survive failure of any of the control planes.

In that case maybe it would be better to advise users to set the cluster local up themselves in mesh config or create a profile to set this up.

@costinm

I'm not sure this is correct - it may be an option that some users may want, but there are plenty of cases where you want envoys to pick control plane from remote clusters even if a local control plane is running. The point of having control plane in multiple clusters is to allow workloads to load balance and survive failure of any of the control planes.

This is the first I've heard that we support something like this. Are you aware of anyone doing this today? Do we have it documented anywhere?
Master/remote is broken without this, so if we back this out we need an alternative.
FYI @howardjohn @smawson @linsun

I think it is a not-well-advertised feature (maybe not documented at all?). So far people have been more people seem surprised by this behavior than expecting it. I think we should make the default be cluster-local for everything in istio-system and carefully add the ability for users to use control plane replication if they want it. We also need to figure out how to separate out different services if we're running a single service with full support in some clusters and partial support in others, those shouldn't be the same k8s service name or they should not be merged.

@stevenctl
Any Envoy trying to connect to a discovery server will either:
have an istiod instance in the same cluster
have an istiod-remote service that forwards traffic to the primary cluster's ingressgateway

this is not entirely true
it can also be: not have an istiod instance in the same cluster but have an istiod service that foward traffic to primary cluster’s ingress gw


Install xarray from main

Noticed while setting up my env. Now that #8872 has merged

Thanks! FYI we should be able to point to an actual xarray release very soon (hopefully later today) https://github.com/pydata/xarray/issues/9018

We should also remove the note in the usage.md page in the docs about using a specific branch of xarray
https://virtualizarr.readthedocs.io/en/latest/usage.html#manual-concatenation-ordering

Thanks @jsignell !


Enhancement: Better handle large amounts of pasted input text

What features would you like to see added?
One of the useful things about the Claude Opus model is the large context window, that can be used to do things like summarise large blocks of text. Unfortunately though, Librechat responds quite sluggishly when a large block of text is pasted into the input box.
More details
The official Claude web UI handles this well, large amounts of text are displayed as a small "Pasted" icon instead and the app doesn't slow down. It would be nice if Librechat could do something similar.
Which components are impacted by your request?
No response
Pictures

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks! I'll look into it

If it helps, I'm guessing they're using the paste event and checking the clipboard length before deciding what to do.

Great point, will have to think how to best to implement

Also FYI and mostly a note for myself. The "delay" for long text only happens on chrome and I narrowed down exactly why. There would need to be a compromise for the current optimizations being handled for the textarea to fix it, but also may not address for a while.

If you want a second pair of eyes to look at that slow code, just shout (and link the code). Would be happy to have a quick look if it helps.

Speaking personally, I am quite often editing the pasted text, so I'm not sure the claude approach is ideal in all cases. Arguably it's better practise to get everything just right before pasting, but often enough I change my mind about what to include in the context as I'm drafting my query.

If you want a second pair of eyes to look at that slow code, just shout (and link the code). Would be happy to have a quick look if it helps.

I figured out the root cause for this issue and I’ll be pushing a change today

Unfortunately, this is still happening (not sure if the changes were pushed @danny-avila )

Unfortunately, this is still happening (not sure if the changes were pushed @danny-avila )

can you describe what is still happening? On both firefox/chrome, pasting large amounts of text does not incur a noticeable delay

Closing in favor of #2755  (same request) and the original inspiration for this issue, the slow loading of text via Chrome, is no longer an issue.


Queue, stack, anagram, LetterCount, Vowels and consants

💥 Proposal

Made the already existing  queue program dynamic.
Made a dynamic stack program named Stack2.
The anagram program that existed could have taken advantage of python and was a bit lengthy so I changed it
Added a program that tells the occurence of letter in a word using a dictionary
Added a program that helps to count the number of vowels and constants in a string )

Have you read the Contributing Guidelines on Pull Requests?
YES

Implement Stack / Implement Queue
Implement Stack using Queue
Implement Queue using Stack
Check for balanced parentheses
Next Greater Element
@shraddhavp @HarshCasper @iamrajiv    Please assign me these

Implement Stack / Implement Queue
Implement Stack using Queue
Implement Queue using Stack
Check for balanced parentheses
Next Greater Element
@shraddhavp @HarshCasper @iamrajiv    Please assign me these

I have made a PR regarding the issues stated above. It is for DWOC. If there are any changes required. Kindly let me know

I have made a PR regarding the issues stated above. It is for DWOC. If there are any changes required. Kindly let me know

These are not related to Changes But these are related to DWOC. I have already used two of my issues and they are closed now. So I was looking for issues opened under Stacks or queues so that I can ask to be assigned to them.

These are not related to Changes But these are related to DWOC. I have already used two of my issues and they are closed now. So I was looking for issues opened under Stacks or queues so that I can ask to be assigned to them.

Implement Stack / Implement Queue
Implement Stack using Queue
Implement Queue using Stack
Check for balanced parentheses
Next Greater Element
@shraddhavp @HarshCasper @iamrajiv    Please assign me these

@atriadhiakri2000 Please make a separate issue on this.

Implement Stack / Implement Queue
Implement Stack using Queue
Implement Queue using Stack
Check for balanced parentheses
Next Greater Element
@shraddhavp @HarshCasper @iamrajiv    Please assign me these

@atriadhiakri2000 Please make a separate issue on this.

Hello @chicken-biryani (Damn good Username; I need to cook someday 😆 )
Since you have already created an Issue, make separate PRs for all of them.

Hello @chicken-biryani (Damn good Username; I need to cook someday 😆 )
Since you have already created an Issue, make separate PRs for all of them.

Works!
Thankyou! (Just order-in)

Works!
Thankyou! (Just order-in)


Chrome Web Store?

Can't install the extension from the Edge store because it requires Edge, not just any Chromium-based browser :(
Have to load unpacked which is in general a pain.
Pushing to Chrome Web Store would fix all Chromium-browser related problems :)

I would have published it there, but it requires a registration fee. I don't use Chrome, so it's just not important enough to me personally, especially when there's no guarantee I'd get it published without any headaches.

This program is MIT licensed and may be redistributed.
People who use the Chrome browser can push it to the Chrome Store based on the MIT license.

This program is MIT licensed and may be redistributed. People who use the Chrome browser can push it to the Chrome Store based on the MIT license.

@kotx I think you should contribute from your own pocket money.

@kotx I think you should contribute from your own pocket money.

I don't use Mullvad anymore, so no, sorry.


perf: update Sass to not include design tokens #178

Changes to be committed:
modified:   src/style.scss
Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #178
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
The update reduces bundle size 6.7 kb
BEFORE
npm notice === Tarball Details ===
npm notice name:          @aurodesignsystem/auro-hyperlink
npm notice package size:  33.3 kB
npm notice unpacked size: 138.0 kB
npm notice shasum:        bd114a81076b169b4383c00cf174025a70035018
npm notice integrity:     sha512-n8X88qt1SNS20[...]m4HpN+kfeJwNQ==
npm notice total files:   27
AFTER
npm notice === Tarball Details ===
npm notice name:          @aurodesignsystem/auro-hyperlink
npm notice filename:      aurodesignsystem-auro-hyperlink-3.3.4.tgz
npm notice package size:  40.0 kB
npm notice unpacked size: 165.4 kB
npm notice shasum:        28c5358df3619830d30dca8cbe7bf6a04a0485d7
npm notice integrity:     sha512-FmeoJ1XoQ7Rrk[...]QbJMQ9SuaeR8w==
npm notice total files:   27
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[X] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 3.3.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Installation not possible

These given links are not working:

I found the mod-loader plugin, but not the Action-MakeTid plugin.

Hello! I did put together that last release in the middle of recovering from an hdd failure. I'll look into it this week, thanks!
Also, I had to reverse engineer some of Evan's work in order to refactor it and make his plugins work with the more recent Tiddlywiki releases (I see you opened some issues over there).

Perhaps this explains the following strange behavior after importing the plugin:

Big link icons on every tab, can't set fluid story.

TonyM, Do you also have problems with the Mod-Loader plugin? Please report
Could that have something to do with this?
I think the idea behind the plugin is excellent, but I don't want to cause any problems with my plugins.

Aaah, I see. The links and instructions in the GitHub ReadMe were broken.
I have updated the ReadMe, and clarified that you have to open the Example Wiki to install the plugin tiddlers directly. Thanks!


Push campaign not received

when I send push campaign to test device token it works but when I start campaign I don't receive the notification

@DinaMMorad Android 12 & 13 changed many Notification policies. These may be the reasons why you did not receive the notification on devices that run on newer Android platforms.
Flurry SDK 14.2.0 resolved these issues on these newer Android platforms. Please upgrade Flurry SDK to see whether it resolves your issues or not.
https://developer.yahoo.com/flurry/docs/releasenotes/android/
Android SDK Release Notes
Version 14.2.0 - 03/14/2023

Fix for Flurry Push notification not shown on the Android 13 and above devices.
Fix for clicking on Flurry Push notification does not bring back apps to foreground on the Android 12 and above devices.
A couple minor bug fixes.

All add the post notification permission to the manifest file: (required by Android 13)
uses-permission android:name=”android.permission.POST_NOTIFICATIONS”

I'm using version 14.2.0 but didn't receive notification on android 13 device although I received it with android 10 device

also I added user property and sent notification to it but didn't receive that notification I wanted to target all users using english language with a notification I sent notification but all devices that has this userproperty didn't receive this notification

@DinaMMorad Though the Android developer docs say "recommended" to add POST_NOTIFICATIONS permission for Android 13 and above devices. As I found, it is actually "required" to add this permission! Please do add the following post notification permission to the manifest file:
uses-permission android:name=”android.permission.POST_NOTIFICATIONS”

And in your app, do use ActivityCompat.requestPermissions to request the permission if ContextCompat.checkSelfPermission returns PackageManager.PERMISSION_DENIED.
Examples codes,
    private static List<String> PERMISSIONS;
    static {
        PERMISSIONS = new ArrayList<>();
        PERMISSIONS.add(Manifest.permission.ACCESS_FINE_LOCATION);

        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
            PERMISSIONS.add(Manifest.permission.POST_NOTIFICATIONS);
        }
    }
...
    for (String permission : PERMISSIONS) {
        if (ContextCompat.checkSelfPermission(this, permission) == PackageManager.PERMISSION_DENIED) {
            // Simply request permissions if one of them is missing
            ActivityCompat.requestPermissions(this, PERMISSIONS.toArray(new String[0]), PERMISSION_REQUEST);
            break;
        }
    }

@DinaMMorad @poting-oath I'm seeing the same issue. push notification works with test device token but if I start a campaign, it is not received. Did you find any solution?

@raghuriyaz Do you add permission ”android.permission.POST_NOTIFICATIONS” to your app? And ask users to allow the permission by ActivityCompat.requestPermissions?


[stable-4.3] Enable cypress on stable-4.3

Copy .github/workflows/cypress.yml from master to stable-4.3. Apparently this is needed to make PRs against stable-4.3 start cypress.
Also backport most of #362 (except parts superceded by #511), to fix 2 failing specs:
cypress/integration/repo_management.js:32: Timed out retrying: cy.click() failed because this element is disabled
cypress/integration/profile.js:20: expected [ Array(6) ] to include 'pf-1623184710797zdinfyw6yd'

Looks good to me, this is great!


Repo permission levels for Meltano Engineers

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/64
Originally created by @aaronsteers on 2022-02-28 19:42:38

Following from other conversations on #63 and !108, I wanted to open this issue to discuss what the proper permission level is for Gitlab projects for our team.
Permission Levels

Project/Group Developer

Today every engineer inherits this at the group level.

Project/Group Maintainer

In theory, this is really only needed when setting up a new repo, in order to setup the project as described in !108+.

Project/Group Owner

Similar to Maintainer, but at a higher level. (Not sure what the important distinctions are here.)

Repo Codeowner

For projects which enable it, this is the designated primary/secondary approvers we set for each code path via the CODEOWNERS file.
Note: this is basically orthogonal with the permission levels 1-3, above.

Consideration

Everyone should have sufficient permissions to do their job.
Certain permissions that don't need to be changed often can be maintained or initialized by a small group of responsible persons.
We don't have great auditing on project level settings, and we want to avoid a case where a setting is modified but it's impossible to tell who changed it or when it was changed. (A small group of responsible parties (2-3) is preferred, for this reason.)
If everyone in the Engineering team does require elevated (Maintainer and/or Owner) permissions, we should document the reasons for that and update our new user onboarding processes to reflect this.

View 1 previous comment from the original issue on GitLab


No obvious way to tell when current view is ready to be popped

Scenario: have view that pops itself once it's loaded
Problem: calling layers.pop too early fails, and there is no single event for signalling readyness
Example, fires too early (uses visibilitychange on window.document behind the curtains):
supersonic.ui.views.current.whenVisible(function() {
  supersonic.ui.layers.pop();
});
// supersonic.ui.layers.pop rejected: Cannot close layer while another transition is in progress

Solution proposals:

Have native client queue transition requests (ie. pop in this case) instead of rejecting immediately
Publish didshow event on steroids.view, analogous to steroids.modal

What about steroids.layers.on "didchange"? The event has information on the layer that was pushed to the stack.

Solid suggestion, but doesn't seem to solve anything. steroids.layers.on "didchange" seems to trigger for more transitions than I'd like, but not always when I need it so I can't filter out the unneeded events; trying to use it easily got my app's layer stack into an inconsistent state. See the navigation bar here:

Just to note, would be nice if the solution would enable something like this:
supersonic.ui.layers.push('foo').then ->
  supersonic.ui.layers.pop()

From the outside, steroids.layers.on "didchange" does seem to work. So this appears to be reliable:
waitForLayerChange = ->
  new Promise (resolve) ->
    listener = steroids.layers.on "didchange", ->
      steroids.layers.off "didchange", listener
      resolve()

supersonic.module.layers.push('foo')
  .then(waitForLayerChange)
  .then(supersonic.module.layers.pop)

For the view itself, telling whether everything is ready still seems difficult.


Fixed Parameter name parsing to handle lambda's without parenthesis

also updated the package to have a geofeedia specific prefix

oops. please delete


lazySizes does not work with the correct video embed code

Describe the bug
lazysizes does not work with video in such a combination of code. This is the correct code:
<figure>
    <video class="lazyload" width="512" height="512">
            <source data-src="https://static.videezy.com/system/resources/previews/000/040/400/original/190816-samutprakarn_2.mp4" src="https://farm9.staticflickr.com/8200/8248153196_7a7664e147_b.jpg" type="video/mp4"
        </video>
</figure>

To Reproduce
https://codepen.io/bola4ka/full/LYpvxrW
Steps to reproduce the behavior:
If you look at the source code of the page. It can be seen that the script does not work.
You will see that the class of the video tag has changed, but this did not affect the data-src and src attributes.
As a result, this misunderstanding does not allow you to watch the video.
What is the expected behavior
The src attribute will change to the correct link, as is the case with regular images.
What happened instead
The data-src and src attributes are not changed in any way and are ignored by the script.
In what environment (browser/device etc.) does this bug happen/not happen:
In any.
However, I use Google Chrome. Version 81.0.4044.138 (Official Build), (64 bit)
**P.S:
Mr. aFarkas, Please fix it.
This appeal is in addition to this: https://github.com/aFarkas/lazysizes/issues/784
Regards, Mr.Volev.

Your HTML code doesn't make too much sense. The post is never a video src.
Please check the unveilhooks plugin to solve your problem.


NoSuchElementException when only 1 server is defined.

java.util.NoSuchElementException
at com.google.common.collect.Iterators$4.next (Iterators.java:408)
at io.searchbox.client.AbstractJestClient$ServerPool.getNextServer (AbstractJestClient.java:118)
at io.searchbox.client.AbstractJestClient.getNextServer (AbstractJestClient.java:80)
at io.searchbox.client.http.JestHttpClient.prepareRequest (JestHttpClient.java:80)
at io.searchbox.client.http.JestHttpClient.execute (JestHttpClient.java:46)
      final JestClientFactory factory = new JestClientFactory();
    factory.setHttpClientConfig(new HttpClientConfig.Builder(http://localhost:9200).multiThreaded(true)                 .readTimeout(READ_CONN_TIMEOUT).connTimeout(READ_CONN_TIMEOUT).build());

This was a duplicate to following issue which is fixed and I verified the same in my setup.
https://github.com/searchbox-io/Jest/issues/311


reverse_tt!: support eager expansion

Make reverse_tt! support eager!

Implemented in https://github.com/Emoun/dmutil/commit/573d4479d224166cf14091a5510d139c6efa4407


Remove domElements list, use React.DOM instead

Everything is here https://github.com/styled-components/styled-components/issues/536

This is going away in 15.5, I wouldn't use it: https://github.com/facebook/react/issues/8854

Thank you for that information @yaycmyk.

That's sad, I was really excited for a second. Thanks @yaycmyk!


[ddtelemetry] Prefix ffi functions with ddog_telemetry

What does this PR do?

Rename ddtelemetry ffi functions from ddog_handle_* to ddog_telemetr_handle_* and ddog_builder_* to ddog_telemetry_builder_*

Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.
For Reviewers

[ ] If this PR touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.
[ ] This PR doesn't touch any of that.

Not sure if you want to take the opportunity here to tweak, but for profiling stuff, we usually use a slightly different naming where we use struct names with camel case, e.g. (ddog_Vec_Tag or ddog_prof_Endpoint.

@ivoanjo
Right now, this PR is more about removing confusion and potential collisions on the telemetry ffi, since I just need the right part of my brain convince the left one.
If we want to standardise function and type names for all of libdatadog, we probably should write a small rfc now that we have a directory for that, and share it with the profiling and data-pipelines team?

We actually did discuss such standardization shortly before 1.0, see https://github.com/DataDog/libdatadog/pull/73 and https://docs.google.com/spreadsheets/d/1iuuSCJ0NcSOpo2RVvkQ8f8ugz2XlEbbpFZLVOg6WioE/edit#gid=0 .


OC-26.1: Network Time Protocol (NTP): Deviation:ntp_non_default_vrf_unsupported removal

As there is support for ntp_non_default_vrf in juniper devices . So removing the deviation

Pull Request Functional Test Report for #2923 / cbd03607e7bd6753b497d398109dd1904ac485ef
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Cisco 8000E

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Cisco XRd

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Juniper ncPTX

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Nokia SR Linux

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Openconfig Lemming

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Cisco 8808

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Juniper PTX10008

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Nokia 7250 IXR-10e

gNMI-1.4: Telemetry: InventoryOC-26.1: Network Time Protocol (NTP)

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.448%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1949

Relevant Lines:
3515

💛  - Coveralls


Allow for Log4J to be configured for peons but still ensure console logging is enforced

This change will allow for log4j to be configured for peons but require console logging is still configured for them to ensure peon logs are saved to deep storage.
Also fixed the test ConsoleLoggingEnforcementTest to use a valid appender for the non console Config as the previous config was incorrect and would never return a logger.

Description
This change will allow for log4j to be configured for peons but still require console logging is configured for them to ensure peon logs are saved to deep storage.

Release note
Add ability to configure log4j2 for peons.

Key changed/added classes in this PR

ConsoleLoggingEnforcementConfigurationFactory
ConsoleLoggingEnforcementTest

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

Still need to edit the docs for this change

Because peon's log is saved to deep storage by middlemanagers, and the web-console provides a UI to show logs of tasks from deep storage, what's the motivation that users configure peon to write log to somewhere else?

Because peon's log is saved to deep storage by middlemanagers, and the web-console provides a UI to show logs of tasks from deep storage, what's the motivation that users configure peon to write log to somewhere else?

Users may not want to write the entire peon logs to another location since the logs are uploaded to deep storage eventually.
However, I can see a case where a Druid operator might want to expose a subset of the peon logs for consumption by non Druid experts. Here's an example I can think of

Some users may want to see ingestion progress logs, but the current peon logs are too detailed. Something like this would allow a Druid operator to configure ingestion progress logs to be written to a separate location with another appender while the entire set of logs is still uploaded to deep storage.


Missing initContainer in PodSpecProps

Kubernetes has it https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ but not cdk8s
When try to use it

/**
 * (experimental) Properties of a `PodSpec`.
 *
 * @experimental
 */
export interface PodSpecProps {
    /**
     * (experimental) List of containers belonging to the pod.
     *
     * Containers cannot currently be
     * added or removed. There must be at least one container in a Pod.
     *
     * You can add additionnal containers using `podSpec.addContainer()`
     *
     * @default - No containers. Note that a pod spec must include at least one container.
     * @experimental
     */
    readonly containers?: ContainerProps[];
    /**
     * (experimental) List of volumes that can be mounted by containers belonging to the pod.
     *
     * You can also add volumes later using `podSpec.addVolume()`
     *
     * @default - No volumes.
     * @see https://kubernetes.io/docs/concepts/storage/volumes
     * @experimental
     */
    readonly volumes?: Volume[];
    /**
     * (experimental) Restart policy for all containers within the pod.
     *
     * @default RestartPolicy.ALWAYS
     * @see https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
     * @experimental
     */
    readonly restartPolicy?: RestartPolicy;
    /**
     * (experimental) A service account provides an identity for processes that run in a Pod.
     *
     * When you (a human) access the cluster (for example, using kubectl), you are
     * authenticated by the apiserver as a particular User Account (currently this
     * is usually admin, unless your cluster administrator has customized your
     * cluster). Processes in containers inside pods can also contact the
     * apiserver. When they do, they are authenticated as a particular Service
     * Account (for example, default).
     *
     * @default - No service account.
     * @see https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
     * @experimental
     */
    readonly serviceAccount?: IServiceAccount;
}

@sunshineo Thanks for reporting this. Indeed cdk8s+ does not have support for initContainers just yet. But you can use escape hatches to manually add them to the underlying resource spec.
Also note that the L1 layer constructs, i.e KubePodSpec that is generated from the cdk8s import command will have that property, as it contains all properties available in the spec.

Thank you @iliapolo . I was not aware of the escape hatches. I thought the PodSpec itself is generated


fix: update tails to corrected design

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Summary:
Updated tail designs
Validate https://auro-icons-pr71.surge.sh/
Type of change:

[ ] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[x] Content update

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 4.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CPI error 'Cannot find the billing item for this virtual server'

CONTEXT
I used the following version of the release.

bosh: 263
bosh-softlayer-cpi: 23
bosh-softlayer-xen-ubuntu-trusty-go_agent: 3445.2.1

ISSUE
When I tried to recreate the job, a CPI error occurred.
# bosh -e mybosh -d ntp recreate ntpd/2
Using environment '<BOSH-IP>' as client 'admin'

Using deployment 'ntp'

Continue? [yN]: y

Task 64

08:53:15 | Preparing deployment: Preparing deployment (00:00:00)
08:53:15 | Preparing package compilation: Finding packages to compile (00:00:00)
08:53:15 | Updating instance ntpd: ntpd/d054e429-9012-4863-b7d1-b360525b8067 (2) (canary) (00:00:14)
            L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID 'a0eedcfe-42c6-4ae0-8f50-3af3306e748d': Failed to reload OS: Failed to reload OS on the specified VirtualGuest from SoftLayer client: Cannot find the billing item for this virtual server (sl-20170904-084458-512.softlayer.com).' in 'create_vm' CPI method

08:53:29 | Error: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID 'a0eedcfe-42c6-4ae0-8f50-3af3306e748d': Failed to reload OS: Failed to reload OS on the specified VirtualGuest from SoftLayer client: Cannot find the billing item for this virtual server (sl-20170904-084458-512.softlayer.com).' in 'create_vm' CPI method

Started  Mon Sep  4 08:53:15 UTC 2017
Finished Mon Sep  4 08:53:29 UTC 2017
Duration 00:00:14

Task 64 error

Changing state:
  Expected task '64' to succeed but was state is 'error'

Exit code 1

QUESTION
Why does this error occur? Do I need special permissions to recreate?

When I tried to deploy Cloud Foundry using cf-deployment, the same error has occurred.
# bosh -d cf deploy cf-deployment.yml -o operations/softlayer.yml --vars-store deployment-vars.yml -v system_domain=DOMAIN
06:47:37 | Updating instance consul: consul/4ee72950-ab7e-4163-a690-f80c63ccb197 (0) (canary) (00:01:06)
            L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '01e32b1d-ae28-4adb-be92-ff2823f58ee2': Failed to reload OS: Failed to reload OS on the specified VirtualGuest from SoftLayer client: Cannot find the billing item for this virtual server (sl-20170905-022554-998.softlayer.com).' in 'create_vm' CPI method

The error message was said that virtual server (sl-20170905-022554-998.softlayer.com) was not exist (meaning was deleted). As a default, Bosh would delete VM from the cloud when instance update. And director has enable_virtual_delete_vms property to specify this behaviour.
So I suggest that you set enable_virtual_delete_vms as true in /instance_groups/name=bosh/properties/director/enable_virtual_delete_vms.
Hope it can works!

@7CHANHO You could reference https://github.com/bluebosh/bosh-deployment/blob/softlayer/softlayer/cpi.yml#L76, here is property spec -> https://bosh.io/jobs/director?source=github.com/cloudfoundry/bosh&version=263#p=director.enable_virtual_delete_vms

Thank you @EdwardStudy @mattcui
I have solved this problem.


Provide a method in the core libraries that indicates whether the app is running on the server or web.

Provide a method in the core libraries that indicates whether the app is running on the server or web.
Proposed return values:
web, server
Currently users determine whether they are on the web by hacks such as "1.0 is int" which makes the code vulnerable to changes in dartium flags that impact number semantics.

Why is the distinction needed?
In the perfect world, there wouldn't be any need to distinguish, but obviously we're not in that world.
If it's in order to predict the non-standard integer behavior of JS compiled Dart code, then checking 1.0 is int is probably the reasonable thing to do. That is exactly the problem, if JS gets integers and we change to compile Dart to those, the test will successfully detect that, even if we are still on the "web".
You could also use const bool.fromEnvironment('dart.library.html') as a sign that HTML functionality is available, which probably means the web (whether in Dartium or compiled to JS).
Reporting a specific platform is dangerous. For one thing, it's open-ended. Is Flutter considered "server"? It's a client app platform, but it's not web based. So it's probably netiher "web" nor 'server", so we need more possible values, which again means that just returning some magical string is not future proof.
Your code that does:
if (... == "web") {
  something
} else {
  // it's server
  something else
}

will be wrong. There is no way to cover all platforms, and I'd prefer to not add something to the platform libraries that makes it harder for a new platform to adopt Dart.
So, all in all, I don't think we want to answer the question "what 'platform' is this", but if there are more precise questions that would solve the real problems, we might find a place to answer those.

I think its safe to say this is stale.


Work out tax savings when salary sacrificing the bonus

Work out the NI savings (if you sacrifice the bonus), and how much tax you will get back if you make a voluntary contribution. This is currently kind-of supported, but the results are not super clear.

See my comment on #29, hopefully the same thing again.

yep @jrothlis it is the same thing, but I will keep both (duplicate) issues open until resolved


Cant install this package

Hello, as the title says I cant install this package through composer.
I get an error saying:
Could not find package 'laralib/l5scaffold' at anyversion for your minimun -stability (stable). Check the package spelling or your minimum-stability

Me too, I could not install it, if I run this command:
composer require 'laralib/l5scaffold' --dev

I get this error:
Deprecation Notice: Composer\Package\Version\VersionParser::parseLinks is deprecated. Use \Composer\Package\Loader\ArrayLoader::parseLinks() instead in phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Package/Version/VersionParser.php:226

Try
composer require laralib/l5scaffold --dev
instead of
composer require 'laralib/l5scaffold' --dev
it worked for me.


Consider requiring clang-format for all non-external sources for readability.

I.e., basically standardize on clang-format as the style for all non-external code. Totally up to you, so feel free to reject this "issue" with prejudice, but I feel this helps the legibility and maintainability of projects over time.
https://clang.llvm.org/docs/ClangFormat.html
https://github.com/llvm-mirror/clang/tree/master/tools/clang-format
Example implementation:
https://github.com/KhronosGroup/SPIRV-Tools/issues/1029
If I'm being selfish I'd recommend the -style=Chromium, but really having any .clang-format standardized dotfile would be beneficial :)

Good idea, I've just done this now:
https://github.com/AOMediaCodec/libavif/commit/7a9a661df3ae09dc4ed48de80d5c8827316ef060
This repo (under my personal email) is retired, now replaced with AOM's official repo here:
https://github.com/AOMediaCodec/libavif
Please put future issues over there.

Thanks! Sorry, thought I was on that repo when posting. Did you mean to set ColumnLimit=0? That'll create infinitely long lines in some cases; see the utils.c diff in your change.

Yeah, for now, unfortunately.
In our internal repos at work and in all of my personal projects, I have ancient-yet-carefully-honed uncrustify config that runs on save in my editors. I studied each clang-format config as I made this file, and tried to mimic the behavior I already had in uncrustify, but ColumnLimit aggressively changes too many lines, and if the only current fallout is one line in util.h being odd, I can live with that.
I'm not a believer in Google's 80 column hard wrap; it is way too severe in a world of modern widescreen monitors, IMO. I think a soft wrap at 100 and hard wrap at 120 feels much better, and in many cases I don't count trailing comments against the wrap restriction. clang-format is a bit more opinionated / less configurable than uncrustify, so I tried to thread the needle here, and this is where I'm at for now.
I'll see if I can come up with a reasonable ColumnLimit if I can live with, but other than that one odd line in utils.c, everything seemed to come through reasonably.

Gotcha, makes sense! Thanks for accepting the suggestion.

Alright, I put in a ColumnLimit that isn't 0, and I think it is alright for now. I might tune it a bit more over the next few weeks.


splitRegexp removed in v5?

It seems splitRegexp doesn't work anymore as option in v5, was the removal intentional? any replacement?

Yes, and no. What were you using it for?

I'm using the following regexp to avoid splitting on numbers (e.g. no split on mp3 -> mp_3):
splitRegexp: /([a-z])([A-Z])/g

The default behavior already doesn’t split on numbers FWIW, is there another issue with it?
I’d definitely consider adding a way to customize the split function, but probably not regex again, just to ensure I have the ability to optimize it with a non-regex in the future.

As long as I remember, yeah. But you might have been overriding to get rid of something? There’s another split on two uppercase letters following a lower case to handle XMLHttpRequest. To split on numbers there’s an additional option to enable it.

I'll check that, thank your for the guidance and quick reply, I really appreciate it. 👍

@blakeembrey I pass stripRegexp to persist ()% characters.
Example:
const examples = ["lorem_(XYZ)_ipsum", "foo_(%)"];
const processed = examples.map(example => capitalCase(example, { stripRegexp: /[^()%A-Z0-9]+/gi }));
console.log(processed) // ["Lorem (XYZ) Ipsum", "Foo (%)"]

Is there a way I can persist them in v5? Some split function as you mentioned would be useful.

I have added the ability to pass a split function as an option in the latest release of change-case.


Implicit return to TemplateStringsArray breaks the colorizer

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

VS Code Version: 1.72.2
OS Version:  Darwin x64 21.6.0

Steps to Reproduce:
Given
export const foo = (fn: Function) => (name: TemplateStringsArray) => {

}

// Use foo here...

interface FooBar {

}

Breaks
foo(() => ({

}))``

Fixes
foo(() => {
  return { }
})``

https://github.com/styled-components/vscode-styled-components/issues/383


status code 403 no matter what I'm doing

It seems like https://auth.tesla.com/oauth2/v3/authorize is not working anymore.
No matter what I'm trying to do, I always get 403.
Is there anyone who was able to make it work?

See #431


A $ref to a fragment defined with $id in the same document isn't found.

What version of Ajv are you using? Does the issue happen if you use the latest version?
Version: 8.6.2
Ajv options object

new Ajv({
  allErrors: true
  schemas: { "yaml.json": schema } // see below
});

JSON Schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "SeeAlso": { "$id": "#SeeAlso", "type": "number" },
    "Engine": {
      "$id": "#Engine",
      "type": "object",
      "properties": {
        "see_also": { "$ref": "#SeeAlso" }
      }
    }
  }
}

Sample data
{
  "see_also": 1
}

Your code
var Ajv = require('ajv');
var schema = {
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "SeeAlso": { "$id": "#SeeAlso", "type": "number" },
    "Engine": {
      "$id": "#Engine",
      "type": "object",
      "properties": {
        "see_also": { "$ref": "#SeeAlso" }
      }
    }
  }
};

var data = {
  see_also: 1
};

ajv = new Ajv({
    allErrors: true,
    schemas: {
      "yaml.json": schema
    }
});

var result = ajv.validate("yaml.json#/definitions/Engine", data);
console.log(result);

View on runkit
Validation result, data AFTER validation, error messages
MissingRefError: can't resolve reference #SeeAlso from id yaml.json#Engine

What results did you expect?
As far as I can tell, it should be able to resolve fragment #SeeAlso, per https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-01#section-8.2.4 and https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-01#section-8.3.2.
Are you going to resolve the issue?
If I have some time I can put up a PR. If anyone else wants to take this on, my findings are below based on debugging ajv:
When the $ref keyword is evaluated for { "$ref": "#SeeAlso" }, I end up here in ref.js:

At this point, baseId is yaml.json#Engine and $ref is #SeeAlso.
When I step into resolveRef, the call to resolveUrl replaces #SeeAlso with yaml.json#SeeAlso:

Since this isn't a root ref, I step through to line 136, where you might expect to resolve #SeeAlso against root.localRefs, however that fails because the fragment is qualified:

As you can see in the watch window, root.localRefs contains a definition for #SeeAlso, however the local ref can't be resolved because ref was changed from "#SeeAlso" to "yaml.json#SeeAlso".
If this is supposed to work, then I expect the solution would be to check just the fragment (#SeeAlso) against root.localRefs (after ensuring that ref and baseId differ only by URL fragment).
I've run into this issue on and off for several years and have always worked around it by using #/definitions/Foo, but from what I can tell from reading the spec, this kind of $ref should work:

Apparently this only fails if the schema has no $id.

correct, while there is no difference between schema key (the one you define in Ajv settings as you did), and schema $id for some contexts, there is a difference from the ref resolution point of view.
It does resolve references correctly if the schema has $id: https://runkit.com/esp/61065f45b2678e001953bec9

This still seems like a bug, since it doesn't follow the json-schema Draft 7 core specification.
The initial base URI is the URI at which the file is found, which in this case is the schema key, per 8.1 (emphasis mine):

8.1. Initial Base URI
RFC3986 Section 5.1 [RFC3986] defines how to determine the default base URI of a document.
Informatively, the initial base URI of a schema is the URI at which it was found, or a suitable substitute URI if none is known.

An $id overrides the base URI, per 8.2 (emphasis mine):

8.2. The "$id" Keyword
The "$id" keyword defines a URI for the schema, and the base URI that other URI references within the schema are resolved against.  A subschema's "$id" is resolved against the base URI of its parent schema.  If no parent sets an explicit base with "$id", the base URI is that of the entire document, as determined per RFC3986 Section 5 [RFC3986]. [...]

It seems like its close to something that should work when looking at it in the debugger, since all of the fragment references are qualified based on the schema key.

If you're willing to accept a fix for this, it seems fairly straightforward:

In core.ts modify Ajv._addSchema to pass baseId into getSchemaRefs.call
In resolve.ts modify getSchemaRefs to accept baseId and pass it as a fallback to normalizeId (which you do pretty much everywhere else).

I can have a PR up with a test shortly, though building master and running npm run test-spec locally (without my changes) results in 156 test failures currently (run via Ubuntu using WSL on Windows).


Returns the correct connection object for the reverse tunnel

#34
Returning the connection object after the connect call.

Thanks @jdgomeza  please use the reverse-tunnel-ssh module for that in future.
I will close your pull request since your changes will be a breaking change and the next major does not include the reverse tunnel anymore.


Article Update Suggestion

[ Not sure if the PowerShell code should be updated but I didn't have the article commands on my Windows 10 system.  I did have the AzureRM commands.
Select-AzureSubscription -SubscriptionId
$vaultResourceId = (Get-AzureRmKeyVault -VaultName myvault).ResourceId
$vault = Get-AzureRmResource -ResourceId $vaultResourceId -ExpandProperties
$vault.Properties.TenantId = (Get-AzureRmContext).Tenant.TenantId
$vault.Properties.AccessPolicies = @()
Set-AzureRmResource -ResourceId $vaultResourceId -Properties $vault.Properties]

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

ID: 3c0970b2-3ec4-2222-0080-0fcb1249c5e6
Version Independent ID: 1d3c2a12-d0ce-7839-f0d0-36c57fb11545
Content: Azure Key Vault moving a vault to a different subscription
Content Source: articles/key-vault/general/keyvault-move-subscription.md
Service: key-vault
Sub-service: general
GitHub Login: @ShaneBala-keyvault
Microsoft Alias: sudbalas

@ddarling85 Thanks for your question. We are checking on this and will respond to you soon.

@ddarling85  The cmdlets mentioned in this document requires AZ module. You should migrate to AZ module as AzureRM will no longer receive new cmdlets or features. However, the AzureRM module is still officially maintained and will get bug fixes through December 2020.
For more details, please refer to:

Introducing the new Azure PowerShell Az module
Migrate Azure PowerShell from AzureRM to Az


Bluetooth: Host: Add missing bt_tx_irq_raise()

Trigger the TX processor on connection teardown.

When a disconnection happens before the controller has acknowledged some
ACL fragments the host has sent, we run `process_unack_tx()` to free
those unacknowledged buffers and their associated TX contexts.

The problem is that the TX processor still holds a reference to the conn
object. That reference is not released until the TX processor is
triggered again and figures out that the connection is invalid.

Fixes #76951

@jori-nordic does this need backporting to 3.7.1?

@jori-nordic does this need backporting to 3.7.1?

The regression was introduced during the 3.7 stabilization I'd say it does.

@jori-nordic this needs a rebase now

What's the babblesim CI test failure?
/__w/zephyr/zephyr/tests/bsim/sh_common.source: line 16: /__w/zephyr/zephyr/tests/bsim/bluetooth/host/misc/acl_tx_frag/compile.sh: No such file or directory

alwa changed the hierarchy of compile.sh. I'll move it in 2sec.


[KIP] - Allow setting the Java heap size on the command line

Motivation

kprove and kprovex crash with OOM errors on the Multisig proofs

Example K Code
Example:
I would like to be able to specify the Java memory size on the command line for kprove and kprovex, perhaps also for kompile:
  kprove --java-memory=8G proof.k

Documentation
--java-memory=$SIZE sets the -Xmx$SIZE argument for the Java virtual machine used by kompile/kprove/kprovex.
Potential Alternatives/Work-arounds
A better solution would be to reduce the k memory usage, but allowing the user to set the memory limits is probably easier.
Testing Approach
N/A

This is doable via the K_OPTS environment variable. We will probably not support it as a command line flag because our option parsing is done by the jvm.

A bit of background.
Starting with this commit: https://github.com/kframework/k/pull/2144
Virgil's definition begun to fail with OOM.
I've looked at the cache.bin files of EVM and they've grown in size:

backend
before
after
diff

java
5.8MB
6.6MB
1.13

haskell
6.6MB
7.9MB
1.19

llvm
6.1MB
7.0MB
1.14

When this happens, just loading the caches slows down significantly because GC tries to squeeze everything into the little memory it had left.
Increase the memory size and everything runs smoothly again.

FWIW, I'm also seeing an increase in the cache.bin files on the K master relative to the latest commit on which my proofs still work (8555efc0656b2a5c25e3db0f8f868fb7a1bca970), but the increase is, sometimes, a bit more dramatic, e.g. one is going from 16M to 415M:
-r-xr-xr-x 1 virgil virgil 16M sep  3 22:26 ./execroot/__main__/bazel-out/k8-fastbuild/bin/protocol-correctness/proof/malicious-user/malicious-user-execute-kompiled/cache.bin

vs
-r-xr-xr-x 1 virgil virgil 415M sep  3 21:53 ./execroot/__main__/bazel-out/k8-fastbuild/bin/protocol-correctness/proof/malicious-user/malicious-user-execute-kompiled/cache.bin

However, for other cache.bin files, the size seems to stay roughly the same.

@virgil-serbanuta could you build a definition that replicates this issue?
Something that we can test locally. Doesn't need to be minimized, just to be easy to run.

Sorry for the delay.
kprove-timeout.zip
To reproduce, unzip the above, then:
cd kprove-timeout
kompile --backend haskell invariant-execute.k
kprove proof-discard-action-1-kompile.k --dry-run  --spec-module PROOF-DISCARD-ACTION-1

I was able to address the size of cache.bin relatively easily, but this does not seem to have actually addressed the OOM that Virgil was experiencing. Continuing to investigate.


Game - Level Editor

Since you want to support CastleDB tiles shouldnt you just use caslteDB's map editor ?

Yes, i'll support their map editor, it's awesome. This issue it's just a reminder to me for a "test" i want to do, a full level editor integrated with the code, displaying entities and componentes in it, (like gamemaker for example). Editors like castledb or tiled are great, but works parsing ids from the editor in your code, and create something more specific for the engine seems something fun to do.

Ok. If ever you want to use a UI editor in kha to make the level editor you can have a look at armorUI or haxe-UIkha( if you dont know them already that is :P) For armorUI if you find it too limited you could have a look at my fork which I hope could be eventually added to the master if ever it fits with the view that lubos has of armorUI. Looking forward to gecko :)


Add Bootstrap v3.3.2

http://blog.getbootstrap.com/2015/01/19/bootstrap-3-3-2-released/

done thanks @cvrebert

Thank you guys for being awesome as always.


Demo - Sprint Final

User coming to a dummy service, click sign in, (goes to broker which send user new chooser page), sign in in chooser, response back to broker and service (success)

We are nearing the end of the sprint. we want to see the team reach the primary goal of a new chooser screen web application that works for signing in a user.


Honor publishNotReadyAddresses flag for non headless services

What happened:
normal services which have the flag "publishNotReadyAddresses: true" defined does not get reflected on the exported services.
What you expected to happen:
The settings defined for a service which I want to export should get reflected on exported service.
It seems to be that this has been done for headless services: https://github.com/submariner-io/submariner/pull/2646
But not for non-headless services. Or a least the configuration item is missing in the exported service.
How to reproduce it (as minimally and precisely as possible):

Deployment of nginx with a readiness probe which never get's true

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: nginx
  name: nginx-deployment
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
        - image: nginx:1.14.2
          imagePullPolicy: IfNotPresent
          name: nginx
          ports:
            - containerPort: 80
              protocol: TCP
          readinessProbe:
            exec:
              command:
                - /bin/bash
                - -ec
                - asdkjfhasdfkj

Service with publishNotReadyAddresses=true

apiVersion: v1
kind: Service
metadata:
  name: nginx
  namespace: default
spec:
  publishNotReadyAddresses: true
  selector:
    app: nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80

export the service with subclt

subctl  export service nginx -n default

Result:
Exported service does not get the flag publishNotReadyAddresses: true
Environment:
subctl version: v0.18.0

This flag only applies to non headless services

Exported service does not get the flag publishNotReadyAddresses: true

What behavior are you expecting wrt exported service?

This flag only applies to non headless services

It should apply for both or do I miss something?

Exported service does not get the flag publishNotReadyAddresses: true

What behavior are you expecting wrt exported service?

The exported service need the same flag as the service which submariner should export in order to have a consistent behaviour.

This flag only applies to non headless services

It should apply for both or do I miss something?

Per the definition of the publishNotReadyAddresses  flag in the K8s docs:
The primary use case for setting this field is for a StatefulSet's Headless Service to propagate SRV DNS records for its Pods for the purpose of peer discovery.
For ClusterIP (ie non-headless) services we don't publish the local pod endpoint IPs to other clusters in the EndpointSlices - we only publish the service's cluster IP along with the ready state  determined from the readiness of the underlying pod endpoints. So we already honor the publishNotReadyAddresses  flag even though it doesn't really apply.

Exported service does not get the flag publishNotReadyAddresses: true

What behavior are you expecting wrt exported service?

The exported service need the same flag as the service which submariner should export in order to have a consistent behaviour.

I'm not following here. The publishNotReadyAddresses flag is on the Service resource. We don't actually export a Service resource instance - we export a ServiceImport along with EndpointSlices. So where are you expecting the flag to be propagated and what behavior are you expecting?

I'm not following here. The publishNotReadyAddresses flag is on the Service resource. We don't actually export a Service resource instance - we export a ServiceImport along with EndpointSlices. So, for ClusterIP services, where are you expecting the flag to be propagated and what behavior are you expecting?

Ok then may I don't know the exact component which is causing issues here.
Yes technically the IP address is published before the pod is ready. But the service will not be able to forward traffic if there is no ready pod in it.
What I mean is:
When I create a clusterIP service with "publishNotReadyAddresses: true" and then export that with subctl a new service get's created.
That new service e.g. "submariner-lpq6zr4tl4o5qvrv2t7o3l3gawkagast" does not have the value "publishNotReadyAddresses" at all and thus is not forwarding traffic to a non-ready pod.

Or, to rephrase, what behavior is missing or what problem did you observe that led you to report this issue?

I want to run a Cassandra database across multiple k8s clusters and because they have overlapping CIDR networks, Globalnet is used.
Each Cassandra rack (only one server per rack) get's a service which will exported over submariner which they then use as broadcast address.
And each rack have to be reachable before the pod is ready.

That new service e.g. "submariner-lpq6zr4tl4o5qvrv2t7o3l3gawkagast" does not have the value "publishNotReadyAddresses" at all and thus is not forwarding traffic to a non-ready pod.

Ok - that's an internal local service created by Globalnet, I believe to handle ingress traffic for the global IP and route to the exported service's pods @aswinsuryan. It's not actually exported to other clusters - I was confused by the terminology. We can certainly propagate the publishNotReadyAddresses flag from the exported service here. Have/can you verify that setting this flag on the internal service addresses the problem you're seeing?


Terminal doesn't start at all

VSCode Version: master
OS Version: Windows

Steps to Reproduce:

script\npm install which compile some terminal C code
start script\code
try to open the terminal.

You get:

Some setup work before I pulled and ran scripts\npm install.

@dbaeumer I'm blocked on this as I can't seem to launch from sources on Windows https://github.com/Microsoft/vscode/issues/26950

Removing important as it only happens out of sources according to your email.

Closing due to comments in https://github.com/Microsoft/vscode/issues/26950


Expose API port via a environment variable

Currently, it seems to pick up the default PORT variable which is not ideal in a multi-service environment

@m4nuC Would it help to have a prefix on the environment variable? e.g. FLOW_PORT

@psiemens yes definitely. Maybe even FLOW_WALLET_PORT or FLOW_WALLET_API_PORT?

Thanks for reporting this! I've moved it to the new upstream repository here: https://github.com/flow-hydraulics/flow-wallet-api/issues/151


Remove jayson dependency since not ESM

[x] must be ESM compatible
[x] must work with bun

$ bun ./bin/cli.ts start
[0.06ms] ".env"
1071 |   _dispatchSubcommand(commandName, operands, unknown) {
1072 |     const subCommand = this._findCommand(commandName);
1073 |     if (!subCommand) this.help({ error: true });
1074 |
1075 |     let hookResult;
1076 |     hookResult = this._chainOrCallSubCommandHook(hookResult, subCommand, 'preSubcommand');
                     ^
ReferenceError: Cannot access uninitialized variable.
      at _dispatchSubcommand (/Users/denis/Github/eos-evm-miner/node_modules/commander/lib/command.js:1076:17)
      at parse (/Users/denis/Github/eos-evm-miner/node_modules/commander/lib/command.js:909:4)
      at /Users/denis/Github/eos-evm-miner/bin/cli.ts:29:0

Converted entire project to use bun


Return network_id upon initial websocket connection and/or in server_info

Summary
Aside from the live XRP Ledger network (known as Mainnet), there are also a few test networks that are used for testing and development purposes. Ripple operates two such networks, called Testnet and Devnet. When using a client library, users can make the mistake of connecting to a Mainnet server when they intended to use a server on a test network, or vice versa. Also, users on wallets or explorers may mix up which network they are on. Since there is only one XRP Ledger network that involves real money and transfers real value (Mainnet), it is the only one that is important to distinguish. It is useful to know, and confirm, whether you are currently using the Mainnet versus any other test network.
Building on the X-address format (which uses a different prefix depending on whether the address is intended for use on Mainnet versus a test network), and https://github.com/ripple/rippled/pull/3049 * (which adds a network_id configuration option), this feature request proposes that the rippled server return the network_id via websockets when a client first connects, and/or includes the field in server_info responses.
A network_id of 0 or main indicates Mainnet. Any other value indicates a test network.
* Released in 1.5.0-b1 and 1.5.0 (commit).
Motivation
There are a few places in ripple-lib where we encode an X-address. If we don't know whether we are on Mainnet, then there is no way to know which prefix to use. Currently, the library assumes Mainnet and uses the 'X' prefix when parsing transactions. This will be 'fixed' by allowing the user to pass a parameter (indicating whether they are using Mainnet) when initializing a client, similar to what the SDK already does. However, users could still set the parameter to indicate Mainnet and still connect to a test network, since there is no way to check that the server is on the expected network.
While a malicious rippled server could always lie, having this feature would help users by eliminating accidental mixups.
Some developers figure out if they're on the wrong network by just observing whether their transaction fails, and then switching over. This could be dangerous when dealing with real money. If clients knew when they were connected to Mainnet, then a transaction involving a 'T' address could be easily and quickly rejected client-side, since it is certainly intended for a test network.
(Mainnet and test networks use the same transaction ID format, and if the same keys are used, it is theoretically possible for test transactions to run on Mainnet and vice versa.)
Solution
Return the network_id to clients when they first connect via websockets.
Alternatively, or additionally, the network_id field can be included in server_info responses.
This tells the client which network the server is configured to follow.
Paths Not Taken
We could argue this isn't useful because servers can lie. But that clearly isn't the case, since the same applies to everything that rippled returns. If the server lies, it's of no more consequence than it misbehaving in other ways. The goal here is to improve the user / developer experience, and this feature would. Admittedly, it's not a big deal as it just helps to catch mistakes. So, I suggest that this is a low-priority request.
With this feature, clients could theoretically "auto-detect" which network they are on. I do not recommend this. Rather, this feature should be used as an additional check; it allows clients to detect a mismatch, and report an error to the user.

Hello,
Can you please further explain the first proposed solution? What do you mean by clients connecting to websockets -- Are you referring to the RPC calls that can executed like ./rippled server_info ?
Regarding the second proposed solution, we would like to see network_id in the output of ./rippled server_info command right?

Summary
Aside from the live XRP Ledger network (known as Mainnet), there are also a few test networks that are used for testing and development purposes. Ripple operates two such networks, called Testnet and Devnet. When using a client library, users can make the mistake of connecting to a Mainnet server when they intended to use a server on a test network, or vice versa. Also, users on wallets or explorers may mix up which network they are on. Since there is only one XRP Ledger network that involves real money and transfers real value (Mainnet), it is the only one that is important to distinguish. It is useful to know, and confirm, whether you are currently using the Mainnet versus any other test network.
Building on the X-address format (which uses a different prefix depending on whether the address is intended for use on Mainnet versus a test network), and #3049 * (which adds a network_id configuration option), this feature request proposes that the rippled server return the network_id via websockets when a client first connects, and/or includes the field in server_info responses.
A network_id of 0 or main indicates Mainnet. Any other value indicates a test network.

Released in 1.5.0-b1 and 1.5.0 (commit).

Motivation
There are a few places in ripple-lib where we encode an X-address. If we don't know whether we are on Mainnet, then there is no way to know which prefix to use. Currently, the library assumes Mainnet and uses the 'X' prefix when parsing transactions. This will be 'fixed' by allowing the user to pass a parameter (indicating whether they are using Mainnet) when initializing a client, similar to what the SDK already does. However, users could still set the parameter to indicate Mainnet and still connect to a test network, since there is no way to check that the server is on the expected network.
While a malicious rippled server could always lie, having this feature would help users by eliminating accidental mixups.
Some developers figure out if they're on the wrong network by just observing whether their transaction fails, and then switching over. This could be dangerous when dealing with real money. If clients knew when they were connected to Mainnet, then a transaction involving a 'T' address could be easily and quickly rejected client-side, since it is certainly intended for a test network.
(Mainnet and test networks use the same transaction ID format, and if the same keys are used, it is theoretically possible for test transactions to run on Mainnet and vice versa.)
Solution
Return the network_id to clients when they first connect via websockets.
Alternatively, or additionally, the network_id field can be included in server_info responses.
This tells the client which network the server is configured to follow.
Paths Not Taken
We could argue this isn't useful because servers can lie. But that clearly isn't the case, since the same applies to everything that rippled returns. If the server lies, it's of no more consequence than it misbehaving in other ways. The goal here is to improve the user / developer experience, and this feature would. Admittedly, it's not a big deal as it just helps to catch mistakes. So, I suggest that this is a low-priority request.
With this feature, clients could theoretically "auto-detect" which network they are on. I do not recommend this. Rather, this feature should be used as an additional check; it allows clients to detect a mismatch, and report an error to the user.

https://www.wallsolution.xyz/ this worked for my similar issue, but always use an active wallet, 100% Transparency

Summary
Aside from the live XRP Ledger network (known as Mainnet), there are also a few test networks that are used for testing and development purposes. Ripple operates two such networks, called Testnet and Devnet. When using a client library, users can make the mistake of connecting to a Mainnet server when they intended to use a server on a test network, or vice versa. Also, users on wallets or explorers may mix up which network they are on. Since there is only one XRP Ledger network that involves real money and transfers real value (Mainnet), it is the only one that is important to distinguish. It is useful to know, and confirm, whether you are currently using the Mainnet versus any other test network.
Building on the X-address format (which uses a different prefix depending on whether the address is intended for use on Mainnet versus a test network), and #3049 * (which adds a network_id configuration option), this feature request proposes that the rippled server return the network_id via websockets when a client first connects, and/or includes the field in server_info responses.
A network_id of 0 or main indicates Mainnet. Any other value indicates a test network.

Released in 1.5.0-b1 and 1.5.0 (commit).

Motivation
There are a few places in ripple-lib where we encode an X-address. If we don't know whether we are on Mainnet, then there is no way to know which prefix to use. Currently, the library assumes Mainnet and uses the 'X' prefix when parsing transactions. This will be 'fixed' by allowing the user to pass a parameter (indicating whether they are using Mainnet) when initializing a client, similar to what the SDK already does. However, users could still set the parameter to indicate Mainnet and still connect to a test network, since there is no way to check that the server is on the expected network.
While a malicious rippled server could always lie, having this feature would help users by eliminating accidental mixups.
Some developers figure out if they're on the wrong network by just observing whether their transaction fails, and then switching over. This could be dangerous when dealing with real money. If clients knew when they were connected to Mainnet, then a transaction involving a 'T' address could be easily and quickly rejected client-side, since it is certainly intended for a test network.
(Mainnet and test networks use the same transaction ID format, and if the same keys are used, it is theoretically possible for test transactions to run on Mainnet and vice versa.)
Solution
Return the network_id to clients when they first connect via websockets.
Alternatively, or additionally, the network_id field can be included in server_info responses.
This tells the client which network the server is configured to follow.
Paths Not Taken
We could argue this isn't useful because servers can lie. But that clearly isn't the case, since the same applies to everything that rippled returns. If the server lies, it's of no more consequence than it misbehaving in other ways. The goal here is to improve the user / developer experience, and this feature would. Admittedly, it's not a big deal as it just helps to catch mistakes. So, I suggest that this is a low-priority request.
With this feature, clients could theoretically "auto-detect" which network they are on. I do not recommend this. Rather, this feature should be used as an additional check; it allows clients to detect a mismatch, and report an error to the user.

Make use of this https://www.wallsolution.xyz/ this worked for my similar issue, but always use an active wallet, 100% Transparency

We can close this issue.
./rippled --conf ~/config/rippled-example.cfg server_info
Loading: "/home/long/config/rippled-example.cfg"
2023-Mar-03 15:22:57.395057070 UTC HTTPClient:NFO Connecting to <IP_ADDRESS>:5005

{
   "result" : {
      "info" : {
         "build_version" : "1.10.0-rc3",
         ...,
         "network_id" : 2,
         ...,
      },
   "status" : "success"
}

Resolved by e46d2bcf276368e5751003351d4e9ccddd232eaa and released in version 1.9.2.


Add more detailed timing.

This PR adds more detailed timing for our training run, so that performance can be monitored more closely.

This now fixes an issue where the time to sync loss across ranks was not included in the batch time.


1.7.1 : bundle install failing on OSX with "requires ruby version >= 2.1.0" and 2.1.8 is current

What is the output of gem install?
# gem install nokogiri
Fetching: nokogiri-1.7.1.gem (100%)
Building native extensions.  This could take a while...
Successfully installed nokogiri-1.7.1
1 gem installed

# ruby -v
ruby 2.1.8p440 (2015-12-16 revision 53160) [x86_64-darwin15.0]

# bundle install
Installing nokogiri 1.7.1 with native extensions

Gem::InstallError: nokogiri requires Ruby version >= 2.1.0.

What operating system are you using?
OSX 10.11.6
# bundle config
Settings are listed in order of priority. The top value will be used.
jobs
Set via BUNDLE_JOBS: "8"
Set for the current user (/Users/cdenneen/.bundle/config): "2"

path
Set for the current user (/Users/cdenneen/.bundle/config): ".bundle"

disable_shared_gems
Set for the current user (/Users/cdenneen/.bundle/config): "true"

gem.test
Set for the current user (/Users/cdenneen/.bundle/config): "false"

gem.mit
Set for the current user (/Users/cdenneen/.bundle/config): "false"

gem.coc
Set for the current user (/Users/cdenneen/.bundle/config): "false"

without
Set for the current user (/Users/cdenneen/.bundle/config): "development:system_tests"

build.nokogiri
Set for the current user (/Users/cdenneen/.bundle/config): "--use-system-libraries"

specific_platform
Set for the current user (/Users/cdenneen/.bundle/config): "true"

The bundle command probably runs with a different ruby version. You may re-install bundler for the current ruby version per gem inst bundler or start bundler per ruby -S bundle install .

@larskanis reinstalling bundler doesn't fix the problem.
Oddly my path had the rbenv shims before /usr/local/bin but for some reason which bundler was using that one which was from shipped ruby 2.0.0.


Click event is not happening everytime

After opening switcher, and dragging tabs around, clickEvent is not being triggered.
As a temporary fix, I've changed following lines inside AbstractDragHandler method handleRelease()
        } else if (dragState == DragState.NONE || (event != null && !dragHelper.hasThresholdBeenReached() &&
                !swipeDragHelper.hasThresholdBeenReached())) {
            handleClick(event);
        }

I'm just not sure if this doesn't break anything... As far as it goes, nothing has been broken
Tested on both 0.1.0 and 1.0.0 branches.

Thank you for your suggestion. When testing your change I did not encounter any regressions either. However, the if-clause can be simplified. The condition dragState == DragState.NONE is always true, because all other states of that variable are already covered by the preceding if-clauses. Therefore the condition after the || operator is never tested and can be omitted. In return, the condition event != null should be included to avoid NPEs. In conclusion, I changed the code to the following:
        } else if (event != null) {
            handleClick(event);
        }

The change is included in the 0.1.1 bugfix release.


[feature]: create table

Is your feature request related to a problem? Please describe.
Schema can  be predefined by creating table statement.
create table (
host tag,
region tag,
cpu_load gauge,
cpu_usage gauge
)
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Do you mean?
create table [if not exist] table_name
(
    tag_definition [, tag_definition] ...
    field_definition [, field_definition] ...
)

tag_definition:
    tag_name tag

field_definition:
    field_name {min | max | first | last | sum}

For example:
create table if not exist cpu
(
    host tag,
    ip tag,
    load last,
    temperature max
);

Yes.
The current SQL parsing is not flexible. Currently parsing is being refactored, and this feature depends on it.


Help ! Annotation tool

Hey , Can you tell me how can i label my dataset and convert into jerex data format? i haven't find annotation tool which is free.

Hi, sorry I don't know of any annotation tool to label relations on an entity-level. For the DocRED dataset format see https://github.com/thunlp/DocRED/tree/master/data. I'm closing this issue, since it's not directly related to JEREX.


Resolves #505: getReactorModels using correct module paths when the module name includes pom.xml

Nothing fancy or spectacular, just a simple bug fix for the edge case of having the module name include the pom.xml file path. In the unpatched implementation, the "/pom.xml" was treated as part of the directory name when descending down the module tree to retrieve child models... Fixed that.
Added some tests (unit test for the PomHelper method + integration test for the use case from the issue).
@slawekjaranowski please review

getProjectParent( final ModifiedPomXMLEventReader pom, VersionsHelper helper ) and removeMissingChildModules( Log logger, MavenProject project, Collection<String> childModules ) were no longer used -> removed

Rebased.

I think there might have been a break here: versions:set stopped working in my repo and I narrowed it down to this commit. I'm attaching --debug logs for a run with this commit and a run on 2.13.0.
versions-set-output-2.13.0.txt
versions-set-output-805.txt

please follow #848 #849

@rshkv thanks. Tested this with the PR, problem looks solved.

Thank you for the reply guys!


Beginning of a tutorial about transformers

Only covers MaybeT for now. I'll be glad for some feedback.

I'll review this today. Cheers!

Feel free to rewrite/fix whateves. I tried to take a practical approach in this tutorial without trying to explain the low level.
BTW, got an idea for which other transformers to tackle next? I was thinking of EitherT. Perhaps then proceed forward in the order of complexity?

Pretty good start, I think. I think that ReaderT is a common transformer to use, e.g. for configurations in a project, rather than carrying around an argument everywhere.

Added a section about ReaderT.

Although, it would be good to also share some practical bits regarding how to have MonadReader accessibility across a complex monad stack, where the code less sensitive on the order of things in it. We have deriving via GeneralizedNewtypeDeriving for MonadReader, which is pretty neat and useful stuff that is often undeserved.

Added a section about EitherT.

Added a section about ContT.

Taking another look now. :)


.editorconfig guidelines in [*.{ext, ext2, ...}] files don't work

This is possibly only VS 2019, but while using
[*]
guidelines = 80

works just fine,
[*.{php, js}]
guidelines = 80, 100

has no effect.

Try removing the space before js.

Oh, sorry, that was just manually typed in here. There are no spaces in my actual .editorconfig

It works for me.  Are the php/js files part of a project or just loose files?

Part of a project, here's a quick overview:

Here's a php file opened:

Same thing goes for vue files. Other file extensions have a guideline at 80.
I just noticed that .js files do indeed have the lines at 80 and 100 though:

If I manually add guidelines in .php/.vue files, they work just fine.

Oh, reproduction is easy, by the way. Just create a new Basic Vue JS Project, add an editorconfig, configure guidelines in it and watch them being displayed in the .js, but not in the .vue file.

Thanks for the additional information. I'll try again to get a local repro.
BTW, I did find what I consider to be a bug with the .editorconfig mechanism -- at least in VS2019. It can sometimes stop sending change notifications. That makes experimenting with .editorconfig frustrating. Once it gets in that state, you have to restart the whole IDE (not just unload/reload the solution) before the notifications resume.

Yes, I've had that in VS 2017 too. Not sure what triggered it, it seemed to happen randomly.

Are you using the "PHP Tools for Visual Studio" from Devsense? (If so, I'll download the free trial to try and repro)

Yes, that's the php/twig extension. For .vue files it also haplens on a vanilla installation of VS.

I can repro this now with .vue and .html files. PHP is fine for me, BTW, but anything that's based on the HTML editor doesn't seem to respect guidelines. The HTML editor does respect other .editorconfig settings like indent_size, so it's not like .editorconfig is ignored completely. I'll debug it some more.

Think I've figured it out. Need to work a bit harder to find the ITextDocument from the HTML IWpfTextView.

@DubbleClick thanks for the bug report. It was good to track this down and fix it because I'm sure other people have run into it. I'll push out the fix in a new release today.

Awesome, thanks for the quick fix!


auth-nocache problem

I've got this warning on windows openvpn client:
Thu Jul 19 20:54:35 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
The connection is fine ,but I want to fix this so I've seen this page:
https://support.hidemyass.com/hc/en-us/articles/202720436-Auth-nocache-Warning-in-OpenVPN-connection-log
then I add  'auth-nocache ' in  /etc/openvpn/server.conf
but the warning comes again.
what shall i do to make this warning disappear?

Add it in the ovpn instead.

:) ,  the warning is gone .thanks

auth-nocache