Availability through PyCharm

It would be great if this was available through PyCharm. Having trouble downloading the package and love the website emulator

Could you share exactly what you're having trouble with when downloading the package?
I agree, this definitely needs to be packaged as an extension. I'll make one for VS Code.

I appreciate your timely response!
So I have a couple of questions, is this package strictly for JavaScript? I
am tinkering with automating CURL requests with Python and love how your
web page filters and sorts through the Raw CURL request so elegantly. It
would be superb if a library for Python to work with your code. Secondly,
do we need permission to pull from the source code? I am getting an error
message stating I need to request permission to pull.
Nonetheless, your work here is pretty excellent. I have been tinkering with
alternative solutions to retrieving, filtering, classifying, and automating
CURL requests, and your page is a blessing.
On Fri, Jan 7, 2022 at 4:44 AM Boris Verkhovskiy @.***>
wrote:

Could you share exactly what you're having trouble with when downloading
the package?
I agree, this definitely needs to be packaged as an extension. I'll make
one for VS Code.
—
Reply to this email directly, view it on GitHub
https://github.com/curlconverter/curlconverter/issues/322#issuecomment-1007270044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG2COKT7HTY4HCJWRRWS4C3UU2YYZANCNFSM5LOKSUVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

curlconverter can also be used from the command line, but that's not really what you're asking.

curlconverter can be used from the command line, not just JavaScript. It also has a JSON output, which outputs a representation of the input command after the first step of parsing, though it's not as good as it could be.
So you could call it like this from Python through subprocess
import subprocess
import json

result = subprocess.run(['curlconverter', '--language', 'json', 'example.com'], capture_output=True)
result = json.loads(result.stdout)
print(result) # {'url': 'http://example.com', 'raw_url': 'http://example.com', 'method': 'get'}

or alternatively
import subprocess
import json

def parse_curl(command):
    result = subprocess.run(['curlconverter', '--language', 'json'], text=True, input=curl_command, capture_output=True)
    return json.loads(result.stdout)

print(parse_curl("curl --data helloworld example.com")) # {'url': 'http://example.com', 'raw_url': 'http://example.com', 'method': 'post', 'data': {'helloworld': ''}}

Note that you'll need to install the preview version of curlconverter for the new command line interface, which you can do with
npm install -g curlconverter@next

http://curlconverter.com/ also links to other project (scroll to the bottom) that try to do the same thing. There is a Python uncurl library, but I've never used it and have no idea how good it is.

am getting an error message stating I need to request permission to pull

if I understood correctly, I bet it's because you're pulling (cloning) over SSH and don't have an SSH key configured for github. The fastest thing would be to use HTTP:

i.e.
git clone https://github.com/curlconverter/curlconverter.git

I created the VS Code extension: https://github.com/curlconverter/curlconverter/issues/147#issuecomment-1008482048

Excellent!
Your code snippet ended up working haha but in my frustration I ended up
writing a filtering algorithm to filter a raw CURL text into headers,
cookies, data etc. based off of their set haha so I am parsing networking
requests pretty efficiently.
My next step is to be able to retrieve individual JSON variables to replace
them with my own inputs and use the same network requests to extract
different data points with my inputted variables.
I might be reinventing the wheel, but it is still an interesting project to
work on.
I will check out your VS Code extension! Your website does it pretty
amazingly! Thank you for your support as well.
On Tue, Jan 11, 2022 at 1:47 PM Boris Verkhovskiy @.***>
wrote:

I created the VS Code extension: #147 (comment)
https://github.com/curlconverter/curlconverter/issues/147#issuecomment-1008482048
—
Reply to this email directly, view it on GitHub
https://github.com/curlconverter/curlconverter/issues/322#issuecomment-1010259040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG2COKW6YD7WBF4GMVFAPC3UVR3NTANCNFSM5LOKSUVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm closing this as wontfix because there's a VS Code extension now and I'm not going to work on a PyCharm extension.
If someone wants to make one, they obviously can.


Equate Whiskey is a crime

🤷♂ There’s an option you can use to turn that on or off: if it’s a crime, then don’t equate! I’d also say that’s it’s a feature that you can swap ingredients in cocktails to make new ones, not a bug 😉

Whiskey is anything made from fermented grain mash. There are many types of whiskey, often very different in flavour, ingredients, and processing. For cocktails, the critical point is that there is a huge difference in flavour between these types and classes.
Below I present a selection of evidence that changing the whisky changes the drink:
A good example of this is the Collins. This cocktail has many variations with different names depending on the spirit chosen. Diffords highlights several versions with different types of whisky:

Captain Collins - Canadian whisky
Colonel Collins - bourbon whisky
Sandy Collins - Scotch whisky
Mike Collins - Irish whisky

Cocktail recipes differentiate between whiskies. IBA and Diffords, the two canonical sources of cocktail recipes clearly draw a line between different types of whisky.
In fact, a strong argument can be made that rum is less diverse than whisky. So why not equate rum? Putting dark rum in a recipe that specifies light rum will change a drink less than substituting rye for scotch.
Why treat whisky, the most popular and diverse spirit as one single type of drink but not do the same to Vodka, Rum, etc...
That said the app now has a pedantic mode which I feel does an equal disservice to all of the large classes of spirit. This seems much more fair 🤪.

While you are totally right, I would say that the equating you’re doing in your list of Collins’s is a perfect example of why equating makes lovely libations, and as a float on top I would like to add that the John and Tom Collins (both based in gin) were the originals, and therefore Whiskey is equated for Gin!
Note that oldfasioned.tech currently does list the original recipes, whether you’re in pedantic mode or not. I’m personally more in favour of creativity and inventing things, instead of being able to follow recipes to the letter. In normal-people-mode, you’re just allowed to make more drinks. No harm in that?! 🍸


deps: update tcmalloc from a08f5483 to 4addd0f7

Commit Message: deps: update tcmalloc from a08f5483 to 4addd0f7
Additional Description:
Update tcmalloc from https://github.com/google/tcmalloc/tree/a08f5483182f41ce626e3f66662966342bb448fa to https://github.com/google/tcmalloc/tree/4addd0f73112338b7425e8dcf744bd23b7bd866f
Pre-work of #21160. Ref it for more background info.
Risk Level: Mid.
Testing: n/a.
Docs Changes: n/a.
Release Notes: n/a.
Platform Specific Features: n/a.

cc @mattklein123

/retest

/retest

@phlax any concerns for this one?

any concerns for this one?

no  concerns from me - but i was waiting on a review from @mattklein123 as that was requested

This is pre-work of #21160. It's OK to waiting for a review from @mattklein123 or merge it directly (If there is no any concerns for other reviewers).

/retest

/retest

cc @mattklein123 friendly ping.


Use update instead of index for updating popularity data

I'm not looking at this at the moment, so closing.


Update Storage Quickstart to AndroidX

Apart from the update to storage v18, the contents here are all auto-generated. The app builds and runs.
This is obviously blocked on the public v18 release.

Being replaced by #883


Change templates to point to the new repo

The problem
We have a new repository under a new organization. We need to change that.
Suggestions
Do it fast.

I appreciate the effort but this just dropped all assignments from this repo. See https://colabti.org/irclogger/irclogger_log/raku?date=2019-11-25#l164 (also includes my angry rant).

Not a big deal. If someone wants to work on that specific issue, they'll
get reassigned to them all over again. They were never intended as hard
assignments, anyway.

Most of them are also closed. So, as I said, no big deal.

OK. I'm not sure what's going to happen with CI because IIRC that needs to be enabled in the organization separately, but I'm not sure. Let me know if you see any problems.

Sure. I think I have privs for that.

I can also use this chance to set up new GitHub actions instead.

@JJ this seems resolved with the relevant commit, is there anything else to update or can it be closed?

Besides translations of the README, only this line seems to be using the old repo
util/issue-with-all-pod6.p6:    my $repo-path =  S[doc] = '/perl6/doc/blob/master/doc' with $d;

I think we still need to check it out...


update Manifest to use registered ClimaLSM

PULL REQUEST
Purpose and Content
Upgrade Manifest to use ClimaLSM - registered version
Note that when I went to do so, there was a conflict between the IntervalSets compat in ClimaAtmos and ClimaLSM. I am broadening the compat in ClimaLSM to overlap with ClimaAtmos. That is the branch that is currently used in this PR. But, I'd like to wait to release another version of ClimaLSM until there are more changes, so this is on hold.

@kmdeck what other dependencies are requiring us to check in the Manifest for this experiment? If just LSM, we could remove the Manifest as long as the compat versions are specified in the Project.toml

we actually can use the current registered ClimaLSM if we upgrade the version of atmos we are using (I think) - I saw a PR in ClimaAtmos that bumps the compat of CA to include 0.7 for Interval sets, which is what ClimaLSM uses.
We may not need to check in the Manifest, Im not sure. Would the above still cause an issue, though? If CA and CLSM have compat entries that do not overlap?

Outdated and addressed in #143


Feature/select component

This PR adds the first basic version of the <Select> component which can be used as drop-down or drop-up depending on your needs (does not have any auto logic based on screen state).
NORMAL:

UPWARD:

@DominikGuzei select box looks great! 👍
What do you think about adding two keyboard event interactions:

close opened dropdown on ESC key
browse through dropdown options using up/down arrow keys (plus selection with ENTER key)?

@DominikGuzei I have added keyboard interaction (closing open dropdown on ESC key, changing selection with Arrows Up/Down and selecting highlighted option using ENTER key).
Besides that I have improved styling and fixed few bugs (e.g. it was not possible to open dropdown if you click on small arrow on the right side of the input).

@DominikGuzei I have added keyboard interaction (closing open dropdown on ESC key, changing selection with Arrows Up/Down and selecting highlighted option using ENTER key).
Besides that I have improved styling and fixed few bugs (e.g. it was not possible to open dropdown if you click on small arrow on the right side of the input).

In latest commit I have added support for FormField label click-to-focus feature.
This feature on input/textarea elements add's focus and on select-fields it opens dropdown.

@DominikGuzei I have added optionRenderer option for the select box ;)
Normal options:

Custom options:

@nikolaglumac pure awesomeness! 😃


Summer '23 release

feat: update to API v58.0

@msrivastav13 looks like a metadata test is failing:
CustomMetadataRecipes_Tests.testBucketingContactAttendancePositive
Fail
System.AssertException: Assertion Failed: Expected to find one matching bucketed picklist field for contact: Expected: 1, Actual: 0

Can you investigate?


Support dumping OVS flows for a Service with antctl

antctl get of -S antrea -n kube-system

FLOW
table=41, n_packets=0, n_bytes=0, priority=200,tcp,reg4=0x10000/0x70000,nw_dst=<IP_ADDRESS>,tp_dst=443 actions=group:5
table=42, n_packets=0, n_bytes=0, priority=200,tcp,reg3=0xad85d17,reg4=0x2286d/0x7ffff actions=ct(commit,table=50,zone=65520,nat(dst=<IP_ADDRESS>:10349),exec(load:0x21->NXM_NX_CT_MARK[]))
table=106, n_packets=0, n_bytes=0, priority=200,ip,nw_src=<IP_ADDRESS>,nw_dst=<IP_ADDRESS> actions=set_field:<IP_ADDRESS>->ip_src,load:0x1->NXM_NX_REG0[18],goto_table:110
group_id=5,type=select,bucket=bucket_id:0,weight:100,actions=load:0xad85d17->NXM_NX_REG3[],load:0x286d->NXM_NX_REG4[0..15],load:0x2->NXM_NX_REG4[16..18],load:0x1->NXM_NX_REG0[19],resubmit(,42)

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@cdfaeb4). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1877   +/-   ##
=======================================
  Coverage        ?   40.94%
=======================================
  Files           ?      116
  Lines           ?    14628
  Branches        ?        0
=======================================
  Hits            ?     5989
  Misses          ?     8130
  Partials        ?      509

Flag
Coverage Δ

unit-tests
40.94% <0.00%> (?)

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

/test-windows-conformance

/test-all

/test-all

/test-all

/test-all-features-conformance

/test-all-features-conformance

/test-all-features-conformance

/test-all


Transaction management in Rest API SOQL

I am unable to find any transaction management options when using Rest API using SOQL.
In my use case -
I am using 1 insert and then one update. If update fails then insert operation should be rolled back.
But after insert is done even after update is failed I am not able to roll back insert.
Can anyone please suggest how an insert (using SOQL ) can be rolled back.
Thanks in Advance!

I believe no long-running transaction (= transaction spread across several API calls) is available when using REST / (or even SOAP) API. Use Apex instead.

Thank you for reply.
I have these two operations in one single API. First insert and then
update. So i was wondering if it is possible to achieve in an api.
On Thu, 11 Oct 2018, 5:06 pm Shinichi Tomita<EMAIL_ADDRESS>wrote:

I believe no long-running transaction (= transaction spread across several
API calls) is available when using REST / (or even SOAP) API. Use Apex
instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jsforce/jsforce/issues/825#issuecomment-428922488,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbYSGSvu2uFKHPMk6d0PDtcnn4w0Ns51ks5ujy1ZgaJpZM4XVXQw
.

Maybe the composite resource might suit to your use case.
There is not special support in JSforce for composite request right now, but you can call the endpoint by Connection.request().
conn.requestPost('/composite/', {
    "allOrNone" : true,
    "compositeRequest" : [{
        "method" : "POST",
        "url" : "/services/data/v38.0/sobjects/Account",
        "referenceId" : "NewAccount",
        "body" : {
            "Name" : "Salesforce",
            "BillingStreet" : "Landmark @ 1 Market Street",
            "BillingCity" : "San Francisco",
            "BillingState" : "California",
             "Industry" : "Technology"
        }
    },{
        "method" : "GET",
        "referenceId" : "NewAccountInfo",
        "url"<EMAIL_ADDRESS>    },{
        "method" : "POST",
        "referenceId" : "NewContact",
        "url" : "/services/data/v38.0/sobjects/Contact",
        "body" : {
            "lastname" : "John Doe",
            "Title" : "CTO of @{NewAccountInfo.Name}",
            "MailingStreet"<EMAIL_ADDRESS>            "MailingCity"<EMAIL_ADDRESS>            "MailingState"<EMAIL_ADDRESS>            "AccountId"<EMAIL_ADDRESS>            "Email"<EMAIL_ADDRESS>            "Phone" : "1234567890"
        }
    },{
        "method" : "GET",
        "referenceId" : "NewAccountOwner",
        "url" : "/services/data/v38.0/sobjects/User/@{NewAccountInfo.OwnerId}?fields=Name,companyName,Title,City,State"
    },{
        "method" : "GET",
        "referenceId" : "AccountMetadata",
        "url" : "/services/data/v38.0/sobjects/Account/describe",
        "httpHeaders" : {
            "If-Modified-Since" : "Tue, 31 May 2016 18:13:37 GMT"
        }
    }]
})

Thank you very much. Will try and update you.
On Thu, 11 Oct 2018, 8:46 pm Shinichi Tomita<EMAIL_ADDRESS>wrote:

Maybe the composite resource
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_composite_record_manipulation.htm
might suit to your use case.
There is no special support in JSforce for composite request right now,
but you can call the endpoint by Connection.requestPost().
conn.requestPost('/composite/', {
"allOrNone" : true,
"compositeRequest" : [{
"method" : "POST",
"url" : "/services/data/v38.0/sobjects/Account",
"referenceId" : "NewAccount",
"body" : {
"Name" : "Salesforce",
"BillingStreet" : "Landmark @ 1 Market Street",
"BillingCity" : "San Francisco",
"BillingState" : "California",
"Industry" : "Technology"
}
},{
"method" : "GET",
"referenceId" : "NewAccountInfo",
"url"<EMAIL_ADDRESS>},{
"method" : "POST",
"referenceId" : "NewContact",
"url" : "/services/data/v38.0/sobjects/Contact",
"body" : {
"lastname" : "John Doe",
"Title" : "CTO of @{NewAccountInfo.Name}",
"MailingStreet"<EMAIL_ADDRESS>"MailingCity"<EMAIL_ADDRESS>"MailingState"<EMAIL_ADDRESS>"AccountId"<EMAIL_ADDRESS>"Email"<EMAIL_ADDRESS>"Phone" : "1234567890"
}
},{
"method" : "GET",
"referenceId" : "NewAccountOwner",
"url" : "/services/data/v38.0/sobjects/User/@{NewAccountInfo.OwnerId}?fields=Name,companyName,Title,City,State"
},{
"method" : "GET",
"referenceId" : "AccountMetadata",
"url" : "/services/data/v38.0/sobjects/Account/describe",
"httpHeaders" : {
"If-Modified-Since" : "Tue, 31 May 2016 18:13:37 GMT"
}
}]
})
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jsforce/jsforce/issues/825#issuecomment-428992415,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbYSGdD-TEGVk3iL4dsN1g_n286uTQGuks5uj2C4gaJpZM4XVXQw
.


Ignore .DS_Store file

Codecov Report

Merging #33 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   99.63%   99.63%
=======================================
  Files           4        4
  Lines         277      277
=======================================
  Hits          276      276
  Misses          1        1

Continue to review full report at Codecov.

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

@tisnik Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-33


Remove the InitializableService interface

Repeating my comment from https://github.com/eclipse-langium/langium/pull/1258#discussion_r1492320068:
Looking at it again, I'd rather remove the InitializableService interface: we already have onInitialize and onInitialized events in the LanguageServer service, which are the recommended ways to hook into the LSP lifecycle. The interface is only used by two core framework classes which require to invert the dependency. The interface is not necessary because LanguageServer hard-codes the calls to these classes anyway.

Actually I didn't want to pollute the service interface definitions like ConfigurationProvider and WorkspaceManager with the initialization stuff. In my customer project there's the need for more non-LSP services to be initialized with the workspace folders, so from my point of view the interface describes a standard way to implement that.
I also still have an idea in mind that is about providing an initialization hook via the constructors of DefaultConfigurationProvider and DefaultWorkspaceManager (and probably others), similar to the language server-based approach, but I didn't get to trying that, yet.
I don't have a strong opinion here.

In my customer project there's the need for more non-LSP services to be initialized with the workspace folders, so from my point of view the interface describes a standard way to implement that.

Do you need to separate the core part from the lsp part in that project? If not, you can simply inject LanguageServer in those non-LSP services and use the onInitialize event.

I added a change to avoid problems during initialization: WorkspaceManager and ConfigurationProvider run their initialized hook in parallel.


Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102300)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102400)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102500)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102600)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102700)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102800)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:44 GMT | got 100 objects from source elasticsearch (offset: 102900)
Tue, 17 Sep 2019 06:51:44 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 103900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 104900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 105900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 106900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 107900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 108900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 109900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110400)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110500)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110600)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110700)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110800)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 110900)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 111000)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 111100)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 100 objects from source elasticsearch (offset: 111200)
Tue, 17 Sep 2019 06:51:45 GMT | sent 100 objects to destination s3, wrote 100
Tue, 17 Sep 2019 06:51:45 GMT | got 96 objects from source elasticsearch (offset: 111300)
Tue, 17 Sep 2019 06:51:45 GMT | sent 96 objects to destination s3, wrote 96
Tue, 17 Sep 2019 06:51:45 GMT | got 0 objects from source elasticsearch (offset: 111396)
File uploaded!
Process finished with exit code 0

Tue, 17 Sep 2019 06:57:17 GMT | starting dump
Tue, 17 Sep 2019 06:57:18 GMT | got 100 objects from source s3 (offset: 0)
Tue, 17 Sep 2019 06:57:18 GMT | sent 100 objects to destination elasticsearch, wrote 100
Tue, 17 Sep 2019 06:57:18 GMT | got 112 objects from source s3 (offset: 100)
Tue, 17 Sep 2019 06:57:18 GMT | sent 112 objects to destination elasticsearch, wrote 112
Tue, 17 Sep 2019 06:57:18 GMT | got 130 objects from source s3 (offset: 212)
Tue, 17 Sep 2019 06:57:18 GMT | sent 130 objects to destination elasticsearch, wrote 130
Tue, 17 Sep 2019 06:57:18 GMT | got 122 objects from source s3 (offset: 342)
Tue, 17 Sep 2019 06:57:18 GMT | sent 122 objects to destination elasticsearch, wrote 122
Tue, 17 Sep 2019 06:57:18 GMT | got 408 objects from source s3 (offset: 464)
Tue, 17 Sep 2019 06:57:18 GMT | sent 408 objects to destination elasticsearch, wrote 408
Tue, 17 Sep 2019 06:57:18 GMT | got 519 objects from source s3 (offset: 872)
Tue, 17 Sep 2019 06:57:18 GMT | sent 519 objects to destination elasticsearch, wrote 519
Tue, 17 Sep 2019 06:57:18 GMT | got 1281 objects from source s3 (offset: 1391)
Tue, 17 Sep 2019 06:57:19 GMT | sent 1281 objects to destination elasticsearch, wrote 1281
Tue, 17 Sep 2019 06:57:19 GMT | got 2104 objects from source s3 (offset: 2672)
Tue, 17 Sep 2019 06:57:19 GMT | sent 2104 objects to destination elasticsearch, wrote 2104
Tue, 17 Sep 2019 06:57:19 GMT | got 7448 objects from source s3 (offset: 4776)
Tue, 17 Sep 2019 06:57:20 GMT | sent 7448 objects to destination elasticsearch, wrote 7448
Tue, 17 Sep 2019 06:57:20 GMT | got 34093 objects from source s3 (offset: 12224)
Tue, 17 Sep 2019 06:57:22 GMT | sent 34093 objects to destination elasticsearch, wrote 34093
Tue, 17 Sep 2019 06:57:22 GMT | got 65079 objects from source s3 (offset: 46317)
Tue, 17 Sep 2019 06:57:27 GMT | sent 65079 objects to destination elasticsearch, wrote 65079
Tue, 17 Sep 2019 06:57:27 GMT | got 0 objects from source s3 (offset: 111396)
Tue, 17 Sep 2019 06:57:27 GMT | Total Writes: 111396
Tue, 17 Sep 2019 06:57:27 GMT | dump complete

Process finished with exit code 0

Can you show your command?

--concurrency
10000
--intervalCap
10000
--concurrencyInterval
5000
--input
s3://backup-pg/es-all.json
--output
http://localhost:9200
--throttleInterval
0
--s3AccessKeyId
xxx
--s3SecretAccessKey
xxx
--s3ForcePathStyle
true
--s3Endpoint
https://my-s3-server.com

@ferronrsmith
Why my resault is different you

my S3 is ceph

minio

I know where the issue is. Rewriting the concurrency logic. I'll release the update in about 30 minutes

Me really looking forward

try the new release v6.10.0

thank you

I want to backup data to s3 from elasticsearch6.xx and restore data to elasticsearch7.xx from s3,
Will there be some errors ?

not for data. mappings/templates will have errors, since in ES 7 there were formatting changes.

I hava indexs a-1, a-2, a-3, b-1, b-2, b-3, c-1, c-2, c-3 ......, I want to backup all data except c-* to s3.  Do you have good command options which like regex mach index?, I dont't want'to wirte so many indexs in command,

I hava about 50 index in my elasticsearch
@ferronrsmith

No that's not supported. You can do regex export, but it would treat it as 1 export instead of 50. multi-elasticdump supports regex, but it dumps to a folder.


improve The error log should be printed by caller

Proposed changes
follow up: #34935
There are many segment files for a cache remote file, so the cached directory will create many times. Therefore, we should call fs->create_directory(dir, failed_if_exists=false) instead of fs->create_directory(dir, failed_if_exists=true)
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

LGTM


improve the integration tests that drops handshake packets

This makes the tests harder (by dropping 1/3 instead of 1/5 of packets) and more comprehensive (by also including a Retry handshake).

Codecov Report

Merging #2270 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2270   +/-   ##
=======================================
  Coverage   86.44%   86.44%
=======================================
  Files         107      107
  Lines        7882     7882
=======================================
  Hits         6813     6813
  Misses        806      806
  Partials      263      263

Continue to review full report at Codecov.

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


wrap paragraphs

0 changes, you can toggle to rich-diff switch.
If any change there is it will make them much easier to comment on, patch.

Ah, but you didn't wrap them how I would wrap them, so they will get re-wrapped differently when I edit :)

Just did the default wrapping. I know you can do semantic wrapping, just one enormous line is horrible.


Feedback/Flash messages

Feedback/Flash messages are only available to the next request.

What are your plans for this?

I don't know if it's a priority right now.
I thought little about implementation and what I see now it's to save these type of messages on session and to remove that messages from session on the next request. What I don't like me with this implementation is that it's not stateless but I think that the implementation is clean enough. Maybe it's valuable to add a "stateless" implementation for Session (ClientSession or other name - keep state in a cookie similar with play and ninja).
How you see things?

I'm still formulating my opinion on server-side session vs.
session-as-cookie.  I think Session should be an interface so we can choose
different backends.
Storing in a session is likely the right place but right now that data
does not automatically go to the template engine.  Response.locals() is
sent to the template engine but that does not include session attributes.
As a start, if a session exists we should probably automatically include
it's attributes in Response.render() OR inject the session itself
put("session", request.getSession()) into the map generated in
Response.render().

I created a branch flash and I tried to propose an implementation for this feature.
I see some little issues (in implementation) but I think that they are not stoppers.

I added some inline comments in the commit https://github.com/decebals/pippo/commit/75734301c8b32997bb7180fc56d2c2ad9ec3979c#comments

This looks good.  Minor improvements...

flash.warn(), flash.info(), etc.
flash.warn("here is my {} message", "test");

I think a "flash" key convention is great.

Resolved by #90.


Create reconvilier.json

Dis moi si c'est bon Hook

@MathieuNls test

Adding logo here as I don't have write access in the logo folder

You forgot to add reconvilier to the watch-brand.json


Large notebook text outputs can't be wrapped

Does this issue occur when all extensions are disabled?: Yes
As described in the title and the clip below will say the rest, the canvas seems overwhelmed with the output and doesn't wrap it.
https://user-images.githubusercontent.com/60842560/139567418-a38697ff-0a3e-4880-80de-21afd37963f5.mp4
The log:
[36297:1031/112848.622152:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x1414a4079800] GL_INVALID_FRAMEBUFFER_OPERATION: Draw framebuffer is incomplete

Because the lower trimmed part are wrapped, it thinks it don't have to show the scrollbar so we can't view the rest if the line is long enough. This is critical.

If we put some colors, we will see the lines overflow at the edge:

Smaller outputs are fine:

System info
Version: 1.62.0-insider
Commit: ff1e16eebb93af79fd6d7af1356c4003a120c563
Date: 2021-10-29T07:49:33.336Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.11.0-38-generic

I haven't got a chance to test on other OSs.
This is my test notebook: https://gist.github.com/thanhph111/b6471bfa16603e56af351447c3cd29de.

@rebornix, this is just a bug, but could probably be considered as part of the discussion about https://github.com/microsoft/vscode-jupyter/issues/7096.

@thanhph111, thanks for the feedback. What are your thoughts on the current behavior, where we supply a link at the top of the output that allows you to open the output in a separate editor tab? This behavior can indirectly essentially solve problems like this.

@rebornix I'm taking this with the assumption you're not currently looking at it.


Circuit can be connected in-use device interface

To reproduce:

create two access switch devices (sw1 and sw2) each with ifaces 0-10.
connect iface 0 on sw1 on to iface 0 on sw2
create a circuit and select iface 0 on sw1 for the A side and select iface 0 on sw2 for the B side

This only appears to be an issue when first creating the termination. If I edit the termination and change it to iface 5 on sw1, save and then try to change it back to iface 0 on sw1 it's grayed out.

I've marked this as fixed because connected interfaces now show up as disabled in the selection lists, however I've opened #1269 to extend the API so that we can also check for circuit connections.


Bug with use

I install plagin and in the file editor.js just imported this plugin and wrote editor.use(VueRenderPlugin).
Why I have this error: TypeError: Object(...) is not a function?

After 2 days i dont know what happens but now all is work


Fix exclude arg

Just fixing a minor issue I found while using the policy generation script. Included a bit of setup help while I was working.

No problem. Also agreed I wish PyYaml were a core library. Thanks for merging!


The css attribute inset  is not supported on Chrome 86

i am using @unocss/preset-uno rule.
Do you have a better solution?

Override with shortcut

Override with shortcut

https://unocss.antfu.me/play/?html=DwEwlgbgBAxgNgQwM5ILwCIwDskFMAuAtAAzoB8wA9OBGQFCiSyIobZ5EAcADgB7pRK9RtHjI0mHAUK8SAoQxrNxbKUQCecwfSA&config=JYWwDg9gTgLgBAbwFBzgEwKYDNgDsMDCEuOA5gDQpxhQYDOGMAgjDFMAEYCuMwWAnpVQ16jAJIBjYnSHVaDGAFVcESgF84WKBBBwA5FxUS6dPUiQYAHpFjpsAQy4AbeJhz4iJYKQAUyVFDO9ABccADaVKhhehJcdDA6ALSBThh65IhwUk7QoXq0aHpwagC6VCWydAAW0DCxMHShEahRAPQAengKiT4AdADUAJQAJK0ZPmEZdCWDcAC8AHxwAAYJYInDCHQa7KRVMBtbGhwQrEmb23CpWAcXassV5bIiCo3hkXKiSio%2Bg7LC8kYLDYnB4fH4v3%2BnwUkmkfg%2BqDoEnsqVCAEZegAmKGoCRoXB5fYwMCNVqteggXrVVpmFrFP7lJBqQZIIA&options=N4IgLgTghgdgzgMwPYQLYgFwKgGzgUwF8g

you mean this?(regex should be sort in order) [x,y, other]
export default defineConfig({
  rules: [['custom-rule', { color: 'red' }]],
  shortcuts: [
    [/^inset-x-(.+)$/, ([, s]) => `right-${s} left-${s}`],
    [/^inset-y-(.+)$/, ([, s]) => `top-${s} bottom-${s}`],
    [/^inset-(.+)$/, ([, s]) => `top-${s} right-${s} bottom-${s} left-${s}`],
  ],

more complex shortcut should be used to handle [xy]. something like
        [/^inset-?([xy])?-(.+)$/, ([_, d, s]) => d
          ? d === 'x' ? `left-${s} right-${s} ` : `top-${s} bottom-${s}`
          : `left-${s} right-${s} top-${s} bottom-${s}`,
        ],

This is a good idea, but in windicss or tailwindcss, the inset syntax is left right top bottom. I think they are not consistent

This is just a sample.
I don't know what's the correct setting of windi or tailwind.
So I  just set as xy word meaning. (x for x-dimension -> left/right, y for y-dimension -> top/bottom)
feel free to change the setting value as you demand.

Your solution is great.
I mean the @unocss/preset-uno whether should change this rule.This may need to be decided by the project maintainer


cypress-registration

GJ!
P.S. You should generate the user and another test data in another file, not in the config one.


Ensure all assets are unique to each project

Going forward all assets should be unique to each project and not shared between

For simplicity sake, delete any duplicate assets that are soft deleted:
DELETE FROM project_asset
WHERE asset_id IN (
    SELECT asset_id
    FROM project_asset
    GROUP BY asset_id
    HAVING COUNT(asset_id) > 1
) AND deleted_on IS NOT NULL

Then query all remaining duplicate assets:
SELECT *
FROM project_asset
WHERE asset_id IN (
    SELECT asset_id
    FROM project_asset
WHERE deleted_on is NULL
    GROUP BY asset_id
    HAVING COUNT(asset_id) > 1
)

There are 191 rows on staging that share the same asset_id with another row.
All are of type MODEL, DATASET, or DOCUMENT.

Closing this as we will instead be wiping staging and prod


When inserting a number in a string field as first character, it becomes a number, and there is no way to type text anymore

If i insert a number as first value of a string, leva makes it become a number and cannot insert text anymore..

Arf that's a bummer and was introduced by the latest version. I'll see what I can do to fix this.

@monkyver actually it wasn't introduced by the latest version!
The reason why this happens is that a text following a number is considered as a unit. But that doesn't make sense for long units. For now, I've considered a unit any text that is 3 characters max. Let me know if this fixes it for your use case.

Actually we solved the issue adding this:
type: LevaInputs.STRING,


No Data

I am only getting
PLEX: NOW PLAYING
Plex Data ....
Maybe Im missing something ?

Can you give some more info?
A photo or screen shot of the output?
The config options used (NOT your Plex token)?
Goto the following address and get the XML data that shows up:
<your_server_IP>:<your_server_port>/status/sessions/?X-Plex-Token=<your_plex_token>

Ok, everytime I go through the motions to get my Token from Plex, it changes...

I do show XML data in that link now..... But MM still shows the same message

Can you post the XML data here, preferably when you're playing something.
For the Plex token, you can have multiple active ones.  I believe it is a token per player, so if you invalidate the player on the server, you would need a new token.

This XML file does not appear to have any style information associated with
it. The document tree is shown below.

On Mon, Mar 30, 2020 at 3:36 PM glitch452<EMAIL_ADDRESS>wrote:

Can you post the XML data here, preferably when you're playing something.
For the Plex token, you can have multiple active ones. I believe it is a
token per player, so if you invalidate the player on the server, you would
need a new token.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/glitch452/MMM-PlexNowPlaying/issues/5#issuecomment-606202456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABP3C3SIRS23NFY4YAPZ6HDRKDYD3ANCNFSM4LW2NADQ
.

This XML file does not appear to have any style information associated with it. The document tree is shown below.

WHEN NOTHING IS PLAYING

Okay, I took a look at the XML and it is a little different than what my Plex server produces for the /status/sessions/ endpoint.  The XML data you sent seems to be missing some playback information like the viewOffset field in the main video tag.  It's also missing session and player tags.  It seems like this is data from the movie description endpoint, not the sessions endpoint?
I'm running Plex server version  <IP_ADDRESS>71 on Windows.
Which platform and version are you running?

You should create an Plex Token just for the magic Mirror.
Is your server running with Encryption on it?

This is what I did.

Create an Plex Authorization-Token for a custom App using python3 in a shell script
https://gist.github.com/fleXible/709e4583086b926646cb5304361693b4
I'm Here to assist if I can.


Show notices and errors inline

Fixes #114.
Display received notices and errors in currently active channel, if the actual target is the network lobby. Reloading the page will put them back into the lobby window.

:tada:
I assume that query windows will return false for chan.hasClass('lobby')? One of the bots I get notices from frequently is also useful to keep a PM window open to, so I'm guessing the current behavior of its notices going to that query window will not change with this PR.
Still :tada: overall though, since I can just close the query as a workaround.

@dgw Yes, it only applies the active window logic only if the intended target is lobby.

Reloading the page will put them back into the lobby window.

Any way to fix this? That would be pretty bad :/

@astorije, that's not exactly a bug. Otherwise this gets super tricky with multi client support.

Is it please possible to differentiate which notices goes in active channel and which goes into server window? All the notices from IRC server when joining network (see screenshot below) is quite a lot of information which for most users are not important nor nice to have in active channel.
e.g. If notices from server when joining network -> send to server window. Else, send notices to active channel.

@xPaw, instead of showing errors inline, maybe we should have them shown at the top of the screen like error messages often do. Kinda how we currently show connection errors, except at the top instead of bottom.
What do you think?

@astorije, that's not exactly a bug. Otherwise this gets super tricky with multi client support.

Honestly, having things disappear on reload (well, moved somewhere else but the effect is the same) is just something we should try to avoid :/
What alternatives do we have?

@astorije As @YaManicKill said, it's an unfortunate design of notices on IRC. We have to reset them to server window (well technically they're always there on the server) due to our support for multiple clients at once. It gets hairy either way.
As for your error design, how are you going to contain these errors within the network?

As for your error design, how are you going to contain these errors within the network?

I don't think we have to. If an error shows up on Freenode while you're browsing a channel on another network, the banner should say something like "Blabla happened on Freenode" or whatever.
The idea is that error banners would stay until closing them and persist when switching channels. There are many ways we could do that, and I can see a few paradigms that exist in other app that would apply to us. This needs experimenting though.


When reopening a folder, the panel created by Agda-mode is restored as an empty window

It can be reproduced by loading a file in a folder, closing vscode and reopening the folder.
It doesn't affect functionality, but it's annoying.

Patch on the way!

Thanks!
By the way, I'm planning to implement a Unicode input method for Agda on
macos. I think this would reduce the effort required to maintain agda-mode.
Ting-gian LUA @.***> 於 2024年11月28日 週四 09:25 寫道：

Patch on the way!
—
Reply to this email directly, view it on GitHub
https://github.com/banacorn/agda-mode-vscode/issues/197#issuecomment-2505089545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7LA2WI32RFD6W6ZVIRNKL2CZWH5AVCNFSM6AAAAABRMVWB4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGA4DSNJUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Incorporating forms into web viewer

Hi,
I am using the default viewer but some of my PDF's contain and need to display dropdowns/textbox/etc. I was hoping someone could guide me on how to enable the form elements  in the main default viewer.
I am using this fork to display the form elements:
https://github.com/mainegreen/pdf.js/tree/master/examples/forms
My question is how do I combine this in the main viewer?
Thanks.

Forms are not fully implemented yet, please follow https://github.com/mozilla/pdf.js/projects/1 . There is the renderInteractiveForms preference to turn on forms support in the demo viewer, you can use that. Closing as answered.

Perfect thank you Yury!


Cannot install crisp-api using pip

Hi,
I plan to use the Crisp API lib in Python but I cannot install it with pip.
I think the issue is due to the last pull request who has not been pushed to the pip servers.
So in the setup.py the encoding='utf-8' is not present and pip during the install cannot read the README.md file : UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 226: character maps to <undefined>.
Can you update pip server with the latest code.
Thanks !

Hello team,
Following my pull request you updated the repo but not the pip package. Could you please make an update to the pip package? I'd rather not have a public git URL in my pip requirements file.

Hello there, tried publishing on PyPI, but it's now failing as README formatting in Markdown has been deprecated. I'll need to convert to the proper README format and then upload; for now I'm unable to upload the package.
Can you please install it from Git instead?

Opened an issue to track this #7

Hi Valerian,
No worries, that is currently what I’m doing, it is not urgent but preferred. 😊
Thanks for your reactivity!
From: Valerian Saliou<EMAIL_ADDRESS>Sent: dimanche 22 décembre 2019 20:59
To: crisp-im/python-crisp-api<EMAIL_ADDRESS>Cc: Antoine Chopin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [crisp-im/python-crisp-api] Cannot install crisp-api using pip (#6)
Hello there, tried publishing on PyPI, but it's now failing as README formatting in Markdown has been deprecated. I'll need to convert to the proper README format and then upload; for now I'm unable to upload the package.
Can you please install it from Git instead?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/crisp-im/python-crisp-api/issues/6?email_source=notifications&email_token=ACO2HBMZ65UM4OEZS2J3JKTQZ7BGTA5CNFSM4IGOISPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPYXSA#issuecomment-568298440 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACO2HBOZ4YZNZXF26JDZZVTQZ7BGTANCNFSM4IGOISPA .  https://github.com/notifications/beacon/ACO2HBJNRJS5YBD3OJWGKRLQZ7BGTA5CNFSM4IGOISPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPYXSA.gif

Hello there, your changes have been taken into account with release 1.1.3 :)
Published on PyPI: https://pypi.org/project/crisp-api/


feat: improve rc release to release only affected package

This is a feature request
Problem
Right now is https://github.com/waku-org/js-waku/actions/workflows/pre-release.yml is triggered - all packages will be released.
Proposed Solutions
We want to release only those that actually have any changes so that if edit happened in @waku/interface and @waku/core - only they should be published to npm.

Low priority task.


Today is 10.1

Test git operation，Please ignore。

@zhaoliangfeng Please don't use other people's repos for testing out GitHub!


Include the test class in the Description

I'm trying to design a JUnit4 Rule and have run into an issue with tests using Burst, because the Description passed to my rule returns null from getTestClass().
It looks like this line is the source of the Description in question, as it passes a custom string instead of a className.
Would Burst be open to fixing this? Something like:
return Description.createTestDescription(
    getTestClass().getJavaClass(),
    getName() + ":" + method.getName(),
    method.getAnnotations());

Is sufficient for my use case, though it does change the result of Description.getDisplayName(). If that works I'm happy to send a PR, otherwise are there other approaches you might be open to?

I think this is probably fine, but it's been so long the nuances of descriptions are definitely lost on me. The only real concern, I think, is the effect on the IDE experience.

Yeah, I'm not sure if there's a specific format for the second argument that would be most-correct, but seeing as nothing's blown up with the malformed className I'd hope IDEs can handle a change like this? :crossed_fingers:

Turns out this bug is also restricting paparazzi from working with burst.


Add version information to scale

Add version/git information to the Scale UI.

Closed when static demo was merged into develop


Performance vs traditional server

Are there any benchmark comparisons to see the response times compared to a traditional server running Rails and Puma?

Normal expectation is to see better performance than running on K8s.
I think I touched on this somewhere deep in the guides... but Lamby recommends running at 1vCPU which is 1792 memory. You dont need all the memory, you need the 1vCPU. Most other container orchestration systems leverage under provisioned min memory to overcommit resources and get scaling to work. This ends up with slower Rails apps and request queuing. Not saying a pro could not tune these things to get near Lambda, but I've seen even expert teams not do it well.
I can create a guide page on that if you are interested. In fact. Think I will. I need to document all this stuff for a talk too. How does that sound so far? Wanna ask more questions on the topic? Happy to discuss.

A page in the guide for this would be super helpful! I was looking into this as a potential solution for a startup. My first question was "is there a performance tradeoff?" because it seems like there might be some extra overhead/latency. I'm very experienced with scaling Rails apps, but very unfamiliar with Lambda.
I'm constantly building new companies and I always start with three options: self-host with Dokku, use a middleman like Cloud66/Hatchbox, or use a PaaS like Heroku/Render/Fly. Lamby is very appealing because it can scale to zero and has virtually (I think?) no limits.
Here's some questions off the top of my head:

How does Lamby compare to a typical server running Puma? Response times would probably be a good metric to start with
I saw "up to" 6 vCPUs on the home page. What happens when you need more than that?
On the How it Works page, there's this: "A small pool of concurrent functions can handle a large amount of traffic". Some benchmarks to elaborate on that would be amazing

I've got more, but I think that's just me needing to read through the Lambda docs to understand it better. A page in the Lamby docs that shows performance comparisons and any scaling limitations would give me the complete picture I need to make a decision
At some point in the future my curiosity will inevitably get the best of me and I'll try this out. When that happens I'd be happy to document my results if you want/need them

because it seems like there might be some extra overhead/latency

No, none. I've seen more latency in K8s figuring out auto scaling with memory or cpu which translates into request queue latency that adds up. Only thing would be cold starts, but that is mostly moot too. More so if you app is uses a lot. It disappears well past the 99th percentile metrics. BTW, speaking of cold starts, have you seen the new news about proactive inits? This make it even more of a none issue. But honestly, it never was. This is icing on the cake.
https://lamby.cloud/blog/2023/07/16/goodbye-cold-starts-hello-proactive-initilizations

Lamby is very appealing because it can scale to zero and has virtually (I think?) no limits.

Yea, that was a great list. I'm constantly trying to make Lamby more appealing to start ups and SaaS bootstrapers like yourself.

How does Lamby compare to a typical server running Puma?

Equal or better. The idea of Puma is that you have to get some number of workers (or threads) to maximize some Xyz value of memory and CPU. It's all a game of getting to some utilization of a single virtual "machine". With Lambda there is no Webserver... you just get Rack events. So every function is a new instance and the reverse proxy is API Gateway or Furls. I think I covered this well here:
https://speakerdeck.com/metaskills/the-case-for-rails-on-lambda-v1

What happens when you need more than that?

You do not. For Rails you give it 1vCPU and scale horizontally like every other person does it. In this case, you do not have to manage the scaling. The Lambda control plane (Firecracker) does that for you. I've never seen Rails need more. Even big large legacy apps.

Some benchmarks to elaborate on that would be amazing

Cool, you might see those in the deck I shared above.

When that happens I'd be happy to document my results if you want/need them

I appreciate that. I think I got most of the data... just need to wrap it up better in a single place. Of course, if you have any new info, outliers, etc... please share!

scale horizontally like every other person does

Let me qualify that... everyone scales horizontally... but you only need more than 1vCPU in other compute platforms because you are stuffing more puma workers, etc in a virtual machine. At the end of the day it is 6 of one and half dozen of the other. For Lambda, you are using distinct functions to truly scale horizontally. You really cant do it any other way... nor is there a need to. Hope that makes sense.


duplicateTab says "This makes a copy of the current tab and opens it." but what is copied ?

From https://github.com/microsoft/terminal/issues/9577

Here:
docs.microsoft.com/en-us/windows/terminal/customize-settings/actions
I read
**Duplicate tab**
This makes a copy of the current tab and opens it.

but what is copied ? What is the difference with a "New tab" ?
I mean: not what was printed previously in cmd.exe for example.
And, for cmd.exe, modified/added ENV VARIABLES are not "copied" =)

Updated the description: https://github.com/MicrosoftDocs/terminal/commit/d8e2ed70811c989875e2e1e3598366f8d799e7dc
Thanks! :)


Empty body when there is a file attachment

Describe the bug
Returns an empty body when there is an attachment on the email. Already tried office 365 and gmail.
Used config
I already tried to remove the inline from the disposition array.
    'options' => [
        'delimiter' => '/',
        'fetch' => \Webklex\PHPIMAP\IMAP::FT_PEEK,
        'sequence' => \Webklex\PHPIMAP\IMAP::ST_MSGN,
        'fetch_body' => true,
        'fetch_flags' => true,
        'message_key' => 'list',
        'fetch_order' => 'asc',
        'dispositions' => ['attachment', 'inline'],
        'common_folders' => [
            "root" => "INBOX",
            "junk" => "INBOX/Junk",
            "draft" => "INBOX/Drafts",
            "sent" => "INBOX/Sent",
            "trash" => "INBOX/Trash",
        ],
        'open' => [
            // 'DISABLE_AUTHENTICATOR' => 'GSSAPI'
        ],
        'decoder' => [
            'message' => 'utf-8', // mimeheader
            'attachment' => 'utf-8' // mimeheader
        ]
    ],

Code to Reproduce
The troubling code section which produces the reported bug.
$message->getHTMLBody(); or $message->getTextBody()

Additional context
I tried to look for all the attachment being fetched, there is always an undefined file which have a text/html mimetype (This only happens when there is an file attachment).
php: 7.2.5, using an 2.3 php-imap when the issue occured, but I already updated to both laravel-imap latest version.

Duplicate of https://github.com/Webklex/php-imap/issues/91

Duplicate of https://github.com/Webklex/php-imap/issues/91


Suggest we reference a specific version of CommonMark

http://spec.commonmark.org/0.27/

CommonMark is updated every few months (four times in 2016; it is not even a 1.x release, and it will probably rev several times in OpenAPI 3.0's lifetime) I suggest we claim a minimum version and not fix it on 0.27, but note that a 1.x version may have incompatible changes and OpenAPI 3.0 tools need only support CommonMark features compatible with 0.27

I'm going to add a new paragraph near the beginning of the spec that talks about using Markdown and references the CommonMark spec.
@DavidBiesack I'm not sure what the difference is between saying "OpenAPI supports CommonMark 0.27" and saying "at minimum 0.27 is supported".   If a tooling vendor decides to support something only introduced in markdown 0.28 I doubt that validators will raise an error.  Giving a warning might not be a bad idea, because some tooling might not support it.
Once we set a minimum any feature beyond that version steps into unknown territory.


Calligraphy 2.0 breaks RecyclerView theme's colorEdgeEffect

Hi,
We're using a RecyclerView in our app with a custom colorEdgeEffect that is different from the main app's colorPrimary. When I upgrade our app from Calligraphy 1.1.0 to version 2.0.0, the colorEdgeEffect reverts to the old color and not the custom one we have in the theme. Is this reproducible from your end?

It is not, this works for me on my main project.


About merge lora weight and lora dropout

Description:
The Dropout layer behaves differently during training and evaluation, leading to inconsistent behavior in the lora_A module. Specifically, during training, dropout(x) will drop some outputs of XA, whereas during evaluation, dropout is disabled and a scaling factor of 1-p is multiplied with XA. To ensure that the merged LoRA weights exhibit the same behavior as the un-merged LoRA weights, the dropout scaling should be applied within the merge method as well. Currently, it appears that PEFT does not handle this discrepancy.
Question
Is there any special handling for dropout scaling in the PEFT library that I might have missed?
Related code
Merge method
    def merge(self, safe_merge: bool = False, adapter_names: Optional[list[str]] = None) -> None:
        """
        Merge the active adapter weights into the base weights

        Args:
            safe_merge (`bool`, *optional*):
                If True, the merge operation will be performed in a copy of the original weights and check for NaNs
                before merging the weights. This is useful if you want to check if the merge operation will produce
                NaNs. Defaults to `False`.
            adapter_names (`list[str]`, *optional*):
                The list of adapter names that should be merged. If None, all active adapters will be merged. Defaults
                to `None`.
        """
        adapter_names = check_adapters_to_merge(self, adapter_names)
        if not adapter_names:
            # no adapter to merge
            return

        for active_adapter in adapter_names:
            if active_adapter in self.lora_A.keys():
                base_layer = self.get_base_layer()
                if safe_merge:
                    # Note that safe_merge will be slower than the normal merge
                    # because of the copy operation.
                    orig_weights = base_layer.weight.data.clone()
                    delta_weight = self.get_delta_weight(active_adapter)
                    if not self.use_dora[active_adapter]:
                        orig_weights += delta_weight
                    else:
                        # handle dora
                        # since delta_weight already includes scaling, set it to 1 here
                        weight_norm = (
                            self.lora_magnitude_vector[active_adapter]
                            .get_weight_norm(orig_weights, transpose(delta_weight, self.fan_in_fan_out), scaling=1)
                            .detach()
                        )
                        # We need to cache weight_norm because it has to be based on the original weights. We
                        # cannot calculate it on the fly based on the merged weights when unmerging because its a
                        # different value
                        self._cache_store(f"{active_adapter}-weight_norm", weight_norm)
                        dora_factor = self.lora_magnitude_vector[active_adapter].weight / weight_norm
                        dora_factor = transpose(dora_factor.view(-1, 1), self.fan_in_fan_out)
                        orig_weights = dora_factor * (orig_weights + delta_weight)

                    if not torch.isfinite(orig_weights).all():
                        raise ValueError(
                            f"NaNs detected in the merged weights. The adapter {active_adapter} seems to be broken"
                        )

                    base_layer.weight.data = orig_weights
                else:
                    delta_weight = self.get_delta_weight(active_adapter)
                    if not self.use_dora[active_adapter]:
                        base_layer.weight.data += delta_weight
                    else:
                        # handle dora
                        # since delta_weight already includes scaling, set it to 1 here
                        weight_norm = (
                            self.lora_magnitude_vector[active_adapter]
                            .get_weight_norm(
                                base_layer.weight, transpose(delta_weight, self.fan_in_fan_out), scaling=1
                            )
                            .detach()
                        )
                        # We need to cache weight_norm because it has to be based on the original weights. We
                        # cannot calculate it on the fly based on the merged weights when unmerging because its a
                        # different value
                        self._cache_store(f"{active_adapter}-weight_norm", weight_norm)
                        dora_factor = self.lora_magnitude_vector[active_adapter].weight / weight_norm
                        dora_factor = transpose(dora_factor.view(-1, 1), self.fan_in_fan_out)
                        new_weight = dora_factor * (base_layer.weight.data + delta_weight)
                        base_layer.weight.data = new_weight

                self.merged_adapters.append(active_adapter)

Compute lora weight method
    def get_delta_weight(self, adapter) -> torch.Tensor:
        """
        Compute the delta weight for the given adapter.

        Args:
            adapter (str):
                The name of the adapter for which the delta weight should be computed.
        """
        device = self.lora_B[adapter].weight.device
        dtype = self.lora_B[adapter].weight.dtype

        # In case users wants to merge the adapter weights that are in
        # (b)float16 while being on CPU, we need to cast the weights to float32, perform the merge and then cast back to
        # (b)float16 because some CPUs have slow bf16/fp16 matmuls.
        cast_to_fp32 = device.type == "cpu" and (dtype == torch.float16 or dtype == torch.bfloat16)

        weight_A = self.lora_A[adapter].weight
        weight_B = self.lora_B[adapter].weight

        if cast_to_fp32:
            weight_A = weight_A.float()
            weight_B = weight_B.float()

        output_tensor = transpose(weight_B @ weight_A, self.fan_in_fan_out) * self.scaling[adapter]

        if cast_to_fp32:
            output_tensor = output_tensor.to(dtype=dtype)

            # cast back the weights
            self.lora_A[adapter].weight.data = weight_A.to(dtype)
            self.lora_B[adapter].weight.data = weight_B.to(dtype)

        return output_tensor

Forward method of a lora layer
    def forward(self, x: torch.Tensor, *args: Any, **kwargs: Any) -> torch.Tensor:
        self._check_forward_args(x, *args, **kwargs)
        adapter_names = kwargs.pop("adapter_names", None)

        if self.disable_adapters:
            if self.merged:
                self.unmerge()
            result = self.base_layer(x, *args, **kwargs)
        elif adapter_names is not None:
            result = self._mixed_batch_forward(x, *args, adapter_names=adapter_names, **kwargs)
        elif self.merged:
            result = self.base_layer(x, *args, **kwargs)
        else:
            result = self.base_layer(x, *args, **kwargs)
            torch_result_dtype = result.dtype
            for active_adapter in self.active_adapters:
                if active_adapter not in self.lora_A.keys():
                    continue
                lora_A = self.lora_A[active_adapter]
                lora_B = self.lora_B[active_adapter]
                dropout = self.lora_dropout[active_adapter]
                scaling = self.scaling[active_adapter]
                x = x.to(lora_A.weight.dtype)

                if not self.use_dora[active_adapter]:
                    result = result + lora_B(lora_A(dropout(x))) * scaling
                else:
                    x = dropout(x)
                    result = result + self.lora_magnitude_vector[active_adapter](
                        x,
                        lora_A=lora_A,
                        lora_B=lora_B,
                        scaling=scaling,
                        base_layer=self.get_base_layer(),
                    )

            result = result.to(torch_result_dtype)

        return result

import numpy as np
def inv_train(rate,x,w1,b1,w2,b2):
layer1=np.maxinum(0,np.dot(w1,x)+b1)
mask1=np.random.binomial(1,1-rate,layer1.shape)# random.binomial(n, p, size=None)
layer1=layer1*mask1
layer1/=1-rate

layer2=np.maxinum(0,np.dot(w2,layer1)+b2)
mask2=np.random.binomial(1,1-rate,layer2.shape)# random.binomial(n, p, size=None)
layer2=layer2*mask2
layer2/=1-rate

return layer2

def inv_test(x,w1,b1,w2,b2):
layer1=np.maxinum(0,np.dot(w1,x)+b1)
layer2=np.maximun(0,np.dot(w2,layer1)+b2)

return layer2

Actually do not need to re-scale the lora weight, my bad

Thanks for bringing this up and then investigating this further. I think this is solved, which is why I'm closing the issue. If there are still open questions, feel free to re-open the issue.


How do I exclude a path from a route path?

Hello,
I am trying to exclude a path from a route.
This is my route:
{ path: '*', component: NotFound, status: 404 }
I would like to exclude the path /assets How could I do that?
I am using react-router version 3.0.0-alpha.1

Based on the /assets name, I assume that you mean on a server, in which case you should have a different request handler for your static assets. If you're using express, that would be something like this:
const app = express();
app.use("/assets", express.static(__dirname + "/assets/"));
app.get('*', function(req, resp) {
  // do the react router request matching here
});

If you don't mean on the server, then the only way to ensure that the wildcard matches is to have a route whose path is /assets that comes before your wildcard route.
Also, you should probably update to the latest version of v3 (currently 3.0.5).


Feature/liayoo/state size mgmt

Added 'state' rule property

A state rule consists of 'max_children' and 'ordering'.
If the # of children exceeds max_children, children will get evicted (deleted) according to the ordering (only 'FIFO' is supported for now)
State rules are only applied to the exactly matching paths
As-is

{
  ".rule": {
    "write": true
  }
}

To-be

{
  ".rule": {
    "write": true,
    "state": {
      "max_children": 100,
      "ordering": "FIFO",
    }
  }
}

Added state rules to native services

Offline discussion summary:

To extend state permission to max_height, max_size, max_bytes (from max_children)
To rename garbage collecting rule to 'gc_max_siblings' and change it's location from the parent state to the child state in the rule tree (/rules)
Apply garbage collecting rule to the closest ancestor state rule only

@platfowner As discussed, I have separated gc_max_siblings from max_children and used the former for the automatic garbage collection and the latter for the permission checking. Also, the hardcoded legacy garbage collection logic has been removed along with the enableHardCodedGC feature flag.
There will be a follow-up PR for extending the state rules by adding max_bytes, max_size, and max_height properties.
PTAL & please let me know if you have any questions! Thanks!

Addressed all comments, PTAL @platfowner

Thanks for the helpful review & feedback. Now merging!


More chase cards

Closes #39
closes #38
The test file isn't really an actual test file.
it's a debugging file i made for quick testing. Will add testing later in the future.

Though tests would be nice, the changes as they are look fine for the issues they are closing.

Though tests would be nice, the changes as they are look fine for the issues they are closing.

yeah, i'll be creating some issues to do some refactoring. so far, i wanna do some quick n dirty fixes/features, to a certain extent. I think I'll try to refactor at least beginning of each month or something so it doesn't get too cluttered. I might pull you in on some of the design decisions.


Run example/with-firebase serverCredentials

serverCredentials: {
// TODO service account json here
}
I dont know what should i fill in this ?
If any body have some sample JSON?

@t42ji2ji This is actually a non-next.js thing, but if you check out the Firebase docs (https://firebase.google.com/docs/admin/setup), they'll walk you through getting the credentials – it's basically a JSON file you have to download from your own Firebase project's console.


ANDROID_SDK_ROOT is deprecated, use ANDROID_HOME instead

Godot version
all | 6758a7f
System information
Windows 10 21H2
Issue description
Building export templates with scons requires user to define the ANDROID_SDK_ROOT variable, which has been made deprecated long ago, ANDROID_HOME should be used instead.
This will avoid people having to figure out why android isn't considered a valid platform when having a proper setup.
see this section | fallback
They may not check for ANDROID_SDK_ROOT in the future, so it's advised to use this newer variable instead.
Steps to reproduce
N/A
Minimal reproduction project
N/A

Should just be replacing all instances of ANDROID_SDK_ROOT with ANDROID_HOME if I'm not mistaken.
Will open a pr upon confirmation.

For reference, ANDROID_HOME used to be read as a fallback until https://github.com/godotengine/godot/commit/48efd563e4bac896cbc4b11df08f1841cd2877f6.

Note that the SDK & the MAUI check tool for example, does not require the path to be strictly of the root, they may also check for the presence of an additional folder called android-sdk in the case the specified folder isn't exactly the root

Had some issues building because of just that 👍🏽
https://github.com/godotengine/godot/blob/6758a7f8c07d1f4c8ec4f052ded6d26402967ebe/platform/android/detect.py#L46

Should just be replacing all instances of ANDROID_SDK_ROOT with ANDROID_HOME if I'm not mistaken.
Will open a pr upon confirmation.

Feel free to open a PR for this, but please read ANDROID_SDK_ROOT as a fallback to avoid breaking existing builds (especially on CI).


Disconnecting from server side.

@michalvasko,
From the server side,I need to disconnect session for certain users. How to do that?
If I use np2srv_del_session_cb(); and  nc_session_free(), I am getting error messages at client side as showm below.
c ERROR: SSH channel unexpected EOF.
nc ERROR: Failed to receive a reply to .
ly ERROR: Loading "ietf-netconf-acm" module failed.
ly ERROR: Parsing module "ietf-netconf" failed.
nc ERROR: Loading base NETCONF schema failed.
ly ERROR: Value "ps_admin" was not found in the dictionary.
ly ERROR: Value "<IP_ADDRESS>" was not found in the dictionary.
cmd_connect: Connecting to the <IP_ADDRESS>:830 as user "cm_admin" failed

Test report:
o-ran-usermgmt-v3.0.xlsx

There is no proper mechanism to terminate a NETCONF session from server-side, so you cannot avoid some errors. But there should not be leaks on the side of the client. Anyway, you should just need to call the callback for terminated sessions.


Issue with Script Tag Generation Causing 404 Requests in Ghost 5.68.0

Issue Summary
After upgrading to Ghost version 5.68.0, I observed the generation of a script tag in the page with the following content:
<script defer src="false" data-i18n="false" data-ghost="https://zhelin.me/" data-key="[delete]" data-api="https://zhelin.me/ghost/api/content/" crossorigin="anonymous"></script>

As per my Ghost configuration, I have set portal.url, sodoSearch.url, and comments.url to false. However, the src attribute of this generated script tag is set to false, leading to a 404 request to https://example.com/false.
Steps to Reproduce

Upgrade Ghost to version 5.68.0.
Set portal.url, sodoSearch.url, and comments.url to false in the configuration file.
Visit the page and inspect the generated script tag.

The generated script tag has src="false", causing a 404 request to https://example.com/false.
I have not been able to isolate the issue to a specific property, and I am using environment variables to set these properties.
Ghost Version
5.68.0
Node.js Version
16.20.0
How did you install Ghost?
Docker
Database type
MySQL 8
Browser & OS version
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Relevant log / error output
<script defer src="false" data-i18n="false" data-ghost="https://zhelin.me/" data-key="[delete]" data-api="https://zhelin.me/ghost/api/content/" crossorigin="anonymous"></script>

Code of Conduct

[X] I agree to be friendly and polite to people in this repository

After upgrading to version 5.69.0, the issue still persists.

I tried version 5.6, and the issue persists.

A workaround found to avoid this 404 errors : https://github.com/TryGhost/Ghost/issues/12865


Support webpack-dev-server

Because yoga instantiates its own server and express app it cannot be used with webpack-dev-server. In order to use graphql-yoga with webpack-dev-server yoga would need to be able to accept as arguments a server and express app when creating a server in the devServer before hook. Additionally when using the subscriptions option, the creation of the websocket server needs to wait until the devServer.listeningApp has been assigned/created.
Below is a hacky workaround I am using to currently make it work but it would be nice to have official support.
GraphQLDevServer.js
import { GraphQLServer } from 'graphql-yoga'
import { execute, subscribe } from 'graphql'
import { SubscriptionServer } from 'subscriptions-transport-ws'
import { defaultErrorFormatter } from 'graphql-yoga/dist/src/defaultErrorFormatter'

export class GraphQLDevServer extends GraphQLServer {
  constructor (app, devServer, props) {
    super(Object.assign({}, props))
    this.express = app
    this.devServer = devServer
  }
  startDev (options, callback) {
    let cb = callback
    let opts = options
    if (typeof options === 'function') {
      cb = options
      opts = {}
    }
    cb = typeof cb === 'function' ? cb : function () {}

    // purposely cause an error during server listen to bypass
    opts = Object.assign({}, options, {
      port: {}
    })
    let subscriptionServerOptions
    if (this.options.subscriptions) {
      subscriptionServerOptions =
        typeof this.options.subscriptions === 'string'
          ? { path: this.options.subscriptions }
          : { path: '/', ...this.options.subscriptions }
    }

    return this.start(opts, callback).then(() => {
      throw new Error('Unable to bypass server start')
    })
      .catch(err => {
        // throw any errors besides the intentional one
        if (!err.message.match(/invalid listen argument/i)) {
          cb(err)
          return Promise.reject(err)
        }

        // basically the same as graphql-yoga except with a nextTick to
        // allow the webpack-dev-server listeningApp to be added
        return new Promise((resolve, reject) => {
          if (!subscriptionServerOptions) {
            cb(this.options)
            return resolve(this.devServer)
          }
          process.nextTick(() => {
            this.subscriptionServer = SubscriptionServer.create(
              {
                schema: this.executableSchema,
                execute,
                subscribe,
                onConnect: subscriptionServerOptions.onConnect
                  ? subscriptionServerOptions.onConnect
                  : (connectionParams, webSocket) => Promise.resolve({
                    ...connectionParams
                  }),
                onDisconnect: subscriptionServerOptions.onDisconnect,
                onOperation: (message, connection, webSocket) => {
                  // The following should be replaced when SubscriptionServer accepts a formatError
                  // parameter for custom error formatting.
                  // See https://github.com/apollographql/subscriptions-transport-ws/issues/182
                  connection.formatResponse = value => ({
                    ...value,
                    errors:
                      value.errors &&
                      value.errors.map(
                        this.options.formatError || defaultErrorFormatter
                      )
                  })

                  return Promise.resolve(
                    typeof this.context === 'function'
                      ? this.context({ connection })
                      : this.context
                  ).then(context => {
                    return { ...connection, context }
                  })
                },
                keepAlive: subscriptionServerOptions.keepAlive
              },
              {
                server: this.devServer.listeningApp,
                path: subscriptionServerOptions.path
              }
            )
          })
        })
      })
  }
}

webpack.dev.conf.js
import { GraphQLDevServer } from './GraphQLDevServer'
import { schema } from './schema'

const config = {
  devServer: {
    before (app, server) {
      const graphqlServer = new GraphQLDevServer(app, server, { schema })
      graphqlServer.startDev({
        endpoint: '/graphql',
        subscriptions: '/subscriptions',
        playground: '/playground'
      })
      .then()
      .catch(console.error)
    }
  }
}

// other webpack stuff

With regards to my use case which is using a graphql-yoga server in a project using vuejs webpack template for development, I think breaking out the different initialization tasks into class methods would allow me (and other use cases) to control the server initialization.
I have mocked up an example untested implementation here https://github.com/graphql-factory/graphql-yoga/blob/flame/src/index.ts#L287-L292

@chrisdevereux I'm using a vuejs webpack template which i would like to keep using so that wouldn't fit the use case. This request is more around exposing the server object and allowing the various initialization steps to be called independently so that the yoga server can be used with things like webpack-dev-server.


[RESTEASY-1555] Move deprecated SerializableProvider into resteasy-le…

…gacy module

tested with SerializableWithParametersTest in legacy-integration-tests

Retest please

I restarted the tests ...
On 11/23/2016 11:01 AM, Katerina Novotna wrote:

Retest please
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/resteasy/Resteasy/pull/1002#issuecomment-262556083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAg38zPwsRFkmUV8chu7mTVS5Srncd3Sks5rBGNxgaJpZM4K6uqm.

--
My company's smarter than your company (unless you work for Red Hat)


refactor: improve query manager [APE-639]

What I did
A couple of small improvements to the QueryManager / default query provider, and one bug fix to improve estimation of single item queries (it previously was replying 0)
Checklist

[x] All changes are completed
- [ ] New test cases have been added
- [ ] Documentation has been updated

Since there is a bug fix, we should highlight that in the PR title and changelog over the refactor.

The bug fix doesn't cause any faults, it was just short-circuting the query manager to whatever is the first query engine registered that returns 0 for an estimate