text:
Dependency with CG OpenMM

After our sub-group meeting on 7/2 we decided that we would like foldamers to not depend on CG OpenMM, to remove the circlular dependency of these two repos. If they both depend on each other then they would be better suited being a single repo.
To this end, let's discuss how we can go about removing the CG OpenMM dependencies in foldamers here.

I went through and found these dependencies of foldamers on CG_Openmm functions. Headers are CG_Openmm functions, and bullets are foldamers functions which depend on them: I haven't done the examples yet because a lot of them are doing both the running of the simulation and the analysis at the moment.
build.cg_build.add_new_elements()

Used in cgmodel.CGModel.__init__

build.cg_build.build_topology()

Used in cgmodel.CGModel.__init__
Used in utilities.utils.get_random_positions

build.cg_build.build_system()

Used in cgmodel.CGModel.__init__
Used in utilities.utils.get_structure_from_library
Used in utilities.utils.get_random_positions

simulation.rep_exch.run_replica_exchange()

Used in ensembles.ens_build.get_nonnative_ensemble

simulation.tools.minimize_structure()

Used in parameters.optimize.optimize_parameter
Used in utilities.utils.get_structure_from_library
Used in utilities.utils.get_random_positions

simulation.tools.build_mm_simulation()

Used in ensembles.ens_build.get_ensemble_data
Used in ensembles.ens_build.get_nonnative_ensemble
Used in ensembles.ens_build.get_native_ensemble

utilities.iotools.get_topology_from_pdbfile()

Used in utilities.utils.get_structure_from_library

utilities.iotools.get_positions_from_pdbfile()

Used in utilities.utils.get_structure_from_library

utilities.iotools.read_pdbfile()

Used in ensembles.ens_build.get_ensemble_data

utilities.iotools.write_pdbfile_without_topology()

Used in ensembles.cluster.get_cluster_medoid_positions
Used in ensembles.ens_build.write_ensemble_pdb
Used in parameters.secondary_structure.get_helical_parameters
Used in utilities.utils.get_structure_from_library

I think one change we could make is to move the pdb read and write functions to foldamers, since we are building the random structures in foldamers.
That brings up the question, should the random builder instead be in cg_openmm, if we want foldamers to be for strictly analysis?

OK, so let's analyze the cg_openmm functions (this is still in progress, had to stop).  A lot of the use of cg_openmm functions appears to be to remove any dependency of simtk.openmm  from foldamers.
cg_openmm

build.cg_build.add_new_elements() - this adds elements to the list of openmm element types, I believe so it won't get confused by having atoms that aren't elements.  The way to remove it would be to add the elements only when the OpenMM object is actually constructed.  seems like this should work, would have to be tested.

build.cg_build.build_topology() - this reads the positions from a pdb, and store the positions in the OpenMM object, and creates the openmm Topology.  It's a little weird, since it reads from a pdb that is produced earlier currently, rather than building from a pdb. Probably because it's realtively easy to create an OpenMM object from a pdb.  The cleanest way to avoid calling openmm object until a simulation is going to be run, so that the attachment of positions is done later.   However, simtk.openmm.app.pdbfile is used to read the pdb files.  I don't think we want to make our own PDB parser, so maybe we just accept that foldamers will depend on simtk.openmm.   Still trying to figure out the dependencies here, will come back.

build.cg_build.build_system() - creates the OpenMM system.  Obviously needs OpenMM.  Needed to run a simulation, so required by any build tools that calculate energies.  Could potentially be run in a second step after the topology is created, but before the simulation is done.

utilities.iotools.write_pdbfile_without_topology()

I don't currently see any functions that use OpenMM here, so this would be easy to move to foldamers.
Looking at some of the foldamer functions that use these:

utilities.utils.get_structure_from_library. This is doing some minimization, so will require OpenMM and therefore cg_openmm.  Should this be moved to cg_openmm?

ens_build functions.  This is actually a split between functions that generate and ensemble, and those that create an ensemble.  I think that this can likely be split apart into functions doing different things, will have to look more closely later.

parameters/ functions.

parameters.optimize.optimize_parameter, involves calculating energies with new topologies, so probably shouldn't be there.
parameters.secondary_structure.get_helical_parameters: just involved PDB writing, so would be fine if that was moved.

I think we dealt with this in the cg_openmm/foldamers merge.

authors: cwalker7 mrshirts tlfobe

repo: shirtsgroup/foldamers


text:
Update couchbase@8.0

Build couchbase@8.0

:beers: @BrewTestBot has triggered a merge.

source: gharchive/pull-request

repo: shivammathur/homebrew-extensions

license: MIT

license_type: permissive

license_source: github-api


text:
Update php@7.3-zts

Build php@7.3-zts

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-php


text:
Update php@7.2

Build php@7.2

:beers: @BrewTestBot has triggered a merge.


text:
Unable to load dynamic library 'mailparse.so'

Describe the bug
PHP Warning:  PHP Startup: Unable to load dynamic library 'mailparse.so' (tried: /usr/lib/php/20190902/mailparse.so (/usr/lib/php/20190902/mailparse.so: undefined symbol: mbfl_convert_filter_flush), /usr/lib/php/20190902/mailparse.so.so (/usr/lib/php/20190902/mailparse.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0
Mailparse must be loaded after mbstring.
mbstring seems already loaded by default. Is there a way to set the order?

@ThomasTr I'm unable to reproduce the error. Here is a test workflow and mailparse installs without any errors: https://github.com/shivammathur/test-setup-php/actions/runs/74589000/workflow
Please provide the yml of the workflow you have so that I can reproduce the error.

@shivammathur thanks for investigating, setting mbstring explizit seems to work (thought it was enabled by default)

source: gharchive/issue

authors: ThomasTr shivammathur

repo: shivammathur/setup-php


text:
Add output of reaction rate

Can we also output the daily "reaction rate" from each pool/zone, so we can have a quick check on reaction? Maybe it is worth a separate output file, as we may have multiple minerals and each mineral have at least two reaction rates from "UZ" and "LZ" zones?

What do you mean by reaction rate? Change of concentration of each species caused by reaction?

What do you mean by reaction rate? Change of concentration of each species caused by reaction?

yes, specifically, I guess daily "reaction rate" [mol/d] could make more sense. Not the rate constant k, but the actual daily reaction rate under the effects of soil moisture and temperature.

Hi, Yuning:
Just use the following equation to calculate the daily reaction rate: let's for C_t is the mineral concentration [mol/L-poroous medium] at the time of t day.
So the reaction rate is for the t day is: (C_t - C_t-1) [mol/L-poroous medium] * V [m3] * porosity [m3/m3] * 1000

@WeiZhiWater What V should we use? So reaction rate is not per unit volume?

That's a good question. I tended to look at the whole watershed reaction rate (not comparing reaction rate in each grid). It is more useful when we are expecting the changed reaction rate by changing its rate constant, soil moisture/temperature function, or just quantifying the contribution of reaction rate by each zone (shallow GW, deep GW). So I think the whole reaction rate over the unit (or sub-catchment) is more useful? So V probably should be the total volume of each zone (shallow GW, deep GW) over the unit (or sub-catchment). What do you think?

Or is it the catchment (or sub-catchment) are not defined in the HBV?

@WeiZhiWater It is not being used when you have only one sub-catchment. Everything is depth based.

Then perhaps we have to use the depth and output reaction rate in the unit of mol/m2/d. I think we can use this.

Should I use total concentration or primary concentration?

I think we should target the solid phase for outputting their reaction rates. That means, to use the total concentration since the solid-phase won't have speciation (total concentration should be equal to primary concentration).

Thanks, @WeiZhiWater . I am not sure what the purpose of the printed reaction rate is. If it is to check if the change of concentration is OK, shouldn't we just use mol/L/d? Perhaps I didn't understand this correctly.

I think it is easier to do a self-check. For example, 1) check the mass balance of chemical reaction, the released chemicals from solid-phase vs. discharged and stored mass in streamflow and soil/gw water; 2) I guess would be easier to track how reaction and environmental conditions works, for example, is reaction happening as I would expect. For example, a double rate constant is expected to release 2x more solutes into water phase, but the concentration may not be doubled (due to water storage changes). But from the reaction output, at least, we know the system (reaction) is working properly, just need to check on other factors.

authors: WeiZhiWater shiyuning

repo: shiyuning/HBV-BioRT


text:
Use Admin Framework from CounterStrikeSharp

CounterStrikeSharp has introduced an Admin Framework which supports admins and flags similar to SourceMod, removing the need to have an admin file for every plugin.
Could you please update your plugin to use this new system so we don't have to have an individual admin file for your plugin.

Hey!
I will surely update my plugin to use the new admin system, I'll check what all changes I have to make because there are already a lot of admin commands

+1 this would be great!

@shobhit-pathak I believe we can use the whitelist system with CSSharp too, right?
In other words, do players who have the CSSharp admin flag automatically enter the Whitelist?

@crashzk Yes I think this can be done, but I was still not able to explore the admin system of CSSharp, because there are already a lot of admin commands and checks in MatchZy which I will have to update :P

Definitely a big +1 for me on more granular admin settings.
I'd bite the bullet and make this a priority because the more commands you add the longer it's going to take to implement.
And if I could add a suggestion:
.map and .prac and probably .exitprac should be grouped together under the map change admin group (@css/changemap)
All other match commands should be separated into cfg change (@css/config)
This would mean that more junior members of a team could join and change the map and practise without having the ability to affect matches.

Yeah that makes sense, I think at this point I should start focusing on using CSSharp's admin framework and pause the other developments for a while. Because as you said, the more commands I add, the longer its going to take to implement CSSharp's admin system.

I know CS2Rcon has a lot less functionality than your plugin, but this is the commit where they changed from their own admin system to CSSharp's and as you can see it cleaned up a lot of their code!

@shobhit-pathak first of all, thank you for this resource, testing it here now.
Just an observation, I noticed in this case that it would be the @css/generic flag for all commands that need to be admin, right?
If so, in the future I believe that an improvement to this feature would be interesting, that is, each admin command has a flag that we can configure which one to use.
Example:

If I want to leave the .prac, .exitprac commands only for admin with the @css/root flag.
.rcon command only for those who have the @css/rcon flag

And so on.

@crashzk the @css/generic flag is needed to make a player an admin. Without it other flags won't work.

@crashzk forget what I said above, that's how source mod works.
The @css/generic sets a player as admin. No other flags do anything.

@shobhit-pathak I'm not sure this should be closed.
Sure it allows admins to be added for CSSharp but it's just an all or nothing approach. All admins have full access to all admin protected commands.
That's not really how the CSSharp system was designed to be used.

authors: ChocOranger crashzk drakin001 kus shobhit-pathak

repo: shobhit-pathak/MatchZy


text:
admins with @css/root don't work, but @css/generic does

with my admin file setup like so
{
  "ar1a": {
    "identity": "76561198199062669",
    "flags": ["@css/root"]
  }
}

matchzy doesn't recognize me as an admin, if i change it to @css/generic, it does

Hey!
This is because @css/generic flag is required for MatchZy admin. All the admin commands currently fall under the @css/generic flag only.
Discussion for adding granular support is going on here: https://github.com/shobhit-pathak/MatchZy/issues/33

From my understanding of the docs, @css/root should grant you all flags, including @css/generic

Thanks for pointing it out, I might have missed it!
I'm working on improving the admin system, currently I had used a workaround to detect an admin. But now I'll use the proper way to define the admin commands :D

There is also a discussion about the @css/root flag here: https://github.com/roflmuffin/CounterStrikeSharp/issues/125
If it is implemented, I believe it will solve this problem,

that explains all the confusion!
On Sat, Nov 25, 2023, 11:20 AM crashzk @.***> wrote:

There is also a discussion about the @css/root flag here:
roflmuffin/CounterStrikeSharp#125
https://github.com/roflmuffin/CounterStrikeSharp/issues/125
If it is implemented, I believe it will solve this problem,
—
Reply to this email directly, view it on GitHub
https://github.com/shobhit-pathak/MatchZy/issues/37#issuecomment-1826200652,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACALSJYRXIW57YIINOKOCETYGFPYRAVCNFSM6AAAAAA7VVRUUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGIYDANRVGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey!
This has been fixed in the 0.4.3-alpha release, thanks! :D

authors: ar1a crashzk shobhit-pathak


text:
Music organization (kog patch 20)

readme created audio folders
rearranged the audio files
changed readme for general instructions of the game

It is.

I've fixed the readme title


text:
(OSX) High CPU usage

The CPU usage on El Capitan is always around 160 / 170%. I thought it was indexing my system or something but after leaving it open for a day, still no improvement.

Typing a command also goes quite slowly, probably a side effect of the high CPU usage.

Does it happen all the time?

If somebody else has the same issue, please leave a comment.

Will update to the latest version and will package again. I'll repost asap.

Ok, the latest version does not seem to be impacted anymore. Weird, had this happen on a few versions so I was losing hope :D. Now it is usable again! Thanks for all your hard work.

@shockone
It seems to happen to me when I split my view.

When I close the splits, it becomes normal again.

authors: kevin-smets luco shockone

repo: shockone/black-screen

license: mit

license_source: bigquery


text:
Cannot cd (change directory) to directory with name that contains spaces

Using the latest code on master, I cannot cd to a directory that contains spaces in it's name.
For example, if my current working directory is /Users/adchilds/Desktop/ and I have a directory inside my cwd named "Desktop Items" I receive an error saying this directory cannot be found. See the following screenshot:

This looks to be caused by the fact that when we parse the path in the Common#resolveFile function, we're preserving escape characters such as \ in the path when we really should be getting rid of them.
I have a fix and want to submit a pull-request for this but would appreciate some scrutiny since I'm not entirely familiar with how this may affect the application as a whole.
Thank you!

Fixed.

authors: adchilds shockone


text:
Admin - Customer-Detail - Addresses can't be changed

The Adresses can't be saved due to:
src\Administration\Resources\app\administration\src\module\sw-customer\view\sw-customer-detail-addresses\index.js - Line 215
Problem is, that the required properties aren't availabe within the entity 'customer_address'. Therefore folling error occurs within the getRequiredProperties function.
TypeError: Cannot read property 'forEach' of undefined
    at Object.getRequiredProperties

isValidAddress(address) {
            const requiredAddressFields = Entity.getRequiredProperties('customer_address');
            let isValid = true;

            isValid = requiredAddressFields.every((field) => {
                return required(address[field]);
            });

            return isValid;
        },

Thanks @rasgor for pointing this out! Here is a hotfix "plugin" that overrides the isValidAddress() function by returning true always. Makes the editing of customer adresses work:
https://github.com/binaermanufaktur/sw6-CustomerAddressHotFix

authors: binaermanufaktur rasgor

repo: shopware/platform


text:
Fix typos in review blocks

1. Why is this change necessary?
See https://github.com/shopware/platform/issues/2777
2. What does this change do, exactly?
See https://github.com/shopware/platform/issues/2777
3. Describe each step to reproduce the issue or behaviour.
See https://github.com/shopware/platform/issues/2777
4. Please link to the relevant issues (if any).
https://github.com/shopware/platform/issues/2777
5. Checklist

[x ] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-24212
Please use this issue to track the state of your pull request.

Thanks again for your contribution, your PR is finally merged! :tada: :blue_heart:

authors: keulinho shopwareBot wannevancamp


text:
Fixing some types and adjusting the wording (a bit).

1. Why is this change necessary?
To fix typos in the docs and make the reading experience a bit more pleasing.
2. What does this change do, exactly?
Change typos and wording in the Storefront docs.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

There are plenty of cases where the docs speak about the "Storefront", but the writing is mixed between lowercase and uppercase. Could you clarify that please? I found many more minor errors in the Storefront section of the docs and would like to fix them.
Thank you!

Hi @mikewink,
thanks for helping out with the documentation.
When talking about the "Storefront" in general it should be uppercase. It should only be lowercase when the docs talk about technical things like the app/storefront directory. So your fixes look fine to me. 👍
Best regards
Tobias

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-7520
Please use this issue to track the state of your pull request.

I have imported your pull request and it should be merged soon.
Thanks for your contribution. 🎉

authors: mikewink shopwareBot tobiasberge


text:
SW5->SW6 orders fail to migrate for SW5.7.5 and below

The field {{invoice_shipping_tax_rate}} was only introduced in SW5.7.6 but is used for all order converters, see:
[https://github.com/shopware/SwagMigrationAssistant/blob/30d805f78b9888b7865ab72b0742341b06b4cd6e/src/Profile/Shopware/Converter/OrderConverter.php#L259|https://github.com/shopware/SwagMigrationAssistant/blob/30d805f78b9888b7865ab72b0742341b06b4cd6e/src/Profile/Shopware/Converter/OrderConverter.php#L259|smart-link]
We need to change the implementation to allow the field to not be there.

[public] Shopware automated response: This issue is linked to the internal issue: MIG-1054
[created from MIG-1054, comment 494823]

repo: shopware/shopware


text:
Prevent smarty variable-leak

The Emotion Banner-Slider has a mechanism which uses a given images' thumbnails when available. If there is none available (not generated / folder doesn't generate thumbanils), the element won't get a srcset and sizes attribute.
The problem arises, when the first image, given to the banner-slider has thumbnails, but the second image has not. Due to the way smarty variable-scoping works, the variables $srcSet and $itemSet will get re-used, because they are not overridden outside of the {if $banner.thumbnails}.
1. Why is this change necessary?
In order to prevent this leak, we have to reset these both variables for every image.
2. What does this change do, exactly?
Reset the variables $srcSet and $itemSet for every media-element given to the banner-slider.
3. Describe each step to reproduce the issue or behaviour.

Add a Banner-Slider to a Shoppingworld
Add an Image to the banner-slider which has thumbnails
Add a second Image to the banner-slider which has no thumbnails (e.g. by creating a new sub-album of the "Einkaufswelten"-Album, which has no thumbnails configured)

The Frontend should now properly display the first image in the banner-slider. The second one however will be a copy of the first one, because the $srcSet variable leaked from the last {foreach}-run.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
None
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hi @screeny05, thank you very much for your contribution! 💙


text:
Readonly attributes in Backend

1. Why is this change necessary?
Sometimes you want to add a attribute that should not be editable for your users but still visible in backend. This allows to make that attribute be readonly.
2. What does this change do, exactly?
Adding a new attribute configuration option that marks that attribute as readonly. This setting is then used to disable the input field in extjs. Therefore changes by code are of course still possible
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
PR https://github.com/shopware/shopware/pull/1645
https://issues.shopware.com/issues/SW-21676
5. Which documentation changes (if any) need to be made because of this PR?
New option "readonly" for attribute cru(d).
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @pascalheidman-bedarf,
please re-add your migration. Tests are currently failing.

@shopwareBot migrations added, tests now run as they should

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-22943
Please use this issue to track the state of your pull request.

Hey @pascalheidman-bedarf,
thanks for your updated contribution!
Unfortunately there are still some bugs when using Datetime, Single- or Multiselection-attributes e.g. at the article detail window which need to be fixed before we can merge this PR.
Also, as you're using the readOnly instead of the disabled property now, there's no need to change the HtmlFieldHandler anymore as the readOnly property is already set in field. Please test your changes with each possible attribute type.
Though the other attribute types are already looking good at the article detail and article overview window. :blue_heart:

While all elements now work more or less, I feel like that the multi selection grid isn't the cleanest solution as there is no way to disable individual columns inside the grid (sorting & deleting). Those are set right in the initComponent() function.
I played a bit around with providing a setReadOnly() function (the Ext.form.FieldContainer component has none), but that is never invoked on itself and has the problem not being able to access the child elements in initComponent() - therefore you can't use it to create a valid initial state.
Any ideas?
Oh and Travis CI fails with a completely irrelevant file...

Hey @pascalheidman-bedarf,
you might want to try rebasing your PR to fix the Travis issues.
Also:
Where exactly do you still see issues with the readOnly attribute, can you please provide a more precise example of what's still broken?

@pascalheidman-bedarf ups, there went something wrong :wink:

@mitelg yeah... gladly I made a backup before. I feel like I will never get rebase right in the first try 😞
@shopwareBot the multi selection contains both the selection/search field as well as the grid with all selected elements. Former is easy as it is an real input but latter is a complex thing that has controls for ordering and deleting elements which can't disabled on the fly. It feels not complete to not being able to change their state later.

Hey @pascalheidman-bedarf,
first of all the Shopware.form.field.Grid has a property called allowSorting- just set this to false if the attribute is readOnly.
This will result in the Drag 'n Drop functionality to be dropped.
Also, you might want to prevent elements like the selection or the action-columns to be created in the first place, instead of hiding / disabling them afterwards.
Additionally you can set attributes via the products batch processing, thus we need you to also prevent that by removing that option from the dropdown.
Furthermore it would be cool to also prevent saving the attributes on the PHP side in the AttributeData Backend Controller (engine/Shopware/Bundle/AttributeBundle/Controllers/Backend/AttributeData.php).
Could you please change that as well? 🙈

@shopwareBot good point with the batch processing. I will take a look at it!
Regarding allowSorting: I played around with that property as well as allowDelete and allowAdd which will disable all those functionality. Only problem I have is that changing those later don't propagate to change the behaviour on the fly. Therefore trying to push all that changes down to their respective element now.

@shopwareBot the 5.6 branch isn't up to date is it?
Neither my local repo nor github find any missing commits and this would explain why shopware/engine/Shopware/Controllers/Backend/Analytics.php always fails in Travis CI

Hey @pascalheidman-bedarf,
why Shopware 5.6 though?
Just use the Shopware 5.5 Branch. :-)

I rebased to current 5.6 as there were some collisions as the code is quite old now ;)
Seems like there have been a database error @ travis so maybe someone can rerun those tests?

Hey @pascalheidman-bedarf,
its not a database issue. The doctrine entity manager is getting closed if a mysql error occured.
Can you fix the build?

@shopwareBot fixed the PR.
The migration wasn't working anymore as there was already another migration with the same class name.

Thanks for your Contribution! :blue_heart:

authors: mitelg pascalheidman-bedarf shopwareBot shyim


text:
Added plugin config element type button

Description
Please describe your pull request:

Why is it necessary? to allow buttons in plugin config form
Does it have side effects? no

Questions
Answers

BC breaks?
no

Tests pass?
yes

How to test?
Install attached LubischTest.zip

The docs for this are ready and only need to be edited because of the shopware version.
-> https://github.com/shopware/devdocs/pull/497
There is also a little fix for a notice with following warning in the MenuSynchronizer.
PHP Notice:  Undefined index: children in /home/vagrant/www/engine/Shopware/Components/Plugin/MenuSynchronizer.php on line 66
PHP Warning:  array_column() expects parameter 1 to be array, null given in /home/vagrant/www/engine/Shopware/Components/Plugin/MenuSynchronizer.php on line 66

After some time i saw that there is probably another solution for my little bugfix.
-> https://github.com/shopware/shopware/pull/938
Looking forward to remove mine if necessary.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-17631.
Please use this issue to track the state of your pull request.

thanks for your contribution @nlubisch  :+1:
I removed your bugfix for the MenuSynchronizer. everything else is scheduled

Thx :)

authors: mitelg nlubisch shopwareBot


text:
chore: remove walletconnect dapp

Why
Remove wallet connect dapp dependency, we're not using it

Seems like there is a conflict

authors: hirbod intergalacticspacehighway

repo: showtime-xyz/showtime-frontend


text:
Bower support

Please add bower support. Thanks.

Can't you do bower install shprink/ionic-native-transitions ?

Included in documentation of beta3

authors: NgYueHong shprink

repo: shprink/ionic-native-transitions


text:
White page showing after splash screen before app load

I have encountered this problem on ios app, today I use v1.7.0 development process, found a solution:
Add two lines In config.xml file to solve:
<preference name = "ShowSplashScreenSpinner" value = "false" />
<preference name = "AutoHideSplashScreen" value = "false" />

Reference Address:
http://forum.ionicframework.com/t/white-page-showing-after-splash-screen-before-app-load/2908/5

good job @mingxia !

Yes it's working also in my app for same problem

authors: mingxia shprink yogeshpatil143

repo: shprink/wordpress-hybrid-client


text:
adding new feature: typography art

Typography art is a Graphic Design Technique. It is made up by using letters and numbers.
Like others make a new python script of typography art and properly comment on it for understanding.

hey @shubhajeet1207
I would like to work on this. I was searching for algorithms/libraries that could be used to generate typography art. I guess it is not that simple.
I came across this blog - https://towardsdatascience.com/creating-typography-using-word-cloud-in-python-9652bd62fa69
but it looks like in order to use this, the image masks must be created first.
Do you have anything in your mind?

Hello, @aimanfatima I've gone through the blog that you mentioned in your query.  If you are interested in this issue I'll assign this to you and then you can go through that, there is no issue in doing this by applying Language Processing and the word cloud concept. But make you push your changes in a separate branch and follow the PR template.
Happy Contributing 😊

@shubhajeet1207 the method mentioned in the blog would be difficult to incorporate. Because it's first creating an image mask (with black and white portion from the image) using photoshop. And then on top of these image masks, texts are embedded using that word cloud concept.
I am looking for a better solution. I'd let you know if I find something.

@aimanfatima okay go ahead 👍🏻


text:
Final Corrections

Corrected and added 'All caught up' in Admin Profile Pages
Corrected overflow in feed card for email and category
Added icon to the notification
Corrected Student Resolved async code
Added Feed Card to the following pages -  Admin Pending, Admin Resolved, Student Filed

Edit: Changed Query for count of pending complaints in Admin Page


text:
Fix case sensitive import for logrus

This is causing issues in case-sensitive build tools like bazel.

Oh... Sorry, it appears I missed the notification. Merging in
Thank you for the the fix!

authors: prestonvanloon shyiko

repo: shyiko/kubesec


text:
isSymmetric assertion in LinearOSNS.cpp when running cylinder.py

Often in the debug build, I need to disable this assertion to run a model.  I think it is related to the NEDS inertia matrix.  For instance, on the current master, cylinder.py in MechanicsIO examples triggers this assertion during the first collision.  On the other hand cube.py and sphere.py do not.  So I think it is likely related to non-identity inertia matrices returned by Bullet's calculateLocalInertia.  Is there a way we can "correct" what is returned by Bullet through some kind of normalization?  Perhaps we should at least put some kind of assertion on the matrix returned by calculateLocalInertia to catch the problem closer to the source.
diff --git a/kernel/src/simulationTools/LinearOSNS.cpp b/kernel/src/simulationTools/LinearOSNS.cpp
index 6e3dd2a..172aed9 100644
--- a/kernel/src/simulationTools/LinearOSNS.cpp
+++ b/kernel/src/simulationTools/LinearOSNS.cpp
@@ -329,7 +329,7 @@ void LinearOSNS::computeDiagonalInteractionBlock(const InteractionsGraph::VDescr
       //      gemm(CblasNoTrans,CblasNoTrans,1.0,*leftInteractionBlock,*work,1.0,*currentInteractionBlock);
       //*currentInteractionBlock *=h;
       DEBUG_EXPR(currentInteractionBlock->display(););
-      assert(currentInteractionBlock->isSymmetric(1e-10));
+      //assert(currentInteractionBlock->isSymmetric(1e-10));

     }

On second glance, I don't see why the output from calculateLocalInertia is problematic.  It outputs a 3-vector which is assigned to the diagonal elements of the inertia matrix in NewtonEulerDS::setInertia(), which is then copied to the lower block of the  _I matrix.
In cylinder.py, the return value of calculateLocalInertia is 0.335068, 0.004802, 0.335068.
I am not entirely sure why this leads to a non-symmetric currentInteractionBlock in LinearOSNS::computeDiagonalInteractionBlock.

Very good remarks. We are still in trouble somewhere with the inertia treatment in Siconos when it comes from bullet or more generally from a special scaling.
The assertion check that the Delassus matrix W = H^T (M_h)^-1 H , with M_h = M+ h^2\theta^2 K, is symmetric.  Theoretically, it has to be a symmetric matrix. When there is no other internal forces, the term K comes from the linearization of the gyroscopic forces. It is a skew-symmetric term that causes a very bad conditioning in the matrix  M_h. Using LAPACK for computing W results in a non symmetric matrix.
Normally, removing K for a while, with setNullifyFGyr(True) should be fixed the problem. I have to continue to investigate other symplectic scheme for the rotation.

Fixed in 5aa10140edfc03058ec0b32412d4a95c8c99d032

repo: siconos/siconos


text:
Use full repository URL in package.json

This will make a link to the repo show up in the sidebar of https://www.npmjs.com/package/auto-install
Cool package!

@zeke I was just about to create the same PR. Makes it much easier to find from NPM. Maybe add homepage too?
"homepage": "https://github.com/siddharthkp/auto-install#readme",
"repository": {
   "type": "git",
   "url": "git://https://github.com/siddharthkp/auto-install.git"
},

@macdonst Added 😄

Looks like this got reverted in https://github.com/siddharthkp/auto-install/commit/6bb02a80b8c7c26b38eb226194db9ff8585f5108
The shorthand version siddharthkp/auto-install you currently have specified will not be recognized by npm or the npm website. Using a fully-qualified URL string value for repository works fine.  The normalize-package-data module takes care of turning it into an object:

If repository field is a string, it will become an object with url set to the original string value, and type set to "git".

@zeke,  npmjs website seems to understand the shorthand, I'm I missing something?

Wasn't there yesterday, but works now! ¯_(ツ)_/¯

authors: macdonst siddharthkp zeke

repo: siddharthkp/auto-install


text:
Add Footer design

Is your feature request related to a problem? Please describe.
Footer Design
*Describe the solution you'd like
Adding good design to footer.

Pls assign it to me under hacktoberfest.

footer design is not a component I guess.

It's okayy you can add footer designs as well,but make sure it's purely html,css and js.

Pls assign it to me under hacktoberfest.

Assigning this to you. 🎊🎊🎊

Thanks for assigning . I will do it in HTML,CSS, JS only.

Any updates ?

Sure. All the best !

Pls consider my PR for the issue #15


text:
Determine expires of cookie token

Describe the feature
The expires of the cookie are 1 month, we want to modify it to 2 months

How would you implement this?
The expires of the cookie are 1 month, we want to modify it to 2 months

Additional information

[ ] Would you be willing to help implement this feature?

Provider

[X] AuthJS
[ ] Local
[ ] Refresh
[ ] New Provider

Hi @agracia-foticos 👋
You should be able to set this inside the NuxtAuthHandler inside the JWT options. Let me know if this is not the case and I will look into it futhur 😊
https://next-auth.js.org/configuration/options#jwt

authors: agracia-foticos zoey-kaiser

repo: sidebase/nuxt-auth


text:
Add an ignorePaths option to the global middleware

Describe the feature
Add an ignorePaths option to the global middleware, so that pages can be excluded from the global protetction without adding:
definePageMeta({ auth: false })

to them.
This approach has some advantages:

it works if a project hast just a app.vue. Currently, in this case, the app.vue cannot be excluded as the definePageMeta macro does not work on it
it may offer a more intuitive way for some users to configure the excluded paths directly in the nuxt.config.ts

Additional information
Originally proposed here: https://github.com/sidebase/nuxt-auth/issues/81#issuecomment-1339004288
Interface proposal for config:
enableGlobalAppMiddleware: boolean | {
  enabled: boolean
  ignoresPaths: string[]
}

wrongly closed via #90 - it did not contain these changes.

closing this for now as so far no real demand was registered + implementation not planned. If you are interested in this feature feel free to comment or add a new issue (:


text:
Added support for ActiveRecord serialize/deserialize using GlobalID for Sidekiq::Cron::Job arguments.

Added support for ActiveRecord serialize/deserialize using GlobalID for Sidekiq::Cron::Job arguments.
https://guides.rubyonrails.org/active_job_basics.html#globalid
Demo
e.g. Use Person model as a arguments of Sidekiq::Cron::Job
class Person < ApplicationRecord
end

class ExampleJob < ActiveJob::Base
  queue_as :default

  def perform(person)
        puts "person: #{person}, class: #{person.class}"
  end
end

person = Person.create(id: 1)
Sidekiq::Cron::Job.create(name: 'Example', cron: '*/1 * * * *', class: 'ExampleJob', args: person)

Before
irb(main):043:0> Sidekiq::Cron::Job.find(name: "Example")
=>
#<Sidekiq::Cron::Job:0x00007f5f22e7a580
 @active_job=false,
 @active_job_queue_name_delimiter="",
 @active_job_queue_name_prefix="",
 @args=["#<Person:0x00007f5f22f35ba0>"],
 @cron="*/1 * * * *",
 @date_as_argument=false,
 @description="",
 @errors=[],
 @fetch_missing_args=true,
 @klass="ExampleJob",
 @last_enqueue_time=nil,
 @message="{\"retry\":0,\"queue\":\"default\",\"class\":\"ExampleJob\",\"args\":[\"#<Person:0x00007f5f22f35ba0>\"]}",
 @name="Example",
 @parsed_cron=#<Fugit::Cron:0x00007f5f22e85c78 @cron_s=nil, @day_and=nil, @hours=nil, @minutes=[0, 15, 30, 45], @monthdays=nil, @months=nil, @original="*/1 * * * *", @seconds=[0], @timezone=nil, @weekdays=nil, @zone=nil>,
 @queue="default",
 @queue_name_with_prefix="default",
 @status="enabled",
 @symbolize_args=false>

Sidekiq logs
[app] I, [2023-02-09T02:17:19.685994 #7]  INFO -- : start
[app] I, [2023-02-09T02:17:19.715124 #7]  INFO -- : Performing ExampleJob (Job ID: cb6eaeb2-a14e-4dc1-8a63-f20c598f60bf) from Sidekiq(default) enqueued at 2023-02-09T02:17:19Z with arguments: "#<Person:0x00007f5f22f35ba0>"
[app] person: #<Person:0x00007f5f22f35ba0>, class: String
...

After
irb(main):043:0> Sidekiq::Cron::Job.find(name: "Example")
[#<Sidekiq::Cron::Job:0x00007fa3f1487ed8
  @active_job=false,
  @active_job_queue_name_delimiter="",
  @active_job_queue_name_prefix="",
  @args=[{"_sc_globalid"=>"gid://app/Person/1"}],
  @cron="*/1 * * * *",
  @date_as_argument=false,
  @description="",
  @fetch_missing_args=false,
  @klass="ExampleJob",
  @last_enqueue_time=nil,
  @message="{\"retry\":0,\"queue\":\"default\",\"class\":\"ExampleJob\",\"args\":[{\"_sc_globalid\":\"gid://app/Person/1\"}]}",
  @name="Example",
  @queue="default",
  @queue_name_with_prefix="default",
  @status="enabled",
  @symbolize_args=false>]

Sidekiq logs
[app] I, [2023-02-09T02:40:26.628976 #8]  INFO -- : start
[app] I, [2023-02-09T02:40:27.407155 #8]  INFO -- : Performing ExampleJob (Job ID: d6f6ab18-5790-4afb-9c26-b2be8bd998ca) from Sidekiq(default) enqueued at 2023-02-09T02:40:26Z with arguments: #<GlobalID:0x00007fa29842b318 @uri=#<URI::GID gid://app/Person/1>>
[app] person: #<Person:0x00007fa29845bcc0>, class: Person

References

https://github.com/rails/rails/blob/v7.0.4/activejob/lib/active_job/arguments.rb

Nice feature @nyuta01 👌
We probably should mention it somewhere in the docs.

@markets
Thank you for the review!
If I were to add docs, I would probably make changes to the README, is this something I should do? Or should I request a more knowledgeable contributor to do this?

Documentation improvements are also really welcome! Feel free to propose changes!
But in order to avoid this pull request to grow so much, I'd probably just add some mention for now and send improvements in new branches.

@nyuta01 could you please rebase from master? We added automatic CI runs for different Sidekiq versions.

Just a couple of minor comments:

We need some mention in the docs
We should remove this file (sidekiq-cron-1.9.1.gem): https://github.com/sidekiq-cron/sidekiq-cron/pull/395/files#diff-51441cd7981cd2ab547716137b96e19a9b0b56c6eb837fb667fc8202fab28250

@markets
Thank you for your comment.
I didn't notice the notification and was late in responding.
I have corrected the areas you pointed out, so please re-review.

Thank you so much @nyuta01! Merging 🚀

repo: sidekiq-cron/sidekiq-cron


text:
Make Prettier use xml instead of the html parser

Note that the formatting kinda sucks because the XML plugin preserves all whitespace, or lack of thereof, between tags. xmlWhitespaceSensitivity: "ignore" results in a better looking file, but also changes the content of text nodes by inserting whitespace. The upcoming xmlWhitespaceSensitivity: "preserve" would've been the best, and would replicate the html parser's behavior. Closes #1

Thanks!
Yeah, I've had to hack on the xml plugin to get it to print the way I wanted in the past...

authors: piousdeer siefkenj

repo: siefkenj/relax-ng-to-typescript


text:
Data source for CloudWAF instance, or specific deployments

Similar to how the Fastly provider has https://registry.terraform.io/providers/fastly/fastly/latest/docs/data-sources/ip_ranges data source for retrieving IP ranges (e.g. for allow-listing IP addresses in firewalls, security groups etc), it would be very handy to have the same functionality in the SigSci provider for the same purpose
Apparently the get /corps/{corpName}/cloudwafInstances/{deployment_id} endpoint would return all of the deployments which can be iterated over to get their respective egress IPs... I'm not sure if starting at the top-level and drilling down is better, or just having a data source for deployments directly (or maybe both) would be a better option. But in either case, a data source to get egress IPs in some manner is necessary.
Since they are per-customer and require authentication it's not as straightforward as just using the http provider and hitting a given endpoint. API authed sessions are required so I think this puts it a bit outside of workaround territory with standard built-ins in Terraform.

We are looking to add cloudwaf support in the future, I will note this as a feature to include, thanks!

authors: jhanrahan-sigsci ohookins


text:
If a user goes out of the app the questions are not resent

run sample-comments
open localhost:8080
close window
open localhost:8080
see there's no old comments

Solved in https://github.com/signicode/humanify/tree/feature/multi-root.

repo: signicode/humanify


text:
Re-expose commands.

I was trying to pull in the recent upstream updates to a downstream repo that was invoking the CLI via cli.Sign().Exec(...) and this regressed in the cobra migration.  In a perfect world, we could pull in the CLI functionality without needing to go through cobra.Command to do it, but we're not there yet.  The alternative to cli.Sign().Exec(...) is cli.SignCmd(...), which takes 11 arguments and growing each release.  The alternative fo cli.Attest().Exec(...) is cli.AttestCmd(...) with 9 arguments.  etc, etc, etc...
What's more, the above functions are also colocated with their cobra wrappers so we also can't save on not vendoring cobra yet, so it's a mystery to me why we'd force folks to not use this interface.
Signed-off-by: Matt Moore mattomata@gmail.com
Ticket Link
Fixes: https://github.com/sigstore/cosign/issues/880
Release Note
NONE

I also noticed that we were generating markdown docs without the piv-tool present, so this passes the needed tags to that command.

touching things to kick DCO 🤞

repo: sigstore/cosign


text:
Better Module Name

Need to think of a better name. Will only change Github/Packigist next major release.

Going to change it to "SortableMenu" for simplicity. SilverStripe 4 version will be in sortablemenu repo.
https://github.com/silbinarywolf/silverstripe-sortablemenu

Nah actually changing things at a packagist level is hassle.
This should get its name changed to SortableMenu though. TreeHugger is a bad name.

repo: silbinarywolf/silverstripe-treehugger


text:
Decoupled entrance rando

Contains the portal direction pairs PR.
The options aren't done very nicely still -- mostly since I think you have a way you like to do them so no real point in me putting too much thought into that.

Need to test it after merging, and rename FixedShop to ERFixedShop

Testing success

repo: silent-destroyer/tunic-randomizer


text:
Pro účetní je přidávání nových služeb je moc složité

Jako účetní chci přidat novou službu bez ověřování a schvalování.

Tato funkce se používá velmi zřídka, prozatím se nebude implementovat.


text:
Fix "Cannot use import statement outside a module"

/Users/.../myproject/node_modules/tailwindcss-group-modifier-plugin/dist/index.js:1
import plugin from "tailwindcss/plugin";
^^^^^^
SyntaxError: Cannot use import statement outside a module

Thanks for the PR @sarimarton!
Could you also please bump the version (patch) for this?

Thanks for the PR @sarimarton!
Could you also please bump the version (patch) for this?

✅

Thanks!
Notice the build is failing now.

authors: sarimarton silicakes


text:
Add counter to TextInput,  TextInput and TextArea outlines red when reaching limit and add utils, add MoneyInput

#Add

min, max, height and width utilities
margin and padding up to 50px in utilities
TextField: icon prop and character counter
MoneyInput and story
#Change
TextField and TextArea: make outline red on maxlength reached

Making some changes after getting feedback from Alex

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: silinternational/ui-components


text:
Update wiki

Da das Backend komplett neu geschrieben wurde, ist die Dokumentation im Wiki vermutlich nicht mehr aktuell. Insbesondere die API-Endpoints wären für Erweiterungen (iOS-App, o.ä.) nützlich zu wissen.

Die API Endpoints sehen noch aktuell aus. Nur, dass da halt noch mehr dazu kamen. Den Rest müsste man auch noch aktualisieren. MQTT unterstützung ist zB derzeit nicht drin.

Interessant wäre noch mal aufzuschreiben, welche APIs benötigt werden und vielleicht noch mal eine neue API from scratch zu designen.

authors: silsha uwap

repo: silsha/fnordcredit


text:
chore: upgrade @silvermine/standardization to 2.0

This commit upgrades Silvermine's standardization library, and removes standards linting
and checking that was formerly run through Grunt.js. Now, linting can be executed using
npm run standards instead of grunt standards.
Also temporarily disables travis CI for latest Node. See: https://github.com/silvermine/standardization/issues/39

Coverage remained the same at 0.0% when pulling a6f58c1fd68ecc0ffaf32fc3ad9e163fc5527b5d on pbredenberg:pb/upgrade-standardization into c83a600a8455c52260f7f05906e4eb24018b85fb on silvermine:master.

authors: coveralls pbredenberg

repo: silvermine/videojs-airplay


text:
Field default value dropdown set empty string

When a MemberProfileField is a DropdownField there is no way to select nothing as the default dropdown value.
$default->setHasEmptyDefault(true); doesn't seem to work.
I have replaced this with $default->setEmptyString(' ');.
This allows the user to select the empty string as a default value.

Is there anything I can do to help this get merged in?

Sorry, the notification was caught in my backlog! Thanks :)

Awesome. Thanks Marcus. :)


text:
adding ability for solr suffix and prefixing

This means the same code can run on a single solr core and have the same indexes but use prefixes or suffixes to keep them separate

@hafriedlander / anyone who is active on this module, this one is exactly for a situation that needs to create two cores on one host server, using one site (code), could you guys have a look, please?
Though I think the pull request's description is a bit blur. misleading.

I'm concerned that there could be other parts of the code that rely on the assumption that indexName === indexClass. It would require a new major version to change this assumption.
Could we, instead of this change, put the new code into a new public function getIndexStoredName() and subsitute that where the index name is otherwise passed to solr?
getIndexName() could remain the original definition (and still be used to lookup the class).
In any case, we probably need to do an exhaustive search of the API to ensure the right value is used in each case.

@tractorcow either ways should work.
JFI, this pull request works in these situations or combinations of these setting:
Environment set as 'dev', so 'SearchUpdateImmediateProcessor' / 'SolrReindexImmediateHandler' used, no matter what.
Environment set as 'test' and QueuedJob module present, so 'SearchUpdateQueuedJobProcessor' and 'SolrReindexQueuedHandler' used.
Have Checked both Configure/Reindex initial process and triggered some process to individually update objects that previously indexed, all works.
Though, I didn't check the situation of using 'SearchUpdateMessageQueueProcessor' and 'SolrReindexMessageHandler'.
I am not objected to the idea to separate the function into 2 functions and use them semantically, that seemed a cleaner way.

Ok, that gives me a bit more confidence in this PR. :)
Do you want to rebase so we can do some more testing?

If @pitchandtone isn't available we might need to rebase it for him in another PR....

Yeah sorry about that. Won't be back in action until next week...
Sent from my iPhone

On 12/01/2016, at 2:30 PM, Damian Mooyman notifications@github.com wrote:
If @pitchandtone isn't available we might need to rebase it for him in another PR....
—
Reply to this email directly or view it on GitHub.

All good; Sorry to let this sit for so long. ;)

Travis failure seem unrelated.

travis is broken on this repo atm

Ugh, was that that versioning test I was ment to fix before 3.2.3? I guess too late now...

Yep...

I'd like @hafriedlander or @chillu to look at this before merging. I'm not confident that this won't have regressions.

bump @chillu @hafriedlander - I can confirm I'm using this patch in production

@dhensby @hafriedlander works fine on prod for Wellingtonnz.com

really sorry @pitchandtone - this needs a rebase now, then we'll get it in

@dhensby rebased now.

Thanks

authors: dhensby normann pitchandtone tractorcow


text:
Module may fail to destroy expired sessions

Note: The following is extracted from a commissioned report by Insomnia Security.
Technical details
The functionality of the SilverStripe DynamoDB module is not accurately documented and, without additional configuration, expired sessions may accumulate in the session table.
The SilverStripe DynamoDB module exists to replace the default session PHP handing with an AWS DynamoDB backed session store. By default, on Debian based systems an operating system ‘cron’ is used to clear away expired sessions. Similarly, with SilverStripe DynamoDB the Crontask module was at one point used to remove expired sessions. However, current versions of the Crontask module do not provide this facility.
The current version of the Crontask module no longer implements GarbageCollectSessionCronTask which removes expired sessions. The removal and reasoning are explained in this commit:
https://github.com/silverstripe/silverstripe-dynamodb/commit/d91baf50a890570258805fde86051bd86eb96d4b#diff-003cb34625bfaea8be18fd87cd2d3afc
Yet the silverstripe-dynamodb module readme still states that: "Inactive sessions are garbage collected by GarbageCollectSessionCronTask if silverstripe-crontask is setup on your instance."
The garbage collection task was removed because AWS DynamoDB now provides a facility to automatically remove expired sessions. However, enabling this functionality requires setting a TTL property named ‘expires’ on the AWS DynamoDB table.
There is no explanation of this step in the module documentation and absent this step sessions will accumulate indefinitely in the AWS DynamoDB session table.
It is also noteworthy that in its default configuration SilverStripe does not set an expiry on the session cookie. Some standardised deployments of SilverStripe (such as CWP) do introduce a cookie lifetime with the following directive in config.yml:
SilverStripe\Control\Session:
timeout: 1440

If the cookie is not expired by the browser and the session is not expired by the server then sessions will have an indefinite lifetime.
Affected modules
▪ silverstripe/crontask
▪ silverstripe/dynamodb
Consequence
In the absence of a timeout being set for the session cookie and a TTL value set in DynamoDB it is possible that user sessions may not expire. It is also possible that entries in the session table will be accumulated indefinitely, which could impose unwanted AWS billing costs.
Recommendations

Update the documentation to explain that setting the expiry TTL attribute on the AWS DymamoDB session table is required for expired sessions to be removed and refer users to the relevant AWS documentation. This document explains using the DynamoDB TTL expiry to automictically remove expired sessions: https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/service_dynamodb-session-handler.html

Remove the crontask module from the list of DynamoDB dependencies.

Consider providing an example AWS CLI command for creating the DynamoDB session table with a correctly configured TTL attribute.

Reference
CWE: CWE-613 Insufficient Session Expiration
▪ https://cwe.mitre.org/data/definitions/613.html
AWS: Documentation on DynamoDB Session Handler
▪ https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/service_dynamodb-session-handler.html

If the cookie is not expired by the browser and the session is not expired by the server then sessions will have an indefinite lifetime.

This is not true. A session cookie with 0 lifetime should be delete by the browser when the session ends (window is closed). Sessions with lifetimes are no longer actually "session" cookies they are persistent cookies.
Have you actually seen this behaviour in the wild or is it theoretical? My understanding of the AWS php-sdk was that it actually made a call to clean up sessions when PHP normally would.
The set up of Dynamo DB tables for PHP sessions is also clearly laid out in their docs (https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/service_dynamodb-session-handler.html) and, again from my previous usage, the php-sdk can set these up for you automatically.
It does appear that dynamo DB recommends deleting session in batches rather than relying on PHP's default behaviour, but it's by no means a requirement.

tl;dr - not the first time a pen test company will have got something wrong ;)

It's worth noting that this is an audit report passed on by Bryn, the original reporter isn't listening in here :) This is public because we don't consider it a security issue as such.

This is not true. A session cookie with 0 lifetime should be delete by the browser when the session ends (window is closed). Sessions with lifetimes are no longer actually "session" cookies they are persistent cookies.

I think that's what they mean by "if the cookie is not expired by the browser" (through closing the window). This is explained here: https://github.com/silverstripe/cwp/blob/c57ecfc065157d31e3761271dcc2e7b00b5893ce/docs/en/01_Working_with_projects/10_Security.md#user-session-expiration. The CWP specific default simply matches the PHP settings on the server.

My understanding of the AWS php-sdk was that it actually made a call to clean up sessions when PHP normally would.

I'm not sure if it used to do that, but the aws docs are pretty clear on this - they don't do automated GC outside of the DynamoDB TTL setting, or the library feature being triggered externally (e.g. through cron).
So in conclusion, our module README made it a bit too easy to set this up wrong. I've sent a PR at https://github.com/silverstripeltd/rainforest/pull/834. Notably in Silverstripe Cloud, we've been creating the expires attribute in new tables since mid 2019, and at that point retroactively applied to to existing tables as well.

authors: brynwhyman chillu dhensby

repo: silverstripe/silverstripe-dynamodb


text:
<% with $Up.Up %> does not work

<% with $Up %>{$Up.Title}<% end_with %> works but <% with $Up.Up %>{$Title}<% end_with %> does not.

Tested on 3.x-dev, no longer an issue

authors: jaydenseric kinglozzer

repo: silverstripe/silverstripe-framework


text:
Object specific templates and the Problem of the $Content Folder

I have a method in my DataObject which renders the class with a object specific template. The problem is, if I iterate over these objects like this:
public function EntryHolder()
{
    return $this->renderWith($this->class);
}

<% loop $Entries %>
    {$EntryHolder}
<% end_loop %>

I cannot use iterator specific methods in the sub-Template, because since SS-3 the iterator scope is no longer inherited to my sub template. I now have to use a custom static variable for this purpose ...
The SSViewer creates two sub templates out of the Box $Layout and $Content.
The $Content Template not realy works in Silverstripe-3 for Pages because the Content-Field of the Page-Class has a higher priority than the Variable for the Sub-Template ...
Another point is these sub templates only works on the base scope not in loops or with-blocks.
Would it be possible to move these lines of code:
        // Makes the rendered sub-templates available on the parent item,
        // through $Content and $Layout placeholders.
        foreach(array('Content', 'Layout') as $subtemplate) {
            if(isset($this->chosenTemplates[$subtemplate])) {
                $subtemplateViewer = new SSViewer($this->chosenTemplates[$subtemplate], $this->parser);
                $subtemplateViewer->includeRequirements(false);
                $subtemplateViewer->setPartialCacheStore($this->getPartialCacheStore());

                $underlay[$subtemplate] = $subtemplateViewer->process($item, $arguments);
            }
        }

to a class like the TemplateIteratorProvider or TemplateGlobalProvider to allow creating Templates for every DataObject which could be used in loops also?

I’m going to close this as a stale enhancement. Supporting passing iterator info down like this (as opposed to just doing something like <% include Foo CurrentPos=$Pos %>) would require a sizeable chunk of work, and we’re not exactly being inundated with requests for this ;)

authors: beerbohmdo kinglozzer


text:
USABILITY: when I click on filter I expect it to open...

when I click on filter I expect it to open...

#3780

authors: kinglozzer sunnysideup


text:
FIX: Class names referenced in Config should be case-insensitive

The config system maps top-level key name to a PHP class. PHP classes are case-insensitive,
but without this patch, the Config system was case-sensitive on this variable. I think this
should be considered a bug.
The following patch makes the "class" key case-insensitive, but leave the "name" key, as
case-sensitive, mirroring the semantics of PHP classes and static variables, respectively.
Arguably, the entire config system could be case-insensitive, but I haven't done that in
this patch.

+1 for this @hafriedlander
I think this is a bug fix and can stay against 3.1

How do you feel about using strtolower, over say, using a case-fixing mechanism? See https://github.com/micmania1/silverstripe-framework/blob/replace-static-manifest/core/ClassInfo.php#L163 for @micmania1 's solution.
Is there a place we could strategically place this in the code so that we have to do as few case corrections as possible? Places such as get_called_class() automatically normalise class casing.
I personally feel that storing the config in the correct case is going to deviate the least amount from what the current behaviour is, and is less likely to introduce regressions.

The issue with my solution is that it only resolves class names - not made up configuration in yaml. I'd be able to remove my fix if it was agreed that this is the best way to go.

fixes #3378

strtolower has to be the least CPU cycles to get this "feature" working.. I prefer it over reflection or normalising the class names

Maybe this would be better in 3.2 instead, just because of the regression risk issue that Damian pointed out.

very much related: https://github.com/silverstripe/silverstripe-framework/pull/3949

I think this is a patch and should stay in 3.1 myself. Under what circumstances could this cause a problem to existing code?

@sminnee @dhensby fixed this in https://github.com/silverstripe/silverstripe-framework/pull/3949 but opted to use a "fix case" method rather than treating all classes as lowercase for matching. Should we use the same solution here?

Makes sense to make it consistent with #3949
@sminnee ?

Superceded by new config api, which stores all per-class config with a lowercase key https://github.com/silverstripe/silverstripe-config/blob/1.0/src/Collections/MemoryConfigCollection.php#L82

authors: dhensby micmania1 sminnee tractorcow


text:
API Implementation of RFC-1 Asset Abstraction

Partial implementation of https://github.com/silverstripe/silverstripe-framework/issues/3792
This PR includes creation of the APL (Asset Persistence Layer) using flysystem as a default backend, and creation of the DBFile field.
This is built on top of https://github.com/silverstripe/silverstripe-framework/pull/4590 which should be merged first.

OK I've posted a bunch of comments, but this is looking pretty solid! I reckon we post a link to this PR to ss-dev so that we can broaden its visibility.

I had reader and writer separate initially, but @hafriedlander didn't like it so I removed it. :D

I've updated FlysystemAssetStore to never unwrap files or streams into raw strings in memory, and using stream / file based sha1 generation if possible.
Where streams are not seekable, they are written directly into temporary files and new streams generated from these.

Rebased from master, as the composite DBField work has been merged.

Fixed and squashed.

Given the scope of this change, it would be good to get 3 :+1:s from core committers before merging.
:+1: from me. Can we get 2 more?

:+1:

:+1:

@dhensby do you want to have a look at this work? @jonom?

@wilr your feedback has been resolved. ;)

Gave it a spin locally. Nice, then a :+1: from me then.

And we're in!

authors: chillu sminnee tractorcow wilr


text:
Added italian localization to jqueryui datepicker

so it's possible to use ->setConfig('jslocale','it') for DateField

Thanks Gabriele!


text:
API use injector for DataObject::newClassInstance()

API Fail on invalid class type change
Partial fix for https://github.com/silverstripe/silverstripe-cms/issues/1210. Second PR will be needed on CMS module (will do later).

Looks good, test failures related?

Wow that's a weird error... er... i'll look into it tomorrow. :D

Other PR is at https://github.com/silverstripe/silverstripe-cms/pull/1599, but I better fix this one first.

Ok, new change with slightly more forgiving behaviour for DataObject::setClassName() to prevent regressions.

ok it's green. :D

authors: kinglozzer tractorcow


text:
BUGFIX: Allow buttons to opt out of display

This bug is breaking Behat tests. https://travis-ci.org/silverstripe/silverstripe-framework/jobs/385964668#L896

Yay for green Behat though!

Merge on green.

Yep still merge on green.

Also fixes https://app.zenhub.com/workspace/o/silverstripe/silverstripe-framework/issues/8123

authors: robbieaverill tractorcow unclecheese


text:
Create user help documentation

Blocked until https://github.com/silverstripe/silverstripe-framework/issues/9883 is merged - we need finalised UI before we can describe it and take screenshots
Overview
The new designs include a 'Learn more' link in the CMS UI. Some user help documentation needs to be written and the button in the CMS created.
Acceptance Criteria

[ ] Information covering how the feature is intended to work and how users interact with it is documented
[ ] The user help documentation is accessible via the CMS UI (through the 'Learn more' button)

[ ] Update the help link in MemberExtension

[ ] Server requirements are updated to include information on this module and include gotchas (from the caveats section of the module docs): https://docs.silverstripe.org/en/4/getting_started/server_requirements/

Notes

The user documentation should be stored in this module and made available for viewing under the 'optional features' section in the CMS user help docs.
There is an internal guide on how to write userhelp on Confluence (ask Paul)

PRs / Actions

[ ] https://github.com/silverstripe/silverstripe-session-manager/pull/36 (TODO: update link to userhelp)
[ ] https://github.com/silverstripe/silverstripe-session-manager/pull/78
[ ] https://github.com/silverstripe/doc.silverstripe.org/pull/232
[ ] Add NETLIFY_BUILD_HOOK secret to session-manager repo (ask @bergice)

We're changing the link to https://userhelp.silverstripe.org/en/4/optional_features/managing_devices for now. https://github.com/silverstripe/silverstripe-session-manager/pull/62/files#r613873046
Might need to change to something else later on.

Server requirements are updated to include information on this module and include gotchas (from the caveats section of the module docs): https://docs.silverstripe.org/en/4/getting_started/server_requirements/

I don't get this.
This is an optional module, and it's already documented on the module itself.

I've just gone through and done a review of the user help guides, hit me up if you have any questions or problems with it.

Link from the "Keep me signed in" segment to the session manager guides for more information. Session manager docs will probably move to sit next to "Log in" guides once it is in core.

Thinking about it a bit, I do feel like it could be too soon to make reference to session-manager in the core 'logging in' userhelp? The module is yet to go stable so it feels like it might just confuse people if they were to read it but don't have the feature?
When we move session manager to core, we'll definitely be updating the userhelp then.
In the meantime though, while we're hear I think the screenshot in https://userhelp.silverstripe.org/en/4/managing_your_website/logging_in/ should be replaced to one with login-forms - that's been the default for multiple minor releases now.

Added another suggestion by Matt P

Add text at the bottom of the page "If you’re having trouble accessing your account please contact the website owner as they can reset your account".

Added another suggestion by Matt P

Add text at the bottom of the page "If you’re having trouble accessing your account please contact the website owner as they can reset your account".

There's already a https://userhelp.silverstripe.org/en/4/managing_your_website/logging_in/#lost-password section.

The use case was more for non CMS users using the login page (they wont realise its the login screen for the CMS itself) and viewing CMS help will be confusing and potentially alarming. For example lost password doesn't make a difference if your email address isn't accepted, you need to contact the site owner.
We've had a few follow on convos yesterday that we think we are going to need to have an option to remove the "Need help?" link and Silverstripe CMS logo if the login is being used by website users (separate issue), or have those things disabled by default and can be enabled if only used by CMS users.

I'm happy with the docs, everything resolved from what I can tell.

Closing.
Opened https://github.com/silverstripe/silverstripe-session-manager/issues/85

authors: bergice brynwhyman clarkepaul maxime-rainville


text:
Support NeXus default attribute pointing to an NXdata at any group level

The proposal https://github.com/nexusformat/NIAC/issues/28 has been unanimously approved by the NIAC.
They found it to me the less controversial of all proposals I have ever made.
BTW, auxiliary_signals was also approved.

Of course at NXroot level it can only point to an NXentry like before.

repo: silx-kit/silx


text:
Does NOT work inside tmux

Prints characters all over the place and shifts cursor when inside a tmux session (viz image)

When not inside tmux session, jid workds as expected in the same terminal.

Seems to be a $TERM-related-issue; with TERM screen-256color or xterm-256color I have that issue as well, if I run jid with TERM=xterm jid < whatever.json, for example, it works as expected.

authors: evs-ch fogine

repo: simeji/jid


text:
🛑 James Finance is down

In 7384b2d, James Finance (https://$JF_SITE1/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: James Finance is back up in 321a563.


text:
No cleverness

@simoncozens I'm opening this as a PR to provide a convenient place for discussion.
I'd also like to be explicit about our goals here: the idea is to have the otspec crate contain a 'dumb' representation of all the types and tables used in the OpenType specification, as well as the ability to serialize and deserialize these types. The idea is that this crate does not present any higher-level API, which will be provided by another layer, built on top. (if you have any clarifications or additions, please correct me!)

So. This PR doesn't do absolutely everything that could be done in terms of separating the low-level from the high-level. But it does enough both to prove the concept and also to meaningfully push forward what fonttools-rs does in terms of OpenType Layout (almost all layout types can now be read and written, without any of the horrible fudging we were doing before), and it does so in a way that doesn't change the public interface to fonttools. Because it doesn't change the public interface, I'm going to merge it to main and continue working on things there as part of the general development of the library.

authors: cmyr simoncozens

repo: simoncozens/fonttools-rs


text:
Deployment Environments usage

Am trying to deploy an app to either a prod or a dev environment (two separate firebase projects)
From the docs, this explanation almost gets me there, but I think I need a clarification

You can now run:
nx deploy my-firebase-app for dev deployment
nx deploy my-firebase-app --prod for production deployment
Note that your-dev-firebase-project and your-prod-firebase-project must exist as aliases in your .firebaserc file for this to work.

Would this be 2 different nx web apps?
Or would the same web app get deployed to prod-project with --prod and dev-project without --prod
Based on the same app deploying to different firebase projects, I would think .firebaserc should look like this, but of course this can't work.
  "projects": {
    "default": "",
    "nx-project-name": "your-prod-firebase-project ",
    "nx-project-name": "your-dev-firebase-project"
  },
  "targets": {},
  "etags": {}
}

Using the --prod flag but not deploying to the "production" configuration
nx deploy my-firebase-app-firebase --prod
and in my-firebase-app/firebase/project.json
      "executor": "nx:run-commands",
      "options": {
        "command": "firebase --config=firebase.my-firebase-app-firebase.json --project=firebase-dev-project"
      },
      "configurations": {
        "production": {
          "command": "firebase --config=firebase.my-firebase-app-firebase.json --project=firebase-prod-project"
        }
      }
    },

When you have a dev and prod environment setup, you will have to create two firebase projects in your firebase account console - lets call them your-prod-firebase-project and your-dev-firebase-project
You then need to add these to your .firebaserc config with aliased names (unrelated to your Nx project names)
  "projects": {
    "default": "",
    "prod": "your-prod-firebase-project ",
    "dev": "your-dev-firebase-project"
  },

You only need one nx-firebase project in your Nx workspace, because we're saying we'll want to deploy this nx-firebase project to either prod or dev depending on the --prod configuration.
So your config above is correct (I've just renamed to use the example aliases here):
      "executor": "nx:run-commands",
      "options": {
        "command": "firebase --config=firebase.my-firebase-app-firebase.json --project=dev"
      },
      "configurations": {
        "production": {
          "command": "firebase --config=firebase.my-firebase-app-firebase.json --project=prod"
        }
      }
    },

Now, when we run deploy with --prod the Firebase CLI command will use --project=prod, so will deploy to your prod firebase project, and without --prod it will deploy the same Nx project to your dev firebase project instead.
See here for more info

Thanks for the feedback, seem to be getting further along with this but am still running into issues.
running
nx run nx-project-firebase:firebase deploy --prod
it seems to be using dev instead of prod
also, it is using the alias in .firebaserc, not the firebase project name, the project in firebase would be named prod-firebase-project, not just dev or prod
getting following error that contains account dev@appspot.serviceaccount.com vs my prod-firebase-project@appspot.serviceaccount.com and the console link with ?project=dev which should be ?project=prod-firebase-project
JSON error trying to load .../.firebaserc
Error: Missing permissions required for functions deploy. You must have permission iam.serviceAccounts.ActAs on service account dev@appspot.gserviceaccount.com.
To address this error, ask a project Owner to assign your account the "Service Account User" role from this URL:
https://console.cloud.google.com/iam-admin/iam?project=dev

am using dev and prod as aliases as shown here:
{
  "projects": {
    "default": "",
    "prod": "prod-firebase-project",
    "dev": "dev-firebase-project"
  }
}

and here:
    "firebase": {
      "executor": "nx:run-commands",
      "options": {
        "command": "firebase --config=firebase.nx-project-firebase.json --project=dev"
      },
      "configurations": {
        "production": {
          "command": "firebase --config=firebase.nx-project-firebase.json --project=prod"
        }
      }
    }

and here:
nx deploy nx-project-firebase --prod

Solved, documenting and closing this issue,
Was able to add configuration options to the deploy target that would then call the firebase target with the needed configuration option, both of these targets are in the app/projectName/firebase/project.json file.
For some reason, probably my lack of understanding, .firebaserc did not seem to be a factor at all.
{
  "name": "projectName-firebase",
  "$schema": "../../../node_modules/nx/schemas/project-schema.json",
  "projectType": "application",
  "targets": {
    "deploy": {
      "executor": "nx:run-commands",
      "dependsOn": [
        "build"
      ],
      "options": {
        "command": "nx run projectName-firebase:firebase deploy"
      },
      "configurations": {
        "production": {
          "command": "nx run projectName-firebase:firebase:production deploy"
        },
        "development": {
          "command": "nx run projectName-firebase:firebase:development deploy"
        }
      }
    },
   "firebase": {
      "executor": "nx:run-commands",
      "options": {
        "command": "firebase --config=firebase.projectName-firebase.json --project=development_firebaseProjectName"
      },
      "configurations": {
        "production": {
          "command": "firebase --config=firebase.projectName-firebase.json --project=production_firebaseProjectName"
        },
        "development": {
          "command": "firebase --config=firebase.projectName-firebase.json --project=development_firebaseProjectName"
        }
      }
    }
  }
}

repo: simondotm/nx-firebase


text:
打包输出第一个Mac可用的版本

是否需要打包成dmg安装程序
注意压缩包的大小

考虑到Frameworks其实没什么可压榨的空间（比atom多5M而已，主要还是Resources目录压榨）
暂时不考虑打包成dmg，输出绿色版即可。
另外压缩打包文件很重要，目前不知道atom是怎么压缩的。
本来想参考atom的相关build和dist代码，不过相关代码太多而杂。
可以参考https://github.com/nylas/N1，和atom的脚本差不多。

目前使用appdmg将应用程序输出成dmg文件，大小非常可观只有44M。

repo: simongfxu/violet


text:
Fix correctness issue with reverse dependencies

If a term is changed in the editor we must re-check those terms that depend on it.

This is fixed in v0.4.0

repo: simonhorlick/kind-vscode


text:
Implement get horoscope intent

To read the current or last week's horoscope for a given sign.

Completed in https://github.com/simonprickett/zestyscopes/commit/147a8d2dfa39016218642a4d8c5aa862c9f62c2a

repo: simonprickett/zestyscopes


text:
Move include statements into module

In another module that was using MAT, when precompiling I was getting errors:
ERROR: LoadError: LoadError: ArgumentError: MAT_v5 not found in path
 in require at ./loading.jl:233
 in stale_cachefile at loading.jl:439
 in recompile_stale at loading.jl:457
 in _require_from_serialized at loading.jl:83
 in _require_from_serialized at ./loading.jl:109
 in require at ./loading.jl:219
 in include at ./boot.jl:261
 in include_from_node1 at ./loading.jl:304
 in include at ./boot.jl:261
 in include_from_node1 at ./loading.jl:304

I'm not exactly sure I understand why MAT was working before (and conversely why including it into my module didn't work), but things are working now that I moved the include statements inside the module. If nothing else, I don't think this should hurt anything.

Agreed. Travis test failure is due to broken Homebrew on nightly, so I'm merging.

Travis failures are consistently limited to OSX nightly and are due to a Homebrew error.

(Should have hit update.)

authors: simonster timholy


text:
Use new datasette.urls.static_plugins() method

Refs https://github.com/simonw/datasette/issues/1033 - this will ensure the plugin works with base_url configuration option.
Relevant code:
https://github.com/simonw/datasette-cluster-map/blob/be66a0b198527c6f2cfd5ae5dad9e2580f2891c7/datasette_cluster_map/__init__.py#L46

Blocked awaiting Datasette release containing that method.

This works already! It turns out Datasette handles that here: https://github.com/simonw/datasette/blob/25c2933667680db045851b2cedcf4666d737d352/datasette/app.py#L881-L883
I'll add a test and close this.

This works already! It turns out Datasette handles that here: https://github.com/simonw/datasette/blob/25c2933667680db045851b2cedcf4666d737d352/datasette/app.py#L881-L883
I'll add a test and close this.

repo: simonw/datasette-cluster-map


text:
Release notes for 0.5

https://github.com/simonw/llm/compare/6c321a3a152472fcb84392e35bf3a5ed8d32b135...fa67b3fdaf413f7c51397f012a45cc0bea5d03a0 shows 120 commits!

Note so far:

llm "prompt" --save template option for saving a prompt directly to a template. #55
Prompt templates can now specify {ref}default values <prompt-default-parameters> for parameters. Thanks,  Chris Mungall. #57
New -o/--option name value syntax for setting options for models, such as temperature. Available options differ for different models. #63
llm models list --options command for viewing all available model options. #82
-m 4-32k alias for gpt-4-32k.
llm openai models command to list all available OpenAI models from their API. #70
llm -s is now a shortcut for llm --system. #69
llm models default MODEL_ID to set a different model as the default to be used when llm is run without the -m/--model option. #31
Python API documentation for using LLM models, including models from plugins, directly from Python. #75
Messages are now logged to the database by default - no need to run the llm init-db command any more, which has been removed. Instead, you can toggle this behavior off using llm logs off or turn it on again using llm logs on. The llm logs status command shows the current status of the log database. If logging is turned off, passing --log to the llm prompt command will cause that prompt to be logged anyway. #98
New database schema for logged messages, with conversations and responses tables. If you have previously used the old logs table it will continue to exist but will no longer be written to. #91
llm install -e directory command for installing a plugin from a local directory.
Comprehensive tutorial on writing plugins that implement new models.
The LLM_USER_PATH environment variable now controls the location of the directory in which LLM stores its data. This replaces the old LLM_KEYS_PATH and LLM_LOG_PATH and LLM_TEMPLATES_PATH variables. #76
Documentation site now uses Plausible for analytics. #79
Documentation covering utility functions for plugins.

Need to add the plugins bit, which won't be bullet points. And maybe arrange those bullets in a more useful way.

In writing the release notes I realize there's no good place in the documentation to link to about how to install a plugin and then use that model.

Release notes are nearly there: https://github.com/simonw/llm/blob/c08e47355c1d18c63832aba909b329c40a352ae2/docs/changelog.md#unreleased

Release notes are ready now.

repo: simonw/llm


text:
Small typo fix in last heading

Hope this doesn't come across as nit-picky! I'm appreciative that you've shared this repo full of great tips and figured you'd want to have this read a little better 😄

Thanks!

authors: simonw tnorthcutt

repo: simonw/til


text:
WIP:  Fix time limit error for CI

This PR is trying to ensure that the 50 minute limit of CI is not exceeded for the framework.

The time is really from simphony-openfoam and simphony-lammps-md.  Both take between 17-20 minutes to build/test which doesn't allow much time for everything else.

repo: simphony/simphony-framework


text:
Add support for nullsafety

@simphotonics
Currently blocked by:

simphotonics/directed_graph#4
dart-lang/source_gen#493

The latest version of source_gen is not yet opted into null safety. But it seems the maintainers of source_gen are working on migrating their project.

Yes! I was also following their migration closely.
As of now, however, they have published 1.0.0. Although it is listed as a min SDK of 1.12 (dev). Whether that matters or not I don't know. You tell me. 🤔

Good to hear that. Just published the migrated version of merging_builder 0.2.0.


text:
Add instanceInitializer

This PR is to pave the way for fixing https://github.com/simplabs/ember-simple-auth/issues/517. I think it is logical to split the fix into multiple commits.

+1

@marcoow Any comment on this?

This would also need to make sure that the existing initializer doesn't use the container's lookup method when that's done in the instance initializer, otherwise you'd still get the deprecation notice. Also there's #532 which takes some more steps to solve the problem which I'm not sure are all actually necessary.

+1

+1

See https://github.com/simplabs/ember-simple-auth/pull/532#issuecomment-113643062 - would be cool to get something like this for the ember-cli-addon branch.

see #564, thanks for the effort!

authors: OpakAlex listepo marcoow quaertym rafaelmezzomo

repo: simplabs/ember-simple-auth


text:
Fix possible missing slashes

This PR makes sure that a trailing slash / always exists at the end of _session.Settings.BaseUri.AbsoluteUri when using absolute reference URIs to keep a valid URL.
Thanks @lordmampf :)

Thanks!

authors: Discjoggy object


text:
Update CLA link

Replace Firebase dynamic links with Bitly alternative
https://firebase.google.com/support/dynamic-links-faq
SC-14984

Test

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

What exactly is missing here to merge the PR?

authors: CLAassistant HenningKuehl IchordeDionysos Prusdrum


text:
Storage stats

Add a new RPC route /dev/stats/storage to get statistics about stored actions.

We can merge it after the issue with droneIO integration is solved. Nice code by the way :+1:

Can you please squash your code into a single signed commit?

Commits squashed and signed! :)

repo: simplestaking/tezedge


text:
Update dobby action to use reusable workflows

https://github.com/simplybusiness/dobby/issues/81

/dobby version patch

repo: simplybusiness/twiglet-ruby


text:
needed a version this way to resolve

tested out node v6.0 and needed to roll my system back. The recommended way was to flush my node_modules as well as uninstalling npm and node.
I did a fresh install of node v4.4.3 which came with npm 2.15.1.
After trying to reinstall the project, the flex-sdk peerDependency would not resolve without specifying a more specific version syntax vs. the wildcard.
Maybe keep this around for a future merge if this rises its head again...

It works with latest 3.x of npm
npm install -g npm

yeah that's likely because you still have node 5.x installed. :)
When they put up node6, they removed node5. So right now with a fresh install you're either pulling down node4 or node6, which contain npm 2.x and npm 4.x respectively.
:tableflip:
At any rate. Here we are. :)

I'm on node 4.4.3 npm 3.8.7 - 3.8.7 should work on node 6 as well.
I think we may be able to find a better version tag that works across npm 2 & 3. Node version shouldn't really affect package installation; just npm version.

authors: erikyuzwa simshanith

repo: simshanith/grunt-mxmlc


text:
make backports an optional dependency

Would it be possible to remove the backports dependency when it's not needed? This would simplify tracing errors and other possible backports related issues.

What about a optional external dependencies that users can opt-in, loading hundreds of files slow down boot time in my app by 0.6s and mega bytes in memory.
# gem 'backports'  # uncomment this line if you are using older rubies < v2.0
gem "sinatra-contrib"

Is this tax worth the extra memory consumption and load time?

Closing as discussed on #133, thanks for your suggestion!

authors: speedmax trevor zzak

repo: sinatra/sinatra-contrib


text:
Benefits of using electron-serve in Angular

Hi,
I am currently developing an Electron application that renders an Angular application using standard win.loadURL('file://…'). It uses the router module from Angular internally for routing tasks and it works ok. What is the advantage of using this library over the standard approach?
Thanks

I don't know anything about Angular development, but I assume the router module is using hashbang instead of real URLs then? That might come with certain downsides.
For example, in the React world, the downsides are:

IMPORTANT NOTE: Hash history does not support location.key or location.state. In previous versions we attempted to shim the behavior but there were edge-cases we couldn't solve. Any code or plugin that needs this behavior won't work. As this technique is only intended to support legacy browsers, we encourage you to configure your server to work with  instead.
- https://github.com/ReactTraining/react-router/blob/master/packages/react-router-dom/docs/api/HashRouter.md

@sindresorhus :pray: for the clarification.

authors: bampakoa sindresorhus

repo: sindresorhus/electron-serve


text:
Running a focused test throws an error when it shouldn't.

Running focused tests results in gulp-jasmine throwing an error when it shouldn't.  The files are below to replicate.
❯ node_modules/.bin/gulp
[11:45:53] Using gulpfile ~/Downloads/jasmine/gulpfile.js
[11:45:53] Starting 'default'...
.
1 spec, 0 failures
Finished in 0 seconds
[11:45:53] 'default' errored after 62 ms
[11:45:53] Error in plugin "gulp-jasmine"
Message:
    Tests failed
Details:
    domainEmitter: [object Object]
    domain: [object Object]
    domainThrown: false

System:

Node 10.9.0
"gulp": "^4.0.0"
"gulp-jasmine": "^4.0.0"

// index.js
describe("add", () => {
    fit("should add", () => {
        expect(1+1).toBe(2);
    });
});

// gulpfile.js
const gulp = require('gulp');
const jasmine = require('gulp-jasmine');

gulp.task('default', () =>
	gulp.src('index.js')
		.pipe(jasmine())
);

Nevermind this is the intended behavior in jasmine 3.0 https://stackoverflow.com/questions/50561109/what-should-i-use-instead-of-fit-and-fdescribe-in-jasmine-3

repo: sindresorhus/gulp-jasmine


text:
Notifications for Participating URL no longer valid

Github seems to have changed the way they conceptualize notifications for the repositories you are participating in and they have reflected this in the URL structure.
URL for repositories that you are participating in have changed from:

https://github.com/someuser/somerepo/notifications/participating

to just:

https://github.com/notifications/participating

So when you have the participating count option enabled in options like below:

When you click on the extension to go to Github, it leads to a 404.
The code needs to be changed to reflect this new URL.

It seems like you're doing it wrong. I just checked and my extension opens the tab to https://github.com/notifications/participating when I have participating checked.
Double-check your root URL settings, as that is where it builds the notification URL from.

@gcochard Damn....I did have that misconfigured. Was messing with something locally and didn't see it. Ugh....My bad!

authors: gauthamchandra gcochard

repo: sindresorhus/notifier-for-github-chrome


text:
npm ERR! Maximum

What's going on about my mac?
node -v v10.0.0
npm - v 5.6.0
npm ERR! Maximum call stack size exceeded happens

That's coming from npm. Try upgrading to latest npm. If that doesn't solve it, you can get npm support here: https://github.com/npm/npm/issues

repo: sindresorhus/sindresorhus


text:
Support For-Each-Join Loops

This PR implements support for joining together two (sorted) arrays of tuples efficiently, using a bitonic sorting network.
The feature is best explained in the language tour:

I couldn't really follow the details of the implementation, but it looks really good to me! Communication-wise it's also quite clear how it should be used!

authors: fkettelhoit raimundo-henriques

repo: sine-fdn/garble-lang


text:
Feedback

Hi @siomari,
One of the requirements of the final project submission was for the front end of your project to be deployed to a web service like Netlify, Vercel or Github pages.
Did you do this? The reason I ask is because I could not see the URL on your GitHub. Please can you reply with the link? Thank you!
Amma

Hi @abakus00
No, I haven't deploy the front end on a web service.

Hi @siomari Thank you for getting back to and confirming you didn't do this. Deploying to a frontend service was one of the requirements to get a certification.
https://courses.consensys.net/courses/take/blockchain-developer-bootcamp-registration-2021/assignments/27500647-final-project-submission.
If you are able to do this in the next few days and resubmit it might possible that your project can be reviewed again. However, I cannot make any promises as I do not make the final decisions... but it is worth a try!


text:
Not able to play when using self hosted navidrome server.

I have a self-hosted navidrome server, which I am able to access via browser and listen to music.
I added the same server to youamp app, and I am able to see the albums / songs listed.
However I am unable to play any music, and nothing happens when I click Play / Play All, and I do not see any album art images for all songs/artists/etc as well.
This server is using a self-signed certificate - could that be causing any issues ? I was able to successfully login successfully, without any issues because of the self-signed certificate, so not sure what the issue could be.
The latest version of the app installed from f-droid store.

Hello, thanks you for reply. Can you play songs from official navidrome demo server, connection info here?

I test it on my own instance of navidrome and it works well. Maybe your instance have special settings or you try play unusual media types? Try to turn on/off transcoding in navidrome player settings.

thank you for your detailed reply @siper !

I am able to successfully play the songs from demo server using youamp on my phone.
On my navidrome server, I only have mp3 and flac formats, no other special media types. I only have a default installation of navidrome, I did not modify any settings on the server.
The transcoding settings on navidrome server was already blank. I tried to change it to mp3 and save it, then back to blank and save it for the "Youamp [okhttp]" player. Max bitrate is also displaying "-". This did not help and I am still having the same issues.

Can you help me understand -

Self-signed certificates - You have mentioned above that your own navidrome server works fine - does your personal navidrome server use self-signed certificates ? and does it serve over https and not via http ?
Does youamp try to download the audio file before playing it ? I check the permissions on the android app settings and it says "no permissions". Should the app have access to any files/folder/media on the android settings ?

No, it's not self signed certificate issue. You can't login, when it's be.
Youamp not uses write permissions, it's play music as stream from url.

Thanks for the reply.
Do you have any suggestions for me on what to check next ? Is there any suggestion forhow to send you any logs from the app that can help to check the issue further ?

Latest Youamp version does't collect any logs or personal data. Maybe in future, I make an option for it. Maybe you can try other selfhosted music stream servers? Like gonic or airsonic-advanced. If you have same error, you can give me an example media file. which not plays, I'll try it on my own instance.

Thank you for your reply.
I am able to confirm that the issue is definitely in scenarios where a self-signed certificate is being used for https in a self-hosted navidrome set-up.
I removed the self signed certificate, and set up my navidrome server to use only via http and not https. Then YouAmp is working properly.
Once I put the self-signed certificate and https back, then the issue is seen again.

No, it's not self signed certificate issue. You can't login, when it's be.

It looks like the app is somehow allowing the login when self-signed certificates are being used for https, but then runs into issues during the playback.

Hello, thanks for you research. I understand the problem. ExoPlayer uses it's own instance of http client, and it not allow self signed certificates. I have a question for you: do you install you self signed certificate in you system?

Yes, on my phone I have installed the rootCA for the self signed certificate.
On Android TV, Fire TV (newer) does not have the option to install self signed certificates.

@accforgithubtest @Kobaratz hello. I published version 1.0.1, that should work, when root CA installed in you system. Can you test it?

authors: accforgithubtest siper

repo: siper/Youamp


text:
ownCloud, Qt Creator, Freenet, rxvt-unicode, etc.

Still seeing a steady flow each day. Will we reach 1000 before July?

I hope so!

authors: crabbedhaloablution siraben

repo: siraben/freenode-exodus


text:
Add lint: don't Import and ImportFrom using the same module

# no!
import re
from re import compile

This reduces the number of symbols a reader needs to remember are available.

For lint-disabling, I think this needs to be flagged on the Import, not the ImportFrom, regardless of the order and locations. That will be interesting.
For example, if someone has this style of usage:
import foo

from foo import alpha
from foo import beta
from foo import upsilon

then the disabled version should be...
import foo  # slyp: disable=W3XX

from foo import alpha
from foo import beta
from foo import upsilon

or something like that.

repo: sirosen/slyp


text:
Add log.Logger's Output method to Logger&Entry

The standard library's *log.Logger type has the method
Output(calldepth int, s string) error

Because it is so minimal, many libraries chose to target
it as an interface, which users could implement to receive
additional log messages:
type Logger {
    Output(int, string) error
}

While it is not overwhelmingly used, it is out there. Implementing
this interface allows us to use logrus.Logger and logrus.Entry
types to receive log messages from such libraries. I chose to log
such messages at the "Info" level, copying the Print* methods. The
"calldepth" argument is ignored.
Addresses issue #118

Why was this issue closed?
It makes perfect sense to me
Thanks

authors: droyo gravis

repo: sirupsen/logrus


text:
Save client secret to instance state during Manual Registration sequence

Quick fix for #139. A more robust solution might be to recurse through any child div.form-groups and collect all the data-prerequsites that way.

Thanks @abjonnes !  @czh-orz could you take a look at this?

Thanks again @abjonnes!  We ended up going with a slightly different fix in #146 that is a bit more consistent with our current approach.  This should be all set on https://inferno.healthit.gov and in master.

authors: abjonnes arscan

repo: siteadmin/inferno