Typescript 2.0 beta VS2015 U3 publish issue.

TypeScript Version:  2.0.0 beta VS2015 U3
Step

Install Typescript 2.0.0 beta
Create blank webapplication project.
Add typescript file.
Install nuget package Typescript msbuild 2.0.0 beta
Build project successfully with any error.
Publish project get error.

Copying file WebApplication20\file1.js to obj\Release\Package\PackageTmp\WebApplication20\file1.js failed. Could not find a part of the path 'WebApplication20\file1.js'.	WebApplication20	C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets	2998
The file in obj\TypeScriptCompilerOutput.text shows project name has been dupilicated.
Expected behavior:
c:\(solution name)\(project name)\file1.js
c:\(solution name)\(project name)\file1.map.js
Actual behavior:
c:\(solution name)\(project name)\(project name)\file1.js
c:\(solution name)\(project name)\(project name)\file1.map.js

I'm hitting this also.

It prevents me from publishing my web app, which is a showstopper.
Anyone know of a workaround? It's looking like I'll need to uninstall TS 2.0 beta for VS 2015.

@paulvanbrenk can you take a look.

@JudahGabriel or @lg314 can post a diagnostic build log? Does this only reproduce with the NuGet package? Is this an ASP.NET v4 or v5/Core project?

Does this only reproduce with the NuGet package?

I didn't use the NuGet package; I just downloaded and installed TS 2.0 beta for VS 2015.

can post a diagnostic build log?

Sure. How do I do that? You want the full obj\TypeScriptCompilerOutput.text file?

Is this an ASP.NET v4 or v5/Core project?

Nope. This is a good old fashioned MVC 5 project.
Repro steps are super simple, and take about 30 seconds:

Install the TS 2.0 beta for VS 2015.

In Visual Studio, File-> New MVC project.

Build -> Publish. Publish anywhere, including the local file system. Voila, the publish will fail.

Figured it out...
As a work around you can add the following to the project file:
<TypeScriptProjectDir>$(MSBuildProjectDirectory)\</TypeScriptProjectDir> after the <TypeScriptToolsVersion>2.0</TypeScriptToolsVersion> element.

Thanks so much for the workaround, Paul! I'll give it a try.

Have a fixed in the VS repo, this will be in the next 2.0 release.

@paulvanbrenk 's suggested fix of <TypeScriptProjectDir>$(MSBuildProjectDirectory)\</TypeScriptProjectDir> definitely fixed the issue! Any ETA on when this will be released?  I downloaded the TS 2.0 beta and still encountered the issue.

TS 2.0 RC (2.0.2) has already been released (https://blogs.msdn.microsoft.com/typescript/2016/08/30/announcing-typescript-2-0-rc/).


Occasionally Overly Persistent Popover/Hovercard

Description
I would expect that if the mouse is moved away from the hover target or hovercard area, the hovercard should disappear, right? However, I've noticed that the popovers don't always disappear following those rules and there seems to be at least two places where this is most noticeable:
(1) PRs
When attempting to copy the branch name, accidentally hovering over the user's profile pictures, fixes ticket id, or name, the hovercard appears and doesn't disappear when moving the mouse, clicking, or tapping ESC.

(2) My Issues
On this page, all the tickets are assigned to me and the popover only disappears when replaced. Clicking, tapping ESC, or moving the cursor away doesn't clear the popover.

Tickets that aren't assigned or opened by me seem to behave as expected
How to replicate the issue + URL
First open PR used to test: https://github.com/refined-github/refined-github/pull/6230
Extension version
22.12.15
Browser(s) used
Firefox (109.0)

Duplicate of #6227

Thanks! I was looking everywhere to find if someone else had seen this issue


Update health violation tutorial

Bring the health violation Model Builder tutorial up-to-date
Fixes #24830
Preview

@luisquintanilla I believe this is ready for an initial review.


[REQUEST] a performance benchmark with other production-grade database

@kawa1214 do you have update on this? already use your db on 8 prod node


Multiproject preferences updates

language and default domain option in preferences, split prefs into new table

create table domainprefs....
alter table user add column language varchar, add column defaultdomain int
migration script to move preferences to domainprefs table
drop columns in user table
adjust prefs page to use new preference locations

domainprefs
This table provides preferences for a domain, and is distinct from userdomain which only holds whether a user is able to access a domain or not. Notably, rows in this table remain even if a user is removed from a domain.

Name
Type

id
int autoinc

updateversion
int

user
int not null fk

domain
int not null fk

creationmode
int not null

welcomesig
string

welcometemplate
int fk

emailsig
string

Based on the idea posted in #675, the approach taken here is:

Remove welcome_sig as unused.
Remove welcome_template, abortpref, emailsig, creationmode, and skin from the user table
Create new userpreference table as (user, domain, preference, value)
Migrate removed columns from user into rows on userpreference
Built a new preference manager class to handle the difference between global and local, and arranging fallbacks between them as needed
Migrated everything to use the new architecture.

Domain specific settings get the domain tagged against them. Global settings get the domain column null. There's more complexity here surrounding the global generated column and the constraints to make this behave properly, but I consider that an implementation detail.
I'll leave the language preference out until we sort out internationalisation.


feat: support mview definition sql in pg_catalog.pg_matviews_info

Is your feature request related to a problem? Please describe.
Add a column definition in pg_catalog.pg_matviews_info: materialized view definition (a reconstructed SELECT query). And record definition sql in Table catalog as its data.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Cc @twocode


hacktoberfest2020

For me the PR that I submitted here is showing "ineligible repository" error. My PR has been merged already.
Is this repo no longer being counted in hacktoberfest?

@Anjalikumari15  i'm facing same problem. @bhaveshlohana What to do?

I am facing the same problem @Anjalikumari15

Yeah same problem here

Same problem here. Initially it was showing that it is waiting for acceptance, but then it changes to invalid pr. What to do now??

I have mailed Digital Ocean, I'll try something else as well.

I think if you add the label hacktoberfest-accepted the pr will be counted. If possible please do that @bhaveshlohana

@harshit3199  I am adding "hacktober-accepted" label to all the merged PR.

its hacktoberfest-accepted according to the hacktoberfest website

Why the project's label went from hacktoberfest to hackoberfest ?

I think label of this repository should be
"hacktoberfest" not
"hackoberfest"

@harshit3199
Yes, I think the only other reason that it's not showing invalid is someone must have reported this repo.

@BroLeaf Yeah, i corrected it.

@BloodyMonkey I have mailed Digital Ocean

Just want to confirm it is showing ineligible repo and not invalid, right?

Yeah it shows the ! mark so it's ineligible repo
On Wed, Oct 14, 2020, 12:36 PM Bhavesh Lohana<EMAIL_ADDRESS>wrote:

Just want to confirm it is showing ineligible repo and not invalid, right?
[image: image]
https://user-images.githubusercontent.com/53433312/95954973-c6f75000-0e19-11eb-9a9c-36b844e74995.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bhaveshlohana/HacktoberFest2020-Contributions/issues/1417#issuecomment-708206201,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNVHP3RRPUMPE7NJS2MIKTSKVEYLANCNFSM4SQBH7GQ
.

Ya it shows ineligible repo (!)

I have added "hacktoberfest-accepted" label and my repo has "hacktoberfest". I don't think the problem is from our side. Digital Ocean has issued me a ticket, they're looking into it.

the pr is showing illegible pr. So I dont think its because anybody has reported my request
although lets see what digital ocean has to stay

Same problem here. Initially it was showing that it is waiting for acceptance, but then it changes to invalid pr. What to do now??

I am sorry its not showing invalid but ineligible.

Hi,
I'm also facing the same problem. My PR is categorised as in Ineligible repository. Hope it will be resolved soon. Thank you for your efforts.

Hacktoberfest-team just made a new issue saying:

I am trying to show them that the contributions are valid.

Does anyone have any idea regarding this?

(https://github.com/abhishekdoifode1/Hacktoberfest2020)[https://github.com/abhishekdoifode1/Hacktoberfest2020] this one hasn't been excluded yet. Do try to PR here.

Digital Ocean told me that this repo doesn't contain any quality content whereas it has some of the most amazing Projects and Games.

I hope you all have contributed in other repos as well so your work doesn't go on vain.


can you help identify the issue why urlNormalizer  removeQueryString is not working as expected

I am using 2.8.2-SNPSHOT of http crawler
    <urlNormalizer class="com.norconex.collector.http.url.impl.GenericURLNormalizer">
			<normalizations>
				removeQueryString, removeFragment,lowerCaseSchemeHost,
                                 upperCaseEscapeSequence, decodeUnreservedCharacters,
                                 removeDefaultPort, removeDotSegments, removeSessionIds,
                                 upperCaseEscapeSequence
			</normalizations>
    </urlNormalizer>

My expectation is that I'll see only one url for the below urls-
    http://intranet.corp.internal.mycompany.com/about/you_helping_others.asp?credocelebration
    http://intranet.corp.internal.mycompany.com/about/you_helping_others.asp?credoweek2016
    http://intranet.corp.internal.mycompany.com/about/you_helping_others.asp?credoweek2017
    http://intranet.corp.internal.mycompany.com/about/you_helping_others.asp.asp?forourcolleagues

And it is showing duplicates.

I cannot reproduce.  Where do you see the duplicates? In the logs? Have you tried running everything "fresh" after you added this configuration entry?  Can you share your config and your logs?

RemoveQueryString should have converted all the 3 urls I mentioned to one base url
http://intranet.corp.internal.mycompany.com/about/you-helping-others.asp but it is not.
All 3 urls are seen in the log as well as in google cloud search datasource which I am using to index.

Is your snapshot version recent?  The "removeQueryString" option was added less than a month ago.
If you still have the issue with the very latest version, please share your config and site so I can reproduce (if private, you can send it by email, referencing this ticket).


Test image resolution

Hello, I am confused about resolution recently.
When I limited the resolution of the test image, I found that different resolutions would bring different effects. I currently speculate that the influencing factors are the resolution of the original image and the parameter setting of resize（）
I wonder if you have any research experience in this kind of question？
Looking forward to your reply

Resize() will usually cause different outputs as the network's receptive field on the objects in the input image changes as well.
This can be avoided by :

zero-padding the images that are too small;
setting the parameter ceil_mode=True in torch.nn.AvgPool2d().

The 1st solution is easy to understand and use, while the 2nd one can solve the problem of 'input image is too small' permanently but you'd better re-train the network (my suggestion).

Resize() will usually cause different outputs as the network's receptive field on the objects in the input image changes as well.
This can be avoided by :

zero-padding the images that are too small;
setting the parameter ceil_mode=True in torch.nn.AvgPool2d().

The 1st solution is easy to understand and use, while the 2nd one can solve the problem of 'input image is too small' permanently but you'd better re-train the network (my suggestion).

Thanked your reply.If I have a higher resolution image, For resolution reduction solutions，Do you have any Suggestions？

You can try to resize the high-resolution image to lower ones and forward it to the network, or crop the image in a sliding-window manner and then stitch the patches.


Using react-svg-morph with react-icons

Hi, I have a problem making these two modules work together. I use pretty basic, that goes like this:
 const MobileIcon = showMenu ? ChevronLeft : Menu
 return (
                      <MorphReplace>
                                <MobileIcon/>
                       </MorphReplace>
        )

There is an error in renderToJsonMethod in particular this part fails with undefined render:
var instance = new Component(element.props);
    res.name = Component.name;
    children = instance.render();

I use the latest versions of both libraries.

Same error..

react-icons have changed, so I think that they will not work because a use of the react context #2

Hi! Any news? Is there any recommended tuple of versions of both packages that work together?


Tracking Issue for Revision V silicon

ST has released a new silicon revision for the H742/742/750/753 with significant changes.

eevblog
ST community

Please report or tag issues with Revision V here! Also see upstream.

In the eevblog link above I see two notes regarding the ADC (which as mentioned in #10 would've been my next addition)
-ADC Now has a extra 'divide by 2' on its clock inside it, making existing clock configurations too slow
-Changes to the ADC registers (For example a value in a register that used to set the ADC to 8bit mode is now setting it to 'reserved' so likely doesn't work)

Now I assume this could be easily resolved using feature gates, however a feature gate named "V" or "Revision-V" might be hard for the average user to understand as they are probably not aware of Revision V.

Yes, these are significant changes! For now I say implement for Rev Y, then add -rev_v feature gates when someone has V silicon to test on.

FYI: The NUCLEO-H743ZI2 I just got from Digikey has Silicon rev V (and non-detachable ST-Link-v3)

https://github.com/stm32-rs/stm32-rs/pull/247 for the PAC split.

@richardeoin Can we close this? The crates/features are nicely split to address this, right?


修复表格的父级的传入的宽度改变时没有重新计算表格宽度的bug

一直用开,应该没有影响

一直用开,应该没有影响

The new version has solved this problem.
Please use version 2.0

The new version has solved this problem.
Please use version 2.0

Thanks for your PR

Thanks for your PR


Random transition not working

Hi there,
I have followed the instructions so my caption are using random transitions but for some reasons it's not working.
When I change the t attribute to a value of my transition array it works using the specified transition but using the star to use the random one it doesn't.
Here is my code:

		<?php // Foreach loop through images ?>

			<img data-u="image" src="<?php echo $imageUrl ?>" alt="<?php echo $slide->getAlt(); ?>" />

                        <?php echo $slide->getAlt(); ?>

		<?php // endforeach ?>

To enable random caption transition, please define transitions in following manner,
        var _CaptionTransitions = [
         {$Duration:1200,x:0.6,$Easing:{$Left:$JssorEasing$.$EaseInOutBack},$Opacity:2},
         {$Duration:1200,x:-0.6,$Easing:{$Left:$JssorEasing$.$EaseInOutBack},$Opacity:2},
         {$Duration:1200,y:0.6,$Easing:{$Top:$JssorEasing$.$EaseInOutBack},$Opacity:2},
         {$Duration:1200,y:-0.6,$Easing:{$Top:$JssorEasing$.$EaseInOutBack},$Opacity:2},
         {$Duration:1200,x:0.6,$Easing:{$Left:$JssorEasing$.$EaseInOutExpo},$Opacity:2},
         {$Duration:1200,x:-0.6,$Easing:{$Left:$JssorEasing$.$EaseInOutExpo},$Opacity:2},
         {$Duration:1200,y:0.6,$Easing:{$Top:$JssorEasing$.$EaseInOutExpo},$Opacity:2},
         {$Duration:1200,y:-0.6,$Easing:{$Top:$JssorEasing$.$EaseInOutExpo},$Opacity:2}
        ];

Awesome thanks for your quick answer, that's fixed now =)


Add rule: yoda_style to Laravel

PHP-CS-Fixer Rule: yoda_style
This PR enfoce non-yoda-style

Can you give some examples?

-        if (null === $this->input->getOption('format')) {
+        if ($this->input->getOption('format') === null) {
             $this->progress->subscribe();
         }

I'm not sure if it's a "bug" as much as my lack of understanding. So I am asking it here...
After upgrading today, the following conditional was changed.
-if (count($failed_tasks) === (count($tasks) - intval(isset($tasks['composer/install'])))) {
+if ((count($tasks) - intval(isset($tasks['composer/install']))) === count($failed_tasks)) {

I didn't think the existing conditional was a "yoda style" conditional. At least not a traditional one. It seems the 'always_move_variable' => true is the culprit. When I set it to false, I don't have any "violations".
I'm sure this change works at inverting "yoda style" conditionals, but my concern would be it swaps all conditionals. Ideally, it would leave non-yoda conditionals alone.

I agree with @jasonmccreary - always_move_variable seems to actually introduce Yoda-style (for want of a better term) in places and should be set to false

always_move_variable¶
Whether variables should always be on non assignable side when applying Yoda style.
Allowed types: bool
Default value: false

Can we get this set to false?

Fixed: https://github.com/laravel/pint/releases/tag/v1.13.1. Next time create an issue folks, because this type of discussions get lost with the other bazillion GitHub notifications we have.

I rarely add some criticism over open source projects since I believe in the hard work of the maintainers and respect their dedication.
But, I'm allowing myself to speak out my opinion about recent changes around the Laravel Pint package. I really hope that the maintainers don't get upset about it, this is supposed to be a friendly comment.
The above said. I recently had to do a lot of digging in order to understand why my style tests were failing or why my project changes were adding a lot of code style changes.
It turns out that all come down to Laravel Pint recent additions.
Some of them were applying PHP CS Fixer default values but others, like this one, are not.
The change in this PR overwrites the default PHP CS Rule value, always_move_variable, which is false.
I know that there are quite a lot of discussion around yoda conditions but, in my humble opinion, the advantages outweigh the disadvantages.
Yes, it is quite easy to overwrite the setting by adding an entry to my pint.json file but, it's not clear why those changes are being introduced.
I can see from the discussion above that there wasn't any reasoning around it, did I miss something?


The package is incompatible with angular 13

Description
When @angular/core@13 is installed, require @ngx-formly/core fails with the following error:
node:internal/modules/cjs/loader:979
    throw new ERR_REQUIRE_ESM(filename, true);
    ^

Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>not supported.
Instead change the require of<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
    at F:\Projects\test-formly\node_modules\@ngx-formly\core\bundles\ngx-formly-core.umd.js:2:85
    at Object.<anonymous> (F:\Projects\test-formly\node_modules\@ngx-formly\core\bundles\ngx-formly-core.umd.js:5:2)
    at Object.<anonymous> (F:\Projects\test-formly\test.js:1:1) {
  code: 'ERR_REQUIRE_ESM'
}

Minimal Reproduction
bug3049.zip
Your Environment

Angular version: 13.0.1
Formly version: 5.10.23

could you please check with https://github.com/ngx-formly/ngx-formly/releases/tag/v6.0.0-next.1

It's the same.

The reproduction is extremely simple:
npm i @ngx-formly/core @angular/core@13
node -r @ngx-formly/core

Ok I'll check on my side once I've got the chance

Angular v13 support is released in v6.0.0-next.4 (release), to give it a try use next tag:
ng add @ngx-formly/schematics@next --ui-theme=bootstrap


Notify volunteer if assigned/unassigned to an itinerary

Fixes #874
I will be adding one more event to write unit tests for ItineraryVolunteerListUpdatedHandler

Looks like it needs a rebase now that the @stevejgordon fire brigade piled on the PRs.  Thanks

@tonysurma, just rebased and pushed. Looks like no conflicts.

@tonysurma, this has been rebased and ready


Error: Attempt to index a non-existent element in an OrderedCollection

Try to do the following to reproduce the error:

Open a fresh Linter (SwaLint reset open).
Select all test categories (right upper window).
Select the magic numbers test (right lower window).
Unselect the "Software System Metrics" test category.

This is the graphical issue you will face...

Should not be a problem in https://github.com/hpi-swa-teaching/SwaLint/tree/developBasedOn2015 any more.


react-wooden-tree integration

Added the react-wooden-tree component as re-export of the original component's redux version. Added the tiny CSS to look like the PF version and created an entry in the storybook for it.
Known problem - Solved: The icons are from the font-awesome and I did not know how to include them (I did not wanted to put into the dependencies.)
@skateman

@Hyperkid123 If I try to load font-awesome (added as dev-dep) it tells me that I need an appropriate loader for the file:
ERROR in ./node_modules/font-awesome/css/font-awesome.css 7:0
Module parse failed: Unexpected character '@' (7:0)
You may need an appropriate loader to handle this file type.
| /* FONT PATH
|  * -------------------------- */
> @font-face {
|   font-family: 'FontAwesome';
|   src: url('../fonts/fontawesome-webfont.eot?v=4.7.0');

@Hyperkid123 If I try to load font-awesome (added as dev-dep) it tells me that I need an appropriate loader for the file:
ERROR in ./node_modules/font-awesome/css/font-awesome.css 7:0
Module parse failed: Unexpected character '@' (7:0)
You may need an appropriate loader to handle this file type.
| /* FONT PATH
|  * -------------------------- */
> @font-face {
|   font-family: 'FontAwesome';
|   src: url('../fonts/fontawesome-webfont.eot?v=4.7.0');

We might not have appropriate loader i will check that out. My question would be why we need to add new font as dev dependency? Font awesome is already part of PF-react. and icons should are used in other components.

I am sorry, yes, I used it and it works correctly without any other modification.

Who do I need to contact to merge this? @Hyperkid123

@brumik @skateman  let me test it

@brumik ok should be fine just fix your snapshots. It was probably caused by higher version of PF just update snapshots and it should be fine.

Locally it passes all tests and there are no snapshots to upgrade. The local version is the same as the repository version here. @Hyperkid123 I don't know what can be the problem.

@brumik you have never version of dependencies that is fine just run yarn test -u

@Hyperkid123 can you force Travis to re-run the second tests (which is not passing)?

@brumik i think you will need to skip more snapshots.

@brumik nice i will see what is going on with the snapshots once i have some window.

Okay :) :+1:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add semantic release and dependabot to this repo

As an developer, I want a pipeline with semantic release and dependabot so that with a commit and semrel defined tags new versions of the zitadel provider will get released on the terraform registry and the dependencies used are held up-to-date.
Acceptance criteria

[ ] Dependabot is included in the pipeline
[ ] SemRel conform commits result in new releases of the terraform provider
[ ] New releases of the terraform provider are automatically released to the terraform registry

From my perspecitve we can close this issue
feel fre to reopen if needed


dockerTools: Fix Docker layers order

The layer order was not correct when a parent image was used: parent
image layers were above the new created layer.
This commits simplifies the code related to layer ordering. In
particular, layers in layer-list are ordered from bottom-most to
top-most. This is also the order of layers in the rootfs.diff_ids
attribute of the image configuration.
A test is added to avoid such kind of issues in the future.
Motivation for this change
Fix bad behavior of our Docker tooling.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test docker-tools

Tests passed on 19.03 and backported in 39d3dd40a42238ae8bfa578012023170add56567.


Device configured without offpeak_time are started a 23:59

This configuration:
- name: "Chargeur"
     entity_id: "switch.pz10_battery_in"
     power_max: 110
     check_usable_template: "{{ (states('sensor.pz10_battery_in_energy_counter') | float) | round(2) < 1.41}}"
     duration_min: 20
     duration_stop_min: 5
     action_mode: "service_call"
     activation_service: "switch/turn_on"
     deactivation_service: "switch/turn_off"
     # We authorize the pump to start if there is 10% battery in the solar installation
     #battery_soc_threshold: 10
     # One hour per day maximum
     max_on_time_per_day_min: 450
     #start time of off-peak hours
     #offpeak_time:
     #the minimal time on 'on' per day in minutes
     #min_on_day_per_day_min:

should not start the device because min is deactivated and offpeak_time also.

https://github.com/jmcollin78/solar_optimizer/releases/tag/2.1.1


v1.1 - The multi-part identifier "x.Id" could not be bound

The following linq:
var foo = await _context.Things
                .Select(x => new ThingViewModel
                {
                    Name = x.Name,
                    Bars = x.Bars
                        .Take(5)
                        .Select(q => new ThingViewModel.BarViewModel {
                            OtherName = q.Name,
                    })
                }).ToListAsync();

Generates a Select N+1 of the following:
SELECT [t].[Name]
FROM (
    SELECT TOP(5) [q0].*
    FROM [Bars] AS [q0]
    WHERE [x].[Id] = [q0].[ThingId]
) AS [t]

This is invalid SQL, as [x] doesn't exist here. Removing the .Take(5) allows the query to proceed without issue (it is a select n+1, but I presume this is by design for now).

I should also flag, this is a regression from v1.0.

We do client eval in this case producing N+1 queries.
In the second query, ParameterInjection is faulty hence we generated incorrect SQL instead of having injected parameter.

Possible workarounds

Makes 2 queries but fetches all records from second table though only relevant columns. So if there are many Bars for each Thing it may perform poorly.

var foo1 = db.Things.Select(t => new {Id = t.Id, Name = t.Name}).ToList();
var bars =
    db.Set<Bar>()
        .Select(b => new {Id = b.ThingId, OtherName = b.Name})
        .GroupBy(t => t.Id)
        .Select(g => new {Id = g.Key, Bars = g.Take(5)})
        .ToList();

var foo = foo1.Join(bars, f1 => f1.Id, f2 => f2.Id,
    (f1, f2) => new { Name = f1.Name, Bars = f2.Bars }).ToList();

N+1 queries but only fetches required rows from Bars table. (Also fetches all columns)

var temp = db.Things.Select(t => new { t.Name, Bars = t.Bars.Take(5) }).ToList();
var foo = temp.Select(t => new {Name = t.Name, Bars = t.Bars.Select(b => new {OtherName = b.Name})}).ToList();

@smitpatel could you please take a stab at writing a justification/risk assessment for taking the fix in 1.1.1? A comment here in the bug works for me. Thanks.

Justification: This is regression from 1.0. Due to changes in query pipeline we started binding with outer query even though it was a separate SelectExpression overzealously without verifying if it would generate valid scenario. The fix blocks additional binding which could generate invalid queries.
Risk: This is low risk. It makes queries to evaluate certain parts on client side instead of translating to server. And in most of those cases, the server side translation was producing invalid queries.

This patch bug is approved. Please use the normal code review process w/ a PR and make sure the fix is in the correct branch, then close the bug and mark it as done.

merged to 1.1.1 in b8fb258be5b50922ce6405002f040d2ce51edaa9
in dev a457f2e22f7b2e29a645ad6a8c60c433c04f6d73

Thanks @smitpatel  👍


Deprecated selectors

Here is a deprecation warning in updated Atom:
atom-ungit
keymaps/ungit.cson
Use the atom-workspace tag instead of the workspace class.

I see it is fixed in the code, but the code is not released yet.

Fixed in #19 will be releasing a new tag soon.


Can't link in develop branch

Hello!
I have something like this in my component:
	void do_work()
	{
		std::vector<userver::engine::TaskWithResult<void>> tasks;
		for (int i = 0; i < 10; i++)
		{
			auto task = userver::utils::Async(
				"work",
				[i]
				{
					userver::engine::SleepFor(std::chrono::seconds(12 - i));
					LOG_INFO() << fmt::format(">>>> finishing task {}", i);
				});
			tasks.emplace_back(std::move(task));
		}

		summary_ = std::make_unique<userver::engine::TaskWithResult<void>>(userver::utils::Async(
			"result task",
			[tasks = std::move(tasks)]() mutable
			{
				userver::engine::GetAll(tasks);
				LOG_INFO() << ">>>> all tasks are completed - do some work";
			}));
	}

Run several task asynchronously and summary task that waits it all and do some work after that, but after switching to develop branch I can't link it
/usr/bin/ld: AsyncComponent.cpp.o: in function `userver::engine::FutureStatus userver::engine::impl::WaitAllCheckedFromContainer<std::vector<userver::engine::TaskWithResult<void>, std::allocator<userver::engine::TaskWithResult<void> > > >(userver::engine::Deadline, std::vector<userver::engine::TaskWithResult<void>, std::allocator<userver::engine::TaskWithResult<void> > >&)':
_deps/userver-src/core/include/userver/engine/wait_all_checked.hpp:83: undefined reference to `userver::engine::impl::DoWaitAllChecked(std::span<userver::engine::impl::ContextAccessor*,<PHONE_NUMBER>3709551615ul>, userver::engine::Deadline)'

And can't create minimal project to reproduce, because it's linked like a charm! And I can't understand how to fix this in the bigger one.
I've already rebuild all without ccache but small projects links and works, bigger project - nope.
Maybe you have some suggestions how to fix it?
Also I've compared all linked libraries between projects - all userver libs linked in both projects. The difference only in external dependencies.
Thanks.

Continue investigation:
libuserver-core.a has userver::enigne::impl::DoWaitAllChecked entry
I do not add some linker options for this target
verbose compile string:
[518/861] /usr/bin/ccache /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_ENABLE_ASSERT_HANDLER -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOCALE_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED=1 -DBOOST_STACKTRACE_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DCARES_STATICLIB -DPIC -DUSERVER -DUSERVER_NAMESPACE=userver -DUSERVER_NAMESPACE_BEGIN="namespace userver {" -DUSERVER_NAMESPACE_END=} -DUSERVER_USE_BOOST_DWCAS=1 -D_GLIBCXX_ASSERTIONS -I/home/ws/_build/_deps/userver-src/core/uboost_coro/include -I/home/ws/_build/_deps/userver-src/core/include -I/home/ws/_build/_deps/userver-src/third_party/pfr/include -I/home/ws/_build/_deps/userver-src/core/../universal/src -I/home/ws/_build/_deps/userver-src/core/src -I/home/ws/_build/userver/core -I/home/ws/_build/_deps/userver-src/universal/include -I/home/ws/_build/_deps/userver-src/third_party/date/include -I/home/ws/_build/_deps/userver-src/third_party/function_backports/include -I/home/ws/_build/_deps/fmt-src/include -I/home/ws/_build/_deps/cctz-src/include -I/home/ws/_build/_deps/userver-src/third_party/boost_stacktrace/include -I/home/ws/_build/_deps/userver-src/third_party/uboost_coro/include -I/home/ws/_build/_deps/c-ares-build -I/home/ws/_build/_deps/c-ares-src -I/home/ws/_build/_deps/c-ares-src/include -I/home/ws/_build/_deps/userver-src/universal -I/home/ws/_build/_deps/cryptopp-cmake-build/cryptopp -I/home/ws/_build/_deps/cryptopp-cmake-build -isystem /home/ws/_build/_deps/userver-src/core/libc_include_fixes -isystem /home/ws/_build/_deps/userver-src/third_party/moodycamel/include -g -std=c++17 -fvisibility-inlines-hidden -pipe -g -gz -fPIC -Wall -Wextra -Wpedantic -mcx16 -ftemplate-backtrace-limit=0 -Wdisabled-optimization -Winvalid-pch -Wlogical-op -Wformat=2 -Wno-error=deprecated-declarations -Wimplicit-fallthrough -Wno-useless-cast -fmacro-prefix-map=/home/ws//= -fmacro-prefix-map=/home/ws/_build//= -fmacro-prefix-map=/home/ws/= -MD -MT userver/core/CMakeFiles/userver-core.dir/src/engine/wait_all_checked.cpp.o -MF userver/core/CMakeFiles/userver-core.dir/src/engine/wait_all_checked.cpp.o.d -o userver/core/CMakeFiles/userver-core.dir/src/engine/wait_all_checked.cpp.o -c /home/ws/_build/_deps/userver-src/core/src/engine/wait_all_checked.cpp
In file included from /home/ws/_build/_deps/userver-src/core/src/engine/task/task_counter.hpp:9,
                 from /home/ws/_build/_deps/userver-src/core/src/engine/task/counted_coroutine_ptr.hpp:6,
                 from /home/ws/_build/_deps/userver-src/core/src/engine/task/task_context.hpp:15,
                 from /home/ws/_build/_deps/userver-src/core/src/engine/impl/wait_any_utils.hpp:7,
                 from /home/ws/_build/_deps/userver-src/core/src/engine/wait_all_checked.cpp:5:
/home/ws/_build/_deps/userver-src/core/src/concurrent/impl/interference_shield.hpp:12:10: warning: use of ‘std::hardware_destructive_interference_size’ [-Winterference-size]
   12 |     std::hardware_destructive_interference_size;
      |     ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/ws/_build/_deps/userver-src/core/src/concurrent/impl/interference_shield.hpp:12:10: note: its value can vary between compiler versions or with different ‘-mtune’ or ‘-mcpu’ flags
/home/ws/_build/_deps/userver-src/core/src/concurrent/impl/interference_shield.hpp:12:10: note: if this use is part of a public ABI, change it to instead use a constant variable you define
/home/ws/_build/_deps/userver-src/core/src/concurrent/impl/interference_shield.hpp:12:10: note: the default value for the current CPU tuning is 64 bytes
/home/ws/_build/_deps/userver-src/core/src/concurrent/impl/interference_shield.hpp:12:10: note: you can stabilize this value with ‘--param hardware_destructive_interference_size=64’, or disable this warning with ‘-Wno-interference-size’

userver/core$ grep -r DoWaitAllChecked .
grep: ./libuserver-core.a: binary file matches
grep: ./CMakeFiles/userver-core.dir/src/engine/wait_all_checked.cpp.o: binary file matches

as expected

I found it!
target_compile_features(${PRJ_TARGET} PUBLIC cxx_std_20)
break all the linking
there is minimal project
cpmt.zip

Looks like my code with C++20 after header parsing expected std::span<> usage, but userver compiles with internal span class (userver-src/universal/include/userver/utils/span.hpp)
Can I use C++20 with userver? Can I set C++20 through CPM?

target_compile_features(userver-universal PUBLIC cxx_std_20)
target_compile_features(userver-core PUBLIC cxx_std_20)

fixes it
but... maybe
Should userver build system use system-wide settings if it satisfies, for example, C++STD not less than 17? Then use system wide, if not - use C++17 at least to build

To use C++20 in your project, either

pass -DCMAKE_CXX_STANDARD=20 to cmake configure invocation, or
add set(CMAKE_CXX_STANDARD 20) to the beginning of your CMakeLists.txt.

Same with C++23.

ok. Think it is not bug, but consider it somewhere in documentation, which standard use and how.


Invalid xml in latest zip from Kevin

@foo4thought : The ingest hasn't completed, so I can't give you the clean report, but out of 26K records I have 125 errors. Not bad. List-as-far-as-I've-gotten is attached. Some of them are schema errors. Others (empty content) are ad hoc checks that I've added. I could be wrong on those.

ingest-errors-1-21.txt

Thanks!

IDK the validation errors about "This element is not expected."  They appear in the proper order, have the correct name, namespace, etc.  Truly null elements will end in '/>' so the appearance of dual tags open/close "empty-looking" data is wrapping whitespace character(s).  I confirmed that in the FMP source.

Hmm, so our theory is that Nokogiri's interpretation of the XSD is buggy? Maybe, but this needs to stay open until the errors go away, one way or another.

@foo4thought : back in your court. Looking at one record:
<pbcoreDescriptionDocument xmlns="http://www.pbcore.org/PBCore/PBCoreNamespace.html" annotation="V_F98F1F90D7E84F77A06524CCDC26EC83">
  <pbcoreAssetType>Program master</pbcoreAssetType>
  <pbcoreAssetDate dateType="Item Date">07/20/1992</pbcoreAssetDate>
  <pbcoreIdentifier source="Open Vault UID">V_F98F1F90D7E84F77A06524CCDC26EC83</pbcoreIdentifier>
  <pbcoreTitle titleType="Program">BOB AND RAY : THE ONE AND ONLY</pbcoreTitle>
  <pbcoreAnnotation annotationType="Duration">00:56:00:00</pbcoreAnnotation>
  <pbcoreAnnotation annotationType="Media Type">Video</pbcoreAnnotation>
</pbcoreDescriptionDocument>

Error:
Schema validation errors:
Element '{http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreAnnotation':
This element is not expected. Expected is one of (
  {http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreTitle,
  {http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreSubject,
  {http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreDescription
)

and the schema:
...
<xsd:element maxOccurs="unbounded" minOccurs="1" name="pbcoreDescription"
...

Basically, the schema parse errors are based on a state machine, and so very often they are a long list of optional elements, and then the one required one that is missing, as in this case.
I think we were getting a small enough number of errors that maybe the fix is to just do the cataloging that needs to be done? That can be between you and Casey.

@foo4thought : There are still errors in the latest I have from you. I can give you a full list maybe later in the day, but for example:

WARN [2016-01-29 13:11:15]: /Users/chuck_mccallum/Downloads/2015_OV_MASTERS_FINAL_pbcoreRENAMED.zip :: V_184C15CF434948629BB6E255699B626F.xml : Schema validation errors: Element '{http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreGenre': This element is not expected. Expected is one of ( {http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreTitle, {http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreSubject, {http://www.pbcore.org/PBCore/PBCoreNamespace.html}pbcoreDescription ).
Still missing description, I think?

Warnings from the latest full ingest

@mccalluc @foo4thought
I have a ticket to myself to fix the 61 asset_type errors you are getting
#46

Latest ingest has fewer error: I'm going to close this, and open new more granular bugs for the different kinds of errors.


Add innerHTML option

I have a use case where my text has anchors in it but because it uses innerText / textContent, it actually removes links and post parsing it is just a nightmare so I added an option to use innerHTML instead.

@jethrodew thank you so much for this thoughtful PR. Sorry I didn't see it sooner! Could you write a test in tests/test.js?
I will then go through it all to make sure we're fully covered for now & then. 😊

@jethrodew I thought about your scenario more and the shave readme notes that shave is for text content. If shave were to support trimming of html, the plugin would have 2 problems:

html elements which would not necessarily be inline and could have their own styles which would create un-thought-of results defeating the purpose of the plugin.
It is a UX problem. If there are html links within the trimmed text, then the links, etc would potential be hidden which mutes the reason for trimming text at all.

For your scenario, I would suggest 3 things:

Remove html from the content of the item you'd like to trim, then trim it.
Hide a portion of the text and add show-more button.
Use Line Clamp

What are your thoughts?
If you agree, we can close this PR, add a note in an issue, and then link to it in the readme.
Thanks again!

Hey Jeff, I totally understand the issue with this; it's a nasty business with the extra possibilities which obviously couldn't be supported as it would add huge bloat to the project. The problem I have is that if my sample text has a nice simple anchor in it, that gets removed by Shave when it runs so I would have to post process it to add it back in.
Line Clamp has yet to be properly implemented by Edge and Firefox which is a massive pain so i can't use that route for client reasons. I have implemented a wrapper for my app which gives it the ability to have read more / show less functionality but links that are in the visible portion of text are not clickable even though they were rendered that way. I don't want it to be a cause for efficiency problems, if you feel that it is not suited to Shave, I shall simply add it to my wrapper layer and leave it at that. Thanks for your time and consideration, I absolutely love the simplicity and effectiveness of Shave; keep up the good work!!

@jethrodew cool! I'm going to close this PR. Please share your implementation—would love to see it! 🙌

Thanks Jeff!! 👍


Need two left arrow presses to get to parent

re https://github.com/microsoft/vscode/issues/85928

use Java 12 dev container
in the explorer reveal and select App.java
press App.java, press arrow-right
press Arrow-left
:bug: app-folder isn't selected, it requires a 2nd arrow-left press

It's weird that you also need to press Arrow Right more than once to expand the compressed node, however you only need one mouse click to expand.


Add base32 is possible

Hi, it is a suggestion. The main geocodes, like Geohash, use something between base16 and base36 to compress, because   for humans and use in resilient protocols  we can use alphanumeric codes (no extra-symbols) with case insensitive letters.  PlusCode e.g. uses base20, in this range. And the most useful are the base32 variants... Is important to show (here  without patents, this is the merit of the open work!) how to offer Hilbert indexation of base32.
As 32×32=1024, we have an exact representation for each two base32 digits. In the Hilbert hierarchical grid terms, it is a "level L5" or "level L+5".  So one digit is "L+2.5" (level L+3 minus a half)... It can be represented as "degenerated grid" merging pairs of cells:

The reindexation is necessary only when identifing the cells of the grid, and it is easy, for each cell x, of an index x starting with zero, there are a merged cell  i=floor(x).
It is only a problem of spatial interpretation (grid interface construction when need), the base32 geocode existense is independent of a visual grid interface.

The internal INT representation is a 64 bit integer. you can treat this as 2 32-bit unsigned integers. Will that be a good solution?


Support multiple interceptors together

Is your feature request related to a problem? Please describe.
Add support for invoking two or more interceptors.
Describe the solution you'd like
Replace SetInterceptor on IConfigurator with AddInterceptor method that allows chaining of interceptors.
Describe alternatives you've considered
Today, one can create the class ChainedInterceptor that delegates to multiple interceptors to circumvent this feature gap.
class ChainedInterceptor(params ICommandInterceptor[] interceptors) : ICommandInterceptor
{
    public void Intercept(CommandContext context, CommandSettings settings)
    {
        foreach (var interceptor in interceptors)
        {
            interceptor.Intercept(context, settings);
        }
    }
}

I'm interested in having library support for interceptor chaining.
Additional context

I'll be happy to contribute code to close this feature request. However, I'm not sure how to achieve this feature request without causing backward-incompatible changes to either the IConfigurator or the ICommandAppSettings interface.

Wouldn't it be better if we allowed multiple interceptors to be registered instead of a single one?

Yes, that's the intention of the feature request too. The SetInterceptor method can be deprecated in favour of an AddInterceptor method on the IConfigurator interface IMO.

@aditnryn would #1412 solve your problem?

Fixed by https://github.com/spectreconsole/spectre.console/pull/1412.


HMX: Add recipes for stable can/ethernet names

Add recipe to rename CAN and Ethernet interfaces to canoX and enX
Add recipe to rename interfaces to the old ethX/canX names for old legacy software with a systemd service that runs before networking is configured.

@mattiasbus  Waiting on fridays work to be pushed up, before i review again. I think the solution with 11-...rules that uses your custom script to cange cano back to can is good enough. if we use it as a service it could fail if we need to restart any can driver or it redetects.


FUSETOOLS2-1970 - Avoid IllegalArgumentException for file without

extension in same folder
when using JBang and that we let auto-detect routes, the files without extensions were added as potential routes and, as expected, no RouteLoader were found. An IllegalArgumentExeption was thrown at this time.
Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

not found a way to write a test easily.

Given that it is a regression in Camel 3.21, I think we should backport it to 4.0.x and 3.21.x and 3.x if and when the PR is accepted

Ah can you move that logic after the // skip dirs check as essentially almost all dirs are named without a dot / extension.


WIP: Upgrade omniauth-google-oauth2 to 0.8.1, fixes #2141

I rule and have completed some work on Case Manager that's ready for review!
This pull request makes the following changes:

upgrade omniauth-google-oauth2
upgrade devise

It relates to the following issue #s:

Fixes #2141

For reviewer:

When this is ready, I will remove the WIP prefix from the PR title and assign reviewers.
I will create user accounts for the reviewers on sandbox.
I will deploy this branch to sandbox, temporarily hijacking the normal release flow for testing purposes.
Reviewers will try to sign in with Google to confirm that the change works.

Current status: Login with Google test fails in this way:

Also, the current PR is still not great, because it requires pointing to the head of master for the devise package.

hm, these are the endpoints that the sandbox creds are auth'd on:

so if you're grabbing the googly creds from sandbox, I would have expected that to not complain about forbidden. I'll try to recreate this tmw.
I'm not sure #2120 matters -- I thnk that's more for adding more authorized domains, and I don't think we need that for this, right?

My plan was to deploy to sandbox for testing the upgrade; I don't think telling Google to redirect to localhost will work.
Also, where did you get that screenshot from? AFAIK we removed the Sandbox Google OAuth creds when onboarding the latest fund because we ran out of domains (prompting you to go through app verification in #2120).
I think we are done with verification though, because I was able to add back Sandbox to the list of OAuth clients just now, and test that logging in with Google works.

This is the failing test:
test_0001_can sign in with Google Auth Account - GoogleSSOTest::access top page
Why do we also need to upgrade devise? This is the thread: https://github.com/heartcombo/devise/pull/5327
In the mean time, there is a failing test, and it's unclear whether this is something devise still needs to fix for the new omniauth version, something broken in the test, or something broken in our app since the upgrade.
This can be tested by deploying this PR to Sandbox and seeing if "Login with Google" still works. Even if it does though, I would feel super uncomfortable merging a PR that essential points to HEAD of devise. That maintainer hasn't released a new version yet with the required fixes. In my opinion, the best thing to do is wait.

Definitely agree we should keep our powder dry until a new devise version comes out! I'll adjust issue title accordingly.

Codecov Report

Merging #2145 (41186e7) into main (1bb6afb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2145   +/-   ##
=======================================
  Coverage   91.13%   91.13%
=======================================
  Files          84       84
  Lines        1986     1986
=======================================
  Hits         1810     1810
  Misses        176      176

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 1bb6afb...41186e7. Read the comment docs.


vis: 0.3 -> 0.4

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis -v and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-menu -v and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/.vis-wrapped -v and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete -h got 0 exit code
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete --help got 0 exit code
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete help got 0 exit code
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete -V and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete -v and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete --version and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete version and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete help and found version 0.4
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-open -h got 0 exit code
ran /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-open --help got 0 exit code
found 0.4 with grep in /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4
found 0.4 in filename of file in /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4

cc "@vrthra @ramkromberg"

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-menu
gzipping man pages under /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin
patching script interpreter paths in /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4
/nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-clipboard: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
/nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-open: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
/nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4/bin/vis-complete: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
checking for references to /tmp/nix-build-vis-0.4.drv-0 in /nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4...
/nix/store/zr63rvkc5wimxwiwglp97yvdg71yj1jx-vis-0.4

Success on x86_64-darwin (full log)
Partial log (click to expand)
wrapping /nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4/bin/vis with runtime environment
post-installation fixup
gzipping man pages under /nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4/share/man/
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4/bin
patching script interpreter paths in /nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4
/nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4/bin/vis-open: interpreter directive changed from "/bin/sh" to "/nix/store/pkjmwq7sqrvjg7cjiph6hq0khsmfl6p8-bash-4.4-p12/bin/sh"
/nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4/bin/vis-clipboard: interpreter directive changed from "/bin/sh" to "/nix/store/pkjmwq7sqrvjg7cjiph6hq0khsmfl6p8-bash-4.4-p12/bin/sh"
/nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4/bin/vis-complete: interpreter directive changed from "/bin/sh" to "/nix/store/pkjmwq7sqrvjg7cjiph6hq0khsmfl6p8-bash-4.4-p12/bin/sh"
/nix/store/5p0gwfgickw391sk0jnc9wx6ysd9dgvc-vis-0.4

Success on aarch64-linux (full log)
Partial log (click to expand)
these paths will be fetched (0.56 MiB download, 2.90 MiB unpacked):
  /nix/store/4h6jqpd73qz1g59m3nsf18cny7xvs8j5-lua5.2-lpeg-0.12
  /nix/store/g9k1885kdxyrpr62xmrcd2f5dsrdx2nw-vis-0.4
  /nix/store/gcgr3bd2i77k6vjvc2hgrm7xkpw0417c-libselinux-2.4
  /nix/store/yxzn26hdqmc67ngmvnh0bdk9h31qapdz-libtermkey-0.20
copying path '/nix/store/gcgr3bd2i77k6vjvc2hgrm7xkpw0417c-libselinux-2.4' from 'https://cache.nixos.org'...
copying path '/nix/store/yxzn26hdqmc67ngmvnh0bdk9h31qapdz-libtermkey-0.20' from 'https://cache.nixos.org'...
copying path '/nix/store/4h6jqpd73qz1g59m3nsf18cny7xvs8j5-lua5.2-lpeg-0.12' from 'https://cache.nixos.org'...
copying path '/nix/store/g9k1885kdxyrpr62xmrcd2f5dsrdx2nw-vis-0.4' from 'https://cache.nixos.org'...
/nix/store/g9k1885kdxyrpr62xmrcd2f5dsrdx2nw-vis-0.4


Proposal: ## devspec for machine readable development/maintenance metadata

Is your feature request related to a problem? Please describe.

OfBorg doesn't always know what to test, especially when the file isn't a package definition.
Users often don't know how to test changes in a given file (if it's not a package, where we have the tests attribute).
A template for adding this info to a file would be helpful even if not machine-readable:

Fewer thoughts required for each comment.
Users and contributors can recognize it and create a habit.

Suitable for quick "find in file" navigation.

Consistency is good.

Highly reused modules currently have a maintenance problem because testing all use cases is somewhat difficult. Nixpkgs maintainers do not want to reverse engineer a test protocol, and shouldn't have to.

Describe the solution you'd like

A standard format
A machine readable format
If it's a package, just keep using the tests attribute and such. A meta attribute for docs could be helpful, but out of scope for this discussion. I'm specifically trying to solve a problem for non-package files.

Draft
Example:
## devspec
# documentation:
#   - ../doc/foo-bar.md
# tests:
#   - /pkgs/tests/foo/bar.nix
# test-commands:
#   - nix-build -A tests.foo.bar
#   - nix-build -A nixosTests.foo-bar
# maintainers:
#   - alice
#   - bob
# ---

## devspec marks this as a standard header that must be parseable

#-style comment because it's about the implementation; not the interface, like documentation comments (/** */)
## is a bit like the ** in /**, marking that it's more significant somehow.
devspec is "grep-able", e.g. 6 or 7 keypresses while already editing the file
devspec is searchable in issue tracker, documentation, etc

The lines after are s/^# /  / and parsed as yaml, until # --- is encountered or a line that doesn't start with #

Then any tooling can use the info. Standard fields:

documentation: list of paths and/or URLs that must be maintained
tests: list of paths that have tests that check the current file
test-commands: how to run the tests. This attribute can perhaps also be specified in the tests files instead. These are meant to be Nix CLI  compatible, but tooling is allowed to parse the commands. Test files should contain collections of tests that are fast enough, or taking the test-commands from the tests files would be a problem. Factoring large suites into multiple files seems like a good idea anyway.
maintainers: people to ping, somewhat like CODEOWNERS, but controlled by us and without the mass ping problem

All paths are "relative URLs" (which include paths) that are resolved relative to the base directory, but / refers to the root of the project (ie Nixpkgs) instead of the system root.
Implementation steps:

[ ] Refine this spec while writing one or two parsers
[ ] Add support in ofborg

Enumerate files that have changed
Parse the devspec in all files that have changed. Fail if invalid
Implement a heuristic that avoids running all tests on tree-wide changes. E.g. limit number of test-commands
Add jobs and commit status(es)

[ ] Add spec and user docs in Nixpkgs manual

Add a :+1: reaction to issues you find important.

Robert, I think I'd like to use the currently unused shebang at the top of these files for testing purposes, so that when you ran the file it'd run the tests for the file.

That's an interesting idea, but it is a bit less capable.

not applicable to files that are already executable
limits the usefulness of the executable bit when looking for scripts that actually do something
not as easy to have multiple test commands; not impossible but harder to shoehorn that into a single shebang

More subjectively, I also expect that bundling it with the other attributes makes it a nice, coherent experience that's similar to the package tests and meta attributes.

The lines after are s/^# /  / and parsed as yaml, until # --- is encountered or a line that doesn't start with #

we should limit that to a very limited subset of yaml, like only lists of strings. Otherwise we might run into subtle differences between yaml 1.1 and 1.2 or some other less fun parsing things.


TST: stats: don't pass invalid alpha to np.random.dirichlet

Fixes gh-7747

straightforward, merging


Logging exception including dead-lettering message.

Is it possible to log exception when exception occurs for receiver within message handler when messages have to be moved to dead-letter queue?
Is it possible to log the number of retries when message is moved to dead letter queue?
Due to limitation of the trigger, is it possible to MessageReceiver and MessageSender, or similar instead?

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

ID: 0440205f-adcc-0fc5-3adb-db4dbe1d1292
Version Independent ID: 14ad1300-590c-8102-6887-366078e1882a
Content: Azure Service Bus bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-service-bus.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Thanks for the feedback! We are currently investigating and will update you shortly.

Please see this?

link to stackoverflow is a broken link.


Fix backwards compatibility tests, raise error for torch version mismatch

What does this PR do?
Fixes FSDP checkpoint backwards compatibility tests, and raises a helpful error for likely torch version mismatch on checkpoint load. For context, the test that was failing was when trying to load a checkpoint written with torch 2.3.0 when using torch < 2.3.0, since the older torch versions could not correctly read the new metadata file.

What issue(s) does this change relate to?

Before submitting

[ ] Have you read the contributor guidelines?
[ ] Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
[ ] Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
[ ] Did you update any related docs and document your change?
[ ] Did you update any related tests and add any new tests related to your change? (see testing)
[ ] Did you run the tests locally to make sure they pass?
[ ] Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

daily tests are passing too


logger: log_writer_file increase stack 1170 -> 1472 bytes

One weird thing to note here is that neither px4_fmu-v5_stackcheck or px4_fmu-v5_debug are hardfaulting.

Something doesn't add up here. After I increased the log_writer_file stack 1170 -> 1472 bytes it's now only using ~ 800 bytes?

Still seeing this in master and bumping the stack stops the hardfaults.

I'll merge this for now and we can re-evaluate.


Local claims UI

The local-claims-ui branch should represent the complete user interface for handling claims without saving to or pulling from the database (hence "local").

The big remaining tasks include:

I need to have the various content boxes update the context.
I need to implement the deleteClaim state management function.
I need to use deleteClaim in the claim tab dropdown menu.
I need to create warning pages before the user can delete a claim.
I need to make the body extend all the way down the screen for large screen sizes.

The big remaining tasks include:

I need to compute additional information as I parse, such as a parse tree (to be passed to the backend) and a dependencies set.
I need to implement the deleteClaim state management function.
I need to use deleteClaim in the claim tab dropdown menu.
I need to create warning pages before the user can delete a claim.
I need to be able to condition and un-condition claims.
I need to display claim conditioning correctly.
I need to make the body extend all the way down the screen for large screen sizes.

Also, I think I should re-consider how I'm going to use conditioning in my program. In the old version of logicgraph.dev, I used conditioning for two purposes: (1) letting the user specify claims that they were uninterested in debating the truth or falsity of, and (2) letting the user specify a set of beliefs that the user wanted to examine (by looking at which other claims helped or hurt that partial truth assignment). I don't see why these ways of conditioning should be one and the same: the user should be able to specify which claims they want to condition on taking certain values and also specify which other claims they want to play with assignments of.

Okay, I think that conditioning is still useful but that it should be reserved for purpose (1). There will be plenty of claims that the user never wants to entertain and the user should be able to specify that information as they enter the claims. Conditioning should live with the Claims interface. I think that ideology specification should become a separate thing in the Analysis section.

The big remaining tasks include:

I need to be able to condition and un-condition claims.
I need to display claim conditioning correctly.
I need to make the body extend all the way down the screen for large screen sizes.
I need to rename "Zeroth Order Claim" as "Constraint Claim."
I need to make the navigation bar depend on the page. The "New Claim" button should not be visible from Analysis, for example.

The big remaining tasks include:

I need to make the body extend all the way down the screen for large screen sizes.
I need to remove the interpreted text. It's not worth the extra confusion.
I need to make the navigation bar depend on the page. The "New Claim" button should not be visible from Analysis, for example.
I need to figure out how the user interface will integrate having different debates. For example, I've decided that I want to have a "My Debates" page. Presumably users should be able to save and name these debates and then maybe publish them so that other users can pull claims from them. If that's the case then I should display the name of the current debate somewhere.

The big remaining tasks include:

I need to make the body extend all the way down the screen for large screen sizes.
I need to make the navigation bar depend on the page. The "New Claim" button should not be visible from Analysis, for example. I also need to figure out how the user interface will integrate having different debates. For example, I've decided that I want to have a "My Debates" page. Presumably users should be able to save and name these debates and then maybe publish them so that other users can pull claims from them. If that's the case then I should display the name of the current debate somewhere.
I need to figure out how to give the user meaningful error messages during parsing. These error messages need to be delivered via a separate channel so that they don't get displayed in the dialog box for claim deletion. I guess I could also rely on the fact that if a claim doesn't parse then it won't be seen as an ancestor in the first place. On the other hand, my current parsing error messages are terrible and I should improve them anyway.

The big remaining tasks include:

I need to make the body extend all the way down the screen for large screen sizes.

Looks good in testing. Let's finally merge into main!


unable to render local image with relative path

For example:
![hello](imgs/hello.png)

rendered as
[hello](imgs/hello.png)

But
![hello](/Users/kamidox/imgs/hello.png)

rendered correct as
<img src="/Users/kamidox/imgs/hello.png" />

Sorry, This should not be a issue. I can enable safe_links_only to enable local relative image path.


Use webui.service.port for WEBUI_URL secret value

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area falcosidekick-chart
What this PR does / why we need it:
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Sryther
Once this PR has been reviewed and has the lgtm label, please assign cpanato for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @Sryther! It looks like this is your first PR to falcosecurity/charts 🎉

LGTM label has been added.  Git tree hash: 289f46f50c04a285bbf36fed44e0b661054e2813

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, Sryther
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ImmutableJS SyncValidationForm does not prevent submit

Are you submitting a bug report or a feature request?

Bug
What is the current behavior?

Sync validation contains errors, but form can still get submitted even though it is completely empty.
What is the expected behavior?
Prevent submission if fields have errors (checks on the format/length etc have not been passed)
What's your environment?

Redux-form v6.6.1
React v15.4.2
Other informations

Using react-boilerplate as a base for my project.
reducer setup:
import { reducer as reduxFormReducer } from 'redux-form'

export default function createReducer(asyncReducers) {
  return combineReducers({
    route: routeReducer,
    form: reduxFormReducer,
    ...asyncReducers,
  });
}

Form component
import React from 'react'
import { Field, reduxForm, reducer } from 'redux-form/immutable'

const validate = values => {
  const errors = {}
  if (!values.username) {
    errors.username = 'Required'
  } else if (values.username.length > 15) {
    errors.username = 'Must be 15 characters or less'
  }
  if (!values.email) {
    errors.email = 'Required'
  } else if (!/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i.test(values.email)) {
    errors.email = 'Invalid email address'
  }
  if (!values.age) {
    errors.age = 'Required'
  } else if (isNaN(Number(values.age))) {
    errors.age = 'Must be a number'
  } else if (Number(values.age) < 18) {
    errors.age = 'Sorry, you must be at least 18 years old'
  }
  return errors
}

const warn = values => {
  const warnings = {}
  if (values.age < 19) {
    warnings.age = 'Hmm, you seem a bit young...'
  }
  return warnings
}

const renderField = ({ input, label, type, meta: { touched, error, warning } }) => (

    {label}

      <input {...input} placeholder={label} type={type}/>
      {touched && ((error && {error}) || (warning && {warning}))}

)

const SyncValidationForm = (props) => {
  const { handleSubmit, pristine, reset, submitting } = props
  return (
    <form onSubmit={handleSubmit}>
      <Field name="username" type="text" component={renderField} label="Username"/>
      <Field name="email" type="email" component={renderField} label="Email"/>
      <Field name="age" type="number" component={renderField} label="Age"/>

        <button type="submit" disabled={submitting}>Submit</button>
        <button type="button" disabled={pristine || submitting} onClick={reset}>Clear Values</button>

    </form>
  )
}

export default reduxForm({
  form: 'syncValidation',  // a unique identifier for this form
  validate,                // <--- validation function given to redux-form
  warn                     // <--- warning function given to redux-form
})(SyncValidationForm)

Using the form:
import SyncValidationForm from './SyncValidationForm'
<SyncValidationForm onSubmit={(values)=>console.log(values)} />

Would so much appreciate any help!

Have exactly same issue, it becomes valid, after 2 consecutive resets, and can be submitted, even though it's empty

I'm meeting same problem


sh

use java.util.HashMap
hm! = new HashMap()
hm!.pu

Check if we have parameter information from java already.
See also  #47

@StephanWald
Works almost the same way as for #47.
Return type is also shown.


Hover animation on cards

Closes #11
Changes proposed
Added hover animation on cards in explore section
Screenshots
https://github.com/Nishitbaria/OpenGrame/assets/113261155/531d8536-d067-4e93-a06c-6ef1e0e84083

Hey @raghavawasthi24 please take reference from here: https://tailwindcomponents.com/component/card-with-hover-animation
I want this type of card hover Effect

@Nishitbaria I have changed hover effect as refrenced.

@Nishitbaria I have changed the hover effect as referenced.

Good work  @raghavawasthi24  ✨

@Nishitbaria I think you forget to label this PR with gssoc?


229/buffer update -- Changed OniNotifyBufferUpdate

Sorry for the dud PR from before.
This is a short and simple one, I just added some logic in init.vim to only send relevant parts of the buffer when updating

Thanks for looking at this, @bert88sta !
There's a few things I'm not sure how they will work with this PR:

Right now, when we receive the buffer_update event in UI (which happens in NeovimInstance.ts), it emits an event where the listeners expect all the buffer lines. We might have to add some context around which line numbers we are sending, in the case we send a subset. Right now we just send an array of lines, but maybe we should send something like { startLine, endLine, array of lines that changed }

It doesn't look like we're ever sending the full contents over. I'm thinking that, for the first change, we'd send over the entire file, but then, for incremental changes, we'd send over only the lines that changed, something like.

@extr0py I've been using this for a little bit now and haven't managed to break anything, but I'll try to get into it and make the appropriate changes

The sort of issues you'd see here would be that completion or quick info might not work as expected.
You might want to try setting a breakpoint in vim\core\oni-plugin-typescript\src\index.ts in the Oni.on("buffer-update", ...) section, around line 255 - and check out the buffer being passed in. It looks like what would happen here is that we'd only send a subset of the current file, but we'd be telling the language service provider that it is the whole file.
A scenario to try might be to open up NeovimInstance.ts and try typing Neov at the top and see if you get that completion picked up - I would guess it may not come up, because that wouldn't be in the buffer.

@extr0py : I've definitely been able to find some of the glitchy cases here. I think this is going to have to go hand in hand with the adding of the Change event for TS Language Server.

Sounds good - thanks for the update


Added OpenShot Video Editor

Adding a new cask, OpenShot Video Editor

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[ ] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

I wasn't sure if I should use openshot-video-editor as the token, or just openshot. Since the DMG was named openshot, and thats also the websites URL, I decided to just use openshot. If I was wrong, I can easily fix it. Also, I know brew and brew cask often don't accept betas, but this software has been in beta for awhile and is for the most part, stable.

The token referenced (you checked the box) is explicit: the name of the app is what matters. The longer nane is the correct one.
We have no problems with betas in the main repo if there exists no stable version (search the docs for “finding a home for your cask”).

Thank you for the contribution. It needed some fixes, so they were made in b8c07fe14f64f078c180951df5eb7d33f97899f1. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Crash (SIGSEGV) in ServerInterface::Shutdown() of Synchronous gRPC server, Linux, C++

What version of gRPC and what language are you using?
C++, gRPC version: commit 5d57a8d09a7f7202ba8eaa56b3b88a5da05ad057 (tag: v1.13.0)
What operating system (Linux, Windows,...) and version?
Linux, Ubuntu 16.04.6 LTS
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc version: 7.3.0
What did you do?
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
We have written a synchronous gRPC service implementing the gNMI service.
We are trying to test this service interface in a c++ gTest.

Create and start an instance of the gRPC/gNMI service
Do the tests
Stop the gRPC/gNMI service, by calling ServerInterface::Shutdown()

What did you expect to see?
gRPC/gNMI service should shutdown fine and the test should pass.
What did you see instead?
The test fails intermittently about 5 times in 100 times, a SIGSEGV is thrown from Shutdown(), here is the back trace:
Core was generated by `bazel-bin/devmgr/devmgr_gnmi_test --gtest_repeat=100'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f251ddbe3d7 in gpr_unref ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs$
Uh10_Sx86_U64_Susr_Slib/libgpr.so.6
[Current thread is 1 (LWP 29583)]
warning: File "/var/cache/tarana/releases/TCN.A3.H10.XXX.0.410.000.00/host/x86_64/x86_64-tarana-linux-gnu/x86_64-tarana-linux-gnu/sysroot/lib/libstdc++.so.6.0.24-gdb.py" auto-loading has
been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
(gdb) bt
#0  0x00007f251ddbe3d7 in gpr_unref ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs$
Uh10_Sx86_U64_Susr_Slib/libgpr.so.6
#1  0x00007f251dcc99c0 in grpc_error_unref(grpc_error*) ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs$
Uh10_Sx86_U64_Susr_Slib/libgrpc++_cronet.so.1
#2  0x00007f251dcc9a1e in grpc_error_unref(grpc_error*) ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs$
Uh10_Sx86_U64_Susr_Slib/libgrpc++_cronet.so.1
#3  0x00007f251dcc9a1e in grpc_error_unref(grpc_error*) ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs$
Uh10_Sx86_U64_Susr_Slib/libgrpc++_cronet.so.1
#4  0x00007f251dcd4d09 in grpc_core::ExecCtx::Flush() ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs_
Uh10_Sx86_U64_Susr_Slib/libgrpc++_cronet.so.1
#5  0x00007f251dcf5f6c in grpc_server_shutdown_and_notify ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs_
Uh10_Sx86_U64_Susr_Slib/libgrpc++_cronet.so.1
#6  0x00007f251dd9e8e8 in grpc::Server::ShutdownInternal(gpr_timespec) ()
   from /var/tmp/prasanta.behera/dff6c68026f1f353/cpu/applications/bazel_output_base/execroot/cap/bazel-out/k8-opt-bn_h10/bin/devmgr/../_solib_k8/_U@cfs_Uh10_S_S_Cgrpc++___Uexternal_Scfs_
Uh10_Sx86_U64_Susr_Slib/libgrpc++.so.1
#7  0x00007f251f19155f in grpc::ServerInterface::Shutdown<std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l,<PHONE_NUMBER>l> > > > (
    deadline=..., this=0x19c69b0) at external/cfs_h10/x86_64/usr/include/grpcpp/impl/codegen/server_interface.h:63
#8  cmf::SyncService::Stop (this=0x19bc440) at cmf/sync_service.cpp:114
#9  0x00000000004d3c25 in void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) ()
#10 0x00000000004ce422 in void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) ()
#11 0x00000000004b4409 in testing::Test::Run() ()
#12 0x00000000004b4c28 in testing::TestInfo::Run() ()
#13 0x00000000004b524d in testing::TestCase::Run() ()
#14 0x00000000004bbb13 in testing::internal::UnitTestImpl::RunAllTests() ()
#15 0x00000000004d4c35 in bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::
UnitTestImpl::*)(), char const*) ()
#16 0x00000000004cf16e in bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::Uni
tTestImpl::*)(), char const*) ()
#17 0x00000000004ba844 in testing::UnitTest::Run() ()
#18 0x0000000000490620 in RUN_ALL_TESTS () at external/cfs_h10/x86_64/usr/include/gtest/gtest.h:2233
#19 main (argc=<optimized out>, argv=0x7fff99aaec48) at devmgr/device_manager_gnmi_test.cpp:194

Anything else we should know about your project / environment?

We have also tried Shutdown with deadline, ServerInterface::Shutdown(const T &deadline) but still not able get around the crash.
We use bazel to build our c++ code inside a docker instance running Linux (Ubuntu 16.04.6 LTS)

pkbehera@ - can you try the latest gRPC version and see if this issue is reproducible? will help us narrow down the issue.

No response from user, assuming stale.


Messages are not loading for new users if user not allowed for notification permission

Hi, I am using applozic in my iOS app, When a user signup in my app we will send him a message trough Applozic admin API's.
this works fine if the user allows permission for push notifications.
If user don't allow permission for push notifications and signup in my app, the messages are not loading in applozic chat.
I have went inside the chat list page and refreshed but still, it shows no chats available until I restart my app or logout and login.
To Reproduce
-> signup with new number without allowing notification permission
-> Send a message from different number by keeping the app open OR send a message to that number by using admin API
-> It suppose to receive message because the SDK uses socket connection
-> Go to list of chats screen and refresh the page you will not be able to see the meesages

Hi @raviteja11b
We'll look into this.
Did you tried to reproduce this in our Sample Application?

We tried it in the latest version but we were not able to reproduce this.
Closing this, feel free to open this issue with more details.


fix(types): union function prop

Fix union typed function prop's type error.
Reproduction:
https://codesandbox.io/s/smoosh-cherry-q8rv1?file=/src/index.ts

@pikax

fix 3357

@HcySunYang Code is reviewed

Any progress?


Custom /404/index.html location

[x] This is a question about using the theme.

As I am using firebase for hosting, it requires me to place my custom 404 page on the root directory itself named 404.html. Currently it is being generated on /404/index.html instead. May I know how should I go about customising the location?

Consult Jekyll's documentation about setting a page's permalink.
Closing as this isn't a theme issue.


react-scripts/node_modules/react-app-polyfill/jsdom.js not found

Discussed in https://github.com/facebook/create-react-app/discussions/12637

Originally posted by mkochman August  5, 2022
Hi 👋
I have a quite strange problem with jsdom. I get it on bitbucket CI:

Validation Error:
Module /opt/atlassian/pipelines/agent/build/node_modules/react-scripts/node_modules/react-app-polyfill/jsdom.js in the setupFiles option was not found.
 is: /opt/atlassian/pipelines/agent/build

I checked node_modules and react-scripts and I see in package.json dependency that react-app-polyfill is included but I don't see it in eact-scripts/node_modules 🤔
The code responsible for it is in file scripts/utils/createJestConfig.js
    setupFiles: [       isEjecting         ? 'react-app-polyfill/jsdom'         : require.resolve('react-app-polyfill/jsdom'),     ],
I tried to overwrite setupFiles or use separate install of react-app-polyfill but without any success :(
My package.json:

"devDependencies": {
"@babel/cli": "^7.15.7",
"@babel/core": "^7.18.10",
"@babel/eslint-parser": "^7.17.0",
"@babel/preset-env": "^7.18.10",
"@babel/preset-typescript": "^7.18.6",
"@playwright/test": "^1.23.1",
"@types/jest": "^27.4.1",
<EMAIL_ADDRESS>"^4.4.6",
"@types/node": "^14.14.16",
"@types/react": "^17.0.2",
"@types/react-dom": "^17.0.2",
"@types/uuid": "^8.3.4",
"@wojtekmaj/enzyme-adapter-react-17": "^0.6.2",
"babel-plugin-transform-inline-environment-variables": "^0.4.4",
"chromedriver": "^93.0.0",
"edgedriver": "^4.17134.1",
"enzyme": "^3.11.0",
"enzyme-to-json": "^3.4.3",
"eslint": "^8.15.0",
"geckodriver": "^3.0.1",
"jest-junit": "^14.0.0",
"jest-watch-typeahead": "^2.0.0",
"mini-css-extract-plugin": "^2.6.1",
"pdfkit": "^0.11.0",
"pretty-format": "^28.1.3",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-scripts": "^5.0.1",
"rimraf": "^2.6.3",
"sass": "^1.51.0",
"sass-loader": "^13.0.2",
"selenium-webdriver": "^4.0.0-alpha.5",
"ts-loader": "^8.2.0",
"typescript": "^4.6.4",
"webpack-cli": "^4.10.0",
"webpack-node-externals": "^3.0.0"
},
"dependencies": {
"bowser": "^2.11.0",
"date-fns": "^1.30.1",
"lodash.get": "^4.4.2",
"prop-types": "^15.7.2",
"react-app-polyfill": "^3.0.0",
"resize-observer-polyfill": "^1.5.1",
"uuid": "^8.3.2"
},
"peerDependencies": {
"react": ">= 16.6.0 < 18.2",
"react-dom": ">= 16.6.0 < 18.2"
},

Maybe it is a problem with library versions? Or maybe with configuration?
I will be grateful for help.

I just ran into this issue in our CI environment as well.

For what it's worth, I was able to resolve this in my environment by down-grading the version of NPM I was using. The package-lock was getting created with NPM 6; I was using NPM 8.

I was using before version NPM 6 too, but I had to update it to NPM 8 because I had an issue after project libs update and to resolve it I had to upgrade node.


Installation to minikube does not complete

When following the instructions within quickstart using minikube, installation job is terminated within metrics server step. It gives certification error.
Solution advice from Maurice:

command:
- /metrics-server
- --kubelet-insecure-tls
- --kubelet-preferred-address-types=InternalIP

so the way to override that in otomi is this config snippet:
apps:
  metrics-server:
    enabled: true
    _rawValues:
      extraArgs:
        kubelet-preferred-address-types: InternalIP
        kubelet-insecure-tls: true

If otomi-core/values-schema.yamlis modified then kubelet-insecure-tls will be true for all vendors. Instead we would like it to be active in only minikube right? So is this to be written conditionally to otomoi-core/values/metrics-server.gotmpl

I will add this as a known issue to the docs on otomi.io

@leiarenee , sounds  good
Why did you close it Sander ?


upgrading to 0.11.0 broken

Hello,
I just wanted to let you know that doing a pack_install(clpBNR). or pack_upgrade(clpBNR). in swi-prolog will upgrade clpBNR to the version 0.11.0 and fails to load with the following error:
?- use_module(library(clpBNR)).
ERROR: /home/kwon-young/.local/share/swi-prolog/pack/clpBNR/prolog/clpBNR.pl:29:
ERROR:    Domain error: `module_header' expected, found `:-print_message(error,history(expande
d("This version of clpBNR requires SWIP 9.1.5 or greater")))'

Since version 0.11.0 has no release on github, I suppose the fact that it is available on swi-prolog.org is an error.

Oh, that's right. I'm using SWIP 9.0.4 on fedora 38.
Previous version would generate a message so I assumed i was something else.


attr_reader: for the queue

Dear all,
We have an issue that we have to re-enqueue the sidekiq-cron jobs on every deploy because there could be some new. While runtime we create dynamically new cronable jobs, they are deleted because we reload all of them (as written above). We have implemented a kind of hack that stores these dynamically created jobs on deploy and puts them back afterwards.
The problem is, that we cannot access the queue we have defined for these jobs (except, job.instance_variable_get....) would you agree to create an attribute reader for the queue?
Or doesn't it make any sense to you?
Here is an example
https://gist.github.com/tfluehmann/8807ce5d4ada60c57a39ddbbb9c131d5
Thx

@tfluehmann you should not use
Sidekiq::Cron::Job#load_from_hash! hash
Sidekiq::Cron::Job#load_from_array! array

when you use not bang method, it will not remove anything, it will just update jobs you are setting up so it will work afterwards with your dynamically added cronable jobs.


Create table directly from Hash

It would be great to add support for data saved in array of hash. Eg:
users = [
  { name: "Foo", city: "XYZ", admin: true },
  { name: "Bar", zip: 987654, city: "ABC"}
]

table = TTY::Table.new(users)
renderer = TTY::Table::Renderer::Unicode.new(table)
renderer.render

Output:
#  ┌─────┬───────┬─────┬─────┐
#  │name │zip    │city │admin│
#  ├─────┼───────┼─────┼─────┤
#  │Foo  │       │XYZ  │✔    │
#  │Bar  │987654 │ABC  │     │
#  └─────┴───────┴─────┴─────┘

Current implementation expects each header to have value defined for each row. If values are not available then it is to be replaced by nil. For above example sample input would be:
users = [ {
  name:  ["Foo", "Bar"],
  zip:   [nil, 987654],
  city:  ["XYZ", "ABC"],
  admin: [true, nil]
} ]

I can submit a PR if required.

Hi @vaibhavatul47; if you have a patch for this completed already, let me know - otherwise I may tackle this.

I know this is old, but @vaibhavatul47 this would be super nice to have :)

No change to the library is required.  It has established its contract w/r/t its API.  Just convert your data to match the contract like this:
#!/usr/bin/env ruby
# convert_hash_to_data.rb

require 'tty-table'

headers = [:key1, :key2, :key3]

array_of_hashes = [
  {
    key1: 'one',
    key2: 'two'
  },
  {
    key1: 'one',
    key2: 'two',
    key3: 'three'
  },
  {
    key2: 'two',
    key3: 'three'
  },
  {
    key3: 'three'
  }
]

def convert_hash_to_data(headers, array_of_hashes)
  data = []
  array_of_hashes.each do |entry|
    row = []
    headers.each do |key|
      row << entry[key]
    end
    data << row
  end

  data
end

data = convert_hash_to_data(headers, array_of_hashes)

table = TTY::Table.new(headers, data)
puts table

__END__

produces this output ...

key1 key2 key3
one  two
one  two  three
     two  three
          three


Set clean start property on application / node connect with MQTTv5.

In the Sparkplug IIOT standard, version 3.0, the host application must set the clean start property = true and session expiry interval = 0 for MQTT v5.0 on connect.

Waiting for https://github.com/dotnet/MQTTnet/issues/1710.

Basically started in https://github.com/SeppPenner/SparkplugNet/commit/1c04efd0d5deda0ea79dd5ef2b33e455ee07bee6, waiting for reply to set options for MQTT v5.0.

Use WithCleanStart method when available in release build.


Unable to read the license file LICENSE for the spec `SwiftAudioEx (0.13.2)-IOS

Describe the bug
I encountered the above problem when pod install
"react-native": "0.64.1"
"react-native-track-player": "^2.0.3"

same here

Did anyone come up with a solution for this yet?

Same here

same here

Thanks all. This should be resolved via https://github.com/DoubleSymmetry/react-native-track-player/issues/1248#issuecomment-942025812
Can you test and confirm? @jr00n @thebuddha @shawnFallon @IacoCesar @bralandealmeida


Update site header to LeadsForce

This PR fixes some formatting issues in DG and UG.
Tips:
Make sure to run ./.github/run-checks.sh before pushing

Codecov Report

Merging #27 (5fc2a9e) into master (b11317c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #27   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 b11317c...5fc2a9e. Read the comment docs.


Users presented with macOS Sonoma even if it's deferred

Users are presented with an upgrade to macOS Sonoma option through SupportApp even though an MDM based deferral policy is in place and enforced. Users who click on the version are navigated to System Settings however no upgrade is available due to this deferral policy.

same her...need a fix for this. THX

I can only support this request. It is very unfortune from a users perspective that an alert / notification is displayed, but no update can be installed. I understand that the cause of the alert / notification are the preferences of softwareupdate, which show the update even though it is deferred, but a solution would be cool.

As a workaround, we are now using key config key HideMajorUpdates. While an automatic solution would be easier to handle, this is still a good help for us at the moment.

Hi, please refer to the documentation and search for HideMajorUpdates. This is the current way (same a last year) to hide the new major macOS version. The app looks at this preference domain /Library/Preferences/com.apple.SoftwareUpdate.plist and nothing is in there to detect the configured deferral and all updates (even deferred) are shown in this plist. Open to any suggestions if anyone was able to find the available updates as shown in System Settings.

We just have submitted a feedback to apple that an API to query updates as visible in system settings is needed and we will also open an enterprise care ticket for this issue.

HideMajorUpdates key is not working for me. I haven’t announced this feature to my users, but eventually someone is going to notice the red pip

Resolved with v2.5.1 and HideMajorUpdates no longer needed


Uncaught TypeError: Cannot read property 'super' of undefined

[Enter steps to reproduce below:]
Using V4 preview

Click the cogwheel on minimap

Atom Version: 0.165.0
System: linux 3.13.0-39-generic
Thrown From: minimap package, v3.5.3
Stack Trace
Uncaught TypeError: Cannot read property 'super' of undefined
At /home/alexo/.atom/packages/minimap/lib/minimap-quick-settings-view.coffee:3

TypeError: Cannot read property '__super__' of undefined
  at Object.<anonymous> (/home/alexo/.atom/packages/minimap/lib/minimap-quick-settings-view.coffee:3:9)
  at Object.<anonymous> (/home/alexo/.atom/packages/minimap/lib/minimap-quick-settings-view.coffee:1:1)
  at Module._compile (module.js:468:26)
  at Object.requireCoffeeScript [as .coffee] (/opt/atom/resources/app/src/coffee-cache.js:61:19)
  at Module.load (/opt/atom/resources/app/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:318:12)
  at Module.require (module.js:373:17)
  at require (module.js:392:17)
  at HTMLDivElement.<anonymous> (/home/alexo/.atom/packages/minimap/lib/minimap-element.coffee:169:37)

Commands
     -0:00.0 settings-view:open (atom-text-editor.editor)

Config
{
  "core": {
    "useReactEditor": true,
    "themes": [
      "seti-ui",
      "seti-syntax"
    ],
    "disabledPackages": [
      "tabs",
      "tree-view",
      "symbols-view",
      "minimap-find-and-replace"
    ]
  },
  "minimap": {
    "plugins": {
      "highlight-selected": true,
      "find-and-replace": true,
      "git-diff": true
    },
    "v4Preview": true
  }
}

Installed Packages
# User
atom-ctags, v2.5.5
autocomplete-plus, v1.1.0
blackspace, v1.0.0
build, v0.22.1
editor-stats, v0.16.0
git-log, v0.2.0
highlight-selected, v0.7.0
language-actionscript, v0.1.0
language-ini, v1.3.0
linter, v0.9.1
linter-jscs, v1.4.9
linter-jshint, v0.1.0
linter-php, v0.0.11
minimap, v3.5.3
minimap-git-diff, v3.1.0
minimap-highlight-selected, v3.1.0
seti-syntax, v0.2.1
seti-ui, v0.5.1
sublime-tabs, v0.4.8
symbols-tree-view, v0.3.2

# Dev
No dev packages

/cc @atom/core

Looks like there's a trouble with your installation, atom-space-pen-views should be installed with the package. Can you confirm the module is properly installed in the node_modules directory of the package?

I'm not seeing the issue any more. It is likely it had something to do with https://github.com/atom/atom-space-pen-views/issues/5.
When atom-space-pen-views was fixed, the issue disappeared for me. I'm closing this for now.


turn off the plugin in background mode

Is it possible to turn off the plugin in background mode without opening the app? For example, I want it to stop tracking when a trip ends.

You are free to call .stop() whenever you wish.

Even if the app is closed? In my case, it is configured to call with the app closed and tracking on, but it does not execute the stop.

but it does not execute the stop.

Then your own function, where you are calling .stop(), is not being executed.  When .stop() is called, the plugin stops.

I created with headless, a Java class that stop the plugin when the trip is end. Thank you


An easy way to download full collection

An OPDS feed is available which you can use in an ereader to download the collection: https://standardebooks.org/opds/
Right now I would rather not script a download of the entire corpus because bandwidth is still limited.

An OPDS feed is available which you can use in an ereader to download the collection: https://standardebooks.org/opds/

I never used an opds feed in my kindle before, could you please tell me how I can do that?

I'm not sure, but that would be a good question for the mailing list, or a Google search to see if it's possible.

Thought you knew this was possible in the eink reader by how you said it
above...
Anyway, I will create an script do to it automatically in my system out of
the file.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120745

TagBot fix

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/121120


Error when building from source.

❓ Questions and Help
Hello i am having the following error when building from source (see log). can someone help me resolve it ?
the steps to reproduce this error are same as those in the guide on git.
log.txt

That is an issue with git updating the submodules.  It seems like you made changes to the submodules.  Please revert those