text:
NIF-GO-CC-Bridge.ttl causes most unsatisfiable axioms

GO:0043005, sao-20931889, sao-867568886 unsatisfiable
GO:0043005 asserts equivalence to both of these classes despite the fact that they are disjoint.
Should Neuron Process be disjoint from Neuron Protrusion? I think the answer is yes, and that GO:0043005 is incorrect.

Related
GO:0043198, Trunk, Dendritic Shaft caused by conflict centring on Subregional Part Of Neuron Process

Is the plan to maintain the bridge and a distinct SAO moving forward?
The plan we put into place here: http://www.jbiomedsem.com/content/4/1/20
has us using GO CC as the standard, no need to maintain mappings

Not entirely sure what to do.
I suspect that I can resolve most of these by removing one of the equivalentClass axioms* from the bridge and replacing it with another edge 'alsoSubsumesSAO' or something similar. However I expect that this will cause nasty issues where synonyms in GO are considered as disjoint entities in NIF. Thoughts?

It seems that most of the issues arise directly from equivalentClass assertions in the bridge being made between two disjoint classes (first comment), or cases where a an equivalentClass axiom conflicts indirectly because SAO has disjointness axioms between parts and subparts (second comment).

closed by 3353b34034581c42ae729805a531d641b9585334
The solution was to remove spurious equivalentClass assertions where GO had has_related_synonym and to make the other GO terms equivalentClasses of unions of the disjoint nif terms as they always should have been.

authors: cmungall tgbugs

repo: SciCrunch/NIF-Ontology


text:
Gspread Integration

Replace boilerplate and sheet update with gspread. In large part, this will be future proofing against significant google sheet API updates.

Closing since the pyontutils sheets implementation has received a number of bug fixes and avoids additional dependencies. It is still lacking documentation, but that is not a show stopper. At some point we might try to integrate all the various tabular representations to make it easier to interconvert between them, but ideally we would remove the google sheets part of the workflow entirely, so better not to spend any time on this since we want it to go away entirely.

source: gharchive/issue

authors: tgbugs tmsincomb

repo: SciCrunch/sparc-curation

license: MIT

license_type: permissive

license_source: github-api


text:
HISAT2 aligner

Most of the basic code for running with HISAT2 and building its required references is now written. It seems to compile and start on some of the first processes. There's almost certainly stuff broken, but I figured if I create a pull-request then we can share the testing as it's slow.

Looks real nice, good job. Does it run at all?

It runs a little :) Testing more and bugfixing now, will get back to you when I think it's ready for a final test / merge.

Ok @Hammarn - ready to merge when you're happy (would be great if you could run a test again, haven't run it to completion with more than one file for a while).

Ok I've tested and the Pipeline ran to completion on Milou with human data, so I'm happy to merge this! 👍

source: gharchive/pull-request

authors: Hammarn ewels

repo: SciLifeLab/NGI-RNAseq

license: mit

license_source: bigquery


text:
Use smarter truncation for Fourier Modes

Problem
For the moment, the first $n_{i}$  fourier modes are truncated.
While this works well for most diffusion like problems, this fairs poorly for advection dominated ones.
Solution
Perform an rfftshift and truncate the modes about the center of the array.

It's welcome to open a PR for that.

authors: dynamic-queries yuehhua


text:
Update accordingly to latest marcandre/packable master

My bad, I've PRed wrong repo :(

:tada: Please notify me on a new gem version release, I'll continue with Daru.

New version with your patch has been release (1.3.9).

repo: SciRuby/packable


text:
Merge "default_units" feature branch (to master)

WIP: DO NOT MERGE
We will eventually do this...
It seems we have gained a test failure somehow
Otherwise, nearly ready to go.

Resolving conflict in #3794

Superseded by #3795

authors: abooton pp-mo

repo: SciTools/iris


text:
Finalise whatsnew and version string; update CI to fix.

🚀 Pull Request
Description
Final changes prior to tagging v3.1
A docs-build is available here

Consult Iris pull request check list

the final merge back from the v3.0.x release feature branch has not been included in the v3.1.x release branch.

Oh, I hadn't spotted that at all.
That seems a really serious problem, and should have been in the RC
So
Can we add a mergeback now without releasing another RC ?
Personally, I have the impression that no-one has paid much attention to this one.

Made changes addressing all the text points (I hope).
@bjlittle please re-review.
Still awaiting: mergeback from 3.0.x

The biggest issue I have at the moment is that the final merge back from the v3.0.x release feature branch has not been included in the v3.1.x release branch.

I thought this was done.  The last commit on v3.0.x was in July, and there is a mergeback commit from 10th August in v3.1.x.  Or have I got the wrong end of the stick entirely?

@pp-mo Okay, I finally understand what's happened here... and why I'm confused.
Why did https://github.com/SciTools/iris/pull/4285 change the whatsnew history by collapsing all the v3.0.1, v3.0.2, v3.0.3 and v3.0.4 releases into the whatsnew for v3.0.0 ?
Those patches are separate releases and not part of the v3.0.0 release.
This will now be confusing post-v3.1.0, when comparing documentation with v3.0.x releases.
Specifically, our GH Discussions...

... and all our patch release annotations for v3.0.x...

... link to resources that don't exist in v3.1.0. So when viewing the v3.1.x docs you've now lost the convenience of easily seeing the self-contained patch changes for v3.0.x and instead force users to search.
Also, from a release managers perspective we're also adding an extra step to the release process i.e., collapse the previous release history and blend it together, all of which requires to be reviewed and checked.
Personally, I think we should break from the previous pattern of blending release history together. That was the advantage of leveraging sphinx-panels throughout v3.0.x for patch clarity.

Why did #4285 change the whatsnew history by collapsing all the v3.0.1, v3.0.2, v3.0.3 and v3.0.4 releases into the whatsnew for v3.0.0 ?

As explained there, essentially because we that is what we did to the 2.2.1 changes when making 2.3
- we put the bug fixes into the 2.2 release notes  : see https://github.com/SciTools/iris/pull/3263#issuecomment-467832740
Which after some thought, made good sense to me

Thanks @bjlittle .
Great stuff, I'll now attend to #4320 which I think is really valuable in this context

@pp-mo Thanks for hanging-out so that we would align understanding - it was hard to easily clarify in prose :smile:

authors: bjlittle pp-mo rcomer


text:
supermium@122.0.6261.152: hash check failed

> scoop install extras/supermium
Installing 'supermium' (122.0.6261.152) [64bit] from 'extras' bucket
supermium_122_64_setup.exe (103.9 MB) [=======================================================================] 100%
Checking hash of supermium_122_64_setup.exe ... ERROR Hash check failed!
App:         extras/supermium
URL:         https://win32subsystem.live/supermium/downloads/supermium_122_64_setup.exe#/dl.7z
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    8c500966b7c644dbf40f57c8cc9fd14a60a2acdaf4c5f05425eafe7cc8f9c053
Actual:      ddf7a41ee3444cb32c141a60844d2f0ee7c3fdcf8f8be015328d9b0582400752

should be re-opened, the correct hash is:
3bd306b6bc1bae4a603b7be777ccf159c8de86ceac98e32cc37d7766545f0f88

Expected:    3bd306b6bc1bae4a603b7be777ccf159c8de86ceac98e32cc37d7766545f0f88
Actual:      88cadd4496444da50c756c52b1ac439a115b6026f78ee87bf35b7e549d5607d8

@bt4ibwem8 Please raise next time new issue in form that scoop suggest in case of hash check failure
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=supermium%40122.0.6261.152%3a+hash+check+failed

instead of commenting to the closed issue.
In that case bot will check and resolve the issue automatically (like this one above) that seems to be a bit more productive than waiting for maintainer's reaction.
Looks like 122.0.6261.152 (R4) was silently hotfixed, which couldn't be detected by scoop, and 122.0.6261.152 (R5) uses the same version. I wonder if we could/should add "release" part to version, since naming strategy looks still quite unstable.

authors: aliesbelik bt4ibwem8 quardbreak

repo: ScoopInstaller/Extras

license: Unlicense


text:
Update komorebi.json with aarch64 build for v0.1.30

Adding aarch64 build

[x] I have read the Contributing Guide.

/verify


text:
micswitch: Add version 1.0.217

Closes #5755

MicSwitch is a tool which allows you to mute/unmute your microphone using a predefined hotkey

/verify


text:
veracrypt-np: Add version 1.25.9

Closes https://github.com/ScoopInstaller/Extras/issues/2381
Closes https://github.com/ScoopInstaller/Extras/issues/10728

[x] I have read the Contributing Guide.

/verify

Thank you for mentioning this PR, @aliesbelik.
@FlawlessCasual17, I tested your manifest, and it works for me like a charm. However, as of now, there is already version 1.26.7 available. Scoop installs only version 1.25.9, and scoop update doesn't seem to have an effect. Am I using Scoop incorrectly in this case?

@Gabriel-Graf I changed it

may i ask why this PR is not added to main?

may i ask why this PR is not added to main?

You mean the Main bucket?

sorry for the confusion. i meant why is this PR not merged because i would like to install veracrypt with scoop and the extra bucket-repo.

sorry for the confusion. i meant why is this PR not merged because i would like to install veracrypt with scoop and the extra bucket-repo.

Sorry, but you are going to have to wait, as I am doing already, until somebody with admin privileges wants to merge my Pull Request.

repo: ScoopInstaller/Nonportable


text:
JavaScript

JavaScript
user story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
acceptance criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

added javascript

repo: ScorpionFiko/prework-study-guide


text:
FAQ: How to add a WinForms control programmatically

The WinForms quickstart page https://scottplot.net/quickstart/winforms/ shows how to drag/drop a FormsPlot control onto a Form in the Visual Studio Designer view
... but what if the WinForms control is crashing inside Visual Studio? A Solution is to create and add a FormsPlot to the Form programmatically. It would be useful to have a FAQ page clarifying how to do this to aid troubleshooting when the control crashes inside Visual Studio.

WinForms: Add a ScottPlot control programmatically
Step 1: Open Visual Studio and create a new Windows Forms App
Step 2: Right-click the project, select "Manage NuGet Packages", search for "ScottPlot", and install the "ScottPlot.WinForms" package
Step 3: Edit your Form's .cs file to create a FormsPlot instance and add it to the Form at startup
namespace WinFormsApp21;

public partial class Form1 : Form
{
    readonly ScottPlot.FormsPlot formsPlot1;

    public Form1()
    {
        InitializeComponent();

        // Add the FormsPlot
        formsPlot1 = new() { Dock = DockStyle.Fill };
        Controls.Add(formsPlot1);

        // Add sample data to the plot
        double[] data = ScottPlot.Generate.Sin();
        formsPlot1.Plot.AddSignal(data);
        formsPlot1.Refresh();
    }
}

https://scottplot.net/faq/add-winforms-programmatically/

repo: ScottPlot/ScottPlot


text:
Some way to limit zoom min and max

Suggestion: (Describe your idea here)
Is that any possible to make function 'ZoomFrac' virtual  in class 'CoordinateRangeMutable' ,I am try to override it to limit zoom min and max, Or there are some way else to implement it.
    public class MyRange : CoordinateRangeMutable
    {
        public MyRange() : base(double.NegativeInfinity, double.PositiveInfinity)
        {
        }

        public double MinSpan { get; internal set; }
        public double MaxSpan { get; internal set; }

        public override void ZoomFrac(double frac, double zoomTo)
        {
            double spanLeftX = zoomTo - Min;
            double spanRightX = Max - zoomTo;
            var min = zoomTo - spanLeftX / frac;
            var max = zoomTo + spanRightX / frac;

            var abs = Math.Abs(max - min);
            if (abs < MinSpan)
            {
                return;
            }
            else if (abs > MaxSpan)
            {
                return;
            }

            Max = max;
            Min = min;
        }
    }

I was able to achieve this using Rules, maybe you can leverage them as well.
My code, for you to visualize it a bit:
//This rule will set the zoom-in limit to be able to see 3 x-axis samples at all times
XMinimumSpan = new MinimumSpan(
                    xAxis: Plot!.Axes.Bottom,
                    yAxis: Plot!.Axes.Right,
                    xSpan: 3,
                    ySpan: 0);

//This rule will set the zoom-out limit to be able to see 3 times the PlotXRange  set for the x-axis
XMaximumSpan = new MaximumSpan(
                    xAxis: Plot!.Axes.Bottom,
                    yAxis: Plot!.Axes.Right,
                    xSpan: PlotXRange * 3,
                    ySpan: 0);

Plot!.Axes.Rules.Add(XMinimumSpan);
Plot!.Axes.Rules.Add(XMaximumSpan);

There is also a WinForms demo called AxisRules

It will scroll the axis range when zoom to max or min span limit @jpgarza93

One option is axis rules https://scottplot.net/demo/5.0/#axis-rules
Another option is to use the Plot.RenderManager.RenderStarting event to customize the axis limits to apply custom logic just before each render

authors: ZSYMAX jpgarza93 swharden


text:
Failed prop type: invalid prop source supplied

Looks like the propType for source needs to be updated; it's still expecting PropTypes.oneOfType([PropTypes.string, PropTypes.number]).

I'll totally revamp this library with hooks and less encapsulation to allow accessing the Video component itself in an easier way. I've written that 2/3 years ago and I had way less experience than now for making libs 😅
Waiting for that, I switched the props to any :)

@FrenchSam Released a new 2.0.0 version that could help to solve this issue, also with full TS support

authors: FrenchSam ScreamZ

repo: ScreamZ/react-native-true-sight


text:
[Bug] Error occurs when parsing a calendarObject

When using the export feature of this extension, I found the ics file fails to be imported in google calendar.
Further investigation shows that this is because of some of the courses in workday have a tag (Alternate weeks) in the place where which days of the week the courses are held is displayed.
eg:

This will cause Not A Number being append to the string generated. This is probably because it cannot find the key in the map, and causes some data to become undefined, and when converting to a number explicitly it becomes NAN (I am just guessing because I don't know js well).

Please considering fix this, probably we may should also change the INTERVAL to be 2 if we found this tag. (I am not sure if that's the case).

Thank for this report, this is an interesting problem... I'll take a look and see what I can do

I think a quick fix could be throw an exception when the key is not presented in the map, and push the calendarObject to calendarObjects after that. So if there is an exception then the code would not execute. Definitely need to catch that though.
This will not lost any courses because the problem comes from the function fails to interpret "(Altenalte" and "weeks)" as valid days in a week, but still created a calendarObject, which is redundant and erroneous.
But if  you want to change the interval when the course being held in alternate weeks then there are much more work to do.

Apologies for the slow updates, I believe this bug is (temporarily) fixed by simply ignoring anything that's not a day of the week. In the future we may add support for these tags. Thanks for this report!

authors: SeabertYuan YiRanMushroom

repo: SeabertYuan/better-workday-calendar


text:
Problem: 'Stale' bot spams with notifications

Solution: revert to the default settings of the bot, which are quite reasonable and not spammy.
Signed-off-by: Valery V. Vorotyntsev valery.vv@gmail.com

cc @mssawant @chumakd

@mssawant @chumakd Guys, would you merge this please?

repo: Seagate/cortx-hare


text:
Update generate cortx-all doc

Step 4 on this document https://github.com/Seagate/cortx/tree/main/doc/community-build/docker/cortx-all is not required in generating cortx-all image.
The step raises this error make: *** No rule to make target  iso_generation'.
Issue raised on slack

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/EOS-28397. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

Rose Wambui commented in Jira Server:

Update step 4 of the documentation

Rose Wambui commented in Jira Server:

Completed

Rose Wambui commented in Jira Server:

Fixed on GitHub

Rose Wambui commented in Jira Server:

The document has been updated

authors: cortx-admin r-wambui

repo: Seagate/cortx


text:
HALON-612:  Allow changing TS options in bootstrap cluster.

Created by: qnikst
Env variable HALOND_STATION_OPTIONS will allow to set non-default
options.

Closing as an obsolete

repo: Seagate/halon


text:
🛑 IPFS Gateway 2/2 is down

In 0ecef3c, IPFS Gateway 2/2 (https://ipfs.seanstaffiery.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: IPFS Gateway 2/2 is back up in 420ee47.


text:
Add test for invalid CapturePieceType when en passant is available

See issue https://github.com/SebLague/Chess-Challenge/issues/320

Merged, thanks! (for some reason didn't update here after resolving merge conflicts, so closing).

authors: SebLague laurirasanen

repo: SebLague/Chess-Challenge


text:
Added openURL command and updated README

Added command to directly open a URL on the TV.

Thank you very much for your help! Excellent work!

authors: SebastianSchultz Shoggomo


text:
Create Selenium UI Workflow Tests

Piyush, it would help the team to have these based on this sheet that Seth will give you access to here: https://docs.google.com/spreadsheets/d/1MxpNMTEkhSYptWsJxTy9RdF9kipxYm2jDFzAP-8GhdY/edit#gid=1413317393

Sure thing @ParkeBrown. I'll start working on it and keep you posted with progress. Thanks.

@iPiyushPatel no rush but sometime next week could you call out where you're tracking this?

authors: ParkeBrown iPiyushPatel

repo: SeedCompany/cord-field


text:
Client crashes after multiple login/logout events

Steps to reproduce
Keep server running the entire time. Log in and out of the same account multiple times. Logging in and out of different accounts will produce the same effect with less consistency.
OS and Server Version.
Tested against current commit 20332196 on Linux only. I would love it if someone can confirm on Win or OSX.
Notes
Initially I thought this was related to Having set titles for a character, as it happened twice right after doing so, but I can confirm that it happens without titles as well. It's possible that they are two separate issues masquerading as each other.

I was unable to reproduce this symptom using 2033219 under FreeBSD 11.1-RELEASE 64 bit when logging in with "joe/joe" and backing out from server select back to login screen. I attempted this 50 times in fairly rapid succession with no peculiar result. Do you have to actually connect to the game/map server and logout (waiting 10 seconds) to induce the crash?

In my experience yes. You must actually log into the mapserver (game world)

I never did get the client to crash using the long logout route. I did manage to get the server to crash just moments ago doing this however. The server aborts during a call to the following method and assertion:
Warning : Unhandled unqueue all request: -1
Warning : Unhandled unqueue all request: -1
ACE_ASSERT: file /home/ldilley/Segs/Projects/CoX/Common/Servers/ClientManager.h,
line 96 assertion failed for 'getById(id)!=0'.Aborting...
Abort (core dumped)

void ClientManager::removeById(uint64_t id)
{
    ACE_ASSERT(getById(id)!=0);
    ...
}

Stack trace:
(lldb) target create "./authserver" --core "authserver.core"
Core file '/home/ldilley/Segs/bld/out/authserver.core' (x86_64) was loaded.
(lldb) bt
* thread #1, name = 'authserver', stop reason = signal SIGABRT
  * frame #0: 0x00000008026bf84a libc.so.7`__sys_thr_kill + 10
    frame #1: 0x00000008026bf814 libc.so.7`raise + 52
    frame #2: 0x00000008026bf789 libc.so.7`abort + 73
    frame #3: 0x0000000800fb37f9 libACE.so`ACE_OS::abort(void) + 9
    frame #4: 0x0000000800f853f2 libACE.so`ACE_Log_Msg::log(char const*, ACE_Log_Priority, __va_list_tag*, ACE_Log_Category_TSS*) + 19618
    frame #5: 0x0000000800f8073c libACE.so`ACE_Log_Msg::log(ACE_Log_Priority, char const*, ...) + 348
    frame #6: 0x0000000800f256e5 libACE.so`__ace_assert(char const*, int, char const*) + 197
    frame #7: 0x000000000049b049 authserver`ClientStore<MapClient>::removeById(unsigned long) + 89
    frame #8: 0x00000000004b4d20 authserver`MapInstance::on_disconnect(DisconnectRequest*) + 208
    frame #9: 0x00000000004b417d authserver`MapInstance::dispatch(SEGSEvent*) + 1117
    frame #10: 0x0000000000598aa2 authserver`EventProcessor::svc(void) + 162
    frame #11: 0x000000080101db6d libACE.so`ACE_Task_Base::svc_run(void*) + 77
    frame #12: 0x000000080101e9a1 libACE.so`ACE_Thread_Adapter::invoke_i(void) + 273
    frame #13: 0x000000080101e851 libACE.so`ACE_Thread_Adapter::invoke(void) + 273
    frame #14: 0x0000000800f3af2e libACE.so`ace_thread_adapter + 30
    frame #15: 0x0000000800a66bc5 libthr.so.3`___lldb_unnamed_symbol1$$libthr.so.3 + 325

I concur. This likely disappeared with the implementation of the message bus and thread changes. I've assigned the invalid label and will close this out.

authors: broxen ldilley

repo: Segs/Segs


text:
Environment preparation

Repo/code related

Create new repo for POC
Create .gitignore for VisualStudio
clone repo, be on main branch
cut and paste contents of the project (vs solution) to the new location (new repo)
git push (if needed - git push --force)

Other

Create account on Miro.com

Task done.
Invited @asolowiej94 to POC repo(admin access can be grant once invitation accepted)


text:
🛑 Sekai Viewer is down

In b354bdd, Sekai Viewer (https://sekai.best) was down:

HTTP code: 523
Response time: 595 ms

Resolved: Sekai Viewer is back up in df1f64c after 4 minutes.

repo: Sekai-World/uptime-monitor


text:
Clone logger with different channel name

I'd like to add another logger which is different channel (different component in application). It seems to be a case described in documentation:
https://github.com/Seldaek/monolog/blob/master/doc/01-usage.md#leveraging-channels
The problem is in order to avoid sharing handlers and processors in Dependency Injection Container I had to write ugly piece of code as below:. The main point here is to keep the same UID processor instance for both loggers:
    $logger = new \Monolog\Logger('elasticsearch');
    // reuse UID processor and handlers
    $logger->setHandlers($c['logger']->getHandlers());
    foreach ($c['logger']->getProcessors() as $proc) {
        $logger->pushProcessor($proc);
    }

Easier (and more performant) would be to just clone the logger object and change it's channel name, like:
$logger2 = clone $logger;
$logger2->setName('elasticsearch');

Fixed by cb2778ae77fa64003afb1967e30a4aea07f4503b - you can do $logger2 = $logger->withName('elasticsearch');

Thank you @Seldaek

authors: Seldaek adambro

repo: Seldaek/monolog


text:
Elastica vs Elasticsearch api?

First of thanks for this logger, I am very grateful for having such a useful logger available to me :)
I'm wondering why Monolog is not using the Elasticsearch php API for the Elastic logger? In stead of a 3rd party API that may or may not be up to date and may or may not stay so.
Are there deeper reasons for the choice that I'm not aware of? If not may I suggest using the official API (e.g., as that was the logical search for me was actually that) to integrate with Elasticsearch?
No matter what I would suggest updating the documentation for the handler, for instance referring to the API to use :)

AFAIK Elastica has been the option of choice for a long time, and was started in 2010 while the official client only dates 2013.. That said at this point both might be equally good options. It probably would be possible to update the ElasticSearchHandler to accept either an Elastica client or one instance of the official one, if you are interested in using that one feel free to send a PR for that.

@Seldaek PR is ready :smile:

authors: Seldaek akalongman rohdef


text:
Modal: on close warning in 0.75

Steps
0.75.1 example
0.74 example
Sometimes I have to pragmatically open or close a modal without the help of trigger prop. This is just an example:
class Example extends React.Component {
  state = { open: false }
  constructor(props){
      super(props);
      this._toggle = this._toggle.bind(this);
  }
  render() {
    const { open } = this.state
    return (
      open?
      <Modal
        open={open}
        onOpen={this.open}
        onClose={this._toggle}
        size='small'>
        dgfdgfdgfdgf
      </Modal>
       : <Button onClick={this._toggle} primary>Open</Button>

    )
  }

  _toggle(){
    this.setState({open:!this.state.open})
  }
}

Before 0.75, I can do that without a warning, as shown in the 0.74 example.
Actual Result
However, since 0.75, I'm getting this warning when onClose is fired:
Warning: Can only update a mounted or mounting component. This usually means you called setState, replaceState, or forceUpdate on an unmounted component. This is a no-op.

Is it a bug or do I really need to use a trigger element from now on?
Version
0.75.1

Looks like bug, the investigation and contributions are welcome.

@layershifter
I suspect the new argument {scrolling:false} for trySetState in Modal.js is causing the error in /lib/AutoControlledComponent.js
  handleClose = (e) => {
    debug('close()')

    const { onClose } = this.props
    if (onClose) onClose(e, this.props)

    this.trySetState({ open: false }, { scrolling: false })
  }

The error is thrown when trySetState in /lib/AutoControlledComponent.js is updating the new state { scrolling: false }

@stonecold123 Thanks :+1: Seems, you're right. I will check this in evening and will make PR

repo: Semantic-Org/Semantic-UI-React


text:
Popup: is not rendered when trigger is React.Fragment

Bug Report
Steps
Popup does not appear when the trigger component is React.Fragment (<>)
Expected Result
Popup should be displayed
Actual Result
Popup does not render
Version
0.88.2
Testcase
https://codesandbox.io/s/little-sunset-j0lsf

@sergii-van thanks for reporting, I merged #3998 recently to add meaningful errors. It's impossible to use React.Fragment as we React.cloneElement() to add props to a passed element to the trigger prop.
I also reopened #1187 to consider a better approach than React.createElement().

authors: layershifter sergii-van


text:
Dropdown buttons no longer populate the hidden input field associated with them

I've upgraded my Semantic UI installation from 1.11.4 to 1.12.2 and have found that the hidden input field is no longer populated on my button dropdown.  The code for my dropdown is below:

    <input type="hidden" name="mc_code" value="" />

    Select a Merchant Category Code

            Item A

                    Sub Item A

Sub Sub Item A

Sub Sub Item B

If I select an item from the final dropdown the button text and the hidden input value do not change.  If I try again using version 1.11.4 it works fine.
Thanks.

http://jsfiddle.net/khtpm9qL/
Looks fine to me

Nope. Try clicking the sub menu & you'll see it doesn't appear as the text
of the button (which it should unless specified otherwise). Furthermore,
the input field isn't populated with a value.
The same HTML works fine with version 1.11.4.
Cheers.
On Thu, 7 May 2015 19:39 Patrick Hennessy notifications@github.com wrote:

http://jsfiddle.net/khtpm9qL/
Looks fine to me
—
Reply to this email directly or view it on GitHub
https://github.com/Semantic-Org/Semantic-UI/issues/2223#issuecomment-99972629
.

Can you show a fiddle of it working in 1.11.4?
Also, I'm not sure if i'm understanding the problem correctly, but shouldn't the data-value attribute determine the value loaded into the hidden input?

Yes the data-value does determine that as I understand it.
I've tried to get it working using 1.11.4 on jsfiddle but I can't reproduce
it, which is strange.
I'm sure what I'm expecting is how it should work unless someone else can
correct me?
Thanks.
On Thu, 7 May 2015 21:23 Patrick Hennessy notifications@github.com wrote:

Can you show a fiddle of it working in 1.11.4?
Also, I'm not sure if i'm understanding the problem correctly, but
shouldn't the data-value attribute determine the value loaded into the
hidden input?
—
Reply to this email directly or view it on GitHub
https://github.com/Semantic-Org/Semantic-UI/issues/2223#issuecomment-100006377
.

Keep in mind you do not need to initialize dropdown on sub menus. So don't add the ui class to sub menus or else it will trigger events twice.

repo: Semantic-Org/Semantic-UI


text:
Modal autofocus option doesn't work

The paramenter "autofocus" for the modal() module has no  effect.
I have a modal dialog with a login form inside and and none of the input fields gets focused after show.
The code of modal.js reveals that the problem seems to be the use of $module.filter(':input') to select the input elements. In my case $module is the jquery-wrapped "div" containing all the dialog contents and filter's job is to filter an array of elements by applying a selector to them, not that of "finding" child elements.

This code is just wrong. Sorry about that

What about making this autofocus feature more flexible by allowing it to receive a boolean or a function/callback that would set the focus?
I am thinking about scenarios where I wouldn't want to the set focus on the first input or where my first field isn't exactly an input (e.g a select2 dropdown).

You always have the "show" action callback to perform more complex tasks that's the one i'm using now to focus the first input. By the way, are you sure $(':input') doesn't match a select2 dropdown. I've tried here https://select2.github.io/examples.html but without a clear answer

But we have a multi select :smile:

Right now I am using the show action callback for this, but it doesn't seems quite "right" to me. Also it took me sometime to figure I could pass a callback to it, since there's no example of this in the documentation.
Maybe something with an onVisible callback would make more sense, but it will be called before autofocus :(

@jlukic multi select currently doesn't have all the features I need :(

What features?

I created an issue about they: https://github.com/Semantic-Org/Semantic-UI/issues/2746

Met the problem. Hope 2.1 will come soon.

authors: azazel75 bianjp davialexandre jlukic


text:
giant css file, how to buildsmaller css?

✖ USAGE QUESTIONS → Use these dedicated resources:
Expected Result
A small css file for the site, and than each page imports few modules it needs.
Version
latest 2.3.1
/////////////////////////
Build generates a 160k kb css file. That is HUGE!
I think < 16K should be enough.
Normal use is to load a small site file, and than each page can include module/css it wants.
Documentation says edit semantic json:
https://stackoverflow.com/questions/31842963/remove-unused-modules-components-from-semantic-ui-build
In 2.3.1 semantic json is very small and does not include components or a way for me to disable most.
Help/hint to build a small css file?
(as a feature request, that should be how it's distributed. here is the small site css. If you  need modules in a page, you load them separate)
(aside, it be nice to just be able to use less but I can't build that either, I tried prepros.io and no joy )

Fixed by me: https://github.com/topseed/semi/blob/master/semantic-ui.scss


text:
[Theme] In the end, I made an inverted theme myself

Since it seems that an official inverted theme isn't a priority, I made a super quick, super easy and super dirty edit to the semantic.css and semantic.min.css that results in a completely inverted theme. Finding a way to invert all the colors took the longest, but in the end it turns out there's a website that does just that in a few seconds.
Yes, all the colors are inverted. That includes green -> purple, blue -> orange, etc. I'm hoping to change those back sometime soon.
Here's the gist, hope it'll prove useful to someone 👌
~~https://gist.github.com/Atulin/bdcf51f9c5d62f5bf045b7a0cb73eaa0~~
EDIT:
The dark theme should look much better now. Colors are as they should be and all. I had to write a cute lil' app that grabs all RGB and RGBA colour values, changes them into HSB, flips the Brightness, and writes them back as RGB and RGBA [source code].
It was well worth it, though. Here's the brand new version. Still has some quirks, but they can be ironed out.

Full code
Minified

This is great and I am sure a lot of people will appreciate this. However, I am going to close this since it isn't an issue or enhancement request.

Maybe it would make sense to add this to http://semantic-ui-forest.com/ ?

authors: Atulin hammy2899 hubertguillemain


text:
Support for MSSQL

See https://github.com/Senzing/docker-compose-demo/issues/35
Tasks
:ballot_box_with_check: Check History. Add issue number in comment (e.g. #5)
:ballot_box_with_check: Update CHANGELOG.md
:ballot_box_with_check: Update Dockerfile version
:ballot_box_with_check: Compare to docker-template
:ballot_box_with_check: Pull into master
:ballot_box_with_check: After DockerHub creates image, tag it
:ballot_box_with_check: Create GitHub release
:ballot_box_with_check: Close GitHub issue
Legend
:black_square_button: Not done
:ballot_box_with_check: Done

Pull Requests:

https://github.com/Senzing/docker-web-app-demo/pull/19

repo: Senzing/docker-web-app-demo


text:
🛑 MedicoVet is down

In 60d8028, MedicoVet (https://medicovet.eu) was down:

HTTP code: 429
Response time: 1540 ms

Resolved: MedicoVet is back up in 6c5e310 after 14 minutes.

repo: SeoWeb/upptime


text:
Add plugins support

It allow serenity to support custom plugins (create a new folder plugins in serenity root)
Example plugin:
package.json:

main example:

Console:

Ingame:

It is s good start for a plugin system, there are a few things I would like to rework. Looks good!

repo: SerenityJS/serenity


text:
hide statusbar item

hi, if it's possible to hide statusbar item? I know I can hide this by click statusbar, but it should be better if there is a setting to control this.

Hey DragonBillow. Thanks for the feature request.
I am not a fan of re-implementing features that vscode already has.

authors: Sertion cathaysia

repo: Sertion/vscode-gitblame


text:
🛑 HypeParty is down

In 4d6c8df, HypeParty (https://hypeparty.cr4.live) was down:

HTTP code: 502
Response time: 1062 ms

Known Issue
Resolving of http://id.twitch.tv/ times out.
https://status.twitch.com/ doesn't reflect that issue.
Until the service is reachable again, the website will be down.

Resolved: HypeParty is back up in 6c1da45.


text:
Add sitemap for better SEO against web crawlers

A sitemap is a list of pages on a website. With SPA, it's more difficult for web crawlers such as Google's to index SPAs when compared against non-SPA apps. With sitemaps crawlers can be given information on what pages they should attempt to reach. Ultimately, this will allow all pages from the site to be indexed, and increase engagement with users since all site content will be searchable.

Ignore commit  99fb778, it was removed from remote since it was causing the deployed site to not grab the index page stylesheets on initial page load


text:
is possible to check if a Lua Sprite exist?

Describe your problem here.
heya :D, im actually doing a script for a mods and i need to know if is it possible to check if a certain lua Sprite exist and how to use it, i already sheerch in the doc and i can't find anything.
thanks for your futur help :D
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
nop, im just doing LUA script and other things

if luaSpriteExists('sprite') then
-- do shit
end

i already try that and its not working

i already try that and its not working

well then it's clearly something you're doing wrong, maybe outdated psych version or invalid sprite?

I use the last versionbof psych engine,
I can test Again with another sprite

if luaSpriteExists('sprite') then -- do shit end

does this command even exists

I don’t know…
Its why i asking

if luaSpriteExists('sprite') then -- do shit end

does this command even exists

i don't know, its why i asking dude

if luaSpriteExists('sprite') then -- do shit end

Cette commande existe-t-elle même ?

okay but how i can call it? i already try and its not working

authors: CaptainBaldi Isaagomen Noel3454565FNF

repo: ShadowMario/FNF-PsychEngine


text:
I really need help with this

Describe your bug here.

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
nothing

It looks like the notes aren't being loaded correctly

what’s the null object reference even pointing to

idk

It looks like the notes aren't being loaded correctly

when i pressed the notes it crashed
also the bf sprite didnt play

why close it


text:
Charting editors load null difficulty

Describe your bug here.
so if you don't insert a null difficulty to your data song file, it crashes when debug key is pressed
(source & lua)
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

Update to psych 0.5.2h bc it is fixed

Update to psych 0.5.2h bc it is fixed

It isn't-

Couldn't replicate the bug, record a video.

From what I understand the chart editor in the main menu loads normal difficulty, so if you switch to another song that doesn't have it you get the usual "chart json doesn't exist" error

this happens because you never loaded in a difficulty when accessing through the chart editor instead of the song, which is why this happens since it takes the recent difficulty played on

they are talking about this:

(happens when psych engine hasn't loaded in a song in that current session)

Ok I figured what is the bug, it will try to load the latest difficulty that was loaded in, when the game start, the editor difficulty is null but when you load test, the actual chart is on normal, so the game seach for a null difficulty which doesn't exist, this bug will also happen if you are on a chart with a custom difficulty and then go to another song using the Reload Json button
To make it shorter, the internal difficulty is "normal" while the editor difficulty is null, causing a crash when trying to load any song (even itself)
I do wonder, why doesn't it check if the song even EXIST before trying to go in it... crashing the game because of a spelling mistake/wrong difficulty is so annoying

I am not sure of myself but this line might be at cause (in CoolUtils)

Maybe because Test isn't in a story week, it cannot reach a difficulty and so the array is empty, it just sends out a null which then cause the game to crash since no song have a null difficulty, only a theory tho

If you have no way to acces source code to fix this, adding a null difficulty while working does solve the problem temporarily.


text:
compile shit

Describe your problem here.
i can compile 5.1 fine but i go to compile 5.2h and i get
C:/HaxeToolkit/haxe/lib/flixel-ui/2,3,3/flixel/addons/ui/FlxUIPopup.hx:23: characters 13-19 : Field facing has different type than in flixel.IFlxSprite
C:/HaxeToolkit/haxe/lib/flixel/4,10,0/flixel/FlxSprite.hx:1418: characters 2-45 : ... Interface field is defined here
C:/HaxeToolkit/haxe/lib/flixel-ui/2,3,3/flixel/addons/ui/FlxUIPopup.hx:23: characters 13-19 : ... Int should be flixel.util.FlxDirectionFlags
what the fuck is wrong now?
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No, pure regular source code

I've got something similar but only with html5

authors: Theoyeah Thepipisman


text:
/r/plexshares is apparently gone

Going to https://www.reddit.com/r/plexshares/ shows that the subreddit has been banned. :(

Removed. Thanks.

authors: Shakil-Shahadat abcasada

repo: Shakil-Shahadat/awesome-piracy


text:
Buttons stay "selected" after pressing them on boids and tile game on phone

Very small problem, only worth it if the solution is easy
Button restores to normal size after "x" is pressed
Only an issue on the phone

So I added fixTouchHover() to all html's from fix-touch-hover.js which similates a mouse up at the end of a touch. And I also did
/* Define style for link */
a {
  color: var(--link-color);
  text-decoration: none; /* Remove the underline */
}

a:hover {
  text-decoration: underline; /* Add underline on hover */
}

/* Touch devices need this workaround so that
they dont trigger the hover behavior on tap.
This just reverts touch devices back to the
original value instead of the hover one */
@media (hover: none) {
  a {
    text-decoration: none;
  }
}

For all hovers to cancel them if they are done on a touch screen. Still getting the issue where the button is stuck enlarged after pressed on phone :/

May be worth removing or modifying these. They should work

Kinda fixed it, but now there is a new issue:

[ ] Fix the fact that slider on better boids on phone does not show the numbers when sliding the slider
[ ] Make sure every button on click actually plays a lil color change etc. anim on phone so its obvious it was clicked. Should be a thing, but make sure it works for all desired clickable objs

repo: ShaneBonkowski/ShanesGames


text:
在cpu上能获得加速吗？

在cpu上能获得加速吗？我打印出来的batch都是1

cpu 调大batch 也没啥用，离线情况下batchify以后 差不多能得到1.2的加速比，但是考虑这里你需要等一段时间凑齐batch，所以可以认为几乎没有加速。

谢谢，我尝试过了，有一定效果，wrk 并发测下来大概有3-4倍的提升

cpu 调大batch 也没啥用，离线情况下batchify以后 差不多能得到1.2的加速比，但是考虑这里你需要等一段时间凑齐batch，所以可以认为几乎没有加速。

CPU调大batch还是有用的吧，我测试的结果和batch size=10能比batch_size=1快6-7倍。

authors: alanwang93 gikerch qiuwei

repo: ShannonAI/service-streamer


text:
IDX10503 Exception with Secret Issued from Partner Center for Store Listed Application (SharePoint Provider hosted addin)  - Client Secret is no longer base64 string

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint Add-ins
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
No response
Describe the bug / error
I have a Store listed SharePoint Add-in that was created few years ago, and need to update the secret. Our old Client Secret expired before we noticed. Yesterday in the morning we created a new client secret and removed old ones from the Partner Portal. New client secret that we get from the Partner Portal is no longer a base64 string and when we replaced ClientSecret in our web.config, we got the following error:
System.FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
In order to avoid this issue, we encoded the client secret to base64 string and now we get the following error:
Microsoft.IdentityModel.Tokens.SecurityTokenInvalidSignatureException: 'IDX10503: Signature validation failed. Keys tried: '[PII is hidden]'.
It's already been more than 24 hours since we created new Client Secret, so we believe it should already propagate correctly.
Is the basic encoding to base64 a wrong choice, or what could be a reason for our application not to validate a token properly?
I have also checked the new client secret using Connect-PnPOnline via powershell and without any additional encoding the secret works.
Thanks in advance - as this is about our live application, I would appreciate any help.
Steps to reproduce

Locate a SharePoint Store listed, provider hosted add-in, created several years ago.
Create a new Secret in Partner Center
Update the application with the new secret.

Expected behavior
The expected behaviour is for the JWT token to pass validation correctly.

We have also noticed that related App Registration in Portal Azure is missing valid Certificate:

Old certificates were added automatically when we created new Client Secret in Partners Portal.
At the same time, new client secret created in Partners Portal was automatically added in our App Registration in portal azure.

Any ideas? Should we manually create a new certificate?

@RafalUrbanski : Can you please open a ticket with Partner Center for this? Did you associate your Add-In with a tenant?

@jansenbe We opened tickets everywhere we could, also with Partner Center, hoping anybody had a same issue. Partner Center need 1-2 business to validate, we are still waiting for a response.
We associated Microsoft Entra Tenant with Microsoft Partner Center (acording to this article https://learn.microsoft.com/en-us/partner-center/account-settings/multi-tenant-account#add-a-microsoft-entra-tenant-to-your-account )

@RafalUrbanski : great to hear you got the issue resolved and thanks for sharing the write-up, sharing is caring 💖

authors: RafalUrbanski jansenbe

repo: SharePoint/sp-dev-docs


text:
Everything worked  -- Until .... we "transform-the-plain-javascript-code-to-typescript"

[Enter feedback here]
This example how-to went into the trash after transforming it to use Typescript. Gulp stopped "serving" (no serve task error)
after that  I'd found fixes and work-around for these only to get the webpart serving and then failing in the browser with the errors below.
These are same type of errors I had gotten using React to create a simple data table from a list.
I have built the same kind of web part using JavaScript or React (have not attempted PnPS and don't want to)
the project framework and all moving pieces seem so fragile and/or arbitrary what is going break when.
this sucks frankly.
Tomorrow  I will repeat this exercise but won't "improve it by moving to TS."  for me it these other frameworks barely work after  many hours of petty errors only have a some package break the whole damn thing.
PS D:\SPFx_Builds\DataTablePart> npm ls -g --depth=0
C:\Program Files\nodejs
+-- @microsoft/generator-sharepoint@1.12.1
+-- @microsoft/sp-build-web@1.12.1
+-- @microsoft/sp-core-library@1.12.1
+-- @microsoft/sp-lodash-subset@1.12.1
+-- @microsoft/sp-module-interfaces@1.12.1
+-- @microsoft/sp-office-ui-fabric-core@1.12.1
+-- @microsoft/sp-webpart-base@1.12.1
+-- @microsoft/sp-webpart-workbench@1.12.1
+-- @types/webpack-env@1.16.0
+-- gulp@4.0.2
+-- npm@6.4.1
`-- yo@3.1.1
[21:44:06] Error - [tslint] Failed to load D:\SPFx_Builds\DataTablePart\tslint.json: Invalid "extends" configuration value - could not require "./node
_modules/@microsoft/sp-tslint-rules/base-tslint.json". Review the Node lookup algorithm (https://nodejs.org/api/modules.html#modules_all_together) for
the approximate method TSLint uses to find the referenced configuration file.
[21:44:06] Finished subtask 'tslint' after 4.49 s
Error - [tslint] Failed to load D:/SPFx_Builds/DataTablePart/tslint.json: Invalid "extends" configuration value - could not require "./node_modules/@microsoft/sp-tslint-rules/base-tslint.json". Review the Node lookup algorithm (https://nodejs.org/api/modules.html#modules_all_together) for the approximate method TSLint uses to find the referenced configuration file.
Error - [tsc] src/webparts/dataTableWebPart/DataTableWebPartWebPart.ts(90,17): error TS2416: Property 'dataVersion' in type 'DataTableWebPartWebPart' is not assignable to the same property in base type 'BaseClientSideWebPart'.
Error - 'tsc' sub task errored after 4.55 s
Browser errors after working through gulp gulch.
Uncaught (in promise) Error
at t [as constructor] (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:283)
at new t (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:914)
at Function.e.buildErrorWithVerboseLog (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:914)
at Function.e.buildLoadComponentError (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:914)
at sp-webpart-workbench-assembly.js?uniqueId=NTnAt:914
sp-webpart-workbench-assembly.js?uniqueId=NTnAt:283 Uncaught (in promise) Error: ***The value for "error" must not be undefined
at Function.e.isNotNullOrUndefined (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:283)
at Function.window.spModuleLoader.e.logError (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:479)
at sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383 Uncaught TypeError: Cannot read property 'searchablePlainTexts' of undefined
at sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
at e._serializeAsJson (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383)
at e.serialize (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383)
at e.serialize (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383)
at e.savePageState (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:105)
SPAndroidAppManifest.aspx:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
DevTools failed to load source map: Could not load content for https://localhost:4321/temp/manifestsFile.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
5sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383 Uncaught TypeError: Cannot read property 'searchablePlainTexts' of undefined
at sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
at e._serializeAsJson (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383)
at e.serialize (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383)
at e.serialize (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383)
at e.savePageState (sp-webpart-workbench-assembly.js?uniqueId=NTnAt:105)
(anonymous) @ sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
e._serializeAsJson @ sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
e.serialize @ sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
e.serialize @ sp-webpart-workbench-assembly.js?uniqueId=NTnAt:383
e.savePageState @ sp-webpart-workbench-assembly.js?uniqueId=NTnAt:105

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

ID: b56fb9ec-59c2-413f-eaa2-e84abfb30211
Version Independent ID: ca610020-3018-fd78-1da5-7f00fed5b04f
Content: Migrate jQuery and DataTables solution built using Script Editor web part to SharePoint Framework
Content Source: docs/spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Looks like you have two errors here.

You need @microsoft/sp-tslint-rules as a devDep so base-tslint.json resolves e.g. this file

Error - [tslint] Failed to load D:/SPFx_Builds/DataTablePart/tslint.json: Invalid "extends" configuration value - could not require "./node_modules/@microsoft/sp-tslint-rules/base-tslint.json". Review the Node lookup algorithm (https://nodejs.org/api/modules.html#modules_all_together) for the approximate method TSLint uses to find the referenced configuration file.

You have a TypeScript compilation error (type mismatch)

Error - [tsc] src/webparts/dataTableWebPart/DataTableWebPartWebPart.ts(90,17): error TS2416: Property 'dataVersion' in type 'DataTableWebPartWebPart' is not assignable to the same property in base type 'BaseClientSideWebPart'.
Error - 'tsc' sub task errored after 4.55 s

Thanks for the suggestion
Number 1  I will give that a try to repair.
Number 2 I will revisit after implementing your first   suggestion.
One other thing - is there an issue with using WinServer12  vs. Win10 as development machine?
I use a my develop machine is laptop running Win12 Server to host VMs etc.
I have access to other machines this is my personal lab machine.


text:
Microsoft Teams spfx webpart - error initializing application error cannot read properties of undefined (reading 'componentType')

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[X] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[X] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version V16
Node.js version v16.13.1
SPFx for Teams used Teams Toolkit

Issue description
Microsoft teams and SPFx 16
We are deploying spfx webpart to microsoft teams (in base of Teams Toolkit) and the site: https://learn.microsoft.com/de-de/microsoftteams/platform/sbs-gs-spfx?tabs=vscode%2Cviscode&tutorial-step=1
I receive this error: Fehlerdetails: Error: Error initializing application. Error: TypeError: Cannot read properties of undefined (reading 'componentType')
Any idea please ?
Best regards
Amir MSAI

@amirmsai - could you provide details on when you're getting this error?
what is the call stack?
are you calling teams-js initialize in your code?

@AJIXuMuK  sorry i dont have any details to describe the error; in debug it working good, but if i install the solution in my Teams i receive this error

@amirmsai - you should not call initialize by yourself.
We initialize the sdk for you. You just need to use the instance provided by web part's context (this.context.sdks.microsoftTeams).

Hi @AJIXuMuK  it's not working, i have the same error:  Error initializing application. Error: TypeError: Cannot read properties of undefined (reading 'componentType')

@amirmsai - could you share your code? You can send it to me directly using aterentiev@microsoft.com

@AJIXuMuK  E-mail has been sent
Thanks

The solution, local debugging and deployment using both SPFx generator and Teams Toolkit work fine for me.
@amirmsai could you try to create a new solution from scratch and double-check your user has appropriate permissions to install apps both to SharePoint and Teams.

authors: AJIXuMuK amirmsai


text:
js-display-list sample update from drop3 to GA

Q
A

Bug fix?
yes

New feature?
no

New sample?
no

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
The js-display-list sample updated from drop3 to the GA version of the SharePoint Framework.
Small refactoring around the JsDisplayListWebPart.ts class to make it compatible with the GA version.
Additional check when the list does not exist added.
Minor string interpolation fixes.
The loader removed because of undefined behavior. Will investigate when have some time.
README.md updated.

thx Velin, appreciated. I'll double check that everything is good to go soon and get this processed.

thx Velin, appreciated.

authors: VelinGeorgiev VesaJuvonen

repo: SharePoint/sp-dev-fx-webparts


text:
Issue with reading a single column csv

While reading a csv file, if the csv file contains a single column and if the header contains more than 10 characters with space, the column is split into two.
For eg:
If column name is "sepal length", it is read as ["sepal leng", "th"]
~On examining your code, I found that function prn_to_aoa_str defined in xlsx.js to be cause of this issue.~
Edit: I was wrong. If the file doesn't have tabs or comma, file is read as a prn file. Can you add any delimiter option for csv?

I'm also facing the same issue. :(

This should have been fixed in the latest version (the PRN processing is disabled).  Please confirm you are using a version above "0.16.2"

Thanks.
It is fixed in latest version :)

authors: SheetJSDev kirupakaranh-opex sachingoel

repo: SheetJS/sheetjs


text:
tie_params doesnt work ?

I am trying to tie my length scales together using m.kern.rbf.tie_params('.*len') but I get the error: AttributeError: 'Add' object has no attribute 'tie_params'.
So, has the syntax changed or we cannot tie params anymore ?

No it is not implemented unfortunately. The easiest is to write a wrapper kernel, that does the tie itself.

On 3 Dec 2016, at 04:49, Kshitij Tiwari notifications@github.com wrote:
I am trying to tie my length scales together using m.kern.rbf.tie_params('.*len') but I get the error: AttributeError: 'Add' object has no attribute 'tie_params'.
So, has the syntax changed or we cannot tie params anymore ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am quite new to all this so would you mind suggesting how can I write a wrapper kernel ?

Here is how to write a kernel:
http://pythonhosted.org/GPy/tuto_creating_new_kernels.html
By wrapper kernel we mean a new kernel around the kernel you want to have, binding the lengthscales together (setting them to be equal to its lengthscale). Make sure you fix the lengthscales of the tied kernels and unlink their parameters (e.g. kern.unlink_parameter(kern.lengthscale)).
Sry for the inconvenience, but noone got around to actually getting the automatic tieing to work.

repo: SheffieldML/GPy


text:
Issue #93: simple workaround for infeasibility of Monte Carlo

These changes were motivated by issue #93 where it was found that the random samples used to initialize the acquisition function maximization under constraints may struggle to find feasible points in some cases.
Simple changes are made to allow users to instead define their own sampling function for the continuous variables:

A new class variable, cont_sampler, is introduced in GPyOpt.methods.bayesian_optimization.BayesianOptimization which is set through **kwargs. cont_sampler is a function of two variables that returns samples of x. By default, cont_sampler = None.
cont_sampler is then passed in during the initialization of GPyOpt.optimization.acquisition_optimizer.AcquisitionOptimizer where, if there are continuous variables, cont_sampler is then passed through **kwargs to the initialization of GPyOpt.optimization.acquisition_optimizer.ContAcqOptimizer where the member variable sampler is assigned to cont_sampler (or None, if the key does not exist).
When GPyOpt.optimization.acquisition_optimizer.ContAcqOptimizer.generate_initial_points() is called, if sampler == None then the samples are initialized as in the past; otherwise, the customized sampling is computed by calling self.sampler(self.free_bounds, self.n_samples).
One last change was adding **kwargs to __init__ in the Opt functions of GPyOpt.optimization.optimizer to transmit the **kwargs (there are key errors otherwise).

These changes did not create any new errors from running the unit tests (and worked on my topical application where a sampler was necessary). Although, at least on the two computers I tried, the devel branch (without the above changes) does not pass the unit tests with 1 error and 5 fails (which are the same after my changes).
In issue #93, there was discussion of taking an automatic approach to finding a feasible initialization. I ended up turning against this because it is not generally possible to guarantee convergence to a feasible point for any given set of nonlinear constraints (at least not in a timely manner). More related to this is brought up in a reply in the discussion of the issue.
Conflicts:
GPyOpt/methods/bayesian_optimization.py
GPyOpt/optimization/acquisition_optimizer.py

HI @jkaardal,
As you may have noticed, we have refactored a large part of the code un our release last week. Do you think it would be possible to merge your changes there and send another PR?
Sorry about this and thanks so much for your contributions!
Javier

Hi @javiergonzalezh. It looks like merging the changes shouldn't be too much trouble. I will likely work on making these changes this week or over the weekend. Thanks for the notification!

That's great! Just let us know when you are ready for the merge then.

An updated version of the pull request is here: https://github.com/SheffieldML/GPyOpt/pull/123.

authors: javiergonzalezh jkaardal

repo: SheffieldML/GPyOpt


text:
[bug]: dont use random port in dev mode

What area(s) will this request affect?
App
What type of change do you want to see?
New feature
Overview
I meet some problems to develop Shopify app with my colleague at the same time. If I run the Shopify app dev which overwrites the URLs whitelist and app URL and  having to collide with  coding togetther
So that I find the solution about this , If we use the localhost and the same port we can develop at the same and no collision in Shopify app-bright mode
But the problems is when use shopify app dev to dev app which use a random port that make me confuse why we can Specify port on Shopify app dev
Motivation
Hoping support Specify port on Shopify app dev,  no random port

You may find this valuable.
Should be available in the next prerelease and minor release when they each come out.

authors: amcaplan schapicool

repo: Shopify/cli


text:
Issues with graphql-relay 0.9.5 and graphql 0.13

Looks like the interface for connections has changed somehow
NoMethodError - undefined method `offset' for #<Team:0x00000007fc2d60>:
  activemodel (4.2.6) lib/active_model/attribute_methods.rb:433:in `method_missing'
  graphql-relay (0.9.5) lib/graphql/relay/relation_connection.rb:32:in `sliced_nodes'
  graphql-relay (0.9.5) lib/graphql/relay/relation_connection.rb:23:in `paged_nodes'
  graphql-relay (0.9.5) lib/graphql/relay/relation_connection.rb:82:in `paged_nodes_array'
  graphql-relay (0.9.5) lib/graphql/relay/relation_connection.rb:5:in `cursor_from_node'
  graphql-relay (0.9.5) lib/graphql/relay/edge.rb:14:in `cursor'
  graphql (0.13.0) lib/graphql/field.rb:111:in `block in build_default_resolver'
  graphql (0.13.0) lib/graphql/field.rb:67:in `resolve'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:69:in `block in get_middleware_proc_from_field_resolve'
  graphql (0.13.0) lib/graphql/schema/middleware_chain.rb:24:in `call'
  graphql (0.13.0) lib/graphql/schema/rescue_middleware.rb:34:in `call'
  graphql (0.13.0) lib/graphql/schema/middleware_chain.rb:24:in `call'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:58:in `get_raw_value'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:26:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:98:in `resolve_field'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:18:in `block in result'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:17:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/value_resolution.rb:72:in `non_null_result'
  graphql (0.13.0) lib/graphql/query/serial_execution/value_resolution.rb:23:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:45:in `get_finished_value'
   () home/andrew/bundle/ruby/2.3.0/bundler/gems/graphql-batch-9cf8341196a8/lib/graphql/batch/execution_strategy.rb:56:in `get_finished_value'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:30:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:98:in `resolve_field'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:18:in `block in result'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:17:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/value_resolution.rb:72:in `non_null_result'
  graphql (0.13.0) lib/graphql/query/serial_execution/value_resolution.rb:23:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:45:in `get_finished_value'
   () home/andrew/bundle/ruby/2.3.0/bundler/gems/graphql-batch-9cf8341196a8/lib/graphql/batch/execution_strategy.rb:56:in `get_finished_value'
  graphql (0.13.0) lib/graphql/query/serial_execution/field_resolution.rb:30:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:98:in `resolve_field'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:18:in `block in result'
  graphql (0.13.0) lib/graphql/query/serial_execution/selection_resolution.rb:17:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution/operation_resolution.rb:20:in `result'
  graphql (0.13.0) lib/graphql/query/serial_execution.rb:17:in `execute'
   () home/andrew/bundle/ruby/2.3.0/bundler/gems/graphql-batch-9cf8341196a8/lib/graphql/batch/execution_strategy.rb:4:in `execute'
  graphql (0.13.0) lib/graphql/query/executor.rb:38:in `execute'
  graphql (0.13.0) lib/graphql/query/executor.rb:15:in `result'
  graphql (0.13.0) lib/graphql/query.rb:47:in `result'
  graphql (0.13.0) lib/graphql/schema.rb:55:in `execute'
  app/controllers/api/v1/graph_ql_controller.rb:14:in `execute'

graphql-batch is in no way related to graphql-relay and we aren't experiencing any problems when using it with graphql gem version 0.13.  Please provide steps to reproduce your problem rather than just a backtrace that references your application code.

Sounds like: https://github.com/rmosolgo/graphql-relay-ruby/issues/38

Whoops. Thanks

authors: andrewfader dylanahsmith rmosolgo

repo: Shopify/graphql-batch


text:
Log error

What are you trying to accomplish with this PR?
Passes errors to reject so that during watch it will output to console.
Fixes #40
Checklist
For contributors:

[x] I have updated the documentation in the README file to reflect these changes, if applicable.

For maintainers:

[x] I have :tophat:'d these changes.
[ ] I have bumped the package.json version in a separate PR, if applicable.

You're right - thanks for catching that

repo: Shopify/node-themekit


text:
🐛 add gem read me to template so it wont get overwrite

Description
Fixes (issue #)
Close https://github.com/Shopify/quilt/issues/964

My understanding was that this PR backfills the missing ones and #977 tries to make sure it doesn't happen again.

@ismail-syed the root Readme is written from scratch every time, so any changes to it in a PR like this will get overwritten on the next generate.

Its two different approaches to the same thing.
I opt for a manual method of adding it to the README template because I dont think we will have many gem packages in the future and they can be static.
Matt opt for dynamically generating it so it will always be up to date with the shape of the repo.
Since Matt already merged his PR, I will be closing this one.

authors: cartogram ismail-syed michelleyschen

repo: Shopify/quilt


text:
Should I make a PR for Gift card adjustment?

I found myself needing a resource for Gift card adjustments and so I fashioned the following:
module ShopifyAPI
  class GiftCardAdjustment < Base
    include Metafields
    include DisablePrefixCheck

    conditional_prefix :gift_card

    def self.element_name
      "adjustment"
    end

    def self.create(**params)
      raise ArgumentError, "No :gift_card_id provided." unless params[:gift_card_id]
      super
    end
  end
end

Would it be useful for me to comb this into a PR?

That sounds right to me. Thanks!

Hello @joallard
I am trying to implement GiftCardAdjustment API. Is it worked for you? Have you done any PR for the same?
Thanks

@sachingevariya I have not made a PR, but the above workaround worked fine if I recall correctly

Ok, thanks. Let me try.

Yes. It helped me. Thanks to @joallard

authors: joallard sachingevariya


text:
Backwards compatible https

What it does and why:
Checklist:

[x] Testing & QA: Passes tests and linting.
[x] :tophat:: I have manually tested these changes.

Related issues:
Closes:

@Gamingpc this is an old development branch that was not intended to be merged to master in this state. Many of the changes are actually in master already. Is there a specific change you would like to see?

authors: Gamingpc ericroberts


text:
Auto Select gift card code

Problem
The auto select gift card code doesn't work.
Replication steps
Issue a gift card and click the gift card code.
More Information
Fix
Change:
 {{ gift_card.code | format_code }}
to:
 {{ gift_card.code | format_code }}

Also seems to be an issue with the Giftcard value. (It isn't displayed)

repo: Shopify/slate


text:
Managing Divergence Between SIF Agents and Eliza Repositories

Related Ticket - https://github.com/ai16z/eliza/issues/305
Description:
The SIF Agents project is currently based on a fork of the Eliza repository. As both projects evolve independently, maintaining compatibility and managing code divergence becomes a crucial concern.  This ticket aims to create a plan for managing the relationship between the two repositories, balancing the need for customization within SIF Agents with the desire to benefit from and contribute to the upstream Eliza project.
Problem:

Diverging Codebases: As we add SIF-specific features, our codebase will increasingly differ from the upstream Eliza repository.
Merge Conflicts:  Merging changes from Eliza into SIF Agents (or vice versa) will become more complex and prone to conflicts as the divergence increases.
Maintenance Overhead: Keeping track of changes in both repositories, resolving merge conflicts, and maintaining compatibility requires significant effort.
Duplication of Effort:  We might inadvertently re-implement features already developed in Eliza or miss out on valuable improvements made upstream.

Goals:

Minimize Divergence:  Develop strategies to minimize code divergence where possible.
Streamline Merging:  Establish a process for efficiently merging changes between repositories.
Reduce Maintenance Overhead:  Reduce the time and effort required to maintain compatibility.
Maximize Code Reuse: Leverage existing Eliza functionality and avoid duplicating effort.
Contribute Back to Eliza:  Contribute our SIF-specific improvements and bug fixes back to the Eliza project when appropriate.

Near-Term Plan (Given Current Resources):

Identify Core Divergences: Conduct a thorough review of the SIF Agents codebase and identify the key areas where it deviates from Eliza. Document these divergences clearly.

Modularization:  Where feasible, refactor SIF-specific code into separate modules or plugins that can be easily integrated with or detached from the core Eliza framework. This minimizes changes to the core Eliza code and simplifies merging.

Regular Upstream Syncing: Establish a regular schedule (e.g., weekly or bi-weekly) for syncing changes from the Eliza repository into SIF Agents.  This reduces the accumulation of merge conflicts.

Automated Testing: Implement comprehensive automated tests that cover both SIF Agents-specific functionality and core Eliza features.  This helps identify integration issues early during the merge process.

Dedicated Merge Team (if resources allow): Assign a small team or individual to be responsible for managing the merge process, resolving conflicts, and ensuring compatibility.

Documentation: Document the merging process clearly, including branching strategies, conflict resolution procedures, and testing protocols.

Future Considerations (Speculative):

Upstream Contributions:  Actively contribute SIF-specific features and improvements back to the Eliza repository as plugins or modules when they are of general value to the community.  This reduces long-term divergence. Work closely with the Eliza maintainers to coordinate these contributions.

Automated Merging Tools:  Investigate and potentially implement automated merging tools or strategies to simplify the merging process and reduce manual effort.

Fork Management Tool: Consider whether it would be good to use an actual fork management tool to help track changes, visualize diffs and manage the merging process more efficiently.

Shared Core Library:  Explore the feasibility of creating a shared core library that both Eliza and SIF Agents depend on.  This centralizes common functionality and reduces code duplication. This involves considerable effort upfront to refactor both code bases.

Inter-Repository Communication Protocol:  If AI-driven code synchronization becomes a future goal, developing a structured protocol or language for communication between agents managing different repositories could be beneficial.  This is a long-term, research-oriented consideration.

Acceptance Criteria:

A clear plan is documented for managing divergence between the SIF Agents and Eliza repositories.
The plan includes specific steps for minimizing divergence, streamlining merging, and reducing maintenance overhead.
The plan addresses both near-term resource constraints and future possibilities.
The plan is communicated effectively to all SIF Agents developers.

This ticket outlines the major challenges and provides concrete steps for managing the divergence between your forked project and the upstream Eliza repository. The key is to prioritize minimizing divergence, streamline merging, and establish clear processes and responsibilities for managing the relationship between the two codebases. This proactive approach will reduce maintenance overhead and maximize code reuse while allowing the SIF Agents project to benefit from ongoing developments in Eliza.

https://x.com/somewheresystem/status/1857384948002418746
In principle, there's no reason we need to only consider this for Eliza. We can also consider it for other forks.

https://github.com/timshelxyz/eliza

https://github.com/ai16z/eliza/issues/764 Key issue that needs to be resolved?

This is completely unnecessary.
Forks are BAD and should be avoided at any cost. Forks happen when people cannot agree upon something fundamental, which is basically a failure of project management (think LibreOffice / OpenOffice). If this happens it's a lose/lose situation.
The rules are simple: use upstream UNLESS we have something that cannot, or should not, be part of upstream for reasons beyond our control.
Either our code should use upstream as a library, or upstream should use our code as a plug-in. Any differences need to be isolated, minimized, and constantly and carefully maintained to preserve compatibility.
As for Git workflow, "forking" model simply means that we are keeping working branches in our private repos (one per developer) until they are ready to be merged. This is only a matter of hygiene, i.e. to avoid over-polluting the repo with too many working branches.

Makes sense @jzvikart I would say we are probably leaning towards having our code use upstream as a library. As we will end up being quite opinionated, and are not necessarily sure how much or what to send back to upstream at this moment.

Yeah, I agree, but I just want to clarify that until we actually come up with an alternate form of code management, we're going to stick to the current strategy, which is that we are shipping features to our fork and just maintaining our fork alongside the main repo. Once we come up with a better strategy for managing this stuff, we can revisit. Also keep in mind that we are stakeholders of both our codebase and the ai16Z codebase.

authors: jkbrooks jzvikart

repo: Sifchain/sa-eliza


text:
Audio Player not running in isolates.

I am trying to fetch the audio from server and extracting waveform from it in background in an isolate to stop the main UI isolate from blocking.
Code:
Future<void> downloadAudioIsolate(String docsPath) async {
  PlayerController controller = PlayerController(); // Initialise
        // Extract waveform data
        final waveformData = await controller.extractWaveformData(
          path: 'path',
          noOfSamples: 100,
        );
        Map<String, dynamic> jsonData = {
          "data": waveformData,
        };
        String jsonString = jsonEncode(jsonData);
        controller.dispose();
        final dataPath = File("$docsPath${audio.path.split('/').last.split(".mp3").first}.json");
        await dataPath.writeAsString(jsonString);
        // Write audio to file
        await filePath.writeAsBytes(audioResponse.bodyBytes);
}

main->
void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  final appDocDir = await getApplicationDocumentsDirectory();
  // Spawn the isolate and wait for completion
  await Isolate.spawn(downloadAudioIsolate, appDocDir.path);

  // Continue with your main UI logic
  runApp(const MyApp());
}

ERROR:

E/flutter ( 5223): [ERROR:flutter/runtime/dart_isolate.cc(1107)] Unhandled exception:
E/flutter ( 5223): 'package:flutter/src/services/platform_channel.dart': Failed assertion: line 554 pos 7: '_binaryMessenger != null || BindingBase.debugBindingType() != null': Cannot set the method call handler before the binary messenger has been initialized. This happens when you call setMethodCallHandler() before the WidgetsFlutterBinding has been initialized. You can fix this by either calling WidgetsFlutterBinding.ensureInitialized() before this or by passing a custom BinaryMessenger instance to MethodChannel().
E/flutter ( 5223): #0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
E/flutter ( 5223): #1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
E/flutter ( 5223): #2      MethodChannel.setMethodCallHandler (package:flutter/src/services/platform_channel.dart:554:7)
E/flutter ( 5223): #3      AudioWaveformsInterface.setMethodCallHandler (package:audio_waveforms/src/base/audio_waveforms_interface.dart:196:20)
E/flutter ( 5223): #4      PlatformStreams.init (package:audio_waveforms/src/base/platform_streams.dart:37:44)
E/flutter ( 5223): #5      new PlayerController (package:audio_waveforms/src/controllers/player_controller.dart:81:32)
E/flutter ( 5223): #6      downloadAudioIsolate (package:isolate_demo/main.dart:48:37)
E/flutter ( 5223):

Hello @SyedZeeshanAijaz,  I just want to confirm one thing, If we run the above method downloadAudioIsolate as standalone method(without isolate), does it working for you?

Flutter does not support this type of functionality in isolates, and there is already an open issue in the official repo. #119207


text:
Select input on show

Is your feature request related to a problem? Please describe.
It is not possible to select or focus input.pcr-result on 'show'.
I went through the code, I noticed the selection is disabled on launch [I suppose in order to prevent mouse scrolls altering the value before someone clicks inside the input?]
Describe the solution you'd like
Add the option to select/focus the result input on 'show'
Describe alternatives you've considered
N/A
Additional context
My use case: I need to enable a user of my app to quickly add a new color by pasting the contents of the clipboard.
I noticed I am not able to attach an event listener in order to use 'Enter' key to save. Possibly related.

Here you go. The browser needs to to two repaints (Recalculating position and updating HTML Properties if I remember correctly).

That fixes it. Thanks!

authors: Simonwep nevilleomangi

repo: Simonwep/pickr


text:
Why one package.json is not enough? Potential project restructure

There are two package.json's right now and I read the docs on why it is like that. But I just noticed that the root one uses only dev dependencies and the other one uses "normal" dependencies. If you were to merge them into a single one there would be an easy way to tell which dependency is for what.
Am I missing something?

@deiucanta
Yes you could separate dependencies using devDependencies but then electron-packager wouldn't know the different and also include all those devDependencies into your production builds where they will never be used. In terms of electron-builder, this is actually possible.

@SimulatedGREG thanks
Are you aware if electron-packager is planning to do something about it? The overhead is not that big when working with two package.json files but if we can improve the developer experience... why not?

@deiucanta you'd want to check their issues / projects for that. Like @SimulatedGREG said though, electron-builder ( which this boilerplate provides ) supports the single-manifest setup you're asking for.

Well it turns out electron-packager did release make an update to --prune devDependencies. This is something that was not available at the initial creation of this boilerplate. Its worth considering, but IMO I feel a separate app folder is a much easier structure to use. Typically when you put all source files and dev configurations in one space its gets cluttered quickly.

electron-builder doesn't require you to use separate directories. Only production deps are packed and only production native deps are rebuild. And files/extraFiles/extraResources allows you to easily configure files to pack.

I'm fully aware now that both packagers handle this properly, but I'm still not convinced putting everything in one document space really keeps things organized. This goes probably into a bigger discussion about whether or not its worth putting all dev configuration files into its own folder (maybe .electron-vue?).

Here's the other side of the coin though - in this ecosystem there's already a lot of muscle memory involved in installing dependencies. In a node app the root project folder is the only place we install things. We've already got a clear separation within package.json between dependencies and devDependencies.
Separating them further into two files kind of flies in the face of the ecosystem, and I think the electron packaging tools acknowledged this to some extent by supporting the single file structure.
TL:DR; there's a reason both major packaging tools now support single file structure and a reason there's already been issues raised because people installed a dependency in the wrong folder.

Just as a quick experiment, putting all configurations in a folder .electron-vue does clean up nicely. What do you guys think?

Expanded

Going to spend some time today to implement this. I'll have an update when you guys can give it a try on another branch.

looks good :) let me know when you have something up

Currently on vacation, but got some free time. You can now try the first draft of this new structure with...
vue init simulatedgreg/electron-vue#feat/simpler-structure my-project

Currently have not brought support for all vue-cli configurations expect for the defaults. Most other configurations should work fine, but the major one that still needs work is electron-builder.

I'm using the simpler-structure on a new project and It's actually great, didn't have any problems until now.

@SimulatedGREG
I created a new project by
vue init simulatedgreg/electron-vue#feat/simpler-structure my-project
However, npm run lint:fix triggers this error:

And my editor(Atom)'s eslint says “Parsing error: The keyword ‘import’ is reserved.”
It seems that .eslintrc.js cannot be found(by Atom?) within .electron-vue.
In my case, moving .eslintrc.js to the root directory solves eslint problem.
package.json
line 11: "lint": "eslint --ext .js,.vue -f ./node_modules/eslint-friendly-formatter --ignore-path .electron-vue/.eslintignore src test",
line 12: "lint:fix": "eslint --ext .js,.vue -f ./node_modules/eslint-friendly-formatter --fix --ignore-path .electron-vue/.eslintignore src test",
.electron-vue/webpack.renderer.config.js
line 128: configFile: path.resolve(__dirname, '../.eslintrc.js'),
Is this a bug or I miss some configuration?

I was hoping to move .config files into the .electron-vue folder but that doesn't seems like it will be feasible for users that have text editors expecting them to be in the root directory.

Well, it seems only .eslintrc has to be in the root directory. I leave all other .config files in .electron-vue and it works fine.
Overall, I still think it's a great structure. Like it a lot :smiley:

I like new structure very much too. Waiting stable release

#171

Possible, but I would like to keep everything in that folder if possible. What benefit would there be for that?

I just felt it is unnecessary to separate it from the directory where .babelrc and .eslintrc.js are placed, but there is no further reason.

Alright, I believe everything has been migrated over to a new single package.json setup and merged to the dev branch. There may still be a few issues here and there, so please do provide any feedback if you run into anything.

authors: Derek-X-Wang SimulatedGREG alexey2baranov citycide deiucanta develar rafaelpimpa re-fort

repo: SimulatedGREG/electron-vue


text:
OLED Theme

I am very impressed by this plugin's various features like the floating TOC button and other quality of life changes. However, I do not dig the theme. I would like to keep using this plugin, however I'd prefer for the styling to remain mostly the same.
Could it be possible to add Joplin's default themes as an option or at least some OLED mode (pitch black background) as an alternative to the still very bright Dusk and Night?

Hi Opisek! Yes, it's possible, I would try to add the pure black background color as an extra option for the night mode but I won't consider developing an extra theme selection at the moment. And, you will see it in the next release as an experimental feature.

This request has been partially implemented in the v4.6.0 release, feel free to let me know if there is any problem. Thank you again!

Looks amazing so far! Thanks for the work.

authors: Opisek Sinacs


text:
update spark to 2.2.0

Hi @fjhoelsg! Please, can you merge this pull request to master?

Thanks @GregaVrbancic!

authors: GregaVrbancic jomarinb

repo: SingularitiesCR/spark-docker


text:
Интерфейс управления правами пользователей

Задача
Требуется реализовать интерфейс управления правами пользователей.
Требования

[x]  Удобный и простой для понимания интерфейс
[x]  Интеграция в сервис редактирования профиля пользователей
[x]  Доступность лишь администратору

Сроки реализации
Требуется реализовать данную фичу к релизу v1.0.

Реализовано.


text:
Support JSXElement and JSXFragment

When attempting to pass JSX (React component fragments or elements) it fails with Error: JSXElement isn't implemented and Error: JSXFragment isn't implemented
I assume sval doesn't really need to implement said as technically those can be passed through React's JSX runtime (import { Fragment, jsx, jsxs } from 'react/jsx-runtime';)
So I wonder what steps would be needed here to support such Node types?

Well. Actually JSXElement and JSXFragment is not a valid node defination of the ESTree Spec. Even though the parser supports parsing

 to JSXElement, it can't be handle by JS.
I think what you should do is, instead of passing a JSX syntax into Sval, you should use some tools like babel/esbuild to transform the JSX syntax to a normal JS call like React.createElement('div') first, then pass that call into Sval.

By the way, I love your Github profile since I just got rickrolled lol

Well. Actually JSXElement and JSXFragment is not a valid node defination of the ESTree Spec. Even though the parser supports parsing

 to JSXElement, it can't be handled by JS.
I think what you should do is, instead of passing a JSX syntax into Sval, you should use some tools like babel/esbuild to transform the JSX syntax to a normal JS call like React.createElement('div') first, then pass that call into Sval.

Oh yeah, totally, and we were able to circumvent our issue cleverly by doing this: https://github.com/nodejs/nodejs.org/blob/main/apps/site/next.mdx.evaluater.mjs
So closing the issue :D

authors: Siubaak ovflowd

repo: Siubaak/sval


text:
「クロンダイク」を追加

クロンダイク（いわゆるソリティア）を作りました。
レビューなど、お願いします。
コードについての補足

PlayingCard::Card::Front や PlayingCard::Card::Back を使っていないのは、「 card.side = Card::Back なら分かるが、 card.isFrontSide = Card::Back は変ではないか？　card.isFrontSide = false のほうが自然ではないか？」と思ったためです。

Window の高さを 800 に変更しているのは、場札のカードが最大（19枚）まで重なってもはみ出ないようにするためです。正方形にこだわっているわけではありません。

まだ途中ですが、リファクタリングの途中経過です。
https://gist.github.com/Reputeless/96049a30a70f9b2843712196cbda806c

コードの難易度を下げる変更

std::list ではなく Array にした
捨て札を表す m_waste 配列を追加した
イテレータを扱うコードを減らした

コードを短くする変更

絵文字を SimpleGUI の標準フォントから持ってくるようにした

などの変更点があります。

リファクタリング、ありがとうございます。
クロンダイクの操作が連結リストとピッタリだと思ったんですが、やはり std::list を使うと難易度がかなり上がりますよね……。
分かりやすさでいうと断然 Array ですね。

英語対応（最後の「おめでとう」メッセージは削除）
マウスカーソルの形状変更対応
deltaTime を可変に（演出の速度を制御可能に）

といった変更を追加しました。
https://gist.github.com/Reputeless/96049a30a70f9b2843712196cbda806c

上記コードでリファクタリングはほぼ完了としたいと思います。
さらに加筆修正したいことがあれば反映してください。

リファクタリングありがとうございます。
特に修正箇所はありません。

お待たせしましてました。本日中の公開に向けて進めます！
スクリーンショットはこちらで最新コード準拠に更新しておきます。

authors: Raclamusi Reputeless


text:
Buttons are reversed.

Buttons are reversed for normal Windows pattern. (Have no info on what is normal for OSX.)
The normal order follows the left to right naming of the MB constants.
(See UI::messagebox for listing.)

In addition, the button names do not match UI::messagebox button names ("OK" vs "Accept".)

I support that the 'Ok' button should be called 'Ok'.

It's on our list to apply Modus to these examples. In which case the primary button is on the right. https://modus.trimble.com/components/modals/#specifications
A PR of customizing the title of the buttons will be accepted.

Well, the Modus CSS is separate issue which I discussed in passing in another issue 3 years ago now.
I myself in my edition already replaced the stylesheets will my own. (I and other devs see no good use for huge complicated stylesheets like Modus and Bootstrap for an interface a simple as one mimicking UI::inpubox.)
Enough of this we can discuss more in the Modus issue #5.

... back on issue topic:
Thomas, I think that you miss the point here that we have been talking about.  And this is the "rule" whether (or not) the HtmlUI::inputbox wrapper method is meant to mimic UI::inputbox in function, behavior and appearance.
Even if you (and your team) do not apply this "rule", @matthes-b makes the point that he does and that other coders may.

So, what I simply said above was that, if the accept button had an "OK" override set in ArgumentParser#get_options_args(), at about line 84, then that would only apply when the "mimicking" HtmlUI::inputbox wrapper method was used.
It would not apply when advanced hash arguments where used.
As far as button order goes ... devs can use edited html files for their own editions, if they want different order.

The button order for Mac is right to left, so this isn't necessarily reversed. Sticking to Modus is probably better than having it be platform dependent.

Alrighty then, ... I created another issue for the "OK" button text.
Ie ... Issue 12 : Text for Accept button should be "OK" for HtmlUI::inputbox wrapper

Since it seems there is no desire to change the button order per platform, and it appears that there is a general impetus to promote Trimble Modus UX styling (here and elsewhere,) ... I am closing this issue. (There is no point in debating it further.)
Y'all can label it "Works as intended" if ya' like.

And this is the "rule" whether (or not) the HtmlUI::inputbox wrapper method is meant to mimic UI::inputbox in function, behavior and appearance.

The intention of this project was to present an example of using UI::HtmlDialog. Making an "extended" version of UI.inputbox makes it relatable, and possible useful. However, it was never intended to be a complete library. And certainly never to mimic the  appearance and UX behaviour of UI.inputbox. UI.inputbox has a number of problems and quirks, it'd make no sense to replicate that. I wouldn't really encourage the API that mimicks UI.inputbox, it was just a very simple wrapper to implement that would let you easily switch from that and this HtmlDialog example. In a more polished variant I would probably have made prompt return a Hash instead of an Array so it would be possible to access the result by keys and not positional indicies.
While this example wasn't intended to be more than that, we do see it has sparked interest. So if the community is interested in contributing via pull requests we're happy to consider them.

However, it was never intended to be a complete library.

I noted this in another thread where Matthes and I were discussing the "mimic rule".

And certainly never to mimic the appearance and UX behaviour of UI.inputbox.

Okay. Thank you for the "official" clarification. I also noted in that other issue that the comments in the code use the phrase "similar to UI.inputbox".

UI.inputbox has a number of problems and quirks, it'd make no sense to replicate that.

And I said this same thing also and Matthes agreed.

I wouldn't really encourage the API that mimicks UI.inputbox ...

Well, there are devs (Matthes is one) who want it's behavior to be the same. Meaning the interaction with the user and how the user moves from field to field, how the dropdowns and listboxes work and what the ENTER key does. I pointed out that this might vary with platform (and I do not have a Mac to test and know how the native inputbox behaves.)
This gets into the old quagmire we had with the deprecated UI::WebDIalog and the platform differences. I think I would rather have the input controls on both platforms work the same way as (I think) the W3C specifications would say they should.

In a more polished variant I would probably have made prompt return a Hash instead of an Array so it would be possible to access the result by keys and not positional indices.

Yes, I was thinking of this as well. But hadn't gotten to the point of coming up with a solution.
Maybe a constructor boolean argument or perhaps a dedicated "prompt_for_hash" method.
Anyway ... a bit off-topic for this thread.

Anyway .. I closed this issue as it is not worth keeping open and is too much work to implement platform dependent button ordering. Ie ... it wouldn't really bring much to this example project.
It might be done with VueJS component files conditionally loaded on demand, but I'll look into that at a later date.
I do not want to get into the scenario of having one html file for Mac and another for Windows. That would double the maintenance of the JS and HTML interface.

Well, there are devs (Matthes is one) who want it's behavior to be the same. Meaning the interaction with the user and how the user moves from field to field, how the dropdowns and listboxes work and what the ENTER key does. I pointed out that this might vary with platform (and I do not have a Mac to test and know how the native inputbox behaves.)

We need to move these discussions away from "because UI.inputbox does it" to talking about "why it is an improvement".
For instance, we don't want to adopt how UI.inputbox moves between input fields when tabbing, it starts with the focus on the last element and the order isn't even looping around in an ordered manner:

Replicating UI.inputbox 1:1 will never be a goal. But features/behaviour in UI.inputbox that was useful and not buggy can off course be adopted here. But we should focus on talking about the reasons why something was good/useful. SketchUp's UI elements and paradigm for the desktop application is very dated, they origin back to version 1, twenty years ago. We're working on rewamping this and to help bring extensions into a more consistent user experience. This means our UI/UX examples going forward will be rooted in Trimble's Modus design system. When that doesn't cover everything we will be looking to the platform guidelines for references:

https://docs.microsoft.com/en-us/windows/apps/design/
https://developer.apple.com/design/human-interface-guidelines/

We have more UX people to consult with these days to help us for projects like this if we should run into scenarios where it's not clear which design option to choose.

I never considered bringing the tabbing order over to this repo. That would be silly.

But features/behaviour in UI.inputbox that was useful and not buggy can off course be adopted here.

Yes, the native UI.inputbox has the ability to pass 1 prompt array argument without a window title.
But it stupidly will not allow 2 args with the 2nd being the window title. (It raises an exception.)
Your code mimicked this. So I reordered the statements in the ArgumentParser to allow anywhere from 1..4 args.
A consumer can now do ...
HtmlUI::inpubox(["Name"], "Who are you?")

It is silly to force coders to stuff empty literal arrays into a method call, ie ...
HtmlUI::inpubox(["Name"], [], "Who are you?")

If there are no defaults, there is no good reason to force the passing of an empty array.
This is a "be just like UI::inputbox" kind of thing.

@thomthom Please copy and paste your Modus comments to the Modus issue thread.

authors: DanRathbun Eneroth3 matthes-b thomthom

repo: SketchUp/htmldialog-inputbox


text:
Check length expectations after replication converges in JS tests

Use waitSynch more liberally in JS tests to force convergence, and check expectations on the results.
This reinstates some tests I had inadvertently skipped a couple weeks ago assuming that waitSynch asserts its predicate on convergence.  Just ran make test-wasm 50x in a row on my machine without failure, but will keep an eye out for any flakiness in CI going forward

LGTM

authors: bennostein gregsexton

repo: SkipLabs/skdb