bug: "E-commerce Product Description" example not working

Steps to reproduce:

npx create-fabrice-ai
Choose a template to get started:
│  E-commerce Product Description - Convert product photos into compelling store listings
cd fabrice-ai-example
npm install
node --import=tsx src/ecommerce_product_description.ts

Result:
 node --import=tsx src/ecommerce_product_description.ts
🕒 Distributing the task...
Request: Analyze the picture './example/assets/example-sneakers.jpg' to identify and list all visible technical features of the sneakers, such as color, size, material, and brand.
🛠 Agent "Technical expert" is beginning to work on the task
Step details: Analyze the picture './example/assets/example-sneakers.jpg' to identify and list all visible technical features of the sneakers, such as color, size, material, and brand.
🔄 Agent "Technical expert" is moving to the next step
Step details: Use the 'functions.visionTool' to analyze the image for technical details.
🔧 Agent "Technical expert" is calling tools
Tools: visionTool
node:internal/fs/promises:639
  return new FileHandle(await PromisePrototypeThen(
                        ^

Error: ENOENT: no such file or directory, open './example/assets/example-sneakers.jpg'
    at async open (node:internal/fs/promises:639:25)
    at async Object.readFile (node:internal/fs/promises:1249:14)
    at async encodeImage (file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/@fabrice-ai/tools/dist/vision.js:8:25)
    at async Object.execute (file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/@fabrice-ai/tools/dist/vision.js:63:75)
    at async file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/fabrice-ai/dist/teamwork.js:167:25
    at async Promise.all (index 0)
    at async runTools (file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/fabrice-ai/dist/teamwork.js:163:25)
    at async nextTick (file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/fabrice-ai/dist/teamwork.js:286:35)
    at async iterate (file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/fabrice-ai/dist/teamwork.js:324:23)
    at async teamwork (file:///Users/michalrusinek/repos/ai-investigations/fabrice-ai/fabrice-ai-example/node_modules/fabrice-ai/dist/teamwork.js:351:31) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: './example/assets/example-sneakers.jpg'
}

Node.js v20.15.0

I've tried to modify the path to the image, moved it directly to ecommerce_product_description.is directory. I tried to use my image example too. Nothing seems to work

Hey @marelix2! Thanks for raising this issue. The fix is on the way: https://github.com/callstackincubator/fabrice-ai/pull/104
Quick fix:
Change the relative path in the src/ecommerce_product_description.ts - line 27, from:
const productDescriptionWorkflow = workflow({
  members: [techExpert, marketingManager],
  description: `
    Based on the picture './example/assets/example-sneakers.jpg' make the eCommerce product to
    list this product on the website.

... to fixed one:
const productDescriptionWorkflow = workflow({
  members: [techExpert, marketingManager],
  description: `
    Based on the picture '${path.resolve(__dirname, '../assets/example-sneakers.jpg')}' make the eCommerce product to
    list this product on the website.

Hey @marelix2! Thanks for raising this issue. The fix is on the way: https://github.com/callstackincubator/fabrice-ai/pull/104
Quick fix:
Change the relative path in the src/ecommerce_product_description.ts - line 27, from:
const productDescriptionWorkflow = workflow({
  members: [techExpert, marketingManager],
  description: `
    Based on the picture './example/assets/example-sneakers.jpg' make the eCommerce product to
    list this product on the website.

... to fixed one:
const productDescriptionWorkflow = workflow({
  members: [techExpert, marketingManager],
  description: `
    Based on the picture '${path.resolve(__dirname, '../assets/example-sneakers.jpg')}' make the eCommerce product to
    list this product on the website.


#301 List of available config accessible for end-users

Motivations:
As pointed out by issue #301 , in the online tutorial for plotting the gallery of fusion machines, we ask the user to read a hidden variable tf.geom.utils._DCONFIG_TABLE.
This is not good practice, a public method should exist to list all available pre-implemenetd configurations.
Main changes:
Two new methods are created, a hidden and a public:

tf.geom.utils._get_listconfig() : a hidden method used to generate the dict of (unique keys, shortcuts) from hidden variables _DCONFIG and _DCONFIG_TABLE and return either a fully formatted str message or the dict itself. It is used to provide the core message of the public method, and also re-used to properly generate the error message when tf.geom.utils.create_Config() is not properly called by the user.
tf.geom.utils.get_available_config(): a public method that prints a fully formatted explicit message containing all available keys to pre-implemented config

Example:
In [1]: import tofu as tf

In [2]: tf.geom.utils.get_available_config()
A config is the geometry of a tokamak
You can define your own (see online tutorial at https://tofuproject.github.io/tofu/auto_examples/tutorials/tuto_plot_create_geometry.html)
tofu also also provides some pre-defined config ready to load
They are available via their name or via shortcuts

	unique names	shortcuts
	------------ 	-------------------------
	- ITER-V1     	['ITER-V1', 'A2']
	- ITER-V2     	['ITER-V2', 'B4', 'ITER']
	- JET-V0      	['JET-V0', 'JET']
	- NSTX-V0     	['NSTX-V0', 'NSTX']
	- WEST-Sep    	['WEST-Sep', 'A3']
	- WEST-V1     	['WEST-V1', 'A1']
	- WEST-V2     	['WEST-V2', 'B1']
	- WEST-V3     	['WEST-V3', 'B2']
	- WEST-V4     	['WEST-V4', 'B3', 'WEST']

  => to get a pre-defined config, call for example:
	config = tf.geom.utils.create_config('ITER')

Issues:
Fixes, in devel, issue #301

Hello @Didou09! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tofu/geom/utils.py:

Line 716:17: E225 missing whitespace around operator
Line 724:25: E128 continuation line under-indented for visual indent

Codecov Report

Merging #327 into devel will decrease coverage by 0.07%.
The diff coverage is 23.8%.

@@            Coverage Diff             @@
##            devel     #327      +/-   ##
==========================================
- Coverage   40.23%   40.15%   -0.08%
==========================================
  Files          79       79
  Lines       23993    24010      +17
==========================================
- Hits         9653     9641      -12
- Misses      14340    14369      +29

Impacted Files
Coverage Δ

tofu/version.py
100% <100%> (ø)
:arrow_up:

tofu/geom/utils.py
42.39% <20%> (-0.95%)
:arrow_down:

tofu/data/_core_new.py
13.15% <0%> (-0.47%)
:arrow_down:

tofu/geom/_core_optics.py
14.35% <0%> (-0.35%)
:arrow_down:

tofu/geom/_comp.py
60.3% <0%> (-0.22%)
:arrow_down:

tofu/data/_core.py
39% <0%> (-0.18%)
:arrow_down:

tofu/geom/_plot.py
64.98% <0%> (-0.11%)
:arrow_down:

tofu/geom/_core.py
63.24% <0%> (-0.11%)
:arrow_down:

Continue to review full report at Codecov.

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


Add more crypt schemes (sha512/bcrypt)

After we removed the 'clear'-password field, now I added support for more advanced hashing for user passwords. Sha512 can be used on Linux, exim can authenticate via courier or dovecot-imap. Bcrypt is only available (by default) on *BSD systems.
Configuration and documentation updated.

I rebased my request to remove conflicts.

I thought we could leave final testing to the admin setting their system up.
What we could do is perhaps list the methods that we have tested and provide good examples and sane defaults.
I tried playing with the crypt() function, and it doesn't seem like a too long salt would break anything, so I assume we could always use the salt long enough to satisfy all commonly used algorithms.

I just put in some of your remarks.
Regarding the hash and salting, I don't really see the point for a user to change all these settings by default. I haven't seen any solution where you can change all these parameters. If you think it's better to use a longer salt or to use more rounds, let's do this straight away.

My idea was that we don't have to limit our users to a certain list of crypt algorithms. If we allow specifying salt prefix directly, we wouldn't have to keep track of what algorithms are available/practical at any given time and what their prefixes are. For example, the Blowfish-based crypt scheme may use $2a$, $2b$, $2x$ or $2y$ prefixes, with the latter two introduced only in 2011. I presume even $2$ was valid at some point. If we allow the admin to specify "blowfish" as crypt scheme, we have to choose only one prefix for that scheme, and assume that it will always be practical, or that the admin will edit Vexim code to cater with the new reality, or that we will release an update and the admin will use it. 10 iterations may be secure enough today, but not so in a few years. I'm just saying we have a choice here – we can allow the user to choose the password encryption algorithm from a list, or we can let them enter it free-form, but make the entry itself a bit more complicated. Or we can even support both ways, shipping our friendly-named defaults, yet allowing custom crypt schemes starting with the $ character.

What I like about your idea is that you can even increase security over time. Assume you start with sha512 and 5000 rounds (default). Later, you can add more rounds in the configuration and all new passwords will respect this new definition. Previous passwords are still valid.
So I try to implement the salt-prefix into the crypt scheme. I would keep the options des, md5 and clear for compatibility.

For the moment, I kept sha512 and bcrypt. You can set a prefix like you want, e.g. $6$rounds=N$ or $2y$10$, $2a$12$, ...

Latest commit https://github.com/Udera/vexim2/commit/c7e2a61c3d50b10c6677b1c76a68a370b30bbb2f
If password "CHANGE" is used the siteadmin is redirected to the change-password-page after login.

I removed some lines, we can even put MD5 into this generalized salt-part.

Should be still working ;-)

I applied the changes.

Ok, they are back in.

Good!
I haven't looked at the Perl script changes, as I want to remove it before the release.
One last thing: could you now squash all these commits into one, and give that commit the same name as this PR?

You mean a new PR?
I could do this tonight.

No, not necessarily a new PR. You may push to the same branch (with --force) after squashing in which case this PR will be updated.
It's not really elegant as it rewrites history, but assuming that your branch hasn't yet been cloned by anyone your branch yet, it's safe.
How to squash really simply is explained here.
Note that if you don't feel confident about squashing, you may want to copy your repository before doing that. Or you can ask me to do that for you. :)

I changed history :D

Congrats! :)


[FEATURE] Enable "Leave Session" for Participants

Description
A user can decide that they want to leave a session in the session overview page. Leaving a session means:

[ ] Maintained annotations stay, but connection to the user is anonymized
[ ] Participant is not listed in session participants list
[ ] Invitations are not send to the user any more
[ ] Dialog is shown to the participant telling the consequences of leaving a session (not able to participate any more)

@KoALa-MHF/mh-team when a user leaves a session, in which places should their annotations still be visible:

[ ] Session analysis page?
[ ] Export?
[ ] Participant Counter (not directly annotations, but connected to this)
[ ] Participant Overview List (also not directly annotations, but connected)

After a participant left a session the related data should not be available in any view. @KoALa-MHF/mh-team Am I getting this right?
In the export the data should be added. This is maybe obvious in the data by labeling the dataset of the user as anonymous.


Feature/parmoo

This PR for the inclusion of ParMOO in the BAND.
Note that rather than being included as a submodule or have the source code in bandframework, the approach taken was to instead include sufficient documentation for the quick installation of ParMOO as well as how to obtain an example problem of ParMOO being run for a multi-objective calibration of (surrogate of) the Fayans energy density functional.
We are asking for reviewers to:

follow the instructions in the README and confirm they are clear and complete
examine the SDK compatibility document for correctness and completeness

Thank you!

Atting @thchang for awareness

Thanks @odell @mosesyhc @asemposki !
This has been updated by @thchang using PR 59.
In addition to clarifying the README, the corresponding REQUIREMENTS.txt file in the parmoo-solver-farm/fayans-model-calibration-2022 repository has been updated to better pull in dependencies.

Thanks all


but he can help me with the problem I have with my miner Bobocat300, he doesn't do anything for many hours, that is 12, , 15.20 h daily https://explorer.helium.com/hotspots/latest mining name. Swif Vini Babger. Romania (Bucharest)

but he can help me with the problem I have with my miner Bobocat300, he doesn't do anything for many hours, that is 12,
, 15.20 h daily https://explorer.helium.com/hotspots/latest mining name. Swif Vini Babger. Romania (Bucharest)

Thanks for your submission, but this repository is for Helium Improvement Proposals (HIPs) and is not a support or discussion forum.
If you'd like to write and submit proposal, you should follow the format and process prescribed in HIP7, Process for managing Helium Improvement Proposals
I've also written a rough guide to doing this using the github.com web interface: https://jamiedubs.com/blog/how-to-submit-helium-manufacturer-application/
I am closing this as invalid but feel free to ask further questions here or in Discord


ILogger resolved before external container configuration

https://github.com/aspnet/Hosting/blob/a5b083a39bae974e95ff1a9437468a103e72f6ea/src/Microsoft.AspNetCore.Hosting/WebHostBuilder.cs#L177
This line of code seems to attempt to resolve ILogger. However, providing a custom ServiceProvider is done within the Startup class, which happens after this.
This is a new problem in the latest version of ASP.Net Core. I didn't have this issue on at least 2.0.0. The WebHostBuilder never attempted to log anything, I guess, so never needed to go through this.
So, what's the answer now? I remove the ILogger/LoggerFactory implementations from the IServiceCollection so they are not accidentally used, and my IServiceProvider is used instead.
Being able to specify the IServiceProvider implementation to the WebHostBuilder would be ideal. That way setup could be done outside Startup.cs

One way of working around this I thought would be to register a specific ILogger<WebHost> into the service collection preemptively, while NOT registering a generic version. However, because WebHost is an internal type, this is harder than I thought it would be.

@Tratcher @pakrym thoughts on this one?

What’s the problem you’re hitting?

This is a continuation of the discussion on why having two containers is problematic. The long term plan is to move to Generic Host and only use a single container. https://github.com/aspnet/Hosting/blob/c9a4ee8b719ffb01eb44705d68efd158eb80c221/src/Microsoft.Extensions.Hosting/HostBuilder.cs#L174
In the short term we're left with awkward workarounds like the one above.


[DOCS] ask Taylor to review new NMIND check achievements

This is to ask Taylor to review recent changes in BABS (mostly in docs) and to make sure more NMIND checks have been achieved.

These NMIND checks have been achieved:
Documentation Domain:

[ ] issue #149  - see PR #148
[ ] issue #150 - see PR #148
[ ] issue #151 - see PR #148
--> so all checks at Silver level in this domain are done.

Infrastructure Domain:

[ ] issue #147 - see PR #130
[ ] (silver) No excessive files included (i.e., unused files / cache; e.g., .gitignore)

I have cleaned up files on github, esp notebooks folder
--> so all checks at Silver level in this domain are done.

(def not a Friday afternoon work - I will ask you on Monday, Taylor!)

Confirmed by Taylor today (10/30/2023) that all silver checks have been done except testing.


Update to V12

This modual is essential for Functionality of V12

Try out 12.0.0 and let me know it


fix: Windows binaries properly use the .exe extension

Windows won't spawn a process unless it has the magical exe file extension. The secondary benefit of this pull request is it'll always restore missing symlinks, regardless of platform.

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

v0.117.4
v0.117.4
GitHub release

Your semantic-release bot :package::rocket:


feat: delete open scoped Classical in finsuppTensorFinsupp

Replace open scoped Classical with DecidableEq type class implicit arguments
in finsuppTensorFinsupp, and add DecidableEq elsewhere when needed as a result.

Closing, then. Thanks!


KeyError in setter for observation_summaries - when it calls assess_process_obs in XMMPointed

XMM-Newton Pointed - Generating ODF summary files: 100%|█| 424/424 [06:34<00:00,  1.
Traceback (most recent call last):
File "xmm_process_script.py", line 31, in
odf_ingest(lovoccs_arch)
File "/mnt/ufs18/home-218/turne540/code/DAXA/daxa/process/xmm/_common.py", line 389, in wrapper
obs_archive.observation_summaries = parsed_obs_info
File "/mnt/ufs18/home-218/turne540/code/DAXA/daxa/archive/base.py", line 490, in observation_summaries
self._use_this_obs[mn][o_id] = self._missions[mn].assess_process_obs(rel_dat)
File "/mnt/ufs18/home-218/turne540/code/DAXA/daxa/mission/xmm.py", line 401, in assess_process_obs
to_return = {inst: {e_id: True for e_id in list(obs_info[inst]['exposures'].keys())} for inst in insts}
File "/mnt/ufs18/home-218/turne540/code/DAXA/daxa/mission/xmm.py", line 401, in
to_return = {inst: {e_id: True for e_id in list(obs_info[inst]['exposures'].keys())} for inst in insts}
KeyError: 'exposures'
Probably happening because I have acquired an observation with no exposures or something? That would be very weird though. Possibly also iterating through the wrong instruments? I specified only PN, MOS1, and MOS2 for this, and may have left R1, R2, and OM still technically 'allowed' by the mission?

So the first ObsID I managed to grab that caused this problem (using a workaround to get it to run) was<PHONE_NUMBER> - it only has OM data because it was a calibration observation - that means all of the instruments that DAXA was told to process imply aren't active. The 'proper' fix will be to check that at least one of the requested instruments are active before going to the mission obs info checker.
The list of all the observations (in the LoVoCCS lot) for which an error popped up are:
0095011401
0109980501
0095011501
0112951301
0145260301
0159567901
0827031801
0827032001

The errors are happening for any observation where not all the expected instruments are activated I think.

I think the change in behaviour I make is going to be in the mission method that checks to see whether things should be used or not - it'll check the 'active' entry, and if it is false it'll make sure to flag that instrument as being unusable without trying to extract sub-exposure information.


Calling git on module import could be avoided

This is a feature proposal rather than a bug.
I've found that, when git execution is skipped within Import-Module call, it can save about 100 milliseconds of module startup time. It's not that much even on my machine, but the same framework allowing this, could be "easily" used to entirely disable prompt support, which can save 1/3 of total module import time, or about 1/4 of everything when including pwsh startup too.
This could be done through support for setting posh-git module prerequisites via beforehand prepared global key-value hash set (i.e. @{}) with:

old module parameters
current git version
additional config

Some time ago, I've decided to find out a way to speed up posh-git module import time. Then, I've figured out that skipping whole prompt-support could be a useful thing - e.g. https://github.com/dahlbyk/posh-git/issues/927
However, avoiding "dot-sourcing" everything related to prompt, could be problematic to integrate with "bundling everything into a single file" as proposed in https://github.com/dahlbyk/posh-git/pull/698 - but will we finalize it?
Moreover, setting module arguments with array of numbers (i.e. -ArgumentList 0,0,0) is kind of hard to grasp at the call site, as one need to know meaning and order of module parameters. On the other side, I'm not sure if using global-dictionary is a "tolerable" way to pass configuration into PowersShell module.
This feature could be also used to toggle additional features, like setting strict-mode, or enabling warnings from exceptions occurred while generating a completion result - what was useful when I've been discovering what is required for completion without Posh-Git prompt support.
I'm suggesting something like:
$global:PoshGit_InitProps = @{
  DisablePoshGitPrompt = $true;
  UseFunctionCompletion = $true;
  ShowCompletionErrors = $true;
  LocalGitVersion = [System.Version]"2.39.2";
  LocalGitExtensions = @{ flow = $true }
}

Import-Module posh-git

Thus, I would love to bring support for providing prerequisites into posh-git module. I've explored that possibility in my private fork, and I would like to prepare a little bit more "serious" Pull-Request to be merged here:

without "profiling" code - __log* methods, from my own Profile.ps1
with fixed or newly introduced tests or extended documentation
ensured compatibility with older PowerShell versions

Based on my pwsh-profile-benchmarker.ps1, where pwsh -NoProfile was called with different scripts as "profiles", I've found that my machine has two modes: "slow", and "twice-slower" 😅. However, lower values and trend-lines of different series, show improvements described above:

I like the performance energy here, I also had a look at this
I found that a $PROFILE with a single line of Import-Module ~\git\posh-git\src\posh-git.psd1 adds 412ms to my startup time of 214ms.
❯ hyperfine --warmup 2 'pwsh -c "echo hello world"' 'pwsh -NoProfile -c "echo hello world"'
Benchmark 1: pwsh -c "echo hello world"
  Time (mean ± σ):     626.3 ms ±   3.9 ms    [User: 3.1 ms, System: 10.9 ms]
  Range (min … max):   619.2 ms … 631.8 ms    10 runs

Benchmark 2: pwsh -NoProfile -c "echo hello world"
  Time (mean ± σ):     214.5 ms ±   2.6 ms    [User: 2.4 ms, System: 6.7 ms]
  Range (min … max):   210.6 ms … 220.1 ms    13 runs

Summary
  'pwsh -NoProfile -c "echo hello world"' ran
    2.92 ± 0.04 times faster than 'pwsh -c "echo hello world"'

Using feature/profiling of posh-git and feature/human-readable-duration of PSProfiler to profile , I found some of the hotspots:
 pwsh -NoProfile {
    Import-Module ~\git\PSProfiler\src\PSProfiler.psd1
    Measure-Script -HumanReadable -Path ~\git\posh-git\src\posh-git.ps1
}
...
 1    10             42ms . $PSScriptRoot\CheckRequirements.ps1 > $null
 0    11              0ms
 1    12             34ms . $PSScriptRoot\ConsoleMode.ps1
 1    13             24ms . $PSScriptRoot\Utils.ps1
 1    14              8ms . $PSScriptRoot\AnsiUtils.ps1
 1    15              8ms . $PSScriptRoot\WindowTitle.ps1
 1    16             12ms . $PSScriptRoot\PoshGitTypes.ps1
 1    17             15ms . $PSScriptRoot\GitUtils.ps1
 1    18             65ms . $PSScriptRoot\GitPrompt.ps1
 1    19             15ms . $PSScriptRoot\GitParamTabExpansion.ps1
 1    20             63ms . $PSScriptRoot\GitTabExpansion.ps1
 1    21              5ms . $PSScriptRoot\TortoiseGit.ps1
...

By removing code that isn't related to tab completion, I could get a measured startup time of 486ms in hyperfine, which 271ms for the module, a 34% improvement (271 / 412).
If anybody is interested to try, the code is on feature/profiling of posh-git.

However, avoiding "dot-sourcing" everything related to prompt, could be problematic to integrate with "bundling everything into a single file" as proposed in https://github.com/dahlbyk/posh-git/pull/698 - but will we finalize it?

I wanted to say about this one, it would be nice if we could have a bundle just with the tab completion logic? Like we could have two bundles, one with prompt + tab completion, and the other with just tab completion, and choose which one to source based on $DisablePromptSupport or similar. Or we could split tab completion to an entirely new PSModule?

Nice, I saw similar distribution of times related to "dot-sourcing" respective files.

In the matter of separated modules with different set of bundled code. I think, this could be a very neat option to have, e.g. posh-git and posh-git-completion, where the latest will not support prompt at all. However, I believe this would bring more burden for maintainers, and could rise possible issues with confusion of what do what, and which module who should use - but maybe this should be a way.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/525 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit 69a4d3e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-06-18-01-36-40 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-06-18-01-36-40

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[SPARKR][SPARK-17442] Additional arguments in write.df are not passed to data source

What changes were proposed in this pull request?
additional options were not passed down in write.df. This patch fixes that
How was this patch tested?
Adds unit test for passing header = "true" for CSV data source in R unit tests

Test build #65065 has started for PR 15007 at commit 7da87cd.

Test build #65065 has finished for PR 15007 at commit 7da87cd.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65065/
Test FAILed.

Test build #65067 has started for PR 15007 at commit 78d1dce.

Test build #65067 has finished for PR 15007 at commit 78d1dce.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65067/
Test FAILed.

Merged build finished. Test FAILed.

sorry for the trouble, I opened #15010 with the fix

Test build #65078 has started for PR 15007 at commit e2f88dc.

Test build #65078 has finished for PR 15007 at commit e2f88dc.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65078/
Test FAILed.

@falaki We can use the PR at https://github.com/apache/spark/pull/15010 and close this one ?


Standalone optic API

optic-ts contains a standalone api which looks a bit more like this
O.compose(
  'foo',
  O.optional,
  O.when((value: number) => value > 42)
)

I've come across instances where this API is preferable, especially if I'm reusing complex optics
e.g.
const myComplexOptic = O.compose(
  'foo',
  O.optional,
  O.guard((obj:{type:string}) => obj.type === 'bar')
)

const bazAtom = focusAtom(dataAtom,O.compose(myComplexOptic,'baz'));
const quxAtom = focusAtom(dataAtom,O.compose(myComplexOptic,'qux'));

This might also contribute to solving such issues as #15 without introducing new concepts
I think this would be worth implementing

Would you be interested in implementing it?
I think we should create a completely new function.


Removes MouseCapture

This avoids to capture the mouse enabling copy/paste with it.
Closes #422

Thanks :-)


Dynamically constructionhe computation graph based on dimensions

The code can construct the computation graph based on dimensions dynamically，how can author realize it？ by Trimming or filling ？

It resizes it using TensorFlow bilinear interpolation here.


Node version discovery is botched for Windows workers

Docs page says run az webapp list-runtimes to get the Node version to populate WEBSITE_NODE_DEFAULT_VERSION app setting. But that's incorrect for Windows workers, values like 14-lts or node|14-lts will not match an installed version and will result in HTTP 500 for any site request.
~ $ az webapp list-runtimes
[
...
  "node|10.6",
  "node|10.10",
  "node|10.14",
  "node|12-lts",
  "node|14-lts",

However if you fill in WEBSITE_NODE_DEFAULT_VERSION = 14.16.0 (meaning any value that you get via Kudu API at https://{yourWebAppName}.scm.azurewebsites.net/api/diagnostics/runtime), that will be picked up and the Node version will be successfully set. The example in the docs page is hinting at this but your are overwhelmingly leading readers to believe that whatever az webapp list-runtimes gives you will work.

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

ID: 896b5d4c-ac3b-f0a2-5102-9e59bbe2ed48
Version Independent ID: 32fd9660-0d08-205c-c7f3-57b00f35e667
Content: Configure Node.js apps - Azure App Service
Content Source: articles/app-service/configure-language-nodejs.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @snobu, I see what you mean. az webapp list-runtimes returns values that you can use with the --runtime argument for az webapp create command. With values like -lts, this won't work. We'll get the doc updated to make this more clear.


Image bounds are in geographic coordinate system

Hello!
I'm not sure what I'm doing wrong here, but I'm trying to generate tiles from a GeoTIFF, but it can't assess that a tile is within its bounds because in the tile_exists method within base.py, the bounds array contains geographic lat/lon coordinates instead of projected coordinates.
My basic code is as follows:
from rio_tiler.io import COGReader

with COGReader("myraster_projected.tif") as img:
  img.tile(1, 1, 1)

Which throws the error
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/mnt/c/Users/Alex/WORK/coding/landsat-tiler/rio-tiler/rio_tiler/io/cogeo.py", line 264, in tile
    raise TileOutsideBounds(
rio_tiler.errors.TileOutsideBounds: Tile 1/1/1 is outside myraster_projected.tif bounds

I've tried re-projecting my raster to EPSG:3857 but the issue still prevails - I've added some print statements to get the bounds array contents and it still prints out that it is in a geographic coordinate system. Is there an additional step I should be doing?

Hi @mcvittal thanks for opening the issue.
the error message says that the Mercator Tile x=1, y=1, z=1 bounds coordinates do no intersect with your raster bounds.
what is the output of
from rio_tiler.io import COGReader
import morecantile

tms = morecantile.tms.get("WebMercatorQuad")
print(tms.bounds(1, 1, 1)

with COGReader("myraster_projected.tif") as img:
    print(img.bounds)

Thanks for the quick reply!
This outputs
BoundingBox(left=-2.0078911277343066e-13, bottom=-85.05112877980652, right=179.9999999999992, top=2.0355549961366507e-13)

(2.125432099751016, 48.64001935810568, 2.147842404720507, 48.65631726102131)

BoundingBox(left=-2.0078911277343066e-13, bottom=-85.05112877980652, right=179.9999999999992, top=2.0355549961366507e-13)

(2.125432099751016, 48.64001935810568, 2.147842404720507, 48.65631726102131)

☝ shows that your raster doesn't intersect with tile 1-1-1 (latitude of your file is ~48 North, while grid max lat is ~0)

I'm going to close this issue because it's not bug, but please feel free to re-open if you feel the documentation should better explain that we cannot read tiles that are outside your raster bounds 🙏

I'm just a little bit confused here. The image is a small high-res image located in Paris, France (Hence the location of 2, 48) - this should be well within the bounds of the Web Mercator maximum and minimum bounds. I'm trying to serve this as a tiled webmap, and thought that this tool would be the best way to do something like this on the fly. Below is a screenshot of the image with a Google Maps basemap:

Obviously, at zoom level 1, it would be a pretty useless webmap tile as it is very small, but it should be able to generate something at least.

@mcvittal you are right, rio-tiler can create tile from you file (but I wouldn't recommend using it for really low zoom level).
The error you are experiencing for tile 1-1-1 is absolutely expected, the tile x=1, y=1, z=1 DO NOT intersect with your file thus rio-tiler CANNOT read the corresponding data for the tile bounds ... because it doesn't exist.
if you try tile x=1, y=0, z=1. it should work (but it will be really memory intensive: see https://github.com/cogeotiff/rio-tiler/issues/348)


Feature request: Support multiple processes on the same port

Support reuseport
See https://github.com/shadowsocks/shadowsocks-libev/issues/493

Or an option like --workers=4

https://github.com/libp2p/go-reuseport

There's no need for it. Unlike ss-libev, which is single-threaded, go-ss2 is multi-threaded by default. It will use all available cores to handle multiple connections.


Infinite recursion when using with Django SimpleLazyObject

Hi,
I use an object of type django.utils.functional.SimpleLazyObject as a template variable.
When an AttributeError happens in the inner of a lazy object the template rendering falls into infinite recursion.
Expected Behavior
A traceback about the attribute error is displayed.
Actual Behavior
Template rendering falls into infinite recursion.
Minimal Code To Reproduce
from django.utils.functional import SimpleLazyObject
import jinja2

def raises_attribute_error():
      raise AttributeError()

template = jinja2.Template('{{ obj.hello.recursion }}')
template.render(obj=SimpleLazyObject(lambda: raises_attribute_error()))

Full Traceback
Traceback (most recent call last):
  File "main.py", line 10, in <module>
    template.render(obj=SimpleLazyObject(lambda: raises_attribute_error()))
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 1, in top-level template code
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/jinja2/environment.py", line 471, in getattr
    return getattr(obj, attribute)
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/jinja2/runtime.py", line 738, in _undefined_message
    object_type_repr(self._undefined_obj),
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/jinja2/utils.py", line 169, in object_type_repr
    if obj.__class__.__module__ in ("__builtin__", "builtins"):
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/django/utils/functional.py", line 224, in inner
    self._setup()
  File "/Users/rkashapov/Library/Python/3.7/lib/python/site-packages/django/utils/functional.py", line 360, in _setup
    self._wrapped = self._setupfunc()
  File "main.py", line 10, in <lambda>
    template.render(obj=SimpleLazyObject(lambda: raises_attribute_error()))
  File "main.py", line 6, in raises_attribute_error
    raise AttributeError()
RecursionError: maximum recursion depth exceeded while calling a Python object

Your Environment

Python version:  3.7.3
Jinja version: 2.11.1

This is due to the way that Jinja variable lookup and undefined handling works. First it tries to get the attribute hello, which raises an attribute error. Then it tries to treat the variable as a dict key, which also raises an attribute error, so it returns an undefined object. Then it tries to look up the attrribute recursion on the undefined object, which raises an undefined error, which tries to print out some information about the object (obj.__class__.__name__), which raises an attribute error again.
In this case, it's possible to fix this by changing the undefined code to use type(obj) instead. But in general, the code you've shown indicates a bad design. Avoid code that could potentially raise an AttributeError in every situation it's used, as that's a recipe for disaster, especially when looking up attributes.

Thanks


add support for UpdateCustomerPaymentProfileRequest endpoint

Please let me know what I can do to get this in as soon as possible. I need it for my project.
Thanks for the great library! :)

I'm not sure I understand the build failures. My local run of phpunit passed, but the log seems to be complaining about whitespace. I'm not familiar with this system so I'm not sure if that's the error that's causing it to fail. I believe I matched the whitespace to what you guys already have. Please let me know what I missed if you can. Thanks again :)

Hey, thanks for PR! I can give it a look over. If it's phpcs I can tweak up
before merger.
Thanks for this, got missed in initial SDK hustle.
On Fri, Aug 11, 2017, 7:03 PM KC Erb<EMAIL_ADDRESS>wrote:

I'm not sure I understand the build failures. My local run of phpunit
passed, but the log seems to be complaining about whitespace. I'm not
familiar with this system so I'm not sure if that's the error that's
causing it to fail. I believe I matched the whitespace to what you guys
already have. Please let me know what I missed if you can. Thanks again :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/commerceguys/authnet/pull/21#issuecomment-321943091,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhv1GCmNNBtZL9MBvUe8juizRUN_1kUks5sXOvXgaJpZM4O1PQx
.

Yep, just because space is 2 instead of 4 (to match PSR-2). I can fixup for merge no problem

Thanks for the quick response, the library was well architected so it was a piece of cake. Since I already have this ready to push, I could just fix it here. OK by you? (We're just talking about the new class right?)

Yeah, go ahead. The Travis output says which and where. If you install
phpcs and actually run phpcbf --standard=psr-2, I believe it is, and it
can autofix it
On Fri, Aug 11, 2017, 7:12 PM KC Erb<EMAIL_ADDRESS>wrote:

Thanks for the quick response, the library was well architected so it was
a piece of cake. Since I already have this ready to push, I could just fix
it here. OK by you? (We're just talking about the new class right?)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/commerceguys/authnet/pull/21#issuecomment-321943812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhv1AKcm4rQpbNGd-ikwIG8SitJfo0Fks5sXO3RgaJpZM4O1PQx
.

Hmm, those failures are interesting. When I ran locally, I would see those methods (not ones that I touched by the way so I hope I didn't break them 😬 ) fail 1 in 5 times or so. It seems kinda sporadic. Perhaps you guys know more about that?

Out for a walk, realized main branch is failing. Maybe I committed the
failure way back
On Fri, Aug 11, 2017, 7:22 PM KC Erb<EMAIL_ADDRESS>wrote:

Hmm, those failures are interesting. When I ran locally, I would see those
methods (not ones that I touched by the way so I hope I didn't break them
😬 ) fail 1 in 5 times or so. It seems kinda sporadic. Perhaps you guys
know more about that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/commerceguys/authnet/pull/21#issuecomment-321944632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhv1H9wm-hskHKdIWR3qkGyyjE0wQgmks5sXPAtgaJpZM4O1PQx
.

Thanks for the PR! Merged!

Awesome, thanks for the quick turn around!


users unable to search files

I change the name here since the bug affected more than just read only users.
If a user who is not the owner of a dataset searched for files, they would not find files in the dataset.
This is because the user_ids were not updated in the elasticsearch entries for the files.
To fix this, I added a method index_dataset_files which is called after datasets are updated and indexed.
I also checked and a user that is part of a group will find files in the group. Ready for review.

I'm converting to draft again because some issues are coming up with groups. Adding and removing members from groups seems to mean that some users who are in a group that has access to a file or dataset will not get it in search results.

Important Note:
I cannot get the shellcheck pre-commit hook to run on my machine. So far I have found no solution - I can install it via brew but if my pre-commit config is not the same as the one in the github repo, it rejects the commit.
So if someone else can please run it as part of the review, thank you very much.
This should be ready to review now.

I see this. Could you please check?


🐛 Ambiguous filter settings

Area
Proposal Pillar
Domain
gov.tools
Which wallet were you using?
No response
Context
Clarity issue for users.
Steps to reproduce
The difference between "active proposal" and "submitted for vote" is unclear, leading to confusion about the status of actions.
Actual behavior
The difference between "active proposal" and "submitted for vote" is unclear, leading to confusion about the status of actions.
Expected behavior
Improve explanations and labels for filter settings to differentiate between proposal statuses.

Duplicate of #2262 .


Merge changes from main

Summary by Sourcery
Enhance the README with a comprehensive description of the 'diverse_seq' tool's capabilities and update the 'ruff' dependency version in the build configuration. Add 'statsmodels' to the documentation dependencies.
Enhancements:

Update the README to provide a more detailed description of the 'diverse_seq' tool, highlighting its alignment-free algorithms and efficiency in phylogenetic workflows.

Build:

Update the 'ruff' dependency version from 0.7.2 to 0.7.3 in the 'pyproject.toml' file.
Add 'statsmodels' to the documentation dependencies in the 'pyproject.toml' file.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.892%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
1190

Relevant Lines:
1295

💛  - Coveralls


sidecar injection cm change requires istiod restart

Bug description
While testing remote cluster and mutating webhook configuration, I found out sidecar injection cm change does require istiod to restart to pick up the change.  It would be great if this isn't required.
The change I did for testing: https://github.com/istio/istio/issues/23879#issuecomment-630268528
Expected behavior
restart istiod should not be required
Steps to reproduce the bug
modify something in the sidecar injector cm (for example ISTIO_META_CLUSTER_ID) and check if it is picked up by deploying a new pod with auto sidecar injector.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
1.6 rc.0

I don't think it does unless it recently regressed. It should be automatically updated.
However, kubernetes configmaps are incredibly slow to update for some reason - takes 30-60s

I think this is a regression. curl 0:8080/debug/inject shows the update but injection calls use the old one

Actually nevermind, its just slow :slightly_smiling_face: at least for me, it seems to update

https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#mounted-configmaps-are-updated-automatically
When a ConfigMap already being consumed in a volume is updated, projected keys are eventually updated as well. Kubelet is checking whether the mounted ConfigMap is fresh on every periodic sync. However, it is using its local ttl-based cache for getting the current value of the ConfigMap. As a result, the total delay from the moment when the ConfigMap is updated to the moment when new keys are projected to the pod can be as long as kubelet sync period (1 minute by default) + ttl of ConfigMaps cache (1 minute by default) in kubelet. You can trigger an immediate refresh by updating one of the pod’s annotations.

@howardjohn @hzxuzhonghu thank you very much for your comments!  This makes sense, and I have validated it does take 2 mins to pick up the change without restart.


Create slim for Ribbon display of prokaryotes

For display in UniProt
@alexsign

CC
GO:0005737 	cytoplasm
GO:0005886 	plasma membrane
GO:0005840 	ribosome
GO:0043226 	organelle
GO:0042597 	periplasmic space
GO:0009579 	thylakoid
GO:0005576 	extracellular region
GO:0009279 	cell outer membrane
GO:0042995 	cell projection
GO:0005694 	chromosome
GO:0005618 	cell wall
GO:0043590 	bacterial nucleoid
MF
GO:0016209 	antioxidant activity
GO:0009975 	cyclase activity
GO:0016787 	hydrolase activity
GO:0016853 	isomerase activity
GO:0016874 	ligase activity
GO:0016829 	lyase activity
GO:0060090 	molecular adaptor activity
GO:0140104 	molecular carrier activity
GO:0098772 	molecular function regulator activity
GO:0016491 	oxidoreductase activity
GO:0140299 	small molecule sensor activity
GO:0005198 	structural molecule activity
GO:0090729 	toxin activity
GO:0016740 	transferase activity
GO:0005215 	transporter activity
GO:0003723 	RNA binding
GO:0140110	transcription regulator activity
BP
GO:0006091 	generation of precursor metabolites and energy
GO:0006259	DNA metabolic process
GO:0006351 	DNA-templated transcription
GO:0006355 	regulation of DNA-templated transcription
GO:0006412 	translation
GO:0006457 	protein folding
GO:0006520 	amino acid metabolic process
GO:0006629 	lipid metabolic process
GO:0006810 	transport
GO:0007155 	cell adhesion
GO:0008152	metabolic process
GO:0015979 	photosynthesis
GO:0023052 	signaling
GO:0042254 	ribosome biogenesis
GO:0044238	primary metabolic process
GO:0044283 	small molecule biosynthetic process
GO:0048870 	cell motility
GO:0050896 	response to stimulus
GO:0071554 	cell wall organization or biogenesis
GO:0098542 	defense response to other organism
GO:0098754 	detoxification

I attach a file that shows the coverage of the ribbon versus the full prokaryote subset for bacteria (NCBI Taxon:2), reviewed UniProt entries.
prokaryote-ribbon.xlsx


An error occurred: File size<PHONE_NUMBER>) is greater than possible Buffer:<PHONE_NUMBER> bytes

OS Version: darwin 18.7.0
Notable Version: v1.7.3

RangeError [ERR_FS_FILE_TOO_LARGE]: File size<PHONE_NUMBER>) is greater than possible Buffer:<PHONE_NUMBER> bytes
    at FSReqCallback.readFileAfterStat [as oncomplete] (fs.js:274:11)

Yep, thanks. I did just that.

I'm reopening this as I think eventually we should support arbitrarily sized files.

Closing this in favor of #22.
The library now throws a regular error for huge files.


a biggish revamp of the toplevel documentation

The colab link is broken; the build and test badge is reading failed


feat(day21): implement solutions

Checking tests + README.

Codecov Report

Merging #17 (4626e3f) into main (6171d0a) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
+ Coverage   97.76%   97.87%   +0.11%
==========================================
  Files          39       41       +2
  Lines        3617     3815     +198
==========================================
+ Hits         3536     3734     +198
  Misses         81       81

Impacted Files
Coverage Δ

Sources/Library/Game.swift
100.00% <100.00%> (ø)

Tests/LibraryTests/GameTests.swift
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Update troubleshooting guide for Podman-in-Podman

Add a small section on the bad things that can happen if you don't mount in our temporary directories.
Fixes #1602

This is going to be a merge conflict once https://github.com/containers/libpod/pull/2576 finally gets in.

LGTM other than the merge dance you and @rhatdan will have to do.

Rebased

/lgtm


Refactor Readme

Missing parts:

Explorative analysis
Contribution

@tobiasgrantner : do we want to merge this after we add the youtube link, so that those parts are finally up to date . And we add Contributing.md and Explorative, when they are finished?


The problem of vanilla alternative crafting

Hello, I ran into a problem. I need to disable alternative vanilla recipes. They are added when the EnderIO mod is installed on the client. I could not find information on how to disable them anywhere. Also, there are no custom recipes in the file in the directory. The EnderIO version is 1.12.2-5.1.55.

https://github.com/SleepyTrousers/EnderIO/blob/master/enderio-base/src/main/resources/assets/enderio/config/recipes/misc.xml

Thank you very much, the information helped.


No footer in the default theme and renderhooks

Search Terms
footer, theme
Problem
No footer in the default theme. This makes things like copyright notice, privacy notice (e.g., for those who use Google analytics), logo that commonly appear at the footer have no good place to go.
Suggested Solution
Add a footer to the default theme and add footer.{begin,end} render hooks.

To clarify, when I say footer, I meant a footer that uses the footer tag. Currently, with the default theme, the "Generated by TypeDoc" text is not enclosed by a footer tag, and appending a footer tag using body.end render hooks would cause somewhat unnatural results.

The "Generated by TypeDoc" probably ought to be in a footer tag


Fix for Character Sheet

Fix iteration breaking at ageSystemActor.js when changes are undefined.  Give me your number so we can talk more in private, please

Hi! Thank you very much for pointing out this issue. It is now updated in my working branch with a slightly different solution (this is the reason I didn't add the PR as is). In the next release we may see the effects. Cheers!


Rate limit errors due to checksum fetching

With a large number of hosts, the task "Get checksum for amd64 architecture" usually fails for at least some of them with the following error:
fatal: [HOST1]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/prometheus/node_exporter/releases/download/v0.16.0/sha256sums.txt : HTTP Error 429: Too Many Requests"}
fatal: [HOST2]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/prometheus/node_exporter/releases/download/v0.16.0/sha256sums.txt : HTTP Error 429: Too Many Requests"}
fatal: [HOST3]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/prometheus/node_exporter/releases/download/v0.16.0/sha256sums.txt : HTTP Error 429: Too Many Requests"}
fatal: [HOST4]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/prometheus/node_exporter/releases/download/v0.16.0/sha256sums.txt : HTTP Error 429: Too Many Requests"}

This appears to be because the checksum is fetched for each node (which makes sense, they don't all share the architecture), but is fetched by the controller node, so for 40 amd64 nodes, the controller will fetch the amd64 checksums 40 times.
For now I have locally set run_once: true in ~/.ansible/...`, but I think this needs a proper solution.

Possible fix is to create a list of all CPU arch used in deployment and use run_once for checksum and download tasks. This would also speed up deployment.

@mineo could you test if solution from #51 works for you?

@paulfantom #51 appears to fix this, thank you! I've only verified it on amd64 nodes, since I don't have access to any other architecture supported by node_exporter (only ppc64le, for which there are no pre-built binaries).

@mineo Thanks!


feat: revamp landing page

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup
/kind design
/kind user-interface
/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos
What this PR does / why we need it:
This PR has

featured videos content
minor refactoring

Which issue(s) this PR fixes:
#825

Fixes #
Special notes for your reviewer:

@alexakvelon: The label(s) area/videos cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup
/kind design
/kind user-interface
/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos
What this PR does / why we need it:
This PR has

featured videos content
minor refactoring

Which issue(s) this PR fixes:
#825
Fixes #
Special notes for your reviewer:

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: alexakvelon
Once this PR has been reviewed and has the lgtm label, please assign jasondellaluce for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alexakvelon, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: cf1cd0ea194625d943c798df5aca63a19c1cb4b9


Extremely stretched 3d aspect ratio regardless of settings

The 2d menus and hud render fine but the 3d is extremely squashed regardless of which settings I change. I changed resolution, internal resolution, ran it windowed. Nothing was different. RTX 2080 Super on windows 10. Driver 546.33 WHQL.

were you previously using a widescreen patch by any chance?  the pixelaspectratio value is being modified in an unexpected way here

were you previously using a widescreen patch by any chance? the pixelaspectratio value is being modified in an unexpected way here

Yep that was the issue. Previously had the cumulative patch but deleted the files thinking it would be fine. Used it on a fresh install and the issue did not persist. My bad lol

Good to hear!  I should probably add a note about possible conflicting files to the installation instructions as other patches often use dinput.dll or other regular looking dlls


Please verify that the --pid_suffix option works as intended

Discussed in https://github.com/gaogaotiantian/viztracer/discussions/345

Originally posted by kllp June 13, 2023
Recent versions of viztracer don't seem to append the PID to the filename. Instead it creates result.json.
viztracer --pid_suffix single_process.py appends the PID in version 0.12.3 but not in 0.15.6
https://viztracer.readthedocs.io/en/latest/concurrency.html#combine-reports

Seemed that ofile with pid_suffix is not set correctly in VizUI. I can make a pr to fix it.


onClick prop should be optional

The latest doc change indicates you can indirectly toggle the switch via the "on" prop, but not having an onClick still throws an undefined err.

Thanks for catching that.  This is now fixed in 2.0.1.


Make watcher restarts clean

This allows to cleanly restart the watcher. The previous approach with
manually trying to clean require.cache didn't work well and produced
various memory leaks.
This commit changes the brunch init process: the binary does not
directly run brunch commands, but instead, creates a child process that
processed the commands. In case the child process needs to restart, it
kills it and runs another one.
It works properly under two conditions: both global brunch binary and
the local brunch installation contain this commit. If the global brunch
is older, or if the local brunch is older, the old behavior will be
preserved.

Note: what this means is there will be at least two processes when running brunch watch (but not other commands) — one that handles restarts, another that does the actual processing. However, the overhead of this approach should not be significant since the binary process does not actively do anything but wait for the restart message from the watcher. Its memory footprint should also be minimal since it only requires system modules.

Let's find a way of not running the second process by default.

A new process is only spawned only when it's really needed — i.e. only in watcher. No way around this if we want to be able to cleanly restart the watcher without quitting the process and having the user run brunch again manually.


Infer the literals used in the type of the groups

🆒 Your use case
When I create a regexp group using anyOf and groupedAs, the type of the matched group should be inferred based on the inputs to anyOf.
Similar to the type of the main regexp that gets inferred.
E.g.
const regex = createRegExp(
  anyOf("A", "B", "C")
    .groupedAs("opponent")
    .and(" ")
    .and(anyOf("X", "Y", "Z").groupedAs("self")),
);

Here, the type of regex is
MagicRegExp<"/(?<opponent>A|B|C) (?<self>X|Y|Z)/", "opponent" | "self", ["(?<opponent>A|B|C)", ...any[]], never>

so the information that the groups have literals of ABC and XYZ respectively is included in the type. However, the type of
"A Y".match(regex)?.groups.opponent

is string | undefined instead of "A" | "B" | "C".
🔍 Alternatives you've considered
No response
ℹ Additional info
My goal is to use this library in conjunction with colinhacks/zod. magic-regexp complements zod well when it comes to string validation and parsing while still being typesafe.
I'm open to work on this myself. Please let me know where I should have a look to get started with such a feature.

This is definitely a worthy enhancement. I think @didavid61202 might be working on this very thing (so let's wait to hear from him), but if not then contribution would be very welcome ❤

Hi @michaelschufi,
Yes, I've been working on a new type inferencing (fully parse, interpret, exact match, permutation all possible values) for string.match, string.replace, string.matchAll and string.replaceAll
a little peek at what's possible (blue text are type hints from vscode-twoslash-queries):

Still have to finish writing more robust test cases and testing for some edge cases.

Yes, I've been working on a new type inferencing (fully parse, interpret, exact match, permutation all possible values) for string.match, string.replace, string.matchAll and string.replaceAll

Sounds awesome! 😀
Of course, if the other functions can also benefit of the inference, it's even better. I haven't worked yet with .replace with this library, but this sounds really game changing. It makes it so much easier to work with string manipulation of all kind.
The inference looks great so far. Tell me if I can help with some testing or similar.

Hi @michaelschufi, Here's the repository for the type-level RegExp parser and matcher. Check out examples in the 'tests/index.test-d.ts' file and others when you have some time. Please let me know if you encounter any issues or have any ideas. Thank you!
https://github.com/didavid61202/type-level-regexp

HI @didavid61202
Thank you. I've got a lot on my plate right now, so it might take me a moment. But I'll try to have a look at it this weekend.

Sorry for my late response @didavid61202
I have tested the repo lately, and I couldn't find any breaking issue. I'm in awe of what this thing can do! 😍
Only one negative thing that I noticed: It seems to push either VS Code or the typescript language server to their limits. But this could be because of my pc, VS Code, TS, TLS, the repo itself with many complex examples, or any combination of those things...
I have a few minor things that I would like to discuss. E.g. what the restInput key represents. Should I file an issue in your repo?

Hi @michaelschufi, thanks!
Yes, I think this is pushing the language server to its limit by both lots of recursions and also lots of test examples. 😂  There are some performance issues that can be improved by a better parser and match algorithm. I've been testing some benchmark methods and I will start by rewriting the ParseRegExp generic. Any inputs regarding performance improvement are welcome!
Do file issues if you have any questions 👍
The restInput generic argument in RegExpMatchResult  represents the rest of input string that is not matched by the regexp provided, it's used for resolving the preceding string before the matching string, and getting the preceding string length for index value of the match result.

Hi @didavid61202
About performance:
I've just read about the TypeScript 5.1 Beta's release notes and came across the Negative Case Checks for Union Literals section. Maybe those optimizations also affect the regex type literals.

Hi @michaelschufi, thanks for the info! 👍
I'll have to check if this affect the current implementation, or how we can utilize this to improve the performance


Photo of the Spectator View bracket used with Hololens 2

Hi,
I tried looking for photos of the Spectator's bracket on the Hololens 2, and cant seems to find them on the internet.
Does anyone have photos of this Spectator View's bracket being used with Hololens 2.
I would like to check before I print them, to see if it can hold its pose precisely every time it is removed and put back on.
Thanks.

https://github.com/microsoft/MixedReality-SpectatorView/tree/master/doc/models/HoloLens2CameraMount
here you are
you can print it out with 3D printer

There are multiple ways to mount the camera to the bracket, this is just my quick and mediocre way to do it.

The main attachment point is a 3/4" threaded rod running through the central column of the bracket with a coupling nut on either end.  This is the standard thread for almost all cameras.       I do NOT recommend this,   It's a hassle to attach and remove the camera, and you have no guarantee that the camera will be facing the same direction each time. Also if the nuts are not tight enough, the headset can swivel easily.
Instead, i'd recommend getting a hotshoe mount and attaching that to the bottom of the hololens bracket.  Then your bracket  will mount on top of your camera, and should maintain it's relative position better.

A few other notes about the 3d print files:

"body.stl" is actually 2 separate parts:  the main body, and an attachment piece for the backside that encircles the adjustment knob
"clamp.stl" is the small piece that goes underneath the visor and supports most of the weight.  However, it is only held in place by friction!  So far for me, it's a pretty tight connection,  but i assume with repeated assembly that this will weaken and will fail.
the overall design is not very FDM printer friendly and requires a lot of supports.  (I'm actually working on an variation that will split the piece up into smaller, easier to print parts. But it won't be ready anytime soon.)


feat: add docker test for current protocol(vmess, ss, trojan)

🤔 This is a ...

[x] New feature
[ ] Bug fix
[ ] Performance optimization
[ ] Enhancement feature
[ ] Refactoring
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Workflow
[ ] Other (about what?)

🔗 Related issue link
https://github.com/Watfaq/clash-rs/issues/246
💡 Background and solution

background: currently, there is no verification for the protocol implementations
solution: migrate docker test logic in clash.meta to clash-rs

📝 Changelog
☑ Self-Check before Merge
⚠ Please check all items below before requesting a reviewing. ⚠

[x] Doc is updated/provided or not needed
[x] Changelog is provided or not needed

To Be Discussed

whether we need this test method
should we add some docs or setup codes(to pull the images)
whether we should run ignore the docker test in github actions

we should also setup Docker on the CI runners?

the condition is failing on Windows
   2 |  CLASH_RS_CI=true cargo test --all --all-features
     |  ~~~~~~~~~~~~~~~~
     | The term 'CLASH_RS_CI=true' is not recognized as a name of a cmdlet, function, script file, or executable
     | program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
     | again.
Error: Process completed with exit code 1.

the condition is failing on Windows
   2 |  CLASH_RS_CI=true cargo test --all --all-features
     |  ~~~~~~~~~~~~~~~~
     | The term 'CLASH_RS_CI=true' is not recognized as a name of a cmdlet, function, script file, or executable
     | program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
     | again.
Error: Process completed with exit code 1.

i see...


Add variable for EBS type and size

what
Set a variable for changing default EBS. Please note that because we specify the setting, default values come from this module, not from Elastic BeanStalk (which can be platform specific).
why
Because 8G might be very small is there is lot of logs generated.
reference
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html

Thanks again for the contribution @guikcd!


How to migrate Promisable UIViewController to PromiseKit 6

Hi,
I'm migrating to PromiseKit 6 following the migration guide (very helpful, thanks). But I do not know how to migrate my ViewControllers implementing  the deprecated Promisable protocol. Any hint?
Regards,
Quentin

PromiseKit version: 6

Hi, I'll add this to the guide, I forgot. I removed this from the library because I didn't feel it was a good general solution (as well as a bad pattern due to violating encapsulation) and instead I recommend a custom solution each time. Our common-patterns guide contains this:
class ViewController: UIViewController {

    private let (promise, seal) = Guarantee<…>.pending()  // use Promise if your flow can fail

    func show(in: UIViewController) -> Promise<…> {
        in.show(self, sender: in)
        return promise
    }

    func done() {
        dismiss(animated: true)
        seal.fulfill(…)
    }
}

// use:

ViewController().show(in: self).done {
    //…
}.catch { error in
    //…
}

What do you think?

The custom solution seems good to me. Thanks.
In my case, I will extract show and dismiss in another object (like a Coordinator) in order to remove navigation logic from view controller.
And thanks for PromiseKit, I love this tool. ❤

LMK if you have any new ideas about it that we can supplement our guides with.


[improvement](dynamic partition) Fix dynamic partition no bucket

Problem summary
when dynamic partition no bucket setting, set by distribution
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


fix(supportbundle): update support bundle image pull policy to if not present

ref: https://github.com/longhorn/longhorn/issues/7998
Current image pull policy of support bundle is Always which is not necessary.
Change to IfNotPresent

@mergify backport v1.6.x v1.5.x

Hi @c3y1huang fixed, thanks!
I have tested in my local env, and it is now using IfNotPresent


update golangci config: exclude G107 and G501 issue

Pull Request Test Coverage Report for Build 467930593

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

Totals

Change from base Build 438008200:
0.0%

Covered Lines:
438

Relevant Lines:
497

💛  - Coveralls

Pull Request Test Coverage Report for Build 467930593

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

Totals

Change from base Build 438008200:
0.0%

Covered Lines:
438

Relevant Lines:
497

💛  - Coveralls


Generate more human-readable migration dir names

Seperate Year/Month/Day with - when generating migration directory names, results in the following:
$ diesel migration generate add_table_users

Creating migrations/2017-03-24-061420_add_table_users/up.sql
Creating migrations/2017-03-24-061420_add_table_users/down.sql

Format I went with  YYYY-MM-DD-HHMMSS_migration_name ( my preferred middle ground from #358 )
I haven't created any new-tests, as I'd like to see how others feel about the .replace('-', "") before I do.
I did this so the resulting migrations will still generate the same 'version' slug as the old-ones would. Though im not sure if we care about that at all.

@ggrochow Sorry that this never got reviewed. Are you still interested in working on this? This change looks fine, it'll just need a changelog entry (and a rebase)

I took the liberty of rebasing and adding a CHANGELOG entry. Thanks for your work on this @ggrochow

@Eijebong CI failure seems legit

Thanks, CI seems happy, merging


Add osx build.

Error:  Packages missing in current osx-64 channels:

bob.ap ==2.0.4

bob.db.atnt ==2.0.3

bob.db.base ==2.0.6

bob.db.iris ==2.0.4

bob.db.mnist ==2.0.3

bob.db.verification.utils ==2.0.7

bob.db.wine ==2.0.3

bob.io.audio ==2.0.0

bob.io.image ==2.0.6

bob.io.video ==2.0.6

bob.ip.base ==2.0.9

bob.ip.color ==2.0.4

bob.ip.draw ==2.0.3

bob.ip.facedetect ==2.0.7

bob.ip.gabor ==2.0.5

bob.ip.optflow.hornschunck ==2.0.6

bob.ip.optflow.liu ==2.0.5

bob.learn.activation ==2.0.4

bob.learn.boosting ==2.0.7

bob.learn.em ==2.0.8

bob.learn.libsvm ==2.0.3

bob.learn.linear ==2.0.7

bob.learn.mlp ==2.0.11

bob.measure ==2.1.1

bob.sp ==2.0.4

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Spanish format dropdown list missing element

Describe the bug
There are two empty items in the format dropdown
To Reproduce

In the DOM I can see:

Expected behavior
We should have values or nothing, but no empty line
Additional context
It happens only with ES language.
If I switch in English it is working fine:

'partir' should be 'split' then it will display as a split line, will fix it soon.
In addition, the translation is incomplete, still need some extra work.

Contributing Spanish translations to this project is also appreciated if you need to use the Spanish version.

Sorry but I'm not Spanish speaker - and my only knowledge is on google translate tool :)


Release 2.0?

Seems it is still in RC status.

Just wasn't sure if there was something blocking this or not. Thanks!

Not at all, I thought it had already been released :)


Add ElasticSearch support

BotKube should be able to send events to Elastic search
As of now, we have only Slack as a medium to send events. Since we already have sender interface implemented, it should be very straight forward to add new channels.
Describe the solution you'd like

User should be able to provide ELS credentials in the configuration file
User should be able to configure the events he/she is interested in
BotKube should forward events to the ELS collector if an event occurs

Fixed with https://github.com/infracloudio/botkube/pull/59


HTML entities not being stripped from description

Looks like HTML tags are being removed, but not character entities.

Released v0.2.8


Move client implementations for content store and snapshotter

The client implementations for content store and snapshotters are just proxy implementations of the interface. Move these next to the other implementations. These could be used for any proxy implementation.

Will docker use this for all filesystem? Or only filesystem which containerd doesn't support today?

Will docker use this for all filesystem? Or only filesystem which containerd doesn't support today?

The proposed snapshot proxy would only be used for snapshotters based on Docker graph drivers, which are not supported today.  The proxy drivers could also be used to provided other implementations which all clients could end up using transparently, such as P2P content stores.

@dmcgowan I see. Thanks! I'm just curious whether Docker will partially use containerd image management, and partially use graph driver. Or Docker will still keep using graph drivers for a long time.

I don't quite understand this PR. Why is the logic moved into the proxy package?
Will Docker replace the grpc service? Or the internal interface https://github.com/containerd/containerd/blob/HEAD/snapshots/snapshotter.go#L231:6?

I'm just curious whether Docker will partially use containerd image management, and partially use graph driver. Or Docker will only use graph drivers for a long time.

The goal is to move Docker over in stages, ultimately completely using the image management and only graph drivers to support upgrade or graph drivers which do not have a snapshotter equivalent.

Why the package is called "proxy"?

These implementations of the content store and snapshotter just proxy over GRPC, there is no concrete implementation. I used the term "proxy" here because the caller is not intended to distinguish between using the proxy or directly using a concrete snapshotter.

Codecov Report

Merging #2341 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2341      +/-   ##
==========================================
+ Coverage   44.98%   44.99%   +<.01%
==========================================
  Files          92       92
  Lines        9340     9350      +10
==========================================
+ Hits         4202     4207       +5
- Misses       4459     4461       +2
- Partials      679      682       +3

Flag
Coverage Δ

#linux
49.28% <ø> (ø)
:arrow_up:

#windows
41.25% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

oci/spec.go
28.57% <0%> (-11.43%)
:arrow_down:

metadata/buckets.go
56.79% <0%> (+2.12%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Projected Range : division by zero

Hello,
After having my SOC at 0%, I have an exception in the report "Projected Range".
Now my SOC is > 0%, but I still have this issue, not possible to have my projected range report working.

You completely deleted the bug report template, so now the following information is missing. Please add.
**Environment**

- TeslaMate version:
- Type of installation: Docker or Manual
- OS TeslaMate is installed on:
- User OS & Browser:
- Others:

TeslaMate version: 2021.4.11
Type of installation: Docker
OS TeslaMate is installed on: Synology DSM
User OS & Browser: Windows 10 / Android - Chrome 89

2021.4.11 is not a TeslaMate version :) You can find that information on the TeslaMate settings page. It's just important to know whether you are using the latest version.

Indeed 😁
The version is 1.21.6

PR submitted. I am guessing this was a API issue, but still having the SQL account for this possibility isnt bad.

I get the same error 'db query error: pq: division by zero' on the 'Updates' page.

I get the same error 'db query error: pq: division by zero' on the 'Updates' page. I am using TeslaMate 1.27.2.

PR submitted for Updates page.


landing-page

This is the branch containing the landing page for issue #21

@Festusali I'm not pushing the code to the main branch. I'm pushing it to the 21-build-the-landing-page branch. Check it out, you'll notice I'm pushing it to a branch.


Race condition in node 0.8.x

Hi.
I found a race condition in mock-spawn that affects node 0.8.x users.
Consider the following code:
var mockSpawn = require('mock-spawn')
  , mySpawn = mockSpawn();

mySpawn.setDefault(function(done) {
  this.stdin.on('data', function(chunk) {
    console.log('data:', String(chunk));
  });
  this.stdin.on('end', function() {
    console.log('end!');
    done(0);
  });
});

var proc = mySpawn();

proc.once('close', function(code) {
  console.log('Ended with code', code);
});

proc.stdin.end('Hello world!');

It should print something like
data: Hello world!
end!

But in node 0.8.x data gets emitted before mySpawn handler function is called, so nothing got printed.
This bug can only be reproduced in node 0.8.x, because of a new streaming API that was introduced in node 0.10.x and took care of things like that.

Have you confirmed that this doesn't break behavior on node v0.10.x? Can your add tests for this issue?

@gcochard on the second thought, there is one particular case when calling resume() will break behavior of node 0.10.x streams.
I'll close my PR and create an issue instead.


New VS 2019 installation , selected all the components. Failed to train a model.

System Information (please complete the following information):

Model Builder or CLI Version:
Visual Studio Version (if applicable):

Describe the bug
Not able to train the model. Missing Path/Python configuration ?
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Followed the steps at:
https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/train

@xzenin Sorry you ran into this problem and thanks for reporting. Can you try training longer? Does it still fail at 60 seconds?

Any luck with a longer training time?

Closing this due to inactivity - ping me or reopen if you need additional help!


Fix IRQ enabled in serial_irq_set()

This is resolution of #1586
UART_IT_TC was enabled instead of UART_IT_TXE
This was causing an issue because UART_IT_TXE (and not UART_IT_TC) was disabled  by same function.
Consequently if a transfer was ongoing when serial_irq_set() was called to disable IRQ, UART_IT_TC would still trigger (once).
Side effect is maybe speed: I guess using UART_IT_TC prevented implementation of continuous transfer.
This commit is focused on solving an issue observed with TARGET_STM32F4. It doesn't presume it should or shouldn't be done for other targets.

@bcostm @adustm

@arnaudrichard Please sign https://developer.mbed.org/contributor_agreement/

Done.
From: Martin Kojtal<EMAIL_ADDRESS>Sent: jeudi 10 mars 2016 16:15
To: mbedmicro/mbed
Cc: Arnaud RICHARD
Subject: Re: [mbed] Fix IRQ enabled in serial_irq_set() (#1603)
@arnaudrichardhttps://github.com/arnaudrichard Please sign https://developer.mbed.org/contributor_agreement/
—
Reply to this email directly or view it on GitHubhttps://github.com/mbedmicro/mbed/pull/1603#issuecomment-194898342.

What about the line 95, does your patch affects that line:
__HAL_UART_DISABLE_IT(handle, UART_IT_TC|UART_IT_TXE);

cc @bcostm

__HAL_UART_DISABLE_IT(handle, UART_IT_TC|UART_IT_TXE);
looks good to me and should not be affected by my patch.
cc @bcostmhttps://github.com/bcostm
From: Martin Kojtal<EMAIL_ADDRESS>Sent: lundi 14 mars 2016 17:24
To: mbedmicro/mbed
Cc: Arnaud RICHARD
Subject: Re: [mbed] Fix IRQ enabled in serial_irq_set() (#1603)
What about the line 95, does your patch affects that line:
__HAL_UART_DISABLE_IT(handle, UART_IT_TC|UART_IT_TXE);
cc @bcostmhttps://github.com/bcostm
—
Reply to this email directly or view it on GitHubhttps://github.com/mbedmicro/mbed/pull/1603#issuecomment-196395845.


[WIP] AEROGEAR-2453 Implement storage and credential managers for iOS

Motivation
JIRA: https://issues.jboss.org/browse/AEROGEAR-2453
Description
Implement the storage and credential managers for iOS.
Progress

[x] Implementation
[x] Unit tests for managers
[x] Move iOS unit tests
[x] Documentation

@wei-lee I can't find any hard limit from a quick search. Looks to be limited more by NSString which is very large. I'll do a more thorough search though to make sure.

@aidenkeating it's ok. I think it's good for our use case. But based on the actual implementation, should we rename the class to SecureKeyValueStore to make it more clear? Just a thought...

@wojta Mind taking a look?

@ziccardi Mind taking a look?

@wei-lee Mind taking a look?


🟢 French Translation NEEDED for Documentation

French translation is needed for the following files:

[ ] README
[ ]  CODE_OF_CONDUCT
[ ]  CONTRIBUTION-GUIDELINES.md
[ ]  LICENSE
[ ] about.md

Please add these files in the empty French section.
And please work off the branch french-translation for organization purposes.
Modeling after the GitHub Repository first-contributors

Hi @lucasfirmo62!
Of course! THank you for reaching out, and I will go ahead and assign this issue to you! Have a great day!


Resolve Network.Fetch.{Things,Actions}

Thanks, let me know if you get stuck here @etiennedi and @laura-ham.

This finding might be another argument pro "every peer uses their own contextionary", as it would reduce the overall complexity: https://github.com/creativesoftwarefdn/weaviate/issues/618#issuecomment-460626928. However, it's not a very strong argument, so if we find a strong argument against this distributed approach it might still tip the scales.

Oef, this is a difficult thing. Currently, I communicate that Weaviate networks should have a similar contextionary.

@bobvanluijt I meant, each peer should use the local contextionary to run the queries/searches against (rather than the querying peer running the searches for all peers). This still assumes all contextionaries are more or less in sync.


[BUG] Renaming a file keeps the old file and creates another file with a new name

Please confirm

[ ] I am running the latest version of this plugin

Describe the bug
When I rename file I get an error and have 2 files: old and new with new name

To Reproduce
Steps to reproduce the behavior:

Start nvim
Try to rename file
Get an error and two files width old name and new name

E5108: Error executing lua ...cal/share/nvimvimplug/telekasten.nvim/lua/telekasten.lua:
1652: Vim(bdelete):E94: No matching buffer for Fromm.md
stack traceback:
        [C]: in function 'cmd'
        ...cal/share/nvimvimplug/telekasten.nvim/lua/telekasten.lua:1652: in function '
rename_note'
        [string ":lua"]:1: in main chunk

Expected behavior
A clear and concise description of what you expected to happen.
Operating system (please complete the following information):

OS: Fedora 35

Additional context
Add any other context about the problem here.

Just made some tests. It looks like the issue is with filenames with a space in it. Don't do that :smile:
Fixing that now...

Closed by https://github.com/renerocksai/telekasten.nvim/commit/7f5b625e4ffc5dea570835396a02e775e59ff0e2

Thanks

Just made some tests. It looks like the issue is with filenames with a space in it. Don't do that 😄
Fixing that now...

It is common for file paths to contain spaces in macOS.


Feature/robust optimization

implementation of the orbital transformation method (10.1063/1.1543154) in Python.
small changes / bug fixes in cpp code:
Local_operator::apply, avoid overwriting other ispn with zeros
avoid illegal memory access in pp/exact diagonalization (results are still wrong)
omit Field4D::allocate in pp case
make UPF converter scripts more robust (omit size checks if length field in UPF file is missing)
warn about negative densities only if above threshold of 1e-9

@simonpintarelli any clue why this check still hangs?

@toxa81 the jenkins builds are currently offline because of the upgrade on daint

Ah!


pwa docker build is printing ngcc_lock_file warning

Actual Behavior
Start docker build wait and look for Step 19/34 : RUN npm run build:multi client. This will start the build tooling in parallel processes. Unfortunately you'll see a message like this from Angular CC
Another process, with id 116, is currently running ngcc.
Waiting up to 250s for it to finish.
(If you are sure no ngcc process is running then you should delete the lock-file at<EMAIL_ADDRESS>
Expected Behavior
Ideally no such waiting is necessary during the build process. See below for technical investigation note.
Steps to Reproduce the Bug
Steps to reproduce the behavior:

Go to project root
Execute docker-compose build pwa

Technical investigation
The reason for this is falling into angular build tooling that tries to find dependent packages that needs build processing. Since we're starting scripts to run in parallel (depending on cpu-core count) on the same filesystem state we share that state over the different processes. Consequently angular-cli will try to build the same node module. One process will succeed to acquire the log. Others will issue the warning and will wait for the condition to pass.
See: https://github.com/angular/angular/issues/35000
AB#65749

As a workaround it is possible to run npm run build client --configuration=default,production -- --output-path=dist/default/browser --progress=false to prepare the node_modules folder state for all following parallel builds


#162 - Added query repository to config

issue #162

Hi @albamig, I changed the destination branch to point to the 0.5.2 release 😉


Constant tensor with more than one dimension

Hi, been hitting into this error quite frequently. Have this error when I declare a new Tensor and pass it into a torch function.
local d = require 'autograd'
d.optimize(true)

local lossf = d.nn.ClassNLLCriterion()
local f = function(params, y)
  local yhat = torch.Tensor(2, 400003):uniform(-0.1,0.1)

  -- also, if you uncomment this block, the autograd will print out the entire tensor :\
  -- local t = {
  --   torch.Tensor(400003):double():uniform(-0.1, 0.1),
  --   torch.Tensor(400003):double():uniform(-0.1, 0.1)
  -- }
  -- yhat = torch.cat(t,1)

  local loss = lossf(yhat, y)
  return loss
end

local df = d(f)
local y = torch.Tensor({9516,400003})
local params = {}

df(params, y)

/torch/install/bin/luajit: .../install/share/lua/5.1/autograd/runtime/codegen/Node.lua:25: constant tensor with more than one dimension. is this an upvalue that should be a function argument?
stack traceback:
	[C]: in function 'error'
	.../install/share/lua/5.1/autograd/runtime/codegen/Node.lua:25: in function 'init'
	.../install/share/lua/5.1/autograd/runtime/codegen/Node.lua:10: in function 'new'
	...install/share/lua/5.1/autograd/runtime/codegen/Graph.lua:19: in function 'lossf'
	train.lua:154: in function 'fn'
	...install/share/lua/5.1/autograd/runtime/codegen/Graph.lua:281: in function 'protectedFn'
	...install/share/lua/5.1/autograd/runtime/codegen/Graph.lua:309: in function 'record'
	.../install/share/lua/5.1/autograd/runtime/codegen/init.lua:44: in function 'generateFn'
	.../install/share/lua/5.1/autograd/runtime/codegen/init.lua:66: in function 'df'
	train.lua:161: in main chunk
	[C]: in function 'dofile'
	...gfei/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
	[C]: at 0x00406670

I use switched to code below and it is working fine now.
If this is expected, then this issue is solved. :)
torch.uniform(torch.zero(params.w.new(2, 400003)))

I've run into this a bunch, too. I believe it is because codegen is unwilling to tape-ify a constant tensor (i.e. upgrade it to a Value to that it can flow along the AD computation). I'm not sure if that is by design or just something that hasn't gotten cleaned up yet.
A work-around is to pass the constant tensor into the target function as an argument. So for your above code something like:
local yhat = torch.Tensor(2, 400003):uniform(-0.1,0.1)
local f = function(params, y,yhat)
  ...

However, it's pretty annoying to have to do this all the time. It would be great if either constant tensors could be upgraded automatically, or if a Constant() util could be provided to do this by hand.
(Note that this error doesn't happen in non-optimizing mode. It's slightly disconcerting that one errors on constant tensors and the other doesn't blink!)

Yeah, we should be throwing much better errors here.
Also (and we should be throwing errors for this, too), we don't support any calls to self inside an autograd'd function. So stuff like myTensor:view(10,10) is invalid, and instead you should use torch.view(myTensor,10,10).
I'm not sure if we have a call to torch.uniform() added, though.

So the root issue is that the operation:
local yhat = torch.Tensor(2, 400003):uniform(-0.1,0.1)

Isn't tracked by autograd, so we have no idea where that tensor came from, and assumes it's some upvalue constant. Since the optimized mode is producing standalone lua code for your function, any constants have to become literals in the code. This isn't really practical for large tensors, so I limit it to smaller 1D tensors.
(the fix you made is the right thing to do)


Error Trigger postgresql ce.4.1.2

i  can't show trigger function on postgresql with ce v4.1.2
but version 4.1.1 is okey

This is probably the same as #1987

okey thanks


Geoparsing for uploaded file

Server should start the Geoparsing process as soon as file/s being uploaded to server and send the status back to front-end.

app.js it now taking care of this.
It starts geoprocesing as soon as any file uploaded.


github/CI: Restrict merge if not passing lint

Added the 4 linters to be required for merge cc @renaynay


feat(ontology): new cardinality workflow (DSP-1652)

resolves DSP-1652 and DSP-1656
This PR contains the new workflow to create resource class and to add properties. It means: the user creates first a resource class. Then s/he has to go to this resource class and add  the properties one by one. The GUI order can be changed at any time. It's the first iteration that helps to create new resource classes and to add properties incl. the cardinality. The update of a cardinality of existing properties in a resource class will be part of the next iteration.
I had to clean up some old (or now outdated) components:

There's no need anymore for a resource-class-form.service and the resourceClassFormSub because we have separated the cardinality from the resource-class. But I moved some of the general methods to handle the data in the ontology editor from this service to a new service called ontology.service.
The old component resource-class-property-form.component is not needed anymore, because we can use the property-form.component to handle the cardinality.

This is how it works at the moment:
Uploading Screen Recording 2021-06-04 at 11.07.44.mov…

I tried to test the functionality but my properties are not updating correctly in the resource class and for every action it gives me Bad request(400) error.
am I doing something wrong here?

As mentioned already in one of the meetings, it doesn't work with the test data like the anything ontology. Because this ontology is already in use. It means that the properties have already data in it. You have to start from scratch and create your own example ontology.

For me, it works but I have to refresh the page to see any changes I've made. However the response has the correct data I believe. I was trying to add a Date of Birth (DOB) property to my class. I'm using DSP-API v13.9.2 and there are no console errors 🤔

For me, it works but I have to refresh the page to see any changes I've made. However the response has the correct data I believe. I was trying to add a Date of Birth (DOB) property to my class. I'm using DSP-API v13.9.2 and there are no console errors 🤔

It reloads the view when I connect to the API on the test-server (v13.9.1), but not when using the local instance (v13.9.2). It has nothing to do with the API version, but maybe with an async time issue and for sure with the closeDialog.emit() command in the property-form.component.ts. It runs twice (s. my comment here). I'll fix it...


WebView PHPSESSID cookie not working correctly on iOS

Hello, my application has a shared session between the app and page in WebView through the PHPSESSID cookie. In the app, I retrieve an access token, that has value for this cookie encoded in it. I use react-native-cookie package for managing this cookie.
After I set the cookie and load the WebView, on the initial page load the session is still not working, but after I redirect it starts working correctly. Do you have any idea, what can be the problem?
Also, it works when I hard-code a WebView reload after 500ms after load, but it is not a good solution.
I tried combining it with the headers attribute in source prop, where I also passed the PHPSESSID in the Cookie header and it works even strangely. The session is there after the initial page load, but after I redirect it doesn't work and after I redirect again, it works again :D
Any suggestions are welcome.
I call this method after retrieving the access token after app startup if the user is already logged in or after login.
export async function setSessionCookie(token: AccessToken): Promise<Cookie | undefined> {
  const cookie = getCookieFromToken(token)
  if (cookie) {
    const country = getStoredCountry()
    const url = getStoreURL(country)
    await CookieManager.set(
      url,
      {
        name: 'PHPSESSID',
        value: cookie.sub
      },
      useWebKit
    )
    const cookies = await CookieManager.get(url, useWebKit)
    return cookies.PHPSESSID
  }

  return undefined
}

Then this is the webview.
const Example = ({source}: Props) => {
  const [isReady, setIsReady] = useState(false)
  const [currentURI, setCurrentURI] = useState(source.uri)
  const [cookieHeader, setCookieHeader] = useState('')
  const webViewRef = useRef<WebView>(null)
  const newSource = {
    ...source,
    uri: currentURI,
    headers: {
      Cookie: cookieHeader
    }
  }

  useFocusEffect(
    useCallback(() => {
      const getCookieHeader = async () => {
        const token = getUserAccessToken()
        if (token) {
          const cookie = await setSessionCookie(token)
          const cookiesString = cookie ? `${cookie.name}=${cookie.value}` : ''
          setCookieHeader(cookiesString)
        }
        setIsReady(true)
      }
      getCookieHeader()
      webViewRef?.current?.reload()
      return () => {
        setIsReady(false)
      }
    }, [])
  )

  if (!isReady) {
    return false
  }

  return (
    <Browser
      ref={webViewRef}
      source={newSource}
      applicationNameForUserAgent={APPLICATION_NAME}
      allowsBackForwardNavigationGestures
      sharedCookiesEnabled
      pullToRefreshEnabled
      textZoom={100}
      decelerationRate="normal"
      scalesPageToFit={false}
      setBuiltInZoomControls={false}
      autoManageStatusBarEnabled={false}
      {...otherProps}
    />
  )
}

Environment:

OS: iOS
OS version: 17.1.2
react-native version: 0.71.8
react-native-webview version: 13.6.8

i  met the same problem , how do you resolved it ?  thanks your help


Revert SP and SQL to old VM sizes

Since today, all Edsv4-series VMs fail to start in region "East US", which impacts SharePoint template since it's used for SP and SQL VMs.
So I revert SP and SQL to their old VM size as a workaround.

This PR only intends to fix an issue with availability Edsv4-series VMs in "East US" (that surfaced just today).
My guess is that it's pure bad luck that we face this problem, and it's totally unrelated to other issues in the past few weeks.
I prefer to revert to old sizes until Edsv4-series works again, as internally we use "East US" region a lot.


Update gpo.py to support latin-1

Small pull request because the utf-8 charset doesn't support french accents (which raises the UnicodeDecodeError).
Adding the try: except decode("latin-1) fixes the bug. :)

Thank you @Dfte!