PushFileService(): u'...' is not in local cache

ansible_tests
Python: 2.6
MODE=ansible VER=<IP_ADDRESS>
PLAY [integration/action/transfer_data.yml] ************************************

TASK [file path=/tmp/transfer-data, state=absent] ******************************
ok: [target-debian-1]
ok: [target-centos6-2]
ok: [target-centos7-3]

TASK [action_passthrough method=_transfer_data, kwargs={u'data': {u'I am JSON': True}, u'remote_path': u'/tmp/transfer-data'}] ***
ok: [target-debian-1]
ok: [target-centos6-2]
ok: [target-centos7-3]

TASK [slurp src=/tmp/transfer-data] ********************************************
ok: [target-debian-1]
ok: [target-centos6-2]
ok: [target-centos7-3]

TASK [assert that=out.content|b64decode == '{"I am JSON": true}'
] *************
ok: [target-debian-1] => {
  changed: False
  failed: False
  msg: All assertions passed
}
ok: [target-centos6-2] => {
  changed: False
  failed: False
  msg: All assertions passed
}
ok: [target-centos7-3] => {
  changed: False
  failed: False
  msg: All assertions passed
}

TASK [action_passthrough method=_transfer_data, kwargs={u'data': u'I am text.', u'remote_path': u'/tmp/transfer-data'}] ***
ok: [target-debian-1]
ok: [target-centos6-2]
ok: [target-centos7-3]

TASK [slurp src=/tmp/transfer-data] ********************************************
ok: [target-debian-1]
ok: [target-centos6-2]
ok: [target-centos7-3]

TASK [assert that=out.content|b64decode == 'I am text.'] ***********************
ok: [target-debian-1] => {
  changed: False
  failed: False
  msg: All assertions passed
}
ok: [target-centos6-2] => {
  changed: False
  failed: False
  msg: All assertions passed
}
ok: [target-centos7-3] => {
  changed: False
  failed: False
  msg: All assertions passed
}

TASK [file path=/tmp/transfer-data, state=absent] ******************************
changed: [target-debian-1]
changed: [target-centos6-2]
changed: [target-centos7-3]

PLAY [integration/async/multiple_items_loop.yml] *******************************

TASK [start long running ops _raw_params={{item}}, _uses_shell=True] ***********
changed: [target-debian-1] => (item=sleep 3; echo hi-from-job-1)
changed: [target-centos6-2] => (item=sleep 3; echo hi-from-job-1)
changed: [target-debian-1] => (item=sleep 5; echo hi-from-job-2)
changed: [target-centos7-3] => (item=sleep 3; echo hi-from-job-1)
changed: [target-centos6-2] => (item=sleep 5; echo hi-from-job-2)
ERROR! [pid 6600] 03:30:05.909573 E mitogen.ctx.fork.78: mitogen: PushFileService(): u'/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/ansible/modules/commands/command.py' is not in local cache
changed: [target-centos7-3] => (item=sleep 5; echo hi-from-job-2)

TASK [Ensure static files are collected and compressed jid={{ item.ansible_job_id }}] ***
FAILED - RETRYING: Ensure static files are collected and compressed (30 retries left).
FAILED - RETRYING: Ensure static files are collected and compressed (30 retries left).
FAILED - RETRYING: Ensure static files are collected and compressed (30 retries left).
changed: [target-centos7-3] => (item={'_ansible_parsed': True, u'changed': True, '_ansible_no_log': False, u'ansible_job_id': u'c4c986b8f062476f', 'item': u'sleep 3; echo hi-from-job-1', u'started': 1, '_ansible_item_result': True, 'failed': False, u'finished': 0, '_ansible_ignore_errors': None})
changed: [target-centos6-2] => (item={'_ansible_parsed': True, u'changed': True, '_ansible_no_log': False, u'ansible_job_id': u'b09812d810d2da58', 'item': u'sleep 3; echo hi-from-job-1', u'started': 1, '_ansible_item_result': True, 'failed': False, u'finished': 0, '_ansible_ignore_errors': None})
changed: [target-debian-1] => (item={'_ansible_parsed': True, u'changed': True, '_ansible_no_log': False, u'ansible_job_id': u'83670a2c6dcbef75', 'item': u'sleep 3; echo hi-from-job-1', u'started': 1, '_ansible_item_result': True, 'failed': False, u'finished': 0, '_ansible_ignore_errors': None})
FAILED - RETRYING: Ensure static files are collected and compressed (30 retries left).
changed: [target-centos6-2] => (item={'_ansible_parsed': True, u'changed': True, '_ansible_no_log': False, u'ansible_job_id': u'd990415a4afb0a7c', 'item': u'sleep 5; echo hi-from-job-2', u'started': 1, '_ansible_item_result': True, 'failed': False, u'finished': 0, '_ansible_ignore_errors': None})
changed: [target-debian-1] => (item={'_ansible_parsed': True, u'changed': True, '_ansible_no_log': False, u'ansible_job_id': u'7977e7b38737064e', 'item': u'sleep 5; echo hi-from-job-2', u'started': 1, '_ansible_item_result': True, 'failed': False, u'finished': 0, '_ansible_ignore_errors': None})
FAILED - RETRYING: Ensure static files are collected and compressed (29 retries left).
failed: [target-centos7-3] (item={'_ansible_parsed': True, u'changed': True, '_ansible_no_log': False, u'ansible_job_id': u'42e3e0acea84d390', 'item': u'sleep 5; echo hi-from-job-2', u'started': 1, '_ansible_item_result': True, 'failed': False, u'finished': 0, '_ansible_ignore_errors': None}) => {
  ansible_job_id: 42e3e0acea84d390
  attempts: 3
  changed: False
  failed: 1
  finished: 1
  invocation: {
    module_args: {
      jid: 42e3e0acea84d390
      mode: status
    }
  }
  item: {
    ansible_job_id: 42e3e0acea84d390
    changed: True
    failed: False
    finished: 0
    item: sleep 5; echo hi-from-job-2
    started: 1
  }
  msg: Job reached maximum time limit of 15 seconds.
}

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
target-centos6-2           : ok=130  changed=31   unreachable=0    failed=0
target-centos7-3           : ok=133  changed=31   unreachable=0    failed=1
target-debian-1            : ok=135  changed=41   unreachable=0    failed=0

Trigger nasty process pileup ------------------------------------------- 86.62s
Ensure static files are collected and compressed ----------------------- 15.23s
Gathering Facts --------------------------------------------------------- 4.60s
Find regular homedir ---------------------------------------------------- 0.78s
Find out root's homedir. ------------------------------------------------ 0.66s
Get auth token ---------------------------------------------------------- 0.52s
Try writing to temp directory for the readonly_homedir user ------------- 0.51s
Create file tree -------------------------------------------------------- 0.34s
start long running ops -------------------------------------------------- 0.25s
Copy files from content: arg -------------------------------------------- 0.15s
Command exited with non-zero status 2
71.73user 8.36system 2:22.72elapsed 56%CPU (0avgtext+0avgdata 105956maxresident)k
1256inputs+2528outputs (6major+1883940minor)pagefaults 0swaps
travis_time:end:0958507e:start=1549769260347002334,finish=1549769421345887159,duration=160998884825
The command ".ci/${MODE}_tests.py" exited with 1.

travis_fold:start:cache.2
store build cache
travis_time:start:10ccba38
travis_time:end:10ccba38:start=1549769421351499492,finish=1549769421355115951,duration=3616459
travis_time:start:1034d390
nothing changed, not updating cache
travis_time:end:1034d390:start=1549769421359668746,finish=1549769424013813097,duration=2654144351
travis_fold:end:cache.2

Done. Your build exited with 1.

Seeing a similar error on a new run after upgrading to v0.2.4.
TASK [workers : Label worker node] ***********************************************************************
Sunday 10 February 2019  17:30:20 -0800 (0:00:00.481)       0:01:19.315 *******
ERROR! [pid 121839] 17:30:27.787325 E mitogen.ctx.ssh.kube-master: mitogen: PushFileService(): '/home/jmreicha/.pyenv/versions/3.7.0/lib/python3.7/site-packages/ansible/modules/commands/command.py' is not in local cache
ERROR! [pid 121839] 17:30:27.788915 E mitogen.ctx.ssh.kube-master: mitogen: PushFileService(): '/home/jmreicha/.pyenv/versions/3.7.0/lib/python3.7/site-packages/ansible/modules/commands/command.py' is not in local cache

I'm looking at this right now. It's a regression due to 'fixing' redundant
transfers of Ansible modules.
On Mon, 11 Feb 2019 at 17:07, Josh Reichardt<EMAIL_ADDRESS>wrote:

Seeing a similar error on a new run after upgrading to v0.2.4.
TASK [workers : Label worker node] ***********************************************************************
Sunday 10 February 2019  17:30:20 -0800 (0:00:00.481)       0:01:19.315 *******
ERROR! [pid 121839] 17:30:27.787325 E mitogen.ctx.ssh.kube-master: mitogen: PushFileService(): '/home/jmreicha/.pyenv/versions/3.7.0/lib/python3.7/site-packages/ansible/modules/commands/command.py' is not in local cache
ERROR! [pid 121839] 17:30:27.788915 E mitogen.ctx.ssh.kube-master: mitogen: PushFileService(): '/home/jmreicha/.pyenv/versions/3.7.0/lib/python3.7/site-packages/ansible/modules/commands/command.py' is not in local cache
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dw/mitogen/issues/532#issuecomment-462409155, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAJCz3BovWqr-hYsbmlv3zFxHn7fzNfks5vMaNNgaJpZM4ay4nK
.

sorry for the hassle, this is on master now :) New release by Monday at the latest. Thanks for letting me know this was hurting you

This is now on the master branch and will make it into the next release. To be updated when a new release is made, subscribe to https://www.freelists.org/list/mitogen-announce
Thanks for reporting this!


Backfill SafeGraph 7-day averages, HRRs, and MSAs to cover entire time period

Actual Behavior:
#332 introduced SafeGraph 7dav signals; #416 also added HRR and MSA aggregation. However, these were not backfilled for the entire history of SafeGraph data, resulting in this:
                        signal geo_type   min_time
9         completely_home_prop   county 2019-01-01
10        completely_home_prop      hrr 2020-11-01
11        completely_home_prop      msa 2020-11-01
12        completely_home_prop    state 2019-01-01
13   completely_home_prop_7dav   county 2020-10-01
14   completely_home_prop_7dav      hrr 2020-11-01
15   completely_home_prop_7dav      msa 2020-11-01
16   completely_home_prop_7dav    state 2020-10-01

Expected behavior

All SafeGraph signals have consistent min_time across geographic levels.

hrr_completely_home_prop* (including 7dav) files from before 20201101, msa_completely_home_prop* (including 7dav) files from before 20201101, state_completely_home_prop_7dav* files from before 20201001, and county_completely_home_prop_7dav* files from before 20201001 are dropped into receiving/ and should be picked up tomorrow

hrr_completely_home_prop* (including 7dav) files from before 20201101, msa_completely_home_prop* (including 7dav) files from before 20201101, state_completely_home_prop_7dav* files from before 20201001, and county_completely_home_prop_7dav* files from before 20201001 are dropped into receiving/ and should be picked up tomorrow

This should be resolved. Not sure metadata has updated yet though.

This should be resolved. Not sure metadata has updated yet though.

I don't expect meta to finish until 3. In the meantime your update comment is suspiciously light -- are the completely_home signals the only ones updated? I think Alex's quote was supposed to just be an example; we really do want all safegraph signals to go back to 1/2019.
The database shows the following, if that helps:
MariaDB [epidata]> select `signal`,geo_type,min(time_value) start from covidcast where source="safegraph" group by `signal`,geo_type order by start;
+-------------------------------+----------+----------+
| signal                        | geo_type | start    |
+-------------------------------+----------+----------+
| completely_home_prop_7dav     | msa      | 20190101 |
| completely_home_prop_7dav     | hrr      | 20190101 |
| median_home_dwell_time        | county   | 20190101 |
| completely_home_prop_7dav     | county   | 20190101 |
| completely_home_prop          | state    | 20190101 |
| completely_home_prop          | msa      | 20190101 |
| part_time_work_prop           | state    | 20190101 |
| completely_home_prop          | hrr      | 20190101 |
| completely_home_prop          | county   | 20190101 |
| restaurants_visit_prop        | state    | 20190101 |
| bars_visit_prop               | state    | 20190101 |
| part_time_work_prop           | county   | 20190101 |
| restaurants_visit_prop        | msa      | 20190101 |
| bars_visit_prop               | msa      | 20190101 |
| full_time_work_prop           | state    | 20190101 |
| restaurants_visit_prop        | hrr      | 20190101 |
| bars_visit_prop               | hrr      | 20190101 |
| restaurants_visit_prop        | county   | 20190101 |
| bars_visit_prop               | county   | 20190101 |
| restaurants_visit_num         | state    | 20190101 |
| bars_visit_num                | state    | 20190101 |
| full_time_work_prop           | county   | 20190101 |
| restaurants_visit_num         | msa      | 20190101 |
| bars_visit_num                | msa      | 20190101 |
| restaurants_visit_num         | hrr      | 20190101 |
| bars_visit_num                | hrr      | 20190101 |
| restaurants_visit_num         | county   | 20190101 |
| bars_visit_num                | county   | 20190101 |
| median_home_dwell_time        | state    | 20190101 |
| completely_home_prop_7dav     | state    | 20190101 |
| part_time_work_prop_7d_avg    | county   | 20200901 |
| full_time_work_prop_7d_avg    | state    | 20200901 |
| full_time_work_prop_7d_avg    | county   | 20200901 |
| median_home_dwell_time_7d_avg | state    | 20200901 |
| median_home_dwell_time_7d_avg | county   | 20200901 |
| completely_home_prop_7d_avg   | state    | 20200901 |
| completely_home_prop_7d_avg   | county   | 20200901 |
| part_time_work_prop_7d_avg    | state    | 20200901 |
| part_time_work_prop_7dav      | state    | 20201001 |
| part_time_work_prop_7dav      | county   | 20201001 |
| full_time_work_prop_7dav      | state    | 20201001 |
| full_time_work_prop_7dav      | county   | 20201001 |
| median_home_dwell_time_7dav   | state    | 20201001 |
| median_home_dwell_time_7dav   | county   | 20201001 |
| median_home_dwell_time        | msa      | 20201101 |
| median_home_dwell_time        | hrr      | 20201101 |
| part_time_work_prop_7dav      | msa      | 20201101 |
| part_time_work_prop_7dav      | hrr      | 20201101 |
| full_time_work_prop_7dav      | msa      | 20201101 |
| part_time_work_prop           | msa      | 20201101 |
| full_time_work_prop_7dav      | hrr      | 20201101 |
| part_time_work_prop           | hrr      | 20201101 |
| full_time_work_prop           | msa      | 20201101 |
| full_time_work_prop           | hrr      | 20201101 |
| median_home_dwell_time_7dav   | msa      | 20201101 |
| median_home_dwell_time_7dav   | hrr      | 20201101 |
+-------------------------------+----------+----------+

I don't expect meta to finish until 3. In the meantime your update comment is suspiciously light -- are the completely_home signals the only ones updated? I think Alex's quote was supposed to just be an example; we really do want all safegraph signals to go back to 1/2019.
The database shows the following, if that helps:
MariaDB [epidata]> select `signal`,geo_type,min(time_value) start from covidcast where source="safegraph" group by `signal`,geo_type order by start;
+-------------------------------+----------+----------+
| signal                        | geo_type | start    |
+-------------------------------+----------+----------+
| completely_home_prop_7dav     | msa      | 20190101 |
| completely_home_prop_7dav     | hrr      | 20190101 |
| median_home_dwell_time        | county   | 20190101 |
| completely_home_prop_7dav     | county   | 20190101 |
| completely_home_prop          | state    | 20190101 |
| completely_home_prop          | msa      | 20190101 |
| part_time_work_prop           | state    | 20190101 |
| completely_home_prop          | hrr      | 20190101 |
| completely_home_prop          | county   | 20190101 |
| restaurants_visit_prop        | state    | 20190101 |
| bars_visit_prop               | state    | 20190101 |
| part_time_work_prop           | county   | 20190101 |
| restaurants_visit_prop        | msa      | 20190101 |
| bars_visit_prop               | msa      | 20190101 |
| full_time_work_prop           | state    | 20190101 |
| restaurants_visit_prop        | hrr      | 20190101 |
| bars_visit_prop               | hrr      | 20190101 |
| restaurants_visit_prop        | county   | 20190101 |
| bars_visit_prop               | county   | 20190101 |
| restaurants_visit_num         | state    | 20190101 |
| bars_visit_num                | state    | 20190101 |
| full_time_work_prop           | county   | 20190101 |
| restaurants_visit_num         | msa      | 20190101 |
| bars_visit_num                | msa      | 20190101 |
| restaurants_visit_num         | hrr      | 20190101 |
| bars_visit_num                | hrr      | 20190101 |
| restaurants_visit_num         | county   | 20190101 |
| bars_visit_num                | county   | 20190101 |
| median_home_dwell_time        | state    | 20190101 |
| completely_home_prop_7dav     | state    | 20190101 |
| part_time_work_prop_7d_avg    | county   | 20200901 |
| full_time_work_prop_7d_avg    | state    | 20200901 |
| full_time_work_prop_7d_avg    | county   | 20200901 |
| median_home_dwell_time_7d_avg | state    | 20200901 |
| median_home_dwell_time_7d_avg | county   | 20200901 |
| completely_home_prop_7d_avg   | state    | 20200901 |
| completely_home_prop_7d_avg   | county   | 20200901 |
| part_time_work_prop_7d_avg    | state    | 20200901 |
| part_time_work_prop_7dav      | state    | 20201001 |
| part_time_work_prop_7dav      | county   | 20201001 |
| full_time_work_prop_7dav      | state    | 20201001 |
| full_time_work_prop_7dav      | county   | 20201001 |
| median_home_dwell_time_7dav   | state    | 20201001 |
| median_home_dwell_time_7dav   | county   | 20201001 |
| median_home_dwell_time        | msa      | 20201101 |
| median_home_dwell_time        | hrr      | 20201101 |
| part_time_work_prop_7dav      | msa      | 20201101 |
| part_time_work_prop_7dav      | hrr      | 20201101 |
| full_time_work_prop_7dav      | msa      | 20201101 |
| part_time_work_prop           | msa      | 20201101 |
| full_time_work_prop_7dav      | hrr      | 20201101 |
| part_time_work_prop           | hrr      | 20201101 |
| full_time_work_prop           | msa      | 20201101 |
| full_time_work_prop           | hrr      | 20201101 |
| median_home_dwell_time_7dav   | msa      | 20201101 |
| median_home_dwell_time_7dav   | hrr      | 20201101 |
+-------------------------------+----------+----------+

Ah ok I misunderstood, sorry about that. I thought it was just the ones in the original comment. I'll drop the rest in now.

Ah ok I misunderstood, sorry about that. I thought it was just the ones in the original comment. I'll drop the rest in now.


Support for Deuterocanon

Is your feature request related to a problem? Please describe.
Firstly, can I thank you for this brilliant plugin. It has been really good helping me move over from Joplin. However as a Catholic, I am missing 7 books from my Bible! I am using the NRSV Catholic Edition version and I am still unable to fetch text from the book of Judith, the books of the Maccabees, Wisdom, etc. (however may I thank you again for including the NRSV? Thank you!)
Describe the solution you'd like
I would like the deuterocanonical books ('apocrypha') to be available. The ecumenical edition of the NRSV for example includes the following books variously used by Catholics and orthodox, some by different groups of orthodox only:

1 Esdras
2 Esdras
1 Maccabees
2 Maccabees
3 Maccabees
4 Maccabees
Additions to Daniel
Additions to Esther
Baruch
Judith
Letter of Jeremiah
Prayer of Manasseh
Psalm 151
Sirach
Tobit
Wisdom

Describe alternatives you've considered
(Not relevant)
Additional context
The NRSVCE does include some of these books if you look on some websites, but I would be keen to see the NRSV Ecumenical Edition so we could access the Orthodox books also (sometimes just the regular NRSV includes the Orthodox books, as on BibleGateway.com).
Once again, thank you for such a great and useful plugin.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Still ongoing.

Hi @shivermetim
Thanks for the feedback, the issue here is that bible gateway does not offer an API.


2.0.181018003 causing crash in 1803 or lower

Describe the bug
Updating my UWP app to use the latest package (2.0.181018003) causes app crashes in all versions of Windows below 1809. Upon further inspection, the 2.0.181018003 package apparently requires 1809 or higher.
Steps to reproduce the bug
Steps to reproduce the behavior:

Set your target version to 1803 or lower.
Go to your app's nuget package manager and update Microsoft.UI.Xaml to 2.0.181018003

Expected behavior
I thought that the packages were backwards compatible? So I was expecting that updating to 2.0.181018003 will not cause crashes in 1803 or lower. I could be wrong, so please correct me if I am!
Screenshots

Version Info

NuGet package version:
Microsoft.UI.Xaml 2.0.181018003
Windows 10 version:

[ ] Insider Build (xxxxx)
[ ] October 2018 Update (17763)
[x] April 2018 Update (17134)
[x] Fall Creators Update (16299)
[x] Creators Update (15063)
[x] Anniversary Update (14393)

Device form factor:

[x] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Additional context

Daniel,
Just like the screenshot said, it requires 1809 or higher as TargetPlatformVersion. Microsoft.UI.Xaml doesn’t support a lower version as target version.
My question is why do you set target version to 1803?
If you want the app to run on 1803 os and above, you just set min version to 1803. And target version to 1809. Then your app works on any version of Windows in the range from Minimum Version to Target Version
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Daniel Paulino<EMAIL_ADDRESS>Sent: Monday, October 22, 2018 8:38:41 PM
To: Microsoft/microsoft-ui-xaml
Cc: Subscribed
Subject: [Microsoft/microsoft-ui-xaml] 2.0.181018003 causing crash in 1803 or lower (#11)
Describe the bug
Updating my UWP app to use the latest package (2.0.181018003) causes app crashes in all versions of Windows below 1809. Upon further inspection, the 2.0.181018003 package apparently requires 1809 or higher.
Steps to reproduce the bug
Steps to reproduce the behavior:

Set your target version to 1803 or lower.
Go to your app's nuget package manager and update Microsoft.UI.Xaml to 2.0.181018003

Expected behavior
I thought that the packages were backwards compatible? So I was expecting that updating to 2.0.181018003 will not cause crashes in 1803 or lower. I could be wrong, so please correct me if I am!
Screenshots
[image]https://user-images.githubusercontent.com/7649589/47333915-ac7aa980-d639-11e8-9505-73c5475a3103.png
Version Info
NuGet package version:
Microsoft.UI.Xaml 2.0.181018003
Windows 10 version:

Insider Build (xxxxx)
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)
Anniversary Update (14393)

Device form factor:

Desktop
Mobile
Xbox
Surface Hub
IoT

Additional context
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/microsoft-ui-xaml/issues/11, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AF_9BIHaSNraWoRTo7__cnGHuS-8SzXsks5uno9BgaJpZM4X0o58.

The readme lists following OS as  supported, which none of the available NuGet packages fulfill:

Supported OS versions
Windows Insider Preview (17135+)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)
Anniversary Update (14393)

After further investigation, I have identified the crash to be something else. It's still related to Microsoft.UI.XAML and versioning but it's not as I described originally. Closing issue.

Windows SDK 17763 (1809) is available to install and target your projects, you don't need 1809 to run (that's what min version is for).


Expand num_class from pretrained model

Hi everyone,
I want to use the pretrained model "TPS-RestNet-BiLSTM-Att-case-sensitive.pth" and fine tune it with more characters, like '£' or '€' and ' ' (space).
I use the --sensitive custom with my new character set but I got a size mismatch in the attention layer (rnn, weights, and bias) even with the --FT option due to the increase in the cardinal of opt.characters. If I only swap some characters, like '^' -> '£' , everything is still fine.
Is there any simple way to copy the model and only expand the number of target classes, to avoid loosing all the information learned during pre training ? Should I simply reinitialize the attention layer ?
Otherwise I understand I'll have to train from scratch with my custom character list.
Let me know if you need any additional information.
Thanks again for this amazing software !

Hey!
I'm facing the same problem and I don't have a lot of data neither computational power, I would like to know if you train your model with spaces and '€', '£' and if you can share it!
Thank you in advance!

same problem! i want to train with many characters and use weight from pretrained model (TPS-RestNet-BiLSTM-Att-case-sensitive.pth)
So, How i can do that!
Thanks!


Document weakref to slot class

This adds a paragraph to the documentation that includes the method
described by @Tinche in #174 for making a slot class weak-referenceable.
Pull Request Check List
This is just a reminder about the most common mistakes.  Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!

[ ] Added tests for changed code.
[ ] New features have been added to our Hypothesis testing strategy.
[ ] Updated documentation for changed code.
[x] Documentation in .rst files is written using semantic newlines.
[ ] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
[ ] Changes (and possible deprecations) are documented in CHANGELOG.rst.

If you have any questions to any of the points above, just submit and ask!  This checklist is here to help you, not to deter you from contributing!

Thanks!


Review: Component/Child Code

There is the beginnings of a component pattern in Tyrian (inherited) that is not connected to anything, nor is it featured in the examples - not even the sub component example.
Suspect it's heading towards halogen style component nesting. It isn't needed for anything but we should decide what to do with it. Keep it and make it work, or remove it.

Removed! Could bring it back later.


Tournamentality

Refactoring the underpinnings of our multiplayer simulation architecture to better support esports leagues.

Merging this into our qa-hoc-2020 branch to centralize bug fixes and the status of next.codecombat.com


Do  not have any change

hi
In template project when i change icon or add some components I do not have any change
Plesase direction me

Can you please explain more in detail what you are trying to achieve ?


Fixed broken build-and-release link

Notes for Reviewers
This PR fixes #7394

fixed broken build and release link on project/releases

Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 1955e7b7c5223dcb2121834e0bdd112455e49b8f at: https://642027477164c01671f56678--meshery-docs-preview.netlify.app

please have a review.
@Chadha93 @Nikhil-Ladha @leecalcote

Thanks @adarshrajpathak :rocket:


pkgs.darktable: 1.6.9 -> 2.0.0

See http://www.darktable.org/2015/12/darktable-2-0-released/
Nixpkgs already have PR #11982 about this subject.
In a discussion, @ikervagyok (the author of the related PR) suggested to take this variant over his: https://github.com/lancelotsix/nixpkgs/commit/5354617c9096ae22aa4221782007b2539c369344#commitcomment-15354657
Considering the absence of activity on PR #11982, I propose this one as drop-in replacement. One of the two PR should be closed.
cc @nckx @rickynils @flosse

Merged with changes adding wrapGAppsHook and gnome3.adwaita-icon-theme in c5379e7


VoyagerServiceProvider Class There are some design issues.

Laravel Version: 5.5.36
Voyager Version: v1.0.16
PHP Version:7.1.9
Database Driver & Version:5.6.29

Description:
vendor/tcg/voyager/src/VoyagerServiceProvider.php:331
            VoyagerFacade::addFormField("TCG\\Voyager\\FormFields\\{$class}");
vendor/tcg/voyager/src/VoyagerServiceProvider.php:334
        VoyagerFacade::addAfterFormField(DescriptionHandler::class);
There is a small problem you want to submit to voyager.
register  method of VoyagerServiceProvider Class:
/**
* Register the application services.
*/
public function register()
{
$this->app->register(VoyagerEventServiceProvider::class);
$this->app->register(ImageServiceProvider::class);
$this->app->register(WidgetServiceProvider::class);
$this->app->register(VoyagerHooksServiceProvider::class);
$this->app->register(DoctrineSupportServiceProvider::class);

    $loader = AliasLoader::getInstance();
    $loader->alias('Voyager', VoyagerFacade::class);

    $this->app->singleton('voyager', function () {
        return new Voyager();
    });

    $this->loadHelpers();

    $this->registerAlertComponents();
    $this->registerFormFields();
    $this->registerWidgets();

    $this->registerConfigs();

    if ($this->app->runningInConsole()) {
        $this->registerPublishableResources();
        $this->registerConsoleCommands();
    }

    if (!$this->app->runningInConsole() || config('app.env') == 'testing') {
        $this->registerAppCommands();
    }
}

registerFormFields  method of VoyagerServiceProvider Class:
protected function registerFormFields()
    {
        $formFields = [
            'checkbox',
            'color',
            'date',
            'file',
            'image',
            'multiple_images',
            'number',
            'password',
            'radio_btn',
            'rich_text_box',
            'code_editor',
            'markdown_editor',
            'select_dropdown',
            'select_multiple',
            'text',
            'text_area',
            'timestamp',
            'hidden',
            'coordinates',
        ];
        foreach ($formFields as $formField) {
            $class = studly_case("{$formField}_handler"); VoyagerFacade::addFormField("TCG\\Voyager\\FormFields\\{$class}");
        }

        VoyagerFacade::addAfterFormField(DescriptionHandler::class);

        event(new FormFieldsRegistered($formFields));
    }

Just finished loading, it should be used in registerFormFields inside.
             $ this-> app-> make ('voyager') -> addFormField ("TCG \\ Voyager \\ FormFields \\ {$ class}");

         $ this-> app-> make ('voyager') -> addAfterFormField (DescriptionHandler :: class);

When we replace VoyagerServiceProvider, the original call addFormField method and addAfterFormField method, they will not take effect.

It could be splitted into multiple methods for easier overwriting.
We are open to pull requests.

Probably happened many times, but please explain, I beg you.
Class 'TCG \ Voyager \ VoyagerServiceProvider' not found
I have the / vendor folder in the root, and I have a folder with in the laravel project which is in /public_html/site.сom/vendor.
There is an installation in / vendor to the root.
How to install a voyager in the c / laravel folder
thanks

@smartcoder01 Sorry, my version at the time was: Voyager Version: v1.0.16

@smartcoder01 but , u can to install Voyager in your project, u need a document of Voyager.

This is a project I have a long time ago, I think you need to install the latest version of Voyager, you can view its related documentation, this address is: https://docs.laravelvoyager.com/getting-started/installation

Why you can't find the file, maybe because you didn't execute it: php artisan vendor:publish --provider="TCG\Voyager\VoyagerServiceProvider" @smartcoder01

I hope this will help you. If you have been unable to solve it, I can provide remote assistance for you. You can communicate with me by email. I hope to promote the ecology of Voyager.
My email address is<EMAIL_ADDRESS>@smartcoder01

@t0rjan, can this one be closed? It's quite old and sidetracked by @smartcoder01 posting unrelated questions.

@fletch3555 Yes, although I hope to help him, it does not matter what I posted.

Understandable. I'm just trying to keep threads focused, and he posted the same comment on a number of super old issues


improved remove dubbogo config file

What this PR does:
improved remove dubbogo config file
Which issue(s) this PR fixes:
#3
Fixes #

Codecov Report

Merging #37 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #37   +/-   ##
========================================
  Coverage    79.43%   79.43%
========================================
  Files            6        6
  Lines          214      214
========================================
  Hits           170      170
  Misses          33       33
  Partials        11       11

Impacted Files
Coverage Δ

pkg/config/config_load.go
53.94% <0.00%> (ø)

Continue to review full report at Codecov.

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

Can it merge?


[api-docs] Fix markdown fail in Thread Member docs (#5505)

A new commit was made into the api-docs repo: https://github.com/discord/discord-api-docs/commit/3ff0e4e55126ed47c9064457a2a1128209425e7f

Fix markdown fail in Thread Member docs

Update docs/resources/Channel.md

Co-authored-by: ckohen<EMAIL_ADDRESS>Co-authored-by: ckohen<EMAIL_ADDRESS>This is a bot created issue.

Why is this even an issue?

Just, uhm, ye bot created .-.


Add copy ingest processor

Description
This PR adds a new ingest processor called copy processor which can copy the whole object from one existing field to another field, this is useful when users want to copy a nested field to the root level and then delete the original field, this cannot be achieved by set processor because it doesn't support copying object, only basic data types are supported. In addition, even though script processor can be used to copy object, but writing painless script is not easy for users. The copy processor provides an easy way to copy object.
The usage of copy processor are as follows:
POST _ingest/pipeline/_simulate
{
  "pipeline": {
    "processors": [
      {
        "copy": {
          "source_field": "{{foo}}",
          "target_field":"target",
          "ignore_missing":true,
          "override_target":true,
          "remove_source":true
        }
      }
    ]
  },
  "docs": [
    {
      "_version_type":"external_gte",
      "_version": 1,
      "_source": {
        "foo":"a",
        "a": {
          "c":"1"
        },
        "target":1
      }
    }
  ]
}

, the result is:
{
  "docs": [
    {
      "doc": {
        "_index": "_index",
        "_id": "_id",
        "_version": "1",
        "_version_type": "external_gte",
        "_source": {
          "foo": "a",
          "target": {
            "c": "1"
          }
        },
        "_ingest": {
          "timestamp": "2024-01-12T13:44:27.287123Z"
        }
      }
    }
  ]
}

.
Both the source_field and target_field support template snippets, and there are three extra parameters:

ignore_missing: if true, exit quietly when source_field doesn't exist or has a empty field path, defaults to false
override_target: if true, override the value of target_field if it already exists, defaults to false
remove_source: if true, remove the source_field after the copy operation, defaults to false

Related Issues
https://github.com/opensearch-project/OpenSearch/issues/10134
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM

@gaobinlong -- thanks for doing this! I really like this approach.
Can you link to the document issue for the new processor?

Thanks, I've done that, and I'll open a document PR for this processor.

Anything remaining here? Can we merge?

Do you want this in 2.x? Backport?

Do you want this in 2.x? Backport?

Yeah, see this PR has been backported to 2.x yet, thank you all @dblock @msfroh @deshsidd.

New flaky tests https://github.com/opensearch-project/OpenSearch/issues/11974


Move admin routers from /admin to /-/admin

Resolve #32181

Maybe move it to /-/admin/ instead so in the future some others could be moved/added there as well?

Test failures are related

Seems like a breaking change?

Seems like a break change?

If the user always uses the menu to enter the admin page, it should not be considered as a break change.

Conflicts caused by my PR have been resolved.