[Snyk] Upgrade @alaskaairux/icons from 4.8.3 to 4.15.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @alaskaairux/icons from 4.8.3 to 4.15.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 13 versions ahead of your current version.
The recommended version was released 2 months ago, on 2022-07-25.

Release notes

Package name: @alaskaairux/icons

4.15.0 - 2022-07-254.15.0 (2022-07-25)
Features

icon: add qr icon #131 (cc31cd7)

4.14.0 - 2022-06-184.14.0 (2022-06-18)
Features

icon: add new tail icon for Air Tahiti Nui (cea309b)
metadata: add TN meta data (fff3f8e)

4.13.0 - 2022-05-054.13.0 (2022-05-05)
Features

icon: add sparkle-stroke icon #118 (afd3442)

4.12.0 - 2022-04-294.12.0 (2022-04-29)
Features

support TypeScript #121 (6016704)

4.11.1 - 2022-04-224.11.1 (2022-04-22)
Bug Fixes

sparkle stroke: remove offending icon #118 (c756dbf)

4.11.0 - 2022-04-224.11.0 (2022-04-22)
Features

upsell: add new icons #115 (733c3cc)

4.10.2 - 2022-04-144.10.2 (2022-04-14)
Bug Fixes

perf: update aa tail icon to be less complex (7eb5ffc)

4.10.1 - 2021-12-104.10.1 (2021-12-10)
Bug Fixes

npmignore: remove unnecessary resources from package (b1e12d4)

4.10.0 - 2021-12-094.10.0 (2021-12-09)
Features

performance: update generate.js build step to include svgo to optimize svg output (dc7b3bc)

4.9.2 - 2021-11-294.9.2 (2021-11-29)
Bug Fixes

node: update engine version reference (145ab1b)

4.9.1 - 2021-11-12

4.9.0 - 2021-11-02

4.8.4 - 2021-08-20

4.8.3 - 2021-07-28

    from @alaskaairux/icons GitHub release notes

Commit messages

Package name: @alaskaairux/icons

603c36f chore(release): 4.15.0 [skip ci]
cc31cd7 feat(icon): add qr icon #131
71364e3 build(deps): bump shell-quote from 1.7.2 to 1.7.3
0374db4 chore(release): 4.14.0 [skip ci]
fff3f8e feat(metadata): add TN meta data
cea309b feat(icon): add new tail icon for Air Tahiti Nui
4e42993 build(deps-dev): bump semantic-release from 17.4.7 to 19.0.3
52d4467 build(deps): bump semver-regex from 3.1.3 to 3.1.4
71ee6cf build(deps): bump hosted-git-info from 2.8.8 to 2.8.9
520ea7d chore(release): 4.13.0 [skip ci]
e09c8eb chore(deps): update dependencies
afd3442 feat(icon): add sparkle-stroke icon #118
bd6a2ed chore(release): 4.12.0 [skip ci]
6016704 feat: support TypeScript #121
00fd0ca docs(readme): update use docs
3e694b3 chore(release): 4.11.1 [skip ci]
c756dbf fix(sparkle stroke): remove offending icon #118
61c3321 chore(release): 4.11.0 [skip ci]
733c3cc feat(upsell): add new icons #115
e22f52c chore(release): 4.10.2 [skip ci]
7eb5ffc fix(perf): update aa tail icon to be less complex
fe4be07 chore(deps): update packages
f99e001 build(deps): bump minimist from 1.2.5 to 1.2.6
37099c5 chore(release): 4.10.1 [skip ci]

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add more baseline bots

In addition to the trout_bot, would it be possible to add the baseline bots, Oracle and Marmot mentioned on the challenge webpage?

You can challenge any connected bot (that isn't already busy with too many games)! Occasionally, the servers get restarted, and the usual baseline bots remain offline for a while.

I'm sorry that I wasn't clear, I was referring to adding the code for the baseline bots to this repo under /reconchess/bots like how to code exists for trout. This allows for users to play against these bots locally.
I understand that the code for bots like Strangefish2 and others would be closed source, but would it be possible to share the code for the baseline bots?

Oh, I see! Yes, several bots authored by APL employees are under review for public release. It is a slow process, but eventually Oracle and StrangeFish2 will be available. These will not be included in the reconchess library, but will be accessible from their own repos.


revert: rollback commits to build v3.9.0 tags

Describe what this PR does
This commit reverts a couple of changes from release v3.9 branch.
Since template changes were not done pointing image tag to 3.9-canary, v3.9.0 images were
overwritten.
This revert is done in order to restore v3.9.0 tagged image.
https://quay.io/repository/cephcsi/cephcsi?tab=history

This will be followed by another pr to restore the commits and point templates to 3.9-canary.

I would suggest not to rollback now; we made a mistake not to revert back immediately, let live with it and update the release branch to build canary images.

okay, sounds good to me :disappointed:


Sending Documents Larger than 100MB with Baileys API

I am trying to use the Baileys API to send documents, but I'm running into issues when dealing with files larger than 100MB. Is it possible to send documents larger than 100MB using the Baileys API, and if so, how can I do it?

Please help me same problem


Floating label support for material theme

Hi,
is it possible to implement floating label support for material theme?
something similar to what is implemented in http://www.material-ui.com/#/components/select-field
I'm using that material-ui React library but planning to replace the select component with react-selectize

It can be done by keeping the placeholder element in the DOM, even if the search field is updated, this would require changes to ReactSelectize.ls i.e. a way to customise the component based on the theme prop.

Hi @yelmu  !! Did you achieve the floating label?


Ut telnet handler adapter test

What is the purpose of the change
add test for TelnetHandlerAdapter
see more detail from #8257
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8258 (33997c0) into master (11e15f2) will decrease coverage by 0.15%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #8258      +/-   ##
============================================
- Coverage     61.24%   61.09%   -0.16%
  Complexity      489      489
============================================
  Files          1090     1090
  Lines         43963    43918      -45
  Branches       6420     6388      -32
============================================
- Hits          26924    26830      -94
- Misses        14063    14114      +51
+ Partials       2976     2974       -2

Impacted Files
Coverage Δ

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-20.69%)
:arrow_down:

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
79.66% <0.00%> (-6.78%)
:arrow_down:

...apache/dubbo/common/config/ConfigurationUtils.java
61.29% <0.00%> (-6.46%)
:arrow_down:

...moting/transport/netty4/NettyEventLoopFactory.java
30.00% <0.00%> (-6.37%)
:arrow_down:

...mmon/threadpool/support/AbortPolicyWithReport.java
80.76% <0.00%> (-5.77%)
:arrow_down:

... and 37 more

Continue to review full report at Codecov.

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

Thanks for your contributions. Please also pick these changes to 3.0 branch.

Thanks for your contributions. Please also pick these changes to 3.0 branch.

OK! thx!


server.py#MyHandler.t   variable

Hello developers.
sorry my little write english.
Q1, server.py#MyHandler.t   variable non cler
HTTP request  t variable endless appends.
use function code search　server.py)
MyHandler#do_POST
MyHandler#ret_result
Q2,release code print function use?
suggest) server.py files addoptions -loglevel n   (ex n=numelic positive number)
□environment
JP Win10 IE11 (11.576.14393)
□run script options
cd /d %~dp0
cd PaintsChainer
python server.py -g -1
thank you for reading.

yeah it was debugging code and should be removed later ...
あ、あと英語が苦手なら日本語でも大丈夫ですよ。

server.py#log_t  thank you taizan.
Closed isses.


Own (Build Your Template) import not working.

Neither for older ones nor for new ones just exported by "demogen-code" new site.

Fixed importer issue. Hence closing


refactor: adjust sentry alerts

This PR resolves PHIRE-548
Description
Adjusting the fetchNotificationsInfo failed https://artsynet.sentry.io/issues/4594942792/events/936f079ddb4d4a6dbaca107f3e17bcb7 and fetchCurrentUnreadConversationCount failed messages to include the exception since it is not visible on sentry

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

adjust sentry alerts - gkartalis

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (adjust sentry alerts - gkartalis)

  Generated by :no_entry_sign: dangerJS against 7eb415a23794c0fa2629bc22f9acb5b6893a248d


C# enable special_status_message interop test

Is this a dup of https://github.com/grpc/grpc/pull/18837?

Not quite, this one enables the interop test for Grpc.Core (and not Grpc.AspNetCore.Server)

Known failures:
https://github.com/grpc/grpc/issues/18608


[Bowling] Add edge case with fill balls in a last-frame strike

The previous test does not quite capture the behavior.
If the first fill fill is a non-strikes, then the total fill-ball score
must be less than 10.
But, if the first fill ball is a strike, then the total fill-ball score
must be less than 20. Because that first fill-ball strike resets the
pins.
I had what I thought was a working implementation but it totally missed
the 2nd case. Adding a test to cover that case.

I'm also wondering about adding
 }, {
      "description": "Two bonus rolls after a strike in the last frame can have a strike on the second roll",
      "rolls": [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 6, 10],
      "expected": -1

To check for logic that looks for either of the fill balls being == 10 and then checking that the fill score is <= 20

Case that is currently added 10, 10, 6 seems good.
You might think 10, 6, 10 seems to overlap with our existing 10, 5, 6, so it would only fail if someone is special-casing 10. Admittedly, someone might, given the before test. Given that we can think of an implementation that would fail it that it seems like someone could write, seems good to add it, I think.

10,6,10 definitely failed for me. I had some code that checked if any of the fill balls were a 10. And if so, it checked that the total of the fill balls was less than 20. That was incorrect.

Oh dear I've made a mess of this :cry: sorry!

@IanWhitney can you make another PR for this? I can't work out how to re-apply this PR through github.
I merged this PR, then saw that it caused #416 to have conflicts and thought if I merged that one first I could merge this one without conflicts, so I reverted this merge and applied #416 but now I cant seem to re-apply this one.

I think I've recovered this now, and don't need @IanWhitney to make another PR.
Sorry everyone for the trouble. :frowning_face:


fix order of chained bijector

tfb.Chain applies bijectors from right to left. When it comes to the scale parameter of the truncated normal posteriors, the shift was being applied before the exp.

Codecov Report

Merging #122 (dcda8ff) into main (28975fc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   78.82%   78.82%
=======================================
  Files          49       49
  Lines        2135     2135
=======================================
  Hits         1683     1683
  Misses        452      452

Flag
Coverage Δ

unittests
78.82% <ø> (ø)

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

Impacted Files
Coverage Δ

careless/models/merging/surrogate_posteriors.py
89.01% <ø> (ø)

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


Merging maps within structs

Considering this example
type Test struct {
      A map[string]string
      B string
      C string

}

func test() {
      foo := new(Test)
      foo.B = "one"

      bar := new(Test)
      bar.A = map[string]string{"biz": "baz"}
      bar.B = "two"
      bar.C = "three"

      mergo.Merge(foo, bar)
}

What am I doing wrong to be getting this error?
Adding This line solves the problem and merges happen as expected. But its not ideal.
Foo.A = map[string]string{}
panic: assignment to entry in nil map

goroutine 1 [running]:
reflect.Value.SetMapIndex(0x8123380, 0x184382a8, 0xd5, 0x8122d80, 0x1840a178, 0x58, 0x8122d80, 0x1840a180, 0x58)
        /usr/local/go/src/reflect/value.go:1440 +0x21a
github.com/imdario/mergo.deepMerge(0x8123380, 0x184382a8, 0xd5, 0x8123380, 0x184382b8, 0xd5, 0x18436480, 0x1, 0x0, 0x0)
        /home/vagrant/go/src/github.com/imdario/mergo/merge.go:56 +0x7b3
github.com/imdario/mergo.deepMerge(0x813e540, 0x184382a0, 0xd9, 0x813e540, 0x184382b0, 0xd9, 0x18436480, 0x0, 0x0, 0x0)
        /home/vagrant/go/src/github.com/imdario/mergo/merge.go:36 +0x9a5
github.com/imdario/mergo.Merge(0x811b080, 0x184382a0, 0x811b080, 0x184382b0, 0x0, 0x0)
        /home/vagrant/go/src/github.com/imdario/mergo/merge.go:96 +0x1bb
main.test()
        /home/vagrant/go/src/github.com/Jmeyering/zealot/main.go:38 +0x12e
main.main()
        /home/vagrant/go/src/github.com/Jmeyering/zealot/main.go:41 +0x28

goroutine 2 [runnable]:
runtime.forcegchelper()
        /usr/local/go/src/runtime/proc.go:90
runtime.goexit()
        /usr/local/go/src/runtime/asm_386.s:2287 +0x1

goroutine 3 [runnable]:
runtime.bgsweep()
        /usr/local/go/src/runtime/mgc0.go:82
runtime.goexit()
        /usr/local/go/src/runtime/asm_386.s:2287 +0x1

goroutine 4 [runnable]:
runtime.runfinq()
        /usr/local/go/src/runtime/malloc.go:712
runtime.goexit()
        /usr/local/go/src/runtime/asm_386.s:2287 +0x1
exit status 2

Sorry, I didn't see your issue. Probably I could check it in the next weeks to improve the way Mergo works in this case.

I closed because my example had a problem that ended up being a case of me not RTFM.
However I did have a question regarding deep merging slices.
Example would be having two structs with a field of []string and instead of completely overwriting, appending values on to do a true deep merge.
Thoughts on this?

That's a nice idea but it would be confusing due the way of work of Mergo. It works on zero values so appending values isn't exactly the same.
I don't know right now how to handle this good idea in a proper and non-confusing way.


WARN  Require cycle

 WARN  Require cycle: node_modules/react-native-applovin-max/src/index.js -> node_modules/react-native-applovin-max/src/AppLovinMAXAdView.js -> node_modules/react-native-applovin-max/src/index.js
I there anyone tell me why i always get the following warning every time i run my app ?
Is there anything I missed or what I can do to fix it?
"react": "17.0.1",
"react-native": "0.64.2",
"react-native-applovin-max": "^2.2.0",

Hey, thanks for reporting it. We'll look into it.

Hi @jacow this warning is on our end, but to resolve it we would have to change our API. This warning shouldn't affect your integration, so we are not going to make this change for now.
Let us know if you run into other issues!

Hi, i found new warn and error on android after updating to newest version applovin and react native 0.65.1

 WARN  `new NativeEventEmitter()` was called with a non-null argument without the required `addListener` method.
 WARN  `new NativeEventEmitter()` was called with a non-null argument without the required `removeListeners` method.
 WARN  `new NativeEventEmitter()` was called with a non-null argument without the required `addListener` method.
 WARN  `new NativeEventEmitter()` was called with a non-null argument without the required `removeListeners` method.
 WARN  Require cycle: node_modules/react-native-applovin-max/src/index.js -> node_modules/react-native-applovin-max/src/AppLovinMAXAdView.js -> node_modules/react-native-applovin-max/src/index.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  `new NativeEventEmitter()` was called with a non-null argument without the required `addListener` method.
 WARN  `new NativeEventEmitter()` was called with a non-null argument without the required `removeListeners` method.

Just released v2.3.1 with a NPE check. Feel free to re-open issue if issue persists.
Feel free to ignore the warning as well (or feel free to submit a PR with a fix). Thanks!


sof-firmware: add new files from 2024.09

The sof-ipc4-lib folder which is needed for audio hardware on Lunar Lake processors was missing from the derivation's output. This PR copies it in like the other folders.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/lunar-lake-support/54374/1


MGMT: Angular 5 Form Fix

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

Coverage remained the same at 45.791% when pulling 12b5b08f6c868136bd4295dded8212dbd8cf1642 on Unicon:mgmt-ng-5-fix into 399b5f3c1ac48777a9593b68cdb366811fab7364 on apereo:master.


[BUG]: relational query doesn't work

What version of drizzle-orm are you using?
0.26.1
What version of drizzle-kit are you using?
0.18.1
Describe the Bug
My schema files
tables.ts
export const tables = pgTable("tables", {
  id: uuid("id").primaryKey().defaultRandom(),
  number: integer("number").notNull(),
  createdAt: timestamp("created_at").defaultNow().notNull(),
  updatedAt: timestamp("updated_at").defaultNow().notNull(),
})

export const tablesRelations = relations(tables, ({ many }) => ({
  sessions: many(sessions),
}))

sessions.ts
export const sessions = pgTable("sessions", {
  id: uuid("id").primaryKey().defaultRandom(),
  tableId: uuid("table_id")
    .notNull()
    .references(() => tables.id),
  createdAt: timestamp("created_at").defaultNow().notNull(),
  updatedAt: timestamp("updated_at").defaultNow().notNull(),
})

export const sessionsRelations = relations(sessions, ({ one, many }) => ({
  table: one(tables, {
    fields: [sessions.tableId],
    references: [tables.id],
  }),
  orders: many(orders),
}))

My API route
export async function GET() {
  const result = await db.query.sessions.findFirst({
    with: {
      table: true,
    },
  })

  return NextResponse.json(result)
}

It returns an error quoting
error rendering: Error: Relation tables not found

Expected behavior
No response
Environment & setup
My db setup
import { env } from<EMAIL_ADDRESS>import { drizzle } from "drizzle-orm/node-postgres"
import { Pool } from "pg"

import * as schema from "./schema"

const pool = new Pool({
  connectionString: env.DB_URL,
  ssl: true,
})

export const db = drizzle(pool, { schema })

Are you using a monorepo?

Are you using a monorepo?

Nope, just a Nextjs app.
Although, I have my schema as multiple files, and export it through an index.ts file inside the schema folder.

So I have figured out why it wasn't working for me
src/drizzle/schema/users.ts
export const users = pgTable(...);

export const usersRelations = relations(...);

src/drizzle/schema/index.ts
import * as users from './users';

const schema = {user} // this causes the error because the users and relations is inside another object

const schema = {...user}; // this fixed the above issue

Problem
Then I have to spread everything inside schema which doesn't look good and also annoying to do.
Am I doing it wrong? Is there a better way to implement this?
I still want to have separate schema files, so that its easy to organize.

So I have figured out why it wasn't working for me
src/drizzle/schema/users.ts
export const users = pgTable(...);

export const usersRelations = relations(...);

src/drizzle/schema/index.ts
import * as users from './users';

const schema = {user} // this causes the error because the users and relations is inside another object

const schema = {...user}; // this fixed the above issue

Problem
Then I have to spread everything inside schema which doesn't look good and also annoying to do. Am I doing it wrong? Is there a better way to implement this? I still want to have separate schema files, so that its easy to organize.

you can probably do
export * from './users'

Okay, so I have a multi file setup like 20 Tables, and how am I supposed to import them into the schema option? I'm a bit lost.  I couldn't make it work for the past 5 Hours.
It tried it with:
`ts
let schema= {
Table1,
Table1Relations
....
}
const db = drizzle(connection, {schema, mode:"default"} );
`
Because it said can use schema option only in default mode or plantescale.

Okay, so I have a multi file setup like 20 Tables, and how am I supposed to import them into the schema option? I'm a bit lost. I couldn't make it work for the past 5 Hours. It tried it with: `ts let schema= { Table1, Table1Relations .... }
const db = drizzle(connection, {schema, mode:"default"} ); `
Because it said can use schema option only in default mode or plantescale.

You can refer to my comment above


using Dataloader to query InfluxDB

Hi, I'm trying to make use of DataLoader option in my not so common configuration:
I have two resolvers: first one queries Mongo for a set of Ids of variable length, second one gets those Ids through the parent object and then queries InfluxDB. An array of Ids gets converted to a single string Influx query which returns aggregated result, so the payload is a single value rather than array with the same set of keys.
Expectedly, graphql-out node complains that resulting array differs in length from array of keys and refuses to parse the payload.
Is there a way to handle such situation with Dataloader or I should find another approach?

hi @chemmex you would need to return the same length as the parent array. I usually either use Jsonata or a function to iterate through the results coming from your database, then ensure that you return something for each item in the parent array.
This is how Dataloader works at current implementation which does not use an Id field per sa . However generally speaking for each parent object, a response object is required. Hope this makes sense

@chemmex can I close this issue now?

Yes, sure. Though I am wondering how I can construct the function to fake the results for GraphQL-out node while keeping my aggregated result. Return N copies if the aggregate value?

@chemmex you got to share examples of what the data structure look like. you will need to use a function node or a change node to build the output structure in the required format. This is not a limitation of the node itself or Dataloader, this is how GraphQL requires it in order to build the return back to the client.


Replace findUrlFactory with findUriFactory for Psr17FactoryDiscovery

https://github.com/php-http/discovery/blob/master/src/Psr17FactoryDiscovery.php#L125-L135
    /**
     * @return UriFactoryInterface
     *
     * @throws Exception\NotFoundException
     *
     * @deprecated This will be removed in 2.0. Consider using the findUriFactory() method.
     */
    public static function findUrlFactory()
    {
        return static::findUriFactory();
    }

Sorry, this change is from php-http/discovery 1.11.0 .
https://github.com/php-http/discovery/pull/181

I think there is no problem in bumping the minimum required version to 1.11, if it makes it easier to then also support the next major :wink:

Thank you, I actually think so too 😂
May you help me re-run the CI workflows check?

Thank you for the contribution!


[ Feature Request ] useSmoothScrolling

For a project I was doing I wanted all my users to have a nice scrolling experience - like macOS users have when using native hardware (magic mouse, trackpad).  It's always bothered me how rough it can feel on windows or using a 3rd party mouse.  So I wrote this action and thought I would see if it's something people are interested in.  I'm not very familiar with Svelte-Legos, so I didn't want to just fork and open a pull request out of nowhere. Was sent here from a different library project when I asked if they were interested in the action.
/* helper */
function clamp(num: number, min: number, max: number): number {
    return Math.min(Math.max(num, min), max);
}

/* useSmoothScrolling */
interface SmoothScrollOptions {
  friction?: number;
  maxSpeed?: number;
  deadZone?: number;
}

//friction around 0.94-0.95 feels the best, imo (behaves oddly outside of 0.9 to 0.96)
//lower max speed does weird things if users mouse wheel is set to scroll a lot of lines at once
//deadZone is to prevent run away scrolling from small scroll movements
export default function useSmoothScrolling(node: HTMLElement, params: SmoothScrollOptions) {
    const {friction = 0.94, maxSpeed = 60, deadZone = 0.5} = params;

    //todo: map 1-100 to 0.9 to 0.96 to make friction more readable
    let clampedFriction = clamp(friction, 0.9, 0.96);

    let velocity = 0;
    const wheelHandler = (e: WheelEvent) => {
        velocity += e.deltaY * 0.1;
        velocity = clamp(velocity, -maxSpeed, maxSpeed);
    };

    const animationHandler = () => {
            if (Math.abs(velocity) > deadZone) {
        velocity *= clampedFriction;
        node.scrollTop += velocity;
      } else {
        velocity = 0;
      }
      frameId = window.requestAnimationFrame(animationHandler);
    };

    node.addEventListener('wheel', wheelHandler, { passive: true });
    let frameId = window.requestAnimationFrame(animationHandler);

    return {
      destroy() {
        node.removeEventListener('wheel', wheelHandler);
        window.cancelAnimationFrame(frameId);
      }
    };
}

Link to Gist
If it's something people are interested in I'm happy to refactor it and make a more robust implementation.

Been without internet for a while (Army stuff for upcoming deployment), but I'll get something put together.  Thanks!


I made a Kindle edition of the web documentation

https://github.com/danchoi/kindlefodder
It's under "Frontend Docs Bundle". I hope it's useful. Cheers, Dan

Neat -- I'd love it if you could add a link to your documentation on the Backbone wiki ... as long as you're planning on keeping it up to date...

I can't guarantee that it will be up to date yet. For that I will have to write an automated build process that updates all the ebooks from their sources periodically. But that will be implemented, eventually.


Clean up mapped tenants after a CloudManager is destroyed

Tenants created by cloud tenant mapping are not destroyed when their provider is destroyed, which prevents tenant mapping from working if the provider is readded with the same name. This PR causes the mapped tenant tree to be destroyed along with the provider.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1547740

@agrare do you know who could review this?

@mansam could you just add a :dependent => :destroy to the has_one  :source_tenant and let cascade deletion take care of the rest?

@agrare I'll give that a shot, I hadn't considered it.

Hm okay so you'd have to have some before_destroy to clear the sub-tenants first, and there isn't an actual relation for the sub tenants so I was hoping we could dependent destroy those as well but I guess not.

@miq-bot add_label hammer/yes

@agrare no worries, I figured you'd get to it eventually :) thanks for the merge!


Support Topic Level ConsumeQueue/BatchConsumeQueue

Based on PR #3671, I hope that can choose to use ConsumeQueue or BatchConsumeQueue at the Topic level.

When the user creates a Topic, specify the Queue type (Single/Batch), ConsumeQueue uses dense index, and BatchConsumeQueue uses sparse index, so as to meet the needs of different scenarios in the same cluster.

I'm working on it.

This is a very impressive optimization we have discussed two years ago, pls come on.

The pr #3712 may solve this issue.
https://github.com/apache/rocketmq/pull/3712


pip install fails with SystemError

For example, pip installing pyyaml fails with:

SystemError: Parent module 'pkg_resources._vendor.packaging' not loaded, cannot perform relative import

I've attached a "simple" repro of the issue:
ipy3_import.zip

Basically, it fails because IronPython is not using importlib as the implementation of __import__.
For instance, if test.py from the zipfile, instead of doing __import__('extern.packaging.version'), did import importlib; importlib.import_module('extern.packaging.version'), the test works, both under CPython and IronPython.
More specifically, the culprit its the "mysterious hack" in VendorImporter.load_module (from extern/__init__.py):
                # mysterious hack:
                # Remove the reference to the extant package/module
                # on later Python versions to cause relative imports
                # in the vendor package to resolve the same modules
                # as those going through this importer.
                if sys.version_info > (3, 3):
                    del sys.modules[extant]

VendorImporter imports its extant _vendor.packaging using __import__, which places the imported module in sys.modules under the module key (_vendor.packaging). This is not good enough for importlib which expects the module to be accessible under the key based on the original import name extern.packaging. So VendorImporter reassigns the module in sys.modules to the new key. So far, so good. But then, the hack deletes the old key for some reason.
Without this hack, the test works under IronPython as well.
The hack is really mysterious, because it seems totally unnecessary. I tested it with CPython from 3.4 to 3.9, and in no circumstances, the key _vendor.packaging, when present, was actually used by importlib. However, when not present, it causes IronPython to fail.
I don't have CPython 3.0 - 3.2 to compare, but from the hack comment I gather that the current IronPython behaviour is in line with CPython's import machinery behaviour written in C, which presumably was slightly different than importlib. After all, one of the main justification for CPython to switch over to importlib was the elimination of subtle incompatibilities.
But now I am confused about the intended future path for IronPython.
On one hand, following CPython, the task to switch over to importlib is on the to-do list for 3.3.
On the other hand, @slozier writes:

what really needs to happen is fixing up the import system so we don't need to rely on importlib anymore.

So what is it: patching the import machinery in IronPython trying to match importlib of follow CPython? After all, CPython's reasons for relying on importlib are pretty compelling.

A small side note: line 71 in extern/__init__.py in the zipped example test:
names = 'packaging'

should be
names = 'packaging',

but it is further inconsequential for the validity of the test.

So the solution would be to inject the the importlib implementation of __import__ into __builtins__.__import__ after bootstrapping? Seems fairly straight forward. I'll give it a try...

So what is it: patching the import machinery in IronPython trying to match importlib of follow CPython? After all, CPython's reasons for relying on importlib are pretty compelling.

I guess what I should have said is we so we don't need to rely on the current bootstrapping of importlib anymore. Obviously I would prefer to use the importlib mechanism as-is, however the current performance hit on startup is likely unacceptable in the long term.

But now I am confused about the intended future path for IronPython.

So am I. I don't have any clear ideas about how to get around the performance issue. Some possibilities:

Beefing up the current implementation to match importlib -- not particularly appealing since we'd have to patch every time CPython changes something.
Trying to optimize the hot code paths.
Precompiling the module in a DLL -- this would have been my approach, however the method we previously used to do this was ripped out of .NET Core.
Magic 😃

So the solution would be to inject the the importlib implementation of import into builtins.import after bootstrapping? Seems fairly straight forward. I'll give it a try...

Looks like it's not as simple as that since the import of .NET is not hooked up to the standard import hooks. The correct solution is probably to have a proper importer, but I think I might just hack it for now...

Trying to match up to importlib — across CPython versions, all platforms, fixing bugs and shortcomings in the current Importer — is not a very appealing idea. The more we can rely on the existing stdlib pure python implementation, the better. But sometimes it is not easy and/or comes with significant performance, as the codecs example shows.
As an exercise, I have made a modification to Importer to match this particular importlib behaviour needed to solve this particular issue, I can submit it if you think it will be helpful in the short term. (But installing pyyaml still fails, this time because "distutils do not support VC 6.0..."). Though some places in Importer made my eyebrows rise...
Longer term, I think that importlib is the way, with proper extensions (it is pretty extensible) and optimizations (e.g. eliminate heavy exceptions).

Precompiling the module in a DLL -- this would have been my approach, however the method we previously used to do this was ripped out of .NET Core.

Precompiling into a DLL sounds like a great idea. What was the method?

As an exercise, I have made a modification to Importer to match this particular importlib behaviour needed to solve this particular issue, I can submit it if you think it will be helpful in the short term.

Might be worth it (in particular if we want to get an alpha out the door).

But installing pyyaml still fails, this time because "distutils do not support VC 6.0..."

Well, at least that seems like a reasonable failure and not some obscure import issue.

Precompiling into a DLL sounds like a great idea. What was the method?

You can do it via ClrModule.CompileModules. It can be useful for debugging compiled code since you end up with a .NET DLL which you can open up with ILSpy.

@slozier  instead of creating an issue.
Question.  Is it feasible to do ipy -m pip install regex‑2019.2.7‑cp34‑cp34m‑win_amd64.whl from Python Extension Packages for Windows - Christoph Gohlke

@GeorgeS2019 All those windows binaries are C extension modules which won't work with IronPython.

@slozier  do you have a long term plan to make C extensions (e.g. numpy etc. ) work?

@slozier  Here is the link (up-to-date to 2019) of Ironclad for Ironpython2. Perhaps you could gather interest from users here. I believe many would like to see that works for Ironpython3 eventually.


Setup CLI

Have you considered adding a CLI setup process, similar to how the T3 Stack does it? I'm a big fan of this project but find a lot of the features aren't relevant to me, especially as some require third-party services.
Would be great to have a custom setup experience, so I can say what I do/don't want, and then have options for each, such as Drizzle vs Prisma.
Would speed up the process a lot when first developing, as I don't need to go through the code and remove services I don't want to use.

Hey @JedPattersonn, yep been thinking about that recently. I think as we build out more migration guides (e.g. switch your database to X or switch your auth provider to Y) we'll end up seeing patterns that will help us create more isolated packages. Then, as you noted, we can make those packages and even the specific providers customizable in the init command.


Don't use sudo on TravisCI

This should allow building without script blocks requiring root permissions (if container infrastructure becomes available again, this would let it run on that, I think).
This is a second attempt, as my previous try didn't have an access token.

Removing the silent flag from curl is printing a 403 error, so I presume that is because the access token doesn't work in a pull request. I've tried putting the script all on one line and that still doesn't fix it, and I still can't see a problem with anything the script block is doing.
Maybe this would work if it was merged and then we just revert it if it still doesn't work. At least that might clarify whether it was a token issue or whether there is something wrong with the script block handling.

It seems the problem is with the script block parsing. I've validated the script itself multiple times, so I think there is something strange about how TravisCI gets the content into a shell.


Add a new option to limit the number of requests in a single RPC batch request

Description
Adds a --rpc-max-batch-size CLI option to restrict the maximum number of requests in a single RPC batch request.
Default 50
When -1: unlimited - the current configuration.
When number of requests in batch > --rpc-max-batch-size:

Throw a JsonRpcError.EXCEEDS_RPC_MAX_BATCH_SIZE); with type INVALID_PARAM and message Number of requests in batch exceeds --rpc-max-batch-size.

Mitigation for https://github.com/ConsenSys/protocol-misc/issues/681

I haven't confirmed but it seems geth only accepts batch size 1 - so maybe that should be our default


Update Karaf to see if it fixes CI [do not merge, please]

(there will be a proper JIRA and PR if it fixes the issue)

Jenkins, retest this please

Jenkins, retest this please

Didn't work :/


Weird light mode dark mode monitor icon

I assume that this means to use preferred system but that is weird because usually you just have light and dark and it only defaults to system default. If you want to switch through it you are not interested in the system default.

We've fixed the issue and deployed our brand-new documentation site. Let me know what you think of it and as always, share your feedback.

I think it looks very good, at least visually, but the link buttons and content buttons should perhaps be seperated


feat(new): Added Azure.Grafana.Version

PR Summary
Fixes #2878
Added Azure.Grafana.Version.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Let me know what you think @BernieWhite. I ended up with not using the version expression as the field value will not follow semantic versioning principles. I felt that the greaterOrEqual expression was a better fit in this case.
field: properties.grafanaMajorVersion
version: '>=10'

$ruleResult[0].Reason | Should -Be "Path properties.grafanaMajorVersion: The version '9.-1.-1' does not match the
constraint 'PSRule.Data.SemanticVersion+VersionConstraint'.";

Thanks for the updates @BernieWhite.


Local JS classes inside anonymous classes cause IR checking errors

Take the following:
val supplier = new Supplier[js.Dynamic]{
  def get(): js.Dynamic = {
    class LocalInsideAnonymousClass extends js.Object {
      def x: Int = 1
    }

    new LocalInsideAnonymousClass().asInstanceOf[js.Dynamic]
  }
}

val obj = supplier.get()

assertEquals(1, obj.x)

Causes:
file:/home/tschlatt/20p/scala-js/test-suite/js/src/test/scala/org/scalajs/testsuite/jsinterop/NestedJSClassTest.scala(517:15:CreateJSClass): Invalid CreateJSClass of top-level class org.scalajs.testsuite.jsinterop.NestedJSClassTest$$anon$1$LocalInsideAnonymousClass$1

I suspect that the local class wrongly gets identified as anonymous class by later compiler phases because some checks are name based.

Yep: https://github.com/scala/scala/blob/v2.13.3/src/reflect/scala/reflect/internal/Symbols.scala#L3354
So that means we cannot use isAnonymousClass post flatten anymore (at least without caveats).

Ouch. I guess we'll need to do a more sophisticated check that does not look anywhere inside, but only at the end followed by digits only or something like that. (I'm not sure what's the exact format, but hopefully it's too hard to identify.)


Hoped that the onscroll event can be bound to the component

What problem does this feature solve?
  <textarea v-on:onscroll="this.scroll()" name="" id="" cols="30" rows="10">
    onscroll 事件在元素滚动条在滚动时触发。
  </textarea>

for app to handle onscroll event
What does the proposed API look like?
v-on:onscroll

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server, gitter or StackOverflow.

it's v-on:scroll


alt click mech debug assert doafter

Description
you know the drill
repro

get in ripley
alt click the ripley
instantly hop out
crash when doafter completes

This, and the disposal & table asserts should just be combined into a single issue, rather than having three nearly identical issues up.


remove tiller from documentation

https://github.com/MicrosoftDocs/azure-docs/blob/e7c1454d452bbe333658cccc031909a4c0b88086/articles/application-gateway/ingress-controller-install-existing.md?plain=1#L56
https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-existing

@EvertonSA
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-existing

@EvertonSA
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.


Update BIPMapper

Faster BIPMapping heuristic and improved user control features are directly from a previously unmerged PR in terra originally authored by @gnannicini:
https://github.com/Qiskit/qiskit-terra/pull/8787

Merged more recent changes currently still in qiskit-terra:
https://github.com/Qiskit/qiskit-terra/pull/9840
https://github.com/Qiskit/qiskit-terra/pull/9840

transpile, BIPMapping, and BIPMappingModel all behave as expected with various inputs

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

There is an issue with file formatting:
lint: commands[0]> black --check qiskit_bip_mapper setup.py
would reformat qiskit_bip_mapper/bip_mapping.py
would reformat qiskit_bip_mapper/bip_model.py
This is blocking the merge. Can you have a quick look at it? Running the automatic formatting tool should be enough.

There is an issue with file formatting:
lint: commands[0]> black --check qiskit_bip_mapper setup.py would reformat qiskit_bip_mapper/bip_mapping.py would reformat qiskit_bip_mapper/bip_model.py
This is blocking the merge. Can you have a quick look at it? Running the automatic formatting tool should be enough.

reformatted with black, should work now!

Now these are reported as errors:
qiskit_bip_mapper/bip_mapping.py:168:9: D205 1 blank line required between summary line and description
qiskit_bip_mapper/bip_mapping.py:311:9: D205 1 blank line required between summary line and description
qiskit_bip_mapper/bip_mapping.py:311:9: D209 [] Multi-line docstring closing quotes should be on a separate line
qiskit_bip_mapper/bip_model.py:47:9: D202 [] No blank lines allowed after function docstring (found 1)
qiskit_bip_mapper/bip_model.py:47:9: D205 1 blank line required between summary line and description
qiskit_bip_mapper/bip_model.py:47:9: D212 [] Multi-line docstring summary should start at the first line
qiskit_bip_mapper/bip_model.py:47:9: D415 [] First line should end with a period, question mark, or exclamation point
qiskit_bip_mapper/bip_model.py:730:15: UP011 [] Unnecessary parameters to functools.lru_cache
qiskit_bip_mapper/bip_model.py:738:15: UP011 [] Unnecessary parameters to functools.lru_cache
Found 9 errors.
[*] 6 potentially fixable with the --fix option.
lint: exit 1 (0.03 seconds) /home/runner/work/qiskit-bip-mapper/qiskit-bip-mapper> ruff check qiskit_bip_mapper setup.py pid=2030
.pkg: _exit> python /opt/hostedtoolcache/Python/3.8.17/x64/lib/python3.8/site-packages/pyproject_api/_backend.py True pbr.build
lint: FAIL code 1 (46.89=setup[46.41]+cmd[0.45,0.03] seconds)
evaluation failed :( (47.59 seconds)
Error: Process completed with exit code 1.

Now these are reported as errors:
qiskit_bip_mapper/bip_mapping.py:168:9: D205 1 blank line required between summary line and description qiskit_bip_mapper/bip_mapping.py:311:9: D205 1 blank line required between summary line and description qiskit_bip_mapper/bip_mapping.py:311:9: D209 [] Multi-line docstring closing quotes should be on a separate line qiskit_bip_mapper/bip_model.py:47:9: D202 [] No blank lines allowed after function docstring (found 1) qiskit_bip_mapper/bip_model.py:47:9: D205 1 blank line required between summary line and description qiskit_bip_mapper/bip_model.py:47:9: D212 [] Multi-line docstring summary should start at the first line qiskit_bip_mapper/bip_model.py:47:9: D415 [] First line should end with a period, question mark, or exclamation point qiskit_bip_mapper/bip_model.py:730:15: UP011 [] Unnecessary parameters to functools.lru_cache qiskit_bip_mapper/bip_model.py:738:15: UP011 [] Unnecessary parameters to functools.lru_cache Found 9 errors. [*] 6 potentially fixable with the --fix option. lint: exit 1 (0.03 seconds) /home/runner/work/qiskit-bip-mapper/qiskit-bip-mapper> ruff check qiskit_bip_mapper setup.py pid=2030 .pkg: _exit> python /opt/hostedtoolcache/Python/3.8.17/x64/lib/python3.8/site-packages/pyproject_api/_backend.py True pbr.build lint: FAIL code 1 (46.89=setup[46.41]+cmd[0.45,0.03] seconds) evaluation failed :( (47.59 seconds) Error: Process completed with exit code 1.

all issues should be fixed now


Jwilaby/#1185 app insights

resolves #1185

Pull Request Test Coverage Report for Build 1628

57 of 61 (93.44%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.2%) to 58.42%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/app/main/src/commands/connectedServiceCommands.ts
0
2
0.0%

packages/app/main/src/services/appInsightsApiService.ts
50
52
96.15%

Files with Coverage Reduction
New Missed Lines
%

packages/app/client/src/data/sagas/servicesExplorerSagas.ts
1
70.11%

Totals

Change from base Build 1624:
0.2%

Covered Lines:
5065

Relevant Lines:
7798

💛  - Coveralls


0x0008d2abf5Ab348137CdcA8b4AA9674c0e4367E4

YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/
Checklist

[ ] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

world Kooperation Investment social humanitäre Projekt ab 300000 euro

Please submit the correct information, invalid information will cause the issue to close

Super


Use cases where apko is not recommended?

We rely on Alpine images a lot for https://dagger.io (it's our base image of choice). At the moment we have quite a lot of automation built around pulling a base OCI image, then executing apk. It seems like perhaps we could (should?) use apko instead. Is the goal for apko to be a drop-in replacement for all alpine image builds? Or are there cases where it's not the best tool?
Note: at the moment I'm not interested in the "your app artifacts are apk packages" pattern. I just want the best possible way to build an image. Will apko make it a requirement to go all in on that pattern, or can I stick to assembling system packages and still be considered a first-class citizen?

apko is suitable for building base images where you have all of the artifacts you want to put in that layer already.  If you want to add more stuff outside of APK artifacts, then yes, composing it with other tools (such as ko or docker) is a supported usecase.  We want to enable people to use the patterns that suit them the best.

I'm planning to do a blog outlining the wider vision over the next week or so, either on the Chainguard blog or my own personal one, which should outline a few envisioned usage scenarios.
Obviously at Chainguard, we're very into the "your app artifacts are also apk packages" pattern because that makes compliance and auditability (e.g. scanning, SBOMs, etc.) really easy, but as I'm sure you're aware, philosophically, it's always been the position of the Alpine community that good ideas and tooling will become dominant without forcing anyone into any specific workflow, and that belief is also reflected at Chainguard :)

Yes the pattern is definitely interesting and I agree with your assessment that it will gradually gain ground as a best pratice. It just doesn't coincide with my immediate use case.

Yep, anyway, composing apko in pipelines with other tools is fully supported, and encouraged, for example to generate base images for ko and kaniko to layer things on top.

This info was added to the FAQ, so I'm going to close this issue. Please open a new issue if I've missed something.


Implement a simple search dialog

This PR implements a simple search dialog as described in #154.
Two notes:

The search is affected by the Filter. So if the user has defined a filter, then the list of services shown in the search only includes those matched by the filter.
At the moment, we perform simple substring matching. In the future, we could think about adding fuzzy searching capabilities using a library like FuseJS.

Screenshots

In the future, we could think about adding fuzzy searching capabilities using a library like FuseJS.

@MBuchalik https://github.com/leeoniya/uFuzzy#a-biased-appraisal-of-similar-work


Broken on new version of slippi.

The dolphin replay .exe has been renamed, even when fixing this it never properly renders any frames.

To add to this: I get it to work kind of, but 1440p produces corrupt files, and I don't see a meaningful quality difference between 720p and 1080p renderings. Maybe the py-slippi module needs to be updated?

Yeah, change the DOLPHIN_NAME variable in config.py to this:

By the way, I fixed this be renaming "Dolphin Slippi " to just Dolphin.

Hmm, probably the executable name should just be part of the path in config.json
Feel free to submit a patch or fork the project by the way, if you've fixed something


Duplicate effort

It seems we have a duplicate effort with our find-glob.
Perhaps you might be interested to focus our efforts instead.

Well yours has the null separator option and mine has API & CLI support along with an automated test & docs. So maybe it would be good to add an option to mind with the -0 option and I can add you as a full-access collaborator?

I don't mind which project stays, I am happy to consolidate them. I don't really need the collaborator status, but it might help, of course.
I find the following advantages of cli-glob: the name of the package, tests available.
I find the advantage of API & CLI support questionable. We have glob for Node access, the point of cli-glob and find-glob is to provide the CLI. It's even in the name of cli-glob.
I find the find-glob advantages to be the multiple pattern and exclusion functionality (find-glob **/*.js !node_modules/**), zero separator, and the smaller implementation code-wise leaving less space for bugs.
I propose to take find-glob source code, replace cli-glob code with it, leaving the name cli-glob, add tests from cli-glob and then deprecate find-glob in favor of cli-glob. If you agree with this, I can prepare a PR.

For the most part those are valid points, however please allow me to explain some of my choices:
The purpose of the API is not for other modules to use it but so it can be tested separately from the CLI implementation. This way we can very quickly programmatically test all the possible combinations of input & output with cleaner, more maintainable test code than using callbacks or child process spawning systems throughout to test the CLI. I much prefer to test all the functionality internally then use a single test case for the CLI to confirm it's functional as I trust stdout & stdin are working just fine.
Second, while yes your implementation is smaller your final package size is much bigger. After installing a fresh copy of our packages:

My overall package size is 15% the size of yours for doing a nearly identical amount of functionality. On another note, yours installs 2 separate versions of lodash.

Personally I can't in good consciousness justify bloating this tool just for a more terse, less testable source file.
That said, I'd still much enjoy collaborating and making a better tool overall.

Simplify the cli-glob source code. Obviously it could be better written, cleaner, and we can probably remove the use of promises entirely which will also remove the necessity of the es6 promise polyfill.
Try glob-all for the multi-pattern searches. It offers the same functionality as your globExpand but it doesn't rely on lodash resulting in a smaller file-size and fewer dependencies. Unfortunately, neither of these libraries have tests :cry:
Add support for the -0 option.

I think if we make those changes we'll have a pretty badass library that is very lightweight, testable, without sacrificing the functionality you added.
What do you think about that?

I don't really see much value in total package size, but if you're analyzing it, notice that find-glob includes glob, glob-expand, and argparse. The first is the same cli-glob uses for obvious reason, and glob-expand and argparse functionality is missing in cli-glob. If we add glob-expand and argparse to cli-glob, the resulting size will be the same. =7
I don't really see value in testing the package, which sole purpose is to be a cli wrapper around glob, through an API exposed specifically for this reason. That's testing glob! The only valuable tests in this package are those that test this specific package, so, cli tests with exec.
I don't have an opinion between glob-all and glob-expand. It'd be better if there was one package that did that, but alas.
In any case, you seem to be pretty excited about cli-glob, and you have a better name, so let's ensure that it stays that way. I really only need the multi-patterns with ignores and the -0 option.
Make your calls, let me know if I can help beyond providing find-glob source code as an example.

@jayzawrotny, seemes that you've added promise polyfill for supporting old environments (324c1fce3c13922b8ce7cf310085ff785da5ab36). Does your tests really run on 0.10, 0.12? If so, you could notice that in travis and in package.json in "engines". If not, I believe you can throw out polyfill harmlessly and have a clean and beautiful deps from minimist and glob only :)

Well my assumption is that misteroneill needed the polyfill to work on his 0.10 environment so it could work on 0.10. However, I agree with you that it would be better if my only deps were minimist and glob. In which case it would be better to rewrite it and not use promises at all and then the Polyfill would not be needed and 0.10 and 0.12 can still be supported. I tested it on 0.10.41 before that pull request was merged in but it definitely should have been reflected in the package.json and travis as you mentioned.


Remove duplicated counters and filter group id in kernel

What this PR does / why we need it:
Currently, in the eBPF code, when a new cgroup_time (i.e., new_cgroup) is created, it is initialized with counter values, and shortly after the initialization, the structure instance is also updated with the same counter, doubling the values.

While this only happens at the initialization, we shouldn't duplicate the counters. Also, for the sake of performance and memory usage into the kernel, we should only create a new structure instance when it does not exist, not every time that the existing structure instance is updated.
Additionally, the cgroup id 0 is filtered in the user space, however, it is possible to filter it in the kernel space, which also reduce the in-kernel computation and memory usage.
Finally, we just need to read the process's command (bpf_get_current_comm) during the  structure instance initialization.

Thank you @marceloamaral
I should have documented this, hopefully this is not too late :D
To update the ebpf module, please modify it here, then generate the bindata using this script. You'll then have two modified file: the .c and .go files.
Once you update the PR, I'll happily merge it.

Thanks @rootfs! I updated this PR according to your comments. Could you please review it again?

thank you @marceloamaral !


Page instantiation protection by combined ruleset.

There is currently no way to annotate a page with instantiation rules on
multiple roles. It is possible to use an AuthorizeInstantiation. But
this can only roles using an OR ruleset.
With this annotation in use we are able to combine multiple OR rulesets
in an AND relation.
Example:
A page can be instantiate only by users with ADMIN and DATABASE role.

Created a ticket: https://issues.apache.org/jira/browse/WICKET-6265

I've cherry picked this commit and applied it at master (8.x) with https://git1-us-west.apache.org/repos/asf?p=wicket.git;a=commit;h=e9b812c3.
Git merge/rebase leads to too much noise in the commits@ mailing list.
@rene-d-menoto Thank you for the contribution! Please close this PR!

Thanks for merging.


TypeError not being caught when using --query on experimental command group: az account subscription

Related command
az account subscription list-location --subscription-id "$subid" --query "[? contains(name, "uk")]"
Describe the bug
--query "[? contains(name, "uk")]" should use single quotes instead of double quotes. In which case the following TypeError is not being caught and generates a traceback in the az cli:
TypeError: 'in <string>' requires string as left operand, not NoneType
The correct version of the command (single quotes) works as expected:
az account subscription list-location --subscription-id "$subid" --query "[? contains(name, 'uk')]"
To Reproduce
az account subscription list-location --subscription-id "$subid" --query "[? contains(name, "uk")]"
Expected behavior
The error should be caught and output should silenced. This would make the behaviour consistent with GA status command groups. For example, the following equivalent invalid query (double quotes) will silence the output instead:
az account show --query "[? contains(name, "uk")]"
Additional comments
The existing behaviour of silencing output is applied in both cases of
az account show --query "[? contains(name, "uk")]" (bad syntax) and az account show --query "[? contains(name, 'uk')]" (good syntax). In my opinion this isn't optimal as it doesn't differentiate between a syntax error and a not found result (valid user experience). Ideally the caught error should be communicated differently (i.e. not silenced) to the user so that they can modify their syntax accordingly. Otherwise they may mistakenly believe that their syntax was valid but that the string they searched for did not exist.
Environment summary
az version -o table
Azure-cli    Azure-cli-core    Azure-cli-telemetry

2.42.0       2.42.0            1.0.8
echo $BASH_VERSION
4.4.23(1)-release
az extension list -o table
Experimental    ExtensionType    Name             Path                                              Preview    Version
False           whl              account          C:\Users\dc.azure\cliextensions\account          False      0.2.5
False           whl              azure-devops     C:\Users\dc.azure\cliextensions\azure-devops     False      0.25.0
False           whl              datafactory      C:\Users\dc.azure\cliextensions\datafactory      False      0.7.0
False           whl              storage-preview  C:\Users\dc.azure\cliextensions\storage-preview  True       0.3.0

@jiasli for awareness


fix(theme): update button colors

Changes

Update button/chip stylings

Screenshots
Before

After

It looks like the dark mode disabled is different.
Current

Design


Error:Failed to resolve: org.tensorflow:tensorflow-android:1.2.0-rc0

Error:Failed to resolve: org.tensorflow:tensorflow-android:1.2.0-rc0
Open FileShow in Project Structure dialog

Seems like tensorflow has moved their packages from tensorflow-android to tensorflow on Jcenter
https://bintray.com/bintray/jcenter/org.tensorflow%3Atensorflow
So you need to replace tensorflow-android with tensorflow in the gradle file

thanks


etcdserver: check loaded WAL matches the snapshot

fixes #1838

refreshed.

based on the discussion ool, the current impl for dummy entry is not very clear because dummy entry doesn't match snapshot one by one. And it cannot help further detection. will try it in another approach.


Update Facebook API version

Updating v2.3 to current v2.5 version of facebook api

Some critical errors occurred during the tests. This PR can't be merged.

+1
Currently, latest facebook api version is v2.7.

fixed by #798

API version was recently changed to 2.7.


Update .gitattributes

Ibet

Haha

Hi app hay

Hu

Hu

Lololo

Hsjs

Hsjs

Ho

Hahaha

Hahaha

Bababa

@kunam1 are you a bot ?

No idea what this was. I banned the account since I can't really think of a valid justification for that kind of noise.


Add log message when drawing '\t' character

I have spent some hours trying to figure out why my text wouldn't render properly until I swapped my '\t' characters for spaces and it worked fine. Right now, '\t' renders as a single space but behaves like any other character that isn't a space. If you have a list of words separated by '\t', it's as if the whole string is a single word and will not properly align in a column as it should (it stays on one single line and is clipped at the width of the column).  Until SDL_FontCache adds support for '\t', it would be wise to alert the user of this hazard so it's easier to avoid. Those logs are only enabled in debug mode.

Thanks for the idea and pointing out this bug!  I thought I'd just support the tab character better instead of a special case log, if that resolves your issue.  Can you check out f1a34802e3b2ae1fb3b4f5bc67e37331fe878809 to see if that works for you?

This works wonderful! Thanks a lot grimfang


Investigation of stack trace: too many open files

Leaving this one here for investigation later.
goroutine 1 [running]:
github.com/docker/docker/client.(*Client).getAPIPath(0x0, {0x0, 0x0}, {0x100d83502, 0x10}, 0x14000839de8)
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/client.go:188 +0x28
github.com/docker/docker/client.(*Client).sendRequest(0x0, {0x0, 0x0}, {0x100d7e09d, 0x3}, {0x100d83502, 0x10}, 0x14000839de8, {0x0, 0x0}, ...)
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/request.go:116 +0x5c
github.com/docker/docker/client.(*Client).get(...)
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/request.go:36
github.com/docker/docker/client.(*Client).ContainerList(0x0, {0x0, 0x0}, {0x0, 0x1, 0x0, {0x0, 0x0}, {0x0, 0x0}, ...})
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/container_list.go:48 +0x570
github.com/pygmystack/pygmy/service/interface/docker.DockerContainerList()
	/home/runner/work/pygmy/pygmy/service/interface/docker/docker.go:53 +0xd0
github.com/pygmystack/pygmy/service/interface.(*Service).GetRunning(0x1400083ac68)
	/home/runner/work/pygmy/pygmy/service/interface/interface.go:161 +0x3c
github.com/pygmystack/pygmy/service/interface.(*Service).GetFieldString(0x1400083ac68, {0x100d7e57a, 0x4})
	/home/runner/work/pygmy/pygmy/service/interface/field.go:33 +0xac
github.com/pygmystack/pygmy/service/library.Up({{0x1400030d500, 0x1, 0x1}, {0x0, 0x0}, 0x0, {0x0, 0x0, 0x0}, 0x0, ...})
	/home/runner/work/pygmy/pygmy/service/library/up.go:138 +0x9c8
github.com/pygmystack/pygmy/cmd.glob..func10(0x101319500, {0x1013549c8, 0x0, 0x0})
	/home/runner/work/pygmy/pygmy/cmd/up.go:69 +0x180
github.com/spf13/cobra.(*Command).execute(0x101319500, {0x1013549c8, 0x0, 0x0})
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:856 +0x640
github.com/spf13/cobra.(*Command).ExecuteC(0x10131ab80)
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:960 +0x404
github.com/spf13/cobra.(*Command).Execute(...)
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:897
github.com/pygmystack/pygmy/cmd.Execute()
	/home/runner/work/pygmy/pygmy/cmd/root.go:58 +0x30
main.main()
	/home/runner/work/pygmy/pygmy/main.go:28 +0x20

The initial investigation appears to indicate an upstream issue in Docker.
I will be merging the docker-related PRs and then re-evaluate.

I got the same issue on M2 MAX. Is that any solution?

Does look like a Docker bug rather than a Pygmy bug. Sharing details here to help track. Will look for issues in the Docker queues.
System information
Hardware details
Apple MacBook Pro

Model Name:	MacBook Pro
Model Identifier:	MacBookPro18,4
Chip:	Apple M1 Max
Total Number of Cores:	10 (8 performance and 2 efficiency)
Memory:	32 GB

Operating System details
Apple macOS

System Version:	macOS 12.6.6 (21G646)
Kernel Version:	Darwin 21.6.0

Software details
Docker Desktop for Mac

Version: 4.19.0 (106363)
Docker Engine: 23.0.5
Docker Compose: v2.17.3

Error details
I find this error only occurs for me on a second start, or restart, of pygmy. If I cold boot into macOS the error doesn't appear on the first use of pygmy. It occurs for me on a restart of pygmy or if I stop and start pygmy.
Steps to reproduce:

Cold boot into macOS
Open a terminal
Start pygmy as normal with pygmy up (no errors)
Restart pygmy with pygmy restart or pygmy down; pygmy up;

fcntl /Users/chopper/.docker/contexts/meta: too many open files
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x71 pc=0x104fa5a58]

goroutine 1 [running]:
github.com/docker/docker/client.(*Client).getAPIPath(0x0, {0x0, 0x0}, {0x105113502, 0x10}, 0x14000a896f8)
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/client.go:188 +0x28
github.com/docker/docker/client.(*Client).sendRequest(0x0, {0x0, 0x0}, {0x10510e09d, 0x3}, {0x105113502, 0x10}, 0x14000a896f8, {0x0, 0x0}, ...)
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/request.go:116 +0x5c
github.com/docker/docker/client.(*Client).get(...)
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/request.go:36
github.com/docker/docker/client.(*Client).ContainerList(0x0, {0x0, 0x0}, {0x0, 0x1, 0x0, {0x0, 0x0}, {0x0, 0x0}, ...})
	/home/runner/go/pkg/mod/github.com/docker/docker@v23.0.1+incompatible/client/container_list.go:48 +0x570
github.com/pygmystack/pygmy/service/interface/docker.DockerContainerList()
	/home/runner/work/pygmy/pygmy/service/interface/docker/docker.go:53 +0xd0
github.com/pygmystack/pygmy/service/interface.(*Service).GetRunning(0x14000a89f58)
	/home/runner/work/pygmy/pygmy/service/interface/interface.go:161 +0x3c
github.com/pygmystack/pygmy/service/interface.(*Service).GetFieldString(0x14000a89f58, {0x10510f7e3, 0x7})
	/home/runner/work/pygmy/pygmy/service/interface/field.go:33 +0xac
github.com/pygmystack/pygmy/service/library.SshKeyAdd({{0x1400029d500, 0x1, 0x1}, {0x1051138f2, 0x10}, 0x1400030b6e0, {0x14000302000, 0x5, 0x5}, 0x14000396ff0, ...}, ...)
	/home/runner/work/pygmy/pygmy/service/library/sshkeyadd.go:30 +0x1e8
github.com/pygmystack/pygmy/service/library.Up({{0x1400029d500, 0x1, 0x1}, {0x0, 0x0}, 0x0, {0x0, 0x0, 0x0}, 0x0, ...})
	/home/runner/work/pygmy/pygmy/service/library/up.go:131 +0x128c
github.com/pygmystack/pygmy/cmd.glob..func10(0x1056a9500, {0x1056e49c8, 0x0, 0x0})
	/home/runner/work/pygmy/pygmy/cmd/up.go:69 +0x180
github.com/spf13/cobra.(*Command).execute(0x1056a9500, {0x1056e49c8, 0x0, 0x0})
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:856 +0x640
github.com/spf13/cobra.(*Command).ExecuteC(0x1056aab80)
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:960 +0x404
github.com/spf13/cobra.(*Command).Execute(...)
	/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:897
github.com/pygmystack/pygmy/cmd.Execute()
	/home/runner/work/pygmy/pygmy/cmd/root.go:58 +0x30
main.main()
	/home/runner/work/pygmy/pygmy/main.go:28 +0x20

I'd be very interested in anything you find @christopher-hopper .
I don't have M1/M2 hardware I can test directly on it, but I did merge a dependency issue which might be related to when I opened this one. It might be helpful to try to compile and run it - I'd be happy to cut a release if that's the case.

Okay, found the cause and a solution to this error.
On macOS Darwin (and BSD and Linux) there are limits placed on the number of file descriptors that can be opened at once. The error we're experiencing occurs when the soft limit on max open files is reached by the command running in the shell.
You can see the max open file descriptors limit in your shell by running:
ulimit -aS

On macOS Monterey the default limit is 256. This must be not enough for Docker when we use pygmy and docker compose.
Steps to fix on macOS
To increase the max open files limit on macOS, so that it persists, you need to create a LaunchDaemon property list (plist) file. The limit set in the plist file for the LaunchDaemon will then be used by all new running shells.

As root, create a file at /Library/LaunchDaemons/limit.maxfiles.plist
 sudo touch /Library/LaunchDaemons/limit.maxfiles.plist

Open the file in an editor
 sudo vim /Library/LaunchDaemons/limit.maxfiles.plist

Copy paste this LaunchDaemon property list into the file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>Label</key>
        <string>limit.maxfiles</string>
        <key>ProgramArguments</key>
        <array>
            <string>launchctl</string>
            <string>limit</string>
            <string>maxfiles</string>
            <string>61440</string>
            <string>524288</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
        <key>ServiceIPC</key>
        <false/>
    </dict>
</plist>

Save the file and confirm it is owned by root:wheel

Load the LaunchDaemon service with the new maxfiles limit values
 sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist

Confirm the LaunchDaemon limits are now set
 launchctl limit

Close and reopen your terminal shell

Confirm the new limits have persisted in your shell
 ulimit -aS

The above file will configure the system LaunchDaemon maxfiles limit as 61,440 (soft limit) 524,288 (hard limit). This hard limit is equivalent to unlimited on macOS Darwin, which is the default.
Now when we run our pygmy up or pygmy restart commands we no longer hit the "Too many open files" errors.
References

https://discussions.apple.com/thread/253001317
https://stackoverflow.com/questions/73977844/too-many-open-files-during-rspec-tests-on-macos
https://unix.stackexchange.com/questions/108174/how-to-persistently-control-maximum-system-resource-consumption-on-mac

Unfortunate there's no globally scoped solution to this... thanks for the run-down.
I suppose this is just one of the nuances of MacOS... 😥

This error comes and goes, somehow once I restart the docker desktop, everything works.
BTW, the macbook I got pretty new, I dont have limit.maxfiles.plist under Library/LaunchDaemons/
here is my ulimit -sS
ulimit -aS -t: cpu time (seconds)              unlimited -f: file size (blocks)              unlimited -d: data seg size (kbytes)          unlimited -s: stack size (kbytes)             8176 -c: core file size (blocks)         0 -v: address space (kbytes)          unlimited -l: locked-in-memory size (kbytes)  unlimited -u: processes                       5333 -n: file descriptors                1048575

Solved this by a restart, but next time I'll run running this first: ulimit -n 10240 before rerunning in the same session. The 256 limit has never been hit by me for anything I run, and I have a lot of apps open, and this has only ever happened for this one tiny app (it seems).

Happened to me today on Sonoma. I then just stopped and started pygmy with no issue.


Support contextFactory

Having context factory as a parameter is the only missing part of this package.
Example implementation can be https://github.com/anonrig/bookclub/blob/main/src/lib/graphql/index.ts#L119

@anonrig I'll add this tomorrow

@anonrig I've just released 0.9.0

It seems that next-auth requires reference to res as well as req (https://next-auth.js.org/configuration/nextjs#unstable_getserversession). Can you also add res as a second parameter?


sdf_write: sort output

Signed-off-by: Karol Gugala<EMAIL_ADDRESS>

I'm going to merge this, but can we also add some tests for this?


Rails <IP_ADDRESS> upgrade

NB: This branch is WIP, do not merge
This is the fix for #1447, bumping the Rails version to <IP_ADDRESS>. Lots of work to be done here, may need some help with this one.

[x] Establish why commented out Gems do not resolve when bundle installed
[x] Run rails app:update to update Rails binaries
[x] Create ApplicationRecord by default, ensure models inherit from it
[x] Create ApplicationMailer and ApplicationJob superclasses
[ ] Ensure test suite passes
[ ] Fix DEPRECATION WARNING: Directly inheriting from ActiveRecord::Migration is deprecated

More to come as I think of it.

Quiet assets can go completely, it's not needed in 5.0

Nice work kicking this off btw! ☃

Rails 5 support on the konacha gem is coming soon per https://github.com/jfirebaugh/konacha/pull/233

Compatibility with octicons-rails seems to be a known issue per https://github.com/torbjon/octicons-rails/issues/5. @andrew, you have an unmerged PR on that repo and it seems that repo hasn't seen much love in a while... maybe we could drop this particular gem?

@xadamy Great work! I pushed a few changes and got most of the tests passing, lots of deprecation warnings in the tests and a few failing ones still to fix.
I've switched the octicons gem to pull from github for now, I don't really want to add all those images directly to the repo.

Only 6 failing tests now 🌮
Will also open a seperate issue up to switch to using https://github.com/primer/octicons_gem

Nice work and thanks for the assist @andrew! 🎉 I'll investigate those other tests tonight.

Just merged in the latest changes in master to fix the conflicts 🤓

Fixed a load of the deprecation warnings and I'm pretty sure that the 5 remaining test failures are related to the same bug in the way the projects_controller is handling its params

Rails tests pass now although I did a horrible thing 🙃
Now we jsut need to get konacha to find the js files that have moved to /vendor/assets

A fine job, sir. I can have a look at the konacha issue today.

Merged in the latest changes from master including removing konacha 🎿

omg test pass 🎉

Does this mean we can finally merge now? I guess it's dependant on whether you want to fix those deprecation warnings on the DB migrations first?

@xadamy I don't think we need to fix those, let's ship it!

Pushing to heroku now, will keep an eye on bugsnag to see if we missed anything 🙈


Add Delete User By Name Endpoint

https://github.com/ariesprayoga/swagger-java-sample-app/blob/master/src/main/java/com/wordnik/swagger/sample/resource/UserResource.java

Unclear if this is "unregister" or what not just yet.


fix jinja version

Issue #, if available:
Description of changes:
Fix jinja version to fix ci
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-1691-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1691/1/index.html


Kinesis Elasticsearch Sink: getting strange error

I'm getting an error with the current version of the ES sink that I don't understand.
Oct 22, 2015 5:21:34 PM com.snowplowanalytics.snowplow.storage.kinesis.elasticsearch.SnowplowElasticsearchEmitter apply
SEVERE: Record failed with message: UnavailableShardsException[[snowplow][3] Primary shard is not active or isn't assigned to a known node. Timeout: [1m], request: org.elasticsearch.action.bulk.BulkShardRequest@412e8fd]

Any help?

Sorry, this was a cluster issue. I fixed in ES.

Okay - in the future, snowplow-user is the place for these support requests.


feat[file format]: allow empty string for null_if argument

Summary
The Snowflake Terraform provider handles file formats, but does not allow empty string to be added in the null_if directive. This PR aims to fix so that the go string "" is not ignored anymore, and can be handled by Terraform without having to use the ignore_changes lifecycle option. This was solved by adding a new expansion function in pkg/resources/helper_expansion.go called expandStringListAllowEmpty, and using it in pkg/resources/file_format.go instead of expandStringList.
An acceptance test was added in the CSV test with an empty value.
Test Plan

[ ] acceptance tests - needs to be validated
[x] A provider was build using the latest version creation/plan/modification were tested

References

could reference #1609
#708

After closer investigation with Snowflake, it seems there is a bug on Snowflake, here is the answer from the support:

We have tested it out and we were able to reproduce the problem. It looks like a unexpected behaviour as parameter EMPTY_FIELD_AS_NULL doesn't get honoured when FIELD_OPTIONALLY_ENCLOSED_BY is used for the enclosed fields.

Closing the MR then.

@tmlp-lv thank you for your contribution


Cookies not loaded for website sign-in

When I run SteP with this code on my environment, I'm seeing significantly worse performance than reported in the paper. I was digging into this and I see sign-in pages in the environment state that I don't see when running the "run.py" script in WebArena, e.g.:
[1] RootWebArea 'Sign in · GitLab' focused: True
        [24] img 'GitLab Community Edition'
        [25] heading 'GitLab Community Edition'
        [11] tabpanel ''
                [13] Section '' live: assertive atomic: False relevant: additions text
                        [50] StaticText 'Username or email'
                        [15] textbox 'Username or email' focused: True required: True
                        [56] StaticText 'Password'
                        [54] textbox 'Password' required: True
                        [64] checkbox 'Remember me' checked: false
                        [66] link 'Forgot your password?'
                        [62] button 'Sign in'
        [29] StaticText "Don't have an account yet? "
        [30] link 'Register now'
        [19] separator '' orientation: horizontal
        [31] link 'Explore'
        [33] link 'Help'
        [35] link 'About GitLab'
        [37] link 'Community forum'

This looks like the Gitlab sign-in page. In the default WebArena runner script, you never see this, because cookies are loaded from file to avoid sign-in.

I think the WebArena environment in this repo is broken because it's missing this cookie loading.

WebArena websites require authentication before being used. The README in Webarena specifies how to setup authentication so you end up with an .auth folder with cookies with login information. I have copied over the instruction below
mkdir -p ./.auth
python browser_env/auto_login.py

Once you have the .auth folder, copy it over to webagents-step/ root directory.  You should then be signed in to all the websites.
(I have the updated the README with these instructions)


Add Support for generic value dictionaries

Would be nice if the library supported dictionaries with generic types.
var inputs = new Dictionary<string, double>
{
    { "a", 1 },
    { "b", 2 }
};
var result = "{a},{b}".FormatWith(inputs, MissingKeyBehaviour.ThrowException);
// throws System.Collections.Generic.KeyNotFoundException

Since an IDictionary<string, double> can't be passed as an IDictionary<string, object> it is using the object extension method which is not working as desired with dictionaries.
If you convert the dictionary it will work. (Note: you can't cast)
var inputs = new Dictionary<string, double>
{
    { "a", 1 },
    { "b", 2 }
};
var inputs2 = new Dictionary<string, object>();
foreach (var item in inputs)
    inputs2[item.Key] = item;
var result = "{a},{b}".FormatWith(inputs2, MissingKeyBehaviour.ThrowException);
// expected behavior

Are there better ways to do this conversion so the extension methods work?
My suggestion is to add extension methods with type parameters, ex:
public static string FormatWith<TValue>(this string formatString, IDictionary<string, TValue> replacements);

Great idea, with the generic overload. I'll roll it in with the IReadOnlyDictionary change in the 4.0 release.

Implemented in commit 6dc381ed2fc7ced0ac3100f096cf1ca081e08431, will be included in 4.0 release.

Excellent. I like this library over SmartFormat because it's light weight and has a more explicit API. I appreciate your dedication to continuous improvement! Kudos.

Closing this since it's implemented on 4.0 and I want the little milestone graph to go up.


(At least) 20.15.1 signed by expired key: 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4

Release: https://nodejs.org/dist/v20.15.1/node-v20.15.1-linux-x64.tar.gz
Hashsum signature: https://nodejs.org/dist/v20.15.1/SHASUMS256.txt.sig
Hashsums: https://nodejs.org/dist/v20.15.1/SHASUMS256.txt.asc
gpg: Signature made Mon 08 Jul 2024 08:09:13 PM CEST
gpg:                using RSA key 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4
gpg: Good signature from "RafaelGSS<EMAIL_ADDRESS>[expired]
gpg: Note: This key has expired!

Cheers
Thomas

I will re-upload them with the new expiry date. cc: @nodejs/releasers

It should be solved now


Fixed phone mask for Nepal

Nepalese phone numbers contain 10 digits after the country code.
So I changed the phone mask from ['## ### ###'] to ['##### #####']

@hassansari4a Thanks for your contribution ;)
🚀 AstrOOnauta 🚀


No TileSet atlas source with id -1.

Tested versions
Godot 4.2.1 - Stable.
System information
Windows 11, Godot 4.2.1-Stable. Vulkan, Mobile.
Issue description
I made a world generator using a tile map, but oddly it keeps crashing with this error:
E 0:00:25:0323   get_source: No TileSet atlas source with id -1.
<C++ Error>    Condition "!sources.has(p_source_id)" is true. Returning: nullptr
<C++ Source>   scene/resources/tile_set.cpp:549 @ get_source()
This error happens at complete random times when I walk around. Note: I made it generate more tiles when the player walks and erase the tiles too far from the player for optimization on mobile.
This world generator works great until this error crashes the game.
I do not use any plugins or modified versions of Godot.
Steps to reproduce
Uncertain. The issue may be part of the erase_cell() function or set_cell().
Minimal reproduction project (MRP)
None.

Without more details of how to reproduce this issue, it is nearly impossible to fix this. If you find a way to reliably reproduce this error, it would be great to post it here.

I appreciate your comment! I understand that it is extremely difficult without extra information about the issue. I have spent several hours removing and adding to the code in hopes of finding what causes the issue. It is simply too random to diagnose. I made this report in hopes of getting more to see this and experiment with this issue as well, and hopefully have someone comment with more information about the issue.

Without more details of how to reproduce this issue, it is nearly impossible to fix this. If you find a way to reliably reproduce this error, it would be great to post it here.

Update. I was able to play the game without any errors when I ran the generation code on the main thread. However, when I switched back to a sub thread, It would crash the game randomly without telling me the issue. I looked into the log files in my AppData/Roaming/Godot/app_userdata/ProjectName/logs and found this error within the newest log file:
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.215 - Forward Mobile - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics 620

USER ERROR: No TileSet atlas source with id -1.
   at: get_source (scene/resources/tile_set.cpp:549)

I hope this update helped you or someone else diagnose the issue.
I'll see if I can attempt to make a project file that recreates this error.
Note: My code does use the tilemap.get_cell_atlas_coords(layer,position) function. Which may be causing an issue with using a sub thread.


Stop on virtualbox-iso: Waiting for SSH to become available...

Hi,
I use your code for creat custom image of ubuntu, but I got this error after packer build command
virtualbox-iso: Waiting for SSH to become available..
How I can fix this?

There should be an error in your virtualbox additional guest extensions, you may need to re-install it.  Or there might be another application which makes used ssh port inaccesible.


"Error: No commits found in the payload."

Hi. We randomly get these errors in some of our CI runs. We have not found a real pattern when it happens.
Run mristin/opinionated-commit-message@f3b9cec249cabffbae7cd564542fd302cc576827
Error: Error: No commits found in the payload.
Error: No commits found in the payload.

https://github.com/mullvad/mullvadvpn-app/actions/runs/10095396820/job/27915446657
Our workflow is defined like this: https://github.com/mullvad/mullvadvpn-app/blob/cdf26548063f26317029995d1c4eaf38a49ca43e/.github/workflows/git-commit-message-style.yml#L27-L37
Is this a known issue? Do you think it's a configuration miss on our end? Since it happens so sporadically, could it be a race of some kind in the action code?

It looks like a race condition, but I have no clue how to fix it.

P.S. I have not encountered it myself so far.

Hi! I'm closing this issue due to inactivity. Please re-open if you observe this behavior again.

I get this error again in this run: https://github.com/mullvad/unicop/actions/runs/12071382562/job/33663094848?pr=28

@faern Do you always get the issue or only sometimes? To be all honest, I don't even have an idea where to start searching for a bug. :-(

We seem to get it rather randomly. This time I got it twice in a row, then I force-pushed to the PR branch and it went away :shrug:


Fix filters params

Remove array indicator from params keys that broke labels / ips filtering
This is related to changes around type QueryArguments = { [k in AnyQueryArgs]?: unknown }; that now sends array of values instead of a comma separated string so the backend receive array indicators in keys that contains multiple values.
That could be useful in the future for more complex cases and to simplify switch / case on backend side

Thanks @jpinsonneau for fixing my mistakes! 😧
/lgtm


Getting an error when running a race on a 3 node Elastic-Search Cluster

When trying to run a benchmark on a 3 node elastic cluster, we are getting the below error.
Version of Rally - 2.8. 0
Version of Elastic Search - 7.17.0
The document count of index - 35,845,521
**[INFO] Race id is [d5179e91-1c44-44a6-9f57-72bcd08891a2]
[ERROR] Cannot race. Error in task executor
Cannot download data because no base URL is provided.**
Attaching the log file
error.txt

We did not get the same issue when running the benchmark on a single node cluster with document count 3,556,667

Thanks very much for your interest in Rally.
This appears to be a user question, and we'd like to direct these kinds of things to the forums. If you can stop by there, we'd appreciate it. This allows us to use GitHub for verified bug reports, feature requests, and pull requests. There's an active community in the forums that should be able to help get an answer to your question. As such, I hope you don't mind that I close this.
That said, when opening your topic, make sure to include your track definition, your Rally configuration file (.ini file), the full logs and the precise Rally invocation that fails. (It's very surprising to see --track=/home/ec2-user-tracks/ES-Cluster because that looks like a track path, not a track name.)
And for what it's worth, the error is saying that base-url is not set in the corpora section: https://esrally.readthedocs.io/en/stable/track.html#corpora. And Rally is using the 7.17 branch of /home/ec2-user/.rally/benchmarks/tracks/default, not sure if that's expected.


Improve code style

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (8f9b8f3) to head (17a956e).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #534   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           66        66
  Lines         1788      1789    +1
  Branches       208       208
=========================================
+ Hits          1788      1789    +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feat: add alt to imgTag

@omartin9203 thanks for your contribution, your changes have been included in the v4.4.0


viewDidDisappear not called on MainViewController, when presenting SideMenu by code

New Issue Checklist

I have read the guidelines for contributing and I understand:

[x] My issue is happening in the latest version of SideMenu.
[x] My issue was not solved in the README.
[x] My issue can not be answered on stackoverflow.com.
[x] My issue is not a request for new functionality that I am unwilling to build and contribute with a pull request.
[x] My issue is reproducible in the demo project.

Issue Description

There is different behaviour of presenting SideMenu via Storyboard and via code:
I tried to present SideMenu by calling:
present(SideMenuManager.default.menuLeftNavigationController!, animated: true, completion: nil)
SideMenu appeared successful, but MainViewController did not notified 'bout disappearing, viewWillDisappear and viewDidDisappear not called.
Its works fine on presenting Side menu via Storyboard with Segues

I have been able to reproduce your problem.
Unfortunately, this library has been out for a long time and you're the first one to request a fix, so I'm not inclined to dedicate my time for a fix. You are welcome to investigate a solution and propose it to the library.
Using breakpoints, there is no specific SideMenu code that is calling appearance events. It is all happening (inconsistently) as part of the transition APIs built by Apple.

I think I may have some useful feedback regarding this issue.
It all comes down to this line in SideMenuManager :
forMenu.modalPresentationStyle = .overFullScreen
Modal Presentation style decides whether system callbacks such as viewWillDisappear will be called on presenting view controller.
Problem is, that when you're using segues, it overwrites the modal presentation style in prepare(forSegue:) the modalPresentationStyle is set to default value, which is fullScreen. fullScreen causes viewWillDisappear to be called on presenting View Controller.
Maybe this library could provide a custom segue, instead of using the default present segue, but I'm not sure this is what the author of this library intends.. It might add some overhead to setup of the menu.
Instead, what you can do is, in your case since you want to present the menu manually from code using present(viewController:), prior to actually presenting the viewcontroller, change it's modalPresentationStyle to .fullscreen like this:
SideMenuManager.default.menuLeftNavigationController.modalPresentationStyle = .fullScreen
I personally have run into the OPPOSITE issue. I'm opening the menu via storyboard segue, but since the menu does not cover the whole screen, I don't want the view will appear and view will disappear methods to be called on my presenting view controller.
Therefore, what I personally did for my project is, that in prepare(forSegue:) method I set the modalPresentationStyle to .overFullScreen (as in the code of the library).
Maybe it would be nice to add this information to documentation or somewhere, so that other people don't waste their time figuring out issues related to viewWillDisappear etc being called/not called, due to the modalPresentationStyle.
I hope that helps.

@lukas1 you absolutely right


Python editor shows wrong line numbers

When you have a script that has empty lines at the beginning, we are seeing wrong line numbers on error reporting. This is probably a side effect of trimming the lines and ignoring them.
In the example below, line 7 should have been line 11.

Removing the lines at the top then give the right line number on the reported error

I believe this is a function of the kernel - or some other logic in lab - that is trimming preceding lines.  Here's a similar issue from a notebook...

This is not an Elyra issue but regular Kernel/Notebook as commented above by Kevin.