Datepicker and Select immediately closing on open

I have form and when I click on the datepicker or select field, it opens and then immediately closes.
Any idea if this is a bug or am I missing something crucial here?
Datepicker
<input type="text" [(ngModel)]="transaction.dateTemp" name="date" materialize="pickadate [materializeParams]="[{ format: 'dd/mm/yyyy' }]" />

Select

          <select materialize="material_select" [(ngModel)]="transaction.direction" name="direction">
            <option value="outgoing" selected>Outgoing</option>
            <option value="incoming">Incoming</option>
          </select>
          Incoming/Outgoing Transaction

Got the exact same issue only on Google Chrome though Firefox seems to work fine....

I just tried and I can confirm what jeroen says. In firefox all seems to be fine.

It looks like this is a problem in Materializecss  / pickadate.js check this thread for a quick fix:
https://github.com/Dogfalo/materialize/issues/6312

This is a big problem. The same with me of all my projects!
Datapicker and Select is totally broken on Chrome..
:(

This is a solution for SELECT component:

Edit node_modules/materialize-css/dist/js/materialize.js
Insert SetTimeout here:

$newSelect.on({
	'focus': function () {
		var _this = this;

		setTimeout(function () {
			if ($('ul.select-dropdown').not(options[0]).is(':visible')) {
				$('input.select-dropdown').trigger('close');
				$(window).off('click.select');
			}
			if (!options.is(':visible')) {
				$(_this).trigger('open', ['focus']);
				var label = $(_this).val();
				if (multiple && label.indexOf(',') >= 0) {
					label = label.split(',')[0];
				}

				var selectedOption = options.find('li').filter(function () {
					return $(_this).text().toLowerCase() === label.toLowerCase();
				})[0];
				activateOption(options, selectedOption, true);

				$(window).off('click.select').on('click.select', function () {
					multiple && (optionsHover || $newSelect.trigger('close'));
					$(window).off('click.select');
				});
			}
		}, 75);
	},
	'click': function (e) {
		e.stopPropagation();
	}
});

This is a solution for SELECT component:

Edit node_modules/materialize-css/dist/js/materialize.js
Insert SetTimeout here:

$newSelect.on({
	'focus': function () {
		var _this = this;

		setTimeout(function () {
			if ($('ul.select-dropdown').not(options[0]).is(':visible')) {
				$('input.select-dropdown').trigger('close');
				$(window).off('click.select');
			}
			if (!options.is(':visible')) {
				$(_this).trigger('open', ['focus']);
				var label = $(_this).val();
				if (multiple && label.indexOf(',') >= 0) {
					label = label.split(',')[0];
				}

				var selectedOption = options.find('li').filter(function () {
					return $(_this).text().toLowerCase() === label.toLowerCase();
				})[0];
				activateOption(options, selectedOption, true);

				$(window).off('click.select').on('click.select', function () {
					multiple && (optionsHover || $newSelect.trigger('close'));
					$(window).off('click.select');
				});
			}
		}, 75);
	},
	'click': function (e) {
		e.stopPropagation();
	}
});

If I do this, won't this give problems whenever I deploy it on a server that does npm install to restore packages?

This is a solution for SELECT component:

Edit node_modules/materialize-css/dist/js/materialize.js
Insert SetTimeout here:

$newSelect.on({
	'focus': function () {
		var _this = this;

		setTimeout(function () {
			if ($('ul.select-dropdown').not(options[0]).is(':visible')) {
				$('input.select-dropdown').trigger('close');
				$(window).off('click.select');
			}
			if (!options.is(':visible')) {
				$(_this).trigger('open', ['focus']);
				var label = $(_this).val();
				if (multiple && label.indexOf(',') >= 0) {
					label = label.split(',')[0];
				}

				var selectedOption = options.find('li').filter(function () {
					return $(_this).text().toLowerCase() === label.toLowerCase();
				})[0];
				activateOption(options, selectedOption, true);

				$(window).off('click.select').on('click.select', function () {
					multiple && (optionsHover || $newSelect.trigger('close'));
					$(window).off('click.select');
				});
			}
		}, 75);
	},
	'click': function (e) {
		e.stopPropagation();
	}
});

If I do this, won't this give problems whenever I deploy it on a server that does npm install to restore packages?

You are absolutely right, this is a temporary solution! for a definitely solution its necessary a new version of materializecss

The example on the website does this too:
http://archives.materializecss.com/0.100.2/forms.html
I can't wait to get off our legacy application and ditch this library. So many issues.

There should be a fix for this otherwise i need to take out materialize out of all my projects.
I can't use the current solution, it's not working.

Yea, this is quite annoying. If you go to the actual website where they have their demos, you see the exact same behavior:
http://archives.materializecss.com/0.100.2/forms.html
The fix above came with some improvement but it's not a real fix.

I'm having the same issue. The first time I click if I hold it will stay open, but the next time I click it doesn't open until after I release the click. It seems to alternate between these 2 states: press and hold to keep open and click to open.

Solution for materializecss  calendar opening & closing immediately
The solution is quite simple, It can be resolved using preventDefault() method.
for eg:-
Markup: <input class = 'datepicker' />
then after initialization in jquery just use preventdefault like this
JS:
     $('.datepicker').on('mousedown',function(event){         event.preventDefault();       })
and it will work
@oussamaelhajoui @jelkinsiv @guigons
just let me know if this helps

@goodwillsandy it partly works, but occurs another issue - I can't choose needed date right now. Calendar is not closed after I select any value.

unable to see the reply on GIhu
On Fri, May 17, 2019 at 2:04 PM Roman Melnyk<EMAIL_ADDRESS>wrote:

@goodwillsandy https://github.com/goodwillsandy it partly works, but
occurs another issue - I can't choose needed date right now. Calendar is
not closed after I select any value.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/InfomediaLtd/angular2-materialize/issues/444?email_source=notifications&email_token=AFQRVC342D2Q6ARIS5YZCZLPVZUYDA5CNFSM4HACITK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVUD53Y#issuecomment-493371119,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFQRVC3GL5HMPAQRO3UBVHDPVZUYDANCNFSM4HACITKQ
.

--
Sandeep Kumar

Great its working for me... thanks alot

I thought this may help some who stumbled on this page. I am using angular2-materialize and my materialize select input sometimes closes immediately after opening.
I solved this by adding a click listener on a div that wraps the select tag, with nothing by event.stopPropagation() in the listener. This fixed the issue for me.

thanks it works....
On Thu, May 30, 2019 at 12:35 AM armando-navarro<EMAIL_ADDRESS>wrote:

I thought this may help some who stumbled on this page. I am using
angular2-materialize and my materialize select input sometimes closes
immediately after opening.
I solved this by adding a click listener on a div that wraps the
select tag, with nothing by event.stopPropagation() in the listener. This
fixed the issue for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/InfomediaLtd/angular2-materialize/issues/444?email_source=notifications&email_token=AECTW6S3UAVREH2F3UUP4K3PX3F67A5CNFSM4HACITK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQJQEY#issuecomment-497063955,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AECTW6SU33QFTAWMGSKZ2UDPX3F67ANCNFSM4HACITKQ
.

--
Regards,
Guddu kumar

When adding preventDefault on the parent of a select tag, it wont close anymore..

Guys i find it solution for this problem and works for chrome.
You need to edit function which open datepicker and incrase the timeout.
Line 6522:
setTimeout(function () {
      // Add the “opened” class to the picker root.
      P.$root.addClass(CLASSES.opened);
      aria(P.$root[0], 'hidden', false);
    }, 100);

Try this.
$(document).on("click", ".select-wrapper", function (event) {     event.stopPropagation();   });

    $('.datepicker').on('mousedown',function(event){
        event.preventDefault();
    });

This solution works partially. I have two datepickers in my form, when I click the first it works as it used to, but then if I click the first one again, nothing happens. If I click the second, it shows, and then clicking the first it shows again, and so on so forth.

Solution for materializecss calendar opening & closing immediately
The solution is quite simple, It can be resolved using preventDefault() method.
for eg:-
Markup: <input class = 'datepicker' />
then after initialization in jquery just use preventdefault like this
JS:
 $('.datepicker').on('mousedown',function(event){ event.preventDefault(); })
and it will work
@oussamaelhajoui @jelkinsiv @guigons
just let me know if this helps

Thanks, mate:)

hi,
I faced the same problem and solve it.
I think that the problem is that $('#the-id-of-select') does not give you the element so you cannot get its value. It gives you an array of all the elements with the id that you typed.
so $('#the-id-of-select').value will be undefined.
I used $('#the-id-of-select')[0] to specify the first select box and it solved the problem for me.

Thanks @daya-s this worked for me. I got this problem after I opened my project after 2 years today, but I didn't have this problem before. What do you think caused this?


Holdinvoice redesign [wip]

@Roasbeef @cfromknecht
Processed and replied to your comments.
Closing this PR and continuing in the original hold invoice PR #2022.


jquery-application-beautify-calc-column

Q
A

New sample?
yes

What's in this Pull Request?
This SPFx extension beautifies the HTML markups used in the calculated column if the tag is configured with class name "beautifyCalcMarkup".

@sprider,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Hi Joseph,
this looks pretty cool, but to ensure that the community understands the value around this, I'd suggest adding slightly more clarification on the use case. The picture is good, but it's unclear around what does the extension actual provides - as in what does the "beautify" actually means unless you look in the code. Any change we could get some more clarity on the readme, so that the value of the sample is understood more widely? - I could do that obviously by myself as well, but since it's your sample, wanted to double check your preference.

Thank you for the feedback Vesa. I have updated the README file. Could you please check now?

thx Joseph, appreciated.


get the date a song was saved

I'm trying to make an app that visualizes data from your liked songs. One of the things I wanted to chart was the data songs were saved but I can't find anything on the Spotify docs about this. Does anyone know if this is possible?

I don't think this is appropriate to label as an issue for spotify-web-api-node.  This is more a question about on Spotify's API. You should delete this issue.
That being said the endpoint to get your saved tracks returns the date each song was added. I think you meant to say "date songs were saved"?


How can provide multilingual versions of the wiki ？

how to change the docusaurus config to  support chinese version？

Please start from here: https://docusaurus.io/docs/i18n/introduction


Service down

Tools at https://tools.axinom.com/ are unreachable on 15/02/2022 1100 UTC. Is it planned maintenance?

same issue here!

It is still down. Is there any update?

Hello! The website should be up again now. Except for the Widevine license request decoder functionality -- this needs to undergo further maintenance.

Hello! The website should be up again now. Except for the Widevine license request decoder functionality -- this needs to undergo further maintenance.

Hello Dev. Is license request decoder still maintenance? It's still not working since last week.
Thank you.

Hello @zackmark29. Yes, and unfortunately I don't have an exact ETA right now. The Widevine decoder is planned to be made available only to registered Axinom users and will be made available again with a bit different feature set once this move is finished. Until then, and for the general public users, we recommend to use the public Google decoder at https://integration.widevine.com/diagnostics . Sorry for the inconvenience!

Hello @zackmark29. Yes, and unfortunately I don't have an exact ETA right now. The Widevine decoder is planned to be made available only to registered Axinom users and will be made available again with a bit different feature set once this move is finished. Until then, and for the general public users, we recommend to use the public Google decoder at https://integration.widevine.com/diagnostics . Sorry for the inconvenience!

Please sign-in to Axinom Portal to continue using the site.


Single page

this PR includes
#63
#80
#56 (handled by Clerk and not localStorage)

Could you please add references to the relevant issues that this addresses in your description?

One item left over is that that the following error is popping up in the browser's console.

Josh and I checked and we can't see this error, could you please double check if you still see it?

Could you please add references to the relevant issues that this addresses in your description?

we added the issue numbers, thank you!

Could you please add references to the relevant issues that this addresses in your description?

resolved thank you


Tests fail due to DeprecationWarning: pkg_resources is deprecated as an API

Describe the bug
After a clean installation following the contribution guidelines, pytest fails with the error in the topic.
To Reproduce
Install and run pytest.
Expected behavior
Tests should run.
Additional context

[X] OmegaConf version: master
[X] Python version: 3.8
[X] Operating system: Ubuntu

This is related to #1068


Update isochrones on drag rather than release

Even before we rework the isochrones, simply updating the layer when the threshold slider is moved instead of when it is released will make the interface feel more responsive and interactive.

Changing analysis-single.js around line 193 to bind to the "slide" event rather than "slideStop" achieves the desired effect, but it's a bit sluggish on Firefox. The effect on Chrome and Safari is much smoother, but still a lot of flickering. I think this is just because the function being called (updateMap) peforms a lot of extra work, when all we really want to do is update the shapes in the isochrone layer.
On all browsers, it's very laggy for the accessibiilty results which are sent back as tiles.
I am sure this can be done smoothly but it will require some work.

Actually isochrone animation is extremely smooth on Chrome under Linux. It looks great, and you can really perceive temporal aspects of the results on bike+transit trips from outlying areas.


need help with installation of CFR_ICADS

Hi Andrew,
I would like to install your package but when I do
julia> Pkg.instantiate()

I get the error:
   Updating registry at `C:\Users\carl\.juliapro\JuliaPro_v1.4.0-1\registries\JuliaPro`

ERROR: expected package `RLInterface [3065fe53]` to be registered

...

So then I tried
(StrategyGames) pkg> add https://github.com/JuliaPOMDP/RLInterface.jl

and got this error:
    Cloning git-repo `https://github.com/JuliaPOMDP/RLInterface.jl`

   Updating git-repo `https://github.com/JuliaPOMDP/RLInterface.jl`

  Resolving package versions...

ERROR: expected package `ARDESPOT [d96c9ae4]` to be registered

Do you know what the problem is and/or what I have to do to install CFR_ICADS?
Thanks,
Carl

@carlcotner apologies for the long delay - I had my watching status set incorrectly. I'll take a look soon but I believe the project file on master had some errors. The version on the rev1 branch should instantiate correctly on Julia v1.1

@carlcotner apologies for the long delay - I had my watching status set incorrectly. I'll take a look soon but I believe the project file on master had some errors. The version on the rev1 branch should instantiate correctly on Julia v1.1

Excuse me, which version could I choose, 1.1.0 or 1.1.1 ?


Enable freezing the position of certain atoms

Similar to #244. Currently, the only way of freezing certain atoms in a simulation in place (at least that I'm aware of) is by using an ase calculator which outputs 0 forces on the respective atoms. However, this alone doesn't work for methods where random noise is applied, such as Langevin dynamics.
In conjunction with #244 , it might be best to allow specifying frozen atoms when defining a Simulation, which makes the necessary modifications to methods. (ignoring initial velocities from DynamicalDistributions, position/velocity updates, random noise, ...)

It's currently possible to define frozen atoms for individual models by implementing NQCModels.mobileatoms that should return the indices of the atoms that are not frozen. Though this is not used everywhere in the code so there are some cases where this won't work yet. I like the idea of attaching the constraints to the model because I think it makes logical sense and the model is available everywhere that the Simulation is so I think the current implementation should be good for most scenarios. It's just a case of checking NQCModels.mobileatoms whenever an atom is about to be moved.


Exception on tables with Date column

(Original issue 6 created by {u'display_name': u'coderazzi coderazzi', u'account_id': u'557058:790eb198-2ae4-49b4-b920-8d654aa86b3f'} on 2011-03-05T05:13:12+00:00)
What steps will reproduce the problem?
1. Create a table with a model associating a Date.class type to a column
2. Associate a table filter header to this table

Instead of being created the filter, an exception is raised

Original issue reported on code.google.com by coderazzi on 2011-03-05 05:13:12

(Original issue 6 last updated on 2011-03-05T05:13:12+00:00)
(Issue automaticaly closed due to status in Bitbucket: invalid)

(Original comment by {u'display_name': u'coderazzi coderazzi', u'account_id': u'557058:790eb198-2ae4-49b4-b920-8d654aa86b3f'} on 2011-03-05T14:13:30+00:00)
The problem does not happen because of a Date column, but as described on the separated
issue 'Exception raised when a model is set on the table  after attaching the filter
header'

Original issue reported on code.google.com by coderazzi on 2011-03-05 14:13:30


[json] hover in JSON documents hides '*'

VSCode Version: 1.2.1
VSCode C++ extension Version: 0.7.0
OS Version: Windows 10 Enterprise

NOTE: You need the C++ extension version 0.7.0 or later because we introduced the c_cpp_properties.json schema file.
Steps to Reproduce:

Open any folder containing a .cpp file with unresolved header files.
Click on the lightbulb for an unresolved header and select the "Add include path to settings"
3.The c_cpp_properties.json file opens. Save once so intellisense works (see issue 8067 for more details).
Hovering to see a description over "includePath" the '' character is not visible. But if you start typing "includePath" the intellisense shows the '' character. See the two attached screenshots for more info.

I still see this issue with version 1.3.1 (see attached image for details on the version).

You need the latest insider build (1.4.0-insider): https://code.visualstudio.com/insiders

This works on the latest insider build. These are the daily builds so it will appear in the next official vscode release as well?


Auto completion issue android studio.

Steps to Reproduce

In android studio, auto completion while writing the code deletes some portion of code and puts some stray brackets, which causes error. So i undo one step and rewrite that particular line again.
Steps to reproduce:

... type Color: Colors.w
...press tab
...messes up the code

Logs

Hello @VrajGohil !
Thank you for posting.
Can you please attach the flutter doctor -v command output?

╔════════════════════════════════════════════════════════════════════════════╗
║ A new version of Flutter is available!                                     ║
║                                                                            ║
║ To update to the latest version, run "flutter upgrade".                    ║
╚════════════════════════════════════════════════════════════════════════════╝
[√] Flutter (Channel master, v1.10.3-pre.39, on Microsoft Windows [Version 10.0.17134.1006], locale en-GB)
• Flutter version 1.10.3-pre.39 at D:\flutter
• Framework revision 0ef89bb969 (2 weeks ago), 2019-09-14 15:34:29 -0700
• Engine revision 00c8941dae
• Dart version 2.6.0 (build 2.6.0-dev.0.0 a554c8be6b)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\Users\Vraj\AppData\Local\Android\sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 3.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 31.3.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[!] IntelliJ IDEA Ultimate Edition (version 2019.1)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.1
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins
[√] VS Code (version 1.38.1)
• VS Code at C:\Users\Vraj\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.4.1
[√] VS Code, 64-bit edition (version 1.28.2)
• VS Code at C:\Program Files\Microsoft VS Code
• Flutter extension version 3.4.1
[√] Connected device (2 available)
• Chrome • chrome • web-javascript • Google Chrome 77.0.3865.90
• Server • web    • web-javascript • Flutter Tools
! Doctor found issues in 1 category.

Hi,
this is a problem of the Android Studio plugin. please File this issue here https://github.com/flutter/flutter-intellij


How can we train on higher resolution images ?

My training images are of 1200 * 800 resolution. How can i train using your pre trained model ?

Please take a look at https://github.com/foamliu/Deep-Image-Matting-v2.

I am using this repo for training on my custom dataset. I am using your pretrained model in my training.
I get following values.
loss: 2.3741e-06
acc: 0.4070
loss becomes very low quickly. Is this correct ? or is there any other way to check if my training is going fine ?


feat(frontend): Introduce secrets prop to hide from the terminal

End-user friendly description of the problem this fixes or functionality that this introduces
If defined like the GITHUB_TOKEN are exported in the shell environment, the user (or assistant) could reveal them with commands such as echo $GITHUB_TOKEN

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Give a summary of what the PR does, explaining any non-trivial design decisions
Introduce a secrets prop for the terminal to check and replace any secrets present. Currently, the secrets that are monitored are the GitHub token and session token

Link of any specific issues this addresses

Maybe also any *_API_KEY (like LLM_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY)?

@tobitege The path I'm going with this PR are hiding secrets that the agent may be aware of (token actually may not be required in the array in that case). GITHUB_TOKEN is exported if the user is logged in, and therefore in the event stream. In the cases the assistant wants to clone a private repo and use the token, it is not accidentally exposed.
Not sure there are scenarios where the agent may blurt out the API key in the terminal

What if a user just enters an env command? If this is solely LLM-driven, and not catching user commands, than my bad. 😃

After analyzing the pull request, here are my findings:
Overall Feedback:
The introduction of the secrets prop to the terminal component is a significant enhancement for user privacy, ensuring sensitive information is not displayed in the terminal output. The implementation appears solid, but there are opportunities to improve code clarity and maintainability.
Score: 90/100
Labels: Enhancement, Tests
Code Suggestions:

File: frontend/src/hooks/useTerminal.ts

One-Sentence Summary: Improve regex performance by compiling it outside the loop.
Suggestion Content: Move the creation of the secretRegex outside the loop to avoid recompiling it for each command.
Relevant Line: +          const secretRegex = new RegExp(secret, "g");
Existing Code:secrets.forEach((secret) => {
    const secretRegex = new RegExp(secret, "g");
    content = content.replace(secretRegex, "*".repeat(10));
});

Improved Code:secrets.forEach((secret) => {
    const secretRegex = new RegExp(secret, "g");
    content = content.replace(secretRegex, "*".repeat(10));
});

File: frontend/src/hooks/useTerminal.ts

One-Sentence Summary: Ensure that the secrets array is not empty before processing.
Suggestion Content: Add a check to skip the replacement logic if secrets is empty to avoid unnecessary processing.
Relevant Line: +          secrets.forEach((secret) => {
Existing Code:secrets.forEach((secret) => {
    const secretRegex = new RegExp(secret, "g");
    content = content.replace(secretRegex, "*".repeat(10));
});

Improved Code:if (secrets.length > 0) {
    secrets.forEach((secret) => {
        const secretRegex = new RegExp(secret, "g");
        content = content.replace(secretRegex, "*".repeat(10));
    });
}

File: frontend/src/components/terminal/Terminal.tsx

One-Sentence Summary: Consider using default props for secrets to enhance component usability.
Suggestion Content: Set default values for the secrets prop to ensure the component behaves correctly even if no secrets are passed.
Relevant Line: +function Terminal({ secrets }: TerminalProps) {
Existing Code:function Terminal({ secrets }: TerminalProps) {

Improved Code:function Terminal({ secrets = [] }: TerminalProps) {

Great enhancement with the secrets prop! Here are some suggestions:

Move the creation of the regex outside the loop in useTerminal for better performance.
Add a check to skip processing if secrets is empty.
Consider using default props for secrets in the Terminal component to enhance usability.

Ah no, at least not yet. We should eventually store all other secrets too, but that would most likely require watching the shells environment variables 🤔
Have any idea how we may approach this? I can open an issue for it

Overall Feedback:
The introduction of the secrets prop to the terminal component is a significant enhancement for security, ensuring sensitive information is not exposed in the terminal output. The implementation is well-integrated into the existing codebase, with appropriate updates to the terminal component and related hooks. The test cases are comprehensive, covering the new functionality effectively.
Score: 92/100
Labels: Enhancement, Tests
Code Suggestions:

File: frontend/src/hooks/useTerminal.ts

Language: TypeScript
One-Sentence Summary: Optimize the secret replacement logic for performance.
Suggestion Content: Use a single regular expression to replace all secrets in one pass, improving performance when multiple secrets are present.
Relevant Line: +          content = content.replace(secretRegex, "*".repeat(10));
Existing Code:secrets.forEach((secret) => {
  const secretRegex = new RegExp(secret, "g");
  content = content.replace(secretRegex, "*".repeat(10));
});

Improved Code:const secretRegex = new RegExp(secrets.join('|'), "g");
content = content.replace(secretRegex, "*".repeat(10));

File: frontend/__tests__/hooks/use-terminal.test.tsx

Language: TypeScript
One-Sentence Summary: Improve test reliability by resetting mock call counts.
Suggestion Content: Ensure mock call counts are reset between tests to avoid test order dependencies.
Relevant Line: +    // BUG: vi.clearAllMocks() does not clear the number of calls
Existing Code:// BUG: `vi.clearAllMocks()` does not clear the number of calls
// therefore, we need to assume the order of the calls based
// on the test order

Improved Code:beforeEach(() => {
  vi.clearAllMocks();
  mockTerminal.writeln.mockClear();
});

The introduction of the secrets prop to the terminal component is a significant enhancement for security, ensuring sensitive information is not exposed in the terminal output. The implementation is well-integrated into the existing codebase, with appropriate updates to the terminal component and related hooks. The test cases are comprehensive, covering the new functionality effectively.


There is no Run on the Test branch of the menu bar

The comment below was machine translated
@wraith13 commented on Mon Aug 19 2019
https://docs.microsoft.com/ja-jp/visualstudio/get-started/tutorial-projects-solutions?view=vs-2019#next-steps
Select ** Tests ** ** Run **** ** All Tests ** from the menu bar.

However, when I checked in the Japanese version of Mirosoft Visual Studio Community 2019 Version 16.2.2, only [Window] existed in [Test] on the menu bar. (The same function appears to be usable without problems from Test Explorer.)

@srvbpigh commented on Mon Aug 19 2019
Hello, @wraith13
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

Not sure if a product feedback or if the user is reporting an inaccuracy in the documentation
best regard

@CeciAc -- Cecilia, please forward this reply on to wraith13:
Thanks for your feedback; we appreciate it. To make sure that this is logged in the right place, please use the Report a Problem tool to report the issue. When you do so, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.

https://developercommunity.visualstudio.com/content/problem/672211/test-menu-items-missing-except-windows.html
I found it. But I'm sad...


broken treatmentBank link

          @punkish Hello! I did some tests, and saw that no one link to TreatmentBank works. I did also in others collections code and happen the same.

Originally posted by @juwingert in https://github.com/punkish/ocellus/issues/54#issuecomment-2312567696

fixed


Immich | Data location on networkshare permission denied

Description
Data location on networkshare permission denied. What can I do to fix this? I want to save the photos on my network drive which I connected with home assistant
Config of the Add-On:
DB_DATABASE_NAME: immich DB_HOSTNAME: homeassistant.local DB_PASSWORD: homeassistant DB_PORT: "5432" DB_USERNAME: postgres DISABLE_MACHINE_LEARNING: false JWT_SECRET: SECRET PGID: 1000 PUID: 1000 TZ: Europe/Berlin data_location: /media/NAS/photos/
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Addon Logs
`[Nest] 1126  - 04/09/2024, 11:25:48 AM   ERROR [Error: EACCES: permission denied, mkdir '/media/NAS/photos/upload/191974e7-d85f-498a-a436-4cb737395bce/26/5f'
    at mkdirSync (node:fs:1373:26)
    at StorageRepository.mkdirSync (/app/immich/server/dist/repositories/storage.repository.js:112:37)
    at AssetService.getUploadFolder (/app/immich/server/dist/services/asset.service.js:114:32)
    at /app/immich/server/dist/middleware/file-upload.interceptor.js:127:52
    at callbackify (/app/immich/server/dist/middleware/file-upload.interceptor.js:63:31)
    at FileUploadInterceptor.destination (/app/immich/server/dist/middleware/file-upload.interceptor.js:127:16)
    at DiskStorage._handleFile (/app/immich/server/node_modules/multer/storage/disk.js:31:8)
    at FileUploadInterceptor.handleFile (/app/immich/server/dist/middleware/file-upload.interceptor.js:137:29)
    at /app/immich/server/node_modules/multer/lib/make-middleware.js:137:17
    at callbackify (/app/immich/server/dist/middleware/file-upload.interceptor.js:63:16)] Error: EACCES: permission denied, mkdir '/media/NAS/photos/upload/191974e7-d85f-498a-a436-4cb737395bce/26/5f'`

Architecture
aarch64
OS
HAos

Supervisor log:
2024-04-09 13:25:01.379 ERROR (MainThread) [supervisor.docker.addon] Add-on Immich try to access to blocked device sdb1!

Supervisor log: 2024-04-09 13:25:01.379 ERROR (MainThread) [supervisor.docker.addon] Add-on Immich try to access to blocked device sdb1!

Hi, this is not an issue it is just a routine message as the addon tries to check it's access in case users want to mount such drives. This message just means that there is no sdb1 device.
Regarding immich I haven't used it for a long time - does it allow setting puid/pgid to 0/0? It might be a solution, or correcting the ownership in the mounted drive? From the path (/media instead of /mnt) it seems you are using the embedded HA mount system instead of my own so i'm not sure how they handle permissions when mounting... Hope this helps?

Hi @alexbelgium
I have the same problem and setting the puid/pgid to 0/0 did not help. I am using the embedded HA mount system (by going to HA settings>system>storage). I can't find any articles about allowing docker addons to access HA mounts. Any suggestions?
this is the log:
Failed to write /media/4TB/HASS/immich/encoded-video/.immich: Error: EACCES: permission denied, open '/media/4TB/HASS/immich/encoded-video/.immich' [Nest] 2611 - 09/18/2024, 11:24:51 AM ERROR [Api:StorageService] The "encoded-video" folder cannot be written to, please make sure the volume is mounted with the correct permissions


remove invisible elements on load

Dunno how, but I managed to create an invisible element (rectangle). For good measure, we should remove invisible elements on scene load.
Nevertheless, we should review the logic to find out what case allows for still creating invisible elements.

Do you have the scene file? Does it actually show that width and height are (0,0) or is it so slow that we just can't see it?

Yep, it's 0/0.

I just created a PR for it: #754 :) You can merge it if you like. I just added a filter to remove all the invisibly small elements on during restore


SQS queue resources fail to complete creation with timeout error

Problem
I'm unable to create aws_sqs_queue resources. I'm using Terraform provider 4.67.0 & 5.34.0 (latest) with Terraform version 1.5.7.
Note: I did try different SQS queue configs but was unable to pinpoint this down to a specific resource attribute. I was able to successfully run the same code within AWS.
Reproduction
provider "aws" {
  region                      = "us-east-1"
  s3_use_path_style           = true
  skip_credentials_validation = true
  skip_metadata_api_check     = true
  skip_requesting_account_id  = true

  endpoints {
    acm            = "http://localhost:5000"
    apigateway     = "http://localhost:5000"
    cloudformation = "http://localhost:5000"
    cloudwatch     = "http://localhost:5000"
    dynamodb       = "http://localhost:5000"
    es             = "http://localhost:5000"
    firehose       = "http://localhost:5000"
    iam            = "http://localhost:5000"
    kinesis        = "http://localhost:5000"
    lambda         = "http://localhost:5000"
    route53        = "http://localhost:5000"
    redshift       = "http://localhost:5000"
    s3             = "http://localhost:5000"
    secretsmanager = "http://localhost:5000"
    ses            = "http://localhost:5000"
    sns            = "http://localhost:5000"
    sqs            = "http://localhost:5000"
    ssm            = "http://localhost:5000"
    stepfunctions  = "http://localhost:5000"
    sts            = "http://localhost:5000"
    ec2            = "http://localhost:5000"
  }

  access_key = "my-access-key"
  secret_key = "my-secret-key"
}

terraform {
  required_providers {

    aws = {
      source  = "hashicorp/aws"
      version = "4.67.0"
    }
  }
}

resource "aws_sqs_queue" "queue" {
  name                        = "test-queue"
  fifo_queue                  = false
  delay_seconds               = 0
  max_message_size            = 16384
  message_retention_seconds   = 86400
  visibility_timeout_seconds  = 30
  receive_wait_time_seconds   = 0
  redrive_policy              = null
  content_based_deduplication = false
  sqs_managed_sse_enabled     = true
}

Error:
Terraform will perform the following actions:

  # aws_sqs_queue.queue will be created
  + resource "aws_sqs_queue" "queue" {
      + arn                               = (known after apply)
      + content_based_deduplication       = false
      + deduplication_scope               = (known after apply)
      + delay_seconds                     = 0
      + fifo_queue                        = false
      + fifo_throughput_limit             = (known after apply)
      + id                                = (known after apply)
      + kms_data_key_reuse_period_seconds = (known after apply)
      + max_message_size                  = 16384
      + message_retention_seconds         = 86400
      + name                              = "test-queue"
      + name_prefix                       = (known after apply)
      + policy                            = (known after apply)
      + receive_wait_time_seconds         = 0
      + redrive_allow_policy              = (known after apply)
      + redrive_policy                    = (known after apply)
      + sqs_managed_sse_enabled           = true
      + tags_all                          = (known after apply)
      + url                               = (known after apply)
      + visibility_timeout_seconds        = 30
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_sqs_queue.queue: Creating...
aws_sqs_queue.queue: Still creating... [10s elapsed]
aws_sqs_queue.queue: Still creating... [20s elapsed]
aws_sqs_queue.queue: Still creating... [30s elapsed]
aws_sqs_queue.queue: Still creating... [40s elapsed]
aws_sqs_queue.queue: Still creating... [50s elapsed]
aws_sqs_queue.queue: Still creating... [1m0s elapsed]
aws_sqs_queue.queue: Still creating... [1m10s elapsed]
aws_sqs_queue.queue: Still creating... [1m20s elapsed]
aws_sqs_queue.queue: Still creating... [1m30s elapsed]
aws_sqs_queue.queue: Still creating... [1m40s elapsed]
aws_sqs_queue.queue: Still creating... [1m50s elapsed]
aws_sqs_queue.queue: Still creating... [2m0s elapsed]
╷
│ Error: waiting for SQS Queue (http://localhost:5000/123456789012/test-queue) attributes create: timeout while waiting for state to become 'equal' (last state: 'notequal', timeout: 2m0s)
│
│   with aws_sqs_queue.queue,
│   on main.tf line 47, in resource "aws_sqs_queue" "queue":
│   47: resource "aws_sqs_queue" "queue" {
│
╵

Moto server logs during the apply:
Note: Moto server is running in Docker using motoserver/moto:latest image
2024-01-29 11:28:00  * Running on all addresses (<IP_ADDRESS>)
2024-01-29 11:28:00  * Running on http://<IP_ADDRESS>:5000
2024-01-29 11:28:00  * Running on http://<IP_ADDRESS>:5000
2024-01-29 11:28:00 Press CTRL+C to quit
2024-01-29 11:28:50 <IP_ADDRESS> - - [29/Jan/2024 17:28:50] "POST / HTTP/1.1" 200 -
2024-01-29 11:28:50 <IP_ADDRESS> - - [29/Jan/2024 17:28:50] "POST / HTTP/1.1" 200 -
2024-01-29 11:28:55 <IP_ADDRESS> - - [29/Jan/2024 17:28:55] "POST / HTTP/1.1" 200 -
2024-01-29 11:29:05 <IP_ADDRESS> - - [29/Jan/2024 17:29:05] "POST / HTTP/1.1" 200 -
2024-01-29 11:29:15 <IP_ADDRESS> - - [29/Jan/2024 17:29:15] "POST / HTTP/1.1" 200 -
2024-01-29 11:29:25 <IP_ADDRESS> - - [29/Jan/2024 17:29:25] "POST / HTTP/1.1" 200 -
2024-01-29 11:29:35 <IP_ADDRESS> - - [29/Jan/2024 17:29:35] "POST / HTTP/1.1" 200 -
2024-01-29 11:29:45 <IP_ADDRESS> - - [29/Jan/2024 17:29:45] "POST / HTTP/1.1" 200 -
2024-01-29 11:29:55 <IP_ADDRESS> - - [29/Jan/2024 17:29:55] "POST / HTTP/1.1" 200 -
2024-01-29 11:30:05 <IP_ADDRESS> - - [29/Jan/2024 17:30:05] "POST / HTTP/1.1" 200 -
2024-01-29 11:30:15 <IP_ADDRESS> - - [29/Jan/2024 17:30:15] "POST / HTTP/1.1" 200 -
2024-01-29 11:30:25 <IP_ADDRESS> - - [29/Jan/2024 17:30:25] "POST / HTTP/1.1" 200 -
2024-01-29 11:30:35 <IP_ADDRESS> - - [29/Jan/2024 17:30:35] "POST / HTTP/1.1" 200 -
2024-01-29 11:30:45 <IP_ADDRESS> - - [29/Jan/2024 17:30:45] "POST / HTTP/1.1" 200 -

Additional testing with AWS provider 5.34.0
Initializing provider plugins...
- Finding latest version of hashicorp/aws...
- Installing hashicorp/aws v5.34.0...
- Installed hashicorp/aws v5.34.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform/moto_testing/sqs_queue took 5.4s
➜ tfa

Terraform used the selected providers to generate the following execution plan. Resource actions are
indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_sqs_queue.queue will be created
  + resource "aws_sqs_queue" "queue" {
      + arn                               = (known after apply)
      + content_based_deduplication       = false
      + deduplication_scope               = (known after apply)
      + delay_seconds                     = 0
      + fifo_queue                        = false
      + fifo_throughput_limit             = (known after apply)
      + id                                = (known after apply)
      + kms_data_key_reuse_period_seconds = (known after apply)
      + max_message_size                  = 16384
      + message_retention_seconds         = 86400
      + name                              = "test-queue"
      + name_prefix                       = (known after apply)
      + policy                            = (known after apply)
      + receive_wait_time_seconds         = 0
      + redrive_allow_policy              = (known after apply)
      + redrive_policy                    = (known after apply)
      + sqs_managed_sse_enabled           = true
      + tags_all                          = (known after apply)
      + url                               = (known after apply)
      + visibility_timeout_seconds        = 30
    }

Plan: 1 to add, 0 to change, 0 to destroy.
╷
│ Warning: AWS account ID not found for provider
│
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on main.tf line 1, in provider "aws":
│    1: provider "aws" {
│
│ See https://registry.terraform.io/providers/hashicorp/aws/latest/docs#skip_requesting_account_id for
│ implications.
╵

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_sqs_queue.queue: Creating...
aws_sqs_queue.queue: Still creating... [10s elapsed]
aws_sqs_queue.queue: Still creating... [20s elapsed]
aws_sqs_queue.queue: Still creating... [30s elapsed]
aws_sqs_queue.queue: Still creating... [40s elapsed]
aws_sqs_queue.queue: Still creating... [50s elapsed]
aws_sqs_queue.queue: Still creating... [1m0s elapsed]
aws_sqs_queue.queue: Still creating... [1m10s elapsed]
aws_sqs_queue.queue: Still creating... [1m20s elapsed]
aws_sqs_queue.queue: Still creating... [1m30s elapsed]
aws_sqs_queue.queue: Still creating... [1m40s elapsed]
aws_sqs_queue.queue: Still creating... [1m50s elapsed]
aws_sqs_queue.queue: Still creating... [2m0s elapsed]
╷
│ Warning: AWS account ID not found for provider
│
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on main.tf line 1, in provider "aws":
│    1: provider "aws" {
│
│ See https://registry.terraform.io/providers/hashicorp/aws/latest/docs#skip_requesting_account_id for
│ implications.
╵
╷
│ Error: waiting for SQS Queue (http://localhost:5000/123456789012/test-queue) attributes create: timeout while waiting for state to become 'equal' (last state: 'notequal', timeout: 2m0s)
│
│   with aws_sqs_queue.queue,
│   on main.tf line 47, in resource "aws_sqs_queue" "queue":
│   47: resource "aws_sqs_queue" "queue" {

Testing against AWS
provider "aws" {
  region  = "us-east-1"
  profile = "us-cloud-sandbox"
}

terraform {
  required_providers {

    aws = {
      source  = "hashicorp/aws"
      version = "4.67.0"
    }
  }
}

resource "aws_sqs_queue" "queue" {
  name                        = "rafal-test-queue"
  fifo_queue                  = false
  delay_seconds               = 0
  max_message_size            = 16384
  message_retention_seconds   = 86400
  visibility_timeout_seconds  = 30
  receive_wait_time_seconds   = 0
  redrive_policy              = null
  content_based_deduplication = false
  sqs_managed_sse_enabled     = true
}

Result:
Terraform used the selected providers to generate the following execution plan. Resource actions are
indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_sqs_queue.queue will be created
  + resource "aws_sqs_queue" "queue" {
      + arn                               = (known after apply)
      + content_based_deduplication       = false
      + deduplication_scope               = (known after apply)
      + delay_seconds                     = 0
      + fifo_queue                        = false
      + fifo_throughput_limit             = (known after apply)
      + id                                = (known after apply)
      + kms_data_key_reuse_period_seconds = (known after apply)
      + max_message_size                  = 16384
      + message_retention_seconds         = 86400
      + name                              = "rafal-test-queue"
      + name_prefix                       = (known after apply)
      + policy                            = (known after apply)
      + receive_wait_time_seconds         = 0
      + redrive_allow_policy              = (known after apply)
      + redrive_policy                    = (known after apply)
      + sqs_managed_sse_enabled           = true
      + tags_all                          = (known after apply)
      + url                               = (known after apply)
      + visibility_timeout_seconds        = 30
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_sqs_queue.queue: Creating...
aws_sqs_queue.queue: Still creating... [10s elapsed]
aws_sqs_queue.queue: Still creating... [20s elapsed]
aws_sqs_queue.queue: Creation complete after 25s [id=https://sqs.us-east-1.amazonaws.com/$ACCOUNT_NUM/rafal-test-queue]

Looks like Moto is missing an attribute in the response for GetQueueAttributes, and Terraform doesn't like it. Raising a PR for it now.


add role for getting build pipeline configmap

STONEBLD-2276
Checklist:

PR has reference to the issue(s) it resolves
Write / update unit tests
Write / update integration (envtest) tests
Ensure there is an issue for e2e tests if needed
Ensure make test passes
Ensure test coverage hasn't decreased
Test code changes manually
Update readme and documentation
Write PR description that highlights overall changes and add usage examples if applicable

/retest

/retest

/retest

/retest


⚠ Bofrost.at has degraded performance

In 61125bd, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1448 ms

Resolved: Bofrost.at performance has improved in 13d192f.


Handling of native dialogs inconsistent with handling in Firefox

What is your Scenario?
I have a form with a beforeunload handler attached on changes. I want to write a test that verifies the conditions of the dialog being shown.
What is the Current behavior?
The dialog appears when opened in the browser directly, but it is not triggered when exercised in a test.
What is the Expected behavior?
The dialog should be triggered in the test.
What is your public website URL? (or attach your complete example)
The behavior can be reproduced with the following example page
<html>
<body>
    <script>
        var formSubmitting = false;
        var setFormSubmitting = function () { formSubmitting = true; };

        window.onload = function () {
            window.addEventListener("beforeunload", function (e) {
                if (formSubmitting) {
                    return undefined;
                }

                e.preventDefault();
                e.returnValue = '';
            });
        };
    </script>
    <form method="post" onsubmit="setFormSubmitting()">
        <input type="text">
        <button type=submit>Ok!</button>
    </form>
    <button type="button" onclick="window.location.reload()">Refresh!</button>
</body>
</html>

This is an adaption of the example used in https://github.com/DevExpress/testcafe/issues/5994#issuecomment-789537195. According to the MDN documentation on onbeforeunload strings returned or set for returnValue are not presented to the user anymore. The example present in the documentation gives the above e.preventDefault() and e.returnValue commands to display the dialog, which works in Firefox directly.
What is your TestCafe test code?
import { Selector } from 'testcafe';

fixture `New Fixture`
    .page `file:///<path>/test.html`

test(`New Test`, async t => {
    await t
        .setNativeDialogHandler(() => true)
        .typeText('form input', 'wqeqweqw')
        .click(Selector('button').withText('Refresh!'))

    console.log(await t.getNativeDialogHistory());
});

Your complete configuration file
No further configuration
Your complete test report
 Running tests in:
 - Firefox 95.0 / Linux 0.0

 New Fixture
[]
 ✓ New Test

 1 passed (1s)

Screenshots
No response
Steps to Reproduce

Run the above test with Firefox; at least in my setup no dialog is logged
Compare with opening the page directly in the browser and testing by hand

Curiously some changes to the example page do trigger it. One way is to set a nonempty string for the returnValue, another one is to switch the order of calling preventDefault and setting returnValue. None of these changes change the result when testing in the browser directly, and they are not required by my reading of the MDN documentation. This only happens in Firefox, Brave for example (Chromium based) triggers the dialog also in the test all the time.
TestCafe version
1.18.1
Node.js version
v16.13.1
Command-line arguments
testcafe firefox test-handler.js
Browser name(s) and version(s)
Firefox 95.0
Platform(s) and version(s)
openSUSE Tumbleweed
Other
No response

Hello @dfn-certling ,
Thank you for pointing out this issue and sharing the code example.
We reproduced the empty output for the Firefox browser. We will research this issue in detail.

The issue is still present as originally described with TestCafe 2.2.0, Node v16.18.0 and Firefox 108.0.2.

fixed in https://github.com/DevExpress/testcafe-hammerhead/pull/2980


Implement Maintenances

Implemented web part for Maintenances

Types store is basically all number position attributes (like for charts)
Share some code with known attributes and fixed a bit CustomNumberField

I do not know how I missed it, but just noticed that I used the same glyph as for Server. Do you have an idea about substitution?

Maybe we should change server glyph to something else and keep maintenance as it is?

Yes, I wanted suggest the same.
Something like this https://fontawesome.com/v4.7.0/icon/server/ or this https://fontawesome.com/v4.7.0/icon/cogs/

I like the first one.

Changed the icon


@JSON has no effect

I have this macro:
extension JSONDecoder {
    static var testing: JSONDecoder {
        Container.shared.jsonDecoder()
    }
}
extension JSONEncoder {
    static var testing: JSONEncoder {
        Container.shared.jsonEncoder()
    }
}

@API
@Mock
@JSON(
    encoder: .testing,
    decoder: .testing
)
@KeyMapping(.snakeCase)
protocol Auth {
    @POST("/register")
    @JSON(
        encoder: .testing,
        decoder: .testing
    )
    func register(body: Body<RegisterRequestBody>) async throws -> TokensResponse
}

But in expansion i see:
struct AuthAPI: Auth {
    private let provider: PapyrusCore.Provider

    init(provider: PapyrusCore.Provider) {
        self.provider = provider
    }

    func register(body: Body<RegisterRequestBody>) async throws -> TokensResponse {
        var req = builder(method: "POST", path: "/register")
        req.requestEncoder = .json(JSONEncoder())
        req.responseDecoder = .json(JSONDecoder())
        req.setBody(body)
        let res = try await provider.request(req)
        try res.validate()
        return try res.decode(TokensResponse.self, using: req.responseDecoder)
    }

    private func builder(method: String, path: String) -> RequestBuilder {
        var req = provider.newBuilder(method: method, path: path)
        req.requestEncoder = .json(JSONEncoder())
        req.responseDecoder = .json(JSONDecoder())
        req.keyMapping = .snakeCase
        return req
    }
}

According to
req.requestEncoder = .json(JSONEncoder())
req.responseDecoder = .json(JSONDecoder())

in both places, It looks like @JSON has no effect on macro

Oh, it looks like @KeyMapping and @JSON are just mutually exclusive

However, even without @KeyMapping @JSON is still not working properly

Thanks @F0x1d - looks like this is a multiline issue. Somehow SwiftSyntax isn't picking up the arguments here when the @JSON(...) is spaced on multiple lines.
If you space it on one line, it'll work (see the test I just added). I'll investigate how to see the arguments on separate lines.

Okay, found the issue. Fixed in v0.6.7.
Thank you!


Resolves FHIR-29366

Clarifies the guiding principles behind launchActivity, and provides better examples demonstrating these guidelines more clearly.

See discussion leading to voted-upon resolution here:
https://confluence.hl7.org/pages/viewpage.action?pageId=97475869#SMARTWebMessagingBallotReconciliationCC20210104-UIActions,modeling,catalog…

See discussion leading to voted-upon resolution here:
https://confluence.hl7.org/pages/viewpage.action?pageId=97475869#SMARTWebMessagingBallotReconciliationCC20210104-UIActions,modeling,catalog…


Add script to update copyright years in LICENSE files across the board

We should write a script to automatically update the copyright year in the LICENSE file for each package.

Perhaps this could be scheduled automatically by a GitHub action as well?

If we can schedule this that would be great!


add eth-hash dependency

What was wrong?
Fixes #8
Cute Animal Picture

merging b/c minor update

muahahahahha


Group pseudo state prop crashes

Current Behavior
If I nest a component within a group component, and apply some pseudo state prop like $group-myCustomGroup-press or $group-myCustomGroup-hover, the app crashes with:
Cannot read property add of undefined.
It comes from this line: https://github.com/tamagui/tamagui/blob/052f8699d57c2e63ab24d878acc6a0377cb21be2/packages/web/src/createComponent.tsx#L415 and was introduced by https://github.com/tamagui/tamagui/pull/1960.
It works on web though
Expected Behavior
The starter does not crash
Tamagui Version
1.79.17

Platform (Web, iOS, Android)
iOS & Android only

Reproduction
Check https://github.com/CorentinAndre/tamagui-group-issue under app/features/home/screen.tsx

System Info
No response

This is fixed in latest versions, thanks.


Fix Javadoc Broken

javadoc build failed because of  https://github.com/apache/beam/commit/a1e55a234719318d9d82adb173700b7a9937dce9
Failure build log: https://scans.gradle.com/s/3dt7s6zugcdr6/console-log#L345
r: @reuvenlax @aaltay

Thanks for fixing this Boyuan:)
On Tue, Jul 17, 2018, 9:24 PM Boyuan Zhang<EMAIL_ADDRESS>wrote:

Run Java PreCommit
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/5972#issuecomment-405804658, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPc7JJl-MzHD497xQAQ5KFMeKrQaDlfks5uHrh5gaJpZM4VTvWR
.

--
Got feedback? go/pabloem-feedback

Run Java Precommit

I checked previous JavaPreCommit failure. It's related to ElasticSearchIOTests, which is unrelated to my changes.

Policy is to merge on green.

All checks passed. This PR is ready to merge.


Events / state?

Would it be possible to trigger events when the tethered element goes out of bounds, or to at least inquire into the state of the element?
Use cases:

attach to another target
choose to scroll the parent/window instead

My particular use case is that I'm building an on-selection menu. The selection Range has an array of ClientRects starting from the start of the selection ("the" in the screenshot), continuing so as to cover the selected nodes, and ending with a final ClientRect ("thousand" in the screenshot). Since the selection is created onmouseup, it makes sense to attach a drop to the last ClientRect.
The problem is that when the user scrolls and the tether goes out of bounds, flipping it above "thousand" will obscure the selection. What I want to do is either scroll the page down, or re-attach the drop element to a different target, likely the first ClientRect of the selection.

As of Tether 1.3.0, the instance object now fires an 'update' event when its attachment changes due to constraints (a088128).

@TrevorBurnham Is there any documentation on how to listen to the 'update' event? In particular, how can I have my custom callback function being called and if so, which params are passed?

var tether = new Tether(...);
tether.on('update', function(event) {
  console.log(event);
});

The event object contains attachment and targetAttachment objects of the same form as those options.


URL encoded colon in request path breaks the proxy's without option

1. What version of Caddy are you running (caddy -version)?
0.9.3
2. What are you trying to do?
Proxy a request to an upstream server.  The request URL is
http://api.docker:80/api/v1beta/admin/policies/kylo:kylo:admin:policies%3Akey-owners

3. What is your entire Caddyfile?
:8080 {
    root /srv
    proxy /api tyk:8080 {
        transparent
        without /api
    }
    log stdout
}

4.
Using docker compose:
caddy:
    image: abiosoft/caddy
    ports:
    - 80:8080
    - 443:8443
    restart: unless-stopped
    volumes:
    - ./Caddyfile:/etc/Caddyfile
    - ./public:/srv

5. What did you expect to see?
Because the "without" directive is present, I expected my upstream service to see a request with a path of /v1beta/admin/policies/kylo:kylo:admin:policies%3Akey-owners
6. What did you see instead (give full error messages and/or log)?
The request was sent to the upstream server, but retained the /api prefix.
7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
Configure a caddy file with a proxy directive to an upstream caddy with logging turned on.  Use the "without" option to the proxy directive.  Send a url with a prefix matching the "without" option, but also include %3A (the URL encoding of a colon) somewhere later in the path.  Note in the logs of the upstream caddy that the prefix was not stripped.
It's got something to do with the encoded colon.  If I send the request with a literal colon instead, it works.

Duplicate of #1154 which is already fixed in master.


Utilize test_passed API

Instead of having different cases, just check if passed.txt exists in the level directory and use a standard message otherwise.

Will do this on next pass over levels


Using utask as a task manager for people.

Hello, thanks for the wonderful utask
Is your feature request related to a problem? Please describe.
We want to try using utask as a task manager for people. For example, the negotiation of contracts or the execution of a high-level task by several executors (subtasks). Do you have an experience of using utask for such cases?

Thank you for your interest.
Supporting human processes is one of the features of utask yes.
I personally have not used it for 100% human-implemented workflows, but I have often implemented workflows where 1 of the steps was human/manual.
This is typically done by having this step be of type subtask, using a task template with no steps, and resolver_inputs configured so the human can enter the values via a form in the UI.


spawn google chrome ENOENT

After updating to ionic@alpha, 'ionic serve' gives me 'spawn google chrome ENOENT' error and I have to init it using 'ionic serve -b'.

I am having the same problem

I have 2.0.0-alpha.9

The same problem here...

This should be fixed in latest version of the CLI (ionic@alpha), please re-open https://github.com/driftyco/ionic-app-lib/issues/37 if it's not, thanks!


Fix selectors for MM 10.x and update default version to 10.15.0

this PR is now ready for merging. 9.7.1 is no longer available from the download URL.

cool stuff. thanks. will launch a version this.


🐛 [BUG] : Image Preview Cross button overlay

Describe the bug
When viewing the image preview, the cross button overlay appears inappropriately.
To Reproduce

Open the image preview.
Observe the position of the cross button overlay.

Expected behavior
The cross button overlay should not appear or should appear at an appropriate position that does not obstruct the image preview.
Screenshots
https://github.com/languageXchange/languageXchange/assets/3280475/f9992349-a424-4388-a596-a4bfaf61f3af
Desktop (please complete the following information):

OS: [e.g. Windows 10]
Browser: [e.g. Chrome, Firefox]
Version: [e.g. 91.0.4472.124]

Smartphone (please complete the following information):

Device: [e.g. iPhone 12]
OS: [e.g. iOS 15.2]
Browser: [e.g. Safari, Chrome]
Version: [e.g. 15.0.2]

Additional context
Add any other context about the problem here.
If you want speed up process of this issue, please send 🚀 as a reaction.

It's fixed with RN version.


Shared Service Templates in API

Feature #23
The API needs extra endpoints to cater for shared-service-templates. These will work in the same way as workspace-services.
Acceptance:

[ ] A new shared service template can be POSTed and seen in the data store
[ ] Shared service templates can be listed via GETs
[ ] Appropriate unit tests

@tanya-borisova the PR looks like it addresses all of the acceptance criteria above - ok for me to close this?


Wrong architecture 'amd64'

Hi, I have a ubuntu 32 bit and I like the idea of nanobox and donwload the nanobox-bundle.deb from the website but when I open the .deb get:
Wrong architecture 'amd64'

Thanks for letting us know. Apparently our downloader just defaults to 64bit. We should have alternative links for different architectures. @Tolmark12

Where I can download the 32bit?
On Fri, Nov 20, 2015 at 1:14 PM lyondhill<EMAIL_ADDRESS>wrote:

Thanks for letting us know. Apparently our downloader just defaults to
64bit. We should have alternative links for different architectures.
@Tolmark12 https://github.com/Tolmark12
—
Reply to this email directly or view it on GitHub
https://github.com/nanobox-io/nanobox/issues/77#issuecomment-158470331.

@Revod try this link here https://s3.amazonaws.com/tools.nanobox.io/cli/linux/386/nanobox (don't forget to chmod 755 and stick it in your path)

@Revod did that version of the CLI work for you?

sorry for the late reply, I download the file but it is not the complete
bundle like the web link
On Fri, Nov 20, 2015 at 4:19 PM Steve Domino<EMAIL_ADDRESS>wrote:

@Revod https://github.com/Revod did that version of the CLI work for
you?
—
Reply to this email directly or view it on GitHub
https://github.com/nanobox-io/nanobox/issues/77#issuecomment-158520156.

@Revod the file is just the executable. but s3 didn't retain the permissions so you have to 'chmod +x nanobox' then mv it to somewhere in your path.

Just so you know, the only thing you can do with the 32 bit cli is develop engines. The box we use in virtualbox is 64 bit and won't be able to start on other architectures.

Oh, thanks


multi regions being highlighted

I think is related to overall Mongolia issues, which I think are related to
the fake data. I don't think we should worry about it until we replace with
real.
On Thu, Nov 23, 2017 at 11:51 AM, Judy<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/11801365/33183131-a026a36a-d044-11e7-817a-a92e5e18d6cf.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EAPTSD/EAP-Map/issues/11, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKBZddHqk2yHPV49l4VZ5XhXWA2zG7Bwks5s5aKegaJpZM4QpA5G
.


Compilation error

Thanks for the bug report!
Describe the bug
Following the documentation, the project failed to build.
Steps to reproduce
environment:

Linux rust-lang 4.4.0-142-generic #168~14.04.1-Ubuntu SMP Sat Jan 19 11:28:33 UTC 2019 i686 GNU/Linux
Debian 9 LXC container
freshly installed php7.4-dev debian 9 package from deb https://packages.sury.org/php/ stretch main

Compile with 'just build'

LXC[rust-lang]:~/rust/php-ext-wasm$ just build
Cleaning..
Configuring for:
PHP Api Version:         20190902
Zend Module Api No:      20190902
Zend Extension Api No:   320190902
autoconf: warning: both `configure.ac' and `configure.in' are present.
autoconf: warning: proceeding with `configure.ac'.
autoheader: 'configure.ac' and 'configure.in' both present.
autoheader: proceeding with 'configure.ac'
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
checking for pkg-config... no
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for PHP prefix... /usr
checking for PHP includes... -I/usr/include/php/20190902 -I/usr/include/php/20190902/main -I/usr/include/php/20190902/TSRM -I/usr/include/php/20190902/Zend -I/usr/include/php/20190902/ext -I/usr/include/php/20190902/ext/date/lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
checking for PHP extension directory... /usr/lib/php/20190902
checking for PHP installed headers prefix... /usr/include/php/20190902
checking if debug is enabled... no
checking if zts is enabled... no
checking for gawk... no
checking for nawk... nawk
checking if nawk is broken... no
checking whether to enable wasm support... yes, shared
checking for a sed that does not truncate output... /bin/sed
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no

creating libtool
appending configuration tag "CXX" to libtool
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC...
checking if g++ static flag  works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... unsupported
configure: patching config.h.in
configure: creating ./config.status
config.status: creating config.h
/bin/bash /home/greg/rust/php-ext-wasm/src/libtool --mode=compile g++  -I. -I/home/greg/rust/php-ext-wasm/src -DPHP_ATOM_INC -I/home/greg/rust/php-ext-wasm/src/include -I/home/greg/rust/php-ext-wasm/src/main -I/home/greg/rust/php-ext-wasm/src -I/usr/include/php/20190902 -I/usr/include/php/20190902/main -I/usr/include/php/20190902/TSRM -I/usr/include/php/20190902/Zend -I/usr/include/php/20190902/ext -I/usr/include/php/20190902/ext/date/lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -DHAVE_CONFIG_H  -std=c++11   -c /home/greg/rust/php-ext-wasm/src/wasm.cc -o wasm.lo
mkdir .libs
 g++ -I. -I/home/greg/rust/php-ext-wasm/src -DPHP_ATOM_INC -I/home/greg/rust/php-ext-wasm/src/include -I/home/greg/rust/php-ext-wasm/src/main -I/home/greg/rust/php-ext-wasm/src -I/usr/include/php/20190902 -I/usr/include/php/20190902/main -I/usr/include/php/20190902/TSRM -I/usr/include/php/20190902/Zend -I/usr/include/php/20190902/ext -I/usr/include/php/20190902/ext/date/lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -std=c++11 -c /home/greg/rust/php-ext-wasm/src/wasm.cc  -DPIC -o .libs/wasm.o
In file included from /home/greg/rust/php-ext-wasm/src/wasm.cc:19:0:
/home/greg/rust/php-ext-wasm/src/wasm.hh:229:5: error: ‘wasmer_trampoline_buffer_t’ does not name a type
     wasmer_trampoline_buffer_t *trampoline_buffer;
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc: In function ‘bool initialize_wasm_imports(HashTable*, std::__cxx11::list<wasm_imported_function*>**, wasmer_import_t**, uint32_t*)’:
/home/greg/rust/php-ext-wasm/src/wasm.cc:966:33: error: ‘struct wasm_imported_function’ has no member named ‘trampoline_buffer’
             trampoline_context->trampoline_buffer = NULL;
                                 ^~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:969:13: error: ‘wasmer_trampoline_buffer_builder_t’ was not declared in this scope
             wasmer_trampoline_buffer_builder_t *trampoline_builder = wasmer_trampoline_buffer_builder_new();
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:969:49: error: ‘trampoline_builder’ was not declared in this scope
             wasmer_trampoline_buffer_builder_t *trampoline_builder = wasmer_trampoline_buffer_builder_new();
                                                 ^~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:969:107: error: ‘wasmer_trampoline_buffer_builder_new’ was not declared in this scope
             wasmer_trampoline_buffer_builder_t *trampoline_builder = wasmer_trampoline_buffer_builder_new();
                                                                                ^
/home/greg/rust/php-ext-wasm/src/wasm.cc:972:18: error: ‘wasmer_trampoline_callable_t’ was not declared in this scope
                 (wasmer_trampoline_callable_t *) imported_function_trampoline,
                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:972:48: error: expected primary-expression before ‘)’ token
                 (wasmer_trampoline_callable_t *) imported_function_trampoline,
                                                ^
/home/greg/rust/php-ext-wasm/src/wasm.cc:976:13: error: ‘wasmer_trampoline_buffer_builder_add_callinfo_trampoline’ was not declared in this scope
             );
             ^
/home/greg/rust/php-ext-wasm/src/wasm.cc:978:13: error: ‘wasmer_trampoline_buffer_t’ was not declared in this scope
             wasmer_trampoline_buffer_t *trampoline = wasmer_trampoline_buffer_builder_build(trampoline_builder);
             ^~~~~~~~~~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:978:41: error: ‘trampoline’ was not declared in this scope
             wasmer_trampoline_buffer_t *trampoline = wasmer_trampoline_buffer_builder_build(trampoline_builder);
                                         ^~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:978:111: error: ‘wasmer_trampoline_buffer_builder_build’ was not declared in this scope
             wasmer_trampoline_buffer_t *trampoline = wasmer_trampoline_buffer_builder_build(trampoline_builder);
                                                                                ^
/home/greg/rust/php-ext-wasm/src/wasm.cc:979:33: error: ‘struct wasm_imported_function’ has no member named ‘trampoline_buffer’
             trampoline_context->trampoline_buffer = trampoline;
                                 ^~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:982:19: error: ‘wasmer_trampoline_callable_t’ does not name a type
             const wasmer_trampoline_callable_t *trampoline_callable = wasmer_trampoline_buffer_get_trampoline(trampoline, trampoline_index);
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:986:36: error: ‘trampoline_callable’ was not declared in this scope
                 (void (*)(void *)) trampoline_callable,
                                    ^~~~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc: In function ‘void wasm_instance_destructor(zend_resource*)’:
/home/greg/rust/php-ext-wasm/src/wasm.cc:1166:65: error: ‘struct wasm_imported_function’ has no member named ‘trampoline_buffer’
             wasmer_trampoline_buffer_destroy(imported_function->trampoline_buffer);
                                                                 ^~~~~~~~~~~~~~~~~
/home/greg/rust/php-ext-wasm/src/wasm.cc:1166:82: error: ‘wasmer_trampoline_buffer_destroy’ was not declared in this scope
             wasmer_trampoline_buffer_destroy(imported_function->trampoline_buffer);
                                                                                ^
Makefile:192: recipe for target 'wasm.lo' failed
make: *** [wasm.lo] Error 1
error: Recipe `build` failed with exit code 2
LXC[rust-lang]:~/rust/php-ext-wasm$

Additional context
If I simply run cargo build I also have a compilation error
  Compiling typetag v0.1.4
error[E0425]: cannot find function `get_fault_info` in this scope
   --> /home/greg/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-runtime-core-0.11.0/src/fault.rs:289:21
    |
289 |         let fault = get_fault_info(siginfo as _, ucontext);
    |                     ^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find value `ARCH` in this scope
   --> /home/greg/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-runtime-core-0.11.0/src/fault.rs:294:82
    |
294 |                     let magic_size = if let Some(x) = get_inline_breakpoint_size(ARCH, v.backend) {
    |                                                                                ^^^^ not found in this scope
help: possible candidate is found in another module, you can import it into scope
    |
30  | use std::env::consts::ARCH;
    |

error[E0425]: cannot find value `ARCH` in this scope
   --> /home/greg/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-runtime-core-0.11.0/src/fault.rs:303:29
    |
303 | ...                   ARCH,
    |                       ^^^^ not found in this scope
help: possible candidate is found in another module, you can import it into scope
    |
30  | use std::env::consts::ARCH;
    |

   Compiling target-lexicon v0.8.1
error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0425`.
error: could not compile `wasmer-runtime-core`.
warning: build failed, waiting for other jobs to finish...
error: build failed

Problem
I am trying to figure out what I did wrong but had no clue.

It seems the issue is on Wasmer. Moving the issue to that repo :)


Set Ruby version to 2.2.4

Heroku is starting to yell at me about how they're depreciating 2.0.0, and I don't want this to go by the wayside. We shouldn't resolve now to avoid having to lock people into specific ruby versions, but we should resolve before the MVP goes live.

Changing to 2.2.4 since that's the version ruby-audit recommends.


Update documentation to highlight two different packages

For people not being too familiar with the install process or just tend to forget things, then ideally the install documentation could highlight that there are two different releases/packages. The error message given when installing the wrong package does not reveal the real problem but simply states:

An error occured while fetching package

Giving visibility on multiple packages can reduce filed issues here 😁
Adaption on documentation page could be to change it into something like this:

Installing the package
The pfSense REST API package is built just like any other pfSense package and can therefor be installed easily using pkg from the pfSense command line. Do note that there are two different packages, depending on your system:
pkg-static -C /dev/null add https://github.com/jaredhendrickson13/pfsense-api/releases/latest/download/pfSense-2.7.2-pkg-RESTAPI.pkg
If you are installing this on Netgate hardware then use this:
pkg-static -C /dev/null add https://github.com/jaredhendrickson13/pfsense-api/releases/latest/download/pfSense-24.03-pkg-RESTAPI.pkg

There are a couple different things here:
First, the An error occured while fetching package is more likely to do with the pkg system not being up-to-date on the system, which is more problematic with pfSense Plus because the plus package repos are locked down more than the CE repos. Running pkg-static update is generally the fix for that, although that doesn't happen often. When trying to install a version that was not built for the running version of pfSense (for example, installing the 24.03 build on 2.7.2, you get this error:
$ pkg add https://github.com/jaredhendrickson13/pfsense-api/releases/download/v2.1.0/pfSense-24.03-pkg-RESTAPI.pkg
Fetching pfSense-24.03-pkg-RESTAPI.pkg: 100%  783 KiB 801.8kB/s    00:01
Installing pfSense-pkg-RESTAPI-2.1...
pkg: wrong architecture: FreeBSD:15:* instead of FreeBSD:14:amd64

Failed to install the following 1 package(s): https://github.com/jaredhendrickson13/pfsense-api/releases/download/v2.1.0/pfSense-24.03-pkg-RESTAPI.pkg

The only reason the package is built for specific versions of pfSense like it is currently is because the underlying versions of FreeBSD vary across releases. When CE and Plus are operating on the same FreeBSD version, it actually doesn't matter which package is used to install as the package's code is exactly the same across both.

Second, as for the documentation, this is the intent of the notation below the install command:

I can differentiate the commands between CE and Plus, but even then it won't be fully sufficient as there are times where the package is built for older versions of CE and Plus alongside the latest where the issue could still occur. I will definitely make this scenario more apparent though. Appreciate the suggestion!


first rough software architecture

Create first rough version of folders tree.

Created first versoin of folders tree; prepared first version of a module.


Content removed prematurely

Viva Connections does not exist for O365 GCC customers yet, and has no timeline for release. Please restore the old content in the meantime for those that don't have access to Viva Connections.

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

ID: 8ef9b82d-5475-c5fa-ac7a-7005558e06f1
Version Independent ID: 1d9d4923-c44f-b00b-a553-60c73ed8b8e6
Content: Embedding modern SharePoint pages in Microsoft Teams as personal apps (preview)
Content Source: docs/features/embed-pages-to-teams.md
Product: sharepoint
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Dupe #7039


Offered another identifier for orphaned assignments

Clarified that ObjectType reflects an unknown value for orphaned role assignments in PowerShell #atcp

@WhitWaldo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Hi @WhitWaldo
Thanks for taking the time to add this clarification to the docs. We'll get your changes merged.
thanks!

#sign-off


update to reflect dataset changes (to PETS)

Closes #41
in this PR, I updated the notebook to run inference on

SavedModel downloaded from TFX Trainer's output Artifact. So, this case shows how to run inference on a local environment
Vertex Endpoint where the produced model from TFX pipeline is deployed to

@sayakpaul
this notebook shows how to run inference on Vertex Endpoint as well. Do you think it is better to create a separate notebook? In my opinion, it is OK to go with a single file (maybe change the filename). WDYT?

@sayakpaul
this notebook shows how to run inference on Vertex Endpoint as well. Do you think it is better to create a separate notebook? In my opinion, it is OK to go with a single file (maybe change the filename). WDYT?

Sounds good to me. But what about the CONCRETE_INPUT fix?

I have to say sorry that CONCRETE_INPUT was fixed without a PR today's afternoon. I thought it's a so simple issue since we could simply set CONCRETE_INPUT to transform_name(IMAGE_KEY), and I just did.
Anyways, my apologies, and I will make sure to create PRs on any issues in the future.

No worries. Glad it was resolved.

addressed your comments!


Unable to connect

Connecting to a FACT view from Datasphere, but I'm getting the following error:

Unable to connect
We encountered an error while trying to connect.
Details: "OData: The feed's metadata document appears to be invalid. Error: The metadata document could not be read from the message content.
InvalidEnumMemberPath : 'Collection(Capabilities.FilterExpressionRestrictionType)/MultiValue' is not a valid enum member path. : (70, 14)
Where should I look to resolve this issue?
Regards,
Mel Calucin

HI Mel,
this error message indicates that the meta data description generated by SAP Datasphere is corrupt. MS PowerBI reads the metadata and validates it - the error message says, that "Collection (Capabilities.FilterExpressionRestrictionType) /MultiValue" is a non permitted value. We had similar error messages in the past, which required a fix provided by SAP Datasphere.
Next steps: Follow up with SAP Datasphere support
Details to provide: (if possible) Add the metadata response to the incident and provide the name of the space and view.
Workaround Options:
Open the metadata respose and search for /MultiValue - when scrolling up a bit you typically find the name of the column/field which is related to /MultiValue. Remove or hide this field and your data requests should be successfull. In addition, check the data type of this column - if it is somehow "special" try to use a common data type.
Please let us know the result of the proposed steps.
Best regards, Olaf


请教一下，口型同步的能力什么时候能加上

如题，我在代码中看到「TODO: Add lip sync API」，貌似现在并不支持口型同步，而官方SDK的demo里是有这个能力的。
想请教一下这个能力是会补上嘛~

这个坑一直没有填上的动力，因为感觉几乎没什么场景能用上，而且准确来说也不属于 Live2D 自身带有的功能（而是作为示例），也没必要放在这个库里，想要使用的话直接把官方的文件复制进你的项目里使用就好了：
https://github.com/Live2D/CubismWebSamples/blob/2a2d4f34c6f04e301a82f642f548efb9442cbaa1/Samples/TypeScript/Demo/src/lappwavfilehandler.ts
https://github.com/Live2D/CubismWebSamples/blob/2a2d4f34c6f04e301a82f642f548efb9442cbaa1/Samples/TypeScript/Demo/src/lappmodel.ts#L515-L524

等等，我仔细看了一下，原来这个同步是基于模型的声音文件的，我一直以为是基于用户的语音输入……
那看来还是有必要加入的，我会重新考虑一下

等等，我仔细看了一下，原来这个同步是基于模型的声音文件的，我一直以为是基于用户的语音输入……
那看来还是有必要加入的，我会重新考虑一下

对的，核心代码就是  this._model.addParameterValueById(this._lipSyncIds.at(i), value, 0.8);
感觉把官方demo里那个读取wav文件音量大小的逻辑抄过来就行。
因为我这边想让口型和motion解绑，所以准备在大佬提供的事件通知里（beforeModelUpdate）去更新口型

补充一下后续：这部分代码是在 Live2D 自己的 license 下的，但那个 license 我实在是看不懂，不确定能不能在二次分发的项目里使用，目前就卡在这里了

I made some modifications in my fork to play model audio files. I don't know anything about the licensing unfortunately:
https://github.com/fatalgoth/pixi-live2d-display/commit/ebfb98ad91f221794e70fa94064d19aab4c2a6e8

I made some modifications in my fork to play model audio files with lip sync. I don't know anything about the licensing unfortunately:
fatalgoth@ebfb98a

thanks for you job and one question is that does the static vars contents and analysers at the SoundManager.ts not clean correctly while the audio had been removed?

I made some modifications in my fork to play model audio files with lip sync. I don't know anything about the licensing unfortunately:
fatalgoth@ebfb98a

thanks for you job and one question is that does the static vars contents and analysers at the SoundManager.ts not clean correctly while the audio had been removed?

Can you teach me how to use this fork?

I made some modifications in my fork to play model audio files with lip sync. I don't know anything about the licensing unfortunately:
fatalgoth@ebfb98a

thanks for you job and one question is that does the static vars contents and analysers at the SoundManager.ts not clean correctly while the audio had been removed?

Can you teach me how to use this fork?

I haven't use it for the prod env yet. 3 ways that might work：

clone the fork project and run npm run setup && npm run prepublishOnly after npm install.  Then you can use the  lib index.min.js  via cdn.

clone the fork project and republish it to npm as your own package.

fork the project and use it as a submodule in your project. However you have to handle the problem of import path since it use alias path.

I haven't use it for the prod env yet. 3 ways that might work：

clone the fork project and run npm run setup && npm run prepublishOnly after npm install.  Then you can use the  lib index.min.js  via cdn.
clone the fork project and republish it to npm as your own package.
fork the project and use it as a submodule in your project. However you have to handle the problem of import path since it use alias path.

I have reviewed and tried this fork source code.
It seen incomplete.
I'm trying to implement it by self.
Do you has any thinking about that?

I haven't use it for the prod env yet. 3 ways that might work：

clone the fork project and run npm run setup && npm run prepublishOnly after npm install.  Then you can use the  lib index.min.js  via cdn.
clone the fork project and republish it to npm as your own package.
fork the project and use it as a submodule in your project. However you have to handle the problem of import path since it use alias path.

I have reviewed and tried this fork source code. It seen incompleted.
I'm trying to implement it by self. Do you has any thinking about that?

You can replace pixi-live2d-display in package.js like this:

"pixi-live2d-display": "git+https://github.com/fatalgoth/pixi-live2d-display.git",

Run yarn install.

It really a good idea but seems not work for me unless i add a prepare script.
windjackz@ 499d2c8
This fork source code is work but it seems not clean clean correctly.
I will implement it by my self too and try to decouple the sounds and json file

大佬们能考虑下用wav2lip+lipsync试试看,能否搞定口型绑定

大佬们能考虑下用wav2lip+lipsync试试看,能否搞定口型绑定

我半年前就已经做好了，没那么复杂。

大佬们能考虑下用wav2lip+lipsync试试看,能否搞定口型绑定

我半年前就已经做好了，没那么复杂。

大佬能给个技术路线建议或者参考工程,我研究研究,谢谢🥹

大佬们能考虑下用wav2lip+lipsync试试看,能否搞定口型绑定

我半年前就已经做好了，没那么复杂。

大佬能给个技术路线建议或者参考工程,我研究研究,谢谢🥹

给你发邮件了，里面有些参考代码（虽然写的很乱哈哈哈）

大佬们能考虑下用wav2lip+lipsync试试看,能否搞定口型绑定

我半年前就已经做好了，没那么复杂。

大佬，我也需要这部分，我发现之前看到有个项目中依赖的 pixi-live2d-display源码中 存在 speak  函数，好像该函数是实现说话的，但是我到了仓库这边发现并没有这个 speak 如图：

大佬们能考虑下用wav2lip+lipsync试试看,能否搞定口型绑定

我半年前就已经做好了，没那么复杂。
大佬能也给我发一下吗,我研究研究,谢谢


search results link to right place and docs for build Deps

This closes #3250 and part 1 of #3366

@niravasher please follow these commit specifications

Please separate this branch in 2, one for each issue.


"ASP.NET Core Blazor Server additional security scenarios" is incorrect in token-based authentication example

This section of the MS docs: https://learn.microsoft.com/en-us/aspnet/core/blazor/security/server/additional-scenarios?view=aspnetcore-6.0#pass-tokens-to-a-blazor-server-app outlines an example for retrieving a user's access_token and refresh_token using the HttpContext at the top-level of the application (_Host.cshtml). After following this guide, I have found it to be incorrect. (But please let me know if I'm doing something incorrectly :D)
Suggestion
Either remove this section or add a correction, although I'm not sure what the correction should be - I'm still not totally sure how this can be done in Blazor Server.
Steps to Reproduce

Set up a Blazor Server app with OpenIdConnect auth. I'm using Keycloak for authentication. Relevant portion of my Program.cs:

builder.Services.AddScoped<TokenProvider>();

builder.Services.AddAuthentication(auth =>
	{
		auth.DefaultAuthenticateScheme = CookieAuthenticationDefaults.AuthenticationScheme;
		auth.DefaultSignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
		auth.DefaultChallengeScheme = OpenIdConnectDefaults.AuthenticationScheme;
	})
	.AddCookie()
	.AddOpenIdConnect(OpenIdConnectDefaults.AuthenticationScheme, options =>
	{
		options.MetadataAddress = builder.Configuration["Keycloak:Metadata-Address"];
		options.Authority = builder.Configuration["Keycloak:Authority"];
		options.ClientId = builder.Configuration["Keycloak:Client-Id"];
		options.ClientSecret = builder.Configuration["Keycloak:Client-Secret"];
		options.ResponseType = OpenIdConnectResponseType.Code;

		options.SaveTokens = true;
		options.Scope.Add("openid");
		options.Scope.Add("profile");
		options.Scope.Add("offline_access");
	});

Create a TokenProvider class as in the example. I also put a GUID on the TokenProvider class to show how this example doesn't work:

public class TokenProvider
	{
		private string? _token;
		private string _guid;

		public TokenProvider()
		{
			_guid = Guid.NewGuid().ToString();
		}

		public string? AccessToken
		{
			get
			{
				Trace.WriteLine("GUID: " + _guid);
				Trace.WriteLine("TOKEN: " + _token);
				return _token;
			}
			set => _token = value;
		}
		public string? RefreshToken;
	}

Pull the user's access_token and refresh_token from their HttpContext as in the linked page in _Host.cshtml:

TokenProvider.AccessToken = await HttpContext.GetTokenAsync("access_token");
TokenProvider.RefreshToken = await HttpContext.GetTokenAsync("refresh_token");

Put some dummy code in the App.razor's initializor ( or some other top-level component, doesn't really matter)

protected override void OnInitialized()
	{
		base.OnInitialized();
		var howdy = TokenProvider.AccessToken;
	}

Now run the application and access the site. You should see two back-to-back log statements when you load the site. One will include your access token, and one won't.
GUID: 8e7cc8a1-6dde-41af-b07d-1675fac1e2f7
TOKEN: eyJhb.....<abbreviated>
GUID: cf379e66-ac85-4264-8f3a-6c984bbe9a67
TOKEN:

This happens because we are using the "ServerPrerendered" render-mode in our _Host.cshtml(This is the default render mode):
<component type="typeof(App)" render-mode="ServerPrerendered"/>
in ServerPrerendered the app will load once with just static assets and then load again once the server has responded (2 loads total). On the first load, it looks like we get our token as expected.
If you change the render-mode to "Server" You lose the first render and just get the post-server render, with no token returned by the HttpContext. Since TokenProvider is scoped to a single session, it also changes on load. We could hold onto the token if we change
builder.Services.AddScoped<TokenProvider>();
to
builder.Services.AddSingleton<TokenProvider>();
in Program.cs, but then all clients to the application will share a single TokenProvider and will be overwriting each other's tokens. We want a TokenProvider scoped to each user's session (circuit). When following the example, in the docs, it appears that the application will always get an empty access token.
Some references:

https://stackoverflow.com/questions/60996170/blazor-scoped-service-initializing-twice
https://stackoverflow.com/questions/72319872/token-is-coming-as-null-from-gettokenasync-in-blazor-server

The doc linked in this issue does not recognize this critical issue. The code provided in the doc does not work due to this.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 6f8acbbf-c9d4-7041-c1a7-ec9ce8f0981b
Version Independent ID: c98be365-408d-7ee6-cb74-14c44d01b0b8
Content: ASP.NET Core Blazor Server additional security scenarios
Content Source: aspnetcore/blazor/security/server/additional-scenarios.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

Alright, after 2 days of this problem I found out the docs are actually correct. You have to make an InitialState (or whatever name) custom class to hold the token from _Host.cshtml, and pass it down to App.razor to set in the scoped TokenProvider. I foolishly thought this intermediary step was unnecessary and injected + assigned the tokens to the TokenProvider in _Host.cshtml. For some reason, you have to pass the tokens into App.razor and set them on the TokenProvider in App.razor.
tl;dr: Don't skip these two sections or you'll be a sucker like me:
_Host.cshtml:
@{
    var tokens = new InitialApplicationState
    {
        AccessToken = await HttpContext.GetTokenAsync("access_token"),
        RefreshToken = await HttpContext.GetTokenAsync("refresh_token"),
        XsrfToken = Xsrf.GetAndStoreTokens(HttpContext).RequestToken
    };
}

<component ... param-InitialState="tokens" ... />

App.razor:
@inject TokenProvider TokenProvider

...

@code {
    [Parameter]
    public InitialApplicationState? InitialState { get; set; }

    protected override Task OnInitializedAsync()
    {
        TokenProvider.AccessToken = InitialState?.AccessToken;
        TokenProvider.RefreshToken = InitialState?.RefreshToken;
        TokenProvider.XsrfToken = InitialState?.XsrfToken;

        return base.OnInitializedAsync();
    }
}


Scheduler cron job is running but artisan schedule:run command did not triggered

Description:
I followed the instruction to update the crontab in workspace
`

laradock /usr/bin/php /var/www/marketplace artisan schedule:run >> /dev/null 2>&1
`

I added \Log::debug("schedule run"); in my Kernel.php to verify that it is working.
Then i rebuild the workspace and found out there is no log, when check the /var/log/cron.log, it showed the command had been executed

I also tried execute the command manually inside workspace and confirmed it is working if without the crontab.
Expected Behavior:
Crontab should execute artisan schedule:run and trigger the logging "schedule run"
Stacktrace & Additional info:
PHP_VERSION=7.3
Docker version = 4.2.0

After change the cronjob into  * * * * * laradock cd /var/www/marketplace && php artisan schedule:run >> /dev/null 2>&1 and it worked, not sure why the documentation way is not working.
Furthermore, i hit another issue which is "crontab missing newline before eof". This is caused by my host OS which is window 10. The recommended way to solve this is using linux to create the cronjob file. But for me to solve this, i removed the code inside crontab/laradock and add one more line to append the cron job after copy the cron tab files.
`
COPY ./crontab /etc/cron.d
RUN chmod -R 644 /etc/cron.d
RUN echo "* * * * * laradock cd /var/www/marketplace && php artisan schedule:run >> /dev/null 2>&1" >> /etc/cron.d/laradock
`


add a brief thing about the channel restriction

Please describe the changes this PR makes and why it should be merged:
Adds a brief statement about the reaction handler in the report system being restricted to the report logging channel
Status

[✔ ] Code changes have been tested on an instance of YAGPDB, or there are no code changes
[✔ ] I have read and followed the contribution guide
[✔ ] I have written documentation for my changes, or there is no need to

Thanks!


Support non-docker

Most of our CI are running on systems where either:

Docker isn't installed or allowed (because it would open up docker in docker and thus need the sock open)
Docker sock is disabled
Running in kubernetes where it isn't using docker

Is it possible to shift to a set of libraries that can pull the images and layers without needing docker?

Indeed! dive already supports opening a tarball, so combining this with skopeo you should be good to go:
❯ skopeo copy docker://docker.io/centos:8 docker-archive:centos-8.tar
Getting image source signatures
Copying blob 8a29a15cefae done
Copying config 470671670c done
Writing manifest to image destination
Storing signatures
❯ dive docker-archive://centos-8.tar

(If this didn't resolve your issue feel free to repoen)

What is the supported docker version?
I've got a pretty old system with Docker 1.6.2 and it run into error with:
$ docker save -o centos-8.tar centos:8
$ dive docker-archive://centos-8.tar
Image Source: docker-archive://centos-8.tar
Fetching image... (this can take a while for large images)
cannot fetch image
could not find image manifest