[TextField] Remove empty label with variant filled

I'd like to be able to center the value when a Filled TextField Label is empty.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
Using a Filled TextField, when there is no label, the value should be centered.
Examples 🌈
Reproduction: https://codesandbox.io/s/outlined-select-no-shrink-forked-k0ikn?file=/demo.js
In this example the value is not centered.
Vuetify does it with a prop single-line: https://vuetifyjs.com/en/components/text-fields/#single-line (note it also works using Textarea)
Motivation 🔦
I have a list of TextFields which would have the same label. I'd rather group them under a Typography component:
<Typography>Title</Typography>
<TextField/>
<TextField/>

tip: hiddenLabel

tip: hiddenLabel

solved it for me by adding hiddenLabel thx @oliviertassinari  🌈 🙌 🎉


Add startup task, setting to launch application on login

Summary of the Pull Request
This PR adds a new boolean global setting, startOnUserLogin, along with associated AppLogic to request enabling or disabling of the StartupTask. Added UAP5 extensions to AppX manifests.

References
#2189

PR Checklist

[x] Closes #2189
[x] CLA signed. If not, go over here and sign the CLA
[x] Tests added/passed
[x] Requires documentation to be updated
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #2189

Detailed Description of the Pull Request / Additional comments
Please note, I'm a non-practicing C++ developer, there are a number of things I wasn't sure how to handle in the appropriate fashion, mostly around error handling and what probably looks like an incredibly naive (and messy) way to implement the async co_await behavior.
Error handling-wise, I found (don't ask me how!) that if you somehow mismatch the startup task's ID between the manifest and the call to StartupTask::GetAsync(hstring taskId), you'll get a very opaque WinRT exception that boils down to a generic invalid argument message. This isn't likely to happen in the wild, but worth mentioning...
I had enough trouble getting myself familiarized with the project, environment, and C++/WinRT in general didn't want to try to tackle adding tests for this quite yet since (as I mentioned) I don't really know what I'm doing. I'm happy to give it a try with perhaps a bit of assistance in getting started 😃
Further work in this area of the application outside of this immediate PR might need to include adding an additional setting to contain launch args that the startup task can pass to the app so that users can specify a non-default profile to launch on start, window position (e.g., #653).

Validation Steps Performed
✔ Default settings:
Given the user does not have the startOnUserLogin setting in their profile.json,
When the default settings are opened (via alt+click on Settings),
Then the global settings should contain the "startOnUserLogin": false token
✔ Applying setting on application launch
Given the startOnUserLogin is true and
the Windows Terminal startup task is disabled and
the application is not running
When the application is launched
Then the Windows Terminal entry in the user's Startup list should be enabled
✔ Applying setting on settings change
Given the startOnUserLogin is true and
the Windows Terminal startup task is enabled and
the application is running
When the startOnUserLogin setting is changed to false and
the settings file is saved to disk
Then the Windows Terminal startup task entry should be disabled
note: Task Manager does not seem to re-scan startup task states after launch; the Settings -> Apps -> Startup page also requires closing or moving away to refresh the status of entries

holy wow alright this'll take some time to digest.  That's really impressive.
I'm going to be the pre-emptive bearer of badish news - we're starting to make harder cuts about what is and isn't making it into the 1.0 release of the Terminal. As awesome as this feature is, I'm going to go with my gut here and guess that this isn't going to make that cut unfortunately. That being said, we're still going to review this now and get feedback to you. Once this gets approved, we'll probably just hold in until we make an official 1.0 release branch, and then we'll get it merged immediately after that.

holy wow alright this'll take some time to digest.

The excellent work you folks have put into the docs is the only thing that made it feasible for me to undertake. 👍 I'm happy to make any changes suggested - I know there's a lot that can be improved upon.

we're starting to make harder cuts about what is and isn't making it into the 1.0 release of the Terminal...this isn't going to make that cut unfortunately.

Honestly, I haven't been paying attention to the release schedule you guys have been so transparent about communicating, so only mildly disappointing 😆 - I'm happy you're all not laughing yourselves to the ground after looking at the products of my flailing around in VS! 😅
Joking aside, if it doesn't make 1.0, that'll just mean there's more time to add some more polish and refinement :)
Thanks for the consideration 😄

Question for @zadjii-msft -- do you typically prefer to keep PR's updated from the master branch periodically, once prior to review, not at all, something else? Wanted to ask before I pushed up a merge commit that brings in latest from master

In my experience, it's easier for me to do merges if I keep pulling master at regular intervals. Usually that keeps the merge conflicts as manageable as possible.

Looks like the unit test run is responsible for the timeout - ran for 46min, but seemed to be reporting results up to the point of cancellation.
Is this anything I can remedy, or is it OK to ignore it for now?

The x86 tests can be flaky. I'll re-schedule this one. :smile:

@DHowett-MSFT -- I had no errors building locally with Invoke-OpenConsoleBuild /p:Configuration=Release /p:Platform=x64, and I can't see anything obvious in the diffs that point to a specific change that could cause the build failure:

\Microsoft.Windows.CppWinRT.2.0.200316.3\build\native\Microsoft.Windows.CppWinRT.targets(164,13): Error MSB4006: There is a circular dependency in the target dependency graph involving target "ComputeGetResolvedWinMD"

Is there anything you can see that I might be able to do to resolve this, or is it another one of those "flaky build" types of things?

@jelster That's unfortunately one of those "flaky build" issues. At least with the unit test failure, we know that's our fault, but we're still trying to track down whatever the heck is causing this error.
For the future us, the failing build was https://dev.azure.com/ms/Terminal/_build/results?buildId=74825&view=logs&jobId=fe5d217b-357f-5a83-11fa-ea15ba02c406&j=fe5d217b-357f-5a83-11fa-ea15ba02c406&t=1dea19ec-49ff-524b-2675-ea6f89a90475
I'll kick it again, and it'll probably just fix itself.

Thanks for the info @zadjiii-msft.
I delved into the logs for this build a bit, and I think that the build is sporadically failing due to the non-deterministic ordering and appearance of each individual project's output during the build. This is due to the -m (allow parallel builds) switch being specified on the MSBuild command line:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\msbuild.exe" "d:\a\1\s\OpenConsole.sln" /nologo /nr:false /t:"Clean" ... /p:platform="x64" /p:configuration="Release" /p:VisualStudioVersion="16.0" /m
I believe I didn't encounter this issue primarily because I've not been supplying the /m parameter flag in my local builds.
HTH

I was able to locally reproduce the same build error by using this command-line on my dual core+HT = 4 logical CPU's laptop:
Invoke-OpenConsoleBuild /p:Configuration=Release /p:Platform=x64 /t:Build /m:4
Error:
"C:\source\terminal\OpenConsole.sln" (Build target) (1) ->        "C:\source\terminal\src\cascadia\TerminalAzBridge\TerminalAzBridge.vcxproj" (default target) (51) ->          C:\source\terminal\packages\Microsoft.Windows.CppWinRT.2.0.200316.3\build\native\Microsoft.Windows.CppWinRT.targets(164,13): error MSB4006: There is a circular dependenc        y in the target dependency graph involving target "ComputeGetResolvedWinMD". [C:\source\terminal\src\cascadia\TerminalAzBridge\TerminalAzBridge.vcxproj]

Hi @zadjii-msft -- congrats to you and the team for getting v1.0 released! 🥳 🎈
I know you folks have all been really busy, but I wanted to give a bit of a nudge to see if we can move this PR along a bit. What needs to happen for the review, and is there anything I might do to facilitate?

But if you leave the other StartupTaskState's empty, the app just doesn't launch on startup right? Won't cause any weird problems other than just ignoring your json setting when you try to set it?

Fortunately, this is something I made sure to specifically check in my testing 😄. If the setting's value is blank or empty, the application will start just fine - it will just use the default of false as the materialized value (via LayerJson).
Similarly, if the user has disabled the startup task via the Settings App or Task Manager, setting the config value to true will have no visible effect . I agree, a separate issue makes sense to track the UX for this scenario

Thanks for the feedback @zadjii-msft! I didn't have any issues with the requested changes, but I do want to understand the weak ref pattern you demonstrated a bit better. Is the capture of the weak ref just being explicit about what's happening, whereas the previous code does this implicitly?

Sorta, yea. Basically, the pattern above is used to say "I'm not sure that this will still be valid on the other side of the co_await. I'm going to get a weak_ref before the co_await that won't keep this alive. When this is method is resumed, I'll check that the weak_ref is still pointing to something valid. If it is, then we know that we can use this safely".
Otherwise, there's no good way of checking the value of this to make sure that it's a valid object on the other side of the co_await. The object might have been released, because this isn't an owning pointer.
It's a bit of a weird pattern that I'm still getting used to myself, so lemme know if that's not totally clear. There were a couple PRs a little while back that went through all of TerminalPage and tried to update it as best we could, but I'm not sure we got every case.

Sorta, yea. Basically, the pattern above is used to say "I'm not sure that this will still be valid on the other side of the co_await. I'm going to get a weak_ref before the co_await that won't keep this alive. When this is method is resumed, I'll check that the weak_ref is still pointing to something valid. If it is, then we know that we can use this safely".
Otherwise, there's no good way of checking the value of this to make sure that it's a valid object on the other side of the co_await. The object might have been released, because this isn't an owning pointer.
It's a bit of a weird pattern that I'm still getting used to myself, so lemme know if that's not totally clear. There were a couple PRs a little while back that went through all of TerminalPage and tried to update it as best we could, but I'm not sure we got every case.

This makes complete sense. It also makes sense why it's not 100% needed for the AppLogic members, but at least by doing it the "right" way here the application will be just that much more robust :smiley:
Thanks for taking the time to review this PR as well as for providing the great explanations and feedback! I'm happy to have had the opportunity to contribute to something I use and ❤ every day. The team is doing a lot of really exciting and great things - kudos and 🍻!


backports.lzma issue

It looks like setuptools is now complaining about backports.lzma, causing Travis.ci failures.
https://travis-ci.org/dask/dask/jobs/135465223
cc @wabu

This was fixed upstream. Closing.


ERROR 100 Unable to render instance groups for deployment - uaa.yml.erb

Used cf-stub at: https://docs.cloudfoundry.org/deploying/common/vsphere-vcloud-cf-stub.html
bosh create release and bosh upload work. bosh deploy creates the following error:
NOTE: Revised admin passwords to NOT have special characters.
Error 100: Unable to render instance groups for deployment. Errors are:
Unable to render jobs for instance group 'uaa_z1'. Errors are:
Unable to render templates for job 'uaa'. Errors are:
Error filling in template 'uaa.yml.erb' (line 236: undefined method +' for nil:NilClass) Unable to render jobs for instance group 'uaa_z2'. Errors are: Unable to render templates for job 'uaa'. Errors are: Error filling in template 'uaa.yml.erb' (line 236: undefined method +' for nil:NilClass)
Bosh Debug output:
D, [2016-09-22 02:36:41 #13569] [task:20] DEBUG -- DirectorJobRunner: Deleted lock: lock:deployment:WHCF uid: 1a6b31bf-49b8-4852-9149-8dda4ca0b9f4
I, [2016-09-22 02:36:41 #13569] [task:20] INFO -- DirectorJobRunner: sending update deployment error event
D, [2016-09-22 02:36:41 #13569] [task:20] DEBUG -- DirectorJobRunner: SENT: hm.director.alert {"id":"85958601-2a90-4180-8c45-72c56abe3b09","severity":3,"source":"director","title":"director - error during update deployment","summary":"Error during update deployment for 'WHCF' against Director 'bf9e34d8-325f-47f5-85bd-0b48d6f854ed': #","created_at":1474511801}
E, [2016-09-22 02:36:41 #13569] [task:20] ERROR -- DirectorJobRunner: Unable to render instance groups for deployment. Errors are:
Unable to render jobs for instance group 'uaa_z1'. Errors are:
Unable to render templates for job 'uaa'. Errors are:
Error filling in template 'uaa.yml.erb' (line 236: undefined method `+' for nil:NilClass)
Unable to render jobs for instance group 'uaa_z2'. Errors are:
Unable to render templates for job 'uaa'. Errors are:
Error filling in template 'uaa.yml.erb' (line 236: undefined method +' for nil:NilClass) /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/jobs/update_deployment.rb:175:inrender_job_templates' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/jobs/update_deployment.rb:84:in block in perform' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/lock_helper.rb:13:inblock in with_deployment_lock' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/lock.rb:53:in lock' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/lock_helper.rb:13:inwith_deployment_lock' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/jobs/update_deployment.rb:64:in perform' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/job_runner.rb:94:inperform_job' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/job_runner.rb:32:in block in run' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh_common-1.3262.9.0/lib/common/thread_formatter.rb:49:inwith_thread_name' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/job_runner.rb:32:in run' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/jobs/base_job.rb:10:inperform' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/jobs/db_job.rb:30:in block in perform' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-1.3262.9.0/lib/bosh/director/jobs/db_job.rb:78:inblock (3 levels) in run' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/eventmachine-1.0.4/lib/eventmachine.rb:1046:in block in spawn_threadpool' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:inblock in create_with_logging_context' D, [2016-09-22 02:36:41 #13569] [task:20] DEBUG -- DirectorJobRunner: (0.000080s) SELECT NULL D, [2016-09-22 02:36:41 #13569] [task:20] DEBUG -- DirectorJobRunner: (0.000052s) BEGIN D, [2016-09-22 02:36:41 #13569] [task:20] DEBUG -- DirectorJobRunner: (0.000237s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2016-09-22 02:36:41.085044+0000', "description" = 'create deployment', "result" = 'Unable to render instance groups for deployment. Errors
Unable to render jobs for instance group ''uaa_z1''. Errors...', "output" = '/var/vcap/store/director/tasks/20', "checkpoint_time" = '2016-09-22 02:36:37.831866+0000', "type" = 'update_deployment', "username" = 'admin', "deployment_name" = 'WHCF', "started_at" = '2016-09-22 02:36:37.831809+0000' WHERE ("id" = 20) D, [2016-09-22 02:36:41 #13569] [task:20] DEBUG -- DirectorJobRunner: (0.000806s) COMMIT I, [2016-09-22 02:36:41 #13569] [] INFO -- DirectorJobRunner: Task took 3.257565093 seconds to process.

i've seen this issue too with a PCF Ops Man 1.8 generated manifest (wanted to use a newer UAA for this particular CF instance)

The SCIM bootstrap user format changed
https://docs.google.com/spreadsheets/d/1C3VlW7BmUZ7b8o3zHwmbRxdOnSAP7nWA6Q8QKwiAj8s/edit#gid=2007038770
interestingly I didn't see this as deprecated in 3.6.0 (v13) but it is there in 3.6.1 (v13.1)


Bayesian optimization based adaptation

Hi,
Would you guys be interested in an implementation on the adaptative HMC scheme proposed in "Adaptive hamiltonian and riemann manifold monte carlo." ? I'm currently writing an implementation to go with AdvancedHMC.jl for my personal project, and if you guys are interested, I could contribute it.
AHMC involves fitting a Gaussian process, and running Bayesian optimization for maximizing the expected jumped squared distance. The former should require a GP or kernel learning library (my current implementation uses KernelFunctions.jl) and a simple global optimization algorithm like DIRECT (I'm using Nopt.jl).
Do you guys think it is worth adding considering the additional dependencies?

This looks like a great algorithm to have.
You're welcome to fire a PR to add this.
Regarding the extra depedencies, what I would suggest is we host codes for this algorithm in the src/contrib folder and make the dependencies optional; see examples here.
So there would be no real concern for extra dependencies.
I can offer more help once there is a PR :)


Added more swifty guard statements

I think travis not setupped properly.
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)

/home/travis/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `eval'

/home/travis/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `<main>'

@vadimeisenbergibm  @rfdickerson  I have addressed changes. Can you please review it.

We were recently told by the higher ups that we cannot accept anymore PRs until some legal issues are worked out. We'll let you know when those get resolved!

Thanks

Hey @codestergit we are now set up to accept contributions. However, you'll need to follow the process in CONTRIBUTING.md before we can accept any PRs from you.

@dfirsht
Updated the pull request to resolve conflicts.
Also sent the CLA.

Hey @codestergit, I'm not sure why Travis is failing, seems to be some internal error. In any case, I manually reviewed the code revisions and they all look good. I'm going to go ahead and merge this in.


orderBy failed when some item in the array don't have key

http://jsfiddle.net/pandada8/031shLq1/1/
maybe this worked on purpose……, then just close this issue.
BTW, if there is a value has same name with vusjs internel name, $value or  $index by example, what's the designed behavior ?
to reproduce: delete line 9 in js and the orderBy function normally

If the sub element is an array, orderBy doesn't traverse into it. This is working as intended.
Your object having properties like $value or $index is fine, because you have to access them via the v-for alias.

I don't want orderBy to traverse into it, actually in a more general
situation orderBy would fail when the item don't have a sortkey, and I
think orderBy could be more robust to such situation.
Evan You<EMAIL_ADDRESS>上午12:11写道：

Closed #1923 https://github.com/vuejs/vue/issues/1923.
—
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue/issues/1923#event-476465800.

But what would you expect to be the desired behavior? Should items with no sortKey be always at top? At bottom? To me the best solution is just make sure your data is formatted consistently...

fine……maybe we can make it more clear in the document


Fix the gluon deconv test

Also, refactor deconvolution into an op file and move some utilities around to make the op-files easier. Also, clang-format the op files.

TESTNOW


html api doc generator

@eukreign who needs to review this?

I think @NetOperatorWibby is working on some CSS for this and will have a feedback for me on what else needs to be done.

Yup, massive changes are coming to .tech so this will have to wait a bit.

I have been keeping a eye on the design changes and too be honest I have
not been happy with most of them --
Can someone PLEASE get a designer who has their eyes open ... Who signed it
off.
Pissed --
Mathew Waller
On Wed, Jul 25, 2018, 12:36 AM Lex Berezhny<EMAIL_ADDRESS>wrote:

Merged #1290 https://github.com/lbryio/lbry/pull/1290.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry/pull/1290#event-1751406185, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHrNEKZFnBidBjk_HNgzDUptWHFJJbDRks5uJ69sgaJpZM4VE260
.


Running a typescipt example fails the build due to old node version

Describe the bug
Build fails with node verison
2019-03-26T10:31:50.230Z [DEBUG] lyra.node: exports.runtimeAuthority = new URL('http://puppet.com/2016.1/runtime');
2019-03-26T10:31:50.230Z [DEBUG] lyra.node:                                ^
2019-03-26T10:31:50.230Z [DEBUG] lyra.node:
2019-03-26T10:31:50.230Z [DEBUG] lyra.node: ReferenceError: URL is not defined
2019-03-26T10:31:50.230Z [DEBUG] lyra.node:     at Object.<anonymous> (/home/travis/gopath/src/github.com/lyraproj/lyra/examples/ts-samples/node_modules/lyra-workflow/dist/pcore/TypedName.js:16:32)

https://travis-ci.org/lyraproj/lyra/builds/511412473?utm_source=github_status&utm_medium=notification
To Reproduce
Run a build
Expected behavior
sample_ts should run and not error.
Logs
https://travis-ci.org/lyraproj/lyra/builds/511412473?utm_source=github_status&utm_medium=notification
Environment (please complete the following information):
Travis
Additional context
URL became public after version 8 of node
https://stackoverflow.com/questions/52566578/url-is-not-defined-in-node-js#comment92070757_52566578
Node version in travis is v8
$ node --version
v8.9.1
The command "node --version" exited with 0.

https://travis-ci.org/lyraproj/lyra/builds/511527358

Can this be resolved by telling Travis to use a later version? https://docs.travis-ci.com/user/languages/javascript-with-nodejs/#specifying-nodejs-versions

Yes, done with
nvm install 11
nvm use 11

in #194


[FEATURE] Improve Docker Compose file

Description
Make the Docker Compose more standard and complete according to the project by including the LinkFree image (service) building on the fly. Currently, we are only using the  Mongo image just to get for DB connection which is not good. Changes will connect the App and DB internally.
Also after this, a contributor doesn't need to step into the environment locally, everything will run inside containers. After this, the whole project setup will need just two-step

Clone the repo
Then docker compose up

Great idea 👍  we can include this in the new docs too

How would you do development with everything running in a container? Would you have to make changes then rebuild the container?

How would you do development with everything running in a container? Would you have to make changes then rebuild the container?

Great question. We will use bind mounts (Volumes) so that we don't have to rebuild the images.

Great question. We will use bind mounts (Volumes) so that we don't have to rebuild the images after every iteration.

So there is a link between the src files outside & inside the container.
How are you going to handle package.json & node_modules?
Would any install or update require a rebuild?
I am trying to think through my dev workflow to figure out where the points of maximum confusion or breakage would be.

Sorry missed the comment.
Yes, we will do it that way. I think we don't need to worry about the package.json & node_modules Next handles it wonderfully, and if there is some issue we can improve over time with your and the community's contribution.

Would any install or update require a rebuild?

I don't think so we run so that, if it's, we will add that in the docs to run docker compose up --build

I think we don't need to worry about the package.json & node_modules

So you will do an npm ci inside the container & it will have its own node_modules folder?
I was worried about OS specific dependencies if you are running Windows or MacOS outside with Linux inside the container.

I think we don't need to worry about the package.json & node_modules

So you will do an npm ci inside the container & it will have its own node_modules folder? I was worried about OS specific dependencies if you are running Windows or MacOS outside with Linux inside the container.

Yes, for now, I am less worried about that, because I have never faced any problem with a web application. Because we can improve with time. Thank you for all questions, helps to brainstorm

if I understand the concern correctly, I do not think it is an issue because where the dependencies are installed is where the app will run - yes people people try to do both, run the container and run it outside there will be an issue, but I think they need to select one of the options to run the project not both. Hope I understood correctly?

I just thought up another issue.
How do you run playwright tests with this compose file?
Playwright runs its own dev server, but is dependent on having mongo running.

oh that is a good question @dan-mba 👍 it is something we would need to look into, maybe running playwright on another port - yes please raise a new issue Dan, as this can be a further improvement

if I understand the concern correctly, I do not think it is an issue because where the dependencies are installed is where the app will run - yes people people try to do both, run the container and run it outside there will be an issue, but I think they need to select one of the options to run the project not both. Hope I understood correctly?

Exactly. That's the whole point of Compose, we need not care about our local machine environment and OS-specific dependencies, everything is isolated within the container.
Also, OS specific problem arises when using pre-build images (not building them on the fly)


Automatically resume collecting the data in case of temporary Bluetooth connection loss

Hi,
I had gone through your source code, am developing one such application. All i want to know is how efficient is to implement a feature like when the user goes out of the Bluetooth range and comes back again to the range, if the service is running the background it should automatically start collecting the data without intimating the user.
How feasible is the requirement, else if you guide me how to go about on it, i would try implementing it.

It is feasible. One would need to handle Bluetooth errors on https://github.com/pires/android-obd-reader/blob/master/src/main/java/pt/lighthouselabs/obd/reader/io/ObdGatewayService.java and play with the service lifecycle to act accordingly.

So its basically when even the connectivity is lost, (i.e) in ObdGatewayService.java, inside executeQueue(), catch block will be called. But if i call the method startService() at that time, some times AT Z command fails and comes into the catch block. So i should ignore this condition for AT commands alone?

This is most probably due to the explicit delay in sending commands.

@vivek40 is there a PR coming?


How to set a custom compiler

Don't have much clue about Bazel
$ cat .bazelrc.local
build --config debug
build --config gnulike
build --compiler clang++

$ bazel build //...
ERROR: /home/johannes/.cache/bazel/_bazel_johannes/aad01079729eb077ed623d0aacdac2cd/external/local_config_cc/BUILD:47:19: in cc_toolchain_suite rule @local_config_cc//:toolchain: cc_toolchain_suite '@local_config_cc//:toolchain' does not contain a toolchain for cpu 'k8' and compiler 'clang++'.
ERROR: Analysis of target '//style:style' failed; build aborted: Analysis of target '@local_config_cc//:toolchain' failed
INFO: Elapsed time: 0.548s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (38 packages loaded, 723 targets configured)

:arrow_forward: https://docs.bazel.build/versions/master/tutorial/cc-toolchain-config.html
:arrow_forward: https://docs.bazel.build/versions/master/cc-toolchain-config-reference.html

You use the CC/CXX env vars:
robin@machine:~/code/hastur$ CC=clang-11 CXX=clang++-11 bazel build dom
INFO: Analyzed target //dom:dom (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /home/robin/code/hastur/dom/BUILD:3:11: Compiling dom/dom.cpp failed: (Exit 1): clang-11 failed: error executing command /usr/bin/clang-11 -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -fcolor-diagnostics -fno-omit-frame-pointer -g '-std=c++0x' -MD -MF ... (remaining 32 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox clang-11 failed: error executing command /usr/bin/clang-11 -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -fcolor-diagnostics -fno-omit-frame-pointer -g '-std=c++0x' -MD -MF ... (remaining 32 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
In file included from dom/dom.cpp:1:
./dom/dom.h:4:2: error: "boom!"
#error "boom!

robin@machine:~/code/hastur$ CC=gcc-10 CXX=g++-10 bazel build dom
INFO: Analyzed target //dom:dom (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /home/robin/code/hastur/dom/BUILD:3:11: Compiling dom/dom.cpp failed: (Exit 1): gcc-10 failed: error executing command /usr/bin/gcc-10 -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g '-std=c++0x' -MD -MF ... (remaining 32 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox gcc-10 failed: error executing command /usr/bin/gcc-10 -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g '-std=c++0x' -MD -MF ... (remaining 32 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
In file included from dom/dom.cpp:1:
./dom/dom.h:4:2: error: #error "boom!"

Ok it works when defining both CC and CXX :woman_shrugging:


Use cloudpathlib for the storage API?

@cisaacstern and I were wondering what was the rationale of the lithops project making your own implementation for the lithops cloud proxy storage API.
There are other libraries that deal with this problem already - why not use one of them?
In particular one I like is cloudpathlib, which provides classes that deliberately follow the same interface as the python pathlib standard library module, but for different cloud storage providers. It seems to me that your lithops.storage.CloudFileProxy class could possibly just be replaced with cloudpathlib.CloudPath?

Hi @TomNicholas, nice catch! Just note that this API has always been treated as a research prototype due to the ease of use provided by Lithops. In Lithops, we've always pursued simplicity in cloud usage. The main API has consistently been the Storage API, but we've realized that users who want to use Lithops can easily transition to an API they already know, that's why we implemented it.
You may have noticed that we also implemented the multiprocessing.Process API. Other projects like Ray or Dask have also implemented similar functionalities, but this doesn't mean we cannot implement our own. There are likely tens of frameworks that do similar things, but with Lithops, it's quite easy to implement and allows users to change just one line of code without learning a new API.
When we began developing the cloud proxy internally in 2019, the framework you mentioned didn't exist. Our intention was simply to provide more APIs familiar to users for adoption. I agree the API you mentioned looks good, but in any case, there are probably more than one API attempting to achieve the same goal. We developed it, but our focus has always been on the main Storage API and , of course, the compute api

Thanks for the quick response @JosepSampe !

When we began developing the cloud proxy internally in 2019, the framework you mentioned didn't exist.

That's totally reasonable, but I'm not clear from your answer whether you would be for or against using cloudpathlib now?

users who want to use Lithops can easily transition to an API they already know, that's why we implemented it.
I agree the API you mentioned looks good, but in any case, there are probably more than one API attempting to achieve the same goal.

These are the reasons I like cloudpathlib! I notice that your existing storage API interface is inspired by the os module in the python standard library, so that it is familiar to users. The cloudpathlib CloudPath object follows the interface of the Path object in the pathlib module in the python standard library, so that it is familiar to users!
The other reason it's nice is that the two projects seem to care about exactly the same scope: abstracting away details of different cloud providers by providing a common interface, but not trying to extend that interface to work in non-cloud contexts. It seems to me that what lithops aims to do for cloud serverless APIs cloudpathlib aims to do for cloud storage APIs, so the two projects might therefore fit naturally together.

Thanks for @TomNicholas for voicing the question and @JosepSampe for the fast engagement!
The only thing I think I'd add, as a relative newcomer to Lithops, is that the documentation placing a (roughly) equal emphasis on the Storage API alongside the Compute API has been hard for me to understand.
Perhaps I misunderstand the focus of the project, but from my naive newcomer perspective, it feels to me that in 2024 at least, the truly novel and unique contribution of Lithops is the Compute API, which other packages such as Dask etc do not offer a replica of (even if they try to solve similar user problems, they do it in different ways, with different tradeoffs).
I am not aware of another fully OSS Python project that offers a seamless abstraction over both local multiprocessing and cloud-agnostic serverless parallel data processing. This uniqueness and the elegance of the Compute API implementation is what had lead me to recommend we adopt Lithops as the core framework for a contract I am currently working on.
By contrast, to me it has seemed that the Storage API mostly exists as an enabler of the uniqueness of the Compute API... (am I misunderstanding, for example, that it's used to facilitate storage monitoring?)...
Have I misunderstood the relationship of these components?

After developing several workflows with Lithops I think it would be a great addition. In my opinion, one of the most painful things with lithops is the Storage layer, not because of the API, but because you need to work with files after downloading them to a remote worker, and that means using the OS storage api.
One thing I've talked about with @danielBCN was the ability to have some sort of abstraction or object that you can instantiate around, this object would be a lazy/transparent representation of some path in object storage.
At some point i've also tried to create an adapter between cloudpathlib and lithops: https://github.com/abourramouss/cloudpathlib-lithops-adapter

@abourramouss @cisaacstern @TomNicholas I understand there might be different API for Storage layer. We implemented our own in Lithops, you suggest another way. What is rationale for your suggestion? Do you have some specific use case where existing API doesn't work? Or it just a matter of convenience? In any case, even we implement another Storage API then all changes should be backward compatible and Lithops will need to have 2 Storage APIs... We can't just replace existing with new one and that's it

Hi, IMO this is quite straightforward: first, it is true that the storage API was implemented when smart_open or cloudpathlib did not exist yet, and now it would be costly to refactor and get an equivalent functionality; but if someone needs some cloudpathlib functionality that lithops storage does not implement, it can be installed it in the runtime and used without any issue in the code, both can coexist and be used when needed for each specific use case

What is rationale for your suggestion?

My rationale is (a) convenience for the user (pathlib is nicer to work with than os) and (b) convenience for lithops developers in the long term (not having to maintain the Storage Layer yourselves). There may be other advantages too.

In any case, even we implement another Storage API then all changes should be backward compatible and Lithops will need to have 2 Storage APIs... We can't just replace existing with new one and that's it

Of course there is always a trade-off with any refactoring. But if we felt that this idea would really save effort in the long term, it's not impossible to make a switch - you just have a (long) deprecation cycle. I.e.

add the path-like implementation of the storage layer,
use the new storage layer internally,
add DeprecationWarnings when importing the original storage layer API,
then after a sufficiently long time for the users to make the change (e.g. 6-12 months for such a big change) you actually remove the original API.

Totally up to you if you (or others) think this is worthwhile, but it can be done without keeping two APIs around indefinitely.


RangeError due to Analyzer plugin

I don't know if this is caused by the Angular Analyzer plugin but as soon as I add this plugin to the Analyzer options I get various error messages like:
RangeError (byteOffset): Invalid value: Not in range 0..77956, inclusive: 101728
#0  _ByteDataView.getUint32 (dart:typed_datapatch/dart:typed_data/typed_data_patch.dart:4021)
#1  BufferContext._getUint32 (package:front_end/src/base/flat_buffers.dart:72)
#2  BufferContext.derefObject (package:front_end/src/base/flat_buffers.dart:54)
#3  StringReader.read (package:front_end/src/base/flat_buffers.dart:662)
#4  Reader.vTableGet (package:front_end/src/base/flat_buffers.dart:644)
...

RangeError (index): Invalid value: Valid value range is empty: 0
#0  List.[] (dart:core-patch/dart:core/array.dart:133)
#1  _LibraryResynthesizer.createUnitResynthesizer (package:analyzer/src/summary/resynthesize.dart:1025)
#2  _LibraryResynthesizer.buildLibrary (package:analyzer/src/summary/resynthesize.dart:963)
#3  SummaryResynthesizer.getLibraryElement.<anonymous closure> (package:analyzer/src/summary/resynthesize.dart:256)
#4  _HashVMBase&MapMixin&&_LinkedHashMapMixin.putIfAbsent (dart:collection-patch/dart:collection/compact_hash.dart:275)
...

Here is my analysis_options.yaml:
analyzer:
  strong-mode: true
  plugins:
    angular:
      enabled: true

    # foo:
    #   enabled: true

linter:
  rules:
    - cancel_subscriptions
    - close_sinks
    - hash_and_equals
    - iterable_contains_unrelated_type
    - list_remove_unrelated_type
    - test_types_in_equals
    - unrelated_type_equality_checks
    - valid_regexps

If I add a dummy plugin to it like foo I get no errors and the plugin (Angular Analyzer) works again.
angular_analyzer_plugin:
    version: "0.0.12"

analyzer:
    version: "0.31.0+1"

dart:
    version: "2.0.0-dev.20.0"

--------------------------------
macOS:
    version: "10.12.6"

@MichaelRFairhurst Sounds like this might be for you.

Hey @akaufmann, we have a workaround that should get you unblocked:
rm ~/.dartServer/.analysis-driver/*
This should not, unfortunately, ever be required to do. But in the meantime, it would be useful if we can verify that running this solves your problem, or not.
I think we've heard other reports on this and its cause is still a mystery, @scheglov did you find anything on this front?

No, I still don't know why these happen.
However in this case it is a low-level flatbuffer error, and it has much higher chance to be a race condition damage. So, if the most recent Angular plugin is used, the cache is cleared, and analysis server restarted, then the problem might be fixed.

Hi @MichaelRFairhurst, after I removed the files, the first run of the analyzer didn't cause any errors and everything works as expected but the second run of the analyzer caused the errors again.

Ok, super weird! After the next restart the foo plugin doesn't help anymore but if I rename foo to bar it will work again after the next restart and all other restarts. Did you save the plugin names in a file under the .dartServer/.analysis-driver folder?

Yes, .dartServer/.analysis-driver is the cache that is used in Dart Analysis Server to store intermediate and final results of Dart and Angular analysis. It is expected to be big, but not too big (up to 1.125GiB, then we start removing older results).

Thanks for all the research, @akaufmann. I'm going to be publishing a new version of the plugin shortly, once that's done I'll give you some upgrade steps and we can see if that fixes it.
You may also want to try an older version of the SDK, if an upgraded plugin doesn't help, and we still haven't figured it out by then. Hopefully it doesn't come to that!

@MichaelRFairhurst Should this issue be closed?


Effect gravity is not correctly displayed in multiplayer.

Minecraft version
1.20.1
Describe the issue
Running this mod on Multiplayer, other players are not rotated in accordance to their effect-induced gravity. This results in players appearing stuck in the floor.
Steps to reproduce

Set up a multiplayer server (this is expected to also occur in LAN worlds, but is untested)
Have two players join the server
Give Player A a potion effect such as Up Gravity.
See from the Player B's perspective that the orientation of Player A has not changed.

I cannot reproduce this issue

It may be a mod compatibility issue? Can you backup the world, remove all other mods and test again?

Can you provide some video about the issue?

I see. I can reproduce now. Video not needed now.

Fixed in 1.1.1


Feature Request: Packaging system

Figure an issue should probably be open for this. The plan is to implement some kind of packaging system for toaruos. The details of how it will work are still not complete, but I'm fairly certain we'll need to be able to read/write some archive format in order to make it easier to bundle files together, tar is the obvious first choice.
I'm currently trying to port libarchive (http://www.libarchive.org/) to toaruos and it's going okay I guess.

Problably dependent on the Userspace interface of #44.

While having repositories over a network link would be nice (and an ultimate goal) I don't think it's really a strict dependency. I'm thinking in its first iteration the only kind of repository it will support will be from a filesystem. That could just be somewhere like /usr/share/repo or it could be on a CD that is mounted in a similar location.

I'm going to link into merging the libarchive branch.
We can actually download packages or binaries with the current web stack, though it still needs a lot of work:

This issue was moved to PoisonNinja/ToyOS#2

I think get-py now pretty much covers this, right?

get-py is a temporary implementation. I think I'll leave this issue open until we have something more complete, which I plan on working on this week.


Unexpected character '@'

Failed to build
{ Error: (client) ./pages/index.tsx
Module parse failed: Unexpected character '@' (8:0)
You may need an appropriate loader to handle this file type.
| import { Emerge, Toolbar, Button } from '../utils/recoilClient';
|
| @inject('appStore')

Using next-typescript as a plugin - thinking it has something to do with that, as running "next build"  locally works perfectly. I also have the "experimentalDecorators" flagged true on my tsconfig.json.
Or there is an issue with the .next "pages" folder handling .tsx files and using decorators when deploying to .now

this might not fix it, but sometimes deps can be mismatched between server and client. It's a long shot but try to drlete your node_modules folder completely and yarn or npm install to simulate a fresh build like on now servers. If it fails building locally after, then it means youre missing some dep from your package.json, or inconsistency with yarn.lock and deps

Thank you for the input! I cleaned the "node modules" folder, did a fresh npm install and checked to see if my local build worked and it did. Sadly deploying with "now" still returns the following errors:
`> Initializing…

Building
▲ npm install
✓ Using "package-lock.json"
⧗ Installing 25 main dependencies…
✓ Installed 1102 modules [8s]

<EMAIL_ADDRESS>preinstall /home/nowuser/src
git clone https://www.github.com/jisaac89/recoil.git
warning: redirecting to https://github.com/jisaac89/recoil.git/
<EMAIL_ADDRESS>build /home/nowuser/src
rimraf ./.next && next build
Failed to build
{ Error: (client) ./pages/about.tsx
Module parse failed: Unexpected character '@' (8:0)
You may need an appropriate loader to handle this file type.
| import { Emerge, Toolbar, Button } from '../utils/recoilClient';
|
| @inject('appStore')
| @observer
| class Index extends React.Component {
@ multi ./pages/about.tsx
at /home/nowuser/src/node_modules/next/dist/server/build/index.js:207:31
at runWithDependencies (/home/nowuser/src/node_modules/webpack/lib/MultiCompiler.js:154:4)`

I had another typescript project with react that successfully deployed with now. The only difference between the two is that the one that fails uses next js with next-typescript instead of webpack and ts-loader.

Fixed**, pulled a rookie move - don't put tsconfig.json on the .gitignore =)


Show valid types in SceneTreeDialog

When picking node for Node/NodePath property, allowed type is now displayed at the top:

Multiple types:

Closes #62483

You have shadowing issues 🙃

Thanks!


Add cssnano to the allowed dependencies

cssnano now ships its own types, so this is setting the infrastructure up to deprecate @types/cssnano by adding cssnano to the allowed dependencies.

For posterity's sake, this PR is for DefinitelyTyped/DefinitelyTyped#59155


Missing docs on how to format a library mapping file properly (LIBRARY_FILE input)

Hello! 👋
I decided to open this issue after trying to figure the proper format for the libraries mapping file (accepted by this GHA) by myself.
I've followed the source code from Gradle plugin, but not sure what I'm missing. On my case, I'm transforming my project's dependencies - generated by the well established Ben Manes plugin for Gradle - into something that AppSweep would accepts

Example of Workflow run (library mapping attached on Workflow artefacts)
Related build that could not be analyzed by AppSweep

Hi @titze, thanks for your response!

Do you mind moving this question to our Community?
For sure not! I'll do it asap 😄

Is it possible for you to use the gradle task?
It is doable for sure; my point is that I already have an artifact (APK) generated as part of my pipeline, and since it is possible to integrate with AppSweep with a Github Action, I'd like to enrich the Security analysis over such artifact with metadata I compute/provide rather than installing a Gradle plugin to compute the metadata.

A concrete use case would be : suppose I use some (3rd) private project dependencies that eventually I don't want to disclose (or I can't disclose). In this case

The AppSweep Gradle plugin could allow me to flag such dependencies via the public plugin extension or
I can provide the list of libraries I want to analyze by myself (focusing on open-source ones)


Add double data type

Closes #498

Codecov Report

Merging #1208 into master will decrease coverage by 0.01%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master    #1208      +/-   ##
==========================================
- Coverage      72%   71.98%   -0.02%
==========================================
  Files          35       35
  Lines        5598     5605       +7
==========================================
+ Hits         4031     4035       +4
- Misses       1567     1570       +3

Impacted Files
Coverage Δ

src/Phinx/Db/Adapter/PdoAdapter.php
87.43% <100%> (+0.06%)
:arrow_up:

src/Phinx/Db/Adapter/MysqlAdapter.php
97.69% <50%> (-0.15%)
:arrow_down:

src/Phinx/Db/Adapter/SQLiteAdapter.php
86.54% <50%> (-0.12%)
:arrow_down:

src/Phinx/Db/Adapter/PostgresAdapter.php
92.65% <50%> (-0.14%)
:arrow_down:

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 6d93070...68d1b54. Read the comment docs.

This is basically a copy of #1069 but with the signed column

Do we want to add any (regression) tests for this new feature?

Sure, give me a sec

Gonna have to leave this till tomorrow unfortunately, should have updated by 1:30 BST tomorrow

How's that? Sorry if I haven't done anything properly.
Also, what should be done about SQL Server? Don't think they support doubles

Sorry for the late reply. I think you could use double precision or float for SQL Server. See:
https://docs.microsoft.com/en-us/sql/t-sql/data-types/float-and-real-transact-sql

The synonym for double precision is float(53).

@chinpei215 Should we continue here?

What happened with this PR?

@piotr-cz there are conflicts with the master branch. If you want to continue it, please open a new PR. I'll close it as it is dormant now, and cannot be merged.


Updated Jenkins pipeline and underlying Docker image

This PR comprises four improvements:

The Jenkins pipeline now contains four steps to verify

that no Spotbugs checks fail
that the Javadoc documentation can be generated
that all tests pass
compliance with Google's Java Style Guide

The Docker image steady-pipeline is now based on maven:3-adoptopenjdk-11, thus, all Steady modules are compiled and tested with Java 11.
Several Maven plugins and dependencies have been updated.
Javadoc documentation has been fixed.

TODOs

[x] Tests
[x] Documentation

@serenaponta Please focus your review on the non-Java files (which "only" contain Javadoc changes)


Changed fromTaggedBase64 to return bytes instead of UTF-8

fromTaggedBase64 was returning the value as UTF-8, but that's not always possible, so changed it to returning a byte array, and added another function for cases where the value is expected to be UTF-8.
Closes https://github.com/EspressoSystems/tagged-base64/issues/21

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 75.843%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
135

Relevant Lines:
178

💛  - Coveralls


FIX: global declarations were error nodes

Small error in the grammar, the hare compiler allows implicit type in globals. Just changed the type param to be optional(seq(":", $.type)).
I also regenerated the bindings, not sure what the general convention for pr's is.

I also regenerated the bindings, not sure what the general convention for pr's is.

In general, PRs (and certainly commits) should stick to their declared purpose. Unless needed, use tree-sitter generate --no-bindings (and be careful about using pre-release commits! always stick to the latest release) and leave binding updates to a dedicated "chore" PR.


Sitemap & URL Update

Description
This PR based on this file assigned to me https://docs.google.com/spreadsheets/d/1ozKp4tBdMCvzA6ysEz2-URwYtccJowS1Zxiu83TSTbg/edit#gid=0 by @felixwidjaja
This PR will change urls and content structure and also add sitemap
Sitemap urls:

/sitemap.xml

/sitemap-terms.xml

/sitemap-community.xml

/sitemap-examples.xml

/sitemap-docs.xml

How Has This Been Tested?

I test it by visiting new urls

I can't test the redirections until this commit is in netlify staging

How are existing users impacted? What migration steps/scripts do we need?
User will be redirect to all new urls
Checklist:
I have:

[x] restructure content for seo purpose
[x] add redirections
[x] create sitemap

@ronggur there are some merge conflicts here - can you fix those and I'll look it over/approve it?

@thomcrowe would you please check again, I already rebase the brach

@ronggur Something seems to have happened to the ordering in the docs in this PR. About half of them are nested under the Documentation but they should be top-level.

@DailyAlice let me know what needs to change. I am referencing this document for this PR https://docs.google.com/spreadsheets/d/1ozKp4tBdMCvzA6ysEz2-URwYtccJowS1Zxiu83TSTbg/edit#gid=0

@ronggur , I'm not sure what should change, the urls look fine to me, but if you look at the deploy preview, some of the pages with URL changes end up nested under Documentation on the docs page, and some don't.

Ideally, they wouldn't be nested and the table of contents would look like it currently does.

Or if nesting is the new thing, the Templates and Workflows should also be in their places in the toc under Hardware Data and above Setup.
Also, the Concepts page was removed in a previous PR, so should also be removed from this one.

@DailyAlice could you please check again https://deploy-preview-118--festive-goldwasser-489842.netlify.app/

Hey @ronggur, this looks good, except that the first entry in the toc is no longer there. It seems there is no way to get back to the documentation landing page after navigating away from it. Can we add that back?

@DailyAlice Please check again https://deploy-preview-118--festive-goldwasser-489842.netlify.app/docs/

Yep. all looks good, should be good to merge


Static lib: changes to make Core, WebSocket and Cryptalgo lib to build in static as well

Can you revert back to the original add_library calls. Then add all optional source files with target_sources to the desired library.
Thank you

done


ssh: test config to limit to deployer ip address

This works! It limits the ssh access to the computer where it is deployed from.
Onward to future deployments without those very special emails... :foot:  :email:
cc @lisejolicoeur @milroy let's make sure to make these changes in the netmark deployment.


RHOAIENG-766 dashboard config

Adding dashboard configuration content from https://ai-on-openshift.io/odh-rhoai/configuration

closing this MR - I will download  Amy's files and create a new MR for these updates


Migrate to eslint 2

For #31

Two failing travis builds are for node versions < 4 that don't like the back ticks

Keep the normal quotes in for now. This module still supports older versions of Node. The plan is to stop doing that, but it's not implemented yet.

:+1: reverted

Thanks! Landed in bd415cbebb3c6d4d25447206b92eecee0ff302dc


[Feature]: Pixel snapping / devicePixelContentBox

Is the feature relevant to the Firefox PDF Viewer?
Yes
Feature description
To avoid pixel aliasing/blur due to pixel snapping as described at https://web.dev/articles/device-pixel-content-box#pixel_snapping, you might want to use devicePixelContentBox as described at https://web.dev/articles/device-pixel-content-box#devicepixelcontentbox
I haven't checked which projects that use PDF.js have fractional pixel values, but that might happen.
(Also please check whether devicePixelRatio is being used correctly as described at https://web.dev/articles/device-pixel-content-box#pixel_perfection so that devicePixelRatio and devicePixelContentBox work together correctly.)
Other PDF viewers
No response

We're already, since many years, using devicePixelRatio as can be seen here:

https://github.com/mozilla/pdf.js/blob/77c7ec6927c0263a0ed2be2b0aae46b655855239/web/ui_utils.js#L79-L103
https://github.com/mozilla/pdf.js/blob/77c7ec6927c0263a0ed2be2b0aae46b655855239/web/pdf_page_view.js#L1012-L1046

However, using devicePixelContentBox would apparently require introducing ResizeObserver as part of rendering and that's not really planned as far as I'm aware (since that might introduce various other issues/complications).

This demo linked from the aforementioned article implements a check for whether ResizeObserver is supported. Old browsers that don't support it can skip that adjustment.
Or do you mean other potential issues/complications?


⚠ Bofrost.fr has degraded performance

In 76fe6dd, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 845 ms

Resolved: Bofrost.fr performance has improved in 795d716 after 8 minutes.


Add new strings to GodSVG.pot in advance of global menu PR

I also snuck in the new signal in GlobalSettings.gd.

I think we need to do "Move to (Relative) and "Move to (Absolute)" to spare ourselves from 20 translations.

I don't think this pull request is relevant after #711. I'll still keep it as a reminder for the keybinds_changed signal (which is irrelevant as all shortcuts display only in things like ContextPopup and probably tooltips in the future, both of which will are generated on the spot).

Closing as superseded by #799.


VSCode command for showing Comments panel

When an extension adds comments, the extension should be able to show the Comments panel to bring users' attention to them.
It will be very helpful to have something like VSCode command workbench.actions.view.comments that would show up the Comments panel.

workbench.action.focusCommentsPanel was added to support focusing into the Comments Panel, it only works when there is comment controller registered.


How to debug causing 100% CPU usage?

Periodically I see 100% CPU usage by S1N1. When I try to stop Impress (impress stop) I see something like this:

root@server:/ias# impress stop
Impress Application Server 0.4.26
Stopped
root@server:/ias# impress status
Impress Application Server 0.4.26
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     31802 13.8 15.0 1481060 308980 pts/1  Rl   Oct28 113:51 impress S1N1

As you can see the process S1N1 does not unloaded from memory after "impress stop". And still 100% CPU usage. After reboot everything is fine, but after some time the problem recurs.
Is no info in log files about this - error.log, warning.log, slow.log are empty.
How can I understand what is wrong?
Thanx.

@dmitrystas Hi! As I know (in my case - 0.4.20, latest version with low memory consumption), you need to stop the slave processes manually. The first step implies that you get PID of slave processes and the second step is to gracefully stop them. Example:
kill -15 $(ps aux | grep impress | awk '{if(NR>1)print $2}') * the result may depend on the shell

@johnbizokk, Hi!
Youre right, it will help with service stopping. But how to understand what the cause of the problem? For examle in "clean" nodejs (without Impress) we can use V8 Profiler node --prof app.js`
And what about Impress? How can I catch the 100% CPU usage in Impress?

I believe this is fixed in 1.x


Add unit tests for the point feature.

Fixed some issues with the pointFeature:

Setting the position on construction resulted in different behavior than setting it afterwards.
Setting the clustering on construction allowed non-default values, but during the setter would only allow defaults.
If set, the clustering could not be changed except by unsetting it and resetting it.
The maximum radius of any point is used when deciding where to search for points, but it was potentially not calculated until after it was used.

Made some improvements:

The position function wraps the position in another function to handle clustering.  If the position is not a function, then only one function call is made rather than two.
Removed the unused internal _boundingBox function from the pointFeature.
Added some comments about when you would want to use a different primitiveShape with the gl point feature.

I think this PR illustrates why we want to have unit tests on everything -- I discovered a few bugs and inconsistencies while writing them that weren't exposed in our various test cases.

Codecov Report

Merging #684 into master will increase coverage by 1.86%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #684      +/-   ##
==========================================
+ Coverage   92.02%   93.89%   +1.86%
==========================================
  Files          84       84
  Lines        8857     8856       -1
==========================================
+ Hits         8151     8315     +164
+ Misses        706      541     -165

Impacted Files
Coverage Δ

src/gl/pointFeature.js
100% <100%> (+7.29%)
:arrow_up:

src/pointFeature.js
100% <100%> (+42.06%)
:arrow_up:

src/util/wigglemaps.js
49.77% <0%> (+40.35%)
:arrow_up:

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 31ddb36...03fea0f. Read the comment docs.


Schema Support

Cedar Schema allows Actions to be members of Action Groups. Action Groups are useful for authorizing multiple Actions with a single policy.
Here is an example Cedar policy file:
@id("Any user can View")
permit(
  principal is User,
  action == Action::"View",
  resource
);

@id("Owner can Edit")
permit(
  principal is User,
  action == Action::"Edit",
  resource
) when { resource.owner == principal };

@id("Users with isAdmin=true can Delete")
permit(
  principal,
  action in Action::"AdminActions",
  resource
) when { principal has isAdmin && principal.isAdmin };

And here is a corresponding Cedar schema file:
entity User {
  isAdmin?: Bool
};

entity Image {
  owner: User
};

action AdminActions;

action View in [AdminActions] appliesTo {
    principal: [User],
    resource: [Image]
};

action Edit in [AdminActions] appliesTo {
    principal: [User],
    resource: [Image]
};

action Delete in [AdminActions] appliesTo {
    principal: [User],
    resource: [Image]
};

Currently, there is no way to use a Cedar Schema in cedar-policy-rb, so the Users with isAdmin=true can Delete policy cannot be used.
Schema can also be used to validate the structure of Entities data during authorization.
I have implemented Schema support by wrapping the rust Schema class with a ruby one, adding a schema accessor on the ruby Entities class, and passing the schema from the ruby Entities class to the rust Entities::from_json_value method.
Are you open to receiving a pull request for a feature like this?

Sure, the pull request is welcome.


Can't left-click on lightbulbs anymore

Issue Type: Bug
Left-clicking still works in the stable build, so I assume this wasn't intentional.
Steps to reproduce:

Place the cursor on any code with a quick fix available.
Attempt to left-click on the lightbulb.

Notes:

Right-clicking still works.

VS Code version: Code - Insiders 1.35.0-insider (6964233e81c68f5a5f34e7eb1da0836e1d539f14, 2019-05-29T05:18:15.943Z)
OS version: Windows_NT x64 10.0.17134
Extensions: none

@sbatten I believe this is the same problem that was discussed in #71580

@mjbvz Yea that one won't get closed so let's keep this one open to be verified since this has now been fixed.


Icons Not Loading On v3 When Using ISR

Environment

Operating System: Darwin
Node Version:     v22.7.0
Nuxt Version:     3.14.159
CLI Version:      3.15.0
Nitro Version:    2.10.4
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      default
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Is this bug related to Nuxt or Vue?
Nuxt
Version
v3.0.0-alpha.9
Reproduction
No Caching/ISR: https://preview.live-for-today.com - Icons All Load
Caching/ISR: https://live-for-today.com - Some Icons Fail To Load
Description
Dev: localhost - Icons All Load
No Caching/ISR: https://preview.live-for-today.com - Icons All Load
Caching/ISR: https://live-for-today.com - Some Icons Fail To Load
On the deployment with Caching/ISR I get this warnings in the console, i.e.:
[Icon] failed to load icon heroicons:chevron-double-left [Icon] failed to load icon heroicons:chevron-double-right
I've installed all of the icon dependencies I'm using.
Seems to be some conflict as soon as I'm using caching.
Additional context
No response
Logs

@antfu Would you have an idea about this?


regression: "Cannot document a package where a library and a binary have the same name" error when [[bin]] has "doc = false"

STR
$ tree src
src
├── bin
│   └── foo.rs
└── lib.rs
$ cat src/bin/foo.rs
fn main() {}
$ cat src/lib.rs
// empty

[package]
name = "foo"
version = "0.0.1"
authors = ["japaric"]

[[bin]]
doc = false
name = "foo"
path = "src/bin/foo.rs"

$ cargo doc
Cannot document a package where a library and a binary have the same name. Consider renaming one or marking the target as `doc = false`

Version
cargo 0.0.1-pre-nightly (0e42b4d 2015-03-25) (built 2015-03-25)

However, cargo doc works if I use yesterday nightly: cargo 0.0.1-pre-nightly (e689383 2015-03-16) (built 2015-03-16) or an older nightly.
cc @alexcrichton

I believe this will be fixed by https://github.com/rust-lang/cargo/pull/1453 transitively


[Bug?] subtle influence of/by preact "render": wrong effect function invoked

First of all: thank you very much for this module!
But I have the impression, that it does not work properly - because of a subtle (but really nasty) influence of (or by) the preact "render" function
Consider the following code (do not ask for any deeper sense, I have tried to extract the essence of a much larger application with dynamic plugins):
  import { render, html, effect }   from 'preact-with-htm'
  import { observable, Observable } from 'preact-observables'

  const global = (new Function('return this'))()

  global.Store = observable({
    Value:0
  })

  class Hugo extends Observable {
    _Store = Object.create(null)
  }

  const hugo = new Hugo()

  Object.defineProperty(hugo, 'Value', {
    configurable:true, enumerable:true,
    get () { return this._Store.Value},
    set (newValue) { this._Store.Value = newValue; this.render() }
  })

  hugo.render = function () {       // defined before any effects with "render"!
    render(html`Value is now ${hugo.Value}`,document.body)
  }
  hugo.render()

  effect(() => {
    console.log('deriving "hugo.Value" from "global.Value"',global.Store.Value)
    hugo.Value = global.Store.Value
  })
  effect(() => {
    console.log('updating "global.Value" from "hugo.Value"',hugo.Value)
    global.Store.Value = hugo.Value
  })

  console.log('\n\nsetting "hugo.Value" to 1')
  hugo.Value = 1

  console.log('\n\nsetting "global.Value" to 2')
  global.Store.Value = 2

which produces the following output:
deriving "hugo.Value" from "global.Value" 0
updating "global.Value" from "hugo.Value" 0

setting "hugo.Value" to 1
deriving "hugo.Value" from "global.Value" 0
updating "global.Value" from "hugo.Value" 0

setting "global.Value" to 2
deriving "hugo.Value" from "global.Value" 2
updating "global.Value" from "hugo.Value" 2

As you can see, after setting hugo.Value to 1, the wrong "effect" function is called which sets hugo.Value back to 0 (the current global.Store.Value)
Now, disable the render invocation in the value setter and run the same code again. It will now output:
deriving "hugo.Value" from "global.Value" 0
updating "global.Value" from "hugo.Value" 0

setting "hugo.Value" to 1
updating "global.Value" from "hugo.Value" 1
deriving "hugo.Value" from "global.Value" 1

setting "global.Value" to 2
deriving "hugo.Value" from "global.Value" 2
updating "global.Value" from "hugo.Value" 2

which is correct.
Even worse: if you re-enable the render invocation but simply swap the two effect calls (like so
  effect(() => {
    console.log('updating "global.Value" from "hugo.Value"',hugo.Value)
    global.Store.Value = hugo.Value
  })
  effect(() => {
    console.log('deriving "hugo.Value" from "global.Value"',global.Store.Value)
    hugo.Value = global.Store.Value
  })

) and run the code again, its output will be correct again:
updating "global.Value" from "hugo.Value" undefined
 deriving "hugo.Value" from "global.Value" undefined

setting "hugo.Value" to 1
updating "global.Value" from "hugo.Value" 1
deriving "hugo.Value" from "global.Value" 1

setting "global.Value" to 2
deriving "hugo.Value" from "global.Value" 2
updating "global.Value" from "hugo.Value" 2

This is a really severe problem which makes my code (using preact-observables) practically unusable as I cannot predict its behaviour.
Do you have any idea what the reason for this strange (race condition?) could be?

For those who may come across the same problem: it might be that a workaround could be to change this.render to setImmediate(() => this.render()) or setTimeout(() => this.render(),0)
However, this would just be a really ugly workaround as it does not solve the underlying problem but only this single "manifestation" of it - and may cause other unwanted side-effects.

Thanks for the issue! I should have time to take a look at it this week, do you happen to have a codesandbox or stackblitz link handy with the reproduction?

Thanks for raising this. I had a chance to look into it and few things worth mentioning
This has nothing to do with the render call but rather the hugo.Value getter. If you remove everything but that in render it will still trigger this issue.
I'm not sure why you're rendering in a setter, render should be an effect.  Either way this does look like a legitimate bug though it's not a bug in preact-observables I can reproduce it with just<EMAIL_ADDRESS>. You might want to raise this issue there.
stackblitz: https://stackblitz.com/edit/typescript-vlzyrk?file=index.ts
import { effect, signal, computed, batch } from '@preact/signals-core';

const Store = { Value: signal(0) };

const hugo = { _Store: { Value: signal(0) } };

const comp = computed(() => hugo._Store.Value.value);

Object.defineProperty(hugo, 'Value', {
  configurable: true,
  enumerable: true,
  get() {
    return comp.value;
  },
  set(newValue) {
    batch(() => {
      this._Store.Value.value = newValue;
      this.render();
    });
  },
});

hugo.render = function () {
  hugo.Value;
};
hugo.render();

effect(() => {
  console.log('deriving "hugo.Value" from "global.Value"', Store.Value.value);

  batch(() => {
    hugo.Value = Store.Value.value;
  });
});
effect(() => {
  console.log('updating "global.Value" from "hugo.Value"', hugo.Value);
  batch(() => {
    Store.Value.value = hugo.Value;
  });
});

console.log('\n\nsetting "hugo.Value" to 1');

batch(() => (hugo.Value = 1));

console.log('\n\nsetting "global.Value" to 2');
Store.Value.value = 2;

same output:

deriving "hugo.Value" from "global.Value" 0
updating "global.Value" from "hugo.Value" 0

setting "hugo.Value" to 1
deriving "hugo.Value" from "global.Value" 0
updating "global.Value" from "hugo.Value" 0

setting "global.Value" to 2
deriving "hugo.Value" from "global.Value" 2
 updating "global.Value" from "hugo.Value" 2

Here's a simplified reproduction with preact/signals-core
import { effect, signal, computed } from '@preact/signals-core';

const a = signal(0);
const b = signal(0);
const comp = computed(() => b.value);

effect(() => {
  console.log('deriving "b" from "a"', a.value);
  b.value = a.value;
  comp.value
});

effect(() => {
  console.log('updating "a" from "b"', b.value);
  a.value = comp.value;
});

console.log('\n\nsetting "b" to 1');
b.value = 1;
console.log('\n\nsetting "a" to 2');
a.value = 2;

uncommenting comp.value in the first effect produces the "correct" results

Thank you very much for your effort - particularly for the simplified version of my example!
One of my problems (in the real application) was that the "effect"s in the above example actually are "plugins" from other users which I do not have under my control - although I would like to assert that they behave "as expected".
However, what I indeed have under my control is comp.value (or its counterpart in the real code) - and I surrounded that with a call of untracked. Since then, everything works as intended - although the solution still smells a bit like a hack or ugly workaround...
So, again, thank you very much for your help!


Unit test for jQuery 1.7.2

Thought you might find it handy.

Part of https://www.npmjs.com/package/jquery-hashchange/v/1.4.0


fastcgi_pass instead of proxy_pass?

Hello,
I have a container with php-fpm and my app. Can I use nginx-proxy for it using fastcgi_pass instead of proxy_pass? It is a good idea? Or maybe it's better to use a webserver for each instance of my php-fpm app?
Thanks a lot!

I briefly discussed this with myself in another ticket (cf https://github.com/jwilder/nginx-proxy/issues/99 :wink), but it's not currently possible. I think it's a good idea, but possibly tricky to get the details right across the different upstream protocols.

@md5 OK, thanks for answer.

is this still not possible?

@sandrodz, I haven't tested yet after I wrote the question.

Stumbled on the same problem :(
Can't we have the container assume someone intended to mount as readonly? e.g have it auto gen -> stop -> modify it -> Mount as readonly ?

Hey @starikovs @sandrodz could you please explain how you linked both nginx-proxy and nginx? Thanks!

@vitorsdcs first you start jwilder/nginx-proxy container and then you can start any number of nginx containers with -e VIRTUAL_HOST=foo.bar.com param. nginx-proxy detects those containers automatically. Read more here https://github.com/jwilder/nginx-proxy. Did I understand your question correctly?

@starikovs Yes. Thanks!


[PE-D] n/ parameter in help command does not work

Steps to Reproduce:

Type help n/add in the command box
Hit Enter key

Expected: The help window will be brought up with the add command segment automatically opened (see below)

Actual: The help window is brought up and switched to the command section, but the add command segment is not opened. (see below)

I tested this with a few other valid commands and none of them work, either.

Labels: severity.Low type.FunctionalityBug
original: Graphcalibur/ped#2

Similar to: #135


[Bug]: Devices running iOS versions lower than 17 cannot function properly.

Application
Outline Client
Describe the bug
Apple devices running iOS 16 or earlier can successfully install the Outline app, but after installation, no areas of the app are touch-responsive. Tapping on any page element produces no reaction. Even when importing via an SS URL format, the interface elements remain completely unresponsive.
Steps to reproduce
Apple devices running iOS 16 or earlier can successfully install the Outline app, but after installation, no areas of the app are touch-responsive. Tapping on any page element produces no reaction. Even when importing via an SS URL format, the interface elements remain completely unresponsive.
What did you expect to happen?
No response
What actually happened?
No response
Outline Version
1.14.0
What operation system are you using?
iOS
Operating System Version
iOS16
Screenshots and Videos
No response

Thanks for providing these details. I can now see this is a dupe of #2276. We'll post updates there.


Replace github.action_path into GITHUB_ACTION_PATH

Due to the bug of GitHub Action Runner (actions/runner#716), github.action_path context value is not evaluated into valid path in containers on self-hosted runners. The corresponding environment variable GITHUB_ACTION_PATH always contains valid path even actions running on self-hosted runners, so this PR replaces github.action_path context into GITHUB_ACTION_PATH environment variable.

@SSW-SCIENTIFIC great, thank you for your contribution


Principle of least privilege should be applied in operator (Cluster)Roles

Describe the bug
Today the operator is by default granted all permissions on all resources clusterwide by a blanket ClusterRole
Expected behavior
Only specifically those permissions which are necessary in order to create a functional Knative serving setup should be added, using escalate and/or bind to create roles or rolebindings that the operator itself does not need explicitly, but which are needed transitively by knative serving.
To Reproduce

Install Knative Eventing Operator.
kubectl describe clusterrole knative-eventing-operator

Name:         knative-eventing-operator
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"rbac.authorization.k8s.io/v1","kind":"ClusterRole","metadata":{"annotations":{},"name":"knative-eventing-operator"},"rules":...
PolicyRule:
  Resources  Non-Resource URLs  Resource Names  Verbs
  ---------  -----------------  --------------  -----
  *.*        []                 []              [*]

Sibling bug of https://github.com/knative/serving-operator/issues/282
Going to use this to attempt to solve both in a way that generalizes well.

/assign Cynocracy


Add missing AdministratorName parameter

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

This fixes a bug in 80016a412edbe5ebaea8ce65cd7efea419600b10 . Why didn't we get any linter, model, or semantic errors for this?

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/serverAzureADAdministrators.json
Before the PR: Warning(s): 1  Error(s): 3
After the PR: Warning(s): 1  Error(s): 3
Know more about AutoRest Linter Guidelines.
Send feedback and make AutoRest Linter Azure Bot smarter day by day!
Thanks for your co-operation.

No modification for AutorestCI/azure-sdk-for-node

 https://github.com/Azure/azure-sdk-for-ruby/pull/832

 https://github.com/Azure/azure-sdk-for-python/pull/1290


change event does not emit on IE 11

I use the Demo (https://stackblitz.com/edit/ng2-ckeditor) On IE 11.
When I hold Back space key to delete all the content. The change event does not emit and the model is not updated.
Actual:

Expected:

Before:

After:

You can reproduce it by holding the backspace and release it as soon as all the character is cleared.

Can you help me to check again

If you want to update your model data in shorter intervals, you can change the debonce value as follow:
            #myckeditor="ngModel"
            name="myckeditor"
            required
            [config]="ckeConfig"
            debounce="50"
            (change)="onChange($event)">
	</ckeditor>```

Thank Kzimny, i will try this


Diagram Deployment: Message of Process-Engine-Exception in Log Panel

Referring to a previous discussion in the Camunda forum.

When trying to deploy an incorrect model, it would be helpful to show the explanable message of the ProcessEngineException, the response content of the REST API, in the log panel of the Modeler.
Similar as shown in this Postman response body:

Valuable information that is currently hidden, indeed.
Thanks for reporting!


FermipyLike.py needs new IRFS for P305

In FermipyLike.py there is an hardcoded lookup table to match event class number with IRFS names. It's call "evclass_irf", and needs to be updated with new IRFS name, or any analysis with P305 will fail. Also, would be good to keep backwards compatibility.

Working on IS322 branch.


Spell check enhancement

Is it possible to get an inline spell check feature added? Would be really useful.

You can enable it manually.
Edit -> Spelling and Grammer -> Check Spelling While Typing

Good tip by @xxdavid; this should definitely be enabled automatically however!

+1 on this. Thanks for the tip!

There is no Edit -> Spelling and Grammer for me on 10.12.6 (16G29) using Version 3.2.2 (2001)


Fedora IoT base Bootc image is defined and composed automatically

determine which IoT packages to include in an IoT specific Bootc base image
add any configuration files needed to compose the iot base image in an IoT compose
update the Fedora IoT Pungi configuration files to include the base image
 * IoT Bootc base image is pushed to a publicly available registry

Added:
https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-41-20240930.0/compose/bootc-base/
https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-42-20240927.1/compose/bootc-base/


Fix unexpected SSO behaviour for trusted proxy

This bugfix adds a Behat scenario the reproduces the behavior described in the bug report. It then proceeds to fix the issue by preventing IdP scope limiting based on previously selected IdPs.
More details about this bug can be found in:
https://www.pivotaltracker.com/story/show/164069793

@pablothedude the last commit is the experiment we discussed over the landline with @quartje. Can you review this critically? If you see any problems with that commit, I'll drop it and go with 4ae4893

FYI: I dropped the initial commit, containing the IdP scoping quick fix. That solution was dropped in favor of the more elegant solution that was proposed by @quartje


How to use the api

An epic guide written by yours truly 🎉

Looks good to me, examples seemed easy to follow.


Example on how to listen for messages on a exchange

Are there any examples how how to listen for messages on an exchange?

No, you have to bind a queue to the exchange and subscribe to that queue. Messages to an exchange will be routed to all queues bound to it with the matching routing keys.


fixing the login page

Related Issue

Mention issue for which this pull request is a part of (#373  )

Proposed Changes

Change Image styling with add responsiveness to the page
The form elements seems to break when we pulled the screen down to minimum size, fixed that breaking

Additional Info

Any additional information or context

Checklist

[ x] ✅ My code follows the code style of this project.
[ x] 📝 My change requires a change to the documentation.
[ x] 🎀 I have updated the documentation accordingly.
[ x] 🌟 ed the repo

[x ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ x] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Title goes here
Title goes here

Image goes he

re
Image goes here

Please fetch the latest version of code


modified the ir data structure to include the external cells and invoke

Looks like formatting checks are failing? Try running cargo fmt and cargo clippy to make sure there are no warnings.

Awesome!! :tada:


Requiem's "Mortal" and "Demon" no longer appears on the origins interface when picking origins like before

Requiem compatibility with origins interface is gone, not appearing when choosing an origin. This worked fine before 0.6, but now does not appear. Would be nice to have it back.
I also posted it to Requiem's github if it's not an issue from Origins: https://github.com/Ladysnake/Requiem/issues/256

Yeah, seems like Requiem hasn't updated to accomodate for my Origins 0.6.x update yet. :( Sorry for the inconvenience.

They have updated, no worries!


[feedly] add python packages to data connector

Required items, please complete
Change(s):

Adding python packages in the data connector zip

Reason for Change(s):

missing folder

Hello Mathieu, I hope this function app is good now. Can you share the working images of the same

Hello Mathieu, I hope this function app is good now. Can you share the working images of the same

The connector has been working since the beginning when I send it with VSCode, it's the deployment that is not working, but I don't know how to test that without updating the offer...

 Can you share this with me

How do I share that securely?

 Can you share this with me

How do I share that securely?

you can mail me at<EMAIL_ADDRESS>

Hey hi @Mathieu4141 maybe you missed sharing the credentials over mail. Can you please share it.

Hello @Mathieu4141, Can you please share the credentials.

Hello @Mathieu4141, we are waiting for the credentials.

Hello @Mathieu4141, We are waiting for the credentials

Hello @Mathieu4141, We are waiting for the credentials

I already sent the details to the email you provided above

Hey thanks @Mathieu4141, for sharing the details. I'll test the connector and get back to you by 20 December, 2023.

Hello @ajcollins0, due to lack of availability it was not possible for me to touch this PR.
I'll investigate this PR and get back to you by 22 December, 2023.

Hello @Mathieu4141, The folder structure in the zip file is still improper. Correcting the folder structure. Will update you by today EOD or tomorrow first half (IST)


[BugFix] Fix habitat integration and doc

Description
Fixes Habitat integration and doc.
The goal is to make a benchmark for Habitat as we do for dm_control and Atari.
cc @vincentpierre

Added support for device casting.
You can now call env = HabitatEnv(..., from_pixels=True, device=3) and the whole rendering will be executed on the appropriate device. You can also call env.to(device), and the env will be restarted on device.


fix llama kv cache

Hi @zhisbug @Viol2000
The llama model needs to cache up with HF as HF uses KV cache in the llama model.
Relate issue: https://github.com/hao-ai-lab/LookaheadDecoding/issues/35

Thanks for your efforts. I will merge the code soon.

Hi @Viol2000 . Would you please merge this PR? Thx!


Use individual modules instead of gulp-util (Close #17)

See https://github.com/lpender/gulp-cloudfront-invalidate-aws-publish/issues/17 for more details about the migration.

@lpender Thank you for updating! Loving this plugin 💕


Overriding CSS stylesheets

How could I go about overriding the stylesheet of a website packaged with nativefier? One of the uses I'm keen to try out is wrapping another site but also tweaking a couple of UI things to better suit its new life as a desktop application.
Any ideas?

I sort of worked it out by using WebContents.insertCSS(), though it requires me to customise the nativefier source. Regardless, it works :)
https://github.com/atom/electron/blob/master/docs/api/web-contents.md#webcontentsinsertcsscss


Autocomplete crashes

The above error occurred in the <WithStyles(ForwardRef(Autocomplete))> component:
in WithStyles(ForwardRef(Autocomplete)) (at Offers.js:482)
in div (created by ForwardRef(Grid))

@bipindubey-technoark  Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template is a good starting point. Thank you!

this is my code
<Autocomplete
multiple
id="checkboxes-tags-demo"
options={top100Films}
name="cities"
size="small"
getOptionLabel={(option) => option.title}
renderOption={(option, { selected }) => (
<>
<Checkbox
icon={icon}
checkedIcon={checkedIcon}
style={{ marginRight: 8 }}
checked={selected}
/>
{option.title}
</>
)}
style={{ width: '100%' }}
renderInput={(params) =>
(
<Field
{...params}
label="Cities"
fullWidth
name="cities"
component={TextField}
/>
)}
onChange={(event, val) => {
if (val !== null) {
const city = [];
val.map(v => city.push(v));
setFieldValue('cities', city);
}
}}
/>

See the warning: "Invalid field name. Either pass useField a string or an object containing a name key.". This is likely an issue with formik-material-ui. If you can't reproduce this issue without 3rd party libraries please open an issue in formik-material-ui instead.