Send Grid Event Web hook using php to update the record in data base of mail status

I would like to know if an event Webhook works for the free sendGrid account. I am sending my emails using API keys via sendgrid- php curl and I'm not receiving any webhook callbacks. I did set up the url in email settings and did a test nothing received at end point . When I send mail via the application, I get no webhook callbacks although I do receive the emails and the statistics in the sendgrid site.
Steps to Reproduce
1.Create an API key with all permissions in the Free account
2.In email settings, setup the event webhook
3.Send mails using the sendgrid php  api using the api key
4.Check if a webhook event has been received.
Here the code for sending mail using sendgrid .
filename: mail_process.php
/* sendgrid curl method ----*/
$urls = 'https://api.sendgrid.com/';
$params = array(
'api_user'  => '............',   // My send grid username
'api_key'   => '.............',   // My send grid password
'to'        => $row['email'],
'from'      => '.....something',
'fromname'  => ".....",
'subject'   => "Sendgrid Event hook",
'html'      => "thank you",
                'from'      =><EMAIL_ADDRESS>                );

                $request =  $urls.'api/mail.send.json';
                $session = curl_init($request);
                curl_setopt ($session, CURLOPT_POST, true);
                curl_setopt ($session, CURLOPT_POSTFIELDS, $params);
                curl_setopt($session, CURLOPT_HEADER, false);
                curl_setopt($session, CURLOPT_RETURNTRANSFER, true);
                $response = curl_exec($session);
                curl_close($session);

Now I want to track the mail status..using sendgrid Webhook. I have search google stackover flow but I could not understand as I am new to this API thing.
What I have done is set up the Event notication active and end point path is
filename: test.php
// Get the raw POSTed data
$data = file_get_contents("php://input");
// Decode said data
$records = json_decode($data, true);
print_r($records);
// Loop through the records
foreach ($records as $record) {
// Store the event
// Assume store_event does your data processing and inserting
//store_event($record);
// You should be able to access any parameter of the event as so
// $record["email"];
// e.g.

echo $record["email"];
echo " had an email ";
echo $record["event"];

}

Hello @Aadencoder,
I'm not sure, I will find out for you.

Hi @Aadencoder,
It is included. So I have added this issue to our backlog for deeper inspection. Thanks!

thanks, waiting for the inspection result..

Hi @Aadencoder,
Did you start with this guide?

Hi @Aadencoder ,
Curious to know, are you able to resolve your issue or not ?

@visabhishek Please open a new issue with details about what you're experiencing.


Snake Water Gun Game with JS

You have 10 chances in game, You play against the computer that will generate the other player, after 10 rounds your result will be displayed i.e the number of draws, wins and loses against the computer, and it will evaluate you based on your performance! Good luck!

Thanks for the PR. It has been merged.
If possible leave a star for this repository.


Missing notification on Android 13

Android 13 requires explicit permission.

Is the notification responsible for closing the app?
If so, I was just about to open a new issue...
BTW I really love the idea of this app. I believe its the best idea since someone thought of combining missions into banners ;)
Works perfect on Android < 13
One small feature request: Could you add an option (somewhere) to change the color?... (I'd prefer green of course :wink:)

Fixed in #29


Only use a spinner on a tty

I tried to use bk to push a package from GitHub Actions, but it failed:
https://github.com/sj26/github-actions-to-buildkite-packages-javascript-example/actions/runs/12133880719/job/33830150889#step:5:8

Pretty sure that message comes via spinErr. I think it's because it's trying to start spinner, and that seems to require a tty.
This wraps up the spinner a little function that checks if we're in a tty when starting a spinner, and skips the spinner if we're not.
I haven't attempted tests yet .. I just wanted to see if this works.
I did test this locally and could still push a package and it showed a spinner. I couldn't figure out quickly how to simulate a no-tty environment.

Sadly this doesn't seem to have fixed my issue 😢


Rephrase template documentation to be more clear about .gitea/template

Closes #27336

Well, that's really confusing. When I reviewed this PR, I still misunderstood the meaning of .gitea/template and kept wondering why the files don't match glob rules are still included.

@lng2020 I can rephrase it if you have suggestions. I am struggling to figure out how to phrase it, and it was already hard to understand.

@lng2020 I can rephrase it if you have suggestions. I am struggling to figure out how to phrase it, and it was already hard to understand.

I mean the name .gitea/template itself and its usage are confusing. Your PR looks good to me.

Maybe we should explain "variable expansion" first? Otherwise it's easily ignored.


NF: option for silent screenshot on OS X

This option lets Mac users get a screenshot silently, without making the "click click" sound. I'm happy to add to the documentation if this looks ok as a feature. Non-silent remains the default (I personally would make silent the default).
Usage:
>>> pyautogui.screenshot(silent=True)

Merged this in, except I made silent the default only option (I don't really see a reason anyone would want that sound). Thanks Jeremy!


[FLINK-5804] [table] Add support for procTime non-partitioned OVER RA…

…NGE BETWEEN UNBOUNDED PRECEDING aggregation to SQL.
Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[×] General

The pull request references the related JIRA issue ("[FLINK-5804] Add [non-partitioned] processing time OVER RANGE BETWEEN UNBOUNDED PRECEDING aggregation to SQL")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[ ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[×] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

HI, @fhueske Thanks a lot for your review. I had updated the PR according to your comments.

Thanks for the update @sunjincheng121.
The PR looks good to merge.

merging


Can we relax the JWT dependency a bit?

Bundler could not find compatible versions for gem "jwt":
  In Gemfile:
    firebase_id_token was resolved to 2.3.0, which depends on
      jwt (>= 2.1.0, ~> 2.1)

    stream-ruby was resolved to 2.7.0, which depends on
      jwt (~> 1.5.2)

Sounds like a good idea; I created a branch and a PR for the upgrade (#90) let's see if all tests are happy. @ruggi


Add stream argument support to BaseplateSession

💸 TL;DR
Add stream argument support to pass it to BaseplateSession.send()
✅ Checks

[x] CI tests (if present) are passing
[x] Adheres to code style for repo
[ ] Contributor License Agreement (CLA) completed if not a Reddit employee

Hey Andrii! Thanks for this contribution! Would you mind sharing a bit more how you intend on using this as well as some more pydoc for the function so folks know how to use it?
For reviewers, that kwarg translates to this

Hey Nathan! I would like to partially read the response content using ExternalRequestsClient. I have to pass stream=True to achieve it, but this argument is not propagated to the underlying session.send method.
Current pydoc refers to the requests.request page, which explains usage of stream argument. We just didn't support this argument in our wrapper.


Able to go above 20% in the Race Creator

The Race Creator will allow me to select a growth rate over 20% and allow me to save. Growth rates over 20% cost no points.

Whoops! had it 1 to 100% 😄 Thanks!


Old versions have disappeared

All of the older versions of my libraries have disappeared, leaving only the latest version:

https://registry.platformio.org/libraries/nomis/uuid-common/versions
https://registry.platformio.org/libraries/nomis/uuid-log/versions
https://registry.platformio.org/libraries/nomis/uuid-console/versions
https://registry.platformio.org/libraries/nomis/uuid-syslog/versions
https://registry.platformio.org/libraries/nomis/uuid-telnet/versions
https://registry.platformio.org/libraries/nomis/uuid-modbus/versions

This breaks all builds that happen to be using a previous version, and any attempts to build with an earlier version for debugging/bug fixing. What's the point of semantic versioning if you're going to unpublish all the older versions and break everything?
Library Manager: Installing nomis/uuid-log @ ^2.2.0
Error: Could not find the package with 'nomis/uuid-log @ ^2.2.0' requirements for your system 'linux_x86_64'

Sorry, this a known issue. We have already applied the actions to avoid similar issues in future.
See https://community.platformio.org/t/missing-packages-in-registry/39076/5

You've published a newer version of tool-scons yesterday and now the older version has gone missing:
Error: Could not find the package with 'platformio/tool-scons @ ~4.40400.0' requirements for your system 'linux_x86_64'

v6.1.5 is not 2 years old, and #4531 hasn't been fixed yet

Is this going to be republished or not?
I don't like that you're making all the older versions of my projects impossible to build, especially when they can only be built with older versions of PlatformIO because of all the incompatible changes in v4, v5, v6.

I have to use "ancient buggy releases" because the bugs don't affect me and they're the versions that work, whereas newer versions have different incompatibilities.
I can't upgrade because of platformio/platformio-core#4884 which I'm only now aware of because I had to downgrade to v6.1.5 when v6.1.6 came out for platformio/platformio-core#4531.

Could not find the package with 'platformio/tool-scons @ ~4.40400.0'

This version is reverted to the registry. Please re-test your project with the latest PlatformIO Core 6.1.x and report all issues. We work on the PlatormIO Core 7.0 and there will be no support for 6.x soon.


Determine workspace location in execution engine

For incremental units of work such as tasks and project-bound artifact transforms we have an identity (basically the location of the workspace for the work) and a cache key (that is a unique identifier for the outputs). For this reason we have UnitOfWork.getIdentity(). This works well for tasks, because getIdentity() is trivial to calculate early in the execution, while calculating the cache key requires input snapshots, so it happens later, when such snapshots are available (and only if needed). For project-bound transforms the situation is fairly similar, though the calculation of the identity is a bit more complicated.
This doesn't work so well for non-incremental (=immutable) work, though. Such work include global artifact transforms and the different parts of Kotlin script compilation. For these work items identity is the cache key.
This means that for now we need to pre-calculate the identity/cache key before invoking the execution engine (and then just expose the cache key as a single input to the execution engine). This means that we miss out on the features provided by the execution engine to snapshot inputs and calculate the cache key (i.e. we need to duplicate the code), and the work we do outside the execution engine will not be captured in build operations.
We can improve this by introducing the concept of the workspace to the execution engine. A good representation of what we need to do is to show how the pipeline would need to change:
 return new DefaultWorkExecutor<>(
       new LoadExecutionStateStep<>(
       new MarkSnapshottingInputsStartedStep<>(
       new SkipEmptyWorkStep<>(
       new ValidateStep<>(validationWarningReporter,
+      CaptureInputsBeforeExecutionStep(/* ... */,
-      new CaptureStateBeforeExecutionStep(buildOperationExecutor, classLoaderHierarchyHasher, valueSnapshotter, overlappingOutputDetector,
       new ResolveCachingStateStep(buildCacheController, buildScanPlugin.isBuildScanPluginApplied(),
+      DetermineWorkspaceLocationStep(/* ... */,
+      CaptureOutputsBeforeExecutionStep(/* ... */,
       new MarkSnapshottingInputsFinishedStep<>(
       // ...

Meaning that we'd need to break up CaptureStateBeforeExecutionStep into two separate steps: one capturing inputs, the other the outputs. This works because we have the following dependencies:
  input snapshots      (provided by CaptureInputsBeforeExecutionStep)
    ^
    |
  cache key            (provided by ResolveCachingStateStep)
    ^
    |
  workspace location   (provided by DetermineWorkspaceLocationStep)
    ^
    |
  output snapshots     (provided by CaptureOutputsBeforeExecutionStep)

Note that for tasks we don't currently need to determine a workspace location. However, we have a plan for Gradle to auto-configure task output locations, in which case a workspace provider for tasks would make sense.
Moreover, having a Workspace abstraction could work to collect all output properties of any unit of work, including tasks.

cc: @gradle/build-cache, @eskatos

The problem here is that the first step - LoadExecutionStateStep - also depends on the identity of the work.

Good point.
It seems that we need to differentiate between incremental work (that requires an execution history, and an identity different from the cache key), and non-incremental/immutable work (that doesn't require an execution history, or an identity separate from the cache key). Both of these types of work could make use of a workspace determined as described above.
We can have two different pipelines for this, the immutable one having none of the stale file cleanup etc. steps required for the incremental one. We could get away without snapshotting the outputs for immutable work at all.

If the immutable work is not up-to-date, we need to clean up the workspace. For determining whether it is up-to-date, we need the input snapshots and can use those to determine the workspace/identity. And then we would load the execution history so we can check if the last execution succeeded and nobody messed with the outputs.

Right. What I'm suggesting is we can also drop the up-to-date check on the immutable workspace, and replace it with existence check. This could work well if we made these cache directories atomic by moving the results into the directory.
We don't check the integrity of our other caches AFAIK. We could make the integrity check a switch to enable if the user wants more strictness in their workflow. Either way we could have a mode where immutable work output is never snapshotted.
Not sure how useful this is, as most immutable work is used in the same build in some downstream work unit, so... And we are planning to include output hashes in the cached artifact, which means we'd need to snapshot the outputs that we want to store anyway, so...
Okay, probably not worth trying to optimize this out.

FTR, I just talked with @britter and Maven caching snapshots their outputs because of the cache store use case.

For determining whether it is up-to-date, we need the input snapshots and can use those to determine the workspace/identity. And then we would load the execution history so we can check if the last execution succeeded and nobody messed with the outputs.

I'm not sure what you are suggesting here, but if you are proposing to move the loading of the current state to later in the pipeline, then that's not trivial. We'd either need to break up SkipEmptyWorkStep to determine early if we can skip things, and then clean things up once the previous outputs are loaded. Or we need to move it to later in the pipeline.
The latter will make projects that apply language plugins they don't use (such as the build-tool itself) somewhat slower to execute. Maybe we can re-evaluate the regression when we had the discussion about the role of fully up-to-date performance tests.
In any case, SkipEmptyWorkStep should come later in the pipeline, at least after ValidateStep, so we learn about problems with the configuration of empty tasks, too. Doing this will probably break some builds, so we need to be careful.
At best we could move SkipEmptyWorkStep after CaptureInputsBeforeExecutionStep, and use the input snapshots to determine emptiness. This would slow things down even more, but again, maybe that's an acceptable regression.


Pechakucha

[ ] First day of TD when it rained
[ ] Friends visited
[ ] Food
[ ] Dinning hall
[ ] Beach
[ ] dinner time
[ ] Study lounge
[ ] Soccer field

great start! how will this expand to 20 images?


Clarify Project Status

Would it be possible to add a visible notice on the project's front page (or at least CONTRIBUTING.md) that no new features are being accepted? It's a bit discouraging for community contributors to spend the time trying to help, only to get rejected.
Examples:
https://github.com/docker/machine/pull/4287#issuecomment-338842549
https://github.com/docker/machine/pull/4280#issuecomment-338842944
https://github.com/docker/machine/pull/4254#issuecomment-338843050

See #4537


unable to update review

@micnncim I am also seeing another issue on another repo:

The action worked on this repository yesterday, when it updated this PR:
https://github.com/sdras/awesome-actions/pull/231
Any ideas on what might have changed here?

Oh sorry! I'll trace the cause and fix the bug.

lgtm


e2e: pr warning testTue, 25 Jul 2017 12:39:10 GMT

:warning: Validation status: warnings

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:warning:Warning
View
Details

E2E_DocsBranch_Dynamic/index.md

Line 2: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 3: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 4: [Warning] Invalid file link:(~/../nonexisted3.md).

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


Added support for fedora 2 FOXML files.

Resolves https://jira.duraspace.org/browse/FCREPO-1596

Hi @mikedurbin, I wanted to give you an update on our work with the Fedora 2 supporting version of the migration-utils. I'm still having trouble getting it to work -- though with an hour of a developer's time today I got somewhat further along, I'm still not quite there.   The latest issue is a "Content is not allowed in prolog" error when parsing the XML.  Either it is pointing at something that is not an XML file, or there is something about our XML that the parser doesn't like.  I probably need somebody with more debugging experience to have a look.  I'll keep you posted!
As an aid to testing, I was considering just exporting one single FOXML (Archive Context) and trying to get that to work first. Do you think I should be able to just use the fedora3-exported.xml migration configuration file with a Fedora 2 FOXML, or are there Fedora3-specific things happening there?

Resolved with:
https://github.com/fcrepo4-labs/migration-utils/commit/2f1f3e51573c398e180ce70f8001fb78955ef106 and
https://github.com/fcrepo4-labs/migration-utils/commit/ea3b76e8211978b46aac25acf6125614c9aefc5d


Add i18n thai language

We've now added Thai translations internally, and it should release later this week! We'll update this repo's package when that happens.


Remove heroku and add K8s

Removed all Heroku references
Added the 2 new k8s conditions:
Added K8s resource documentation

I've created a task for Denis to review the texts. Please make sure he does before publishing https://app.clickup.com/t/860pday36

@denisvitchevsky I'd appreciate your review here, thanks


WIP: Reenable test/AutolinkExtract/import_archive.swift

Verify that the failure is reproducible here. (It seems to have passed for me.)
This test was disabled: https://github.com/apple/swift/pull/14677
See rdar://problem/37605557.

@swift-ci please test linux platform

@swift-ci please smoke test OS X platform

I didn't reproduce this either with my usual Release+Asserts Linux build, so I'm going to say we should just turn this back on and see if the test fails again.

Did it get turned back on?


decrease prominence of author info in ui

yo! saw this repo and thought the interface looked slick!
here's a quick pr to tweak the commit info, which is less important than the overall commit hash & message.
attached is what things look like post tweak. feels a bit better wrt spacing imo :) middle commit also has a lil quick test to see what a longer email would look like

Hey there! Thank you, I'd been meaning to do this—it does indeed look way cleaner.


switch to Ruff instead of flake8

Description
Recently Ruff has become very popular among also mainstream projects for:

much faster, they say 70x
integrate several other tools under one roof, such as isort or bandit

Use case
if you are fine with this change I am happy to send such PR for review... :rabbit:

Hey @Borda, thanks for the suggestion. This is something we've been meaning to do, feel free to open a PR.


type_info always returning same value

In trying to upgrade from libuv 1.40.0 and uvw 2.8.0 to libuv 1.43.0 and uvw 2.11.0 we ran into major breakage in some of our internal tests. We are building under gcc 9.3.1-2 (from devtoolset-9 on CentOS 7.9) but it seems __PRETTY_FUNCTION__ in type_info.hpp is always returning type as the function name, regardless of template parameters. As best I can tell __PRETTY_FUNCTION__ is being converted to __FUNCTION__. Forcing back to fake() appears to work, once corrected to introduce the proper template parameter in the call.
I'm not sufficiently well versed in the details of PRETTY__FUNCTION to start troubleshooting this. It seems to work from simple unit tests within uvw just calling type<>() directly, but not within our application. The end result is error events are emitted to listen callbacks and close events are emitted to error callbacks and all kinds of messes ensue.
If you have suggestions on how to minimally reproduce this, I'm open to ideas. Every time I try, it works, which makes me think it has to do with compiling a complex application in some way.

I'm sorry but I've no idea. I can look into it if you've a reproducible example. Otherwise, I can't help but throw at you random thoughts because, as you rightly noted, it works in uvw and only breaks when used in a project that I don't have access to. 🤷♂

Mystery solved; I tracked it down to g3log and went to open a ticket there and wouldn't you know it... https://github.com/KjellKod/g3log/pull/424
Sorry for the noise!

Oh, wow 😅 thanks for the quick turnaround.


Consideration: Undefined names don't throw statically

I am not sure if I missed it, but I think dynamic modules are a good place to argue against static errors for import { notdefined } from 'that-dynamic-module' and instead this could simply result in a local binding to the contextual undefined. Only for imports from dynamic module namespaces.
Why this makes sense semantically, it is similar to import * as namespace from 'that-dynamic-module'; const { notdefined } = namespace; but without the ability to do something like const { notdefined = fallback } = namespace; which would really complicate semantic code analysis.
Why this makes sense practically, well, it is a dynamic module.
Any thoughts?

Note that namespaces don't reflect undefined values, as Object.keys(namespace) will provide a list of exported names. If we allow importers to define what names are defined this means that Object.keys(namespace) is now dependent on who is importing this module and how they are importing it determining if namespace has a someNonExistingExport name.

So I was coming from a different notion that a dynamic module's declared name would be undefined until set. Which made me think of all names being undefined until declared and set. To me, this is abstractionally more sound and potentially non-breaking to the concrete concepts that reflect all non-ES modules currently interfacing with JavaScript, but I could be wrong.
Because I default to thinking on the abstract side (to a fault), I think more of this as a future feature of the JavaScript, which are Dynamic Modules that make it possible for people to use as a building block for completely novel ideas. This makes me hope that for some scenarios like prototyping and development, they would be able to leave names that import from a module if they comment out that particular export (assuming they also factor in for undefined of course). I could also extend this to hot reloading but I am probably not the best advocate for this whole can.

Seems irrelevant at this point


[next] update custom-abstraction.mdx to match new types.ts documentation/abstraction style

update this page: https://next.threlte.xyz/docs/learn/advanced/custom-abstractions
I don't know if we want people to think they have to use a types.ts file instead of typing things in the component. I think it's a good practice to separate types from the code that actually runs but it's not necessary in a general case.
I also think it might be a good idea to include information about doing something like this:
type WhateverComponentProps = Props<Group> & {
  // a more concrete example of putting props in here
}

and maybe add info about the second type argument to Props in cases where they want to pass more than just the ref through the children snippet.
Maybe we can use this file as an example of a custom component: https://github.com/threlte/threlte/blob/next/apps/docs/src/examples/extras/bake-shadows/spaceships/Spaceship.svelte
it doesn't showcase using the "Snippet" argument of Props though but maybe it can be used as a guide.
see #1161 for more details.

Done!


Rebase on tabulator-js?

Overview
Now tabulator-py core is around 100-150 lines of code and js-compatible so porting it to javascript to use here as read/write tabular data encapsulation could be a workable idea.

Based on tabulator architecture for now only for Python stack.


Hardcore Disconnects after death (when trying to resurrect)

Hey ZhengPeiRu,
It seems the hardcore mode is now working in the respect that if you die you cannot come back to life, the only issue is that if you try to do so it will disconnect you from the server.
Is this intended? I suppose it works but maybe just not being able to click the button might be better?
Thanks in advance

Yes, that is the intended behavior. Unfortunately the core does not have hooks required to disable to resurrection button, so this is the best solution I could come up with.


Airmiles: Doesn't work with airmiles

https://airmilescardlink.ca/link
or try this: https://airmilescardlink.ca/#enrolFormPosition

@YesTrustMe, that site is blocking paste functionality, and this extension is circumventing their blocking. Unfortunately, they are also listening for the keyboard shortcut for paste and interfering with paste that way as well. This extension does not event listeners for key presses, and therefore cannot undo that aspect of paste blocking. You are able to paste on their site, but either need to right click on the input field and then choose "Paste" or do so from the browser's "Edit" menu.


Use Token Modifier to set editorUnnecessaryCode.opacity through SemanticTokens API

When using the proposed Semantic Tokens API #86415 , I'd like to be able to use a Token Modifier to de-emphasize variable or function Token Types in the code open in the active editor that aren't being used.
From the Semantic Tokens API Documentation there doesn't seem to be a way to do this.
I'm proposing we have have a specific 'unnecessary' Token Modifier and then have a way to style  this with a semanticTokenStyleDefaults 'opacity' property setting.

Both semantic tokens and diagnostics are semantic code annotations, and they result in the color changing, but at this time the only API we have for setting this is via diagnostics that have the tag DiagnosticTag.Unnecessary.
I am not in favor of adding competing API that gives two distinct ways to achieve the same effect.
Diagnostics are established, and are used also for code fixes, which can participate on save, show lightbulbs, and a custom message. Also, diagnostics can show in the problem panel when a severity of at least warning is used.

@alexdima Thanks, I wasn't aware of the Diagnostics API as an alternative. In light of this, I'm happy to close this issue.


Lambda support for notification module

This PR provides the code necessary to run the notification module as a lambda. In order for adyen to call the lambda, you are required to spin up an API Gateway which invokes the lambda with the request from adyen.

This is the second part of the lambdarising work that we have been doing. Once this and #68 are merged, this will resolve #65. Please suggest any changes that you would like to see made to this PR.
Cheers!


Clear editor filters when opening a new empty project

We carryover filters from the previous editor state in internalLoadHeaderAsync which means if you call newEmptyProject from inside a tutorial, the toolbox filters are not cleared.
@abchatra can we take this as a patch fix for Minecraft? i think it will help the Prodigy Learning folks with the tutorial thing they're doing

Sounds good. Port to stable6.4 and bump


SETI-787: add gitleaks script into travis.yml file

Closing since we already did it with Github Actions


[Doc Improvement][Unfurl links in Teams using bot-SBS testing][2689511]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-botbuilder-linkunfurling.yml
89
28
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 648be0c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/sbs-botbuilder-linkunfurling.yml
:white_check_mark:Succeeded
View

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


Use Named Clients

Rewrite parts of setup to use Escendit.Extensions.Hosting.RabbitMQ packages
AMQP, Stream Protocols

Fixed with #65


Feature/flyway migrate

Introduces flyway to migrate future changes.
Currently no migrations except the baseline version "3"

Merge glitched and actually already happened.


added Heroku

NOTE:

Please fill out the template below

Did you read the instructions in the README?

Y

Have you read the instructions in CONTRIBUTING?

Y

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?

[I have taken inspiration from some youtube videos and then written it in my words]

Include more about Heroku(app launchers for example)
Correct typos

Okay..I'll correct them 😃
On Wed 4 Jul, 2018 5:05 pm Dhruv Apte<EMAIL_ADDRESS>wrote:

Include more about Heroku(app launchers for example)
Correct typos

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/the-ethan-hunt/first-timers-guide/pull/107#issuecomment-402452641,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae3EuqtRNhKcO2IaUHeLFyxmbHGPk6kdks5uDKiOgaJpZM4VBT8e
.

Merging this


fix(RHTAPBUGS-823): wait for Snapshot to succeed

Description

Add Eventually block when waiting for Snapshot to be marked as Succeeded when running integration tests in ephemeral environments
Deploying the Snapshot in the ephemeral environment and running the integration test pipelineRun can take a non-trivial amount of time

Issue ticket number and link
RHTAPBUGS-823
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e

CI on e2e-tests are blocked due to RHTAPBUGS-872

fix PR got merged, so hitting a retest now:
/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/lgtm


Chatflows node filters are too restrictive

For certain chatflows like minio and kubernetes:
We are searching for unique nodes which all need to match the same units.
This should be changed to be smart for example kubernetes you want all your masters to be on unique nodes, but your workers can be again on those nodes...

verified.


Use tauri-winres

Description
tauri-winres is way faster because it is using embed_resource and this also means it does not rely on rc.exe or windres.exe and ar.exe, making cross-compile possible.
(See https://github.com/Snowiiii/Pumpkin/issues/312#issuecomment-2483389125)

Testing

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings cargo clippy

Looks good to me.
Thanks @Commandcracker :D


SASS-2174 - Create CIS materials amount EOY page.

Description
Please include a brief summary of the change you've made and the issue that it fixes.
Add a link to the relevant story in Jira
SASS-2174
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[x]  Have you moved the task to “in review” on JIRA?
[x]  Have you checked to ensure all dependencies are up to date?
[x]  Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[x]  Have you run the tests?

[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of main?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[x]  Have you checked the PR Builder passes?

bootstrap-frontend-play-28 is at 5.23.0

hmrc-mongo-play-28 is at 0.63.0

uk.gov.hmrc.mongo: hmrc-mongo-play-28 is up to date. Version 0.63.0 is already the latest, isn't it?

bootstrap-frontend-play-28 cannot be updated beyond 5.20.0 at this point

bootstrap-frontend-play-28 cannot be updated beyond 5.20.0 at this point, thank you
uk.gov.hmrc.mongo: hmrc-mongo-play-28 is up to date. Version 0.63.0 is already the latest, isn't it?, it is showing o.62.0 in IntelliJ

I think you are looking at the wrong branch. The correct branch is: SASS-2174-hristo

Liz, are you sure you are running the right branch? Your comment about selecting no on the radio button works correctly. There are even tests for that.


[SEDONA-138] Fix ST_GeoHash for Flink to work

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the assoicated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-138. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?
Currently the ST_GeoHash function for Flink fails with EOFException. This PR fixes it.
How was this patch tested?
By running mvn test -pl flink locally. In addition, I ran the following query from a Flink application:
SELECT ST_GeoHash(ST_Point(0, 1), 5)

then got the following result.
+--------------------------------+
|                         EXPR$0 |
+--------------------------------+
|                          s00j8 |
+--------------------------------+

Did this PR include necessary documentation updates?

No, this PR does not affect any public API so no need to change the docs.

To be merged after this PR: https://github.com/apache/incubator-sedona/pull/647


The code of training the resnet or vgg?

Hello, thanks for sharing your great job! Can you provide the code of adversarially training the classical models, such as VGG, Resnet?

Thanks for your attention, the original adversarial training code maybe out-of-date, but you can visit robustness or easyrobust for adversarial training code.


manage errors for single and multiple files

I have an error regarding single file error, that when I see on the project that it not handled correctly. At this pull request, I have changed some logic regarding the errors handler. Please review it. Thanks :)

@JakeHartnell can u review this?

@JakeHartnell can you please review this? it's fix when we upload single image and when there is error message showing up, the messages keep stacking, this code fix the error message validation in my project.


Add github social  in footer

Feature idea.
Add github social  in footer and link with repo

Describe the solution you'd like

@MonalikaPatnaik

Hi @MonalikaPatnaik , I would like to work on this, kindly assign this to me.

@Kanchan253 look for another issue

Please assign me this issue under GSSoC-2023 I love to contribute to this issue.


Missing tests

There seem to be a couple of areas that we used to have tests for, but these seem to have been removed and not replaced with anything equivalent:

extension function
Boolean operators

Thanks for noticing, I've added these tests to the reference implementation in 14e8b75.


Add French Translation

hi @xmine64
I translated the app to French but I don't know how to submit/add it?
as I can't add it myself I give it to you so that you can integrate the translation !
I upload the file here: french translation.zip
It should therefore be added the folder -fr- to the following directory : MicaForEveryone/MicaForEveryone.UI/Strings/
Thank for your confirmation 👍

We need a document on translation guide.


Help Please

Idk how to dm on here. I'm fairly tech savvy not the best coder. I'm trying to help my girlfriends son mod gorilla tag on his quest 2. How do I patch the APk with these files? Thank you!

quest 2 mods dont exist


Float locale issues

Prometheus can only deal with floats written with a dot (2.20 in en_EN for example). However if a project is set to use ru_RU, floats are written with a comma.
<?php

setlocale(LC_NUMERIC, 'en_EN');
printf("%f\n", 2.22); // prints 2.220000 which is correct

setlocale(LC_NUMERIC, 'ru_RU');
printf("%f\n", 2.22); // prints 2,220000 which is not correct

This can be fixed dropping the locale to C and returning it back after stringifying. Symfony guys fixed it in the VarDumper component here https://github.com/symfony/symfony/pull/23575/files .
Of course a project can drop locale when rendering the metrics, but IMO this should be handled by the library.

It's not only when rendering.
The APC.php storage handler has a function histogramBucketValueKey that just converts the float to string for naming the buckets, which causes the bucket to not be updated if the float is rendered with comma.


duplicate entries in completion menu

Platform e.g. macOS
Terminal software Tabby
Describe the problem you are observing.
Steps to reproduce

type key
see duplicates
A side note here - I also cannot arrow down to get to the other menu items.

Screenshots/Screencaptures

/cc @elferherrera

I think the completer is repeating those entries

I think it does come from the completer. If you add a space after keybindings it gets you the unique values

agreed. I see the same thing.  how do we not show duplicates?

imho, the duplicates and sorting should be handled by the thing making the completions list (the implementer of that trait)

Might have a fix for this. Looking now

Found it. PR incoming

nice!


Adds matchGlob functionality & resolves <IP_ADDRESS> error inside Docker Compose

The underlying GCS client library now supports the matchGlob capability.
Syntax is outlined here
Because syntax is non-standard glob matching, customized filtering on gcs file paths had to be created in the get_file_list function.
PR also includes the requisite upgrade for the underlying google client.
Testing is provided for the internal unit tests as well as the external integration tests via the client.  All tests have been manually matched against the GCS responses, so they should represent real cloud performance despite their odd glob patterns.
Additionally, resolves #210 and possibly #82

@oittaa any updates on this?

Sorry, I've been a bit busy and haven't had really time to check this project, but I just added Python 3.12 support. Could you resolve the remaining conflicts and then I'll merge this?


linked data directories into /data

I tried to overcome the problem with the whole installation being copied into the volume.
To solve this I did:

start the application at build time for 60 seconds to get the initial data directories being created
added a script part to the entrypoint which check

if the asset in the data volume already exists
moves the asset to the data volume, if it does not already exist
deletes the 'container' asset in the application directory
creates a link for the asset in the application directory

This works for the following assets:

db_cloud
db_local
db_remote
etc
log
jre/lib/security/cacerts

Unfortunately the assets cert/ and extcmd/ as links give massive Java errors and prevent the application from starting.
Now also the bind mounts to host directories work :)
Please have a look
CU
Snorre

I was to fast - found some bugs in my scripts. I will do a new pull request, when I fixed them.


Various Windows optimizations

Hold onto mutexes instead of releasing and then immediately re-locking
Don't move in and out of state so often in read_done for TCP

:+1:


Investigate creation of a systemwide database for single sign-in

Vino to explore her tests of 2019 to cost work required to create central table of UserIDs

@Vino-S to test on her local and provide information


updating error when running powershell installer as root

PR Summary

Testing on Ubuntu, if the user is root, the $SUDO variable will be blank when attempting to execute the command 'sudo -v' on line 99. By checking if the EUID is not 0 will verify that the $SUDO variable was set above so that 'sudo -v' executes correctly as opposed to executing just '-v' which will throw an error as an unknown command.
PR Checklist

[ ] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Change is not breaking
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[ ] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

Just pushed the requested update

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: bjh7242 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@bjh7242 I made the other scripts consistent per @iSazonov 's request.

@bjh7242 My changes triggered the code complexity rules (code across multiple files) that mean you need to sign the CLA?  Would you mind signing?

So I'm getting this error right now. I'm about to be AFK for the next 12ish hours, but I'll check again tomorrow morning to see if there are still issues with the site

FYI, this [answer] explains what was going on.

@bjh7242 I have asked for help with CLA.  I'll get back to you when I get an answer.

@bjh7242 Thank you so much for reporting this. I just fixed the CLA system. Could you give it a try again?

Just signed it, let me know if you need anything else from me. Thanks!

@bjh7242  Thanks for your contribution.


Update plutus deps

To avoid fatal: reference is not a tree: 09433fe537a4ab57df19e70be309c48d832f6576
Created a PR to have hydra the CI build stuff for us.

Just trying to merge this branch in master rn

Just trying to merge this branch in master rn

Made it fast-forward and pushed a PR so you could get pre built stuff from Hydra. Feel free to merge / close.


Add LiteTimeoutBlockingWaitStrategy

Log4j 2 uses the TimeoutBlockingWaitStrategy as the default for its Async Loggers (see related issues https://github.com/LMAX-Exchange/disruptor/issues/138 and https://issues.apache.org/jira/browse/LOG4J2-1221 ).
Recent discussion on the Mechanical Sympathy mailing list suggested that some performance improvement may be possible under lower workloads where the consumer thread often falls asleep. In this scenario, if multiple producer threads get additional work they can cooperate in waking up the consumer. Before trying to wake up the consumer, they can first check if another producer has already started to wake up the consumer, and avoid taking the lock if this is the case. This is exactly what the LiteBlockingWaitStrategy does.
This pull request is to add a wait strategy that combines LiteBlockingWaitStrategy with TimeoutBlockingWaitStrategy.
Question: the LiteBlockingWaitStrategy javadoc says that "this wait strategy should be considered experimental as I have not full proved the correctness of the lock elision code". Is this still the case? It looks like the projectreactor.io project used to use this wait strategy. Did they ever give you feedback on any issues with this strategy?

I'll have a look at merging this later this week.  The LiteBlockingWaitStrategy should work, but I haven't been able to absolutely convince myself that it is correct.  It was based of an optimisation from the Rust implementation of the Disruptor.

Merged manually.


human-readable error message

When user try to enter more than one question with same email, he get this error. It needs to be human-readable

@l3r8yJ, yours

Now it looks like this

@l3r8yJ, take a look at this please

@Andrew-Sem should be fixed


Add support for negating equality conditions in query helper

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.11 :tada:

Comparison is base (b1c486e) 55.05% compared to head (9b073f1) 55.16%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##               main       #5      +/-   ##
============================================
+ Coverage     55.05%   55.16%   +0.11%
- Complexity      166      167       +1
============================================
  Files            12       12
  Lines           396      397       +1
============================================
+ Hits            218      219       +1
  Misses          178      178

Flag
Coverage Δ

unittests
55.16% <100.00%> (+0.11%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/Helper/QueryHelper.php
100.00% <100.00%> (ø)

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

@emulgeator @SajtiDH , I'm merging and releasing a minor version, please still review and ping me if you see any problems

postmortem reviewed :)


Uncaught TypeError: Cannot read property 'top' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 0.175.0
System: Mac OS X 10.10.2
Thrown From: minimap package, v3.3.3
Stack Trace
Uncaught TypeError: Cannot read property 'top' of undefined
At /Users/Buero/.atom/packages/minimap/lib/minimap-view.coffee:353

TypeError: Cannot read property 'top' of undefined
  at MinimapView.module.exports.MinimapView.updateScrollY (/Users/Buero/.atom/packages/minimap/lib/minimap-view.coffee:353:64)
  at MinimapView.updateScrollY (/Users/Buero/.atom/packages/minimap/lib/minimap-view.coffee:1:1)
  at MinimapView.module.exports.MinimapView.updateScroll (/Users/Buero/.atom/packages/minimap/lib/minimap-view.coffee:368:6)
  at MinimapView.updateScroll (/Users/Buero/.atom/packages/minimap/lib/minimap-view.coffee:1:1)
  at /Users/Buero/.atom/packages/minimap/lib/minimap-view.coffee:268:8

Commands

Config
{
  "core": {
    "disabledPackages": [
      "linter-csslint",
      "linter-less",
      "linter"
    ],
    "themes": [
      "atom-dark-ui",
      "monokai"
    ]
  }
}

Installed Packages
# User
No installed packages

# Dev
No dev packages

/cc @atom/core

Please see #195


[BUG] Lidl Melinera LED String Lights HG06467 website does not match code

Bug? Lidl Melinera LED String Lights HG06467 website does not match code:
https://zigbee.blakadder.com/Lidl_HG06467.html
https://github.com/blakadder/zigbee/blob/master/_zigbee/Lidl_HG06467.md
Code is correct that only z2m is compatible today.
ZHA and Tasmota are not yet compatible with this device.

have you tested it with ZHA or Tasmota?

@blakadder I do not own it myself but other many ZHA users (and developers) report it does not work with ZHA yet, see:
https://github.com/zigpy/zha-device-handlers/issues/604
https://community.home-assistant.io/t/lidl-has-released-a-bunch-of-inexpensive-zigbee-3-0-certified-smart-devices/248825/16
https://community.home-assistant.io/t/silvercrest-lidl-smarthome/243561/123
As you can read and link to Zigbee2MQTT and deCONZ development discussions it is a very non-standard device and it it is designed it will not work by default with any Zigbee solution before some development work has been done.
So the same goes for Tasmota2Zigbee where it is not supported yet either:
https://github.com/arendst/Tasmota/issues/9051
It will however soon work in an upcoming deCONZ version as the development work has been done there. See:
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3716
Summery and conclusion; So far it is only supported in the very latest Zigbee2MQTT, however even in it they say it is still buggy:
https://github.com/Koenkk/zigbee-herdsman-converters/issues?q=HG06467

Just to clarify; it is not supported by Tasmota either as of yet, see https://github.com/arendst/Tasmota/issues/9051
It is only supported by Zigbee2MQTT.
deCONZ support is however in the pipeline.

That issue is not relevant to this discussion

For a device that can adjust colors and has multiple scenes, I wouldn't define the ability to switch it on and off as "working". I bought it and am willing to assist in making it compatible with tasmota, but the low level commands through my sonoff zigbee bridge are giving me a headache..


AttributeError: Can't pickle local object 'train..'

D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\python.exe train.py --config configs/gnt_llff.txt --train_scenes fern --eval_scenes fern
Setting up [LPIPS] perceptual loss: trunk [alex], v[0.1], spatial [off]
D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torchvision\models_utils.py:208: UserWarning: The parameter 'pretrained' is deprecated since 0.13 and may be removed in the future, please use 'weights' in
stead.
warnings.warn(
D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torchvision\models_utils.py:223: UserWarning: Arguments other than a weight enum or None for 'weights' are deprecated since 0.13 and may be removed in th
e future. The current behavior is equivalent to passing weights=AlexNet_Weights.IMAGENET1K_V1. You can also use weights=AlexNet_Weights.DEFAULT to get the most up-to-date weights.
warnings.warn(msg)
Loading model from: D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\lpips\weights\v0.1\alex.pth
Setting up [LPIPS] perceptual loss: trunk [vgg], v[0.1], spatial [off]
D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torchvision\models_utils.py:223: UserWarning: Arguments other than a weight enum or None for 'weights' are deprecated since 0.13 and may be removed in th
e future. The current behavior is equivalent to passing weights=VGG16_Weights.IMAGENET1K_V1. You can also use weights=VGG16_Weights.DEFAULT to get the most up-to-date weights.
warnings.warn(msg)
Loading model from: D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\lpips\weights\v0.1\vgg.pth
outputs will be saved to ./out\gnt_llff
training dataset: llff_test
loading ['fern'] for train
loading ['fern'] for validation
No ckpts found, training from scratch...
Traceback (most recent call last):
File "D:\code\3D_Reconstruction\GNT\train.py", line 319, in
train(args)
File "D:\code\3D_Reconstruction\GNT\train.py", line 97, in train
for train_data in train_loader:
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\utils\data\dataloader.py", line 441, in iter
return self._get_iterator()
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\utils\data\dataloader.py", line 388, in _get_iterator
return _MultiProcessingDataLoaderIter(self)
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\utils\data\dataloader.py", line 1042, in init
w.start()
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\process.py", line 121, in start
self._popen = self._Popen(self)
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\context.py", line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\context.py", line 327, in _Popen
return Popen(process_obj)
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\popen_spawn_win32.py", line 93, in init
reduction.dump(process_obj, to_child)
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\reduction.py", line 60, in dump
ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 'train..'
PS D:\code\3D_Reconstruction\GNT> Setting up [LPIPS] perceptual loss: trunk [alex], v[0.1], spatial [off]
D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torchvision\models_utils.py:208: UserWarning: The parameter 'pretrained' is deprecated since 0.13 and may be removed in the future, please use 'weights' in
stead.
warnings.warn(
D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torchvision\models_utils.py:223: UserWarning: Arguments other than a weight enum or None for 'weights' are deprecated since 0.13 and may be removed in th
e future. The current behavior is equivalent to passing weights=AlexNet_Weights.IMAGENET1K_V1. You can also use weights=AlexNet_Weights.DEFAULT to get the most up-to-date weights.
warnings.warn(msg)
Loading model from: D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\lpips\weights\v0.1\alex.pth
Setting up [LPIPS] perceptual loss: trunk [vgg], v[0.1], spatial [off]
D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\torchvision\models_utils.py:223: UserWarning: Arguments other than a weight enum or None for 'weights' are deprecated since 0.13 and may be removed in th
e future. The current behavior is equivalent to passing weights=VGG16_Weights.IMAGENET1K_V1. You can also use weights=VGG16_Weights.DEFAULT to get the most up-to-date weights.
warnings.warn(msg)
Loading model from: D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\site-packages\lpips\weights\v0.1\vgg.pth
Traceback (most recent call last):
File "", line 1, in
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 116, in spawn_main
exitcode = _main(fd, parent_sentinel)
File "D:\Users\gracejwang\AppData\Local\Programs\Python\Python39\lib\multiprocessing\spawn.py", line 126, in _main
self = reduction.pickle.load(from_parent)
EOFError: Ran out of input

set num_workers=0


Add thirstyice/Olimex16x2

Also fix my alphabetization error from last time I submitted

❌ ERROR: Arduino Lint found errors with https://github.com/thirstyice/Olimex16x2:
Linting library in Olimex16x2
ERROR: Library name Olimex16x2 not found in the Library Manager index. Library names are not allowed to change after
       being added to the index.
       See: https://github.com/arduino/library-registry/blob/main/FAQ.md#how-can-i-change-a-librarys-name
       (Rule LP018)

Of course it's not found, this is me adding it?

WARNING: No license file found.
See:
https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
(Rule LD002)

Fixed

WARNING: No example sketches found. Please provide examples.
See: https://arduino.github.io/arduino-cli/latest/library-specification/#library-examples
(Rule LD004)

Fixed

Will do


Dex Implementation Tracking Issue

[ ] Composition of AMMs (for routing)
[x] Implement Path type for routing
[x] Design indices for liquidity positions
[ ] Implement routing
[ ] Implement execution
[ ] Implement arbitrage
[ ] Implement liquidity management APIs
[ ] protocol.penumbra.zone documentation

Future work

[x] #1942
[x] #1950

Reference: Dex planning document

Replacing by #1724

Deleting this issue because it contains no information that isn't tracked in the actual tracking issue and clutters search results, and bugs the automatic sub-issue <> tracking issue tracking of #1724


Abi memory

The embed cairo0 code has been transformed in abiEncode.ts and abiDecode.ts file to correspoding cairo1 version as well adopting the latest memory layout proposed for WARP.
Modals traits such as ByteAccessorTrait and DynamicArrayUtilTrait  has been added for bytes_access.cairo and dynamic_array_utils.cairo files. Some of the existing methods of the traits is still yet to be implemented though.
trait DynamicArrayUtilTrait {
    // WARP Memory Dynamic Arrays Utils
    fn dynamic_array_copy_felt(ref self: WarpMemory, to_loc: felt252, to_index: felt252, to_final_index: felt252, from_loc: felt252, from_index: felt252);
....
}

trait ByteAccessorTrait {
    fn byte256_at_index(base: u256, index: felt252) -> felt252;
   ....
}

After these traits methods implementation would be done then we remaining ts files inside cairoUtilFuncGen/abi folder needs to be transformed adopting the implemented trait and newer cairo1 changes.
will go in after #1045

The embed cairo0 code has been transformed in abiEncode.ts and abiDecode.ts file to correspoding cairo1 version as well adopting the latest memory layout proposed for WARP.
Modals traits such as ByteAccessorTrait and DynamicArrayUtilTrait  has been added for bytes_access.cairo and dynamic_array_utils.cairo files. Some of the existing methods of the traits is still yet to be implemented though.
trait DynamicArrayUtilTrait {
// WARP Memory Dynamic Arrays Utils
fn dynamic_array_copy_felt(ref self: WarpMemory, to_loc: felt252, to_index: felt252, to_final_index: felt252, from_loc: felt252, from_index: felt252);
....
}
trait ByteAccessorTrait {
fn byte256_at_index(base: u256, index: felt252) -> felt252;
....
}
After these traits methods implementation would be done then we remaining ts files inside cairoUtilFuncGen/abi folder needs to be transformed adopting the implemented trait and newer cairo1 changes.
will go in after https://github.com/NethermindEth/warp/pull/1045


paperless: provide a way to set PAPERLESS_SECRET_KEY safely

Describe the bug
The paperless module does not provide a way to safely set PAPERLESS_SECRET_KEY (i.e. in a way that does not end up in the nix store, at least I couldn't think of any). Since paperless also does not support reading the key from a file something like sops-nix can't be used.
To make matters worse, paperless defaults to a hard-coded and publicly known secret key (as documented in https://docs.paperless-ngx.com/configuration/#PAPERLESS_SECRET_KEY). That means the only options are to set the value directly in the nix config and have it exposed in the nix store or use the default, which makes paperless insecure to open to the internet.
Since the documentation of the NixOS module does not mention the PAPERLESS_SECRET_KEY at all I'd imagine there might be a few unknowingly unsafe instances out there.
This is my understanding from reading the docs. If this is not an issue because of something I missed please correct me.
Steps To Reproduce
Steps to reproduce the behavior:

setup paperless using the module
set PAPERLESS_SECRET_KEY
observe that it gets put into the systemd file directly

Expected behavior
Having some way to specify this secret safely.
Additional context
The best fix would be if paperless was able to read the secret from a file. There is a request to add that feature in https://github.com/paperless-ngx/paperless-ngx/discussions/614. Until then, it might be useful to address this issue in the NixOS module, if possible.
Notify maintainers

@erikarvstedt @Flakebi

Now that I thought about this a bit more I think I could use systemd's EnvironmentFile to load the secret safely (from sops-nix). That the "path of least resistance" is rather unsafe is still suboptimal though, in my opinion.

We could fail in prestart, if there is no secret key in the environment.
diff --git a/nixos/modules/services/misc/paperless.nix b/nixos/modules/services/misc/paperless.nix
index 9b8bd62809c5..fb5a427bbc79 100644
--- a/nixos/modules/services/misc/paperless.nix
+++ b/nixos/modules/services/misc/paperless.nix
@@ -252,6 +252,11 @@ in

           echo ${pkg.version} > "$versionFile"
         fi
+
+        if [ -z "$PAPERLESS_SECRET_KEY" ]; then
+          echo "Refusing to start without PAPERLESS_SECRET_KEY. See https://docs.paperless-ngx.com/configuration/#PAPERLESS_SECRET_KEY."
+          exit 1
+        fi
       ''
       + optionalString (cfg.passwordFile != null) ''
         export PAPERLESS_ADMIN_USER="''${PAPERLESS_ADMIN_USER:-admin}"

Note: I started a discussion upstream about this, since I feel like paperless should enforce a randomized secret in any case (even when in local network). See https://github.com/paperless-ngx/paperless-ngx/discussions/4386.

Why not provide a secretKeyFile attribute similar to services.paperless.passwordFile?

I support this. It could be a mandatory option (or at least show a warning if unset) that explains the issue in its description. As far as I understand it, it is more or less safe to change the secret key even for existing instances. This would just invalidate everything that is signed using the secret key, so e.g. existing user sessions get logged out.

The way that I handle this typically is to create a file on disk during the first startup and then use an exported environment variable every time.

This is the solution, that should be implemented. It fixes the situation for everyone and makes it an implementation detail, not another pointless setting.

I think it is possible to set PAPERLESS_SECRET_KEY_FILE (see https://github.com/paperless-ngx/paperless-ngx/pull/1034)

I think it is possible to set PAPERLESS_SECRET_KEY_FILE (see paperless-ngx/paperless-ngx#1034) if our package uses the docker-entrypoint.sh.

I did not double check, but I strongly assume that the nix package is not using the docker entrypoint script. paperless-ngx is a "standard" buildPythonApplication without any reference to docker. See: https://github.com/NixOS/nixpkgs/blob/ca012a02bf8327be9e488546faecae5e05d7d749/pkgs/applications/office/paperless-ngx/default.nix#L88


Refine OSS-Fuzz set up and documentation

Make it more clear how to build oss-fuzz images depending on what's the use case (trying out, developing post processing, developing compiler extension).

@AdamKorcz does this make it easier in terms of what to do when developing in the post processing part?


Exception "raise Empty” starting server for new repo

I decided to try Seagoat on a different repo, a smaller one. (The other server process was not running anymore.) This time it failed immediately with two exceptions.
$  seagoat-server start ~/Projects/xxxxxx
2023-09-24 11:12:56,738 Creating server...
2023-09-24 11:12:56,739 Starting worker thread...
2023-09-24 11:12:56,741 Serving on http://<IP_ADDRESS>:61607
2023-09-24 11:12:57,971 Checking repository for new changes
Exception in thread Thread-1 (_worker_function):
Traceback (most recent call last):
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 76, in _worker_function
    task = self._task_queue.get(timeout=1)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 179, in get
    raise Empty
_queue.Empty

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 1038, in _bootstrap_inner
    self.run()
  File<EMAIL_ADDRESS>line 975, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 81, in _worker_function
    self.handle_maintenance(context)
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/task_queue.py", line 50, in handle_maintenance
    remaining_chunks_to_analyze = context["seagoat_engine"].analyze_codebase(
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/engine.py", line 84, in analyze_codebase
    return self._create_vector_embeddings(minimum_chunks_to_analyze)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/engine.py", line 106, in _create_vector_embeddings
    for chunk in file.get_chunks():
                 ^^^^^^^^^^^^^^^^^
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/file.py", line 81, in get_chunks
    lines = self._get_file_lines()
            ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/file.py", line 36, in _get_file_lines
    for i, line in enumerate(source_code_file.read().splitlines())
                             ^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'charmap' codec can't decode byte 0x8e in position 510: character maps to <undefined>

What kind of operating system are you using, and what kind of character encodings are used for the files?
This could be either a new bug that comes from fixing a previous bug, or some unexpected scenario that we have not seen yet

oh, and by the way, does this happen in all repos, or just one specific one?

looking at this issue: https://github.com/kantord/SeaGOAT/issues/250 maybe you copied the same error message twice?

Nope, it logged both exceptions at the same time.

even in that case, in theory most encodings that are going to show up in any code repo should be supported :thinking:  so it might be that SeaGOAT is trying to read a file with the wrong encoding, even though the correct encoding should be supported

Nope, it logged both exceptions at the same time.

I'm not 200.00% sure but I think that the first part:
Exception in thread Thread-1 (_worker_function):
Traceback (most recent call last):
  File "/Users/snej/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 76, in _worker_function
    task = self._task_queue.get(timeout=1)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 179, in get
    raise Empty
_queue.Empty

should just be because it was the last thing in the queue :thinking:  or in any case, I am not sure that there is anything wrong wit the queue itself, as it seems like the error is really because of the encoding. feel free to reopen if the same error happens also without the encoding error being present


[connect] Charge/Invoice do not inherit from AccountRelatedStripeObject

Invoices and Charges do not inherit from AccountRelatedStripeObject, but only take the account into consideration for the stripe_invoice and stripe_charge properties (using the customer):
https://github.com/pinax/pinax-stripe/blob/fda68d45cbd68a67ca0be9f5cf6edb46dcf9edc1/pinax/stripe/models.py#L364-L372
https://github.com/pinax/pinax-stripe/blob/fda68d45cbd68a67ca0be9f5cf6edb46dcf9edc1/pinax/stripe/models.py#L297-L306
@lukeburden
Is there a reason for doing it like that?
Shouldn't they just derive from AccountRelatedStripeObject also?

It seemed overly redundant to me, as both Invoice and Charge models are already related to Customer, which is an AccountRelatedStripeObject.

Fixed in 0799022c.


Restore previously disabled dependency behaviour checks

These would have detected issue #1257 introduced in PR #1200.

This failed in one CI run with:
parsl/tests/test_python_apps/test_rand_fail.py .F.

E           RuntimeError: Expected DependencyError, but got no exception
parsl/tests/test_python_apps/test_rand_fail.py:115: RuntimeError

... I think this test has some chance of not causing dependency errors, because failure is deliberately random.
So actually test_rand_fail probably has no place in the test suite at all, and I will amend this PR to remove it rather than re-enable it.


Output generated setup.py to project folder.

Hi,
I found a case where I need to keep the setup.py on the root of my repo.
Sometimes changes are commited to repository, but not yet released to PyPI, specially for staging and dev branches one is able to do.
pip install http://github.com/myname/myrepo/tarball/master

The above is a common use case and pip looks for a setup.py to perform the installation.
I see that flit generates a setup.py and packages it on the sdist, I am using a script to extract it, but I wonder if a flit build --output or something like this is possible?

another idea is to allow callbacks/hooks

flit.ini
[post-hooks]
my_post_script:hook

So after flit [anything] that hook is executed receiving the current sys.args as parameter.

We're working on PEP 517, which will allow pip to install from a source directory or URL without needing setup.py.
I'm against adding setup.py into repositories using flit: it either contains duplicate information which can get outdated, or it can't do everything people will want to do with it, or it involves some ugly code I don't want to maintain to integrate flit and setuptools.
In the meantime, you can of course do what you're doing and use the setup.py from an sdist. But it's not something I'm going to encourage by providing any easier way to do it.
You might also want to look at pbr - that's another packaging effort which tries to extend setuptools rather than avoiding it like flit does.


Result of predict is only "NaN"

Hi,
When I run a script after trained,  all of Sharpe Ratio =  0
and predict all value = nan
Please advice me.

solved my problem is NAN/missing value in data set

solved my problem is NAN/missing value in data set


When I run modeling_test.py, I get the error "Tensor.name is meaningless when eager execution is enabled."

Hi, I'm trying to set up a simple Bert model to play around with.  However, when I run modeling_test.py, the test "BertModelTest.test_defualt" fails and I get the error "Tensor.name is meaningless when eager execution is enabled."  Is there a way to fix this?  Thanks in advance.

2019년 11월 8일 (금) 오전 1:46, mkuoch<EMAIL_ADDRESS>작성:

Hi, I'm trying to set up a simple Bert model just to play around with.
However, when I run modeling_test.py, the test "BertModelTest.test_defualt"
fails and I get the error "Tensor.name is meaningless when eager execution
is enabled." Is there a way to fix this? Thanks in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google-research/bert/issues/905?email_source=notifications&email_token=AMDX7AVOF2AX2GRZAJRJOOLQSRA5VA5CNFSM4JKJZQJ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HXVF6TA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMDX7AWTGGMFZ2IP5ZGPLW3QSRA5VANCNFSM4JKJZQJQ
.

Do you use TF 2.0? You need to disable eager behavior. https://www.tensorflow.org/api_docs/python/tf/compat/v1/disable_v2_behavior?hl=en


Is this examples page any good?

I've made a new page of code snippets examples. Nearly tried to merge it back onto the google docsy project. Doh!

I will assign reviewers using the @British-Oceanographic-Data-Centre/wcssp grouping

Reviewed it myself! Probably not best practise but I want to see if it works.


A bit of errors

1. invalid get index 'UNARMED' (on base 'Dictionary')
error when pressing R without ammo
2.  dependencies error
res://Sonniss_GDC_Game_Audio/Gamemaster_audio_gun_sound_pack/gun_revolver_pistol_shot_04_edited.ogg
3. Poor performance on fairly powerful devices
40 fps but very strong freezes
4. In the test scene, the cubes after going into a steady state do not move the player until they are shot (can be interacted after shot)
Disable "Can sleep" in cubes RigidBodies
5. the change in gravity during a sprint affects the height of the jump

Thanks Soarex16! I'll look into fixing these soon!

disabling GI_probes does not help
Regarding acceleration - no, this is not the best idea, because you can lock the shift only in order to jump higher

Hmm... I'll see if I can nail down the performance issue.
(and I'll remove the extra jump height when sprinting :+1: )

Fixed all but number 3 in the most recent commit: be35009c8d5d1b750360b85b23a306b418a84ae0
(probably should have made a pull request instead of directly pushing the changes... Oh well!)
I tried fixing the performance drops in Test_level.tscn but I couldn't find a solution. I think the problem is due to how many static collision shapes there are, but I have not been able to confirm this. I will open a new issue for this matter.
Thanks!


Add email validation scoping

For multi tenancy the email validation scoping is
crucial. This enhancement is actually based on the
currently open PR:
https://github.com/plataformatec/devise/pull/5094
As soon as the feature is merged, one should use the
Devise trunk again.

Isn't this a duplication of #5049?


doc: adds grafana cloud instructions

Fixes #63

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[WIP]implement IO Throttling or QoS

What this PR does / why we need it:
Special notes for your reviewer:
Does this PR introduce a user-facing change?

implement IO Throttling or QoS

Codecov Report

Merging #803 (892c4b5) into main (404d080) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #803   +/-   ##
=======================================
  Coverage   29.49%   29.49%
=======================================
  Files          25       25
  Lines        1614     1614
=======================================
  Hits          476      476
  Misses       1073     1073
  Partials       65       65

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

can we add documents about QoS :)


Add optional policy parameter for vulnerabilities older than N days

fixes #149
cc @nurmi
Let me know how this looks, and what other changes would need to be made for it to be included. How are tests handled for policy filters like this? Does the cli need to be updated to include the creation date in vulnerability output?

Thanks @emaildanwilson ! We'll take a look at comment here!

Any chance someone could take a look this week?

hello!
We’re finishing up some feature work, and you’ll see some flurry of work in the next couple of weeks as we gear up for the next oss engine release - your pr is on the list for adressing for that next release - stay tuned and appreciate your patience!

I think the primary question is the semantics you're trying to achieve. The created_at timestamp on vulnerability records in anchore is when the db entry was created, not when the vulnerability was created in in the upstream source. So, for example, none of the created_at timestamps will be older than the anchore deployment date itself. Is that what you're expecting?

Yes, given that some of the sources do not contain a discovery date it seems like it's the best we can do right now. Aside from the caveat of the installation being brand new or the local scan database getting deleted/recreated, the created_at date should match the discovery date within the polling period. Using the created_at date for feeds where the discovery date is not available might create even more confusion. I'm open to ideas if there are ways we could make this better.

Ack, just wanted to make sure the semantics were understood and acceptable. I tend to agree that there isn't a cleaner way to do it in this case given the diversity of input data.

Thanks! Much appreciated, this is a super-useful feature.


pp asyn await

Is this a bug report?
(write your answer here)

Have you read the Contributing Guidelines?
(Write your answer here.)
Environment

react-native -v:
node -v:
npm -v:
yarn --version:

Then, specify:

Target Platform:

Development Operating System:

Build tools:

Steps to Reproduce

(Write your steps here:)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Sorry, believe it or not but it was a cat on my keyboard, while reading one of the issues and searching for async await stuff  ...


Dscs 457

algorithm field for copy and  support for carriers having a default algorithm, @shuangzhou , @terenceingram could you please have a look.

Looks good apart from above comments.

Thanks Shuang, I have made suggested changes, please have a look.

Looks fine to me, might be good to have a unit test to illustrate how CarrierAlgorithm will be accessed and validated.  Good work.


Feeds not always showing in expanded folders

App Store Connect report: “just noticing that certain folders are not showing the feeds from within - usually toggling it a few times will fix it and there really isn’t a any rhyme or reason to it - ios latest - iphone 8”

Clearly the user has encountered a bug here. I just have no idea how to track it down. I've never seen this happen before and we don't have important information like what kind of account it is and if the filter is active. "there really isn’t any rhyme or reason to it" isn't very helpful.
I don't know what we can do until we a better bug report about this issue.

Moving this out of the milestone. Hopefully we can get more info. Or it was a fluke and it won’t happen again.

Moving this out of the milestone. Hopefully we can get more info. Or it was a fluke and it won’t happen again.

@brentsimmons I don't think was a fluke, I'm able to reproduce it and now I get how to, because it happened several times with my use of NNW on iOS.
iOS version : 14.6
NNW version : 6.0 (Build 604)
Here's a video that shows how to reproduce the behavior.
https://user-images.githubusercontent.com/72861758/121100634-8d38e680-c7fa-11eb-8c96-025b32aa52d6.MOV
I didn't try on macOS yet.

This is fixed and will be in the upcoming 1.1 iOS release. cc @jaanus


Compiling fails with segfault

Compiling libhermit-rs currently fails with a segmentation fault. This behaviour was introduced with the nightly-2020-08-24. This is likely to be related to the following issue: https://github.com/rust-lang/rust/issues/75922.
The comments there suggest that we will have to make changes on our end to the #[naked] functions.

Yes! Hm, I also create an issue rust-lang/rust#76061. I will look into rust-lang/rust#75922.

I had a similar issue with naked functions recently (though this were runtime issues), where naked functions with parameters behaved weirdly. https://github.com/rust-lang/rust/pull/75417 fixed some of that, but people are unsure if naked+parameters should be supported or not. My workaround was using global_asm! and declaring the symbol as a extern 'C' fn.

Yes, seems to be the better solution

I close this issue. PR #95 solved it.


Added factorial using recursion

#176  Added factorial using recursion.

Fixed issues #171 & #172

Sorry for the inconvenience, as I'm new to the open source world, I made a lot of commits here.
Issue #176 solved


Update Arbitrum, BSC and BSC Testnet names and aliases

Updates the names & aliases for the following chains:

Arbitrum -> Arbitrum One
BSC -> BNB Smart Chain
BSC testnet -> BNB Smart Chain testnet

Happy to adjust any other chains - let me know
Closes: https://github.com/api3dao/chains/issues/63

Discussed privately in Slack - only updating the names of the 3 chains


Strange behavior of read_parquet when multiple big partitions are involved

Hello,
I am working with a large (very large that even only a small portion [2 partitions] does not fit in an entire single server) dataset which is saved on disk with 30 parquet partitions. Each partition weights 7GB, but when loaded in memory and decompressed the size of a single partition is about 250-300GB.
Now, base on Best Practices and usual workflows I decided to read the parquet folder and launch a repartition, to split the data in smaller chucks, taking only the required columns. During this process I experienced a behavior that, to the best of my knowledge should not happen, as dask should understand how to load partition in memory by itself.
What happened:
In reality, if I read the folder, dask always read multiple partitions at once. To fix this behavior I tried:

1 thread only
1 worker with full memory
pyarrow as read engine
fastparquet as read engine

Nothing works and read_parquet always read multiple files at once. I though then to wait some "restart worker" messages to give the scheduler time to understand how to better schedule the tasks, unfortunately no change (even when the number of trial is a lot higher than the default 3).
I then moved to something that is usually discouraged, working manually on single partitions, de facto mimicking
what actually the scheduler should do, at least with my current understanding. When providing a single partition of the parquet files dask behaves perfectly with the following steps:

read_parquet
drop_by_shallow
repartition
reset_index
to_parquet

Of course this is not ideal. This workflow will create multiple folders, with multiple parquet files and Dask by itself is not suited to read this structure, which will force us to create the DataFrame from_delayed, writing my own code to select the partitions in memory (there is nothing wrong with from_delayed, but my understanding is that when I can use dask collections APIs I should use them instead of custom delayed pandas read operation).
As this is not the first time that, when I use Dask, I experience some issues with very large partitions that are, in my experience, always loaded in memory concurrently, I have decided to submit an issue instead of a simple question.
Minimal Complete Verifiable Example:
Reproducing the behavior is quite hard as a lot of data a required. Below there are the 2 versions of code that I described above.
Single read_parquet:
import dask.dataframe as dd
from dask.distributed import Client

#tried all possible combinations
client = Client(n_workers=1, processes=True, memory_limit='500GB', interface = 'eth2')

npartitions = 1000

ddf = dd.read_parquet('data/raw_parquet/', gather_statistics = True, engine = 'pyarrow')

ddf = ddf.drop([columns], axis = 1)

ddf = ddf.repartition(npartitions=npartitions)
ddf.to_parquet(save_path, write_index = False)

Multiple read_parquet manually selecting partitions:
import dask.dataframe as dd
from dask.distributed import Client
import glob

client = Client(n_workers=45, processes=True, memory_limit='500GB', interface = 'eth2')

npartitions = 10

partitions = glob.glob('data/raw_parquet/*.parquet')

for partition in partitions:
        ddf = dd.read_parquet(partition, gather_statistics = True, engine = 'pyarrow')

        ddf = ddf.drop([columns], axis = 1)

        ddf = ddf.repartition(npartitions=npartitions)
        ddf.to_parquet(save_path+partition_name, write_index = False)

With the second method, I can see that Dask actually launches multiple read_parquet on that single partition, reading I guess different part of the partition.
Anything else we need to know?:
Tested on a AWS EC2 m5.24xlarge
Environment:
Thinking the environment was the problem, I tested on a brand new conda env with only dask installed.

Dask version: 2021.03.0
Python version: 3.7
Operating System: Red Hat 7.2.1-2
Install method (conda, pip, source): conda

I suspect that @martindurant will be able to advise. I suspect you might be interested in the chunksize option.

@muscionig are you still struggling with this problem?
@martindurant Do you have any advice?

I had completely forgotten about this issue, sorry.
Firstly, there is nothing that Dask ca do about the basic chunk size ("row-group" of a parquet file) of your data - it will be read into a single dataframe partition, which will typically be much larger than the on-disc representation, and extra memory will typically be used to create it.
In your case, you can handle one partition at a time, but no more, but you'd like to write it out into multiple pieces (as I understand). You method for doing this by hand is probably just fine, and you could manage the file locations after the fact - I don't particularly see a problem with this. You could achieve the same using dask's delayed mechanism, if you'd like Dask to handle scheduling.
To use Dask's own mthods, however, you'll want to limit the workers. You could use the single-threaded "sync" scheduler (nothing wrong with this, but writes won't parallelise), but maybe the best would be to run a single worker with a few threads, and assign worker resources to the read_parquet call, but not to the write call. If the worker has one resource, and read requires one, you should ensure that only one partition is read at a time. Ne ones might still get read while a previous one is being written.

Closing this as answered, but if you feel this is not the case, feel free to ping here and we can reopen


Added Meta Module Groovy Script

GCI TASK 2017
This adds the following functions:
groovyw metas get
Clones Meta Module  from MetaTerasology
groovyw metas create
Creates a new Meta Module  with a .gitignore in it

Can one of the admins please verify this patch?

I think its done...
Sorry for the issue of line ending....I'll resolve it next time.
Also, I did not add the remote 'origin' now....I'll do that later....
I think this is enough for this task...
Please Review.

Superseded / merged via #3263 - thanks! :-)


Closes #264

Closes #264
Checkbox

[ ] Confirm that this PR is linked to the dataset issue.
[ ] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[ ] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[ ] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[ ] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[ ] Confirm dataloader script works with datasets.load_dataset function.
[ ] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

script output:
# yuz @ null in ~/workspace/seacrowd-datahub on git:mysentence x [15:25:40] C:2
$ make check_file=seacrowd/sea_datasets/mysentence/mysentence.py
black --line-length 250 --target-version py38 seacrowd/sea_datasets/mysentence/mysentence.py
All done! ✨ 🍰 ✨
1 file left unchanged.
isort seacrowd/sea_datasets/mysentence/mysentence.py
flake8 seacrowd/sea_datasets/mysentence/mysentence.py --max-line-length 250
(ani)
# yuz @ null in ~/workspace/seacrowd-datahub on git:mysentence x [15:25:58]
$ python -m tests.test_seacrowd seacrowd/sea_datasets/mysentence/mysentence.py --subset_id mysentences
INFO:__main__:args: Namespace(path='seacrowd/sea_datasets/mysentence/mysentence.py', schema=None, subset_id='mysentences', data_dir=None, use_auth_token=None)
INFO:__main__:self.PATH: seacrowd/sea_datasets/mysentence/mysentence.py
INFO:__main__:self.SUBSET_ID: mysentences
INFO:__main__:self.SCHEMA: None
INFO:__main__:self.DATA_DIR: None
INFO:__main__:Checking for _SUPPORTED_TASKS ...
module seacrowd.sea_datasets.mysentence.mysentence
<module 'seacrowd.utils.schemas.seq_label' from '/Users/yuz/workspace/seacrowd-datahub/seacrowd/utils/schemas/seq_label.py'>
INFO:__main__:Found _SUPPORTED_TASKS=[<Tasks.POS_TAGGING: 'POS'>]
INFO:__main__:_SUPPORTED_TASKS implies _MAPPED_SCHEMAS={'SEQ_LABEL'}
INFO:__main__:schemas_to_check: {'SEQ_LABEL'}
INFO:__main__:Checking load_dataset with config name mysentences_source
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:2479: FutureWarning: 'use_auth_token' was deprecated in favor of 'token' in version 2.14.0 and will be removed in 3.0.0.
You can remove this warning by passing 'token=<use_auth_token>' instead.
  warnings.warn(
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:922: FutureWarning: The repository for mysentence contains custom code which must be executed to correctly load the dataset. You can inspect the repository content at seacrowd/sea_datasets/mysentence/mysentence.py
You can avoid this message in future by passing the argument `trust_remote_code=True`.
Passing `trust_remote_code=True` will be mandatory to load this dataset from the next major release of `datasets`.
  warnings.warn(
<module 'seacrowd.utils.schemas.seq_label' from '/Users/yuz/workspace/seacrowd-datahub/seacrowd/utils/schemas/seq_label.py'>
Generating train split: 40000 examples [00:01, 27495.17 examples/s]
Generating test split: 4712 examples [00:00, 29037.50 examples/s]
Generating validation split: 2414 examples [00:00, 29159.99 examples/s]
INFO:__main__:Checking load_dataset with config name mysentences_seacrowd_seq_label
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:2479: FutureWarning: 'use_auth_token' was deprecated in favor of 'token' in version 2.14.0 and will be removed in 3.0.0.
You can remove this warning by passing 'token=<use_auth_token>' instead.
  warnings.warn(
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:922: FutureWarning: The repository for mysentence contains custom code which must be executed to correctly load the dataset. You can inspect the repository content at seacrowd/sea_datasets/mysentence/mysentence.py
You can avoid this message in future by passing the argument `trust_remote_code=True`.
Passing `trust_remote_code=True` will be mandatory to load this dataset from the next major release of `datasets`.
  warnings.warn(
Generating train split: 40000 examples [00:01, 27806.30 examples/s]
Generating test split: 4712 examples [00:00, 26885.91 examples/s]
Generating validation split: 2414 examples [00:00, 29224.80 examples/s]
INFO:__main__:Dataset sample [source]
{'id': '0', 'tokens': ['ဘာ', 'ရယ်', 'လို့', 'တိတိကျကျ', 'ထောက်မပြ', 'နိုင်', 'ပေမဲ့', 'ပြဿနာ', 'တစ်', 'ခု', 'ခု', 'ရှိ', 'တယ်', 'နဲ့', 'တူ', 'တယ်'], 'labels': [0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 2, 2, 2, 3]}
INFO:__main__:Dataset sample [seacrowd_seq_label]
{'id': '0', 'tokens': ['ဘာ', 'ရယ်', 'လို့', 'တိတိကျကျ', 'ထောက်မပြ', 'နိုင်', 'ပေမဲ့', 'ပြဿနာ', 'တစ်', 'ခု', 'ခု', 'ရှိ', 'တယ်', 'နဲ့', 'တူ', 'တယ်'], 'labels': [0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 2, 2, 2, 3]}
INFO:__main__:Checking global ID uniqueness
INFO:__main__:Found 2414 unique IDs
INFO:__main__:Gathering schema statistics
INFO:__main__:Gathering schema statistics
train
==========
id: 40000
tokens: 543541
labels: 543541

test
==========
id: 4712
tokens: 63622
labels: 63622

validation
==========
id: 2414
tokens: 32315
labels: 32315

.
----------------------------------------------------------------------
Ran 1 test in 7.920s

OK
(ani)
# yuz @ null in ~/workspace/seacrowd-datahub on git:mysentence x [15:26:15]
$ python -m tests.test_seacrowd seacrowd/sea_datasets/mysentence/mysentence.py --subset_id mysentences_para
INFO:__main__:args: Namespace(path='seacrowd/sea_datasets/mysentence/mysentence.py', schema=None, subset_id='mysentences_para', data_dir=None, use_auth_token=None)
INFO:__main__:self.PATH: seacrowd/sea_datasets/mysentence/mysentence.py
INFO:__main__:self.SUBSET_ID: mysentences_para
INFO:__main__:self.SCHEMA: None
INFO:__main__:self.DATA_DIR: None
INFO:__main__:Checking for _SUPPORTED_TASKS ...
module seacrowd.sea_datasets.mysentence.mysentence
<module 'seacrowd.utils.schemas.seq_label' from '/Users/yuz/workspace/seacrowd-datahub/seacrowd/utils/schemas/seq_label.py'>
INFO:__main__:Found _SUPPORTED_TASKS=[<Tasks.POS_TAGGING: 'POS'>]
INFO:__main__:_SUPPORTED_TASKS implies _MAPPED_SCHEMAS={'SEQ_LABEL'}
INFO:__main__:schemas_to_check: {'SEQ_LABEL'}
INFO:__main__:Checking load_dataset with config name mysentences_para_source
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:2479: FutureWarning: 'use_auth_token' was deprecated in favor of 'token' in version 2.14.0 and will be removed in 3.0.0.
You can remove this warning by passing 'token=<use_auth_token>' instead.
  warnings.warn(
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:922: FutureWarning: The repository for mysentence contains custom code which must be executed to correctly load the dataset. You can inspect the repository content at seacrowd/sea_datasets/mysentence/mysentence.py
You can avoid this message in future by passing the argument `trust_remote_code=True`.
Passing `trust_remote_code=True` will be mandatory to load this dataset from the next major release of `datasets`.
  warnings.warn(
<module 'seacrowd.utils.schemas.seq_label' from '/Users/yuz/workspace/seacrowd-datahub/seacrowd/utils/schemas/seq_label.py'>
Generating train split: 47002 examples [00:02, 23178.28 examples/s]
Generating test split: 5512 examples [00:00, 24106.80 examples/s]
Generating validation split: 3079 examples [00:00, 21768.96 examples/s]
INFO:__main__:Checking load_dataset with config name mysentences_para_seacrowd_seq_label
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:2479: FutureWarning: 'use_auth_token' was deprecated in favor of 'token' in version 2.14.0 and will be removed in 3.0.0.
You can remove this warning by passing 'token=<use_auth_token>' instead.
  warnings.warn(
/Users/yuz/anaconda3/envs/ani/lib/python3.10/site-packages/datasets/load.py:922: FutureWarning: The repository for mysentence contains custom code which must be executed to correctly load the dataset. You can inspect the repository content at seacrowd/sea_datasets/mysentence/mysentence.py
You can avoid this message in future by passing the argument `trust_remote_code=True`.
Passing `trust_remote_code=True` will be mandatory to load this dataset from the next major release of `datasets`.
  warnings.warn(
Generating train split: 47002 examples [00:02, 22890.47 examples/s]
Generating test split: 5512 examples [00:00, 24039.65 examples/s]
Generating validation split: 3079 examples [00:00, 21711.39 examples/s]
INFO:__main__:Dataset sample [source]
{'id': '0', 'tokens': ['နားလည်', 'ပါ', 'ပြီ'], 'labels': [0, 2, 3]}
INFO:__main__:Dataset sample [seacrowd_seq_label]
{'id': '0', 'tokens': ['နားလည်', 'ပါ', 'ပြီ'], 'labels': [0, 2, 3]}
INFO:__main__:Checking global ID uniqueness
INFO:__main__:Found 3079 unique IDs
INFO:__main__:Gathering schema statistics
INFO:__main__:Gathering schema statistics
train
==========
id: 47002
tokens: 834243
labels: 834243

test
==========
id: 5512
tokens: 96632
labels: 96632

validation
==========
id: 3079
tokens: 61782
labels: 61782

.
----------------------------------------------------------------------
Ran 1 test in 11.307s

OK