Updates for PO files

The following has been done to correct a possible unexpected processing of PO
files described in issue #14490 :

All existing PO files were reformatted to textwidth 79;
The modeline vim:tw=79:ts=8:ft=po: was added to the PO files;
In makefiles, the --width=79 parameter has been set for gettext tools;
An $(PS) $(PSFLAGS) Set-ItemProperty -Path '$@' -Name LastWriteTime -Value (Get-Date -Format 'o')
command was added to Make_mvc.mak for guaranteed timestamp updates.

Other:

Added the option to Makefile to convert files using the "msgconv" tool;
When creating a template file "vim.pot", the values in the
"Project-Id-Version" and "Report-Msgid-Bugs-To" fields of the file header are
automatically set.

Timestamps of PO files after commit:
$ ls --time-style=full-iso -l *.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>44 2024-04-20 14:02:51.774302800 +0300 af.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>99 2024-04-20 14:02:51.774302800 +0300 ca.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>11 2024-04-20 14:04:46.112465000 +0300 cs.cp1250.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>03 2024-04-20 14:02:51.774302800 +0300 cs.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>38 2024-04-20 14:02:51.774302800 +0300 da.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>25 2024-04-20 14:02:51.774302800 +0300 de.po
-rw-r--r-- 1 Admin 197121  14954 2024-04-20 14:02:51.774302800 +0300 en_GB.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>52 2024-04-20 14:02:51.774302800 +0300 eo.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>30 2024-04-20 14:02:51.774302800 +0300 es.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>31 2024-04-20 14:02:51.774302800 +0300 fi.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>78 2024-04-20 14:02:51.774302800 +0300 fr.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>09 2024-04-20 14:02:51.774302800 +0300 ga.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>44 2024-04-20 14:02:51.774302800 +0300 hu.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>68 2024-04-20 14:02:51.774302800 +0300 it.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>36 2024-04-20 14:04:46.742465900 +0300 ja.euc-jp.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>01 2024-04-20 14:02:51.774302800 +0300 ja.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>66 2024-04-20 14:04:48.912468900 +0300 ja.sjis.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>08 2024-04-20 14:04:49.532469800 +0300 ko.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>54 2024-04-20 14:02:51.774302800 +0300 ko.UTF-8.po
-rw-r--r-- 1 Admin 197121   9073 2024-04-20 14:02:51.774302800 +0300 lv.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>53 2024-04-20 14:02:51.774302800 +0300 nb.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>86 2024-04-20 14:02:51.774302800 +0300 nl.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>53 2024-04-20 14:02:51.774302800 +0300 no.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>42 2024-04-20 14:04:50.802471600 +0300 pl.cp1250.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>34 2024-04-20 14:02:51.774302800 +0300 pl.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>99 2024-04-20 14:04:50.202470700 +0300 pl.UTF-8.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>99 2024-04-20 14:02:51.774302800 +0300 pt_BR.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>05 2024-04-20 14:04:51.542472600 +0300 ru.cp1251.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>97 2024-04-20 14:02:51.774302800 +0300 ru.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>45 2024-04-20 14:04:52.132473400 +0300 sk.cp1250.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>37 2024-04-20 14:02:51.774302800 +0300 sk.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>27 2024-04-20 14:02:51.774302800 +0300 sr.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>28 2024-04-20 14:02:51.774302800 +0300 sv.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>48 2024-04-20 14:02:51.774302800 +0300 tr.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>22 2024-04-20 14:04:52.802474400 +0300 uk.cp1251.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>04 2024-04-20 14:02:51.774302800 +0300 uk.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>44 2024-04-20 14:02:51.774302800 +0300 vi.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>03 2024-04-20 14:04:53.992476000 +0300 zh_CN.cp936.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>54 2024-04-20 14:04:53.452475300 +0300 zh_CN.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>21 2024-04-20 14:02:51.774302800 +0300 zh_CN.UTF-8.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>22 2024-04-20 14:04:54.582476800 +0300 zh_TW.po
-rw-r--r-- 1 Admin<PHONE_NUMBER>82 2024-04-20 14:02:51.774302800 +0300 zh_TW.UTF-8.po

Hi, i tested your tree and I'm not sure why but some files are still being modified. At least for me:
~/p/vim ((2a4cf5d2b...) *$%) $ git status
HEAD detached at FETCH_HEAD
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   src/po/ja.euc-jp.po
	modified:   src/po/ja.sjis.po
	modified:   src/po/ru.cp1251.po
	modified:   src/po/sk.cp1250.po
	modified:   src/po/uk.cp1251.po

@julio-b
Thanks for the feedback!
That's too bad.
Honestly, I don't have any ideas on how to fix it yet.
Hopefully @k-takata  will give me some tips on where to at least start.
But in any case, I'll try to solve it somehow.

@julio-b
Can you please tell me how you got this?
On the host machine (WinNT 6.1 32-bit) I have no reproduction.
$ git fetch VimOrigin pull/14601/head && git checkout FETCH_HEAD && git status
From https://github.com/vim/vim
 * branch                refs/pull/14601/head -> FETCH_HEAD
Updating files: 100% (79/79), done.
Note: switching to 'FETCH_HEAD'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 2a4cf5d2b Remarks eliminated
HEAD detached at FETCH_HEAD
nothing to commit, working tree clean

What am I doing wrong?

@julio-b
I started Ubuntu 22 in a virtual machine today. I tweaked it a bit and tried the same thing I did on the host machine.
The result is the same.
user@user-vm:~/vim4tst$ git fetch origin pull/14601/head && git checkout FETCH_HEAD && git status
remote: Enumerating objects: 83, done.
remote: Counting objects: 100% (83/83), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 83 (delta 67), reused 80 (delta 67), pack-reused 0
Unpacking objects: 100% (83/83), 1.75 MiB | 1.50 MiB/s, done.
From https://github.com/vim/vim
 * branch                refs/pull/14601/head -> FETCH_HEAD
Note: switching to 'FETCH_HEAD'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command.  On the host machine (WinNT 6.1 32-bit) I have no reproduction.
$ git fetch VimOrigin pull/14601/head && git checkout FETCH_HEAD && git status

@RestorerZ you need to compile vim after getting these commits. Just a checkout will not modify the po files, obviously.
Anyway, I think trying to predict the wrap behavior is not going to solve the problem for everyone. After digging around in the mailing list i discovered this message https://lists.gnu.org/archive/html/bug-gettext/2023-07/msg00026.html which explains the situation. (This thread is about msgattrib, but the same thing applies for msgconv and the whole gettext suite).
Also it appears that these files have been problematic since forever, forcing Bram to add workarounds like this: https://github.com/vim/vim/blob/ea999037a41292b3d3e00700a87a82fe5d2c12b2/Makefile#L335-L343

@RestorerZ you need to compile vim after getting these commits. Just a checkout will not modify the po files, obviously.

Yeah, just updated “gettext” in Ubuntu now and will try to compile.

Anyway, I think trying to predict the wrap behavior is not going to solve the problem for everyone. After digging around in the mailing list i discovered this message https://lists.gnu.org/archive/html/bug-gettext/2023-07/msg00026.html which explains the situation. (This thread is about msgattrib, but the same thing applies for msgconv and the whole gettext suite).
Also it appears that these files have been problematic since forever, forcing Bram to add workarounds like this:

@julio-b
Look, that changes everything then.
Thank you very much for this research!
I'll see what I can do then and if anything can be done at all.
Thanks!

Closing as the original issue will be solved by #15469.
For "Project-Id-Version", please create a new PR.


Not able to execute "npm run compile:js" successfully

I am trying to compile js for the last version of sfcc adyen integration, 23.2.0 and receive such erros during npm run compile:js:
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyenAccount.js 102:9
Module parse failed: Unexpected token (102:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     event.preventDefault();
|   } else {

card?.showValidation();

|   }
| });
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyen_checkout/helpers.js 10:53
Module parse failed: Unexpected token (10:53)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     adyenPaymentMethod.value = store.brand
|       ? store.brand

  : document.querySelector(paymentMethodlabelId)?.innerHTML;

|   }
| }
@ ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyenCheckout.js 13:4-39
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyen_checkout/checkoutConfiguration.js 122:27
Module parse failed: Unexpected token (122:27)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     renderAddedGiftCard(card);
|   });

if (store.addedGiftCards?.length) {
|     showGiftCardInfoMessage();
|   }
@ ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyenCheckout.js 8:4-53

ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/amazonPayExpressPart1.js 37:6
Module parse failed: Unexpected token (37:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     const amazonPayConfig = paymentMethodsResponse.find(
|       (pm) => pm.type === AMAZON_PAY,

)?.configuration;

|     if (!amazonPayConfig) return;
|
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/checkout/billing.js 38:55
Module parse failed: Unexpected token (38:55)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|  */
| function updatePaymentInformation(order) {

if (order.billing.payment.selectedPaymentInstruments?.length) {
|     const selectedPaymentInstrument =
|       order.billing.payment.selectedPaymentInstruments[0];
@ ./cartridges/int_adyen_SFRA/cartridge/client/default/js/checkout.js 5:16-45

ERROR in ./cartridges/int_adyen_SFRA/cartridge/store/index.js 4:19
Module parse failed: Unexpected token (4:19)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| class Store {

MASKED_CC_PREFIX = '************';
|
|   @observable checkout;
@ ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyenCheckout.js 1:14-39

ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/commons/index.js 57:9
Module parse failed: Unexpected token (57:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|       document
|         .getElementById('express-loader-container')

    ?.classList.add('hidden');

|       document.getElementById('express-container')?.classList.remove('hidden');
|     }
@ ./cartridges/int_adyen_SFRA/cartridge/client/default/js/expressPaymentMethodsVisibility.js 1:42-62
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/amazonPayCheckout.js 6:40
Module parse failed: Unexpected token (6:40)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| function handleAuthorised(response) {
|   document.querySelector('#result').value = JSON.stringify({

pspReference: response.fullResponse?.pspReference,

|     resultCode: response.fullResponse?.resultCode,
|     paymentMethod: response.fullResponse?.paymentMethod
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/applePayExpress.js 81:40
Module parse failed: Unexpected token (81:40)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|   resolveApplePay();
|   document.querySelector('#result').value = JSON.stringify({

pspReference: response.fullResponse?.pspReference,

|     resultCode: response.fullResponse?.resultCode,
|     paymentMethod: response.fullResponse?.paymentMethod
ERROR in ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyen_checkout/renderGenericComponent.js 92:29
Module parse failed: Unexpected token (92:29)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|       renderAddedGiftCard(card);
|     });

if (store.addedGiftCards?.length) {

|       showGiftCardInfoMessage();
|     }
@ ./cartridges/int_adyen_SFRA/cartridge/client/default/js/adyenCheckout.js 4:4-54

Hello @kirill-kostiuk
I managed to compile the code using node v18.12.0 and npm v8.19.1
Can you check your node an npm versions?
Kind Regards
Aleksandar
Adyen

Hello @kirill-kostiuk
I just checked with node v14.21.3 and it is being compiled.

We use this command on a daily basis in order to deploy our code so we would've experience this during development.
Can you maybe reinstall the node dependencies?
Kind Regards
Aleksandar
Adyen

Hello @amihajlovski ,
I reinstalled node dependencies and issue is fixed.
Thanks for support!


How to use post to submit data.

I need to submit data using post.

Hi, I saw @jahenkor doing a POST with the crawler. You might ask him how he did that

thx.

@chunfytseng , when you are happy with the answers, can you close this issue please?

hi,so far, I still don't know how to get post data, so I need your help.

If you need to login to a page, you can submit your post request using AuthInfo (BasicAuth or FormAuth), and receive a cookie(s) you can persistent across your crawl session. However, if you want to submit and receive post data across multiple pages, I've got no clue.

@chunfytseng

@jahenkor
hi, jahenkor
I have already used AuthInfo to login, and after logging in, I need to submit data using post.

please!!!

I don't understand your scenario, what are you trying to do ?
On Sun, Sep 16, 2018 at 6:27 AM chunfytseng<EMAIL_ADDRESS>wrote:

please!!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yasserg/crawler4j/issues/342#issuecomment-421681642,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrbW4FkW55h35c9W2Pq96QoD7Aol4UOks5ubcUhgaJpZM4WZgK4
.

I don't understand your scenario, what are you trying to do ?
…
On Sun, Sep 16, 2018 at 6:27 AM chunfytseng @.***> wrote: please!!! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#342 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrbW4FkW55h35c9W2Pq96QoD7Aol4UOks5ubcUhgaJpZM4WZgK4 .

There are scenes as follows:

Login system
Get information
3, post submit data to obtain the results.
There are two results in step 3. If the successful task ends, if it fails, continue to step 3..
The above is my usage scenario.
Now, I have landed, and how to use post to submit data.

@Chaiavi

We don't support failed logins.
So if the login fails you won't get any data from the site as you are not
logged into it.
The authentication component in c4j is very basic and not sophisticated, it
was kind of a later hack added to the crawler, so it is not so flexible.
You can try to hack the auth system to do as you wish but as it is coded
now I don't see a way to try logging into a site, parsing the response so
according to it you will be able to login with a different user/pass
combination.
Chaiavi.
On Sun, Sep 16, 2018 at 6:57 PM chunfytseng<EMAIL_ADDRESS>wrote:

@Chaiavi https://github.com/Chaiavi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yasserg/crawler4j/issues/342#issuecomment-421787076,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrbW8zHdigqj5jZoi2NhQCokKblZBILks5ubnTtgaJpZM4WZgK4
.

hi, Chaiavi.I have 2 questions.
1.I have solved the problem of logon failure. Now, there is a question of using post to get data.
2.If my crawler task is long-running and crawls data with multi-user logins (I deal with multi-user logins myself), would you recommend that I start multiple PageFetcher instances and give different configs? Or do you have any better advice?
@Chaiavi

No better advice.
Just be sure you don't mix sessions of different users.
Login with one user, crawl, logoff
Login with a different user etc...
Chaiavi.
On Tue, Sep 18, 2018 at 4:54 PM chunfytseng<EMAIL_ADDRESS>wrote:

hi, Chaiavi.I have 2 questions.
1.I have solved the problem of logon failure. Now, there is a question of
using post to get data.
2.If my crawler task is long-running and crawls data with multi-user
logins (I deal with multi-user logins myself), would you recommend that I
start multiple PageFetcher instances and give different configs? Or do you
have any better advice?
@Chaiavi https://github.com/Chaiavi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yasserg/crawler4j/issues/342#issuecomment-422402466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrbW-LRdNYyQo9p9ML-SAXCaCrOWwioks5ucPswgaJpZM4WZgK4
.

thx.


Unrecognized argument in option '-mmcu=cortex-m3' : using wrong makefile

Hi,
I have decided to switch over to an Arduino Due for one of my projects and while trying to run ano build, I am getting the error
avr-g++: error: unrecognized argument in option '-mmcu=cortex-m3'
I have had a rummage around the files and I believe that the issue may be stemming from Arturo using the makefiles from
/Applications/Arduino.app/Contents/Resources/Java/hardware/arduino/avr/boards.txt
instead of those from /Applications/Arduino.app/Contents/Resources/Java/hardware/arduino/sam/boards.txt
I am using arduino 1.6.1 and my ano.ini file is as follows
[build]
board-model = arduino_due_x_dbg
cpu = atmega16u2

[upload]
board-model = arduino_due_x_dbg
cpu = atmega16u2
serial-port = /dev/cu.usbmodem1421

[serial]
serial-port = /dev/cu.usbmodem1421

I have had a look into the Arturo files to see if I can figure this out but it is way out of my league. I assume its a case of putting a clause it to check to see if we are using a Due or not.
Thanks for any time and effort in advance.

Hmm. Should be easy to add yet another config option ([sam|avr|intel|etc]). Do you have a repo I can pull to reproduce the error and I'll see if I can hack in a fix?

I have given you contributor access to the project. The Arturo project can be found at https://github.com/Swapnull/Olympus/tree/master/zeus.
Thanks

Huh. I found a hardcoded "AVR" that was using the wrong toolchain but when I fix this I still get the error. I'll dig deeper tonight. Thanks for the repo access.

Unfortunately the problems turned out to be more fundamental. The problem with Arturo v1 is that is forms its own command strings instead of using the ones from the Arduino SDK. because of this, even if you do find the right compiler, none of the other switches are correct.
Sorry to be the bearer of bad news. Arturo 2 would solve this but I still don't have a firm date for when I'll get around to finishing it.
You'll have to just switch to using the Arduino commandline if you can handle running Java in your environment:
https://github.com/arduino/Arduino/blob/ide-1.5.x/build/shared/manpage.adoc

Ah I see, thanks for looking anyway, I will try find some other way to
compile until Arturo 2 :)
On 10 February 2016 at 05:19, Scott Dixon<EMAIL_ADDRESS>wrote:

Closed #57 https://github.com/scottdarch/Arturo/issues/57.
—
Reply to this email directly or view it on GitHub
https://github.com/scottdarch/Arturo/issues/57#event-545315870.


[BUG] Default mask targets are not used when creating new segmentation annotation tasks

Describe the problem
The documentation states that datasets can have dataset.default_mask_targets or dataset.mask_targets here:
https://docs.voxel51.com/user_guide/using_datasets.html#storing-mask-targets
When creating a new segmentation task with FiftyOne without specifying mask_targets, classes 0-255 appear on CVAT.  I doubt this default behavior is intuitive for users and perhaps this should work like annotating classifications, where users must specify classes or the annotation run crashes.
dataset.take(2).annotate("masks8", label_field="asdf", label_type="segmentation")
Code to reproduce issue
In [5]: from fiftyone import zoo

In [6]: dataset = zoo.load_zoo_dataset("quickstart")
Dataset already downloaded
Loading 'quickstart'
 100% |█████████████████████████████████████████████████████████████████████████████████████████████| 200/200 [1.6s elapsed, 0s remaining, 122.7 samples/s]
Dataset 'quickstart' created

In [7]: dataset.default_mask_targets
Out[7]: {}

In [8]: dataset.take(2).annotate("jobbyjob", label_field="asdf", label_type="segmentation")

Computing metadata...
 100% |█████████████████████████████████████████████████████████████████████████████████████████████████| 2/2 [12.5ms elapsed, 0s remaining, 160.1 samples/s]
Uploading samples to CVAT...
Out[8]: <fiftyone.utils.cvat.CVATAnnotationResults at 0x7e5936062090>

System information

OS Platform and Distribution (e.g., Linux Ubuntu 22.04): Ubuntu 22.04.4 LTS
Python version (python --version): 3.11.8
FiftyOne version (fiftyone --version): 0.25.1
FiftyOne installed from (pip or source): source

Other info/logs
The following diff seems to resolve the problem, but thought I'd open the issue first as this is more of a API/information flow change than a bug perhaps...
diff --git a/fiftyone/utils/annotations.py b/fiftyone/utils/annotations.py
index 9639da8d0..430af375a 100644
--- a/fiftyone/utils/annotations.py
+++ b/fiftyone/utils/annotations.py
@@ -844,10 +844,14 @@ def _parse_classes_dict(
 def _get_mask_targets(samples, mask_targets, label_field, label_info):
     if "mask_targets" in label_info:
         mask_targets = label_info["mask_targets"]
-
+
+    # Check if we have defined a default mask target for the dataset
     if mask_targets is None:
-        mask_targets = {i: str(i) for i in range(1, 256)}
-        mask_targets[0] = "background"
+        if samples.default_mask_targets is not None:
+            mask_targets = samples.default_mask_targets
+        else:
+            mask_targets = {i: str(i) for i in range(1, 256)}
+            mask_targets[0] = "background"

     classes = [c for v, c in mask_targets.items() if v != 0]

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently
[x] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community
[ ] No. I cannot contribute a bug fix at this time

Hi @geke-mir 👋
I agree that it would be consistent with how the classes argument works if we did the following for the mask_targets argument:
When annotating new segmentation fields:
The user is required to provide mask_targets argument to annotate()
When annotating existing segmentation fields:
If the user doesn't provide mask_targets to annotate(), then:

use mask targets from dataset.mask_targets[label_field] if they exist
else fallback to dataset.default_mask_targets if those exist
else fallback to the current default of:

mask_targets = {i: str(i) for i in range(1, 256)}
mask_targets[0] = "background"

A PR would be fantastic if you're open to contributing it! 😄

Thanks, Brian!
https://github.com/voxel51/fiftyone/pull/4990


[BUG] Error when trying "Receive from metamask" (SepoliaETH)

Describe the bug
When trying to receive SepoliaETH via Metamask, I get an error as seen in the screenshot. Please note, that the selected network on Metamask is indeed "Sepolia".
Expected behavior
I should be able to receive funds from the connected Metamask if the selected network is correct.
Screenshots

Describe the bug When trying to receive SepoliaETH via Metamask, I get an error as seen in the screenshot. Please note, that the selected network on Metamask is indeed "Sepolia".
Expected behavior I should be able to receive funds from the connected Metamask if the selected network is correct.
Screenshots

Hello @marc0olo If you're getting an error while trying to receive SepoliaETH in MetaMask, it might be worth double-checking a few things. Make sure your wallet address is correct and that you have enough gas for the transaction. If everything looks good on your end and the problem persists, you might want to reach out to MetaMask support for help. They can provide more specific guidance based on the error message you're seeing.


Hello world

Basic hello world app
Please review @jyasskin @scheib @reillyeon

LGTM other than the above comments.

LGTM Discussed verbally some points, and suggested this be moved to a src/ directory in a follow up patch.


Flatten directory structure

Since the line between notebook and slides is blurry with the use of IPython for slides would be it acceptable to move the content of both the notebooks and slides directories into the root directory.  I think numbering the content to indicate the order would also be helpful.  I'll be happy to volunteer to do both if everyone approves.

Cool, no worries here.. I am also going to create a $PATH/data dir as
well.. I will be putting data in there but I will NOT submit a PR
changing paths to ./data/blah.wt until you submit your PR
When I make thumbdrives I will populate data with the data so that
everything can be done relative
On 9/10/15 2:45 PM, Jonathan J. Helmus wrote:

Since the line between notebook and slides is blurry with the use of
IPython for slides would be it acceptable to move the content of both
the notebooks and slides directories into the root directory. I think
numbering the content to indicate the order would also be helpful.
I'll be happy to volunteer to do both if everyone approves.
—
Reply to this email directly or view it on GitHub
https://github.com/openradar/AMS-Short-Course-on-Open-Source-Radar-Software/issues/12.

--
I ride for Parkinsons research http://www.events.org/sponsorship.aspx?id=51573

I have put one file in the new place and I will be doing a PR soon for the Gridding NB.. Once you have moved the other NBs I will then make some slight changes to the Birds NB to allow relative paths to data so people can run IPYNB from Thumbdrive

Sounds good, I think it should be possible for folks to run everything from the flash drive and not need to copy over to their machines.  Might be a bit slower for some IO but I don't think it will cause issues.

Moving and renaming complete in PR #20.  Paths in notebooks will now need to be fixed.  I'll work on mine shortly.


lnrpc: fix comment typo

i guess "creted" should be "created"

Looks good! Can you squash the commits into one? :)

squashed 🙌

make rpc had to be run with the correct proto version for the file to be generated correctly, so I did that for you: https://github.com/lightningnetwork/lnd/pull/2634


mypy: Remove typing ignores

This PR removes some type ignores for mypy that appear to be not necessary now, or can be removed after refactoring slightly.

I just merged #12939, can you rebase this on top of that?

@andersk Updated for different import style.
@timabbott Rebased.

This is great, merged, thanks @neiljp!


Change option name for disabling Jupyter Spawner from OdhDashboardConfig CR

In order to block users from spawning jupyter notebooks from the Jupyter spawner (i.e., Dashboard > Enabled page > Jupyter tile > Launch) we can disable the notebookController option in the OdhDashboardConfig CR:
  notebookController:
    enabled: false

Users can still use workbenches (create new one, launch existing one, etc), as I think it's expected. But if I'm not wrong, the workbenches use the notebook controller too, so maybe we could change the name of the option in the CR to avoid confusion.
What do you think?

Was working my way through the issues I moved from opendatahub-io/opendatahub-community repo (a generic logging spot).
Although I agree with Sven and Berto here, this is not likely something we will handle or change at this time.
We will need to rework our flags in general. We are also undergoing some rework with the new operator -- our config needs to get updated to support more component-separation model which may impact our configurations. TBD really, but doing this change is going to impact existing installations and it's going to just be a headache of moving things around while we are nearing a state of changing the dashboard config anyways (which is part of why it's still v1alpha1)
Related issues:

https://github.com/opendatahub-io/odh-dashboard/issues/1108
https://github.com/opendatahub-io/odh-dashboard/issues/1475

Migrated to:  https://issues.redhat.com/browse/RHOAIENG-1159


cookies

Cant figure out which cookies/how the cookies needed to be stored

Use the extension : Get cookies.txt LOCALLY
https://chromewebstore.google.com/detail/get-cookiestxt-locally/cclelndahbckbenkjhflpdbgdldlbecc?hl=fr&utm_source=ext_sidebar
Then Go to Linkedin.com , open the extension and click export
it should download a TXT file


[SPARK-43976][CORE] Handle the case where modifiedConfigs doesn't exist in event logs

What changes were proposed in this pull request?
This prevents NPE by handling the case where modifiedConfigs doesn't exist in event logs.
Why are the changes needed?
Basically, this is the same solution for that case.

https://github.com/apache/spark/pull/34907

The new code was added here, but we missed the corner case.

https://github.com/apache/spark/pull/35972

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.

cc @HyukjinKwon and @gengliangwang and @ulysses-you

lgtm, thank you @dongjoon-hyun

Thank you, @ulysses-you .

Could you review this when you have some time, please, @viirya ?

The error happens during loading the old event logs and I'm trying to avoid touching Store layers.

I mean the places where SQLExecutionUIData is created, and null is passed as the init value. For example:
https://github.com/apache/spark/blob/0cd5ca5a7b31f65a005c8ee2e90a6b4a29623ba7/sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala#L492
https://github.com/apache/spark/blob/0cd5ca5a7b31f65a005c8ee2e90a6b4a29623ba7/sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala#L515

Got it. I double-checked and found more usages
$ git grep '\.modifiedConfigs' | grep -v test | grep -v sessionState
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/ExecutionPage.scala:          executionUIData.modifiedConfigs.filterKeys(
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/ExecutionPage.scala:          executionUIData.modifiedConfigs.filterKeys(_.startsWith(pandasOnSparkConfPrefix)).toMap)
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala:          executionData.modifiedConfigs = sqlStoreData.modifiedConfigs
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala:    exec.modifiedConfigs = modifiedConfigs
sql/core/src/main/scala/org/apache/spark/status/protobuf/sql/SQLExecutionUIDataSerializer.scala:    if (ui.modifiedConfigs != null) {
sql/core/src/main/scala/org/apache/spark/status/protobuf/sql/SQLExecutionUIDataSerializer.scala:      ui.modifiedConfigs.foreach {

It's read from sqlStoreData.modifiedConfigs.
https://github.com/apache/spark/blob/8c6a54d70a79ecbbca45610b5d7dbf788e1e696d/sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala#L97

It's read from event.
https://github.com/apache/spark/blob/8c6a54d70a79ecbbca45610b5d7dbf788e1e696d/sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala#L344-L345

It's assigned manually.
https://github.com/apache/spark/blob/8c6a54d70a79ecbbca45610b5d7dbf788e1e696d/sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListener.scala#L363

In case of SQLExecutionUIDataSerializer, it loads from protobuf and it used null check.

https://github.com/apache/spark/blob/8c6a54d70a79ecbbca45610b5d7dbf788e1e696d/sql/core/src/main/scala/org/apache/spark/status/protobuf/sql/SQLExecutionUIDataSerializer.scala#L88

https://github.com/apache/spark/blob/8c6a54d70a79ecbbca45610b5d7dbf788e1e696d/sql/core/src/main/scala/org/apache/spark/status/protobuf/sql/SQLExecutionUIDataSerializer.scala#L37-L41

It seems that we have various ways to create SQLExecutionUIData. Given that, UI change is the minimal one.

Let me merge this. I believe this prevents NPEs from all generated cases ultimately.

Thank you, @viirya .


Update to include "Windows Virtual Desktop" service principal

Please update under "Assign the Desktop Virtualization Power On Contributor role with the Azure portal" - Include "Windows Virtual Desktop" alongside "Azure Virtual Desktop" for service principal as some tenants registered before it was called AVD. This can (and has) caused confusion.

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

ID: fac2ed89-73b2-b382-d331-bef4df300297
Version Independent ID: a4364f7a-f260-36db-b08e-08c5a3a4762c
Content: Set up Start VM on Connect for Azure Virtual Desktop
Content Source: articles/virtual-desktop/start-virtual-machine-connect.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@marinegeek23
Thanks for your feedback! We will investigate and update as appropriate.

@marinegeek23
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)


cmake build system

-Basic cmake build system added
-Test added to travis build script
-Minor changes to compile for MSVC

Thanks for the PR. This is great! @RAMitchell do you mind add a tutorial on how user can build with MSVC?


Create customer

Fixes #{issue number here}
Changes proposed in this pull request:

Thanks for this attempt to contribute, but I don't think we need this file.


Mod causing strange behavior with beds and doors

It took me a while to track this down to this mod because it was literally the last one I expected to be responsible for it, but I've tested a world with no mods, and the same world with only ToLaserBlade running, so it appears this is the culprit.
Essentially: when this mod is loaded, placing a bed down on the floor causes only the lower half of it to display. You can use the bed as normal, but in terms of minecraft physics it acts like only half a bed -- i.e., if you hit the block where the bed is visible, the bed reacts. If you hit the block where the second half should be (but isn't) the floor acts like it's getting hit.
The entire bed shows up if you leave and reload. Even with only half a bed you can still sleep in it.
The second issue has to do with doors. Basically, I can open a door and not be able to go through it. my character reacts as if I'm pushing against an invisible wall. If I open and close the door quickly a few times, I'll wind up in a situation where half the door is open, half the door is closed. A few more times and the door will open as normal and I'll be able to pass through.
I've attached screenshots of both issues.
I've only seen this in 1.14.4 - I also play 1.12.2 and it doesn't show up there.

Could you tell me the forge and mod versions?

This was fixed in version 1.14.4-<IP_ADDRESS>.
Please try it.

It appears to be fixed!


docs: include Roadmap

Description
As a user (or potential user) of the package, I would like to know the upcoming or possible features and what the team is working on. Is there any publically available documentation or board that indicates so?
Additional context

https://github.com/tensorflow/flutter-tflite/issues/64#issuecomment-1561965053 makes reference to the roadmap

Week @PaulTR mentioned this is mainly a community based project and there is no real roadmap see here
But for TF it seems like delegate support will be the major area of work from now on

Now that we're on 2.12, acceleration service and delegates are going to be the next big focus for features I think. I'll talk to product when they're ready to see what priorities should be from there as I ramp up on how this all works under the hood.

I am trying to get this running on desktop (#64) right now, if you have some MacOS experience that would be greatly appreciated.

So a quick update. I'm going to try and push for additional samples through a vendor we work with. I want to get the UI cleaned up on existing samples (scale images to take up full view area, support a live camera feed), then add additional samples based on ones that we already support for native Android and iOS, particularly:
Audio classification
Bert QA
Digit classifier
Gesture classification
Image segmentation
Model personalization (maybe)
Pose estimation
I also want to move the models to a remote location and download them at build time through a script for each example. My goal there is to reduce repo size going forward.

Maybe a simple solution would be to have a simple script just for us to execute before building the app.
Then we can put the assets/model/* path in .gitignore and remove it from here.
Here maybe for the text_classification example:
# Delete old models
rm -r assets/model/

# Create folder if not already exists
mkdir assets/model

# Download model
curl https://storage.googleapis.com/download.tensorflow.org/models/tflite/text_classification/text_classification.tflite \
    -o assets/model/text_classification.tflite

# Unzip model to get labels and vocab
unzip assets/model/text_classification.tflite \
    -d assets/model/


Tutorial on ONNX [part 1 of 3]

Tutorial on Inference using ONNX models

@safrooze @Ishitori see updated version

@safrooze are you happy with the changes? I need to add this tutorial to my other MXNet PR to have it tested

@safrooze ping


Implement unit tests

Implementing unit tests using the Polymer test framework.
The tests ensure the basic behaviors are working properly.

Also present in the rebase no?


Supporting emails with HTML content type

Hi,
thank you for the development of this OLM mailbox to EML converter.
If I understand correctly, the description says it can only output emails with HTML content type.
Is there a possibility to support plain text emails? Could you state the challenges with exporting plain text emails?
Thanks and best regards
hailigblechle

Thank you, it is not that challenging given the codebase I have already written, merely requiring a couple of extra lines. I hope to add the feature soon, and will get back to you when I do.

After further testing, the program is able to read and export plain-text emails at present, but only as HTML embedded within eml files. Does this meet your requirements?

I have made changes such that exported emails now contain plain-text, alongside any HTML content: https://github.com/PeterWarrington/olm-convert/commit/79273aa32b60c372b0c6605f3bd1cd9aa0edc281
For example, an exported EML file now looks like:
...
--B_1
Content-type: multipart/alternative;
	boundary="B_2"

--B_2
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

test

--B_2
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<b>test</b>
--B_2--
--B_1--

Does this meet your requirements?


onError fallback component

This which allows users to specify a fallback component, which is great for folks who do not want to fallback to a different image source. For example, users can have a "default profile" component that gets passed in as the fallback prop.
Related feature request:
https://github.com/KyleAMathews/react-gravatar/issues/134
Usage
const fallbackComponent =
Fallback!

return (
  <Gravatar email={email} size={40} default='404' className={s.avatar} fallback={fallbackComponent} />
)

This would be great


[Todoist] Due Dates One Day Behind

Extension
https://www.raycast.com/thomaslombart/todoist
Description
Due dates both in the menu bar and in the Raycast app are one day behind the actual set due date.
Steps To Reproduce

Open Todoist Raycast app
Task is one day behind set due date

Current Behaviour
One day behind set due date
Expected Behaviour
Show actual due date

Thanks for the feedback! Could you send some screenshots with the expected results? Would you mind sharing your timezone as well (there might be issues with it 😊)?

I've been having the same issue myself! Hope this helps.
Timezone: Eastern Standard Time (1:15pm at time of posting)
Menu bar:

Todoist app:

Thanks for the additional details. Unfortunately, I don't have any bandwidth for that at the moment. I'll eventually check it 😊

Not sure what changed, or when, but my Raycast UI and menu bar are showing due dates 1 day (24 hours) after the actual due date on the task. However, this is only happening when there's a time on the due date. If the due date is just a day then it works as expected.
(Todoist app)

(Raycast AI)

(menu bar)


Create a deployment manager and associated CLI

We want to make it as easy for people to launch their workflows in a llama-deploy system
To this end, we can

allow for yaml-config of workflows, control plane, message queue, etc.
create utils for parsing configs launching multiple deployments
creating a deployment manager server to manage your deployments

Closing as completed


Prometheus stucks on protection from Host Header Injection

What did you do?
I configured NGINX that:
    if ($host != $server_name) {
        return 444;
    }
    if ($http_host != $server_name) {
        return 444;
    }

And configured Prometheus on this target:
https://$server_name/mntr

If i'll try to run curl on this target, everything will be ok, and i'll get application metrics.
If i'll try to reload Prometheus config, i'll get it in a Error column: Get "https://$server_name:443/mntr EOF

I looked NGINX logs, and saw this:
"GET /mntr HTTP/1.1" 444 0 "-" "Prometheus/2.30.0" "-"
If i'll try to comment that NGINX block:
"GET /mntr HTTP/1.1" 200 0 "-" "Prometheus/2.30.0" "-"
I think, that's a bug. What request does Prometheus?
What did you expect to see?
I expected to see this answer from NGINX:  "GET /mntr HTTP/1.1" 200 0 "-" "Prometheus/2.30.0" "-"
What did you see instead? Under which circumstances?
I got: "GET /mntr HTTP/1.1" 444 0 "-" "Prometheus/2.30.0" "-"
When i configured my NGINX from Host Header Injection.
System information
Linux 4.15.0-20-generic x86_64
Prometheus version
prometheus, version 2.30.0 (branch: HEAD, revision: 37468d88dce85ac507f3fb7864c7d1c078e3e27d)
  build user:       root@e913c65aa170
  build date:       20210914-09:49:24
  go version:       go1.17.1
  platform:         linux/amd64

Prometheus configuration file
prometheus.yml:
  - job_name: federate
    honor_labels: true
    file_sd_configs:
    - files:
      - scrape/*.yml
    tls_config:
      ca_file: /etc/prometheus/cert.pem
    scheme: https

scrape/federate/targets.yml:
- targets:
  - $server_name
  labels:
    cluster: $server_name
    __metrics_path__: /mntr

Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

Hello!
I think, i've found the reason: $host = $server_name and $http_host = $server_name:443.
I'll try to change the rules in NGINX.


error in uploading a file through selenium webdriver in a Selenium grid architecture

Karate UI fails when trying to upload a file through selenium webdriver in a Selenium grid architecture.
All the details, the description of the issue, the instructions and a possible fix are in the README file inside the test project in attachment: test-upload-files-ui-karate.zip
The issue is linked to the question made in [https://stackoverflow.com/questions/60673922/]

@forlixdev thanks for the details. for now I'm tagging this as help wanted - I did a quick check as to how this LocalFileDetector works, but could not, so if anyone can provide pointers on how to implement this in Karate - that would help. Of course ideally we would love a PR :)
That said - note that Karate has an alternative architecture for distributed (or grid based) testing and you can find details here: https://github.com/intuit/karate/wiki/Distributed-Testing - and the advantage over Selenium is that your test always runs on the same node where the browser is.
Also note that we are working on karate-robot which can be used as a work-around when traditional file-upload automation fails, see: https://twitter.com/ptrthomas/status/1215534821234995200

I'll try to have a look on the source code and try to help even if to be honest my knowledge of Java is not as complete a developer one (I'm a tester).
Anyway in my java test I had to separate the behaviour when using a local or a remote webdriver, instantiating two different objects (example below). Maybe this workaround can by applied to karate as well depending on the webDriverUrl property in karate driver config, i.e. if webDriverUrl property is set it can be instantiated a RemoteWebDriver otherwise a proper webdriver (ChromeDriver, FirefoxDriver, etc)
WebDriver wd;
String grid = System.getProperty("grid", "false");
ChromeOptions chromeOptions = new ChromeOptions();
if (grid.equalsIgnoreCase("true")) {
   RemoteWebDriver rwd = new RemoteWebDriver(new URL(gridUrl), DesiredCapabilities.chrome());
   rwd.setFileDetector(new LocalFileDetector());
   wd = rwd;
} else {
   wd = new ChromeDriver(chromeOptions);
}

@forlixdev thanks ! tagging @paaco  and @djangofan if they have any experience in this area that can help. I am trying to understand what exactly does rwd.setFileDetector(new LocalFileDetector()); do - since Karate doesn't use a RemoteWebDriver at all.

Yes, I remember that I was forced to introduce a RemoteWebDriver in my class to let it work. I'll dig into the Selenium library to see if there's a workaround anyway.

@forlixdev I'm using the following one-liner helper to determine the full path:
* def getAbsolutePath = function(fname) { p = karate.properties['user.dir']+"\\"+fname; return (karate.os.type == 'windows') ? p : p.replace(/\\/g, "/") }
* def example = getAbsolutePath("uploads/files.jpg")

@ptrthomas I have no direct experience with Selenium grid, but the LocalFileDetector does little more than validating the given path is an existing local file.
The RemoteWebElement object of Selenium here triggers an upload for each valid file that sends an "uploadFile" command with the zipped contents of the file. I guess this will send it across the grid to the node.  See here: https://github.com/SeleniumHQ/selenium/blob/2a8d807214bf024c4897e97a5dd92bdc725b0b56/java/client/src/org/openqa/selenium/remote/RemoteWebElement.java#L111
Since Karate talks to (grid) webdriver directly by sending commands to the webDriverUrl, it never uploads anything to the node.

closing for now, note that karate.toAbsolutePath() has been implemented and will be available in 0.9.6.RC3 onwards
we have the following options for file upload:

use a multipart upload (recommended): https://stackoverflow.com/a/61393515/143475
use Chrome: https://github.com/intuit/karate/issues/1124
use Karate Robot: https://stackoverflow.com/a/61393515/143475
do it yourself for uploading a file to the Selenium Grid or contribute code to Karate (use this issue reference for a PR)


Cert signature algorithm parsing

👋
Use case:
I'm having a case now where I need to know if the certificate is using SHA1 as signature algorithm. SHA1 is deprecated in TLS 1.2 (*) and most browsers block certs signed with SHA1 (*). However Erlang's :ssl module does not validate signature algorithm.
Fix:
Added a field for signature_algorithm that returns the stringified version of :public_key.pkix_sign_types() for the cert.
Thank you for your review and consideration.

Hi there, thanks for the PR! This looks good to me, will merge it along with a few other PRs and let you know when this is publicly available.

Should be live! https://hex.pm/packages/easy_ssl/1.2.1
Thanks again


refactor: remove unnecessary setUnresolvedUrlToModule, and update types

Description
removed unnecessary _setUnresolvedUrlToModule(), and update a few of types.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[X] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the PR Title Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

We want to record the promise-resolved value for perf.


v0.1.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/294
After the above pull request is merged, it is recommended that you create
a tag on this repository for the registered package version:
git tag -a v0.1.1 -m "<description of version>" a62c1489612e400a905232462b4c3ab1a7356926
git push origin v0.1.1


testing: ods: clusters: support multiple sutest cluster types

/cc @kpouget

/test ?

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-ocp
On Thu, Jun 23, 2022 at 2:16 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/ods-jh-on-ocp 7820214
https://github.com/openshift-psap/ci-artifacts/commit/7820214bf748265a55203855677f4113cd16297d
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-ocp/1539940615704285184
true /test ods-jh-on-ocp
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=395.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/395#issuecomment-1164334792,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISE7F5DBSX7XJXJQIDVQRITFANCNFSM5ZUA2BZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-single
On Thu, Jun 23, 2022 at 7:37 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/ods-jh-on-ocp 247e009
https://github.com/openshift-psap/ci-artifacts/commit/247e0093338e9cd9ed5cbcdfd590d897a2f7257e
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-ocp/1539967126930984960
true /test ods-jh-on-ocp
ci/prow/ods-jh-on-single bd4a996
https://github.com/openshift-psap/ci-artifacts/commit/bd4a9960416cf0b3c44469c0c97d671fe2f0e11a
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-single/1540025984298782720
true /test ods-jh-on-single
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=395.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/395#issuecomment-1164689712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISTV67JWUVWQF4PNHDVQSOGDANCNFSM5ZUA2BZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

/test ods-jh-on-single
On Thu, Jun 23, 2022 at 7:53 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/ods-jh-on-ocp 247e009
https://github.com/openshift-psap/ci-artifacts/commit/247e0093338e9cd9ed5cbcdfd590d897a2f7257e
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-ocp/1539967126930984960
true /test ods-jh-on-ocp
ci/prow/ods-jh-on-single bd4a996
https://github.com/openshift-psap/ci-artifacts/commit/bd4a9960416cf0b3c44469c0c97d671fe2f0e11a
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-single/1540030172428767232
true /test ods-jh-on-single
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=395.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/395#issuecomment-1164704474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISZYFCPHMW32WOMXJLVQSQBVANCNFSM5ZUA2BZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-single

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-ocp

/test ods-jh-on-single
/test ods-jh-on-osd

/test ods-jh-on-osd
On Fri, Jun 24, 2022 at 5:59 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/ods-jh-on-osd fabbe6a
https://github.com/openshift-psap/ci-artifacts/commit/fabbe6a0786685e38d4208b0263d9b7ea77f2473
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-osd/1540343724238704640
true /test ods-jh-on-osd
ci/prow/ods-jh-on-single fabbe6a
https://github.com/openshift-psap/ci-artifacts/commit/fabbe6a0786685e38d4208b0263d9b7ea77f2473
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-single/1540343724297424896
true /test ods-jh-on-single
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=395.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/395#issuecomment-1165712076,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQITGGVAHFH4HCYM2XCLVQXLODANCNFSM5ZUA2BZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

/test ods-jh-on-osd
On Fri, Jun 24, 2022 at 10:59 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/ods-jh-on-single fabbe6a
https://github.com/openshift-psap/ci-artifacts/commit/fabbe6a0786685e38d4208b0263d9b7ea77f2473
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-single/1540343724297424896
true /test ods-jh-on-single
ci/prow/ods-jh-on-osd 79b4338
https://github.com/openshift-psap/ci-artifacts/commit/79b433826098b25cb56516d8ccf8c8dcd97dcb68
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/395/pull-ci-openshift-psap-ci-artifacts-master-ods-jh-on-osd/1540437394157735936
true /test ods-jh-on-osd
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=395.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/395#issuecomment-1165934264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIVXEMGW6ONS3IQXO7LVQYOUPANCNFSM5ZUA2BZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

The cluster launches went well:
-[x] jh-on-ocp passed \o/ with OCP+OCP clusters
-[x] jh-on-single test flaked, but single OCP cluster creation/destruction was OK
-[x] jh-on-osd test flaked, but OCP+OSD cluster creation/destruction was OK
Merging.


Can't to create new account

I have imported private key, and my default wallet is unlocked, but when I try to create a new account I get error:

and what was happened when I tried to create a hello account for my first smart contract

I've just created account, but not in mainnet...
if i run
nodeos --data-dir . --config-dir . -e --producer eosio
it is start new blocjchain and it is able to create a new accounts... but how can I do it on mainnet???

@SavostinVladimir  have you imported private keys of eosio account ? if not then must do it.

Use an account creation service to get an account on mainnet.  New accounts are always created by existing accounts and you don't control any existing account, so you can not create an account on mainnet.  Once you use a service to get and fund an account, you may use it to create further new accounts yourself.


GS-Form 'Waiting to save'

Like the Ace in PGManage, if the GS-Form doesn't save in five or so seconds it should have a red popup to let you know that there is an issue. Same with GS-Envelope and related.

It is working in the form, the CSS needs to be improved and we need to prevent it from coming up multiple times.

@michaeltocci
I have it working for GS-Form
Please test it here and let me know what needs to be added:
https://www.sunnyserve.com/env/app/developer_g/greyspots-1.1.1/test/new-datasheet/test-form.html

GS-Table is done, GS-Datasheet and GS-Envelope remain. Because GS-Table does not reload the template after a save the code needed modification.

GS-Datasheet and GS-Envelope are done, will be seen in next release.


load_pretrained_model dependency issues

I've been working on trying to get the Scivision example gallery notebooks running (#83, and I've come across an issue with load_pretrained_model that is causing some problems.
Running load_pretrained_model(<url>, allow_install=True), if the model is not present, currently force installs both the model and its dependencies. As I understand it, this was intended as an intentional feature to make sure that the dependencies were updated to the required versions (#223). However the force reinstalling of dependencies is leading to issues with some of the scivision-examples-gallery notebooks (e.g. scivision-basic-usage-example #5, plant-phenotyping-classification #8). In both these cases, running load_pretrained_model causes the latest version of packages (tensorflow and timm respectively) to be installed. However, these versions are causing the errors in running the notebooks.
There seem to be a couple of possible options to fix this:

Install the model separately, whether in the environment.yml or in the terminal before running the notebook
Update the model requirements.txt to a pinned version of the package
Change load_pretrained_model so it doesn't force reinstall dependencies by default

Does anyone have any preferences on which is the best option?

This is a good question, and a bit of a fundamental one for scivision! My opinion has been that installing models via the scivision package is too inherently problematic for reasons like this and we should no longer support this - see #346 (which proved controversial).
I think the tension here is we could either:

Make the postdocs notebooks just work somehow, e.g. one of @IFenton first two bullet points
Take some time to consider what scivision "best practice" should be for installing models in a Python environment, then conform all the project notebooks to this way of working (which could still be the first option, via enironment.yml)

There could even be a rule like "We only accept models for the scivision catalog that have pinned package versions" or as @ots22 has discussed previously, some kind of installation checks that run in GitHub actions

There are a few general issues with model-loading-as-package-installation as noted by Ed. Fixing this bug should at least let us maintain a reproducible environment without load_pretrained_model clobbering it, even without addressing these wider issues, so some comments in that spirit.
It might not be appropriate to completely pin dependencies in a model repository (or use a lockfile from the model if one exists) for the usual reasons - the right place to pin things would seem to be in the environment.yml in the gallery example.  A model should ensure that its dependencies are specified correctly.
We should pin the version of the model itself in the gallery example.  The options for doing that are:

as part of the load_pretrained_model command (e.g. include the commit hash when loading it)
in environment.yml (in this case, allow_install would not need to be set when loading the model)

We should allow for either possibility if we can: option 2 means someone running the model doesn't have the installation appearing inline, and option 1 if we want to explicitly show off this behaviour. (Some guidance on this could be useful to capture perhaps something like - when working interactively you might want to use allow_install=True but as soon as you start specifying dependencies in a virtual environment of some kind you should include your models there too - I'm not sure if that's right, but probably for a separate discussion.)
It seemed like (from our discussion the other day) the 'force' flag of pip is inherited when installing dependencies and this is the real culprit, since it is then no longer possible to use option 1 above (it might result in an 'upgraded' version of the package for instance, different from the version in environment.yml).  Have you tried passing the 'force' flag to pip only when allow_install='force'?  I think we had assumed that there was no downside to this flag if the package wasn't installed.
So I'd say it would be nice to end up with:

load_pretrained_model(..., allow_install=True) not clobbering versions of other packages in the environment if the environment is consistent with the model dependencies
having pinned versions of everything in the gallery examples, including the model - both options above should work - then make a decision separately about which is preferable

Did https://github.com/alan-turing-institute/scivision/pull/533 fix this?

It fixed the specific problem of force updating to the latest versions, although I think the broader discussion of how to handle the dependencies are still unresolved

Okay, will close based on having fixed the force install problem.
Is there a summary of the broader problem somewhere?


great-expectations>=0.14 causes commented_map missing error

I could not check if this has to do with Airflow 2.4.x, but I'm getting this error when using GreatExpectationsOperator with CheckpointConfig when using great-expectations>=0.14:
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - Exception in thread Thread-1:
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - Traceback (most recent call last):
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 209, in assert_valid_keys
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     _ = self[name]
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 73, in __getitem__
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return getattr(self, item)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 151, in commented_map
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return self._get_schema_validated_updated_commented_map()
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 125, in _get_schema_validated_updated_commented_map
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     commented_map: CommentedMap = copy.deepcopy(self._commented_map)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - AttributeError: 'CheckpointConfig' object has no attribute '_commented_map'
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -
During handling of the above exception, another exception occurred:
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - Traceback (most recent call last):
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 212, in assert_valid_keys
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     _ = self[f"_{name}"]
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 73, in __getitem__
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return getattr(self, item)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - AttributeError: 'CheckpointConfig' object has no attribute '_commented_map'
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -
During handling of the above exception, another exception occurred:
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - Traceback (most recent call last):
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     self.run()
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/threading.py", line 917, in run
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     self._target(*self._args, **self._kwargs)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/openlineage/airflow/listener.py", line 114, in on_running
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     **get_custom_facets(task, dagrun.external_trigger, task_instance_copy)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/openlineage/airflow/utils.py", line 265, in get_custom_facets
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     "airflow_version": AirflowVersionRunFacet.from_task(task),
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/openlineage/airflow/facets.py", line 34, in from_task
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     to_json_encodable(task),
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/openlineage/airflow/utils.py", line 101, in to_json_encodable
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return json.loads(json.dumps(task.__dict__, default=_task_encoder))
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/json/__init__.py", line 234, in dumps
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return cls(
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/json/encoder.py", line 199, in encode
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     chunks = self.iterencode(o, _one_shot=True)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/json/encoder.py", line 257, in iterencode
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return _iterencode(o, 0)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/openlineage/airflow/utils.py", line 99, in _task_encoder
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return str(obj)
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2883, in __str__
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     return self.__repr__()
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2862, in __repr__
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     json_dict: dict = self.to_json_dict()
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2850, in to_json_dict
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     dict_obj: dict = self.to_dict()
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 140, in to_dict
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     for key in self.property_names(
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 227, in property_names
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     assert_valid_keys(keys=exclude_keys, purpose="exclusion")
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -   File "/usr/local/lib/python3.9/site-packages/great_expectations/types/__init__.py", line 214, in assert_valid_keys
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING -     raise ValueError(
[2022-10-07, 19:23:04 UTC] {logging_mixin.py:117} WARNING - ValueError: Property "commented_map", marked for exclusion on object "<class 'great_expectations.data_context.types.base.CheckpointConfig'>", does not exist.

I don't see this error with >=0.15, but with 0.14.x, I see this additional error:
[2022-10-07, 19:46:14 UTC] {taskinstance.py:1851} ERROR - Task failed with exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/util.py", line 117, in instantiate_class_from_config
    class_instance = class_(**config_with_defaults)
TypeError: __init__() got an unexpected keyword argument 'site_names'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/great_expectations_provider/operators/great_expectations.py", line 142, in execute
    self.checkpoint = instantiate_class_from_config(
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/util.py", line 121, in instantiate_class_from_config
    class_name, format_dict_for_error_message(config_with_defaults)
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/util.py", line 165, in format_dict_for_error_message
    return "\n\t".join("\t\t".join((str(key), str(dict_[key]))) for key in dict_)
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/util.py", line 165, in <genexpr>
    return "\n\t".join("\t\t".join((str(key), str(dict_[key]))) for key in dict_)
  File "/usr/local/lib/python3.9/site-packages/great_expectations/core/config_peer.py", line 80, in __repr__
    return str(self.get_config())
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2130, in __str__
    return self.__repr__()
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2109, in __repr__
    json_dict: dict = self.to_sanitized_json_dict()
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2098, in to_sanitized_json_dict
    serializeable_dict = self.to_json_dict()
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/types/base.py", line 2088, in to_json_dict
    serializeable_dict: dict = convert_to_json_serializable(data=dict_obj)
  File "/usr/local/lib/python3.9/site-packages/great_expectations/core/util.py", line 161, in convert_to_json_serializable
    new_dict[str(key)] = convert_to_json_serializable(data[key])
  File "/usr/local/lib/python3.9/site-packages/great_expectations/core/util.py", line 161, in convert_to_json_serializable
    new_dict[str(key)] = convert_to_json_serializable(data[key])
  File "/usr/local/lib/python3.9/site-packages/great_expectations/core/util.py", line 256, in convert_to_json_serializable
    raise TypeError(
TypeError: <great_expectations.data_context.types.base.DatasourceConfig object at 0x7f4009f096a0> is of type DatasourceConfig which cannot be serialized.

Current environment:
apache-airflow==2.4.1
airflow-provider-great-expectations==0.1.5
great-expectations>=0.14
I confirmed that the same DAG works with great-expectations==0.13.49 (this requires pinning jinja2>=3.0.0,<3.1.0)

I think there were just some issues with great-expectations>=0.14,<0.15 and I had 0.13.49 pinned for a long time for this reason.


Feature/branding populate providers

Purpose
Needed for branded preprints (see Jira ticket)
Changes

changes from @hmoco under CenterForOpenScience/osf.io#6428
Updates to scripts/populate_preprint_providers.py

Side effects
N/A
Ticket
https://openscience.atlassian.net/browse/PREP-216

👍  - merged to feature/staging-2 and deployed


pear install ?

Hi, do you know how to install pear with fpm?
Thank you very much,

Hi @lryo,
I've not installed pear as I've switched to using composer for packages, but hopefully you'll find this useful.
https://jason.pureconcepts.net/2012/10/install-pear-pecl-mac-os-x/
Thanks,
Luke


introduce pages open-mss.github.io

Intro
We need a place better than the builtin wiki of github to share Proposals for the next google summer of code
And we have already in static markdown files which are used on all MSS servers
A quite similiar theme layout can be used by jekyll minima. I configured this for https://open-mss.github.io/
Because a common jekyll local installation will install newer packages than the github is using it is important to read these documentations before you start

https://github.com/github/docs/issues/2177
https://docs.github.com/en/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll

to create and serve on localhost:4000 before pushing please use

bundle exec jekyll serve

Next steps

optimize theme, e.g. add rtfd link on bottom, add logo
add markdown pages "getting started" questions
adding a dir with proposals in makdown
write regular blog posts ;)

Mail from github:
You are currently using the 'markdown' Markdown engine, which is no longer supported by GitHub Pages and may cease working at any time. To ensure your site continues to build, remove the 'markdown' setting in your site's '_config.yml' file and confirm your site renders as expected. For more information, see https://docs.github.com/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.

Mail from github:
You are currently using the 'markdown' Markdown engine, which is no longer supported by GitHub Pages and may cease working at any time. To ensure your site continues to build, remove the 'markdown' setting in your site's '_config.yml' file and confirm your site renders as expected. For more information, see https://docs.github.com/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.

introduced an exclude from navigation entry and added already some sample documents
https://open-mss.github.io/develop/
next is to add the GSOC related docs

introduced an exclude from navigation entry and added already some sample documents
https://open-mss.github.io/develop/
next is to add the GSOC related docs

site is prepared for the MSS suborg of the python-gsoc. requested our participation in the python-gsoc application.

site is prepared for the MSS suborg of the python-gsoc. requested our participation in the python-gsoc application.

remove server install from
https://open-mss.github.io/install/

apache2 setup needs to be decribed by ansible. Until is this is given we use the rtfd documentation

decribe options by docker

remove server install from
https://open-mss.github.io/install/

apache2 setup needs to be decribed by ansible. Until is this is given we use the rtfd documentation

decribe options by docker

cleanup wiki, remove all gesoc planning pages. keep results

cleanup wiki, remove all gesoc planning pages. keep results


added navbar

Signed-off-by: Debopriya Bhattacharjee<EMAIL_ADDRESS>Description
This PR fixes #6
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

@debo19 yesterday we discussed that in mobile view the nav-bar would come out from either the left or the right side and like it is right now.

Also font doesn't look good.

@debo19 I may be wrong but Ig it isn't responsive for all the mobile views??

@debjani1413 actually that's because of the footer and the other contents, they are not mobile responsive but the nav-bar seems to be.

@warunicorn19 oh yes, that may be the case, alright then, no issues @debo19 🥇

@warunicorn19 @debjani1413 @sayantan1413 Let me know if this structure looks fine. I'll do changes to the color (use theme) then.

@debo19 good stuff, merging this Right now, let's track the themes in a different PR.


Fastshap handling nominal variables

How does fastshap handle nominal variables?
`library(tidymodels)
library(tidyverse)
library(mlbench)
library(xgboost)
library(lightgbm)
library(treesnip)
data(Glass)
head(Glass)
Glass$Type
rec <-recipe(RI ~., data = Glass) %>% step_scale(all_numeric())
prep_rec <- prep(rec, retain = TRUE)
split <- initial_split(Glass)
train_data <- training(split)
test_data  <- testing(split)
model<-
parsnip::boost_tree(
mode = "regression"
) %>%
set_engine('lightgbm' , verbose = 0 )
wf_glass <- workflow() %>%
add_recipe(rec) %>%
add_model(model)
fit <- wf_glass %>% parsnip::fit(data =  train_data)
library(fastshap)
explain(object = fit %>% extract_fit_parsnip(), newdata = test_data %>% select(-RI) %>% as.matrix(), X = train_data %>% select(-RI) %>% as.matrix(), pred_wrapper = predict)`
This will lead to the following error : Error in genFrankensteinMatrices(X, W, O, feature = column) :    Not compatible with requested type: [type=character; target=double].
My guess :
This might be due to the fact that transforming a data.frame with different vector types  with as.matrix() will lead to a character matrix. This matrix can't be transformed to a matrix of type double without loosing the values of the factor columns here Type. On the other hand, as the error expresses, we can't use a numeric target for the regression task if all other variables are of class character.
Am I missing something or is this a possible transforming problem?

Closed this issue because this is the wrong page. I was looking for the R-package of this implementation fastshap


Pushing to heroku

How can I push my changes to heroku?

Brackets 1.2.0-15697 (linux), Git 1.9.1 & Brackets-Git 0.14.17

How do you do that usually from command line?

heroku login ...
heroku push

Ok, we'd need a special buttons to launch those commands, it's not supported yet.

I config Automatic deploys from GitHub


Tooltip Model documentation sounds not correct

Fixed #7591

I wonder if these were removed since 2.9 and need to be added to the migration guide or if the docs were incorrect in 2.9

I wonder if these were removed since 2.9 and need to be added to the migration guide or if the docs were incorrect in 2.9

My lib (last version) is based on 2.9.3 and it's using the model what we updated, therefore the 2.9.3 DOC is correct.

This update should be introduced because in version 3.0 the configuration elements have got the options property with the options (of course...).
Doing that, many properties of tooltip model in version 2.9.3 have been correctly removed because you can find into the options (for instance xPadding).
Maybe it could be mentioned in the migration guide. I didn't, sorry.

Ok, that makes sense. Do you mind adding a line to the migration guide as well?

@benmccann yes, I can do it.
Let me ask you if we can also add additional lines on migration doc.
For instance, as far as I have seen, Chart.scaleService is not available anymore and it should add as "was removed" from Chart.
Furthermore, it's not explain what you should use instead of scaleService.
It's not a problem to register new scale type because it's explained into "new Scale" doc but scaleService had got other methods, for instance updateScaleDefaults or getScaleDefaults.
From what I got to see, the scale defaults are now into Chart.defaults.scales but it's not written anywhere.

Ok, that makes sense. Do you mind adding a line to the migration guide as well?

@benmccann done! But please, have a look because my English could not be so good as you expect.

thanks!!


Documents dvc remote modify myremote sse for s3 remotes

See https://github.com/iterative/dvc/pull/2106

@dberenbaum thanks! I'll merge it after PR for DVC is merged.


Get CI Time under check. Aka CI takes waaayyy too long.

IMHO CI is taking way too long it takes forever to get feedback on PRs.
There are many culprits:

Priority of what GitHub action run first.

For example building docs and Bundle often first. I think those should start only if all unittests are passing.

Extremely long tests.

Windows Bundle creation (20 minute), I think should start only if unittests are passing, or run daily
test_conda_installer take 15% of the whole unit-test time. Maybe we should only run in on latest Python and not on all matrix items ?

Pinging @jaimergp

Thanks @Carreau, I very much like your suggestions!

test_conda_installer take 15% of the whole unit-test time. Maybe we should only run in on latest Python and not on all matrix items ?

This one will be removed with https://github.com/napari/napari/pull/5743

Windows Bundle creation (20 minute), I think should start only if unittests are passing, or run daily

If this one meant the Briefcase bundles, then see https://github.com/napari/napari/pull/5804

Related: https://github.com/napari/napari/issues/5473

A lot has changed this this was opened.
First: PR tests are now multistage so there is faster fail, see: https://github.com/napari/napari/pull/6156
Second, docs are done on CircleCI, so split from tests.
Finally, bundle and conda stuff has been removed.
While we should aim to improve CI efficiency, I'm going to close this issue as solved.


Cannot Generate Clean Captions With BLIP

AssertionError: /content/drive/MyDrive/datasets/universal/train/uncompleted/GT is not a valid directory
There doesn't seem to be a GT directory in the dataset you provided, what should I do?

For each degradation dataset, you should manually create GT and LQ directories. Then put the clean images into GT and put low-quality images into LQ.


Automated cherry pick of #9386: feat(region): support sync skus by cloudregion

Cherry pick of #9386 on release/3.6.
#9386: feat(region): support sync skus by cloudregion

Codecov Report

Merging #9389 (d86f9a2) into release/3.6 (b9d30c0) will increase coverage by 10.64%.
The diff coverage is 3.69%.

@@               Coverage Diff                @@
##           release/3.6    #9389       +/-   ##
================================================
+ Coverage         5.86%   16.51%   +10.64%
================================================
  Files              828       87      -741
  Lines           129133     9114   -120019
================================================
- Hits              7577     1505     -6072
+ Misses          120876     7477   -113399
+ Partials           680      132      -548

Flag
Coverage Δ

aFlag
16.51% <3.69%> (+10.64%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/conditions/nodataquery.go
0.99% <0.00%> (ø)

pkg/hostman/diskutils/nbd/driver.go
0.75% <0.75%> (ø)

pkg/monitor/alerting/conditions/suggestquery.go
2.00% <2.00%> (ø)

pkg/hostman/diskutils/nbd/lvmutils.go
4.93% <4.93%> (ø)

pkg/mcclient/modules/monitor/suggestsysrule.go
100.00% <100.00%> (ø)

pkg/util/bitmap/bitmap.go

pkg/compute/models/cloudprovidercapacities.go

pkg/appsrv/workers.go

pkg/compute/models/dynamicschedtags.go

... and 647 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 9b5f8ae...d86f9a2. Read the comment docs.


docker image size of kube-batch is too big

Use Alpine image instead of ubuntu:18.04 for building kube-batch docker image, this will reduce the size of docker image considerably
Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
docker image size is too big
What you expected to happen:
docker image should be small <10MB
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Maybe we could use scratch or other minimal image as base image?
cc @k82cn

a minimal image, e.g. alpine, should be enough for this case.

/assign


Show confirmation dialog when program admin changes statuses

Description
When confirmed, this dialog redirects to the newly-added updateStatus handler, which currently automatically redirects with success (and a TODO to implement).
Behind the scenes, a distinct modal is created for each status option, since each modal will have different content (including status name and whether to show an email checkbox if email is configured).
Modals are triggered by some custom JavaScript tied to the program application view which finds the modal associated with the selected status and displays it.
To support the "Cancel" option from the mocks, modal.ts was adjusted to use the cf-modal-close reference class rather than selecting based on a specific ID. The previous implementation overly constrained things such that there couldn't be multiple ways to dismiss a dialog.
Screenshots
Modal shown for status change with no email:

Modal shown for status change with email:

Toast after confirming the modal:

Release notes:
Describe the change as it should be communicated to partners in the release notes.
Checklist

[X] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[X] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
#2912

Codecov Report

Merging #3191 (647d3bd) into main (99f69df) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main    #3191      +/-   ##
============================================
- Coverage     78.48%   78.36%   -0.12%
  Complexity     2219     2219
============================================
  Files           280      280
  Lines          8914     8927      +13
  Branches        599      600       +1
============================================
  Hits           6996     6996
- Misses         1696     1709      +13
  Partials        222      222

Impacted Files
Coverage Δ

.../controllers/admin/AdminApplicationController.java
15.48% <0.00%> (-1.42%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Bugs when dequeue a 3-D input tensor from FIFOQueue

x = tf.random_normal([time_length, batch_size, feature_size], mean=0, stddev=1)
## prepare data
q = tf.FIFOQueue(capacity=4, dtypes=tf.float32)
enqueue_op = q.enqueue(x)
num_threads = 1
qr = tf.train.QueueRunner(q, [enqueue_op] * num_threads)
tf.train.add_queue_runner(qr)
inputs = q.dequeue()

As above code shows, when I use FIFOQueue and Cordinator to do input pipeline, the input is a 3-D tensor variable, but when I dequeue it from the FIFOQueue, errors comes:
ValueError: as_list() is not defined on an unknown TensorShape.

Thus, I go to the source code of FIFOQueue, I found that FIFOQueue.enqueue method doesn't use a shape function. So, I add a line of code as following, it works well.
x = tf.random_normal([time_length, batch_size, feature_size], mean=0, stddev=1)

## prepare data
q = tf.FIFOQueue(capacity=4, dtypes=tf.float32)
enqueue_op = q.enqueue(x)
num_threads = 1
qr = tf.train.QueueRunner(q, [enqueue_op] * num_threads)
tf.train.add_queue_runner(qr)
inputs = q.dequeue()
inputs.set_shape(x.get_shape())

But if I change my input from 3-D tensor into 2-D tensor, the code runs very well without set_shape function manually. So I want to know why my 3-D input tensor can't work well but 2-D tensor input work well? Can the source code of FIFOQueue or QueueBase support shape function?

@mrry, this seems like it could need fixing. Please take a look. Thanks!

Can you please share the entire stack trace for that ValueError? I can't see any calls to TensorShape.as_list() in the queue implementation.

@mrry Ok, my code is as follows:
q = tf.FIFOQueue(capacity=4, dtypes=tf.float32)
enqueue_op = q.enqueue(x)
num_threads = 1
qr = tf.train.QueueRunner(q, [enqueue_op] * num_threads)
tf.train.add_queue_runner(qr)
inputs = q.dequeue()
#inputs.set_shape(x.get_shape())
y = tf.reduce_mean(tf.reduce_sum(inputs, axis=0), axis=1, keep_dims=True)
labels = tf.cast(tf.greater(y, 0), tf.int32)

## build model
sequence_length = tf.Variable([time_length]*batch_size, dtype=tf.int32)
cell_fw = LSTMCell(num_units=hidden_size)
cell_bw = LSTMCell(num_units=hidden_size)
outputs, state = tf.nn.bidirectional_dynamic_rnn(
      cell_fw=cell_fw,
      cell_bw=cell_bw,
      inputs=inputs,
      sequence_length=sequence_length,
      dtype=tf.float32,
      time_major=True)

error is
Traceback (most recent call last):
  File "test1.py", line 32, in <module>
    time_major=True)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/rnn.py", line 350, in bidirectional_dynamic_rnn
    time_major=time_major, scope=fw_scope)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/rnn.py", line 546, in dynamic_rnn
    dtype=dtype)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/rnn.py", line 615, in _dynamic_rnn_loop
    const_time_steps, const_batch_size = inputs_got_shape[0].as_list()[:2]
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/tensor_shape.py", line 761, in as_list
    raise ValueError("as_list() is not defined on an unknown TensorShape.")
ValueError: as_list() is not defined on an unknown TensorShape.

and I think the error is caused by BLSTM, so maybe the set_shape bug can be fixed.

This doesn't sound like a bug (in the queues, at least). The actual error is in the tf.nn.bidirectional_dynamic_rnn() code, which does not seem to support inputs with unknown shape; the solution is to provide more static shape information.
When you create a tf.FIFOQueue with no shapes argument, you are allowing the queue to store tensors of any shape. Therefore, since when you create the q.dequeue() op we don't know exactly which tensors will be dequeued, we have to give it an unknown shape.
By calling inputs.set_shape(x.get_shape()) you are asserting that all elements have a particular shape. You could have done the same thing by creating the queue as:
q = tf.FIFOQueue(capacity=4, dtypes=tf.float32, shapes=x.get_shape())

@mrry Thank you a lot, I understand now.

Glad to help clear things up!


Extending user model to store additional attributes?

I am deploying the UAA

using a bosh release I downloaded from bosh.io

What did you expect to see? What goal are you trying to achieve with the UAA?
Add app specific custom attributes to UAA user model.
Hi, I came across an old issue regarding this. Was wondering if this has changed?

This is a much-needed feature. User model should be allow to add custom attributes

I know that this feature is often requested, therefore I simply answer, please propose it via PR and then we can discuss it, because I agree, community asks for this

Thanks @strehle . Created PR


Improving README

Readme script works with other image sizes, has comments, uses PIL instead of OpenCV, and returns image labels in same dimension as original image

LGTM


Registering DiscordCommandClient & Discord does not run in the same script

example here :
$discord = new Discord([
	'token' => '***',
	'loadAllMembers' => TRUE
]);

$discordCommands = new DiscordCommandClient([
	'token'  => '***',
	'prefix' => '!',
	'name'   => 'TestBot'
]);

$discordCommands->run();
$discord->run();

how can i run both loops ?

Actually i solved this issue by removing $discord variable
and use only DiscordCommands because it is extending the Discord Class