Geckodriver 0.24.0

What are you trying to achieve? (Expected behavior)

Test Firefox with Codeception
What do you get instead? (Actual behavior)

SessionID Is Null
How could the issue be reproduced? (Steps to reproduce)

Geckodriver 0.24.0, Codeception 3.0.2, facebook/webdriver 1.7.1
Details Geckodriver logs

1564127990035	webdriver::server	DEBUG	<- 200 OK {"value":{"sessionId":"5492b5ae-cc46-f641-8f9a-4c868cdd608e","capabilities":{"acceptInsecureCerts":false,"browserName":"firefox","browserVersion":"68.0.1","moz:accessibilityChecks":false,"moz:buildID":"20190717172542","moz:geckodriverVersion":"0.24.0","moz:headless":false,"moz:processID":1115,"moz:profile":"/var/folders/xt/8b1hm05j32vc19t4cc1xnt0m0000gp/T/rust_mozprofile.bOTneERvRiUa","moz:shutdownTimeout":60000,"moz:useNonSpecCompliantPointerOrigin":false,"moz:webdriverClick":true,"pageLoadStrategy":"normal","platformName":"mac","platformVersion":"18.6.0","rotatable":false,"setWindowRect":true,"strictFileInteractability":false,"timeouts":{"implicit":0,"pageLoad":300000,"script":30000},"unhandledPromptBehavior":"dismiss and notify"}}}

Here https://github.com/facebook/php-webdriver/blob/community/lib/Remote/HttpCommandExecutor.php#L324 sessionID is returning not as $result['sessionId']. It contains in the $result['value']['sessionId'].
Then sessionId is still null and  we have GET /session//screenshot 404

Php-webdriver version: 1.7.1
PHP version: 7.1
Selenium server version:
Operating system: OsX
Browser used + version:  Firefox 68

Geckodriver support was added in #560 and will be part ofnext php-webdriver release (1.8.0).


Consider making asynchronous operations cancelable.

Asynchronous operations can be canceled by the application, or at least, the application can request that the operation be canceled, the cancelation may or may not succeed.
To implement this we would need to return an object (maybe of AsyncOperation type) from each member function that implements an asynchronous operation. Then the object would cancel the request (using the underlying gRPC cancelation mechanisms), or the timer if the operation is in a retry loop.
It is unclear if there is much value on this: most operations succeed on the first request, so there is little opportunity to cancel them.
It is also complicated to signal to the application that the cancelation completed, specially for operations like AsyncBulkApply that may have partially succeeded before the cancelation is issued.
Finally it is not clear how that would work with std::future<>-based requests (how I am planning to implement async operations for exception-enabled builds), because it is not possible to cancel via a future.
My vote is to not provide a mechanism to cancel the request. I would like to hear other opinions.
If we converge on not having a mechanism to cancel requests then we would create an ADR to document this decision.
If we converge on having a mechanism to cancel request we would need to open bugs to implement it.

@deepankarsharma @dopiera @sduskis I am interested in your thoughts about this bug.

@houglum because what we decide here will influence our decisions for Cloud Storage someday, also interested in your thoughts.

Here are my 10 cents:
I tried to come up with scenarios when one would need cancellation; I'm not sure how real-life these examples are (probably not much), but this is what I figured:

writing to several locations and cancelling as soon as the fastest location confirms (AKA reimplementing one of the routing policies)
if a user hammers their CBT cluster they probably use long deadlines, so if they want to cancel their pipeline, they'd be stuck
flow control? a sophisticated controller could cancel requests under very heavy load
if CBT suffers from a long unavailability, we might make the client app stuck

By making the decision not to implement cancellations, we'll be making it much harder for users to reimplement the routing policies if they wish (maybe that's OK). The other examples seem to boil down to answering the question whether we consider setting long deadlines an anti-pattern. If we do, then we are basically shifting the responsibility to do back-offs to the user, which sounds like an inconvenience to me.
The other thing is what semantics cancellation has. It seems that there is an inherent race with cancellations - what if we issue the cancellation right after the request manages to complete. Due to that, I can't come up with anything other than making cancellation advisory, i.e. the client is free to ignore it. If we treat it as such, we could make cancellation completely async with no indication of completion.
We could start with a simple implementation: it would only cancel the requests which are waiting to be sent. The user would get to know by checking the individual request status upon their completion (one of them would be CANCELLED). For bulk mutations, it doesn't seem a problem unless the mutations are on the server side and if they are, tough luck - cancellation is likely to be ignored, unless it refers to all requests stuck on the server side.
If we go this way cancellation would be an ordinary exception, so std::future should just work, no?
Having said all of that, I'm not sure whether implementing cancellations is worth it. Maybe the way to go is in between - return a cookie for every operation, so that we can retrofit cancellation later.

The most compelling argument you make is that removing cancelations takes away functionality from the application developers.  There are algorithms that one can implement with asynchronous gRPC calls that become hard or impossible to implement if we do not have a hook to cancel the operation.  As a general principle we try to offer a more convenient API, but one that is at least as powerful as the raw gRPC calls.
That I think convinces me that we need to support cancelation, the issue is how?  What changes are needed in the APIs outlined in the go/cbt-cpp:async-dd (you have access to the direct link, but not the go/ link) design doc?
The next questions are in that spirit.

If we go this way cancellation would be an ordinary exception, so std::future should just work, no?

The question is what should an asynchronous function with futures return?  In the design doc, I outlined APIs like this:
future<Foo> f = table.Operation(...);
// Use f.get() to block for a value or f.then() to set a callback.

Now, neither std::future<>, nor std::experimental::future<> have a "cancel" member function, so where is the application supposed to say "cancel"?
For the noex:: APIs where we are returning void it is not hard to see us returning a different thing.  I guess we could return a std::pair<> with a future and the cancelation object?
Or we could "enhance" the future<> class to support a cancel() request? I do not like that idea because I want a class that can be replaced with std::experimental::future<> once that becomes widely available (2020 is not that far into the future).

For bulk mutations, it doesn't seem a problem unless the mutations are on the server side and if they are, tough luck - cancellation is likely to be ignored, unless it refers to all requests stuck on the server side.

The issue(s) with bulk mutations are two fold (both minor for this discussion I think):

An API design question, how do we signal to the application: these mutations failed, these succeeded, these we do not know because you cancelled while we were retrying?  The blocking API returns a std::vector<FailedMutations> so presumably the callback could take that and some of the "failures" will be "operation cancelled"?

A different API design question (but probably less important): the Apply() and BulkApply call use move semantics to minimize the number of copies from the application down to the gRPC layer, some of these mutations are large sometimes. Move semantics are Okay when things succeed: "I stole your data buffers but I did something useful with them" is a reasonable excuse, but when we signal a failure/cancellation: should we give the buffers back to the application ("I was borrowing these buffers, but now I cannot use them, take them back").

Thoughts?

I don't have much to contribute here, except for a couple things:

I agree they should be cancelable.

WRT this quote:

A slight improvement to std::pair is to have a custom object - it might be more convenient than using opaque first and second.

I agree with this, as it's more extensible and cleaner (IMO) than a std::pair.

WRT this quote:

The blocking API returns a std::vector<FailedMutations>

This model sounds most intuitive to me.  Maybe we could return something similar, but instead of FailedMutation, maybe MutationResult (or something appropriately named) objects that have a status enum to disambiguate between Failed vs Cancelled/Unknown state?

Since we are converging on making the operations cancelable then the question is only around the API for future<> based requests:

Having put more thought into it, I think there is one more caveat: cancelling a chain of requests. The cool part about the std::future<>::then() is that you can be left with just one future holding the whole chain (if my understanding is correct).

Well, it is unspecified what you have... you have a future that will (eventually) get satisfied when the chain is.  How is that implemented is not specified at all.

Getting the cancellation object outside of the continuation might be tricky, which IMO is an argument for either improving the future<> or the golang way.

I agree.  Maybe we should write a paper to improve std::experimental::future<>, that is the point of technical specifications really, to gain experience and gather this type of requirements.
But I digress.

In summary, @dopiera and @houglum changed my mind, we need to be able to cancel requests.  Therefore we need to:

[ ] Change AsyncRetryUnaryRpc<> to derive from AsyncOperation. The AsyncRetryUnaryRpc<>::Cancel() function should try to cancel the pending timer and/or the pending request, as needed (and there are some potential race conditions to deal with).

https://github.com/GoogleCloudPlatform/google-cloud-cpp/blob/3f96177a48442982e711175ba84e0ac1537c9f76/google/cloud/bigtable/internal/async_retry_unary_rpc.h#L72

[ ] Change the existing noex::*::Async*() functions to return a std::shared_ptr<AsyncOperation> so all operations become cancelable in the no-exceptions case.

I think we continue to work on the existing async functions, the cleanup to return AsyncOperation will be pretty once AsyncRetryUnaryRpc<> is ready.
Separately, prototype the idea of adding a cancel() member function to the future<> classes in my branch.  If it is possible to add such a member function then the design doc needs to be updated to say that.  Otherwise we need to change the design doc to say we return both the future and the AsyncOperation object.

The most common use case I have seen for cancellable async operations is handling scroll events in UIs. When building a data viewer it is fairly common to cancel any existing prior requests in flight and then issue a new one when the scroll position changes.
My preference would be to not diverge from std::future / std::experimental::future and instead do the clunky thing for now and return another object along with the future that supports cancellation.

While looking at API options for flow control, I encountered an interesting way to do cancellation.
Summary of the problem:

we want to give the user the option to cancel a request
in the noex API it's simple - we return an AsyncOperation which has a Cancel() memfn (this is already implemented for all operations)
in the future-based API, it gets trickier, because the async member functions are supposed to return future<>, not AsyncOperation.

We've so far considered these options:

instead of returning a future, return a std::pair of the future and a cancellation object
augment the future<> to incorporate a cancel() member function (not that infeasible, given that we've already reimplemented std::future<> to allow for using future<>::then() in C++11)

The first option gets ugly, when future<>::then() is used because it's tricky to get the cancellation object from any async call other than the outermost.
The second options has the big disadvantage of being non-standard.
We could do something along the lines of CancellationToken from C#.
This is how the code could look like:
void AppCode(CompletionQueue &cq) {
  CancellationToken ct = table.CreateCancellationToken();
  std::future<void> apply_chain = table.AsyncApply(GenerateMutation(), cq, ct).then(
      [&cq, ct](std::future<void> fut) {
          fut.get();
          return table.AsyncApply(GenerateMutation(), cq, ct);
      });
  // I changed my mind - I don't want it to complete.
  table.Cancel(ct);
}

@devjgm @coryan What are your thoughts? Shall I implement it?

That sounds cool, though I would prefer if the cancellation token was created and used with the completion queue.
My guess is that we will prioritize the conversion to use StatusOr<> in the bigtable client for now.

FWIW, the future<T> class gained a .cancel() function a while back.  I think that fixes this problem.  We can reopen if I happen to be wrong.


playback audio loss

only video displayed when recording played back.
our demo deeply screwed.
please help
every stream is included in the recording through the following call.
recorder.getInternalRecorder().getMixer().appendStreams([stream]);

this._recorder = RecordRTC(this.recordStreams, {
type: "video",
video: {
width: 960,
height: 540,
},
audioBitsPerSecond: 128000,
videoBitsPerSecond: 2560000,
frameRate: 18,
/*        canvas: {
width: 1280,
height: 720
},/
mimeType: "video/mp4" ,
timeSlice: 1000,
/        timeSlice: 1000,
ondataavailable: (blob)=>{
blobs.push(blob);
console.log('A ')
}*/
});


fetchcrl::install: allow to disable CA repo management.

PR allowing to disable yum repository managememt using the boolean fetchcrl::manage_carepo class attribute.
Users might want to manage yum repositories using some special modules (like example42/yum) and in order to do this the yumrepo/gpg keys calls should be optional.
This PR is reverse compatible as repo management is enabled by default.

Any news about this commit please ? I would need it too.

Hi, looking now.


Most Mod Functionality does not work on version 0.5.1

Describe your bug here.
Most mod functionality does not work on Mac 0.5.1
Command Prompt/Terminal logs (if existing)
source/Discord.hx:17: Discord Client starting...
source/Discord.hx:67: Discord Client initialized
source/Discord.hx:24: Discord Client started.
source/Discord.hx:17: Discord Client starting...
source/Discord.hx:67: Discord Client initialized
source/Discord.hx:24: Discord Client started.
source/Discord.hx:17: Discord Client starting...
source/Discord.hx:67: Discord Client initialized
source/Discord.hx:24: Discord Client started.
source/FreeplayState.hx:323: zanta-taiko
source/FreeplayState.hx:329: CURRENT WEEK: zanta
source/LoadingState.hx:162: Setting asset folder to shared
source/Conductor.hx:75: new BPM map BUDDY []
zsh: segmentation fault

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

Are you modding a build from source or with Lua?
Source
What is your build target?
Mac
Did you edit anything in this build? If so, mention or summarize your changes.
No

pc issue

I believe Mac compatibility is experimental. It hasn't been tested much iirc, it was just added in a commit; Def needs more looking at.


Fe homework 15

[Server stopped abruptly in the video, but it worked on restart, it is present in the video]
Drift video:https://video.drift.com/v/ab4T80xA2SHz4BpIj9Y2YG4bgiofhOC0ctFQw8QSRTjk/
UI is same as previous hands on
Component tests -
Header component - Shoud be able to type in search field

Container Component - Button at disabled at start, Button enabled on typing, Button disabled again on removing text, New item should get added to store on button click, Checked item (according to store) removed from store on button click

Items Component - Display previous state, Update list on store update, Remove items on clicking X

Integration tests - Add an item to the list correctly, Remove checked items correctly, Retain correct items on search, Retain items on relaod

Unit tests - only required for slice and store functions

Metric
Value

alert_status
:white_check_mark: OK

bugs
1

code_smells
0

reliability_rating
C (at least 1 Major Bug)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Metric
Value

alert_status
:white_check_mark: OK

bugs
1

code_smells
0

reliability_rating
C (at least 1 Major Bug)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

The commit message's format must be proper
Work on the directory structure
Use separate files for the interfaces, constants, etc.
Modularize the code


[BUG] Monitoring the change of the time property

closes #188

add repro unit test, to check this is issue when we update to later versions of MongoDB driver


Skeletons not mining Silver

Describe the bug
The miner Skeletons are not mining silver
To Reproduce (if applicable)
Steps to reproduce the bug. For example:

Clear silver vein
raise ground around the solver, so the skeletons don't go after the stones in the immediate area
Summon miner skeletons

Expected behavior (if applicable)
Mine Silver
Screenshots (if applicable)

The same happens for any kind of ore.
Seems like they only look for normal rocks and once there are none in their radius they just freeze in place.

Thanks for the feedback. I'll look into this soon

@jpw1991 Any chance this would be fixed using the new FindClosest? Woodcutters also not seeing nearby wood. Feels like the neckro problem all over again.

Dam adorable Neckros. They are too cute not to use.

Hi @suRedLance & @jdalfonso4341 can you please try adding the following to the config for the miner ores list and seeing if it fixes the problem for silver:

silvervein
silvervein_frac

For copper and other ores, hmm. I am still not sure.

Any chance this would be fixed using the new FindClosest? Woodcutters also not seeing nearby wood. Feels like the neckro problem all over again.

Yeah it would help I think @CW-Jesse

Seems like MineRock_Tin is the name for the tin. It's hard to find them all

Ah damn it. MineRock_Tin has a different mask

Alright so they're mining Tin and Obsidian now in my unreleased test version. They are still not mining silver and copper. I'm not sure yet why that is.
@CW-Jesse I also refactored to make use of that FindClosest function

I have tried out using MineRock_Tin and MineRock_Copper too (using the documentation from Jotunn's) but it doesn't change anything.
I feel like this is more of an AI problem than anything.
Next few days I'll take the FindClosest version for a spin, and see if it works.

Same thing on 2.3.0, just checked.

Same thing on 2.3.0, just checked.

Please try 2.3.3

Please try 2.3.3
Works on Tin now, but they still ignore copper, even when standing on top of a full vein.

This one really isn't making sense to me. Technical "proof" that it should be able to mine copper:

Because it is no different from tin:

I will probably figure it out eventually, but it's a tough cookie...

Success! I got it! Just gotta polish it up some,t hen I will release


Combining services

Is it possible to combine the services? We'd really like webserver, websockets and nanolets all in one application server. I feel like all the pieces are there but it's not obvious to me how to combine them cleanly.

You can run the Webserver and a Websockets server on top of the default NanoWSD server, running both protocols on a single port.
I have a personal project that does just that and pretty much the same as Nanolets, but with a slightly different structure. It is also able to load jars as application modules which can register handlers to endpoints on both HTTP and WS requests. It currently isn't public because of licensing issues (it doesn't have a license, and I don't exactly want it to be open source, and it happens that NanoHTTPD's license is viral), but as soon as I sort it out I can share it :)
Coming back to point, it shouldn't be hard to allow Nanolets to use the full spectrum of NanoWSD's capabilities, but it may be better to let that go into v3.x

As I started working in v3.0 I noticed how easy this actually is to implement.
This is definitely going in!

I am also wanting to run a HTTP server and WEBSOCKETS at the same time.  Do they have to be in separate classes or can i run it off the same server class?  Any simple example would be very helpful

Just use the NanoWSD server and override serveHttp() to also have http in :)


[BUG]Failed to Sync AD users (emails are required for new users)

Describe the bug
After an initial installation with a customized domain name (something like my.domain.edu, not corp.res.com and the default .ldif file), I added two users through the windows Admin Node. However, the users are not synced to RES.
Issue identified
After a lengthy debug process, it appears that emails are required for new users.
Steps to debug the issue

From the windows AD Admin Node, I can see the new users, and the domain controllers etc.
From the Linux Ad admin Node, I can locate the new users after running

sh-4.2$ ldapsearch  -h my.domain.edu  -D "CN=ServiceAccount,OU=Users,OU=my,DC=my,DC=domain,DC=edu"  \
    -w 'PASSWORD' -b "OU=my,DC=my,DC=domain,DC=edu" | grep cn:
cn: IDEA-xxxxx
cn: RESAdministrators
cn: New User1
cn: New User2
cn: ServiceAccount
cn: RES Service Account
cn: Admin

It looks like the DC are synced.

Following this tutorial to trigger sync from <environment-name>-cluster-manager-tasks.fifo, then "Poll for message", no message was returned (maybe expected).
The lambda function <env-name>.manager-scheduled-ad-sync shows that the lambda function has been called a few times (including ones in the past).
From cloud watch /aws/lambda/<env-name>-cluster-manager-scheduled-ad-sync, I do not see any error message (not see if I am checking the correct log stream).

INIT_START Runtime Version: python:3.9.v56	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:52e9b67213e4ba48e3c265ce3aa86c478ce792bbd68bc88225db1202a975ddda
[INFO]	2024-09-16T15:00:35.792Z		Found credentials in environment variables.
START RequestId: f1ddc0bb-1dec-4ef7-a672-bfa22615a39c Version: $LATEST
[INFO]	2024-09-16T15:00:35.915Z	f1ddc0bb-1dec-4ef7-a672-bfa22615a39c	Forwarding scheduled ad sync task to cluster manager task queue
[INFO]	2024-09-16T15:00:36.171Z	f1ddc0bb-1dec-4ef7-a672-bfa22615a39c	{'MD5OfMessageBody': '373b00dd55ed9f30e6685dedfa0c80b7', 'MessageId': 'a03efca8-e862-4592-a5ca-ce655b3208f2', 'SequenceNumber': '18888727775768047616', 'ResponseMetadata': {'RequestId': 'ff9b869e-383c-5e8f-8e49-d9fc7268add6', 'HTTPStatusCode': 200, 'HTTPHeaders': {'x-amzn-requestid': 'ff9b869e-383c-5e8f-8e49-d9fc7268add6', 'date': 'Mon, 16 Sep 2024 15:00:36 GMT', 'content-type': 'application/x-amz-json-1.0', 'content-length': '146', 'connection': 'keep-alive'}, 'RetryAttempts': 0}}
END RequestId: f1ddc0bb-1dec-4ef7-a672-bfa22615a39c
REPORT RequestId: f1ddc0bb-1dec-4ef7-a672-bfa22615a39c	Duration: 275.14 ms	Billed Duration: 276 ms	Memory Size: 128 MB	Max Memory Used: 72 MB	Init Duration: 472.88 ms

Go back to RES, new users do not appear.
Checking the log events for <env-name>/cluster-manager,

[2024-09-16 04:00:08,325] [ERROR] [ad-sync] Error while adding user newuser to RES. Error: [INVALID_PARAMS] Invalid parameters: email is required
This looks like the culprit.

Going back to the AD admin, node, add emails to new users. The ldap search generates mail: records for new users.

Repeating the SQS to trigger ad sync, and new users appear.

** Expected behavior**
Somewhere in the documentation the requirement for email should be mentioned. This is confusing because the example .ldif file does not have a mail field either.
Environment (please complete the following information):

RES Version: [e.g. 2024.8]

Thanks for reporting the issue. I'll follow up with the document team for the clarification.


Can't Upload PDFs to PrivateGPT

Discussed in https://github.com/zylon-ai/private-gpt/discussions/1818

Originally posted by kj4274 April  1, 2024
Hello, I am new to coding / privateGPT.
Initially, I had private GPT set up following the "Local Ollama powered setup". Under that setup, i was able to upload PDFs but of course wanted private GPT to run faster. So I switched to Llama-CPP Windows NVIDIA GPU support. Now, Private GPT can answer my questions incredibly fast in the LLM Chat mode. However, i can no longer upload PDFs, enabling Query Files.
Whenever I try to upload a PDF, I always get ---- ValueError: could not broadcast input array from shape (384,) into shape (768,)
What can I do to make PrivateGPT accept my pdfs again? Thank you for the help.

The issue is resolved #1759

The issue is resolved #1759

thank you that fixed it


[Improvement][server] varPool support syntax #{setValue(key=value)}

Purpose of the pull request
This pr will close #9576
Brief change log

Verify this pull request

This change added tests and can be verified as follows:
Manually verified the change by testing locally

I think your describe #9416 is not work for this case.
to target specific issue from PR, we recommend use keyword fix: #issue_id or close: #issue_id or closes: #issue_id in your PR describe(not title, jus desc). I would not only connect issue to PR but also close issue automatically when PR is be.

Thank @wangxj3 reviwing


Add ability to put default password for username in keystore

Suggested by @lindensc in https://github.com/intersystems-community/vscode-objectscript/issues/255#issuecomment-704626928

Perhaps related and can help simplify: when selecting a 2nd server to connect, the bottom status bar goes looping wildly while Code prompts for my password, even though it's stored proper in the keychain for each server.  Since we use AD for central authentication, it locks out my account by policy, ugh.
References: COS #424, COS #417

@theflyingape please see https://github.com/intersystems-community/vscode-objectscript/issues/616. A fix is about to merge, and I will ping you from there shortly to ask you to try the beta VSIX.

I can confirm the ObjectScript 1.0.10beta behaves much closer to expected with the updated Server Manager 2.0.2.
The backend logs sometimes show multiple attempts to fully login (non-cached hits); but subsequent operations & reloads perform a single-hit.

@theflyingape thanks for the feedback. I'll try and get 1.0.10 released soon.

Decided not to implement option for a global password.


Next jumping to last

Hello and thanks for this great paginator.
Let's say I have 72 pages I'm paging using the next button, when I reach page 15 it will jump to the last page instead of going to page 16.
If i put an alert just before the function it works right.
Any clues? Thanks.
items: 359,
    itemsOnPage: 5,
    cssStyle: 'compact-theme',
    prevText: '<',
    nextText: '>',
    currentPage: currentPnum,
    displayedPages: 24,
    edges: 3,

are you check currentPnum ?

Problem is solved it was my mistake.


Image resizing prioritizes image ratio higher than resize target dimensions

Question about an existing feature => resize(number, number, { fit: 'inside' })
Using the resize method to scale down an image into a target format

Existing and occurring dimensions written on filenames.

import sharp from 'sharp';

sharp('input-image-1650×1275.jpg')
  .resize(610, 854, { fit: 'inside' })
  .toFile('output-image-610×471.jpg');

What are you trying to achieve?
Keeping the desired dimension:
The resulting output image is 610 × 471 and desired taget height of 854 is not applied as value for the down sized image.
I think especially with fit:insideoption set that the output image has a size of 610x854 with the image having a size of 610x471 vertically centered. Is this somehow achievable? Thanks very much for any guidance :-)
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question
The code above is a working example that can be reproduced by e.g. using this image:

Did you see https://sharp.pixelplumbing.com/api-resize#resize ? What you describe sounds more like fit: contain.

Thanks yes using fit contain it's working. Had another issue that made it appear contain was the wrong solution.
Thank you so much for pointing me to the right direction.


Chore: Upgrade candid IC-Managment canister

Motivation
Upgrade ic-management candid files that have some changes that break the pipeline even though they are backwards compatible.
This breaking of the pipeline prevents the bot from making PRs that can be merged without manual changes.
Changes
Automatic Changes

"ic-management.did" file with ./scripts/import-candid ../ic. In this step, I removed the changes in all the other candid files.
"ic-managment.certified.idl.js", "ic-management.d.ts", "ic-management.idl.js" files with "./scripts/compile-idl-js"

Manual Changes

Add new optional field to toCanisterSettings.
Change the return of toInstallMode for the InstallMode.Upgrade. In another PR, we might want to add a new field to InstallMode enum to support new functionality.

Tests

Fix tests expecting new optional field.

Todos

[ ] Add entry to changelog (if necessary).

Upgrade ic-management candid files that have some changes that break the pipeline even though they are backwards compatible.
This breaking of the pipeline prevents the bot from making PRs that can be merged without manual changes.

Which pipeline and which PRs? In ic-js?

Upgrade ic-management candid files that have some changes that break the pipeline even though they are backwards compatible.
This breaking of the pipeline prevents the bot from making PRs that can be merged without manual changes.

Which pipeline and which PRs? In ic-js?

Yes, ic-js. An example: https://github.com/dfinity/ic-js/pull/512


python3Packages.angr: 9.0.6281 -> 9.0.6790 and dependencies

Motivation for this change
Update to latest upstream releases.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 119894 run on x86_64-linux 1

12 packages built:

python38Packages.ailment
python38Packages.angr
python38Packages.archinfo
python38Packages.claripy
python38Packages.cle
python38Packages.pyvex
python39Packages.ailment
python39Packages.angr
python39Packages.archinfo
python39Packages.claripy
python39Packages.cle
python39Packages.pyvex

Result of nixpkgs-review pr 119894 at 7ce92f76 run on aarch64-linux 1

8 packages marked as broken and skipped:

python38Packages.ailment
python38Packages.angr
python38Packages.cle
python38Packages.pyvex
python39Packages.ailment
python39Packages.angr
python39Packages.cle
python39Packages.pyvex

4 packages built successfully:

python38Packages.archinfo
python38Packages.claripy
python39Packages.archinfo
python39Packages.claripy

2 suggestions:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/ailment/default.nix:27:0:
   |
27 |     description = "The angr Intermediate Language";
   | ^

warning: unused-argument
Unused argument: pkgs.
Near pkgs/development/python-modules/angr/default.nix:21:3:
   |
21 | , pkgs
   |   ^

Result of nixpkgs-review pr 119894 run on x86_64-linux 1

12 packages built:

python38Packages.ailment
python38Packages.angr
python38Packages.archinfo
python38Packages.claripy
python38Packages.cle
python38Packages.pyvex
python39Packages.ailment
python39Packages.angr
python39Packages.archinfo
python39Packages.claripy
python39Packages.cle
python39Packages.pyvex

@ofborg build python38Packages.angr python39Packages.angr


added dep:  Intervals = "d8418881-c3e1-53bb-8760-2df7ec849ed5"

Sorry for breaking the build.
With it's tested I meant my unit test.
Now it passes CI.yml

Hello!
Could You register? So that I can register my first version of BitemporalPostgres, which is deployment ready now.
Thank You
Michael Fliegner


quick fix to get it working (with cookie) and solve warnings

I currently don't know how often you'll have to replace the cookie. But it works with the cookie extracted from developer tools for a login at google.com (!!). See screenshot:

Which should fix #20 (at least temporarily).
Next step should be looking at @Apollon77 / alexa2 adapter and trying to implement a similar proxy solution (did not have to touch alexa2 login for months, now... works really great).
Also I fixed a lot of warnings, because object definitions were not perfect. Should solve #28 and #27.
I hope you are still around.
If you do not have time to maintain the adapter anymore (or no fun, because you moved away from ioBroker?), please think about migrating it to iobroker-community-adapters, so someone else can maintain it and issue new npm builds.

kann es sein, dass Google wieder was geändert hat, da selbst mit frischen Cokkie das im Log steht und der Adapter gelb bleibt:
`

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at endReadableNT (_stream_readable.js:1221:12)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at IncomingMessage.emit (events.js:327:22)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at Object.onceWrapper (events.js:421:28)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at Request.emit (events.js:315:20)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at Request.emit (events.js:315:20)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at Request._callback (/opt/iobroker/node_modules/iobroker.google-sharedlocations/main.js:517:11)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
at parseLocationData (/opt/iobroker/node_modules/iobroker.google-sharedlocations/main.js:552:11)

google-sharedlocations.0
2020-06-27 08:14:27.244
error
(1833449) An error occurred during polling the locations: Error: No location data in response. Cookie expired.

`

Hier geht es. Adapter grün und Positionen scheinen zu stimmen.
Hat es denn mal funktioniert? Der Fehler kann auch auftreten, wenn niemand seine Position mit deinem ioBroker-Google-User teilt.

Heute läuft er wieder, seltsam.


Remove implicit from max and min since SQL is very flexiable regardin…

Remove implicit ordering from max and min since SQL is very flexible regarding types.
Problem
Implicit ordering makes it hard to adapt to SQL flexibility regarding types. In SQL you can use max and min with anything, so there is no point to limiting this with scala.
Solution
Just removed the implicit ordering
Notes
Additional notes.
Checklist

[X] Unit test all changes
[X] Update README.md if applicable
[X] Add [WIP] to the pull request title if it's work in progress
[X] Squash commits that aren't meaningful changes
[X] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers
…g types

👍


GH-33783: [C#] Update release verification to use .NET 7.0

Update verification script to download and install 7.0 but run tests against 6.0 if the 6.0 SDK is present.  Update examples to use 7.0 only.

Closes: #33783

@github-actions crossbow submit --group verify-rc-source --param release=11.0.0 --param rc=0

@github-actions crossbow submit --group verify-rc-binaries --param release=11.0.0 --param rc=0

@github-actions crossbow submit --group verify-rc-binaries

@github-actions crossbow submit --group verify-rc-source

I almost wonder if we need both 6.0 and 7.0.

Are you asking if it is worth testing with 6.0?  I agree that may be excessive.  I was erring on the side of caution but if you want me to refine this so its a strict upgrade to 7.0 I'd be fine with that.

Would it be better to just require 7.0 when doing development on the library?

You should be able to get away with doing development with just 7.0.  The only downside will be that you will need to make sure to run your tests with dotnet test --framework net7.0 or else it will try and run them for each target and fail on 6.0 (I believe Visual Studio IDE makes this a drop down and only tests a single framework at a time).

By default, VS will run both:

@eerhardt circling back on this.  Would you rather we just upgrade everything to .net7 (and remove references to .net6) to keep the developer experience simple?

I'm fine with having both .NET 6 and .NET 7 support, I guess, if we need it.
Maybe let's just do .NET 7 for now. And if someone finds a reason to keep supporting .NET 6, we can add it then?

@github-actions crossbow submit --group verify-rc-source-csharp

@github-actions crossbow submit --group verify-rc-source

Maybe let's just do .NET 7 for now. And if someone finds a reason to keep supporting .NET 6, we can add it then?

Done.  CI failures are unrelated and the wheel verification builds seem to be passing.  I'm going to go ahead and merge this.


Updated sp3 dupe check \w has_duplicates property

As has_duplicates is an already a property inside the sp3 dataframe it is literally free. You may argue that index.duplicated() before if is not a waste  as you still need it to compute first dupe, but I could speculate that 99% of sp3 files come without dupes.

@treefern Originally I added a comment on has_duplicates to you branch but never clicked on Finish your review button so it was a pending [read as invisible] comment. But this branch is also a great test on how-to commit/merge etc when one is a poor contributor, not a maintainer :)


Security builder

Coverage decreased (-0.4%) to 87.395% when pulling 779f8690f37e1722c88badf131dbbf911d64da99 on security_builder into 8598d3c656897e687b8b443ef256839e0792f42a on master.


Rolltable for only "Currency"

I created a rolltable for only generate "Currency".
It's ok but i have a warning message

After, i created a rolltable(master) for calling another rolltable to generate "currency".
I haven't message error but nothing is happening, no currency generate ...

I will expand the currency support ( https://github.com/ultrakorne/better-rolltables/issues/1 )
to be able to add currency field directly as a text field in the roll table, this way you don't need an extra table just to do 1 currency roll.
Will probably do this in the next milestone

So this is closed, and so is #1, but I don't understand if this is meant to work now, or how to generate currency loot by itself?


Pre-8 remote stacks

This is implementation mechanics for the spec, so not covered in that

Was wrong direction in development, see the pull request for refactoring basics


Create template

We could add the repo setup (minus some cleanup) to https://github.com/vitejs/awesome-vite
A good starting point is probably https://github.com/neurobagel/react-query-tool/commit/411404d4b309f211360f8e31c6769228eb63d489

Closed by https://github.com/neurobagel/react-bagel in https://github.com/neurobagel/react-bagel/commit/0da3d07ca8122a2a99fff80597805165cd8a28b0


ENH: add predict proba estimator

@mrahim let me know what you think.

@mrahim need to run now. Feel free to checkout /modify / merge. cc @fraimondo

ping @mrahim

LGTM, merging.


react-native response error code 500

Hello
I'm encountering a strange issue ,  when I  use react-native run-android command on the template project which I've created using react-native init I get the following the red error page on the device:

and then it disappears leaving me with a totally blank page!
the packager terminal shows the following error:

Development OS: Win 7
react-native-cli: 2.0.1
react-native: 0.47.1
node-v: 6.11.2
npm -v: 3.10.10
yarn --version: 0.27.5
device android version:6.0.1

I was getting the same error today. For me, I fixed by downgrading babel-preset-react-native from 3.0.0 to 1.9.2 in my package.json.
"devDependencies": { 		"babel-jest": "20.0.3", 		"babel-preset-react-native": "1.9.2", 		"jest": "20.0.4", 		"react-test-renderer": "16.0.0-alpha.12" 	}
Then just run 'yarn' in your terminal

Thank you very much @adon94 , you saved a day !

Should be fixed in the next release of babel-preset-react-native.

@facebook-github-bot duplicate #15513

Hello,
I'm getting this error "The development server returned response code:500"
I decremented the version of the dependencies but still the error is not going.
Please help.

Did you try to connect on same wifi network (phone & computer)?


no code

no code is present on github.

looks like spam project

@jayph88 There is code inside of the repository and the code works.  Have you dug down into the folders to look at any of it?  If you have questions on how to use the code you can also look at the tests here: https://github.com/selfjared1/quickbooks_desktop/blob/master/src/quickbooks_desktop/tests/test_session_manager.py


Missing jar 0.5.1 and 0.5.2 for scala 2.11

Hi could you please the jar for 0.5.1 and 0.5.1 for scala 2.11. So far the only available are for scala 2.12.
2.11 stop at 0.5.0

duplicate of #109


new Google Play In-App Review API not working, popup is not available

hi
see below video where rating was request and Review popup not able to show

Please fill the issue template. Then make sure you read this two things :

"You must upload your app to the Play Store to test the plugin. An easy way to do this is to build an apk/app bundle and upload it via internal app sharing." From in_app_review.
"To provide a great user experience, Google Play enforces a quota on how often a user can be shown the review dialog. Because of this, calling a launchReviewFlow method might not always display a dialog. For example, you should not have a call-to-action option (such as a button) to trigger a review as a user might have already hit their quota and the flow won’t be shown, presenting a broken experience to the user." From the official documentation. This means that when you call the showRateDialog (or showRateDialog) method with ignoreNative set to false, the Google Play Services may choose to not show the dialog.

Yes i see its now working, Q if user decide not now will the popup
displayed again according to old functionality?
On Fri, Aug 14, 2020, 13:44 Hugo Delaunay<EMAIL_ADDRESS>wrote:

Please fill the issue template. Then make sure you read this two things :

"You must upload your app to the Play Store to test the plugin. An
easy way to do this is to build an apk/app bundle and upload it via internal
app sharing https://play.google.com/apps/publish/internalappsharing/."
From in_app_review https://pub.dev/packages/in_app_review#android.
"To provide a great user experience, Google Play enforces a quota
on how often a user can be shown the review dialog. Because of this,
calling a launchReviewFlow method might not always display a dialog.
For example, you should not have a call-to-action option (such as a button)
to trigger a review as a user might have already hit their quota and the
flow won’t be shown, presenting a broken experience to the user." From the official
documentation
https://developer.android.com/guide/playcore/in-app-review. This
means that when you call the showRateDialog (or showRateDialog) method
with ignoreNative set to false, the Google Play Services may choose to
not show the dialog.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Skyost/RateMyApp/issues/64#issuecomment-674014310,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJEI6XUP6AR5OXIQAYLFOLSAUIRRANCNFSM4P7H6RRQ
.

@kw2019ltd You're talking about Google's new rating dialog or Rate my app rating dialog ?

Google dialog.
On Sat, Aug 15, 2020, 13:29 Hugo Delaunay<EMAIL_ADDRESS>wrote:

@kw2019ltd https://github.com/kw2019ltd You're talking about Google's
new rating dialog or Rate my app rating dialog ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Skyost/RateMyApp/issues/64#issuecomment-674380192,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJEI6WIE76BZV352WFJGTTSAZPPVANCNFSM4P7H6RRQ
.

@kw2019ltd They handle it as they want and the developer cannot do anything. They can decide to show it or not to show it.


Fix bug in pkgname extraction

Codecov Report

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

@@            Coverage Diff             @@
##             master        #5   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         2
  Lines             ?        31
  Branches          ?         0
==========================================
  Hits              ?        31
  Misses            ?         0
  Partials          ?         0

Flag
Coverage Δ

unittests
100.00% <0.00%> (?)

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

Continue to review full report at Codecov.

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


[RELENG-7490] 🐛 Bug fixing

Codecov Report

Merging #27 (410a043) into improvement/RELENG-7490-cost-estimate-at-PR (aa882bc) will increase coverage by 33.54%.
The diff coverage is 73.75%.

@@                               Coverage Diff                                @@
##           improvement/RELENG-7490-cost-estimate-at-PR      #27       +/-   ##
================================================================================
+ Coverage                                        13.97%   47.52%   +33.54%
================================================================================
  Files                                                9       13        +4
  Lines                                              415      585      +170
================================================================================
+ Hits                                                58      278      +220
+ Misses                                             357      307       -50

Impacted Files
Coverage Δ

gh_actions_exporter/githubClient.py
80.00% <0.00%> (+34.54%)
:arrow_up:

tests/api/app/test_app.py
23.07% <ø> (ø)

tests/api/conftest.py
69.04% <ø> (ø)

tests/api/metrics/test_job.py
11.84% <ø> (ø)

gh_actions_exporter/cost.py
30.90% <36.36%> (+21.98%)
:arrow_up:

tests/unit/test_cost.py
65.21% <45.45%> (ø)

gh_actions_exporter/main.py
55.55% <100.00%> (+42.51%)
:arrow_up:

gh_actions_exporter/metrics.py
20.66% <100.00%> (+20.66%)
:arrow_up:

gh_actions_exporter/types.py
100.00% <100.00%> (+100.00%)
:arrow_up:

... and 3 files with indirect coverage changes


A few minor fixes

See individual commits and their respective messages.

:tada: This PR is included in version 0.8.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: Fixed a bug which prevented mypy version update

Summary of Changes
Fixed a bug which prevented the update from mypy version 1.8.0 to 1.9.0.
Mypy Update PR: https://github.com/Safe-DS/Stub-Generator/pull/91

:tada: This PR is included in version 0.3.0 :tada:
The release is available on:

v0.3.0
GitHub release

Your semantic-release bot :package::rocket:


[YUNIKORN-1345]  Updating the Spark tutorial in yunikorn website

Issue description
The spark image mentioned in the spark tutorial doesn't exist.
Currently, the Spark community provides the official image.
This tutorial adopts spark:v3.3.0.
I updated the commands and the authentication files.
Issue classification

[x] improvement
[ ] task
[ ] bug

Issue Jira
https://issues.apache.org/jira/browse/YUNIKORN-1345
How to test

BTW, the yunikorn UI didn't reveal the spark application although the application assigned with applicationId is completed.
I will create an issue for tracing this situation.


Cleanup: VIO

No logical changes
Remove unnecessary include headers
Fix format
Make const functions

Cherry-picked to v9.0.x branch.


Setting ssl_verify_mode

Hi,
Pretty new to chef and i want to disable SSL for our test environment, but can't for the life of me figure out how to do it via the chef-client cookbook.
I understand i need to set ssl_verify_mode     = 'verify_none' somewhere. I've tried putting it in the config.rb and also in default.rb.
could someone advise please?
thanks

You want to set the attribute ['chef_client']['config']['ssl_verify_mode'].


fix link

Thank you @Lukas1818,
Can you please amend your commit message so it respect the conventional commits specification ?

It's sad to see that projects unnecessarily raise the bar pretty high for simple pull requests like this one. Reading such a long documentation is definitely not worth the time investment for a one-line fix like this one. Feel free to disagree.

I do disagree,
I really think raising the bar from the start and holding to it as
many benefits in the long run.
Successful projects use these kind of conventions for a reason.
Respecting the convention is mandatory here because version are automatically bumped from the commit history,
changelogs are generated using the convention and it makes the git log human readable and meaningful.
Also I really don't see in what way amending a commit to make it meaningful could be see as "raising the bar",
It's just hygiene to me.
I am a bit biased because I maintain the tool we use here.
I hope there is no hard feeling though.


TestClipPaintingContext should dispose ContainerLayer

Prerequisite: https://github.com/flutter/flutter/pull/135942
Fixes: https://github.com/flutter/flutter/issues/134572
Fixes: https://github.com/flutter/flutter/issues/134575

FYI @ksokolovskyi


Could not resolve all dependencies for configuration ':_debugCompile'.    > Could not find any version that matches com.google.android.gms:play-service s-gcm:7.5.+.      Versions that do not match:

Edit config file: platforms/android/cordova-plugin-gcmpushplugin/appointment-build-extras.gradle
Replace by below lines:
apply plugin: 'com.google.gms.google-services'

buildscript {
    repositories {
        jcenter()
    }

    dependencies {
        classpath 'com.google.gms:google-services:3.0.0'
    }
}

dependencies {
    compile "com.google.android.gms:play-services-gcm:9.0.0"
}


Balder/balder/per document query coverage rebased 2

@havardpe and @toregge These is a rebase of #6583 + some error checking

I will take out all style changes by themselves.


ERROR in ./src/main.ts Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in 'C:\temp\foobar\src'  @ ./src/main.ts 3:0-74  @ multi ./src/main.ts

Bug Report or Feature Request (mark with an x)
- [X] bug report
- [ ] feature request

Versions.
@angular/cli: 1.2.3
node: 6.10.2
os: win32 x64
@angular/animations: 4.3.1
@angular/common: 4.3.1
@angular/compiler: 4.3.1
@angular/core: 4.3.1
@angular/forms: 4.3.1
@angular/http: 4.3.1
@angular/platform-browser: 4.3.1
@angular/platform-browser-dynamic: 4.3.1
@angular/router: 4.3.1
@angular/cli: 1.2.3
@angular/compiler-cli: 4.3.1
@angular/language-service: 4.3.1
Repro steps.
npm install @angular/cli -g
ng new foobar
cd foobar
npm install
ng build --prod
The log given by the failure.
C:\temp\foobar>ng build --prod
Hash: fbb89132e330aaa03dd9
Time: 7068ms
chunk    {0} polyfills.1553fdd8173a081c720c.bundle.js (polyfills) 177 kB {4} [initial] [rendered]
chunk    {1} main.c22b61509cde9fcee2d3.bundle.js (main) 1.1 kB {3} [initial] [rendered]
chunk    {2} styles.d41d8cd98f00b204e980.bundle.css (styles) 69 bytes {4} [initial] [rendered]
chunk    {3} vendor.f7457d5ac1e9743fd76f.bundle.js (vendor) 849 kB [initial] [rendered]
chunk    {4} inline.3a7e7a530cd68edb2099.bundle.js (inline) 0 bytes [entry] [rendered]
ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in 'C:\temp\foobar\src'
@ ./src/main.ts 3:0-74
@ multi ./src/main.ts
Desired functionality.
A simple production build of a generated application. I noticed that after updating to the latest angular/cli version, I'm constantly getting this error (on all existing and all new projects).
Mention any other details that might be useful.

See comments here: https://github.com/angular/angular-cli/issues/7118

Thanks. That indeed seems to be the issue.
npm i<EMAIL_ADDRESS>resolved my issue.

I didn't work with npm i<EMAIL_ADDRESS>:(

@Tohnmeister  is any configuration need to be done after installing enhanced-resolve?

No. No configuration was needed. I just needed to install the specific
version.
2017-08-19 9:36 GMT+02:00 nilesh<EMAIL_ADDRESS>
@Tohnmeister https://github.com/tohnmeister is any configuration need
to be done after installing enhanced-resolve?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/7122#issuecomment-323507101,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABn6CQYncePe5IwO0czPkfhaZhgxwtWcks5sZpBhgaJpZM4OhTcf
.


Added uri_unescape() to handle escaped characters in URI (%XX).  v2

Manage escaped hex characters within URI (%XX).

👍


Can you provide a bit more info about how to expose the geojson?

This seems like what I want to use to share a geojson. I have it as a gist...but am not exactly sure how to generate the site still.
Thanks!

Well.
I figured it out.
And I guess it only took 6 minutes, so maybe everyone else is just six minutes smarter than me.
This is awesome.
I still think it may be worth adding a line in the readme about how to just add the link to the url to the base link, and add parameters to modify. I am surprised I haven't seen this before.


Absorb upstream changes up to v0.27-beta

Context: https://centrepopgen.slack.com/archives/C02E83V5JSF/p1678910500913689?thread_ts=1678841985.740089&cid=C02E83V5JSF
Prior to continuing adoption work we've been advised to adopt changes up until the v0.27b release (c. 12 hours ago)
I've not done a downstream merge on a forked repo before 😬 Hoping this is the right process

I expected way more conflicts, so this seemed too good to be true.. I'll bear that in mind for future changes!

Can this be closed, now that https://github.com/populationgenomics/gatk-sv/pull/12 has been merged?

Closed - see #12


StrongParameters with hash values have to be at the end

Fixes #79
https://github.com/rails/rails/commit/e86524c0c5a26ceec92895c830d1355ae47a7034

@bzwei @gmcculloug Please review


Too many WAFv2 types

The WAFv2 module contains a large number of types which causes knock-on impact in other areas.
Downstream issues:

https://github.com/pulumi/pulumi/issues/11552
https://github.com/pulumi/pulumi-aws/issues/2250
https://github.com/pulumi/registry/issues/1481

We need to find a way of reducing the number of types to avoid these issues. One low-complexity solution could be to just change the offending type to a fully untyped "any" type.

I was able to view the Go package documentation in terminal like this:
go doc -all github.com/pulumi/pulumi-aws/sdk/v5/go/aws/wafv2 | less

interesting to note the scale of the issue:
$ go doc -all github.com/pulumi/pulumi-aws/sdk/v5/go/aws/wafv2 | wc -l
  979307
$ go doc -all github.com/pulumi/pulumi-aws/sdk/v5/go/aws/ec2 | wc -l
   73026
$ go doc -all github.com/pulumi/pulumi-aws/sdk/v5/go/aws/s3 | wc -l
   22090

I was unable to actually use this package because the Go compiler would use over 30 GB of memory on my system trying to compile this package while importing it (before I gave up and killed it).

This will be fixed by https://github.com/pulumi/pulumi-aws/pull/2589 in 6.0 of the provider


BucketFS: File '/buckets/bfsdefault/default/EXASolution-6.0.0/exaudfclient' does not exist

Hi again!
For our development process, we'd like to create a pre-migrated and ready-to-use Exasol image.
We are using MyBatis to run some DDL statements against the DB, but unfortunately on some machines this fails with the following error:
ERROR: Error executing command.  Cause: org.apache.ibatis.jdbc.RuntimeSqlException: Error executing: CREATE OR REPLACE PYTHON SCALAR SCRIPT dwh_partitions.py_generate_uuid_char_base64()
RETURNS CHAR(22) CHARACTER SET ASCII AS
import uuid
import base64
def run(ctx):
  return base64.b64encode(uuid.uuid4().bytes)[:-2]
/

.  Cause: java.sql.SQLException: BucketFS: File '/buckets/bfsdefault/default/EXASolution-6.0.0/exaudfclient' does not exist. (Session:<PHONE_NUMBER>663861959)

The exaudfclient file seems to exist although separated by a : in the path instead of a /:
# find /exa/data/bucketfs/ | grep exaudf
/exa/data/bucketfs/bfsdefault/default/EXASolution-6.0.0:exaudf.jar
/exa/data/bucketfs/bfsdefault/default/EXASolution-6.0.0:exaudfclient

One machine where this is failing is running Docker version 17.04.0-ce, build 4845c567eb, one machine where it is working runs Docker version 1.12.3, build 6b644ec.
Could this be Docker version related? Or might something else be going on?
Thanks!

Hi!
The path /exa/data/bucketfs/bsfdefault/default is used as source, but real data are in the .dest directory. On my system your find gives following:
$ docker exec -it dreamy_visvesvaraya /bin/bash
[root@n11 /]# find /exa | grep exaudfclient
/exa/data/bucketfs/bfsdefault/default/EXASolution-6.0.0:exaudfclient
/exa/data/bucketfs/bfsdefault/.dest/default/EXASolution-6.0.0/exaudfclient
[root@n11 /]#

Your problem seems to be, that you have waited not long enough. On each start, this package need to be extracted:
# ls -lh /exa/data/bucketfs/bfsdefault/default/EXAClusterOS\:ScriptLanguages-2017-01-30.tar.gz
-rwxr-xr-x 1 u00500 g00500 494M Apr 27 08:40 /exa/data/bucketfs/bfsdefault/default/EXAClusterOS:ScriptLanguages-2017-01-30.tar.gz

It contains the environment for UDFs and it can take some time, especially on somewhat slower machines. This is a point to be optimized in future versions.
Best regards
Oleksandr

Hi Oleksandr,
correct again! If I start the container manually and wait for a while, the file in .dest appears.
Is there a way (e.g. an SQL statement) to ask Exasol if it has already finished unpacking the required stuff?

Unfortunately it is no API there to check it.
But you can define and run an dummy UDF, if it worked without errors, than everything work, if not, you need to wait a bit.

Fair enough. We adapted the script that waits until it can connect to EXASOL to check if it can create a script now.
Thanks for your help!


Code analysis pull down broken

From<EMAIL_ADDRESS>on 2012-01-18T21:37:37Z
What steps will reproduce the problem?

Create a syntax error in any script and enable pyflakes code analysis in Tools...Preferences.
Click on the pull-down arrow next to the "Show code analysis warnings/errors" icon in the toolbar. What is the expected output? What do you see instead? Should see a list of pyflakes code analysis results for the current file. No list appears. The following traceback occurs in the Internal Console:

>>> Traceback (most recent call last):
File "C:\Py27\lib\site-packages\spyderlib\plugins\editor.py", line 1183, in update_warning_menu
for message, line0, error in check_results:
ValueError: need more than 2 values to unpack
Problem was initially discovered in the discussion of issue #906 .
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=912

From<EMAIL_ADDRESS>on 2012-01-18T19:21:01Z
A potential fix can be located on the branch called Issue912 in my clone: https://code.google.com/r/jedludlow-spyderlib/source/detail?r=e1abfec6ea739d0fc100113ed24a820065591581&name=Issue912 .
I'm not confident that I completely captured the original design intent with this fix, so as always your review and subsequent changes are welcome.
Status: Started
Owner: pierre.raybaut

From<EMAIL_ADDRESS>on 2012-01-21T15:01:22Z
I've attached a patch file for /spyderlib/plugins/editor.py to remove dependence on my clone.
Attachment: editor.py.patch

From pierre.raybaut on 2012-01-22T03:22:34Z
Actually, you forgot to handle the 'error' value like here: https://code.google.com/p/spyderlib/source/browse/spyderlib/widgets/sourcecode/codeeditor.py#1486 I'm on it.

From pierre.raybaut on 2012-01-22T03:22:53Z
This issue was closed by revision 683d1ad20456 .
Status: Fixed

From pierre.raybaut on 2012-01-22T10:24:54Z
BTW, the "Show TODO/FIXME/XXX/HINT/TIP comments list" button was not working too!
But not for the same reason at all actually.
Anyway, I've fixed it too: https://code.google.com/p/spyderlib/source/detail?r=3d00dd5650316d3522d94b42fdbb9accaff20b8e


com.vdurmont.semver4j.SemverException: Invalid version (no major version): "^1.2.0"

Since an upgrade to 6.5.2 we are getting an error when running dependency check. Log Here
I suspect this change is the cause. Seems like semver isn't handling the ^ symbol correctly.

Do you have a sample project? I'm betting this is due to the Node.js Package Analyzer being enabled -  we have plans to deprecate this analyzer and fold some of its capabilities into the Node Audit Analyzer.

I would, however, not expect the package-lock.json to have a semver range version. Always thought that package-lock.json was meant to keep development state at an explicit version and only package.json was supposed to have ranged versions?
https://docs.npmjs.com/cli/v6/configuring-npm/package-locks

The error can be re-created by:
package.json
{
  "name": "my-awesome-package",
  "version": "1.0.0",
  "dependencies": {
    "minimist": "^1.2.5",
    "sharkdown": "^0.1.1"
  }
}

#create package-lock.json
npm install
dependency-check --scan ./package-lock.json

[WARN] An unexpected error occurred during analysis of '.../tmp/package-lock.json' (Node Audit Analyzer): Invalid version (no major version): "^1.2.5"
[ERROR]
com.vdurmont.semver4j.SemverException: Invalid version (no major version): "^1.2.5"
	at com.vdurmont.semver4j.Semver.<init>(Semver.java:61)
	at org.owasp.dependencycheck.analyzer.AbstractNpmAnalyzer.determineVersionFromMap(AbstractNpmAnalyzer.java:530)
	at org.owasp.dependencycheck.analyzer.AbstractNpmAnalyzer.processResults(AbstractNpmAnalyzer.java:471)
	at org.owasp.dependencycheck.analyzer.NodeAuditAnalyzer.analyzeDependency(NodeAuditAnalyzer.java:151)
	at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
	at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
	at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)

The error is confusing as there is no mention of version ^1.2.5 in package-lock.json.
Running it with --disableNodeAudit causes it not to error.

We've also hit the same error, after going from 6.2.2 to 6.5.2
[ERROR]  com.vdurmont.semver4j.SemverException: Invalid version (no major version): "6.0.1" 	at com.vdurmont.semver4j.Semver.<init>(Semver.java:61) 	at org.owasp.dependencycheck.analyzer.AbstractNpmAnalyzer.determineVersionFromMap(AbstractNpmAnalyzer.java:530) 	at org.owasp.dependencycheck.analyzer.AbstractNpmAnalyzer.processResults(AbstractNpmAnalyzer.java:471) 	at org.owasp.dependencycheck.analyzer.YarnAuditAnalyzer.analyzeDependency(YarnAuditAnalyzer.java:108) 	at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131) 	at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88) 	at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37) 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) 	at java.base/java.lang.Thread.run(Thread.java:832) [INFO] Finished Yarn Audit Analyzer (2 seconds)
In 6.2.2 the Yarn Audit Analyzer worked as expected - the exception we now get is a bit cryptic - as the semver appears valid (there is a major version) and the log doesn't indicate which library (in our yaml.lock) has the issue?

Your package.json specifies the required version of minimist to be ^1.2.5.
Your package-lock.json contains the resolved version 1.2.5:

"minimist": {
  "version": "1.2.5",
  "resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
  "integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw=="
},

The error is confusing as there is no mention of version ^1.2.5 in package-lock.json, which i'm guessing is being picked up from the package.json

Your package-lock.json will not generally include the tilde and caret notations (specifying tolerance around updated minor and patch versions) except in the requires object - not for the resolved dependencies, as seen in your example.
A package-lock.json using ^ or ~ rather than version pinning would kinda defeat the point of its existence. But you're right, the error output from Node Audit Analyzer implies the referenced version is in your lock file - which it clearly isn't.
This wasn't obvious in my example, because the referenced version (6.0.1) does appear in my yarn.lock (coincidentally, for several unrelated libraries).


mac默认配置文件在哪里，不想自动上传

qiniu.cfg在mac上面怎么设置？
qiniu4blog /Users/qq/Desktop/QQ20160925-0.png
Error Config File: No section: 'config'
Exception in thread Thread-1:
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/Library/Python/2.7/site-packages/qiniu4blog/qiniu4blog.py", line 32, in run
job(self.filePath, self.mode)
File "/Library/Python/2.7/site-packages/qiniu4blog/qiniu4blog.py", line 41, in job
url = upload_with_full_Path_cmd(file)
File "/Library/Python/2.7/site-packages/qiniu4blog/qiniu4blog.py", line 139, in upload_with_full_Path_cmd
upload_without_key(bucket, filePath, fileName.decode(setCodeingByOS()))
NameError: global name 'bucket' is not defined

请问这个问题怎么解决的？

没有解决 作者应该已经弃坑了

..... 我跟了半天代码发现是那个config获取不到


cookbook with dask client gives out a lot of warnings about bad chunking

I've been getting these for a while. I think we shouldn't ignore these.
I managed to pin it down to the warnings appearing only when a dask client is present. See
https://gist.github.com/navidcy/2fd2a4464d8cf06b25e1b2130c3cfbe9

Discussion in https://github.com/COSIMA/cosima-recipes/pull/305 might be relevant.
cc @angus-g, @dougiesquire

I think this is the same issue as #333
And per https://github.com/COSIMA/cosima-recipes/pull/305#issuecomment-1776394141, the suggestion is to remove the chunking that the cookbook is doing.

And per https://github.com/COSIMA/cosima-recipes/pull/305#issuecomment-1776394141, the suggestion is to remove the chunking that the cookbook is doing.

Yup. Xarray v2023.09.0 introduced some changes to the way the chunks argument to open_dataset is handled. As part of this, a warning was added when the requested dask chunks divides the netcdf chunks. The cosima-cookbook getvar function internally determines the netcdf chunking of first variable in the file and opens the file using that chunking. If there are other variables in the file with larger chunks than the requested variable, their chunks will be divided and the warning will be thrown.
As I said in https://github.com/COSIMA/cosima-recipes/pull/305#issuecomment-1776394141, the best fix is probably to change the cosima-cookbook to open the files with chunks={} rather than the chunking of the first variable. This will then use each variable's netcdf chunking.
Note that all that's changed is that the warning has been added to xarray. This was always happening in the cosima-cookbook.

oops, yes this may be a duplicate or related to #333!
@dougiesquire yeap thanks for re-iterating. I just wanted this in the cookbook repo.
So I understand that the only change we got is that the warnings appeared. But I presume, that the folks at xarray/dask decided to add the warnings for a reason. Therefore, from what I understand, we could either:

take these warnings into consideration because we agree they are important and do something about it
or
point out to them that we have a case in which these warnings are not relevant and showcase an example via an issue in their repo
or
decide that the warnings are relevant but still we are doing the best we can anyway... in that case do something so that the warnings don't show up to every cookbook user
or
something else?

point out to xarray devs that we have a case in which these warnings are not relevant and showcase an example via an issue in their repo

I think the warnings are doing what they're supposed to here.
If you want to, you could ignore the warnings with something like:
import warnings
warnings.filterwarnings("ignore", message="The specified chunks separate the stored chunks along dimension")

Probably the best option is to change the cosima-cookbook as described above, but afaik there is no one maintaining the cookbook.

something else?

Use the intake-catalogue :)

@angus-g is this resolved with #341?

something else?

Use the intake-catalogue :)

cheeky :)

@angus-g is this resolved with #341?

No


Feed title and description are empty

The blog title is displayed as "unknown" in my feed reader because the TITLE tag is empty.

Thanks!


assertions should receive boolean expressions

Compliant Solution
System.assert(cond1 || cond2 || (cond3&cond4));
System.assert(a boolean boo = x/y >= 2;


Social auth broken in supabase-js v2.7 (works in v2.6.0)

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Social auth worked perfectly in my app (quizfreely.ehan.dev) until today (v2.7 was published on npm today i think). When trying to sign in with google, supabase would redirect to google's auth screen and google's auth screen would redirect back to my app successfully. However supabase wouldn't sign the user in once redirected back. Email sign in still works perfectly, but social auth doesn't.
To Reproduce

Use supabase-js v2.7 (I used it through a cdn, jsdelivr)
Try to sign in with some social auth (In my case it's google)
Supabase redirects to google auth screen
Google auth screen redirects back to your site
Your not sign-in-ed ¯\_(ツ)_/¯

How I temporarily un-broke my app
This problem does not happen in v2.6.0 (which is why it only started happening to me today), so I downgraded to v2.6.0 and now everything works! ¯\_(ツ)_/¯
System information

Browser: Chrome
Version of supabase-js: 2.7

Additional context
This is probably NOT the same problem as (#811), because #811 mentions that their problem still happens in 2.6, while my problem is solved in 2.6 and only happens in 2.7

I think you meant v2.26 and v2.27 instead of v2.6 and v2.7?


Number of indexed documents decrease during indexing

I noticed a strange behavior when I index 500 000 documents.
At some point during the indexing, the number of documents is decreasing:

meilisearch.log
ram.log

grep 'indexed_documents' meilisearch.log
2022-08-24T15:16:05Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 1000 }
2022-08-24T15:16:05Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 2000 }
2022-08-24T15:16:06Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 3000 }
2022-08-24T15:16:07Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 4000 }
2022-08-24T15:16:33Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 20000 }
2022-08-24T15:16:37Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 21000 }
2022-08-24T15:16:40Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 22000 }
2022-08-24T15:16:43Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 23000 }
2022-08-24T15:16:44Z INFO  DocumentAdditionResult { indexed_documents: 1000, number_of_documents: 24000 }
2022-08-24T15:17:08Z INFO  DocumentAdditionResult { indexed_documents: 10000, number_of_documents: 50000 }
2022-08-24T15:17:36Z INFO  DocumentAdditionResult { indexed_documents: 23000, number_of_documents: 88000 }
2022-08-24T15:18:18Z INFO  DocumentAdditionResult { indexed_documents: 34000, number_of_documents: 150000 }
2022-08-24T15:18:45Z INFO  DocumentAdditionResult { indexed_documents: 46000, number_of_documents: 196000 }
2022-08-24T15:19:18Z INFO  DocumentAdditionResult { indexed_documents: 58000, number_of_documents: 254000 }
2022-08-24T15:19:42Z INFO  DocumentAdditionResult { indexed_documents: 64000, number_of_documents: 318000 }
# ☠ Something is weird here, it goes from 64000 to 45000 documents
2022-08-24T15:20:04Z INFO  DocumentAdditionResult { indexed_documents: 45000, number_of_documents: 363000 }
2022-08-24T15:20:46Z INFO  DocumentAdditionResult { indexed_documents: 39000, number_of_documents: 441000 }

Workaround

Disable --enable-auto-batching but it takes ages to index all documents.
Or create the index from a dump file.

Technical information

Meilisearch commit: 8e370ed9ab7f794f6fa97f7483a61061818ce1d8
Meilisearch commit date: 2022-07-11T12:41:15Z
Meilisearch version: 0.28.0 (I also tried 0.28.1)
MEILI_ENV=production
System:                   RedHat 8
CPU Architecture:        x86_64
CPU Socket(s):           4
RAM:                      7928MB
Auto-batching feature is enabled.

Dataset information

I have 500 000 documents to index.
Each batch contains 1000 documents.
Language is English.

A document looks like this:
{
  "id": "1",
  "author": "",
  "test_case_id": 20792,
  "state": "mixed",
  "submission_date":<PHONE_NUMBER>,
  "status": "deprecated",
  "language": "c",
  "application": "cpe:2.3:a:ffmpeg:ffmpeg:3.2.15:*:*:*:*:*:*:*",
  "cve": ["CVE-2022-38667"],
  "file": [
    "file-a.c",
    "file-b.c",
    "file-c.h",
    "file-d.h"
  ],
  "operating_system": "windows",
  "flaw": [
    "CWE-194"
  ],
  "description": "CWE: 194 Unexpected Sign Extension\n BadSource: negative Set data to a fixed negative number\n GoodSource: Positive integer\n Sinks: memmove\n BadSink : Copy strings using memmove() with the length of data\n Flow Variant: 45 Data flow: data passed as a static global variable from one function to another in the same source file",
}

settings of index
{
  "displayedAttributes": [
    "*"
  ],
  "searchableAttributes": [
    "author",
    "test_case_id",
    "state",
    "submission_date",
    "status",
    "language",
    "application",
    "cve",
    "file",
    "operating_system",
    "flaw",
    "description"
  ],
  "filterableAttributes": [
    "application",
    "author",
    "cve",
    "description",
    "file",
    "flaw",
    "id",
    "language",
    "operating_system",
    "state",
    "status",
    "submission_date",
    "test_case_id"
  ],
  "sortableAttributes": [
    "submission_date"
  ],
  "rankingRules": [
    "words",
    "typo",
    "proximity",
    "attribute",
    "sort",
    "exactness"
  ],
  "stopWords": [],
  "synonyms": {
    "cplusplus": [
      "c"
    ],
    "csharp": [
      "c"
    ]
  },
  "distinctAttribute": null,
  "typoTolerance": {
    "enabled": true,
    "minWordSizeForTypos": {
      "oneTypo": 5,
      "twoTypos": 9
    },
    "disableOnWords": [],
    "disableOnAttributes": []
  },
  "faceting": {
    "maxValuesPerFacet": 100
  },
  "pagination": {
    "maxTotalHits": 10000
  }
}

Misc

I have the same meilisearch instance running on another machine (Ubuntu 20.04.4 LTS, 16GB), same index settings, same documents and the indexing runs like a charm.
meilisearch.log
ram.log

Let me know if you have any questions!

Hi @curquiza,
You're absolutely right, my bad. I had issues with Meilisearch a week ago, the indexing crashed the machine, I suspect Meilisearch to eat all the RAM memory.
I reindexed all the documents this morning and it works.
indexed_documents is not important to me. I was a bit confused with the term index_documents and number_of_documents.
Sorry for the inconvenience.

Not a problem at all 😄

You're absolutely right, my bad. I had issues with Meilisearch a week ago, the indexing crashed the machine, I suspect Meilisearch to eat all the RAM memory.

Sorry for this, Meilisearch indeed has issues with RAM consumption. We are doing our best to improve this!
Could you give your usecase (machine + dataset size + auto-batching or not) and how you got this crash on this issue? It would be really helpful 🙏
Do you still have the crash now?

Unfortunately, I was not able to reproduce the crash and I don't have the logs anymore.


Updated dependencies: repos and versions

Upped versions of proj4js and leafletjs. Also pointing to official leaflet repo instead.

+1

It'd be great to see this merged.
As it stands, pulling in leaflet-dist instead of leaflet can break some build chains by causing both leaflet and leaflet-dist to be installed -- in our case, grunt-wiredep would first wire in the leaflet provided by leaflet-dist, then proj4leaflet, then... leaflet, which replaced the leaflet-dist and effectively removed proj4leaflet.
We have an easy workaround, but it seems like the stopgap that leaflet-dist was addressing in terms of Bower is no longer relevant and it'd make sense to point at the official repo.

@perliedman that's actually a good observation: should be the earliest possible release. I was a bit overzealous at the time and not too familiar with Bower myself. Will revert version numbers, while keeping the main repo for Leaflet.js.


added in lua

What does the program do ?

In what programming language it is written?

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


14.1.6 support

14.1.6 support

All tests are passed in 14.1.6 except

Because there are no structural changes here, another way to do this is to leave the file in the original location, but add a compile-time constant to call the different API:
In IdeaTarget.java:

  public static final int SDK_14_1_CODELINE = 141
  public static final int SDK_14_1_6_BUILD_NUMBER = 3056
  public static final boolean IS_VERSION_14_1_6_OR_LATER =
                                   (SDK_CODELINE >= SDK_14_1_CODELINE
                                    && SDK_BUILD_NUMBER >= SDK_14_1_6_BUILD_NUMBER)

And in the sources:

  if (IdeaTarget.IS_VERSION_14_1_6_OR_LATER) {
    // use new api
  } else {
    // use old api
  }

BTW, all tests were passing in Linux.

I don't really understand, override function API was changed for shiftIndentInsideRange, I can't see the way how it could be implemented

Can you add the old function signature back to the object?  I think so.  But maybe it's harder than I think.
Once we get clean builds, I'll take the change and I'll see about re-working it the way I envision.  I want to get rid of the v13/v14/v15 source trees as much as possible.  They're already becoming a maintenance headache, since I have to make changes in several files any time I touch one of them.

old function signature won't compile, because overridden function doesn't exists,
Their FormattingModel class in IDEA was changed

I want to get rid of the v13/v14/v15 source trees as much as possible. They're already becoming a maintenance headache, since I have to make changes in several files any time I touch one of them.
Yeah I agree

It looks like JetBrains has locked down or removed the 14.1.4 version from their distribution site so Travis can't get to it.  We have to find another solution for serving the older builds.  And, we have to add a 14.1.6 build, since it's not compatible with 14.1.4.

Do you want to keep compatibility with 14.1.4?

Do you want to keep compatibility with 14.1.4?

Yes, I want to keep compatibility with all 14.x releases.  At least until we get to version 16.

By the way, the breaking change was released in 14.1.5, not 14.1.6.

So version number should be 2735

So version number should be 2735

Yes, and the names of the properties files should contain 14.1.5 instead of 14,1,6.  And the 14.1 properties file needs to be limited to builds 1532 (14.1.4) or less.  But just in case folks use intermediate builds, we can be nice and limit 14.1 at 2734 (unless you want to go find the actual build where it changed, but that's a bit of work, I think.

This PR was superseded by #384.  Closing.

@as3boyan Any reason to keep the 14.1.6 branch?

@EBatTiVo I think I moved files from 14.1.6 to 14.1.5, to me there is no reason for keeping separate branch for 14.1.6


probable bug in sql function

Sorry maybe i dont understand correctly the way for passing parameters in a sql function
but it seams a bug considering different attempts executed
language: sql
function test(a)
body : return $a;
select test(1)
it dont return anything.
body : return a;
exception : so it implies $a is correct.
body : return 1;
it returns correctly result.
I hope i submited a bug usefull to fix to loveable orientdb:)

Hi @publicocean0
It seems to work fine here (v.2.2). If there was a bug, it's already fixed.
Maybe the problem was due to the $
I defined the function with input param = a and with body return a;
Thanks
Luigi


[Feature Request] Option to only use Tokens from the Custom Autocomplete Dictionary

Hello @tadashi-aikawa !!!!!!
I'd like to suggest an option in the Settings to only use the words in the custom dictionary
From README.md

Auto Complete
It complements the text with tokens that exists in a current file.

In my case I just want to complement the text with tokens from the Custom Autocomplete Dictionary and NOT from the current file :)

Let me know if you need more information !
Thanks for reading this :)
I wish you a fantastic day!

Hi, @FelipeRearden. Thank you for your Feature Request!

I'd like to suggest an option in the Settings to only use the words in the custom dictionary

It looks good. I'll add a new option 👍

Hi, @FelipeRearden. Thank you for your Feature Request!

I'd like to suggest an option in the Settings to only use the words in the custom dictionary

It looks good. I'll add a new option 👍

Hello @tadashi-aikawa !!!!!
Thank you very much !!! I'm glad that you like my FR :)
Have a great day!

@FelipeRearden
I have released as v1.3.0 🚀

@FelipeRearden
I have released as v1.3.0 🚀

Hello @tadashi-aikawa !!!!!
Thank you very much !!!!!!!!
I updated and is working perfect !!!! Thank you very much for this new feature, it's perfect :)
Working on version 1.3.0 Obsidian 0.12.19
I wish you a fantastic day :)


关于mention type和argument role

Agreement

[x] Fill the space in brackets with x to check the agreement items.
[x] Before submitting this issue, I've fully checked the instructions in README.md.
[x] Before submitting this issue, I'd searched in the issue area and didn't find a solved issue that covers my problem.
[x] This issue is about the toolkit itself, not Python, pip or other programming basics.
[x] I understand if I do not check all the agreemnt items above, my issue MAY BE CLOSED OR REMOVED WITHOUT FURTHER EXPLANATIONS.

Problem
您好，您论文Figure 1中涉及到了两个概念：mention type和argument role，并且在Entity Representation部分也使用到了mention type这一信息。这两者的含义和区别我明白，但是在duee数据集中有mention type这个标注信息吗？我检查了一下，似乎只有argument role。
Environment

Environment
Values

System
Windows/Linux

GPU Device

CUDA Version

Python Version

PyTorch Version

dee (the Toolkit) Version

Full Log
Log:

好的 感谢您的回复！


Implement action for webook

Implemented action creation for webhooks and added functionality to link multiple actions to a capability.

a  demo video attached below
demo view

@sethumadhavan-k  resolve conflicts

@sethumadhavan-k  Linked Actions are not showing

@sethumadhavan-k  documentation section is not required for this category

@ashmilhussain fixed the conflict


Add custom telemetry instrumentations

Couldn't figure out how to add @opentelemetry/instrumentation-pg support with telemetry configuration enabled. Is it supported?

How are you adding it? If you use the @opentelemetry packages, you can completely avoid the telemetry config option and just configure those.

Problem was that I am using ESM, finally got it working: https://github.com/xxzefgh/platformatic-otlp-esm-example
Couple of notes:

When I start the project, instrument.mjs gets loaded 3 times, probably something to do with runtime loader?

@opentelemetry/instrumentation-fastify has a bug where it doesn't re-export fastify.errorCodes and it breaks @fastify/restartable (probably other things too)

After patching it I got a lot of obscure spans because it also traces plugins I guess, so I ended up with @autotelic/fastify-opentelemetry

Eventually we will add instrumentation to all of @platformatic/sql-mapper.

Created https://github.com/platformatic/platformatic/issues/2594. Thanks for reporting this.


Add a table of content with a link to snippets so it is easier to navigate the readme file.

Hey, @Deveesh-Shetty can you assign this issue to me? I'd love to contribute further to it.

Oh yeah sure!
@vagxrth I assigned the issue to you...

can you assign it to me

@Salonikansal2 this issue has already been assigned to @vagxrth, you can checkout other issues in the repo.
If you have any questions feel free to comment on those issues.

Hey @Deveesh-Shetty I would like to ask you to help me with an issue over this. Can you please tell me like which is the main page of the project on which a table of contents has to be created, by table of contents what I'm comprehending is a navbar so If I'm not wrong please help me out with the query.

@vagxrth sorry for the confusion, I meant the table of contents for the readme file... But now It seems there are some issues with the Readme file.

The contributor has to add a Folder path which is redundant as we have a codepen link, and it is work to put in while creating a PR.
The Image is also another thing, we should completely remove it because to add an Image to the GitHub cloud storage they have to drag and drop it to the Readme file in GitHub, which is again difficult while creating PR.

So I am thinking of adding a Frontend website for the repo where we can show all the projects, with preview and code links. I will push the template website soon.
And we have snippets.json as well which we can use to populate the website snippets.
So now what you can do is create a readme file with content like this on top of the current table we can remove the old one in later stages...
## Snippets
- [Name of the Snippet](Code Pen Link) - Author
- [Name of the Snippet](Code Pen Link) - Author
- [Name of the Snippet](Code Pen Link) - Author
<Continue this>

I hope this helps. If not, feel free to ask questions about it if I missed something

I would like to contribute on this. Can you assign this task to me?

Last contributor doesn't seem active... Assigning it to you!


Allows for simulated reads that are present in the sample but not present in the ref db

Done by keeping two ref dbs at once, the full db and the truncated db. Most changes are in the workflo.sh script. Changed two other files to control the number of genomes to be considered when creating a genome or a protein reference database.

Re-ran a small test, found a bug (bitscore_threshold was not being set) that caused all Diamond inferences to be zero.

Hi @dkoslicki, I am just trying to understand in which script bitscore_threshold was set, could you kindly help me with that?

@mahmudhera this option didn't originally have a default, and (mistakenly) wasn't set to be required. So here it wasn't being invoked. I set the new default to be zero (i.e. ignore the bit score)

Thanks! I got it.


Feature: Add Tooltips

What are Tooltips?
Tooltips are text labels that appear when a user hovers over, focuses, or activates an element. They provide brief helper text about its function.
Benefits

Help guide users through their journey
Can assist with the user onboarding flow
Help direct attention toward a specific item or action
Direct users to self-help resources so that they don't have to unnecessarily reach out to support

Some options:

Create a tooltip component
Opentip
Tippy
Bootstrap Tooltip

I'll do it using chakra ui tooltip library as it is prominent and renowned ui lib nowadays


possibility to output long strings via Buffers

Hi.
check please this patch.

Returned both changes.

ko


Add show password functionality, implement welcome to HireHub redirection, and fix 'remember me' alignment

Issue Reference:
#166
Description:
Show Password Functionality:

Added the ability for users to toggle the visibility of their password in the sign-up form.
Users can now click on the eye icon to show or hide the password as needed.

Welcome to HireHub Redirection:

Implemented a redirect link for the "Welcome to HireHub" on sign in page. This now correctly navigates the user to the homepage  when clicked.

Fix 'Remember Me' Alignment:

Corrected the alignment issue with the 'Remember Me' checkbox and label in the sign-in form

Screenshots:
1 ->
Before

After

2 ->
Before
https://github.com/user-attachments/assets/56e526a8-e184-461b-ac79-dc62517b27f9
After
https://github.com/user-attachments/assets/2c26e674-fcf3-4ca2-aedc-d0c6e4b1ae11
3 ->
Before

After

Type of change:

[ ] Bug fix
[x] New feature
[ ] Breaking change
[x] Enhancement

@Yashgabani845 please assign me the labels #168


test: pip_list: Fix replacement pattern computation

Summary
Fix computing replacements pattern for pip_list tests to count characters in the original directory string rather than the regex::escape'd string.  The latter yields incorrect results if the workspace path contains characters such as - or ..
Fixes #2232
Test Plan
cargo test --test pip_list in a directory named uv-test to provoke the bug.

Thanks!


Cross-compilation fails on undefined reference to `rpl_realloc'

When compiling libpostal on Sailfish SDK for ARM, a cross-compilation is used. Compilation fails with
/bin/sh ../libtool  --tag=CC   --mode=link gcc -std=gnu99 -Wfloat-equal -Wpointer-arith -DLIBPOSTAL_DATA_DIR='"/usr/local/share/libpostal"' -O3 -Wfloat-equal -Wpointer-arith -DLIBPOSTAL_DATA_DIR='"/usr/local/share/libpostal"'  -L/usr/local/lib -o libpostal libpostal-main.o libpostal-json_encode.o libpostal.la -lm -lsnappy
libtool: link: gcc -std=gnu99 -Wfloat-equal -Wpointer-arith -DLIBPOSTAL_DATA_DIR=\"/usr/local/share/libpostal\" -O3 -Wfloat-equal -Wpointer-arith -DLIBPOSTAL_DATA_DIR=\"/usr/local/share/libpostal\" -o .libs/libpostal libpostal-main.o libpostal-json_encode.o  -L/usr/local/lib ./.libs/libpostal.so -lm /usr/local/lib/libsnappy.so -Wl,-rpath -Wl,/usr/local/lib
libpostal-main.o: In function `main':
main.c:(.text.startup+0x15c): undefined reference to `rpl_realloc'
main.c:(.text.startup+0x1ea): undefined reference to `rpl_malloc'
main.c:(.text.startup+0x1fe): undefined reference to `rpl_malloc'

To overcome it, one can define
ac_cv_func_malloc_0_nonnull=yes
ac_cv_func_realloc_0_nonnull=yes

in a shell before ./configure. I hope that there is a more elegant way to fix it in configuration scripts.

libpostal is primarily tested on are Mac OSX and Ubuntu. It typically works fine on most other flavors of Linux with a few modifications, but for platform-specific issues, I usually defer to users who have the relevant machines to test on.
If you're comfortable with autoconf (or are like me and Google "[issue] autoconf" until something minimally works and you can stop thinking about autoconf), feel free to add the relevant checks to configure.ac. Happy to accept pull requests.

Fair enough. I'll look around and will try to fix it.

I guess this can be closed now