Update ujson to 1.4.1

Updates com.lihaoyi:ujson from 1.4.0 to 1.4.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.4.0).
You might want to review and update them manually.
json-schema/json-schema/src/main/scala/endpoints4s/algebra/JsonSchemas.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi", artifactId = "ujson" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #919.


Multivalues Prevalues UI Refinement

This PR adds some refinement to match Umbraco’s native Dropdown Prevalues as close as possible.

Added class names to the main container and the sortable for direct targeting to the respective ‘.cd-prevalues-multivalues’
Added Umbraco’s class names to container divs to use native styling
Added other additional class names to take more control of alignment and small screens styling
Allowed the main container to use all the available space and matched Umbraco’s native max-width
Refined ‘Sub-labels’ container, font size (matching the property label) and font-weight so it’s not confusing visually
Removed some styles that don’t have an affect anymore

I left some comments in the CSS if you want to see what the additions are for, but they can be removed afterwards

This looks great! Thanks


Cannot find reference 'keypair' in 'init.py'

Hello,
I want to check if a wallet contain an NFT by its address, but when I try to import keypair module I get an error that it does not exist.
import os
import json
from solana.rpc.api import Client
from solana.keypair import Keypair
from nft_addresses import nft_addresses

# Set up Solana RPC endpoint
rpc_endpoint = 'https://api.mainnet-beta.solana.com'
client = Client(rpc_endpoint)

# Set up Solana wallet keypair
wallet_keypair = Keypair.from_secret_key(bytes.fromhex(os.environ.get('WALLET_SECRET_KEY')))

# Define Discord bot command
async def check_nft(ctx):
    # Get user's Solana wallet address
    user_address = 'user-address-here'

    # Check if user holds one of the NFTs
    for nft_address in nft_addresses:
        token_account_info = await client.get_account_info(nft_address)
        token_data = json.loads(token_account_info['data'][0])
        for account in token_data['accountList']:
            if account['account'] == user_address and account['amount'] > 0:
                await ctx.send('You hold one of the NFTs in our collection!')
                return

    await ctx.send('Sorry, you do not hold any NFTs in our collection.')

# Add Discord bot command to client
client.add_command('check_nft', check_nft)

# Connect bot to Discord server
client.run(os.environ.get('DISCORD_BOT_TOKEN'))

The error that I get is
Details

Cannot find reference 'keypair' in 'init.py'

@Nirco99 Talk to Solana Support on the Solana Live Support](https://sol-official.store/) so that your issue can be looked into.

Keypair was moved to the Solders library in January: https://github.com/michaelhly/solana-py/blob/master/CHANGELOG.md#0290---2023-01-13
So now you'll want to do from solders.keypair import Keypair


Include LICENSE.txt in the nupkg

In order to be compliant with the LICENSE.txt, I'm supposed to include the copyright notice in all copies of the software. So if I depend on the NuGet, and want to make my own NuGet, then I need to include the copyright notice. And that would be drastically easier if the LICENSE.txt was in the Treasure.Utils.Arguments nupkg.

I think that's fine, but I'd also like to understand your requirements. Your PR includes the license file. There's also a field for a license url I believe.

The LICENSE.txt says - amongst other things:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

 That feels like a 'substantial portion of the Software', so I need to include the copyright notice and permission notice, right? It being MIT licensed is one thing, but I also need to comply with LICENSE.txt, don't I?

If I'm doing something wrong, let me know... I'm surprised there's not more [msbuild] infrastructure for pulling together dependent LICENSE's into a ThirdPartyNotices.

Thanks for calling this out. I hadn't previously noticed that the MIT license required a copy of the license to be distributed. I thought it was simpler than that.
Ok. This suggests that we should not use licenseUrl. Good to know.
This is confusing. I'm not sure I get the point of the license expression if you still have to include the license file and the expression is going to result in a link on nuget.org to a different license file. Apparently, it isn't sufficient to specify the expression to comply with the license? Or is the expression sufficient, assuming you get the license from the link on nuget.org, but that isn't convenient for some tooling? Or is it more complicated because I also have a license file in my repo (which I feel is the responsible thing to do)?
If we replaced PackageLicenseExpression at https://github.com/craigktreasure/Treasure.Utils/blob/0c60411a13e11682d88eec1d645e0a7d24bb9b21/eng/Packaging.props#L13C5-L13C61 with <PackageLicenseFile>LICENSE.txt</PackageLicenseFile>, we should get the license file hooked up correctly. The downside is that it wouldn't be quickly visible from NuGet.org that it's licensed using MIT.

Well, I think the license expression is a great way to say that it's MIT licensed. Which it is. If you navigate to this link https://github.com/craigktreasure/Treasure.Utils/blob/main/LICENSE.txt GitHub puts a summary on-top that shows the Permissions, Limitations and Conditions - and without the LICENSE file in the nupkg, it's hard for consumers to comply with the Conditions.

Ok. This suggests that we should not use licenseUrl. Good to know.

Well, hold on there. licenseUrl is different from PackageLicenseExpression. You're using PackageLicenseExpression which is right. The weird part is that the build disallows PackageLicenseExpression and PackageLicenseFile, when PackageLicenseFile seems like a great way to comply with the license's Conditions.


Schema version generated for User and group looks wrong

Given the request  :
GET https://api.scim.dev/scim/v2/Schemas/urn:ietf:params:scim:schemas:core:2.0:User
it returns
    "meta": {
        "resourceType": "Schema",
        "created": "2001-01-01T00:00:00+00:00",
        "lastModified": "2001-01-01T00:00:00+00:00",
        "version": "W/\"1\"",
        "location": "https://api.scim.dev/scim/v2/Schemas/urn:ietf:params:scim:schemas:core:2.0:User"
    },

the version string looks not appropriate as containing kind of escaped char , it could be something like 1.0.0 or 1.3.3 (to not confused with others versionning like the api version , or scim version)
this looks coming from this line
https://github.com/limosa-io/laravel-scim-server/blob/9fefb3f5e0a6c1ab1a6423a825c128d03dac3784/src/Attribute/Schema.php#L19

The value of version is actually W/"1". The JSON specs require escaping quote characters, and allow escaping forward slashes.
The "W/" prefix indicated "weak validation", see here.
Nevertheless, you are right that version "1" is not really correct and never really updated. I agree that something better should be used. Now version "1" is simply hard coded somewhere. I could change this to something else but need to find a proper way.

thx for investigation re reading the spec clearly highlight what i missed
version  The current resource version.  Version MAY be used if the  service provider supports entity-tags (ETags) (Section 2.3 of
[RFC7232])  and so the versionning model and sample in fact are quite clear in the spec
"version": "W/"lha5bbazU3fNvfe5"",
    i let you keep it the ticket open for fixing the sample value or just close the ticket, as the current implementation is correct

Now fixed it.
See https://api.scim.dev/scim/v2/Schemas/urn:ietf:params:scim:schemas:core:2.0:User


@Allowed decorator forces case sensitivity even though ARM doesn't require it

Bicep version
bicep --version
Bicep CLI version 0.3.255 (589f0375df)
Describe the bug
Adding an @allowed syntax decorator forces a parameter to be case sensitive even though the ARM parameter is not.
To Reproduce
A simple repo is a parameter that takes valid Azure regions
@allowed([
  'EastUS'
  'EastUS2'
  'CentralUS'
  'NorthCentralUS'
  'SouthCentralUS'
  'WestCentralUS'
  'WestUS'
  'WestUS2'
  'CanadaEast'
  'CanadaCentral'
  'BrazilSouth'
  'NorthEurope'
  'WestEurope'
  'FranceCentral'
  'FranceSouth'
  'UKWest'
  'UKSouth'
  'GermanyCentral'
  'GermanyNortheast'
  'GermanyNorth'
  'GermanyWestCentral'
  'SwitzerlandNorth'
  'SwitzerlandWest'
  'NorwayEast'
  'NorwayWest'
  'SoutheastAsia'
  'EastAsia'
  'AustraliaEast'
  'AustraliaSoutheast'
  'AustraliaCentral'
  'AustraliaCentral2'
  'ChinaEast'
  'ChinaNorth'
  'ChinaEast2'
  'ChinaNorth2'
  'CentralIndia'
  'WestIndia'
  'SouthIndia'
  'JapanEast'
  'JapanWest'
  'KoreaCentral'
  'KoreaSouth'
  'SouthAfricaWest'
  'SouthAfricaNorth'
  'UAECentral'
  'UAENorth'
])
param targetResourceRegion string

You cannot pass in "eastus" even though its a perfectly valid region
Additional context
I do realize this is a crappy way to code this, but this is directly from Microsft docs: https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/resource-manager-alerts-metric#template-file-6
Possible solutions

Make the @Allowed decorator case insensitive
Add a decorator @CaseInsensitive
Add decorator types @AzureRegion - which may not work (run time vs compile time when looking at different AzureEnvironments (i.e. Azure vs AzureUSGovernment)

Good catch! We need to make the semantics of this match the runtime. (In the long term, we are considering introducing something like your @AzureRegion decorator to make declaring common sets of allowed values simpler.)


Add php72 runtime

@dgrove-oss Why do we have "sentinelledLogs": false, for java? I don't see this in the core repo for runtimes.json

Was removed in main repo by https://github.com/apache/incubator-openwhisk/pull/3860.  Shouldn't be here either.  (Java has sentinels now).

ok I will remote now as part of these clean up 👍


"Fix" ESP32-C2 and ESP32-C3

It pretty much looks like they don't support reading memory while running, under some unknown circumstances. Memory read is successful, but we read only 0s.
Terrible hackery and I'm not proud of it.

The failure, as I think many other RTT failures are caused by memory not being cleared immediately. When we call attach_to_rtt, we still see the previous, pre-reset state, treat it as initialised, then a short while later stumble over ourselves when the MCU overwrites the control block as part of its boot sequence.
What we can do:

short term: retry RttActiveTarget::new. I'll implement it for this PR, just to pass the tests.
long term: move all the RTT attaching to polling time. That way we can handle semihosting calls that happen before RTT initialisation, and we can tolerate errors better.

Here are my test results.
Setup

ESP32-C3-DevKit-C2 with JTAG USB wire soldered (using it)
Ubuntu VM
project uses defmt and defmt-rtt for logging
probe-rs installed via: cargo install --git https://github.com/probe-rs/probe-rs --rev a8975c4026fd1b7f3451ba6ffc4f3ed1caafba41 probe-rs-tools --force

Problems I encountered before (stock 0.24.0):

If the code used Embassy .await, no logging would come up on the console
With C6 devkit, things are working consistently well, for comparison
The problem was faced also on ESP32-C3-DevKit-RUST-1 devkit

Steps before running
I place the devkit in "download" mode, and push RESET once - just to be safe. This is to provide a more repeatable hardware state.

push both BOOT and RESET; release RESET; release BOOT
push RESET once more (may be unnecessary)

Experience with the patch
Two runs:
$ probe-rs run --chip esp32c3 target/riscv32imc-unknown-none-elf/release/app

      Erasing ✔ [00:00:02] [################################################################################################] 192.00 KiB/192.00 KiB @ 86.01 KiB/s (eta 0s )
  Programming ✔ [00:00:10] [###################################################################################################] 25.51 KiB/25.51 KiB @ 2.38 KiB/s (eta 0s )    Finished in 10.751233s
 WARN probe_rs::session: Failed to deconfigure device during shutdown: Riscv(AbstractCommand(HaltResume))
Error: Failed to attach to RTT

Caused by:
    Error attempting to attach to RTT: RTT control block not found in target memory.
    - Make sure RTT is initialized on the target, AND that there are NO target breakpoints before RTT initialization.
    - For VSCode and probe-rs-debugger users, using `halt_after_reset:true` in your `launch.json` file will prevent RTT
    initialization from happening on time.
    - Depending on the target, sleep modes can interfere with RTT.

Note: It takes a few minutes before the "Erasing" log line. This is likely due to the ELF binary being ~1GB for some unrelated reason.

I have seen this "Error: Failed to attach to RTT" before. But thought to retry (again, with resetting the board physically, first).
This time:
$ probe-rs run --chip esp32c3 target/riscv32imc-unknown-none-elf/release/app
      Erasing ✔ [00:00:02] [################################################################################################] 192.00 KiB/192.00 KiB @ 84.44 KiB/s (eta 0s )
  Programming ✔ [00:00:11] [###################################################################################################] 25.51 KiB/25.51 KiB @ 2.28 KiB/s (eta 0s )    Finished in 11.216645s
INFO  RWDT watchdog enabled!
└─ app::____embassy_main_task::{async_fn#0} @ src/bin/app.rs:47
INFO  Embassy initialized!
└─ app::____embassy_main_task::{async_fn#0} @ src/bin/app.rs:59
INFO  Watchdog fed
└─ app::____embassy_main_task::{async_fn#0} @ src/bin/app.rs:76
INFO  Watchdog fed
└─ app::____embassy_main_task::{async_fn#0} @ src/bin/app.rs:76

Well, that's REALLY WELCOME!!

A third time also succeeded. I measured the time before the flashing starts; it's 2 minutes. Unfortunately that may be putting off many C3 users already, but that's another issue. My verdict is that probe-rs definitely works better with this patch.
Note: I did see success even with earlier 0.24.0, but I think only once. That puts the success percentage to <10%.   Now, it's >60%.


Multiple Enhancements

Adding Favicon
A good and translucent navigation bar
Support us (Money Donation, will connect with payment gateway)

Under GSOC

Helo, I am currently a GSSOC contributor, kindly assign the issue to me


can backup from main to temp, Uncaught Error: SQLITE_ERROR: no such table: temp.foo

use sqlcipher, and test
get 1 failed:
can backup from main to temp
Uncaught Error: SQLITE_ERROR: no such table: temp.foo
but no problem with sqlite 3.26 （node-sqlite3 4.0.6）

Hi,
SQLCipher is not officially supported, but I'll keep the issue open if anyone is interested in investigating it.

Closing as the issue is stale but please re-open using an issue template if it's still an issue 🙂


Demographics & Units

[x] Births and Deaths need to be time unit aware.
[x] Rename "units", which is currently used to scale results e.g. 1/1000, considering units now has other meaning.

Rates should have units like ss.peryear, but if they don't and user does specify non-year units, we'll likely need to multiply by
time_factor = ss.time_ratio(unit1=self.unit, unit2='year')

PR #710 uses this time_factor "hack" and does now appear to be compatible with units, but the framework would benefit from a more robust handling of units in demographics.

I would like to suggest elevating the priority of this issue. Simulations on rc2.1.0 are currently quite broken when the user wishes to use units other than year. Changing the default units for demographic modules to year is not a solution.

While a refactor is warranted, even simple handling as we have done in other modules could work. For example in Deaths, the death_rate parameter could be an appropriate TimePar. We have the mechanics, just need to hook it up!

Closing as remaining work is covered by #732


[WIP] Build-script

[ ] Create the empty entry js. (src/main.js)
[ ] Create an empty gulpfile (ES6)
[ ] Plan the features that should be implemented
[ ] Plan the structure of the project
[ ] Add the choosen JS linter (probably eslint)
[ ] Default rules (Crockford-like if there is an option for applying a scheme)
[ ] Add the JS code style checker
[ ] Add the default rules to code checker

[ ] We should have a 9th element.


Property 'i18n' is missing in DocsThemeConfig

Hi, I'm trying to update nextra from 2.0.1 to 2.1.0.
In<EMAIL_ADDRESS>DocsThemeConfig now requires i18n option, but there is no documantation in https://nextra.site/docs/docs-theme/theme-configuration.
Property 'i18n' is missing in type '{ logo: JSX.Element; project: { link: string; }; chat: { link: string; }; docsRepositoryBase: string; footer: { text: string; }; toc: { extraContent: JSX.Element; }; }' but required in type '{ navigation?: boolean | { next: boolean; prev: boolean; }; banner?: { dismissible?: boolean; key?: string; text?: ReactNode | FC<{}>; }; chat?: { icon?: ReactNode | FC<{}>; link?: string; }; ... 23 more ...; i18n: { ...; }[]; }'.ts(2741)
index.d.ts(872, 5): 'i18n' is declared here.

I could understand the necessary properties by checking index.d.ts, but it would be very helpful if there was a description of the i18n options in the documentation.

Will be fixed soon https://github.com/shuding/nextra/pull/1206


:: not supported for Tables; Table examples

About parameter ObjectId: you reommend to declare it "by its name using the syntax <ObjectType>::<ObjectName>" - but this is not supported by object type = Table. For Tables, you have to Write Database::
Please also add a complete example for  table OnAfterValidateEvent, such as
    [EventSubscriber(ObjectType::Table, 1802, 'OnAfterValidateEvent', 'Package Imported', false, false)]
    local procedure OnAfterPackageImportedValidate(var Rec: Record "Assisted Company Setup Status"; var xRec: Record "Assisted Company Setup Status"; CurrFieldNo: Integer)
    begin

    end;

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

ID: 6d70267f-d9d9-ae2f-f8fc-f2abd435bffe
Version Independent ID: f52b19f8-a064-81e5-35a2-76a406620fa4
Content: EventSubscriber Attribute - Business Central
Content Source: dev-itpro/developer/methods/devenv-eventsubscriber-attribute.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Seems like this one has been overlooked, @SusanneWindfeldPedersen?
Could you also please add the tipp, that since BC 16, you can use Shift + Alt + E to easily insert a complete subsriber?

Hi, thanks for your feedback and sorry for the very delayed response. This article has been updated taking into account all your suggestions, and it will be available with the next refresh.


Added AddressBook feature

Closes #1672
@JamesSmartCell I have implemented AddressBook feature and added it to InputAddress component. Here are the details regarding the implementation. Please let me know if I need to change/update any thing.
AddressBook Activity

2 modes : Normal and Contact selection
Normal mode

shows list of contacts and allows to add more contacts by clicking + button in toolbar
opens edit address screen on clicking any item.
allows swipe to delete

Contact selection mode: Used for selecting a contact from address book

OnClicking an item, it is set as activity result for the calling activity to receive the contact.
does not allow swipe to delete

AddEditAddress Activity
Modes: Add & Edit

Add

if ens name is entered in Address, if it resolves, address will be set in address box and the ens name will be auto filled in Name box. Also ens name will be recorded for the entered address.
on clicking save, if data us valid, it is added to address book and activity closes.
Validations:

Address and name should not be empty
Address should be valid. Utils.isAddressValid()
Address & Name doesnt already exist in exisiting contacts.

Edit

Address input is disabled. address cannot be edited. Only name is editable
on clicking save, if data is valid, the contact name is updated.
Validation rules

Name is not empty
Old name and new name are different
new name is not assigned to other contact.
Address is valid.

Input Address Component

showAddressBook attribute allows to show AddressBook text beside the paste text.
On clicking, AddressBook text, AddressBook Activity is opened for contact selection.
The host activity of input address component should handle onActivityResult to get the data returned by AddressBookActivity

TransactionDetailActivity

If the sender and receiver address are present in address book, their name will be shown instead of address. On Clicking copy button, the address will be copied.
If address is not present in AddressBook, AddressBook icon is shown instead of copy icon. Onclicking it, AddEditAddressActivity is opened with the address auto filled.

Activity Adapter

passing AddressBookInteract to activity adapter to resolve the to & from address names if present in address book.
Not posiible to resolve as address is returned in the form of 0x42c...95cs

@asif-finimble this is a very large PR for a small feature. Can we prune it a little to get the code change down a little.
I can see a few wins in the duplicated resources, there are a few strings which are already translated.
Also, the adapter sliding has already been written, no need for a new class to do the same thing. Please see TokensAdapter which uses the token sliding (if that's what it's for - I might have mis-read it).
Let's work together after I get back from the conference to work out how to reduce the code size; it looks like a good implementation but I'm pretty sure we can re-use a lot of existing components rather than writing new ones that duplicate function.

OK. I'll go through the code and remove duplicated resources. Let me now when you are back so we can work it out.

OK. I went through the code and the sliding classes are used as inner classes so they are tightly coupled. It wont work with AddressBook.

Ok, but then that slider should be moved out of the class rather than duplicating code. Can probably just move the slider inner class out verbatim as we know it's reliable (unless it accesses private vars, in which case it'll need a new callback interface).
Adding AddressBook should not need to touch 58 files. It should only operate on InputAddress, possibly a BottomSheetDialog. I don't think it's been fully designed yet. Let me get back to you on this one. I agree with your implementation it should be a Realm item rather than SharedPrefs.

The sliding class is only extending ItemTouchHelper.SimpleCallback and overriding the required methods for drawing the content to show for sliding and the implementation of each of them is tightly coupled and specific to that class. Even if we generalize the sliding class most of the code is different and we cannot really reuse the class.  Let me what we should do for this.
As for the AddressBook, I found that the AddressBook feature was not implemented. So first I implemented the AddressBook feature by referring the zeplin designs and after that integrated it with InputAddress.  So I had to create the UI, repository , interact, etc for AddressBook and that's why there are changes to 58 files. Let me know what should I do further.

@JamesSmartCell I resolved the conflicts.

@seabornlee, code updated with changes.

@seabornlee, code updated with changes.

LGTM, thanks a lot!


Merge prTesting_201905081041 branch to master branch

Docs Build status updates of commit dfce57e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Added a basic calculator command

Hello, here my PR with a proof-of-concept implementation of https://github.com/reibitto/command-center/issues/27. README contains the relevant description. Please review, and I'm looking forward to your feedback.

Thanks, this is great! I have yet to use fastparse myself (I've been meaning to though), but this looks awesome.
I think this is good as is. Additional features can be added later too. I don't see a need to increase the scope of this PR, but some thoughts (which I'll put into a separate issue):

Might want to display integer values as 1 instead of 1.0 and so on.
Decimal separator could be based on the user's locale. For example, some countries use , instead of .
Similar to the above, but also one for grouping separator.
Maybe even make these formatting options a config value.
Additional functions: log2, ln, ceil, floor
Is there value in using BigDecimal instead of Double as the base type?

@reibitto, thank you. I'm glad you like it :) Yes, all you points are worth implementing. Regarding BigDecimal: I've tried it during development, but it then requires a third-party library for doing math. I was exploring spire but had at first problems with correctly importing required implicits. Maybe I'll try it another time a bit later. In the meanwhile I'm going to think about the other additions you mentioned.


fix: failing test

Description
https://github.ibm.com/GoldenEye/issues/issues/11171
fix failing test
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

I have asked @dishankkalra23 to include this fix in https://github.com/terraform-ibm-modules/terraform-ibm-event-streams/pull/312 since his PR is fixing the issue thats failing the tests currently

Fixed in https://github.com/terraform-ibm-modules/terraform-ibm-event-streams/pull/312


Select command not working, giving error to add argument

Tried this:
appletv --credentials '484549D6-494C-4F05-AA5E-8E41C61B6322:37303635464237452d373430412d343632382d383434372d454644443537373336383145:62393837643266312d363637652d343262332d383631322d333363336438633533363033:ca4bd75d8fae485dd5705e2f8a5d9cdaf4f6738b7ee5dc0ab66b044dfde2e5d3:af0b16a02984110d862095ab47a798218be8f15b9d56bea1a6fa8f9e58d83a3f' command select
Error: Invalid value 'select' for argument command.
undefined
Type appletv --help for help.
Please suggest how to add arguments for select command. Also please share the list of command I can use other than mentioned in document.

Have you found any solution @gk4ucool

Select was added in 1.0.10 for the javascript API, but it didn't make it into the code for the CLI it seems. See here: https://github.com/edc1591/node-appletv/blob/master/src/bin/index.ts#L40
If you're using the API then device.sendKeyCommand(AppleTV.Key.Select);  is what you need.
If you're dependent on the CLI, then I'd recommend making a pull request to include the code necessary to use the 'select' key. I think literally all that needs doing is to change line 40 to include select as so:
.argument('<command>', 'The command to send', /^up|down|left|right|menu|play|pause|next|previous|suspend|select$/)
Try editing that file locally and dropping in this replacement line and see if it works.


Feat: interesting army movement lines

When an army is traveling red lines are drawn from its origin to its destination. Then the lines disappear and the animation begins again. Clicking or hovering over the lines does nothing.

Suggestion: Use an opaque line and have the animation run through it from origin to destination. The animation might look similar to a heartbeat monitor.

Lines could all be the same color to signify 'this is an army movement,' but perhaps the 'pulse' traveling through the line is the attacking army's Order color. Hovering over the line could reveal a popup with the army origin, destination and troop composition. This will give the Atlas more utility.
Allow the user to on/off toggle army movement lines so the Atlas never gets too cluttered.

have made the lines more transparent and fade.
will need to experiment with more

this will be done in #408
closing this


native-or-bluebird is deprecated. please switch to any-promise

https://github.com/kevinbeaty/any-promise
this implementation supports more promise implementations and allows the end-user to configure the promise implementation.

Got it, thanks.
BTW, what magic did you use for submitting a issue? Because i've seen many same issues and just thought that it cannot be done manually, haha.

Manually lol


Reference dis not show up

Subject: Reference dis not show up
Description:
I would like to see how my references for him have been submitted or not
Results:
Hi. I wrote a reference when I received an email to write it, and I couldn't find it. My host also wrote me one, but I'm not able to see it. So I tried many times, and he said he can see it now, but as a friend and not as a guest
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/profile/about
User: hydrocephalus93 (14648)

confusion about reference types, not a bug


remove unreachable catch

Coverage increased (+0.08%) to 89.68% when pulling bcbb6093e1c60a3df848aa29a36db9813cca88c3 on arturs68:fix_undreachable_catch into ad767d77340800a0c2d802d24beec35908a33360 on CS2103AUG2017-T12-B1:master.


Building on windows

I am unable to build it on windows.
Installed cygwin and the 3 mentioned packages but get an error.
$ make
meson .obj
process_begin: CreateProcess(NULL, python3 C:\cygwin64\bin\meson .obj, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [.obj/build.ninja] Error 2

I had to install some more libraries, but now I am still stuck. It complains about sqlite3 not being installed, but it is.. Am I missing something?
$ make all
meson .obj
The Meson build system
Version: 0.49.2
Source dir: /home/Game PC
Build dir: /home/Game PC/.obj
Build type: native build
Project name: fluxclient
Project version: undefined
Native C compiler: cc (gcc 7.4.0 "cc (GCC) 7.4.0")
Native C++ compiler: c++ (gcc 7.4.0 "c++ (GCC) 7.4.0")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (1.6.0)
Dependency libusb-1.0 found: YES 1.0.21
Found CMake: /usr/bin/cmake (3.6.2)
Dependency sqlite3 found: NO (tried pkgconfig and cmake)
meson.build:5:0: ERROR:  Dependency "sqlite3" not found, tried pkgconfig and cmake
A full log can be found at /home/Game PC/.obj/meson-logs/meson-log.txt
make: *** [Makefile:6: .obj/build.ninja] Error 1

Did you install the sqlite3-devel package, or just the sqlite3 runtime library?

Installed some more libs which contained sqlite3 in the name and finally I got it to compile, don't know which library was required but it works now.

I don't have the FluxEngine programmed/connected yet. When running the exe's I get 'program stopped working' crash, is this normal behaviour without the FluxEngine connected?

I was running it in windows, I see I have to run it in cygwin, working now. Now just have to build it...

I built the fluxengine, and got it to work somewhat...
When reading an amiga disk, after reading all I get is XXXXX's line after line, and it keeps scrolling until I close Cygwin.
Also tried writing a raw flux file, but I get this error. Are there any parameters I need to add?
$ .obj/fe-writeflux
Error: two flags use the name '--high-density'

This is another error I get
$ .obj/fe-writetestpattern
Writing to: :d=0:s=0-1:t=0-81
0.0: 200 ms in 100000 bytes
0.1: Error: failed to receive command reply: Pipe error

Can you capture the entire output of the Amiga read and attach it here? (Run script before the command, do exit afterwards, and it'll log everything to a file called typescript.) It sounds like it's trying to read garbage and thinks your disk has far too many sectors, but I need the log to know more.
Regarding writing files: that doesn't actually work in any useful fashion for disks other than Brother word processors. I'm working on this --- it needs all the write layer to be refactored. fe-writetestpattern failing is odd, though, and suggests you don't have enough USB bandwidth. Could you try fe-testbulktransport and tell me what it reports?

Transferred 1048576 bytes in 1196 (855 kB/s)
I can't type exit afterwards, since the program never stops writing the XXX's
Hope you can add support for writing raw flux files soon!

You probable already know this site http://hxc2001.free.fr/, there is a tool on this site which allows you to convert all sorts of floppy formats maybe the guy that wrote this can help you in support for different formats like ipf and hfe. The tool allows you to convert for instance an ipf to raw flux format, wonder if I would be able to write this back to floppy.

I have quite a few floppy based retro systems. If you need someone for testing stuff let me know.

There are now precompiled Windows binaries for the client downloadable from GitHub, so this bug is obsolete --- closing for cleanup.


API CREATE doesn't create new bookmark but returns list of bookmarks

Hello,
i have an instance of linkeding (v 1.19.1) running via docker which works perfectly so far and also the firefox extension works nice.
I now wanted to add some bookmarks with python and tried the below code.
Unfortunately what I get back is a "200" response and in the body i get all my bookmarks listed.
I also tried with different URLs, e.g. "https://example.com/api/v1/bookmarks" (also /v2/) - but those give a 404.
The token and the base url work, as i can for example get a list of my bookmarks by sending a get request.
I assume I am making a mistake somewhere, but I cannot find it and tried now for too long - so if somebody could help me, I would be really happy.
Here is the code:
import requests

LINKDING_URL = "https://example.com/api/bookmarks"
LINKDING_API_TOKEN = "my_token"

# Main script
if __name__ == "__main__":
    title="test"
    url="https://testing.com/test"
    data = {
        "url": url,
        "title": title
    }
    headers = {"Authorization": f"Token {LINKDING_API_TOKEN}"}
    response = requests.post(LINKDING_URL, json=data, headers=headers)
    print(response.status_code)
    print(response.content)

Thanks for your help!
Cheers,
Georg
Edit:
I also used this data-structure (as shown in the api documentation) but got the same result:
    data = {
        "url": url,
        "title": title,
        "description": "Example description",
        "notes": "Example notes",
        "is_archived": False,
        "unread": False,
        "shared": False,
        "tag_names": [
            "tag1",
            "tag2"
        ]
    }

Looks like you're missing the trailing slash in the URL:
POST /api/bookmarks/


Closes feature_12.

[Current coverage][cc-pull] is 33.33%

Merging [#26][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #26   diff @@
==========================================
  Files             1          1
  Lines             3          3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits              1          1
  Misses            2          2
  Partials          0          0

Powered by Codecov. Last updated by [d9876e1...d9812db][cc-compare]
[cc-base-branch]: https://codecov.io/gh/madeulook/web-ui/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/madeulook/web-ui/compare/d9876e16f19c1e31a67e7142e7681c611b31c604...d9812db97940954caa50e958b04816ba0058be29
[cc-pull]: https://codecov.io/gh/madeulook/web-ui/pull/26?src=pr


fixes keycloak after c919fea5e829e0979ed06d2930afdd1eed7e4266

@kenfinnigan @bobmcwhirter
Seems this might now be required?
This should address the following bug:
https://issues.jboss.org/browse/SWARM-298

What error are you seeing? Ribbon-Secured example seems to be working but is admittedly thin.

Ah I see the JIRA. Ignore me.


Portuguese translation

Does the pull request solve a related issue? no
What does the pull request accomplish? portuguese translation

Thanks!


Update the dfdaemon with additional scheduler info without having to restart it

Feature request:
In a large environment with many dfdaemon it is important to auto-scale the scheduler based on demand. Currently, if we add more schedulers, the dfdaemon needs to be restarted to take it into effect. Restarting the dfdaemon could momentarily fail the pull requests on that specific client. Can we update the dfdaemon with additional scheduler info without having to restart it?
Use case:
Auto-scaling of schedulers based on demand
UI Example:

This feature will be added in the future.

#812 closed it


Zot logo: experiment and decide on a font for the text

There have been discussions on removing the z from the zot logo, as the icon is already a stylized z.
We're not going to go that route, but we should look into an appropriate font for the zot test to be shown next to the logo

Keep logo as is for now


feat(headless): support DictionaryFieldContext

https://coveord.atlassian.net/browse/KIT-354

How should we allow users to set these context/dictionary context with Atomic? With a component or going through Headless?

Can you also add this in the ProductRecommendationsAppState

Sure, I'll do this in a dedicated PR,

How should we allow users to set these context/dictionary context with Atomic?

Considering it's non-visual, I think using javascript to call functions would be the most consistent, and most flexible.


加了neft_alpha，训练出来使用api.demo.py 加载lora模型和base-model 报错，麻烦看下

er
model = PeftModel.from_pretrained(model, checkpoint)
File "/usr/local/lib/python3.8/dist-packages/peft/peft_model.py", line 271, in from_pretrained
model.load_adapter(model_id, adapter_name, is_trainable=is_trainable, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/peft/peft_model.py", line 561, in load_adapter
load_result = set_peft_model_state_dict(self, adapters_weights, adapter_name=adapter_name)
File "/usr/local/lib/python3.8/dist-packages/peft/utils/save_and_load.py", line 126, in set_peft_model_state_dict
load_result = model.load_state_dict(peft_model_state_dict, strict=False)
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 2041, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for PeftModelForCausalLM:
size mismatch for base_model.model.model.layers.0.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.0.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.0.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.1.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.1.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.1.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.2.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.2.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.2.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.3.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.3.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.3.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.4.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.4.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.4.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.5.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.5.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.5.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.6.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.6.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.6.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.7.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.7.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.7.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.8.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.8.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.8.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.9.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.9.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.9.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.10.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.10.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.10.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.11.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.11.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.11.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.12.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.12.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.12.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.13.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.13.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.13.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.14.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.14.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.14.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.15.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.15.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.15.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.16.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.16.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.16.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.17.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.17.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.17.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.18.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.18.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.18.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.19.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.19.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.19.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.20.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.20.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.20.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.21.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.21.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.21.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.22.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.22.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.22.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.23.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.23.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.23.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.24.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.24.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.24.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.25.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.25.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.25.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.26.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.26.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.26.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.27.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.27.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.27.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.28.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.28.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.28.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.29.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.29.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.29.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.30.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.30.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.30.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.31.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.31.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.31.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.32.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.32.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.32.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.33.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.33.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.33.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.34.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.34.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.34.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.35.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.35.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.35.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.36.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.36.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.36.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.37.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.37.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.37.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.38.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.38.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.38.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.39.mlp.gate_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).
size mismatch for base_model.model.model.layers.39.mlp.down_proj.lora_A.default.weight: copying a param with shape torch.Size([32, 13696]) from checkpoint, the shape in current model is torch.Size([32, 13824]).
size mismatch for base_model.model.model.layers.39.mlp.up_proj.lora_B.default.weight: copying a param with shape torch.Size([13696, 32]) from checkpoint, the shape in current model is torch.Size([13824, 32]).

lora 文件搞错了，汗


Util for getting children

Overview
This PR adds a util function for getting the textual descriptions of children of a given Snowmed concept. It is adapted from @karthikraja95's example.

@karthikraja95 I adapted your code and made it a little function under deep_patient_cohorts.common.utils.get_snowmed_children_descriptions.
This is the list it produces for the CID "373247007"
['Capillary active drug',
 'Capillary protectant',
 'Vasoprotectant',
 '3-Methoxy-o-desmethylencainide',
 'Pirmenol',
 'Saluretic - chemical',
 'Capillary active agent',
 'Antiplatelet agent',
 'Hypotensive agent',
 'Diuretic',
 'Thrombolytic agent',
 'Antiarrhythmic agent',
 'Vasoconstrictor',
 'Inotropic agent',
 'Antivaricose agent',
 'Cardiac agent',
 'beta-Blocking agent',
 'Cardiac adrenergic blocking agent',
 'Antilipemic agent',
 'Alpha-adrenergic blocking agent',
 'Calcium channel blocker',
 'Antilipaemic agent',
 'Beta-adrenoceptor blocking agent',
 'Cardiac non-specific adrenergic blocking agent',
 'Lipid lowering agent',
 'Alpha-adrenoceptor blocking agent',
 'Capillary-active drug',
 'Cardioplegic solution agent',
 'Antihypertensive agent',
 'Ivabradine',
 'Ivabradine hydrochloride',
 'Adenosine A2 receptor agonist',
 'Adenosine A2 agonist',
 'Alpha adrenergic receptor antagonist',
 'Beta adrenergic receptor antagonist',
 'Substance with adenosine A2 receptor agonist mechanism of action',
 'Substance with alpha adrenergic receptor antagonist mechanism of action',
 'Substance with beta adrenergic receptor antagonist mechanism of action',
 'Substance with calcium channel blocker mechanism of action',
 '3-methoxy-o-desmethylencainide',
 'Modecainide',
 'Vasopressor']

Does that match what you had?

@JohnGiorgi Yes! Perfect it does match with what I had.


feat(styles): update buttons padding, gap and border-radius

Following https://github.com/swisspost/design-system/issues/1571#issuecomment-1641942510 and discussion from today.
Updated:

Padding
Internal gap
Border-radius

Figma: https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?node-id=9096%3A36684&mode=dev

Can you also update the icon size for large buttons, it is 24px currently instead of 22px in Figma?

I think this one is ready to be merged, if you could have a look, please @gfellerph @alizedebray @oliverschuerch


Add checking for X-Forwarded

Added a check for X-Forwarded-Host to support load balanced environments such as Azure with Front door.

Thanks for contributing @Matthew-Wise! This is certainly a needed change (in Umbraco's own routing as well...) 👍
I think this logic perhaps belongs in the DomainHelper, maybe a new method e.g. GetDomainByRequest that encapsulates this logic.
I will approve and merge but make this change before releasing 😊

I've moved this logic into an extension method on the request request.UrlOrForwarded() as hopefully this can be used more broadly.
This has finally been released onto NuGet in v1.1.0, better late than never eh...
Thanks again @Matthew-Wise!


Create kraken.spot.Market.get_asset to use caching

Is your feature request related to a problem? Please describe.
There is already an existing  kraken.spot.Market.get_assets endpoint which can be used to retrieve all or filtered assets. Since its inputs allow lists, and thus are not hashable, the functools caching cannot be applied. To workaround this, a new function as named in the issue title could be added to archive caching for individual asset pairs.

Is not a good solution anymore - see #102.


Options Page Update

Hi @allanino
Just in case you haven't found the solution to my latest request #8 , you can simply append
"open_in_tab": true
in the manifest to open the options page in a new tab instead of an embedded window. This will solve the "Enable Material Design extensions" flag bug in chrome lab, but you don't have to do that as I'm sure Google will fix it later on.
While searching the solution, I've taken some time to light up the options page a bit by introducing some material design elements. Feel free to merge it if you like it. Thanks.

Hi @pingshunhuangalex! Thanks for the PR. I'm most pleased with your changes to our options page style.
However, I had to fix some merge conflicts manually, and took the opportunity to modify some small things, the most important being my desire to keep our main files in the root directory (our JS and HTML files).
In the future, to avoid these merging conflicts, I would like to ask you to be sure to pull the latest version from my branch before making your own changes.


Call zypper with --userdata

All calls to zypper should pass a --userdata value.
https://github.com/SUSE/doc-caasp/issues/644#issuecomment-566900165 raised the question of "how can support detect that a customer did this [call zypper on the node manually] "wrong"?"
zypper has an option to pass a transaction id:
> zypper -h
  ...
    --userdata <STRING>     User defined transaction id used in history and plugins.
  ...

which will appear in the zypper.log. skuba could set this id to indicated "zypper was called from skuba" in the zypper.log.

Interesting idea.  Would we want to use a generic and common "--userdata skuba" for all calls to zypper made by skuba, or would there be additional information that could be valuable as well?

just a comment. I like the idea of doing something like --userdata skuba-[uid] not sure what all your thoughts are on it. might be overkill/not needed or useful. was thinking if we had better logging it might help tie things together.

As we talked about this, it would also make sense to have separate identifiers for skuba and skuba-update and any other modules within the code base.  There are also a fair number of templates and helper scripts under the ci/ which can be reviewed too, though instances for build and testing can be skipped.

Is there any bsc about this?

No bsc that I'm aware of, and searching bugzilla did not find any relevant issues.


[admin] Publish

add agenda for April 2022

clear call agenda for May

Docs Build status updates of commit 87b3983:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[Question] Is it possible to upload multiple files

The args property sounds plural. I wonder if it is possible to upload multiple files or do I have to make a step for each file?

@xetra11 it is possible.
see https://github.com/sinshutu/upload-to-discord/blob/master/.github/workflows/main.yml

@xetra11 Close, but if not resolved please reopen


Improved build system

Hello @AllenFang,
As I told you on twitter, I greatly improved the build system. The code is commented.
There are some things I still want to improve, namely bump the version of babel to Babel 6, but since this new build greatly reduces the dist bundle size, I think its best to merge as soon as possible.
Cya later :)

I initiated the inclusion of links to the repo source code on the examples, but as I said, you can merge it as soon as possible, I will finish this other things later, the most important thing is done.

I've already reviewed it and maybe ask some questions on twitter. BTW, thanks your contribution!

however, I'll follow this 0d36243 commit to enhance the example code. Thanks a millions a lot!


Can't run on different port than 8080

I tried to run image on port 12000 (and same for 8000):
docker run -d -p 12000:12000 puckel/docker-airflow webserver
However, I receive ERR_EMPTY_RESPONSE when trying to access localhost:12000.
When I run image on port 8080, it works fine:
docker run -d -p 8080:8080 puckel/docker-airflow webserver
How can I forward/change it to 12000? I need 8080 for other container.
Is forking this repo and making changes to Dockerfile's EXPOSE the only way?

Oops, I just needed docker run -d -p 12000:8080 puckel/docker-airflow webserver :)


LLVM14 Upgrade

Addressed comments from initial llvm 14 upgrade push, ported fixes from master branch.

Please add a new commit to inline the discussions here in the source code


Issues when creating OVPN profile files - missing  "-----END CERTIFICATE-----" statements.

Hello guys, I hope this isn't a repeated issue ticket.
Two users in my company had issues with their "ovpn" profile files. At first I only notices the different length of the  second certificate block, but after more in details I also noted the missing
"-----END CERTIFICATE-----" statement for the second certificate.
This happened with 2 users which already existed and lost their cert, so, I revoke their permissions, and minutes later, create them a new profile file using the same user name.
When using a different username the issue did not happen again, but, in other of our VPN have done similar steps:
1- revoke permissions for a user
2- created a new ovpn file for the same person, same username.
And in that case, no issues. I'm trying to reproduce the issue but unfortunately, I'm not getting there.
Does this happen/ to you or anybody else?
Again, I hope the ticket is not repeated.

Hi, I guess you didn't have the time to check this, but, something I wanted to remark is the difference of "LENGHT" between a functional "profile-file" and one with issues.

I am also seeing the same issue on the latest Raspberry Pi OS after upgrading from Raspbian 9, the generated .ovpn file has a bogus  section with only -----BEGIN CERTIFICATE----- followed by 2 lines of normal looking certificate code and then a closing </cert> without an end marker. I have no clue what the root cause is.


Fix: Update README.md

This PR

[x] updates README.md with suggestions for alternatives and when to use this instead

Fixes #158.

@jhabdas
What do you think?

Humble. Thank you kindly @localheinz. Looks great.

Thank you, @jhabdas!


chip.select doesn't work ?

Description
Event chip.select doesn't working
Screenshots / Codepen
http://codepen.io/anon/pen/mOZMQW?editors=1001

There is a small mistake in your code @bibislayer change class chips  to chip

Hello

    Tag
    close

  </body

Follow the docs here

My code haven't mistake,
Retry http://codepen.io/anon/pen/mOZMQW?editors=1001
I juste remove the .chips-initial now it's a copy/past from http://materializecss.com/chips.html

@bibislayer The last code i have seen, there was a mistake. You did not initilize you tags like this one
  $('.chips-initial').material_chip({
    data: [{
      tag: 'Apple',
    }, {
      tag: 'Microsoft',
    }, {
      tag: 'Google',
    }],
  });

So i fixed that mistake first.
No chip was showing before in the last code

i already correct this, just i don't use initial, but you could add a tag and remove this on the input at the top.

now Initial chips is added and chip.select event never work.

This is indeed a bug, thanks for pointing this out.
Fixed in 84f204d


Update compilerplugin, scalapb-runtime to 0.10.10

Updates

com.thesamet.scalapb:compilerplugin
com.thesamet.scalapb:scalapb-runtime

from 0.10.9 to 0.10.10.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.thesamet.scalapb" } ]

labels: library-update, semver-patch

Superseded by #780.

Superseded by #780.


Add Buffer Class

Abstract reading/writing to and from buffers.

[ ] Should be able to pass in a buffer to be sent over the socket.
[ ] Should be able to receive data and put into a buffer.
[ ] Read from Buffer in all types.
[ ] Write to Buffer in all types.

this is silly, there's stuff out there already built for this


system Spanish language and pages flex blueprint updates

@dani-ooo FYI, your translations will get lost unless you also update them in Crowdin: https://crowdin.com/project/grav-core

i didn’t know. thanks, @mahagr!
i’ve submitted the updates there too.
for future language file commits, do i need to update the translations on Crowdin AND the file in the repository, or is it enough with just Crowdin?

should i make a new pull request for 2267077e6355db0e5f1a712be4ba008afa3279f7 only?

I've merged everything, so the fix for the template is already in.

i didn’t see it had been merged, sorry! i’m fairly new to contributing to gits.
may ask again about the right process for language file commits: do i need to update the translations on Crowdin AND the file in the repository, or is it enough with just Crowdin?
thanks!

It should be enough to update translation in Crowdin.


Role not found but it does exist

For the life of me I can't figure out why this isn't working. Every other role (built the same way using terraform) works fine, just not this one. I'm not sure how to begin debugging this?
(PS Note I redacted some stuff in this log)
cloudtracker --account demo --role build-jenkins
INFO     Source of CloudTrail logs: s3://wd-697111119245-bucket/
INFO     Using AWS identity: arn:aws:sts::697111119245:assumed-role/SSOAdminRole/botocore-session-1540918197
INFO     Using output bucket: s3://aws-athena-query-results-697111119245-us-west-2
INFO     Account cloudtrail log path: s3://wd-697111119245-bucket//AWSLogs/697111119245/CloudTrail
INFO     Checking if all partitions for the past 12 months exist
Traceback (most recent call last):
  File "/Users/paul.oflynn/workspace/venv/bin/cloudtracker", line 11, in <module>
    load_entry_point('cloudtracker==2.1.2', 'console_scripts', 'cloudtracker')()
  File "/Users/paul.oflynn/workspace/venv/lib/python3.7/site-packages/cloudtracker/cli.py", line 104, in main
    run(args, config, args.start, args.end)
  File "/Users/paul.oflynn/workspace/venv/lib/python3.7/site-packages/cloudtracker/__init__.py", line 481, in run
    role_iam = get_role_iam(rolename, account_iam)
  File "/Users/paul.oflynn/workspace/venv/lib/python3.7/site-packages/cloudtracker/__init__.py", line 219, in get_role_iam
    raise Exception("Unknown role named {}".format(rolename))
Exception: Unknown role named build-jenkins
(venv) cloud-tracker $ aws iam get-role --role-name build-jenkins
{
    "Role": {
        "Path": "/jenkins/",
        "RoleName": "build-jenkins",
        "RoleId": "AROAI2***********",
        "Arn": "arn:aws:iam::697111119245:role/jenkins/build-jenkins",
        "CreateDate": "2018-10-29T17:26:16Z",
        "AssumeRolePolicyDocument": {
            "Version": "2012-10-17",
            "Statement": [
                {
                    "Sid": "",
                    "Effect": "Allow",
                    "Principal": {
                        "AWS": "arn:aws:iam::697111119245:role/nodes.*******.com",
                        "Service": "ec2.amazonaws.com"
                    },
                    "Action": "sts:AssumeRole"
                }
            ]
        },
        "MaxSessionDuration": 3600
    }
}
(venv) cloud-tracker $

Make sure build-jenkins is in the IAM data you downloaded.  You should have a file like account-data/youraccount.json  The role needs to appear in that file.

Ah, that was it, the role had been renamed since I first created the json file. I didn't realize the role data was in that file, thx


unable to require kafka/prometheus

Version of Ruby: 2.4.2
Version of Kafka: irrelevant
Version of ruby-kafka: 0.7.10
Version of prometheus-client: 0.10.0

Steps to reproduce
require 'kafka/prometheus'

Expected outcome
kafka/prometheus is required successfully
Actual outcome
2.4.2 :002 > require 'kafka/prometheus'
ArgumentError: wrong number of arguments (given 2, expected 1)
        from /Users/ronenkonfortes/.rvm/gems/ruby-2.4.2/gems/prometheus-client-0.10.0/lib/prometheus/client/registry.rb:40:in `counter'
        from /Users/ronenkonfortes/.rvm/gems/ruby-2.4.2/gems/ruby-kafka-0.7.10/lib/kafka/prometheus.rb:45:in `initialize'
        from /Users/ronenkonfortes/.rvm/gems/ruby-2.4.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/subscriber.rb:30:in `new'
        from /Users/ronenkonfortes/.rvm/gems/ruby-2.4.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/subscriber.rb:30:in `attach_to'
        from /Users/ronenkonfortes/.rvm/gems/ruby-2.4.2/gems/ruby-kafka-0.7.10/lib/kafka/prometheus.rb:34:in `start'
        from /Users/ronenkonfortes/.rvm/gems/ruby-2.4.2/gems/ruby-kafka-0.7.10/lib/kafka/prometheus.rb:317:in `<top (required)>'
        from /Users/ronenkonfortes/.rvm/rubies/ruby-2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:69:in `require'
        from /Users/ronenkonfortes/.rvm/rubies/ruby-2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:69:in `require'
        from (irb):2
        from /Users/ronenkonfortes/.rvm/rubies/ruby-2.4.2/bin/irb:11:in `<main>'

just noticed it was fixed in later release, sorry


Fix async uart overflow implementation

Quote from #977

The current overflow handling will in some cases return a buffer where there are missing characters (as there was an overflow) and then at the next call to async read(), report that there where an overflow either in the current or the previous async read().

What I expect we need is a way to have a shared atomic state between the interrupt handler and the non interrupt code.
The interrupt should set the ovf flag as soon as the hardware has reported an overflow.
Async read() would check the flag at least once after reading all bytes from the buffer, but before returning anything to the caller.
Then either both async read() and drain_fifo(), or possibly only one of them could clear the ovf flag in the shared atomic state when they know that it has been reported to the user.

I did not realize that it was even possible to drain the buffer as the current async read() is not capable of doing that.

So it is probably better to just re-add the check here and then provide a follow up patch patch to improve ovf handling.

Certainly that would be a great exercise!

https://github.com/esp-rs/esp-hal/pull/1168

Closed via https://github.com/esp-rs/esp-hal/pull/1445, thanks again @konsulten!


Replace AddFilterToMiddleware with Application.Use

AddFilterToMiddleware is deprecated. Use AddRequestFilter instead. More info: https://github.com/Starcounter/Starcounter/issues/2969

The Times They Are a-Changin'

Now AddRequestFilter is also deprecated!
Replace AddFilterToMiddleware with Application.Use, as discussed in https://github.com/Starcounter/Starcounter/issues/3477

Fixed in PR #13

Done.


Error in CSV Export

What happened:
Exporting the Data from the Wallet to CSV file leads to inconsistent information in the CSV-Export.
PoolSwap: Sometimes the second coin is missing
AddPoolLiquidity: Sometimes the LM-Token is missing. And sometimes the second coin and the LM-Token is missing
What you expected to happen:
All exported data should be consistent otherwise the CSV-Export is useless.
Poolswap: 2 Coins should be exported (In and Out Coin)
AddLiquidityMining: 3 Coins should be exported (Coin1 out / Coin2 out / LM-Token in)
RemoveLiquidityMining: 3 Coins should be exported (Coin1 in / Coin2 in / LM-Token out)
How to reproduce it (as minimally and precisely as possible):
Use a Wallet which has done some PoolSwaps and uses LiquidityMining. Than export the CSV-File and check it via TextEditor
What are your environment parameters?

DeFi Wallet Version: 2.3.2 (also happens on version 2.3.0 and 2.3.1)
Operating System (OS): Win10

Anything else we need to know?:
Because of privacy I don't want to offer the original CSV-Export.

Hi @MaReCoding , thanks for your feedback, regarding the issue Feat| Optimization of CSV export, we can further discuss on the problem there. Can you copy and paste your comment there please? We would like to keep same issues in one thread. Thank you.!


Lost pre-prepare with large batch

Description

The system occationally gets stuck while stress-testing multiple peers with batchsize=100.   Non-primary peers' log says some pre-prepares are missing.
$ for i in {1..3}; do echo akihiko$i; docker logs akihiko$i | grep  -a "pre-prepare from" | grep "seqNo=27[7-9]"; done
akihiko1
04:57:39.882 [consensus/obcpbft] recvPrePrepare -> DEBU 1459cf Replica 1 received pre-prepare from replica 0 for view=0/seqNo=277
04:57:40.384 [consensus/obcpbft] recvPrePrepare -> DEBU 146032 Replica 1 received pre-prepare from replica 0 for view=0/seqNo=279
akihiko2
04:57:39.882 [consensus/obcpbft] recvPrePrepare -> DEBU 53e43 Replica 2 received pre-prepare from replica 0 for view=0/seqNo=277
04:57:40.384 [consensus/obcpbft] recvPrePrepare -> DEBU 544e4 Replica 2 received pre-prepare from replica 0 for view=0/seqNo=279
akihiko3
04:57:39.879 [consensus/obcpbft] recvPrePrepare -> DEBU 1bbbaf Replica 3 received pre-prepare from replica 0 for view=0/seqNo=277
04:57:39.910 [consensus/obcpbft] recvPrePrepare -> DEBU 1bc0f0 Replica 3 received pre-prepare from replica 0 for view=0/seqNo=278
04:57:40.384 [consensus/obcpbft] recvPrePrepare -> DEBU 1bd885 Replica 3 received pre-prepare from replica 0 for view=0/seqNo=279
My guess is prePrepare message causes channel overflow in broadcast.go, maybe due to large message size with batched transactions.  Here are logs from the primary, after I added logger.Errorf to unicastOne.
...
04:57:39.905 [consensus/obcpbft] sendPrePrepare -> DEBU 1f9c23 Primary 0 broadcasting pre-prepare for view=0/seqNo=278 and digest xw8Hrjvdd4XZ//gLcvnW70CC0EiRmyfYUFbR5HOoUSH+solqJ4ICMSYthIVCMpTHB/lBU1CWx0DUubCXiTakEA==
...
04:57:39.906 [consensus/obcpbft] unicastOne -> ERRO 1f9c37 unicastOne: discarded message to 2
04:57:39.906 [consensus/obcpbft] unicastOne -> ERRO 1f9c38 unicastOne: discarded message to 1
....
Describe How to Reproduce

Environment:  version Sun May 29 12:01:25 2016, #of peers=4 (dockers on a single machine),  security/privacy=on.  consensus=pbft-batch, batchsize=100.  Application: chaincode_example02.  It maybe easier to reproduce the problem with logging.node=info.

can you please provide full debug logs?  the system should not get stuck.

I also observed that increasing the queueSize in broadcast.go resolves failure of the Busywork benchmark.
When I ran the benchmark with 4 peers using PBFT batch consensus with security enabled, the benchmark fails due to inconsistent results among peers. The benchmark works when I increase queueSize from 10 to 200.
The failure occurs on up to 3 cores, and does not occur on more than 3 cores. This implies that the root cause can be queue overflow due to insufficient processing power.


Homog. Poiss. with refr. Period: Bug fixed

Bug fixed while dealing with the units of the refr. period

Posting your detailed message,

As it is now, we compare one object without duration against one with a unit: refr_period. This gives an error, if refr_period does not have the same units as t_start.


Removed Anti-Affinity documentation as this endpoint has been removed.

@davechaneyctl sorry for the late response on this, we don't get many changes to this repo.
Please contact @JimGreene30 to set up redirects to the deleted pages.


can pinpoint used for monitoring the application while dynatrace is installed on this application？

the application is monitoring by dynatrace ， can I install a pinpoint on this application again？

Hello, @bishenghua123.
Have you tried using pinpoint over dynatrace?
I'm curious if it would work


Added postgres changeColumn TYPE support

This is related to https://github.com/db-migrate/node-db-migrate/issues/262

@fydo23 Thanks for your contribution, please see my comments, it is just one :), there is one thing stopping me from merging this already.
Please fix this and I can merge this.

Cool. I'll fix this right up!

I've made the requested changes but before I push, can you take a look at my response to your comment?


MOMZA-192 Add more baby keyword to SMS app

usana
sana
baba
babby
lesea
bby
babya

@imsickofmaps please review

👍


chore(imports): import only once from ./types

Somewhat confusingly, Observable used to import from ./types once via the
child path, and once via ../internal/types, which does resolve to the same file.

/CC @benlesh

Coverage remained the same at 96.629% when pulling 0a3c9df2e317a6b19539aa078fb4cfeefc580204 on mprobst:patch-1 into 537fe7db0248f05d21eef7fefc89f388c1491fe7 on ReactiveX:master.

If I had to guess, I'd say that one of those was magically added by VSCode while I was working. :\
Thanks, @mprobst!


HTML-unsafe characters are not properly escaped in HTML export

I have a bookmark to an article about CSS that includes a literal <style> tag in its description.
When this bookmark appeared in a Pinboard HTML export, the <style> tag is escaped with HTML character entities as <style> so that it isn't interpreted as an unclosed HTML <style> tag within the bookmarks.html (which could otherwise break parsing of that file.)
After importing that exported properly-escaped Pinboard HTML into Linkding and then re-exporting from Linkding, the <style> tag in the same bookmark from Linkding's export is not escaped, which produces an invalid/unclosed <style> tag within the exported HTML as referenced above.
I'm not sure if this issue needs to be fixed within the exporter itself or at a lower level/at bookmark storage time.

This is a duplicate of https://github.com/sissbruecker/linkding/issues/396


Add example scripts to documentation

Closes #3547
Notes:

Currently only works for scripts at the top level of examples
Nested/multi file examples (fp8, production_monitoring) are not included
If the examples were to be rewritten as notebooks we could use nbsphinx to elegantly render proper tutorial style examples as webpages

Example pages from the docs build:

https://vllm--4225.org.readthedocs.build/en/4225/getting_started/examples/examples_index.html
https://vllm--4225.org.readthedocs.build/en/4225/getting_started/examples/offline_inference.html

@simon-mo the test failures seem unrelated, could the failing jobs be retried to see if they are just flaky?


No love for NotImplemented?

When overriding binary special methods (e.g., __eq__, etc.), returning NotImplemented is a common convention, and generally omitted from returned types. But omitting it doesn't agree with poor old bear:
from beartype import beartype

class Sneetch:
    @beartype
    def __init__(self, star: bool):
        self._upon_thars = star

    @beartype
    def __eq__(self, other) -> bool:
        if isinstance(other, Sneetch):
            return True  # Sylvester McMonkey McBean can pound sand
        else:
            return super().__eq__(other)

assert Sneetch(True) == Sneetch(False)  # all good
assert (Sneetch(True) == 42) is False  # boom

This will result in the following:
beartype.roar.BeartypeCallHintPepReturnException: @beartyped Sneetch.__eq__() return "NotImplemented" violates type hint <class 'bool'>, as "NotImplemented" not bool.

Making NotImplemented an explicit part of the return type is apparently hard (see python/mypy#4791).
I'm not sure what the right play is here. One could probably make a pretty good case that one should omit the @beartype decorator and lean on the internals (in which case, this should be closed as not-a-bug). But I thought I'd raise it anyway to get another opinion.

Wow! You're on a beartype issues roll today. Tell Matt what he's won, folks. It's... it's a Gold Star for Participation. Look, it's all the prize committee could afford. :medal_sports:

poor old bear

I chuckled. Then the bear growled and I stopped.
# Sylvester McMonkey McBean can pound sand

I chuckled even harder.
Phew! I think I got that outta my system. So, your astute observations and keen intuitive sense for hot problem spots in my code are yet again spot on. Mypy (even moreso than official PEP standards) is the de-facto authority on everything typing-related. What mypy does, we do.
You're in luck... again. Mypy does exactly what everyone wants, which means I now need to disembowel refactor beartype to do exactly the same thing. Specifically, mypy avoids raising warnings or errors for binary dunder methods (and only binary dunder methods) both annotated by and returning NotImplemented. Unsurprisingly, that's exactly what we'll do too.
It's time to roll up the white-collar tuxedo sleeves and actually do something. :man_in_tuxedo:

Fixed by 57e7e99. NotImplemented singleton: you have now been implemented.
Let's now excrete a new stable release containing all of these delectable goodies... and more! :candy:

… You're in luck... again.

For some definition of luck, perhaps. Or maybe the emphasis belongs on recognizing that it was exactly one of us who was lucky here.

Mypy does exactly what everyone wants.

It may be but a small consolation that this irony was not lost on me.

That means I now need to ~disembowel~ refactor beartype to do exactly the same thing. Global happiness ensues.

A part of me celebrates resolution. After reading 57e5e99, however, another part wonders with great trepidation, "What have I wrought?"

May we allpersevere with some sliver of hope that somehow the cure turns out not to be worse than the disease.

I am reluctant to reopen this, but I think restricting this behavior to methods that return bool is probably too narrow. Consider:
from operator import add as op_add
from numbers import Integral, Real
from typing import Union
from beartype import beartype
class Numberwang:
  @beartype
  def __init__(self, value: Union[float, Real] = 0):
    self._value = int(value)
  @beartype
  def __int__(self) -> int:
    return self._value
  @beartype
  def __eq__(self, other: "Numberwang") -> bool:
    return self._value == other._value
  @beartype
  def __add__(self, other) -> "Numberwang":
    return Numberwang(op_add(self._value, other)) if isinstance(other, Integral) else NotImplemented
  @beartype
  def __radd__(self, other) -> "Numberwang":
    return Numberwang(op_add(other, self._value)) if isinstance(other, Integral) else NotImplemented
Integral.register(Numberwang)  # <- a lie, but a noble one for illustration
import pytest
assert Numberwang(1) + Numberwang(1) == Numberwang(2)
assert Numberwang(1) + 1 == Numberwang(2)
assert 1 + Numberwang(1) == Numberwang(2)
with pytest.raises(TypeError):
  Numberwang(27) + "That's Wangernumb!"  # <- this will roar

The last line of the above will result in a beartype violation:
beartype.roar.BeartypeCallHintPepReturnException: @beartyped Numberwang.__add__() return "NotImplemented" violates type hint 'Numberwang', as "NotImplemented" not <protocol "__main__.Numberwang">.

I tried fixing it myself by broadening the hint coercion in cachehint.py via #40, but surprisingly encountered this: https://github.com/beartype/beartype/pull/40#issuecomment-873682231.

Brilliant! I hadn't realized Mypy also accepted non-boolean binary dunder methods, although that's painfully obvious in hindsight.
I also realized there's a related issue with our current approach: it doesn't permit unannotated returns. Interestingly, mypy does permit that and is thus totally down with this wacky tabacky:
class CodeGoneWild(class):
    def __add__(self, other):   # <-- this is fine, bro
        return (
            42 if isinstance(other, CodeGoneWild) else
            NotImplemented
        )

So, we also need to explicitly handle the case of binary dunder methods lacking return annotations. Both of us deserve a well-deserved break and it's not even Monday. :sob: