Copy of the sample data

Hi Fernando. Thank you very much for the amazing tutorial. Unfortunately the URL in the README seems to be deactivated. I'd like to use the dataset for my master's thesis. Have you got a local copy of the sample data?

Hi Shamil,
Sorry for the inconvenience. The dataset was accessed by Microsoft URL, but last year the link stopped working.
Some people asked me for the dataset, but I didn’t save any copy due to its big size.
Best regards.
Fernando de Castilla
Enviado desde mi iPhone
El 16 abr 2022, a las 12:47, Shamil Nabiyev @.***> escribió:

Hi Fernando. Thank you very much for the amazing tutorial. Unfortunately the URL in the README seems to be deactivated. I'd like to use the dataset for my master's thesis. Have you got a local copy of the sample data?
—
Reply to this email directly, view it on GitHubhttps://github.com/fernandodecastilla/Machine-Learning-for-Predictive-Maintenance/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI7X6XQ4A44KOVFSK4DEAE3VFKLETANCNFSM5TSGYDWQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

It's OK :) Thank you very much, Fernando.


Page builder does not remember navigation state

Describe the bug
When pressing save and close in page builder it always brings you to the admin panel
To Reproduce
Edit page, press save and close.
Expected behavior
Should navigate you to where you came from (e.g. page detail page)
Screenshots
https://user-images.githubusercontent.com/19151369/193866281-a054c04d-2ac0-402b-aaaf-712eef2d8040.mp4

Hey, thank you for raising this issue. We have general navigation improvements in the pipeline (for 2023.3), which includes this problem you're experiencing.


Changes to the home page

Style fixes, wording fixes

Pull Request Test Coverage Report for Build 257

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.009%) to 54.281%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

routes/commandpedia.js
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

routes/commandpedia.js
1
66.67%

Totals

Change from base Build 255:
-0.009%

Covered Lines:
4231

Relevant Lines:
7223

💛  - Coveralls


feat(icon): add new icon

FX-2255
Description
Add missing "new" icon available in BASE
How to test

Run & test manually

Review

[x] Read CONTRIBUTING.md and Component API principles
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure that tests pass by running yarn test
[ ] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.


subaru outback 2015 on Comma2 : dashcam mode

Describe the bug
Hi, I have been driving Subaru outback 2015 with comma 2 for last 5 years and it abruptly stopped working a week ago. It went completely blank one day and then I had to reset the device and install fresh OP.  I am able to ssh into my comma 2 device but I am not sure which branch will be right for suabru-outback 2015. I had fingerprinted my 2015 car few years ago (OUTBACK_PREGLOBAL in values.py). I had SnG feature working in my car with c2.
can someone please suggest which branch will be right for my comma2 with outback 2015.
I tried many different branches where README say it is for C2 & c3  but my screen become blank after reboot.
Now I have the default main branch and it actually shows the typical display but when I turn on the car, I get this error dashcam mode, see attached photo.

Provide a route where the issue occurs
abf68062e576acda/2024-10-11--22-06-44
openpilot version
<IP_ADDRESS>
Additional info
dongle id abf68062e576acda

what does it mean "not planned", can you provide some feedback please?


Reimplement battery voltage read and display for Badger 2040 W

This measures VSYS ADC on Pi Pico W, which should be OK accuracy since the 3.3V reference is provided from the Pico W's buck regulator. Battery display is only enabled for Badger 2040 W because I didn't reimplement the battery measuring logic for Badger 2040.
Nothing special needs to be done to restore pin 29 back to output because the driver in Pico SDK automatically sets it on starting SPI comms.
Resolves #26

Thank you-
However I am still very much of the opinion that it's MicroPython / Pico SDK's responsibility to implement the correct way of accomplishing this, taking into account any thread locks and other edge cases that we might otherwise encounter and smoothing over the implementation differences between Pico and Pico W.
This issue in particular touches upon that idea - https://github.com/micropython/micropython/issues/11185
And this reference implementation uses specific cyw43_thread_enter()/_exit() locks to ensure there are no WiFi hiccups while reading battery - https://github.com/micropython/micropython/issues/11185
Right now I don't think we can do this correctly in just Python?

That's a good point. I did end up with some issues with the pin not reading correctly in a previous iteration perhaps due to this. Where would be a good place to insert new code? In a Badger-specific board module, or patching the rp2 module?


Add panel-serve as a CDS dashboard option

Fixes | Closes | Resolves #

Please remove anything marked as optional that you don't need to fill in. Choose one of the keywords preceding to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666). If there is no issue, remove the line. Remove this note after reading.

Changes:
New feature based on the work @pierrotsmnrd, @danlester and I worked on for recent client project.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[ ] Yes
[ ] No

In case you checked yes, did you write tests?

[ ] Yes
[ ] No

Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

@iameskild what is the status of this PR? Is it ready for review

@costrouc I was gonna hold off merging since we were in a freeze prior to the v0.4.0 release. I wanted to get this in so that it would remind me to return to it later. The only thing that might be worth following up on is trying to make the timeout values configurable from the qhub-config.yaml. Is that something you think would be worthwhile? Otherwise, I'm happy to see this merged.

@iameskild May we close this (as its currently a draft) and re-open once migrated to Nebari?

@viniciusdc I need to wrap up this PR this week. I might request your review when I get it finished :)

@pierrotsmnrd this is ready for review. This will likely need to be tested on the beta-deployment to ensure that it works. Thanks for your patience :)

@iameskild @aktech Can we fix this and get it merged and deployed. I need it for a demo on Monday.

@costrouc I made some changes based on the concern you had. I tested this on minikube and I am able to successfully get the username and launch a panel-serve app 🙌  let me know if you have any other questions or concerns!
cc @pierrotsmnrd


test: Refactor Cilium tests with grep

Proposal / RFE
The function CiliumExecContext is used to call grep in several cases (search k8sT). grep does not exit with a zero-code when it doesn't find what it is looking for. Often times this is the desired behavior, so checking the Success method for the exec result is not useful. We should refactor these tests so that CiliumExecMustSucceed can be used in these instances.

I can take up this. Assign it to me.

@soumynathan done! Thanks!

test-me-please

@soumynathan you need to open a PR, test-me-please doesn't work on issues.

Often times this is the desired behavior, so checking the Success method for the exec result is not useful. We should refactor these tests so that CiliumExecMustSucceed can be used in these instances.

I'm not sure I understand this issue. I think the reason we sometimes don't use CiliumExecMustSucceed is that it has a fixed offset of 1 for ExpectWithOffset and we would need e.g. an offset of 2.


aurutils terminal coloring with systemd 256

With systemd 256 (the upcoming systemd release) it includes possibilities to color terminals, i.e. on systemd-nspawn and run0. When nspawn is now used in a program this very much looks like a visual bug IMO:

I have therefore disabled the behaviour in devtools (https://gitlab.archlinux.org/archlinux/devtools/-/commit/0e2b16b0ac63e33e32a6cb889bc4b047e0d451e9), but since I couldn't get the above trivial fix to work with aurutils I thought I'd open this issue as a heads-up.
Feel free to close as wont-fix if you want to keep the default behaviour.

Seems like an nspawn issue; the bleeding background colour appears to come from pacman.

@Earnestly I'm not sure I follow, what do you mean?

I'm confused by the commit message:
Disable this bevaviour for pkgctl, so it stays active for arch-nspawn (for now).

but arch-nspawn, makechrootpkg, and mkarchroot use src/lib/common.sh. In turn, aur-chroot uses those three tools for chroot functionality.

I forgot that they include common.sh so its a side-effect but fine by me 😆 Disregard this issue then 👍🏻

Just noticed this. It looks like eye bleed unfortunately. Any way to get this fixed in aurutils?

This is fixed in the devtools 1.2.1 release thats currently still in testing 😊


Delete grants

PR Acceptance Criteria
Closes #10
Guidelines

[x] PR follows the Contributing guidelines?
[x] PR Adheres to our Code of Conduct?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Code complete

[x] A README.md available describing how to setup and test the code?
[x] The code sample in the correct location (i.e. email/node/read-email)?
[x] Link added to the repository readme (view # Code Snippets created by the Nylas Community with examples) describing what the code sample does for others to try out
[x] The code can be run using Github Codespaces, so the maintainer can try out the code sample remotely to ensure everything is working before we accept the PR.

For PR Reviewer use

[ ] Purpose of code sample is clear
[ ] The code sample is readable
[ ] Steps try out the code are provided
[ ] Code sample runs on codespaces environment
[ ] Code works as expected
[ ] PR labels added

@amit-ksh - can you resolve the conflicts in the readme.md and we will merge shortly after.

Done!


Problem with call objects availability and persistency

problem area
Imagine pretty dummy use case - developer mentioned a "bad image" that is not available on the registry. So, when i submit a call the only thing I get - call ID, so, any attempts to get call state would just fail because call ID is not getting persisted at all.
Unfortunately, there's no way to discover the source of a problem using calls API for such particular cases (make function sync will show you most of problems with images, but not the case).
how to solve the problem
First of all, create call object as soon as call submitted (see the related issue: #978). If there's a problem with related docker images that agent can't pull, Fn must persist call object in error state with the corresponding error.
side note
There might be more problems that must be reported to a caller through calls API, such as:

Too busy is not reported to the caller
image not found

what else?

there is an issue somewhere documenting that certain behaviors cause an async call to attempt to be invoked forever. again, async getting ripped out of core.

triaging to #281

triaging to #1055


Add replace phpunit command option

Add phpunit.replace_phpunit_cmd_if_key_exists option, to run $WORK_DIR/artisan, test, or running tests from project script.
But there are two issues:

On first run it will run phpunit command itself
When running tests on sublime panel, there is no color:

Codecov Report
Patch coverage: 8.33% and project coverage change: -0.49 :warning:

Comparison is base (d84d714) 46.64% compared to head (a441f76) 46.15%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #106      +/-   ##
==========================================
- Coverage   46.64%   46.15%   -0.49%
==========================================
  Files           1        1
  Lines         551      559       +8
==========================================
+ Hits          257      258       +1
- Misses        294      301       +7

Impacted Files
Coverage Δ

plugin.py
46.15% <8.33%> (-0.49%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

See #102 and #103 on why there are some issues with running tests via test runners like artisan.
I wouldn't want the artisan test runner or any other test runner to replace the PHPUnit runner by default.
Test runners like artisan and pest are essentially wrappers around the PHPUnit runner. They generally work the same as PHPUnit with all the options and functionality except they add some functionality, sometimes change the default options, and have different styled output. The phpunit --testdox output is very similar to the artisan test output. You can toggle the --testdox via the command palette "PHPUnit: Toggle Option --testdox`.
In the case of artisan and pest I don't think I mind having specific settings to enable those as candidate test runners instead of the phpunit executable e.g. boolean settings phpunit.pest and phpunit.artisan.
The working directory variable is potentially an issue because paths are already filtered for environment variables the user directory e.g. $HOME/path/... will expand to the user home directory. A relative path like vendor/bin/runner should resolve relative to the working directory so I'm not sure there is a need to explicitly specify it. An absolute path /home/code/project/vendor/bin/runner should resolve without issue too.
The alternative test runner use cases I know of are artisan and pest. At the moment to use pest you can replace the phpunit executable (see #103):
"phpunit.executable": "vendor/bin/pest",
"phpunit.options":
	{
		"colors=never": true
	},

And to use artisan it's a bit hacky (see #102):
	"phpunit.prepend_cmd": ["artisan"],
	"phpunit.executable": "test",
	"phpunit.options":
	{
		"colors=never": true,
	},

We can fix the artisan one to allow the following by allowing the phpunit.executable option to be a list:
	"phpunit.executable": ["artisan", "test"],
	"phpunit.options":
	{
		"colors=never": true,
	},

You can set settings on per-project basis: Menu > Project > Edit Project
{
   "settings": {
       "phpunit.executable": ["artisan", "test"],
       "phpunit.options":
       {
           "colors=never": true,
       },
   }
}

Yeah that's lighter solution.

We can now replace the phpunit.executable with a list so any of the following work:
"phpunit.executable": ["artisan", "test"],
"phpunit.executable": ["vendor/bin/pest"],
"phpunit.executable": "vendor/bin/pest",

I've also added some color output for Pest.


[5.3] Allow reconnect in transaction by setting transactions to 0

I am not sure if I apply this to 5.1 as well. The tests and codes changed. Maybe need another PR.
Also here is a history you may check #5944 #5937
Thanks.

So is this to replace all your other PRs? I'm confused by all these PRs.

Can you provide description of initial problem and how this fixes it?

Code history check
In Laravel 4.2, this line were added to Connection::setPdo():
if ($this->transactions >= 1) throw new \RuntimeException("Attempt to change PDO inside running transaction");

As mentioned in #5937, the motivation was to prevent Connection::run() from breaking transaction logic by retrying part of a transaction in a lost connection inside another connection.
The initial proposed solutions in #5937 was this

(1) skip Connection::reconnectIfMissingConnection and Connection::tryAgainIfCausedByLostConnection calls if Connection::$transactions > 0
or
(2) modify them to throw exceptions and reset Connection::$transactions to 0 when they called.

Then (2) was implemented (without resetting $transactions to 0) in #5944, which I think was wrong, and some time later (1) is also done.
The behavior after this PR
I think by having solution (1) in the code, there is no need to throw exception in setPdo() when Connection::transactions > 0. Just reseting the value to 0 is enough.
The three new added tests shows the new behavior:

Connection::setPdo(), which may be called by DB::reconnect(), will not throw exception if a transaction is open in the current connection. Instead, it just resets Connection::transactions to 0.
Connection::run() attempts to reconnect(swap PDO) on lost connection event if and only if there is no open transaction in the connection. If there is an open transaction, it re-throws the exception so the client code decides what to do; It may give up and die, but only after this PR it can call DB::reconnect() and retry the transaction or pick the next job from the queue.

Thanks.


More list recommendations

The unified host list was already in rethinkdns and I had a good experience with it so I recommend bringing it over here. Phishing army extended is a bit self explanatory, just an add on to the standard phishing army. Dandelion sprouts Nordic filter list is a little list but could be useful to certain people

Just added inversion here because it is basically the list that google says “these are malicious sites”. Or what not

If you can make the recommended changes, then the list will be live in <10 minutes.

If you can make the recommended changes, then the list will be live in <10 minutes.

I’m not the most experienced with GitHub. Did you recommend changes?

I’m not the most experienced with GitHub. Did you recommend changes?

It's okay, I'll do it myself 😅


small cleanup

As discussed in gh-1385.

be explicit when discarding returned errors from .Close(), etc.
remove named return values from funcs when naked return not used
fix some "err" shadowing when redeclaration not needed

A few files are not formatted with gofmt.
I'd like to suggest installing fmt-check from https://github.com/edsrzf/gofmt-git-hook as a pre-commit hook (just copy it to .git/hooks/pre-commit).

Sorry about that. I actually did take care to run "gofmt", but I ran gofmt -w **/*.go, which produced no output (if you squint I think you can see the problem there. 😄)
I will install the pre-commit hook as you suggested.

Codecov Report

Merging #1390 into master will decrease coverage by 5.53%.
The diff coverage is 34.61%.

@@            Coverage Diff             @@
##           master    #1390      +/-   ##
==========================================
- Coverage   51.17%   45.64%   -5.54%
==========================================
  Files         136      136
  Lines       13585    13595      +10
==========================================
- Hits         6952     6205     -747
- Misses       5777     6587     +810
+ Partials      856      803      -53

Impacted Files
Coverage Δ

internal/cache/cache.go
29.87% <0%> (ø)
:arrow_up:

internal/backend/b2/b2.go
0% <0%> (-79.93%)
:arrow_down:

internal/restic/lock.go
69.32% <0%> (ø)
:arrow_up:

internal/cache/file.go
40.29% <0%> (ø)
:arrow_up:

internal/restic/restorer.go
0% <0%> (ø)
:arrow_up:

internal/checker/checker.go
72.02% <100%> (ø)
:arrow_up:

internal/pipe/pipe.go
72.41% <100%> (ø)
:arrow_up:

internal/backend/local/local.go
68.92% <100%> (ø)
:arrow_up:

internal/restic/node.go
36.61% <35.71%> (-0.06%)
:arrow_down:

... and 4 more

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 e44ac55...eea96f6. Read the comment docs.


hatari: 2.2.1 -> 2.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/hatari/versions.
meta.description for hatari is: "Atari ST/STE/TT/Falcon emulator"
meta.homepage for hatari is: "http://hatari.tuxfamily.org/"
meta.changelog for hatari is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.3.0 with grep in /nix/store/j5l6nnk1jqia52p66qbx49qkx65d50j7-hatari-2.3.0

directory tree listing: https://gist.github.com/e1ee76fcbcc13aa7b0efde0f4c9ee4df

du listing: https://gist.github.com/58419c2f8f97ca60e4f0579b7e1304f9

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
hatari

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j5l6nnk1jqia52p66qbx49qkx65d50j7-hatari-2.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hatari https://github.com/r-ryantm/nixpkgs/archive/dc798e96046a187a81034b576198663ac3198831.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j5l6nnk1jqia52p66qbx49qkx65d50j7-hatari-2.3.0
ls -la /nix/store/j5l6nnk1jqia52p66qbx49qkx65d50j7-hatari-2.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

hatari

Maintainer pings

Result of nixpkgs-review pr 105686 run on x86_64-linux 1

1 package built:

hatari


Assignment_3

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

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

A3 complete


eBPF should publish arm64 binaries with releases

Describe the bug
eBPF builds arm64 code, and other projects (e.g. xdp-for-windows) have taken build and test CI dependencies on this platform, so eBPF should release artifacts in future releases. The release documentation should be updated to make this a standardized and repeatable process.
OS information
No response
Steps taken to reproduce bug
Visit https://github.com/microsoft/ebpf-for-windows/releases/tag/Release-v0.20.0, prior to arm64 binaries being manually uploaded post-release.
Expected behavior
eBPF publishes arm64 binaries for releases.
Actual outcome
eBPF 0.20.0 started building arm64 binaries, but did not publish them.
Additional details
No response

Required for https://github.com/microsoft/xdp-for-windows/pull/759


Clarify type for "channels" argument in Schedule.draw()

Information

Qiskit Terra version: 15.1

What is the current behavior?

In the docstring for Schedule.draw(), the description for the "channels" kwarg reads "A list of channel names to plot" suggesting the argument should be a list of strings (maybe obtained via Channel.name), but the indicated type (red text in image) is a list of Channel objects. Which is it? Or are both supported?
Suggested solutions
Figure out what types are accepted by this function. If it's a list of strings, update the type indicated in the docs to be Optional[List[str]]. If it's a list of Channels, update the text to read "A list of Channels to plot". If both types are supported, update the text to read "A list of Channels to plot", and the type accordingly.

It is just Channel objects that are supported.

@taalexander So the docstring should be channels: A list of Channels to plot.


Create NNNN-upgrade-c++-standard.md

The proposal is to use new c++11 standard in SDL core

Please propose minimal version of compiler for full c++11 support


[BUG] About the refresh of the page permission cache

djangocms: 4.1.1

Create a user group
Add the user to the user group
In the advanced settings of the page, add the user group for View restrictions
At this point, the user should have permission to browse the page.
However, the user will see a 404 page (insufficient permissions)
Restart the service 'python manage.py runserver'
Users can access it normally

I'M NOT SURE IF IT'S INTENTIONAL DESIGN, OR IF IT'S A BUG. My current solution, though, is to manually flush the cache
@fsbraun :)
from cms.cache.permissions import clear_permission_cache
clear_permission_cache()

Hi @baloyou ! I've come up with a fix: #7963

hi @fsbraun
I've been working hard lately to get the site online and just came back to test the permissions issue.
My needs are: set access permissions for the page (visible to specified user groups)
I tested the two versions separately: https://github.com/django-cms/django-cms/pull/7963 and https://github.com/django-cms/django-cms/pull/7965
python -m pip install git+https://github.com/django-cms/django-cms.git@43f8b71da66993f4bd986251575dc7ce98a9d51f
Actual result: After the user joins the group, the page is still not visible in the navigation menu, but the page can be accessed by entering the URL (it can be accessed, but the menu will not be updated, maybe it is related to caching?). ）

@baloyou It seems we forgot to also clear the menu cache.
Can you check this:
python -m pip install git+https://github.com/fsbraun/django-cms@fix/menu-cache

@fsbraun It works very well and thank you so much for your dedication and effort!!


Generate Language Specific Themes

Use Gulp to generate language specific themes (https://www.npmjs.com/package/gulp-static-i18n-html).  This could also be a good solution for site translations via Respond or using Gulp watch.

Fixed in latest release.


samples:update slates and CDN keys to return LROs; add live config sa…

…mples and tests
b:277359252
Please merge on approval.

This is great! I tried to make these changes in https://github.com/GoogleCloudPlatform/php-docs-samples/pull/1871, but this is better


ManifestMerger error on build (preview 03)

When I try to build using the ManifestMerger I get this error. I am not sure why. I tried cleaning, deleting bin and obj because I had problems in the past using the manifest in the obj directory, but I couldn't get it anyway to work.
Did anyone get this?
/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/Xamarin.Android.ManifestMerger.targets(5,5): Error MSB3073: The command ""/Users/coosmiyn/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_<IP_ADDRESS>/bin/java" -cp "/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/common.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/guava.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/kotlin-stdlib-jdk8.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/kotlin-stdlib.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/kxml2.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/manifest-merger.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/sdk-common.jar:/Users/coosmiyn/.nuget/packages/xamarin.android.manifestmerger/1.0.0-preview03/build/monoandroid/sdklib.jar" "com.android.manifmerger.Merger" --main "obj/Release/android/AndroidManifest.xml" --libs "obj/Release/lp/61/jl/AndroidManifest.xml:obj/Release/lp/95/jl/AndroidManifest.xml:obj/Release/lp/59/jl/AndroidManifest.xml:obj/Release/lp/92/jl/AndroidManifest.xml:obj/Release/lp/66/jl/AndroidManifest.xml:obj/Release/lp/50/jl/AndroidManifest.xml:obj/Release/lp/68/jl/AndroidManifest.xml:obj/Release/lp/57/jl/AndroidManifest.xml:obj/Release/lp/32/jl/AndroidManifest.xml:obj/Release/lp/35/jl/AndroidManifest.xml:obj/Release/lp/102/jl/AndroidManifest.xml:obj/Release/lp/69/jl/AndroidManifest.xml:obj/Release/lp/56/jl/AndroidManifest.xml:obj/Release/lp/51/jl/AndroidManifest.xml:obj/Release/lp/58/jl/AndroidManifest.xml:obj/Release/lp/67/jl/AndroidManifest.xml:obj/Release/lp/93/jl/AndroidManifest.xml:obj/Release/lp/94/jl/AndroidManifest.xml:obj/Release/lp/60/jl/AndroidManifest.xml:obj/Release/lp/34/jl/AndroidManifest.xml:obj/Release/lp/20/jl/AndroidManifest.xml:obj/Release/lp/18/jl/AndroidManifest.xml:obj/Release/lp/29/jl/AndroidManifest.xml:obj/Release/lp/42/jl/AndroidManifest.xml:obj/Release/lp/89/jl/AndroidManifest.xml:obj/Release/lp/45/jl/AndroidManifest.xml:obj/Release/lp/73/jl/AndroidManifest.xml:obj/Release/lp/87/jl/AndroidManifest.xml:obj/Release/lp/74/jl/AndroidManifest.xml:obj/Release/lp/28/jl/AndroidManifest.xml:obj/Release/lp/1/jl/AndroidManifest.xml:obj/Release/lp/26/jl/AndroidManifest.xml:obj/Release/lp/21/jl/AndroidManifest.xml:obj/Release/lp/75/jl/AndroidManifest.xml:obj/Release/lp/86/jl/AndroidManifest.xml:obj/Release/lp/72/jl/AndroidManifest.xml:obj/Release/lp/44/jl/AndroidManifest.xml:obj/Release/lp/43/jl/AndroidManifest.xml:obj/Release/lp/88/jl/AndroidManifest.xml:obj/Release/lp/38/jl/AndroidManifest.xml:obj/Release/lp/36/jl/AndroidManifest.xml:obj/Release/lp/91/jl/AndroidManifest.xml:obj/Release/lp/65/jl/AndroidManifest.xml:obj/Release/lp/96/jl/AndroidManifest.xml:obj/Release/lp/100/jl/AndroidManifest.xml:obj/Release/lp/54/jl/AndroidManifest.xml:obj/Release/lp/98/jl/AndroidManifest.xml:obj/Release/lp/53/jl/AndroidManifest.xml:obj/Release/lp/30/jl/AndroidManifest.xml:obj/Release/lp/37/jl/AndroidManifest.xml:obj/Release/lp/39/jl/AndroidManifest.xml:obj/Release/lp/99/jl/AndroidManifest.xml:obj/Release/lp/52/jl/AndroidManifest.xml:obj/Release/lp/101/jl/AndroidManifest.xml:obj/Release/lp/55/jl/AndroidManifest.xml:obj/Release/lp/97/jl/AndroidManifest.xml:obj/Release/lp/63/jl/AndroidManifest.xml:obj/Release/lp/64/jl/AndroidManifest.xml:obj/Release/lp/90/jl/AndroidManifest.xml:obj/Release/lp/46/jl/AndroidManifest.xml:obj/Release/lp/41/jl/AndroidManifest.xml:obj/Release/lp/83/jl/AndroidManifest.xml:obj/Release/lp/77/jl/AndroidManifest.xml:obj/Release/lp/48/jl/AndroidManifest.xml:obj/Release/lp/70/jl/AndroidManifest.xml:obj/Release/lp/84/jl/AndroidManifest.xml:obj/Release/lp/24/jl/AndroidManifest.xml:obj/Release/lp/23/jl/AndroidManifest.xml:obj/Release/lp/4/jl/AndroidManifest.xml:obj/Release/lp/3/jl/AndroidManifest.xml:obj/Release/lp/85/jl/AndroidManifest.xml:obj/Release/lp/71/jl/AndroidManifest.xml:obj/Release/lp/76/jl/AndroidManifest.xml:obj/Release/lp/49/jl/AndroidManifest.xml:obj/Release/lp/40/jl/AndroidManifest.xml:obj/Release/lp/47/jl/AndroidManifest.xml:obj/Release/lp/22/jl/AndroidManifest.xml:obj/Release/lp/25/jl/AndroidManifest.xml" --out "obj/Release/android/AndroidManifest.xml"" exited with code 1. (MSB3073) (ClubHub.Android)

@coosmiyn

Did anyone get this?

I did, but few weeks ago. Updating to newer version helped. I know preview03 is the latest one.
This looks like commandline:
"com.android.manifmerger.Merger" \
--main "obj/Release/android/AndroidManifest.xml" \
--libs \
      "obj/Release/lp/61/jl/AndroidManifest.xml:obj/Release/lp/95/jl/AndroidManifest.xml: .... VeryLongList"

I would

run the sample in this repo and try to deduce commandline pattern.
then switch to your sample and try to run the commandline with increased verbosity

Do you maybe mix Android.Support and AndroidX?
Can you list Android.Support (AndroidX) and GooglePlayService/Firebase package references?
Few links

.   https://developer.android.com/studio/build/manifest-merge
.

I am using quite a few packages.
From Android.Support I am using Compat, Core.UI, Core.Utils, CustomTabs, Design, Fragment, Media.Compat, v4, v7.AppCompat, v7.CardView, v7.MediaRouter.
From Firebase I have Ads, Analytics, Analytics.Impl, AppIndexing, Auth, Auth.Interlop, Common, Config, Core, Iid, Measurement.Connector, Measurement.Connector.Impl and Messaging.
The Google Play Services are Ads, Ads.Identifier, Base, Basement, Flags, Gass, Gcm, Location, Maps, Measurement.Api, Measurement.Base, Places, Stats, Tasks.
I am in the process of deleting most of them, but I think it asked me before to install some of those, I was in a rush and I just installed them, also they are listed as dependencies for some of the packages.

Getting same error. Installed Manifest Merger preview03 to try and get latest Xamarin.Firebase.Messaging to work.

Some more info: When running the command in the command line, the errors I get are the following:
D:...\obj\Debug\90\android\AndroidManifest.xml:36:5-88 Error:
Element service#com.xxxxxx.app.mp.Services.MPFirebaseMessagingService at AndroidManifest.xml:36:5-88 duplicated with element declared at AndroidManifest.xml:21:5-25:15
D:...\obj\Debug\90\android\AndroidManifest.xml:37:5-84 Error:
Element service#com.xxxxxx.app.mp.Services.MPAuthenticatorService at AndroidManifest.xml:37:5-84 duplicated with element declared at AndroidManifest.xml:13:5-18:15
D:...\obj\Debug\90\android\AndroidManifest.xml:181:5-183:15 Error:
Element service#com.google.firebase.components.ComponentDiscoveryService at AndroidManifest.xml:181:5-183:15 duplicated with element declared at AndroidManifest.xml:164:5-166:15
D:...\obj\Debug\90\android\AndroidManifest.xml:202:5-146 Error:
Element activity#com.braintreepayments.api.threedsecure.ThreeDSecureWebViewActivity at AndroidManifest.xml:202:5-146 duplicated with element declared at AndroidManifest.xml:195:5-99
D:...\obj\Debug\90\android\AndroidManifest.xml Error:
Validation failed, exiting

OK, it seems that fixing the first two duplicate entries by only declaring them as attributes on the classes (and not in the manifest), fixes it.

@coosmiyn have you fixed your issue? what was the solution for you?

Same issue here, locally preview3 works but on CI it doesn't. I'm able to reproduce locally when downgrading to preview2.
Running from command line:
.../Xamarin.Android.ManifestMerger.1.0.0-preview02/build/monoandroid/sdk-common.jar: line 14: syntax error near unexpected token )' .../Xamarin.Android.ManifestMerger.1.0.0-preview02/build/monoandroid/sdk-common.jar: line 14: ?P%[?
dM4?"-ޑ?S<?
???1?.?u
?_.E??????PK'                                                                                ?M?rWN?o?,Ca?0F?&p)??-F
Not mixing AndroidX.
List of packages:

Any thoughts?

@otshenri
I hit those and updates did help. Not sure whether VS4mac, mono od Android SDK.
please can you provide more data about those 3?

@moljac I think VS4mac shouldn't matter because we're having the same issue with Azure CI build. Targeting Android 9.0 and using MonoAndroid90.

I have some problem, can't publish production. using VS4Mac latest version.

@moljac is there anything else we could try or some more information we could provide you? It's preventing us from publishing as well.

Is everyone using PackageReference ?

Solution for was changing the build agent from Windows machine to Mac machine. Hope it helps someone :)

same here!
build error.txt

Hmm... I wonder if we're hitting the max command line argument invocation length or something funny (which would explain why it would work on Mac and not Windows).
@xamarindevelopervietnam can you try copying and pasting the command it's trying to run into a terminal and manually running it to see more output?
So
"C:\java-jdk-231-x64\bin\java.exe" -cp "C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\common.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\guava.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\kotlin-stdlib-jdk8.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\kotlin-stdlib.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\kxml2.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\manifest-merger.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\sdk-common.jar;C:\Users\ASUS\.nuget\packages\xamarin.android.manifestmerger\1.0.0-preview03\build\monoandroid\sdklib.jar" "com.android.manifmerger.Merger" --main "obj\DB_SMHOME\100\android\AndroidManifest.xml" --libs "obj\DB_SMHOME\100\lp\101\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\102\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\103\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\104\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\105\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\110\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\112\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\113\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\114\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\115\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\116\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\117\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\118\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\120\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\121\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\123\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\124\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\125\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\127\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\129\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\130\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\131\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\132\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\133\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\134\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\135\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\136\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\137\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\138\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\139\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\140\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\141\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\142\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\143\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\144\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\145\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\146\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\147\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\148\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\149\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\150\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\151\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\152\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\153\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\154\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\155\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\156\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\157\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\158\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\160\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\161\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\162\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\163\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\164\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\165\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\166\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\167\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\168\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\169\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\170\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\171\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\172\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\173\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\174\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\175\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\176\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\177\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\178\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\179\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\18\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\180\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\187\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\188\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\189\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\190\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\191\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\192\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\193\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\194\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\195\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\196\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\197\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\198\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\199\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\20\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\200\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\203\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\22\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\23\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\27\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\28\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\29\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\3\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\30\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\31\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\32\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\5\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\64\jl\AndroidManifest.xml;obj\DB_SMHOME\100\lp\66\jl\AndroidManifest.xml" --out "obj\DB_SMHOME\100\android\AndroidManifest.xml"

@Redth obj\DB_SMHOME\100\android\AndroidManifest.xml does not exist

same thing on macOS
same on macOS.docx

@xamarindevelopervietnam are you able to create a .binlog and share it?

@Redth how to create .binglog?

https://docs.microsoft.com/en-us/visualstudio/msbuild/obtaining-build-logs-with-msbuild?view=vs-2019

Having the same issue on Mac.

We are having the same issue. We do use PackageReference in all csproj files.
Executing the command from the command line (from Android project folder) gives the next error:
/Users/Seifer/Projects/Proj/Droid/obj/Debug/android/AndroidManifest.xml:49:9-51:51 Error:
	Attribute meta-data#onesignal_app_id@value at AndroidManifest.xml:49:9-51:51 requires a placeholder substitution but no value for <onesignal_app_id> is provided.
/Users/Seifer/Projects/Proj/Droid/obj/Debug/android/AndroidManifest.xml:53:9-55:70 Error:
	Attribute meta-data#onesignal_google_project_number@value at AndroidManifest.xml:53:9-55:70 requires a placeholder substitution but no value for <onesignal_google_project_number> is provided.

OneSignal package referenced only from the Core project. Simply updating nuget from 3.6.0 to 3.7.0 fixed the issue.


Improve AWS credentials parsing verbosity

Codecov Report

Merging #47 (1ab5c8f) into main (df9b365) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
+ Coverage   96.74%   96.86%   +0.12%
==========================================
  Files          16       16
  Lines        1013     1052      +39
==========================================
+ Hits          980     1019      +39
  Misses         33       33

Impacted Files
Coverage Δ

src/s3.rs
99.67% <100.00%> (+0.04%)
: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 df9b365...1ab5c8f. Read the comment docs.


REGEX functions not visible in Tableau

I've connected to Exasol using the .trex connector and I'm not seeing the REGEX functions available in the Tableau calculations Window. Let me know what I can do to help troubleshoot. Happy to jump on a WebEx.

Thank you @ugamarkj  for your ticket. I will look into this once Kerberos support #15 is finished.

This bug is fixed with release 0.3.0 of the connector.


fix: podcast style

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your default branch!
[x] Make sure you are making a pull request against the default branch (left side). Also you should start your branch off default branch.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.
[x] I have added necessary documentation (if appropriate)

Linked Issues
Fixes #354
Description
Please describe your pull request.
❤Thank you!
Post merge checklist

[x] Follow steps from the guidelines for contributing to this repository.
[x] If you are a new contributor, ping in the thread and one of the maintainers will add you to all-contributors list.

@kanhaiya88628 more than requested time already assigned.

@kanhaiya88628 sync the code with the latest changes.


SnackBar without duration doesn't show

Bug, feature request, or proposal:
Bug in MdSnackBarModule with the following simple code:
this.snackBar.open('hello');
setTimeout(() => {
   this.snackBar.open('world');
}, 2000);

What is the expected behavior?
A snackBar with "hello" should be opened, 2 seconds later it should be dismissed and a snackBar with "world" should be opened.
What is the current behavior?
A snackBar with "hello" is opened, 2 seconds later it is dismissed and the snackBar with "world" doesn't appear.
What are the steps to reproduce?
Demo
Weirdly, it works if I define a duration for the "world" snackBar: demo.
What is the use-case or motivation for changing an existing behavior?
It's not consistent to have to define a duration in some cases, not in others.

I'm seeing the same problem. Looking at https://github.com/angular/material2/blob/master/src/lib/snack-bar/snack-bar.ts#L83 it seems like the intentional behavior would be to close the open one and once the closing animation is done, open up the new snackbar.
Effectively this doesn't seem to work as expected.
Could it be connected to this change https://github.com/angular/material2/commit/2732bb4fbb953b3778b9b7de6d592fa861b9644d ?


Getting Started needs some explanation of why there is no DashBoard for Linux.

File: get-started/index.md
I am just getting started but I am stuck with this sentence "To access the dashboard, follow the instructions for either Mac or Windows. ". I am not using Mac or Windows. Do I need to download something else for Linux?
Please could the get-started page be changed to explain what to do on Linux.
thanks

/assign


Refactor/simplify config

Some spring cleaning, notice from the last commit that the prod and dev configs have not changed (with one tiny exception for the prod config to include tsx files in the banner plugin) but the profile config has changed substantially.
Largely this is due to the limited use of profiling and the belief we should be profiling our prod config (or as closely as we can) when and if we do it.
Also, i left the rspack config out of this PR since it has not stabilized yet, once they get to v1 we can reuse parts of the webpack base to build that as well.

Base config changes (ordering only of plugins) -

Prod config changes (adding tsx to banner plugin) -

And the profile config (which is the bulk of the changes, doesn't even fit on one screenshot -

, etc. but it still profiles a prod build as expected.

bump


ansible: temp dir handling is broken on master

Some recent change has broken master, but looking into it revealed more inconsistencies between Mitogen and vanilla Ansible.
There are a seemingly endless selection of cases to emulate:

AnsibleModule.tmpdir reuses a controller-supplied directory (ansible_tmpdir) if it is present.
If ansible_tmpdir is not present, it creates and manages its own subdirectory under the vars/tilde-expanded ansible_remote_tmp template passed by _update_module_args().
If ansible_tmpdir isn't writeable, it creates and manages its own subdirectory in the system default temp directory.

Random logic:

ansible_tmpdir is present if ActionBase._make_tmp_path() was ever called, and become=false or become=root
_make_tmp_path() may or may not be called depending on the value of ANSIBLE_PIPELINING and ANSIBLE_KEEP_REMOTE_FILES

Two task variables are passed to the module executing on the child:

ansible_tmpdir: set if _make_tmp_path() has ever been called and become=false or become=root
ansible_remote_tmp: the unexpanded version of the template used to set ansible_tmpdir by _make_tmp_path()

One environment variable is passed to the module executing on the child:

ANSIBLE_REMOTE_TMP: set by _make_tmp_path() if become=false or become=root. The expanded version of the template, i.e. equivalent to ansible_tmpdir.

When pipelining=false and become=root, AnsibleModule.tmpdir is /home/sshuser/...
When pipelining=true and become=root, AnsibleModule.tmpdir is /root/...
When pipelining=true and become=mitogen__user1, AnsibleModule.tmpdir is /home/mitogen__user1/...
When pipelining=false and become=mitogen__user1, AnsibleModule.tmpdir is "Failed to set permissions on the temporary files Ansible needs to create when becoming an unprivileged user (rc: 1, err: chown: /var/tmp/ansible-tmp-1532536799.25-196509554541606/: Operation not permitted\nchown: /var/tmp/ansible-tmp-1532536799.25-196509554541606/custom_python_remote_tmp.py: Operation not permitted\n}). For information on working around this, see https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user"

If you drop by IRC, jborean or I can explain the logic behind the various cases in tmpdir handling.
ANSIBLE_REMOTE_TMP should be removed (it was an earlier implementation of a feature for 2.4 that got mostly changed... that particular couple lines of code was missed when the rest of it was removed). but I think the others all have reasons.


Force restart / deploy

There should be a "simple" way to force a restart / a deploy for whatever reason. Or i think it should?

Vili-dash is a "simple" but lacking solution to this. Reopen if this topic needs to be looked at at a later time.


Update mesos dependency to 0.27.0

We require now mesos 0.27.0 to build the plugin but we retain runtime compatibility with versions older than 0.25.0 by using reflection for the changed API.
External containerizer has been deprecated in Mesos, so support has been removed from the plugin.
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

Would also appreciate an update to 0.27 and the removal of deprecated functionality.


Make ext4 rootfs great again

This set of patches fixes the ext4 rootfs generation. Main problem was in the image size difference between squashfs image and ext4 which leads to an incorrect GPT table. The solution is to calculate resulting image dynamically.
Patch makes creation of the ext4 rootfs possible and also has a size reduction for the installer.raw images:
                      before      after
     installer.raw     592Mb      296Mb

Unfortunately for the rootfs we have a hardcoded partition size equal to 512Mb, which can't be changed, otherwise upgrade logic fail when we try to fit bigger rootfs into smaller one partition. This means that upgrade from squashfs image to ext4 is currently impossible. But who cares.
Now live image can be generated as following:
  make ROOTFS_FORMAT=ext4 live

My motivation to generate ext4 rootfs is to have possibility to persist changes on eve while running.
Another great feature becomes possible is to "patch" resulting qemu image with changed files and not generate rootfs from scratch, which can take minutes of CPU time.
This patch changes the pkg/mkverification-raw-efi/make-raw, which almost a copy of the original one. I kindly ask @jsfakian to help me to review and to test the resulting verification images, that those work and nothing is broken because of my changes.
cc: @mikem-zed

Does this change anything in the build docs here? Both internal as to how build is done and the UX (which we care about more)?

Another great feature becomes possible is to "patch" resulting qemu image with changed files and not generate rootfs from scratch, which can take minutes of CPU time

How does that work?

What's the impact on the current squashfs installer and live image from the dynamic size? I can't tell whether the partition sizes will be dynamic or fixed with these changes.

Answering my own question, the partition size (at least in the live image) is the size of the image.
linuxkit-525400123456:~# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    0   64G  0 disk
├─sda1   8:1    0   36M  0 part
├─sda2   8:2    0  232M  0 part /
├─sda3   8:3    0  232M  0 part
├─sda4   8:4    0    1M  0 part
└─sda9   8:9    0 63.5G  0 part /persist
That means it can't be used to update to a slightly larger image.
Can't we fix that to use the same fixed size for the partitions?

@eriknordmark

That means it can't be used to update to a slightly larger image.
Can't we fix that to use the same fixed size for the partitions?

This is very good point, I forgot about upgrade. Actually without borrowing free space from the /persist we are screwed by default to upgrade to image greater than these hardcoded values. So in the future if image grows this has to be fixed by doing dangerous operations on the /persist. Now I can fix that by returning old values and taking max.

I cloned this workspace and tried what works on master, and it fails to boot the installer.

This was fixed just before your comment, here https://github.com/lf-edge/eve/compare/8ab4fde0385564de8f57a560a255a6d8bed92179..21b71376ddaa6789ee9303e52b63c737743f2c9d
Please checkout once again.

@eriknordmark @jsfakian
Folks, now installer and verification images should work. I would appreciate if you offer me a hand in testing this.
Also the rootfs partition size is kept as is, i.e. 512Mb, so upgrade won't fail. This is for the imga, imgb partitions only, the installer/verificator keeps rootfs as a file on fat32, so we don't keep this max value.

Another great feature becomes possible is to "patch" resulting qemu image with changed files and not generate rootfs from scratch, which can take minutes of CPU time

How does that work?

@deitch here #3842. Can we continue improving? Still a lot of room for improvements, but help of the linuxkit is required.

This needs to be approved and merged before #3842

Also the rootfs partition size is kept as is, i.e. 512Mb, so upgrade won't fail. This is for the imga, imgb partitions only, the installer/verificator keeps rootfs as a file on fat32, so we don't keep this max value.

So this is ready to go?

Still a lot of room for improvements, but help of the linuxkit is required

For this PR? Or for next steps you want in #3842? Or for something else beyond that?

Also the rootfs partition size is kept as is, i.e. 512Mb, so upgrade won't fail. This is for the imga, imgb partitions only, the installer/verificator keeps rootfs as a file on fat32, so we don't keep this max value.

So this is ready to go?

Still a lot of room for improvements, but help of the linuxkit is required

For this PR? Or for next steps you want in #3842? Or for something else beyond that?

This is ready to go. There was some important concern from @eriknordmark , I fixed that. If he does not have any objections  or anyone else, this can be merged. Also would be great if @jsfakian can help me with verification image. Last time he spotted one thing, which breaks the image. This is also fixed.

Yeah, I see @eriknordmark still has changes pending. Let's let him sign off and merge it in. Hats off @rouming


Add a php artisan command to destroy the tunnel

I've just started using this package and think it's awesome. What I've noticed though is that there either might be an error in the setup or it just needs an option to also close the tunnel again.
Currently there isn't any option to close / destroy the tunnel, right? I would like to have that option.
php artisan tunneler:deactivate or php artisan tunneler:destroy would make sense..?
The reason I'm coming up with this is that I need it for multiple projects simultaneously. Now when I open one tunnel it works for that project, when I then try to open another tunnel in another project directory, the artisan command tells me that "The Tunnel is already Activated." which makes me unable to connect to that project as well.
Or did I just miss some configuration in the .env where we would be able to give the tunnel a name or tag or something? If I just missed some things then maybe an update for the README would be appreciated. :)

PS: As I'm working simultaneously on multiple projects where I need the Tunneler open to different servers, it might make sense to enable opening multiple tunnels. Not sure how much rework or change efforts that would require though or if I would just need to make adjustments in the .env / config() setup.


The settings tab is gone

Did you check for existing issues?

[X] I have searched the open and closed bugs.

Platform
PC
Version
ee84edf
Description

The settings tab is just gone, I literally can't find it. (maybe im blind)
Repro
No response
Details
No logs

I found why it was missing, now the creator himself customizes the values for certain tabs in the settings, sorry for the mistake

Fixed in 5eb9c68


environment.yml in need of update

2017-10-31 12:09:28,027 ERROR   esmvaltool.main: Program terminated abnormally, see stack trace below for more information
Traceback (most recent call last):
File "/group_workspaces/jasmin/ncas_cms/valeriu/anaconda2/lib/python2.7/site-packages/ESMValTool-1.1.1.dev1344+g8500eaa.d20171030-py2.7.egg/esmvaltool/main.py", line 495, in run
main()
File "/group_workspaces/jasmin/ncas_cms/valeriu/anaconda2/lib/python2.7/site-packages/ESMValTool-1.1.1.dev1344+g8500eaa.d20171030-py2.7.egg/esmvaltool/main.py", line 225, in main
ncl_version_check()
File "/group_workspaces/jasmin/ncas_cms/valeriu/anaconda2/lib/python2.7/site-packages/ESMValTool-1.1.1.dev1344+g8500eaa.d20171030-py2.7.egg/esmvaltool/interface_scripts/auxiliary.py", line 78, in ncl_version_check
if int(out[1].split(".")[0]) < 6:
ValueError: invalid literal for int() with base 10: 'ncl: error while loading shared libraries: libopenblas'
(esmvaltool) [valeriu@jasmin-sci1 ESMValTool_Testing_Len]$ which ncl
/group_workspaces/jasmin/ncas_cms/valeriu/anaconda2/envs/esmvaltool/bin/ncl
(esmvaltool) [valeriu@jasmin-sci1 ESMValTool_Testing_Len]$ ncl --version
ncl: error while loading shared libraries: libopenblas.so.0: cannot open shared object file: No such file or directory
FIX: conda install -c anaconda openblas

Digging into this a bit, it seems our environment.yml is not quite consistent. We have specified versions for a number of libraries, and these now conflict with the latest ncl install.
I propose we take this as a good opportunity to clean up the environment.

Should be fixed in #142. Let me know if you have further problems.


Decode / encode round trip produces unexpected results

Here's something I ran into:
from threefive import Cue

orig = '/DAlAAAAAyiYAP/wFAVNqW2Jf+//WP/YQ/4AUnrYAAEBAQAAGk9JoA=='
orig_cue = Cue(orig)
orig_cue.decode()

new_cue = Cue(orig_cue.encode())
new_cue.decode()

print(orig_cue.get()['info_section']['pts_adjustment_ticks'], new_cue.get()['info_section']['pts_adjustment_ticks'])

Different results for the two values:<PHONE_NUMBER>99

I think the issue is probably in the encode process:

_encode_pts_adjustment uses nbin.add_90k(self.pts_adjustment, 33)
add_90k uses floating point math instead of integer math.

It looks like pts_adjustment_ticks is still saved as an integer, so perhaps it could be encoded again directly instead of going through the computed value?

Good catch.
You're right, I should be using ticks there.
I'll try to push an update tonight.
You know you can use dot notation, right?

print(cue.info_section.pts_adjustment_ticks, new_cue.info_section.pts_adjustment_ticks)

I added this to the SCTE35Base class

    @staticmethod
    def as_ticks(float_time):
        """
        90k timestamps to ticks
        """
        return  int(round(float_time * 90000))

I updated the SpliceInfoSection class  ( I applied similar updates to Splice Commands and Descriptors)

    def _encode_pts_adjustment(self, nbin):
        """
        encode SpliceInfoSection.pts_adjustment_ticks
        """
        if not self.pts_adjustment_ticks:
            self.pts_adjustment_ticks = 0
            if self.pts_adjustment:
              self.pts_adjustment_ticks =  as_ticks(self.pts_adjustment)
        self._chk_var(int, nbin.add_int,"pts_adjustment_ticks", 33)

then I ran your test.

a@debian:~/build/scte35-threefive$ pypy3
Python 3.8.13 (7.3.9+dfsg-5, Oct 30 2022, 09:55:31)
[PyPy 7.3.9 with GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>> from threefive import Cue
>>>> orig = '/DAlAAAAAyiYAP/wFAVNqW2Jf+//WP/YQ/4AUnrYAAEBAQAAGk9JoA=='
>>>> orig_cue = Cue(orig)
>>>> orig_cue.decode()
True
>>>> new_cue = Cue(orig_cue.encode())
>>>> new_cue.decode()
True
>>>> print(orig_cue.info_section.pts_adjustment_ticks, new_cue.info_section.pts\
_adjustment_ticks)
207000 207000

I'll push a new pip release shortly

pip it up.
latest is 2.3.63


antsRegistration step size differences from ANTs

I have noticed that antsRegistration with SyNCC in R has much bigger step sizes than antsRegistrationSyN.sh for linear transformation (i.e., Rigid[1], Affine[1] vs Rigid[0.1], Affine[0.1]). Does this make a huge difference, is this set on purpose so different in R?

A quick report on the comparison ANTs vs ANTsR:
antsRegistration with SyNCC has better registration than the shell antsRegistrationSyN.sh. I have noticed this before as well. The example results are here:
templateBrain.nii.gz
ANTsR_withSyNCC.nii.gz
[ANTs_fromShell
RegistrationMask_without_Lesion.nii.gz
.nii.gz](https://github.com/stnava/ANTsR/files/369222/ShellSubOntemp.nii.gz)
Commands that lead to above results:
Shell
antsRegistration --dimensionality 3 --float 0
--output [$thisfolder/pennTemplate_to_${sub},$thisfolder/pennTemplate_to${sub}_Warped.nii.gz] --interpolation Linear --winsorize-image-intensities [0.005,0.995] --use-histogram-matching 0 --initial-moving-transform [$t1brain,$template,1] --transform Rigid[0.1] --metric MI[$t1brain,$template,1,32,Regular,0.25] --convergence [1000x500x250x100,1e-6,10] --shrink-factors 8x4x2x1 --smoothing-sigmas 3x2x1x0vox --transform Affine[0.1] --metric MI[$t1brain,$template,1,32,Regular,0.25] --convergence [1000x500x250x100,1e-6,10] --shrink-factors 8x4x2x1 --smoothing-sigmas 3x2x1x0vox --transform SyN[0.1,3,0] --metric CC[$t1brain,$template,1,4] --convergence [100x70x50x20,1e-6,10] --shrink-factors 8x4x2x1 --smoothing-sigmas 3x2x1x0vox
-x $brainlesionmask
#ANTsR
regist=antsRegistration(fixed = n4denoisedbrain, moving = templatebrain, typeofTransform = 'SyNCC', mask = masknolesion)

@ntustison - see above .... not sure if you have any guesses as to the meaning of this observation from @dorianps .... it may be relevant in that i recently changed some of the default behavior in antsRegistration.R ... may need to change antsRegistration.R again for backward compatibility.

i addressed SyNCC backward compatibility with this commit 6b4986efba37c05d7e26e2551e1d4025f7654f1a

I don't know.  As you know, it's hard to make an assessment for n=1 cases.  It doesn't look like the difference is occurring during the linear stages.  Would be nice to actually see the antsRegistration call for the SyNCC option for this particular case.


'haxelib' is not recognized as an internal or external command

Describe your problem here.
for some reason it wont work. I have haxe 4.1.5, and I restarted my pc. pls help.
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no.

i dont know a lot abt this but try reinstalling i guess? worked for me once

Haxe 4.1.5 is outdated and you cannot compile the Flixel project. Please switch to 4.2.5 or to latest


add .Now() to datetime package

Mainly putting this up for consideration, could easily put this abstraction in the consuming code.
Also not sure if there's a way to test this. Is there a way to mock a package that isn't injected in go?

Reasoning behind this: vet doesn't like DateTime{time.Now()} (composite literal uses unkeyed fields)

Is the test failure real? Otherwise lgtm.
On Wed, May 10, 2017 at 3:21 PM, Jesse Ditson<EMAIL_ADDRESS>wrote:

Reasoning behind this: vet doesn't like DateTime{time.Now()} (composite
literal uses unkeyed fields)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/3472#issuecomment-300629662, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAE6BEPUDrxAKl_B-gPGBhtjv2Q6bt2Lks5r4jhmgaJpZM4NXSo5
.

Failures look unrelated to me, it's in go/types (TestStreamingMap2 and TestMapSuite4KStructs). They don't fail locally for me, so not really sure what's going on here. Perhaps intermittent?

jenkins: build this

I haven't seen this test failure before. The weird thing is that from the output, the look like they're equal.


[WIP] Service registration extensions

Some initial ideas on baking service registration extensions for .NET Core into the library itself to avoid the need for repetitive boilerplate in our consuming applications.
I've included several different flavours of registration method, maybe too many, but we can always remove some if we think it's a bit too excessive.
Main use cases I've tried to cater for are:

Simple registering of the default required types, but with the step to configure the host left to the integrator to achieve by other means, such as using Configure() from the Microsoft.Extensions.Configuration package.
Simple registration with a string for the host name and an optional prefix.
Registration from a provided StatsDConfiguration instance.
Registration using a callback delegate to configure a StatsDConfiguration object passed to the caller, similar to Configure().
Registration with a factory method to provide a StatsDConfiguration for us to use provided by the callee.
Variations on the above but with IServiceProvider as a delegate parameter so the integrator can lazily-resolve their other services  to populate/provide a StatsDConfiguration instance.

Use the included tests as pseudo-examples of use cases. Proper documentation can be added later after review/refinement.
For now, I've intentionally only supported this with netstandard1.6 to avoid polluting net451 consumers with all the extra libraries from ".NET Standard Land" full framework projects would otherwise pull in and cause a mess/bloat. We can revisit that if there's a nice way to make it available for them without introducing a tonne of additional dependencies.

Good idea, I suggest that we start with a minimal set of extensions for only NetStandard/NetCore apps, and which cover the actual scenarios where we are using StatsD v2 in our apps - there are a couple of these already.

I might also update this to register the endpoint source as well, as that’d make registering a custom IStatsDTransport easier (I think).

Plugging this into an internal application, I got the StatsD registration down to:
services.AddSingleton<IStatsDTransport, CustomUdpTransport>();
services.AddStatsD(
    (provider) =>
    {
        var options = provider.GetRequiredService<CustomOptions>().StatsD;
        var logger = provider.GetRequiredService<ILogger<StatsDConfiguration>>();

        return new StatsDConfiguration()
        {
            Host = options.Hostname,
            Port = options.Port,
            Prefix = options.Prefix,
            OnError = (error) =>
            {
                logger.LogWarning(error, "Failed to publish metric to StatsD. {Message}", error.Message);
                return true;
            },
        };
    });

Is it time to look at feeding in the IStatsDTransport via the config object?

I don't think so, I don't see that as configuration, personally. It's more DI registration.

This is really nice @martincostello. With the 2 examples you gave I think I slightly prefer the Action<StatsDConfiguration> but not strongly enough to make a case for it.
Would it be worth making this a separate package, I know that it is an abstractions package that is only present in the netstandard target, but it still makes me feel slightly uncomfortable having it all in one package.

It's quite common for netstandard stuff to ship with its own IServiceCollection extensions nowadays though. It would seem a bit weird to me in a netcoreapp application to have to install a non-obvious extra package just get the easiest "plug-in-and-go" experience.

Oh right, I thought the opposite, but I'm thinking of MediatR and AutoMapper. Do you have examples?

To be honest I'm thinking of more the core framework packages themselves (HttpClientFactory is doing this), rather than 3rd party things, but a whole extra package for 1 class seems like overkill.

Yeah, that's a fair point 👍

So I think the two outstanding questions I have are:

Which overloads do we want to drop?
Does this justify a bump for the next version of 2.1.0 instead of 2.0.1?

it should be version 2.1.0

MINOR version when you add functionality in a backwards-compatible manner
https://semver.org/

Version bumped, so which overloads do we want if not all?
My suggestions are:

AddStatsD(string host, string prefix = null) - Simplest use case to get things usable.
AddStatsD(Func<IServiceProvider, StatsDConfiguration> configurationFactory) - Allows you to provide your own configuration object, with the service container available to allow you to resolve any other dependencies you might need to be able to do that. This is the one in the first registration example above.
AddStatsD() - One-liner that configures everything you need but leaves you to populate the configuration yourself somehow, either by registering it yourself beforehand, or using Configure().

@AnthonySteele @stuart-lang poke

@AnthonySteele Have trimmed the AddStatsD(...) overloads as discussed this morning.


spark: tests run multiple times

Tests in app:test are run both in build-integration-spark and integration-test-integration-spark (each is run 3 times because of different spark versions). The workflow should be modified to avoid rerunning jobs that already succeeded.

I think we mitigated it a moment ago with those lines:
https://github.com/OpenLineage/OpenLineage/blob/863b42e943417db969cc5b943f12dbc6e4004565/integration/spark/app/build.gradle#L242-L244


Add blocklist-update.

Thank you very much for your contribution.
Don't forget to tick the checkbox in supported operations list 😉

Cheers @ngoquang2708


Update calibre to 2.77.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Merged as 411a04dbf859a5700bbe791a35fcf76655f6a40e.


Create About Page

Create the About page as seen in the Figma design.
With the help of already created components such as

Top Navigation,
Bottom Navigation bar,
Cards (Ambassadors, Organizers and community members)
Join Our Community button

seen in closed issues here, create the about page.

good morning @PetraAG, please i will love to work on the about page

Alright... go ahead.  Assigned


TextInput autoCapitalize="words" not working when keyboardType prop is passed on Android

When adding autoCapitalize="words" and keyboardType with any value, on Android, nothing is auto-capitalized. There have been other issues regarding this, but they have been closed, locked and since ignored (#11776 #8932).
In older issues/comments it's stated that this happens only when margin or padding is applied through style on the TextInput, but this is not the case. It also happens without.
If this has been fixed in React Native 0.60+, please let me know. I'm only able to test on 0.59.
React Native version:
info
React Native Environment Info:
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 4.79 GB / 15.89 GB
Binaries:
Yarn: 1.1.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.10.3 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-191.8<IP_ADDRESS>91312
Steps To Reproduce

Add autoCapitalize="words" to a TextInput.
Also add keyboardType=... with any value. Even undefined, even though undefined props are supposed to be ignored in React.

Describe what you expected to happen:
The first letter of each word is capitalized.

I investigated this issue on master, it works correctly with the physical keyboard; however, not with soft input (inputs from your computer).
With soft input notice how the capitalize on the keyboard turns on with every space. This is a dev environment issue, not a bug to a shipped app.

@safaiyeh It's not. I've confirmed this issue on Android devices in development and production. It occured on every Android device I tested on. The only workaround was to remove the keyboardType prop. If it's only happening with soft inputs for you, there might be other factors (props) that also impact this behavior, but it's definitely not a PC-only bug.

@WouterFlorijn I understand now.
Android's InputType.TYPE_TEXT_FLAG_CAP_WORDS or any InputType.TYPE_TEXT_FLAG_CAP_* only works with InputType.TYPE_CLASS_TEXT with no text variations like password + email.
So the only time this is true is when there is no prop or keyboardType={'default'}
Current behavior
no prop ✅
keyboardType={'default'} ❌

Submitted a PR to fix this bug: https://github.com/facebook/react-native/pull/27523

This can be closed as the fix was merged in.
cc @TheSavior

Ao invés de usar AutoCapitalize="Words"
é mais fácil manipular a entrada de texto com javascript
ex..:
<TextInput
style={styles.searchBar}
ref={(ref) => { ref }}
placeholder="(Ex..:Fotografia, Advocacia, Odontologia)"

onChangeText={text => {setSearch(text.charAt(0).toUpperCase() + text.slice(1))}}
onClear={index => {setCategoria(categoria)}}
keyExtractor={pesquisa => pesquisa._id}
value={pesquisa}
placeholderTextColor='#4EA3DA'
placeholderTextSize="10"

/>
ext.charAt(0).toUpperCase() + text.slice(1)
Essa parte do codigo faz com que toda entrada no textinput seja com a primeira letra maiúscula e o restante minuscula.
Espero poder ter ajudado!

I keep having the problem

autoCapitalize still doesn't work even after removing multiline & keyboardType props. Any update on this?

@KPS250 any update have you resolved ?

any updates on this? Autocap still doesn't work on Android


Drop Down Menu is not shown

Hey everyboy,
I have some problems with the qtwebengine in this version of the meta-qt5:
1650757f4182435a63985f73e477ed80927f0eac
If I click on some html dropdown menus the menu is not popping out.
I can reproduce it with this website: Link to webpage
On the qtwebengine git I found this commit that handles some problems with the dropdown menu. But the qtwebengine version thats in the meta-qt5 is newer that this one.
Link to Commit
Does anyone else have the same problem or can recreate it?

Hey everyone,
I found this Bug in the QT Bugreports:
Link
Someone else have the same problems with embbeded devices.

I'm experiencing the same issues. Have a look: https://bugreports.qt.io/browse/QTBUG-87281


Linker error in libz on Linux

Linking ./.build/x86_64-unknown-linux/debug/KituraPackageTests.xctest
/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:function _T08NIOHTTP122HTTPResponseCompressorC19deinitializeEncoder33_E8A369BA8CC72FD6D05117C456504CA2LLyyF: error: undefined reference to 'deflateEnd'
/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:function _T08NIOHTTP119PartialHTTPResponse33_E8A369BA8CC72FD6D05117C456504CA2LLV12compressBody3NIO10ByteBufferVSgSC10z_stream_sVz10compressor_AF0oP9AllocatorV9allocators5Int32V4flagtF: error: undefined reference to 'deflateBound'
/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:function _T0SC10z_stream_sV8NIOHTTP1E15deflateToBuffer33_E8A369BA8CC72FD6D05117C456504CA2LLs5Int32V3NIO04ByteE0Vz6buffer_AG4flagtFSis016UnsafeMutableRawE7PointerVcfU_: error: undefined reference to 'deflate'
/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:/root/Kitura/.build/x86_64-unknown-linux/debug/NIOHTTP1.build/HTTPResponseCompressor.swift.o:function CNIOZlib_deflateInit2: error: undefined reference to 'deflateInit2_'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
<unknown>:0: error: link command failed with exit code 1 (use -v to see invocation)

swift test -Xlinker -lz is used as a temporary work-around for the above issue.

@nethraravindran Does this happen on both 14.04 and 16.04?

@pushkarnk No, this doesn't happen on 14.04

A found a handful of projects/forums in which this problem was discussed:
https://elixirforum.com/t/ubuntu-exec-erlexec-not-found/10499/6
https://github.com/arybczak/ncmpcpp/issues/138
https://github.com/TrinityCore/TrinityCore/issues/19074
https://github.com/grpc/grpc/issues/11768
All of them talk about solving the problem using -lz but there's no drill-down into why this problem didn't show up on Ubuntu 14.04.
On Ubuntu 16.04, I ran ldconfig and I can see libz present in the search path:
ldconfig -v | grep "libz"
	libz.so.1 -> libz.so.1.2.8

Does the linking still fail if we add CNIOZlib to the dependencies of the KituraNet target?

That sounds to me like either zlib or pkg-config isn't installed. You can test this by running
pkg-config --libs zlib

which should output
-lz

Or (on Debian systems) you should be able to see if zlib is installed with development headers like this
dpkg -l zlib1g-dev

And I can see that the trusty images (Ubuntu 14.04) have pkg-config pre-installed.

@nethraravindran Can we try adding pkg-config to the apt-get install ....  list in build.sh

@pushkarnk Sure! Have created the PR :https://github.com/IBM-Swift/Kitura-NIO/pull/77

PR merged. Closing this issue.


fatal: not a git repository (or any parent up to mount point /github)

Hello,
I'm trying to use the fastpages action to convert my notebooks to .markdown and publish them on my github.io page. I've run into an error while adding the action to my repository (https://github.com/novice03/novice03.github.io/runs/2671567434). It says:
Run fastai/fastpages@master
Agent pid 9
No notebooks were modified
fatal: not a git repository (or any parent up to mount point /github)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
My ci.yml file is located at https://github.com/novice03/novice03.github.io/blob/main/.github/workflows/ci.yml. How can I fix this?

I cannot troublehsoot this error because you have pointed me at a private repo.   Closing this issue


Gem breaks Rails 5 belongs_to required: true by default settings

Described in detail here: https://github.com/rails/rails/issues/26557

Are you actually calling deep_clone somewhere in the update call you describe in rails/rails#26557?

Closing due to lack of info.


It is not documented how to start the migration process with an existing Serverpod project

Describe the bug
document how to start the migration process
To Reproduce
Steps to reproduce the behavior:

read the docuentation on migrations. It describes migration but not how to start it. Do we need to force the initial migration to be created?

Expected behavior
A clear and concise description of how to start the migration process.
Screenshots
If applicable, add screenshots to help explain your problem.
Serverpod versions

CLI Version: Run serverpod version to determine the version of installed tooling.
Library version: Check the pubspec.yaml file for the version of Serverpod you are using.

Platform information
On which platforms do you experience the issue. Please provide as much information here as you can. Where are you running the server, which front end device are you using?
Additional context
Add any other context about the problem here.

Hey @mike-novarca!
This should be covered by the documentation on this page: https://docs.serverpod.dev/upgrading/upgrade-to-one-point-two#initialize-the-migration-system
Is there anything missing there?

The documentation on the linked page are not correct

@mike-novarca

The documentation on the linked page are not correct

Could you describe in what way?

It does not work as stated

@mike-novarca do you mean on a production server like aws or gcp maybe, because I also don't really understand how that would work when the server is already deployed. But that may be me 😃


AmqpError: Out of available 0 channels

The server I'm connecting to has a channel max of 0, which appears to mean unlimited.  This throws an OverCapacityError.
amqp10:connection Connected with params { maxFrameSize= 32768 , channelMax= 0 , idleTimeout= 120000 , remoteIdleTimeout= 120000  } +0ms
https://github.com/noodlefrenzy/node-amqp10/blob/master/lib/connection.js#L341

@mfisch04 what server are you connecting to? The spec makes no mention of a special case for 0, this sounds like something that needs to be shoehorned into a policy


Ubuntu - installation fails with "No package freetype2 found"

Ubuntu 16.04, with all the dependencies listed in the README installed. The full error is

--- stderr
configure: error: Package requirements (freetype2) were not met:
No package 'freetype2' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables FREETYPE_CFLAGS
and FREETYPE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [/tmp/cargo-install.qGDQTA1ENDff/release/build/servo-fontconfig-sys-ac2ac06b8cdaf817/out/Makefile] Error 1
thread 'main' panicked at 'assertion failed: Command::new("make").args(&["-R", "-f",
"makefile.cargo"]).status().unwrap().success()', /home/frank/.cargo/git/checkouts/libfontconfig-3d5e920c02c2e53f/5c1845e/build.rs:17:5
note: Run with RUST_BACKTRACE=1 for a backtrace.
warning: build failed, waiting for other jobs to finish...
error: failed to compile alacritty v0.1.0 (https://github.com/jwilm/alacritty#6debc4f3), intermediate artifacts can be found at /tmp/cargo-install.qGDQTA1ENDff
Caused by:
build failed

Have you tried rebooting after installing the freetype2 dependency? Also make sure the package was actually installed successfully.

Yes, all the dependencies installed succesfully (the freetype package listed for ubuntu was freetype6-dev instead of freetype2, although that shouldn't matter). Unfortunately I still ran into the same error after restarting.

It should be libfreetype6-dev.

You're correct, I made a mistake in my comment. That is the package I had installed however, so that is not the source of this problem.

Manually exporting PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig solved it in my case.


Role Assignment error 400 -- {"error":{"code":"BadRequestFormat","message":"The request was incorrectly formatted."}}

Discussed in https://github.com/Azure/enterprise-azure-policy-as-code/discussions/469

Originally posted by arretesting February  2, 2024
While using the newly uploaded Deploy-RolesPlan.ps1, which now includes Remove/Get/Set-AzRoleAssignmentRestMethod, I am receiving the following error message from the compilation for the @ splat.
Is there anyone who has faced the similar error message with the most recent push?
`> .\Deploy-RolesPlan.ps1
===================================================================================================
Read global settings from 'C:\Git\EpacTest\Definitions/global-settings.jsonc'.
PowerShell Versions: 7.4.1
PAC Environments: epac-dev, epac-prd
Definitions root folder: C:\Git\EpacTest\Definitions
Input folder: C:\Git\EpacTest\Output
Output folder: C:\Git\EpacTest\Output
Select Policy as Code environment [epac-dev, epac-prd]: epac-dev
Environment Selected: epac-dev
cloud      = AzureCloud
tenant     =
root scope = /providers/Microsoft.Management/managementGroups/EPAC-DEV
Telemetry is disabled

Deploy Role assignments from plan in file 'C:\EpacTest\Output/plans-epac-dev/roles-plan.json'
Plan created on 2024-02-02 16:10:20Z.

===================================================================================================
Add (44) new Role assignments
Assignment 'Virtual networks should be protected by Azure DDoS Network Protection', principalId 94dc2ae6-eb13-4991-9e6a-31945050563b, role Network Contributor(4d97b98b-1d4f-4787-a291-c67834d212e7) at /providers/Microsoft.Management/managementGroups/EPAC-DEV-Platform-Connectivity
Write-Error: C:\Git\EpacTest\Scripts\Deploy\Deploy-RolesPlan.ps1:155
Line |
155 |              Set-AzRoleAssignmentRestMethod @splat -IgnoreDuplicateErr …
|              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Role Assignment error 400 -- {"error":{"code":"BadRequestFormat","message":"The request was incorrectly formatted."}}`

Hi @techlake , @anwather , and the rest of you co-developers,
Do you maybe have some ideas on how I can proceed from here?
I ran the deployment using the debug flag but that didn't make me any wiser as everything looks okay to me:
DEBUG: ============================ HTTP REQUEST ============================

HTTP Method:
PUT

Absolute Uri:
https://management.azure.com/providers/Microsoft.Management/managementGroups/EPAC-DEV-Platform-Connectivity/providers/Microsoft.Authorization/roleAssignments/c12a4d26-e897-4ca2-8bb5-7ce8b09d4379?api-version=2022-04-01

Headers:
Accept-Language               : en-US
x-ms-client-request-id        : _abc_

Body:
{
  "properties": {
    "principalType": "ServicePrincipal",
    "roleDefinitionId": "4d97b98b-1d4f-4787-a291-c67834d212e7",
    "principalId": "94dc2ae6-eb13-4991-9e6a-31945050563b"
  }
}

DEBUG: ============================ HTTP RESPONSE ============================

Status Code:
BadRequest

Headers:
Cache-Control                 : no-cache
Pragma                        : no-cache
Set-Cookie                    : x-ms-gateway-slice=Production; path=/; secure; samesite=none; httponly
x-ms-request-id               : _def_
X-Content-Type-Options        : nosniff
Strict-Transport-Security     : max-age=31536000; includeSubDomains
x-ms-ratelimit-remaining-tenant-writes: 1198
x-ms-correlation-request-id   : _ghi_
x-ms-routing-request-id       : SWEDENCENTRAL:20240205T135635Z:_jkl_
X-Cache                       : CONFIG_NOCACHE
X-MSEdge-Ref                  : Ref A: _mno_ Ref B: _pqr_ Ref C: 2024-02-05T13:56:35Z
Date                          : Mon, 05 Feb 2024 13:56:35 GMT

Body:
{
  "error": {
    "code": "BadRequestFormat",
    "message": "The request was incorrectly formatted."
  }
}

Are you able to post part of the roles plan into this issue so we can validate the format - I've tested role deployment as of yesterday with no issues.

Hi @anwather,
My sincere apologies for taking up your time.
I managed to solve the issue. I had a mismatch of files that originated from an old setup to the new fork I had synced with the repo (as the repo had some major changes as of the last few weeks). I started over and it worked out nicely! Thanks for being present! I will mark this bug as resolved.


Kremlib.h separation in different files for easier integrations in other projects

As discussed before, we typically don't want everything that is currently in kremlib.h for production.
We have an example of split in 2 parts for HACL*  based on the current kremlin/kremlib.h
https://github.com/mitls/hacl-star/tree/master/snapshots/kremlib
Deciding of a nicer splitting is not urgent but is important so that we can remove unused code from production code such as the one used in NSS, while having HACL* kremlib(s).h aligned on Kremlin.

currently underway in https://github.com/FStarLang/kremlin/tree/cleanup-kremlib/kremlib, including a restructuring of the kremlib/ directory -- the goal is to have kremlin automatically pick up the right -add-include foo.h and foo.c arguments for you, unless using -minimal

Merged in a21b1e0bad4b1bc80cc520fbeb01bc385fef5641 and others


Feature/adds custom user model

On this PR I do what I suggested on #4.
If we need to update in the end our user model, we are gonna be able because I added those changes.

@brunachaves maybe I could change the app to users instead of user, to keep consistency with the installed apps WDYT?


Explore async io options for redis

As we move towards concurrency, we should explore if redis can use asyncio https://aioredis.readthedocs.io/en/latest/

Since moving to TaskIQ we no longer provision the client and pass it to the task queue and hence this is abstracted away from us


get_token fails using credentials obtained through FB auth flow

I have credentials through a modified version of https://github.com/hrkfdn/ncspot/pull/537 that uses a newly created client id and client secret (CLIENT_ID from here on out). These credentials authenticate:
[2021-05-24][14:45:53] [librespot_core::session] [INFO] Authenticated as "##########" !
[2021-05-24][14:45:53] [librespot_playback::audio_backend::pulseaudio] [INFO] Using PulseAudio sink with format: S16
[2021-05-24][14:45:53] [librespot_core::session] [INFO] Country: "DE"

However librespot is unable to get a token using these credentials:
[2021-05-24][14:45:53] [librespot_core::mercury] [WARN] error 403 for uri hm://keymaster/token/authenticated?client_id=CLIENT_ID&scope=user-read-private,playlist-read-private,playlist-read-collaborative,playlist-modify-public,playlist-modify-private,user-follow-modify,user-follow-read,user-library-read,user-library-modify,user-top-read,user-read-recently-played

I have a hacked up version of examples/get_token.rs that works off of these credentials instead of whats passed on the command line (see https://github.com/medwards/librespot/commit/fed29f4ceca9d4fedf49f251b1b7d9a0cdc74ed2).
This works for the streaming scope:
~/forks/librespot$ cargo run --package librespot --example get_token -- /home/medwards/.cache/ncspot/librespot CLIENT_ID streaming
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running `target/debug/examples/get_token /home/medwards/.cache/ncspot/librespot CLIENT_ID streaming`
Connecting..
Token: Token {
    access_token: "AN_ACCESS_TOKEN",
    expires_in: 3600,
    token_type: "Bearer",
    scope: [
        "streaming",
    ],
}

For any other scope or combination of scopes I get MecuryError.
~/forks/librespot$ cargo run --package librespot --example get_token -- /home/medwards/.cache/ncspot/librespot CLIENT_ID playlist-modify
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running `target/debug/examples/get_token /home/medwards/.cache/ncspot/librespot CLIENT_ID playlist-modify`
Connecting..
 Got error: MercuryError
~/forks/librespot$ cargo run --package librespot --example get_token -- /home/medwards/.cache/ncspot/librespot CLIENT_ID playlist-read
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running `target/debug/examples/get_token /home/medwards/.cache/ncspot/librespot CLIENT_ID playlist-read`
Connecting..
 Got error: MercuryError

I originally requested the following scopes when going through the oauth2 flow so I expect these to work (and mysteriously streaming does):
                  "app-remote-control",
                  "playlist-modify",
                  "playlist-modify-private",
                  "playlist-modify-public",
                  "playlist-read",
                  "playlist-read-collaborative",
                  "playlist-read-private",
                  "streaming",
                  "user-follow-modify",
                  "user-follow-read",
                  "user-library-modify",
                  "user-library-read",
                  "user-modify",
                  "user-read-private",
                  "user-read-recently-played",
                  "user-top-read",

I made https://github.com/medwards/ncspot/tree/env-client-secrets if you want to reproduce your own credentials. However while setting it up I realized I was using the normal Spotify client id with my own client secret. If I use my client id and client secret then I can still authenticate however I can't get a token for any token in this case (incl. streaming).
This might be expected behaviour, in which case feel free to close.

It's possible that the keymaster endpoint simply doesn't support OAuth2 clients and their tokens. Given that this service is essentially an interop service that allows mercury clients to consume the HTTP endpoints protected by OAuth, the devs at Spotify may have not seen the point of supporting oauth sessions in the oauth token generating keymaster.
With regards to the streaming scope working and no others, I believe the streaming scope is required to interact with mercury endpoints. I may be wrong on this though.
As for your client ID not working for streaming whilst Spotify's ID does work somewhat, it's possible that they do some form of whitelisting on their end.
It may be worth examining this behaviour further, but given the simplicity of the keymaster endpoint and what it does, combined with your observations around the behaviour with different client IDs, I'd place my bet on this being expected behaviour from Spotify servers rather than a bug, though the line is often blurred :)

Does this mean it's not possible to use librespot with tokens generated using the Authorization Code Flow ?


DSL for testing

The bulk of testing in blaze is done through a DSL:
1 example per file:
https://github.com/firebase/blaze_compiler/tree/master/test/scenarios
many examples per file:
https://github.com/firebase/blaze_compiler/blob/master/test/anticases/objects.yaml
This is the quickest way to react to user bugs. Given that in bolt, putting source code inside source code is already a problem (e.g. decision to use ' instead of " due to escaping issues). I suggest Bolt should move to a more productive test harness, it will pay for iteself over the long term

The added "simulator" addresses Bolt testing in a DSL-like embedded language.


Show available casefiles previously shared

In VSCode, this requires selecting a folder to work with (from among the workspace.workspaceFolders that have file-system paths and are valid Git repositories).  Retrieving the list of casefiles will also require selecting a Git remote configured in the target folder.

Is it possible/reasonable to think of this as a tree: folder -> remote -> casefile name (with possible additional level of specific instance, where multiple exist)?  Would this fit in the sidebar or, if not, in another region of the editor?

It probably would be good, when planning the UI here, to consider the possibility of non-Git stores for casefiles.  The casefile data format could support other version control systems, and it would be reasonable that those VCSs might support a metadata system capable of sharing casefiles.

Rather than the "folder -> remote -> casefile name" hierarchy, I think I'll prefer selecting a single "casefile store," where the only initial store type is a Git repository (configured as a remote of one of the workspace folders).
For the "single folder workspace" case, if no store has been explicitly identified and the one workspace folder is a Git repository, it will be used for all casefile sharing operations.
Once an explicit selection has been made, it will be kept in the workspaceState as an object identifying the store type ('git'), the folder path, and the Git remote name.  The folder must be checked against the folders in the workspace, and an error shown if the folder is not among those included in the workspace.
If the workspace contains multiple folders, then any operation involving the Casefile sharing store should show an error and direct the user to select a store via the SCM view.

Closing this unblocks #7


Missing license

Hello,
would it be possible to add a license to the code (e.g. MIT) to enable reuse?

BSD-3 license added


docs(core|capture): fix dependency name

Codecov Report

Merging #417 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #417   +/-   ##
=======================================
  Coverage   82.56%   82.56%
=======================================
  Files          14       14
  Lines         562      562
=======================================
  Hits          464      464
  Misses         98       98

Impacted Files
Coverage Δ

src/js/core/capture.js
100% <ø> (ø)
:white_check_mark:

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 5ec10ac...a515ad4. Read the comment docs.