fix: stop win service when context.Done is closed

@jehiah I think this is ready

Note the branch is now main and I moved the package from github.com/judwhite/go-svc/svc to github.com/judwhite/go-svc


Hosts file entries are commented out after some period of time (on windows)

Title pretty much sums it up. At least on Windows, after ~15 minutes the entries that hostsupdater makes are commented out, and I have to manually un-comment them.
Is this behavior configurable somewhere? I wasn't able to find any documentation for it.
Thanks!

Answering my own issue: turns out this has nothing to do with hostsupdater. It comes from the security suite I'm using, Bitdefender. See: http://superuser.com/questions/1018133/windows-10-hosts-file-entries-been-commented-out


unable to force close channel

Background
First I tried to openchannel with low onchain fee. After more then 2 weeks of not-confirming, I did lncli bump fee channelpoint:outputindex. Channel got finally confirmed but was inactive probably because of longer then 2week of not-confirming. Therefore, i tried to force close it. After force closing it (via LiT terminal), it shows in lncli pendingchannels but not as "pending_force_closing_channels" but in "waiting_close_channels" with "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator", when i do lncli closechannel --funding_txid --output_index --force to force close it again, it throws error ... "channel is already in the process of being force closed". I can see closing_txid in mempool.space, but lncli walletbalance cannot see those funds "unconfirmed"
Your environment

version of lnd lnd 16.4
which operating system (uname -a on *Nix) ubuntu server 22  5.15.0-83
version of btcd, bitcoind, or other backend - bitcoind
any other relevant environment details

Steps to reproduce
lncli openchannel
lncli wallet bumpfee --sat_per_byte xx outputpoint:index
force closing channel via LiT terminal (v10.5)
Expected behaviour
I was expecting to have this channel force closed, in lncli pendingchannels as "pending_force_closing_channels"
Actual behaviour
in lncli pendingchannels i have this channel under "waiting_close_channels" with "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator"

Was the force close transaction confirmed? If yes then the next step is that you have to wait for the CSV timelock to expire in order to get the channel fully resolved, which could take some days.

could it be that when i was bumping fee in openning channel (lncli wallet bumpfee --sat_per_byte xx outputpoint:index) .... i accidentaly put --sat_per_byte (not --sat_per_vbyte) so channel got openned with closing non segwit address and that is why i cannot see it in my onchain segwit wallet?

That shouldn't have to do with it. It would be helpful if you could share the txid or give more info about the confirmation status of the force close.

Moving this issue to a discuss thread, as there is nothing for us to fix here


--latest and --freeze flags

We should carefully review the install constraint situation and properly support these flags ensuring they are behaving as designed. See also in reference to use cases like described in https://github.com/jspm/generator.jspm.io/pull/7 where updating the package.json range and then installing should use the new package.json range either by default or explicitly when adding --latest, I'm not sure which just yet though!

Currently jspm install <blah> will perform an update of <blah> if it's outside the package range, and jspm update <blah> will update to the latest in the package range explicitly. So maybe we don't need to support --latest, keep things simpler.
I'll add a flag for --freeze though, I guess the semantics is that any existing stuff in the import map should remain totally unchanged, right?


Include dummy audit event for each cycle?

So it's obvious that revolver is working, and completing.  Otherwise, for tools that consume the audit output, broken looks the same as no-changes.

Nah, just use the resource CSV output.


Function Documentation: Ability to use flex-gutter as a size function throughout stylesheet

Generally just seeing if there was any interest in adding something around this. I swear i've looked through the documentation site up & down, and haven't found anything.
The ability to set/use flex-gutter() as a sizing function is one of the most convenient and powerful things i've come across. It's been really nice to use the gutter as margins to set consistent sizing throughout.

Going to ping on gitter first. That's a better idea :)


Sitemap links pointing to the wrong base URL

Story link URLs in the sitemap have a base URL of sitemap.theworld.org URL and not the base URL: https://sitemap.theworld.org/wp-sitemap-posts-post-1.xml

Adding to Four Kitchens Queue

Fixed in #216


Maybe[A] should be renamed

Per mailing list discussion here: https://groups.io/g/pony+user/thread/689696#36
Maybe[A] should be renamed MaybePointer[A]

Resolved in #590


Indexer: Warpcast links are treating the local-fetch UserAgent as a user in a browser and serving CORS secured open graph urls

https://warpcast.com/df/0x517afbce
We should consider either a special rule for this domain or to change our User-Agent string

I don't think there's a way for us to fix, with a browser UA it's rendering no OG tags


NDK 25

Next RN will use NDK 25. checking everything compiles fine with it.

Closing. will open a new one when https://github.com/BabylonJS/JsRuntimeHost/pull/70 is merged.


Support JSON with the MQTT Trigger

I'm submitting a ...  (check one with "x")
[] bug report => search github for a similar issue or PR before submitting
[x] feature request
[] support request
[] general question

Current behavior (how does the issue manifest):
MQTT messages are normally JSON ... but the MQTT trigger output a string
Expected behavior:
output a "object" type when required
Minimal steps to reproduce the problem (not required if feature enhancement):
revieve a message and try to find a way to parse it to an object
What is the motivation / use case for changing the behavior?
make FLOGO easier to use with JSON data
Please tell us about your environment (Operating system, docker version, browser & web ui version, etc):
Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X
0.5.5
Additional information you deem important (e.g. issue happens only occasionally):
Very

@ayh20 assuming the message from the trigger is mapped to a flow param of typ object and message contains a valid json string, then the engine will coerce the type into the object that the flow executes against.
Were you experiencing a different behavior?


chore(FA): Add info log when merging a fleet policy

What does this PR do?
Adds a small info log when merging a fleet policy
Motivation
QA comment in https://datadoghq.atlassian.net/browse/ASCII-2146
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[Bug]: SyntaxError: Unexpected token '&&='

What happened?
After running commands:
npx create-discordx # selected 1-starter
npm run build
export BOT_TOKEN=MY_BOTS_TOKEN
npm run start

I get this error:
file:///home/ugnelis/GIT/exergale/bird-game-discord-bot/my-app/node_modules/@discordx/internal/build/esm/decorator/util.js:43
                cond &&= a.index === b.index;
                     ^^^

SyntaxError: Unexpected token '&&='

Reproduction
npx create-discordx # selected 1-starter, package manager NPM
npm run build
export BOT_TOKEN=MY_BOTS_TOKEN
npm run start

Package
@discordx/internal
Version
Stable
Relevant log output
npm run start

><EMAIL_ADDRESS>start /home/ugnelis/GIT/exergale/bird-game-discord-bot/my-app
> node build/main.js

file:///home/ugnelis/GIT/exergale/bird-game-discord-bot/my-app/node_modules/@discordx/internal/build/esm/decorator/util.js:43
                cond &&= a.index === b.index;
                     ^^^

SyntaxError: Unexpected token '&&='
    at Loader.moduleStrategy (internal/modules/esm/translators.js:145:18)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

what's your node version?

The problem was with node version


Automate bower dependencies

Scenario:
Dev A adds bower dependency, pushes code. Dev B pulls code, runs nitro and gets a broken Frontend > due to missing dependencies.

We should probably find a way how to solve that.
This ticket is more of a reminder than a bug report.

Possible solution: https://gist.github.com/sindresorhus/7996717

Thanks Simon
Works like a charm – in a modified version also on windows.
But this must be configured manually on each project.
What du you think about git-guppy or ghooks?

Something similar: we could add a postinstall hook in the package.json to install bower dependencies automatically, after running npm install.
"scripts": {
    "postinstall" : "bower install"
}

This git hook should solve this:
https://github.com/namics/generator-nitro/blob/master/app/templates/project/.githooks/post-merge
As default it will be installed with npm install


#125 relative path to absolute path

Summary
It closes #125
Extra info

Needs more than 2 reviewers? n
Needs more than 10 minutes for review? n
Needs to execute in order to review? n

Frame/이나 Tools/가 많이 쓰이는것 같은데 아래와 같이 설정해서 @Frame/~로 쓰는건 어떤가요.

@imYourChoi 반영하였습니다!


added remaining methods from provided cyanide documentation

All are tested and functional. Except that teammatches is currently not working. No clue as to why.

it is teammatches, not matches

it is teammatches, not matches

Ah, of course. Thanks for spotting the mistake.


After editing issue key actions no longer works

I open jira-ui, select a query, use down-arrow to select an issue, enter to view issue.  Then "E" to edit the issue, I see edit screen, make a change and exit out of edit and back to viewing issue.  At this point navigation is dead, I cannot "q" back to the query results, and "P" and "N" do not go away from issue.  In fact it seems like no keys work, include C-c q, so I cannot even exit.  The only way to get back to console is it open another console and kill the process.  No idea what the root cause of this is.

Did a bit of debugging, I can see the "registerEventHandlers" routine getting called after the editor completes but none of the event handler ever get triggered after that, not sure why that is yet.
-Cory

Oddly enough it works if I use vim, but not if I use (my default) emacs for the editor of issues.  So It seems like the emacs shutdown process is doing something to the tty/terminal that is confusing the termui event processor somehow.
-Cory

Thanks for the feedback Cory, will take a look. Someone has just got a PR merged into termui that better manages the removal of handlers, so that's one avenue I can pursue. I don't know if it handles the tty mangling though, which is - as you point out - is the likely cause.

Thanks, I went down the rabbit hole for a while debugging termui and termbox and was never able to resolve it.  It it acting like stdin is closed to the jira-ui, or at least the stdin that termui is reading from is closed after returning from the emacs subshell.  After I launch emacs and go back to jira-ui then entering keys does nothing, but as soon as I kill jira-ui all the keys that I pressed get printed to the console.  So something is getting blocked up, but not sure what/why.  In any case this is unlikely an issue specifically with jira-ui and I think more to do with termui or termbox. When I get more time to dig in I will try to reproduce in a smaller test case and file an issue with the appropriate project.
fwiw, I did pull in the latest termui to test against and had the same issue.


"We're sorry, but something went wrong." in development env

Description
On a Rails project, if I force an error (e.g. RoutingError) in development environment, the stack trace is printed in the browser, no problem (First screenshot below).
But after installing RailsAdmin, the stack trace is only printed in the console but not on the browser, showing the "We're sorry, but something went wrong" (Second screenshot below).
An ActionView::Template::Error appears in the console with RailsAdmin installed. (see "Console logs" section below)
Console logs

Without RailsAdmin
With RailsAdmin

Screenshots
Without RailsAdmin :

With RailsAdmin :

can you share your routes.rb too?

I forced the RoutingError by using a fake path but if you want
Rails.application.routes.draw do
  resources :articles do
    resources :comments
  end
  root "articles#index"
  # For details on the DSL available within this file, see http://guides.rubyonrails.org/routing.html
end

Your rails version is 5.20?

Yes but I had the issue two days ago with Rails 5.1.6
Le jeu. 12 avr. 2018 à 16:00, Cristopher Vidal Machado <
<EMAIL_ADDRESS>a écrit :

Your rails version is 5.20?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sferik/rails_admin/issues/3012#issuecomment-380815311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHZt6pZzypofvh5U1PjlVZ-ZUQrCRBbvks5tn14MgaJpZM4TPfdX
.

I got a same issue with ruby 2.4.1, rails 5.0.7

Had this happen to me as well. Happens when you do not run:
 rails g rails_admin:install

Something in the package without installing breaks Rails' error view, which makes any exception go to the production (rather than development) 500 page.

^ I've just checked, and the same error occurs even if you don't mount RailsAdmin (step 8 above)

Seems like it is an issue from remotipart https://github.com/JangoSteve/remotipart/issues/194

I got a same issue with Ruby2.4.4,  Rails5.1.6

Looks like it's an issue with remotipart (1.4.0).
You can choose to downgrade remotipart by:

Opening your Gemfile.lock
Find and replace remotipart (1.4.0) with remotipart (1.3.0)
bundle and restart your server

remotipart 1.4.1 is out, upgrade will solve the problem.

I'm having this issue and I have remotipart 1.4.2 currently.

I installed the gem 'better_errors "and I solved the problem momentarily, but then it came back to me as soon as I created new resources ... does anyone know how to solve it?


HDDS-10487. Intermittent crash in TestSnapshotDiffManager

What changes were proposed in this pull request?
Fix intermittent crash in TestSnapshotDiffManager:

Avoid recreating SnapshotDiffManager without closing the previous instance.  Actually the new one seems to be unnecessary, as original one is created @BeforeEach.
Close SnapshotDiffManager before closing RocksDB objects.

https://issues.apache.org/jira/browse/HDDS-10487
How was this patch tested?
No crash in 500 runs (but had 5 failures due to NPE, reported in HDDS-10490):
https://github.com/adoroszlai/ozone/actions/runs/8191095498
Regular CI:
https://github.com/adoroszlai/ozone/actions/runs/8191527914

Thanks @hemantk-12 for the review.


benchmarks & comparisons

To show how fast memo can be

For example, here's a preliminary result with the gridworld value iteration demo


When is a project old/not maintained?

It would be nice to have a clearer definition of old projects so we know exactly when they are ready to be put in the archive. In fact if we had a "X days without a commit" kind of definition, then in theory a script could go through the github links and check for outdated apps automatically.

Time would be an indicator but basically we should archive projects that no longer build or that was not updated for current iOS - 2
There could be exceptions
What do you think

I think that's fair. Certainly not all old applications are broken and not all new applications work. Could you put that somewhere in the CONTRIBUTING.md or on the wiki please?

Will do

Updated https://github.com/dkhamsing/open-source-ios-apps/wiki/Deleting

Good work, thanks!


use videojs-hotkeys in Angular

Thank you Team for the plugin.
Guys, can anyone here give an example of how to make use of videojs-hotkeys in Angular.

@akashgaikwad91 Did you come up with an example? If so, will you please share it here?

I just found a solution myself. I followed the sample that thijstriemstra gave a link to in issue [#6747](https://github.com


different GitHub & npm versions

🐛 Bug Report
The newest unstable versions on npm (v3.0.0-charlie.1) & Github (v23.0.0-alpha.0) are different.  The difference is confusing & seems like a mistake.  I'd advise either keeping one platform pre-RC free, or release all versions to both platforms in sync.
Thanks so much for all your hard work & constant updates!

Pushing the prerelease tags seems like the best solution IMO, but just deleting the one from github might be easier

The alpha one shouldn't be there. Sorry! :)

POF! It's gone :) Thanks for the report!


Automated cherry pick of #8361: fix: do not lock guest after lock eip, to prevent possible dead lock

Cherry pick of #8361 on release/3.4.
#8361: fix: do not lock guest after lock eip, to prevent possible dead lock

/lgtm
/approve


Investigate scoreboard right click functionality

I can't seem to figure out what causes this to happen; disabling the scoreboard.res file doesn't have any effect, which would suggest something else controls this. Will have to poke around some more.

Interestingly enough, I think this is merely just bugged as all heck still. It randomly works for me. I don't believe this is a hud issue, but I'll leave it open for a bit in case anyone else has any comments.


Deduplicate inline fn dav1d_get_cpu_flags to src/cpu.rs and enum CpuFlags to src/x86/cpu.rs

I'm not sure why it can't find src::cpu::dav1d_get_cpu_flags on --target armv7-unknown-linux-gnueabihf, as cargo check --target armv7-unknown-linux-gnueabihf works fine locally.  Is there an easy way to reproduce what CI runs locally?  Having everything in rust-toolchain.toml and .cargo/config.toml so it can run anywhere would be nice.

Ahh, asm is disabled.  I think I figured it.

@thedataking, is there any reason for keeping the arch-specific enum CpuFlags,

Yes, the flags are all x86 specific so it makes sense to keep them where they are. A second reason is that we don't want to diverge from the structure of the C code (at least at this stage) since it would complicate debugging and troubleshooting. A third reason is that we've asked you to keep your changes focused on one thing. Finally, on a more general point, you should bias leaving stuff alone unless you have a good working understanding of the code you're changing and there is a need to change it; this reduces the risk that stuff gets messed up inadvertently. For theses reasons, I would strongly recommend you revert bc2c2883835af77033f695ffe91b0d3674d1a82e.


Azure Form Recognizer Sample Issue

Section link

Reason:
Property does not exist on type 'string | number | Record<string, FormField> | Date | FormField[]'.
Suggestion:
Update fields.Items.value to fields.Items.value as StrongObjectField<ReceiptItem>[].
@jongio for notification.

Thanks for reporting @zzhxiaofeng
@willmtemple Do you agree with the recommendation above? If yes, then please add the help wanted and good first label.

@zzhxiaofeng I'm unable to reproduce this error. Can you provide the following information to help me diagnose this?

TypeScript Compiler Version
Node.js Version
Versions of installed azure SDK packages for the sample:

@azure/ai-form-recognizer
@azure/identity

tsconfig.json settings

@willmtemple Well, my configurations are shown as below:

TypeScript Version: 3.9.5
Node.js Version: 12.18.0
Versions of installed azure SDK packages for the sample:

@azure/ai-form-recognizer: 3.0.1-alpha.20200924.1
@azure/identity: 1.2.0-alpha.20200921.2

tsconfig.json settings:

{
  "compilerOptions": {
    "target": "ES6",
    "module": "commonjs",
    "moduleResolution": "node",

    "allowSyntheticDefaultImports": true,

    "strict": true,
    "alwaysStrict": true,

    "outDir": "dist",
    "rootDir": "src"
  },
  "include": ["src/**.ts"],
  "exclude": ["node_modules"]
}

I find the reason must be I specify ECMAScript target version as ES6. Please have a look at this.

I can't think of any reason that changing the target would have this effect, but indeed it does. The sample compiles with TypeScript 4.0.0.There is some manipulation we can do to the StrongObjectField and StrongArrayField types to make them more accurate. I have a feeling that's what is causing the weirdness here.
@zzhxiaofeng thanks for reporting this issue, we've added this to the November milestone for the next planned Form Recognizer preview release.

@zzhxiaofeng I believe we addressed this incompatibility by making the types in the sample more specific in #12203 . I am closing this issue, but feel free to re-open it if the problem persists.

@willmtemple The code here has rolled back to the origin version. Can you have a look or tell me the reason if it is right.


make icon appear on left in vertical menu item

so, I have the following menu :

  tables

Hosting

      Shared
      Dedicated

Support

      E-mail Support
      FAQs

which gives me this ..

However, I would like the icon on the left of the label - but can't seem to find the words (!) to get it to move to the left
What is the magic incantation / chicken-bone throwing thing I have to do in order to get the icon on the left ? ;)
First-time semantic-ui user, so perhaps I'm missing something really simple
thanks!

Not sure if you still need it, but anyway—I think you’ll have to write your own CSS to add this. Something like that.

Add the following CSS
.ui.vertical.menu .item > i.icon.left {     float: none;     margin: 0em 0.35714286em 0em 0em; }
and modify icon tag by adding left to the class as shown below
`
tables

Hosting

Shared
Dedicated

Support

E-mail Support
FAQs

'


./examples/oauth.js "Secure Connection Failed"

I'm trying ./examples/oauth.js
I get the flickr page, and after I click [OK, I'LL AUTHORIZE IT], I get a "Secure Connection Failed" page
Any hint?
Secure Connection Failed

An error occurred during a connection to localhost:3000. PR_END_OF_FILE_ERROR

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

using an https server, with self-signed certificate, allows to go through the authentication process and get the oauth token.
See attached patch
flickr-sdk_examples_oauth.js__use-https.patch.txt


Add config file for lab19

Related to:

https://github.com/VILLASframework/documentation/pull/81
https://github.com/VILLASframework/documentation/pull/79

Hi @pipeacosta @al3xa23,
Do we still want to merge these changes? Or should we abandon the PR?


move some tensor ops out of extensions

This lets AD differentiate functions containing these ops before we fix SR-8699.
This only moves the static differentiable functions out of the extensions. Rewriting the few nonstatic differentiable functions (e.g. transposed, convolved2D) sounds like a bunch of throwaway work, so I did not do that.

@swift-ci please test tensorflow linux cpu


Pagination component for logs is left-aligned.

Steps

Go to project dashboard of a project with many log entries.
View the log widget on the project dashboard.

Expected
The bootstrap pagination component should be centered.
Actual
The bootstrap pagination component is left-aligned.
See
@jlcohoon Are there other pagination components that are left aligned on the OSF?

The other place has the pagination is the add contributor and add link modal:

@JeffSpies do you want there to be centered as well?

We don't like the left-align?

If we get a vertical separator between Results and Adding similar to the
horizontal separators we currently have.
On Thu, May 28, 2015 at 10:43 AM, Nan Chen<EMAIL_ADDRESS>wrote:

The other place has the pagination is the add contributor and add link
modal:
[image: screen shot 2015-05-28 at 10 40 30 am]
https://cloud.githubusercontent.com/assets/4974056/7862800/3fc7107c-0526-11e5-987c-47809d54245b.png
@JeffSpies https://github.com/JeffSpies do you want there to be
centered as well?
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/issues/2861#issuecomment-106368143
.

@lbanner traditionally that would be centered or full-width. The latter making some sense because we have "..." indicating we don't have space to fill out the pagination (while we do).
Left-aligned looks off to me, but it is subjective.

@GaryKriebel Can I work on this?

I am good with that @ZobairAlijan -- you are tagged. Check with @chennan47 w/any questions -- he did the foundational work.

@lbanner Thank you

One more place with left align—the watchlist:

The watch log is using the same template as logs. So change on one place
will affect the other. It's good for people who did this fix to verify that.
On Fri, May 29, 2015 at 12:45 PM, jlcohoon<EMAIL_ADDRESS>wrote:

One more place with left align—the watchlist:
[image: screen shot 2015-05-29 at 12 42 51 pm]
https://cloud.githubusercontent.com/assets/4965832/7887623/82beeb40-0600-11e5-9c65-c9f5d7882c01.png
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/issues/2861#issuecomment-106868168
.

This issue has been fixed and waiting to be merged.

Will be considered in later pagination enhancement. Thanks.


The canvas layer image shows abnormal white stripes

Attach (recommended) or Link to PDF file here:
test.pdf
Configuration:

Web browser and its version: chrome 86.0.4240.198
Operating system and its version: macOS Catalina 10.15.7
PDF.js version:  The latest code on the master branch
Is a browser extension: no

Steps to reproduce the problem:

Clone this project and gulp server
Upload my pdf

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

After uploading my pdf to your web demo, white stripes appear in the two rectangles. I guess there is a problem with the canvas layer. How can I solve it?

WFM, in both Firefox and Google Chrome on Windows.

Web browser and its version: chrome 86.0.4240.198
Operating system and its version: macOS Catalina 10.15.7

This is most likely a platform, or possible <canvas>-related, bug in Google Chrome on MacOS; as such it's unfortunately difficult to see that this is an actionable/valid issue here.


Backport of PRs to 3.1 branch [batch 2]

Second batch of backport commits to 3.1.
Made on top of first batch #19587 so draft until that one is merged.

First batch is merged. This is now rebased on top of the first batch. Please approve.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merging this now.

Merged to 3.1 branch. Thank you.


Ordering Facility Phone Number is missing if ORC-23-1 is missing

OBE.  Fixed by #1069 when support for XTN phone number was added.


Need to configure ryuk memory size

Don't own or maintain the build servers in my organization. Need to be able to configure the memory and swap size of the ryuk container. Currently the default it is using the Docker default of allocation 2GB per container.
Example (in a Spring Boot app):
src/resources/testcontainers.properties
ryuk.container.memory = 8388608
ryuk.container.swap = 16777216

Hi @jamesdschmidt,
There is no "default memory allocation" in Docker. By default, Docker containers are not limited in memory, and Ryuk process is a tiny Golang process that requires ~4Mb of RAM:


So 304 is all good by why no package?

The log says it all.
info it worked if it ends with ok
verbose cli [ 'node', '/usr/local/bin/npm', 'install', 'http' ]
info using<EMAIL_ADDRESS>info using<EMAIL_ADDRESS>verbose config file /Users/billn/.npmrc
verbose config file /usr/local/etc/npmrc
verbose config file /usr/local/lib/node_modules/npm/npmrc
verbose cache add [ 'http', null ]
silly cache add: name, spec, args [ undefined, 'http', [ 'http', null ] ]
verbose parsed url { pathname: 'http', path: 'http', href: 'http' }
verbose addNamed [ 'http', '' ]
verbose addNamed [ null, '' ]
silly name, range, hasData [ 'http', '', false ]
verbose raw, before any munging http
verbose url resolving [ 'http://registry.npmjs.org/', './http' ]
verbose url resolved http://registry.npmjs.org/http
verbose etag "7X9WCTXT1Y0BJLF9HXB4412R1"
http GET http://registry.npmjs.org/http
http 304 http://registry.npmjs.org/http
silly get cb [ 304,
silly get cb   { server: 'CouchDB/1.1.0 (Erlang OTP/R14B04)',
silly get cb     etag: '"7X9WCTXT1Y0BJLF9HXB4412R1"',
silly get cb     date: 'Wed, 08 Feb 2012 01:07:04 GMT',
silly get cb     'content-length': '0' } ]
verbose etag http from cache
silly name, range, hasData 2 [ 'http', '', true ]
silly versions [ 'http', [] ]
ERR! Error: No compatible version found: http
ERR! No valid targets found.
ERR! Perhaps not compatible with your version of node?
ERR!     at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:488:10)
ERR!     at next_ (/usr/local/lib/node_modules/npm/lib/cache.js:438:17)
ERR!     at next (/usr/local/lib/node_modules/npm/lib/cache.js:415:44)
ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:408:5
ERR!     at saved (/usr/local/lib/node_modules/npm/lib/utils/npm-registry-client/get.js:147:7)
ERR!     at Object.oncomplete (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:231:7)
ERR! You may report this log at:
ERR!     http://github.com/isaacs/npm/issues
ERR! or email it to:
ERR<EMAIL_ADDRESS>ERR!
ERR! System Darwin 11.3.0
ERR! command "node" "/usr/local/bin/npm" "install" "http"
ERR! cwd /Users/billn/Documents/Nodejs/webserver
ERR! node -v v0.6.10
ERR! npm -v 1.1.0-3
ERR! message No compatible version found: http
ERR! message No valid targets found.
ERR! message Perhaps not compatible with your version of node?
verbose exit [ 1, true ]

It's right there in the error message.
ERR! Error: No compatible version found: http
ERR! No valid targets found.
ERR! Perhaps not compatible with your version of node?

Your version of node is 0.6.10.  It wants ~0.4.8.
$ npm view http engines -q
{ node: '~v0.4.8' }

You can use the --force flag to make it install inspite of this constraint, but this may cause unexpected run-time behavior.
If you're wanting to make HTTP requests, I'd strongly recommend using request.  It's extremely easy to use, and very well maintained.  (npm uses it internally.)

What is 'it'
the http package
or
npm
?

OK. its the package.
--force appears to work but http.js is content free!
For something that is supposed to simplify life there seem to be a lot of snafus.

Ah, you're right.  It's also from several months ago.  I just removed it.
What is it you're trying to do.  Do you know that http is a native module in node already, so you don't have to install anything to amke require("http") work?


Trusted Sources Tab

Corresponding Services PR: https://github.com/CatalystCode/project-fortis-services/pull/152

Closing this to use https://github.com/CatalystCode/project-fortis-interfaces/pull/78 instead.


Switching to Screen if already open

Sorry about the newbie question
I am using a TabBar to navigate my app and it works great because it switches seamlessly between screens. However, I have not been able to duplicate its behaviour inside the screens themselves.
My chat screen has 2 buttons: one that shows a messaging list and the other a friend list. When clicking the buttons I open the relevant screens. However, it is creating a new screen each time I press a button instead of just switching to the screen that already exists (as in the TabBar). How can I do this?
BTW I am using open ScreenName, not open ScreenName.new

@augustosamame Sorry about the late response. I think I need a little more context -- could you post some code?

I'm going to close this since it has been open for a long time. Let us know if you need any more help!


Fixed some scripts issues with EACCES

This PR updated the readme by indicating the user location when running the scripts and adding sudo on some scripts where needed to avoid EACCES -- DELETE BRANCH AFTER MERGE.

Why would a build and test need sudo?

Why would a build and test need sudo?

I agree that that shouldn't be necessary. In the GH Action log, I don't see an EACCESS, but I do see the problem with the non-presence of the lionweb-integration-testing repo still, so that can't be (directly) related to root access.
The clarification about in which working directory to execute the scripts: 👍

I agree. They shouldn't, but when I ran them, they threw EACCES permission denied. So, probably, this can be fixed within the code

It seems to work without problems, so no need for the sudos.


[WIP] Implement 'base_site' filter on LocationFilterSet

Closes: #2518
What's Changed

Implement a base_site Location filter using a fairly naïve approach (filter on site, or on parent__site, or on parent__parent__site, etc. up to the maximum current depth of the Location tree). I tested UI filtering with about 2000 Locations (thanks #2540!) and it seems reasonably quick (a couple of seconds to apply), especially compared to alternate approaches I've tried.

Further progress is probably blocked by #2540 for now as I don't want to collide with its extensive alterations to the DCIM tests.
Showing the use of this filter in query_params to only show Locations that match the selected site, including descendants

Filtering Locations table by multiple sites

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

My thinking is that we might want a base_location or parent_location filter at that time which would basically work the same as this one, just filtering directly on parent, parent__parent, etc. instead of on parent__site, parent__parent__site, etc.


Port Parser.js to @flow

@marcianx I think this is going to be the hardest one.  Thanks for tackling this.

Yes. Yes it is. ;) I've run into at least 4 challenges.
The first two a are just a bunch of grunge work, but doable:

functionHandler's return type (in defineFunction) is *. It needs to be enumerated.
ParseNode's value type is *, and that needs to be enumerated *.
Although, who knows what surprises await. ;)

The third one is more fundamental. Many uses of ParseFuncOrArgument (which I've turned to ParsedFunc | ParsedArg | ParsedDollar) predicate strictly on whether or not it is a function, an they don't distinguish ParsedArg from ParsedDollar. It's a locally non-obvious (to me at least) implementation artifact that ParsedDollar cannot appear in these places and so the implementation doesn't check it. I would, of course, increase the final js size by adding thrown Errors, but I'm guessing that's not desired, and we might just want to $FlowFixMe those places to suppress the errors.
The fourth thing is that parseImplicitGroup methods call functions (parseFunction), but treat the return value as non-nullable and directly dereference it. It's not locally-obvious (at least to me) why that should be the case. I was going to try to produce cases that would fail based on local reasoning and see if they don't when running the full parser. Maybe tomorrow.

Yup, definitely a bit of a ball of yarn.  If possible, please try to separate this into multiple PRs.  The ParsedDollar is quite implicit so anything we can do to make that more explicit is probably good.  We might want to switch out isFunction: boolean for type: "function" | "argument" | "dollar".
Is functionHandler's return type the same as ParseNode's value's type?
We should try to get rid of parseImplicitGroup.  This should be doable at this point since we're including a reference to the Parser instance in the context we pass to the function handlers.  This might actually be a good first step to take as its own PR.

This is quite the adventure! I'm trying to go a bit more deeply into the weeds to understand the extent of the changes needed to have strong guarantees and convertibility to @flow without resorting to type-unsafe features like any.
One example I've been trying to understand is FunctionHandler vs ParseNode. The problem is that ParseNode's value type can either be the output of FunctionHandler (let's call it NodeData)  or something else that's been constructed in Parser itself (like the "size" ParseNode created there). NodeData has a type field, but ParseNode has its own type field on top of that, which makes it very difficult to make them both type-safe without a lot of redundancy. For example, NodeData is already something like
type NodeData = {|
    type: "sqrt",
    body: ParseNode,
    index: ?ParseNode,
|} | {|
    type: "text",
    body: ParseNode[],
    font: ?string,
|} | {|
    type: "color",
    color: string,
    value: ParseNode[],
|} | {|
    type: "enclose",
    label: string,
    backgroundColor: ParseNode,
    borderColor: ?ParseNode,
    body: ParseNode,
|} | {|
    type: "overline" | "underline",
    body: ParseNode,
|} ... // more here

If ParseNode were turned into an object with a method to construct it, then for maximal type-safety, it would have a type like
type ParseNode = {|
    type: "\\sqrt",
    value: {|
        type: "sqrt",
        body: ParseNode,
        index: ?ParseNode,
   |},
   mode: Mode,
   ... // lexer, start, end
|} | ... // additional variants

and also some variants like the following that are constructed within Parser.js itself.
... {|
    type: "size",
    value: {|  // has no `type` field!
        number: number,
        unit: string,
    |},
    mode: Mode,
   ... // lexer, start, end
|}

So now ParseNode serves two purposes: (1) many ParseNodes constructed in Parser serve as input into FunctionHandler (like the "size" example above), and (2) it also wraps the output of FunctionHandler (NodeData, which always provides a type field). I'm not sure whether we need to separate those out, but it feels a little messy to me when it comes to reasoning about things.
So I'm considering a systemic refactor of ParseNode so that it no longer has its own separate type, but becomes
{|
data: NodeData,
mode: Mode,
... // lexer, start, end
|}
IOW, we'd collapse the two redundant types. The type-discriminated union would then be isolated to NodeData which would serve as the single enumeration of all possibilities. Note that this would be slightly lossy since there are multiple functions that map to the same NodeData type—e.g. \\colorbox, \\fcolorbox, \\cancel and others map to type="enclose" in functions.js. However, if the original function name is needed, it could be stored in NodeData itself as an additional field.
 So this refactor would have to be...diligent. But I'm up for it for all that's worth.
I could start with first putting up the intended types in comment @params for reference and we can go forward from there. A lot of it can be incremental, like ensuring that the ParseNode's value always has a type field before ParseNode's own type field can be dissolved. E.g. the "size" ParseNode's value type would become
    {|
        type: "size",   // redundantly added
        number: number,
        unit: string,
    |}

and things like ordgroups and others would be changed from
new ParseNode("ordgroup", expression, this.mode,
                    firstToken, lastToken)

to
new ParseNode("ordgroup", {type: "ordgroup", args: expression}, this.mode,
                    firstToken, lastToken)

WDYT? Is the test suite up to par? Or do you think we should go a different way?

@marcianx thanks for digging deep and providing a detailed writeup.
I was actually thinking we'd combine ParseNode and NodeData into a single node.  Maybe something like:
type Common = {
   loc: SourceLocation | null,
   mode: "math" | "text",
}

type SourceLocation = {
   start: Token,
   end: Token,
   lexer: Lexer,
}

type SqrtNode = BaseNode & {
   type: "sqrt",
   body: ParseNode,
   index: ?ParseNode,
}

type TextNode = BaseNode & {
    type: "text",
    body: ParseNode[],
    font: ?string,
}

type ParseNode = SqrtNode | TextNode | ... ;

The main benefit I see in this approach is a shallower tree.  The reason for introducing loc is to avoid conflicts between metadata props and node specific props.
I find it weird that sqrt nodes use body: ParseNode whereas text nodes use body: ParseNode[] while color nodes use value: ParseNode[].  I would like to suggest introducing a new node type called a GroupNode which looks like:
type GroupNode = BaseNode & {
   type: "ordgroup",
   children: ParseNode[],
}

All other nodes would always use body and body would always be a single node.  I guess GroupNode is kind of like ordgroup, but we'd use it more consistently.  Also, ordargument would become:
const ordargument = function(arg: ParseNode) {
    return arg.type === "ordgroup" ? arg : new ParseNode("ordgroup", {children: [arg]});
};

As for the lossy nature, one nice benefit of being non-lossy is being able to generate LaTeX code from the AST.  This may be useful for interactive editors or other tools people may develop in the future like codemods for TeX code.  I think we include the name of the function that was used to generate the node.  If it's the same as the type that's okay.
Before doing any major refactor we should get the following PRs reviewed and merged: #871, #875, #885, and #887 (and maybe #884).

Sounds good to me. In the meantime, I'll do some minor refactors that don't seep (too far) outside Parser, but allow making it more type-stringent.

It's great that type checking is leading us toward refactoring improvements to the parse tree!  FWIW, I've found the difference between what's returned by a function (a la defineFunction) and the actual parse node (wrapping in another value, as I recall) to be confusing and unnecessary.  I think that's one of the things you're discussing fixing?

@edemaine Indeed!
@kevinbarabash Actually, isn't it "harder" to construct and pass around
type SqrtNode = BaseNode & {
   type: "sqrt",
   body: ParseNode,
   index: ?ParseNode,
}

// Given
type BaseData = {
   loc: SourceLocation | null,
   mode: "math" | "text",
}

type SourceLocation = {
   start: Token,
   end: Token,
   lexer: Lexer,
}

than, say,
type SqrtNodeData = {
   type: "sqrt",
   body: ParseNode,
   index: ?ParseNode,
}
type Node<Data> = {
   value: Data,
   mode: Mode,
   loc: SourceLocation,
}

?
The former seems to require constructing the whole object at once, whereas for the latter, FunctionHandler can return SqrtNodeData and Parser can construct Node<Data> with all the metadata. Or did you wish to require updating all the FunctionHandlers to set the metadata (mode, loc) as well?

Or perhaps your suggestion can be modified to
type SqrtNodeData = {
   type: "sqrt",
   body: ParseNode,
   index: ?ParseNode,
}
type NodeData = (SqrtNodeData | ...);
type Nodes = NodeData & Common;

Then, FunctionHandler can return NodeData, and Parser can add the additional metadata fields in the same object itself.

@marcianx I really like your suggestion of doing type Nodes = NodeData & Common;

@kevinbarabash I noticed that #871 and #887 seem to be on a bit of a lull, but they don't obviously seem blocked. Is there anything I can do to help?
I'm not sure I can make any particular progress on refactoring ParseNode's structure that would not touch a lot of code overlapping with those PRs.

@marcianx if you'd like to review them that would definitely help.


Sonarr/Radarr version, api changes.

Radarr.log
Sonarr.log
sonarr - <IP_ADDRESS>9 — Jan 20 2024    linuxserver docker
radarr - <IP_ADDRESS>76 — Dec 24 2023  linuxserver docker
Apparently, there have been changes in the API in the latest versions, and "current_free_space" either changed its name or no longer exists.
It would be helpful to add the last known working version for both.

Can you please send over your configs, this is a config issue. I run the testing branch of both Radarr and Sonarr to stay ahead and detect changes early

Fixed, please update to the latest version

Also just a side note, this had nothing to do with Radarr/Sonarr. I run the develop branches of both to ensure I detect any issues ahead of most people


Added bad and good samples answers

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Hi Amanda, can you please check the file now? I don't know why it was not pushed before, sorry.


Feature/theme 04

ignore hyde branch, this is what I had working locally.

:+1:
this looks good to me. just checked locally.
close the issues that are related to this when you merge it :-D


Synthia Dataset

"May I ask which sequences from the SYNTHIA dataset were used for training and testing in your article? I would like to compare my method with yours using this dataset."

train model


dnsmasq problem when installing tuya-convert on two Linux Mint machines

I am trying to flash four newly bought Nous A1 - that had no contact to the app so far.
Therefor, I tried to install tuya-convert on a desktop (Intel NUC with wifi) and a Lenovo laptop, both failed with the message:
dnsmasq (2.80-1.1ubuntu1.4) wird eingerichtet ...
Created symlink /etc/systemd/system/multi-user.target.wants/dnsmasq.service → /lib/systemd/system/dnsmasq.service.
Job for dnsmasq.service failed because the control process exited with error code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dnsmasq, action "start" failed.
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-02-24 12:28:52 CET; 5ms ago
    Process: 120537 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
    Process: 120538 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=2)

Feb 24 12:28:52 ande-hac systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Feb 24 12:28:52 ande-hac dnsmasq[120537]: dnsmasq: Syntaxprüfung OK.
Feb 24 12:28:52 ande-hac dnsmasq[120538]: dnsmasq: failed to create listening socket for port 53: Die Adresse wird bereits verwendet
Feb 24 12:28:52 ande-hac dnsmasq[120538]: failed to create listening socket for port 53: Die Adresse wird bereits verwendet
Feb 24 12:28:52 ande-hac dnsmasq[120538]: Start fehlgeschlagen
Feb 24 12:28:52 ande-hac systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Feb 24 12:28:52 ande-hac systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Feb 24 12:28:52 ande-hac systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

Although I've not installed dnsmasq before, it complains about a port 53 "in use". Not sure why..?
They https://github.com/ct-Open-Source/tuya-convert/pull/838 say it might not be a problem but I still get in the loop
Starting smart config pairing procedure
Waiting for the device to install the intermediate firmware
Put device in EZ config mode (blinking fast)
Sending SSID                  vtrust-flash
Sending wifiPassword
Sending token                 00000000
Sending secret                0101
................
SmartConfig complete.
Resending SmartConfig Packets
.................
[...]
.................
SmartConfig complete.
Resending SmartConfig Packets
...........
Timed out while waiting for the device to (re)connect
======================================================
Attempting to diagnose the issue...
No ESP82xx based devices connected according to your wifi log.
Here is a list of all the MAC addresses that connected:

If you see your IoT device in this list, it is not an ESP82xx based device.
Otherwise, another issue may be preventing it from connecting.
For additional information, check the *.log files inside the scripts folder.
Please include these logs when opening a new issue on our GitHub issue tracker.
======================================================
Do you want to try flashing another device? [y/N]

These are my logs:
MQTT:
ande@ande-hac:~/tuya-convert$ cat scripts/smarthack-mqtt.log
[130880.294249]~DLT~122403~INFO     ~FIFO /tmp/dlt cannot be opened. Retrying later...
1645703474: mosquitto version 1.6.9 starting
1645703474: Using default config.
1645703474: Opening ipv4 listen socket on port 1883.
1645703474: Opening ipv6 listen socket on port 1883.
^C1645703564: mosquitto version 1.6.9 terminating
[130980.235213]~DLT~122403~WARNING  ~Lost log messages in user buffer when exiting: 9
[   78.045761]~DLT~ 2274~INFO     ~FIFO /tmp/dlt cannot be opened. Retrying later...
1645703689: mosquitto version 1.6.9 starting
1645703689: Using default config.
1645703689: Opening ipv4 listen socket on port 1883.
1645703689: Opening ipv6 listen socket on port 1883.
^C1645703967: mosquitto version 1.6.9 terminating
[  365.492876]~DLT~ 2274~WARNING  ~Lost log messages in user buffer when exiting: 9

PSK:
ande@ande-hac:~/tuya-convert$ cat scripts/smarthack-psk.log
^CTraceback (most recent call last):
  File "./psk-frontend.py", line 113, in <module>
    main()
  File "./psk-frontend.py", line 106, in main
    r,_,_ =  select.select(readables, [], [])
KeyboardInterrupt
^CTraceback (most recent call last):
  File "./psk-frontend.py", line 113, in <module>
    main()
  File "./psk-frontend.py", line 106, in main
    r,_,_ =  select.select(readables, [], [])
KeyboardInterrupt

UDP:
ande@ande-hac:~/tuya-convert$ cat scripts/smarthack-udp.log
Listening for Tuya broadcast on UDP 6666
Listening for encrypted Tuya broadcast on UDP 6667
^CListening for Tuya broadcast on UDP 6666
Listening for encrypted Tuya broadcast on UDP 6667

WEB:
ande@ande-hac:~/tuya-convert$ cat scripts/smarthack-web.log
Listening on <IP_ADDRESS>:80
^CReceived SIGINT, exiting...
Listening on <IP_ADDRESS>:80
^CReceived SIGINT, exiting...

WIFI:
ande@ande-hac:~/tuya-convert$ cat scripts/smarthack-wifi.log
System info
===========
61ba060
Linux ande-hac 5.4.0-100-generic #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
OpenSSL 1.1.1f  31 Mar 2020
Dnsmasq Version 2.80  Copyright (c) 2000-2018 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth nettlehash DNSSEC loop-detect inotify dumpfile

Für diese Software wird ABSOLUT KEINE GARANTIE gewährt.
Dnsmasq ist freie Software, und du bist willkommen es weiter zu verteilen
unter den Bedingungen der GNU General Public Lizenz, Version 2 oder 3.
hostapd v2.9
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2019, Jouni Malinen<EMAIL_ADDRESS>and contributors
Python 3.8.10
===========
Attempting to stop wpa_supplicant
Stopping NetworkManager...
Configuring AP interface...
RTNETLINK answers: File exists
Starting DNSMASQ server...
Starting AP on wlp0s20f3...
Configuration file: /dev/stdin
Using interface wlp0s20f3 with hwaddr 24:41:8c:9e:30:b3 and ssid "vtrust-flash"
wlp0s20f3: interface state UNINITIALIZED->ENABLED
wlp0s20f3: AP-ENABLED
wlp0s20f3: interface state ENABLED->DISABLED
wlp0s20f3: AP-DISABLED
wlp0s20f3: CTRL-EVENT-TERMINATING
nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
AP closed
Stopping DNSMASQ server...
Restarting NetworkManager...
System info
===========
61ba060
Linux ande-hac 5.4.0-100-generic #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
OpenSSL 1.1.1f  31 Mar 2020
Dnsmasq Version 2.80  Copyright (c) 2000-2018 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth nettlehash DNSSEC loop-detect inotify dumpfile

Für diese Software wird ABSOLUT KEINE GARANTIE gewährt.
Dnsmasq ist freie Software, und du bist willkommen es weiter zu verteilen
unter den Bedingungen der GNU General Public Lizenz, Version 2 oder 3.
hostapd v2.9
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2019, Jouni Malinen<EMAIL_ADDRESS>and contributors
Python 3.8.10
===========
Attempting to stop wpa_supplicant
Stopping NetworkManager...
Configuring AP interface...
RTNETLINK answers: File exists
Starting DNSMASQ server...
Starting AP on wlp0s20f3...
Configuration file: /dev/stdin
Using interface wlp0s20f3 with hwaddr 24:41:8c:9e:30:b3 and ssid "vtrust-flash"
wlp0s20f3: interface state UNINITIALIZED->ENABLED
wlp0s20f3: AP-ENABLED
wlp0s20f3: interface state ENABLED->DISABLED
wlp0s20f3: AP-DISABLED
wlp0s20f3: CTRL-EVENT-TERMINATING
nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
AP closed
Stopping DNSMASQ server...
Restarting NetworkManager...

Where could I look to help?
Both machines are Linux Mint version 20.3
Thanks for any hint on this..
Andreas

Not sure if this helps, but I had a similar issue.  I am running tuya-convert as a docker container.
I had a DNS server running on the host (i.e. which is a Raspberry Pi).  As the docker configuration is using "host" networking, there was a conflict when the dnsmasq service in the container attempted to listen on the wifi interface of the Raspberry Pi.
I had to change the DNS server to be more specific for the interfaces that it is listening on.


Non-local Ollama server Fail to connect

Describe the bug
In the ouput I keep getting the app-dev_1   | WARN Constants Failed to get Ollama models:  fetch failed messages over and over.  My setup is a bit different from most of the posts I see here as I am running a Ollama server on my local network.  The URL is set in the .env.local file and it is being set in the UI from what I can tell because the UI seems to have a value set as you can see in the screenshot below.

This seems similar to #721 but the fix that worked for him is not working for me.
I know the Ollama server is running and ports are open since I also run an openwebui frontend from the same box I am trying to run bolt.diy from.  In other words the route is tested every time I run a query in openwebui.
Additionally the model select dropdown is not populated with any options as I would expect if the connection was just full failing.
My architecture is pretty simple.  Ollama server on local network-> Web server for Bolt.diy on different box on local network.
Link to the Bolt URL that caused the error
Not public accessable
Steps to reproduce

Install bolt.diy on a different box form the Ollama server
Configure the URL in the .env.local file
start the bolt.diy server
navigate to the UI and it should be broken

Expected behavior
I expected the bolt.diy frontend to be able to find the Ollama server
Screen Recording / Screenshot

Platform

OS: Ubuntu
Browser: Brave
Version<EMAIL_ADDRESS>dev

Provider Used
No response
Model Used
No response
Additional context
No response

can you try setting the url in the setting tab?

Same issue here. I've tried git clone of main as well as download of the v0.0.2 tar.gz.
I've tried settings environment variables OLLAMA_API_BASE_URL to http://<IP_ADDRESS>:11434. I've tried .env (also removed this file from .dockerignore)`. I've also tried setting this value through the UI. No matter how it's set I get this warning in stdout:
[WARN] Failed to get Ollama models:  Network connection lost.

Using...

Docker host OS: Debian 12.7 amd64
Ollama 0.4.4 at http://<IP_ADDRESS>:11434 (no acls etc and reachable by other containers and network devices)
Deployment: docker compose --target production up -d --build with configuration in, .env

From within the bolt-ai container I can successfully curl http://<IP_ADDRESS>:11434/api/tags to enumerate ollama models. In the container .env.local is symlinked to .env file so, if the application is looking for either will find the same configuration.

Logging the import.meta.env object shows that it is not populated as expected (OLLAMA_API_BASE_URL is an empty string, while there is a sensible value for this variable in .env file, Wrangler even sees it) :

when using the UI to set the baseUrl which I recommend it uses the browser cookies in both server and the frontend to get the configuration so these variables will be ignored

can you provide a screen shot??

 When I load the page I see no activity from ollama, I would expect to see a GET /api/tags maybe. If I enter text into bolt chat prompt with ollama selected and no model set I do see requests from ollama's side.
From ollama stdout:
[GIN] 2024/12/17 - 17:35:12 | 200 |    1.757872ms |      <IP_ADDRESS> | GET      "/api/tags"
[GIN] 2024/12/17 - 17:35:12 | 404 |     680.206µs |      <IP_ADDRESS> | POST     "/api/chat"

From bolt stdout:
✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

✘ [ERROR] workerd/server/server.c++:3613: error: Uncaught exception: workerd/io/io-context.c++:1207: failed: remote.jsg.Error: The script will never generate a response.

  stack: /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@35294c0 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@352a9d0 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@352b5d0 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2f03e90 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2f03f6e /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@359b35d /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2ee4b00 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@419688c /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@5aa58af /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4195280 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2ed9f10 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@38d5e90 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@36dacf0 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@36db121 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@5aa58af /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@352ac70 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@352b5d0 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2f03e90 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2f03f6e /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2f05fdc /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@41aa9e7 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@41abbf2 /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@41ac69e /app/node_modules/.pnpm/@cloudflare+workerd-linux-64@1.20241106.1/node_modules/@cloudflare/workerd-linux-64/bin/workerd@4171f90

✘ [ERROR] Uncaught (in response) Error: The script will never generate a response.

[wrangler:inf] POST /api/chat 200 OK (261ms)

Hope this helps.

Cookies for page cleared, then all LLM providers disabled except ollama, with URL set through the GUI. I reload the page, ollama is selected, there are no models shown in the dropdown.
I am running packet capture on ollama docker interface, I see nothing when bolt page is loaded, it's not pulling ollama models, but in the bolt stdout I still see [WARN] Failed to get Ollama models:  Network connection lost..
Nothing that I do in the bolt UI generates traffic to ollama until attempting to start a chat "hello world" and press enter (again, no model selected), then I see this in ollama docker interface packet capture...
   24 11.070320324   <IP_ADDRESS> → <IP_ADDRESS>   HTTP 119 GET /api/tags HTTP/1.1
   26 11.071783873   <IP_ADDRESS> → <IP_ADDRESS>   HTTP/JSON 2558 HTTP/1.1 200 OK , JavaScript Object Notation (application/json)
   32 11.239335116   <IP_ADDRESS> → <IP_ADDRESS>   HTTP/JSON 3046 POST /api/chat HTTP/1.1 , JavaScript Object Notation (application/json)
   34 11.240106465   <IP_ADDRESS> → <IP_ADDRESS>   HTTP/JSON 259 HTTP/1.1 404 Not Found , JavaScript Object Notation (application/json)

Now for details about the above... the GET to /api/tags and json payload is returned containing the models hosted by ollama. However, the next POST from bolt is asking for model claude-3-5-sonnet-latest which I don't have. Every other provider is disabled in the UI and I provide no API keys or any other configuration for other providers. It makes sense that if the dropdown doesn't populate and I don't have a model selected it would 404 or error when a valid model is needed.
As a sanity check are any of these models (not) supported by bolt?
From: curl -s http://<IP_ADDRESS>:11434/api/tags | jq -r '.[][].name' | sort
all-minilm:33m
chroma/all-minilm-l6-v2-f32:latest
llama3.1:70b
llama3.3:70b
llama3:70b
qwen2.5-coder:7b-instruct-q8_0
qwq:32b

As a sanity check are any of these models (not) supported by bolt?

all the models are supported and should appear.
can you please use the 0.0.2 version. it has fix for auto select correct model.
can you give us the debug details in the debug tab. just click on copy to clipboard and paste here

@k1rb You need to figure out why the UI fails to load models list from Ollama (which in turn leads to Bolt performing a chat request to Ollama with a model Ollama does not know). May be you should check if there is any specific error message or request error in your browser's console or network requests log (using dev tools) when you refresh the index page. May be you can also try to re-enable another provider, switch to it and then back to Ollama (I'm unclear of when the UI triggers the reloading of the model list).

Correct, my primary issue is that ollama models aren't populated by bolt. The chat errors are secondary. I have reread the issue title and body and they accurately describe my issue.
The chat errors only help to prove that, despite not pulling ollama models initially, that bolt can communicate with ollama.
I have tried re-enabling other providers and tried switching between providers to get bolt to get ollama models. No change.
But hey, here's some good information from browser console (in both ff and chrome), a 403 caused by CORS (strict-origin-when-cross-origin). And I'm not sure why it's showing localhost:1234, assuming some default value somewhere.

are these in separate vm or container? can you tell us about your configurations or setup on how these are running (ollama and bolt)?

These are separate physical boxes. 1 running ollama and 1 running bolt.

Seeing the same kind of stuff on my end

I'm having same issue.. I've updated the BASE URL in the .env.local file yet it is not recognizing the ollama models installed locally on the server. I also updated the OLLMA BASE URL in the UI but still no luck.
WARN[0000] The "GROQ_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "HuggingFace_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "OPENAI_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "ANTHROPIC_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "OPEN_ROUTER_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "GOOGLE_GENERATIVE_AI_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "OLLAMA_API_BASE_URL" variable is not set. Defaulting to a blank string. ---------------> says variable not set
WARN[0000] The "TOGETHER_API_KEY" variable is not set. Defaulting to a blank string.
WARN[0000] The "TOGETHER_API_BASE_URL" variable is not set. Defaulting to a blank string.
WARN[0000] The "GROQ_API_KEY" variable is not set. Defaulting to a blank string.

The solution for me is to include the bolt URL in ollama environment variable OLLAMA_ORIGINS.
docker run -d \
  --name ollama \
  ...
  -e OLLAMA_ORIGINS=https://bolt.domain.tld \
  ...
  ollama/ollama:0.4.4

When the container starts you'll see this value prepended to the default list.
OLLAMA_ORIGINS:[https://bolt.domain.tld http://localhost https://localhost http://localhost:* https://localhost:* http://<IP_ADDRESS> https://<IP_ADDRESS> http://<IP_ADDRESS>:* https://<IP_ADDRESS>:* http://<IP_ADDRESS> https://<IP_ADDRESS> http://<IP_ADDRESS>:* https://<IP_ADDRESS>:* app://* file://* tauri://* vscode-webview://*]

I believe cors header is related to Ollama server
and cannot be solved in this project
i found an issue in ollama repo you can check
https://github.com/ollama/ollama/issues/7150

@Jeevanhm Not sure if this helps but it turned out that initially in my setup the .env.local file was made available to the Docker container (image built in production mode), given that "*.local" files are excluded as per .dockerignore contents. I had to manually add a volume to the running container to mount it to /app/.env.local. That being said, it is probable that your issue is somewhere else given that UI settings should be taken into account and take precedence over what is specified in the .env.local file.

The solution for me is to include the bolt URL in ollama environment variable OLLAMA_ORIGINS.
docker run -d \
  --name ollama \
  ...
  -e OLLAMA_ORIGINS=https://bolt.domain.tld \
  ...
  ollama/ollama:0.4.4

When the ollama container starts you'll see this value prepended to the default list.
OLLAMA_ORIGINS:[https://bolt.domain.tld http://localhost https://localhost http://localhost:* https://localhost:* http://<IP_ADDRESS> https://<IP_ADDRESS> http://<IP_ADDRESS>:* https://<IP_ADDRESS>:* http://<IP_ADDRESS> https://<IP_ADDRESS> http://<IP_ADDRESS>:* https://<IP_ADDRESS>:* app://* file://* tauri://* vscode-webview://*]

Mentioned ollama FAQs

I'm running ollama on the server and bolt on a docker container.

@Jeevanhm Not sure if this helps but it turned out that initially in my setup the .env.local file was made available to the Docker container (image built in production mode), given that "*.local" files are excluded as per .dockerignore contents. I had to manually add a volume to the running container to mount it to /app/.env.local. That being said, it is probable that your issue is somewhere else given that UI settings should be taken into account and take precedence over what is specified in the .env.local file.

This could be my issue, how do i add a volume to the running container to mount it to /app/.env.local? sorry I'm basic with docker commands.

I would like to throw in my 2 cents here. Rewritten this 4 times so please bear with me if it's confusing.
I've been dealing with this issue for days now since I built a local headless Ubuntu server (Bolt and Ollama same server) and want to communicate with Bolt via my other workstations. Works fine with Grok but latency is too slow. Hacked through the other options with many CORS/SSL cert errors. Here's my findings so far.
My Configuration
Both Bolt and Ollama are setup into their own Docker containers. Both are proxied through Nginx and work through SSL independently confirmed with Curl testing. I've installed the self signed certs on my primary Mac laptop and Firefox recognizes them.
Common issues
The constants.ts file seems to be shared between client and server which is creating tons of issues not only with endpoint setup, but confuses new installs by throwing errors on the server that aren't affecting the outcome of the app. For example, I finally fixed the model list dropdown by setting my Ollama https domain URL on the client side through the settings window, however setting that same URL in the .env file on the server side throws a fetch() error in docker. The server side error doesn't seem to affect anything however the next issue may be the problem.
After getting the ollama models list working, the prompt call just hangs and eventually fails with NetworkError. I'm sure this is the call to Ollama for the api/chat and it is not allowing it because this call is from a different context or maybe server side fetch() doesn't recognize my self signed cert. I don't see any errors on the client side. Bolt terminal starts and there's an attach terminal log. Looks fine. But I get a failed to fetch() on the server in docker. I can call Ollama api/chat no problem using curl and my cert. So frustrating these CORS issues. I'm still hacking through it. Some calls seem local from the server and some calls seem to be from the browser.
Maybe I'm not understanding the WebAssembly or WebContainer or Vite as to why all calls to the LLM's aren't pub/sub?  Requiring only the server side to make outbound API calls and streaming the results back to the client reactively. Seems to be what's its trying to do, but something is blocking it and error is suppressed.

I think bolt can help with this issue in a few ways...

Fix inconsistencies between environment variables and values set in .env.local and .env files. If you look through issues and even replies on this issue you will see a lot of confusion and conflicting advice when compared to documentation (ie use .env in prod and not .env.local). This should be straight forward, set values in .env.local and then load up bolt, the default values when the client does not have any, should be what is set in the .env.local.
If some of the calls to ollama will come from the server then all calls to ollama should come from the server, do not split the responsibility between server and client.

If, for whatever reason, you cannot move all communication with ollama to server-side, at the very least, mention OLLAMA_ORIGINS in bolt documentation for ollama providers.
@Jeevanhm Despite not running ollama in the container the solution is the same. Set the environment variable for the env where the ollama process runs. Alternatively you can run your browser with no security to verify that this is your problem, but I wouldn't recommend doing this for any other reason. Example using chromium (on linux): chromium-browser --disable-web-security --user-data-dir=/tmp/chrome. If bolt and ollama work with browser security disabled you need to figure out how to set the value of OLLAMA_ORIGINS (for the ollama process) to the URL of your bolt instance.

Hi jumping into the conversation. like @stormbkk87 said, the provider code is spread across multiple files and its causing issues. I have added one fix which should allow you to use ollama by setting base url in env file. and its working for me. might need to test on other OS I saw one scenario where in windows the baseurl was have an extra trailing "/" added for no reason and causing issue .
to correct @stormbkk87, the server and client both needs base url as for different reasons.
client needs it to show the models list and server needs it to make the actual llm call. and server never throws cors error its the browser that throws it. so the cors issue I am seeing in the screenshot is from browser only issue.
the constants file is infact shared between server and clients. there was an issue with server was not able to properly reading the env value correctly,
this PR fixes that https://github.com/stackblitz-labs/bolt.diy/pull/816
so you should be able to get ollama models even without setting baseurl from settings window and from env file
and this PR refactors the provider code to be modular and maintained from one single place
https://github.com/stackblitz-labs/bolt.diy/pull/832

to correct @stormbkk87, the server and client both needs base url as for different reasons.
client needs it to show the models list and server needs it to make the actual llm call. and server never throws cors error its the browser that throws it. so the cors issue I am seeing in the screenshot is from browser only issue.

In my opinion bolt should be changed so that it does not require the client to have direct access to ollama.

we are exploring ways to eliminate the need of server altogether. cuz currently the server still getting the keys set in the cookies and if a user self host bolt technically he/she can snoop into a users api keys as he  has access to the server. so might be an option worth exploring. due to the cors issue its currently challenging. but if at all not possible then will use server to generate list for the client

@thecodacus my Ollama is in it's own docker container with environment vars OLLAMA_HOST=<IP_ADDRESS> OLLAMA_ORIGINS=* OLLAMA_FLASH_ATTENTION=1
I have tried running Bolt in it's own docker and pnpm run dev --host.
Pretty sure the issue is with the self signed cert and I just need to setup a test inside the server contexts to find it. I've had problems with fetch() in the past and switched to axios. Not sure if that's the case here though. Thanks for all the comments.

might be the case


DomainsDB does not accept CORS

[x] My submission is formatted according to the guidelines in the contributing guide
[ ] My addition is ordered alphabetically
[ ] My submission has a useful description
[ ] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[ ] I have searched the repository for any relevant issues or pull requests
[ ] Any category I am creating has the minimum requirement of 3 items
[ ] All changes have been squashed into a single commit

Good, thanks for contribution @bobziroll 😆


With 2 strike datepickers on one page selecting one will not close other if open

strike datepicker: with 2 or more datepickers on a page, clicking on one when another is open does not close the other datepicker

added a fix that will make this component behave as expected


How to mock fastlane actions in order to test Fastfile

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject

First: I'm not extremely proficient neither in Ruby nor in testing, so bear it with me.
My scenario: I'm trying to have tests for my Fastfile. We have many lanes and deploy 30 iOS apps using this Fastfile, it is growing complex each time... It's 900 lines long and takes care of creating new apps, submitting to testflight, submitting to the store, release approved apps, submitting to our testing environment, etc. It accepts external parameters, download json's, and with all this functionality came the need to make tests for it in order to ensure our CI and CD does not break too often because of our fastfile.
What I have done so far: Searching for fastlane tests is really difficult, once you search google or even github issue for fastlane tests, the majority of results are for using fastlane to test iOS or android code. But, after some persistence, I've hit a jackpot when finding this file: fast_file_spec which is a huge help to know how to test my own fastfile.
My problem: Mocking. How do I mock fastlane actions? The aforementioned example uses fixtures that do not contain any fastlane action (it write to files).
Question Description

To illustrate my problem here is a snippet of code (modified), the idea is how to mock the produce command in the bottom.
lane :my_lane do |options|
    environment = "production"
    if not ["sandbox", "production"].include?(options[:env])
        UI.user_error!("Environment #{environment} not recognized, valid values are 'sandbox' and 'production'")
    else
        environment = options[:env]
    end

    list_targets = download_whitelabel_json(environment)

    app_id = options[:app_id]
    if app_id.to_s.empty?
        UI.warning "app_id not defined, doing for all apps"
    end

    app_to_create = // logic to get specific app from apps list

    if not apps_to_create.any?
        UI.user_error!("Specified app_id not found...")
    elsif apps_to_create.size > 1
        UI.user_error!("Only one app can be created at each time...")
    end

    apps_to_create.each_with_index do |app_to_create, index|

    developer_team_id = app_to_create["id1"]
    appstore_team_id = app_to_create["id2"]
    store_name = app_to_create["name"]
    bundle_id = app_to_create["id3"]

    if store_name.to_s.empty?
        UI.user_error!("App name cannot be nil...")
    end

    if defined?(developer_team_id).nil?
        UI.user_error!("dev team id cannot be nil")
    end

    if defined?(appstore_team_id).nil?
        UI.user_error!("appstore_team_id cannot be nil")
    end

    begin
        produce #how to mock this guy
    rescue => ex
        message = "Error creating #{app["app_name"]} with produce\n```Error: #{ex}```"
        stops_execution = index == target.size-1
        send_slack_message(message = message, stops_execution = stops_execution)
      end
end

@janpio,
First of all: Thank you for taking the time to answer
Second: Sorry for the late reply...
Actual reply: If I override produce on my Fastfile, that will affect real execution, won't it? Maybe I'm not seeing something here.
Finally, I've actually have other problems, the fast_file_spec I've linked previously has many dependencies to run the Fastfile by itself. One of them being the source code, apparently.
Again, my lack of ruby knowledge might be getting in the way. If you can point to any learning materials that can help me achieve my goal, I'd much appreciate that.

Actual reply: If I override produce on my Fastfile, that will affect real execution, won't it? Maybe I'm not seeing something here.

Yes, that would of course only be a temporary workaround for you to enable to write some "tests". But that is pretty much what actually mocking would do - remove the actual implementation and replace it with something else.
The file you linked to, https://github.com/fastlane/fastlane/blob/f32b007ff45e648b37b6c9c2037ac481f36b7780/fastlane/spec/fast_file_spec.rb, is actually the set of tests for https://github.com/fastlane/fastlane/blob/f32b007ff45e648b37b6c9c2037ac481f36b7780/fastlane/lib/fastlane/fast_file.rb.
The fastlane tests are written with rspec: https://blog.teamtreehouse.com/an-introduction-to-rspec
Looking as your Fastfile above again, you can probably "extract" most of the actual logic into individual methods that are imported from another file into the Fastfile - which then only calls one after another and finally calls produce. Then you can write normal tests for that file and its methods.
(Although I of course am not sure if this is the best way to test a Fastfile)


Unit tests and bug fix

PR for #59
Also added EvenlyIndentedLine which checks if the indentation is multiple of 2.

Coverage increased (+9.4%) to 89.911% when pulling 70b86152c024251e8feb406334573bed1f5d4a71 on 59 into ee44d353ec75ee766736f737aa483c901b1219f7 on master.

@rultor pls merge

@rultor pls merge

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor pls merge

@amihaiemil Done! FYI, the full log is here (took me 1min)


[VT-5] vit; cmd P priority

David Patrick on 2013-04-08T05:40:29Z says:
This cheeky feature request is to condense the current priority cmds into "Ph, Pm, Pl, Pn", for a couple of reasons.

for me, mnemonically, the letter "p" could well be  "project" as "priority".
Why not both p and P? It's almost easier to remember "upper-case P raises priority" (lower-case being project).

there rumor of user-definable priority, maybe not soon, but they might turn into P1, P4.. or P< tab >

the keyboard real-estate occupied by "h, m, l, n" is too valuable for setting a single  attribute!

Migrated metadata:
Created: 2013-04-08T05:40:29Z
Modified: 2014-02-09T01:14:58Z

Scott Kostyshak on 2013-06-23T18:24:43Z says:
I agree with the change to Ph, Pm, Pl, Pn.
I mildly disagree with overloading a key like you are suggesting for priority and project. For example, I often confuse "a" and "A" (one is annotate and one is add). Perhaps I just haven't used Vit long enough. In Vim, I feel the overloading is natural. "project" and "priority" are not related. In Vim, the pairs (a,A), (c,C), (w,W), (e,E), etc are intuitive. Eventually one runs out of keys, but this should be put off as long as possible in my opinion.
If we do go with (p,P) for (project,Priority) and other similar matchings, if we can think of more good mnemonics like you have, we should consider putting these directly into the documentation.

Scott Kostyshak on 2013-07-07T02:05:57Z says:
Does anyone have an opinion on this? I'm still hesitant to overload "p" but I will be fine with it if we get a "+1" from somebody. The way I would use to remember it is that both "p" and "P" would require two-key combinations: "p-h" and "shift+p".

David Patrick on 2013-07-07T14:56:17Z says:
Scott Kostyshak wrote:

Does anyone have an opinion on this?

yup; go for it! :)

I'm still hesitant to overload "p" but I will be fine with it if we get a "+1" from somebody.

+1

The way I would use to remember it is that both "p" and "P" would require two-key combinations: "p-h" and "shift+p".

I sort of think of is like the SHIFT key is for upper-case, SHIFT-P is for higher priority (or "shifted" priority) but I don't think it will be too confusing in normal usage.

Scott Kostyshak on 2013-08-14T07:50:46Z says:
OK I'll work on this. If someone does not like this change, they can just use shortcuts (to disable 'P' and to add back the functionality of 'h', 'm', 'l', 'n'.

Scott Kostyshak on 2013-09-27T23:14:37Z says:
This should go into VIT 1.2.

Scott Kostyshak on 2013-09-28T15:53:55Z says:
Done at 1b0038d4.


One more BSOD on monitoring NTFS driver

Hi Pavel,
Please see the crash dump result screen shot.
I will keep the dump file for the moment If any further check on the dump file needed, just let me know.

Regards,
Ethan

You can't monitor the NTFS driver with this technique on Windows 8+ because it's protected by PatchGuard.

I'll take a look anyway

Thanks again.


Typecasting to type

typecasted the type so the isConfidential() function works as intended.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Thanks! 👍


[Feature Request] Split mode component

This is really just a feature request, I wish to have a component to show if nog is splitting horizontally or vertically. That would greatly help.

I have a version that is part of a WIP pull request that can be seen here. It's not compatible with the current nog branches but conceptually it's the same thing: it indicates what split mode you're in.

Two things to note:

I implemented the component to show vertical/horizontal/fullscreen. I mostly did it for the fullscreen indicator because I actually confused myself enough times that I thought it would be nice to show. So, when a window is fullscreened it shows the fullscreen icon (because splits aren't really important when you're fullscreened) and otherwise it shows the current split mode. My vote would be to have something like that.

I had hardcoded it to emojis 🔳, ↔, ↕ but I suspect it should be something that people would want configurable? Little technical, but not sure if it's worth adding another spot where the bar is locking the config to see what the configured values are; maybe it should be something that is just cached in the component and refreshed on hotreload?

This issue actually shows a different problem. We should probably expose some metadata to the user in the config files, so they could create such components themselves or even using popups.

This issue actually shows a different problem too. We should probably expose some metadata to the user in the config files, so they could create such components themselves or even using popups.

Yes. Actually, I think there should be an API where user can control nogs, like the onclick function of a component can be used to launch something, show/hide Windows, switch workspace, etc.

@takase1121
I currently have two functions implemented:

nog_get_split_direction
nog_do

nog_get_split_direction
Returns the split direction of the focused window.
Possible values:

Horizontal
Vertical
empty string

nog_do
Basically simulates a keybinding activation.
usage
no_do(change_workspace(10));

Can you list all of the things you need included in the core lib?

maybe

get the state of window (hidden/unmanaged),

I dunno, maybe some other people could think of more things to add

show whether a workspace is fullscreened or not

I'm actually struggling to think of other things.. like, maybe config settings like your current gaps? I don't know how useful that'd be.

@takase1121 the newest release now contains a split_direction component that does what you want.


Added LimelightLib

I think this might be a bit out of the scope of this being event focused. I'm happy to take this for the new rewrite

I think the issue is that if a CSA provides a newer limelight image that needs a newer LimelightLib, teams would be stuck.

The removal of the JSON in the latest LL image is what I was thinking of


Strapi v.3.6.5 - draft content not found

Hi - I'm from a backend development background - so this issue is possibly due to lacking javascript knowledge.
Having installed the preview plugin - this works for cloning, and getting published content - via the preview API using a url like this:
/preview-content/custom-pages/2
However - for draft content - we get a 404 and the message: "Preview not found for given content type and Id".
Trying to debug the plugin - I can see that that line 131 in preview.js is returning null:

However I am unable to identify why this is.
Any help much appreciated!

hi - resolved this by creating a custom controller - and then in the \node_modules\strapi\lib\core-api\service\index.js - I added method:
const getFetchParamsPreview = (params = {}) => {
 return {
   _publicationState: DP_PUB_STATE_PREVIEW,
   ...params,
   _limit: getLimitParam(params),
 };
};

And in \node_modules\strapi\lib\core-api\service\collection-type.js
findOnePreview(params, populate) {
      return strapi.entityService.findOne(
        { params: getFetchParamsPreview(params), populate },
        { model: modelName }
      );
    },

This can probably be done in a better way ... but us this something that is missing in v3.6.5 in order for the preview plugin to work - ?


Wrong IPv6 subnet

Sorry for such a flimsy report, but I was just reading through the code when I spotted this.
In https://github.com/gaomd/docker-ikev2-vpn-server/blob/master/bin/start-vpn#L32
shouldn't it say fd6a:6ce3:c8d8:7caa::/64 instead of 2a00:1450:400c:c05::/64 ?
The former is the prefix setup in ipsec.conf

Thank you so much for the report. The problem was introduced from #20, where I made a bad review.
I'll fix it ASAP, luckily the recently added IPv6 features were not tagged and pushed to Docker registry yet.


Changes to workflow semaphore seems not to trigger reload semaphore state in workflow-controller

I'm not sure this is a bug or not but I got some feedback when asking on stackoverflow to submit an issue.
I'm learning about semaphores in the Argo project workflows to avoid concurrent workflows using the same resource.
My use case is that I have several external resources which only one workflow can use one at a time. So far so good, but sometimes the resource needs some maintenance and during that period I don't want to Argo to start any workflow.
This is my example semaphore configMap:
sempaphore
apiVersion: v1
kind: ConfigMap
metadata:
  name: testsystem-sync
data:
  darksow: "1"

This is my example workflow using the claiming the semaphore:
apiVersion: argoproj.io/v1alpha1
kind: Workflow                  # new type of k8s spec
metadata:
  generateName: counter-    # name of the workflow spec
  Labels:
spec:
  serviceAccountName: fke-sa
  entrypoint: counter          # invoke the whalesay template
  synchronization:
    semaphore:
      configMapKeyRef:
        name: testsystem-sync
        key: darksow
  templates:
  - name: counter              # name of the template
    container:
      image: alpine
      command: ["/bin/sh"]
      args: ["-c", "n=0; while [ $n -lt 60 ]; do echo $n; sleep 1; n=$((n+1));done" ]
      resources:                # limit the resources
        limits:
          memory: 32Mi
          cpu: 100m

When submit some of these Argo will only execute one at the time as expected. Let's say I want to do some maintenance on the resource I would like to block argo from starting any new workflow so I do a:
kubectl edit configmap ...

and set the semphore to value 0 (in the future I would do that programatically through Kube-api but this will do for testing). So I then submit a new job but Argo start the workflow even if I changed the configmap.
If I cycle the workflow pod it sometimes work and when I restore the configmap again with the value 1 it wont start any workflow until I cycle the workflow-controller pod again.
So it seems that the argo workflow-controller pod does not reload the semaphore state when the configmap changes.
Related question on stackoverflow is here
Kubernetes 1.17
Argo 2.11.6

It is working as expected. The controller has a 20 minutes  Workflow resync period if there is no change in workflows.  All pending workflows will be picked up in 20 minutes or if any user creates/updates new workflows.

I discussed it with Team. We are going to improve the user experience in this scenario to process the workflow immediately once the config map updated. I am going to work on this.

@sarabala1979
You can copy what Rollouts does with Istio VirtualServices. We run a VirtualService informer which indexes on VirtualServices referenced by a Rollout. When a VirtualService is modified, we immediately enqueue the referencing Rollout.
https://github.com/argoproj/argo-rollouts/blob/df1ac603aad887cc018b43aff62226bbc26a2d17/rollout/controller.go#L238-L243

That's really great news and Argo will support our use case better then :smiley:
Out use case is that we have workflows connected to test systems for long running system level software/integration test on embedded devices. Occasionally we need to perform maintenance on the test systems and need  a way to block Argo from starting workflows during that time. So we change the semaphore value manually (through kubeapi) to "0" which I got to work now as well. When semaphore value is restored to "1" Argo should start new workflows as soon as possible so great news again.
Thanks for your quick feedback and help.


Win 2008 support

The project doesn't seem to support Windows 2008.
This work item was migrated from CodePlex
CodePlex work item ID: '3270'
Assigned to: 'tfabraham'
Vote count: '1'

[tfabraham@10/21/2008]
Would you mind posting some details on what errors you are seeing?  Thanks.

[beriz@10/27/2008]
I got the following error "the method setWinVer.6.0 doesn't exist"
I solved the issue by manually adding the following in the BizTalkDeploymentInclude.nant file

[UnknownUser@11/3/2008]

[UnknownUser@11/3/2008]
Resolved with changeset 16764.

[UnknownUser@5/16/2013]


support for cuda 121

Description
I use pytorch, have cuda 121 installed on my computer and cannot easily downgrade.
My computer is running archlinux x64.
How could I get djl to use the gpu?
Will this change the current api? How?
it shouldn't change the current api
Who will benefit from this enhancement?
everyone running the latest cuda version
References

list reference and related literature
list known implementations

I didn't try it myself, but you can try to set environment variable or system properties:
export PYTORCH_FLAVOR=cu117-precxx11

or
System.setProperty("PYTORCH_FLAVOR", "cu117-precxx11");

I8 gave it a try but got:
16:41:59.005 [pool-3-thread-1] WARN ai.djl.pytorch.jni.LibUtils - No matching cuda flavor for linux-x86_64 found: cu121.
16:41:59.007 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libc10.so
16:41:59.007 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libgomp-52f2fd74.so.1
16:41:59.008 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libtorch_cpu.so
16:41:59.173 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libtorch.so
16:41:59.173 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/0.21.0-libdjl_torch.so

I8 gave it a try but got:
16:41:59.005 [pool-3-thread-1] WARN ai.djl.pytorch.jni.LibUtils - No matching cuda flavor for linux-x86_64 found: cu121.
16:41:59.007 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libc10.so
16:41:59.007 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libgomp-52f2fd74.so.1
16:41:59.008 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libtorch_cpu.so
16:41:59.173 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/libtorch.so
16:41:59.173 [pool-3-thread-1] DEBUG ai.djl.pytorch.jni.LibUtils - Loading native library: ~/.djl.ai/pytorch/1.13.1-cpu-linux-x86_64/0.21.0-libdjl_torch.so

@larochef
You can try it again with 0.22.0-SNAPSHOT release.

I tested it and  it worked, thx


Bug report, @ApiModel.value property can't contain dot(.) char?

my springfox version:
        <springfox.version>2.9.2</springfox.version>
        <swagger.version>1.5.22</swagger.version>

Model:
@ApiModel("doctorschedule.ScheduleLevel")
@Data
class ScheduleLevel {
    private Long id;
    private String name;
    private String code;
    private int defaultQueueSize;
    private int defaultFee;
    private boolean enabled;
}

Example Value from Swagger UI:
[
  null
]

If I change the model name to doctorschedule-ScheduleLevel which doesn't contain dot(.), it works.

BTW, is there a way to configure model name prefix? or provide my custom model name generator?


More optional history logging

This adds additional optional logging. This is useful when the Arnoldi-method fails.
It is e.g. quite easy to investigate what is going wrong in #93 with this:
@load "myerror.jld2" W
local history;
for k=1:30
    decomp, history = partialschur(W, nev=3, which=LR(), tol=1e-13, history_level=DetailedHistory);
    λ, V = partialeigen(decomp);
    if (abs(maximum(real(λ)) - maximum(real(eigvals(W)))) > 1e-6)
        break;
   end
end

The eigenvalues that should be computed are
julia> e=eigvals(W); II=sortperm(-real(e)); e[II[1:3]]
3-element Array{Complex{Float64},1}:
  0.15368465993022115 + 0.0im
 9.871248233586328e-9 + 1.0327891056793643e-8im
 9.871248233586328e-9 - 1.0327891056793643e-8im

It seems the two last eigenvalues are incorrectly locked in the first restart:
julia> history.ritzval_history[1][history.ritzval_lock_history[1]]
2-element Array{Complex{Float64},1}:
 3.5489275362237446e-7 + 0.00012663869814285724im
 3.5489275362237446e-7 - 0.00012663869814285724im

The PR is not quite ready yet. Putting it here for comments. What should be collected?

Thanks! I will try it probably tomorrow :)

That did not happen.
I think I'll close this since it out of date, but can come back to it if necessary at some point.


Would the be a chance to include time in the log messages?

Centipede has very informative log messages, e.g.:
centipede.cc:177] [74000000] new-feature: ft: 16886 cov: 717 cnt: 717 df: 17 cmp: 16152 path: 0 pair: 0 corp: 10002/10061 max/avg<PHONE_NUMBER>1 d202/f0 exec/s: 1111.6 mb: 823

Would there be any chance that it could also include how long it has been running?
I would really appreciate that, as it could largely help us to easily identify if Centipede has terminated earlier than expected during evaluation.
Thanks : )

Here is a quick example for libFuzzer, hope it could help:
#870850783: cov: 699 ft: 3763 corp: 1674 exec/s 10057 oom/timeout/crash: 0/0/0 time: 82511s job: 423 dft_time: 0

It shows time: 82511s, implying that it has been running for ~23 hours.
I reckon this feature will also benefit other users, as many other fuzzers (e.g., honggfuzz, eclipser) print similar time information as well : )

This is certainly possible. Not to say that that wouldn't be useful, or that we aren't going to add that, but aren't the recently enabled log timestamps at least partially helpful in that regard:
I0919 04:25:55.872262     188 centipede.cc:181] [9000] new-feature: ft: 879 cov: 31 cnt: 31 df: 0 cmp: 668 path: 0 pair: 180 corp: 342/342 fr: 0 max/avg 531 30 d0/f0 exec/s: 0 mb: 265
I0919 04:25:55.893925     188 centipede.cc:181] [10000] new-feature: ft: 883 cov: 31 cnt: 31 df: 0 cmp: 672 path: 0 pair: 180 corp: 344/344 fr: 0 max/avg 531 30 d0/f0 exec/s: 0 mb: 265
I0919 04:25:55.894154     188 centipede.cc:181] [10000] end-fuzz: ft: 883 cov: 31 cnt: 31 df: 0 cmp: 672 path: 0 pair: 180 corp: 344/344 fr: 0 max/avg 531 30 d0/f0 exec/s: 0 mb: 265
?

Ah yes, that is great.
I just realised that I was not using the latest version of Centipede in the evaluation, hence did not notice this new feature.
Testing the latest version with the benchmarks now.
Thanks!


feat: remove helm & java install from ci pipeline

Description
This pull request changes the following:

remove helm & java install from ci pipeline

Related Issues

Closes #161

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: