[Bug]: another devbox binary is used

Current Behavior (bug)

I want to use the binary in /usr/local/bin whose version is 0.4.4, but it seems that the binary in dist is used.
Expected Behavior (fix)
Use the former devbox instead of the latter one.
Additional context

This has thrown me off too. I tend to build and run with go install ./cmd/devbox && devbox which puts it in my $GOBIN directory. I didn't realize I had been running an old dist/devbox binary instead.
The reason is because devbox.json sets PATH=$(pwd)/dist:$PATH in the init hooks. @mikeland86 is it okay to remove this? I think it's a bit surprising if you don't know about it.

I think it makes sense to remove it. It's convenient, but easy to miss and pretty unexpected.

This has thrown me off too. I tend to build and run with go install ./cmd/devbox && devbox which puts it in my $GOBIN directory. I didn't realize I had been running an old dist/devbox binary instead.
The reason is because devbox.json sets PATH=$(pwd)/dist:$PATH in the init hooks. @mikeland86 is it okay to remove this? I think it's a bit surprising if you don't know about it.

Oh, I forgot it...


Fibonacci series using recursion

hi, I am a Gssoc'21 participant I want to work on the "Fibonacci series using recursion " in python.
could you please assign me and also guide me through my first contribution.

I want to work on this issue. Please assign me.

Hello, @rudrakshi99
I am a GSSOC'21 participant and would like to contribute to this issue " Fibonacci series using recursion" in Python.
I will make sure that the code is readable and understandable by the beginner by using proper comments.
Please, assign this issue to me.

present at #635


Cannot get engine version

I think there is a regression between the 2 commits 05838ef..5c9feb2
I couldn't test the intermediate commits due to rust crashing but with the 1st commit, 93/95 extensions from my config were converted to nix but with the 2nd commit only 9/95 succeeded.
I get warning message for different versions of every failing extention, eg: src/main.rs:58: Cannot get engine version for GitLab.gitlab-workflow 2.2.0

Yes, I encountered this problem too. According to the current logs, it is because the requested data is missing some data. I will fix it as soon as possible.

I recently committed some changes, is there any improvement in your scenario?

I just tried 1f1537c but I get the same result, here's my config.toml: config.txt (I had to change the extension to upload on GH)

ok, thanks

dev branch should fix this. can you give it a try?

The issue is fixed on dev branch thanks!

thanks for your report. :)


[BUG] - Summary of the problem here

REQUESTS WILL BE IMMEDIATELY DELETED, you cannot do feature requests such as "Update to Angular xx"
I deal with updates with my own schedule, don't need a reminder.
Describe the bug
The visual is not the same if you select different hours. I had this bug in a project I use and found the same one in the online examples.
In my own project I also get the same visual problem with the hours display

In the example page of the project (https://tonysamperi.github.io/ngx-mat-timepicker/), the bug is present in the minutes section of the 12 hour format when you select "4 hours"

To Reproduce
The error is present on the main example page as shown in the fallowing video.
https://github.com/tonysamperi/ngx-mat-timepicker/assets/22448486/39a563cb-c397-42ee-b3c2-335c78771ccc
Expected behavior
Same visual for all different hours and no as crowded in the minute page.
This image shows what I would expect

Screenshots

Desktop (if execution):

Brave
Edge
Probably others

** Versions

ngx-mat-timepicker version 17.0.0
@angular/core version 17.0.4
@angular/material version 17.0.1
typescript version 5.2.2

Additional context (optional)
Thank you for the amazing package. It has been a game changer for time input in my different projetcts.

I tried adding global style as suggested in #57 and the same behavior continues.

In my apps case i had to be very specific in the overrides, this is what i did to get it looking properly...
I understand this snippet does not follow all best practices, but it is working for now. I hope it helps.
`.timepicker {

.timepicker__main-content > .timepicker__body {

ngx-mat-timepicker-12-hours-face > * > .clock-face > .clock-face__container > .clock-face__number {
.mdc-fab {
box-shadow: none;

    &.mat-mdc-mini-fab.mat-primary {
      --mat-fab-foreground-color: #{rgb(133, 38, 62)};
    }
  }
}

> ngx-mat-timepicker-minutes-face > ngx-mat-timepicker-face > .clock-face {
  > .clock-face__container > .clock-face__number > .mdc-fab {
    &.mat-mdc-mini-fab {
      &.mdc-fab--mini {
        height: 0;
        width: 0;
      }

      &.mat-primary {
        --mat-fab-foreground-color: #{rgb(133, 38, 62)};
        height: 40px !important;
        width: 40px !important;
      }
    }

  }

  > .clock-face__clock-hand > .mdc-fab {
    top: -16px;
    left: calc(50% - 8px);
    height: 16px;
    width: 16px;
  }
}

}
}`
Results:

Hi @achapman009,
I just tested your snippet and it fixes the minutes dialog, but not the hours one in my case. If I put my picker in 12h display everything work as intended with your suggested edit.  I'll search in that direction and find what I need to fix the 24h hour page.
I'll leave the issue open since having it not consistent on the main example page is still an issue though.
Thanks for guiding me in the right direction and the quick reply!

@MaximBolduc
I took a glance, i think i got it figured out.. please look at line 24, i addeda  24 hour variant

@MaximBolduc
I took a glance, i think i got it figured out.. please look at line 24, i added a 24 hour variant

We arrived basically at the same conclusion. I edited my last post a couple minutes ago to add the --inner field and the 24h variant. I'll update my styling for all my projects that use this library.
Thanks for taking the time to look at it a little more.
Have a nice day!

Ok guys. Thanks, now I get the problem. Another guy raised the issue, but he didn't say anything on how to reproduce.
It's about the disabled buttons. When no minute is suitable (in the example the max hour is 4, so when you have 4 as hour, you can only have 0 as minute, so all the rest will be disabled).
Fixing this tomorrow morning.
Thanks

Fixed in v 17.0.1


add github workflow to assign tasks to people commenting 'take'

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Assign an issue to the person who comments "take".
Does your contribution introduce a new dependency? If yes, which one?

No
PR checklist for new estimators

Any other comments?

Not sure how to test workflow

Thanks @hiqbal2 for the contribution, now merged!


tmp fix added for 4.15 e2e

/approve

More details on why the fix is needed will be helpful.
We should create an issue before and then raise a pull request to mark the issue.

Created a issue https://github.com/ocp-power-automation/ocp4-playbooks-extras/issues/64 with the details


ADC/linker problem - won't compile (STM32L432KC)

I'm trying to use the ADC example with an STM32L432KC, using the latest version from GH ("git = "https://github.com/stm32-rs/stm32l4xx-hal"). It won't compile, throwing the following error:
note: "rust-lld" "-flavor" "gnu" "--eh-frame-hdr" "-L" (omitted)
= note: rust-lld: error: undefined symbol: ADC1_2
>>> referenced by stm32l4.arnfbrxu-cgu.3
>>> stm32l4-3c82b24cdd335e86.stm32l4.arnfbrxu-cgu.3.rcgu.o:(__INTERRUPTS) in archive

As suggested in the L4 section, I cross-checked between PAC and Reference Manual:
in PAC  there are the following lines:
ADC1:
    _modify:
        _interrupts:
            ADC1:
                name: ADC1_2

and ADC1_2 also appears in the NVIC vector table in the RM as ADC1 and ADC2 global interrupt (page 322).
So it does seem to be all in order, yet it won't work. What am I doing wrong?

I had a look now an am unable to see where this goes wrong.
Could you share an example that exercises the error?

I basically tried to replicate this example, but I will upload my actual code later.

Thanks, please post here when you have it available

https://github.com/nebelgrau77/STM32L4_ADC_test - I just put together a simple ADC to UART code, following the example from the STM32L4 crate.


feat(tibuild): support dev-build with image builder param for tekton engine

support -builderImg cli option for tekton engine.
support tag ref type for tekton engine.

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Finish cookbooks

Hi @sethvargo, any plans to merge this PR soon?
I found your nice chef-api gem today, and started to use it for some chores that needed automation, until I ran into the cookbook iteration issue, but with this PR rebased with master I created the gem and installed it, and as far as I can tell everything works like a charm, tested some stuff using nodes and cookbooks.
Great work, thanks.


[Templates] Fix spelling and use FluentValidationSummary

Fix spelling mistake FluentValidationMesssage (3 x s)
Replave ValidationSummary with FluentValidationSummary

Hi @vnbaaij, is the Template nugget package getting updated with this change?

Yes, a new Templates package will be part of the next release (v4.3). We have not settled on a date yet (but definitely not this year anymore)


Feature/314 - Improve Nav Bar Responsiveness & Update Account Layout

What

Updated various acceptance test files related to the Header and ProfilePage components.
Updated the ProfilePage form to include the LanguageDropdown and reworked the page to match the proposed new layout
Updated the LanguageDropdown's style and responsive behavior per it's new location to display correctly there.
Updated the Persona, PersonaNav and TopNav components layout and style to handle the changes to responsiveness as well as to catch missing expect behavior like cursors for actionable items.
Updated the locale files to account for new and updated strings that were needed for all of this.

Why

Provides a much more responsive header bar that keeps more of the important items visible in narrower viewports.
ProfilePage becomes more like like a general account settings page.

How

Per the issue's design, changed some of the styling and breakpoints such that it would keep the desired header menu elements on screen longer, as well accounting for edge things like longer names that could create an issue with the breakpoint changes by adding some CSS rules to avoid those problems.
Similarly, reworked the layout of the account/profile view into the dual column design proposed in the issue design by moving various existing sections of that layout to match and handle the addition of the language selection.

Testing

Moved language related testing from the header to the profile.
Cut language tests that were over-zealous (we just need to see the element is on the profile page.)
Did manual testing of the breakpoint changes during development to ensure that they triggered as expect as the viewport changed/shrunk.

Screenshots
Before Mobile:

After Mobile:

Before Medium/Tablet:

After Medium/Tablet:

Before Full:

After Full:

Anything else
Reworking the profile was a strong reminder we should consider specifically calling out the work to start doing two things:

Start deprecating react-bootstrap components like Row and Col to say nothing of the myriad bootstrap classes in favor of FluentUI React elements like Stack (https://developer.microsoft.com/en-us/fluentui#/controls/web/stack) such that we don't have as many library dependencies so dev is less challenging as we can stick to one set of documentation.
While handling the above, we also have some pretty similar forms for Admin/User accounts and Clients amongst other code duplication, so there's a strong reuse opportunity here to clean that up while streamlining dependencies.

Okay, looks like trying to remove testing related classes continue to be an issue. I think there's some tooling that let you add conditional handles for testing that get filtered out in prod for stuff like this. Nothing for this check in (I am going to relent and put the class back for now,) but something I am going to note here to consider later.


feat(rules): enable all recommended rules

This PR completes the enabling all of ESLint's recommended rules. I ran it against api and there are only 76 errors, mostly because of one rule so it should be easy it to adjust.
In a future PR, I'll enable all the es6 features and linting rules before we cut a new version. I didn't do that here so it would be easy to tell which rules are for es6 and which are more general.
As far as how to review this, I don't necessarily expect you to look up each rule's definition, but this is more of an opportunity to provide feedback on the linter so far and to solicit suggestions for rules you'd like to see added. However, you can see these new rules in action by checking out this branch locally, and running npm link. Then from your chosen project, e.x. api, run npm link eslint-config-lob. Then when you run npm run lint in api, it will be using the rules in this branch. When you're done, run npm unlink eslint-config-lob to point api back to the version of the config in its node_modules folder.

Some rules I think we should have as well:

no-redeclare
dot-location: [2, "property"]
no-extra-bind: 2
no-redeclare: [2, { "builtinGlobals": true }]
no-loop-func: 2
no-implied-eval: 2
no-eval: 2
no-with: 2
no-useless-concat: 2
no-delete-var: 2
no-shadow: [2, {"builtinGlobals": true, "hoist": "all"}]
no-shadow-restricted-names: 2
no-catch-shadow: 2
newline-after-var: 2 - this one is a bit controversial and would cause quite a few errors in lob-api
no-lonely-if: 2
new-parens: 2
padded-blocks - this one should either be always or never, we can discuss which, but I'd like it to be consistent

I'm completely open to discuss it though!

Thanks @robinjoseph08! I updated the rules in a new commit. Let's discuss newline-after-var and padded-blocks before we add them. @brianseitel and @mgartner, what are your thoughts on those two rules?

I don't personally think any of these are worth the effort, but it's up to you guys, I guess.
My vote for padded-blocks is "never".

@elnaz sorry for the delay - I'll take a look at this later today and we can get it closed out.

I could go either way on padded-blocks. newline-after-var seems like a rule that is hard to lock down, and if we set it to either always or never it would fail on all our requires at the tops of files. I definitely like how we logically split up requires based on if they are external modules, or fixtures, or other logical groups.
All the other rules LGMT.

We talked IRL and decided to hold off on the two controversial rules. We'll explore writing our own plugin to enforce padding describes and its in tests for example.


Changes the text from SDN to OVN

Changes the labels for multus selections

/retitle Changes the text from SDN to OVN

/cherry-pick release-4.14

/cherry-pick release-4.14-compatibility

/lgtm

/cherrypick release-4.14

/cherrypick release-4.14-compatibility


RFC: API change: drivers: can: remove CAN_FILTER_FDF flag

Introduction
The CAN_FILTER_FDF was added in #52483 on the premise that the NXP S32 CANEXCEL driver (added in #52450) needed to know whether a CAN filter should match a classic CAN or a CAN FD frame; it could not match both.
This was opposite of all other in-tree supported CAN controllers, which are unable to filter on classic CAN/CAN FD in hardware. In order to maintain a uniform behaviour across the in-tree CAN FD capable CAN controller drivers, support for this flag was added to these by amending their hardware filtering with a software-based filter, which would discard frames not matching the presence/non-presence of the CAN_FILTER_FDF flag.
Problem description
Unfortunately, this added software-based filtering (or rather, the mix of hardware- and software-based filtering) leads to issues like the one reported in #64554.
Investigation of how this flag was used in the NXP S32 CANEXCEL IP core revealed that the premise presented in #52483 was false. The NXP S32 CANEXCEL IP core has the ability to filter on classic/FD vs. CAN XL frames, but not between classic CAN and CAN FD frames. The NXP HAL API Canexcel_Ip_SetRxIndividualMask () leads to this false conclusion (see https://github.com/zephyrproject-rtos/hal_nxp/blob/78d1912dbc2b5f6e114d7fd19a31053716a3b01d/s32/drivers/s32ze/Can_CANEXCEL/include/CanEXCEL_Ip.h#L93C48-L93C48), while in fact the implementation only distinguishes between CAN XL frames/non-XL frames (see https://github.com/zephyrproject-rtos/hal_nxp/blob/78d1912dbc2b5f6e114d7fd19a31053716a3b01d/s32/drivers/s32ze/Can_CANEXCEL/src/CanEXCEL_Ip.c#L297). This is in line with the reference manual for the CANEXCEL IP core.
Proposed change
The CAN_FILTER_FDF flag should never have been introduced. It leads to overhead, false promises of the API, and issues like those reported in #64554. I propose this flag is removed again as no known CAN controllers provide hardware support for filtering between classic CAN and CAN FD frames.
Detailed RFC
Please see #65108
Proposed change (Detailed)
Please see #65108
Dependencies
The detailed RFC currently includes the proposed changes from #65058 in order to completely remove the mix of hardware- and software-based filtering from the Bosch M_CAN driver backend.
Concerns and Unresolved Questions
None.
Alternatives
None.

@manuargue, @congnguyenhuu, @dleach02, @str4t0m, @martinjaeger, @alexanderwachter: FYI

@henrikbrixandersen Your explanations make sense and I agree to remove the software filtering based on FD flag.
The FDF bit in the CAN frame is not part of the arbitration field, but belongs to the control field. So it does not make much sense to filter based on the FDF flag either.

@manuargue, @congnguyenhuu: Any opinions on this?

@manuargue, @congnguyenhuu: Any opinions on this?

@henrikbrixandersen based on my general knowledge of CAN and the evidence presented here, it seems to me your proposal is the right move. I have no objections.

@manuargue, @congnguyenhuu: Any opinions on this?
Hello,
You are right. NXP S32 CANEXCEL not ability to set filter on classic/FD frames by Canexcel_Ip_SetRxIndividualMask(). It is only mask to filter msg ID.
But We need to configure type frame for each Rx msg to receive corresponding frames classic/FD frames with Canexcel_Ip_ConfigRx()
Need to configure CTRL.RXCTRL, configure allows only receive classic/FD frames.
For FD frame:
CANEXCEL.EXL_MSGD[instance]->MSGDSC[descNo].CTRL.RXCTRL |= CANXL_MSG_DESCRIPTORS_RXCTRL_RXFDFRM_MASK;

=>So NXP S32 CANEXCEL still need the FDF flag for Canexcel_Ip_ConfigRx

Hello, You are right. NXP S32 CANEXCEL not ability to set filter on classic/FD frames by Canexcel_Ip_SetRxIndividualMask().
But the current shim driver for CANEXCEL uses Receive Message Descriptor mode for receiving (beside that hardware also support RxFIFO mode). In that mode, there is Message Descriptor Control which configures the Receive Message Descriptor. The bit RXFDFRM in CTRL.RXCTRL register indicates whether the message descriptor is configured to receive classic or FD type frame.
* 0 for classic frame

* 1 for FD frame

It is used to filter type frame beside filter by message ID mask. =>So NXP S32 CANEXCEL still need the FDF flag for to know the type frame before sending/receiving. The type frame is configured by Canexcel_Ip_ConfigRx()

Okay. Thank you for the analysis. The driver will need to be changed to RX FIFO mode, then, in order to get rid of this flag?

Okay. Thank you for the analysis. The driver will need to be changed to RX FIFO mode, then, in order to get rid of this flag?

I need more time to analyze this mode. I'm not even sure whether it fits the expectation of CAN API Zephyr.
Your proposal will break current support CAN FD for CANEXCEL shim driver.

Okay. Thank you for the analysis. The driver will need to be changed to RX FIFO mode, then, in order to get rid of this flag?

I need more time to analyze this mode. I'm not even sure whether it fits the expectation of CAN API Zephyr. Your proposal will break current support CAN FD for CANEXCEL shim driver.

I'm quite busy right now so I can't come to a conclusion right away. I will back to this early next month.

Okay. Thank you for the analysis. The driver will need to be changed to RX FIFO mode, then, in order to get rid of this flag?

Hello @henrikbrixandersen, after investigating I see that using RxFIFO for NXP S32 CANEXCEL, it doesn't require this flag and also fits the expectation of CAN APIs.
So I will add RxFIFO support for NXP S32 CANEXCEL.
Could you please open PR for apply your proposal ? Thanks.

Hello @henrikbrixandersen, after investigating I see that using RxFIFO for NXP S32 CANEXCEL, it doesn't require this flag and also fits the expectation of CAN APIs.
So I will add RxFIFO support for NXP S32 CANEXCEL.
Could you please open PR for apply your proposal ? Thanks.

Great! You should be able to apply your CANEXCEL changes on top of #65108. We can pick and squash the relevant commits afterwards.

@congnguyenhuu Any news regarding this?

Related RFC for removing run-time RTR filtering suffering from similar issues: https://github.com/zephyrproject-rtos/zephyr/issues/67128

@congnguyenhuu Any news regarding this?

Perhaps this weekend, I will open PR for this.

@congnguyenhuu Any news regarding this?

Hello, Perhaps this weekend, I will open PR for this.

Hello @henrikbrixandersen, I opened this draft PR https://github.com/zephyrproject-rtos/zephyr/pull/67264.
Could you please help me review it.
Thanks


Inconstant List Indentation

Pull request for issue #615

Create test to replicate issue #615
Correct improper indentation handling by using current indentation to limit scan on later levels

@progmem Can you rebase or resolve the conflict in the branch?

@Stargator Should be good now!


Fix pixi link

Maybe point directly to installation? pixi.sh/latest#installation

Happy to, whatever you prefer TBH, just thought I'd merge this quickly so it doesn't further send people in the wrong direction

Maybe point directly to installation? pixi.sh/latest#installation

Happy to, whatever you prefer TBH, just thought I'd merge this quickly so it doesn't further send people in the wrong direction

Just fixed this after Bas commented above as well :)


Submenu item is visible while submenu is close

Hi,
When there is more sub menu items than main menu items under the submenu, then the last sub menu items are visible, as you can see from the screenshot.
Any idea about this?

Thanks in Advance.
fnrbh

On #48 issue there is a possible solution.


Problems with MultiPolygon GeoJSON in Internet Explorer

Hi all, I've spent several hours identifying the "long running script" issues with leaflet on Internet Explorer 10, 11 and Edge. And I've found out, that big MultiPolygons will crash Internet Explorer if the user doesn't wait until all calculations for all polygon layers are done. And this can take up to minutes.
The problem in my webapp is, that I must add GeoJSON features to the map right after initialization. It's a central use case that the user can select a single country with just one click. This will highlight the country in a different style.
All works good if I have single Polygons, but if I use MultiPolygons (e.g. for enclaves or countries which own regions spread over the world) then IE have a lot of work to do.
To fix this problem I've tried all together:

Reducing the amount of data points by using the integratet Simplify.js (http://mourner.github.io/simplify-js/) which uses the Douglas-Peucker algorithm
Using geoJsonLayer.addData instead of pushing all data at once with L.geoJSON(geoJsonFeatures)
Using async approaches with setTimeouts

Do you have any idea how I can handle this?
Currently I use this approach:
var simplifyGeometry = function(geometry) {
	var simplifyPolygon = function(polygonCoordinates) {
	  var coordinates = polygonCoordinates.map(function(point) {
		return {
		  x: point[0],
		  y: point[1]
		};
	  });

	  return L.LineUtil.simplify(coordinates, 0.1).map(function(point) {
		return [point.x, point.y]
	  });
	};

	if (geometry.type === 'Polygon') {
	  geometry.coordinates[0] = simplifyPolygon(geometry.coordinates[0]);
	} else if (geometry.type === 'MultiPolygon') {
	  geometry.coordinates.forEach(function(c, index) {
		geometry.coordinates[index][0] = simplifyPolygon(c[0]);
	  });
	}

	return geometry;
};

featureCollection.features.forEach(function (f, index) {
	if (f.geometry) {
	  featureCollection.features[index].geometry = simplifyGeometry(f.geometry);
	}
});

layer['country'] = L.geoJson(featureCollection, {
	style: function () {
	  return defaultCountryStyle
	},
	onEachFeature: function (feature, localLayer) {
	  // when clicking on a layer, we want to highlight the clicked polygon
	  localLayer.on('click', function (e) {
		if (selectedCountry.featureLayer) {
		  // unselect last highlighted country
		  selectedCountry.featureLayer.setStyle(defaultCountryStyle);
		}
		// set highlight style only for clicked country
		localLayer.setStyle(highlightCountryStyle);

		selectedCountry = {
		  code: feature.properties.ISO2,
		  featureLayer: localLayer
		};
		$rootScope.$emit('mapService:countryClicked', {code: feature.properties.ISO2});
	  });
	}
}).addTo(myMap);

I don't know if this issue is caused by applying the styling, so maybe it would be better to do that work async.

It's hard to say what may be the problem here before we see a minimal test case here, e.g. in http://playground-leaflet.rhcloud.com/ or JSFiddle. It may be related to the way MultiPolygons are implemented in Leaflet 0.7.* — can you try the same data in Leaflet 1.0 beta 2? It might improve performance significantly.

@mourner This worked perfectly. Performance is now lightning fast in Internet Explorer. Thanks for your advice using beta 2.

Awesome!


How about adding support for the Wyze Wall Switch?

The Wyze Wall switch is an extremely useful addition to there product line. The double tap and triple tap feature would be an excellent way to control non Wyze accessories via HomeBridge.

@SteveQ2 This is a duplicate of issue #13. As I stated there, I do not have and cannot install a Wyze Switch because my house is 51 years old and doesn't have the neutral wires in the switch boxes. Not having one installed locally makes it impossible to develop software for it. And the multi-tap features would not be exposed to Homebridge anyway. The detection of multi-taps is a hardware feature. Not sure how that event would be visible to the plugin. Sorry.

Hey there! Just checking in on this one. I'm only interested in the on/off of the switch and not multi taps. I believe I sent you some logs previously that would help, but I don't recall what came of it.


local source plugin can introduce non-determinism

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Jul 30, 2018, 13:30
Summary
It came to light while discussing potential new features for the new remote plugin in !581, that we might be relying on the user's umask to determine what permissions local sources will have when staged.
Steps to reproduce
What is the current bug behavior?
The result of staging local sources can depend on how the BuildStream project was stored or obtained (was it in a tarball ? was it cloned in a git repository ?), or local host configuration (what is the user's umask ?).
What is the expected correct behavior?
The result of staging local sources should always be deterministic
Relevant logs and/or screenshots
Possible fixes
Not sure what the solution for this will be, perhaps we need:

A sane default:

Fully deterministic mode bits set at stage time, accounting only for whether the local file is executable or not
This approach makes a reasonable assumption that whatever way you obtained your project, the local files inside the project directory at least retained the information of whether the file was executable or not.
This would by default, e.g. use always 0755 for executable files, and 0644 for non-executable files

Some way to control the permission bits for individual files, only for the case where the user asks for that

Other relevant information

BuildStream version affected: /milestone %BuildStream_v1.4

In GitLab by [Gitlab user @tristanvb] on Aug 1, 2018, 10:19
mentioned in merge request !581

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:37
marked this issue as related to #540

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:40
marked this issue as related to #541

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:48
marked this issue as related to #542

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:51
marked this issue as related to #543

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
marked this issue as related to #544

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:57
marked this issue as related to #545

In GitLab by [Gitlab user @toscalix] on Aug 6, 2018, 09:36
assigned to [Gitlab user @valentindavid]

In GitLab by [Gitlab user @valentindavid] on Aug 6, 2018, 10:41
marked this issue as related to #555

In GitLab by [Gitlab user @valentindavid] on Aug 6, 2018, 17:09
mentioned in commit 45900c561a8ac7b4bf10d6f619d0c91c78841c01

In GitLab by [Gitlab user @valentindavid] on Aug 7, 2018, 17:33
mentioned in commit 6fdad8891cda9a68c9b9dbf85947f20ecf0cb6f9

In GitLab by [Gitlab user @valentindavid] on Aug 7, 2018, 17:40
mentioned in merge request !616

In GitLab by [Gitlab user @valentindavid] on Aug 9, 2018, 15:18
mentioned in commit b97d03a340f373ff1d2d2b4b5bc17d5c668bb808

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 09:53
mentioned in commit 32d571e6a34c172e61e498d335bce6154357291a

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 14:50
mentioned in commit cc2434c7d4396a2400c5fd14d34f55e830caab73

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 15:21
mentioned in merge request !634

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 15:22
mentioned in commit a250b5f7501e81626e598d244573dbce428888d4

In GitLab by [Gitlab user @valentindavid] on Aug 12, 2018, 06:54
mentioned in commit ccf6e479df23c2f28ea56f237459d32086af1406

In GitLab by [Gitlab user @valentindavid] on Aug 12, 2018, 06:57
mentioned in commit b9f6b1d7f538c2c6e4b2f075c20d8f4a583e9120

In GitLab by [Gitlab user @valentindavid] on Aug 12, 2018, 07:59
closed via commit ccf6e479df23c2f28ea56f237459d32086af1406

In GitLab by [Gitlab user @tristanvb] on Aug 12, 2018, 07:59
closed via merge request !616

In GitLab by [Gitlab user @tristanvb] on Aug 12, 2018, 07:59
mentioned in commit c1fdebb3137891305bea7db8b4f1ad9f0b1e2043


Add base for dockerfile

Add docker file so this project can be compiled without having to install more stuff locally (this is done in preparation so I can verify those library updates etc)
Also:

Update npm-run-all to 4.1.5 to avoid using<EMAIL_ADDRESS>which is no longer available.
Update  node-sass to 4.12.0 so it works with newer node.
Fix Readme link to example page.

Nope there should be just one of those
ke 4. elok. 2021 klo 11.11 Heikki-Jussi Niemi @.***>
kirjoitti:

@.**** commented on this pull request.
In package.json
https://github.com/by-pinja/ng-virtual-keyboard/pull/50#discussion_r682390365
:

@@ -51,9 +51,9 @@
"codelyzer": "^2.0.1",
"core-js": "^2.4.1",
"css-loader": "^0.28.0",

"extract-text-webpack-plugin": "^2.1.0",
"node-sass": "^4.5.2",
"npm-run-all": "^4.0.2",

"extract-text-webpack-plugin": "^2.1.2",
"node-sass": "4.12.0",
"npm-run-all": "4.1.5",

Good point.
BTW, do we have a need for both, package-lock.json and yarn.lock in this
project?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/by-pinja/ng-virtual-keyboard/pull/50#discussion_r682390365,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAERM2PIZXQ44XJSIRO2YR3T3DY4LANCNFSM5BOTYX4A
.

Okay, I'll choose yarn.lock then.


0.6.3 error

Describe your bug here.
help me with this.

Command Prompt/Terminal logs (if existing)
D:\Nova pasta\FNF-PsychEngine-0.6.3>lime test windows
source/Main.hx:85: characters 61-65 : Float should be Int
source/Main.hx:85: characters 61-65 : ... For optional function argument 'updateFramerate'
source/Main.hx:85: characters 61-65 : ... For function argument 'child'
source/PlayState.hx:75: characters 8-22 : Type not found : vlc.MP4Handler
source/PlayState.hx:1620: characters 13-23 : Type not found : MP4Handler

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No.

help soon as possible, i need quick help. cuz yes

dont report bugs for older versions + research these errors have been mentioned and fixed a million times

These errors have been fixed on 0.7+, so don't report it


Missing Documentation for minecraft:dimension

There is no documentation detailing the components, modules, or any form of guidance to using the minecraft:dimension object.
Create a documentation page that details all the components, and subcomponents in order to develop dimensions.
Another option would be a tutorial that displays how to develop a custom dimension in bedrock.

Thank you for your feedback! You can find an article on the dimension type here and the minecraftdimensionstype class here. As stated in the articles, these are experimental features and at many points are in a pre-release state. Documentation will continue to improve as the features become more concrete.


Regular Expression Error

For the below regex -
t = t.replace(/((.+)to(?=the)?(.+)power/g, "0");
duktape throws "Error : SyntaxError: quantifier without proceeding atom (line 35)" error.
Although, this is supported by standard regex handlers.

For comparison this is the Node.js behavior:
> 'fooxthey'.replace(/x(?=the)?/g, "0")
'foo0they'
> 'fooxthey'.replace(/x(?=thx)?/g, "0")
'foo0they'

The root cause of the issue seems to be the quantifier ? which is preceded by an Assertion (positive lookahead) rather than an Atom. This doesn't seem to be allowed by the ES RegExp syntax, even by Annex B, so the behavior would be engine specific. (I may be misreading the syntax...)
Regarding the RegExp intent: what should the final ? in to(?=the)? quantify?


Some types of white space cut off text in feed entries

Newsboat version 2.12.0:
Steps to reproduce the issue:

Add The Intercept's RSS (https://theintercept.com/feed/?rss/) feed to .newsboat/urls and reload the feed

Open the feed entry A Guatemalan Family Faces Endless Obstacles as They Struggle to Recover a 9-Year-Old Boy From U.S. Custody

Some of the sentences are cut off abruptly with a line break An example:

[...]
with local immigration and health services. The
40 years; the
the most brutal civil wars in the Latin American history. They are legal U.S. residents, but
[...]

Other info you think is relevant:
When reading the article in Newsboat, pressing S to save it and reading it using less, the last parts of the lines are no longer missing (which is why I assume this a rendering issue, and not just The Intercept sending a garbled feed). From a hexdump of the article, the hex code of the character(s) that causes Newsboat text rendering to break is ef  bf bd  represented as .... Not sure what character that exactly is.
00000230  6c 20 69 6d 6d 69 67 72  61 74 69 6f 6e 20 61 6e  |l immigration an|
00000240  64 20 0a 68 65 61 6c 74  68 20 73 65 72 76 69 63  |d .health servic|
00000250  65 73 2e 20 54 68 65 ef  bf bd 6d 61 6e 20 68 61  |es. The...man ha|
00000260  73 20 6c 69 76 65 64 20  69 6e 20 74 68 65 20 55  |s lived in the U|
00000270  6e 69 74 65 64 20 53 74  61 74 65 73 20 66 6f 72  |nited States for|
00000280  20 6d 6f 72 65 20 74 68  61 6e 20 34 30 20 79 65  | more than 40 ye|
00000290  61 72 73 3b 20 0a 74 68  65 ef bf bd 77 6f 6d 61  |ars; .the...woma|
000002a0  6e 20 68 61 73 20 62 65  65 6e 20 68 65 72 65 20  |n has been here |

The RSS has U+00A0 NO-BREAK SPACE after the text "with local immigration and health services and "40 years; the". And ef bf bd is UTF-8 representation of U+FFFD REPLACEMENT CHARACTER. I hope this helps to solve the issue.


feat(Visibility): add updateOn prop

Refs #2318.

Codecov Report

Merging #2791 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2791      +/-   ##
==========================================
+ Coverage   99.74%   99.74%   +<.01%
==========================================
  Files         160      160
  Lines        2762     2766       +4
==========================================
+ Hits         2755     2759       +4
  Misses          7        7

Impacted Files
Coverage Δ

src/behaviors/Visibility/Visibility.js
100% <100%> (ø)
:arrow_up:

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 6a22434...d59010e. Read the comment docs.

❤


How to have fonts in a flutter package?

I am trying to create a separate widget catalog as a flutter package and am unable to get my fonts to be recognized. The flutter app builds and runs just fine but the font is still the standard material font.
My setup is as follows:
fonts are located in ./my_ui_catalog/lib/fonts/my_font.ttf
./my_ui_catalog/pubspec.yaml:
name: my_ui_catalog
description: custom ui catalog
version: 0.0.1

environment:
  sdk: ">=2.0.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  assets:
    - packages/my_ui_catalog/assets/my_logo.png
  fonts:
    - family: MyCustomFont
      fonts:
        - asset: packages/my_ui_catalog/fonts/my_font.ttf
          style: normal

./pubspec.yaml:
name: example
description: example

version: 1.0.0+1

environment:
  sdk: ">=2.0.0 <3.0.0"

dependencies:
  my_ui_catalog:
    path: ./my_ui_catalog
  flutter:
    sdk: flutter

dev_dependencies:
  flutter_driver:
    sdk: flutter
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

./lib/main.dart:
import 'package:flutter/material.dart';

import 'package:my_ui_catalog/my_ui_catalog.dart';

void main() => runApp(
   MaterialApp(
        themeData: ThemeData(fontFamily: 'MyCustomFont'),
        home: Scaffold(
          body: (
            child: Center(
              child: Text('Hello'),
            )
          )
        )
      ),
    );

The font family name will include a path to the package - in this case it would be packages/my_ui_catalog/MyCustomFont
You can see how the fonts are named in the application by looking at the FontManifest.json file that is built by the Flutter tools and embedded within the app's APK file


stream_getc: use lib_stream_eof instead of EOF

Summary
EOF is libc definition, not the stream definition, we should use errno to handle the stream getc EOF case.
As we have lots of backend to support stream, which necessary to get errno.
first find in #14778, casing scanftest break
at " %4c%n" case.
then scanf use INT_MAX cause meminstream EOF break.
Impact
sscanf will do strlen firsttime, and then meminstream.
filestream/blkstream/mtdstream will able to handle the errno.
Testing
CI-test, local sim:citest test.

[Experimental Bot, please feedback here]
This PR does not fully meet the NuttX requirements, though it's on the right track.  Here's a breakdown of what's missing and how it could be improved:
Missing/Insufficient Information:

Summary:

Why is the change necessary?  "sscanf will do strlen firsttime, and then meminstream" doesn't explain why the existing behavior is a problem.  Explain the bug or deficiency this fixes. Why is relying on libc's EOF definition incorrect? What are the negative consequences of the current implementation?
What functional part of the code is being changed? Be specific.  Which files/functions/modules are affected?  E.g., "Changes the implementation of getc within the lib/stdio directory to use errno for EOF detection."
How does the change exactly work? More detail is needed.  "use errno to handle the stream getc EOF case" is too vague.  Explain the mechanism used to set and check errno.

Impact:  While some impact is mentioned, use "YES" and "NO" explicitly and elaborate more where necessary.

Is new feature added? Is existing feature changed? State this clearly. It sounds like an existing feature is being changed (bug fix).
Impact on user:  If sscanf now behaves differently (even if it's fixing a bug), the user might need to adapt. Explain how the behavior changes and under what circumstances.
Impact on documentation: If this changes behavior, the documentation likely needs updating.  State "YES" and specify what needs to be documented.

Testing:

Build Host(s): Be specific. "CI-test" isn't sufficient. Provide details about the CI environment (OS, compiler, etc.).  Also provide details about your "local sim" setup.
Target(s): Be specific about the architecture and configuration of the simulator used.  e.g., "sim:qemu-x86_64" or "sim:nsh."
Testing logs:  Provide actual logs, both before and after the change, demonstrating the incorrect behavior and the fix.  These logs should show the problem and how the change addresses it.  "CI-test" is not a log.

Example of an Improved PR Description:
## Summary

The current implementation of `getc` for memory streams (`meminstream`) in `lib/stdio` incorrectly relies on the libc definition of EOF, which can lead to unexpected behavior, particularly with `sscanf`.  This was highlighted by a bug (#14778) where `sscanf` with the format string `" %4c%n"` failed and by incorrect EOF handling when `INT_MAX` is encountered. This change modifies `getc` to correctly use `errno` to signal end-of-file conditions for memory streams, ensuring consistent behavior across different stream types and resolving the aforementioned issues.

## Impact

* Is new feature added? NO
* Is existing feature changed? YES.  This changes the behavior of `getc` for memory streams and consequently affects functions like `sscanf` that use it.
* Impact on user: YES.  Code that relies on the previous, incorrect EOF behavior of `meminstream` with `getc` might need to be adjusted. This primarily affects cases where `INT_MAX` was encountered in the stream, or formats like `" %4c%n"` in `sscanf`.
* Impact on build: NO
* Impact on hardware: NO
* Impact on documentation: YES.  The documentation for `getc` and `meminstream` should be updated to reflect the corrected EOF handling using `errno`.
* Impact on security: NO
* Impact on compatibility: YES. This change fixes a bug and improves consistency. While it's a positive change, it could theoretically affect code that inadvertently relied on the previous incorrect behavior.
* Anything else to consider? No.

## Testing

I confirm that changes are verified on local setup and works as intended:
* Build Host(s): Linux (Ubuntu 20.04), x86_64, GCC 9.4.0
* Target(s): sim:qemu-x86_64 (nsh configuration)

Testing logs before change:

nsh> help scanftest
scanftest
scanftest 1234 5678 "abcd efgh"
sscanf: abcd 5678 1234
(incorrect output - should be 1234 5678 abcd)

Testing logs after change:

nsh> help scanftest
scanftest
scanftest 1234 5678 "abcd efgh"
sscanf: 1234 5678 abcd
(correct output)

*(Include more relevant test cases, demonstrating the `INT_MAX` issue and the fix)*


Auth0 in Laravel not working

Hello everyone,
I followed this guide: https://auth0.com/docs/quickstart/webapp/laravel/01-login
But Auth::user() returns null all the time. Why is that so?

Hi @LozziStyle 👋 Hard to say, we'd need a lot more information. Does the application in this repository work for you?

We managed to solve this issue by updating auth0-sdk with composer update... 😅
For anyone having the same issue. This issue is resolved.


fix the include section in the c3-e2e-dependabot yml indentation

The indentation of the include field in the c3-e2e-dependabot yml is wrong, making the workflow not take effect:
https://github.com/cloudflare/workers-sdk/actions/runs/7207803909/workflow#L79
(sorry it's my bad, I missed this in https://github.com/cloudflare/workers-sdk/pull/4576 😓 🙇 )

Oops. I missed it in the review too!


Download required version of kustomize to bin/kustomize/

What does this PR do?
Make the _kustomize rule download kustomize to .kustomize/kustomize, and use this version of kustomize for all Makefile-related calls. This is required since different versions of kustomize output differently formatted yaml templates, resulting in spurious changes to files in deploy/.
What issues does this PR fix or reference?
Is it tested? How?
Tested three cases:

Nothing in .kustomize or folder does not exist -> download kustomize v4.0.5 there
Wrong version kustomize in .kustomize/kustomize -> delete current and redownload
Kustomize present and correct version -> do nothing

cc: @benoitf Could you also test these changes to make sure it works as expect on macOS?

Fixed an issue where cached kustomize isn't used in generate_deployment.sh, and moved binaries into bin/ instead of separate folders.

/test v5-devworkspaces-operator-e2e

/test v5-devworkspaces-operator-e2e

/retest

/retest


ERROR - Could not create detector pytorch/pytorch: No module named 'IPython'

Tried Doods2 by running,
docker run -it -p 8080:8080 snowzach/doods2:latest
The container successfully ran but out of the 3 models, only 'default' and 'tensorflow' shows in the dropdown on the http://localhost:8080/. The pytorch(Yolo5s) is missing. The following error is seen in the logs:

ERROR - Could not create detector pytorch/pytorch: No module named 'IPython'

What hardware are you running on?

AMD.

And just the default config file?

Yes.

Ughhhh... The yolo guys changed something again.... It downloads their model from the torch hub and if they change something it breaks... I'll see if I can fix...

Issue #56 and #63 and this one(#60) are basically reporting the same error. Seems to be an issue with the latest docker image.

Ughhhh... The yolo guys changed something again.... It downloads their model from the torch hub and if they change something it breaks... I'll see if I can fix...

Ok. Thanks for checking.

Repull your image and try it now..

The Pytorch detector is now available and working under the Web Interface ... and might I add it gives the most accurate results of the 3. Thank you.

Great!


Minor UI improvements

Trilling to be applied if, the title is long use tooltip to show full title.
Some components are taking time for making request, check for improvements or add a loader eg create new private url comp.
On mobile view Login and Register button is not aligned well, fix it.
Add name input for register comp

Tasks Completed


build<EMAIL_ADDRESS>[dev]

Publish version 4.4.1 [dev].

coverage: 100.0%. remained the same when pulling 08b067c93c192707ceb41edd7c5a8b40cb268b69 on v4.4.1 into 682db4f4696976609160724049a45e2c2b4735a3 on dev.


Openvpn startup problem

I'm able to run an openvpn client from my Debian wheezy chroot, but starting it generally requires two or more attempts.  When it fails, its log ends with:

Sat Sep 21 17:32:18 2013 TUN/TAP device tun0 opened
Sat Sep 21 17:32:18 2013 TUN/TAP TX queue length set to 100
Sat Sep 21 17:32:18 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sat Sep 21 17:32:18 2013 /sbin/ifconfig tun0 <IP_ADDRESS> pointopoint <IP_ADDRESS> mtu 1500
SIOCSIFADDR: No such device
tun0: ERROR while getting interface flags: No such device
SIOCSIFDSTADDR: No such device
tun0: ERROR while getting interface flags: No such device
SIOCSIFMTU: No such device
Sat Sep 21 17:32:18 2013 Linux ifconfig failed: external program exited with error status: 1
Sat Sep 21 17:32:18 2013 Exiting

When successful:

Sat Sep 21 17:33:46 2013 TUN/TAP device tun0 opened
Sat Sep 21 17:33:46 2013 TUN/TAP TX queue length set to 100
Sat Sep 21 17:33:46 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sat Sep 21 17:33:46 2013 /sbin/ifconfig tun0 <IP_ADDRESS> pointopoint <IP_ADDRESS> mtu 1500
Sat Sep 21 17:33:46 2013 /sbin/route add -net <IP_ADDRESS> netmask <IP_ADDRESS> gw <IP_ADDRESS>
Sat Sep 21 17:33:46 2013 /sbin/route add -net <IP_ADDRESS> netmask <IP_ADDRESS> gw <IP_ADDRESS>
Sat Sep 21 17:33:46 2013 GID set to nogroup
Sat Sep 21 17:33:46 2013 UID set to nobody
Sat Sep 21 17:33:46 2013 Initialization Sequence Completed

Once up it works fine.  If killed, it will re-start on the first try.  It looks like a problem creating and/or accessing the tun0 device.  Suggestions?

"all it does during execution is try to create a new tunnel instead of using the existing one". same here. any help?

I've been having the same problem. the openvpn --mktun --dev tun0 seems to work sometimes but honestly I'm not sure if it works at all because other times I try that I still get the same errors everyone else has been getting with the 'no such device' stuff. But what has been working for me recently is to power off my chromebook completely and then power back up and then run the openvpn commands again.

using the --mktun ends me at
resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory

If you are getting the issue where OpenVPN tries to create another tunnel when using:
openvpn --mktun --dev tun0

Changing the OpenVPN config file from dev tun to dev tun0 should cause it to use the one you created.
I've personally been using the following because I had some issues rerunning OpenVPN but it might not be necessary.
openvpn --rmtun --dev tun0
openvpn --mktun --dev tun0
openvpn --config /path/to/config

Following Flamewires' suggestions has worked very well for me so far with an Ubuntu 14.04 chroot on a Toshiba Chromebook 2

In case of problem of stability of the tun0 interface you can have a look [[Using-Cisco-AnyConnect-VPN-with-openconnect#solution-to-make-the-tun0-interface-stable-and-the-openvpn-command-reliable][here]]

Thankyou thankyou @pippo0312!
sudo stop shill
sudo start shill BLACKLISTED_DEVICES=tun0
did the trick for me!


Dependency Update - fork-ts-checker-webpack-plugin version 9

Description
We are a major version behind on fork-ts-checker-webpack-plugin.
Since it is a major version upgrade, there may be some breaking changes. Read over the release notes and be sure to test everything out to make sure there haven't been any regressions .
fork-ts-checker-webpack-plugin      ^8.0.0  →    ^9.0.0

Contribution Guide
Please first request that this issue will be assigned to you and begin work once the issue has been assigned to you.
🎃 Happy Hacktoberfest!
If this is your first time contributing to UI Kit, please review the How to Contribute guide beforehand.

Hi, @nataliepina can you assign this issue to me please !!!

I've assigned it over to you, thanks!


[oceanBase] add metrics for oceanbase cdc connector

add metrics for oceanbase cdc connector #986

@LXin96 Could you rebase the master brach?

Thanks @LXin96 for the great work! Before this PR could be merged, could you please rebase it with latest master branch? com.ververica.cdc.connectors have been renamed to org.apache.flink.cdc.connectors.
cc @whhe


PDF of this doc?

[Enter feedback here]
Would it be possible, please, to provide this document as a printable PDF, like the Q# Quick Reference Guide.
Thank you.

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

ID: 6b9fcca6-76bd-468b-c388-952832e4b5e3
Version Independent ID: dd1ca9b0-6388-bf2e-ad0d-75e80d30390a
Content: Q# Style Guide - Azure Quantum
Content Source: articles/contributing-style-guide.md
Service: azure-quantum
Sub-service: qdk
GitHub Login: @cgranade
Microsoft Alias: chgranad

Hi @TonyHoldroyd !
Which Q# Quick Reference Guide do you mean? I don't think it would be possible, the documentation is constantly improving and updating, so a PDF could become obsolete.

Ciao Sonia,
This is the one:
https://github.com/microsoft/QuantumKatas/blob/main/quickref/qsharp-quick-reference.pdf
Surely a PDF of a style guide would not become obsolete except in the very long term. it would be very handy to have a paper copy of the style guide to hand whilst coding.

I think maybe @tcNickolas can answer your question, she has created most of the Quantum Katas content. Mariia, what do you think about Tony's suggestion?

@SoniaLopezBravo @TonyHoldroyd: I wrote and maintain the Q# style guide, happy to help here. At the moment, we don't have a quick reference version of the style guide available as a PDF, but the style guide content is included in the PDF automatically generated from the full docs, currently starting at page 529.

Thank you Sonia, thank you Chris, it''s really handy to know about the pdf - there are other very useful sections I'll be printing out as well as the important style guide. I'm more than a bit old (fashioned) and for some things you just can't beat seeing them on paper.


PDF not working

Prerequisites

[X] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[ ] Checked that your issue isn't already filed.
[X] Checked if no PR was submitted that fixes this problem.

Versions

PHP version: 7.0
Laravel version: 5.6
Package version: 2.1.0
dompdf/dompdf: ~0.6.1,
mpdf/mpdf: ~5.7.3,
tecnick.com/tcpdf: ~6.0.0,

Description
PDF export is not working giving ERR: invalid
Steps to Reproduce
Tried Both functions:

return Excel::create('investments-report', function($excel) use ($arr) {
$excel->sheet('mySheet', function($sheet) use ($arr)
{
$sheet->fromArray($arr, null, 'A1', false, false);
});
})->export('pdf');

return Excel::create('investments-report', function($excel) use ($arr) {
$excel->sheet('mySheet', function($sheet) use ($arr)
{
$sheet->fromArray($arr, null, 'A1', false, false);
});
})->download('pdf');

Expected behavior:
It should be export to pdf
Actual behavior:

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Version 2.1 is no longer officially supported. Please use stackoverflow or laracasts forum.


Sprint 22 Review

This Release includes the event archive pages, transition from jshint to eslint, static content update, and a whole lot of code cleanup.
Additions

Added individual archived events pages
Added eslint settings file

Removals
None
Changes

Updated archived events landing page to display events, filters and pagination
Updated the Gruntfile for eslint over jshint
Updated form macro layout to account for optional content
Updated macro arguments for clearer conditions
Updated static content
General code cleanup

Testing
Navigate to:

/events/archive
/events/archive/
/the-bureau
/budget
/doing-business-with-us

Review

@sebworks
@anselmbradford
@duelj
@ajbush
@jameshupp

Preview

Notes

URLs from the blog landing page are still pointing at events, these will need to be fixed before beta goes live
Browser testing is a larger project and will become part of Sprint 23

Done w/ review.

:+1: as well from me

:100:


Add FD_READ and FD_SEEK to dir handles

This commit adds FD_READ and FD_SEEK rights to dir handles. This way
we allow the user to open a directory with those rights (perhaps by mistake)
but we throw EISDIR when the user attemps to call fd_read or fd_pread
on the obtained handle. This matches the expected behaviour one would expect
in POSIX and related.
Closes #1935

@sunfishcode I've gone ahead and also permitted FD_SEEK on dir handles so that we can throw EISDIR in fd_pread calls as well. Could you have a look and lemme know what you reckon? In particular, do you think this is reasonable or should we leave FD_SEEK out of the picture, and only remap errnos in fd_read calls leaving fd_pread untouched?

Hmm, now that I think about it, should we also give FD_TELL right to dir handles and let fd_seek and fd_tell fail with an appropriate error message (I believe this should be equivalent to EBADF in POSIX)?

After many offline discussions with @sunfishcode, we've agreed this is not the best approach so closing for now.


Allow concepts to have default input types

#3
Need to add some sort of database model for this

Estimate: 2 weeks


win: make uv__get_osfhandle public

The uv__get_osfhandle function is a private functio of the Windows
subsystem, and its used to get a Windows HANDLE out of a file descriptor
number.
The motivation behind making this function public is to allow Node.js
programs to pass file descriptors created using fs.open() to native
Node.js C++ add-ons, and be able to successfully convert them to Windows
HANDLEs.
This commit implements uv_get_osfhandle() in both src/win/handle.c
and src/unix/fs.c, and returns uv_os_fd_t, which is typedef'd to
HANDLE on Windows, and to int otherwise. If called on UNIX based
operating systems, the function will simply return back the file
descriptor number.
The function is then made public on include/uv.h.
This work is based on https://github.com/libuv/libuv/pull/1166
Fixes: https://github.com/libuv/libuv/issues/1291
See: https://github.com/nodejs/node/issues/6369
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

Also please double check uv_os_fd_t is what we want here.
@vtjnash can you please review this?

This is valid, but specifically doesn't fix #1291 (in particular, the comment about 'static inline' at https://github.com/libuv/libuv/pull/1323/files#diff-56343bd7ad8bf449c2693082fb3e4081R447 is the exact opposite of the functionality needed by that issue).
I would recommend dropping most of these changes and adding a simple wrapper function somewhere in the src/win/handle.c file:
uv_os_fd_t uv_get_osfhandle(int fd) {
  return uv__get_osfhandle(fd);
}

and then just add the corresponding prototype to the uv.h header:
UV_EXTERN uv_os_fd_t uv_get_osfhandle(int fd);

@vtjnash Sounds good to me! I'll update the PR in a minute. Just a couple of questions:

Should I still preserve the pre-processor conditional that makes uv_get_osfhandle simply return back fd on unix? Given uv_get_osfhandle lives inside src/win, should I  create its unix counterpart instead?

Should we prefix the public function with fs? E.g: uv_fs_get_osfhandle?

Updated!

This looks correct to me. I can't comment on the naming or formatting of APIs though.

Any chance of getting this in an upcoming release? Using windows specific file apis are tricky without this.

I'll try to add a test for this.

I added a test case that opens a file, writes a test buffer to it, uses uv_get_osfhandle to get a uv_os_fd_t, and then uses the uv_os_fd_t to read back from the file (ensuring that its really valid), and compare the result with the initial buffer.
I wrote the case on macOS, but I'll give it a go on Windows in a minute.

@jviotti I think you might need to rebase this :)

Thanks for the heads up @addaleax. The conflicts are now resolved.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/281/

Landed in e133923e935acc3a0b6371372c4ec56f797c8cae. Thanks!

Thanks for this fix, works well.


feat (guide): added java implementation for red-black trees

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Hi Quincy,
Thank you so much! Will be contributing more in the future
On Fri, Jul 19, 2019, 11:23 PM Quincy Larson<EMAIL_ADDRESS>wrote:

Merged #36026 https://github.com/freeCodeCamp/freeCodeCamp/pull/36026
into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/pull/36026?email_source=notifications&email_token=AE6MEUCGWXTAT443U3NZQLTQAIWFHA5CNFSM4HMICIR2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSTKYWKI#event-2497022761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6MEUEUVHGBGVSQ326SDADQAIWFHANCNFSM4HMICIRQ
.


Threebot improvements & features unplanned

Features

[ ] Interactive playground actors threefoldtech/jumpscaleX_threebot#288
[ ] Registry package threefoldtech/jumpscaleX_threebot#229
[ ] Improve wiki loading time threefoldtech/jumpscaleX_threebot#209
[ ] calendar package threefoldtech/jumpscaleX_threebot#37

moved to the right repo


IntegrationError: You must pass in a clientSecret when calling stripe.confirmPayment()

Using the example that was provided, I received the following error upon checkout.
IntegrationError: You must pass in a clientSecret when calling stripe.confirmPayment().

I logged the result of my client secret, and it logged successfully. I even tried hard-coding in the client secret value, and I still get the error.
Refer to the example in the README for the code. The versions that I'm using:
"@stripe/stripe-js": "^4.9.0",
"solid-js": "^1.9.3",
"solid-stripe": "^0.7.0",
"stripe": "^17.3.1",

thanks for reporting, Ill take a look asap

Thanks! I tried implementing elements using plain JS/HTML and it worked fine. Also for more information, I'm using Astro for SSR and astro islands. Not sure if that has any effect on this.

Update: I think this may be an issue on my end on how I setup my backend logic. I believe I'm passing in the wrong type of secret. I will try to get it working with this in mind. I will also update here if it fails.

Feel free to reopen!


Upgrade to core 0.95.6

Still need to update the performance baselines (to be faster, hopefully...).

Fixes #2984.

:+1: we can merge this now as long as we create a new GH issue to track updating the performance baselines.

AFAIK we no longer need to update the performance baselines for this. :+1:


Feature/update docs flags and mac

Updates docs to include information for using dockstore CLI with mac and how to use extra cwltool flags.

[x] Check that you pass the basic compilation and unit tests by running grunt

Coverage remained the same at 8.637% when pulling f892debd9cb7f8c4d93b0340d2ce3c05cdb56e83 on feature/update_docs_flags_and_mac into 7c27b45acb24cdaee65cddbcd388f37b9a409109 on develop.


Batch processing

Summary
This pull request introduces a new feature to the pdf-slides-utils that enables the script to automatically process all PDF files in the current directory. This enhancement eliminates the need to manually specify each file, significantly streamlining the workflow for users dealing with multiple PDFs.
Changes Made

Modified pdfdeanimate-image.py to iterate over all .pdf files in the current directory.
Incorporated a function process_pdf(pdffile) which encapsulates the existing logic for processing a single PDF file.
The script now applies this logic to each PDF found, automating the process of converting and reducing pages.

Impact

Users can now process multiple PDF files in one go, without the need to run the script separately for each file.
This feature is particularly useful for batch processing scenarios, where users have a collection of PDF files that require uniform processing.
It simplifies the user experience and enhances the utility of the script.

Testing
The updated script has been tested with various PDF files to ensure reliability and consistent performance. All tests indicate that the script processes each file in the directory as expected, maintaining its functionality and efficiency.
Looking forward to your feedback and any further suggestions for improvement!

Hi, thanks for the pull request! I'm sorry, I must've missed it.
Would you mind removing the .idea directory from the commit and making it compatible with the changes in #3?

I think it would also be good if this were a command line option rather than the default behaviour.

could default shell expansion be sufficient already?

To run the script, you can use the following commands:

To process specific PDF files:
python pdfdeanimate-image.py file1.pdf file2.pdf

To process all PDF files in the current directory:
python pdfdeanimate-image.py

To use shell expansion and process multiple PDF files:
python script.py *.pdf

Thanks for the review. I now changed it.


Add missing comments to olm makefile rules

This adds the missing comments to olm rules.

/cc @msherif1234

LGTM


feat: support multiple scopes

Without this change, I get the invalid_scope error when I request multiple scopes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for contribution. It was already fixed in v0.0.7.


Chlorine version

Hi!
Just trying to get your attention in order to collaborate!
Hence the PR
Have you done anything further with your branch?
I'm about to start this up during the summer in order to get a working RaspiPool with I2C and chlorine injection.
Waiting for my parts to arrive so far

Hi @ptomasroos! sorry for the delay, but somehow I missed your PR (I do get a lot of mail each day..).
I did add an extra sensor to monitor the inside temperature of my filter (Filtrinov MX18) but nothing shocking yet.
Ezo-pumps require a bit more work for which I still have to find the time.

All right! Thanks for the feedback! Good to know! Looking forward helping out when I've got the stuff up and running :)


Redis cache storing wrong tenant name?

Bug description
I have two tenants with Id: first and second. And my cache driver is set to Redis.
In my controller I am adding a value to cache like so:
Cache::put("name", tenant()->id);
To retrieve this data:
Cache::get("name");
This works fine and displays the correct names for both tenants.
But when I try to fetch the keys of the cache, the Redis CLI gives me these keys:
myapp_cache:2deec9455c60ae3b6bdd13e5228ed6fbed455a2d:name
myapp_cache:eae589c9ff5e298a44422d7d0c7bdcd3f307e9e5:name

The documentations says that the Tenant ID is added to the cache key, but here I see random generated string "2deec9455c60ae3b6bdd13e5228ed6fbed455a2d" and "eae589c9ff5e298a44422d7d0c7bdcd3f307e9e5"
What are these strings?
I wouldn't care about this as it was working fine, but for some reason, on my Central DB connection, I need to retrieve some data that is stored in the Cache of each tenant.
So I am not able to do this:
Cache::get(config('tenancy.cache.tag_base') . $tenant->id . ':name');
But when I do
Cache::get('eae589c9ff5e298a44422d7d0c7bdcd3f307e9e5:name') I get the data.
How is that random string generated?
Steps to reproduce
Cache::put("name", tenant()->id);
In Redis CLI: keys *
Output:
myapp_cache:2deec9455c60ae3b6bdd13e5228ed6fbed455a2d:name
myapp_cache:eae589c9ff5e298a44422d7d0c7bdcd3f307e9e5:name

Expected behavior
The expected output for Cache Keys:
myapp_cache:tenantfirst:name
myapp_cache:tenantsecond:name

Laravel version
6.0
stancl/tenancy version
3.5

To access the tenant's cache on the Centeral Route, I did this:
foreach ($tenants as $tenant) {
tenancy()->initialize($tenant->id);
$cacheData = Cache::get('name');
dd($cacheData);
}
This works fine, but I am still confused what are those random strings on the Redis cache key 😕

iirc those are the tags on the key. Not the key itself. We don't change the key


Can't see "Quest available" particles.

What is your Quests version / build number (do not say "latest")?
3.7.2
Describe the problem and how to replicate it. Any console errors to post using Pastebin.com?
I can't see the Particles above a NPC when a quests is available. I turned the feature on in the config file of the Quests folder but I still can't see them.
I have Particles turned on "All" but still can't see the Particle I set up.

Thanks for the report. What is your MC server version?
Sent with GitHawk

Thanks for the report. What is your MC server version?
Sent with GitHawk

Spigot 1.12.2

I'm having trouble creating any fault on my test server. Could you please provide the quest from quests.yml that you're using (via Pastebin or Hastebin)?

Closing due to lack of response from OP.


Fix typo on data types overview page

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c5242885d9796f559a631785d48a6ab5f9e9550f/


Add optional indicator

I think this is fine for now.  We may be able to make these a bit more aesthetically pleasing though.


Create Builder API for Connect

Connect
stomp::client()
  .with(HeartBeat(0,0))
  .with(LoginCredentials("myUserName", "myPassword"))
  .with(header!("client-id", "my-jms-client-id"))
  .connect(("<IP_ADDRESS>", 61613));

Added in v0.6.0.


While running my first docker command i get the following error:

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/microservice-tutorial/install-docker
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

myMicroservice>docker ps
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/containers/json: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Can you verify that you've checked these two things?

Closing out, please reopen if you can provide more detail.


Add Export to CSV button on Connect Analytics cards

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
The focus of this PR is to refactor components and improve data visualization in the PayAnalytics section of the dashboard.
Detailed summary

Moved ExportToCSVButton to a shared location for reuse.
Added valueFormatter prop to ChartTooltipContent.
Enhanced chart components with better data handling and styling.
Improved button styling and functionality for exporting CSV data.

The following files were skipped due to too many changes: apps/dashboard/src/app/team/[team_slug]/[project_slug]/connect/analytics/_components/WalletDistributionChartCard.tsx

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4617  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite

ah my bad - forgot to do gt submit

pushed now


Allow snippets to include user input, prompted when the abbreviation is triggered

Rationale
So, snippets with multi-cursors or similar functionality seems to be tricky to do without adding a lot of complex code (at least from what i can tell?), so instead a simpler way is to trigger the abbreviation, leave input placeholders, and then prompt the user for what to replace the placeholders with. This sounds (and kind of is) a bit hacky, but seems to work smoothly enough, and can be refined further (suggestions at the end).
Example implementation
First, a SnipInput() function:
function! SnipInput()
    let s:placeholder = localtime() . localtime()
    return s:placeholder
endfunction

The placeholder needs to be a large and random enough string such that when it is replaced at the end, there's a near-zero chance of colliding with anything else in the buffer. An example (as shown above) is the current time in ms (repeated twice just in case).
Next, the prompt function:
function! SnipPrompt(prompt)
    let str = input(a:prompt)
    execute ":%s?" . s:placeholder . "?" . str . "?g"
    return ""
endfunction

Here we make use of :h input() and then execute a global substitute, replacing the placeholder with the input string and returning an empty string so nothing else is added to the abbreviation.
The abbreviation itself would look like:
inoreabbrev test
    \ \begin{<C-R>=SnipInput()<CR>}<CR>
    \ <CR>
    \ \end{<C-R>=SnipInput()<CR>}<CR>
    \ <C-R>=SnipPrompt("Environment: ")<CR>

Or in snip syntax:
snip test {
\begin{<C-R>=SnipInput()<CR>}<CR>
<CR>
\end{<C-R>=SnipInput()<CR>}<CR>
<C-R>=SnipPrompt("Environment: ")<CR>
}

UX improvements
Obviously, the input/prompt parts are quite unreadable. Since the input part is always constant, it would be easy to add a special keyword (for example, <INPUT>) which can be used in the snip file, and then later when the snippets are being registered it can be replaced with the actual expression. Something similar could be done with SnipPrompt, but it needs to be decided how to handle the prompt string. Maybe something like <PROMPT:Environment>? Spaces and nested colons might be tricky to handle depending on how this is parsed. Regardless, with these changes the syntax would look like:
snip test {
\begin{<INPUT>}<CR>
<CR>
\end{<INPUT>}<CR>
<PROMPT:Environment>
}

This is obviously much cleaner and readable (even more so with syntax highlighting, which isn't available here on GH 🙁).

Note: since SnipPrompt() is placed at the end, the abbreviations seems to end once the function has been called (but not necessarily returned, since input() blocks the thread). This means the trailing characters that triggers the expansion is automatically inserted at the prompt. This can be dealt with by the user simply pressing backspace, but is obviously pretty inconvenient as well. I am not sure if Eat() will work here, I haven't tried yet.

I guess I could just trim the whitespace from the input before running the substitution.


Enhance Python section

Useful pages

Supported Python versions
Using alternatives to pick the default python/python3 binary
Using virtualenvs to install packages
How to build native packages (install python3-devel, development tools, etc)
Pages on important packages to install via pip: pandas, etc
Options for connecting to Db2
Options for calling XMLSERVICE

FYI, I added a Python page a while ago that covers some, but not all of Kevin's suggestions.
We should keep this issue open to track the filling of those gaps. Renamed accordingly.
@abmusse , is this still something you'd like to own?

Yes I can own this one and work on implementing Kevin's suggestions

Is there any style guide or even informal conventions? I have proofreader-level nitpickiness and occasionally have an urge to clean things up.
Example: I notice that there are several small headings (such as "Important Note") styled using boldface. In the source they are on a separate line, suggesting that the intention was for them to render on a separate line. But of course they don't, so it looks kind of kludgy. If indeed they're meant to be on a separate line, I can think of a few possibilities, not limited to

Just add another newline after the heading.
Add a <p> after the heading.
Use level-4 heading (####) instead of bold.

All these render the same in my browser, including a good deal of space between the heading and the text that follows. If that's too much separation, then my suggestion would be to keep the "heading" on the same line as the text, but set off with a colon.
So, either

Important Note
Performing a yum upgrade operation...

or

Important Note: Performing a yum upgrade operation...

or maybe even

Important Note: Performing a yum upgrade operation...

What do people think?
(There are also a lot of smaller changes I would make, mostly for consistency.)

I think this looks the best: Important Note: Performing a yum upgrade operation...

Alternatively, one could escape out to ReStructured Text and make an actual information box like the Note here: https://python-itoolkit.readthedocs.io/en/latest/api.html#itoolkit.transport.DirectTransport.close
` ` `eval_rst
.. note::
   Performing a yum upgrade operation ...
` ` `

Though that's probably overkill for this.

We should also something for when users get a mismatch between SSH and QSH/QP2TERM.

If OPS is still installed, they'll get Python 3.4 which usually gives an error that it can't find its dependencies since they were installed in a different Python version or gives a syntax error since they're running Python 3.6+ code on Python 3.4 (f-strings, etc)
If OPS is not installed, then they'll just get a command not found error.

Either way, the answer is to set the PATH, but the symptoms -- and thus searching to find the answer -- are different.

We should probably document how to use GCC 10 on IBM i 7.4 and up, since GCC 6 has header file compatibility issues.

Sorry for being kind of off-topic, but how the heck do you satisfy the DCO check from the GitHub web interface? Is it even possible? Is there some place I can set all my commits done completely online to automatically include the signed-off-by line?

Thanks for the response, @abmusse - for now I am OK with just manually entering the signed-off-by line. I finally was able to pass the DCO check by using my user name (I had been trying my real name!) in the extended commit description.

Sorry for being kind of off-topic, but how the heck do you satisfy the DCO check from the GitHub web interface? Is it even possible? Is there some place I can set all my commits done completely online to automatically include the signed-off-by line?

 Looking at the commit in your last failed PR: https://github.com/IBM/ibmi-oss-docs/commit/58d36e919d517234bfc4d38148a463ba4fe11b37.patch
From: jkyeung<EMAIL_ADDRESS>...
Signed-off-by: John Yeung<EMAIL_ADDRESS>
These two lines should match. Now that you have done that, your current PR is good.


README: tweaks

Path WB is now CAM
Added markdown 'Alert' syntax to emphasize the Warning (as stated in the docs^1)
misc. tweaks

Preview: https://github.com/luzpaz/better-tool-library/blob/README-tweaks/README.md

Great changes, Thank you!


Error: Failed to get timestamp from a NITROS message

Hello,
I am encountering an error with " Isaac ROS Pose Estimation". When I launch the node and replay the provided example bag, I continuously receive the following error message:
[dope_decoder]: [NitrosPublisherSubscriberBase] Failed to get timestamp from a NITROS message (eid=10479)
[dope_decoder]: [NitrosPublisherSubscriberBase] Failed to get timestamp from a NITROS message (eid=10504)
…
The “/poses” topic does not contain any poses of the ketchup bottle and looks like that:
header:
stamp:
sec: 0
nanosec: 0
frame_id: camera
poses:
The isaac_ros_dope node starts without any errors and when I run the tests with “colcon test --executor sequential” I do not receive any errors as well.
I have followed the instructions provided in the GitHub README.md and I am using the Isaac ROS Dev Docker images. Until replaying the bag everything looks fine.
Some information about my system:
OS: Ubuntu 22.04
GPU: NVIDIA GeForce RTX 3070 Laptop GPU
Driver version: 525.85.05
CUDA version: 12.0
Docker version: 23.0.1
Nvidia-container-toolkit is installed.
I would appreciate any guidance on resolving this error or suggestions on what I may have missed during the setup process.
Thank you for your help.
Lukas

Solved with: https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_pose_estimation/issues/13#issuecomment-1432214979


Python Wrapper: Stream data directly to http connection

Support upload of data using streams

This cannot be closed by a bot.


Ask "Open in new window or current window" when user is opening a folder in VS Code and trying open anọther folder

I want a feature: When I am opening a folder in VS Code and  trying open anọther folder, VS Code will ask me open in current window or open in another windows. Users can setting to always open in current window or open in another window.
Thanks a lot.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add instructions to install hstr on Gentoo.

Hi Martin
We've packaged hstr for Gentoo! :+1:
This PR changes the INSTALLATION instructions and explains how to get hstr running on Gentoo.
Enjoy!

This is a great news - thank you Patrice!


stdout maxBuffer exceeded

electron-packager ./ 'myapp1' --platform=darwin --arch=x64

Packaging app for platform darwin x64 using electron v1.6.11

then

stdout maxBuffer exceeded...

any issues solve this?

Thanks for filing an issue! In order to help you with your problem, we're going to need more information about it. In particular:

Console output when you run electron-packager with the environment variable DEBUG=electron-packager. Please include the stack trace if one exists.

Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
problem. Using electron-quick-start is a good starting point.

Since the original issue reporter has not responded to the request for additional information in about two weeks, I'm going to assume that they either found the answer in another manner or decided not to pursue this issue. If I'm incorrect, they can respond with answers to the questions posed, and I'll reopen.

Hey folks I just ran into this as well and it's making it difficult for me to diagnose the underlying issue. It seems that when you call child_process.exec there's an implicit limit to the amount of output that the exec'd process can emit - by default 200kb (https://stackoverflow.com/questions/23429499/stdout-buffer-issue-using-node-child-process).
This happened after I enabled verbose logging on a bunch of stuff by setting DEBUG=electron-download,electron-packager,extract-zip. I think electron-download is taking a long time and emitting more than 200kb of ....?

What are the implications of increasing the limit? Does it increase the amount of memory Packager allocates? (I don't have time to look into it right now and would appreciate it if someone else could.)

Reported again in https://github.com/electron-userland/electron-packager/issues/734.

Reopening since there's a potential solution in #734.

From #734:
Non-code workaround:

export NPM_CONFIG_LOGLEVEL=info before calling electron-packager. This reduces the output of npm commands significantly.

A better code-based workaround / provisional fix:

The one proposed in a PR that was recently rejected: https://github.com/electron-userland/electron-packager/pull/614

Proper fix:

spawn should be used for executing any commands. Otherwise, if the output is too long, packaging will always be prone to an error like stdout maxBuffer exceeded or stderr maxBuffer exceeded.

I'm actually considering replacing this code entirely so that Packager doesn't call any package managers to prune, so this is not very high on my list of things to fix.


What is the model size of Palette?

What is the model size (number of parameters) of Palette?

You can count it by https://github.com/Janspiry/Palette-Image-to-Image-Diffusion-Models/blob/136b29f58d0af6e5db9f3655d2891f5a855fcdaa/core/base_model.py#L90


Expose nonce to transactions and deployment

What I did

changed transfer, deploy and transact functionality to expose the nonce parameter
minor clarification in error messages
added test cases for manual nonce

doc update is coming!
Related issue: #484
How I did it
Added nonce as kwarg or dict element when creating a transaction. E.g.:
accounts[0].transfer(accounts[1], nonce=5)
tester.doNothing({"from": accounts[0], "nonce": 5})
How to verify it
run tests
Checklist

[x] I have confirmed that my PR passes all linting checks
[x] I have included test cases
[x] I have updated the documentation
[x] I have added an entry to the changelog

Codecov Report

Merging #485 into master will decrease coverage by 38.53%.
The diff coverage is 66.66%.

@@             Coverage Diff             @@
##           master     #485       +/-   ##
===========================================
- Coverage   88.23%   49.69%   -38.54%
===========================================
  Files          56       56
  Lines        6077     6087       +10
  Branches     1337     1338        +1
===========================================
- Hits         5362     3025     -2337
- Misses        494     2724     +2230
- Partials      221      338      +117

Impacted Files
Coverage Δ

brownie/network/account.py
49.54% <0.00%> (-42.16%)
:arrow_down:

brownie/network/contract.py
47.50% <100.00%> (-43.27%)
:arrow_down:

brownie/_cli/bake.py
0.00% <0.00%> (-100.00%)
:arrow_down:

brownie/_cli/init.py
0.00% <0.00%> (-100.00%)
:arrow_down:

brownie/_cli/compile.py
0.00% <0.00%> (-100.00%)
:arrow_down:

brownie/_cli/run.py
0.00% <0.00%> (-88.89%)
:arrow_down:

brownie/_cli/test.py
0.00% <0.00%> (-85.00%)
:arrow_down:

brownie/project/compiler/vyper.py
15.04% <0.00%> (-79.65%)
:arrow_down:

brownie/_cli/ethpm.py
16.10% <0.00%> (-74.58%)
:arrow_down:

brownie/network/alert.py
25.80% <0.00%> (-72.59%)
:arrow_down:

... and 40 more

Continue to review full report at Codecov.

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

This is ready for review @iamdefinitelyahuman
Somehow couldn't resolve that one conflict with rebase o.O

closed in favour of #488


Combine 'My Courses' and 'Find Courses' experiences

Description
LEARNER-2212
Add a description of your changes here.
Notes
How to test this PR

Codecov Report

Merging #978 into master will increase coverage by 0.02%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##           master     #978      +/-   ##
==========================================
+ Coverage   45.53%   45.56%   +0.02%
==========================================
  Files         405      405
  Lines       26884    26885       +1
==========================================
+ Hits        12242    12249       +7
+ Misses      14642    14636       -6

Impacted Files
Coverage Δ

Source/OEXRearTableViewController.swift
0% <ø> (ø)
:arrow_up:

Source/StartupViewController.swift
79.08% <0%> (ø)
:arrow_up:

Source/OEXRouter+Swift.swift
16.34% <0%> (ø)
:arrow_up:

Source/EnrolledCoursesViewController.swift
72% <70%> (+0.36%)
:arrow_up:

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 4eb9622...a883844. Read the comment docs.

@saeedbashir I think we should update the screenshot test cases for the course view screen if possible.

@salman2013 Ready for another pass.

@salman2013 Ready for another pass.


import: clarify -o behavior for subdirectories

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

Clarify dvc import -o behavior when output path contains subdirectories.
See https://github.com/iterative/dvc/pull/4340

Thanks @pmrowla , really appreciate this!
Just curious - is it the same for get?

@shcheklein For get we do a fetch + checkout and create the output subdirectory if it doesn't already exist, since that's the normal behavior for checkout.

For get we ... create the output subdirectory if it doesn't already exist

I'll add this note too.
BTW I get the technicality involving internal processes (checkout) but it's kind of weird that get creates them but import doesn't... And why doesn't import use checkout? Hmmmm 🤔

It's because in import we are defining an actual stage/dependency, but for get it's treated more like a standalone file
from https://github.com/iterative/dvc/pull/4340#discussion_r466158245

We also don't makedirs in dvc run, but rather raise an error that wdir doesn't exist, so it seems it would be more consistent if we raise and error here too. Same with dvc add that shares the same logic with dvc run.

Makes sense, that's relevant context for sure. My idea would be that for consistency maybe no DVC commands should makedirs... In fact probably only get does that. But anyway, I won't open a ticket about this, up to you to bring it up with the core team if you wish Peter 🙂


Doesn't detect changes for projects inside a symlink

Environment data
VS Code version: 1.69.1
C# Extension version: 1.25.0
dotnet: 6.0.302
os: linux
OmniSharp log
None
Steps to reproduce
My workspace contains multiple projects. It also contains a symlink, and inside that there are more projects.
If I make changes to projects inside the symlink, omnisharp won't detect them. So I close and reopen vscode to force it to reanalyse those projects. Very very frustrating.
(The symlink is there because in a large monorepo with many people and subsystems, that is a convenient way to work.)
Expected  behavior
Omnisharp obviously can work with symlinks, because when vscode loads it detects all the projects in the symlink and analyses them normally.
So if they are changed, I'd expect omnisharp to detect the changes.
Actual behavior
Omnisharp doesn't detect changes. I must restart to force it to reanalyse the symlinked projects.
Additional context
None

A lot has changed with VS Code file watching since this issue was opened. If you are still having problems, please open a new issue


Actions

Reorganized the actions so that we have explicit files for mac, windows, ubuntu, and the docker files.
For mac and ubuntu, I test both debug and release versions for gcc and clang. mac also tests 4 versions of xcode across 2 versions of mac. Windows has many tests that I stole from nlohmann/json.
I'm not sure which we should enable for PRs only.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (88d6b5b) 97.00% compared to head (27d7187) 97.00%.

:exclamation: Current head 27d7187 differs from pull request most recent head 7e22577. Consider uploading reports for the commit 7e22577 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #307   +/-   ##
=======================================
  Coverage   97.00%   97.00%
=======================================
  Files          34       34
  Lines        2667     2667
=======================================
  Hits         2587     2587
  Misses         80       80

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


tg-archive: init at 1.1.3

Description of changes
This introduces a package for tg-archive, a tool for exporting Telegram group
chats into static websites like mailing list archives.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 303121 run on aarch64-darwin 1

2 packages built:

tg-archive
tg-archive.dist

Could you do an empty rebase (as in no changes) and force push that so you can trigger OfBorg again? It seems like it had an internal issue.

Result of nixpkgs-review pr 303121 run on x86_64-linux 1

2 packages built:

tg-archive
tg-archive.dist


tidying grammar

minor grammar and formatting

@chauey thank you so much for you effort, please revert server to semver and git commit -a --amend :)

Hi Dmitriy, you guys doing awesome work.
It took time to figure out the amend. Hope it’s correct now.
From: Dmitriy Shekhovtsov<EMAIL_ADDRESS>Sent: Tuesday, January 19, 2016 10:13 PM
To: valor-software/ng2-plans<EMAIL_ADDRESS>Cc: chauey<EMAIL_ADDRESS>Subject: Re: [ng2-plans] tidying grammar (#2)
@chauey https://github.com/chauey  thank you so much for you effort, please revert server to semver and git commit -a --amend :)
—
Reply to this email directly or view it on GitHub https://github.com/valor-software/ng2-plans/pull/2#issuecomment-172883491 .  https://github.com/notifications/beacon/AE5JJYHgCcauxMaZM9zIEb8akKwiBaBuks5pbkoWgaJpZM4HHt-d.gif

Looks good, thanks a lot :)
I will break again all the things with my grammar again soon
but I will try to not do this now :)


Adding the missing Lease* functionality

I finished implementing the api surface for Leases. Also included is a KeepAlive service which will refresh provided leases at a specified interval.
See the readme.md updates for a more detailed explanation of the new functionality.

The build is failing for this on Linux. Since I was working on this on Windows, I didn't realize that the PPL primitives I was using were being including from the MSVC runtime, and not from the subset that is included in the cpprest sdk.
Will look into how to fix...

hi @emusgrave Thanks for your effort! The changes looks good to me, but could you please add a test for the lease/keepalive functionalities? Maybe a tst/LeaseTest.cpp would be great.

Close as in favour of #31.

Close as in favour of #31.