deploying custom maintenance pages in arabic shows question marks live

Description
I have defined custom maintenance pages for 40x and 50x errors. Currently the html for both has arabic text. Locally through vsCode, I can see the text correctly. Also pasting the html code to the browser does display everything just fine. Except when deploying live, all arabic characters get turned into question marks.
Steps to reproduce
files:
  "/usr/share/nginx/html/40x.html" :
    mode: "000755"
    owner: nginx
    group: nginx
    content: |
        <!DOCTYPE html>

                        <title>الموقع في حالة صيانة</title>
                        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
                        <meta name="viewport" content="width=device-width, initial-scale=1" />

لم نتمكن من العثور على تلك الصفحة.

الصفحة التي تبحث عنها بعيدة عن متناولنا

Observed result
deployment works fine. But the produced html files are faulty.
Expected result
I should see the same text I see on vsCode, but live.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS: Ubuntu 18.04
EBCLI version: 3.19.4 (Python 3.6.9)

Hi @omar-dulaimi  thanks for reaching out. Unfortunately I can’t reproduce this bug. I wrote a simple flask application and used the html you provide as a static file. I deployed it to EB and it works well. And you can see this link http://flask-env.eba-cgzckkmb.us-west-2.elasticbeanstalk.com/static/404.html It seems the character is correctly displayed.
Based on the information you provide, I couldn’t determine whether error happens in S3 bucket upload( if you don’t use git), or error happens in S3 download to instance, or instance itself doesn’t have the charset. Could you ssh into the instance, copy the 40x.html on the instance and see if it’s any difference compare to original html file?

Hello @Mickeypeng
Our error pages aren't separate static files ready to deploy .They're defined in .ebextensions directory, as one of the files ending in .config
That .config file had all the code necessary to generate the pages. (above code)

Hi @omar-dulaimi  , @Mickeypeng's suggestion is working for me and i am able to see the characters displayed properly , could you please provide more info / steps to reproduce .


Understand and document the high-level requirements of Nucleus

Gather the high-level requirements of Nucleus, understand the high-level requirements and document them.

Created the following wiki page to document the questions and answers on Nucleus requirements
https://github.com/NASA-PDS/nucleus/wiki/Nucleus-Requirements-:-Questions-and-Answers

🕐 started to captured requirements in a word doc

Documented Nucleus high level requirements in a Google doc and reviewed the requirements with @jordanpadams and @tloubrieu-jpl .
Currently incorporating the  the review comments and preparing a document to be added in GitHub.

Created a markdown requirement document at https://github.com/NASA-PDS/nucleus/blob/nucleus_3_high_level_requirements/docs/requirements/REQUIREMENTS.md and made a pull request (https://github.com/NASA-PDS/nucleus/pull/9)


[Enhancement] Support Fooocus metadata

Describe the bug
Metadata in PNG is not read. The png does not even appear in Diffusion Tookit.
Version:
1.5.1
Tool:
Latest Fooocus including this pull request that adds metadata. I used Automatic1111 style. https://github.com/lllyasviel/Fooocus/pull/1940
To Reproduce
See attached test file. Opening the png in text editor shows metadata. But the image does not even get added to Diffusion Toolkit

Expected behavior
Import the images and show metadata
Affected Image(s)
Happens with all images done with Fooocus and added metadata

Not strictly a bug. I don't support Fooocus yet since this is a new Fooocus feature. :)
Thanks for the image.

 Sorry not a bug
The author of the pull just says it's 99% compatible with Automatic1111 so I thought this is kind of a standard and it should work. Anyway. Let's see if Fooocus will add this feature.

@RupertAvery thank you for the hint, much appreciated!
In https://github.com/lllyasviel/Fooocus/pull/1940/files#diff-86573ae9c883b11ca74722fe0a397713d42b916269a24b596076b631223248bdR31 "Comments" is used but i'll change this to "parameters". I assume this would be sufficient.
Civitai could read all of the data and the params are the same, so i think this is the last step to make it truly compatible. Would you agree?
@Eleksar387 i'll adjust the code, thanks again for reporting and your analysis!

Can you put an identifier in another tag to identify it as Fooocus?  Just in case A1111 or Fooocus diverges metadata implementation, it makes it easier to manage things,

What seems to be the issue?
It reads fine in the latest version

The model root was (still is) not correctly set for me, did always show "not found", but hash information is present.

For ReadRuinedFooocusParameters, that is in JSON format. Do you store both or just one?

Just one, configurable with radio buttons. There are quite a few parameters, 32 + optional 5x3 (for LoRA) => 47 in total, so it's quite much to map but i'll merge prompts in one attribute with resolved wildcards and style params.
This issue can be closed, i'd open a new one or directly implement mapping in a PR when Fooocus is ready.
Thank you for your support!

You guys rock! Thx @mashb1t and @RupertAvery for your efforts!
I now see the images in Diffusion Toolkit including the metadata. 🤩

Implementation of https://github.com/lllyasviel/Fooocus/pull/1940 has completed, will update you guys again when it has been merged.

@RupertAvery i've just released the mentioned metadata feature in Fooocus v2.2.0, see meta_parser.py.
Your suggestion to add a key on root level has been included and the different schemes ("fooocus" / "a1111") can now be differentiated by the key metadata_scheme.
The Fooocus scheme features an array syntax, while A1111 is the well-known schema with concatenated strings and comma separation.
Example images

Fooocus (can be png with pnginfo, but also jpg and webp with EXIF data):

PNG

JPG (not really relevant in this repository i assume)

A1111

PNG

It would be great if you could (help to) add the new schema to this repository.
Thank you very much!

Latest commits have implemented readers for Fooocus metadata

@RupertAvery thank you for the implementation, much appreciated!
@Eleksar387 please check if this works for you and close the issue if solved. Thanks!


add conditions to avoid zero division

Before you submit this PR: make sure to put all operations-related information in a wiki-note, a PR should be about code and is publicly accessible
What is the problem / what does the code in this PR do
Encountered zero division during desaturation
Can you briefly describe how it works?
The min_reference_length should be checking on the number of samples exceeding 1 PE with the reference region. And both the saturated pulse and the summed wf model should be checked.

Looks good, thanks Tianyu


Bottom tabs bar only partly visible after device orientation change when PWA is started from homescreen

Bug Report
Ionic version:

[x] 4.x
Current behavior:
On iOS only:
Tabs bar is only partly visible after changing device orientation to landscape and back to portrait, when PWA was started from homescreen. This works flawlessly when using the PWA in Safari, but not when started from homescreen.
This does not seem to be a problem on Android.
Expected behavior:
Tabs bar is fully visible even after changing orientation to landscape and back to portait.
Steps to reproduce:

ionic start example tabs --type=ionic-angular
cd example; ng add @angular/pwa; ionic build --prod
deploy to server
open app in safari
add to homescreen
rotate device to landscape
rotate device back to portait
tabs bar is only partly visible

Ionic info:

Ionic:

   ionic (Ionic CLI)             : 4.10.3 (C:\Users\jbollacke\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework               : @ionic/angular 4.0.2
   @angular-devkit/build-angular : 0.12.4
   @angular-devkit/schematics    : 7.2.4
   @angular/cli                  : 7.2.4
   @ionic/angular-toolkit        : 1.4.0

System:

   NodeJS : v8.10.0 (C:\Program Files\nodejs\node.exe)
   npm    : 6.8.0
   OS     : Windows 7

After further investigation I think this behaviour is caused by viewport-fit=cover of viewport-meta tag.

I am having the exact same issue.  And like @jbollacke think it goes back to viewport-fit=cover.  When I removed it from the viewport metatag, the behavior was fixed.  Are there any disadvantages to removing viewport-fit=cover?

eu estou com o mesmo problema, aparece uma barra branca quando eu mudo pra landscape e volto pra portrait

This is easily replicable - ionic start myApp tabs. Running on iOS - change orientation to landscape then back to portrait and the tabs at the bottom are partially obscured.
Removing viewport-fit=cover in index.html has no effect.


Change CI provisioning

Sphinx unpinned. lxml pinned as <5 rather than a specific version.
Experimentally, add two workflows: Ubuntu 24.04 and Windows 2022

For the Windows workflow run, test test\MSVC\msvc.py fails due to the precompiled headers speed test.
In #4534, I removed the multiplier (i.e., effectively 1.0):
  # TODO: Reevaluate if having this part of the test makes sense any longer
  # using precompiled headers should be faster
- limit = slow*0.90
+ limit = slow
  if fast >= limit:
      print("Using precompiled headers was not fast enough:")
      print("slow.obj:  %.3fs" % slow)

In hindsight, it probably should have been changed to slow*1.0 (or even marginally larger than 1).
This test fails frequently for me when running tests in virtual machines.  Even with the change, it still occasionally fails in one vm (i.e., pre-compiled headers slower).

There are some mysterious fails due to adding the Windows runner, I guess I should have listed them here.
Failed the following 39 tests:
    test\CPPDEFINES\pkg-config.py
    test\Interactive\added-include.py and 25 others (of 28 Interactive total)
    test\MSVC\msvc.py
    test\packaging\msi\explicit-target.py
    test\packaging\msi\file-placement.py
    test\packaging\msi\package.py
    test\packaging\tar\xz_packaging.py
    test\scons-time\run\config\python.py
    test\scons-time\run\option\python.py
    test\scons-time\run\option\quiet.py
    test\scons-time\run\option\verbose.py
    test\sconsign\script\no-SConsignFile.py
    test\sconsign\script\SConsignFile.py
    test\sconsign\script\Signatures.py
    ```
Many of these are mystifying.  The `sconsign` tests fail because the third field of entries for files is `-1`, which doesn't match the regex expressions `\d+`.  But why is it getting -1?

The `scons-time` test - the `python.py` ones fail by missing the "command echo" from the files, the other two fail because we get back a path that's gone through 8+3 shortening, like: ```
< 'SConstruct file directory: C:\\\\Users\\\\runneradmin\\\\AppData\\\\Local\\\\Temp\\\\scons\\-time\\-[^\\\\]*\\\\foo'
---
> 'SConstruct file directory: C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\scons-time-pim4q763\\foo'

The packaging tests fail with an error I've never seen, ```
scons: *** Missing Packagetag 'X_MSI_LANGUAGE' for SCons.Tool.packaging.msi packager
... even though the packaging tool itself sets that.

The pkg-config test fails because `perl` is not found, but it's also not used !?!?!?  And don't know where it found that path for `pkg-config`, it should be unable to look in such a weird path.

STDERR =========================================================================
'perl' is not recognized as an internal or external command,
operable program or batch file.
OSError: ' "C:/Strawberry/perl/bin/pkg-config.BAT" --cflags bug.pc' exited 9009:

There are a few others.  Not able to spend time chasing these down at the moment.

On windows, when using the default pathext argument(i.e., pathext=None) for the where_is function invocation, all path extensions are tested with the basename. It appears that the Strawberry Perl bin folder contains a pkg-config.BAT which must be on the system path.
I could be wrong...

Unlikely to be wrong.  Yes, the tests are sometimes more ambitious than SCons is going to be with its limited PATH in the execution environment.  I still don't know why perl gets involved.
I've pushed a change to this PR which skips the 39 tests that failed last time, which has gotten us a "pass" this time. I'll record those in an issue and we can whack those off (and reduce the skip list) as motivation appears - no rush, really.

The following could be wrong...

I still don't know why perl gets involved.

The where-is call is returning the fully qualified path to the Strawberry Perl batch file pkg-config.bat.  The Strawberry Perl batch file pkg-config.bat calls perl.
pkg-config.bat:
@rem = '--*-Perl-*--
@set "ErrorLevel="
@if "%OS%" == "Windows_NT" @goto WinNT
@perl -x -S "%0" %1 %2 %3 %4 %5 %6 %7 %8 %9
@set ErrorLevel=%ErrorLevel%
@goto endofperl
:WinNT
@perl -x -S %0 %*
@set ErrorLevel=%ErrorLevel%
@if NOT "%COMSPEC%" == "%SystemRoot%\system32\cmd.exe" @goto endofperl
@if %ErrorLevel% == 9009 @echo You do not have Perl in your PATH.
@goto endofperl
@rem ';
#!/usr/bin/perl
#line 16
...

If the fully-qualified pkg-config.bat call is made in a restricted SCons environment, perl won't be on the path.

Never heard of Strawberry Perl, so I didn't realize it was a "thing", just thought the CI image had some weird paths. But it is a Thing indeed... http://www.strawberryperl.com/.
So yeah, we found something in the more liberal test framework search, and then the necessary path wasn't in env['ENV']['PATH'] when scons fired off the test. Not entirely sure how to fix that, but there will be a way...

Problems found with this runner moved to #4539


VnV Review #4 - T1

For the I/O of the test, it would be useful to provide the actual list of inputs and their associated outputs, so that someone can implement the test.

Addressed by commit d9c9f35


Package Diff implementation

Fixes #21

Function receives name of package to analyse for changes, and outputs whether the package has changed (true or false).

Performs a diff between HEAD and the latest build tag, in the format _v<IP_ADDRESS>

Files matching rules in .forceignore are not included as part of the check

Added package diff task to CLI

CreateUnlockedPackage has a major version update in the next milestone. So lets stick to it. However CreateSourcePackage Task needs to be updated. Also can we move the git tag function to common, with a split of the git url finder to a seperate function.


Add prompt geertjohan

I would like to add my custom prompt as option in prezto.

This is my custom prompt. It uses three lines to display some information.

The first line shows the previous program's exit status, including exit code when not zero. The first line also displays the time it took for the process to run when > 1 second (currently not displaying miliseconds).
The second line displays the current working directory path, using a short notation (first character for each folder in the path, except current folder). The second line also displays git information when in a git repository.
The last line is the prompt input line, as usual.

If you do not intend to modify it further, it can be merged into Prezto provided it matches the coding style. If you intend to modify it frequently, keep it as an external module and from time to time, it will be updated in Prezto.
Themes require several votes from the community to be included.

Thanks @sorin-ionescu
I do intend to modify it now and then, the repo is also open for issues/PR's.
This theme was originally created about 6 months ago, I think. Just polished the source a bit and uploaded this version now. I intend to make the theme a bit more configurable for anyone without zsh/shell knowledge. One thing I have planned to add is to modify the number of characters that are shown for each folder in the path. So when set to 3, the example would show ~/src/git/Gee/prezto_prompt_geertjohan.
I hope you like the theme. I've chosen for three lines to be able to display more information while in narrow terminals (which I tend to have a lot). I like to use the first two lines to separate the information about the previous command from the current environment information.

If users want your theme in Prezto, they'll vote for it in these comments to this pull request.
I require votes to prevent the Wild, Wild, West nature of Oh-My-Zsh from infecting Prezto. I want code in Prezto, in this case a prompt theme, to be used by many, not just by the original author, and prompt themes are often personal.
I'll provide feedback on your theme after I play with it.

Thanks!
I really agree with you on preventing a huge amount of theme's flooding the project. Of course I believe my theme is distinct enough to be added, otherwise I wouldn't have opened a PR. If it was a lot like an existing theme then anyone could've used the existing one and modify to personal preference. I think my theme is a different enough and provides new features.

:+1:

+1


Environment detection by the wrapper failed (once)

I used the AppImage on an Live USB with Ubuntu 18.04 and Xorg, but was notified on the first launch that I was not using Xorg. The error said something along those lines:
Your environnement is not Xorg but is identified as
Note that no environment was detailed at the end of the sentence, probably simply because the wrapper failed to detect my environment, and hence threw the error in the first place.
The error was gone after running the application another time, and it ran correctly, so I'm not sure what caused the issue. The screenshot also gives additional details about the machine and drivers I used, if relevant for troubleshooting.

Got the same error today, for me the problem was that I had launched the program in a terminal logged as root.
Logging back to my normal user make it work fine.
I suspect some missing variables into the env for some users (as the one who have no home like root) to be the cause of the error.

Thanks !
Yes you should not start the script as root because Shadow is designed to use a regular user and store everything in his folder. I will probably change the wrapper to stop if the AppImage is started with root rights.

I don't have any Live USB at hand here, sorry.
You make a good point about the memory being flushed or not, I'm not sure actually. This would need some testing.


{Role} Secure _create_self_signed_cert

Context
When creating a self-signed certificate in commands such as az ad sp create-for-rbac or az ad app credential reset:

Create a temp_file and use its name for creds_file.
The certificate and private key are saved to cert_file and key_file.
The contents of cert_file and key_file are read back and combined into creds_file.
Change the mode of creds_file to 0o600 (rw-------).

This procedure exposes problems:
Problem 1: temp_file is not deleted
According to https://docs.python.org/3/library/tempfile.html#tempfile.mkstemp:

Unlike TemporaryFile(), the user of mkstemp() is responsible for deleting the temporary file when done with it.

Solution: Use NamedTemporaryFile which automatically deletes the temp file.
Problem 2: cert_file and key_file are not deleted
The "write to file and read it back" logic was introduced by https://github.com/Azure/azure-cli/pull/2457. The reason behind it is unknown. At least, they are secure with permission 0o600:
$ ls -ld /tmp/tmp*
-rw------- 1 user1 user1    0 Mar 21 15:37 /tmp/tmp7v82yx_y
-rw------- 1 user1 user1 1704 Mar 21 18:57 /tmp/tmpavuictrh
-rw------- 1 user1 user1  973 Mar 21 18:57 /tmp/tmphv9npp_n

Solution: Only keep certificate and key values in memory as variables. Do not write them to files.
Problem 3: Time gap between creds_file's open and chmod
There is a time gap between creds_file's open and chmod, during which its permission is 0o755 (rwxr-xr-x) meaning other users can read its content.
Solution: Create creds_file with the right mode, instead of changing it later. ADAL-based Azure CLI uses this approach for creating accessTokens.json:
https://github.com/Azure/azure-cli/blob/14cc787d0f58bc649d402b486fdecc5625eee9ac/src/azure-cli-core/azure/cli/core/_profile.py#L1100-L1101
msal-extensions made the same change in https://github.com/AzureAD/microsoft-authentication-extensions-for-python/pull/107.
References

https://stackoverflow.com/questions/5624359/write-file-with-specific-permissions-in-python
https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use
MSRC 70882

Role improvement


Update URL for Seedy-Threepio.Theseus2000 version 3.2

From latest URL Scan:

https://www.seedy.gq/programs/theseus/Theseus2000_Installer.exe for Seedy-Threepio.Theseus2000 version 3.2 redirects to https://t2000.seedy.gq/Theseus2000_Installer.exe

Microsoft Reviewers: Open in CodeFlow

It look like the Azure Pipelines logged the hashes didn't match.

@Trenly It look like the Azure Pipelines logged the hashes didn't match.

Yes, that's what the "Error-Hash-Mismatch" label means

It look like you actually deleting from the master.

Yes, because version 3.6 already exists in master


Create a test framework

Clear and concise description of the problem
A clear and concise, yet simple way of writing & maintaining test suites.
Suggested solution

[ ] unit test support
[ ] e2e test support (playwright or vitest?)
[ ] auth helpers
[ ] API helpers

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate

https://github.com/stacksjs/stacks/issues/338


Bug in ResourceUpdate::SetNextQueueTechOnTop

I don't know if this project is still maintained, but I'll leave this issue for people who wants to use it. Just to they be aware of this little bug.
The bug
There's a bug in includes/classes/class.PlanetRessUpdate.php while updating research. Exactly in SetNextQueueTechOnTop method. It is using resources before any resource update. So it checks if you have enough resources on planet to research based on old planet state.
Example
You got 10000 metal, produce 7000/h. You plan 3 research tasks, each take 1h and each costs 7000 metal. So they all should be done, because each takes 1h to do and 7000 metal and you produce 7000 metal per hour. But only one will be done. After setting first, you had 3000 metal. And this 3000 metal will be used to check if you have enough resources in SetNextQueueTechOnTop.
One more thing...
To solve this problem you can't simply add this->UpdateResources(time), because this will update resources twice in some cases. You have to change a little bit how ResourceUpdate class works or deal with this bug 😄 Maybe I will write solution to this one day 🔧
PS: Sorry for my english, I am trying my best ^^

good, interesting what you say, finally you gave with the solution would be kind to share


Update index.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Yes, thanks @scjane 👍


Edge-case support: Treat hook as sync even when last arg is not passed

@creynders, I'm not sure if you're willing to support this, but I ran into a weird edge-case. This is the scenario:
var instance = {
  // "method" is SYNC, "fn" is NOT a callback
  method: function(fn) { // <-- grappling assumes this is ASYNC when arg not passed
    if('function' === typeof fn) {
       ... do something with fn
    }
  }
}

grappling.mixin(instance)
  .addHooks('method')
  .pre('method', function() {
    ... do something
  });

instance.method();

Since the fn is not passed to instance.method() last parameter (fn) is a function grappling assumes .method() is async., when in this particular case it's not.
Would you be willing to support this edge-case? Maybe with an .addHooksSync() method or something similar ...

Hmmm, weird, if I understand your use case and I'm not mistaken, this should work. Obviously if it doesn't it's bug. But grappling does NOT assume that if the last parameter is a function it's async by default, only if the middleware function accepts one parameter more than the number of arguments passed.
I'll look into it whether it's a bug or not.

I think this needs further explanation ...
The method I'm mixing in grappling is an object from a third-party method. The instance in which I ran into an issue .method() was called without an argument. .method() internally checked for the missing argument.

So ... you have no bug. It works as advertised. Let me know if you're willing to support this edge-case, otherwise I'm sure I can find a workaround.

I updated my original comment to show to actual edge-case.

Ok, I get it. Yes, it's explicitly assumed that wrapped methods are asynchronous, but I must confess I never thought about wrapping 3rd party methods that may or may not be async. I'll think on it. I try to keep the API as clean/simple as possible, but on the other hand, maybe this is a more common use case than we think.
Obviously the solution for the time being is to manually wrap the method:
instance._method = instance.method;
instance.method = function(fn){
  instance.callHook('pre:method', function(err){
    instance._method(fn);
    instance.callHook('post:method');
  });
}

That's exactly what I'm doing right now. :-)

I've been thinking about this, but I can't come up with a good solution. The problem is that the full stack gets dezalgofied, which means it'll always finish async. If I would add a addSyncHooks method it seems to me that people would expect the wrapped method to still operate sync, i.e. you could return a value from the wrapped method, but that's simply impossible (w/o dropping the dezalgofication)
When comparing to hooks and kareem, they seem to have the same "problem". Aarrgh... this sync/async stuff gives me headaches :grin:

Another problem is that if I'd drop the dezalgofication for syncHooks it would open the door for very hard to find bugs. E.g.
instance.syncMethod = function(foo){
  return foo;
}
instance.addSyncHooks('syncMethod');

This works:
console.log(instance.syncMethod('foo'));

# outputs
foo

This too:
instance.pre('syncMethod', function(){
  console.log('sync PRE');
});
console.log(instance.syncMethod('bar'));

# outputs
sync PRE
bar

But then...
instance.pre('syncMethod', function(next){
  console.log('async PRE');
  next();
});
console.log(instance.syncMethod('qux'));

# outputs
async PRE
undefined

:bomb:
So, another step down the ever deepening rabbit hole would mean that... only sync middleware is allowed? Any middleware is allowed, but it's run sync? Or...?

Ok, got it all figured out.

I'm waiting with bated breath ... :-)


Refactor LearningRateScheduler

This line of code and below were taken into that file from another earlier existing file. It implemented the fundamental learning rate scheduling algorithms and two of them were used by BERT model.
It was a good starting point to build our TrainingLoop LearningRateScheduler Callback so I took it as it is in https://github.com/tensorflow/swift-models/pull/679. However this is not the right interface for user to use, so this followup PR comes out to implement a higher level interface.

Have a new one here https://github.com/tensorflow/swift-models/pull/711


scaling_mode command line for samples

Signed-off-by: Dmitry Ermilov<EMAIL_ADDRESS>

@SofyaBalandina


Add an open source license

@pellejacobs Thanks for sharing this project! We have added your library in the Mattermost redux https://github.com/mattermost/mattermost-redux/blob/master/package.json#L37.
Would you consider adding the MIT license as a LICENSE file?
If you use a license it would make it easy to add your work to other open source projects, and we'd love to keep your work in ours.
Thanks kindly for your consideration and let me know if you have any questions!
Please see more context here: https://github.com/mattermost/mattermost-redux/pull/1179#pullrequestreview-437729012.

Of course!


fix preprocess and postprocess operations

Yolov7 prevents the image scale while doing a resize operation. Because of that, I updated the preProcess function.

Thanks for the critical patch. Preprocess and therefore postprocess will now be correct.


[Feature] Load Image file from the internet.

Most of the time, I find myself loading an image directly from the internet rather than local machine.
So, instead of providing the path of an image stored locally (i.e face_recognition.load_image_file(path_to_image) , we could also give an option to paste URLs of the images which are uploaded online.
After which the function call with a URL could look something like face_recognition.load_image_file(url_of_image, url=True).
I figured a way to make it work, if the idea is approved, I shall start working on it right now.

Hello, I'm new to the open source world so I found this issue and I would like to help on implementing this!


66 todo merge GitHub action files

Refactored the Datree workflow and Dependency Review workflow into one pull-request.yml file

@all-contributors please add @hadiyahqureshi for code


Why is necessary a launchSettings.json in the project?

When I install this package on my integration test project, a directory Properties with a launchSettings.json file is created.
How its works? Why this file is needed?

Hello,
The file is from the initial fork and was not deleted. It can be safely deleted. I will clean it up once I find the time. It does not impact the project.


NativeScript 7 update

Is NativeScript 7 update coming anytime soon?
https://nativescript.org/blog/nativescript-7-for-plugin-authors/

https://github.com/triniwiz/nativescript-plugins


Ash node playbook

Depends on:

#12

This PR:

Adds a new module: ash.avalanche.eth_call that allows calling smart contract's functions on EVM networks
Adds new filters: ash.avalanche.XXX_to_XXX to convert strings between encoding (mainly hexadecimal and CB58)
Adds a new playbook to the ash.avalanche.node role: ash-node.yml that enriches the node configuration with on-chain information. For now, it queries the AshRouter contract directly to get the list of subnetIDs to add to avalanche_whitelisted_subnets

@leopaul36 can you take a look at that?


Don't retry JIRA calls on 401 unauthorized

Currently DD retries calls to JIRA 3 times. For 401 unauthorized errors this is not needed/desired. And maybe not even for other calls as well because it may result in 3 findings being created. It might be better to show the error to the user and let the use decide to retry / refresh / etc.
 dojo_async_task: running task in the foreground as block_execution is set to True for admin
trying to create a new jira issue for 49871:app-1.0.0-SNAPSHOT.war: Groovy-2.2.2.jar | CVE-2015-3253
Trying to create a new JIRA issue for finding 49871...
Starting new HTTPS connection (1): jira-uat.isaac.nl:443
https://jira:443 "GET /rest/api/2/serverInfo HTTP/1.1" 401 None
Got recoverable error from GET https://jira-uat.isaac.nl/rest/api/2/serverInfo, will retry [1/3] in 6.240514827858767s. Err: 401
https://jira:443 "GET /rest/api/2/serverInfo HTTP/1.1" 401 None
Got recoverable error from GET https://jira-uat.isaac.nl/rest/api/2/serverInfo, will retry [2/3] in 24.53720235545771s. Err: 401
https://jira:443 "GET /rest/api/2/serverInfo HTTP/1.1" 401 None
Got recoverable error from GET https://jira-uat.isaac.nl/rest/api/2/serverInfo, will retry [3/3] in 54.21921545508111s. Err: 401
https://jira:443 "GET /rest/api/2/serverInfo HTTP/1.1" 401 None
JiraError HTTP 401 url: https://jira-uat.isaac.nl/rest/api/2/serverInfo
        text:

Test

@valentijnscholten @Maffooch
After reviewing this issue and reproducing the same errors in Dojo with a JIRA cloud instance it appears that a solution is out of reach. When it comes to the basic authentication errors like 401 and 403, the 3 default JIRA calls cannot be controlled from the Dojo side. Unfortunately, any code fixes or modifications to the relevant files in DefectDojo won’t change what JIRA has for its connection calls.

On our project, we're calling https://jira.example.com/rest/api/2/issue/ABC-123 in a loop in a cron job, and roughly 1 in a thousand calls fails with HTTP 401 (even though the previous call and the next cron job with same auth had successful responses).
according to HTTP you shouldn't retry on these, but I haven't seen any Jira REST API docs for whether a retry loop is a good approach or not...


[Mildom] Add new extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
This Pull Request adds a new extractor for Mildom (mildom.com). Mildom is a relatively new Japanese live-streaming and video hosting platform with a focus on games. This PR adds an extractor for downloading videos from the site.

I'm not sure if it's okay to ask here, but is there any estimate when this is going to pushed into the master branch?
I don't know if it actually works as intended, but it's been 3 months since the last activity.

I'm not sure if it's okay to ask here, but is there any estimate when this is going to pushed into the master branch?
I don't know if it actually works as intended, but it's been 3 months since the last activity.

This is waiting to be reviewed and merged by one of the maintainers.

This is waiting to be reviewed and merged by one of the maintainers.


Odd issue with Netatmo climate platform in 0.90.

Home Assistant release with the issue:

0.90.1
Last working Home Assistant release (if known):
0.89.x
Operating environment (Hass.io/Docker/Windows/etc.):

arch
armv7l

dev
false

docker
true

hassio
true

os_name
Linux

python_version
3.7.2

timezone
Europe/London

version
0.90.1

virtualenv
false

HASSIO on RPI3
Component/platform:

homeassistant.components.climate
Description of problem:
I don't have a Netatmo termostat, yet HA seems to think I do! I only have a Netatmo camera. Here's the error I'm getting:
Netatmo error:
2019-03-22 15:47:47 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform SLOW_SETUP_MAX_WAIT, loop=hass.loop) File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for return fut.result() File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 87, in setup_platform homes = home_data.get_home_names() File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 301, in get_home_names self.setup() File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 315, in setup self.home_id = self.homedata.gethomeId(self.home) File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 84, in gethomeId home = self.default_home AttributeError: 'HomeData' object has no attribute 'default_home'

Notice the /netatmo/climate.py part, yet I've checked my YAML against the Netatmo camera component here:
https://www.home-assistant.io/components/camera.netatmo/
Very odd, maybe there's something I've done wrong, but I did not have this error when using 0.89.x
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Here's my YAML relating to the camera:
netatmo:
  api_key: !secret netatmo_id
  secret_key: !secret netatmo_secret
  username: !secret netatmo_username
  password: !secret netatmo_password

camera:
- platform: netatmo
  home: !secret netatmo_home
  cameras:
    - front_door

Traceback (if applicable):
2019-03-22 15:47:47 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform SLOW_SETUP_MAX_WAIT, loop=hass.loop) File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for return fut.result() File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 87, in setup_platform homes = home_data.get_home_names() File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 301, in get_home_names self.setup() File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 315, in setup self.home_id = self.homedata.gethomeId(self.home) File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 84, in gethomeId home = self.default_home AttributeError: 'HomeData' object has no attribute 'default_home'

Additional information:
EDIT: I forgot to mention I do have a honeywell thermostat, here's my climate YAML
climate:
  platform: honeywell
  username: !secret heat_username
  password: !secret heat_password
  region: eu

Do you have discovery: in your config?

Hi, yes I do I'm using an include file, here's my YAML:
configuration.yaml:
discovery: !include includes/discovery.yaml

discovery.yaml:
# Discovery: Discover some devices automatically
# https://www.home-assistant.io/components/discovery/
ignore:
  # - apple_tv
  - axis
  - belkin_wemo
  - bluesound
  - bose_soundtouch
  - denonavr
  - directv
  - frontier_silicon
  - google_cast
  # - harmony
  - ikea_tradfri
  # - logitech_mediaserver
  - netgear_router
  - openhome
  - panasonic_viera
  - philips_hue
  - plex_mediaserver
  - roku
  - sabnzbd
  - samsung_printer
  - samsung_tv
  - sonos
  - songpal
  - tellstick
  - wink
  - yamaha
  - yeelight
  - xiaomi_gw

I use it to detect Logitech Mediaserver devices but I've set it to ignore most other things.

So you're autodetecting netatmo devices. Can you exclude netatmo as well and check if the error persists?

This is probably the same as #22273.

So you're autodetecting netatmo devices. Can you exclude netatmo as well and check if the error persists?

There is no way to exclude Netatmo from discovery from what I can see:
https://www.home-assistant.io/components/discovery/

Duplicate of #22273.

So you're autodetecting netatmo devices. Can you exclude netatmo as well and check if the error persists?

I tried adding netatmo to the list of excludes in my discovery.yaml so it now looks like this:
# Discovery: Discover some devices automatically
# https://www.home-assistant.io/components/discovery/
ignore:
  # - apple_tv
  - axis
  - belkin_wemo
  - bluesound
  - bose_soundtouch
  - denonavr
  - directv
  - frontier_silicon
  - google_cast
  # - harmony
  - ikea_tradfri
  # - logitech_mediaserver
  - netgear_router
  - netatmo
  - openhome
  - panasonic_viera
  - philips_hue
  - plex_mediaserver
  - roku
  - sabnzbd
  - samsung_printer
  - samsung_tv
  - sonos
  - songpal
  - tellstick
  - wink
  - yamaha
  - yeelight
  - xiaomi_gw

but when I go to the config checker I get this error:

Configuration invalid
Invalid config for [discovery]: value is not allowed @ data['discovery']['ignore'][10]. Got 'netatmo'. (See /config/configuration.yaml, line 188). Please check the docs at https://home-assistant.io/components/discovery/

So it seems that the discovery component isn't able to exclude netatmo devices?


All indicators colored bars full all the times.

I just had a chance to test a device,
The voltage above and current indicators work as expected,
bu all of

SCK
MISO
MOSI
CS
A
B

bars are filled with color all the time.
I tried to follow the tutorials - the border around CS, A symbols blink, but the bars designated to show signal are filled all the time.
I tried the image rendering (TFT demo) sample, and the TFT is white and bars are filler.
I am sorry for noob question -  really just got my SPIDriver and tried to follow the tutorials
Can you please help me - where to start debugging this

Definitely sounds like a hardware issue. Email me at<EMAIL_ADDRESS>to arrange a replacement.


Option to specify things to remove

The package can remove:

export in export const foo / export function foo
export const foo / export function foo
foo in function (foo)
const foo
files

I would like to limit it to a subset or removed things
(personally I don't really want to remove unused constants, arguments, and export clauses that are still used in the file)
(i.e. I only want to remove completely unused export function/export const and files)
For arguments and constants there already are eslint rules, so if I have any left they are probably intentionally excluded

Thanks! I’d say it’s not a high priority issue at this moment, but the possible solutions could be discussed!


Paper Trail whodunnit model required

If I don't specify
config.audit_with :paper_trail, 'User', 'PaperTrail::Version'
history is not shown.
But I have no User model. I have no way to tell rails_admin that I have no whodunnit model to track.

Have you reported this to the rails_admin crew?
Per our contributing guide if you think you've found a bug in PT, please use our bug report template.


fix spurious assertions that were always true

The syntax:
assert foo, "message"

Checks foo and then prints "message" if foo is false.
The syntax:
assert (foo, "message")

Checks that the tuple (foo, "message") is True, which it always is,
and therefore doesn't actually test anything.

@eklitzke killer, thx


Pivpn and smarthome

Hi, can anyone help me out here please.
I’m not too familiar when it comes to VPN’s and not sure what they can do if anything more than a making a secure link into your home router and onto the web.
Thing is I’ve various sensors and cameras etc around the house, the garden and in my pond. Some I can only monitor when at home on my LAN via various apps and I’d like to access them while out and about.
So my question is, Will pivpn allow me access to my network of cameras & sensors remotely that I can’t access now?  And if not, what can it do, other than create a secure link back home and onto the web.
Thanks

Yes it can.  I have been using pivpn throughout the lockdown to access an office net work remotely and securely (actually multiple people have access).  The remote net work is 192.168.22.XX/24, and has a router onto an ISP.  The pivpn is connected to the network and has an address onto the network of <IP_ADDRESS>.  On the network there is a CCTV camera recorder, with an address of <IP_ADDRESS>.
When I start the VPN client on my PC, it is connected directly to the 192.168.22.xx network.  If I enter <IP_ADDRESS> into my browser, I see the camera server as if I were connected directly to a switch on that network.  I think that is exactly what you are asking for.  If a do a SSH into the pi running the pivpn, I need to connect to<EMAIL_ADDRESS>fro my PC.

Hi shelleycat485
Really appreciate your reply and the news that I can access my camera(s).
That's actually brilliant news for me, so thank you for explaining how to
do it too.
I'm with now tv but moving to Plusnet in a couple of weeks, so I'll get it
ready for then, well as much as I can as I'm told nowtv don't allow port
forwarding.
You mention your pc connecting to it.
So one last question, sorry..
Do you know if a tablet or smartphone would also connect to it , the camera
via the pivpn I mean.
 Alex
On Mon, 29 Jun 2020, 23:55 shelleycat485<EMAIL_ADDRESS>wrote:

Yes it can. I have been using pivpn throughout the lockdown to access an
office net work remotely and securely (actually multiple people have
access). The remote net work is 192.168.22.XX/24, and has a router onto an
ISP. The pivpn is connected to the network and has an address onto the
network of <IP_ADDRESS>. On the network there is a CCTV camera recorder,
with an address of <IP_ADDRESS>.
When I start the VPN client on my PC, it is connected directly to the
192.168.22.xx network. If I enter <IP_ADDRESS> into my browser, I see the
camera server as if I were connected directly to a switch on that network.
I think that is exactly what you are asking for. If a do a SSH into the pi
running the pivpn, I need to connect to<EMAIL_ADDRESS>fro my PC.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pivpn/pivpn/issues/1076#issuecomment-651410831, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQZSFI7OXDVAAAQIQODSADRZELVDANCNFSM4OLR523A
.

Yes, it should work in exactly the same manner.  You need to have the VPN client on your phone, transfer the configuration file to the phone (email it to yourself, its only small), load it into the client, then make the VPN connection.  Then you open the phone browser and type in the home address of your camera.  On my tablet I have used the openvpn client from the android app store.

Hi shelleycat485
Its really decent of you to help out and to know it can work, TBO, it's
more important it works for me than it been awkward
But I appreciate your input, just need to get set up with my new provider
Cheers
A
On Tue, 30 Jun 2020, 00:53 shelleycat485<EMAIL_ADDRESS>wrote:

Yes, it should work in exactly the same manner. You need to have the VPN
client on your phone, transfer the configuration file to the phone (email
it to yourself, its only small), load it into the client, then make the VPN
connection. Then you open the phone browser and type in the home address of
your camera. On my tablet I have used the openvpn client from the android
app store.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pivpn/pivpn/issues/1076#issuecomment-651428884, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQZSFMIJDLLZKH4YBADGTDRZESP5ANCNFSM4OLR523A
.


Gracefully exit & cleanup on Interrupt

Proposed changes
Instead of violently exiting on ^C, provide 2 levels of exits:

Gentle exit
Hard & immediate exit

Current processing suite are interrupted, and upcoming suite are marked as skipped and won't be processed.
Hitting ^C once:
➭ go run ./cmd/saucectl/ run -c .sauce/cypress.yml --test-env docker --ccy 3
12:52:10 INF Running version v0.0.0+unknown
12:52:10 INF Reading config file config=.sauce/cypress.yml
12:52:10 INF Running Cypress in Docker
12:52:10 INF concurrency > 1: forcing file transfer mode to use 'copy'.
12:52:10 INF Launching workers. concurrency=3
12:52:10 INF Setting up test environment suite="saucy test-1"
12:52:10 INF Setting up test environment suite="saucy test-2"
12:52:10 INF Setting up test environment suite="saucy test-3"
12:52:10 INF Using credentials set by environment variables suite="saucy test-2"
12:52:10 INF Using credentials set by environment variables suite="saucy test-1"
12:52:10 INF Using credentials set by environment variables suite="saucy test-3"
12:52:10 INF Starting container id=e1999e167dd7 img=saucelabs/stt-cypress-mocha-node:v5.8.0 suite="saucy test-3"
12:52:10 INF Starting container id=c70d3d2a1205 img=saucelabs/stt-cypress-mocha-node:v5.8.0 suite="saucy test-1"
12:52:10 INF Starting container id=b0d67eec651d img=saucelabs/stt-cypress-mocha-node:v5.8.0 suite="saucy test-2"
^C12:52:11 INF Ctrl-C captured. Ctrl-C again to exit now.
12:52:11 INF File copied from=tests/e2e/cypress.json suite="saucy test-3" to=/home/seluser/
12:52:11 INF File copied from=tests/e2e/cypress.json suite="saucy test-1" to=/home/seluser/
12:52:11 INF File copied from=tests/e2e/cypress.json suite="saucy test-2" to=/home/seluser/
12:52:11 INF File copied from=tests/e2e/cypress suite="saucy test-3" to=/home/seluser/
12:52:12 INF File copied from=tests/e2e/cypress suite="saucy test-1" to=/home/seluser/
12:52:12 INF File copied from=tests/e2e/cypress suite="saucy test-2" to=/home/seluser/
12:52:12 INF Tearing down environment suite="saucy test-3"
12:52:12 INF Tearing down environment suite="saucy test-1"
12:52:12 INF Tearing down environment suite="saucy test-2"
12:52:14 WRN Suite skipped. suite="saucy test-3"
12:52:14 WRN Suite skipped. suite="saucy test-4"
12:52:14 WRN Suite skipped. suite="saucy test-5"
12:52:14 WRN Suite skipped. suite="saucy test-6"
12:52:14 WRN Suite skipped. suite="saucy test-7"
12:52:14 WRN Suite skipped. suite="saucy test-8"
12:52:14 WRN Suite skipped. suite="saucy test-9"
12:52:14 WRN Suite skipped. suite="saucy test-1"
12:52:14 WRN Suite skipped. suite="saucy test-2"
12:52:14 ERR ┌────────────────────────────────┐
12:52:14 ERR  9 of 9 suites have failed (100%)
12:52:14 ERR └────────────────────────────────┘
exit status 1
➭

Hitting ^C twice:
➭ go run ./cmd/saucectl/ run -c .sauce/cypress.yml --test-env docker --ccy 3
14:37:41 INF Running version v0.0.0+unknown
14:37:41 INF Reading config file config=.sauce/cypress.yml
14:37:41 INF Running Cypress in Docker
14:37:41 INF concurrency > 1: forcing file transfer mode to use 'copy'.
14:37:42 INF Launching workers. concurrency=3
14:37:42 INF Setting up test environment suite="saucy test"
14:37:42 INF Using credentials set by environment variables suite="saucy test"
14:37:42 INF Starting container id=154dd73d34a4 img=saucelabs/stt-cypress-mocha-node:v5.8.0 suite="saucy test"
14:37:42 INF File copied from=tests/e2e/cypress.json suite="saucy test" to=/home/seluser/
14:37:42 INF File copied from=tests/e2e/cypress suite="saucy test" to=/home/seluser/
^C14:37:43 INF Ctrl-C captured. Ctrl-C again to exit now.
14:37:43 INF Tearing down environment suite="saucy test"
^Cexit status 1
➭

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Codecov Report

Merging #251 (41eee7e) into master (6147d66) will increase coverage by 0.08%.
The diff coverage is 34.09%.

@@            Coverage Diff             @@
##           master     #251      +/-   ##
==========================================
+ Coverage   35.49%   35.58%   +0.08%
==========================================
  Files          37       37
  Lines        2406     2518     +112
==========================================
+ Hits          854      896      +42
- Misses       1402     1468      +66
- Partials      150      154       +4

Impacted Files
Coverage Δ

cli/command/run/cmd.go
24.48% <0.00%> (-0.20%)
:arrow_down:

internal/docker/container.go
0.00% <0.00%> (ø)

internal/docker/cypress.go
0.00% <0.00%> (ø)

internal/docker/playwright.go
0.00% <0.00%> (ø)

internal/docker/puppeteer.go
0.00% <0.00%> (ø)

internal/docker/testcafe.go
0.00% <0.00%> (ø)

internal/saucecloud/playwright.go
6.81% <0.00%> (-0.33%)
:arrow_down:

internal/saucecloud/testcafe.go
7.31% <0.00%> (-0.38%)
:arrow_down:

internal/resto/client.go
48.36% <71.42%> (+2.99%)
:arrow_up:

internal/saucecloud/cloud.go
60.24% <71.73%> (+4.68%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


basicvsr_plusplus_c64n7_8x1_600k_reds4.log what does “8*1” mean?

in "configs/restorers/basicvsr_plusplus/basicvsr_plusplus_c64n7_8x1_600k_reds4.py"
train_dataloader=dict(samples_per_gpu=4, drop_last=True),  # 2 gpus

8x1 means 8GPUs, with batch size=1 for each GPU. We have updated the config here.


add cupy.random.hypergeometric

Jenkins, test this please.

Jenkins CI test (for commit 3a026a16c78e5ab423ff2f81c2506a4158f44d3e, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit aa26f7982ac67b319aa476957c9ca0a4067632a4, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Could you resolve the conflict?  (loggam is added to _kernels in #1418)

Jenkins, test this please.

Jenkins CI test (for commit 53ce048849bb8d279d6ce9c32e923c3aeedd6788, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Could you check the test failures with cupy-py2?

Jenkins, test this please.

Jenkins CI test (for commit 90d109fe76b9093b78c37748f9fb066914df1b2f, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The Jenkins failure is irrelevant.

Jenkins, test this please.

Jenkins CI test (for commit c95f32486e1b91e89f6cce6b2f1243f222e3937e, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Export useQueryClient from @contentful/field-editor-reference

It would be great to have access to client instance itself on top of SharedQueryClientProvider to be able to invalidate or set data to cache storage from the app code, because right now it is pretty hard to update entry title in case it was modified externally.

Hi @ManasiRoy that was the first thing I have tried, but unfortunately is not exported from this package. Only provider is, you can find it here https://github.com/contentful/field-editors/blob/master/packages/reference/src/index.tsx#L26


Missing package grunt-manifest-packager

Installing latest version is unpossible because grunt-manifest-packager cannot be found.
Error log: https://gist.github.com/maxaon/7c1dff38579ba4e1416f

Please make sure you have private npm configured correctly:
http://kb.wixpress.com/display/dashboard/Using+private+npm+registry


feat: support for deserialization from JSON and XML

BREAKING CHANGE:
This development implements a (currently in Pre-Alpha) library developed specifically to address serialization and deserialization to/from JSON/XML and Pythonic Classes that utilise the @property decorator. See #185.
Included in this PR:

Ensuring all manner of CDX documents and be deserialized
Replacing the hard-coded serialization code with this library
Completing Test Coverage
Bringing the external library py-serializable to a stable state

Also in this PR are the following PR's/Features:

#325

Current known limitations:

Requires Python >= 3.7 (see above)
(De-)serialization of Vulnerabilities in schema version < 1.4 is now NOT supported - prior to 1.4 - we have dropped support for the Vulnerabilities Schema Extension in this PR
Dependency Graph is not yet part of de-serialization

Signed-off-by: Paul Horton<EMAIL_ADDRESS>

Hi @madpah,
first, thanks for your work on this python library, it really helped us in our first steps towards SBOM generation of some of the assets created in the AlmaLinux Build System, which is used to build the packages of the AlmaLinux OS distribution. As you can see here, I gave a try to this branch and although it already meets our expectations, and following @stevespringett's advice, I would like to mention that the bom-refs are missing after reusing an already existing SBOM. Is it maybe already in your radar and that you'll be fixing soon? Thanks and keep up the good work!

@madpah Hey! 'sup? what's the plan on this? Fancy some help?

@keshav-space  We would likely use this for https://github.com/nexB/scancode.io/issues/583 ;)

@pombredanne (and anyone else!) - if you have time, would appreciate eyes over this PR as tests are now stable and passing.
Thanks

Hi @madpah,
first, thanks for your work on this python library, it really helped us in our first steps towards SBOM generation of some of the assets created in the AlmaLinux Build System, which is used to build the packages of the AlmaLinux OS distribution. As you can see here, I gave a try to this branch and although it already meets our expectations, and following @stevespringett's advice, I would like to mention that the bom-refs are missing after reusing an already existing SBOM. Is it maybe already in your radar and that you'll be fixing soon? Thanks and keep up the good work!

Hey @javihernandez - thanks for getting involved and providing feedback so early - it is greatly appreciated.
Am I correct that the issue you are pointing out relates to the bom.dependencies part of model?
Thanks,
P

@javihernandez - fairly confident that the issue you had previously is now resolved on this branch. If you're able to check/test, that would be awesome.


Upstream issue with node-sass and foundation components

The current beta5 of node-sass introduced some bugs together with the foundation scss. An issue on the upstream project is open.
This leads to the behavior, that ember-cli does not compile the sccs of foundation anymore, with the following error:
File: bower_components/foundation/scss/foundation/components/_forms.scss (335) expected a variable name (e.g. $x) or ')' for the parameter list for url

To anyone else having this problem:
downgrade your node-sass version in the ember-cli-sass module to beta4 fixes this problem.
Upstream Issues:
https://github.com/sass/libsass/issues/1059
https://github.com/sass/node-sass/issues/840

I have the same problem, I updated ember-cli and my project to the last version of ember-cli and I got this problem.

Is there a way to downgrade a sub-package without using a shrinkwrap file?

+1 to @seriousben on ways to downgrade the sub-package.
For anyone like me who had trouble with this, to fix this error you actually have to go into
node_modules/ember-cli-sass/node_modules/broccoli-sass-source-maps/package.json and change the node-sass dependency to 3.0.0-beta.4.

Downgrading to<EMAIL_ADDRESS>should also fix this problem (there's obviously issues with the node-sass beta).

See #44 for details on this issue.

I've also published<EMAIL_ADDRESS>which fixes the version of node-sass to 3.0.0-beta.4 to avoid this issue with Foundation. I'll publish another version when this issue is resolved.

The current master branches of the upstream projects have the bugs fixed, but don't know when they want to release the new version. But anyway @aexmachina sticking to a specific version while a beta is so far the best one can and should do. If you publish the new version I suggest you also stick to the new release and not including the new ones already. While a running beta we have to expect, that things like this happen.

So, does beta.4 not resolve your issue?

@aexmachina never said this ;) as also pointed out in my initiual issue it does, I was talking about the future releases of node-sass/libsass

@aexmachina the beta.4 is working fine, thanks!

node-sass is now a peerDependency, so you specify which version of<EMAIL_ADDRESS>to use in your package.json file.

@aexmachina the peer dependency is not correctly configured, there is also already an issue to this open.
https://github.com/aexmachina/ember-cli-sass/issues/46

@wzrdtales I'm not sure I understand what you're saying. See #44 for details on the resolution. Please reopen if you've still got an issue.

Yes @wzrdtales, that's been fixed now.


Input Field Issues

I don't remember seen this before, but maybe I'm wrong. When there's an input field, the text inside the field is right aligned, which makes it harder to tap (tapping on the input field positions the cursor at the beginning instead of end, which would be expected.). It also fails to capture blank spaces. Things get even harder when editing input field with numbers.

Thanks!

Hmmm it didn't shocked me while using it on device, and it's a bit more estetically pleasing, but right for the turnip form it's a bit harder to use, @TheVaan you might want to recheck it.

I agree it’s not perfect. It didn’t felt wrong when I tested my changes. Alignment to the left looked really stupid... I’ll rethink how to get a good look and feel.

Fixed for turnip input in 87dc1ea5147f2bef2f90cfdb27c6b11df3c61dfe
Textfields on phone work bettern than in simulator. Let's wait for WWDC to see, if they will improve form view in SwiftUI.


Pre 3.0 release on the roadmap ?

Given  the discussion  about a 3.0  release in #1558,  do you plan to have a pre 3.0 release version inline with your normal release schedule?
I only ask as we are eager to use a few enhancements you've added since your last release and we would prefer using an actual release versus using a commit directly from master.
Any info/guidance is greatly appreciated.

My apologies, been slammed at work and in the middle of a house move. Yes, I need to get a 2.x release out with all the new changes so I'll get to merging over the weekend (thanks @axelpavageau for the PRs!) to get a release out before I move next week. Appreciate the reminder and again, apologies to the community for the delay.

Just merged a bunch of changes and Release 2.6.0 is now available.


SC4S Vulnerabilities

twistlock_scans_splunk-connect-for-syslog_latest_01_20_23_08_39_38.xlsx
See attached.  I'm trying to get SC4S added to an internal repository.
Are these able to be remediated or explained?

we need to review this and get back.


Add Angular internationalization (multi-language support)

Add functionality to the frontend for changing the display language of the website.
Angular has a detailed guide on how to do this.
Documentation on how to add different languages and modify existing text should be included

It does seem like Angular does not support dynamic language change and multiple apps have to be served
But this plugin seems to allow dynamic change of language in a similar way to what we had in Treecreate Phase 1. Might be worth looking into as a solution for internationalization


docs: restore proper event target in isEditingContent function

'event.currentTarget' points to null in most cases. Changed to 'event.target'. Also, this commit fix one typo
fix #1896 re #1827 re #1919
What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
Typing '/' inside textareas, inputs etc. triggers the search modal. Problem was that someone change event.target to event.currentTarget in #1827 . I just restore event.target.
I also fix one type in 'Github' -> 'GitHub' missed in #1919
Use cases and why
There was console error on official page, when you hit '/' inside monaco editor:

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Thank you much for the awesome fix!


We should not reuse wrapped_sphinx_directory

Problems occur if we do. For example, index.rst is created in a previous run from index.rst.jinja. Now it exists, so index.rst.jinja will not overwrite it.

I have a patch that deletes docs_build to fix this.


evil-mc-make-all-cursors produces an error: "No search pattern"

What did you expect to happen?
evil-mc-make-all-cursors selects all targets with the same pattern.
What actually happened?
Fill the scratch buffer with the following:
temp
temp
temp

Put the cursor on the first word and run M-x evil-mc-make-all-cursors -> error "No search pattern"
Debugger entered--Lisp error: (search-failed "No search pattern")
  signal(search-failed ("No search pattern"))
  evil-ex-find-next(nil forward t)
  evil-mc-make-cursors-for-all()
  evil-mc-make-all-cursors()
  funcall-interactively(evil-mc-make-all-cursors)
  command-execute(evil-mc-make-all-cursors record)
  execute-extended-command(nil "evil-mc-make-all-cursors" nil)
  funcall-interactively(execute-extended-command nil "evil-mc-make-all-cursors" nil)
  command-execute(execute-extended-command)

Describe your attempts to resolve the issue
You can use debug-on-variable-change on the evil-mc-pattern to see what's going on.
At first, it is cleared in evil-mc-set-pattern
Debugger entered--setting evil-mc-pattern in buffer *doom:scratch* to nil:
  debug--implement-debug-watch(evil-mc-pattern nil set #<buffer *doom:scratch*>)
  evil-mc-set-pattern()
  evil-mc-make-all-cursors()
  funcall-interactively(evil-mc-make-all-cursors)
  command-execute(evil-mc-make-all-cursors)

Then it is set to the pattern:
Debugger entered--setting evil-mc-pattern in buffer *doom:scratch* to (("\\_<temp\\_>" t t) 1837 1841 inclusive :expanded t):
  debug--implement-debug-watch(evil-mc-pattern (("\\_<temp\\_>" t t) 1837 1841 inclusive :expanded t) set #<buffer *doom:scratch*>)
  evil-mc-set-pattern-for-range((1837 1841 inclusive :expanded t) t)
  evil-mc-set-pattern()
  evil-mc-make-all-cursors()
  funcall-interactively(evil-mc-make-all-cursors)
  command-execute(evil-mc-make-all-cursors)

And then its cleared when running hooks from evil-mc-before-cursors-created.
Debugger entered--setting evil-mc-pattern in buffer *doom:scratch* to nil:
  debug--implement-debug-watch(evil-mc-pattern nil set #<buffer *doom:scratch*>)
  evil-mc-clear-pattern()
  evil-mc-initialize-vars()
  evil-mc-mode(1)
  turn-on-evil-mc-mode()
  apply(turn-on-evil-mc-mode nil)
  evil-mc-initialize-active-state()
  funcall(evil-mc-initialize-active-state)
  (condition-case e (funcall hook) ((debug error) (signal 'doom-hook-error (list hook e))))
  doom-run-hook(evil-mc-initialize-active-state)
  run-hook-wrapped(doom-run-hook evil-mc-initialize-active-state)
  (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if (symbolp (car (cdr e))) (symbol-name (car (cdr e))) (car (cdr e))) (car (cdr (cdr e))))) (signal 'doom-hook-error (cons hook (cdr e)))))
  (let ((hook (car --dolist-tail--))) (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if (symbolp (car ...)) (symbol-name (car ...)) (car (cdr e))) (car (cdr (cdr e))))) (signal 'doom-hook-error (cons hook (cdr e))))) (setq --dolist-tail-- (cdr --dolist-tail--)))
  (while --dolist-tail-- (let ((hook (car --dolist-tail--))) (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if (symbolp ...) (symbol-name ...) (car ...)) (car (cdr ...)))) (signal 'doom-hook-error (cons hook (cdr e))))) (setq --dolist-tail-- (cdr --dolist-tail--))))
  (let ((--dolist-tail-- hooks)) (while --dolist-tail-- (let ((hook (car --dolist-tail--))) (condition-case e (run-hook-wrapped hook #'doom-run-hook) ((debug doom-hook-error) (if debug-on-error nil (lwarn hook :error "Error running hook %S because: %s" (if ... ... ...) (car ...))) (signal 'doom-hook-error (cons hook (cdr e))))) (setq --dolist-tail-- (cdr --dolist-tail--)))))
  doom-run-hooks(evil-mc-before-cursors-created)
  apply(doom-run-hooks evil-mc-before-cursors-created)
  run-hooks(evil-mc-before-cursors-created)
  evil-mc-cursors-before()
  evil-mc-run-cursors-before()
  evil-mc-make-cursors-for-all()
  evil-mc-make-all-cursors()
  funcall-interactively(evil-mc-make-all-cursors)
  command-execute(evil-mc-make-all-cursors)

These hooks were added in https://github.com/hlissner/doom-emacs/commit/b2b19e7196cb34e3147005680e49b50db2ce547f
Steps to reproduce
Fill the scratch buffer with the following:
temp
temp
temp

Put the cursor on the first word and run M-x evil-mc-make-all-cursors -> error "No search pattern"
System Information
https://pastebin.com/JGqqGVMg

I can't reproduce this. Can you reproduce this in vanilla Doom?

Yes, this fixes issue. Thank you!

As of 4b75100 this issue should now be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!


Problem: Still Edge in Task manager after unistall completely edge.

Please can you fix for force uninstall the Microsoft Edge in [ task manager > App History (tab) ] I want to permanent uninstall after windows update so no problem.
I did force uninstalled edge everything when its gone in task manager (App history) then I updated in Windows 10 when it's back Edge in Task manager.
Note: Sorry For My Bad English
thank you. let me know

There was nothing in the folder.
here is picture.

If that folder is blank, the Chrome based version of Edge is removed.
The built in version of Edge, is not removed by this script.
Try these steps, to disable it.
https://silicophilic.com/disable-microsoft-edge/


Have you meet value function explosion when developing?

Hi Danijar. Yet another question about the actor-critic part.
I am trying to use the actor-critic part in my own project with a different world model. Sometimes the whole model works fine, but sometimes the value function suddenly explodes exponentially. I use the same gradient clip as you, but it did not stop the explosion. I wonder if you have meet the same phenomena when developing. Anything would be helpful. Thanks in advance.

Hi, thanks for your question. Yes, the value function can be a bit unstable and gradient clipping is a simple solution that usually works. If it doesn't, you can simply use a slow target network. Updating it every 100 gradient steps works well. I've been using that for some exploration objectives that change throughout learning. I'll also add a flag for this to the repository at some point, probably when I have more time after upcoming the NeurIPS deadline.


fix the maskinput inside masked date picker

@joelmeiller ignorier d'storybook changes. ich wird die als negstes apasse

Looks promising 🤓 Let's give it a shot.
I am positive that Cypress would fish it out if a unknown regression has been introduced.


telescope ui unexpected

Describe the bug

the telescope ui is dropdown and near cursor
but in select i set ivy default,and cursor for code action
it seems that when defaut is ivy,and indicate one as cursor, telescope ui will mess up
if i change one of the two,everyting ok

System information

OS: windows
Neovim version: v0.8.3
Is this related to a specific vim.ui.select backend? If so, which one? Telescope
Dressing config:

require("dressing").setup({
			input = {
				enabled = true,
				default_prompt = "Input:",
				prompt_align = "left",
				insert_only = true,
				start_in_insert = true,
				anchor = "SW",
				border = "single",
				relative = "cursor",
				prefer_width = 40,
				width = nil,
				max_width = { 140, 0.9 },
				min_width = { 20, 0.2 },
				buf_options = {},
				win_options = {
					winblend = 0,
					wrap = false,
				},
				mappings = {
					n = {
						["<Esc>"] = "Close",
						["<CR>"] = "Confirm",
					},
					i = {
						["<C-c>"] = "Close",
						["<CR>"] = "Confirm",
						["<Up>"] = "HistoryPrev",
						["<Down>"] = "HistoryNext",
					},
				},
				override = function(conf)
					return conf
				end,
			},
			select = {
				telescope = require("telescope.themes").get_ivy(),
				get_config = function(opts)
					if opts.kind == "codeaction" then
						return {
							telescope = require("telescope.themes").get_cursor({}),
						}
					elseif opts.kind == "overseer_template" then
						return {
							telescope = require("telescope.themes").get_cursor({}),
						}
					end
				end,
			},
		})

To Reproduce
Steps to reproduce the behavior:

set dressing config as before
code action

I don't think I understand this bug report. The configuration you have specifies that telescope should use the "cursor" theme for code actions, and the screenshot shows a code action with the "cursor" theme. What is the problem?

sorry, my mistake.  I mix up three telescope theme. Thanks for you time.😹


Default rounding in toFixed as impelmented on MDN

Hi,
have you considered including the very nice and accurate rounding function provided by the guys from Mozilla instead of the Math.round * power / power technique which leads as the code comments says to inconsistent floating point rounding ?
Kind regards
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/round

The current method is very bad: due to double rounding, formatting certain numbers with large enough precision results in errors:
numeral(5241340125).format('0.000000000') // returns "5241340124.999999046"

Using the mozilla function (slightly modified) as follows yields the correct result:
diff --git a/WebApp/Scripts/numeral/numeral.js b/WebApp/Scripts/numeral/numeral.js
index 9f46ab6..7bbe0ea 100644
--- a/WebApp/Scripts/numeral/numeral.js
+++ b/WebApp/Scripts/numeral/numeral.js
@@ -33,6 +33,25 @@
		 this._value = number;
	 }

+    function decimalAdjust(round, value, exp) {
+        // If the exp is undefined or zero...
+        if (typeof exp === 'undefined' || +exp === 0) {
+            return round(value);
+        }
+        value = +value;
+        exp = +exp;
+        // If the value is not a number or the exp is not an integer...
+        if (isNaN(value) || !(typeof exp === 'number' && exp % 1 === 0)) {
+            return NaN;
+        }
+        // Shift
+        value = value.toString().split('e');
+        value = round(+(value[0] + 'e' + (value[1] ? (+value[1] - exp) : -exp)));
+        // Shift back
+        value = value.toString().split('e');
+        return +(value[0] + 'e' + (value[1] ? (+value[1] + exp) : exp));
+    }
+
	 /**
	  * Implementation of toFixed() that treats floats more like decimals
	  *
@@ -46,7 +65,8 @@

		 //roundingFunction = (roundingFunction !== undefined ? roundingFunction : Math.round);
		 // Multiply up by precision, round accurately, then divide and use native toFixed():
-        output = (roundingFunction(value * power) / power).toFixed(precision);
+        output = decimalAdjust(roundingFunction, value, -precision).toFixed(precision);
+        //output =  (roundingFunction(value * power) / power).toFixed(precision);

		 if (optionals) {
			 optionalsRegExp = new RegExp('0{1,' + optionals + '}$');

This looks to be a floating point error, which numeral does not attempt to solve


Multipart request to create a Record with an attachment AND access controls

Hello sorry I am weary of talking to support about this -
A client is using multipart requests to create Records with attachments, this is working perfectly for all types of fields, Title, Container, additional fields, etc.
The problem is that they also want to set access controls (restrict View Metadata/View Document to certain users) at the time of creation.
We can't seem to get the multipart request to accept any format of the Access Controls property, we've tried JSON, form data but the Record is created unrestricted.
Can you offer any advice on how to create a Record with an attachment and access controls in a single request, or do we really need to do 2 requests as suggested by support?

Sorry Jan, you will have to make two requests.  I suggest upload the file
first then create the Record.  The multi-part upload uses a 'simplified'
form of JSON which is not great for representing complex objects so we long
ago made the choice to not support this.
On Wed, 19 Apr 2023 at 10:25, Jan Martin @.***> wrote:

Hello sorry I am weary of talking to support about this -
A client is using multipart requests to create Records with attachments,
this is working perfectly for all types of fields, Title, Container,
additional fields, etc.
The problem is that they also want to set access controls (restrict View
Metadata/View Document to certain users) at the time of creation.
We can't seem to get the multipart request to accept any format of the
Access Controls property, we've tried JSON, form data but the Record is
created unrestricted.
Can you offer any advice on how to create a Record with an attachment and
access controls in a single request, or do we really need to do 2 requests
as suggested by support?
—
Reply to this email directly, view it on GitHub
https://github.com/content-manager-sdk/Community/issues/41, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG7YHVP2NH77X4BW755UO3XB4WGJANCNFSM6AAAAAAXDKPYP4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks, okay we'll have to look at a workaround...


[Followup SPARK-8387][WEBUI] Update driver log URL to show only 4096 bytes

This is to follow up #6834 , update the driver log URL as well for consistency.

Merged build triggered.

Merged build started.

Test build #35118 has started for   PR 6878 at commit a0004f4.

Do you need to update YarnClusterSuite too? looks like it expects start=0

Merged build triggered.

Merged build started.

Thanks for the reminder, @srowen !  The url in YarnClusterSuite is now updated.

Test build #35120 has started for   PR 6878 at commit 13be948.

Test build #35118 has finished for   PR 6878 at commit a0004f4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class CreateStruct(children: Seq[Expression]) extends Expression

Merged build finished. Test FAILed.

Test build #35120 has finished for   PR 6878 at commit 13be948.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

As long as -4096 works (I didn't test this), this LGTM.

LGTM, merging into master.


Fixes #3232 by handling terminating status updates for resident tasks:

introduce an Unlaunch operation
Handling Unlaunch by removing the task launch information

Nice! Just minor comments – would be great if you can address these.

@meichstedt Thanks for the hints! Please review.

Awesome – please squash!

Squashed.

Thanks!
   __|=|_|=|__
   \ o.o.o.oY/
    \_______/
  ~~~~~~~~~~~~~~


Repository.writeall() may not need to write all dirty roles

Description of issue or feature request:
TUF marks roles as dirty if they are changed in roledb. This information is then used by writeall to update role metadata on disk. But not all changes in roledb require updating metadata on disk. E.g. loading a signing key does not.
Current behavior:
At least one function, i.e. load_signing_key marks a role as dirty, although it shouldn't update the corresponding metadata on disk.
Expected behavior:
Reliably track the state of the repository in memory and on disk to know if role metadata needs to be updated. Also see #958.

When fixing this issue, we may remove the explicit mark_dirty()-calls in the tutorial code snippets (and the comments that point to this issue and to #958). Ideally writeall() will know by itself which metadata to update.

Closing this issue as it was filed against (what is now known as) the legacy codebase: issue seems to not be relevant anymore. Please re-open or file a new issue if you feel that the issue is revelant to current python-tuf.
More details
Current source code (and upcoming 1.0 release) only contains the modern components

a low-level Metadata API (tuf.api) and
tuf.ngclient that implements the client workflow,

Legacy components (e.g. tuf.client, tuf.repository_tool, tuf.repository_lib as well as the repo and client scripts) are no longer included. See announcement and API reference for more details.


Is there a way to customize the structure of the output?

Hello, I have some questions about Citation.js.
First one: I find that if I input a BibTeX structure text like this:
let BibTeX = "@article{}"
let cite = new Cite(BibTeX)

It will get the HTML output using the following code:
let bibHtmled = bibParsed.format(
  'bibliography',
  {
      format: 'html',
      template: 'apa',
      lang: 'en-US'
  }
);

The output is like:
"

Tang, H., Tan, K. C., & Yi, Z. (2007). Neural networks: computational models and applications (Vol. 53). Springer Science & Business Media.

"

Now I want to ask If there is a way to customize the structure of the output? For example I want output this:
"

    // Add 'div' block

 Tang, H., Tan, K. C., & Yi, Z. (2007).

    Neural networks: computational models and applications (Vol. 53).

Springer Science & Business Media.

"

Second one: And also I want to ask If there is a way to import modules optionally? For example, I just want to import bibtex module and do not need modules like doi or wikidata. This may narrow the package size.
Thanks for your excellent work,
Hope to get some advice!

Now I want to ask If there is a way to customize the structure of the output?

Citation.js uses CSL and citeproc-js to create formatted bibliographies, and I don't know of a way to make it there but I can ask.

And also I want to ask If there is a way to import modules optionally?

Yep, check out the packages and for browsers the bundle tool (also available at juniper-coat.glitch.me). Example usage:
const {Cite} = require('@citation-js/core')
require('@citation-js/plugin-bibtex') // load BibTeX functionality

// new Cite(...)

@larsgw Thanks!

So there is an (experimental) option to do this in citeproc apparently, I'll see what I can do to implement it.


add documentation for how to enable bucket ACLs

Describe the solution you'd like
I believe we now need to set object ownership rule to enable bucket ACLs.  Let's document this clearly so that users know whats expected in terms of policy and ACL functionality.

see aws documentations here: https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html


Identifier should not be private.

Since Identifier is under a private module, it can't be used by downstream crates. This is an issue since it's needed to match on IdentificationDescriptors.
use scsir::shortcut::inquiry::*;
use scsir::Scsi;

fn main() {
    let scsi = Scsi::new("/dev/sda").expect("Failed to open SCSI device!");
    let mut command = scsi.inquiry();
    let device_info =
        device_identification(&mut command).expect("Failed to get DeviceIdentification!");
    let description = device_info
        .descriptors
        .iter()
        .find(|x| x.identifier_type == 1)
        .expect("Failed to find device description!");
    // This doesn't work, since `Identifier` can't be imported.
    match description {
        Identifier::Ascii(foo) => println!("{foo}"),
        _ => (),
    }
}

Sorry for the late reply, I lost access to my GitHub account and just got it back
It's been fixed now


[SPARK-40185][SQL] Remove column suggestion when the candidate list is empty

What changes were proposed in this pull request?

Remove column, attribute or map key suggestion from UNRESOLVED_* error if candidate list is empty.
Sort suggested columns by closeness to unresolved column
Limit number of candidates to 5. Previously entire list of existing columns were shown as suggestions.

Why are the changes needed?

When the list of candidates is empty the error message looks incomplete:
[UNRESOLVED_COLUMN] A column or function parameter with name 'YrMo' cannot be resolved. Did you mean one of the following? []
This PR is to introduce GENERIC error subclass without suggestion and WITH_SUGGESTION subclass where error message includes suggested fields/columns:
[UNRESOLVED_COLUMN.GENERIC] A column or function parameter with name 'YrMo' cannot be resolved.
OR
[UNRESOLVED_COLUMN.WITH_SUGGESTION] A column or function parameter with name 'YrMo' cannot be resolved. Did you mean one of the following? ['YearAndMonth', 'Year', 'Month']
In addition suggested column names are sorted by Levenstein distance and capped to 5.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test

Can one of the admins verify this patch?

@MaxGekk @gengliangwang ptal.

👍 for the capping and avoiding suggesting an empty list!

@MaxGekk friendly ping.

@cloud-fan ptal

I guess I prefer the subclass over that.
Sent from my iPhone
On Sep 5, 2022, at 10:33 PM, Wenchen Fan @.***> wrote:

@cloud-fan commented on this pull request.

In core/src/main/resources/error/error-classes.jsonhttps://github.com/apache/spark/pull/37621#discussion_r963268208:

 ],

"subClass" : {

 "GENERIC" : {

shall we simply add a new error class like UNRESOLVED_COLUMN_WITH_NO_INPUT_COLUMNS?
—
Reply to this email directly, view it on GitHubhttps://github.com/apache/spark/pull/37621#discussion_r963268208, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA22CFBHHU25NBJMNVWF4OLV43JSTANCNFSM57JXCLFQ.
You are receiving this because you were mentioned.Message ID: @.***>

thanks, merging to master!