Go to today or specific date

It is possible to jump to today's date or go to specific date (e.g by click of a button)?

Yap, with {compact_calendar_view}.setCurrentDate(date)


Action Mailer preview_path warning

Is it really necessary to output a warning: 'Action Mailer preview_path is not the RSpec default.' when the preview_path is changed to something different than its default value?

This is being removed, is part of a PR that will be submitted later today

Great, thanks! :smile:

Closing per #1327


Implement query index delete

This pull request delivers functionality that will allow a user to delete an index that was previously created.

@mikerhodes , where you get a chance can you take a look at this PR?  Thanks.

lgtm, +1.


Added fibonacci_for_big_numbers.cpp

Update readme and contributors list :+1:

Hello, Anyone with write access, please review the PR and if all good merge it.

I have already updated the contributors list and there is no need to update the readme as it is only the another version of already existed solution.


How to use swift 2.3

i getting error from swift 2.3

You need use swift 3 because this project updated to swift 3
Pada tanggal 14 Feb 2017 3.25 PM, "Ilham Malik Ibrahim" <
<EMAIL_ADDRESS>menulis:

i getting error from swift 2.3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/balitax/AutoCompleteAddressMaps/issues/2, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABa9ppyB5GeFZydKKmuIB6zwpxKeidPuks5rcWT0gaJpZM4MAL3V
.


Additional package managers

While it's true that Homebrew is by far the most popular package manager on Mac, It would be great to be able to install Ollama via MacPorts.
This gives people maximum freedom in installing Ollama the way they want to, for a lot of people including me it isn't really acceptable to run an electron GUI application that needs to be granted root privileges to install a CLI.
I understand wanting to make the barrier entry as low as possible for the maximum amount of people, but there should always be a secondary option to just use a package manager of your choice to install a CLI.

The homebrew package is provided by community members, as are the packagings for various linux distribution. I think MacPorts will need similar community initiative.

Will close this for https://github.com/ollama/ollama/issues/3067


worked on setting icon button

PR Title
worked in setting icon button
The purpose of this Pull Request is to fix #46
Description
worked in setting icon button
How you solved
worked in setting icon button
Screenshots

Checklist

[yes ] I have Made this contribution as per the CONTRIBUTING guide in this repo
[yes ] I have tested in local Environment.
[yes ] I have made the fix as per issue converstaion
[yes ] I have starred the repository ⭐

@jsvigneshkanna  can you please review

Thanks, @zainbinfurqan looks good
Please star this repo and look for future issues and feature request


Fix convention and improve stability of NormalCost

Similar to https://github.com/colmap/colmap/pull/2601, I revert the computation to inverse + llt. The only thing to fix in this PR is the bug for applying the L matrix to the residuals.


Replacing function calls with pcode

I'm looking to replace calls to soft library functions with the equivalent pcode. If I understand correctly this is possible with callfixup in the cspec file but I cannot seem to get it to work correctly. Here is an example of what I have tried:
<callfixup name="dpadd">
  <pcode>
    <input name="dp1"/>
    <output name="dp"/>
    <input name="dp2"/>
    <body><![CDATA[
      dp = dp1 f+ dp2;
      ]]></body>
  </pcode>
</callfixup>

I would get rid of the input/output, and use the actual locations used as inputs and outputs directly.
Normally input/output is used to supply pcode to pcode userops.
Also you would need to assign the callfixup to the function by hand (edit function), unless you add

The above only defines a call fixup named dpadd, it doesn't automatically assign it to functions named dpadd.

I would get rid of the input/output, and use the actual locations used as inputs and outputs directly.
Normally input/output is used to supply pcode to pcode userops.
Also you would need to assign the callfixup to the function by hand (edit function), unless you add

The above only defines a call fixup named dpadd, it doesn't automatically assign it to functions named dpadd.

I see. I initially had hard coded the locations and tried my example later. I had used an entry from one of the x86 cspecs. I wasn't aware that I had to manually assign it but I can just script it.
It would be pretty cool to have this done for the built in gcc functions for processors that can't add longs and such. Of course assuming they weren't inlined.

Setting the call-fixup in the function signature did what I was looking for. Thank you.

You could also try adding <target name="dpadd"/>  within <callfixup>. (Also for anyone else who comes across this issue.)


Remove the Saagie Usage Monitoring part from the saagie repository table technologies-community

Trello card: [#194] Remove the Saagie Usage Monitoring part from the saagie repository table technologies-community


End-to-End Question Answering System

I'd like to build an end-to-end QA system with a standard pipeline architecture: document retrieval, sentence retrieval, answer selection with neural networks.
For the answer selection part, as a baseline we'll integrate our S&M implementation or Hua's or Jinfeng's model.

@rosequ Once we get #136 merged in, start building a baseline QA system that does doc retrieval and then sentence retrieval. Start with the simplest sentence retrieval baseline, scoring based on idf term overlap.

With #146 - the speech front end - we have a functional e2e QA system. Not very accurate currently... but we can now start iterating.


Ctrl-click navigation should not suggest files in out folder

When using ctrl-click to navigate in .brs files - sometimes vscode shows two possibilities, one of which is in the out/.roku-deploy-staging folder. If I inadvertently click that one and edit, I lose the edit when I redeploy.
I recommend excluding the out folder from the ctrl-click navigation search.

The out folder can be excluded by including in .vscode/settings.json:
{
  "files.exclude": {
    "out": true,
    "search.exclude": {
        "files.watcherExclude": {
            "out": true
        }
    }
  }
}

I believe this only happens when running with the language server disabled, which falls back to the more primitive "scan every file in the workspace" mode. #391 fixes this issue by excluding the entire ${workspaceFolder}/out folder when in that mode.
There's nothing that can be done about when in language server mode, because the user specifically maintains the entire list of files in the files array, so if they don't want to see those files, just exclude them from the files array.


Add node package highlight.js

Project description
Highlight.js is a syntax highlighter written in JavaScript. It works in the browser as well as on the server. It can work with pretty much any markup, doesn’t depend on any other frameworks, and has automatic language detection.
Metadata

Homepage URL: https://highlightjs.readthedocs.io
Source URL: (npm)
License: BSD 3-Clause
Platforms: any

I tried to add it myself but on my (poor) connection after 4 hours pkgs/development/node-packages/generate.sh still hasn't finished, so it would be rather difficult for me to keep up with conflicts etc.

I tried to package this but it doesn't build against nodePackages_latest currently but only against nodePackages.

I don't know whether it is still recommended to open a PR for it, but I would need to know in time so I do not need to rebuild everything as soon as another node package gets merged :)


Encrypting works fine. What about decrypting?

I cannot find how to decrypt .env programattically using node. I would expect to find something like this in the documentation for someone using node to load secrets. But I cannot find this.
const dotenv = require('@dotenvx/dotenvx')
let opts = { path: '.env.production', keys: '.env.keys' }
// or
opts = { path: '.env.production', keys: process.env.key })

console.log(`Hello ${process.env.HELLO}`)

There is no way to do it from Node itself right?
this is how it is meant to be done? The method above is not supported for decryption?

let me put together a guide on using it inside node with the require. i haven't yet. give me some time. all the best.

while you're waiting, how did you find dotenvx ?

ok, actually this is approach is currently not supported. my mistake. patching up.

progress is happening here: https://github.com/dotenvx/dotenvx/pull/225

That was unbelievably fast.
I found dotenvx  while looking at dotenv and seeing this package recommended by you. I wanted to use the latest recommended practice for a new project and thought I might need encryption. At the moment I am using Railway and I could just copy paste secrets into their frontend which is supposed to inject them, however, for some reason Railway doesnt seem to be recognizing all my variables unless i include the .env in source control, so I decided to try leaving them in the source but encrypting.

In case anyone else reads this. To load encyrpted .env in node now, you just need
File: [./test.js]
const dotenv = require('@dotenvx/dotenvx').config({path: ".env.whatever" })
console.log(`Hello ${process.env.HELLO}`)

DOTENV_PRIVATE_KEY_PRODUCTION="k78u3x_private_key_u6kweo" node ./test.js

That was unbelievably fast.

You're welcome.

for some reason Railway doesnt seem to be recognizing all my variables unless i include the .env in source control

Railway has a gotcha in that they have a default .railwayignore file (hidden) that auto ignores a bunch of files - including .env files. Bad practice in my opinion. They should respect the .gitignore and the .dockerignore files.
here's a guide: https://dotenvx.com/docs/platforms/railway
# .railwayignore
.env.keys
!.env.production
``


Submit script

There was a syntax error in views.py which caused the CI to fail for python3, and as a result the web-link for the app is also not working.
Heroku has now been set to wait for CI to pass before auto-deploying.

@viveksb007 Fixed. Thank you


Types: Fix TransitionItemProps not recognising booleans

Regarding https://github.com/drcmda/react-spring/issues/275, after trying react-spring 6.1.0, the type issue on TransitionItemProps has yet to be resolved, causing an error in Typescript due to props type mismatch. (PR https://github.com/drcmda/react-spring/pull/270 doesn't seem to target this issue)
This PR adds the missing boolean type to the TransitionItemProps that gets used by the Transition component, as documented here
The live example of using TransitionItemProps as a boolean toggle to control mount/unmount component is demonstrated in the 2nd example in the above URL and is tested to be functioning this way.
Reference https://github.com/drcmda/react-spring/issues/26 again since this improves more on the Typescript support.

Thanks! Do we need more of these (since i guess it would also affect trail) for a patch release?

pushed a patch release


Add Presentation

As a Hermes user, I want to add a presentation to the system either by uploading a JSON  document containing the presentation details or by entering data field-by-field through interactive prompts. This will provide users with flexibility in how they input presentation information, accommodating different workflows and preferences.
Command Line Arguments
$ hermes presentations add [--input {add-presentation.json}] [--output {saved-presentation.json}]

Acceptance Criteria

If the user specifies the --input flag followed by a file name, the CLI will attempt to import the presentation fields from the specified JSON document.

If the --input argument is not supplied, the CLI will prompt the user for the presentation information field-by-field.

After collecting presentation information, the CLI should validate the data to ensure all required fields are provided and in the correct format.

If the provided data is valid, the CLI should add the presentation to the system and provide a success message.

if the provided data is invalid or incomplete, the CLI should display appropriate error messages and allow the user to correct the input.

If the user specifies the --output flag followed by a file name, the CLI should write the JSON output to the specified file.

Impact Personas

Alex - The Aspiring Speaker
Emily - The Social Media Savvy Speaker
Marcus - The Personal Brand Builder
Ryan - The Analytics Enthusiast
Sarah - The Busy Speaker

For now, we will only support uploading a presentation JSON file. Manually entry will be added at a later date.


denomailer broken since 1.42.2 deno release

Describe the bug
denomailer is broken since 1.42.2 deno release.
The denomailer e2e tests exec output this :
marco@marco-ubuntu:~/dev/open-source/denomailer$ deno test --unstable -A ./test/e2e/
⚠  The `--unstable` flag is deprecated and will be removed in Deno 2.0. Use granular `--unstable-*` flags instead.
Learn more at: https://docs.deno.com/runtime/manual/tools/unstable_flags
Check file:///home/marco/dev/open-source/denomailer/test/e2e/attachment.test.ts
Check file:///home/marco/dev/open-source/denomailer/test/e2e/basic.test.ts
error: TS2345 [ERROR]: Argument of type 'Conn<Addr>' is not assignable to parameter of type 'TcpConn'.
  Type 'Conn<Addr>' is missing the following properties from type 'TcpConn': setNoDelay, setKeepAlive
      const conn = await Deno.startTls(this.#connection.conn, {
                                       ~~~~~~~~~~~~~~~~~~~~~
    at file:///home/marco/dev/open-source/denomailer/client/basic/client.ts:339:40

To Reproduce
Set your deno version to 1.42.2 :
marco@marco-ubuntu:~/dev/open-source/denomailer$ deno upgrade --version 1.42.2
Downloading https://github.com/denoland/deno/releases/download/v1.42.2/deno-x86_64-unknown-linux-gnu.zip
Deno is upgrading to version 1.42.2
Archive:  /tmp/.tmp9PZqIv/deno.zip
  inflating: deno
Upgraded successfully
Release notes: https://github.com/denoland/deno/releases/tag/v1.42.2
Blog post: https://deno.com/blog/v1.42

Run the fake smtp server :
marco@marco-ubuntu:~/dev/open-source/denomailer$ docker run -d -p 1080:1080 -p 1025:1025 reachfive/fake-smtp-server
Unable to find image 'reachfive/fake-smtp-server:latest' locally
latest: Pulling from reachfive/fake-smtp-server
169185f82c45: Pull complete
53e52a67e355: Pull complete
fc2cb9a5e98e: Pull complete
67e7f49d4884: Pull complete
702661cf2202: Pull complete
Digest: sha256:4b6d2f1e24481527de1429f88db18a377252a5e9e95bc083fa3d77e402cdadc8
Status: Downloaded newer image for reachfive/fake-smtp-server:latest
f43b730f5e89b24c1bae2e9f41ca6d569ed2200a04b5fa113335f717a0840120

Run the e2e tests :
marco@marco-ubuntu:~/dev/open-source/denomailer$ deno test --unstable -A ./test/e2e/
⚠  The `--unstable` flag is deprecated and will be removed in Deno 2.0. Use granular `--unstable-*` flags instead.
Learn more at: https://docs.deno.com/runtime/manual/tools/unstable_flags
Check file:///home/marco/dev/open-source/denomailer/test/e2e/attachment.test.ts
Check file:///home/marco/dev/open-source/denomailer/test/e2e/basic.test.ts
error: TS2345 [ERROR]: Argument of type 'Conn<Addr>' is not assignable to parameter of type 'TcpConn'.
  Type 'Conn<Addr>' is missing the following properties from type 'TcpConn': setNoDelay, setKeepAlive
      const conn = await Deno.startTls(this.#connection.conn, {
                                       ~~~~~~~~~~~~~~~~~~~~~
    at file:///home/marco/dev/open-source/denomailer/client/basic/client.ts:339:40

Expected behavior
Works as expected with deno 1.42.1.
Set deno to 1.42.1 :
marco@marco-ubuntu:~/dev/open-source/denomailer$ deno upgrade --version 1.42.1
Downloading https://github.com/denoland/deno/releases/download/v1.42.1/deno-x86_64-unknown-linux-gnu.zip
Deno is upgrading to version 1.42.1
Archive:  /tmp/.tmp1kqjid/deno.zip
  inflating: deno
Upgraded successfully
Release notes: https://github.com/denoland/deno/releases/tag/v1.42.1
Blog post: https://deno.com/blog/v1.42

Then run the tests assuming fake-smtp-server docker image is running on background :
marco@marco-ubuntu:~/dev/open-source/denomailer$ deno test --unstable -A ./test/e2e/
⚠  The `--unstable` flag is deprecated and will be removed in Deno 2.0. Use granular `--unstable-*` flags instead.
Learn more at: https://docs.deno.com/runtime/manual/tools/unstable_flags
Check file:///home/marco/dev/open-source/denomailer/test/e2e/attachment.test.ts
Check file:///home/marco/dev/open-source/denomailer/test/e2e/basic.test.ts
running 3 tests from ./test/e2e/attachment.test.ts
test text attachment ... ok (383ms)
test binary attachment ... ok (2s)
test more text attachment ... ok (611ms)
running 4 tests from ./test/e2e/basic.test.ts
test simplest mail ... ok (323ms)
test simplest mail with pool ...⚠  The `Worker.deno.permissions` API was used with `--unstable` flag. The `--unstable` flag is deprecated and will be removed in Deno 2.0. Use granular `--unstable-worker-options` instead.
Learn more at: https://docs.deno.com/runtime/manual/tools/unstable_flags

------- post-test output -------
started idle
----- post-test output end -----
test simplest mail with pool ... ok (2s)
test subject ... ok (2s)
test html ... ok (480ms)

ok | 7 passed | 0 failed (8s)

If this package is not maintained anymore it should be archived ;)

Added a PR, it is just a type check failing.


When will Belgium be added to the list?

Just started an important project here. When will Belgium be added to the list?

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

ID: 2033900c-d18a-cdd3-313c-7efed2ceb4ec
Version Independent ID: 87b1f4a4-abb8-f3f6-241e-ca8b9b3d5015
Content: Kaizala regional availability
Content Source: Office365-Kaizala/regional-availability.md
Service: kaizala
GitHub Login: @chuckedmonson
Microsoft Alias: chucked

@mvanders - Thank you for this inquiry.
Please refer to the answer from @chuckedmonson  found in issue #126. According to him, "For Belize and other organizations currently outside the 28 launched markets, the Account Team can request the business desk team to get Kaizala Provisioned. We are working towards general availability for all markets in near future, without requiring special provision by the Account Team.
Originally posted by @chuckedmonson in https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/issues/126#issuecomment-466131373
Hope this answers your query.

@officedocsbot close


Major Release of 4.2 in work?

https://github.com/NotNotTech/Raylib-CsLo/issues/21#issue-1362467000
its only regarding if u plan to work on the major release of 4.2 :)

Yes, we are working on 4.2, there is a branch with all the changes.
I believe the release will be very soon.
We wanted to release a service update to 4.0.0 first (<IP_ADDRESS>), which is now done.

Very nice to hear, thanks!
BTW: right now, in the Version 4.0.2; Is it that that current version, you are already able to reference REVIEWED/UPDATED functions from raylib automatically?? like if ur lib is already referencing raylib 4.2, will the end-user of your 4.0.2 be able to use ACTUALLY a function from the 4.2 from raylib, or does ur 4.0.2 reference sill only the older function from raylib 4.0.2
Short example:
YourRaylib(4.0.2) --------> references: (Raylib 4.2)
User -------> calls: "Raylib_cs.DrawPixel(blaaablaaa)" -------->internally your lib calls into which version of raylib?
I ask this, because it woule be cool without any touch of code that your project will ALWAYS reference the up to date raylib library just by recompiling the entire project, am I right?

I ask this, because it woule be cool without any touch of code that your project will ALWAYS reference the up to date raylib library just by recompiling the entire project, am I right?

You mean using the raylib parser? I've looked at it and it will need some hardcoded fixes to fit C# code style. Example: Color static fields instead of using preprocessor directives.

@graphnode I am disappointed at you! SHAME SHAME!
...
Joke :D.
Dont worry, was just a question, but as the saying goes, "It would have been to good to be true" xD
Wish you good success tho :)

@graphnode Mate sry if i am annoying here, I am just burning to know if you are currently updating to 4.2 raylib^^
Would be cool to know, cheers

Please see the 4.2 branch if you would like to try out the new release.


Bump organization management service version and license.txt

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7911347970

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7911347970
Status: failure

Failing only the RegistryMountTestCase.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7912636802

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7912636802
Status: failure


Invalid Go build tag generated in zz_generated.openapi.go

Bug Report

What did you do?
operator-sdk new app-operator --repo github.com/example-inc/app-operator
cd app-operator
operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService
head pkg/apis/app/v1alpha1/zz_generated.openapi.go

What did you expect to see?
A valid Go build tag. For example, the following build tag was generated by version v0.8.2 of operator-sdk:
// +build !ignore_autogenerated

What did you see instead? Under which circumstances?
The following build tag:
// +build !

AFAIK the above isn't a valid build tag, which may have negative effects on the way the project is built.

Go
Possible Solution

Additional context
Add any other context about the problem here.

I can confirm that I was able to reproduce this. It's strange because it doesn't look like our kube-openapi dependency changed between 0.8.2 and 0.9.0
@estroz Any idea what might have changed?

@johananl @joelanford when the kube-openapi generator was directly imported, default arguments, which contains a default build tag, weren't used. #1757 uses default args to generate the build tag.


FA operation ignored error message

An FA operation ignored error message is present.  Should not execute the commands that cause this, or the error should be eaten.
ERROR:ibapi.wrapper:ERROR 125 321 Error validating request.-'bW' : cause - Incorrect generic tick list of 292,456,225,232,619,165,318,293,294,233,375,295,595,236,236,104,411,106,100,105,101.  Legal ones for (STK) are: 100(Option Volume),101(Option Open Interest),105(Average Opt Volume),106(impvolat),165(Misc. Stats),221/220(Creditman Mark Price),225(Auction),232/221(Pl Price),233(RTVolume),236(inventory),258/47(Fundamentals),293(TradeCount),294(TradeRate),295(VolumeRate),318(LastRTHTrade),375(RTTrdVolume),411(rthistvol),456/59(IBDividends),460(Bond Factor Multiplier),576(EtfNavBidAsk(navbidask)),577(EtfNavLast(navlast)),578(EtfNavClose(navclose)),586(IPOHLMPRC),587(Pl Price Delayed),588(Futures Open Interest),595(Short-Term Volume X Mins),614(EtfNavMisc(high/low)),619(Creditman Slow Mark Price),623(EtfFrozenNavLast(fznavlast))

This problem was originally reported by @rbasralian.
As far as I can tell, this is probably user error.  The codes in the list that are not present in the available options are:

104 - 30 day hist vol
292 - News
See the GenericTickType enum and https://interactivebrokers.github.io/tws-api/tick_types.html for details.

Possibly request_market_data was called with an invalid combination of RegisteredContract and GenericTickType.


chore(deps): replace rouge with js-rouge

To make onboarding easier into certain systems I use, It would be helpful to have pacakges come from npm,.
I have cloned the github repo for rouge, upped the version and pushed to npm, this should hopefully have no effect on most people using this package but make it easier to use in some cases.

Thanks @QuarkNerd! Would you mind moving the type annotations into your package as well? I started a ts rewrite of rouge a few months ago: https://github.com/mldangelo/rouge you are free to copy from that as well if you’d like (but no obligation).
If you’re open to it, we could move js-rouge into the promptfoo npm and/or GitHub orgs too.
Thanks!

I can merge your branch into mine, but I'm happy to let promptfoo take control of the GitHub/npm since I don't really know much about rouge. Would it be easier for you to take control and then make your changes as you see fit? I'm happy either way.

@QuarkNerd can you give mdangelo permissions to modify your npm package?

I've sent you a request

Thanks, @QuarkNerd for suggesting this and driving it!  I switched it over to a ts fork https://github.com/promptfoo/rouge hosted at promptfoo! Happy to add you as a contributor to the ts fork if you would like to make other improvements.


Use with ControlzEx 4.2.1

How can I use the Nugeht while also using ControlzEx 4.2.1? Cause it requires a lower Version

Hi @jogibear9988 ,
which verison of MahApps do you use?
Happy coding,
Tim

1.6.5,

And some lib I use Reference 4.xx

then you will need v2.0.0 alpha

when will it be production ready?

Hi @jogibear9988 ,
it is a free time project maintained by almost only @punker76 . So I think there is no fixed release date, but we are close to release v2.0 as far as I know. I updated all my projects already, because the prerelease is more stable and less buggy than the current v1.6.5 (from my point of view).
Happy coding,
Tim

@jogibear9988 I'm working on it, sorry for the delay...

@punker76
First, congratulations by the project, it is amazing!
What's missing for realease the v2.0.0?

One large missing part is my work on the generic ThemeManger and RuntimeThemeGenerator in ControlzEx. Can't say much about other missing parts.

@batzen
Thanks for the informations


ci: update PR labeler

What
ci: update PR labeler

Codecov Report

Merging #2794 (75174c3) into develop (6fb09e5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop   #2794   +/-   ##
=======================================
  Coverage     7.06%   7.06%
=======================================
  Files          219     219
  Lines        10849   10849
=======================================
  Hits           766     766
  Misses       10083   10083

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Use config environments

We need to use config environments feature and have 2 default set of configs - dev (debug) and prod. Selecting one should be done through YII_ENV environmental variable (or .env).
Same should be applied to all templates and demo apps.

See https://github.com/yiisoft/config/pull/64

Also need environment "test"

We should also get YII_ENV through getenv and not trough $_ENV since it's not populated by default. See https://mattallan.me/posts/how-php-environment-variables-actually-work/

Looks like there is a problem with getenv and nginx fastcgi_param

Yeah. May consider configuring it to fill getenv() or using https://github.com/symfony/dotenv.


Use released versions of the kustomization yamls for the dependent services

redis: v1.0.0
psql: v1.5.0
minio: v3.0.13

we should do this when we support k8s V1.21+


[$250] Approval popup for a report with hold expense has X Close option it.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.67-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1714419087794969
Action Performed:

Create a couple of expenses (e.g. Submit expense)
Once your report has more than one expense, click on the report
Choose one of the expenses on the report
In the transaction thread, tap the three vertical dots and hold an expense
In the report, click approve or pay
See the partial pay modal, asking if you want to pay everything or just what’s not on hold

Expected Result:
The modal should not have an X close option in the top right hand corner.
Actual Result:
The modal has an X close option in the top right hand corner.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[X] Android: Native
[X] Android: mWeb Chrome
[X] iOS: Native
[X] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[X] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/b5cc216c-6fed-4b2e-8600-ceed1b944c88

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01dc4b880c2fe9c645
Upwork Job ID:<PHONE_NUMBER>801417728
Last Price Increase: 2024-04-30

Proposal
Please re-state the problem that we are trying to solve in this issue.
Approval popup for a report with hold expense have X in it.
What is the root cause of that problem?
We render the close button in `DecisionModal without check for screensize
https://github.com/Expensify/App/blob/49db1492b770adc57301c78026dd4790d4e6bb01/src/components/DecisionModal.tsx#L63-L75
What changes do you think we should make in order to solve the problem?
We will add logic to only render the close button if the modal is presented on a small screen.
We will use  isSmallScreenWidth for the check

♻ Reviewing proposals.

Expected result:

The modal should not have an X close option in the top right hand corner.

Given the expected result of this issue, can we get a 2nd opinion from the @Expensify/design team confirming the expected result change ? Including how this should look on both wide and narrow layout devices.
I want to confirm if we want the X (Close) button completely gone from both wide and narrow layout devices so I can move forward with selecting one of the proposals based on the confirmation of the expected result. Thank you!

Are we sure this isn't expected behavior? I think this is how our alert modals work. And given that you have no other way to exit the modal, this seems right. cc @Expensify/design @trjExpensify @JmillsExpensify for a second opinion though.
Though one bug I am spotting - looks like we are using the wrong button sizes for this, shouldn't they be 52px tall (large buttons)?

Doesn't look like it:

You can click outside of the modal to cancel it as well.

Yeah, I prefer it without the X. Most have a way of closing it via the button anyways. So I think we should remove the X

Thanks @Expensify/design for chiming in!

[!note]
I checked and the DecisionModal is only used once within the ProcessMoneyReportHoldMenu component.

Therefore, the consensus so far is that we should completely remove the X (Close) button from the DecisionModal for both wide and narrow layout devices, since click / tap outside the modal is enough to close it.
Do we agree 👍 or 👎.

Sounds like that's the plan, yup. No more close "x" in our modals!

@trjExpensify those are good examples but I guess they always include some kind of cancel/close button as a wider button. In the Hold case, you don't have a cancel/close option - you get two buttons and you need to pick one of them. But that being said, you can easily click outside of the modal or hit escape, so I think it's fine to omit the close icon.

Based on the latest discussion, we concluded here that we should completely remove the X (Close) button from the DecisionModal.
Given the context, @Krishna2323's proposal looks good to me. The root cause was identified first, and they were also first to suggest removing the X button in their solution (based on edits timeline).
🎀👀🎀 C+ reviewed

@cristipaval if offline til Tues 7 May for Orthodox Easter so will review when he's back

@cristipaval bump for review today pls thanks!

I'm good with @Krishna2323 solution. But this issue is a super, super simple one, and I'm thinking of making it a 125$. Do we all agree? 👀

@Krishna2323 is there an ETA for the draft PR thanks

⚠ Automation failed: This was deployed to production today here, therefore should be [HOLD for Payment 2024-05-29] and have Awaiting Payment label.
cc @laurenreidexpensify @cristipaval

Payment Summary:

C+ @Krishna2323 $125 issued in upwork
Contributor @ikevin127 $125 issued in upwork


Updating the GitHub actions workflow to check CodeCov SHAs and commit hash of action

This adds checks in for the bash script that's pulled down from CodeCov and pins the JamesIves/github-pages-deploy-action to a fixed commit hash.

Codecov Report

Merging #65 (e74c1bc) into devel (b873182) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            devel      #65   +/-   ##
=======================================
  Coverage   52.93%   52.93%
=======================================
  Files         105      105
  Lines        6942     6942
=======================================
  Hits         3675     3675
  Misses       3267     3267

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b873182...e74c1bc. Read the comment docs.


Pages Hidden From Navigation

I'd like to make a page full of my react components to use to test variations and such but I don't want it to show up in the sidebar. Is there a way to have a page with a route but hidden from navigation?

Answered my own question! Looks like there's a hideFromMenu prop for pages.
https://github.com/interactivethings/catalog/blob/aa19e78d6f1a2b02efa0bd8fdc1e29492a622e9e/src/components/Menu/Menu.js#L93
Wonder if this should be documented?

I would accept a PR at https://github.com/interactivethings/catalog-docs/ 😉

When you're right, you're right! Added at interactivethings/catalog-docs#6


Scrub dotnet 6 references

Fix a few places where we were still referencing .NET 6 after updating to .NET 8.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.84%. Comparing base (ca29302) to head (8e09d4a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #775      +/-   ##
==========================================
- Coverage   70.13%   66.84%   -3.29%
==========================================
  Files         277      277
  Lines        8651     8651
  Branches     1006     1006
==========================================
- Hits         6067     5783     -284
- Misses       2065     2357     +292
+ Partials      519      511       -8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


⚠ Jenkins Plugins Artifactory has degraded performance

In 4c7b8f8, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1661 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 931bcb8.


Deduplicate SoC/arch-specific task switching related code

Github handles moved files a bit funnily but I can't do much about that. This PR extract the architecture-common parts out of the old timer_*.rs files, moves those timer files into a folder. These files still do more than just timer-related setup and interrupt handling, but I didn't actually want to change how the big picture looks.
I un-public-ed some modules that were hidden. I'm not sure if some dependency relied on these modules being public, but hidden docs usually indicate that is not an intended use.

Looks good! I also meant to do some cleanup there but never got to it
There are however some unused imports - e.g.
warning: unused imports: `Alarm`, `Periodic`, `SystemTimer`, `Target`, `riscv`, `self`
 --> esp-wifi\src\timer\timer_esp32c3.rs:5:23
  |
5 |         peripherals::{self, Interrupt},
  |                       ^^^^
6 |         prelude::*,
7 |         riscv,
  |         ^^^^^
8 |         systimer::{Alarm, Periodic, SystemTimer, Target},
  |                    ^^^^^  ^^^^^^^^  ^^^^^^^^^^^  ^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: unused import: `binary`
 --> esp-wifi\src\timer\riscv.rs:6:5
  |
6 |     binary,
  |     ^^^^^^

warning: unused imports: `TIMG1`, `Timer0`, `Timer`
 --> esp-wifi\src\timer\timer_esp32.rs:4:25
  |
4 |     peripherals::{self, TIMG1},
  |                         ^^^^^
5 |     timer::{Timer, Timer0},
  |             ^^^^^  ^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default


Create GUI

This is obviously a large issue, but I thought it would be worth having this pinned.
Here is what the old program looks like:

@jonemurray states that he would like the new program to look the same (though maybe we can rejig things a little so that e.g. device settings are in a separate window)
Aha! Link: https://imperial-college-ict.aha.io/requirements/RSE-122-19

TODO: Break this up


Ankaios server should warn if port already used

Current Behavior
If the Ankaios server port is already in use by another application, the Ankaios server starts up normally and gives not indication that it is not working properly.
Expected Behavior
The Ankaios server should either crash or at least print a warning, if it is not possible to open the port for the communication with the agents.
Steps to Reproduce

Start some server listening to port 25551, e.g. python -m http.server 25551
Start the ank-server binary
Start the ank-agent binary

Context (Environment)
Tested on Arch Linux.
Logs
Ankaios server
[2023-11-14T06:44:06Z INFO  ank_server::ankaios_server] Starting...
[2023-11-14T06:44:06Z INFO  ank_server::ankaios_server::update_state] The update has 5 new or updated workloads, 0 workloads to delete
[2023-11-14T06:44:06Z INFO  grpc::execution_command_proxy] Agent agent_A not found, workloads not sent. Waiting for agent to connect.
[2023-11-14T06:44:06Z INFO  grpc::execution_command_proxy] Agent agent_B not found, workloads not sent. Waiting for agent to connect.

Ankaios agent
[2023-11-14T06:44:31Z INFO  ank_agent::agent_manager] Starting ...
[2023-11-14T06:44:31Z WARN  grpc::client] Connection to server interrupted. Error: Connection interrupted: 'status: Unknown, message: "h2 protocol error: http2 error: connection error detected: frame with invalid size", details: [], metadata: MetadataMap { headers: {} }'
[2023-11-14T06:44:32Z WARN  grpc::client] Connection to server interrupted. Error: Connection interrupted: 'status: Unknown, message: "h2 protocol error: http2 error: connection error detected: frame with invalid size", details: [], metadata: MetadataMap { headers: {} }'

Final result
To be filled by the one closing the issue.

All done here.


Consider supporting $0

While not very common, $0 is a valid Ion symbol, but attempting to read anything containing $0 into IonElement will result in an exception being thrown.
We should consider adding support for it, if possible. Right now, SymbolElement has a non-nullable textValue: String field. Making this field nullable would be a breaking change.

As a partial improvement, we could make $0 a latent error that gets thrown only when trying to access some symbol that has unknown text rather than throwing eagerly on load.


/login url still mounted when using a non-standard Authenticator

When using a non-standard Authenticator (such as the OAuthenticator setup) the default /login URL is no longer usable (it returns a 405 on POST with OAuthenticator), but it's automatically mounted as a default handler.

#126 is my proposal for a fix.  It moves /login from being a module-level default to being a handler supplied by the Authenticator base class.
I left /logout as an always-on default with my logic being that people are more likely to want to customize login than logout.  Though thinking about it some more I think I'm inclined to move /logout as well...


Rancher WSS Connections are "EOF"'ed when nginx-ingress reloads

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
When running Rancher in HA mode in Kubernetes, when the nginx ingress controller on the local cluster reloads (i.e. endpoint change, etc), all WSS connections to rancher are killed with "EOF". This causes any kubectl -f commands to also fail.
Steps to reproduce are as follows:

Install Rancher HA on an RKE Kubernetes cluster
Gather the kubeconfig through the rancher auth proxy for your cluster and use it to open a watched connection, i.e. kubectl --kubeconfig=rancher-auth-kc-local logs rancher-XXXX -n cattle-system -f
Create a workload/deployment of anything inside of the local cluster in any namespace
Create an ingress pointing to the workload
Wait for nginx-ingress to reload to update the desired ingress

Result:
The kubectl logs will fail with the following error message:
Endeavor:stuff chriskim$ kubectl --kubeconfig=kc-rancher logs rancher-79977f9d95-4dln7 -n cattle-system -f
...
2018/10/25 21:37:27 [INFO] error in remotedialer server [400]: websocket: close 1006 unexpected EOF
2018/10/25 21:40:36 [INFO] Creating token for user user-qstdm
2018/10/25 21:42:11 [INFO] Handling backend connection request [local:machine-nkwwj]

error: http2: server sent GOAWAY and closed the connection; LastStreamID=3, ErrCode=NO_ERROR, debug=""

Logs inside of the cattle-*-agents looks like:
time="2018-10-25T21:37:27Z" level=error msg="Failed to connect to proxy" error="websocket: close 1006 unexpected EOF"
time="2018-10-25T21:37:37Z" level=info msg="Connecting to wss://rancher.<IP_ADDRESS>.xip.io/v3/connect with token <redacted>"
time="2018-10-25T21:37:37Z" level=info msg="Connecting to proxy" url="wss://rancher.<IP_ADDRESS>.xip.io/v3/connect"
time="2018-10-25T21:42:00Z" level=error msg="Failed to connect to proxy" error="websocket: close 1006 unexpected EOF"
time="2018-10-25T21:42:10Z" level=info msg="Connecting to wss://rancher.<IP_ADDRESS>.xip.io/v3/connect with token <redacted>"
time="2018-10-25T21:42:10Z" level=info msg="Connecting to proxy" url="wss://rancher.<IP_ADDRESS>.xip.io/v3/connect"
time="2018-10-25T21:42:48Z" level=error msg="Failed to connect to proxy" error="websocket: close 1006 unexpected EOF"
time="2018-10-25T21:42:58Z" level=info msg="Connecting to wss://rancher.<IP_ADDRESS>.xip.io/v3/connect with token <redacted>"
time="2018-10-25T21:42:58Z" level=info msg="Connecting to proxy" url="wss://rancher.<IP_ADDRESS>.xip.io/v3/connect"

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.1.1
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): RKE
Machine type (cloud/VM/metal) and specifications (CPU/memory): Any
Kubernetes version (use kubectl version):

Endeavor:stuff chriskim$ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-08T16:31:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

/cc @alena1108 @aemneina

Happens because nginx ingress controller acts as a global LB for all ingresses in the system - in this case Rancher ingress and user ingresses - and on any update, the nginx config gets reloaded and it results in connection drop for Rancher. There are a couple of ways to address it:

avoid putting user ingresses on the rancher cluster to minimize the chances of reload
explore alternative ingress controllers that do reload more seamlessly (haproxy, traefik)

Added notes in the docs about how the ingress on k8s cluster should only point to the Rancher application and not other apps.

Similar problem on rancher 2.5.8 on K3s
I have a 2 node K3s (latest version at the moment of writing) that seems installed properly with a nginx balancer in front on a separate machine configured as in the documentation.
Installed 2.5.8 using helm.
Trying to add a "custom cluster" and seems that it canno reach the rancher env since the rancher node signal the error of EOF.
Installed cert-manager 1.3.1 that also seems to be working correctly.
Rancher is on a subnet 10.102.184.x on a domain X, while the custom cluster is on a 10.102.185.x on a domain of Y.
We also have an enterprise proxy to cope with.
How can I better debug to understand the situation?
Thanks

Hi @gioppoluca were you able to dig deep on this? We are in a similar situation.
Best


Script to control Kinect led + hook

Hi,
I just want to share my script (adapted from somewhere else allowing to change the led status of the kinect

#! /usr/bin/env python
import usb.core
import usb.util
import sys
find our device
dev = usb.core.find(idVendor=0x045e, idProduct=0x02B0)
was it found?
if dev is None:
raise ValueError('Device not found')
set the active configuration. With no arguments, the first configuration will be the active one
dev.set_configuration()
if sys.argv[1] == 'off':
led_value = 0x0
elif sys.argv[1] == 'green':
led_value = 0x1
elif sys.argv[1] == 'red':
led_value = 0x2
elif sys.argv[1] == 'orange':
led_value = 0x3
elif sys.argv[1] == 'blink_yellow':
led_value = 0x4
elif sys.argv[1] == 'blink_green':
led_value = 0x5
elif sys.argv[1] == 'blink_red_yellow':
led_value = 0x6
else:
led_value = 0x4
ret = dev.ctrl_transfer(0x40, 0x6, led_value, 0, [])
#print ret

then, you can create hook
on startup: /home/path/to/led_kinect.py green
on exit: /home/path/to/led_kinect.py off
on command : /home/path/to/led_kinect.py orange
etc...
all the colors are not working on my kinect (blinking orange for instance...) but this can give you a visual aspect of what is going on

Merci, c'est maintenant référencé sur le site:
http://domotiquefacile.fr/jarvis/content/hooks


Crocoddyl/unicycle.py - where is it located?

Hey!
Thank you so much for your great framework. I'm just getting started with it and currently trying to implement the unicycle-model to compare it against acados for my thesis. I somehow cannot get it working - it just won't optimize (stays at 0 all the time) the second control action (omega). Since you provided an example with exactly the same problem, I wanted to take a look at your implementation of the unicycle-model, but cannot locate the file (unicycle.py) which the corresponding jupyter notebook refers to. A short google search led me to this, i assume, highly outdated implementation: https://gitlab.iri.upc.edu/jmarti/crocoddyl/-/blob/master/crocoddyl/unicycle.py.
could you point me towards the right file, so I can proceed my research?
Best regards!

Hi @ThorbenPultke,
I assumed you tried to implement the unicycle from your side, but it doesn't converge, right?
The unicycle model used in our notebook (e.g., https://github.com/loco-3d/crocoddyl/blob/master/examples/notebooks/unicycle_towards_origin.py) is implemented in c++. However, we have a Python version for the sake of testing here: https://github.com/loco-3d/crocoddyl/blob/master/bindings/python/crocoddyl/utils/init.py#L179-L219
I hope this help you. I believe this issues can be closed.


could not find layer

when trying to scan an image using one of the examples, the following occurs:
./clair-scanner_linux_amd64 nginx:1.11.6-alpine example-nginx.yaml http://<IP_ADDRESS>:6060 <IP_ADDRESS>
2017-09-19 11:11:22.019062 I | Analyzing 23f9039742dcfc7436c234a037aa1890b36b0a259e009687fe427aeb1691cd22
2017-09-19 11:11:23.022625 I | Analyzing faild: Could not analyze layer: Got response 400 with message {"Error":{"Message":"could not find layer"}}

I am getting the same error, here are the logs from the clair docker container:
$docker logs clair
{"Event":"running database migrations","Level":"info","Location":"pgsql.go:216","Time":"2017-09-19 16:35:38.523420"}
{"Event":"database migration ran successfully","Level":"info","Location":"pgsql.go:223","Time":"2017-09-19 16:35:38.531607"}
{"Event":"notifier service is disabled","Level":"info","Location":"notifier.go:77","Time":"2017-09-19 16:35:38.532130"}
{"Event":"starting main API","Level":"info","Location":"api.go:52","Time":"2017-09-19 16:35:38.532210","port":6060}
{"Event":"starting health API","Level":"info","Location":"api.go:85","Time":"2017-09-19 16:35:38.532406","port":6061}
{"Event":"updater service started","Level":"info","Location":"updater.go:80","Time":"2017-09-19 16:35:38.532521","lock identifier":"84baf63e-c944-4577-b9c9-e67326dc8940"}
{"Event":"updating vulnerabilities","Level":"info","Location":"updater.go:167","Time":"2017-09-19 16:35:38.546804"}
{"Event":"fetching vulnerability updates","Level":"info","Location":"updater.go:213","Time":"2017-09-19 16:35:38.546865"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"ubuntu.go:88","Time":"2017-09-19 16:35:38.546931","package":"Ubuntu"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"alpine.go:52","Time":"2017-09-19 16:35:38.560280","package":"Alpine"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"debian.go:63","Time":"2017-09-19 16:35:38.567972","package":"Debian"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"oracle.go:119","Time":"2017-09-19 16:35:38.572712","package":"Oracle Linux"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"rhel.go:92","Time":"2017-09-19 16:35:38.580827","package":"RHEL"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:227","Time":"2017-09-19 16:35:39.860133","updater name":"rhel"}
{"Event":"Debian buster is not mapped to any version number (eg. Jessie-\u003e8). Please update me.","Level":"warning","Location":"debian.go:128","Time":"2017-09-19 16:35:46.040817"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:227","Time":"2017-09-19 16:35:46.041034","updater name":"debian"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:227","Time":"2017-09-19 16:35:49.093775","updater name":"oracle"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:227","Time":"2017-09-19 16:35:57.578649","updater name":"alpine"}
{"Event":"could not download layer","Level":"warning","Location":"driver.go:129","Time":"2017-09-19 16:39:03.540543","error":"Get http://localhost:9279/fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3/layer.tar: dial tcp <IP_ADDRESS>:9279: getsockopt: connection refused"}
{"Event":"failed to extract data from path","Level":"error","Location":"worker.go:122","Time":"2017-09-19 16:39:03.540614","error":"could not find layer","layer":"fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3","path":"http://localhost:9279/fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3/layer.tar"}
{"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-09-19 16:39:03.540969","elapsed time":33454970,"method":"POST","remote addr":"<IP_ADDRESS>:49340","request uri":"/v1/layers","status":"400"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:227","Time":"2017-09-19 16:39:19.543548","updater name":"ubuntu"}
{"Event":"adding metadata to vulnerabilities","Level":"info","Location":"updater.go:253","Time":"2017-09-19 16:39:19.543730"}
{"Event":"fetcher note","Level":"warning","Location":"updater.go:189","Time":"2017-09-19 16:43:24.495869","note":"Debian buster is not mapped to any version number (eg. Jessie-\u003e8). Please update me."}
{"Event":"fetcher note","Level":"warning","Location":"updater.go:189","Time":"2017-09-19 16:43:24.495919","note":"Ubuntu precise/esm is not mapped to any version number (eg. trusty-\u003e14.04). Please update me."}
{"Event":"update finished","Level":"info","Location":"updater.go:198","Time":"2017-09-19 16:43:24.497495"}
{"Event":"could not download layer","Level":"warning","Location":"driver.go:129","Time":"2017-09-19 16:49:17.652293","error":"Get http://localhost:9279/fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3/layer.tar: dial tcp <IP_ADDRESS>:9279: getsockopt: connection refused"}
{"Event":"failed to extract data from path","Level":"error","Location":"worker.go:122","Time":"2017-09-19 16:49:17.652354","error":"could not find layer","layer":"fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3","path":"http://localhost:9279/fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3/layer.tar"}
{"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-09-19 16:49:17.652515","elapsed time":427421471,"method":"POST","remote addr":"<IP_ADDRESS>:49382","request uri":"/v1/layers","status":"400"}
{"Event":"could not download layer","Level":"warning","Location":"driver.go:129","Time":"2017-09-19 17:12:48.988776","error":"Get http://<IP_ADDRESS>:9279/fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3/layer.tar: dial tcp <IP_ADDRESS>:9279: getsockopt: connection refused"}
{"Event":"failed to extract data from path","Level":"error","Location":"worker.go:122","Time":"2017-09-19 17:12:48.988838","error":"could not find layer","layer":"fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3","path":"http://<IP_ADDRESS>:9279/fa8c9564107436d9aebe3909e91b41a08d5cd910535fdc05a6a620db677d13b3/layer.tar"}
{"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-09-19 17:12:48.989254","elapsed time":2070749,"method":"POST","remote addr":"<IP_ADDRESS>:49392","request uri":"/v1/layers","status":"400"}

If you are running on OSX you will need to provide the ip address of the "en0" adapter because the ip <IP_ADDRESS> and localhost inside 'clair-local-scan' is inside the container and not actually your OSX.

I haven't tested it (I am on osx) but something like this should work I think on Linux:
docker run --net=host -d --name db arminc/clair-db:2017-09-18
docker run --net=host --add-host postgres:<IP_ADDRESS> -d --name clair --net=host arminc/clair-local-scan:v2.0.1
./clair-scanner nginx:1.11.6-alpine example-nginx.yaml http://<IP_ADDRESS>:6060 <IP_ADDRESS>

Context to add to the complexity of debugging: I am running a ubuntu 16.04 VM inside virtualbox on my windows host. Inside the Ubuntu VM I am running docker 17.05.
I modified the end ip address for clair-scanner and it appears to have conducted a scan, but I am unsure how I am supposed to get the results now? For your reference I ran two commands, one is a personal docker container:
 clair-scanner alpine blankwhitelist.yaml http://localhost:6060 <IP_ADDRESS>
 clair-scanner joeyn414/centosgauntlt blankwhitelist.yaml http://localhost:6060 <IP_ADDRESS>
blankwhitelist.yaml is just blank, its only there because you appear to require a file.

It does not matter as long as you run everything in linux. When you run the scan, for example alpine, you will get a response commandline telling you which CVE's are present (as long as they are not whitelisted in the yaml).
For example the output of the above two containers is:
$ ./clair-scanner alpine empty.yaml http://ip:6060 ip
2017-09-20 08:21:59.644498 I | Analyzing 693bdf455e7bf0952f8a4539f9f96aa70c489ca239a7dbed0afb481c87cbe131
2017-09-20 08:21:59.655602 I | Image contains unapproved vulnerabilities: [CVE-2016-9840 CVE-2016-9841 CVE-2016-9842 CVE-2016-9843]

Or your own docker container:
./clair-scanner joeyn414/centosgauntlt empty.yaml http://ip:6060 ip
2017-09-20 08:30:01.019036 I | Analyzing 52fd088917739a96f23826a3c6ef98c465e7dd34a688a52752077da0903a638f
2017-09-20 08:30:07.123831 I | Analyzing afc532cb6eb99801c8f1d60780ff852f57415a5567319c2714c9c2f27d9dac18
2017-09-20 08:30:22.658011 I | Image contains unapproved vulnerabilities: [RHSA-2017:1860 RHSA-2017:1916 RHSA-2017:1916 RHSA-2017:0906 RHSA-2017:2479 RHSA-2017:1916 RHSA-2017:2029 RHSA-2017:2473 RHSA-2017:2679 RHSA-2017:1842 RHSA-2017:0372 RHSA-2017:1916 RHSA-2017:2016 RHSA-2017:1852 RHSA-2017:0906 RHSA-2017:2479 RHSA-2017:2004 RHSA-2017:2484 RHSA-2017:1931 RHSA-2017:0906 RHSA-2017:2479 RHSA-2017:2016 RHSA-2017:1868 RHSA-2017:2029 RHSA-2017:1868 RHSA-2017:2016 RHSA-2017:2004 RHSA-2017:2484 RHSA-2017:1852]

Excellent thank you for the clarification, I was expecting a report to be dropped somewhere but this works just fine for my purposes.
Great work getting this working!

I am glad it works.

@arminc Should the documentation be updated?

@030 what is missing? You mean the explanation regarding "localhost"?

I ran into this issue today, but while using CentOS 7. Make sure you open port 9279/tcp using something like the command below:
sudo firewall-cmd --zone=public --add-port=9729/tcp --permanent
sudo firewall-cmd --reload
An alternative to the above would be to change the listening port in server.go and then open the corresponding port in the firewall.

For me it was the port 9279 which required firewall open.
firewall-cmd --zone=public --add-port=9279/tcp --permanent

I ran into this issue today, but while using CentOS 7. Make sure you open port 9279/tcp using something like the command below: sudo firewall-cmd --zone=public --add-port=9729/tcp --permanent sudo firewall-cmd --reload This did the trick. An alternative to the above would be to change the listening port in server.go and then open the corresponding port in the firewall.

It's exectly this reason, thx.


Fix spelling in content

See changes highlighted in green in the content document.

LSBC -> Law Society of British Columbia
CSB -> Court Services Branch
Verified Person -> Person credential
Lawyer2 -> Joyce
Ensure all sentences end in a period
Headers should only have the first word capitalize (unless other words are pronouns ex. Get your Law Society of British Columbia credential)

Basically spell out all abbreviations unless it's a pronoun.
ex. BC Wallet, BC Services Card are all pronouns.
Screenshots below

Fix capitalization, spell out acronyms. missing period.

Resolved by: https://github.com/bcgov/BC-Wallet-Demo/pull/116


Replace tp-spacer-unit usage

Replaces the couples instances $tp-spacer__unit token with a hardcoded pixel value.

@danoc had a merge conflict. can you re-review?


xournalpp / xournal++ crashes at startup

Issue description
Xournalpp crashes immediately.
Steps to reproduce'
I don't have KDE nor GNOME installed in case that matters.
$ nix-build '<nixpkgs>' -A xournalpp
$ result/bin/xournalpp

** (xournalpp:2719): WARNING **: 08:08:07.696: Failed to load "colornames.ini" (/home/jluttine/.xournalpp/colornames.ini): No such file or directory

ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2636:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2636:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2636:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
**
Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme breeze (gtk-icon-theme-error-quark, 0)

** (xournalpp:2719): WARNING **: 08:08:07.827: [Crash Handler] Crashed with signal 6

** (xournalpp:2719): WARNING **: 08:08:07.832: [Crash Handler] Wrote crash log to: /home/jluttine/.xournalpp/errorlogs/errorlog.20190624-080807.log
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found

** (xournalpp:2719): WARNING **: 08:08:07.942: Trying to emergency save the current open document…

** (xournalpp:2719): WARNING **: 08:08:07.943: Successfully saved document to "/home/jluttine/.xournalpp/emergencysave.xopp"

Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.47, NixOS, 19.09.git.4ab1c14 (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - nixpkgs: `/etc/nixpkgs`

Do you have an icon theme installed?

I don't know, so maybe not..

https://github.com/NixOS/nixpkgs/issues/63089#issuecomment-502201837

Installing gnome3.adwaita-icon-theme as per #63089 fixed it for me (but I tried hicolor-icon-theme first, which didn't). Though crashing is by no means a good or descriptive way to tell the user to install icons. I wonder if there is a fallback icon (not an icon set, just a single one) we could bundle with things to stop this

This should be fixed IMO. It is very against the nix ideology to require one package to be installed for another to function.
cc @andrew-d  @sikmir

I'd be happy to take a fix to xournalpp here, but I'm not quite sure what the best approach is. My understanding is that GTK+ itself is what's crashing if the "image-missing" icon isn't found - see here.
As I understand it, we have the following options:

Unconditionally wrap xournalpp with some icon theme; I'm not sure how this interacts with allowing users to still customize things themselves.
Fix GTK+ to not crash if the icon is missing; I don't know how to do this
Try to detect this case in xournalpp or other utilities and throw an error; I could probably write a wrapper that searched XDG_ICON_DIRS, but I'm not 100% sure this works, and it feels too hacky.
Maybe create an "empty" icon theme that's always linked by default and contains only the image-missing.png image?

I haven't had the chance to test it, but if anyone else wants to: here's an example of a Nix derivation for an icon theme that only contains the image-missing.png images from the Adwaita icon theme:
https://gist.github.com/andrew-d/41f2942a32b02249fac2dadf934cecec

Why isn't

Unconditionally wrap xournalpp with some icon theme; I'm not sure how this interacts with allowing users to still customize things themselves.

The obvious solution? It is still possible to set another icon theme locally (if using .gtkrc and pendants), provided it is also installed to the regarding environment?

I guess it's mostly a question of icons are large (ish) and we don't want to install unnecessary icons. I am pro the image-missing solution, provided we also document it somewhere (not sure if NixOS manual is the best place, could apply to non-NixOS nix installations, so the Nix manual).
Also, the .gtkrc is an annoying solution as it's not part of the nixos config, I guess.

@KoviRobi

I guess it's mostly a question of icons are large (ish) and we don't want to install unnecessary icons. I am pro the image-missing solution, provided we also document it somewhere (not sure if NixOS manual is the best place, could apply to non-NixOS nix installations, so the Nix manual).

This is indeed the primary reason, see the discussion in #43150.
@andrew-d

Unconditionally wrap xournalpp with some icon theme; I'm not sure how this interacts with allowing users to still customize things themselves.

Customization is still possible (the theme used will be still the one set in profile, defaulting to Adwaita), the closure is the main concern.

Fix GTK+ to not crash if the icon is missing; I don't know how to do this

I talked with GTK devs on IRC a few days ago and they also said that GTK should use the image-missing from GTK and the source code looks like that is what should be happening but to no avail.
Actually, it seems to somewhat work – try running env XDG_DATA_DIRS= (nix-build -A gtk3.dev --no-out-link)/bin/gtk3-icon-browser, it will have the image-missing in the CSD.

Maybe create an "empty" icon theme that's always linked by default and contains only the image-missing.png image?

Brilliant idea. This would be an acceptable compromise, I think, until it is fixed in GTK. We should probably use fetchurl { url = "https://gitlab.gnome.org/GNOME/gtk/blob/3.24.13/gtk/icons/16x16/status/image-missing.png"; } to avoid depending on Adwaita, and add it to hicolor-icon-theme instead of new theme. Then we can add the icon theme to wrapGAppsHook.

Try to detect this case in xournalpp or other utilities and throw an error; I could probably write a wrapper that searched XDG_ICON_DIRS, but I'm not 100% sure this works, and it feels too hacky.

We might still want something like this to let users know they should install an icon theme. But we can worry about that once we prevent the crash.

This is still an issue.

Just in case, the same problem with MyPaint (https://github.com/NixOS/nixpkgs/pull/54677), it crashes at startup.

It is still an issue.

I can only reproduce it when trying to export a pdf with xournalpp -p out.pdf in.xopp, which might be a different issue (yet still annoying).
What about you @sikmir @jluttine?

I can only reproduce it when trying to export a pdf with xournalpp -p out.pdf in.xopp, which might be a different issue (yet still annoying).
What about you @sikmir @jluttine?

I really cannot reproduce the crash neither at startup, nor with xournalpp -p out.pdf in.xopp. Could you please provide crash dump or backtrace? Otherwise it's hard to say what is going wrong.

Seems to work for me now. I don't know what has changed. Should I close this or is it still an issue for someone?

I still have this problem.

Try https://github.com/NixOS/nixpkgs/pull/159902, maybe it helps.

@sikmir I cannot reproduce the problem anymore. Good catch!

Hello, this is still an issue for me! On a NixOS unstable 23.11 install with KDE Plasma. Same error as original post:
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.5.5, NixOS, 23.11 (Tapir), 23.11pre531102.fdd898f8f79e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

$ xournalpp
xopp-Message: 15:37:02.273: TEXTDOMAINDIR = (null), Platform-specific locale dir = /nix/store/dn1g7biypbl60pamj5zsc4lhaq8zxggi-xournalpp-1.2.1/share/xournalpp/../locale, chosen directory = /nix/store/dn1g7biypbl60pamj5zsc4lhaq8zxggi-xournalpp-1.2.1/share/xournalpp/../locale
ALSA lib pcm_dsnoop.c:566:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2737:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2737:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2737:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
xopp-Message: 15:37:02.324: Plugin "MigrateFontSizes" UI initialized

(com.github.xournalpp.xournalpp:93805): xopp-WARNING **: 15:37:02.401: No device found. Is Xournal++ running in debugger / Eclipse...?
Probably this is the reason for not finding devices!

(com.github.xournalpp.xournalpp:93805): xopp-WARNING **: 15:37:02.418: No device found. Is Xournal++ running in debugger / Eclipse...?
Probably this is the reason for not finding devices!

**
Gtk:ERROR:../gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Adwaita (gtk-icon-theme-error-quark, 0)
Bail out! Gtk:ERROR:../gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Adwaita (gtk-icon-theme-error-quark, 0)

(com.github.xournalpp.xournalpp:93805): xopp-WARNING **: 15:37:02.455: [Crash Handler] Crashed with signal 6

(com.github.xournalpp.xournalpp:93805): xopp-WARNING **: 15:37:02.455: [Crash Handler] Wrote crash log to: /home/joao/.cache/xournalpp/errorlogs/errorlog.20231007-153702.log
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found
sh: line 1: addr2line: command not found

(com.github.xournalpp.xournalpp:93805): xopp-WARNING **: 15:37:02.586: Trying to emergency save the current open document…

(com.github.xournalpp.xournalpp:93805): xopp-WARNING **: 15:37:02.586: Successfully saved document to "/home/joao/.config/xournalpp/emergencysave.xopp"

installing
gnome.adwaita-icon-theme
solved the problem for me

Thanks. I can confirm that it solves the issues. But if it is a known requirement/dependency for so long already shouldn't the xournalpp package install it in the first place?


(nuxt) send bearer token on each request

Describe the Feature
Send bearer token for each request to the backend

this issue is partly completed, a new one will be opened in the future


Update AdminLastMileFailuresTable.tsx

Improve the modal content for the LastMileFailure Info Dialog.
Before:

After:

@kevinhaube It was a legit callout to see if it was trivial to reduce duplicate react tsx. Thanks for the review!


Add e2e test for Caikit Nlp Client

This is a draft PR for testing https://github.com/opendatahub-io/caikit-nlp-client against models which are deployed using RHOAI single-model serving stack.
The test code was originally written in a python script in my local copy of the caikit-nlp repo for an ease and faster execution. Now I'm moving it to ods-ci.
This is still a draft and it will go over release 2.5 for sure, for at least 2 reasons:

it upgrades python from 3.8 to 3.11 (3.9 is the minimum req for caikit-nlp-client lib)
I have decided to have these tests in a separate suite file. Separate suite requires me to move keywords from llm suite to common resource file and will take some time to make the necessary changes and validate the PR

In the meantime, I've pushed into this draft the python script to test the library as well - you can run it on your local

this one cannot be tested on CI yet for some pkg incompatibility. Will align with @aloganat

I will add the missing Documentation tags and PR validation later


Documentation query/request

I wondered if it would be a good idea in the docker page to advise of special characters that should not make up the password of a user as I recently got caught out by needing to use escape characters in bash in order to login on the command line.

While this is unfortunate, it's not exactly specific to MongoDB (or even more particularly, running MongoDB inside Docker using this specific Docker image), so I don't think it's very appropriate for us to use our limited image description space describing it. :sweat_smile:


Russian and Ukrainian translation

Thank you so much for this!

Oh, I actually forgot to say: the 1.18.2 branch is the latest version. I'll merge 1.18.2 into main and see how it affects the translation.
Would you be able to update it? I'm sure I've added options since then.

I see only 3 new keys in 1.18.2 branch, and it's OK. You can merge, and I'll send another pull there.


npm postinstall fails with recent babel-cli versions

When building from source, I had to install with --ignore-scripts since npm run babel was failing during npm postinstall. Here are some various errors:
npm run babel
Error: Couldn't find preset "es2015" relative to directory "[...]/node_modules/bookshelf"
ReferenceError: Unknown plugin "syntax-object-rest-spread" specified in "[...]/node_modules/bookshelf/.babelrc" at 0, attempted to resolve relative to "[...]/node_modules/bookshelf"
The issue appears to be that when building from source, Bookshelf doesn't specify the appropriate versions of babel and its plugins, presuming them to be available with babel-cli. Since babel 6 unbundles a ton of stuff from the core, this is no longer a safe assumption.
I was able to get it to build by first running npm install babel-preset-es2015 babel-plugin-syntax-object-rest-spread babel-plugin-transform-object-rest-spread to get the necessary extensions.
I propose that Bookshelf's package.json should specify the necessary devDependencies instead of expecting them to exist, or alternatively, specify an older version of babel to use or install that has the necessary bundled extensions.

Related: #981

I propose that Bookshelf's package.json should specify the necessary devDependencies instead of expecting them to exist

Yeah, they're already there. The problem is that the postinstall script that I wrote doesn't install everything.
I've been advised that the set up is to not do anything in postinstall and move the build logic into the prepublish script. This would require users to manually npm install if they would like to depend on a specific commit.

Ah, so they are. Hmm. That seems pretty atypical for npm packages, even ones installed from Github. I think I remember seeing advice like that (maybe from Domenic?), and it seemed like an idealized notion of how npm packages should be installed that is not actually a reflection of real world use or expectations.
It seems reasonable to expect that installing from a github commit or tag will work just like installing from npm proper. This is also a problem for remote installs that rely on specfic github commits in the package.json (very common).
Until this is moved to prepublish, would npm install instead of npm install babel-cli work in the postinstall script to install all of the devDependencies?

Resolved by #1403


Add benchs

Add benchmarks
Description
This PR adds 3 benchmarks for Cairo Native + Starknet in Rust.

Fibonacci
Factorial
ERC20

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #1129 (864ebe9) into main (bf81e72) will decrease coverage by 0.21%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1129      +/-   ##
==========================================
- Coverage   89.55%   89.35%   -0.21%
==========================================
  Files          50       50
  Lines       13404    13405       +1
==========================================
- Hits        12004    11978      -26
- Misses       1400     1427      +27

Files
Coverage Δ

src/syscalls/business_logic_syscall_handler.rs
76.75% <0.00%> (-0.10%)
:arrow_down:

... and 2 files with indirect coverage changes


Support MobileNet

MobileNet is a new architecture from Google (https://arxiv.org/abs/1704.04861) that is designed to run on mobile devices making it a perfect fit for cnndroid: https://github.com/Zehaos/MobileNet
I believe it's not supported due to 1x1 convolutions

MobileNet architecture heavily uses depthwise separable convolution.
So the first step is implementing  depthwiseConv with renderscript.
Reference: depthwise separable convolution in Metal render language
http://machinethink.net/blog/googles-mobile-net-architecture-on-iphone/?utm_source=tuicool&utm_medium=referral


Consumer reconnection

What is the proper way of maintaining a "reliable" consumer? And by reliable I mean that it should be available during whole program execution. Particularly, if there's an error on some call, it should try to recover, if possible (e.g. in case of loosing connection, it should reconnect to the broker)
Should the consumer::Consumer re-constructed once again (and again, ...) in such a case? Or it might be some other way of handling that?

I would expect the library to solve it for you. What's the current behaviour when a connected broker fails?

👋 new to the rust world.  For the question on what should the client do if losing connection to the coordinTor, the client should try to reconnect.  If the poll timed out, it should return nothing/an empty record. This is java clients behavior though...

@philipnee Java is the main client, and has lots of contributors. While we can leverage a big part of the work using librdkafka, it's no surprise it's lagging behind. It might be solved in the meantime. It would be nice to look into the current behavior. I would expect, even with all brokers down, the consumer to reconnect after they are up again.

it would be (very) nice to have a rust native kafka client instead of wrapping around librdkafka. And yes, consumers should retry until timeout.


Reopen log file when rollover is unsuccessful

Fixes https://github.com/apache/logging-log4j2/issues/2592
Fixes RollingFileManager to reopen the log file when the rollover was unsuccessful
See also https://github.com/apache/logging-log4j2/pull/3021#issuecomment-2392077718
Checklist

Base your changes on 2.x branch if you are targeting Log4j 2; use main otherwise
./mvnw verify succeeds (if it fails due to code formatting issues reported by Spotless, simply run ./mvnw spotless:apply and retry)
Non-trivial changes contain an entry file in the src/changelog/.2.x.x directory
Tests for the changes are provided
Commits are signed (optional, but highly recommended)

@king-tyler,
Thank You for your contribution! :100:


ci: remove unit test reporter

Barely used it, reducing things to maintain here :P

#660  👈
main

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

Join @davidlj95 and the rest of your teammates on  Graphite


Can we get an example of how to do a plugin with string and struct parameters?

probably related to https://github.com/denosaurs/plug/issues/10

https://github.com/denosaurs/plug/pull/11

This is not directly related to plug as it is simply the dylib loader, examples and other ffi or related projects can be found:

https://github.com/denoland/deno/tree/main/test_ffi
https://github.com/DjDeveloperr/deno_gl
https://github.com/denodrivers/sqlite3
https://github.com/denosaurs/byte_type/blob/main/ffi.ts

I do it like this for now
const encoder = new TextEncoder();

function encode(value: string) {
  return encoder.encode(value + "\0");
}

const dylib = Deno.dlopen("./path/to/lib.so", {
  "getVersion": {
    name: 'GetVersion',
    parameters: ["pointer"],
    result: "pointer",
  }
})

const pointer = dylib.symbols.getVersion(
  encode("Some string")
)

const value = new Deno.UnsafePointerView(pointer).getCString()

// value is now a string

what about a struct?

Didn't know denosaurs have a good module for this
import { Struct, i32le } from<EMAIL_ADDRESS>
const _lib = Deno.dlopen("app.so", {
  add: { parameters: ["pointer"], result: "i32" }
});

const i32 = i32le
const struct = new Struct({ a: i32, b: i32 })

function add(a0: {a: number; b: number }) {
  const _buf_a0 = new Uint8Array(_Input.size)
  const _view_a0 = new DataView(_buf_a0.buffer)
  _Input.write(_view_a0, 0, a0)
  const _result = sys.symbols.add(_buf_a0)
  return _result as number
}

add({
  a: 6,
  b: 9
})

nice
if you want to go for gold i’d show how to do FFI with a function that returns a pointer to a struct or how to reference a struct that was passed as a pointer (aka if the FFI call modified the struct and it’s Deno’s turn to read the changes back)

nice
if you want to go for gold i’d show how to do FFI with a function that returns a pointer to a struct or how to reference a struct that was passed as a pointer (aka if the FFI call modified the struct and it’s Deno’s turn to read the changes back)

I think this can all be done in that module. It’s just missing docs

What is _Input in that example? Seems to not be in the example.

What is _Input in that example? Seems to not be in the example.

fixed

I am not sure how to read structs yet with byte_type. Only writing.


Chore: Seedfile

Add image to campaigns seed

Pull Request Test Coverage Report for Build 1

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.443%

Totals

Change from base Build 30:
0.0%

Covered Lines:
135

Relevant Lines:
158

💛  - Coveralls


Deeper Babel configuration. Passing options.

Hi there!
I'm building a frontend for embedded device so working with CDN since there's no place for all required modules.
Here is the case: Vue single file component imports js file. Vue file itself is loaded using sfc-loader. This action leads to method transformJSCode and to assertModuleNodeAllowed call for js file. And it fails since it is not a module but a plain javascript.
As I can see, there's nothing passed at the Babel parser level except of additionalBabelParserPlugins.
Is there a way to pass options to parser directly? I'm very interested in allowImportExportEverywhere flag.
So the questions are:

is it possible now to pass required Babel options?
Are there plans to implement this feature?

Hi ru5t, you really want to use import and export from everywhere ?

Hi, Frank. For sure, in general - no.
But in some particular cases in the limited and controlled context - probably. I mean that it is an exception that vue single file component is going to be loaded like this. But to have possibility to tune babel's logic deeper, if needed, would be good.
This particular case was solved by rewriting of provided js library in CommonJS manner. It was small enough to do so.
So, basically absence of this feature is not slowing process. But it seems to me, that deeper configuration possibilities could be of some use for someone.

Hi ru5t,
I will consider additional options on a case-by-case basis.
Feel free to create new enhancement issue for each individual option you need.


Addon does not work with ember-cli 3.4.0-beta.2 or above; NODE_ENV is not defined

Hello!
Summary
ember-cli-prop-types does not work with ember-cli 3.4.0-beta.2 or above.
Description + Repro Steps
I tried to update ember-cli (either only ember-cli or using ember-cli-update [which updates more dependencies]) to the newest version (3.4.3). But after update, I see an error in my app:  ReferenceError: NODE_ENV is not defined.
Uncaught ReferenceError: NODE_ENV is not defined
    at Object.initialize (component-prop-types.js:21)
    at index.js:91
    at Vertices.each (dag-map.js:188)
    at Vertices.walk (dag-map.js:117)
    at DAG.each (dag-map.js:62)
    at DAG.topsort (dag-map.js:68)
    at Class._runInitializer (index.js:112)
    at Class.runInitializers (index.js:88)
    at Class._bootSync (application.js:431)
    at Class.domReady (application.js:385)

ember-cli version 3.3.0 or 3.4.0-beta.1 works correctly. ember-cli 3.4.0-beta.2 or 3.4.2 or above does not work with ember-cli-prop-types
It looks that NODE_ENV, INCLUDE_GET_DEFAULT_PROPS and other variables are not replaced by babel-plugin-inline-replace-variables after ember-cli upgrade.
If I moved configuration of babel-plugin-inline-replace-variables from preprocessTree to the options object (like in the example in the babel/ember-cli-babel https://github.com/babel/ember-cli-babel#options ), then problem disappeared. Of course - env or process.env.EMBER_ENV is not defined yet. But also helped moving this configuration from preprocessTree to the included function (I guess that order of called functions was changed in new ember - it's only my guess).
Environment Information
Here's my setup:

OS: Antergos running version 4.18.12-arch1-1-ARCH
ember-cli: 3.4.3
ember-cli-prop-types: 1.5.0
Node: 10.11.0 with npm 6.4.1, yarn 1.9.4, bower 1.8.4
Browser: Chrome 69.0.3497.100-1

Hey @Krzyrok! Thanks for reporting this. Since you've been able to arrive at a solution with relatively minimal changes, would you be open to making a PR to get those in place?

Hi, sorry for delay. I've forked and pushed the changes - so waiting for merge and release only.

Version 1.6.0 has been published, which includes these fixes. Big thanks to @Krzyrok for getting things working with newer versions of Ember CLI!


Mediapipe support two input streams(video and audio) ?

i input two streams,but it run failed.

Hi @DavinFun, Can you share us the failure logs. Thanks!


[MM-21076] Improve dropdown menu wrapping behavior

Summary

added new element to primary text to assist with wrapping when help text is present
reverted some recent changes to make <span>s block elements again
minor tweaks to spacing to accommodate for element structure changes
Updated with this PR: Add minimum width to prevent short (i.e. two words) menu items for wrapping

Ticket Link
https://mattermost.atlassian.net/browse/MM-21076
Screenshots

Creating a new SpinWick test server using Mattermost Cloud.

Test server creation failed. See the logs for more information.

Test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4535.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

/update-branch

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit 5e6f3708205d4a1fc93f2c43a3968a5b590bbde5.
Access here: https://mattermost-webapp-pr-4535.test.mattermost.cloud

Test server destroyed

/update-branch

Error trying to update the PR.
Please do it manually.

@bradjcoughlin
Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Fetching origin
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-#4535-upstream-release-5.19-1578941836
Branch 'automated-cherry-pick-of-#4535-upstream-release-5.19-1578941836' set up to track remote branch 'release-5.19' from 'upstream'.
+++ Downloading patch to /tmp/4535.patch (in case you need to do this again)

+++ About to attempt cherry pick of PR. To reattempt:
  $ git am -3 /tmp/4535.patch

Applying: Make long <MenuItem>s wrap
Using index info to reconstruct a base tree...
M	components/widgets/menu/menu_items/menu_item.scss
Falling back to patching base and 3-way merge...
Auto-merging components/widgets/menu/menu_items/menu_item.scss
CONFLICT (content): Merge conflict in components/widgets/menu/menu_items/menu_item.scss
Patch failed at 0001 Make long <MenuItem>s wrap
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

+++ Conflicts detected:

UU components/widgets/menu/menu_items/menu_item.scss

+++ Aborting in-progress git am.

+++ Returning you to the master branch and cleaning up.

@bradjcoughlin Is this cherry-picked?

@amyblais yes, thanks


Adding Unit test cases for wrappedNodeFetch and adding github actions

For code coverage added unit test for wrappedNodeFetch function and integrated git hub actions.
test #354
Closes: https://github.com/keploy/keploy/issues/354

Hi @re-Tick! Can you please review the PR?

@Hermione2408 please resolve DCO and commitzen

Can you have a look now @re-Tick

Hey @re-Tick , Can you please review the changes now

a test is failing. I will try these changes locally and request changes if any.

Sure I'll try to resolve too where they are failing

@re-Tick I have made the changes and it is passing all the test cases now.

LGTM. Please add this PR link in GSOC task list.


Localization-xml-centered Terms Testing

After the issue with Indonesian (and Portuguese), it's apparent that the terms localization files are not always themselves clean. We have tests to cover the logic of terms parsing, but maybe we should add a test or two to verify that each localization (and each new one going forward) is working and parsed as expected.

@Enkidu93, do you think this could be a good issue for @mudiagaobrikisil?


Fix to run on both OSX + Linux

@lastcoolnameleft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Dashboard hangs when you Toggle Chart Description for more than one chart.

My Dashboard loads.
I click Toggle Chart Description on one chart. It shows.
I click Toggle Chart Description on a second chart. The browser hangs.
Same behaviour on Safari and Chrome.
Expected results
I expect the Description to show on all the charts for which I have toggled chart description.
Actual results
As described above.
Screenshots

Environment
(please complete the following information):
NAME                    CHART VERSION   APP VERSION
superset/superset       0.5.10          1.0
Using the latest Helm chart.

browser type and version: Safari and Chrome latest.
superset version: superset version 1.0
python version: python --version 3.8
node.js version: node -v. None
any feature flags active:  None

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[checking] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[unable to do that] I have reproduced the issue with at least the latest released version of superset.
[ X] I have checked the issue tracker for the same issue and I haven't found one similar.

@yousoph @kasiazjc We don't even have this anymore... you can still add these descriptions, but they don't appear anywhere in the UI as far as I'm noticing. Was this by design or by mistake?
Tempted to close this bug, since... well, it's not a bug if the menu item is gone... but maybe this is even worse?

Confirmed that the issue is fixed and works as intended in supported versions of Superset.
https://github.com/apache/superset/assets/70410625/c1cfb475-ccf0-44e0-afbd-9a3296e0db98