[Storage] Fix service operations with account SAS

Resolves #24156
As part of the latest beta release, we introduced a regression that caused certain service operations (e.g., list_containers()) to fail when using an account SAS as the authentication method. This was due to the modifications that were made to the generated code as part of the move to the latest version of autorest/python. One of the custom directives we added wasn't fully correct and caused URLs to be malformed with certain service operations using account SAS.
This change modifies the custom directive and re-generates the service operations code to address the issue. This change also introduces a series of tests that would have helped to catch this issue before release and can help prevent future, similar regressions.

API change check for azure-storage-file-datalake
API changes are not detected in this pull request for azure-storage-file-datalake

API change check for azure-storage-queue
API changes are not detected in this pull request for azure-storage-queue

/azp run python - storage - tests


Please reset the Seattle player limit to 24

A 32 player limit creates chaos and lowers the framerate of the game. It feels too crowded and hurts my latency. It makes it less likely for a player to get their preferred class and makes certain classes harder/easier to play.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I would prefer a 24 player limit.
A clear and concise description of what you want to happen.

32 players is not intentional. Will be fixed soon.


Fix: make the data_sources' name unique

Data_sources' name should be unique since it should be uniquely identified from the user interface, as well as when sudo -u redash bin/run ./manage.py ds delete is called.
Ref: https://github.com/EverythingMe/redash/issues/277

This will only apply the change to new installations that use the database create_tables command. For existing ones, you need to add a migration. To save you the trouble, here it is (you might need to verify the syntax):
# migrations/0007_make_ds_name_unique.py
from redash.models import db

if __name__ == '__main__':
    db.connect_db()

    with db.database.transaction():
        #  Make sure all data sources names are unique. Fix those that aren't.
        db.database.execute_sql("""UPDATE data_sources
SET name = new_names.name
FROM (
    SELECT id, name || ' ' || rank as name
    FROM (SELECT id, name, rank() OVER (PARTITION BY name ORDER BY created_at DESC) FROM data_sources) ds WHERE rank > 1
) AS new_names
WHERE data_sources.id = new_names.id;
""")
        # Add unique constraint on data_sources.name.
        db.database.execute_sql("ALTER TABLE data_sources ADD CONSTRAINT unique_name UNIQUE (name);")

    db.close_db(None)

Got it, however, that migration code doesn't guarantee unique for the new name though, for example, if I have: test, test, test 2
It will rename  the second one to test 2, which is already used.

Nice catch. Applying name + id only to the duplicates looks reasonable to me.
I think that having unique constraint is a good move regardless. Also changing DELETE and other operations to use id is a good move too.

Merged manually in https://github.com/EverythingMe/redash/commit/e25b86b10daf57e833530d78a8c073a0aded0f51.
Thanks!


[Publisher] Bug when publishing an API

When a user tries to publish an API which has no previous version while checking the checkbox  no proper error message shown to the end user and following logs in the console

Seems that you have api products as well. This error is related to https://github.com/wso2/product-apim/issues/6164


Issues

I'd like to be able to keep track of issues for each element or action, so if a feature has already been requested for an area we can route folks there.

Can we automate the creation using a collection?

I will just depend on creating them as needed.


Add API performance summary and API throttle summary widgets

Description:
Add widgets to show

Response time over time  of selected API(s)(API performance summary)
Total throttled out request count over time  of selected API(s)(API throttle summary)

Fixed with https://github.com/wso2/analytics-apim/pull/1157


Error: release-please failed: GitHub Actions is not permitted to create or approve pull requests

TL;DR
Error: release-please failed: GitHub Actions is not permitted to create or approve pull requests
Expected behavior
No response
Observed behavior
No response
Action YAML
on:
  push:
    branches:
      - main

permissions:
  contents: write
  pull-requests: write

name: release-please

jobs:
  release-please:
    runs-on: ubuntu-latest
    steps:
      - uses: google-github-actions/release-please-action@v3
        with:
          release-type: node
          package-name: typos-vscode

Log output
✔ Starting GitHub PR workflow...
✔ Successfully found branch HEAD sha "bd5d4ea88c70e234e34e9b97e4401258424f6c62".
✔ Successfully created branch at https://api.github.com/repos/tekumara/typos-vscode/git/refs/heads/release-please--branches--main--components--typos-vscode
✔ Got the latest commit tree
✔ Successfully created a tree with the desired changes with SHA 6dc6d70058023d0000a675c9f53e1b34f574ce4f
✔ Successfully created commit. See commit at https://api.github.com/repos/tekumara/typos-vscode/git/commits/de21fa40fc9eb21569ec85358b4abda8153f7ad6
✔ Updating reference heads/release-please--branches--main--components--typos-vscode to de21fa40fc9eb21569ec85358b4abda8153f7ad6
✔ Successfully updated reference release-please--branches--main--components--typos-vscode to de21fa40fc9eb21569ec85358b4abda8153f7ad6
Error: release-please failed: GitHub Actions is not permitted to create or approve pull requests.

Additional information
See https://github.com/tekumara/typos-vscode/actions/runs/4842582398/jobs/8629626808#step:2:235

To resolve, on the repo settings make sure "Allow GitHub Actions to create and approve pull requests" is checked:

Perhaps this could be added to the readme?

Can this be configured on the workflow level in the permissions field?
// .github/workflows/release.yml
permissions:
  contents: write
  pull-requests: write

Those should propagate to the GITHUB_TOKEN secret set by GitHub Actions.
If not, I suppose you should create a scoped PAT that allows those permissions and provide it as the token argument to the release please action.


Bump ot version to 0.28.0

I've created #108 to track changes required in pkg/processor/cascadingfilterprocessor/processor_test.go in order to reenable the tests there


update russian translation

done on translations touches. another one that needs conflict fix. also setting got improved stealth translations

copied over from your fixes and committed from my end. Still 2 terms got Google translation after that.


ext_proc: Deflak the inactive test

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @phlax


[Snyk] Upgrade @mui/icons-material from 5.14.3 to 5.14.7

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @mui/icons-material from 5.14.3 to 5.14.7.
: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 2 versions ahead of your current version.
The recommended version was released 21 days ago, on 2023-08-29.

Release notes

Package name: @mui/icons-material

5.14.7 - 2023-08-29Aug 29, 2023
A big thanks to the 11 contributors who made this release possible. This release focuses primarily on 🐛 bug fixes, 📚 documentation, and ⚙ infrastructure improvements.
<EMAIL_ADDRESS>
[Autocomplete] Fix listbox opened unexpectedly when component is disabled (#38611) @ mj12albert
[Select][material-ui] Fix select menu moving on scroll when disableScrollLock is true (#37773) @ VishruthR

<EMAIL_ADDRESS>
[useButton][base-ui] Accept arbitrary props in getRootProps and forward them (#38475) @ DiegoAndai

<EMAIL_ADDRESS>
[system][zero][tag] Add support for sx prop (#38535) @ brijeshb42

Docs

[docs] Number Input docs fixes (#38521) @ mj12albert
[docs] Show all the code in the usage section (#38691) @ oliviertassinari
[docs][joy-ui] Change the customization and how-to guides docs tree (#38396) @ danilo-leal
[docs][lab][LoadingButton] Improve loading prop documentation (#38625) @ sai6855
[docs][material-ui] Format key prop JSDoc description in Snackbar component code correctly (#38603) @ jaydenseric

Core

[core] Add use-client to custom icons (#38132) @ mj12albert
[core] Remove unnecessary @ types/jsdom (#38657) @ renovate[bot]
[core] Improve sponsors GA labels (#38649) @ oliviertassinari
[core] Fix ESM issues with regression tests (#37963) @ Janpot
[core] Potential fix for intermittent ci crashes in e2e test (#38614) @ Janpot
[docs-infra] Mark unstable components with a chip in the nav drawer (#38573) @ michaldudak
[docs-infra] Adjust the Material You playground demo design (#38636) @ danilo-leal
[docs-infra] Hide the SkipLink button if user prefers reduced motion (#38632) @ DerTimonius
[website] Add tiny fixes the homepage Sponsors section (#38635) @ danilo-leal

All contributors of this release in alphabetical order: @ brijeshb42, @ danilo-leal, @ DerTimonius, @ DiegoAndai, @ Janpot, @ jaydenseric, @ mj12albert, @ michaldudak, @ oliviertassinari, @ renovate[bot], @ sai6855, @ VishruthR

5.14.6 - 2023-08-24 Read more

5.14.3 - 2023-08-01 Read more

    from @mui/icons-material GitHub release notes

Commit messages

Package name: @mui/icons-material

8a09d53 v5.14.7 (#38698)
a392609 [docs-infra] Mark unstable components with a chip in the nav drawer (#38573)
2ae2e79 [docs] Number Input docs fixes (#38521)
f2a254e [core] Add use-client to custom icons (#38132)
a4d9cb1 [Autocomplete] Fix listbox opened unexpectedly when component is `disabled` (#38611)
b14e8b8 [docs] Show all the code in the usage section (#38691)
7fa043b Bump @ types/react to ^18.2.21 (#38659)
f5d6f6a [system][zero][tag] Add support for sx prop (#38535)
93aefd5 Bump chai to ^4.3.8 (#38663)
56341cd Bump markdownlint-cli2 to ^0.9.2 (#38670)
f031765 Bump eslint to ^8.48.0 (#38669)
0fe16e5 Bump aws-sdk to ^2.1445.0 (#38668)
cdacc86 Bump actions/checkout action to v3.6.0 (#38667)
0d902b2 Bump rollup to ^3.28.1 (#38665)
419b826 Bump concurrently to ^8.2.1 (#38664)
b1be4d0 Bump MUI X (#38661)
de3b47f Bump @ types/node to ^18.17.12 (#38658)
36f65c0 [core] Remove unnecessary `@ types/jsdom` (#38657)
6ef9819 Bump @ types/doctrine to ^0.0.6 (#38656)
d448311 Bump @ googleapis/sheets to ^5.0.4 (#38653)
150ad3d Bump @ definitelytyped tools to ^0.0.169 (#38652)
4b50800 Bump serve to ^14.2.1 (#38666)
c87298f [core] Improve sponsors GA labels (#38649)
8212d3d [core] Fix ESM issues with regression tests (#37963)

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

Thanks for the PR!
Any successful deployments (not always required) will be available below.
API available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

lets merge mui packages together


Clean up redux store/delete redundant and unused code

Summary
It seems like there are redux actions/reducers that serve a single narrow purpose that might logically be combined, and there are definitely 3 reducers, and their associated actions, which are unused/ have been made redundant by subsequent updates.  reducers/behavior, reducers/navigation, reducers/temperature are all unused.  I'd like to at least clean out the unused code, and maybe see if any others make sense to combine.
Motivation
Code clarity/readability/maintainability
Describe alternatives you've considered
We could leave it as is, but as this app grows in complexity, and as new devs onboard, sorting through the redux folder structure and making sense of changes in the redux logs may be unnecessarily difficult.
Additional context

I'll do this.


⚠ Everything Hub has degraded performance

In 168ec4e, Everything Hub (https://hub.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 4129 ms

Resolved: Everything Hub performance has improved in b62ccf3 after 10 minutes.


feat: Lift and implement methods from WalletProvider to NetworkInfoProvider

Context
As part of the refactor to remove WalletProvider, ledgerTip, currentWalletProtocolParameters, and genesisParameters should be moved to NetworkInfoProvider, and then the WalletProvider removed completely. The DbSyncProvider needs to also be extended to support these new methods.
Proposed Solution
N/A
Important Changes Introduced
New feature section: (bae10f3ee3bf8a53d488e6d306f96b1a64473edd)

extend NetworkInfoHttpService with new endpoints: /tip, /genesis-params and /protocol-params
implement DbSynNetworkInfoProvider methods lifted from WalletProvider interface
create db queries and mappers
extend openApi.json schema
add http service tests

Refactoring section: (c549ed450e39fc577a0b4d87459261d037870cb6)

core: extend NetworkInfoProvider, remove WalletProvider interface
cardano-services-client: extend networkInfoHttpProvider with methods
blockfrost: lifted methods from wallet to networkInfo provider, tests
wallet: remove TrackedWalletProvider, extend TrackedNetworkInfoProvide
wallet: update and fix all e2e, load and integration tests
web-extension: update e2e tests

Fixup of another misnamed URL path 5fec9230c1c8321945272546d7d36e12707c8d8c.


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3
Also their maintainer says they probably won't ever use it: http://stackoverflow.com/questions/24844901/bowers-bower-json-file-version-property

Sounds good to me.


ARROW-1253: [C++/Python] Speed up C++ / Python builds by using conda-forge toolchain for thirdparty libraries

@pcmoritz I removed the travis_script_plasma.sh and combined the common bits with travis_script_python.sh; it seemed like there was some redundant work and would be easier to test everything in a single build. Let me know if I messed something up

@xhochy I added ninja to the toolchain for potentially faster builds, we will see how it impacts runtimes

Appveyor looks happy so I'm going to merge this https://ci.appveyor.com/project/wesm/arrow/build/1.0.737


Network sync refactoring (part 3)

This is the third step towards #8686.
As https://github.com/paritytech/substrate/issues/8686#issuecomment-1045993814 suggests, this moves light.v1 proto scheme and a bunch of data structures related to sync into new sc-network-light crate, which sc-network now depends on.
As in previous PR this is an implementation detail of sc-network for now.
A few minor changes, mostly just moving files around.

@bkchr friendly ping here before there are merge conflicts

/tip medium

Ty @nazar-pc :) If you provide your polkadot address, I will call the bot again.

bot merge

If you provide your polkadot address, I will call the bot again.

Done, thanks!

/tip medium

bot merge


Bug：cookies is always be nill in HTTP::Client::Response with pp

r = HTTP::Client.get("https://httpbin.org/cookies/set?name=abc")
pp r
pp r.cookies

result
r # => #<HTTP::Client::Response:0x1091c9cb0
        @body=
         "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>Redirecting...</title>\n
Redirecting...
\n
You should be redirected automatically to target URL: /cookies.  If not click the link.",
        @body_io=nil,
        @computed_content_type_header=nil,
        @cookies=nil,
        @headers=
         HTTP::Headers{"Access-Control-Allow-Credentials" => "true",
          "Access-Control-Allow-Origin" => "*",
          "Connection" => "keep-alive",
          "Content-Length" => "223",
          "Content-Type" => "text/html; charset=utf-8",
          "Date" => "Fri, 15 Sep 2017 04:04:01 GMT",
          "Location" => "/cookies",
          "Server" => "meinheld/0.6.1",
          "Set-Cookie" => "name=abc; Path=/",
          "Via" => "1.1 vegur",
          "X-Powered-By" => "Flask",
          "X-Processed-Time" => "0.000708818435669"},
        @status_code=302,
        @status_message="FOUND",
        @version="HTTP/1.1">
r.cookies # => #<HTTP::Cookies:0x10aa71b40
                @cookies=
                 {"name" =>
                   #<HTTP::Cookie:0x10a1f9eb0
                    @domain=nil,
                    @expires=nil,
                    @extension=nil,
                    @http_only=false,
                    @name="name",
                    @path="/",
                    @secure=false,
                    @value="abc">}>

Not a bug: cookies are computed lazily: https://github.com/crystal-lang/crystal/blob/c0cac8d3b5d46d65344c531a605d7694ffd08d5d/src/http/client/response.cr#L39-L41

But Is it better to pretty print in HTTP::Client::Response?

The method p obj invokes obj.inspect and that shows the value of all instance variables. We could override inspect to expand all lazy instance vars, though. I'm not sure.

@asterite I feel that inspecting something shouldn't trigger any side-effects. So I think its a bad idea.

@RX14 May be change the state of cookies, such like below i don't know.
r # => #<HTTP::Client::Response:0x1091c9cb0
        @body=
         "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>Redirecting...</title>\n
Redirecting...
\n
You should be redirected automatically to target URL: /cookies.  If not click the link.",
        @body_io=nil,
        @computed_content_type_header=nil,
        @cookies=[lazy_loading],

Maybe we can just rename @cookies to @lazy_cookies.
In any case, this will happen with lazy loading everywhere. I don't think there's anything we want to do here.


Cannot use in App Engine

After the commit https://github.com/naoina/go-stringutil/commit/915b2f950394c54fec72e8462a5d223e3fd5f775 this library depends on code using unsafe which is forbidden in the App Engine runtime. Is there some way to get rid of the unsafe import? There is a build constraint appengine that can be used if needed.
I opened the issue here because github.com/naoina/toml uses this library. It would be also ok if it's changed in the other project.

@ernestoalejo
Thank you for your report.
I made a change so that it does not use unsafe in the latest commit https://github.com/naoina/go-stringutil/commit/6b638e95a32d0c1131db0e7fe83775cbea4a0d0b.
I think this issue has been resolved, but please check at your end because I don't have used appengine.

I have deployed a new version of the app with the new code and it's ok now. Thank you!


Use circle-ci builds to make docker images for PR

I changed the docker image used from circleci/golang:1.10 to golang:1.10 because,
surprisingly enough, there seems to be an incompatibility of the tar and gzip tools
between the machine executor and the docker images built by circle-ci. It makes it
impossible to attach a workspace inside a container which as been persisted from
a machine executor.
New/Changed jobs:

promu: factorizes promu building for following build and crossbuild steps
crossbuild: replaces current build job which does a promu crossbuild
crossbuild-linux-amd64: calls promu crossbuild to only build linux/amd64

New/Changed workflow:

prometheus-pr: builds pull requests

 -- promu -+- crossbuild-linux-amd64 -+- docker_push_pr
           |                          |
           +- test                    +- crossbuild

crossbuild step lasts 1 hour so we first use build to only make the binary needed
for the docker image and we build that docker image. This allows to have a docker
image ready to test in a few minutes. Then we crossbuild.
Docker tags are named pr-<github-pr-#> and pushed to quay.io/prometheus repository.

prometheus-master-and-releases: replaces prometheus workflow

 -- promu --- test --- crossbuild -+- docker_hub_master_and_releases
                                   |
                                   +- docker_hub_release_tags

This does exactly what old prometheus workflow used to except it also builds a
master like image for each release-.* branches.
Signed-off-by: Sylvain Rabot<EMAIL_ADDRESS>

It seems that random Joes like myself can't access the $QUAY_LOGIN & $QUAY_PASSWORD and thus can't push on quay.io .
I also came to think that it would be best to have a different repo for PR to avoid polluting the official one, quay.io/prometheus/prometheus-pr maybe ?

@SuperQ @simonpasquier Could you review this ?

Interesting idea, I need to think about this a bit.
One thing I was considering was a way to improve the crossbuild speed by spawning multiple parallel builds. That would reduce the complication added by separating amd64 build. We also want to be able to produce non-amd64 docker images eventually which would mean we need the full crossbuild anyway.

@SuperQ did you think about this ?

I see how it could be useful, for instance to help with prombench (see the description of #4685 too) but I'm a bit afraid that it would clutter the list of tags and history in the registries.
https://hub.docker.com/r/prom/prometheus/tags/
https://quay.io/repository/prometheus/prometheus?tab=tags
https://quay.io/repository/prometheus/prometheus?tab=history

@simonpasquier Yes that's why I think we could push the PR docker image to a separate dedicated registry.


Ollama api key authentication

Feature request
I have Ollama hosted in a server with authentication. It provides api key and jwt token. I want to use my hosted server.
Why?
I want to use Ollama, since it have authentication it won't work with just setting host config.
Alternatives
Yes, a bearer token can be added while creating new Ollama
this.ollama = new Ollama({
    host: this.host,
    headers: { 'Authorization': `Bearer ${this.apiKey}` },
});

Additional context
https://github.com/ollama/ollama/issues/1053#issuecomment-2389752279

@gnpaone I will soon update so that you can set the api key in Ollama as well.

@gnpaone Hello, I updated code to add key option for Ollama. But I haven't done an accurate test. Can you try it and let me know the results?

Okay I'll test it

I'll do some troubleshooting from my side and follow up

I did some troubleshooting

there's api key and jwt token but I get 401 error even using curl, but basic auth is working fine ie<EMAIL_ADDRESS>using curl but not working in aicommit2 for some reason

Update: I've created a new pr in the ollama-js package repo, which should fix the issues and thus ollama can be initialized with
this.ollama = new Ollama({
    host: this.host,
    headers: { 'Authorization': `Bearer ${this.apiKey}` },
});

for api key
this.ollama = new Ollama({
    host: this.host,
    headers: { 'Authorization': `Basic ${this.base64encodedtext}` }, // username:password base64 encoded
});

for basic auth
This can be generalized something like
constructor({ host, apiKey, base64encodedText, jwtToken }:
  { host: string; apiKey?: string; base64encodedText?: string; jwtToken?: string }) {
  this.host = host;
  this.ollamaHeaders = this.createOllamaAuthHeader(apiKey, base64encodedText, jwtToken);
  this.ollama = new Ollama({
      host: this.host,
      headers: this.ollamaHeaders,
  });
}

createOllamaAuthHeader(apiKey?: string, base64encodedText?: string, jwtToken?: string) {
  if (apiKey) {
    return { 'Authorization': Bearer ${apiKey} };
  } else if (base64encodedText) {
    return { 'Authorization': Basic ${base64encodedText} };
  } else if (jwtToken) {
    return { 'Authorization': JWT ${jwtToken} };
  } else {
    return {};
  }
}

@tak-bro Actually there's a way for you test it
You can use docker to test it
docker-compose.yml:
version: "3.9"

services:
  ollama:
    image: ollama/ollama:latest
    restart: unless-stopped
    volumes:
      - ollama_net_data:/root/.ollama
    environment:
      OLLAMA_ORIGINS: "*"
    ports:
      - "11434:11434"
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: all
              capabilities: [gpu]
    networks:
      - ollama_net

  caddy:
    image: caddy:latest
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - caddy_data:/data
      - caddy_config:/config
      - ./Caddyfile:/etc/caddy/Caddyfile
    networks:
      - ollama_net

networks:
  ollama_net:
    driver: bridge

volumes:
  ollama_net_data:
    driver: local
  caddy_data:
    driver: local
  caddy_config:
    driver: local

Caddyfile:
http://ollamaapi.localhost {
   basicauth / {
      username passwordhash
   }

   header Access-Control-Allow-Origin "*"
   header Access-Control-Allow-Methods "GET, POST, OPTIONS, PUT, HEAD, DELETE"
   header Access-Control-Allow-Headers "Content-Type, Authorization"
   header Access-Control-Allow-Credentials "true"

   reverse_proxy / ollama:11434 {
      header_up Access-Control-Allow-Origin {http.request.header.Origin}
      header_up Access-Control-Allow-Credentials "true"
   }
}

(Replace passwordhash with bcrypt password hash where plainn text is the password)
http://<IP_ADDRESS>:11434 is ollama api as usual and same can be accessed via http://ollamaapi.localhost with authentication

Thank you for helping with troubleshooting.
I saw the PR you submitted to ollama-js. That would be the fundamental solution to this issue. Your issue seems like it will be resolved in aicommit2 after your PR to the ollama-js repository is applied.

I've fixed issue in ollamajs and that library works fine but for some reason aicommit2 overrides the headers. In ollama logs it's the Axios that's overriding it. Can you find out why that's happening or point out the code where ollama and axios are linked in the code so that I can troubleshoot?

Update: ollama-js maintainers has accepted and merged my pr with slight modifications.
I've created a PR that solves this issue.

@gnpaone Thank you! aicommt2 is updated! v2.1.9


Reason for bias=False hardcoded in x_proj

Hi! Thanks very much for the very clear paper and code release.
I have one question regarding the biases on the various linear projections in the Mamba block code--
https://github.com/state-spaces/mamba/blob/34076d664838588a3c97727b263478ab9f621a07/mamba_ssm/modules/mamba_simple.py#L77-L79
I understand why we want to always hardcode a bias in dt_proj but I couldn't think of a reason that it is impossible to have a bias in x_proj. However, it appears that MambaInnerFn does not allow a bias for x_proj to be passed, so it seems like a bias here is intentionally unsupported.
Is there something I've overlooked here, or is this a decision that was made based on some preliminary ablations, etc.?
Thank you!

Generally we prefer to not have bias in Linear layers (e.g. following PaLM, LLaMa). dt_proj needs a bias since we want softplus(dt) to fall within some range (e.g. 1e-4 to 1e-1).
I don't think we did an ablation with x_proj bias but I don't expect having a bias to help or hurt.

Thanks for the quick response! makes sense : )

Hi, I have a follow up question about dt_proj.bias: I am curious about the reason behind not adding bias with the dt_proj linear function here, but push the addition to cuda/triton kernel instead:
https://github.com/state-spaces/mamba/blob/34076d664838588a3c97727b263478ab9f621a07/mamba_ssm/modules/mamba_simple.py#L232-L235

Generally we prefer to not have bias in Linear layers (e.g. following PaLM, LLaMa). dt_proj needs a bias since we want softplus(dt) to fall within some range (e.g. 1e-4 to 1e-1). I don't think we did an ablation with x_proj bias but I don't expect having a bias to help or hurt.

For speed reason, though it's probably very minor now that pytorch's F.linear can fuse matmul and bias into 1 kernel.

Hi, another follow up question
https://github.com/state-spaces/mamba/blob/3b0dde5a20659073af5684e966a81981e614789e/mamba_ssm/modules/mamba_simple.py#L134C9-L141C82

Hi, I just have another question that is most similar to this issue, so I'll just ask here :)
I've looked through the issues but couldn't find a reason to manually calculate the input projection.
https://github.com/state-spaces/mamba/blob/3b0dde5a20659073af5684e966a81981e614789e/mamba_ssm/modules/mamba_simple.py#L134C9-L141C82
Why not just do, xz = self.in_proj(hidden_states) ?

As mentioned in the comment, bc We do matmul and transpose BLH -> HBL at the same time


rosjava_core-0.3.2

Another manual one

upstream repository: https://github.com/rosjava/rosjava_core.git
release repository: https://github.com/rosjava-release/rosjava_core-release.git
distro file: kinetic/distribution.yaml
previous version for package: 0.3.1-0

Waiting for another sync...


Upgrade rails-settings-cached. Fix specs. Prepare for settings select…

Upgrade rails-settings-cached.
Fix it: https://github.com/huacnlee/rails-settings-cached/pull/110
Fix specs.
Prepare for settings selection by key with coercion.
Upgrade test deps.

Coverage decreased (-0.4%) to 97.353% when pulling 0bef60f2f39d3dc83428ea64a2d2199ff04f4dc3 on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Coverage decreased (-0.5%) to 97.291% when pulling b0b69a9ece8e81595814adad3f4682a00c869de1 on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Yeah. I have upgraded rsc everywhere, but you can try.
Added checking for old defaults.
Within specs works well.
Now seems that we can update hash fields with merge.
It works when we select key in options.
Saving of plain hashes disallowed.

Rollback rails-settings-cached v0.5.3 support.
Add specs for model instance.
Ability to save within namespaced keys.
Add field_name helpers.
Add save method for model instance.
Added initial docs for keys.

Seems that something failed in CI. i will fix

Coverage decreased (-36.8%) to 60.959% when pulling 4aa4691925f5cc84398eb25fc47868c8390f8cea on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Coverage increased (+0.9%) to 98.652% when pulling 3121cd34003593d8a56f1bbc5cfeebb0762847be on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Coverage increased (+0.9%) to 98.652% when pulling 2e3834a72e141100d3025c1144a5bb59d3ca9be8 on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Thanks for pr 👍

Coverage increased (+0.9%) to 98.655% when pulling 76d8c721bf7853b013c6d24e97cbffa68e9031af on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Coverage increased (+0.9%) to 98.655% when pulling 1e404b861712ac371512b164a3009f3775f4cf40 on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.

Coverage increased (+0.9%) to 98.655% when pulling 0d48cbb8c06d8e7cc37ffac5c5a7c807fb85301f on merqlove:upgrade_rails_settings_cached_0_6_4 into 75e87b5ad386b7b08b950c9bc0169ba6321137d3 on artofhuman:master.


TitleInfo Spacing

Describe the bug
The TitleInfo for each component is too far to the right.
To Reproduce
Open vitessce.io and look at "Data Set" or "Layer Controller" in Linnarsson.
Expected behavior
The spacing should be offset a bit from the rightmost edge.
Screenshots

Environment:

Release or git hash: master fe21a68
Browser: Firefox
Browser version: 78.0.2

I think these values should be flipped
https://github.com/hubmapconsortium/vitessce/blob/master/src/app/PubSubVitessceGrid.js#L70
it should be changed to
const margin = 5;
const padding = 10;


Test in different browsers

Inscriptions weren't loading just now when I looked at them in safari. Try out different browsers and see how they do.

It works, must have been a localhost thing.

Actually, we should check after deploying. Maybe it's an issue with the latest version and not the deployed version.

Latest iOS --> browsers (chrome, brave, safari) do not load images for homepage or inscription page, iirc raw content page does load though. Cleared cache / hard refreshed, no change.

I think this might be an issue with your browser, just tested on iOS Safari and everything worked.

Just tested desktop Chrome, Firefox, and Safari, and mobile Safari, all worked.
@batcavekid This might be issue with a router, proxy, vpn, or other local network configuration.


Shorten stack traces on errors and failed tests

It would be very nice to have an option to see only useful error messages rather than showing the whole stack trace.

@mataps agreed. @ezzatron recently submitted a useful PR to the leo matcher library, maybe this could be integrated into the core.

or something similar

The Leo PR is a bit of a different situation, I think. In that particular case, the exception is always Leo's own exception, so it can be "trimmed" easily by looking at namespaces in the trace.
There are definitely some similarities though. I'll have a look, and see what can be done.

Actually, @brianium, thinking about it again, this issue is from before that Leo PR was accepted. It's quite possible it's referring to Leo's assertion stack traces, and may already be fixed.
@mataps Could you provide some example code / output?

Never mind my comment above. This is definitely still an issue outside of Leo as well. It shouldn't be a big deal to do something similar for Peridot's traces, like I did for Leo's in peridot-php/leo#18.

Released in 1.19.0 🎉


feat: restructure to work for all platforms

PR progress checklist (to be filled in by reviewers)

[ ] Changes to documentation are appropriate (or tick if not required)
[ ] Changes to tests are appropriate (or tick if not required)
[ ] Reviews completed

What type of PR is this?

Primary type

[ ] [build]    Changes related to the build system
[ ] [chore]    Changes to the build process or auxiliary tools and libraries such as documentation generation
[x] [ci]       Changes to the continuous integration configuration
[x] [feat]     A new feature
[x] [fix]      A bug fix
[ ] [perf]     A code change that improves performance
[ ] [refactor] A code change that neither fixes a bug nor adds a feature
[ ] [revert]   A change used to revert a previous commit
[ ] [style]    Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

[ ] [docs]     Documentation changes
[ ] [test]     Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.
Related issues and/or pull requests

Follows-on from discussion in #71 -- CC: @aboe76.
Semi-automated using https://github.com/myii/ssf-formula/pull/377.

Describe the changes you're proposing

Restructure (mainly the os*map.yaml files) to get this formula working for all possible platforms.
The only one that hasn't been enabled yet is Oracle Linux 7, since there doesn't appear to be a networkd package/service available.  The changes made do still work; the formula/tests could be updated later to accommodate for this, allowing that instance to be enabled as well.
The CI changes do not yet include CentOS Stream 8, even though those pre-salted images are now available.  This will be done in an effort to push those out across all formulas, using the ssf-formula.
Pillar / config required to test the proposed changes

As-is.
Debug log showing how the proposed changes work

As seen in GitLab CI.
Documentation checklist

[ ] Updated the README (e.g. Available states).
[ ] Updated pillar.example.

Testing checklist

[ ] Included in Kitchen (i.e. under state_top).
[ ] Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
[ ] Updated the relevant test pillar.

Additional context

@aboe76 So after https://github.com/saltstack-formulas/systemd-formula/pull/72#discussion_r725526601, is there anything else that needs to be done here?

@myii, no this is great, I'm fine with it.

Appreciate the review, @aboe76.


Should be packaged as a module

Can you consider packaging the program as a PyPi package? This would help integrate the code in other software immensely.

As I mentioned in issue #1, I will do this in the future.

@Atharv-Attri Hey, I have published this repo as PyPI package at https://pypi.org/project/locationcrypto/.
Apologies for the long delay.


NPM v7

explore the subject area
decide whether to switch from Yarn to NPM

resources:
https://github.blog/2021-02-02-npm-7-is-now-generally-available/
https://github.blog/2020-10-13-presenting-v7-0-0-of-the-npm-cli/

Yarn v3?

Pnpm?


Selection Sort

❗Write Code in Only One Language (CPP, C, Java, Python)
Give File Name : Selection_Sort ✅ In respective language folder
#📑 DESCRIPTION
Selection Sort

Problem Statement
Sort any given unsorted array of side n in descending order using the selection sort algorithm.
Example
Input :
n = 5
arr = [8, 6, 2, 5, 1]

Output :
1 2 5 6 8

Sample Input 1
6
2 13 4 1 3 6

Sample Output 1
1 2 3 4 6 13

Sample Input 2
5
9 3 6 2 0

Sample Output 2
0 2 3 6 9

Constraints
1 <= N <= 10^3
0 <= arr[i] <= 10^5
Time Limit: 1 sec

Problem

hey @Chitresh-code @lilmistake  I would like to work on this , can you please assign it to me

@Chitresh-code can you please assign this work to me I want to contribute

@gitaditee if you can code in java or c you can do it as the solutions in Python and C++ are already merged.
Assigning it to you.

@Chitresh-code yes sure I"ll do  and can you assigned me for others repo also

@gitaditee I am only maintaining this repo for Hacktoberfest, but if you want to you can follow me as I regularly upload issues with DSA questions in this repository.
You can solve them

Ok I'll follow your profile,, I have  submitted a pull request can you please check @Chitresh-code and I'll be grateful if you merge it because as a it's my first contribution.

I can't see one by you, make sure you submitted the PR; please link it here as well.

https://github.com/gitaditee/DSA_Worksheet @lilmistake check if you can see

Yes I have submmited its also showing on my hacktoberfest account

Looks like you created a PR for your repo and merged it as well.
Go to https://github.com/Chitresh-code/DSA_Worksheet and see if you find an option that says something along the lines of "recent changes in XYZ create pull request". Click on the button and create a PR from there.

Now check if you can see?
@lilmistake

can you tell me why you have not accepted?
I'll correct the issue @lilmistake

I'll merge your PR on verifying the result or let you know if changes are required, thanks for contributing!

Sure thanks please inform me if any changes are required
@lilmistake

@Chitresh-code can you please assign this work to me I want to contribute


Cleanup is not $dir aware

Regression after e4e76d3a32fcc33ca6a0fe6b4d3b99988e6863be

/cc @h404bi

Since Get-ChildItem does not return full path, but only file names. Should be enough to go with $filepath = Resolve-Path "$dir\$file"
https://github.com/lukesampson/scoop/blob/0029f0b29dda9d82e72e1cf53183231cd8bf79d4/libexec/scoop-cleanup.ps1#L49

I see, how about $filepath = fullpath $file

I don't know. Maybe. This was first untested idea.
Test it and you will see.

I can't reproduce, since Resolve-Path works for me. I'll change it to $filepath = fullpath $file, but in PR #2897
https://github.com/lukesampson/scoop/pull/2897/files#diff-c2a7e0e3e8869b7de54b5f172fc77009R1265

Should we revert https://github.com/lukesampson/scoop/commit/e4e76d3a32fcc33ca6a0fe6b4d3b99988e6863be until this is sorted out?

@rasa fixed it on https://github.com/lukesampson/scoop/pull/2897/commits/e7f0977db065a24f597df6b2651504a3ac9a6c52, waiting for reviewing and merging.


crash building in SBCL with certain high safety low speed compiler policy

When I build with a certain high-safety, low-speed compiler policy, it goes into the debugger in SB-C::VOP-OPTIMIZE-BOUNDP-OPTIMIZER.  Using SBCL 2.1.9 and the cl-ppcre-20190521 distribution of CL-PPCRE, which is the current Quicklisp distribution.  I set compiler policy with the following series of commands: (log:)
* (sb-ext:restrict-compiler-policy 'speed 0 0)
NIL
((SPEED . 0))
* (sb-ext:restrict-compiler-policy 'safety 3 3)
((SAFETY . 3))
((SPEED . 0))
* (sb-ext:restrict-compiler-policy 'space 0 0)
((SAFETY . 3))
((SPEED . 0) (SPACE . 0))
* (sb-ext:restrict-compiler-policy 'debug 3 3)
((SAFETY . 3) (DEBUG . 3))
((SPEED . 0) (SPACE . 0))

See attached log showing build going into debugger.
sbcl-crash-with-low-speed-high-safety-loading-cl-ppcre-log.txt

That's not really a cl-ppcre issue, but an SBCL one, isn't it?

And I don't see this with SBCL 2.1.11

Confirmed, not seen in SBCL 2.1.11 [specifically SBCL <IP_ADDRESS>-10ea30f55 on MacOS, built from sources]. Seems it is fixed, so thank you to the SBCL developers.


GH-2583 ProducerFactory.createProducer argument @Nullable

Resolves: #2583
ProducerFactory.createProducer argument txIdPrefix is non-nullable which causes kotlin compiler to emit warning if implementations declare txIdPrefix as nullable txIdPrefix: String?
This PR changes signature of ProducerFactory.createProducer so that txIdPrefix is @Nullable and also adds unit test to verify compilation, and to verify that future versions of Kotlin won't cause compile errors.
Current users of kotlin who implemented ProducerFactory.createProducer(txIdPrefix) with txIdPrefix: String (non-nullable) will start seeing kotlin compiler warning that their signature is not matching base signature.

Did I had to amend my initial commit, or is it ok if requested changes are in second separate commit?

Right. New commit is fully OK.
We squash them on merge.
Thank you!

Cherry-picked to 2.9.x as https://github.com/spring-projects/spring-kafka/commit/b17a04517d74c9adc80f26313e79bc8b54068dad


Philips Tv codes

Only the Turn on/off volume up/down/mute buttons work other source buttons doesnt work on 40pf3208h/12.

In this case you need to create your own json file. Sharing the file would be great.

But there isn't any direct HDMI etc. buttons. Any Idea how to find them.


Grid at edges and on grid points

We can find a model grid to be interpolated, if the values are in the middle of everything. However, if we choose a parameter which is in the models, the grid should be smaller. Also need to handle grid near edges.

This problem is solved.


fix(styles): update yellow-700 and red-600 for a11y

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[x] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
red-600 and yellow-700 failed accessibility tests in certain scenarios.
Issue Number: #204
What is the new behavior?
red-600 and yellow-700 will pass accessibility tests.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

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

GitHub release
v6.4.0

Your semantic-release bot :package::rocket:


Frankreh/graceful test fallback

Fixes #137
I realize there are lots of ways this could have been addressed.

Thank you!


Trigger rebuild.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

Triggering rebuild and render to try and address #34

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge/gsl this build is failing because of an unsatisfiable dependency on OSX and Linux c_compilertoolchain_c. Any ideas on how to resolve this? I'm lost on the details of what conda-build is doing here I'm afraid.

I would be OK just skipping the toolchain. What do you think @isuruf?

@conda-forge/gsl, rerunning the CI using identical changes in #36, shows that the CI passes fine now (for some reason). Can you consider merging this PR and closing #36?
cc @jeromekelleher

Thanks @duncanmmacleod! I've pushed an update to force a rebuild, which will hopefully pass also.
Out of interest, what has changed to make you think this would work?

@jeromekelleher, I think last week I was able to reproduce your failures, but today the local builds passed (macOS local, and linux under docker), which suggested some sort of transient problems. I have no idea what actually might have changed in the mean time. Fingers crossed.

It works; hooray! @conda-forge/gsl can someone push the merge button here please?


Not working in side modal

Hi,
I am having an issue where I put the custom google login function inside Modal, and it is not working. But if I put it outside the modal it is working just fine.
the code is like this:
googleLogin(){
//google login code
}

render: function() {
 return(
  <Modal>
    <TouchableHighlight onPress={() => {this.googleLogin()}}></TouchableHighlight>
  </Modal>
 );
}

and if i modified to get the code without Modal it is working fine
googleLogin(){
//google login code
}

render: function() {
 return(
    <TouchableHighlight onPress={() => {this.googleLogin()}}></TouchableHighlight>
 );
}

Any idea how this happen?
Thanks in advance

well that's a great question. I have to investigate ;)
is it better if you use Navigator to present your modal (as pointed in RN documentation) ?

Hi, I chose the Navigator solution over modal. So, I dont know if it is better.

Just ran into this issue myself, any plans to resolve this? If not, it would be good to mention it in the documentation somewhere as a fair warning

I've experienced this as well and have found it's to do with having multiple stacked views (root view and modal overlay), and then trying to render another one over it (Google login/auth page).
Had luck in getting it working if I close the modal before I run the google login code (it render's a blank page, however, if I have an animation on the modal so try without one).
Using iPhone 6s plus, iOS 10

Fixed in https://github.com/devfd/react-native-google-signin/commit/21f8a3097b26a7af061c261da01788a62abb29a0.


Documentation discrepancy - tsconfig not tsConfig

🐛 Bug Report

I want to specify a separate tsconfig.test.json for ts-jest as I am using Next.js which has a hard-enforce on jsx: preserve and therefore my initial tsconfig.json is not sufficient.
The current documentation page on tsconfig mentions you can do this by setting global.ts-jest.tsConfig to the filepath to your alternative tsconfig configuration. Could not get this working.
After much debugging/googling around it worked when I tried all lowercase (global.ts-jest.tsconfig), not camelCase (global.ts-jest.tsConfig).
To Reproduce
Documentation link - https://huafu.github.io/ts-jest/user/config/tsConfig

pls use the link https://kulshekhar.github.io/ts-jest . The link you are using is not the correct one :)

tsConfig was deprecated in v26 and removed in v27

@ahnpnl. Thanks for that. Just FYI though, the URL I referenced is the #1 result on Google for "ts-jest tsconfig"


Have an option to publish the R Script to Azure ML Experiment, Web Service and Azure ML Store

Consider the option to have an RScript which uses Azure MAML inputs and outputs published to Azure ML Lab experiments, and publish as Web Services if possible.
Provide validation checks to make sure scripts will run in Azure.

@dngoins. Yes! This operationalization of R code is on our radar.


Feature/add support for nip 28 events

Since NIP-28 enabled nostr clients have become so popular lately, I figured it would be nice to have support for the NIP-28 kind range on nostr.info.
NIP-28 spec can be found here: https://github.com/nostr-protocol/nips/blob/master/28.md

Thanks!


Add optional "lookupHeader" to replace default header

Can we have optional "lookupHeader" to replace default header "Accept-Language"?
i18next
      .use(FilesystemBackend)
      .use(i18nextMiddleware.LanguageDetector)
      .init({
        detection: {
          order: ['header', 'querystring'],
          lookupQuerystring: 'lng',
          lookupHeader: 'x-language'
        },
      });

feel free to provide a PR taking value from options: https://github.com/i18next/i18next-express-middleware/blob/master/src/languageLookups/header.js#L12 and default to the "Accept-Language" if not set

@jamuhl would you be able to review my PR?

@jamuhl Would you mind update this option in README.md? Thanks.

@Dominic-Preap was added to readme - thank you for the reminder...


[stable/prometheus-operator] Unable to set grafana.ini in prometheus operator chart.

Describe the bug
Setting grafana.ini section in the custom values.yml file doesn't work.The configurations are no populated to the grafana container.
Version of Helm and Kubernetes:
Helm v2.14.2
GKE
Which chart:
stable/prometheus-operator latest
What happened:
The grafana.ini configuration is not populated to the pod.
What you expected to happen:
The grafana.ini configurations to be applied.
How to reproduce it (as minimally and precisely as possible):
helm install stable/prometheus-operator -f values
Anything else we need to know:
Here is the values.yml file :
values-grafana.txt

My mistake , I was looking the wrong ini file inside the container.


on darwin, rely on -lglfw, not -lglfw3

unbreaks the make process for me on darwin (high sierra 10.13.3).
homebrew seems to treat 'glfw3' as an alias for 'glfw', so installing either of
those package names from homebrew should be ok for the glfw prerequisite.  but
the shared library ends up being called libglfw.3.dylib, so use -lglfw, not
-lglfw3.

Confirmed on my (High Sierra) machine. Thanks, Ben!!!!!!
I'm not 100% where the name changed, but perhaps here:
https://github.com/Homebrew/homebrew-core/pull/7484/files#diff-66f7eb93812d3a0d36b7f672bb987ebdR72


IQoption withdrawal question

I have question for those who have tried to withdraw from this platform. Have you faced with issues from platform side, account ban or other issues while withdraw? I mean when you using this api. (sorry for my english)

@djumpen
I made $25 using the automatic trading system I'm creating, and as a result of that IQoptions has 'Suspended' all my trades
Not sure what they mean by that and if I will ever get access to trades again... I hope it is not a result of my code or that IQoptions can somehow pick up that we are using a computer not their GUI
Their exact message is 'active is suspended' whenever I try and make a purchase

@MightyMaxSaviorOfTheUniverse So, have you successfully withdraw your funds eventually?


sentiment analysis

sentiment analysis NLP query. This should definitely be implemented. Could even be a pre-existing algorithm.

Would like to work on this.


engineHolder.get().invokeFunction("renderServer", comments)  too slow

every execute this method elapsed about 1 minutes.

Maybe linked to https://bugs.openjdk.java.net/browse/JDK-8134403 ...

Didn't noticed such slow perf at the time coding this example. What Java Version do you use?

1.8.0_40-b25

Perf bug mentioned by @sdeleuze is fixed for 8u66. You could test with an older Java version like 8u31.

@winterbe  thanks

I was interested to see what the performance was like. I also wanted to try out the CompiledScript. Here is a commit that tries a hundred runs as-is then a hundred runs as CompiledScript. Plotting output out of mvn test shows on my macbook pro an average runtime of 12.3ms for the original approach and 10.7 for the CompiledScript approach.


Correctly detect and report request errors

The current check for request errors is incorrect and won't report the actual error message (such as missing SSL dependencies, DNS errors, etc). A request error will be found in the request object, rather than the response object, so it needs to be checked before _as_response which only receives the response object. The request object doesn't have a ->message method, the error message will be found in the structure returned by ->error in this case.
There's also probably no use in proceeding to _as_response as the response will always be empty when this happens, but I didn't change anything around that.

Thanks! I'll get this shipped now and investigate bailing out completely if it meets this error.


Remove placeholder text

Description
For a11y reasons, this removes placeholder text from input fields, and where reasonable, adds some of these details to the labels for those fields.  This does not currently mess with the date placeholder text.  See https://github.com/civiform/civiform/issues/3078 for some discussion.
Release notes
The title of the pull request will be used as the default release notes description. If more detail is needed to communicate to partners the scope of the PR's changes, use this release notes section.
Checklist
General

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)
[x] Extended the README / documentation, if necessary

User visible changes

[ ] Wrote browser tests using the validateAccessibility method
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/application.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Issue(s) this completes
Fixes https://github.com/civiform/civiform/issues/2617

Codecov Report

Merging #4099 (dc9888d) into main (fc4253f) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #4099      +/-   ##
============================================
+ Coverage     79.44%   79.46%   +0.02%
- Complexity     2500     2505       +5
============================================
  Files           306      308       +2
  Lines         10098    10112      +14
  Branches        676      676
============================================
+ Hits           8022     8036      +14
  Misses         1813     1813
  Partials        263      263

Impacted Files
Coverage Δ

server/app/services/MessageKey.java
100.00% <ø> (ø)

...erver/app/services/program/predicate/Operator.java
100.00% <0.00%> (ø)

...ontrollers/admin/AdminProgramBlocksController.java
59.55% <0.00%> (ø)

...rs/applicant/ApplicantProgramReviewController.java
100.00% <0.00%> (ø)

...applicant/ReadOnlyApplicantProgramServiceImpl.java
97.88% <0.00%> (ø)

...icant/exception/ApplicationOutOfDateException.java
100.00% <0.00%> (ø)

server/app/modules/ProgramCreationModule.java
100.00% <0.00%> (ø)

server/app/services/program/ProgramDefinition.java
89.23% <0.00%> (+0.14%)
:arrow_up:

...erver/app/services/applicant/ApplicantService.java
89.47% <0.00%> (+0.22%)
:arrow_up:

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

@mferhut These aren't super nice to look at due to the diff in the middle, so sorry about that.  But this should be all the proposed changes.  Original on the left, new on the right.

This is the most interesting one, given that the text moved to a new label outside of the input text box.

Hi @nb1701
Looks great! There's a couple minor tweaks:

Update copy to "Email the applicant about the status change": (https://user-images.githubusercontent.com/122842472/215865316-45bd476f-06ec-4ef8-bcb8-5916842c8d15.png)

Update 'search questions' font color to grey to distinguish it from headers in the panel. (https://user-images.githubusercontent.com/122842472/215865288-731d30be-321d-4e18-b41a-39b5fface5dc.png)

Thanks!

@mferhut Should the 'search question' grey be the same color as the placeholder text was?

Updated text for the other issue


feat: Add multitenant integration test

Hello folks.
This PR is to add the integrations tests for step 2-multitenant.
It also includes the /testutils folder with transforms.go file. This is made to not bind with foundation test.

/gcbrun

Hi @Samir-Cit - Could you rebase?  Probably needs a go mod tidy.

Thanks @gtsorbo - I'll get this merged today


Label showed behind the polygon with extrude setting.

Hi, are there some ways to hide the label behind polygon with extrude? Now all the labels are shown whether the label is front of or behind the polygons, this sometime makes confuse.

Hi @ilully0802 ,
This feature could be achieved by using the inlay blend mode https://mapzen.com/documentation/tangram/styles/#blend. Unfortunately, only the javascript version of Tangram does support this feature for now, you can follow this issue here https://github.com/tangrams/tangram-es/issues/595.

Hi karimnaaji , thanks your cue, #402  has mentioned some resources with branch 'inlay-stencil', but this branch can not be found in github now, how can I follow this branch? Thanks!

This branch was deleted but I restored it, you can find it here https://github.com/tangrams/tangram-es/tree/inlay-stencil.

Thanks karimnaaji.

Closing in favor of https://github.com/tangrams/tangram-es/issues/595


Support for CSharp Script

Hi guys. I'm having some issues trying to format my C# scripts.
C# can be used for scripting. There are tools like dotnet-script to run those files. C# scripts use the .csx extension but csharper doesn't support it. Is there a way to force csharper to format those files?
Input:
dotnet-csharpier ./main.csx
Output:
Warning ./main.csx - Is an unsupported file type.
Expected behavior:
The file formatted.

There isn't currently a way to tell CSharpier which files to format and with which formatter, but I do have a branch where I have csproj/xml formatting mostly done and will need to figure it out.
For now though it will be easy to change the hardcoded ".cs" checks in the cli to ".cs/.csx".
Changing the extensions should also happen, but is probably less important.

Hi, thanks @belav but now there is another problem, can this issue be open again or should I open a new issue?
If I try to run Csharpier in my file, the following error appears:
❯  dotnet csharpier ./main.csx
Warning ./main.csx - Failed to compile so was not formatted.
  (1,1): error CS1024: Preprocessor directive expected
  (3,2): error CS8097: #load is only allowed in scripts
Formatted 1 files in 266ms.

As I can see, CSharpier cannot process files with the #!/usr/bin/env dotnet-script and the #load directive.
This is an example file:
#!/usr/bin/env dotnet-script
#load "other.csx"

WriteLine("Hello World");

If I remove those lines, CSharpier works as expected.
There are no errors with those lines. #!/usr/bin/env dotnet-script is required so I can run the script directly and the #load directive is used to load additional scripts.

That's my bad, I assumed csx were just regular c# code and only tested that way. From my googling it looks like Roslyn can still parse it into a syntax tree, so it should be straightforward for me to get working, it just won't be the two line change that I hoped.


Adding URLs Manually is broken

text isn't correct, and it doesn't provide the Add button

I've fixed this in the features-sources branch

related to #1280


Feat/issue 57 migrate videojs vast vpaid

What is the page you want to be in the github page? The docs or the static demo page?
Because currently, the docs is the one being used by the github page see https://github.com/MailOnline/mol-video-ad-sdk/blob/next-release/.travis.yml#L18 for more details

For now the docz. The static page is just to ensure everything works. We need to build a proper demo asap


Quite a few typos or information not relavent to Ros2

I just wanted to point out a few mistakes in the foxy documention.
This command:
ros2 run open_manipulator_x_teleop open_manipulator_x_teleop_keyboard
should be:
ros2 run open_manipulator_x_teleop teleop_keyboard
This page: https://emanual.robotis.com/docs/en/platform/openmanipulator_x/quick_start_guide/#install-ubuntu-on-pc
Shows usage of ros vs ros2 in section <IP_ADDRESS>
Selction 4.1.3 refers to a robotis_ws folder but the install script in 4.1.2 creates a colon_ws as the build folder
Its working well so far though.
Thank you.

Thank you for raising an issue regarding the typo and some misleading content, I will have our engineers check it and make a change on your request.

Please allow me to transfer to the proper repos. This issue belongs to another branch, OpenManipulator-X.

Hi @sardanian.
This content will be corrected and reflected in the e-manual soon.
Thank you for your contribution!
@ROBOTIS-David
Please update the e-manual after checking the revisions.

Thank you for checking this out.
The given PR is confirmed and has been merged to the Master branch of e-Manual . Please close the ticket if solved.

This issue appears to be resolved, so it will be closed.


Add note in the doc for using naive engine in multithreading environment

Description
Add note for using naive engine in multithreading environment per the request of @bhavinthaker.

I think it's enough to simply say:
ThreadedEngine will deadlock after a fork because it is multithreaded. If you want to use fork, please run mxnet with NaiveEngine.

"ThreadedEngine will deadlock after a fork because it is multithreaded" is NOT technically correct, IMHO, because the actual behavior is unpredictable and may or may not result in deadlock, depending on the use of locks.

Since this is a documentation change, does it need to pass the CI tests?

Right now this is required from technical perspective (i.e. github prevents it from merging because the branch is protected with the required-checks option).
@reminisce do you mind doing a rebase? I see that the PRs based on the latest master is passing, so there's a good chance that a rebase would resolve the CI error.

@piiswrong told me that he is working on the fix. Seems like there is no need to add this PR. @piiswrong could you confirm?


unload vs deleteIndex

Hi,
what is the difference between unload vs deleteIndex ?
In which case should I use which of the options ?'
Thanks,

unload calls the unload() function on C++ Annoy instance. deleteIndex use the delete keyword in C++ to remove the C++ Annoy instance from memory. I've provided unload() since the C++ library has it, but I haven't use it before. Maybe you can figure out more clue from the spotify/annoy project or the source code.


We then run the codecov script. It correctly figures out that we've tested a merge commit. But then it performs some magic to try and determine the SHA of the merge commit. This magic fails.
git show --no-patch --format="%P" returns 808aa3ab5e3b389207a73c4aed07e07c481958b9 5438dfd8f70f3a525eaab95f5dc5caab599d0129 and codecov incorrectly assumes that the second commit must be the commit ID under test. It sends the coverage information to the server with commit ID 5438dfd, which is actually the SHA of the master HEAD.
This in turn causes codecov to decide that the report must belong to the last merged pull request, which messes up the PR coverage administration.

I expect there is no easy way for codecov to figure out which is the correct parent commit and I'd prefer if it does less magic rather than incorrect magic.

CircleCI is affected by this as well: #134. At least CircleCI has the correct SHA already as an environment variable set. Maybe jenkins provides a similar helper?

We have exactly the same Jenkins configuration, and this problem keeps happening and it's killing our productivity. It fails most of the times in our builds.
I'm going to show a real example of my latest build, with my log of commits, in case this helps finding a solution.
We have base branch develop, which latest commit is the merge of feature/ticket1. From there we started two branches in parallel: ticket2 and ticket3. Ticket2 is merged successfully and then we open the Pull Request for Ticket3. This git log is produced from jenkins after the virtual merge:
*   9a3dc566c Merge commit '28f62c89d87b4c369859ecdd7cd27743a696a1d3' into HEAD
|\
| *   28f62c89d Merge pull request #1003 from feature/ticket2 into develop
| |\
| | * 38cd1c5f2 [ticket2] More code
| | * a2f673a33 [ticket2] Amazing feature
| | * 7331c658e [ticket2] Whatever
| |/
* | 45c64e76d [ticket3] Set the branch explicitly in Codecov
* | f3db1e116 [ticket3] Log more info in the codecov stage to understand why it fails sometimes
|/
*   180fc7c7e Merge pull request #997 from feature/ticket1 into develop
|\

The magic to determine the head lines 830 to 850 correctly detects the merge, but the output of mc=$(git show --no-patch --format="%P") is 45c64e76d 28f62c89d.
Then, it always picks the second, which in this case is develop HEAD. This is the problem. It's not always the second.  Today I've been trying merging locally into different branches, and even changing the time of my latest commit in the branch to be newer and older than the develop head, and I always get the first as the right one. I think sometimes the second would be the second would be the right one, but I don't know on what this depends.
We've added some logs in our CI before running the codecov script to try to understand when is the first or the second, because now I have no clue.

The merge commit SHA code has been removed except for GitHub Actions


Inconsistent Project Name Error During Installation via pip

Description:
Issue Summary:
When attempting to install the weatherapipython package from the GitHub repository https://github.com/weatherapicom/python.git using pip, an inconsistency in project naming leads to installation failure.
Steps to Reproduce:
Run the installation command: sudo pip3 install git+https://github.com/weatherapicom/python.git#egg=weatherapipython.
Encounter an error related to project name inconsistency.
Expected Behavior:
The package should be installed successfully without any name mismatch issues.
Actual Behavior:
The installation process fails with the following error message:
Discarding git+https://github.com/weatherapicom/python.git#egg=weatherapipython: Requested swagger-client from git+https://github.com/weatherapicom/python.git#egg=weatherapipython has inconsistent name: expected 'weatherapipython', but metadata has 'swagger-client'
ERROR: Could not find a version that satisfies the requirement weatherapipython (unavailable) (from versions: none)
ERROR: No matching distribution found for weatherapipython (unavailable)
This suggests a mismatch between the specified project name in the pip command (weatherapipython) and the actual project name in the package metadata (swagger-client).
Additional Context:
This issue occurred while attempting to install directly from the GitHub repository.
Swagger-client seems to be the correct project name to use for installation, since it's used in the setup.py file to describe the project.
Concrete action
Correct the readme to use the correct project name in the pip installation guide.

I have the same error as above.

I have the same issue mentioned above


Metric for file cache size may become negative

What type of bug is this?
Incorrect result, User Experience
What subsystems are affected?
Standalone mode, Distributed Cluster
Minimal reproduce step
Run the cluster with the experimental write cache enabled
What did you expect to see?
The metric value should be greater than 0.
What did you see instead?
The value of cached bytes is negative:

What operating system did you use?
Linux
What version of GreptimeDB did you use?
0.9
Relevant log output and stack trace
No response

Maybe caused by overflow


Upgrade ginkgo to v2.11.0

Ⅰ. Describe what this PR does
Fix #1964
Upgrade the ginkgo version to v2.11.0 to facilitate E2E reporting.

Ⅱ. Does this pull request fix one issue?
Yes, #1964

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

PTAL @saintube

PTAL /cc @jasonliu747


bump: version 1.0.0 → 1.1.0

RATIONALE
Bumping version
CHANGES

update changelog
update versions

CHECKLIST

[ ] Tests covering the new functionality have been added
[ ] Documentation has been updated OR the change is too minor to be documented

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (440c0dd) 93.54% compared to head (64f8fab) 93.54%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #171   +/-   ##
=======================================
  Coverage   93.54%   93.54%
=======================================
  Files          17       17
  Lines        1364     1364
  Branches      275      275
=======================================
  Hits         1276     1276
  Misses         54       54
  Partials       34       34

Files Changed
Coverage Δ

src/flake8_custom_import_rules/__init__.py
66.66% <100.00%> (ø)

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


Form submit action url is incorrectly derived in lxmldriver.py

If no action is set then the url is modified to append a slash which may not be a valid url. For example, the form on the following page /question/95 would have an action set to /question/95/ if no action is set. In my case I have resolved this issue by adding an action to my form.
If the maintainer could confirm that they would like a PR to fix this, then I will happily oblige.

@olorton We're always happy to get PRs for bug fixes. Thanks!

Fixed by #900


Anvil only shows Shaped Ore Recipes in JEI

...ordinary shaped recipes seem to be ignored, like the recipes for Siding, Moulding and Corners.

Fixed


Fixed columns creation and legend issue, now allows conditional coloring out-of-the-box

Hi n3-charts team,
I cleaned the columns code a little, in order to use the fill-attr (color option) directly on the rect node. This immediately allows conditional coloring by simply using a coloring function instead of a string as color value and fixes #217.
var colorFn = function(d, i){
  return d && d.y > 10 ? 'red' : 'green';
};

$scope.options = {
  series: [
     {y: 'value', color: colorFn, type: 'column'}
  ]
};

Here is a demo: http://plnkr.co/edit/0vDTzF6mUfDr1Tbnjzvk
This PR also fixes #202 some annoying bug where the legend labels are overlapping.
Best,
Christoph

Great code, however the tooltip should read the color function too. Instead it will default to no color for scrubber, and steelblue for axis mode. Could you fix that please ? Otherwise it looks good.

I have seen that scrubber tooltips are black when we use a coloring function - I will fix this. But do you mean the tooltips should also change colors?

Yeah, that'd be cool :-) Or we would have to specify a default color for the series if it has a color function, because otherwise the tooltip would either stay black or pick a random color...

the nice thing was, that with the restructuring of the columns code, conditional coloring could be achieved without effort - because you can plugin the function instead of the color value. If we want the same behavior for tooltips, I need to mimik this behavior - and call the coloring function manually, if there is one

i just took a look at the code; I need to call it anyway manually, so I can also apply the conditional colors :)

The demo link is still the same http://plnkr.co/edit/0vDTzF6mUfDr1Tbnjzvk actually, it's a really nifty feature with the tooltips also changing the color :)

Alright, almost there :-)

Hi Sébastien,
here is the rebased and corrected fix. I also added parenthesis to all equal and match calls in the unit tests.
Best,
Christoph

:poultry_leg:

Legend bug doesn't seem to be fixed, for graphs that are initially hidden:
http://plnkr.co/edit/PRSO0W9UUBGAjbHMpDpH?p=preview

@rfcee thanks for reporting this bug.

When I comment out the line:
setTimeout(translateLegends, 0);
...the legends do not overlap anymore. But when I do a window resize, then the legends overlap again.
So I tried to comment out as well everything inside the window_resize function and just put:
scope.redraw;
Well that works, no legends overlapping, but the graphs don't resize :(
I hope someone can help me find a workaround for this...please.


Web: Horizontal scroll blocking vertical scrolling on trackpad/touchpad

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Possibly a regression of this?: https://github.com/flutter/flutter/issues/70046.

Create an outer vertical ListView that has horizontal ListViews as children.
Place two fingers on a trackpad/touchpad (im using a macbook touchpad here)
Try to drag vertically, but with a slight angle instead of perfectly straight.

Expected results
The vertical listview keeps scrolling vertically. Since the fingers are dragging with a slight angle, the horizontal listview should probably also scroll a little bit at the same time.
Actual results
The vertical listview stops scrolling when the cursor is over a horizontal listview, and the horizontal scrolling takes over.
It feels like they are competing.
Code sample
Code sample

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: ListView.builder(
          itemBuilder: (context, index) => Container(
            color: Colors.white,
            height: 210,
            child: Padding(
              padding: const EdgeInsets.symmetric(vertical: 30),
              child: ListView.builder(
                scrollDirection: Axis.horizontal,
                itemBuilder: (context, index) => Box(),
              ),
            ),
          ),
        ),
      ),
    );
  }
}

class Box extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
        height: 150,
        width: 150,
        color: Colors.black,
        padding: EdgeInsets.all(10),
        child: Container(
          color: Colors.grey,
        ));
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://user-images.githubusercontent.com/727125/233004032-87b9752b-79aa-4019-b404-1d0e055edc73.mov

Logs
Logs
Launching lib/main.dart on Chrome in debug mode...
main.dart:1
This app is linked to the debug service: ws://<IP_ADDRESS>:59965/oeAyusjUjYc=/ws
Debug service listening on ws://<IP_ADDRESS>:59965/oeAyusjUjYc=/ws
💪 Running with sound null safety 💪
Connecting to VM Service at ws://<IP_ADDRESS>:59965/oeAyusjUjYc=/ws

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.7.10, on macOS 12.6.1 21G217 darwin-arm64, locale en-NO)
    • Flutter version 3.7.10 on channel stable at /Users/andreasgangso/dev/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4b12645012 (2 weeks ago), 2023-04-03 17:46:48 -0700
    • Engine revision ec975089ac
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/andreasgangso/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.12.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.6.1 21G217 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 112.0.5615.121

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @andreasgan, I believe this shares a root cause as https://github.com/flutter/flutter/issues/113416.
Can you look at the issue linked above to see if it's related to your issue?

It feels like they are competing.

I believe they are. See https://docs.flutter.dev/development/ui/advanced/gestures#gesture-disambiguation

It might be the same root cause. I also don't know if it makes sense to treat touchscreen drags and touchpad dragging the same way.

To add some use case context here, this creates a very annoying user experience for media webapps with a lot of horizontal sections like ours: https://beta.app.bcc.media/.

I think the fix might have been applied for only macOS. I see different behaviours when I scroll on mac compared to web.
On macOS, when I scroll at an angle, it doesn't get very far, but it still registers as a vertical scroll. However, on the web, when I scroll, at an angle, a vertical scroll is initially registered but when it gets into the horizontal list, the scroll is captured by the horizontal list. See the recordings below.

macOS
web

@andreasgan, just to confirm, this matches what you're experiencing, correct?

@danagbemava-nc Yes, true. I created this codepen which has a similar setup in pure html and js to check the normal behaviour, and the mac build is behaving correctly.
I hadn't noticed before, but flicking like you are doing in the video makes the bug very obvious. In my video i am doing a long manual drag.

Thanks for the confirmation.
The issue is reproducible using the code sample provided above.
Steps to reproduce

Run the code sample on the web
Place the mouse cursor above the boxes(in the white spaces)
Fling vertically at an angle
Observe that when the mouse pointer gets into the boxes, the scroll is captured by the horizontal listview, and the listview scrolls.

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.12, on macOS 13.3.1 22E261 darwin-arm64, locale en-GB)
    • Flutter version 3.7.12 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (2 days ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode-14.3.0.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9619390/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at /Users/nexus/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 73.0.4
    • Dart plugin version 231.8109.91

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.8109.175/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (4 available)
    • M2007J20CG (mobile) • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • Nexus (mobile)      • 00008020-001875E83A38002E                  • ios            • iOS 16.4.1 20E252
    • macOS (desktop)     • macos                                      • darwin-arm64   • macOS 13.3.1 22E261 darwin-arm64
    • Chrome (web)        • chrome                                     • web-javascript • Google Chrome 112.0.5615.137

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.10.0-10.0.pre.17, on macOS 13.3.1 22E261 darwin-arm64, locale en-GB)
    • Flutter version 3.10.0-10.0.pre.17 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b04efe4ecf (8 hours ago), 2023-04-20 01:31:24 -0400
    • Engine revision 2db85cbe6a
    • Dart version 3.1.0 (build 3.1.0-22.0.dev)
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode-14.3.0.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9619390/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at /Users/nexus/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 73.0.4
    • Dart plugin version 231.8109.91

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.8109.175/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (4 available)
    • M2007J20CG (mobile) • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • Nexus (mobile)      • 00008020-001875E83A38002E                  • ios            • iOS 16.4.1 20E252
    • macOS (desktop)     • macos                                      • darwin-arm64   • macOS 13.3.1 22E261 darwin-arm64
    • Chrome (web)        • chrome                                     • web-javascript • Google Chrome 112.0.5615.137

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

This is expected behavior. When nesting gestures, they cannot both win the gesture arena at the same time, so only one (vertical or horizontal) will claim the drag. We currently have a 2D scroll view in progress, I have added this to that project for tracking.
I am going to close this since it is expected and we have other issues covering the 2D diagonal scrolling feature.

@Piinks I'm worried my wording in the original issue has confused you to believe this issue is about diagonal scrolling.
I've removed (strikethrough) this from the OP now because it was a wrong expectation: "Since the fingers are dragging with a slight angle, the horizontal listview should probably also scroll a little bit at the same time."
The real issue here is that it's not locking the axis like it does on macos and like a normal html-based website.
See Daniels reply above.

Hey @andreasgan thanks for checking! I believe all of this will be resolved by the 2D scrolling project, including locking axes appropriately.


Wrong pod name is visualised in the workflow

Summary
What happened/what you expected to happen?
I started a workflow in my local k8s cluster with the latest version of argo-server and I observed that the name of the pod mentioned in the workflow step is wrong it is not actually the name of the pod which is started which includes the name of the step in the middle.
I expected that executing argo get  will show me the correct pod name.
Output from argo get <name of workflow> -n argo

Output from kubectl get pods -n argo | grep <name of workflow>

What version are you running?
Latest.
I have installed argo using this set of commands before 3 days:
kubectl create ns argo
kubectl apply -n argo -f https://raw.githubusercontent.com/argoproj/argo-workflows/master/manifests/quick-start-minimal.yaml

Message from the maintainers:
Impacted by this regression? Give it a 👍. We prioritise the issues with the most 👍.

@JPZ13 This seems related to pod name change. Would you like to take a look?

@terrytangyuan Yep! I'll take a look this afternoon Eastern Time. Thanks for the heads up

@IoanaIvanova Could you post the workflow that you ran or a reproducible example? I ran a fresh quick start install from the command you provided and submitted a couple workflows from the examples folder. Outputs are looking good on my end:
STEP                  TEMPLATE  PODNAME                            DURATION  MESSAGE
 ✔ dag-diamond-4cxgz  diamond
 ├─✔ A                echo      dag-diamond-4cxgz-echo-3871903043  12s
 ├─✔ B                echo      dag-diamond-4cxgz-echo-3888680662  16s
 ├─✔ C                echo      dag-diamond-4cxgz-echo-3905458281  16s
 └─✔ D                echo      dag-diamond-4cxgz-echo-3922235900  5s

Might be an edge or corner case I haven't seen yet. Thanks for reporting the issue!

@IoanaIvanova Can you check your Argo Cli version?

It is reproducible on my side with your simple workflow example with steps defined here.
 I'm on a later CLI version:
argo: v3.3.5+eefc60b.dirty
  BuildDate: 2022-05-04T05:14:44Z
  GitCommit: eefc60b155c4011a3706d2e3cba90f099ee93b39
  GitTreeState: dirty
  GitTag: v3.3.5
  GoVersion: go1.18.1
  Compiler: gc
  Platform: darwin/arm64

I ran the example you gave and got the following output:
Name:                steps-ddwfk
Namespace:           argo
ServiceAccount:      unset (will run with the default ServiceAccount)
Status:              Succeeded
Conditions:
 PodRunning          False
 Completed           True
Created:             Wed Aug 03 18:28:57 -0400 (18 seconds ago)
Started:             Wed Aug 03 18:28:57 -0400 (18 seconds ago)
Finished:            Wed Aug 03 18:29:15 -0400 (now)
Duration:            18 seconds
Progress:            3/3
ResourcesDuration:   19s*(1 cpu),10s*(100Mi memory)

STEP            TEMPLATE           PODNAME                          DURATION  MESSAGE
 ✔ steps-ddwfk  hello-hello-hello
 ├───✔ hello1   whalesay           steps-ddwfk-whalesay-1020413787  6s
 └─┬─✔ hello2a  whalesay           steps-ddwfk-whalesay-3775412509  8s
   └─✔ hello2b  whalesay           steps-ddwfk-whalesay-3725079652  6s

These pod names match what I'm seeing in K8s:
NAME                              READY   STATUS      RESTARTS   AGE
httpbin-6f9dc6d779-4jn2c          1/1     Running     0          6m25s
minio-76fd8cb46d-wd66h            1/1     Running     0          6m25s
steps-ddwfk-whalesay-1920012444   0/2     Completed   0          4m36s
steps-ddwfk-whalesay-1970345301   0/2     Completed   0          4m36s
steps-ddwfk-whalesay-3941472404   0/2     Completed   0          4m44s

Let me know if you're still running into this issue after upgrading the CLI

Thanks it is working with version
argo: v3.3.8+621b0d1.dirty
  BuildDate: 2022-06-24T01:56:09Z
  GitCommit: 621b0d1a8e09634666ebe403ee7b8fc29db1dc4e
  GitTreeState: dirty
  GitTag: v3.3.8
  GoVersion: go1.18.3
  Compiler: gc
  Platform: darwin/amd64

Could you tell me also from which version or argo-server/argo go client is the pod name change introduced as we have some functionality which is related to the failed pod name and as I can see when the workflow fails there is no direct information in the workflow kind for the name of the failed pod which was the behaviour in the older version of argo server?


Add option --dump-sourceref to generate a file containing sourceKeys

This helps translators to find the context of a message to better understand the meaning of a message.
It generates (at the end of "extract") a file containing (mainly) sourceKeys in a meaningfull sorting order like:
[
  {
    "key": "Device init",
    "line": 384,
    "plural": false,
    "fileName": "../fc/fc.c"
  },
  {
    "key": "Device ready",
    "line": 388,
    "plural": false,
    "fileName": "../fc/fc.c"
  },
  ...

I know about optional "context" in big systems. But is this really worth add for embedded? Usually simple text search in IDE shows all locations at once.

Ok. If not urgent - let's keep it open for a while. I will think about possible solutions for this feature.

Fine. I will rebase the PR to master, so that it does not use lodash anymore and is easily mergable. Stay tuned.

https://github.com/lvgl/lv_i18n/commit/af62c7e2c95cbb332feb2121e41780cae05fb718 - polished some names.
After first refactoring pass, i found we can unify things even better - switch to concept of compiler/runtime lookup index.
Current "slow search" data:
static lv_i18n_phrase_t en_gb_singulars[] = {
    {"s_en_only", "english only"},
    {"s_translated", "s translated"},
    {NULL, NULL} // End mark
};

#define _(text) lv_i18n_get_singular_by_map(text)

will become:
// For slow search only
static const char * en_gb_singulars_idx[] = {
    "s_en_only",
    "s_translated"
    NULL // End mark
}

// The same as optimized
static const char * en_gb_singulars[] = {
  "english only", // 1=s_en_only
  "s translated", // 2=s_translated
  NULL, // 3="s_untranslated"
};

// The same thing, but with runtime index search
#define _(text) lv_i18n_get_singular_by_idx(text, get_singular_idx(text))

That will unify almost everything:

Fast version will use macro index
Slow version will contain extra index table + index search function.

And no more difference!
What to you think?

Rebase done, merge with no problems, no objections or alternative solutions by puzrin.
Is there any question open or please merge.

Thanks for merging!

Thanks for the activity here :slightly_smiling_face:


feat: sdk7 Tween component implementation

What's this?
The implementation of the SDK7 component Tween
What's for?
To handle tweens, silly!
All kinds of tweens should work, including sequences, loops and tweens triggered by player actions.
How to test?
Go to any scene that has tweens, and make 'em tween, for example:
https://sdk-test-scenes.decentraland.zone/?position=77%2C-5&realm=LocalPreview
https://github.com/decentraland/sdk7-goerli-plaza/tree/main/moving-platforms

https://github.com/decentraland/unity-explorer/assets/1031741/37b9cdfe-d233-4148-8119-b332f4a5ddd6


[DEVOPS-879] Introduce '--no-client-auth' flag

Description
--no-client-auth to disable client certificate verification by the wallet backend.
This will re-enable the behavior in place before client certificate verification was introduced. By default, it is turned on (to be discussed).

/!\ TODO /!\ ops remaining work in the installers to make use of this flag.

Linked issue
[DEVOPS-879]
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[x] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[x] I have read the style guide document, and my code follows the code style of this project.
[x] If my code deals with exceptions, it follows the guidelines.
[x] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

Tested with Daedalus. This works perfectly. Thanks @KtorZ


UserInteracted event doesn't fire on iOS

When I subscribe to this event, it only fires on Android. It is never fired on iOS.

Are you sure? There are no other properties set for iOS?

Show me the sample, please

Hi,
I'll out together a simple sample when I have a bit more time, but this is what I'm doing:
Works fine on Android, but never fires on an iOS device or simulator
public partial class ProductImageCarouselView : ContentView
    {
        public ProductImageCarouselView()
        {
            InitializeComponent();

            Carousel.UserInteracted += Carousel_UserInteracted;
        }

        private void Carousel_UserInteracted(PanCardView.CardsView view, PanCardView.EventArgs.UserInteractedEventArgs args)
        {
            if (args.Status == PanCardView.Enums.UserInteractionStatus.Ended && args.Diff > -10 && args.Diff < 10)
            {
                if (BindingContext is ViewProductPageViewModel viewModel)
                {
                    if (Carousel.SelectedItem is ProductImage image)
                    {
                        viewModel.ImageTappedCommand.Execute(image);
                    }
                }
            }
        }
    }

let me check it

Can you post xaml as well?

Just verified, works as expected.
Post sample please, i presume there is any bug in your xaml

http://www.giphy.com/gifs/fVJaPapy5Ppp80Q56y

@AndreiMisiukevich
I think to replicate the issue we need to add the WebView inside the CarouselView.
Then it should stop the firing the UserInteracted event on the iOS.

@AndreiMisiukevich
I think to replicate the issue we need to add the WebView inside the CarouselView.
Then it should stop the firing the UserInteracted event on the iOS.

Yes, there is a conflict of gestures. You should choose where PanGesture is working and where it isn't

I have set IsPanInteractionEnabled="False" on the CarouselView. But still it didn't detect the UserInteracted event on the iOS.

You should set IsEnabled = false to your WebView

Or InputTransparent = true


[WFLY-9553] Add the statistics resource at runtime

The statistics resource is added at runtime only if statistics-enabled
attribute is resolved to true.
JIRA: https://issues.jboss.org/browse/WFLY-9553

@bstansberry this supersedes your branch and I check it is working as expected:
/subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=statistics-enabled, value=true)
reload
/subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-children-names(child-type=statistics)
/subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra/statistics=pool:read-resource(include-runtime)

Note that there was an issue with your commit where the resource was creating by calling context.readResource(PathAddress.EMPTY_ADDRESS) instead of using the resource from the performRuntime() parameter directly.
I suppose that the call to the context.readResource(PathAddress.EMPTY_ADDRESS) was creating a 2nd snapshot instead of the actual one that we get from performRuntime().
I mention that in case, you have spotted other issues similar to https://issues.jboss.org/browse/WFCORE-2930

retest this please