Homebridge builds but then doesn't run

$ homebridge
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Camera.js:28
let options = {
^^^
SyntaxError: Unexpected strict mode reserved word
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/index.js:3:14)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
$

npm is set to use python2.7 by default. I'm currently at python 2.7.8
OS is CentOS 6.8

Fixed. Nodejs version needed to be above 5.0. Installed nodejs from git and used "n stable" to set it to 7.0. Everything compiles and runs now.

By the way you should close this, since it's resolved.


Color Sketch filter

Is there any way to achieve color sketch effect using this framework?

Maybe. There are many filters, and you can create your own. Don't know what a "color sketch effect" looks like, but you can probably reproduce it in some way.


feat: disableaoidb

read commits
disableAoiDB: true/false

update index.d.ts

done done

I just realized you didn't make it === true otherwise it can be any type.


db:seed --class=blahblah has no response

Hey, Just wanted to point out a tiny bug. When you run the database seeder and specify the seeder file with class=ClassNameHere you dont get any response back in the console such as Seeded: ClassNameHere
Nothing important, but I just wanted to share this with you in case you didnt know.

I can't replicate. You should get an exception thrown.

The code looks like this:

    /**
     * Get a seeder instance from the container.
     *
     * @return \Illuminate\Database\Seeder
     */
    protected function getSeeder()
    {
        $class = $this->laravel->make($this->input->getOption('class'));

        return $class->setContainer($this->laravel)->setCommand($this);
    }

I think the issue is if you specify a class to seed (that exists), artisan doesn't provide any confirmation output (unlike just calling db:seed with no arguments where you get information on the classes that get seeded

I think that's right?

Technically, yes. Perhaps there's risk of confusion, though, as calling db:seed confirms every seeder that runs, but calling an individual one doesn't necessarily output that execution is successful, it just errors if something goes wrong.

Ok well whether it's a bug or not I just think it should provide output of success. Every other artisan function I've used seems to provide some sort of feedback
Sent from my iPhone, sorry about the typos.

On Dec 17, 2015, at 9:05 AM, Alex<EMAIL_ADDRESS>wrote:
I think the issue is if you specify a class to seed (that exists), artisan doesn't provide any confirmation output (unlike just calling db:seed with no arguments where you get information on the classes that get seeded
—
Reply to this email directly or view it on GitHub.

Just FYI, this is not solved also in the last Laravel Version (5.6)

Yes, all I ever had mentioned was there was no success feedback after running db:seed and specifying a seeder, but you get success feedback when you call db:seed without any arguments. I believe it should be consistent.

Great, only took 3 years!


Add background color to comparison results to improve visibility

To improve the visual indentification of the support of a specific feature within the comparison page the background of the fields should be colored.

Sebastian

The colour contrast probably isn't high enough in the example above to be accessible.

I agree if you are referring to the Partial status. The text color should be make black for them like for the other statuses.
Sebastian

Even for the non-partial, e.g.

The colors you chose are different from the ones in my mockup. In the mockup they are black (rgb(0, 0, 0)) for the text color and some lighter green (rgb(179, 239, 179)) than in your screenshot for the background color, resulting in a contrast ratio of 15.91:1 according to the Color Contrast Checker.
Sebastian

The colours were with a colour picker but the green text is for the green arrow colour.

You mean the check icon? That's rgb(28, 140, 29) (unchanged from the current color used on the page). Its contrast may be increased, though even when people can't distinguish it from the background, it doesn't matter much, as we then have the text and the colored background indicating the status.
Sebastian


Time zone: support fixed offset e.g. UTC+8

Currently, we only support geographical timezones for interpretation of timezone strings in AT TIME ZONE and session time zone
Note that PG supports such strings.

Seems that postgres' implementation is quite weird. asia/singapore is equivalent to utc-8, not utc+8... :thinking:

https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES

PostgreSQL allows you to specify time zones in three different forms:

A full time zone name, for example America/New_York.

PostgreSQL uses the widely-used IANA time zone data for this purpose, so the same time zone names are also recognized by other software.

A time zone abbreviation, for example PST. Such a specification merely defines a particular offset from UTC, in contrast to full time zone names which can imply a set of daylight savings transition rules as well.

You cannot set the configuration parameters TimeZone or log_timezone to a time zone abbreviation, but you can use abbreviations in date/time input values and with the AT TIME ZONE operator.

In addition to the timezone names and abbreviations, PostgreSQL will accept POSIX-style time zone specifications, as described in Section B.5. This option is not normally preferable to using a named time zone, but it may be necessary if no suitable IANA time zone entry is available.

The positive sign is used for zones west of Greenwich. (Note that this is the opposite of the ISO-8601 sign convention used elsewhere in PostgreSQL.)

Let's stick to the first option.


ARTEMIS-2076 Make Filter updateable

Is this updating the queue on the journal as well ?

It is not !!!   This will need to be a more complete feature.   If you restart the broker you get the old filter back afaik.

@clebertsuconic its updating as per other queue field update.... see updateQueue in postoffice.

if (filter != null && !filter.equals(queue.getFilter())) {
changed = true;
queue.setFilter(filter);
}
if (logger.isDebugEnabled()) {
if (user == null && queue.getUser() != null) {
logger.debug("Ignoring updating Queue to a NULL user");
}
}
if (user != null && !user.equals(queue.getUser())) {
changed = true;
queue.setUser(user);
}
     if (changed) {
        final long txID = storageManager.generateID();
        try {
           storageManager.updateQueueBinding(txID, queueBinding);
           storageManager.commitBindings(txID);
        } catch (Throwable throwable) {
           storageManager.rollback(txID);
           logger.warn(throwable.getMessage(), throwable);
           throw throwable;
        }
     }

IMO all these commits should be squashed.  I don't mind if you take authorship of the test I wrote for the other PR (assuming you don't).

@jbertram yes, i was wondering about squashing and then worried about your commit, as you dont mind, ill squash.

@jbertram all squashed now.

@michaelandrepearce as I talked on the vote thread: Can you tweak (or add a test) that play with a broker restart, and validate the queue is updated on the journal, and messages not lost please?

@clebertsuconic the issue on vote thread is around route-type change from another JIRA and PR, this is separate feature, though we're avoiding the issue that introduced, by following the same update logic of other queue field updates.
I will add a test case though to ensure when running and config is reloaded the queue is not destroyed but updated instead e.g. ensure the queue instance is the same.

LGTM

Dont merge i need to extend the tests still as per cleberts request

@michaelandrepearce if you don't have time to do it don't worry I will do it.. I was asking more in a way like.. if you can... know what I mean?

@clebertsuconic i have enhanced the tests to check binding ids are the same (aka not recreated) and also added check for message loss, this is added both to the redeploy and the restart test cases.

I was able to fix the conflicts myself after the previous merges.. don't worry!

@clebertsuconic i can rebase if you need to merge this? I have one locally already, let me know if you wish me to push up, or if you're merging as is (i assume from your response the latter)

Don’t worry. It was easy to rebase. Simple one.
Will merge it soon.


Multi-paged Webpart Property Panes - Pagination doesn't work as expected, stopping users from accessing pages

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

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

Additional environment details
Hi, I was told by a contributor of the PnP Modern Search repo (https://github.com/microsoft-search/pnp-modern-search) to duplicate a bug we found here as they suspect it is an SPFx issue.
Describe the bug / error
Hi, I was told by a contributor of the PnP Modern Search repo (https://github.com/microsoft-search/pnp-modern-search) to duplicate a bug we found here as they suspect it is an SPFx issue.
The bug in question is the following: https://github.com/microsoft-search/pnp-modern-search/issues/2405. It has gained a lot of traction in the last couple of days as it seems to only have started occurring this week - regardless of version of the PnP Modern Search web parts used.
Here is the original post that started it all by user twodul

Describe the bug
On the search result web part configuration property pane,
1 of 4 : next button working so can see the 2nd page
2 of 4 : when I click next button it go to "1 of 4" page not "3 of 4" page.
I can't set up available connection from 3rd page configuration.
It works fine with my test tenant environment and this issue happens only on our production environments.
I got below JavaScript error when I click next button.

I attached the console log messages. SearchResultsPropertyPannelErrorLog.txt

Steps to reproduce

Add PnP Modern Search "Search Results" or "Search Filters" web parts to a page.
Edit the web part and try access page 3 or 4 of the property pane.
Pages 3 or 4 are not accessible on those web parts -> clicking on "next" on Page 2, will loop back to Page 1.

Expected behavior

Panel page should increment to page 3 and 4 when required.

I got the same problem, with Chrome, Egde and Firefox - all in latest stable Version

I got the same problem in three diferent tenants

@AJIXuMuK FYI, this specific page is all about SPFx dynamic data, listing available data sources and retrieving existing connections if it can help to identify the cause.

This recently started happening to us too. After another issue we faced today, I realized that it seems the common denominator for the tenants it happens in is that SharePoint is now using React 17. Tenants still using 16.13.1 still work fine. Hope this can help give a clue...

The fix has been done and should roll out in the next 2 weeks.

@AJIXuMuK , how is this fix being rolled out?  It is a SharePoint Online release update?   Any client side alternative possible ?

@KuotingChiu - this is service-side update.
We will roll out new version 100% next Monday.
You won't need to do any changes.

@AJIXuMuK , our developer's initial confirmation is positive, Thanks a lot!!!  May I ask if this type of changes to break and fix the issue was announced such as using the M365 message center at all?  We have a support incident opened for this issue and the assigned support person as well as the incident escalation manager were not helpful at all.

@AJIXuMuK "Next Monday", does that mean Monday October 24th to be clear? We have customers with applications that down due to this so they need to be informed.

@rogbac - next Monday is yesterday

Ok thanks, then we hope to see a change to the positive anytime soon. Still same in the customer tenants experiencing this.

@rogbac - that should be already there.
I would try opening the browser page in incognito (Private) mode to see if the error is there.
Also - is that the same error as described in this issue? Or some other kind of error?

Our tenant seems to be fine now.  Isn't this change applied to all tenants?

@KuotingChiu - it is applied to all tenants.
I strongly believe @rogbac has some other type of the issue.
I will close this one.
@rogbac  - feel free to create a new issue with detailed description of what's happening for you.

Thanks for the fix BTW @AJIXuMuK !

Just som feedback in this thread. NOW it works for us again, we noticed it today in several tenants that it just started work. Previously today we still had the error described in this thread, but sometime the last hours it fixed it itself. So the rollout/rollback has not been global on the same day for everyone as feedback. Happy it works again though!

@rogbac - the rollout was global.
The thing here that potentially you could have cache (most probably service worker) that loaded old modules.


[SPARK-21395][SQL] Spark SQL hive-thriftserver doesn't register operation log before execute sql statement

What changes were proposed in this pull request?

Add a private method registerCurrentOperationLog in SparkExecuteStatementOperation
Call registerCurrentOperationLog before execute() and unregister it after execute()  like implementation in SQLOperation.java#L204

How was this patch tested?
Add unittest in HiveThriftBinaryServerSuite
build/mvn -Phive-thriftserver -Dtest=none -DwildcardSuites=org.apache.spark.sql.hive.thriftserver.HiveThriftBinaryServerSuite test

HiveThriftBinaryServerSuite tests passed

Can one of the admins verify this patch?

@cloud-fan Could you please help me to review this PR? Thanks a lot!

Test build #79657 has started for PR 18649 at commit b5c963f.

Test build #79657 has finished for PR 18649 at commit b5c963f.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79657/
Test FAILed.

Test build #79659 has started for PR 18649 at commit fa4ba3d.

@cloud-fan I just fix scala style issue, pls re-test again.

Test build #79659 has finished for PR 18649 at commit fa4ba3d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79659/
Test PASSed.

@cloud-fan Any suggestions?

cc @jerryshao

So it looks like a basic copy-paste from hive code to support this feature in STS (like what I did before to support spnego). It looks fine to me based on my limited knowledge :).

@jerryshao Yes, it's just copied from SQLOperation in Hive. However, those code lines are the key point that HiveServer2 can return operation log to client via TFetchResultsReq which fetchType is FetchType.LOG. If hive-thriftserver in Spark SQL support complete HiveServer2 protocol, registerCurrentOperationLog should be introduced and consistent with Hive.

Sorry I'm not familiar with this part, I cannot give you a valid comment, you could ask others to help reviewing your patch 😄 .

@gatorsmile Could you please help me review this PR?

@cloud-fan This patch is very simple and clear, is there any problem to review or merge it?

I'm not familiar with this code and don't know who I should ping, cc @srowen do we have a maintainer for thrift-server?

@cloud-fan @srowen If we can't find maintainer of hive-thriftserver in Spark, I may have to close this PR in few days later.

CC @vanzin

Really not familiar with this area of the code...

cc @davies

@debugger87 Hello,
There have been a few posts about hive, where this setting causes too many open files issue.
https://community.hortonworks.com/questions/48351/hiveserver2-hive-users-nofile-ulimit-above-64000.html
there are a few concerns on this setting causing too many open file handles..
Does this also impact spark the same way or we have taken care of it already.

@dilipbiswal
Thanks for your reply. In my eyes, there have been some mechanism or configuration to control the number of opening files generated by SQL Operation. e.g:
hive.server2.idle.session.check.operation
hive.server2.session.check.interval
hive.server2.idle.session.timeout
hive.server2.idle.operation.timeout
hive.server2.logging.operation.enabled

If we mind the increase of opening files, we can adjust those configurations. However, in spark sql, there is no any methods or solutions to generate operation logs to provide the standard API: FetchResults with FetchType.LOG.

Test build #80744 has started for PR 18649 at commit 542e427.

Test build #80744 has finished for PR 18649 at commit 542e427.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80744/
Test FAILed.

@liufengdb

Can one of the admins verify this patch?


[BUG] Feed error

A get again the known error on feed , by deleting storage data fixes the issue temporarily
Using LineageOS 19.1
Android 12L

HJC's previous build, with all the fritter branding still works perfectly though.

Yeah im still using @TheHCJ fritter apk because it still works

I am now working on a fix


[Icons] Missing MeetingRoom and NoMeetingRoom icons?

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
MeetingRoom and NoMeetingRoom should exist as components in the @material-ui/icons package.
Current Behavior
MeetingRoom and NoMeetingRoom are not recognized as imports from the icons package nor do they exist in the source packages/material-ui-icons/src
Steps to Reproduce (for bugs)

N/A
Context

I do not see this icon referenced anywhere, including why it isn't added. Am I missing something or did someone just forget to add it?
Your Environment

Tech
Version

Material-UI
v1.0.0

React
16.3.2

browser
Chrome 66

Dupe of #11290


growing nodeset hits limit

Error occurs during network offer validation (file size 600MB).
DEBU[2022-09-15T12:39:38+02:00] configured max distance: 500                  document=epip.xml id=ZV4GB5-iaOInY6zA8qBZE scope=main script=stopPlaceQuayDistanceIsReasonable type=LOG valid=false
DEBU[2022-09-15T12:39:38+02:00] validation using schema<EMAIL_ADDRESS>        document=epip.xml id=ZV4GB5-iaOInY6zA8qBZE scope=main script=xsd type=LOG valid=false
XPath error : Memory allocation failed : growing nodeset hit limit
growing nodeset hit limit
^
XPath error : Memory allocation failed : growing nodeset hit limit
growing nodeset hit limit
^
panic: TypeError: Cannot read property 'push' of undefined or null at builtin/everyStopPlaceIsReferenced.js:33:9(53)

Library used for parse and xpath queries have been replaced in v0.5.5 and should resolve this issue


Will neo4j .net driver support .net framework version 3.5?

I try to involve neo4j using Unity but I find the highest .net framework version of Unity is 3.5, which is unable to use this driver. Therefore, I wonder whether there are any ways to solve this problem? I would be very appreciate if you could help me. Thanks!

The current plan is only .NET framework 4.5.2 and .Net Standard 1.3

Right now as we moved to async, we cannot support 3.5 in newer driver version.


Importing geopandas generates a warning

/env/lib/python3.6/site-packages/geopandas/_compat.py:88: UserWarning: The Shapely GEOS version (3.7.2-CAPI-1.11.0 ) is incompatible with the GEOS version PyGEOS was compiled with (3.9.0-CAPI-1.16.2). Conversions between both will be slow.
  shapely_geos_version, geos_capi_version_string

Yes, just saw that one.

Closed as a) migrated to conda so that all packages are using one set of geos binary.


feature: improve the captions settings ui and add keyboard shortcuts to change font size

Current UI
The settings of caption looks really bad and there is no shortcut to change the size of fonts while watching the video, i have to open the settings everytime to change the size.

Suggestions

[ ]  improve the ui of caption settings
[ ] add shortcuts to change size of font like its on youtube using - and +
[x] and add support for numpad to go forward and backward in video

and add support for numpad to go forward and backward in video

To tackle the 2nd enhancement i.e. "add shortcuts to change size of font like its on youtube using - and +", we will have to

Add a State for current Subtitle Font Size.
Attach a keydown event listener to the component to capture the + and - keys.
Dynamically adjust the font size of the subtitles according to the current state of subtitle and the key that is pressed.
above steps would let us complete the task

If you like the approach lmk and i'll start working on it, even if you have different views you can tell me.

@shahkashish yeah please go on

could you assign it to me?
as it is mentioned that task should be assigned first and then i have to make PR

This issue looks out of scope.


[SUPPORT] How can I create a queue and add more videos while I watch videos

Trying to switch from youtube.com to this and the only feature i really care about in youtube is the queue. I need to be able to start watching a video then add more as I continue browsing for more videos. I would rather not have to create new playlists every time I want to use YouTube.

Take a look at task-spooler, by placing "tsp" in front of the video player command in the config file.
See also: https://m.youtube.com/watch?v=I4tfHUmklWo

So I put tsp in front of the command (right here I assume this is right)
  video_players                 => {
                                     mpv => {
                                              arg => "--really-quiet --force-media-title=*TITLE* --no-ytdl *VIDEO*",
                                              audio => "--audio-file=*AUDIO*",
                                              cmd => "tsp /usr/bin/mpv",
                                              fs => "--fullscreen",
                                              novideo => "--no-video",
                                              srt => "--sub-file=*SUB*",
                                            },

However it complains that the tsp command is not found.

Nevermind installed task-spooler and it works like a charm!

Sorry for replying again but now I have the issue that I can't view comments or anything because the video is no longer playing in youtube-viewer's point of view. Any way to fix that whilst still using tsp?

An alternative to tsp would be to use :q=i option to enqueue videos for playing, followed by :pq which will start playing the enqueued videos.

Only issue with that is that iirc you can't add more videos to it as you go
On Tue, Jun 29, 2021, 5:52 PM Daniel Trizen @.***>
wrote:

An alternative to tsp would be to use :q=i option to enqueue videos for
playing, followed by :pq which will start playing the enqueued videos.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trizen/youtube-viewer/issues/385#issuecomment-870450519,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOJ5TK4NUL4SG3OO2VOJHNLTVGJXPANCNFSM47PG5JVA
.


Refactor app commands

Have refactored commands to now use action passed with the output

this update also fixes the radio bug

@stevenpkg travis is failing because of lint issues. Try to run:
npm run lint

And check the output

This seems to be the problem
/Users/steve/MyFiles/IBM/projects/github/car-dashboard/ui/js/tooltip-dialogs.js
24:1   error  Definition for rule 'react/jsx-wrap-multilines' was not found  react/jsx-wrap-multilines
24:31  error  Missing space before function parentheses                      space-before-function-paren
58:30  error  Missing space before function parentheses                      space-before-function-paren
61:20  error  Missing space before function parentheses                      space-before-function-paren
64:20  error  Missing space before function parentheses                      space-before-function-paren
68:26  error  Missing space before function parentheses                      space-before-function-paren
Any ideas?

I had over 3000 errors with whitespace etc, to many to fix. I noticed that .eslintignore and .eslintrc (now named .eslintrc.yml) had been changed. I changed my refactor branch to use they new setting and only got 30 or so errors. I have fixed these errors now and only left a few warning (all console)
/Users/steve/MyFiles/IBM/projects/github/car-dashboard/ui/ibm/speech-to-text.js
90:15  warning  Unexpected console statement  no-console
97:9   warning  Unexpected console statement  no-console
/Users/steve/MyFiles/IBM/projects/github/car-dashboard/ui/js/api.js
80:9  warning  Unexpected console statement  no-console
84:7  warning  Unexpected console statement  no-console
/Users/steve/MyFiles/IBM/projects/github/car-dashboard/ui/js/ui_tests/tests.js
40:7  warning  Unexpected console statement  no-console
100:9  warning  Unexpected console statement  no-console
✖ 6 problems (0 errors, 6 warnings)
So now there are a few merge problems?

@stevenpkg it seems like you are using an older version. Your initial changes were in sync with the code in master it's just that you had some lint issues. Look at Travis: https://travis-ci.org/watson-developer-cloud/car-dashboard/builds/197105746#L312
You were using double quotes for strings.

You need to pull the changes from master run npm install to make sure your node_modules is in sync with the package.json file and then run npm run lint.
Once you have only warning make sure you commit all the changes. Right now there are merge conflicts in some of the files.

Thanks German, will do it tomorrow


Make ibm-cloud image more generic

Making this image generic so that we can extend it further anywhere needed.

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

Needs approval from an approver in each of these files:

OWNERS [mkumatag]

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

/cc @sudeeshjohn

/lgtm


Result Summary Report should capture all builds status

Currently, the Result Summary Report only displays the failed child builds. This may cause problems when some child builds are still running. When this happens, Result Summary Report will not capture these running builds as their results are unknown and users will get misleading information.
If there are running builds, the Result Summary Report should have a section to show the running builds and display the warning message. Also, I think we should display the timestamp when the report is generated.

related, if not dup of https://github.com/adoptium/aqa-test-tools/issues/596

Yes, this is related to #596 - Capture Grid view in Release Summary Report. The goal of this issue is to display running builds if there are any. However, the ideal solution is to get this resolved at the Jenkins pipeline level. See https://github.com/adoptium/ci-jenkins-pipelines/issues/234

I can take this!


Type guard makes Typescript infer that the type is never

🔎 Search Terms
Type guard narrowing never
🕗 Version & Regression Information

This is the behavior in every version I tried

⏯ Playground Link
https://www.typescriptlang.org/es/play?ts=5.4.0-beta#code/MYGwhgzhAEBi0G8BQ1oEsIEEAUBKAXNAC4AWG6Mmi0ATgKZECuNAdsWTGixEWC8HQD2AM2hUAvigoAhPIVLly06vSat2i7r35DRyyZKShIlaHQAeROiwAmMeAknGo0ZRau37iQ8EFboYACSWnwC0AC80Cx0AO5ieADcRn480ABGwTyhdBFRsa6JSEhoothBIToAdBg4uNAAPvUBmdoC1RCyuHW+3IIgdJUgggDm2ABEgaaCNK5juAnQAPSL0AAqJDnlWVU1eMQAngAOOcOMYDQ20MJgaCAQADToRNAAtmAA1nQwW605IgfHPIANzoNEqSCAA
💻 Code

class F {
  isA(): this is A { return this instanceof A }
  isB(): this is B { return this instanceof B }
}

class A extends F {}
class B extends F {}

const aInstance = new A();
const bInstance = new B();

if (aInstance.isA() || aInstance.isB()) console.log("Is A or B");

🙁 Actual behavior
The aInstance.isA() type guard fails, it makes aInstance of type never.
🙂 Expected behavior
If aInstance.isA() is true, then aInstance must be of type A
Additional information about the issue
No response

I'm not really seeing an issue here. The error is within the context of the condition, in particular the right hand operand to ||.
aInstance is typed as A. If aInstance.isA() returns false then the contextual type of aInstance would be Exclude<A, A>, i.e. never. Which makes sense—when is an A not an A?
Based on the type information available, the right hand operand to ||, aInstance.isB(), will never be evaluated.

Also note that in the given repro, all the classes are structurally identical - see https://github.com/microsoft/TypeScript/wiki/FAQ#why-do-these-empty-classes-behave-strangely

Hi @fatcerberus and @snarbies, sorry, I simplified the code so it wasn't tedious to read.
If aInstance is actually of type A (according to the type guard and the instantiation), why Typescript  assumes that aInstance is of type never? It doesn't makes sense to me.

A and B are still structurally the same.

If aInstance is actually of type A (according to the type guard and the instantiation), why Typescript assumes that aInstance is of type never? It doesn't makes sense to me.

So the problem is that you wrote aInstance.isA() || aInstance.isB() - as far as the compiler can tell, the first condition is always true, so at the point aInstance.isB() is evaluated, it can’t possibly be an A (logical OR is short-circuiting), so aInstance there must be some other type - and since there’s no other possibility, you get never.

Also note that in the given repro, all the classes are structurally identical - see https://github.com/microsoft/TypeScript/wiki/FAQ#why-do-these-empty-classes-behave-strangely

Thanks for your patience @fatcerberus @MartinJohns and @snarbies, I finally understood. Avoiding empty classes did the magic.


Win build

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

I think we need to wait until we have boost 1.76 in conda-forge.

@conda-forge-admin, please rerender

Actually we're missing vlfeat on Win.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Needs https://github.com/conda-forge/cgal-cpp-feedstock/pull/28

@traversaro @wolfv have you this before by any chance? BLAS_LIBRARIES cannot be found on windows.

@traversaro @wolfv have you this before by any chance? BLAS_LIBRARIES cannot be found on windows.

Hi @Tobias-Fischer, at a first glance I could not find any obvious reason this is happening, I will try to debug this on a Windows machine in the next days.

Hi @traversaro, did you have a chance to look at this?

Sorry, I completly forgot about this. I will look into this in the next days.

@conda-forge-admin, please rerender

Got much further after the rettender - just needs a NOMINMAX now I believe :).

@traversaro @wolfv have you this before by any chance? BLAS_LIBRARIES cannot be found on windows.

Just replying here as today I had the same problem, but the only reference I found online was this discussion.
Basically, if you install libblas on Windows by default it installs you the mkl variant, that it is not sufficient to make find_package(BLAS) succeed. To have find_package(BLAS) succeed, you need to install the blas-devel package.


Import statement completions

Screen capture demo

Enables auto-import-style completions on import statements themselves, e.g.
import useS|

can offer a completion to
import { useState| } from "react";

(The | indicates the position of the cursor both before and after the completion.)
This PR is large because, although the feature appears very similar to existing auto imports, it requires us to resolve module specifiers immediately instead of in a subsequent completion details request. Being able to do that with any reasonable amount of code reuse required quite a bit of untangling. The implementation is explained in some detail in code review comments, but note that a large amount of the PR diff is just functions being shuffled around.
Note also this feature is opt-in via a user preference (includeCompletionsForImportStatements) because it requires corresponding editor changes. So, you won’t be able to test this yourself without building my VS Code PR as well.
Design

When these completions are offered, they are generally the same as the auto-imports you’d get elsewhere in the file:

Same list of modules and exports are considered, but we require the first character of what you’ve typed so far to match the first character of the export name, instead of just the “contains characters in order” check. This significantly reduces the number of matches we see after you type a single character, which lets us return results way faster.
Quote preference is respected and semicolon usage is inferred
Inference of preferred import style is same as normal auto-import rules (i.e., when esModuleInterop introduces ambiguity we try to give you what you want)

Does not work on const foo = require("mod"); only works on imports (though import foo = require("mod") is supported in TS)
Does not work on imports where there’s already a module specifier, for I think obvious reasons
Does not work on imports where there’s already another identifier in the declaration, like import foo, { bar| or import { foo, bar|. This could be relaxed a bit later, but it was complicated and seemed fairly low value.
Inserts a snippet, so your cursor snaps to the end of the identifier you were completing, then you can tab to the end of the statement.
Due to client limitations (replacementRange must be a single line), does not work on imports that already span multiple lines, e.g.import {
  foo|
}

Performance

Following measurements assume these dependencies
"dependencies": {
    "@angular/core": "^10.0.7",
    "@types/eslint": "^7.2.5",
    "@types/lodash": "^4.14.165"
    "@angular/material": "^11.2.5",
    "@reduxjs/toolkit": "^1.5.0",
    "@types/node": "^14.14.17",
    "@types/puppeteer": "^5.4.2",
    "@types/react": "^17.0.3",
    "@types/serverless": "^1.78.17",
    "aggregate-error": "^3.1.0",
    "antd": "^4.5.1",
    "aws-sdk": "*",
    "eslint": "^7.14.0",
    "lodash": "4.17.15",
    "mobx": "^5.15.4",
    "moment": "2.24.0",
    "puppeteer": "^6.0.0",
    "react": "16.12.0",
    "typescript": "^4.3.0-dev.20210322",
  }

Import statement completions
Stress-tested with aws-sdk installed, which has just a ridiculous number of exports. First draft took several seconds without caches, which was too much, so I decided to require the first character of the identifier to match the first character of the export name before continuing the fuzzy match. So whereas regular auto imports will offer useState when you have just typed state, import statement completions require you to start with u.

import a|: 865 ms (3604 entries)
import b|: 456 ms(1279 entries) (some cache benefit from previous request)
import a|: 625 ms (max cache benefit)

After npm rm aws-sdk:

import a|: 116 ms (197 entries)
import b|: 44 ms (105 entries)
import a|: 70 ms

Normal auto imports
The first draft of this PR incurred about a 15% performance penalty on all auto-imports; that has now been reduced to zero or has improved performance in some scenarios. The auto import cache has been split into two pieces that are independently more durable and more reusable than they were combined.
Previously, the process went something like this:

For each module in the program:
Can we come up with a module specifier from the importing file to that module without crossing someone else’s node_modules?
If that module specifier is a bare specifier (e.g. "lodash"), do the package.json files visible to the importing file list that package?
If the answer to both of those are yes, proceed with adding info about that module's exports to a big array, deduplicating re-exports along the way.
Save all that info in a cache.
Iterate the big map of info and pull out the exports whose names match the partial identifier typed so far.

The main problem with this process is that steps (2) and (3) are pretty expensive, and that work might go to waste after the filter in step (6) is applied. The other problem is that they are dependent on the location of the importing file and the contents of any package.jsons visible to that file, which makes us have to invalidate the cache a lot. Too many inputs combined into a single cache means that when we invalidate the cache, a lot of work that isn’t actually invalid has to be thrown away. Now, we cache “what are the exports and re-exports of every module” and “is file A importable from file B, and by what module specifier” separately. So the process becomes more like:

For each module in the program:
Add info about that module’s exports to a big map (not throwing away info about re-exports)
Cache that big map
Iterate the big map of info and pull out the exports whose names match the partial identifier typed so far.
For each name match, see if the module is importable by the importing file (both by module specifier validity and package.json filtering)
Add that module specifier / importability info to a cache.

This means for subsequent auto imports, we have better chances of getting cache hits, and we do less expensive work up front, even with the caches are totally empty.
Triggering auto import completions in a project with

dev.20210322 (ms)
This PR (ms)

completionInfo (cold)
259
264

completionEntryDetails
102
74

completionInfo (cached)
68
63

completionEntryDetails
44
35

To-do

[x] Do we need a separate user preference for enabling snippet-formatted completions? Yes, done.
[x] Do some profiling to make sure normal completions / auto imports are not slower
[x] Check performance when there are huge numbers of possible modules to import from (e.g. with aws-sdk installed) and probably implement some limits/mitigations there. Increased strictness of filter to make list smaller.
[x] Get approval on corresponding VS Code PR
[ ] Finish and merge corresponding TypeScript-VS PR (need help from @uniqueiniquity on this one 🙏)

Fixes #31658

@typescript-bot shush it’s just a draft

@typescript-bot pack this

Hey @andrewbranch this doesn't appear to be working for me am I doing something wrong?

It looks like something might have broken on the VS Code side. It doesn't work for me either at the moment, but I can see TS Server returning the right things in the log. I'll take a look. Thanks!

Have it been considered to add support for that in the LSP spec? Or is it already supported?
That question maybe belongs better in https://github.com/microsoft/vscode/pull/119009 but that one is locked.

I made sure that everything we’re doing with VS Code can also be done over LSP so that this will work in VS once their TS completions support swaps over to LSP. I actually have a draft PR up for that in the TypeScript-VS codebase (which is not open source). I’m not sure if that answers your question—let me know if you have more specific questions, and I can try to answer or pull in @uniqueiniquity who is our resident LSP expert.

It looks like something might have broken on the VS Code side. It doesn't work for me either at the moment, but I can see TS Server returning the right things in the log. I'll take a look. Thanks!

Hey @andrewbranch was that issue ever fixed? Or is that what you need to change in the VSCode repo?

@jasonwilliams it was fixed at https://github.com/microsoft/vscode/pull/121975

I’m not sure if that answers your question—let me know if you have more specific questions, and I can try to answer or pull in @uniqueiniquity who is our resident LSP expert.

I guess the more specific question I have is whether that functionality requires changes to the LSP spec (https://github.com/microsoft/language-server-protocol) and if so whether those were proposed or even already implemented?

No, this feature can be implemented with LSP 3.16 (and likely earlier versions) without changes. From the protocol standpoint, this is actually a good bit simpler than normal auto imports (though those are possible with LSP too). The only somewhat interesting thing about this feature is the tab stop at the end, which is supported via snippet text. The only caveat is that I made the space character a trigger character only when preceded by /^import/ via some special logic in VS Code’s TypeScript support layer, which I don’t think is possible in LSP. However, that was only to work around a conflict with a snippet completion whose name is import statement preventing a new completions request triggering on import s. It’s a little kludgy and if it came down to it, we could find other workarounds (the easiest one being ensuring that snippet completions don’t have multi-word names, since they can unexpectedly block new requests anywhere).


Re-written cookies accumulate in browser, causing errors and potential security risks

All cookies of web-sites that are being recorded are currently re-written to the domain webrecorder.io. The cookie jars in client browsers are filling up until further usage of webrecorder becomes nearly impossible. Users clearing their cookie jars typically helps, or running the recording browser in "private" mode.
Storing the cookies server-side (#79) might be one way to do it, other possibilities include a front-end to manage cookies, or using on-demand sub-domains.

This has been much improved in the upcoming version, as cookies are stored at the exact path. Server-side handling in #79 is used to augment the exact path when accessing cross-domain requests.
I believe the currently deployed version has them apply to the root domain, which is problematic.

In the new version, all cookies are set to the rewritten path, never on the root domain. With temp sessions, each temp session will have its own set of cookies. The server-side temp cookie store handles the domain mapping for cookies. Closing this, unless issues arise in the new version.
Will open other issues for separate security concerns.


chore: rid of fs2

fs2 was introduced in PR #500, but we actually don't really need that
much from it. This commit removes the extra dependency in favor of doing
the same directly. I think this is pretty-much equivalent to inlining
the code.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#551  👈
#550
master

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

Join @pepyakin and the rest of your teammates on  Graphite

Merge activity

Nov 5, 4:25 PM EST: A user started a stack merge that includes this pull request via Graphite.


Detailed scores of Phi-3-mini-128k

Hi,
Thanks for your great work on evaluating long context ability of LLMs! Also enjoyed your poster presentation at COLM 2024.
Could you provide the raw scores of phi3-mini-128k? It seems like this model is not included in the original paper.
Thanks.

@huangyuxiang03 here are the full results.

niah_single_1
niah_single_2
niah_single_3
niah_multikey_1
niah_multikey_2
niah_multikey_3
niah_multivalue
niah_multiquery
vt
fwe
cwe
qa_1
qa_2
avg

4k
100.0
100.0
100.0
96.6
99.6
99.6
92.2
98.5
97.1
85.1
91.9
83.8
54.2
92.2

8k
100.0
100.0
100.0
96.6
100.0
99.4
95.2
98.5
99.3
83.4
88.6
75.8
53.0
91.5

16k
100.0
100.0
100.0
95.4
100.0
98.6
92.8
98.0
99.3
86.7
78.7
78.8
50.2
90.7

32k
100.0
100.0
100.0
94.6
99.6
97.4
84.4
96.8
99.0
86.5
52.3
75.6
50.8
87.5

64k
100.0
100.0
100.0
95.0
98.6
95.2
88.8
93.4
87.0
66.4
3.3
74.2
45.4
80.6

128k
98.6
97.8
97.8
86.4
65.2
42.0
66.4
69.1
55.0
84.1
1.8
66.6
36.2
66.7

Thank you for providing these results. I have no futher questions and I'm closing this issue.


Improve the commented suggested "better" auto-generated schema

Here's a good example of where it fails to match properly: https://github.com/KenKundert/nestedtext/discussions/40#discussioncomment-4079299

The feature/experimental-schema-guessing branch now succeeds with the above example. But I will need to do a lot more testing to make sure it never produces worse results than the current method. And I've left a cry for help in the yamlpath discussions.


chore: add a helper to test the project and make eaiser the process

What this PR does / why we need it:
That makes faster/easier test things out since I can just update/comment/change the values and run all by once. Also, help new contributors first check if all is fine for them looking up for customizations and understand the details.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Steps to reproduce
None
Does this PR introduce a user-facing change?
None
Does this PR require documentation?
None

It was not accepted so I am closing this one.


webview not working in flutter web

I am using a web view for showing HTML files but webview not working. Please provide me solutions.

@devndra please provide more details: flutter doctor -v output, which webview_flutter version you use. What do you mean by not working, are there any errors/warnings/crashes?

webview_flutter doesn't have web platform support yet, but you can use HtmlElementView on the web platform. Some examples of usage in the PR https://github.com/flutter/flutter/pull/37819

Thank you @muhleder !


Socket hang up error with multiple subdomains Ubuntu 20.04

I have a proxy configured as with filename *.example
{   "target": "http://<IP_ADDRESS>:8011" }
The same successfully serves a.example.local, but not b.a.example.local. The later request timesout and following error is logged in daemon logs-
Error: socket hang up     at connResetException (internal/errors.js:610:14)     at Socket.socketCloseListener (_http_client.js:400:25)     at Socket.emit (events.js:327:22)     at TCP.<anonymous> (net.js:674:12) {   code: 'ECONNRESET' }
I tried to see the diff in request object in daemon/group.js, but couldn't find anything significant. The only difference is in the host and x-forwarded-host header.

It was a code fault at the server end. It was getting stuck infinitely.


[IndexedDB] Objects should be stored as objects

Describe the feature
The driver always stores objects in a stringified form, which makes it more difficult to inspect properties when storing large objects.
I made a workaround by creating a custom indexedDB driver replacing this line:
https://github.com/unjs/unstorage/blob/e42c01d0c22092f394f57e3ec114371fc8dcf6dd/src/drivers/indexedb.ts#L40-L42
with:
setItem(key, value) {
  try {
    value = JSON.parse(value)
  }
  catch { /* use string value */ }
  return set(makeKey(key), value, customStore);
},

Viewed in Application tab:

Current behavior:

Workaround behavior:

This workaround ensures that object values are stored as objects, otherwise they continue to be stored as strings.
Additional information

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

Please check my comment in https://github.com/unjs/unstorage/pull/512#issuecomment-2531750434. PR welcome.


Error running compiler

I installed simput and tried compiling a simple example. Got an error related to the node_modules path. Simput seems to be looking under its installed path instead of the project node_modules. Am I doing something wrong?
tortuga2:simput-protos john$ ./node_modules/.bin/Simput -c input -o output
Error building

/Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/src/cli/compile.js:246
        throw jsonStats.errors;
        ^
[
  "Entry module not found: Error: Can't resolve 'expose-loader' in '/Users/john/projects/resonant-hpc/git/simput-protos'\n" +
    "resolve 'expose-loader' in '/Users/john/projects/resonant-hpc/git/simput-protos'\n" +
    '  Parsed request is a module\n' +
    '  using description file: /Users/john/projects/resonant-hpc/git/simput-protos/package.json (relative path: .)\n' +
    '    resolve as module\n' +
    '      looking for modules in /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/node_modules\n' +
    '        using description file: /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/package.json (relative path: ./node_modules)\n' +
    '          using description file: /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/package.json (relative path: ./node_modules/expose-loader)\n' +
    '            no extension\n' +
    "              /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/node_modules/expose-loader doesn't exist\n" +
    '            .js\n' +
    "              /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/node_modules/expose-loader.js doesn't exist\n" +
    '            .json\n' +
    "              /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/node_modules/expose-loader.json doesn't exist\n" +
    '            as directory\n' +
    "              /Users/john/projects/resonant-hpc/git/simput-protos/node_modules/simput/node_modules/expose-loader doesn't exist"
]

FWIW, Simput did create index.js and convert.js in the input folder.

Are you trying to build a new type or process a data model into an input deck?

I am trying to process a data model. For a little more context, I am getting familiar with Simput for the first time, and my intent is to compile a simple model and see if I can load it into a Simput viewer. My steps are:

npm init
npm install simput
Create a folder input/ with one file model.js, and set the file contents to your address book example.
./node_modules/.bin/Simput -c input -o output

This is related to a behavior of npm. If you actually follow the documentation the compiler actually works:
$ Simput -c ./input -o ./output
convert.js already exist. Skip generation attempt...
built output/input cleaning up

You can even run it that way without installing it
$ npx Simput -c ./input -o ./output
convert.js already exist. Skip generation attempt...
built output/input cleaning up

But as soon as you provide your own ./node_modules you shortcut the dependency resolutions which tend to break the execution of the CLI.

Tested on
$ node --version
v12.13.1
$ npm --version
6.12.1

Otherwise, I was able to reproduce the issue as soon as I was installing simput as a local dependency.


Readme Improvement in Main Readme File Face-x

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

Update Readme File with Features
Add new Points

Link

Ol

hey @akshitagupta15june  , I'm  Share Screenshot ,  Let me know if you have any Changes , then I'm create pull request
see screenshot

You have to put same logo of face-x and that animation

Can you change that

Can you change that

Sorry , But I have no Idea  so , I can't change this


Convert To Tailwind CSS

Enough said...progress made already and pretty easy going so far.

this is happening within all other tickets.


Remove Back button

Background
Whenever the Back button is clicked on an exercise Dashboard page - irrespective of the page the user is on - the user is taken to the Exercise Set-up Overview page. The button is misleading and would be best removed.

Feature(s) Description

[ ] Remove the Back button from all pages

Definition of Done

[ ] User stories/acceptance criteria met
[ ] Internal reviews passed (feedback actioned)
[ ] User testing passed
[ ] Relevant technical documentation updated
[ ] User guidance updated
[ ] Deployed and merged without errors

User Testing Steps
Internal testing only

Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC @KoWeiJAC @tomlovesgithub @warrensearle


Panes do not scroll when params exceed window height.

Hi.
I've come across this issue where you cannot reach certain parameters if the ui exceeds the window height.
I tried to solve this in the parent container using overflow-y: auto; but still the only way to reach the bottom parameters was to collapse parent folders above. Even adding many separate TweakPane instances to a div container with overflow enabled doesnt seem to allow scrolling to reach them.
Is there a simple way to fix this using custom css for tweakpane or is it something that needs to happen in the library its self?
I'm not a css expert so apologies if this is trivial. Thanks in advance.

Maybe your overflow-y setting doesn't work because that element has no hint for its height.
I created a small example for scrollable pane:
https://codesandbox.io/s/tweakpane-scrollable-f4izl?file=/src/styles.css
Does this solve your problem?

You are absolutely right. I just found this 1min ago and was about to message. Apologies for the noise. :)

No problem! I'm glad the problem was solved.

Maybe your overflow-y setting doesn't work because that element has no hint for its height.
I created a small example for scrollable pane: https://codesandbox.io/s/tweakpane-scrollable-f4izl?file=/src/styles.css
Does this solve your problem?

This codesandbox seems to be missing - :disappointed:


L.PM.Utils circleToPolygon

The api states:
circleToPolygon(circle, sides = 60)
When the Circle draw button is clicked and the user draws a circle on the map, can the program code use the properties from e.layer, such as _mRadius or _latlng when calling this utility program, or does the code first have to instantiate a L.Circle variable using these same parameters and then use the L.Circle variable when calling the circleToPolygon utility?
Basically I am asking how to use this utility.  What will function as the "circle" parameter?  Do you have to instantiate a Circle first or can you use a property from e.layer as the "circle" parameter?
Thank you

In the function a L.Circle needs to be passed. You can create a new circle var circle = L.circle(coords, {radius: RADIUS}) or simply pass the e.layer as circle:
map.on('pm:create', (e)=>{
    L.PM.Utils.circleToPolygon(e.layer);
})

Thank you.  I assume I can use the same e.layer in the L.PM.Utils.circleToPolygon(e.layer) if the user were to click the CircleMarker draw button?
Thank you


Open terminal as a build system

Could you support to use of terminal as a build system as Terminus did?
Terminus build system usage of their docs;
Terminus Build System
It is possible to use Terminus as a build system. The target terminus_exec is a drop in replacement of the default target exec. It takes exact same arguments as terminus_open except that their default values are set differently.

terminus_cancel_build is used to cancel the build when user runs cancel_build triggered by ctrl+c (macOS) or ctrl+break (Windows / Linux).

The following is an example of build system define in project settings that run a python script

{
    "build_systems":
    [
        {
            "name": "Hello World",
            "target": "terminus_exec",
            "cancel": "terminus_cancel_build",
            "cmd": [
                "bash", "-c", "echo helloworld"
            ],
            "working_dir": "$folder"
        }
    ]
}
The same Hello World example could be specified via a .sublime-build file.

{
    "target": "terminus_exec",
    "cancel": "terminus_cancel_build",
    "cmd": [
        "bash", "-c", "echo helloworld"
    ],
    "working_dir": "$folder"
}
Instead of cmd, user could also specify shell_cmd. In macOS and linux, a bash shell will be invoked; and in Windows, cmd.exe will be invoked.

{
    "target": "terminus_exec",
    "cancel": "terminus_cancel_build",
    "shell_cmd": "echo helloworld",
    "working_dir": "$folder"
}

https://packagecontrol.io/packages/Terminus

This is a duplicate of #175, #177, and #202. Have you tried a package like https://packagecontrol.io/packages/Console Exec ?


git restack resurrected some old commits

Description of the bug
I ran:
$ git commit --amend --no-edit -a

Creating this event as expected (transaction 1270):
1. Rewrite commit af97f52d as 4aeb26f0

There were three commits (with branch references branch-1, branch-2, branch-3) on top of this, so I restacked:
$ git restack

Expected behavior
The only changes to the repo should pertain to those three commits that were on top of the rewritten commit.
Actual behavior
On the restack, branchless did this (transaction 1272):
1. Move branch branch-2 from 70b392f5 to f62843df
2. Move branch branch-1 from a9da74e3 to 390becf7
3. Move branch branch-3 from 5c79092c to df79967a
4. Rewrite commit a9da74e3 as 390becf7
5. Rewrite commit 70b392f5 as f62843df
6. Rewrite commit 5c79092c as df79967a
7. Hide commit 927e0271
8. Rewrite commit 05cc033d as 5bc26f72
9. Rewrite commit 1fc271c4 as 31dcbfa5
10. Check out from 4aeb26f0 to 4aeb26f0
11. Check out to 4aeb26f0
12. Check out from 4aeb26f0 to 4aeb26f0

Events 7, 8 and 9 were unexpected. For 7, 927e0271 was not even a commit visible in the smartlog at that time (it had been hidden for a while). And events 8 and 9 resurrected some commits that had been hidden before.
And events 10, 11 and 12 also seem a bit spurious, albeit not harmful.
Version of git-branchless
From master 7f938cad70b142541970f05dad7de8b0a55cd653
Version of rustc
rustc 1.56.1 (59eed8a2a 2021-11-01)

Hi @KevinWuWon, thanks for the report. (By the way, your reports using git undo's event log are very helpful. Maybe I should make a git branchless bug-report command which dumps similar information for recent transactions, and add it to the bug report form.)
Can you clarify a few points?

Were you dealing with any merge commits as part of this operation?
Was this an in-memory restack or an on-disk restack?
Do you have any extra Git hooks that might have come into play, such as a pre-commit or post-commit hook? Can you verify that all of the hooks are installed correctly, or reinstall them with git branchless init?
Can you run sqlite3 .git/branchless/db.sqlite3 'SELECT * FROM event_log WHERE event_tx_id IN (1270, 1271, 1272);' and paste it here? (Redact any data you're not comfortable sharing, like reference names.)

(What was in transaction 1271, if anything?)

Do you have any symbolic references other than HEAD in your repository?

What are the contents of .git/ORIG_HEAD, if present?

Were any of the commits involved pointing to a remote repository's commits? For example, if you ran git checkout origin/master and then git commit --amend, then the behavior might be a little bit weird.
Are any of the commits 927e0271, 70b392f5, df79967a or  a descendant of the pre-amend commit af97f52d?

Some of the events in this view are rendered slightly differently:

Event #7 probably says "hide" because it was actually a "rewrite" event which rewrote the commit into the zero OID, which happens sometimes.
Events #10 and #12 are probably "rewrite" events operating on HEAD.

For compatibility with older versions of Git, we install a post-checkout hook. This probably generated event #11, which is a checkout event, but the old location of HEAD is not known.
The reference-transaction hook probably generated events #10 and #12, but I don't know why it happened twice. That is, I would expect up to two checkout events to appear in the log (one from post-checkout and one from reference-transaction), but not three. I suppose this could happen if you had a symbolic reference like ORIG_HEAD.

Maybe I should make a git branchless bug-report command which dumps similar information for recent transactions, and add it to the bug report form.)

Check out

https://crates.io/crates/human-panic
https://crates.io/crates/bugreport

At some point I need to look to see where the two projects can work together.

Were you dealing with any merge commits as part of this operation?

Was this an in-memory restack or an on-disk restack?

Do you have any extra Git hooks that might have come into play, such as a pre-commit or post-commit hook? Can you verify that all of the hooks are installed correctly, or reinstall them with git branchless init?

Can you run sqlite3 .git/branchless/db.sqlite3 'SELECT * FROM event_log WHERE event_tx_id IN (1270, 1271, 1272);' and paste it here? (Redact any data you're not comfortable sharing, like reference names.)

1636361975.37078|rewrite|1270|af97f52db4dbe3b5fc45d86207daffc7bbc618a4|4aeb26f0119491e9bbb0cfbac5ff97aa3f41b245||
1636361980.43348|ref-move|1271|84ddb093c2ef731e577194184e50bc02ddc4cfb0|f4cf242a9a408c41b1d92ba11f3a1cde341d6737|refs/remotes/origin/green|
1636361993.4834|ref-move|1272|70b392f55b6a9cfa79b306f7487deab174fdf1d2|f62843df4623d4b4e0a75e1403d76bafbb966caf|refs/heads/branch-2|
1636361993.4834|ref-move|1272|a9da74e340ea3e527666f8b8251f7902237cee6c|390becf7067d8616722e114168d5be24246b8912|refs/heads/branch-1|
1636361993.4834|ref-move|1272|5c79092cd09796b4d371dd97bf0fec707e85ef16|df79967af22bb6c609cbb48092266463e161f53b|refs/heads/branch-3|
1636361993.54007|rewrite|1272|a9da74e340ea3e527666f8b8251f7902237cee6c|390becf7067d8616722e114168d5be24246b8912||
1636361993.54007|rewrite|1272|70b392f55b6a9cfa79b306f7487deab174fdf1d2|f62843df4623d4b4e0a75e1403d76bafbb966caf||
1636361993.54007|rewrite|1272|5c79092cd09796b4d371dd97bf0fec707e85ef16|df79967af22bb6c609cbb48092266463e161f53b||
1636361993.54007|rewrite|1272|927e0271a5e9c51a359eeb7e77fc32f06f1b8152|0000000000000000000000000000000000000000||
1636361993.54007|rewrite|1272|05cc033d5a757a8eba21b7359426baee39cedc7e|5bc26f72ae3c5e3cfffe0396f3253bfd33708fef||
1636361993.54007|rewrite|1272|1fc271c478e959b5353dbe1bf507807926c2eeb7|31dcbfa5a03679e944bcba9480e916e2d986caa3||
1636362000.82965|ref-move|1272|4aeb26f0119491e9bbb0cfbac5ff97aa3f41b245|4aeb26f0119491e9bbb0cfbac5ff97aa3f41b245|HEAD|
1636362002.09668|ref-move|1272|0000000000000000000000000000000000000000|4aeb26f0119491e9bbb0cfbac5ff97aa3f41b245|HEAD|
1636362006.30816|ref-move|1272|4aeb26f0119491e9bbb0cfbac5ff97aa3f41b245|4aeb26f0119491e9bbb0cfbac5ff97aa3f41b245|HEAD|

(What was in transaction 1271, if anything?)

It was the result of a fetch that happened automatically in the background. It moved origin/green forward.
Move remote branch origin/green from 84ddb093 to f4cf242a

Do you have any symbolic references other than HEAD in your repository?

I see HEAD, FETCH_HEAD and ORIG_HEAD but all have since been overwritten since I saw this bug.  They all have SHAs in them.

What are the contents of .git/ORIG_HEAD, if present?

6a395d05f37a53da50da2ec59b33b1c12ccb1d6d

But this is newly written after this bug happened.

Were any of the commits involved pointing to a remote repository's commits? For example, if you ran git checkout origin/master and then git commit --amend, then the behavior might be a little bit weird.

No.

Are any of the commits 927e0271, 70b392f5, df79967a or a descendant of the pre-amend commit af97f52d?

I'll just give you the full picture.  Should probably refrain from using the hash character so GitHub doesn't interpret them as issue/PR IDs :)

BTW, took me a while to parse the last part of your comment. Should probably refrain from using the hash character so GitHub doesn't interpret them as issue/PR IDs :)

My mistake, that looks terrible 😆 .
I haven't come up with a hypothesis as to why these events would have been resurrected. Can you include the events which affected the relevant commits, something like this?
for c in 927e0271 05cc033d 1fc271c4; do sqlite3 .git/branchless/db.sqlite "SELECT * FROM event_log WHERE old_ref LIKE '$c%' OR new_ref LIKE '$c%';"; done

Let's focus on the two resurrected commits (events 8 and 9):
sqlite> SELECT * FROM event_log WHERE old_ref LIKE '05cc033d%' OR new_ref LIKE '05cc033d%';
1635838203.40332|ref-move|548|3130f848bd9c72c5f08dbd325be77c6dc4e48221|05cc033d5a757a8eba21b7359426baee39cedc7e|HEAD|
1635838203.40332|ref-move|548|3130f848bd9c72c5f08dbd325be77c6dc4e48221|05cc033d5a757a8eba21b7359426baee39cedc7e|refs/heads/another-branch|
1635838676.62233|ref-move|551|05cc033d5a757a8eba21b7359426baee39cedc7e|623d9dffc0e809ac2620db55670eb98173446223|HEAD|
1635838676.62233|ref-move|551|05cc033d5a757a8eba21b7359426baee39cedc7e|623d9dffc0e809ac2620db55670eb98173446223|refs/heads/another-branch|
1636361993.54007|rewrite|1272|05cc033d5a757a8eba21b7359426baee39cedc7e|5bc26f72ae3c5e3cfffe0396f3253bfd33708fef||

sqlite> SELECT * FROM event_log WHERE old_ref LIKE '1fc271c4%' OR new_ref LIKE '1fc271c4%';
1636361993.54007|rewrite|1272|1fc271c478e959b5353dbe1bf507807926c2eeb7|31dcbfa5a03679e944bcba9480e916e2d986caa3||

And showing transactions 548 and 551:
sqlite> select * from event_log where event_tx_id in (548, 551)
   ...> ;
1635838203.40332|ref-move|548|3130f848bd9c72c5f08dbd325be77c6dc4e48221|05cc033d5a757a8eba21b7359426baee39cedc7e|HEAD|
1635838203.40332|ref-move|548|3130f848bd9c72c5f08dbd325be77c6dc4e48221|05cc033d5a757a8eba21b7359426baee39cedc7e|refs/heads/another-branch|
1635838676.62233|ref-move|551|05cc033d5a757a8eba21b7359426baee39cedc7e|623d9dffc0e809ac2620db55670eb98173446223|HEAD|
1635838676.62233|ref-move|551|05cc033d5a757a8eba21b7359426baee39cedc7e|623d9dffc0e809ac2620db55670eb98173446223|refs/heads/another-branch|

Sidenote: my git undo crashed when I tried to go back that far in history. I was in the 560's and pressing p got this:
The application panicked (crashed).
Message:  A fatal error occurred:
   0: 79708aa2ba5b7a6b2f60685c959715b2268062e4 cannot be found

Location:
   /rustc/59eed8a2aac0230a8b53e89d4e99d55912ba6b35/library/core/src/result.rs:1915

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

   0: branchless::git::dag::find_path_to_main_branch with self=<Dag> effects=<Output fancy=true> head=<static [79708aa2ba5b7a6b2f60685c959715b2268062e4]>
      at src/git/dag.rs:422
   1: branchless::commands::smartlog::graph::walk_from_active_heads with effects=<Output fancy=true> dag=<Dag> event_replayer=<EventReplayer events.len=2521 ref_locations.len=52> event_cursor=EventCursor { event_id: 739 } public_commits=<spans [0354c52e2459d828fe4831b9374c3fef707b62e2:27e2829ca0d8116b47db6be384affebafa873022+0:192187]> active_heads=<or <or <or <or <spans [b5696f860f93162bc8c52c5e2d199a375af42826+N470, 23977c9f52de2ddd0ac6352fc585d025088f0980+N421, 246c610563117c86cdb28a75e1bf98b4a21e52a1+N288] + 1 span> <static [79708aa2ba5b7a6b2f60685c959715b2268062e4]>> <lazy [] + ? more>> <static [27e2829ca0d8116b47db6be384affebafa873022]>> <and <lazy [8449ca9b624e0a2f74e03866ae66424464fbfcb2, 60496efa4cb8b2e93c2d9f8224d47a7aad25b662, 4d9a5105919eaaa475263fc75fe9a431f6bbb73a] + 170 more> <spans [0354c52e2459d828fe4831b9374c3fef707b62e2:27e2829ca0d8116b47db6be384affebafa873022+0:192187]>>>
      at src/commands/smartlog.rs:113
   2: branchless::commands::smartlog::graph::make_smartlog_graph with effects=<Output fancy=true> dag=<Dag> event_replayer=<EventReplayer events.len=2521 ref_locations.len=52> event_cursor=EventCursor { event_id: 739 } remove_commits=true
      at src/commands/smartlog.rs:195
   3: branchless::commands::undo::select_past_event with effects=<Output fancy=true> dag=<Dag> event_replayer=<EventReplayer events.len=2521 ref_locations.len=52>
      at src/commands/undo.rs:302
   4: branchless::commands::undo::undo with effects=<Output fancy=true> git_run_info=<GitRunInfo path_to_git="git" env=not shown>
      at src/commands/undo.rs:782

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Location: src/commands/mod.rs:261

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Thanks, that gives me some ideas. My guess is that this is some kind of disagreement about which commits exist between the DAG and the event log structures.
Did this commit come into existence in the local repository before you ran git branchless init? Then, given that the branch moved, this commit would probably be detected by the DAG, but not subsequently excluded from the restack operation by the event log as a commit which was "obsoleted".
I'll try to get a repro case later.

Did this commit come into existence in the local repository before you ran git branchless init?

Quite plausible. This is a relatively recently init'd repo compared to the age of that branch.

Thanks again for the report. It should be resolved in https://github.com/arxanas/git-branchless/commit/98c6517e252b64f3419d7b769b89d79840b21bd5 with a cute little one-line fix.
If you see similar issues in the future after upgrading, let me know. Since the DAG was added well after the event log, it's not unlikely that there are other integration bugs which might cause extra commits to be selected/not selected for a given operation.

Thank you so much for the quick fix! Just tried it out, did a few amends, and didn't see any resurrected commits!


"Copy patch" button should appear next to patch submission

After the model submits, we see a patch in the Terminal. There should be a copy button ("copy patch") similar to the one shown at the end of the log file so that users can easily copy the patch.
This is the patch:

This is the copy button at the log file:

[!tip]
General tips for frontend contributors:

Please open a separate PR for every issue that you address. Try to keep PRs small and concise (if you're thinking of bigger refactorings, please let us know)
In the web UI under "Extra Settings" there's a switch to run without needing API credits for testing purposes
Please install pre-commit (pip install pre-commit && pre-commit install) to ensure that your submission follows the styling guidelines

Should the copy button appear for the whole EnvFeed or just the patch where it is not text?

Hi! It would've been just for the final patch that's being displayed. But the web UI is also not a priority of this project anymore (we want to focus on the core agent), so let me close this as not planned for the moment.


Check correct configuration field when validating visibility store

Previously we were validating wrong configuration field during factory initialization.
This change fixes that and checks visibility config for the visibility factory.
Without this change it is impossible to use docstore as a default storage and cassandra as a visibility gateway.
Note that abstract datastore is currently not supported for visibility and may be added in future.

Coverage increased (+0.01%) to 67.111% when pulling 041488318f2298de98de40bb03ffda6c53253a5c on vitarb:factory-visibility-bug into b9c6f9b5bf04eb62bcfd1f597165b9fa9d8c5903 on uber:master.


Resizable Columns in Grid Don't Work if uiLibrary Set

Run the resizable columns example from the Gijgo site:
http://gijgo.com/LiveEdit/Index/grid.ResizableColumns.resizableColumns.sample.html#
If you run it, the columns can be resized.
Now add this line of code at line 15:
uiLibrary: "bootstrap",
Run the example again. The columns can no longer be resized. This occurs with jqueryui for the uiLibrary as well.
The expected functionality is to have resizable columns regardless of the uiLibrary value.
Thanks!
D'Arcy

This is fixed in the new development version. You can find the new build only in github at https://github.com/atatanasov/gijgo/tree/master/dist until the release of 1.2.0

I added one more additional fix for that in a commit from a minute ago.


Add NuGet publishing

We should add the package to NuGet as well. I've never done this before but would like to do after resolving #1 #2 and #3

Hi @ashkan-saeedi-mazdeh, appreciate that you'd like to get the mentioned issues resolved for package release.  Would it be possible to obtain a pre-release NuGet package with the current latest commits beforehand?
Be happy to submit a PR with a nuspec file that can be used to publish the package.  Process is pretty straightforward if you're not familiar with it.  How to publish pre-release is available here.

Hi @marjum
I think we could configure AppVeyor to run tests then package and publish to NuGet. I'm happy to look at doing this soon, it's fairly easy to accomplish.

Hi @MikeGoldsmith, even better, thanks!

Thanks Mike 👍


Add emeritus and current kitware members

@waxlamp can you take over this PR (or direct to someone who knows html/css) to add other kitware current and past members and add some annotation for "emeritus" to finally address #37?

ping @waxlamp

I've rebased to resolve conflict.  ping @waxlamp to get it addressed.

Drafting as this appears to be a work in progress.


Cannot install dependencies using "uv pip install -r requirements.txt" in WSL2 Ubuntu 24.04

Hi,
I tried too many solutions out there on Issues tab, SO but still unsuccessful in installing the virtual env for this repo.
Below is the error log:
Using Python 3.12.3 environment at venv  Updated https://github.com/andimarafioti/MeloTTS.git (22866a3)  Updated https://github.com/huggingface/parler-tts.git (650288a)  Updated https://github.com/andimarafioti/moonshine.git (21a2225) Updating https://github.com/descriptinc/audiotools (HEAD) error: Failed to download and build:descript-audiotools @ git+https://github.com/descriptinc/audiotools  Caused by: Git operation failed   Caused by: process didn't exit successfully:/usr/bin/git reset --hard 348ebf2034ce24e2a91a553e3171cb00c0c71678` (exit status: 128)
--- stderr
Downloading tests/audio/ir/h179_Bar_1txts.wav (50 KB)
Error downloading object: tests/audio/ir/h179_Bar_1txts.wav (206aee1): Smudge error: Error downloading tests/audio/ir/h179_Bar_1txts.wav (206aee1e87c966ead8a5755b2b90470eaa7c19d55ddbbbeca263ce203c8cab3a): error transferring "206aee1e87c966ead8a5755b2b90470eaa7c19d55ddbbbeca263ce203c8cab3a": [0] remote missing object 206aee1e87c966ead8a5755b2b90470eaa7c19d55ddbbbeca263ce203c8cab3a
Errors logged to '/home/test/.cache/uv/git-v0/checkouts/6d2e2a8294603438/348ebf2/.git/lfs/logs/20241105T094353.722793724.log'.
Use git lfs logs last to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: tests/audio/ir/h179_Bar_1txts.wav: smudge filter lfs failed
`
Are there anyone encountered the same issue and had the solution to overcome this?

Can you try with python 3.11? I had some issues with 3.12 but they looked different to yours

Thanks for reporting, I'll add it to the readme

Same issue is for me.
Here I am using mac for the program.
Tried on python 3.12, 3.11, 3.10, 3.9 as well.
When using uv pip install -r requirements_mac.txt the error I am getting is:
 × No solution found when resolving dependencies:
  ╰─▶ Because torch==2.4.0 has no wheels with a matching Python implementation tag and you require torch==2.4.0, we can conclude that your requirements are unsatisfiable.

Tried using the pip install -r requirements_mac.txt as well. It errs out with
ERROR: Could not find a version that satisfies the requirement torch==2.4.0 (from versions: 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2)
ERROR: No matching distribution found for torch==2.4.0

Just tried changing the torch version in case to 2.2.2. Erred out with
ERROR: Could not find a version that satisfies the requirement mlx (from lightning-whisper-mlx) (from versions: none)
ERROR: No matching distribution found for mlx

^Had the same issue, but switching uv off of python 3.13 (uv venv -p 3.10) fixed the install.
From a similar thread: https://github.com/astral-sh/uv/issues/7516#issuecomment-2414215516


Caching seems to be faulty: results in no (maybe wrong) communities loaded when switching networks

the desired behaviour is:
switching network --> loading cached data from specific network (if no data available, set all relevant data from that network to null)
right now, we manually set chosenId, communityMetadata and communities to null because else the wrong communities and chosenId are taken.

Closed by #535


Update BTC Url

There don't seem to be any edits to the code, did you forget to commit something?

Apparently it didnt commit the changes to the other file, recommited


Copy site template files (using glob)

We changed site template fetching from clone to download/unzip. However, the unzipping function wasn't copying required template files.
This PR updates the site template download to copy all files listed on the template yml (which may use glob patterns). This functionality requires updates to site templates here: https://github.com/executablebooks/myst-theme/pull/178

Nice, tested locally!


Add encodeURIComponent to params on updateNumber

@pvela would love a merge and release.

Merged and published.


TWAI returns ESP_ERR_INVALID_STATE (IDFGH-11362)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I'm having issues getting TWAI to work. I'm now using the TWAI self test example.
If I run the example with a loop wire between TX and RX all works fine.
I (280) main_task: Calling app_main()
I (280) gpio: GPIO[1]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (290) gpio: GPIO[0]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (300) TWAI Self Test: Driver installed
I (310) TWAI Self Test: Driver started
I (310) TWAI Self Test: Msg received - Data = 0
I (320) TWAI Self Test: Msg received - Data = 1
I (330) TWAI Self Test: Msg received - Data = 2
I (340) TWAI Self Test: Msg received - Data = 3
I (350) TWAI Self Test: Msg received - Data = 4
I (360) TWAI Self Test: Msg received - Data = 5
I (370) TWAI Self Test: Msg received - Data = 6

If I remove the loop wire when TX (gpio 0) and RX (gpio 1) the code is left waiting indefinitely as expected with the following code:
ESP_ERROR_CHECK(twai_receive(&rx_message, portMAX_DELAY));
I (280) main_task: Calling app_main()
I (280) gpio: GPIO[1]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (290) gpio: GPIO[0]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (300) TWAI Self Test: Driver installed
I (310) TWAI Self Test: Driver started

If I change to TX (gpio 4) and RX (gpio 5) with the loop wire all works as expected. If I remove the loop wire with the change in IO to 4 & 5 the response is different.
I (285) main_task: Calling app_main()
I (285) gpio: GPIO[5]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (295) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (305) TWAI Self Test: Driver installed
I (315) TWAI Self Test: Driver started
ESP_ERROR_CHECK failed: esp_err_t 0x103 (ESP_ERR_INVALID_STATE) at 0x4200724e
0x4200724e: twai_transmit_task at E:/Software/esp32_examples/twai_self_test/main/twai_self_test_example_main.c:64 (discriminator 1)

file: "./main/twai_self_test_example_main.c" line 64
func: twai_transmit_task
expression: twai_transmit(&tx_msg, portMAX_DELAY)

The issue I have is I have is trying to track down the what is causing the "ESP_ERR_INVALID_STATE" on twai_transmit as this shouldn't happen.

@jrmurdoch  Nice to meet you,,,,
you can config gpio pulldown for RX pin after twai_driver _install to resolve it: gpio_pulldown_en(RX_GPIO_NUM);
It is a driver issue, we will fix it ASAP, thanks for your report, best wishes !! :heart:

@jrmurdoch  Hello, glad to tell you the result:
After internal evaluation, we don't think your usage (left TX and RX pin as floting) is a valid use case. For common TWAI bus usage, we can:

Connected to external PHY for regular application use
Connect TX and RX with jumper for loopback testing
Use same pin for TX and RX (without jumper) for loopback testing

We can floating CAN_H/L after the PHY, but floating TX/RX don't have a defined status, we should't use as this. PLS check
Thank you.

@jrmurdoch  Any other question is welcome, otherwise issue will closed

Happy, I was debugging an issue and noticed that the response was different depending on the pins used which seemed strange. Would have thought that in the event something goes wrong and the pins are disconnected then a common error would be returned regardless of the pins used. Either way the pull-up suggestion you offered resolved this for me.


Add simple method for multi year investment on assets

Pull request details
Describe the changes made in this pull request
Changes to consider the simple method in the investment of assets.
Other related issues are:

Update on ramping constraints #790
Update on binary method for storage #791
Add simple method for transport assets #792

They are done in separate issues to keep the changes as atomic as possible.
List of related issues or pull requests
Closes #786
Collaboration confirmation
As a contributor I confirm

[x] I read and followed the instructions in README.dev.md
[NA] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[x] Tests are passing
[x] Lint is passing

@abelsiqueira depending on the answer from @gnawin here https://github.com/TulipaEnergy/TulipaEnergyModel.jl/issues/462#issuecomment-2343312397 the code might simplify a bit more depending if we don't allow missing values on the investment method.
But, for now, I would appreciate your feedback. Also, these changes might help to have a better overview for the ones in #784

@gnawin, then let's review it together in person because the code reflects the equations that are in the pdf 🤷

@gnawin, my takeaway is that we might need an extra parameter to cover the cases you describe more easily. Otherwise, I don't see a combination that allows existing capacity to be decommissioned without being an investable asset (with the current parameters' definitions).


Old password is not required for signed in users to change password

hasura-auth-js PR: https://github.com/nhost/hasura-auth-js/pull/7

Yea maybe making the oldPassword optional is better.
My reasoning is, that I foresee us refactoring this password-change feature in the near future to support:

oldPassword - for people who know their old password
Some ticket - that comes from the fact that the user clicks on the password reset link in the email.

Basically, the user can change password if they either know their old password or recently clicked on a password reset link. Not, just by the fact that they are signed in.
However, having the oldPassword optional feels a bit... strange.

That sounds reasonable :ship:


Improve script for orakl-config (generates broken table)

didn't generate proper readme file for recent updates for default aggregator,
should update python script
check here
https://config.orakl.network/

https://github.com/Bisonai/orakl-config/pull/36


HLS live source closed caption support

Should fix #1471.
This is an experimental feature, as these kind of subtitles seems to be partially handled by hls.js library.
By partially, i mean it is properly displayed, but not all events are triggered and internal properties like subtitleTracks are not updated. (always empty array returned).
With hls live source, text track data may not immediatly available (same for video element TextTrack objects).
Another issue is that TextTrack cannot be removed from TextTrackList object. Since Clappr player destroy hls instance on player stop for live stream, then the next hls.js instance add more TextTrack objects to video element. (obviously, cannot be currently fixed, maybe later with future specs)
So i managed to find a workaround using this source provided by @UnitedPeace 👍
The only known issue with this fix is that closed captions are set to disabled each time you click on stop (for this live source closed caption types only). So you have to click on CC button again after each play to display subtitles again. (but at least it work !!! 😃 ).

Coverage decreased (-0.04%) to 73.641% when pulling ad24a2f6c0677d319e2900ec316ccf06cdf0a10b on kslimani:fix-hls-cc into 2b0db4cda96b2a2657a28b027554b74ce79252d0 on clappr:master.

hmmm, no clues why Travis run failed ?!!
I deleted my node_modules folder and run yarn install then npm run test and all succeed.
kslimani@df3:~/projects/clappr (fix-hls-cc)$ npm run test

><EMAIL_ADDRESS>test /home/kslimani/projects/clappr
> karma start --single-run

Hash: e0bdc8cc97632b01d813
Version: webpack 3.2.0
Time: 94ms
webpack: bundle is now VALID.
webpack: bundle is now INVALID.
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
webpack: wait until bundle finished:
Hash: f6975818afe09f40933f
Version: webpack 3.2.0
Time: 18278ms
                                    Asset       Size  Chunks                    Chunk Names
             test/playbacks/flash_spec.js     422 kB      10  [emitted]  [big]  test/playbacks/flash_spec.js
     a8c874b93b3d848f39a71260c57e3863.cur  326 bytes          [emitted]
     809981e5b09d5336c45d72d0869ada2a.swf    63.6 kB          [emitted]
     38861cba61c66739c1452c3a71e39852.ttf    32.7 kB          [emitted]
            test/base/base_object_spec.js     304 kB       0  [emitted]  [big]  test/base/base_object_spec.js
     test/plugins/external_plugin_spec.js    2.07 MB       1  [emitted]  [big]  test/plugins/external_plugin_spec.js
                      test/player_spec.js    2.06 MB       2  [emitted]  [big]  test/player_spec.js
           test/components/loader_spec.js    1.73 MB       3  [emitted]  [big]  test/components/loader_spec.js
    test/components/media_control_spec.js     569 kB       4  [emitted]  [big]  test/components/media_control_spec.js
               test/playbacks/hls_spec.js    1.19 MB       5  [emitted]  [big]  test/playbacks/hls_spec.js
       test/playbacks/html5_audio_spec.js     464 kB       6  [emitted]  [big]  test/playbacks/html5_audio_spec.js
       test/playbacks/html5_video_spec.js     467 kB       7  [emitted]  [big]  test/playbacks/html5_video_spec.js
              test/plugins/poster_spec.js     461 kB       8  [emitted]  [big]  test/plugins/poster_spec.js
           test/playbacks/flashls_spec.js     511 kB       9  [emitted]  [big]  test/playbacks/flashls_spec.js
     4b76590b32dab62bc95c1b7951efae78.swf     3.2 kB          [emitted]
               test/plugins/stats_spec.js     445 kB      11  [emitted]  [big]  test/plugins/stats_spec.js
    test/plugins/google_analytics_spec.js     449 kB      12  [emitted]  [big]  test/plugins/google_analytics_spec.js
test/components/container_factory_spec.js     412 kB      13  [emitted]  [big]  test/components/container_factory_spec.js
        test/components/container_spec.js     418 kB      14  [emitted]  [big]  test/components/container_spec.js
             test/plugins/strings_spec.js     326 kB      15  [emitted]  [big]  test/plugins/strings_spec.js
                test/base/ui_core_spec.js     335 kB      16  [emitted]  [big]  test/base/ui_core_spec.js
    test/base/ui_container_plugin_spec.js     334 kB      17  [emitted]  [big]  test/base/ui_container_plugin_spec.js
               test/base/playback_spec.js     344 kB      18  [emitted]  [big]  test/base/playback_spec.js
              test/base/ui_object_spec.js     331 kB      19  [emitted]  [big]  test/base/ui_object_spec.js
            test/base/core_plugin_spec.js     315 kB      20  [emitted]  [big]  test/base/core_plugin_spec.js
       test/base/container_plugin_spec.js     315 kB      21  [emitted]  [big]  test/base/container_plugin_spec.js
                 test/base/events_spec.js     305 kB      22  [emitted]  [big]  test/base/events_spec.js
                  test/base/utils_spec.js     191 kB      23  [emitted]         test/base/utils_spec.js
          test/components/browser_spec.js    14.9 kB      24  [emitted]         test/components/browser_spec.js
 [222] ./test/components/container_factory_spec.js 1.44 kB {13} [built]
 [223] ./test/base/utils_spec.js 8.98 kB {23} [built]
 [224] ./test/components/container_spec.js 5.46 kB {14} [built]
 [225] ./test/components/loader_spec.js 5.86 kB {3} [built]
 [226] ./test/playbacks/flash_spec.js 1.85 kB {10} [built]
 [227] ./test/components/media_control_spec.js 6.47 kB {4} [built]
 [228] ./test/playbacks/flashls_spec.js 3.18 kB {9} [built]
 [229] ./test/playbacks/html5_audio_spec.js 749 bytes {6} [built]
 [230] ./test/playbacks/hls_spec.js 4.52 kB {5} [built]
 [231] ./test/player_spec.js 3.48 kB {2} [built]
 [232] ./test/plugins/external_plugin_spec.js 3.04 kB {1} [built]
 [234] ./test/playbacks/html5_video_spec.js 13.4 kB {7} [built]
 [235] ./test/plugins/google_analytics_spec.js 4.33 kB {12} [built]
 [236] ./test/plugins/poster_spec.js 4.31 kB {8} [built]
 [238] ./test/plugins/strings_spec.js 1.89 kB {15} [built]
    + 224 hidden modules
webpack: bundle is now VALID.
20 07 2017 16:10:14.903:INFO [karma]: Karma v1.4.0 server started at http://<IP_ADDRESS>:9876/
20 07 2017 16:10:14.905:INFO [launcher]: Launching browsers Chrome, Firefox with unlimited concurrency
20 07 2017 16:10:14.914:INFO [launcher]: Starting browser Chrome
20 07 2017 16:10:14.954:INFO [launcher]: Starting browser Firefox
20 07 2017 16:10:16.005:INFO [Chrome 59.0.3071 (Linux 0.0.0)]: Connected on socket LSqWK5_xr2pkoJaCAAAA with id 32498308
20 07 2017 16:10:18.748:INFO [Firefox 54.0.0 (Linux 0.0.0)]: Connected on socket yje03mUy4Q3R5xV1AAAB with id 77804771
LOG: '%c[error][Events]', 'color: #ff0000;font-weight: bold; font-size: 13px;', 'error on event', 'clappr.any.event', 'trigger', '-', Error{}
LOG: '%c[error][hlsjs: unrecoverable network fatal error, evt hlsError, data [object Object] ]', 'color: #ff0000;font-weight: bold; font-size: 13px;'
Chrome 59.0.3071 (Linux 0.0.0): Executed 142 of 194 (skipped 2) SUCCESS (0 secs / 0.499 secs)
LOG: '%c[error][hlsjs: unrecoverable network fatal error, evt hlsError, data [object Object] ]', 'color: #ff0000;font-weight: bold; font-size: 13px;'
LOG: '%c[error][hlsjs: unrecoverable network fatal error, evt hlsError, data [object Object] ]', 'color: #ff0000;font-weight: bold; font-size: 13px;'
Firefox 54.0.0 (Linux 0.0.0) LOG: '%c[error][Events]', 'color: #ff0000;font-weight: bold; font-size: 13px;', 'error on event', 'clappr.any.event', 'trigger', '-', Error{}
Firefox 54.0.0 (Linux 0.0.0) LOG: '%c[error][hlsjs: unrecoverable network fatal error, evt hlsError, data [object Object] ]', 'color: #ff0000;font-weight: bold; font-size: 13px;'
Chrome 59.0.3071 (Linux 0.0.0): Executed 192 of 194 (skipped 2) SUCCESS (1.043 secs / 0.63 secs)
Firefox 54.0.0 (Linux 0.0.0) LOG: '%c[error][hlsjs: unrecoverable network fatal error, evt hlsError, data [object Object] ]', 'color: #ff0000;font-weight: bold; font-size: 13px;'
Firefox 54.0.0 (Linux 0.0.0) LOG: '%c[error][hlsjs: unrecoverable network fatal error, evt hlsError, data [object Object] ]', 'color: #ff0000;font-weight: bold; font-size: 13px;'
Chrome 59.0.3071 (Linux 0.0.0): Executed 192 of 194 (skipped 2) SUCCESS (1.043 secs / 0.63 secs)
Firefox 54.0.0 (Linux 0.0.0): Executed 192 of 194 (skipped 2) SUCCESS (2.604 secs / 0.839 secs)
TOTAL: 384 SUCCESS

=============================== Coverage summary ===============================
Statements   : 73.13% ( 3861/5280 )
Branches     : 53.62% ( 985/1837 )
Functions    : 55.97% ( 581/1038 )
Lines        : 73.28% ( 3856/5262 )
================================================================================

=============================== Coverage summary ===============================
Statements   : 73.14% ( 3862/5280 )
Branches     : 53.46% ( 982/1837 )
Functions    : 56.36% ( 585/1038 )
Lines        : 73.3% ( 3857/5262 )
================================================================================

@kslimani I rerun it and it passes now 👍  if that happens more often we should try to see what causes it. For instance, we can blame Travis 🤤

cool ! thank you @leandromoreira !


Shepherd successor of NC PR #37914

https://github.com/nextcloud/server/pull/37914
Due to issues with the rebase/merge the PR will need to be re-created.

The successor has still not been created?


Protocol Upload: Session class has a "simulate" method for RPC

Overview
Simulation will be optional. Run app needs a way to initiate a simulation.
The purpose of the simulation is only to find potential errors in the protocol.
Acceptance Criteria

Session has a public simulate method available over RPC.
simulate does not alter the state of the Session object (ie does not recreate run log, equipment list, etc.).

Closing due to different route taken w/ "fast sim" work.


RuntimeError: PyTorch is not linked with support for mps devices

I run two spatial samples with same method and py, one successed, the other one failed with RuntimeError: PyTorch is not linked with support for mps devices
detailed:
Epoch 20000/20000: 100%|██████████| 20000/20000 [12:31:38<00:00,  2.25s/it, v_num=1, elbo_train=1.82e+7]
Sampling local variables, batch:   0%|          | 0/1 [00:00<?, ?it/s]
File "/home/ksd/bin/Python-3.10.4/lib/python3.10/site-packages/cell2location/models/_cell2location_model.py", line 338, in export_posterior
  self.samples = self.sample_posterior(**sample_kwargs)
File "/home/ksd/bin/Python-3.10.4/lib/python3.10/site-packages/scvi/model/base/_pyromixin.py", line 483, in sample_posterior
  samples = self._posterior_samples_minibatch(
File "/home/ksd/bin/Python-3.10.4/lib/python3.10/site-packages/scvi/model/base/_pyromixin.py", line 365, in _posterior_samples_minibatch
  args = [a.to(device) for a in args]
File "/home/ksd/bin/Python-3.10.4/lib/python3.10/site-packages/scvi/model/base/_pyromixin.py", line 365, in <listcomp>
  args = [a.to(device) for a in args]
RuntimeError: PyTorch is not linked with support for mps devices

my code is failed on this step:
adata_vis = mod.export_posterior(adata_vis, sample_kwargs={'num_samples': 1000, 'batch_size': mod.adata.n_obs, 'use_gpu': True})

Is this error reproducible? What happens if you train the model again or simply restart the notebook and load the model?

Is this error reproducible? What happens if you train the model again or simply restart the notebook and load the model?

no，i finally found it must be run one by one，may be CPU is not enough, but my cpu is 72C 144T

What do you mean by "run one by one"? You can also try changing batch size for mod.export_posterior

It 's a CPU problem. You must set 'use_gpu' as false


Fix allowed FQDN for pypi.org

Update tests and lint Python
Resolves #3651
What is being addressed
Incorrect firewall allow rule for pypi.org: *pypi.org
How is this addressed

Update firewall rule to *.pypi.org
Update references in tests

/test-force-approve

LGTH, some of the formatting changes are a bit distracting, but functionally it's fine :)

Understood. I just hit save and some extension's formatter kicked in 🙂.


Extend User object

Describe your issue in as much detail as possible.
I have added a custom SeqNo column to the Parse.User object
Steps to reproduce
i am assigning a value to the SeqNo in the before save trigger
Expected Results
I expect the SeqNo to set correctly.
Actual Outcome
But the value is not set properly. It is null or undefined
Environment Setup

Server

parse-server version: 2.2.10
Operating System:     linux (ubuntu)
Hardware:             ....
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [Digital Ocean]

Database

MongoDB version: 3.2.4
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [Digital Ocean]

Ok, I figured out how to extend the Parse User object.


drawer overlaps with StatusBar on ios

On Android, drawer works perfectly and status bar looks like good. While on ios it overlaps. How can it be solved? I am using expo and tried all in their documentation still the same issue I see on the simulator.

@Hayko1994 you can workaround by calling hide/show status bar on iOS. I've seen a lot of apps do the same thing (Google Inbox and Slack).

Pinging OP @Hayko1994 since this issue has not been active for a while, and it's related to an old version of the lib.
Please let me know if you want this to remain open (does it still happen in the latest version?); if I get no answer in the next 7 days I will close it.

Hi there @Hayko1994 ,
In an effort to cleanup this project and prioritize a bit, since this issue had no follow up since my last comment I'm going to close it.
If you are still having the issue with the latest version (especially if it's a bug report) please check the current open issues, and if you can't find a duplicate, open a new one that uses the new Issue Template to provide some more details to help us solve it.

just use css. in case your side drawer is an aside, use this:
aside {
top: env(safe-area-inset-top)!important;
}