Use of hard-coded passwords and binding to <IP_ADDRESS> are security smells

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts.
I noticed instances of hard-coded passwords, which are against the best practices
recommended by Common Weakness Enumeration (CWE) [https://cwe.mitre.org/data/definitions/259.html] and also by other security practitioners.
I suggest use of undef to mitigate this smell. Feedback is welcome.
PR: https://github.com/puppetlabs/pltraining-bootstrap/pull/354
Source: https://github.com/puppetlabs/pltraining-bootstrap/blob/master/manifests/role/learning.pp

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts. I noticed instances of binding to <IP_ADDRESS>. Binding an address to <IP_ADDRESS> indicates allowing connections from all IP addresses. I would like to draw attention to these instances. Binding to <IP_ADDRESS> may lead to denial of service attacks. Practitioners have reported how binding to <IP_ADDRESS> facilitated security issues for MySQL (https://serversforhackers.com/c/mysql-network-security), Memcached (https://news.ycombinator.com/item?id=16493480), and Kibana (https://www.elastic.co/guide/en/kibana/5.0/breaking-changes-5.0.html).
I suggest to use a dedicated IP address other than <IP_ADDRESS>.
Any feedback is appreciated.
Source: https://github.com/puppetlabs/pltraining-bootstrap/blob/master/manifests/profile/guacamole.pp

Along with binding to <IP_ADDRESS> and hard-coded passwords, I also noticed instances of keeping admin users as default in Puppet classes. I think this is a smell related to security. The smell can violate the ‘principle of least privilege (https://en.wikipedia.org/wiki/Principle_of_least_privilege)’ property, which recommends practitioners to design and implement system in a manner so that by default the least amount of access necessary is provided to any entity.
Would you agree with my finding?
Source: https://github.com/puppetlabs/pltraining-bootstrap/blob/master/manifests/params.pp


Change test url

Gopay changed test url
from https://testgw.gopay.cz/ to https://gw.sandbox.gopay.com/
https://doc.gopay.com/cs/#dokumentace-gopay-rest-api

https://doc.gopay.com/cs/#dokumentace-gopay-rest-api

@wamesro Thank you for the PR, but as you can see, our integration tools shows some fails.
https://travis-ci.org/Markette/GopayApi/jobs/223140982

@f3l1x Sorry, but I changed only the addresses, I did not change the annotations.

Thank you.


Freetype font is blurry on iPhone 6 - iOS8

Example of free type font loading that works on everything except iOS devices / simulator.
I've tried with no scaling and it's worse.
I really think there's an issue with iOS and blurriness with libGDX.
public BitmapFont getFont(String font, float size)
{
    return this.fetchFontAlreadyExist(size, font);
}

private BitmapFont fetchFontAlreadyExist(float size, String fileName)
{
    if(this.bitmapFontOpificio == null)
    {
        this.bitmapFontOpificio = TextureLoader.getInstance().getAssetManager().get(OPIFICIO);
    }

    this.bitmapFontOpificio.setScale((size / FONT_SIZE_LARGE_CM) / FONT_MAGNIFICATION);

    return this.bitmapFontOpificio;
}

public void loadFonts() {
    //This is called at the load of the game. (Before Splash finishes loading)

    //Font settings
    FreetypeFontLoader.FreeTypeFontLoaderParameter fontParams = new FreetypeFontLoader.FreeTypeFontLoaderParameter();

    //Use font magnification because FreeType creates blurry font if you doing resolution independent stuff.
    fontParams.fontParameters.size = Math.round(FONT_SIZE_LARGE_CM * FONT_MAGNIFICATION);
    fontParams.fontFileName = OPIFICIO;
    fontParams.fontParameters.genMipMaps = true;
    fontParams.fontParameters.magFilter = Texture.TextureFilter.MipMapLinearNearest;
    fontParams.fontParameters.minFilter = Texture.TextureFilter.MipMapLinearNearest;

    //Load the font.
    TextureLoader.getInstance().getAssetManager().load(OPIFICIO, BitmapFont.class, fontParams);
}

I'm not an expert and all this is only my hamble opinion :) but...
Just to clarify what is FONT_SIZE_LARGE_CM and FONT_MAGNIFICATION?
And what resolution is set on iOS/emulator? I mean the fontParameters.size AFAIK is pixel-sized value, that means the font with size 30 pixels might look different on retina screen with quite high resolution.

FONT_SIZE_LARGE_CM = 1CM * 0.65f.
FONT_MAGNIFICATION = 2f. In order to get fonts to look sharp on Android, you need to double the size then scale down otherwise it looks blurry.

FONT_SIZE_LARGE_CM = 1CM * 0.65f.
FONT_MAGNIFICATION = 2f. In order to get fonts to look sharp on Android, you need to double the size then scale down otherwise it looks blurry.

Please provide an ApplicationListener that compiles and reproduces the issue. Can't reproduce this issue locally. Will reopen if you provide new info.


Wrap the db errors

Add to the database errors additional meta information.

@saheienko we don't really need this PR because whole current DB layer goes away.

@yegorch OK, closing it.


get tests work for multiple GPUs and up to 4

Also print out helpful message when more than 4 GPUs are detected.

build

Ideally, our tests should run on 2 gpus to have some coverage for distributed use case.

Yeah, all toy tests should support 2 GPUs now.

build


Arrow keys don't work

Experiencing this in chrome, also at the demo site https://reverie.herokuapp.com/arXiv_Demo/#

Arrow keys work on safari


On/off VSync support for vulkan

Being a boolean setting, the code will choose the best available present mode to fit user's choice.
Presentation modes are ordered from no tearing to non-sync modes (will probably have tearing).
Fixes #36467.

Anynews we can implement this so i can test it,
Am trying to fix this #35899

@giarve Out of curiosity, how difficult would it be to adapt this PR to expose adaptive V-Sync? (In other words, V-Sync that automatically disables itself when the FPS is below the monitor refresh rate to avoid stuttering at low FPS.)

@giarve Out of curiosity, how difficult would it be to adapt this PR to expose adaptive V-Sync? (In other words, V-Sync that automatically disables itself when the FPS is below the monitor refresh rate to avoid stuttering at low FPS.)

According to the specification:

VK_PRESENT_MODE_FIFO_RELAXED_KHR specifies that the presentation engine generally waits for the next vertical blanking period to update the current image. If a vertical blanking period has already passed since the last update of the current image then the presentation engine does not wait for another vertical blanking period for the update, meaning this mode may result in visible tearing in this case. This mode is useful for reducing visual stutter with an application that will mostly present a new image before the next vertical blanking period, but may occasionally be late, and present a new image just after the next vertical blanking period. An internal queue is used to hold pending presentation requests. New requests are appended to the end of the queue, and one request is removed from the beginning of the queue and processed during or after each vertical blanking period in which the queue is non-empty.

Looks like what you're asking for. If you have a project in which you're able to reproduce stuttering issues, recompile the engine changing:
VkPresentModeKHR swapchainPresentMode = VK_PRESENT_MODE_FIFO_KHR;
to
VkPresentModeKHR swapchainPresentMode = VK_PRESENT_MODE_FIFO_RELAXED_KHR;
in
drivers/vulkan/vulkan_context.cpp:874
and rerun the game and check if it solves the stuttering.
Depending on the GPU you may not have this presentation mode available, in that case I won't be of much help. In fact, this PR was first created to address compatibility issues with different presentation modes, because this change set what only does is selecting the most differentiating mode for VSync enabled or disabled.
The main problem of this PR is that it doesn't allow you to select which exact mode you want to try, so it could be interesting (if you find the VK_PRESENT_MODE_FIFO_RELAXED_KHR to work) to expose the available presentation mode list to settings, or just exposing what you suggested, toggling adaptive V-Sync.
I wouldn't be able to make a custom adaptive Vsync because it looks like a more advanced topic.
When I last checked the code the default mode was full VSync enabled, with three buffers but without the MAILBOX presentation mode enabled (which would be required to enable triple buffering and minimize latency). By default, the VK_PRESENT_MODE_FIFO_KHR is the one enabled, which is good for mobile because it has the least battery consumption.
Take into account that this PR is Vulkan only and wouldn't solve the problems with Godot stable may have (if there are any, which I don't know).

I would like to see this merged soon since disabling VSync helps with profiling.

Needs to be rebased

I am currently trying to reimplement this with a newer version of Godot since I failed to rebase giarve's branch(too many changes since then).
But for some reason even setting the presentation mode directly to VK_PRESENT_MODE_IMMEDIATE_KHR by passing it to the VkSwapchainCreateInfoKHR constructor does not work as expected (still running at monitors refresh rate). Could someone explain that behavior?
see drivers/vulkan/vulkan_context.cpp:
VkSwapchainCreateInfoKHR swapchain_ci = {
		/*sType*/ VK_STRUCTURE_TYPE_SWAPCHAIN_CREATE_INFO_KHR,
		/*pNext*/ nullptr,
		/*flags*/ 0,
		/*surface*/ window->surface,
		/*minImageCount*/ desiredNumOfSwapchainImages,
		/*imageFormat*/ format,
		/*imageColorSpace*/ color_space,
		/*imageExtent*/ {
				/*width*/ swapchainExtent.width,
				/*height*/ swapchainExtent.height,
		},
		/*imageArrayLayers*/ 1,
		/*imageUsage*/ VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT,
		/*imageSharingMode*/ VK_SHARING_MODE_EXCLUSIVE,
		/*queueFamilyIndexCount*/ 0,
		/*pQueueFamilyIndices*/ nullptr,
		/*preTransform*/ (VkSurfaceTransformFlagBitsKHR)preTransform,
		/*compositeAlpha*/ compositeAlpha,
		/*presentMode*/ VK_PRESENT_MODE_IMMEDIATE_KHR,
		/*clipped*/ true,
		/*oldSwapchain*/ VK_NULL_HANDLE,
	};```

I am currently trying to reimplement this with a newer version of Godot since I failed to rebase giarve's branch(too many changes since then).
But for some reason even setting the presentation mode directly to VK_PRESENT_MODE_IMMEDIATE_KHR by passing it to the VkSwapchainCreateInfoKHR constructor does not work as expected (still running at monitors refresh rate). Could someone explain that behavior?
see drivers/vulkan/vulkan_context.cpp:
VkSwapchainCreateInfoKHR swapchain_ci = {
		/*sType*/ VK_STRUCTURE_TYPE_SWAPCHAIN_CREATE_INFO_KHR,
		/*pNext*/ nullptr,
		/*flags*/ 0,
		/*surface*/ window->surface,
		/*minImageCount*/ desiredNumOfSwapchainImages,
		/*imageFormat*/ format,
		/*imageColorSpace*/ color_space,
		/*imageExtent*/ {
				/*width*/ swapchainExtent.width,
				/*height*/ swapchainExtent.height,
		},
		/*imageArrayLayers*/ 1,
		/*imageUsage*/ VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT,
		/*imageSharingMode*/ VK_SHARING_MODE_EXCLUSIVE,
		/*queueFamilyIndexCount*/ 0,
		/*pQueueFamilyIndices*/ nullptr,
		/*preTransform*/ (VkSurfaceTransformFlagBitsKHR)preTransform,
		/*compositeAlpha*/ compositeAlpha,
		/*presentMode*/ VK_PRESENT_MODE_IMMEDIATE_KHR,
		/*clipped*/ true,
		/*oldSwapchain*/ VK_NULL_HANDLE,
	};```

Closing per discussion on IRC:
<Calinou> I think it's good. Maybe add https://github.com/godotengine/godot/pull/36862 for review?
<reduz> Calinou: no.. still not completely sure how this has to work and I have to do a few more changes to vulkan
<Calinou> yes, it probably has to be redone from scratch
<reduz> Calinou: plus the PR should be redone for Displayservers
<Calinou> should we close the PR and mark it as salvageable?
<reduz> probably salvagable but needs a ton of work

Closing per discussion on IRC:
<Calinou> I think it's good. Maybe add https://github.com/godotengine/godot/pull/36862 for review?
<reduz> Calinou: no.. still not completely sure how this has to work and I have to do a few more changes to vulkan
<Calinou> yes, it probably has to be redone from scratch
<reduz> Calinou: plus the PR should be redone for Displayservers
<Calinou> should we close the PR and mark it as salvageable?
<reduz> probably salvagable but needs a ton of work


[Feature] Adding WHERE codintion during MERGE update

Hi,
It would be nice to be able to  controll the incremental merge strategy by adding a WHERE clause to the WHEN MATCHED THEN part of the merge statement. As i see on dbt-oracle github it seems the adapter doesn't support it.
ON (src.id = tgt.id AND src.date = tgt.date)
WHEN MATCHED THEN
    UPDATE SET
        tgt.end_date = src.end_date
    WHERE
        src.end_date <> tgt.end_date
WHEN NOT MATCHED THEN
    INSERT (tgt.id, tgt.date, tgt.end_date)
    VALUES (src.id, src.date, src.end_date)

I got recommended by #db-oracle on dbt slack to raise a feature request so it gets tracked.
Describe alternatives you've considered
This is the repons i got from #db-oracle slack channel from @aosingh:
dbt-oracle implements the functionality conforming to the standard defined by dbt.
However, I see that you need support for an arbitrary where clause condition during MERGE update. We will need to think about the interface to implement this. One way could be to introduce a dbt-oracle specific parameter. The challenge is to make this a generic config which can work for any where condition. The where condition can be on the target data or source data or both.
You can also raise a feature request here - https://github.com/oracle/dbt-oracle/issues so that this gets tracked

Who will this benefit?
No response
Anything else?
No response

@philiphagglund
We are working on dbt-oracle 1.4 release which will support incremental predicates
We will support incremental predicates in dbt-oracle conforming to rules defined by dbt Labs.
I think, this will solve your feature request. Please read about it and I will let you know when the first cut is released on PyPI.
Let me know if you have any questions

@philiphagglund
Did you try incremental predicates ? Does it solve your usecase.

Hi,
Thanks so much for reply! I am have been on parental leave.
I will take a look asap regarding this feature. Is there any more updates
regarding this?
/Philip
Den tors 9 mars 2023 kl 17:22 skrev Abhishek Singh @.***

:

@philiphagglund https://github.com/philiphagglund
Did you try incremental predicates
https://docs.getdbt.com/docs/build/incremental-models#about-incremental_predicates
? Does it solve your usecase.
—
Reply to this email directly, view it on GitHub
https://github.com/oracle/dbt-oracle/issues/56#issuecomment-1462354553,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALEF4Z45KGN75Q3M6MOF3ZLW3H7TJANCNFSM6AAAAAASOD4664
.
You are receiving this because you were mentioned.Message ID:
@.***>

HI Abhishek,
Unfortunately is this not going to solve the usecase i have. I have now
tried the new incremental predicates functionality and it works fine,
except is doesn't accept a column in the ON statement to be updated:
[0m07:00:02.502344 [info ] [Thread-1 (]: oracle adapter: Oracle error:
ORA-38104: Columns referenced in the ON Clause cannot be updated:
"DBT_INTERNAL_DEST"."END_DATE"
ON (src.id = tgt.id AND src.date = tgt.date AND src.end_date <> tgt.end_date)
WHEN MATCHED THEN
UPDATE SET
tgt.end_date = src.end_date
WHERE
src.end_date <> tgt.end_date
WHEN NOT MATCHED THEN
INSERT (tgt.id, tgt.date, tgt.end_date)
VALUES (src.id, src.date, src.end_date)
Den tors 9 mars 2023 kl 17:22 skrev Abhishek Singh @.***

:

@philiphagglund https://github.com/philiphagglund
Did you try incremental predicates
https://docs.getdbt.com/docs/build/incremental-models#about-incremental_predicates
? Does it solve your usecase.
—
Reply to this email directly, view it on GitHub
https://github.com/oracle/dbt-oracle/issues/56#issuecomment-1462354553,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALEF4Z45KGN75Q3M6MOF3ZLW3H7TJANCNFSM6AAAAAASOD4664
.
You are receiving this because you were mentioned.Message ID:
@.***>

@philiphagglund understood the problem. I guess i need to think about how to support this conditional update clause during MERGE. Probably, a parameter which can be supplied by the user during incremental materialization config.


Separate the request models from the response models

Just to keep the file short I wanted to separate these in half. Everything just moved around, no new code added.

:+1:


Add support some DROP script

Support deparse some DROP statement
DROP SERVER [ IF EXISTS ] server_name [ CASCADE | RESTRICT ]
DROP PUBLICATION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP TYPE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP TABLESPACE [ IF EXISTS ] name
DROP CONVERSION name [ CASCADE | RESTRICT ]
DROP SEQUENCE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP MATERIALIZED VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP TRIGGER [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
DROP RULE [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
DROP CAST [ IF EXISTS ] (source_type AS target_type) [ CASCADE | RESTRICT ]
DROP OPERATOR FAMILY [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ]
DROP AGGREGATE [ IF EXISTS ] name ( aggregate_signature ) [, ...] [ CASCADE | RESTRICT ]
DROP FUNCTION [ IF EXISTS ] name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ] [, ...]
[ CASCADE | RESTRICT ]
DROP COLLATION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP FOREIGN DATA WRAPPER [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP ACCESS METHOD [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP STATISTICS [ IF EXISTS ] name [, ...]
DROP TEXT SEARCH DICTIONARY [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP OPERATOR CLASS [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ]
DROP ROLE [ IF EXISTS ] name [, ...]
DROP POLICY [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
DROP SUBSCRIPTION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP FOREIGN TABLE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP EVENT TRIGGER [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP TEXT SEARCH PARSER [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
DROP EXTENSION [ IF EXISTS ] extension_name [, ...] [ CASCADE | RESTRICT ]
DROP DOMAIN name [, ...]  [ CASCADE | RESTRICT ]
DROP TEXT SEARCH TEMPLATE [ IF EXISTS ] name [ CASCADE | RESTRICT ]
DROP TRANSFORM [ IF EXISTS ] FOR type_name LANGUAGE lang_name

@emin100 Thanks again for all your contributions. As I'm going through them, I noticed a few PRs, including this one, didn't have tests.
Could you add tests to this PR for the statements that are now being supported? That'd be awesome :)

Tests is added

@emin100 Thanks for the quick update!
Sorry again that it took a while to get to all of these, again appreciate your contributions :)


Video 5 - draft script

Description

This is a draft script for AsyncAPI of the fiveth educational and technological video.

Related issue(s)
See also #155

Okis, ya dejé mi review @Barbanio 🐻 💟

Thank you very much, @alequetzalli 🌺

@derberg Thank you for your great feedback. I will restructure and rewrite the script based on your suggestions.

I'm also missing in the script important thing that was in us when designing open governance, important to mention IMHO ->  in https://www.asyncapi.com/blog/governance-motivation I wrote something like
gives power to people that "work", not companies that "pay". In other words, it gives equal power to both individual and corporate contributors.

maybe mention it when you explain that we have TSC, that we choose that TSC consists of maintainers to make sure it consists of not only people that are sponsored by their companies, but also individual contributors that work on the project equally hard, mostly in spare time

Hi! I created this animation for the video: https://drive.google.com/drive/folders/1gIhXOzgnSjObETLSrgE1doZcDbJMJNla?usp=sharing. What do you think?

omg it's so cute!
I don't feel qualified to give critique on animations just yet tho... Oh, one thing I would change is the color of the bus. It is a blue that doesn't seem to display the dark AsyncAPI logo version well... is that an easy change?
One idea: what if the bus also had a banner that said: "Board the OSS Bus," or something similar?
i am curious what others will think!

Thanks for your feedback, @alequetzalli. I changed the AsyncAPI logo to the clear version, and it looks much better 🙂 I added the banner to the bus too. See what you think!


docs: update docs

** PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/azure-seed/azure-functions-typescript/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

** PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] Other... Please describe:

** What is the current behavior?

Issue Number: N/A
** What is the new behavior?
** Does this PR introduce a breaking change?
[ ] Yes
[x] No

** Other information

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #12   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          41     41
  Branches       10     10
=====================================
  Hits           41     41

Continue to review full report at Codecov.

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


Functions: httpsCallable().call() doesn't make a request in iOS app

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.5
Firebase SDK version: 8.0.0
Installation method: CocoaPods
Firebase Component: Functions

[REQUIRED] Step 2: Describe the problem
iOS code using Functions.functions().httpsCallable(...).call(...) doesn't make a call.
Steps to reproduce

Deploy a simple HTTPS callable function
Call said function from iOS client app using Firebase emulator.
Calling the functions return an error
There seems to be no log output on the console.

Relevant Code:
HTTP callable function:
exports.addMessage = functions.https.onCall((data, context) => {
  const text = data.text;
  console.log(text)

  return {
      text: "100"
    };
  })

Swift code to call function:
In my AppDelegate.swift class:
Functions.functions().useEmulator(withHost:"localhost", port:5001)
In my View Controller class:
lazy var functions = Functions.functions()
functions.httpsCallable("addMessage").call(["text": "test"]) { (result, error) in
            self.actionButton.toggleLoadingIndicator(false)
            if let error = error {
                print("Firebase error: \(error)")

            }
            if let text = (result?.data as? [String: Any]) {
                print("SUCCESS: \(text)")
            }
        }

The above functions return the following error:
Firebase error: Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.}

This might be related to #7783

#7783

Already tried setting my local instance of functions to use the emulator. It returns a different error.
Xcode console logs:
 [Firebase/Performance][I-PRF100009] Logging network request trace - http://localhost:5001/copper-bot-289211/us-central1/addMessage, Response code: 404, 36.0950ms
Error returned in callback
Firebase error: Error Domain=com.firebase.functions Code=5 "NOT FOUND" UserInfo={NSLocalizedDescription=NOT FOUND}
2021-05-14 18:57:22.841356+0500 HairS[10632:196725] 8.0.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT

@aledap is this issue reproducible in Firebase 7.11?


Mac OS runner not capable of running MPS for projects using torch

Description
Whenever MPS is used in a runner the following error is generated...

RuntimeError: MPS backend out of memory (MPS allocated: 0 bytes, other allocations: 0 bytes, max allowed: 7.93 GB). Tried to allocate 256 bytes on private pool. Use PYTORCH_MPS_HIGH_WATERMARK_RATIO=0.0 to disable upper limit for memory allocations (may cause system failure).

This has been commented on previously here https://github.com/actions/runner-images/issues/9254#issuecomment-1936326374, but it does not seem to have been addressed. The environment makes it appear as if it is available, but everyone seems to be trying to figure this out for a lot of different projects.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[X] macOS 13 Arm64
[ ] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
2.316.1
https://github.com/TransformerLensOrg/TransformerLens/actions/runs/9206850372/job/25325615370
Is it regression?
no
Expected behavior
Allow MPS to be accessible for projects that need to run tests on MPS devices.
Actual behavior
The runner shows that MPS is available while failing with a cryptic message whenever you try to do anything with it.
Repro steps
Run any code that tries to allocate memory on an arm Mac runner
import torch

if torch.backends.mps.is_available(): # This is returning true, but it should not be since the device is not actually usable
    torch.tensor([1.0, 2.0, 3.0], device='mps')

Hey @bryce13950!
Unfortunately it's an expected behaviour for macOS arm64 runners. It has a description here: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#limitations-for-arm64-macos-runners
We are waiting for some changes in Apple's Virtualization Framework.

@erik-bershel does the nested virtualization in macos-15 solve this ?
https://discussions.apple.com/thread/255314811?sortBy=best

@IlyasMoutawwakil nope.


Will this work if I use JavaScript instead of TypeScript?

Hi,
I want to use this npm package and I love it. I am wondering if this will work with JS in react?
Furthermore, I went through the usage example and converted my code to JS, but I get a lot of errors.
Also, I am wondering if the usage example is correct?
Thanks!

Yes, thank you for your input, I had a small fix to make in th documentation and the demo,
please install v1.1.25 latest version.
Here is a working example using react-vite with javascript only -
`import { CardSwiper } from "react-card-swiper"
import ReactSvg from "../src/assets/react.svg"
const Content = () => (

    Lorem ipsum dolor sit amet.

)
function App() {
const mockData = [{ id: '88552078', meta: { apk: 'some-apk-a.apk' }, src: ReactSvg, content:  }]
return (

<CardSwiper data={mockData} emptyState={Empty State} />

)
}
export default App
`


Context menu items for the tray icon

aka making the tray icon actually useful by adding items like

copying the Job ID/game link
discord rpc toggle (?)
opening the latest log file (?)

Oh, those are some nice ideas for context menu items.

I'm abandoning this idea, because I don't think it's actually possible to do with the way this program is made. Annoyingly, the notification area icon is a WinForms component only, so its smoothness with WPF/non-GUI applications is kind of hit and miss. I barely managed to make toast notifications work, and that's one of the most simple components of it. A context menu, on the other hand is only going to work in a pure-GUI application, which this is not.


fix: React 19 fixes for Table related components

Thanks for contributing to react-virtualized!
Before submitting a pull request, please complete the following checklist:

[x] The existing test suites (npm test) all pass
[ ] For any new features or bug fixes, both positive and negative test cases have been added
[x] For any new features, documentation has been added
[x] For any documentation changes, the text has been proofread and is clear to both experienced users and beginners.
[x] Format your code with prettier (yarn run prettier).
[x] Run the Flow typechecks (yarn run typecheck).

Here is a short checklist of additional things to keep in mind before submitting:

Please make sure your pull request description makes it very clear what you're trying to accomplish. If it's a bug fix, please also provide a failing test case (if possible). In either case, please add additional unit test coverage for your changes. :)
Be sure you have notifications setup so that you'll see my code review responses. (I may ask you to make some adjustments before merging.)

Since update to React 19-rc.1 (which is part of the latest NextJS 15) these functionalities started to fail (at least in the app we have). These changes helped avoid usages of findDOMNode that has been removed as well as defaultProps which didn't have an effect "from outside" all these settings were empty. Cannot say it's complex support for the latest React, but it's a great start.

React 19.0.0 is stable and would be nice to support it:
https://react.dev/blog/2024/04/25/react-19-upgrade-guide

React 19.0.0 is stable and would be nice to support it: https://react.dev/blog/2024/04/25/react-19-upgrade-guide

Please! Really need this

For the love of god and maybe an early xmas gift can someone just come in and hit the merge button?

For the love of god and maybe an early xmas gift can someone just come in and hit the merge button?

@bvaughn any chance this can be merged?

The merge is blocked. Please OKAY this for merge. The world needs this fix yesterday!


False negative: C++ header file classified as C header -> skips all C++ specific tests

Using version: v0.4.131

Create the following C++ header, header.h with the following content:

constexpr unsigned long flags = SECURITY_FLAG_IGNORE_CERT_DATE_INVALID;

Run analyze

> devskim.exe analyze header.h
Issues found: 0 in 0 files
Files analyzed: 1
Files skipped: 0

Rename to header.hpp and run analyze again

> devskim.exe analyze `header.hpp`
file:header.hpp
        region:1,32,1,70 - DS159369 [Critical] - Disabled certificate validation

Issues found: 1 in 1 files
Files analyzed: 1
Files skipped: 0

In step 2 I expected analyze to either

not recognize header.h, and require some flag for assuming what language h files are
to recognize that it is a c++ header, but that seems errorprone

Thanks for your report.  I think I'll have to think a bit on how we want to handle cpp headers with a .h extension.  The workaround for now is to name them hpp.

We've decided to apply apply both C and C++ rules to .h files.  I should have an update out this week with the fix.


Cilium 1.12.0 fails to install on clusters that blocks SYS_MODULE

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
On Kubernetes cluster where containerd is started with SYS_MODULE capability dropped, installing Cilium 1.12.0 fails in the clean-cilium-state initContainer since it explicitly requests SYS_MODULE capability. Modifying the helm chart to set securityContext.privileged: true fixes this issue, since the container then only inherits only the capabilities available to the containerd process (which doesn't explicitly try to use SYS_MODULE).
Since setting securityContext.privileged: true makes the cilium install works and looking at the comments in the helm chart, it seems the SYS_MODULE capability is only needed in some specific operation mode of cilium (I guess something that would involve iptables, but I'm not completely sure).
I would like to propose a solution which makes the SYS_MODULE capability optional and configurable by the user. This would allow the pods to be run without securityContext.privileged: true but still a limited down capability as defined in the securityContext.capabilities.add.
If this idea makes sense I can work on putting up a draft PR
Cilium Version
1.12.0
Kernel Version
5.15.54
Kubernetes Version
1.24.3
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Hello @frezbo,
thank you for opening the GH issue. Unfortunately, the SYS_MODULE is indeed required to install some iptables rules which affects Cilium operations so we can't make it optional.

Isn't that the case only when the iptables module is not loaded? From my testing it was not using that capability when ran as privileged pod and when the containerd was started with the SYS_MODULE capability dropped.

Isn't that the case only when the iptables module is not loaded? From my testing it was not using that capability when ran as privileged pod and when the containerd was started with the SYS_MODULE capability dropped.

Probably that was confusing, in the test scenario, the iptables modules was already loaded, so cilium had no need to load it

@frezbo you are right, it might have been an oversight from our side. Consider submitting a PR removing it from everything. If the CI doesn't complain I don't see why we can't merge it. Thank you

@frezbo I've brought this up in this week's developer meeting. It looks that SYS_MODULE is indeed used when iptables is executed which can load some modules automatically.

@frezbo I've brought this up in this week's developer meeting. It looks that SYS_MODULE is indeed used when iptables is executed which can load some modules automatically.

It probably explains why it worked in Talos when ran with privileged mode even though SYS_MODULE was already dropped (there are no user loadable modules and all modules are already built in to kernel). I'm not sure what would be the right approach here. I can do a PR that by default still allows SYS_MODULE and have an option to optionally disable them.

I believe it works since all the modules are already loaded (the kernel is compiled with all modules in-tree and not as a module)

@frezbo ofc in that case that makes more sense then. Could you submit a PR and describe all of this information in the commit message? Thank you!

I'm working on a PR to fix this specific issue

I'm working on a PR to fix this specific issue

cool, thanks, I didn't get around to fixing it :sweat_smile:

Thanks both.
I have assigned the issue to you @jonkerj. Feel free to shout out in #development channel if you need any help.


Check if symbol requires top-gradient or not

Is there a python symbol API to check whether a symbol requires a top gradient or not? If not, can we get one?

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Specify node engine version

sharedstreets-js only runs on node.js v11, which is the current version. This needs to be specified with the engine parameter in package.json to avoid unexpected behavior for users of the library and CLI.

I have node v8 installed locally on my Mac, so I thought I'd try to get a Docker going.
I tried building from node:11, but I'm not able to get it working:
FROM node:11

ENV NPM_CONFIG_PREFIX=/home/node/.npm-global
ENV PATH=$PATH:/home/node/.npm-global/bin

USER node
RUN npm install -g<EMAIL_ADDRESS>
$ docker build -t shst .
$ docker run -it --rm -v ~/Downloads:/usr/ shst:latest shst match /usr/map.geojson --out=/usr/match.geojson
standard_init_linux.go:207: exec user process caused "no such file or directory"

If I look inside...
docker run -it --rm shst:latest /bin/bash
node@32da0c9ad310:/$ shst help
bash: /home/node/.npm-global/bin/shst: /usr/bin/env: bad interpreter: No such file or directory

This seems to be a path issue. I think I'm following the docker-node Best Practices. Any ideas how to make these play nicely together?

Oddly, the -v seems to be part of the problem.
$ docker run -it --rm shst:latest shst help
SharedStreets, a 'digital commons' for the street

VERSION
  sharedstreets/0.12.0 linux-x64 node-v11.15.0

USAGE
  $ shst [COMMAND]

COMMANDS
  extract  extracts SharedStreets streets using polygon boundary and returns GeoJSON
           output of all intersecting features
  help     display help for shst
  match    matches point and line features to sharedstreets refs

Still looking...

I think the Docker is working now once I point the volume to a directory that matches with the default user node, but there's a different issue. So I will file that separately.
docker run -it --rm -v ~/Downloads/:/usr/node/ shst:latest shst match /usr/node/line_2.in.geojson --out=/usr/node/match.geojson
  🌏  Loading geojson data...
       Matching using car routing rules on all streets
  ✨  Matching 1 lines...
TypeError: Cannot set property '_maxEntries' of undefined
    at RBush (~/.npm-global/lib/node_modules/sharedstreets/node_modules/rbush/rbush.js:65:22)
    at Object.geojsonRbush [as default] (~/.npm-global/lib/node_modules/sharedstreets/node_modules/geojson-rbush/index.js:22:16)
    at new TileIndex (~/.npm-global/lib/node_modules/sharedstreets/build/src/tile_index.js:66:57)
    at new Graph (~/.npm-global/lib/node_modules/sharedstreets/build/src/graph.js:300:30)
    at ~/.npm-global/lib/node_modules/sharedstreets/build/src/commands/match.js:355:23
    at Generator.next (<anonymous>)
    at ~/.npm-global/lib/node_modules/sharedstreets/build/src/commands/match.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (~/.npm-global/lib/node_modules/sharedstreets/build/src/commands/match.js:3:12)
    at matchLines (~/.npm-global/lib/node_modules/sharedstreets/build/src/commands/match.js:277:12)

Is there interest in having this Docker in the repo and instructions in the Readme? I can create a pull request if so.

@josiekre creating a docker install is a great idea. We'll work on that for the next release. We're also looking into support for Node v8.
That said, we pushed a fix today for the Cannot set property '_maxEntries' of undefined problem you identified here and in #50. Another package that we depend on broke last week causing this error. We've replaced it as a dependency and the CLI should now work on Node v10+.


Laravel 10 support

Hi, any one know if this package will be updated to support Laravel 10
Thanks

hyn/multi-tenant version: 5.8
laravel version: 10

We would love to upgrade it to Laravel 10 😄
I will do an attempt this week to upgrade it to Laravel 10. Maybe someone from the community will beat me to it, as it might be as simple as updating the dependencies.

We would love to upgrade it to Laravel 10 😄
I will do an attempt this week to upgrade it to Laravel 10. Maybe someone from the community will beat me to it, as it might be as simple as updating the dependencies.

Thank you for your kindness in answering

@ArlonAntonius any luck with it?

Do you have any news about this?

@ArlonAntonius  I submitted a PR to upgrade to laravel 10, but  CI Circle CI/CD fails due to php 8.0 in docker.
Please find screenshot attached.

@geeky3 you can try to edit the .circleci/config.yml in your branch to fix this.

@geeky3 have you also seen the PR from @ArlonAntonius ? (https://github.com/tenancy/multi-tenant/pull/1036)
Would be great if this package can be used in Laravel 10 environments

Hi, Paul,
I had missed PR from  @ArlonAntonius https://github.com/ArlonAntonius
completely.
So shall I cancel my PR ? (Please feel free to educate me as I am a
beginner to open source contributions).
On Wed, May 31, 2023 at 5:03 PM Paul @.***> wrote:

@geeky3 https://github.com/geeky3 have you also seen the PR from
@ArlonAntonius https://github.com/ArlonAntonius ? (#1036
https://github.com/tenancy/multi-tenant/pull/1036)
Would be great if this package can be used in Laravel 10 environments
—
Reply to this email directly, view it on GitHub
https://github.com/tenancy/multi-tenant/issues/1035#issuecomment-1570020847,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPV7A2QMOVKNVLIAYNNRY3XI4T7NANCNFSM6AAAAAAVBV72ZY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi, Paul, I had missed PR from @ArlonAntonius https://github.com/ArlonAntonius completely. So shall I cancel my PR ? (Please feel free to educate me as I am a beginner to open source contributions).
…

I think one of them should be merged so we can upgrade to Laravel 10. @ArlonAntonius what are your plans regarding Laravel 10 and these PR's ?

Hi, Paul, I had missed PR from @ArlonAntonius https://github.com/ArlonAntonius completely. So shall I cancel my PR ? (Please feel free to educate me as I am a beginner to open source contributions).
…

I think one of them should be merged so we can upgrade to Laravel 10. @ArlonAntonius what are your plans regarding Laravel 10 and these PR's ?

I'm open to merge anything, but I think the CI should at least pass to make sure we don't break anything in a user's application 😅 I tried fixing the CI in my PR, but was unable to do so in the limited time I have.
If one of you has the time to work on it, feel free to work on it 😉

@ArlonAntonius as I am new to open source I have following issue.
I am not seeing any pull request option. Is there any thing else to set in my repo ?

@ArlonAntonius I have closed my pull request.
I see that there is already a pull request for upgrade to laravel 10 and have passed the checks.

@ArlonAntonius could you add a tag please?

@jonquintero: ArlonAntonius just released a new version with Laravel 10 support!

@PouleR @ArlonAntonius Thanks for all support

All of you did the work, thanks for the collaborations of all of you 😊


prime factorization using sieve

An efficient method to calculate the prime factorization using O(n) space and O(log n) time complexity

i would like to take this issue in C++ as a part of Hakin Codes

@Abhijit2505 @Kajol-Kumari

I would like to take up this issue and solve it in C++ with a time complexity of O(logN) as part of Hakin Codes

I would like to work on this issue in C++ and C as a part of HackinCodes

I would like to take up this issue and solve it in C++ with a time complexity of O(logN) as part of Hakin Codes

Hey @reethikprasad as @chandansahuji has already commented I can't assign it to you for c++, please feel free to choose any other language :)

I would like to work on this issue in C++ and C as a part of HackinCodes

@kashika3101  Please go with C as C++ is already taken up by @chandansahuji

I would like to take this issue in JAVA.
Please assign this issue to me.
Participant at HakinCodes

@anime19 assigned Java to you
Hope you read the contribution guideline
Happy Coding!

I would like to work on this issue in Python.

I would like to work on this issue in C#.

I would like to work on this issue in Python.

@Kajol-Kumari @plazzy99 Can I?

Hey @ankitaggarwal23 please go with c# and @Nagasuruthika please go with Python.
Happy Learning :)

@iamrajiv Kindly review my PR #1221 .


It would be nice to be able to control the "rate of integration"

After you freehand something with ppInk, it takes a moment for ppInk to integrate what you've drawn into the screen visuals, perhaps because it's waiting for enough data before applying the smoothing algorithm. In any event, I think it would be nice if it were possible to adjust the time-until-integration under 'Options...' so that different users can adjust to their own taste. I also think the default should be about 30% faster, since this will probably fit better with what most users want.

On second thoughts, the problem seems to be the speed of my computer, not the software. I'll close this for now....


[BUG] Add path validation for proxy-ca-file

It seems that relative path causes problems. Absolute path works OK. The error message isn't great, but maybe just validating input for the path would help.
Also, can we update the description for the proxy-ca-file argument? Currently it says:
* proxy-ca-file                              Path to an HTTPS proxy certificate authority (CA)

I think the following would more accurately describe the item:

Absolute path to an HTTPS proxy certificate authority's certificate file

General information

OS: Linux

CRC version
# Put `crc version` output here

CRC status
# Put `crc status --log-level debug` output here

CRC config
- consent-telemetry                     : no
- host-network-access                   : true
- http-proxy                            : http://host.crc.testing:8888
- https-proxy                           : http://host.crc.testing:8888
- network-mode                          : user
- proxy-ca-file                         : test/testdata/pki/rootCA.crt

Steps to reproduce

$ crc config set proxy-ca-file test/testdata/pki/rootCA.crt
$ crc setup
$ crc start -p ~/Downloads/crc-pull-secret

Expected
Start works OK.
Actual
Is 'crc daemon' running? Cannot reach daemon API: Get "http://unix/api/version": read unix @->/home/jsliacan/.crc/crc-http.sock: read: connection reset by peer

@jsliacan I was thinking it didn't have any validation, but the config option does have path validation, so it verifies the file exists.. wondering what else could've caused the daemon to error out and exit..
https://github.com/crc-org/crc/blob/bb69afc5f2e9a88d3e76a453ef39295090b788b9/pkg/crc/config/settings.go#L117

My guess is that if you use a relative path, and then move to a different directory, and then try to run crc from there, then it will fail
./crc config set proxy-ca-file rel/path/to/ca.crt
cd ../..
./out/linux-amd64/crc ...

At step 3., the relative path will no longer be valid as the working dir changed.

I am not sure I understand @cfergeau . I don't think I (knowingly) changed the dir between setting the proxy-ca-file var and starting crc. It happens when I try it with explicit location of the crc binary in a fixed pwd (~/Github/crc).
jsliacan ~/Github/crc (goproxy)$ ./crc version
CRC version: 2.18.0+73a4b9
OpenShift version: 4.12.13
Podman version: 4.4.1

jsliacan ~/Github/crc (goproxy)$ ./crc config set proxy-ca-file test/testdata/pki/rootCA.crt
Successfully configured proxy-ca-file to test/testdata/pki/rootCA.crt

jsliacan ~/Github/crc (goproxy)$ ./crc setup
.
.
.
Your system is correctly setup for using CRC. Use 'crc start' to start the instance

jsliacan ~/Github/crc (goproxy)$ ./crc start -p ~/Downloads/crc-pull-secret
Is 'crc daemon' running? Cannot reach daemon API: Get "http://unix/api/version": read unix @->/home/jsliacan/.crc/crc-http.sock: read: connection reset by peer

jsliacan ~/Github/crc (goproxy)$ ./crc start -p ~/Downloads/crc-pull-secret
Is 'crc daemon' running? Cannot reach daemon API: Get "http://unix/api/version": read unix @->/home/jsliacan/.crc/crc-http.sock: read: connection reset by peer

The daemon won't be started as ./crc from the ~/Github/crc, but through an absolute path (I think ~/.crc/bin/crc) so it has no way of resolving test/testdata/pki/rootCA.crt as ~/Github/crc/test/testdata/pki/rootCA.crt

This is being worked on in https://github.com/crc-org/crc/pull/3816


Auto-Complete for Java->Javascript is annoying

If i want to post some Java code i type in

```Java

and then press Enter for new line to post my code. This will cause Java to get auto-completed to Javascript which is quite annoying.
OS: Windows 10

I've transferred this issue to the right repository.  @aero31aero this is probably a fairly straightforward typeahead fix if you want to claim it.


[Feature] Support for configuring different role per client

Is there an existing feature request for this?

[X] I have searched the existing issues

Is your feature related to a problem? Please describe.
Hi,
first of all, thanks a lot for making this SPI, it works very well and it is very easy to set up :)
I was wondering if there is a way I could configure this plugin so I can set a different role per client.
For example in my organization we have GitLab and Slack both protected with Keycloak. Since they both use a pay-per-user license model I only want users with the slack_user role to be authorized to use Slack and role_gitlab for gitlab.
Is this something currently possible? If not, do you think it can be something that could be added to the current code?
Thank you very much,
Daniel.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Anything else?
No response

@sventorben, thanks for your quick answer.
I guess it can be either of them.
Maybe client-level role will be a bit cleaner for my use-case, but I wouldn't mind adding them as realm roles.
Full disclosure, before I was using this SPI https://github.com/thomasdarimont/keycloak-extension-playground/tree/master/auth-require-role-extension but unfortunately I couldn't make it work with the new version of Keycloak (quarkus distro)
Thanks a lot!

Sorry for the confusion. I will try to explain my scenario better.
We have 2 different applications protected by Keycloak: GitLab and Slack. They are using 2 different keycloak clients.
Now, of all the users I have in Keycloak I ONLY want the ones that are in the group slack_users
to be able to login to Slack and ONLY the ones that are in gitlab_users to be able to access GitLab.
The users in slack_users and gitlab_users are not the same.
My idea is to implement this restriction via "required roles", so in this case the authentication flow for the Gitlab
client will require the specific role (i.e gitlab_users_role). This role will be mapped to the members of the gitlab_users group.
Likewise for Slack but in this case with the slack_users group and slack_users_role.
But my understanding is that you can only configure one global role. So if I do:
spi-restrict-client-auth-access-provider-client-role-client-role-name=gitlab_users_role
I will be only restring for the gitlab_users_role.
I hope this makes better sense. Thank you very much.

I think this extension already supports exactly what you want to achieve. I think there is a misunderstanding regarding the role name that you can configure globally. Can you check if the information in #118 helps.
If not, please let me know and I try to explain in more detail.

Indeed https://github.com/sventorben/keycloak-restrict-client-auth/issues/118#issuecomment-1300013191 looks like exactly what I need!
Danke schön Steven-Torben!!!


Buildpack error "unable to state file /usr/bin/python3.10"

When I run the maven buildpack, I get this cryptic error. Google turns up nothing. I'm not really sure where to start with this. I think the error is coming from within the container? If not it's extra strange because I have /usr/bin/python3.10.
I'm using pack --version 0.35.1
Paketo Buildpack for Maven 6.18.3
  unable to create application layer
  failed to generate expected metadata
  unable to create file listing for /workspace
  unable to create file listing
  error walking path /workspace
  unable to stat file /usr/bin/python3.10
  stat /usr/bin/python3.10: no such file or directory
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

Full logs is below:
===> DETECTING
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
target distro name/version labels not found, reading /etc/os-release file
10 of 26 buildpacks participating
paketo-buildpacks/ca-certificates   3.8.6
paketo-buildpacks/bellsoft-liberica 10.9.0
paketo-buildpacks/syft              2.1.0
paketo-buildpacks/maven             6.18.3
paketo-buildpacks/executable-jar    6.11.3
paketo-buildpacks/apache-tomcat     8.2.0
paketo-buildpacks/apache-tomee      1.10.4
paketo-buildpacks/liberty           4.3.0
paketo-buildpacks/dist-zip          5.8.5
paketo-buildpacks/spring-boot       5.31.2
===> RESTORING
===> BUILDING
target distro name/version labels not found, reading /etc/os-release file

Paketo Buildpack for CA Certificates 3.8.6
  https://github.com/paketo-buildpacks/ca-certificates
  Build Configuration:
    $BP_EMBED_CERTS                    false  Embed certificates into the image
    $BP_ENABLE_RUNTIME_CERT_BINDING    true   Deprecated: Enable/disable certificate helper layer to add certs at runtime
    $BP_RUNTIME_CERT_BINDING_DISABLED  false  Disable certificate helper layer to add certs at runtime
  Launch Helper: Contributing to layer
    Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
  CA Certificates: Contributing to layer
    Added 151 additional CA certificate(s) to system truststore
    Writing env.build/SSL_CERT_DIR.append
    Writing env.build/SSL_CERT_DIR.delim
    Writing env.build/SSL_CERT_FILE.default

Paketo Buildpack for BellSoft Liberica 10.9.0
  https://github.com/paketo-buildpacks/bellsoft-liberica
  Build Configuration:
    $BP_JVM_JLINK_ARGS           --no-man-pages --no-header-files --strip-debug --compress=1  configure custom link arguments (--output must be omitted)
    $BP_JVM_JLINK_ENABLED        false                                                        enables running jlink tool to generate custom JRE
    $BP_JVM_TYPE                 JRE                                                          the JVM type - JDK or JRE
    $BP_JVM_VERSION              21                                                           the Java version
  Launch Configuration:
    $BPL_DEBUG_ENABLED           false                                                        enables Java remote debugging support
    $BPL_DEBUG_PORT              8000                                                         configure the remote debugging port
    $BPL_DEBUG_SUSPEND           false                                                        configure whether to suspend execution until a debugger has attached
    $BPL_HEAP_DUMP_PATH                                                                       write heap dumps on error to this path
    $BPL_JAVA_NMT_ENABLED        true                                                         enables Java Native Memory Tracking (NMT)
    $BPL_JAVA_NMT_LEVEL          summary                                                      configure level of NMT, summary or detail
    $BPL_JFR_ARGS                                                                             configure custom Java Flight Recording (JFR) arguments
    $BPL_JFR_ENABLED             false                                                        enables Java Flight Recording (JFR)
    $BPL_JMX_ENABLED             false                                                        enables Java Management Extensions (JMX)
    $BPL_JMX_PORT                5000                                                         configure the JMX port
    $BPL_JVM_HEAD_ROOM           0                                                            the headroom in memory calculation
    $BPL_JVM_LOADED_CLASS_COUNT  35% of classes                                               the number of loaded classes in memory calculation
    $BPL_JVM_THREAD_COUNT        250                                                          the number of threads in memory calculation
    $JAVA_TOOL_OPTIONS                                                                        the JVM launch flags
    Using Java version 21 from BP_JVM_VERSION
  BellSoft Liberica JDK 21.0.4: Contributing to layer
    Downloading from https://github.com/bell-sw/Liberica/releases/download/21.0.4+9/bellsoft-jdk21.0.4+9-linux-amd64.tar.gz
    Verifying checksum
    Expanding to /layers/paketo-buildpacks_bellsoft-liberica/jdk
    Adding 297 container CA certificates to JVM truststore
    Writing env.build/JAVA_HOME.override
    Writing env.build/JDK_HOME.override
  BellSoft Liberica JRE 21.0.4: Contributing to layer
    Downloading from https://github.com/bell-sw/Liberica/releases/download/21.0.4+9/bellsoft-jre21.0.4+9-linux-amd64.tar.gz
    Verifying checksum
    Expanding to /layers/paketo-buildpacks_bellsoft-liberica/jre
    Adding 297 container CA certificates to JVM truststore
    Writing env.launch/BPI_APPLICATION_PATH.default
    Writing env.launch/BPI_JVM_CACERTS.default
    Writing env.launch/BPI_JVM_CLASS_COUNT.default
    Writing env.launch/BPI_JVM_SECURITY_PROVIDERS.default
    Writing env.launch/JAVA_HOME.default
    Writing env.launch/JAVA_TOOL_OPTIONS.append
    Writing env.launch/JAVA_TOOL_OPTIONS.delim
    Writing env.launch/MALLOC_ARENA_MAX.default
  Launch Helper: Contributing to layer
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/java-opts
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/jvm-heap
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/link-local-dns
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/memory-calculator
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/security-providers-configurer
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/jmx
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/jfr
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/openssl-certificate-loader
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/security-providers-classpath-9
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/debug-9
    Creating /layers/paketo-buildpacks_bellsoft-liberica/helper/exec.d/nmt
  Java Security Properties: Contributing to layer
    Writing env.launch/JAVA_SECURITY_PROPERTIES.default
    Writing env.launch/JAVA_TOOL_OPTIONS.append
    Writing env.launch/JAVA_TOOL_OPTIONS.delim

Paketo Buildpack for Syft 2.1.0
  https://github.com/paketo-buildpacks/syft
    Downloading from https://github.com/anchore/syft/releases/download/v1.12.2/syft_1.12.2_linux_amd64.tar.gz
    Verifying checksum
    Writing env.build/SYFT_CHECK_FOR_APP_UPDATE.default

Paketo Buildpack for Maven 6.18.3
  https://github.com/paketo-buildpacks/maven
  Build Configuration:
    $BP_EXCLUDE_FILES                                                                                colon separated list of glob patterns, matched source files are removed
    $BP_INCLUDE_FILES                                                                                colon separated list of glob patterns, matched source files are included
    $BP_JAVA_INSTALL_NODE                 false                                                                         whether to install Yarn/Node binaries based on the presence of a package.json or yarn.lock file
    $BP_MAVEN_ACTIVE_PROFILES                                                                                the active profiles (comma separated: such as: p1,!p2,?p3) to pass to Maven
    $BP_MAVEN_ADDITIONAL_BUILD_ARGUMENTS                                                                                the additionnal arguments (appended to BP_MAVEN_BUILD_ARGUMENTS) to pass to Maven
    $BP_MAVEN_BUILD_ARGUMENTS             -DskipTests=true -P make-exe-jar,kubernetes package -pl my/project -am -T 2C  the arguments to pass to Maven
    $BP_MAVEN_BUILT_ARTIFACT              my/project/target/project-1.0.5-SNAPSHOT.jar                                  the built application artifact explicitly.  Supersedes $BP_MAVEN_BUILT_MODULE
    $BP_MAVEN_BUILT_MODULE                                                                                the module to find application artifact in
    $BP_MAVEN_DAEMON_ENABLED              false                                                                         use maven daemon
    $BP_MAVEN_POM_FILE                    pom.xml                                                                       the location of the main pom.xml file, relative to the application root
    $BP_MAVEN_SETTINGS_PATH                                                                                the path to a Maven settings file
    $BP_MAVEN_VERSION                     3                                                                             the Maven version
    $BP_NODE_PROJECT_PATH                                                                                configure a project subdirectory to look for `package.json` and `yarn.lock` files

Paketo Buildpack for Maven 6.18.3
  unable to create application layer
  failed to generate expected metadata
  unable to create file listing for /workspace
  unable to create file listing
  error walking path /workspace
  unable to stat file /usr/bin/python3.10
  stat /usr/bin/python3.10: no such file or directory
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

That part of the code is walking your application files. I suspect that it's probably hitting a symlink that doesn't resolve because the target isn't in the image. I don't know why else it would be looking for that file, nothing in the buildpack directly uses or expects Python to be present.
What is your pack build command? If you're not specifically setting the --path argument, it will use the present directory as the content for your application. Either check that directory or the directory specified by --path and see if there are extra files that don't need to be sent for the build.
You can tell pack to ignore files via the project.toml file. You can usually speed up builds by ignoring unnecessary files as well because it's less for pack to copy into the container.

Thanks for the quick response.
The pack command looks like this:
pack build $IMAGE_NAME --path ~/git/myproject \
 --volume ${BINDINGS_DIR}:/platform/bindings \
 --volume ~/.pack-m2:/home/cnb/.m2:rw \
 -B paketobuildpacks/builder-jammy-full \
 -e PACK_VOLUME_KEY=packvolume \
 -e BP_JVM_VERSION=21 \
 -e BP_MAVEN_BUILT_ARTIFACT=${APP_TO_BUILD}/target/${APP_NAME}-1.0.5-SNAPSHOT.jar \
 -e BP_MAVEN_BUILD_ARGUMENTS="-DskipTests=true -P profile1,profile2 package -pl ${APP_TO_BUILD} -am -T 2C"

The m2 volume mount is a separate m2 folder from my ~/.m2 because I used to get all sorts of permission errors.

I wouldn't expect that to cause the issues you're seeing. I would suggest checking what's in ~/git/myproject. Look for hidden folders, things unnecessary to your app being built and put them in the ignore list.
Everything in ~/git/myproject will be copied into the workspace of the build, unless you specifically ignore it.

Another thing you could try would be to point --path to the target JAR/WAR of your application build. Run Maven locally to build it, and then run pack build with the modified path. This will change so that the build is only the contents of your JAR/WAR, which should eliminate any stray files from making it into the container also.


no_std support

It would be very useful for this crate to be usable in no_std environments. At a glance, the only hard requirement I see in the crate is really alloc, so it could be more lax about requiring the whole std support. That would allow uses in bare-metal and wasm.

Great suggestion! I'm looking into it. WASM would be especially fun.
I recently removed support for 16-bit architectures. I suppose I should put that back in if people might want to run this on a microcontroller.

I have a branch working in WASM now. That mostly required moving crate 'rand' to dev-dependencies.
I tried getting no_std working, but it uses itertools extensively - including .tee() and .kmerge_by() which are only available with itertools std (details). [I'm testing with QEMU as explained by the Rust Embedded Book.] If anyone would really like it on no_std, let me know what features you need. I may keep looking if I can remove some features and make it no_std.
I assume making it WASM-compatible is useful even if it doesn't work on bare metal, yes?

I assume making it WASM-compatible is useful even if it doesn't work on bare metal, yes?

Yes! I mentioned embedded mostly because it's an interesting use case, but WASM is actually something that I could use right now :)

The crate now supports no_std for both WASM and embedded.
I also wrote an article about how to port packages to make them no_std.


Keybindings swallowed

Oni Version:
0.3.6
Operating System:
10.13.5
Issue:
Key bindings swallowed
Expected behavior:
I can use tmux happily with oni
Actual behavior:
When a terminal is loaded in a split (i.e. ctrl+w ctrl+v then :term), oni doesn't seem to allow ctrl+b, through to the terminal instance.
When a terminal is loaded as the only buffer, oni doesn't seem to listen for ctrl+w ctrl+v.
Steps to reproduce:
open a tmux session and try to create a new tmux split. (alternatively, I'm sure this problem goes beyond tmux, and extends beyond ctrl+b, but i'm not sure how to test which keystrokes are making it through (i.e. how to generalize the problem)).

I don't understand, isn't tmux a terminal multiplexer? Should'nt this be a neovim issue then?

Does it work as expected in neovim?

From discord, they said it worked fine in normal nvim so we must be swallowing some form of input.
I've tried this on my machine, and I can't reproduce the second part (When a terminal is loaded as the only buffer, oni doesn't seem to listen for ctrl+w ctrl+v.)
I'm trying it as follows:

Open Oni, run :term.
Try ctrl-w ctrl-v and works as expected.
It does not work if I enter insert mode, but that is also expected due to the input now being sent to the terminal, rather than to nvim itself.

I'm going to try the tmux bit in a linux VM, since it should be easier than attempting it on Windows.


Add teams manifest preview

Q
A

Bug fix?
no

New feature?
no

New sample?
no

Related issues?
none

What's in this Pull Request?
Adds manifest.json and manifest-localhost.json files for preview Teams manifest support.

I'm unable to directly add these comments to the README file, so adding them here for your consideration:

Will this sample be added to the Teams sample page/gallery? If so, we may need to update the products metadata.
At the end of the 'Configure a localhost web server and run the sample from localhost' section, consider mentioning the steps to sideload a Teams manifest and link to the 'Run the Teams manifest version of hello world' section.

Is this ready to be checked in?


raftstore: batch apply msg to reduce apply state keys

Signed-off-by: gengliqi<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: ref https://github.com/tikv/tikv/issues/11303
Problem Summary:
As https://github.com/tikv/tikv/issues/11303 said, this PR reduces some apply state keys through batching apply msg.
Although we know the apply state key can be significantly reduced by writing it regularly, there are some cases that need to think further. This PR uses a simple method to alleviate this problem. Adjacent apply msgs can be batched if they have the same peer id and term.
The test result shows it can reduce about 30% apply state keys.
What is changed and how it works?
What's Changed:
Mentioned above.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Manual test (add detailed scripts or steps below)

Side effects

No

Release note
None.

Perhaps cache the updated ApplyState with HashMap and merge them to the WriteBatch before it is committed to RocksDB is much simpler and more efficient since it can handle well with non-adjacent apply msg.

Perhaps cache the updated ApplyState with HashMap and merge them to the WriteBatch before it is committed to RocksDB is much simpler and more efficient since it can handle well with non-adjacent apply msg.

I have tried to just set RaftApplyState before writing to db. I found a problem that the RaftApplyState is not included in ApplyMetrics. As #11303 said, the number of RaftApplyState can not be ignored.
I choose to batch adjacent apply msg just for simplicity and the result is good enough because most of the msg is apply msg.

But I found the load imbalance in this version. I suspect the root cause is that RaftApplyState is not included in ApplyMetrics. As #11303 said, the number of RaftApplyState can not be ignored.

Sorry I don't get it, ApplyMetrics should be counting from WriteBatch directly, RaftApplyState should not be missed. Also, the ApplyMetrics is just for updating store level write flow, which mean we can add the ApplyMetrics to any region's ApplyRes or just add an additional message to do that.

I choose to batch adjacent apply msg just for simplicity and the result is good enough because most of the msg is apply msg.

Still, I think the above-mentioned approach is much simpler

But I found the load imbalance in this version. I suspect the root cause is that RaftApplyState is not included in ApplyMetrics. As #11303 said, the number of RaftApplyState can not be ignored.

Sorry I don't get it, ApplyMetrics should be counting from WriteBatch directly, RaftApplyState should not be missed. Also, the ApplyMetrics is just for updating store level write flow, which mean we can add the ApplyMetrics to any region's ApplyRes or just add an additional message to do that.

I choose to batch adjacent apply msg just for simplicity and the result is good enough because most of the msg is apply msg.

Still, I think the above-mentioned approach is much simpler

If RaftApplyState is not pushed into WriteBatch before sending ApplyResult, the ApplyMetrics will miss this state. And then the written_bytes and written_keys will send to PD through heartbeat which is peer level, not store level.
The simplicity I mentioned means this method does not change the original behavior as much as possible. This is because I want this PR can be merged as soon as possible.
As the description said, we can significantly reduce the apply state keys by writing them regularly. So after this method is implemented and all the corner case is considered, the code of batching apply msg will be removed.

If RaftApplyState is not pushed into WriteBatch before sending ApplyResult, the ApplyMetrics will miss this state. And then the written_bytes and written_keys will send to PD through heartbeat which is peer level, not store level.

I have a better idea, we can use HashMap to store ApplyRes too, then we can update it for each Apply msg instead of creating a new one, this way we can reduce ApplyRes msg as much as RaftApplyState write. So that we can also update the ApplyMetrics in ApplyRes for the RaftApplyState.

The simplicity I mentioned means this method minimizes the change of original behavior as much as possible. This is because I want this PR can be merged as soon as possible.

I  think simplicity of code is also the key to let PR be merged quickly.

If RaftApplyState is not pushed into WriteBatch before sending ApplyResult, the ApplyMetrics will miss this state. And then the written_bytes and written_keys will send to PD through heartbeat which is peer level, not store level.

I have a better idea, we can use HashMap to store ApplyRes too, then we can update it for each Apply msg instead of creating a new one, this way we can reduce ApplyRes msg as much as RaftApplyState write. So that we can also update the ApplyMetrics in ApplyRes for the RaftApplyState.

The simplicity I mentioned means this method minimizes the change of original behavior as much as possible. This is because I want this PR can be merged as soon as possible.

I think simplicity of code is also the key to let PR be merged quickly.

I don't understand why you think this PR is complex. Also, the method you said should be no better performance improvement compared with this PR because most of apply msgs can be batched together.
The simplicity doesn't just mean less code. I choose to just batch Adjacent msgs because I worry about the reorder of different types of msgs which has a risk and I have not much time to think it through.

I don't understand why you think this PR is complex. Also, the method you said should be no better performance improvement compared with this PR because most of apply msgs can be batched together.

I didn't say this PR is complex, what I mean is, in relatively there is a better approach that is simpler and more efficient (it also reduces the number of ApplyRes msg) why not adopt it? If you are worried about any risk or complexity this approach may bring, would you describe more about them?

I also thought about the write state in flush before. But I think the current way also works and a bit easier to review as besides changing processing orders,  the logic is the same as before except batching up entries. Both ways are OK and acceptable.

/release

/run-build-arm64 comment=true

/merge


Remove custom colour from checkboxes

Old:

New:

No problem, whole app is flaky right now :grin:
I removed something from this to see if it was failing the test, but I think I'll add it back in...


Java 17: issues with classes in org.ice4j.socket.jdk8

I tried compiling ice4j with Java 17 and ran into issues with the stuff in org.ice4j.socket.jdk8. Java 16+ removed --illegal-access=permit and sun.nio.ch.SelChImpl is thus basically not available anymore.
I have a hard time to understand that code. I'm probably missing something, but if this is about filtering/redistributing incoming packets, why can't that be done with a regular (Server)SocketChannel? Is that code still needed at all?
@damencho thinks it's not needed anymore and was used when Jetty was serving web+tcp media. @bgrozev / @JonathanLennox ?

@damencho thinks it's not needed anymore and was used when Jetty was serving web+tcp media

I concur that this is/was the only purpose of this code.

@bgrozev can I interpret that as: the entire JDK8 package can be removed?

Yes.


Use native executable by default and move Docker GHA to another path

As Docker-based GHA is not testable locally and there are a bunch of known and unknown issues due to Docker in Docker limitations, we should not use Docker GHA by default.
This PR uses native executable binary e2e and move Docker-based GHA to subpath docker, if @mrproliu you want to test Docker-based GHA, please use apache/skywalking-infra-e2e/docker@main

This will also closes https://github.com/apache/skywalking/issues/7506

I am good for us to use official docker for longer term.

Yes that's my and @mrproliu 's opinion, but nowadays we'd better use native executable binary as Docker container is not well tested


Make documentation page more responsive

Documentation page style does not look good on small screens

Assign it to me pls


panic when retstart the 0.7.0 client

The  0.7.0 client paniced when I restarted it after synchronizing to the lastest block.
The log shows as below:
[2023-06-25T03:17:23Z INFO  ord::options] Connecting to Bitcoin Core at http://<IP_ADDRESS>:8332
[2023-06-25T03:17:23Z INFO  ord::options] Using credentials from cookie file at `../conf/cookie`
thread 'main' panicked at 'internal error: entered unreachable code', /user/.cargo/registry/src/github.com-1ecc6299db9ec823/redb-0.13.0/src/multimap_table.rs:110:18
stack backtrace:
   0: rust_begin_unwind
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/panicking.rs:579:5
   1: core::panicking::panic_fmt
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:64:14
   2: core::panicking::panic
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:114:5
   3: redb::multimap_table::parse_subtree_roots
   4: redb::db::Database::new
   5: redb::db::Builder::open_mmapped
   6: ord::index::Index::open
   7: ord::subcommand::Subcommand::run
   8: ord::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

How could I resolve the client?
It seems that it cannot be restarted after the client starts...

The log shows as below:
[2023-06-25T03:17:23Z
INFO ord
options:
]
Connecting to Bitcoin Core
at
http://<IP_ADDRESS>:8332
[
2023-06-25
T
03:17:23
Z INFO
ord
options:
]
Using credentials from cookie
file at
*
/
conf:
/
cookie
thread
main
panicked at
internal error
entered unreachable
code
/user/.cargo/registry/src/github.com/1ecc6299db9ec823/0.2/src/multimap-table.rs/10:8
stack:
backtrace:
0:rust-begin-unwind
at
/
<rustc
/
84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc
/library/std/src/panicking.rs:579:51:core:panicki:panic-fmt>
at /
<rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:64:142:core:panicking:panic>
at </rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/panicking.rs:114:5>
3:
'redb
multimap
table
parse
subtree
roots
4
redb
db:
Database:
new:
5
db:
Builder:
open
M:
mapped:
6
ord:
index:
Indexopen:
7
ordsubcommand:
Subcommandrun:
8
ordmain:
note:
Some details are omitted
run with
RUST
BACKTRACE
full
for a verbose backtrace
It seems that it can
be restarted after the
client starts
<Ctrl+Shift+>
<Ctrl+e>

FWIW I see the same issue.

Okay, so the issue only occurs if the redb thinks it needs repair.
I'm not sure multimaps are crash safe or Control-C safe.

FWIW I see the same issue.
Panic is here: https://github.com/cberner/redb/blob/v0.13.0/src/multimap_table.rs#L110
The data seems corrupt in the on-disk redb. I definitely shut down the ord server cleanly before restarting it, so I'm not sure what's going on --something about multi maps is unsafe in v0.13.0 of redb.

In my experience ord server consistently leaves the redb in a bad state. I don’t know if “corrupt” is the right word, but I reported this behavior months ago: https://github.com/ordinals/ord/issues/1861

FWIW I see the same issue.
Panic is here: https://github.com/cberner/redb/blob/v0.13.0/src/multimap_table.rs#L110
The data seems corrupt in the on-disk redb. I definitely shut down the ord server cleanly before restarting it, so I'm not sure what's going on --something about multi maps is unsafe in v0.13.0 of redb.

In my experience ord server consistently leaves the redb in a bad state. I don’t know if “corrupt” is the right word, but I reported this behavior months ago: #1861

In this case, if you log value on that line, it's just random data.
In my case it was just gracefully stopping ord server.

Okay, tracked this down to this redb commit:
https://github.com/cberner/redb/commit/23d1a7071b40101595a5aef6c098d6f31010f5cf
If i make the same modification on a local redb 0.13.0 checkout, the recovery works.
The reason the redb enters recovery every time with ord server is this code:
[2023-06-26T22:08:16Z INFO  redb::transactions] Beginning write transaction id=TransactionId(199)
[2023-06-26T22:08:16Z INFO  redb::transactions] Opening table: HEIGHT_TO_BLOCK_HASH<u64, [u8;32]>
[2023-06-26T22:08:16Z INFO  redb::transactions] Opening table: WRITE_TRANSACTION_STARTING_BLOCK_COUNT_TO_TIMESTAMP<u64, u128>
[2023-06-26T22:08:16Z INFO  ord::options] Connecting to Bitcoin Core at <IP_ADDRESS>:8332/wallet/ord
[2023-06-26T22:08:16Z INFO  ord::options] Using credentials from cookie file at `/home/bitcoin/.bitcoin/.cookie`
[2023-06-26T22:08:16Z INFO  redb::transactions] Aborting transaction id=TransactionId(199)
[2023-06-26T22:08:16Z INFO  redb::transactions] Finished abort of transaction id=TransactionId(199)```

Which happens every second or so. If you Control-C after the begin write transaction and before the abort, the database is in an unclean state.
Might be time to bump redb to 1.0.1 @raphjaph ?

Okay, tracked this down to this redb commit:
cberner/redb@23d1a70
If I make the same modification on a local redb 0.13.0 checkout, the recovery works.
Might be time to bump redb to 1.0.1 @raphjaph ?

Raph has been working on a refactor PR for redb 0.20.0: https://github.com/ordinals/ord/pull/2141, so 1.0.1 seems far.
I just checkout a new disk space to reorg for 0.7.0 and encountered the issue too, not sure if it will be an issue for most people or there's an official solution on that @raphjaph

also encountered the same issue under exactly the circumstances described by @jack-linden.
ord index run stopped by

ssh logout
ctrl-c

had to delete the index db and re-index again. A bit frustrating

also encountered the same issue under exactly the circumstances described by @jack-linden.
ord index run stopped by

ssh logout
ctrl-c

had to delete the index db and re-index again. A bit frustrating

how do you delete the index db and re-index again, do you have a specific command for that ?

same here, crushing again and again.

I can confirm that when I pull in these changes to a local version of redb 0.13.0 it fixes the issue and I can reindex 0.7.0 fine even after ctrl-c or stopping the server.

Okay, tracked this down to this redb commit:
cberner/redb@23d1a70
If I make the same modification on a local redb 0.13.0 checkout, the recovery works.
Might be time to bump redb to 1.0.1 @raphjaph ?

I can confirm that when I pull in these changes to a local version of redb 0.13.0 it fixes the issue and I can reindex 0.7.0 fine even after ctrl-c or stopping the server.

Discussed with @raphjaph - plan is to rebase our 0.20x redb update PR to master and verify it also fixes the issue. Alternative might be a manually patched redb 0.13.x but we'd prefer the proper redb update.

same here

Any time estimates for the 0.20.x update? If it's far off, maybe it makes sense to upgrade to 0.13.x in the meantime so that it stops the crash?

https://github.com/ordinals/ord/pull/2141

Fixed by updating redb https://github.com/ordinals/ord/pull/2141

Even with the fix, I am still getting error
thread 'main' panicked at 'internal error: entered unreachable code', /Users/xx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/redb-1.0.2/src/tree_store/btree.rs:546:18
stack backtrace:
0: rust_begin_unwind
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/panicking.rs:67:14
2: core::panicking::panic
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/panicking.rs:117:5
3: redb::tree_store::btree::RawBtree::verify_checksum_helper
4: redb::tree_store::table_tree::TableTree::verify_checksums
5: redb::db::Database::verify_primary_checksums
6: redb::db::Database::do_repair
7: redb::db::Database::new
8: redb::db::Builder::open
9: ord::index::Index::open
10: ord::subcommand::Subcommand::run
11: ord::main


Close #255,fix pip depandency miss match

Thanks for contributing. (I just changed the one relevant line, because I am not sure about side effect of removing all versions.)


[Enhancement] cache iceberg partition names when mv get updated partition names

…
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 26 (07.69%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
0
9
00.00%
[736, 737, 741, 742, 743, 744, 745, 747, 750]

:large_blue_circle:
com/starrocks/connector/PartitionUtil.java
0
9
00.00%
[259, 261, 262, 265, 266, 267, 268, 269, 271]

:large_blue_circle:
com/starrocks/catalog/IcebergTable.java
2
8
25.00%
[133, 137, 138, 141, 145, 146]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


Unable to import Available Peers that only have a single address family

Environment

Python version:  3.6.8
Peering Manager version:  v1.3.3-dev

Steps to Reproduce
Try to import peer from Available Peers on Internet Exchange with only an IPv4 or IPv6 address (but not both)

Expected Behavior
To be brought to the peer import screen to confirm peer details

Observed Behavior
Brought to blank import screen

This is what Internet Exchange Peering Session Import screen looks like after I click Add Select

Basically no peer details to confirm

Digging a bit deeper in this, it looks like at least some of the peers that won't import are already existing peers, and should not show up on the Available Peers list

@ggiesen To clarify, to replicate this the following conditions need to be met:

Peer is present on an IX via v6 or v4, but not both
Peer is currently a peer on the relevant IX

Is that correct?

I'm unable to reproduce this as of today. Best guess is it got fixed as a side effect of another fix. Anyone still having the issue?


How to configure "fix on save"

Thanks for asking, but to be honest: I don't use that feature, so there currently is no way to configure it.
I'll have a look at it.

and no config for set 1 hotkeys for Fix All

+1

After having found 'Microsoft is sunsetting atom' this weekend, I have come to the decision to not dig any further into atoms api. Instead I will move on to another editor.
However. This is Open Source and if it's important for you, you are free to fork this project and submit pull requests.


[release-0.44] fix ca rotation test

What this PR does / why we need it:
Test with id 4099 and 4100 are not waiting for VMI to come up.
Therefore console connection is attempted sooner than it could succeed.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Connection timeout seems to be high(180sec) but I can see the connection to virt-handler is established just before the timeout and therefore failing the test.
Release note:
None

@xpivarc Hi. Thank you for noticing that. I have seen situations where we had expecter console timeouts, although the VMI was at Running phase as well as the VMI pod. These situations are when the VM guest stuck at BIOS boot stage, when no appropriate boot media was recognized.
Nevertheless this PR introduces more accuracy to the test.

@xpivarc BTW I see that this change also relevant for main branch, why wouldn't you fix it on main and cherrypick?

@enp0s3 Thanks, I opened https://github.com/kubevirt/kubevirt/pull/6827

@xpivarc Hi. I will close this PR in favor to #6848

/close


How to Set Platform Brightness in android When Click one Page Screen will be brightness and again i go back the screen will reduce and go back to platform brightness?

Description (bug summary)
Step to reproduce (how to reproduce the bug)

how to set Platform Brightness in this package

Platform (Android/iOS/macOS/Windows)
Android,Ios

Hi, @DazzlingCVa. Please take a look at the example Route aware example page. I think that is what you needed.


MM-17042: Add ability to run "tagged" cypress e2e tests

Summary
You can use tags like  npx cypress run --env tags='["@smoke"]'. Note that it needs to be a string like that so the JSON is parsed correctly. Calling a command like that will ONLY run tests that have @smoke somewhere in it's full title. Tagging a parent describe block will then run all the tests within it, or alternatively you could target a test somewhere deeply nested. Tests not run are marked pending when it comes to results.
I went and added @smoke to our login_spec.js as a starting point, we can identify more smoke tests (or other tags, perhaps `@enterprise'?) in later PRs.
Ticket Link
JIRA

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei


p5.js mode

Hi, not really an issue here:
Is there a way to use p5.js with ssam? This doesn't seem to work: P5 Mode
Cheers

Hi,
p5 works differently than most other canvas libraries, so I haven't got a chance to integrate it yet.
I cannot promise if or when it will be done as I don't use p5js much personally and with my limited time and resource, I can only focus on the things that I use most often.
Sorry about the confusion! I will edit the doc to be more clear.
Please refer to the Wiki for currently supported features.

Thank you!


compile problem in SimpleOpenGL/vrexample.cpp

Something to do with initializing the "count" variable on line 85.

Dan: Can you confirm that this fix was appropriate and close this issue if it was?

Looks good to me.


Cache CARGO_HOME

Cargo stores downloaded into $CARGO_HOME, which defaults to $HOME/.cargo. That is not going to be useful in CNBS, so we should be setting $CARGO_HOME to a layer that is set with build + cache flags. That way downloaded resources are restored for subsequent runs of the buildpack & if something needs to be recompiled, Cargo will not need to hit the Internet to download resources again.
The entire folder does not need to be cached though. This actually retains some duplicate information. According to this doc link we can trim down the size a bit by storing only these folder:

bin/
registry/index/
registry/cache/
git/db/

I did some testing on this and setting CARGO_HOME does indeed help. It prevents cargo from downloading things over and over. It doesn't seem to do as much as I'd have hoped though. Cargo is still rebuilding a lot of files. Looking deeper it seems to be due to timestamp differences. That seems odd to me, but I didn't have time to look more & need to, since it's adding way too much overhead and rebuilding unnecessarily.

Looked into this a bit more. When cargo install runs, it's looking at the mtimes of the files. These appear to be off slightly in a couple of cases. Those then ripple out and cause other things to be rebuilt, which on a large project can cause significant delays.
You can set CARGO_LOG=cargo::core::compiler::fingerprint=trace to see more details about the decisions it's making.
Testing locally, this doesn't happen. Nor does testing with Dockerfile & docker build.
I suspect that this has to do with the way the cache layer is being restored & that the old mtimes are not persisted. Thus what you have is the mtime set to the time the file was extracted, not the time it was originally written by the Rust compiler. When you cargo next, it checks the mtimes which are wrong and rebuilds accordingly.

Closed by #41


Add options to preload modules

Hi there,
Is it possible to add an option to preload certain modules, so that autocompletion feels faster? For example, useful for big libraries such as numpy.
See jedi docs: https://jedi.readthedocs.io/en/latest/docs/api.html#jedi.preload_module
Thanks!
Hans

In the latest release, I've handled this by exposing auto_import_modules to the end user. See here: https://github.com/pappasam/coc-jedi#jedijedisettingsautoimportmodules
Please let me know if this solution performs acceptably for you.

Hi! Awesome!
Sadly however it doesn't seem to work? At least the first time completions of libraries I add is not sped up.
I wanted to debug myself, but could not find a reference to jedi's preload_module, only to auto_import_modules. Reading the documentation I'm not sure auto_import_modules is the same as preload_module.

@HansPinckaers please install the latest version of jedi-language-server. I suspect that you only updated coc-jedi.
In the future, until we're able to figure out how to set up a nice environment automatically for conda users, you'll need to manually update jedi-language-server.

Additionally, you are correct that preload_module is different than the auto_import_modules. Based on my testing, preload_module didn't yield substantial speed improvements while auto_import_modules sped things up considerably.
It's still not perfect, but it made numpy completions bearable (at least on my machine).

After a first test, I did indeed remember to also update the jedi-language-server :slightly_smiling_face:
For me, numpy autocomplete is pretty fast (also with coc-python), I do not really see any benefit when using auto_import_modules. However, the first time is slow, that is why I wanted to try preload_module.
I tried to hack it in like this, but it does not seem to do improve the first autocomplete. I wonder if it is a bug of jedi in that case.

(I created a preload_module function in jedi_utils that just calls jedi.preload_module)

Perfect! In that case, I think we can consider this particular issue resolved.


Shouldn't the 'tr' register be completely transparent by default?

The original idea with the hardwired 'tr' register is that it should transpose the pitch of all oscillators in a voice. Subvoices automatically inherit their values of 'tr' from their parent voice. It is possible for programs to override this by simply altering the 'tr' register as desired, though that will only affect subvoices spawned after the change - not subvoices already playing.
The problem is when programs generate pitch by other means than via 'wtosc', one of the 'fm' oscillators, or similar. When using 'dc' as an oscillator, or implementing hardsync effects and the like, the 'p2d' instruction is used for converting linear pitch into period times in milliseconds - but 'p2d' does not honor 'tr'! So, to properly support 'tr' with such programs, 'tr' has to be applied explicitly in the script code, which is ugly, unintuitive, and error prone.
Are there other cases where 'tr' doesn't work as intended? Are there other cases we need to handle?

I suppose it all boils down to explicitly stating that the 'tr' register should ALWAYS be honored when dealing with pitch - which of course implies that both oscillators and 'p2d' should honor it.
The "only affects subsequent operations and voices spawned" behavior should probably be explicitly stated as well, as anything else would be rather hairy and expensive to implement, and probably not very useful.

NOTE: 'wtosc', 'filter12', 'dcblock', and the 'fm*' units grab the 'tr' register when they're instantiated, so 'tr' changes in the local voice will have no effect, even when applying new values to the pitch registers!


Amplify Federated Sigin with Gmail needs Email as maindatory attribute

I started a new amplify project using amplify init. I added auth and used Username as Sig-in Method but i used Social providers with default Configuration and added Google and Facebook but in additional required attributes i removed Email and select none.Then i push the code it throws error about HostedUIProviders....
Then if i make email as required attribute it worked but with Facebook it causes error because not every Facebook user uses the email method some of them prefer mobile phones and other..
but before in amplify-cli version < @4.29.0 it does not throw any error.

It looks like this is the same issue reported in #5681 which has been fixed. Please follow up if you're still running into issues

It looks like this is the same issue reported in #5681 which has been fixed. Please follow up if you're still running into issues


Can not able to plot Keras Model API

Keras Model API  not supported with ValueError: ANN Visualizer: Layer not supported for visualizing
I think this arises due to Input layer
my code is
from keras.models import Model
from keras.layers import Input, Dense

a = Input(shape=(32,))
b = Dense(32)(a)
model = Model(inputs=a, outputs=b)
model.summary()

ann_viz(model, title="My first neural network")

I'm getting the same error message using the same model.

I am running into this problem as well. Maybe this is due to the update to Tensorflow 2.0?