Support for non param-based queries

In the docs I see:

//query is parameterized by default

but I can't find where to turn it off. Is this possible?

It's not possible to turn it off, but you can use the toString method.
In this example
var sql = require('sql')

var user = sql.define({
  name: 'user',
  columns: ['id', 'name']
})

var query = user.select(user.star()).where(user.name.equals('aireater'));

console.log(query.toString());

it will return
SELECT "user".* FROM "user" WHERE ("user"."name" = 'aireater')

Just be carefull with SQL injections.

Just wanted to say kudos @brianc for making a query building library that correctly constructs SQL. Unbelievable that there are still people not doing this right today. Not one nodejs ORM gets it right. (Ref #320).

Haha thanks. :)
On Thursday, June 2, 2016, Greg Slepak<EMAIL_ADDRESS>wrote:

Just wanted to say kudos @brianc https://github.com/brianc for making a
query building library that correctly constructs SQL. Unbelievable that
there are still people not doing this right today. Not one nodejs ORM
gets it right. (Ref #320 https://github.com/brianc/node-sql/issues/320).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brianc/node-sql/issues/253#issuecomment-223459845,
or mute the thread
https://github.com/notifications/unsubscribe/AADDoZHDEC7OhRWSosh0XIfZ_bnqNUunks5qH3MIgaJpZM4FgvSo
.


Design advice: specifying data source for an autocomplete editor

Thanks for this library.
I’m making use of it in a project, and I extended Backbone.Form.editors.Base to create an Autocomplete editor that uses jQuery UI’s autocomplete. Usage example:
class Move extends Backbone.Model
  schema:
    person_id:
      title: "Person"
      type: "Autocomplete"
      collection: "Roster.people"

It works nicely, and I’m hoping to be able to contribute this back to the community (tests already written), but there’s a design flaw: the mechanism of specifying the data source.
I originally passed the collection in directly, but then I ran into loading order problems. Now it uses the dreaded eval to find the collection. It’s okay for my purposes, but wouldn’t be happy releasing it that way for general usage. Apart from being a poor solution, it’s also limited in that there can only be one backing collection, so I can’t use, say, a subset of the People collection if I need to.
Does anyone have thoughts on how I can make a clean interface so other people can integrate this type of editor? Is it just not a good fit for the design of Backbone Forms? Here are ideas I’ve considered and why I think they don’t work:

passing in a function for the data source: editor could then only find objects in global scope
specifying a datasource or something that could be passed in when constructing the Form: an Editor has no access to the Form that contains it

An extra benefit for me to solving this would be that I can add validation that depends on an entered value being in a collection determined at runtime.
I debated whether this was the venue for this sort of question or whether Stack Overflow was better. Sorry if I chose incorrectly.

As an example, here's the custom editor I created for a project, using my forked version of the Chosen ajax input (see https://github.com/powmedia/ajax-chosen).

does it require any changes with the latest versions? It doesn't seem to trigger ajax for any inputs... I try to figure it out on my own ATM, but..


Utf8Decode of UnmodifiableUint8ListView crashes on web

I suspect that the fast-path selected via is Uint8List is selected for UnmodifiableUint8ListView, and ends up in inappropriate JavaScript code.
I'm assigning myself to add more details.

@rakudrama as @julemand101 suggests, this may now be working now that the fix to #49898 landed.


Astarte dashboard documentation page is missing

There is no documentation page about Astarte dashboard, therefore it is hidden to end users.
A documentation page should be added.

Should be assigned to @atsetilam

This is fixed now, closing this


⚠ Bofrost.fr has degraded performance

In 2da8dd6, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1391 ms

Resolved: Bofrost.fr performance has improved in aa581eb after 6 minutes.


proposal: support different response convention

Thanks for the library, it's simple yet extremely convenient.
When using it I found the SuccessAPIResponse<T> a little restrictive. (My case is to port existing API endpoints to use this library, so it would be simpler if it's not the only convention).
If we are ok with this, I think I can send a PR afterwards

The PR would be like diff .

For this you can use api.raw — you just need to do res.json({ custom_response: true });
Perhaps nextkit does need some proper documentation! 😄

But api.raw would still force use of ErroredAPIResponse in error handling. Unless of course the provided http method-specific handler never throws.

I believe that, if we move all code that creates wrapped response (SuccessAPIResponse<T> | ErroredAPIResponse ) into the default handler, the getResult would be decoupled from response convention , and free to use for other possible cases.
Please refer to self-review comment in https://github.com/alii/nextkit/pull/6/files .
Sorry for the late reply. I just returned from a long weekend.


chore: 폴더 구조 변경

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update REFERENCE.md with paginate parameter

This updates the documentation; if you merge this into your branch, then the PR against mine should be updated ;)
Signed-off-by: Matt Stratton<EMAIL_ADDRESS>

Merged. Hope this works!


MLHR-1693: Change the zookeeper set configuration.

Change the zookeeper set configuration. Added a unit test for parsing. Fixed the compilation errors in benchmark.

Updated as per the comments.


Update get-best-of-standard-dataflows - Known Limitations Wording Adjustment

In the known limitations, I've adjusted the detail around the 'multiple-select' data load.
Through testing multiple scenarios, I have found that:

if you try and migrate BOTH a multi-select choice column AND a single-select choice column, the dataflow will fail (and the error makes you think it's because of the multi select field).

If you migrate just one TYPE of choice field, dataflow runs perfectly.

I think the wording needs to be clearer to outline this issue with Dataflows.
Image showing the error message received when two different choice types are selected:

Image showing the refresh history when only Multi-select choice fields are published:

@msftyehong  I believed we already similar feedback to this page already? I think it is clear that the change proposed makes sense, however, is this the expected behavior?

@bdiggydogness @msftyehong - Having not heard anything back on this issue for months, I'm closing this issue as "can't reproduce". If you want to continue the conversation, you can reopen this pull request.


a bug in "sample/dcgm/deviceinfo/main.go

In the bind/go/sample/dcgm/deviceInfo/main.go file, there is an error in the definition of deviceInfo. If the GPU device supports DCGM, the following error message will appear:
Template error: Template: Device: 19:10: Execute "Device" in <.GpuID>: Cannot evaluate field GpuID in dcgm.P2PLink type
Here I modified the variable "GPU" in the P2PLink structure in the bindings / go / dcgm / topology.go file to "GpuID" to fix it.

I have fixed it. Its simpler to keep the old variable and fix the template.


New node : Switch in an array

Possibility to search a set of values in an array.
Parameters :

array (eg: payload.entities)
key (eg: entity.name)
possibile values

The comparison would work like a "switch".
Use case : search of entities in LUIS json result.

Done: Search node added.


skate depends on skatejs-build

I understand that his was necessary in https://github.com/skatejs/skatejs/commit/7052894307ea24298b236142ebcc8d9389309a33#commitcomment-19644052 ? Is there another way?
It's a bit problematic because it means that anything depending on skate will also pull in all of the skatejs-build dependencies.

Haven't got around to reverting because I was going to see if there was a
way to get JSDOM working.
On Tue., 1 Nov. 2016, 20:17 Joshua Nelson<EMAIL_ADDRESS>wrote:

I understand that his was necessary in 7052894#commitcomment-19644052
https://github.com/skatejs/skatejs/commit/7052894307ea24298b236142ebcc8d9389309a33#commitcomment-19644052
? Is there another way?
It's a bit problematic because it means that anything depending on skate
will also pull in all of the skatejs-build dependencies.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/skatejs/skatejs/issues/896, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIVbCwJWLJJwJElTG5Z3TIn-RIEnG1hks5q5wOwgaJpZM4Kl5yb
.

But it would be reverted in future? If so I might turn this into a task

For posterity, a yarn add --save-dev was done instead of yarn add --dev, I think.


Some of fixed date ranges in Get-OpenAIUsage & Get-OpenAIBilling may return the incorrect dates.

The fixed date ranges -thisWeek, -lastWeek, -thisMonth & -lastMonth in both Get-OpenAIUsage & Get-OpenAIBilling functions may return the incorrect dates.

Found as of today the API endpoint https://api.openai.com/v1/usage which is used by Get-OpenAIUsage no longer accepts date ranges.
So the parameters -thisWeek, -lastWeek, -thisMonth, -lastMonth, along with -startDate & -endDate all fail with:
error
-----
@{message=Missing query parameter 'date'; type=invalid_request_error; param=; code=}

These parameters will all be removed in the next version and a new -date parameter will be implemented, to allow a usage for a single day to be retrieved.

Hi, in this Get-OpenAICreditGrants.ps1 script, the key being used is apikey, but openai requires it to be sessionkey. Did I misunderstand something?

Hi, in this Get-OpenAICreditGrants.ps1 script, the key being used is apikey, but openai requires it to be sessionkey. Did I misunderstand something?

Hi,
No, you didn't misunderstand anything. It looks like they have changed something on the backend.
I am seeing:

Get-OpenAICreditGrants -jsonOut -Verbose
VERBOSE: APIKey is sk-pkxb**************************************oB1emM
VERBOSE: GET https://api.openai.com/dashboard/billing/credit_grants with 0-byte payload
{
    "error":  {
                  "message":  "Your request to GET /dashboard/billing/credit_grants must be made with a session key (that is, it can only be made from the browser). You made it with the following key type: secret.",
                  "type":  "server_error",
                  "param":  null,
                  "code":  null
              }
}

The API endpoint I am using is an unofficial one, so this is likely to happen.
When I have some free time, I will look to see if this function can be fixed.
Thanks
M


"No deployment available" when deploying with this action

Hi,
my setup is pretty straight-forward. I have a Remix app with a simple build step remix vite:build.
When I run the following commands locally it deploys to Cloudflare successfully.
remix vite:build
npx wrangler@3 pages publish ./build/client --project-name="xxx" --branch="main"

but when I use the action (which uses the same command) I get failed deployment with "No deployment available" in the dashboard, even though GH action output says it was successful:
✨ Compiled Worker successfully
Uploading... (21/21)
✨ Success! Uploaded 0 files (21 already uploaded) (0.33 sec)

✨ Uploading Functions bundle
✨ Deployment complete! Take a peek over at https://5f466361.xxx-dyu.pages.dev/

Is there a way to debug it?

publish.yaml:
...
      - name: Publish to Cloudflare Pages
        uses: cloudflare/pages-action@v1
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          projectName: xxx
          directory: ./build/client
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          wranglerVersion: "3"
...

Closing the issue here as it's related to wrangler itself.


changed order of onDrag call inside handleEndOfDrag

This fixes discrepancy in order of events between iOS and Android, when calling onDrag({state: "end"})

Thank you @matzewagner !


PriceGun component added to Cargo PDA

About the PR
The Price Gun component has been added to PDAs (QuartermasterPDA, CargoPDA, SalvagePDA).
Cargo workers must always know the price of the goods, even when Price Gun is not with them.

[x] I have added screenshots/videos to this PR showcasing its changes ingame.

:cl: Lomcastar

add: NanoTrasen Corporation has equipped all Cargo PDAs with an evaluation module!

https://user-images.githubusercontent.com/129697969/234325569-8d0f451d-2ba0-4bc7-87a7-cf3a6ff1175e.mp4

cool, but... no. Implement it with a cartridge.

I'll try, I think yes, with a cartridge we will be much cooler. Then it will also be possible to replace the medical scanner in the PDA with a cartridge.


Profile section for admin

It will provide the facility of changing email, password and name of admin in admin panel.

@hardikvarshney Profile section for admin is not required for this project as the admin panel will be managed by a single person.


Can not unlock wallet

Anchor v1.2.2 on WAX.
Authorizing individual wallet actions like switching to a different account works. Therefore, I know I am using the correct local wallet password. However, for signing requests and the "unlock wallet" button in the top right do not work. With unlock wallet, clicking the unlock wallet button has no effect and the popup does not disappear.
With signing transactions, I am prompted to enter my local wallet password, which I enter correctly, then the signing request merely reloads as though I have entered an incorrect password - though it doesn't say incorrect password or anything.
Steps:

Go to a smart contract on bloks.io
Click login to anchor wallet
Click "Open Anchor App"
Click "Unlock wallet + Sign" button
Enter local wallet password
Click "Authorize"
Expected behavior:
Wallet should unlock and confirm transaction signing
Actual behavior:
"Enter wallet password" popup disappears, but "Identity request" popup does not. The lock icon on the signing button turns into a loading icon for a second before returning to lock icon state.

This sounds like it might be indicative of it not being able to load the appropriate private key for the account its trying to unlock.
Do you know how you setup this account initially in Anchor, and by chance was it using the "Manual Import" option?
A second question would be, have you ever been able to use this account in Anchor to sign transactions?

This issue appears to be resolved after connection to a different WAX node. While it no longer appears to be an Anchor issue, a clear error message 'We're having trouble connected to the network through your node' - or even any error message indicating it is not an Anchor issue - would be helpful in such a scenario.


[FEATURE] Make a custom border radius generator.

Description
This issue is in response to #5 issue.
Make a custom CSS border-radius generator similar to Fancy-Border-Radius
Screenshots
No response

Why?

You made #5  asking for a new generator idea. So I thought it would be better if we include a custom CSS radius generator.

You made #5 asking for a new generator idea. So I thought it would be better if we include a custom CSS radius generator.

If you can make it then sure

Hi i want to work on this can you assign this to me

Hi i want to work on this can you assign this to me

Definitely, thanks for wanting to contribute

@Dun-sin Can I work on this?

:tada: This issue has been resolved in version 2.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Ensure display name is updated correctly when existed

Fixes #11380. This is the code path where we didn't update the display name correctly when it exists.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for feature-requests.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@9eba87c). Click here to learn what that means.
 Consider uploading reports for the commit 58a9ded to get more accurate results

@@           Coverage Diff           @@
##             main   #11387   +/-   ##
=======================================
  Coverage        ?      63%
=======================================
  Files           ?      476
  Lines           ?    33941
  Branches        ?     5498
=======================================
  Hits            ?    21547
  Misses          ?    10339
  Partials        ?     2055

Impacted Files
Coverage Δ

src/kernels/jupyter/launcher/serverUriStorage.ts
67% <80%> (ø)


Adding emergency upgrades to nctl nightly runs

introduces compile_global_state_update_gen.sh to compile.sh.
adds emergency_upgrade_test & emergency_upgrade_test_balances to nightly wrapper.
small toml update for adding last_emergency_restart

bors r+


about headless rendering

Can I build filament for headless rendering, like building in docker?

You can build Filament with SwiftShader support (with the -t argument when calling build.sh). You can also use headless OpenGL rendering if you have a software implementation like Mesa installed for instance. You can also create headless swap chains in the Filament API (using Engine::createSwapChain(width, height)).

"You can also use headless OpenGL rendering if you have a software
implementation like Mesa installed for instance." If I want to use this
one, what should I do? should I change something in the cmake file?
Thanks.
Regards,
-Wanyan
Romain Guy<EMAIL_ADDRESS>于2020年10月8日周四 下午2:47写道：

You can build Filament with SwiftShader support (with the -t argument
when calling build.sh). You can also use headless OpenGL rendering if you
have a software implementation like Mesa installed for instance. You can
also create headless swap chains in the Filament API (using Engine::createSwapChain(width,
height)).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/filament/issues/3176#issuecomment-705841072,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ7RA4CTVIJWM2KZJNVNITSJYXOLANCNFSM4SJJQC3A
.


Trust region method, crop to object, and cleaning up initialization

The branch name is not very meaningful here.

Awesome


Use the cycle timetable to determine which cycle to carry over to

Context
At the moment, we use the current applications recruitment_cycle_year to determine which cycle to carry over the application to.
It does this by taking the current applications recruitment_cycle_year and adding 1 to it.
This works fine when someone is carrying an application over one cycle. However, if the application form is two years old, this causes two carry overs to happen.
Instead we should just figure out which cycle they should be in by using the cycle timetable to establish where they are in the cycle.
If it's after the apply1 deadline, but before cycle launch, it should be carried over the next cycle. If not then just carry over to the current cycle.
Changes proposed in this pull request

Use the cycle timetable to determine which recruitment cycle to carry over an application

Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

@cwrw spotted it 🙌  Great find


fix(tokens): PostDeposit hook

The PostDeposit hook was running inside try_mutate_account, so the user's balance was still equal to the pre-deposit amount. This caused certain post-deposit actions to fail.
Reason why this was not caught in the tests
The post-hook tests just increment a variable, so there are no real side effects. I thought about adding balance-changing posthooks inside the mock runtime, but those hooks would affect the results of many other tests. I don't think there's an easy way to use multiple mock runtimes in unit tests either.

one why to write tests for this is to instead of just record call count, record the hook parameters in a vector. then you can assert the vector for expected number of calls & expected called values

I tried implementing your suggestion but realised that call parameters were correct, it was the timing of the call that was wrong.
As such, I added checks in the mock posthooks which enforce that the balance of the account is at least amount. I was then able to test the edge case that this PR fixes.

In that case you can read the account data and have it saved to the vector for assertion as well. But I am ok with your current approach.


chore: image for release 13.5.1

Image for 13.5.1 release

Can someone re-run the build? It seems that the docker images are not successfully build and pushed.


Update our performance benchmarking docs for 21.1

@awoods187, @mwang1026, do we have new tpcc benchmarking results for 21.1 that should be reflected in the docs? And should we update the tutorials in any way?
https://www.cockroachlabs.com/docs/v21.1/performance.html

We aren't planning to push the scale here in 21.1 testing-wise. @nvanbenschoten can PTAL and see if we need to update anything else here?

I'm not aware of anything that needs to change on that page, other than the reference to v20.2. There was no significant movement in any of the workloads that it references.


[Translations/Extensbility Bug] report 1304 "Standard Sales - Quote" - ArchiveSalesDocument

🕮 Describe the request
The question to archive a sales quote isn't shown in the user language, when the "Language Code" of the SalesHeader is different.
Therefore I sugges the following change for the "Sales Quote Report".
if not IsReportInPreviewMode() and
    (CurrReport.UseRequestPage and ArchiveDocument or
    not CurrReport.UseRequestPage and (SalesSetup."Archive Quotes" <> SalesSetup."Archive Quotes"::Never))
then
    case SalesSetup."Archive Quotes" of
        SalesSetup."Archive Quotes"::Always:
            ArchiveManagement.ArchSalesDocumentNoConfirm(Header);
        SalesSetup."Archive Quotes"::Question:
            //+Change
            //-ArchiveManagement.ArchiveSalesDocument(Header);
            begin
                SetLanguage(Language.GetUserLanguageCode()); //Set Language to the User Language
                ArchiveManagement.ArchiveSalesDocument(Header);
                SetLanguage("Language Code"); //Set Language to the Document Lanuage to remain extensibility for ReportExtensions, that expect, that language was changed.
            end;
            //-Change
    end;

Additional context
It is very confusing if a german user recieves this question in english or some other report language.

In my opinion this is a bug, but I would be willing to fix it as outlined above in the BaseApp Pilot.
I did post it here - at first only for a public place for discussion, if this is a bug or not.

Got it. But if it's a real bug, the issue can only be reported in two ways:

If a customer is affected by this, the issue must go through support. That way we ensure that SLAs are met and that all supported versions of Business Central will receive the fix.
No customer is as such affected by it / workarounds are in place: You can decide to fix the problem yourself or hope another member of the community does so, by logging an issue in the BaseApp Contribution Pilot.

In this repository we ideally only accept extensibility requests and extensibility bugs (bugs in extensibility requests we've processed). We do accept the occasional bug on other extensibility related issues, which don't have customer impact, but which are needed to be resolved for a partner to bring their extension to market. But we cannot commit to any timelines for these bugs and rather often, it takes quite a while for us to get to those issues.
I know you know most of this, but I thought I'd mention it once more for others who might stumble over this issue :-)

Closing as it is got implemented via related contribution to BaseApp Pilot (BusinessCentralApps repo).


[Bug] New Remote-Play popup cannot be navigated with controller.

Checklist

[X] I will only use English in my report.
[X] I have used the search function for open and closed issues to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

Questions

[X] xCloud officially supports my country/region.
[X] The bug doesn't happen when I disable Better xCloud script.
[X] The bug didn't happen in previous Better xCloud version (name which one).

Device
Other
Device
Steam Deck OLED
Operating System
SteamOS (arch based)
Android app/Browser Version
Chromium 128.0.6613.137 (flathub)
Better xCloud Version
5.7.4
Game list
Remote Play
Reproduction Steps
• Open Xbox Cloud Gaming page.
• Use a gamepad to navigate to remote play button and click it.
• Un-profit.
(This worked as intended on the previous version, 5.7.3.)
Screenshot/video
No response

Fixed: https://github.com/redphx/better-xcloud/raw/refs/heads/typescript/dist/better-xcloud.user.js


Websocket Life

Websocket disconnects after a duration, could be 5 minutes, could be 4 hours- NOT caused by machine/host network.
no useful tracebacks, more information on this issue is required.

Probably discord requesting reconnect (opcode 7)?

No, that has been handled.

Just occurred again and here's the traceback.
Exception in thread Thread-1 (heartbeat):
Traceback (most recent call last):
  File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.11/threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "DankCord/src/DankCord/gateway.py", line 43, in heartbeat
    self.ws.send(orjson.dumps({"op": 1, "d": None}))
  File "DankCord/.env/lib/python3.11/site-packages/websocket/_core.py", line 283, in send
    return self.send_frame(frame)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "DankCord/.env/lib/python3.11/site-packages/websocket/_core.py", line 311, in send_frame
    l = self._send(data)
        ^^^^^^^^^^^^^^^^
  File "DankCord/.env/lib/python3.11/site-packages/websocket/_core.py", line 525, in _send
    return send(self.sock, data)
           ^^^^^^^^^^^^^^^^^^^^^
  File "DankCord/.env/lib/python3.11/site-packages/websocket/_socket.py", line 143, in send
    raise WebSocketConnectionClosedException("socket is already closed.")
websocket._exceptions.WebSocketConnectionClosedException: socket is already closed.

Ok, so its a bit like the reconnect. Here's a pic from the docs.

You just gotta handle it like a new session.

That is handled as well. Currently, dankcord yeets the old connection and opens a new one.

Well apparently it doesn't? Why is the error saying the connection is closed then?

It should raise the exception before, in the receive part (_events_listener). The fact that it waits for heartbeat is more troublesome

Hmm, then idk. I don't have that much knowledge of the code.


s6-maximumtime: warning: child process crashed

It seems, if the database is bigger and consumes more time, it crashes due to the s6 maximumtime limit.
When I manually run backup-now everything is fine.
But the automatic crons wont work. In my logs I find something like:
[INFO] ** [db-backup] Backup routines Initialized on Thu Aug 27 03:09:30 CEST 2020
[NOTICE] ** [db-backup] Compressing backup with gzip
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 10-db-backup: executing...
s6-maximumtime: warning: child process crashed
[cont-finish.d] 10-db-backup: exited 111.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

I was reading something about this on https://github.com/just-containers/s6-overlay:
S6_KILL_FINISH_MAXTIME (default = 5000): The maximum time (in milliseconds) a script in /etc/cont-finish.d could take before sending a KILL signal to it. Take into account that this parameter will be used per each script execution, it's not a max time for the whole set of scripts.
Not sure if it's related. But anyways, it shouldn't right?

Not related unfortunately - that's more used for when you are taking a container down and you want to shut the process down gracefully.
I am interested in a bit in finding out on what size of database / type you are trying to backup. The largest one I back up regularly is approximately 980gb.

Thanks for your quick reply:) Oh really, mine is very small in comparison, maybe 1G. When running manually it takes maybe 2 minutes not much more :'). Maybe it somehow hangs elsewhere. I didn't see it happening real-time. I can test a bit further by actually monitoring the cronjob triggering, I'll let you know when I have more input!

Latest releases I have moved away from using cron and wrote my own scheduler inside the tool itself - What you can do is try either the following: CONTAINER_LOG_LEVEL=DEBUG as an environment variable, or a last resort DEBUG_MODE=TRUE which will give you far too much output and leak all your credentials at the same time to your console which should give you an idea of whats happening. Keep me posted. I can add more debug routines if necessary.

Thanks for your help! I'm not really sure why, but it seems that the issue was 'magically' solved. When changing settings and rebooting the container, the cronjobs now run fine. If I find any other issues or get any idea of cause of it was I'll let you know 👍


Normalization reboot - Artifacts inventory

to:
related to: @Ryxias 's Working proof-of-concept for StreamAlert Normalization v2
resolves:
Background
Coming soon...

Reason for the change
Changes

Summary of changes
...

Testing
Steps for how this change was tested and verified

Coverage decreased (-0.07%) to 95.358% when pulling d495a48bb20a24915d6e945f1b79eeae86bfd29c on cylin-ae-lambda into a83f3e92a69c7d589c428a6aeb597617ed00508b on feature-artifact-extractor.


Documentation links to lessons are outdated

That page and I believe all other pages referencing lessons contain outdated links, as lessons moved from blob/master to wiki.
Please, fix.

Sorry for that. Those pages will soon be replaced when v2.0 is released (currently in beta). The document for the v2.0-beta is available here.


Twilio (verification)

Create a SaaS connector to Twilio's API.

Authentication: Basic auth
Requires pagination? yes

pageStructure:
  indexContainer: PAGE_DATA
  incrementalParam: Page
  nextPageLabel: PageToken
  pageDataFields:
    - name: next_page_uri

Needs pre/post-processing? no
Identity: email, number, verification_resource_sid, entity_identity

Requirements

Is the ask here to try and get a free account for testing purposes?

Free account for testing services - rate limit sandbox
Ethyca certified partner and integration
Value add to them - customers will bring their own twilio licensing giving them more adoption


EE->OSS cherrypick - Operator CRD sync

generator thrashing

copy operator installations CRD

generate files from updated operator installations CRD

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Github resolves the PR reference in the commit msg to the PR of the same number in OSS, ignore...
Picks d2a2ebd  from EE


cmake error!

-- Dawn: using SPIRV-Headers at /home/webgpu/dawn/third_party/vulkan-deps/spirv-headers/src
CMake Error at third_party/CMakeLists.txt:23 (add_subdirectory):
add_subdirectory given source
"/home/webgpu/dawn/third_party/vulkan-deps/spirv-headers/src" which
is not an existing directory.
-- Dawn: using SPIRV-Tools at /home/webgpu/dawn/third_party/vulkan-deps/spirv-tools/src
CMake Error at third_party/CMakeLists.txt:32 (add_subdirectory):
add_subdirectory given source
"/home/webgpu/dawn/third_party/vulkan-deps/spirv-tools/src" which
is not an existing directory.
-- Dawn: using GLFW at /home/webgpu/dawn/third_party/glfw
CMake Error at third_party/CMakeLists.txt:41 (add_subdirectory):
add_subdirectory given source "/home/webgpu/dawn/third_party/glfw"
which is not an existing directory.
-- Dawn: using Tint at /home/webgpu/dawn/third_party/tint
CMake Error at third_party/CMakeLists.txt:54 (add_subdirectory):
add_subdirectory given source "/home/webgpu/dawn/third_party/tint"
which is not an existing directory.
-- Dawn: using Abseil at /home/webgpu/dawn/third_party/abseil-cpp
CMake Error at third_party/CMakeLists.txt:60 (add_subdirectory):
add_subdirectory given source
"/home/webgpu/dawn/third_party/abseil-cpp" which is not an existing
directory.

please use google's official dawn repository, I am not maintaining this repository or providing any form of support https://dawn.googlesource.com/dawn


Switch to strategic-merge-patch

If an object does not yet exist on the server, kubecfg creates it
using a POST - this has not changed.
If an object already exists on the server, previously kubecfg would
PATCH it with a JSON merge patch to produce the updated version.
This was simple and worked for almost all cases, but (eg) failed to
remove annotations that had been removed from local config.  This
latter is surprising because it is not how kubectl apply works, and
it is not the object-level semantics that kubecfg implements with
its own garbage collection.
This change switches to performing a schema-driven client-side 3-way
strategic-merge-patch between the last version of the object created
by kubecfg, the new version of the object found in local configs,
and the current version found on the server.  The "last version" of
the object is stored JSON-serialised in a new
kubecfg.ksonnet.io/last-applied-configuration annotation on each
object.  The updated object is then sent to the server using a
PUT (with retry on resource conflict).
This reimplements the kubectl apply semantics, so is consistent with
the standard kubernetes tools in this space.
Also a few minor but user-visible verbosity improvements:

Now prints only one of "Creating ..." or "Updating ..." progress
message.
Prints no message at all if the object has not changed (according to
Semantic.DeepEqual)

Given the significance of the change, I want to test this further before we merge it...

Do you know how does rc.Update behave in case of a mutating admission controller?
In particular, if the admission controller adds back an annotation we removed during the 3-way merge, will we correctly avoid outputting "Updated"?

Do you know how does rc.Update behave in case of a mutating admission controller?

I would want to test it, but my understanding is that the Update result (ie: the HTTP PUT response body) will include the results of the mutating admission controller.
Note the code does (paraphrased):
if DeepEqual(existing, new) {
   return nil
}
log.Info("Updating ...")
err := rc.Update(new)

So we print the "Updating" message every time we perform the HTTP PUT - and without regard to any changes the server might make from that point.

Yeah, I guess this means we should recompute the differences between the newobj (as returned by update) and the existing object (the object on the API server before our update)

I guess this means we should recompute the differences between the newobj (as returned by update) and the existing object (the object on the API server before our update)

I figured/wanted the "no differences" code to kick in when kubecfg is run repeatedly with no config changes.  Specifically in this case:

we have some initial or modified jsonnet
rc.Create() or Update() with the orig jsonnet(A) stashed in the annotation (as json)
(hypothetically) server or controller makes some additional (non-conflicting) changes to object, producing some result(B) on server
kubecfg is run again with unmodified jsonnet(A')
now we have: 3way merge of A, B, A', which should produce B (since A->A' is no changes)
This will be detected as a no-op because state on server == B

(ie: patch(existing, obj) will return a copy of existing)
I will create some integration tests to verify this and other combinations - this is part of what I wanted to confirm before merging this PR.

ok, if annotations are not conflicting then the behaviour of this PR is sound and easy to reason about.
I was thinking of this scenario:
First version of jsonnet input A had annotation a and once pushed now the state B on server also has annotation a.
Now the user removes annotation a in A' , but the server reinstates the annotation a because the admission controller puts it back.
now, kubecfg can report this in two ways:
a) print "Updated", because in a way that's what happens: the user wanted to remove an annotation and kubecfg obliged
b) don't print "Updated" because the operation had no real world effect (the annotation is still there)
which of those two behaviours is least surprising?
(Since A' is then saved in "last-applied-configuration" this choice matters only once)

This is wonderful to see, @anguslees.
One question so far: Would you consider compressing the content of the "kubecfg.ksonnet.io/last-applied-configuration" annotation? Does it need to be human-readable?

First version of jsonnet input A had annotation a and once pushed now the state B on server also has annotation a.
Now the user removes annotation a in A' , but the server reinstates the annotation a because the admission controller puts it back.

(With this PR) kubecfg will see the removed annotation (A->A'), print "Updated" and update the object removing the annotation (both last-applied and actual object won't have the annotation).
If the server adds the annotation back (either admission-time or later asynchronously), then on the next run kubecfg will see the annotation as added externally (A->A' does not have the annotation, B does), and patch() will preserve the annotation since it does not conflict with A->A'.  kubecfg will not print "Updated" and will not update the object (assuming there are no other A->A' changes) because the existing object matches the result of patch(A, B, A').
Obviously I need to actually do the update before I can see if/what the server might do next.  The current code just prints "Updating" (future tense) whenever it actually does an Update() call - mostly so the error makes sense in context (if the Update() fails).
I think you're suggesting I should compare the REST request vs response and then only print "Updated" (past tense) if that changed.  I can certainly do that instead (I need to strip out the server-set metadata in both cases anyway).

Would you consider compressing the content of the "kubecfg.ksonnet.io/last-applied-configuration" annotation?

:thinking: I had not thought of compressing it, other than using a json rendering with minimal whitespace.
kubectl apply uses regular json, but there is no reason this needs to be human readable (or compatible - we don't want to use the last-applied value for other tools).  I could compress it (eg: gzip+base64) easily enough.
A quick test on a largish object (Deployment) and smallish (Service) produced these file sizes:
2346 | deploy.json
1232 | deploy.json-compact
820 | deploy.json-compact.gz.base64
808 | svc.json
490 | svc.json-compact
412 | svc.json-compact.gz.base64
So it is even a win for small objects.  Good suggestion :)

I'm happy with the test coverage now (and uncovered/fixed several important bugs in my first iteration).
I want to do the base64+gzip thing that seh suggested before merging, however (a small change, but easier to do in the same PR so there is no migration to worry about)

any update here?  I've been eagerly checking in on this PR every few days.

any update here?

The increased test cases uncovered a cache-invalidation bug in this PR, which I hadn't noticed until I ran it against the empty CI test environment.  (A brand new CRD plus an instance of that custom resource in the same run failed.)
I finally fixed that this morning, yay.  Now the same test is catching a race (that was always there) between creating a CRD and when that new custom resource appears in discovery metadata.  Previously I ignored that, since it rarely triggered in practice (round trip delays to the server and updates to other intervening objects were sufficient to cover up the delay).  I figured I'd fix that while I'm here though, rather than insert a sleep() or similar hack just to get the test to pass reliably.
So: yay for tests.

@mkmik: I think we're good to go!  There have been a number of changes since your last review, so you probably want to look it over again.

@anguslees I forgot why we didn't just use kubectl.kubernetes.io/last-applied-configuration. Is attempting interoperability with kubectl apply unsound?


Stripping custom headers from haproxy?

I'm using haproxy to create a custom header with the ip address of the incoming connection.
My setup is like so
fe-http => be-oauth => fe-post_oauth the ip address shows as <IP_ADDRESS> which I understand because the connection came from the oauth client.
Another example is
fe-http => be-oauth => be-app the custom header is completely removed.
So it seems that either oauth is completely either stripping the header or is writing the header as it's local ip. Is there a way to pass custom headers to oauth? I've even tried using a custom header with just text in it and that is being stripped as well.

Any news one this?

Love to get an update on this. We are still having issues with oAuth stripping headers.

Bump

Quite a while later and it seems to still do this, unfortunately.

Which specific request header is oauth2_proxy affecting? You really should do more investigation of any issues you really want to resolve.
I can guess that you're talking about X-Forwarded-For. The httputil.ReverseProxy adds to to the X-Forwarded-For list, see https://golang.org/src/net/http/httputil/reverseproxy.go?s=2588:2649#L195
The application needs to pop entries off the end of the list based on the known trusted addresses of forwarders (or take the first item from the list if you just want to fully trust the contents of this header). nginx can do that with "set_real_ip_from" and "real_ip_recursive", python tornado httpserver can do that with "xheaders" and "trusted_downstream", etc.
But there are other headers affected too, each for a specific reason. oauth2_proxy by default sets GAP-Auth, X-Forwarded-User, X-Forwarded-Email, and (interestingly) Authentication (with Basic auth just specifying username), but these all can be disabled. The ReverseProxy clobbers "Hop-by-Hop headers" (e.g. Connection), see https://golang.org/src/net/http/httputil/reverseproxy.go?s=2588:2649#L117


Ukrainian translation

sup, need help with ukrainian translation?

Hello o/
All translations are created by volunteers wanting to contribute to the project. If you'd like to contribute, you'd need to clone this repository, launch the application from source to let it create the default English.json translation, and then translate all strings in it. The resulting translation can then be tested by running from source again and selecting the new translation file, and then a PR can be made to incorporate the translation into the project.
If all of this sounds too technical for you, I can also "manually" provide you the current English.json for translation purposes, which you can then translate and send back by attaching it as an attachment here. This skips the PR and testing phases, relying entirely on me to do the testing part of the translation, which I'm okay with, provided I can find the time for all of this (my time is quite scarce). The PR route would be significantly faster, but then again, I don't know how familiar you are with the tools and possibilities Github and git provide here.

I think I'm doing something wrong🤔

How do I test it? Changing language requires restart, but program always starts in english

How do I test it? Language changing requires restart, but program always starts in english

Here, .json can't be uploaded here
Українська.txt


Initial Commit

YouTrack Ticket Dev-790
Initial commit for kue library.
Supports:

universal setup through kue.setup(queue, [callbacks])
cleanup based on config on .save()
explicit cleanup through kue.cleanup(jobName, status)

Changes that need to be done in current kue codes (when npm published)

replace require('kue') with require('anytv-kue')(<config>)

I think this is good.
Additionally, how can we make sure the queue job status logs more useful information?

@pandafox its the user's job to do that, kue just logs what it gets when done() is called, first argument should be an instance of error

I know, but it'll help if we have examples, or we include specifics about the jobs so we don't always see "Untitled" etc., perhaps stringify the parameter at least?


Literature for integrating ota, mqtt and wifi_provisioning over ble demos AWS FreeRTOS ESP32

Hello there. Is there any documentation where I could check in order to integrate
demos from here https://github.com/aws/amazon-freertos/releases/tag/202012.00?
I want to integrate:
https://github.com/Yoimer/aws_freertos_esp32_components/blob/main/demos/coreMQTT/mqtt_demo_mutual_auth.c
https://github.com/Yoimer/aws_freertos_esp32_components/blob/main/demos/ota/aws_iot_ota_update_demo.c
https://github.com/Yoimer/aws_freertos_esp32_components/blob/main/demos/wifi_provisioning/aws_wifi_connect_task.c
What's in this code is not that clear to me https://github.com/Yoimer/aws_freertos_esp32_components/blob/main/demos/include/iot_demo_runner.h, in order to add another tasks as they mention.
Thanks in advance.

Hi @Yoimer
You could use one of the demo entry function  vRunOTAUpdateDemo() or RunCoreMqttMutualAuthDemo() and modify it to spawn a new task and run the other demo entry function in it.
However it should be noted that the OTA update demo uses old MQTT library APIs and it works through a SHIM layer implementation. This means the network interface and connection type used is different between demos and could not be shared. The combined demo will create two separate MQTT connections to the cloud, so the client identifier used should be different for both connections otherwise AWS IoT will reject the older connection with duplicate client identifier.
For provisioning WiFi credentials using BLE you can enable the demo and follow the instructions to provision a WiFi network from app as shown in doc here: https://docs.aws.amazon.com/freertos/latest/userguide/ble-demo.html#ble-demo-wifi
The aws_wifi_connect_task.c will take care of reconnecting to a provisioned network when device is rebooted or current wifi connection is lost.
Please let us know if you have more questions.

@ravibhagavandas Dear, thanks a lot for replying and assisting me. I will put in practice this valuable information. Please keep open this issue. I will update over here by tomorrow evening.
Have a wonderful day.

@ravibhagavandas I truly hope you're having a great day. I found an ota + mqtt fully functional demo for AWS FreeRTOS ESP32 for version V202002.00 which you kindly you can check here https://github.com/Yoimer/AFR_ESP32_FreeRTOS_V202002.00/blob/master/demos/ota/V202002.00_aws_iot_ota_update_demo_and_mqtt.c.
My goal is now integrate the wifi_provisioning example on this ota + mqtt integration. Specifically this https://github.com/Yoimer/AFR_ESP32_FreeRTOS_V202002.00/blob/master/demos/wifi_provisioning/aws_wifi_connect_task.c
I had to hard code my wifi credentials here https://github.com/Yoimer/AFR_ESP32_FreeRTOS_V202002.00/blob/master/demos/include/aws_clientcredential.h in order to test the mqtt + ota. I want to use ble over wifi demo to accomplish that goal.
Would you mind guiding me on this, please?
Thanks in advace.

@Yoimer Did you also add the shadow example or are you only looking to use the MQTT ?

Hi @Yoimer
I am looking at your code and it seems you have all the pieces of code in your repo. The wifi connect task as given in demo is initialized through network manager component, when you enable WiFi network, code here.  For the task to initialize,  IOT_BLE_ENABLE_WIFI_PROVISIONING flag should be enabled as in the comment in issue #3048 .
The demo will wait here for a  WiFi credential to be provisioned and connected before running the entry function.

@Yoimer Did you also add the shadow example or are you only looking to use the MQTT ?

Hello @ncohen17 I did not since I do not need it. In case you do, please download it from here https://github.com/aws/amazon-freertos/releases/download/202002.00/amazon-freertos.tar.gz. That tar has all the demos available for the Version 202002.00 including all the vendors.

Hi @Yoimer
I am looking at your code and it seems you have all the pieces of code in your repo. The wifi connect task as given in demo is initialized through network manager component, when you enable WiFi network, code here. For the task to initialize, IOT_BLE_ENABLE_WIFI_PROVISIONING flag should be enabled as in the comment in issue #3048 .
The demo will wait here until a WiFi credential is provisioned through a smartphone app and device gets connected to it, before running the entry function. When the flag is enabled you don't need to configure any static wifi credentials in https://github.com/Yoimer/AFR_ESP32_FreeRTOS_V202002.00/blob/master/demos/include/aws_clientcredential.h.

@ravibhagavandas Thanks a lot for your support. That's very kind from you. I will check this and update over here later. Have a great day.

@Yoimer I am looking to make a similar firmware, are you available as a freelancer for my project?

@ravibhagavandas Thanks a lot for your support. I managed to activate the wifi_provisioning on V202002.00 as you explained. The rest of the code is waiting for the ssid and password to continue.
Now we will test the Android app based on this Workshop. https://teuteuguy.github.io/amazon-freertos-workshop-docs/labs/04-wifi-provisioning/. (Later we will create the app using the Amplify and Cognito services as mentioned on docs)
I will still, making efforts to accomplish the same goal on V202012.00 as you explained here.
https://github.com/aws/amazon-freertos/issues/3056#issuecomment-802265486
I will keep you posted here. Amazing piece of software. I am enjoying a lot from what you've been teaching over here.
Have a great weekend.

Hi @Yoimer
You could use one of the demo entry function vRunOTAUpdateDemo() or RunCoreMqttMutualAuthDemo() and modify it to spawn a new task and run the other demo entry function in it.
However it should be noted that the OTA update demo uses old MQTT library APIs and it works through a SHIM layer implementation. This means the network interface and connection type used is different between demos and could not be shared. The combined demo will create two separate MQTT connections to the cloud, so the client identifier used should be different for both connections otherwise AWS IoT will reject the older connection with duplicate client identifier.
For provisioning WiFi credentials using BLE you can enable the demo and follow the instructions to provision a WiFi network from app as shown in doc here: https://docs.aws.amazon.com/freertos/latest/userguide/ble-demo.html#ble-demo-wifi
The aws_wifi_connect_task.c will take care of reconnecting to a provisioned network when device is rebooted or current wifi connection is lost.
Please let us know if you have more questions.

@ravibhagavandas Hello. I've come across with an idea. What if I adapt the  mqtt  library present in mqtt_demo_mutual_auth.c for the aws_iot_ota_update_demo.c?
Since the ota demo implements and mqtt version older than the current one running on mqtt_demo_mutual_auth.c, would make sense to add that mqtt libraries and make it compatible for both of them?
Would that way let me integrate ota + coreMQTT demos?
Looking forward for your comments. Thanks in advance.

Hi @Yoimer ,
To update the old OTA demo with the new coreMQTT library, it also requires changes in ota library specifically, you need to change the interface file aws_iot_ota_mqtt.c to adapt to new coreMQTT APIs. Also, you need to guarantee thread safety of the shared MQTT connection by implementing concurrency in your application.
We have a labs repository which uses a MQTT agent  that handles thread safety of a shared MQTT connection between different demo application. The file ota_over_mqtt_demo.c shows how the OTA demo task shares the MQTT connection with other demo tasks. More details can be found in documentation here.
We are working on upgrading this repository to use the new modules, but this gives a reference implementation  to get started.

Hi @Yoimer ,
To update the old OTA demo with the new coreMQTT library, it also requires changes in ota library specifically, you need to change the interface file aws_iot_ota_mqtt.c to adapt to new coreMQTT APIs. Also, you need to guarantee thread safety of the shared MQTT connection by implementing concurrency in your application.
We have a labs repository which uses a MQTT agent that handles thread safety of a shared MQTT connection between different demo application. The file ota_over_mqtt_demo.c shows how the OTA demo task shares the MQTT connection with other demo tasks. More details can be found in documentation here.
We are working on upgrading this repository to use the new modules, but this gives a reference implementation to get started.

@ravibhagavandas Thanks a lot for replying and taking time to consider my idea. I really appreciate your support and the helpful information you're providing here. I am reading it already. Thanks again.

Hello ,
Do you still need help on this topic or this issue can be closed?

Hello ,
Do you still need help on this topic or this issue can be closed?

@pvyawaha Thanks a lot for keeping in touch. Still, we are doing QA tests. When we finish them all, I will close this issue.
Have a wonderful day.

Hi @Yoimer,

@pvyawaha Thanks a lot for keeping in touch. Still, we are doing QA tests. When we finish them all, I will close this issue.

Do you have an update on this? Can we close this issue?

Hi @Yoimer,

@pvyawaha Thanks a lot for keeping in touch. Still, we are doing QA tests. When we finish them all, I will close this issue.

Do you have an update on this? Can we close this issue?

@ravibhagavandas Please, close it for now. Thanks


Added Blockchain Programming Book

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

use the packt link

sure

I have resubmitted the PR by providing the packt. Kindly have a look

I guess it's not really free.


Take any user's best consistency goal and store firebase realtime db

Take any user's best consistency goal and store firebase real-time db.

From here you need to take the goal name and consistency of every user ( which goal consistency is high , that will be taken ) .
Then add on firebase

in this structure ..

I want to work on this issue under JWOC

@GeekLord04  within how many days , you will finish approx time ?

Might complete it within 5-6 days. My last issue is almost complete

ohk


Allow more customization on upload service list

In addition to being able to set filters on local file system stores (see #16) it would be great if we could specify a service by name on upload, e.g.:
archive.update('local_path.txt', upload_to=['s3', 'ftp'])

This would pull service configurations from those in the api.services dictionary and would override the base api._upload_services preferences.

Fixed with #35 - now upload to authority and cache=False


Heart icon lag

Description of issue
There's a delay between when I tap o heart and when I get feedback from the UI
Expected behaviour
Shorter lag between tap and vibrate / animation
Steps to reproduce
Tap on heart icon to select it
Feel tha lag
OS / Browser / Device model
Android Pixel

This doesn't appear to be happening now in latest releases.


WebSocket compression can increase data size, even when this exceeds max frame size

Expected behavior
"Compressing" WebSocket frames with io.netty.handler.codec.http.websocketx.extensions.compression.WebSocketServerCompressionHandler will never increase packet size because, otherwise, there is no way to know when data that is "compressed" to a larger size that will exceed the max frame size.
Actual behavior
"Compressing" WebSocket frames with io.netty.handler.codec.http.websocketx.extensions.compression.WebSocketServerCompressionHandler will never increase packet size when the deflated version happens to be larger than the source.  The can result in protocol violations that close the channel.
Steps to reproduce
Create a WebSocket client and server with compression enabled.  Create a WebSocket frame equal to the max frame size that "compresses" to a size larger than the input and send it from the client.  Send the frame.  The server will close the connection with a protocol violation.
Minimal yet complete reproducer code (or URL to code)
PR fixing this, with tests, forthcoming.  Need to get contributor agreement signed, first.
Netty version
4.1.9
JVM version (e.g. java -version)
Any.
OS version (e.g. uname -a)
Any.

I'd like to fix this.    This is crude, but the connection already dies with a max frame size exception if it's at the boundary, anyway, so at minimum, this would make the failure happen on the sending side, which has more opportunity to prevent it.
Making the WebSocket encoders reject frames that are too large; this is less severe than the first option, and again gets the error back to the sending side, but not a whole lot better.
Add a max frame size parameter to io.netty.handler.codec.http.websocketx.extensions.compression.WebSocketClientCompressionHandler and io.netty.handler.codec.http.websocketx.extensions.compression.WebSocketServerCompressionHandler and thread it through to io.netty.handler.codec.http.websocketx.extensions.compression.PerMessageDeflateClientExtensionHandshaker and io.netty.handler.codec.http.websocketx.extensions.compression.PerMessageDeflateServerExtensionHandshaker, respectively.  (For per-frame encoding, just send uncompressed frames when they grow after compression.)  Use the max size to split frames when the compressed value exceeds the max size.  I need to check to see if already compressed frames can be split, but this might require splitting the message pre-compressing and re-compressing.  If compressed frames can be split, a really intelligent version of this might try to add the extra bytes to the next frame in the message when possible to prevent additional fragmentation.

Please advise.

I guess 1) is good enough ?

@mkw ^^

@mkw did you want to do a PR ?


add periodic sync mode

currently grafana-db-exporter only supports single docker run / cronjob (job) mode, it needs to be evaluated whether the continuous mode mode can be supported, i.e. we should periodically check for changes/track dashboards and upload any changes to the repo
this would have to support:

adding changes to a new branch (the current, only supported, mode)
adding changes to a single branch

Additionally to consider:

adding changes directly to the "X" branch (e.g.: main) - seems like something that shouldn't be supported

mode name to be decided, proposals:
proactive, reactive, continuous, stream, live, watch, dynamic

having slept with it I think continuous mode is the most accurate & self-descriptive

having thought about it I don't think it's worth implementing as the continuous mode would just go to sleep for most of the run time, so it'd be a cronjob that is running continuously
it'd also require architecture, whereas you can just run the exporter every h or so if you really need it
seems like an antipattern - closing

I forgot that docker doesn't support cron-like functionality and people would have to jump through hoops to make it work
The point about this feature not being needed in terms of k8s clusters still stands though

I think considering that most of the time the exporter will sleep, a better name for this mode will be periodic


Grids fix

Fixes to the grid outputting to align with recent changes in COMPAS.

Ah! Amazing, well done Reinhold.  Thank you!  That was on my personal to-do list, but apparently sometimes if I'm lazy then wonderful people like you do solve my problems for me!
(I’m curious to try sampling in physical parameters too… not to build a population with a distribution of physics, but hopefully as an efficient way to explore physics variations.)
(In principle I don’t know whether we should move the COMPAS-specific utilities to being associated with the COMPAS interface, in the COMPAS repository rather than with the statistical parts. But we can talk about code locations later.)
Thank you again,
Stephen

On 10 Nov 2020, at 08:22, Reinhold Willcox<EMAIL_ADDRESS>wrote:
Fixes to the grid outputting to align with recent changes in COMPAS.
You can view, comment on, or merge this pull request online at:
https://github.com/lokiysh/stroopwafel/pull/4 https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flokiysh%2Fstroopwafel%2Fpull%2F4&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250332006|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Ho1X3O6kgcFyaRWk9YvzZIhC9NOD1qX7cMqybuU5y8k%3D&reserved=0
Commit Summary
updated the grid output to match the compas format
updated changes to the interface file based on new changes in compas
File Changes
M stroopwafel/utils.py https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flokiysh%2Fstroopwafel%2Fpull%2F4%2Ffiles%23diff-a3bfa8c932b1bfbf4470eb9f81c7203f0b8b5fb3a39ff1f24eb3cb8efd66fca8&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250332006|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=x%2BXBKLbJunY2VM4XL3fHQ7Kn0esEBBNmw8hQM4tSSI0%3D&reserved=0 (13)
A tests/Reinhold_tests/stroopwafel_rundev.py https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flokiysh%2Fstroopwafel%2Fpull%2F4%2Ffiles%23diff-755f346fdafe0f4dfc0d6603e4f6c4e6c415e3149abf3a099c3e570d317a4cac&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250341991|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=gT2bKDBDW%2FA44y%2BqKj%2FR16Udx65D39Dx0r79BA63ppU%3D&reserved=0 (286)
Patch Links:
https://github.com/lokiysh/stroopwafel/pull/4.patch https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flokiysh%2Fstroopwafel%2Fpull%2F4.patch&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250341991|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OH8otRcw7%2BHCer8B7b7KD4Nma80UCf8dFh5GV8Q4vo4%3D&reserved=0
https://github.com/lokiysh/stroopwafel/pull/4.diff https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flokiysh%2Fstroopwafel%2Fpull%2F4.diff&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250351983|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=etfxeV9I89sKPOs4M8B8agwWKTTTNMY27M4EEuBzjOM%3D&reserved=0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flokiysh%2Fstroopwafel%2Fpull%2F4&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250351983|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3sra2oUKsJOkYHKL7wGWzQq2yljb4mbqjVKiFcmZrDI%3D&reserved=0, or unsubscribe https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAORP4ZZKC3AKKOGKC6SVOITSPDSZXANCNFSM4TQJMGQA&data=04|01|S.Justham%40uva.nl|edb5710939c44851a7fb08d885495319|a0f1cacd618c4403b94576fb3d6874e5|1|0|637405897250361979|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=UZ8Wxmjvx%2B7L%2FEDuSGiSv8jDdDhXUJoNBCYs%2BWZx0w8%3D&reserved=0.

@stellarphysicsandpopulations Oh, Stephen, that's you! I was wondering about that - I think Ilya tagged you in a few COMPAS posts.
Yes, I agree, I was chatting with Floor about that earlier. I think it is much more straightforward to do that now with Jeff's latest changes, but we can discuss the implementation later.
Would you mind reviewing this PR?

Extra comment:
In the end, this function probably wants to either be:
(1) COMPAS-specific (if in the SW distribution)
(2) moved to the COMPAS package, along with the COMPAS-specific interface (if/when I streamline the COMPAS interface), so that COMPAS developers can more easily make sure to keep compatibility by maintaining this.

You mean the file stroopwafel_rundev.py ? Yes, this should absolutely end up in the COMPAS repo. I've been leaving it in SW for now since changes to the interface have been moving in parallel with changes to the source code, but the end goal is to add it to COMPAS defaults/ and replace pythonSubmit.

Just for the record, Floris tested and it seems to work very well. So thanks again, Reinhold.


subscribe to Topics

The app subscribe to the same topics every time it starts(onCreate) Isn't a problem?

There is no unsubscribe call in the code. is unsubscribe from a topic happen automatic when uninstalling an app?

Subscribing multiple times is not a problem since only the initial subscription goes to the server, subsequent subscribe calls are handled locally.
Google Play Services will attempt to unsubscribe the topic on uninstall on Android. However once the app is uninstalled the registration token will eventually be invalid and thus any attempt to send messages to that token will fail, even from the topic servers.

If I have 100,000 users and every user is subscribe to 10 topics, is that mean I got to the 1 million subscription limitation? or I only have 100,000 subscription?

Yes you would hit the current limit, the limit only looks at the number of subscriptions, now users.


fix(template): remove non-existing properties correctly in vue 3 template

What?
This PR removes properties that no longer exist in FieldPluginProvider of the vue 3 template.
Why?
JIRA: EXT-1817
The Jira ticket mentions the changing options, but actually the same problem happened to plugin.data.content too.

How to test? (optional)

Hey Eunjae, I remember when i tried copy pasting these changes, the template example did not work? Could you rebase your branch to match with main and apply it to the new vue3. submodule and test it? In case you do not have time I can also check it :)

Hey Eunjae, I remember when i tried copy pasting these changes, the template example did not work? Could you rebase your branch to match with main and apply it to the new vue3. submodule and test it? In case you do not have time I can also check it :)

Hey @BibiSebi I just tested it's working here. Maybe when you copied it over to your branch, something was different there?


[DOC] Improve java doc for DataSkewRangePartitioner

[x] Any interfaces changed?
no
[x] Any backward compatibility impacted?
no
[x] Document update required?
no
[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
NA, only java doc change
- How it is tested? Please attach test report.
NA
- Is it a performance related change? Please attach the performance test report.
NA
- Any additional information to help reviewers in testing this change.
NA
[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2855/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11115/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3086/

LGTM

LGTM


Real World Sample Application

So, I am searching for a new job and have had some positive leads. Whatever the case, I would be able to work less hours and devote more time to things like this. I really want to get Spider to a usable form (0.4) soon. There isn't that much more to do, I don't think.
Anyway, onto this PR. I think it would be beneficial to consider hacking together a sample application that uses Spider. This would be something that is useful in its own right, contain lots of examples of how to integrate Spider into a codebase, and be a great testing mechanism for us to make sure things work beyond our automated tests (real world testing is always important).
It's not a super high priority, and I'd like to keep things pretty simple. I just wanted to throw the idea out there and see if anyone had any ideas. What php general use application would benefit from graph databases? A micro social network? Some data-analysis package? An innovative wiki? I'm really up for anything. @smolinari this may be something you could help contribute to if you don't feel terribly comfortable with the core.
Just thinking out loud. I'm going to dive back into spider next week.

Thanks for considering me. I am not even close to the point where I need to implement Spider, but I'd like to take a jab at using it for a PoC. It would be a good learning experience too. I'd be using ODB as the backend, since I know the most about it.
I'd like to build a proof on concept for a particular discussion engine.
The problem. Discussions are really bad, when they can't "thread out". Good examples are the comment sections in Facebook or any other "social network". The first attempts to make discussions "threaded" where the old UBB forums, where threads where "subthreaded" and you'd have a tree view of the discussion. Though the clicking through the discussion was a pain in the but.
The newer, more accepted form of threaded discussion uses quoting and a more linear view of the posts, either with infinite scrolling or pagination. However, the quoting causes a lot of replication of text and the discussions don't really thread well that way too.
Sites like Slack or Gitter have a chat like functionality, but absolutely no threading. As soon a few discussions are happening, then the "chat" becomes a really big mess. Slack has the ability to split up a channel into subchannels, but that really isn't threaded discussions either. That is just a categorization.
The solution. Something along the lines of how Google Wave's discussions work.
https://www.youtube.com/watch?v=xBzuuWZPaXc
Or sort of like Rizzoma's discussions - https://rizzoma.com/
The PoC would naturally be very simple, but getting a threaded discussion working through a graph database would be a dream.
Scott

Interesting idea. Let's keep chewing on it and drafting some things out. I like the direction, personally.
I would offer a couple thoughts.
1.) Make heavy use of composer packages and probably a micro-framework like Lumen, Slim, or Silex. No need to create all those components and it would make testing Spider more viable if we could be sure to have the rest of the system supported.
2.) Spider won't really be ready for something like this for a few weeks (hopefully), just keep that in mind.
3.) You say you use Orient, which is fine, but the point of Spider is that any of the supported DBs would work identically (with supported features) through Spider. So, we would want to have a basic graph setup which can be loaded into each of the databases and let the user (through a config value) decide which db to use.

To 3). Ok. I guess I have spider-box to help me out too. :smile:
To the rest. Sounds good. Though, what did you mean by this?

it would make testing Spider more viable if we could be sure to have the rest of the system supported.

Which rest of the system?
Scott

The real world application. For instance, if we build the discussion thing, that also includes Authroization, Web Requests, Templating, etc, etc. The "framework level" code. I am saying it may be best to use established code for all this (like a microframework and composer packages) so the only code we are creating/testing is the application logic itself and Spider.
And, yes, spider-box would be perfect for something like this :smile_cat:

Hey Chris. Hope all is well with you?
March is practically empty on my projects list. I'd like to start on this. How are things with you and getting more done on Spider?
Scott

Hey Chris, @chrismichaels84
How are things going? I will be on vacation in May. I could start some serious work on both spider or this idea. I just need to know where to attack.
Scott

That is great. Sorry. I've started a new job and haven't had time to get to this. But, I think I am going to be able to devote most of my tommorrow to cleaning up spider. Maybe we can chat about direction? I believe you have my email address so we can setup a slack or something.

How about a Gitter channel? https://gitter.im
Scott

Works for me. Anytime tomorrow or next week best?
On Thu, Mar 31, 2016 at 8:48 AM, Scott<EMAIL_ADDRESS>wrote:

How about a Gitter channel? https://gitter.im
Scott
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/spider/spider/issues/115#issuecomment-203948296

I am online tomorrow evening around 19:30 CET, which is 13:30 EST.
Scott

This issue was moved to spider/orb#1


Migrate #[allow(...)] to #[expect(...)]

Objective

Rust 1.81 released the #[expect(...)] attribute, which works like #[allow(...)] but throws a warning if the lint isn't raised. This is preferred to #[allow(...)] because it tells us when it can be removed.
Closes #15059.

Solution
Switch all applicable #[allow(...)] attributes to #[expect(...)] with a reason attribute.
Progress

[x] bevy_ptr
[x] bevy_utils
[x] bevy_reflect
[x] bevy_tasks
[x] bevy_ecs
[x] bevy_derive
[x] bevy_app
[x] bevy_reflect_derive
[x] bevy_asset_macros
[x] bevy_encase_derive
[x] bevy_render_macros
[x] bevy_state_macros
[x] bevy_log
[x] bevy_time
[x] bevy_diagnostic
[x] bevy_transform
[x] bevy_asset
[ ] bevy_input
[ ] bevy_gilrs
[ ] bevy_window
[ ] bevy_winit
[ ] bevy_state
[ ] bevy_render
[ ] bevy_picking
[ ] bevy_core_pipeline
[ ] bevy_sprite
[ ] bevy_text
[ ] bevy_pbr
[ ] bevy_ui
[ ] bevy_gltf
[ ] bevy_gizmos
[ ] bevy_dev_tools
[ ] bevy_internal
[ ] bevy_dylib

Testing

cargo clippy --workspace --all-features

I'm going to put this PR up for adoption. I no longer have the energy to work on it, and there are still a lot of crates left. If you want to adopt this, my workflow looked like this:

Run cargo clippy --workspace --message-format=short
cd into the first crate that raises warnings.
Run cargo watch -c -x clippy until warnings stop appearing.
Run cargo clippy --no-default-features and cargo clippy --all-features for good measure.
Repeat step 1 until there are no more warning.

@BD103 I don't know if I can do the rest of this justice, but I figured I'd at least try to clean up the conflicts, it'd be a crime to see all that go to waste :laughing: #15301


check_availability throws error in visual_paneldates heatmap with enddates

error is in line 121 and arises when passing the dataframe from check_enddates()
this can be seen in the example code of check_availability.py and occurs across notebooks since the update of check_availability, meaning it is probably related to the new calculation of dates.

Believe it was ascribed to the type of the column DataFrame. Previously, Int64 and required np.int64.


Refactor Pull Request and Commit Message Creation Process

Description
This pull request includes a series of updates and refactors to the pull request prompts creation and template. The changes aim to improve the logic of creating prompts, simplify the PR template, and enhance the inclusion of Jira tickets in the PR description.
Changes

Refactored the PR prompts creation logic
Updated the PR template structure for simplicity
Improved the method for creating pull request messages
Enhanced Jira ticket inclusion in pull request descriptions
Removed branch and repository name from prompts

The changes seem ok! My only suggestions is that maybe we could merge some of these commits into one, as most of them reference the same file. WDYT?


Bikeshedding: use timing reporter with cachified

Hey Kent,
that was a great talk at remix-conf and i'm exited that you've chosen to make cachified part of this stack 🤗
The way the timings were taken in the cachified wrapper to me felt a little like woking around the library and I wanted to try if we could model this as a reporter instead.
Let me know what you think.

I'm definitely interested in this! I'll give it a look soon.

Thanks for the feedback Kent! Made it so that the verbose reporter can either be disabled with null or replaced with a custom one.

removed the request option for the wrapper. and the timingReporter is already noop when no timing is passed. So we're good to go here from my perspective. 🚀
Have a wonderful day ☀


Add a login-system

From @Fohlen on November 30, 2015 14:27
Add a login bar into our menu (it should contain a gravatar-driven profile picture).
Login should be based on OpenID (OAuth-driven), which is supported by F3.
Members from Github with a specific OAuth ID (we can add a team.json adjustment) should be able to create a markdown patch with a WYSIWYG editor from the website.
This would come handy for many members to productively contribute to the blog.
In further development I'd like to use this technique to offer access via server-side OAuth, which would give us possibilities to create a statistical tracker (and whatsoever we like).
Copied from original issue: inexor-game/website#27

This should not be necessary on the main site.
Logins are handled by:

Git and GitHub in terms of the content
Disqus in terms of comments
OAuth for repositories, competitive (however, this is not part of the main site)

At least not necessary for now. I guess that will change in the future.


Update status and log for AWS Batch jobs

@magland
It seems we're not updating the status for Batch jobs.
This job was successfully submitted, but failed internally (volume mount error inside the running container). From AWS Batch console and boto3 client I can get the failed status and error log, but this is not being passed forward to Dendro.

Yes, I agree! This will be important to add.
Right now the process launched by the controller is completely detached from the controller, and I like it this way. That way we can stop and start the controller without worrying about it affecting the running processes. And it just makes things a lot cleaner over all. But the downside is that if the subprocess crashes or fails, then that information is not communicated back to the controller, and so there's no way to update the status or the console output.
There are a lot of processes involved here. So we'll need to come up with a strategy for capturing the status/console at all the various levels.
In the case of local processing we have
controller -datached-> singularity command -> parent job process (in container) -> child job process (in container)
In the case of slurm we have
controller -detached-> srun command -> singularity command -> parent job process (in container) -> child job process (in container)
In the case of AWS Batch we have
controller -detached-> [some command??] -> AWS batch spins up the container -> parent job process (in container) -> child job process (in container)

maybe related, when I restarted the compute resource, it crashed with this error track:
Loading app https://github.com/scratchrealm/pc-spike-sorting/blob/main/kilosort2_5/spec.json
  awsBatchJobQueue: DendroBatchStack-job-queue | awsBatchJobDefinition: kilosort25-dendro-jd
  3 processors

Reporting the compute resource spec
Getting pubsub info
Starting compute resource
Starting job f11943ec kilosort2_5
Error in processor put api request for https://dendro.vercel.app/api/processor/jobs/f11943ec/status; 500 Server Error: Internal Server Error for url: https://dendro.vercel.app/api/processor/jobs/f11943ec/status
Traceback (most recent call last):
  File "/home/ec2-user/dendro/python/dendro/compute_resource/JobManager.py", line 97, in _start_job
    return _start_job(
  File "/home/ec2-user/dendro/python/dendro/compute_resource/_start_job.py", line 47, in _start_job
    _set_job_status_to_starting(
  File "/home/ec2-user/dendro/python/dendro/compute_resource/_start_job.py", line 28, in _set_job_status_to_starting
    resp = _processor_put_api_request(
  File "/home/ec2-user/dendro/python/dendro/common/_api_request.py", line 148, in _processor_put_api_request
    resp.raise_for_status()
  File "/usr/lib/python3.9/site-packages/requests/models.py", line 943, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://dendro.vercel.app/api/processor/jobs/f11943ec/status
Failed to start job: 500 Server Error: Internal Server Error for url: https://dendro.vercel.app/api/processor/jobs/f11943ec/status


Upgrade pulumi-terraform-bridge to v3.88.0

This PR was generated via $ upgrade-provider pulumiverse/pulumi-acme --kind=bridge --target-bridge-version=latest.

Upgrading pulumi-terraform-bridge from v3.86.0 to v3.88.0.

Superseded by #69


Permission issues

Hi koekeishiya!
First of all thanks for your nice wm's.
Tried to move on from kwm to your new project. But I am stuck. Installed via macports copied over the configs, gave the correct permissions.
When I run chunkc, I get the following output:

chunkc: connection failed!

Checking the /tmp/chunkwm.err file, I get the following output:

sh: /Users/jonas/.chunkwmrc: Permission denied

Pretty sure the permussions are sufficient (set to 644)...
Thanks, Jonas

You need the bash scripts to be executable. Mine is set to 755.
This goes for both the .chunkwmrc and .chunkwmtilingrc

This might need clarification in the README, it tripped me up as well. Unusual for dotfiles to be executable.
Also the example .chunkwmtilingrc in the repo is actually named .chwmtilingrc

Also the example .chunkwmtilingrc is actually named .chwmtilingrc in the repo

I'm aware of this, but the install instructions states the name it needs upon execution.

Unusual for dotfiles to be executable.

I figured this would be self-explanatory given that

the config file is also a bash script

Well that worked. How could I miss that point -.- But maybe really mention that these are scripts rather than config files :)

I personally think that it should be pretty clear already. It is mentioned twice in the configuration part of the readme, and the first line of both config files is #!/bin/bash

I was expecting that would be sourced not executed.


Update MusicStore.sln to reference csproj files

dotnet core migration from project.json/xproj to csproj seems incomplete, sln file was still referencing xproj files

Thanks!


What is the purpose of this script?

https://github.com/apache/infrastructure-pelican/blob/64bf5b809382b168789166740a47b187b472ce74/devtest/grab.sh#L3

Greg used this in development of buildsite.py

Can it be deleted then?

No. I intend to keep/improve the script to do large-scale testing of the pelican workflow.


stats: add checks for drop reason counters - v2

Previous PR: https://github.com/OISF/suricata-verify/pull/1328
Changes from previous PR:

fix wrong min-version: 1 pointed out by Jason

Related to:
Related to:
https://redmine.openinfosecfoundation.org/issues/6230

@jufajardini does this need a rebase ?

Rebased with https://github.com/OISF/suricata-verify/pull/1406


add getSome(count) method

Implement a function which returns an array of quotes with given length.

console.log(movieQuote.getSome(10)); // get an array of 10 quotes.
console.log(movieQuote.getSomeRandom(10)); // get an array of 10 random quotes.

I will be making a pull request.

fixed in pull request #52


Switch to Fetch

Switch to the built-in fetch and update all the appropriate modules. Still needs to be tested based on what methods still work in the current version of Noblox.
Updates ESLint and minimum version to Node.js V18 (the first version introducing fetch natively)
Updates uploadItem/uploadModel/uploadAnimation to their new endpoint.

Damn bout time

Going to go for a more gradual change - moving on a method-by-method basis to fetch. Feel free to discuss in discord


Support customizing timestamp, level labels.

It would be nice to have the ability to customize the label for the timestamp field that includeTimestamp automatically sets (or any other preset field). This would be useful for anyone who wants to maintain a consistent format with other logs that are being sent to loggly from non-angular sources.
This could easily be supported by adding .labels function that accepts an object of label overrides. I'm happy to send a PR if this is approved.
logger
    .includeTimestamp(true)
    .labels({
        timestamp: 'dt',
        level: 'lvl'
    });

Alternatively, you could add support for specifying functions as fields so that users could add the timestamp themselves, but that leads to the possibility of having js errors in your logging. You could even bind the log context to the functions to give them access to some log information like the log level. Happy to send a PR for this too.
`logger
.fields({
ts: function() { return (new Date()).toISOString() }
lvl: function() { return this.level }
});

@jaketodaro I like this approach.  My first thought was to add a second (optional) argument to includeTimestamp, but I like the fact that your approach allows cleanly modifying any of the labels.
If you want to do a PR for it, go ahead.  (Make sure you target develop)

Fixed via #52


Updating StartAskingForBalance

            I've changed the logic for balance exploration using
            BIP44 standard. Also split the method in order to
            improve readbility and testing. I've deleted the
            environment variables for max address to fetch on each
            wallet, also update the compoenents and files those
            variables are involved.

closing for now

Changed to https://github.com/rsksmart/2wp-app/pull/274


Added Ali Parsai's video on mutation testing in industry + some cleaning up

Change summary:

Added a video
Updated the link to LittleDarwin article (now it's a direct link to pre-print)
Cleaned up formatting a bit

Thanks!


Reenable kudzu.

About the PR

Since spreader code underwent a pretty massive rewrite recently, it's fair to say that it's pretty likely that this bug got fixed. Even if it didn't, nobody can reproduce this locally so turning it back on is really the only way to tell.
the joys of playtesting.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

LE CHANGELOG
:cl:

add: Kudzu has been reenabled.

i approve


Math errors

From nexus:
I noticed another issue while looking at the logs, mod description, and rules file. Dunno if you'd want this as a separate bug report or not, but it seems that LootMagnet has a small math error in picking values from the RollupMRBValue array. My company is rated 4 stars, and with MRB ratings going 0 to 5 stars that should make it the fifth value or 180,000, but LootMagnet has been using the fourth value, 130,000, instead.
Edit: Also, it seems like weapons and mech parts aren't having their Claimed Salvage values properly reflected due to increased quantities. 7 medium lasers shows up as 60k not 420k, and I saw the same issue with the Vulcan pieces where a "QTY: 2" has the same Claimed Salvage value as a single piece. On the other hand 21 heat sinks show up as 630,000 Claimed Salvage, not 30,000.

I am seeing the same problem.  Am MRB == 3 and Allied with my employer, but what shows up in the logs is:  At contract start, Player has MRB:2  Employer:(Rasalhague) EmployerRep:HONORED / EmployerAllied:False

I am seeing the same problem.  Am MRB == 3 and Allied with my employer, but what shows up in the logs is:  At contract start, Player has MRB:2  Employer:(Rasalhague) EmployerRep:HONORED / EmployerAllied:False


Supports for exporting CornerNet to ONNX with dynamic shapes and comparable performance

Hi, This implementation supports for exporting CornerNet to ONNX with dynamic shapes, achieving comparable performance (e.g. 40.4 vs 40.6 for onnxruntime and pytorch respectively, with no test-time flip of this config).
Note this PR is relied on customized operations implemented in previous PRs, involving mmcv::cummax, (or mmcv::CornerPool for torch version lower than 1.5,0) and mmcv::SoftNonMaxSuppression.
The difference between pytorch and exported onnx model mainly comes from the handle of regression coordinates relied on border offset. Since RandomCenterCropPad is done on CPU with numpy and it's not dynamic traceable when exporting to ONNX, thus border does not appears as key in img_meta. As a solution, the handle of border is moved to the postprocess after finished exporting to ONNX, which is handle in model_wrappers.py. The performance affected between torch and exported onnx model might be ignored.

@v-qjqs Hi, does this PR depend on mmcv PR#1010? If so, you could mention this info in the PR description.

@v-qjqs Hi, does this PR depend on mmcv PR#1010? If so, you could mention this info in the PR description.

Yes, it has been mentioned.


[LiquidWeb] Filling in shared blanks

Replacing some shared server question marks with numbers.
New customers signing up for shared servers should be able to request a server with one of those version.

Once this PR is merged in then we can also set #279 to solved!


Node: Optimize test utility promises

Issue link
This Pull Request is linked to issue (URL): https://github.com/valkey-io/valkey-glide/issues/2590
Checklist
Before submitting the PR make sure the following are checked:

[X] This Pull Request is related to one issue.
[X] Commit message has a detailed description of what changed and why.
[X] Tests are added or updated.
[ ] CHANGELOG.md and documentation files are updated.
[X] Destination branch is correct - main or release
[X] Commits will be squashed upon merging.

It seems that the test execution time has been reduced by about 2 minutes compared to the most recent main branch.

Thanks. Could you merge it please?