tokenizer.pad_token_id is None

The first training stage, tokenizer.pad_token_id is None. It seems need to add tokenizer.pad_token_id = (
0  # unk. we want this to be different from the eos token
)
after get the tokenizer.

You are right.
The base model of llama does not have pad_token_id. We need to manually set it to 0 after getting the tokenizer.
We will fix this bug in train_stage1.py


falcon-node-sensor-push context in the EKS docs

https://github.com/CrowdStrike/Cloud-AWS/blob/65ba8bf488133f1fa3a45b1ac6697c60f928a6df/container/kernel-eks-implementation-guide.md?plain=1#L138
In the EKS docs, there is mention of a falcon-node-sensor-push script but no context about where you get it.
This may relate to as it may come as part of that container image.

that's correct, it is part of the container image:
https://github.com/CrowdStrike/cloud-tools-image

Closing this issue as we no longer support these tools from this repo. Either Skopeo should be used directly or the container script from github.com/crowdstrike/falcon-scripts should be used.


Progress indicator for loading large images

Hi I am using cropper for editing large images in my web app. Is there a way to show some kind of progress indicator in the cropper canvas when loading is taking long time?

Just add a loading state by yourself. (hide the loading in built event)


Update doc.go

04:30 every day is "TZ=Asia/Tokyo 30 04 * * *". There was an extra star.

Sorry for the long silence; this has since been fixed.


[MM-27249] Add telemetry to team and channel pages

Summary
Adds the following telemetry events

Count of members successfully added / removed / promoted / demoted via team config page
Count of members successfully added / removed / promoted / demoted via channel config page
Event when a channel is successfully archived or unarchived
Events for any filter applied to the channels listing listed below:

'public_filter_applied_to_channel_list'
'private_filter_applied_to_channel_list'
'archived_filter_applied_to_channel_list'
'group_sync_filter_applied_to_channel_list'
'manual_invites_filter_applied_to_channel_list'
'team_id_filter_applied_to_channel_list'

Event when a filter is applied for each role on the channel or team config page members block eg. channel_admin_filter_applied_to_members_block or system_admin_filter_applied_to_members_block

Ticket Link

https://mattermost.atlassian.net/browse/MM-27249

Since @fmunshi is not available today, I will merge and cherry-pick this PR.

/cherry-pick release-5.26


Add ability to monitor selection changed events

The first commit adds the ability to be notified of selection changed events from Scintilla.
The second commit shows how this could be used in a workspace to highlight text equal to the selection.

The builds are failing as it appears that https authentication is broken at GitHub. I'm unable to push over https, although ssh works. The FetchVM script is downloading a released VM over https, and fails immediately.

Upgrading Git for Windows fixed the https issue for me because it upgraded the credential manager. I'll have to look at the AppVeyor issue.

I've rebased your PR on top of master with the AppVeyor build fix. Hopefully it will pass build validation now.

I appreciate the code review and comments and will take a look...

I think I've incorporated the feedback and feel like it is cleaner. More comments welcome!


version [3.1.X] is not working with latest vuetify and cli

So i've been trying to use this module in latest vuetify setup when I try to use.
It shows me error in console saying that this.$vuetify is undefined in this module.
it's working till version 3.0.0 without some props like preset, preset-label etc but on latest versions it's breaking. here is my console error

some module usage snippet
Plugin
`
//VuetifyDatePicker
import VuetifyDaterangePicker from "vuetify-daterange-picker";
Vue.use(VuetifyDaterangePicker)
`
main.js
import "vuetify-daterange-picker/dist/vuetify-daterange-picker.css"
some-component.vue
 <v-daterange ..../>

i have same issue

On initial inspection it doesn't look like a bug in the component at all.
Read more - https://github.com/yariksav/vuetify-confirm/issues/9
It looks like something has changed about how vuetify gets installed and in vuetify's code and this.$vuetify is undefined.
Can you please put your App.vue, main.js and vuetify plugin installation code?

I somehow seem to have fixed it in 3.1.6.
It's a weird thing and I am not sure of is right or wrong.
I had to remove vue, vuetify, and date-fns from dependencies and add them to peerDependencies. But then doing yarn added them back to dependencies.
So, I had to do an npm install those three modules and then remove the generated package-lock.json so i would still have them in my node modules but not in dependencies.
Then built and published.
Can you all try the 3.1.6 release and see if that solves?

I moved to devDependencies so I can do dev work and still not get into a localVue vs globalVue conflict.
This should have been very obvious that I need to use devDependences for dev work
Ref -
https://github.com/praveenpuglia/vuetify-daterange-picker/commit/a55a7c94d8c22d367a269feba0a69ac1ea3884a0

I somehow seem to have fixed it in 3.1.6.
It's a weird thing and I am not sure of is right or wrong.
I had to remove vue, vuetify, and date-fns from dependencies and add them to peerDependencies. But then doing yarn added them back to dependencies.
So, I had to do an npm install those three modules and then remove the generated package-lock.json so i would still have them in my node modules but not in dependencies.
Then built and published.
Can you all try the 3.1.6 release and see if that solves?

@praveenpuglia the date-fns seem to be a dependency, though, as adding the vuetify-daterange-picker@3 now breaks build:
This dependency was not found:
* date-fns in ./node_modules/vuetify-daterange-picker/dist/vuetify-daterange-picker.common.js

To install it, you can run: npm install --save date-fns

That is correct. It is because I expect the application developer to install that library. And that is because I want one single version of date-fns being used in case the author also wants to use date-fns for other parts of the application.


COME ON GUYS LETS DO IT!!!!!!!!!!

I'm really disappointed in Bl. After mcpe 0.15.0 update it will send me a message Block launcher is stopped. Come on guys put the one star in Google play and tell to friends to do the same!!!!!IF THE ISSUE WILL BE FIXED THEN WE REMOVE OUR 1 STAR!!!!!

Plz, close this report because, were spending more time dealing with reports than fixing Blocklauncher.
Thx!

Plus making threats is a good way to loose the issue reporting feature!

Adding a 1 star does not FIX anything.  It is being worked on and takes time.  If you do not like it, revert from 0.15 to 0.14.3, which is the version of BL that matches what is in the Play Store (1.12.8).
I do not know why you are so surprised.  It always takes 2-3 weeks after a new release is finalized before BL is updated.

Zed, degrading the Minecraft Pocket Addition dident work on my city gen Amazon Fire?

@lowjames I'm not sure what you mean. If you use TitaniumBackup you can swap to whatever version you saved. Since the OFFICIAL version is released, I'm not sure you can revert to anything, only update to <IP_ADDRESS>, which is the same as 0.15.0, except that it updated the shaders to help issues such as:
https://bugs.mojang.com/browse/MCPE-14621

Huh...

@lowjames I am not sure what you are asking.  If you have already updated to 0.15+ and have not made a backup of the previous version using something like TitaniumBackup, you will not be able to downgrade.  The way the stores work, you can only go forward.  The other point I made, people are saying 0.15.0 or 0.15.1.  They are essentially the SAME thing from a features perspective.  The only difference was the stock shaders were modified to correct the blocks from showing up BLACK or SPARKLE colored.

Oh


[Bugfix] Resolved issue with message input box margin and send button alignment.

Purpose

Resolved issue with message input box margin
Resolved issue with send button alignment.

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Pull request checklist
This PR has considered:

[ ] Color Theming
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] View Data Injection
[ ] Demo App UI/UX update

How to Test

Open...
Click on...

What to Check

Before
After

Screenshot or description before this change
Screenshot or description with this change

Other Information

this feels like duplicate PR with #575 with some additional margin changes

You're right. I was just waiting for John's PR to go in first and I was going to merge.

this feels like duplicate PR with #575 with some additional margin changes

Should be fixed now


Fixed #27637 -- Fixed timesince, timeuntil in leap year edge case.

Ticket 27637.

Could you add release notes for 1.10, and possibly 1.9? I'd be for pushing the fix in 1.9, too, unless Tim is opposed to that.

I added release notes.

Thanks for review.


Villagers' catchphrases in wrong language.

I tried changing the villagers in Korean version of Animal Crossing: New Leaf Welcome amiibo. I left the default settings. They seem to change okay, but their catchphrases change to the English version instead of Korean.

The editor doesn't have a database for korean strings, that's why they appear in english by default.
Unfortunately, I currently don't have time to data mine the korean files.

How do you go about data mining the file?


Mock more of the Glue Data Catalog APIs

This expands on #1750  and adds some more APIs (much easier to have a base to work on! As pointed out in #1561)
This adds some of the missing Get/Update/Create APIs relating to the Glue data catalog -- but not yet all of them, and improves some of the error handling/edge cases when tables or DBs don't exist etc.

Coverage decreased (-0.4%) to 92.2% when pulling d92351a7777f7224cd364cab75408e862fdccb29 on ashb:expand-glue-catalog-mocking into dfa7935e13e6065810d6fc4e1edbf3e86499aea5 on spulec:master.

Coverage decreased (-0.4%) to 92.2% when pulling d92351a7777f7224cd364cab75408e862fdccb29 on ashb:expand-glue-catalog-mocking into dfa7935e13e6065810d6fc4e1edbf3e86499aea5 on spulec:master.

100% coverage on the moto/glue/* files now. I'm not sure why coverals is reporting a drop in coverage -  unless it's a bit noisy some times?
PTAL when you have a spare moment @spulec

This is great; thanks for your help!


Fix bug in UHF 2dm cumulant

Contraction of vvVV block with eris when nvira xor nvirb is zero, fails.
Added check to skip that contribution when necessary.

Thanks for reporting! Can you verify that the alternative fix I pushed also works for your case?

Yeah, that works too.
I've added the autoconversion of ROHF to UHF to this PR as well.

I've added the autoconversion of ROHF to UHF to this PR as well.

OK great. Alternatively, the conversion could be done in qemb.init_mf, which is called by all subclasses.

That was how I tried to do it initially but setting is_rhf, is_uhf and spinsym appropriately didn't work. Maybe there is some other key attribute I missed.

You wouldn't need to set these - anyway this way is fine too

Codecov Report
Base: 66.92% // Head: 66.85% // Decreases project coverage by -0.06% :warning:

Coverage data is based on head (554e0b6) compared to base (7505c05).
Patch coverage: 56.75% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage   66.92%   66.85%   -0.07%
==========================================
  Files         108      108
  Lines       16106    16124      +18
  Branches     2336     2282      -54
==========================================
+ Hits        10779    10780       +1
- Misses       4694     4714      +20
+ Partials      633      630       -3

Impacted Files
Coverage Δ

vayesta/rpa/rirpa/NI_eval.py
75.79% <44.44%> (-1.42%)
:arrow_down:

vayesta/core/fragmentation/cas.py
84.90% <52.94%> (-15.10%)
:arrow_down:

vayesta/rpa/rirpa/RIRPA.py
58.42% <66.66%> (-0.38%)
:arrow_down:

vayesta/core/ao2mo/helper.py
74.62% <100.00%> (+0.07%)
:arrow_up:

vayesta/solver/solver.py
51.48% <0.00%> (-0.50%)
:arrow_down:

vayesta/core/util.py
72.35% <0.00%> (-0.30%)
:arrow_down:

vayesta/ewf/ewf.py
63.93% <0.00%> (-0.25%)
:arrow_down:

vayesta/core/vlog.py
81.10% <0.00%> (-0.15%)
:arrow_down:

vayesta/mpi/rma.py
28.66% <0.00%> (ø)

vayesta/misc/cubefile.py
21.62% <0.00%> (ø)

... and 4 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Please use more meaningful branch name than fix in future - thanks :+1:


Node v12 and preserve-symlinks/-main flags

Description
With newer versions Node flags can be written with "-" or "_":
f.e. --abort-on-uncaught-exception  <==> --abort_on_uncaught_exception
The same rule works for the two Node flags

--preserve-symlinks (since v6.3.0) <==> --preserve_symlinks
--preserve-symlinks-main (since v10.2.0) <==> --preserve_symlinks_main

Mocha treats both flags as special cases, since they haven't been part of process.allowedNodeEnvironmentFlags before Node v12.
Description of the Change
Update unit test.
Applicable issues
closes #3896

Coverage increased (+0.07%) to 91.742% when pulling abd460058d538f0379a77e1ea2ec8f254cc93d3f on juergba/issue/3896 into ef69b73941a54456e0551893ac2e686cd5ee47b6 on master.