Wallet - State is not auto filled after selecting the address during "Get physical card" flow

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.10-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Log in to account that has Expensify Card<EMAIL_ADDRESS>).
Go to Account settings > Wallet
Click on the second Expensify card (for<EMAIL_ADDRESS>)
Click Get physical card
Enter phone number
Proceed to "Enter your shipping address" step
Enter address and select address from the suggestion list

Expected Result:
State will be auto filled after selecting the address
Actual Result:
State is not auto filled after selecting the address
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/0ff535d7-f665-498a-bd7c-5fddf39d2a58
View all open jobs on GitHub

We think that this bug might be related to #wave-collect - Release 1

@zanyrenney  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

adding an external label, the bug is reproducible.

hey @DylanDylann please review the proposal above.

Proposal
Please re-state the problem that we are trying to solve in this issue.
State is not auto filled after selecting the address
What is the root cause of that problem?
In GetPhysicalCardAddress, we only get the address info from the draft value and we don't control the address state as we do in AddressPage.
https://github.com/Expensify/App/blob/5e6527613d0f234fcb22507b878697a2bec356c5/src/pages/settings/Wallet/Card/GetPhysicalCardAddress.tsx#L42
https://github.com/Expensify/App/blob/5e6527613d0f234fcb22507b878697a2bec356c5/src/pages/AddressPage.tsx#L95-L97
So the state is not auto-filled since the defaultVaule is used here and onAddressChanged prop is not passed in GetPhysicalCardAddress
https://github.com/Expensify/App/blob/5e6527613d0f234fcb22507b878697a2bec356c5/src/components/AddressForm.tsx#L195
What changes do you think we should make in order to solve the problem?
We should use the same way as we do in AddressPage to control the address state and fix some other bugs that we are handling in AddressPage  like the state is not cleared after we change the country, ...
https://github.com/Expensify/App/blob/5e6527613d0f234fcb22507b878697a2bec356c5/src/pages/AddressPage.tsx#L95-L97
What alternative solutions did you explore? (Optional)

@nkdengineer's proposal looks good to me. We implemented the solution for this bug before in AddressPage
🎀 👀 🎀 C+ reviewed

Not overdue.

@DylanDylann this PR is ready for review

2 days remaining before payout!

checked neither are paid via ND.

payment summary
paid @DylanDylann $250 via upwork
paid @nkdengineer $250 via upwork.


Added a note for helpers alias

There is an undocumented feature - helpers() method.
I simply added a note to expose this feature.

Some people make typos and that's the only thing this method is useful for.
I don't want it used or documented, it's just an old time relic that wouldn't be added to the framework today.

Some people make typos and that's the only thing this method is useful for.

I don't want it used or documented, it's just an old time relic that wouldn't be added to the framework today.
— @narfbg

I think anything not documented should not exist. Imagine if there was an undocumented $CI->load->controller() method - of what use is it?
If a developer mistakenly uses $CI->load->helpers() it should return a FATAL error!
This is my standpoint and should be adopted as it prevents CodeIgniter from being an over-bloated framework.


bug(node): TypeError: lancedb.Index.fts is not a function

LanceDB version
0.9.0
What happened?
I am trying to implement full-text search using JavaScript, but I encountered an error when testing the official sample code.
Are there known steps to reproduce?
`import * as lancedb from "@lancedb/lancedb";
const uri = "data/sample-lancedb"
const db = await lancedb.connect(uri);
const data = [
{ vector: [3.1, 4.1], text: "Frodo was a happy puppy" },
{ vector: [5.9, 26.5], text: "There are several kittens playing" },
];
const tbl = await db.createTable("my_table", data, { mode: "overwrite" });
await tbl.createIndex("text", {
config: lancedb.Index.fts(),
});
await tbl
.search("puppy")
.select(["text"])
.limit(10)
.toArray();`

I upgraded to version 0.10.0-beta.0, but it reported a new bug.
Error: No embedding functions are defined in the table

Hi @gy9527 , I think something breaks this,
#1576 would fix this, but you can still do FTS by this for now:
await tbl
  .search("puppy", "fts")
  .select(["text"])
  .limit(10)
  .toArray();`

[2024-10-31T16:13:37Z TRACE lance_encoding::encodings::logical::primitive] Final flush of column 0 which has 680 bytes
[2024-10-31T16:13:37Z TRACE lance_encoding::encodings::logical::primitive] Final flush of column 1 which has 376 bytes
table NativeTable(messages, uri=/Users/a/Downloads/hardhat/lancedb/messages.lance, read_consistency_interval=None)
Error: No embedding functions are defined in the table
    at /Users/a/Downloads/hardhat/node_modules/@lancedb/lancedb/dist/table.js:186:39
    at async /Users/a/Downloads/hardhat/node_modules/@lancedb/lancedb/dist/query.js:451:31
    at async VectorQuery.toArrow (/Users/a/Downloads/hardhat/node_modules/@lancedb/lancedb/dist/query.js:215:21)
    at async VectorQuery.toArray (/Users/a/Downloads/hardhat/node_modules/@lancedb/lancedb/dist/query.js:228:21)
    at async aiDb (/Users/a/Downloads/hardhat/scripts/tmp.ts:61:19)
    at async main (/Users/a/Downloads/hardhat/scripts/tmp.ts:7:3)
    ```

    ```

  // 创建表
  const table = await db.createTable(
    "messages",
    [
      { text: "消息内容1", createdAt: new Date() },
      { text: "消息内容2", createdAt: new Date() },
      { text: "测试", createdAt: new Date() },
    ],
    {
      mode: "overwrite",
    }
  );
  console.debug(`table`, table);

  // 搜索消息
  const results = await table.search("测试").toArray();
  console.debug(`results`, results);

when search

await tbl
.search("puppy", "fts")
.select(["text"])
.limit(10)
.toArray();`

passing the queryType to fix it:
await tbl
  .search("puppy", "fts")
  .select(["text"])
  .limit(10)
  .toArray();`

btw i don't think we support Chinese for now, that may result in unexpected search results

await tbl

.search("puppy", "fts")

.select(["text"])

.limit(10)

.toArray();`

passing the queryType to fix it:

await tbl

  .search("puppy", "fts")

  .select(["text"])

  .limit(10)

  .toArray();`

btw i don't think we support Chinese for now, that may result in unexpected search results

The same goes for English.

await tbl

.search("puppy", "fts")

.select(["text"])

.limit(10)

.toArray();`

passing the queryType to fix it:

await tbl

  .search("puppy", "fts")

  .select(["text"])

  .limit(10)

  .toArray();`

btw i don't think we support Chinese for now, that may result in unexpected search results

The same goes for English.

Does it still report error with passing query_type?


Cannot get genesis block from ckb node

By completing the issue: https://github.com/nervosnetwork/grants/issues/1 I encountered a certain obstacle, when starting the indexer with a synchronized node node receives such an error.
Node: ckb 0.100.0-rc2 (35b2111 2021-07-16)
Indexer: ckb-indexer 0.2.1
[2021-07-28T08:50:04.107Z ERROR ckb_indexer::service] cannot get genesis block from ckb node, error: Failed to parse server response as Option < BlockView >: missing field `uncles_hash`

ckb-indexer 0.2.1 is not compatible with ckb pre-release version, please use ckb 0.43.1 (15427e0 2021-07-16)


Feature/clarify capabilities

Clarify capabilities json object, as it was a bit unclear what the different entries where supposed to be showing.
Also fixed issue with toggling pause, as it used a wrong parameter in ChromeState (which showed if pause where possible)

@Stanback Could you give this one a spin at your end? And see if it breaks things
(Sorry, for using you as a review peer / Guineapig :) )

@tbowmo Sure thing :smile: will test it when I get home from work today

@tbowmo Just tested - it's working well for me 👍

ok, then I'll let it go in then.. should be the last bigger restructuring pr..


embed code fragments from external sources

I would like to import fenced code from GitHub repo files similar to https://docsify.js.org/#/embed-files?id=embedded-code-fragments
Is this on the roadmap?

Yeah but probably using a different syntax, like:
<!-- embed foo.js as code block -->
#include(/foo.js)

A fragment:
#include(/foo.md fragment)

Where foo.md looks like:
# title

<!-- docute-embed-start -->

something to embed

<!-- docute-embed-start -->

Sounds great! A couple more things :stuck_out_tongue: is it possible to add support for:

these files to be externally loaded?
adding arbitrary fencing?

For instance:
<!-- embed example.js as code block -->
#embed(
  https://raw.githubusercontent.com/someuser/somerepo/code/example.js
  type=code
  language="js"
  fence="some-demo"
)

<!-- .../example.js -->
...
/// [some-demo-start]
...
/// [some-demo-end]
...

<!-- result -->
// some content from example.js within the /// [some-demo]

and then
<!-- import content from other .md file -->
#embed(
  https://raw.githubusercontent.com/someuser/somerepo/example.md
  type=fragment
  fence="some-fragment"
)

<!-- .../exmaple.md -->
...
<!-- some-fragment-start -->
something to embed
<!-- some-fragment-end -->
...

Being able to define the fence allows multiple partials from a single file being imported.
Externally loading code decouples the need for it to live alongside the documentation, say in an examples repo.

The api.processMarkdown(fn) API now can return a Promise:

You can probably implement it as a plugin using this API:
const embedPlugin = () => {
  return {
    name: 'embed',
    extend(api) {
      api.processMarkdown(async markdown => {
        return modifiedMarkdown
      })
    }
  }
}

new Docute({
  plugins: [embedPlugin()]
})

Sweet, I'll give this a go soon! Cheers!

@issuehunt has funded $100.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

Can i take this?

@janat08 Feel free. I got caught up with life!


Support Jenkins Pipeline (Jenkinsfile) plugin for Jenkins collector

Adds support for Jenkins pipeline plugin. https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
Includes support for addons to the plugin such as the multi-branch pipeline. Child jobs show up as "parent/child". Note that a job will not show up without a build.
SVN was not tested but should work as there were no provider specific changes made.

We look forward to this pull request getting integrated, particularly because it provides support for folders (Cloudbees).

Hi @Mpluya did you see my comment above? If not can you take a look?

@tabladrum yes I have seen your comment, thank you. Correct me if I'm wrong, but I believe we're saying the same thing - that this enhancement addresses the current limitation of the jenkins collector on handling folders. My intent for the previous comment is just to indicate that we need this pull request.

LGTM

@tabladrum @amitmawkin review/LGTM needed.

@tabladrum Tried a 3 level nested pipeline and freestyle job and it worked.

@tabladrum One issue. The recursive get is not handling redirect urls where auth is needed. Will fix after merging this.
2017-01-10 16:22:07,963 ERROR c.c.d.collector.DefaultHudsonClient - client exception loading jobs
org.springframework.web.client.HttpClientErrorException: 403 Forbidden
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:91) ~[spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:614) ~[spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:570) ~[spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:545) ~[spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:466) ~[spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at com.capitalone.dashboard.collector.DefaultHudsonClient.makeRestCall(DefaultHudsonClient.java:586) [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
at com.capitalone.dashboard.collector.DefaultHudsonClient.recursiveGetJobDetails(DefaultHudsonClient.java:240) [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
at com.capitalone.dashboard.collector.DefaultHudsonClient.getInstanceJobs(DefaultHudsonClient.java:134) [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
at com.capitalone.dashboard.collector.HudsonCollectorTask.collect(HudsonCollectorTask.java:91) [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
at com.capitalone.dashboard.collector.HudsonCollectorTask.collect(HudsonCollectorTask.java:32) [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
at com.capitalone.dashboard.collector.CollectorTask.run(CollectorTask.java:63) [core-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_66]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]


Generate factors for 3-D decomposition

Given a number of processors np the system should try to determine a valid factorisation of the communicator grid.


Problem with translate

I have a webshop www.valhallaofnorway.no I have 2 luanguagges installed. Suddenly if i click on english the products dont show up and it goes back to norwegian menu. Anybody help.

for anyone to help, you have to provide more details, for example by filling in the template provided when creating a new issue


Remove sync, ES and related things

Codecov Report

Merging #167 into feature/dhe-827-service-deliveries-repository will increase coverage by 1.81%.
The diff coverage is 95.83%.

@@                                Coverage Diff                                @@
##           feature/dhe-827-service-deliveries-repository     #167      +/-   ##
=================================================================================
+ Coverage                                          93.93%   95.74%   +1.81%
=================================================================================
  Files                                                 46       35      -11
  Lines                                               1534     1176     -358
  Branches                                             104       71      -33
=================================================================================
- Hits                                                1441     1126     -315
+ Misses                                                80       41      -39
+ Partials                                              13        9       -4

Impacted Files
Coverage Δ

datahub/core/mixins.py
100% <ø> (ø)
:arrow_up:

datahub/core/serializers.py
100% <ø> (ø)
:arrow_up:

datahub/v2/repos/utils.py
100% <ø> (ø)
:arrow_up:

datahub/v2/parsers.py
100% <ø> (ø)
:arrow_up:

datahub/core/utils.py
80.76% <100%> (-0.81%)
:arrow_down:

datahub/search/views.py
100% <100%> (ø)
:arrow_up:

datahub/ping/services.py
54.54% <100%> (-32.96%)
:arrow_down:

datahub/core/viewsets.py
86.36% <90%> (+7.19%)
:arrow_up:

datahub/ping/views.py
40% <0%> (-60%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Ensure rebases only move local branches

As discussed in a 8:30pm SGT call with @saphal1998.
Rebases should only move local branches and ignore remote-only branches

Isn't this already in place? Refer #42

That's true 👍


Consider adding pg_partman extension

As Couldnative PG supports declarative Tablespace (since 1.22), it would be extremely useful to get pg_partman available in the PostgreSQL image.
To quote Cloudnative PG documentation:

In the context of the database industry, tablespaces play a strategic role, particularly when paired with table partitioning, a logical database modeling technique.

While it is perfectly possible to use table partitioning without pg_partman,  it is widely used to managed table partitions.
pg_partman is readily available in the Debian repository, so it can easily be included in the built images.

Note that adding pg_partman would be a one-liner change, so you can easily fork the repo and create your own image with pg_partman included (I've done this with pg_hint_plan which is also readily available in the PGDG Debian repo)
Probably need some thought about how CNPG is going to handle this particular repo, since there could be a lot of potential extension requests. It might make sense to keep this repo smaller but for us to spend some time on instructions to build custom extensions. OTOH if extensions don't add many bytes, then adding them here benefits a lot of people. A few extensions have already been added here (like pgvector & pgaudit), and it might make sense to add a few more widely used ones which are already in the debian repos (eg. pg_hint_plan, pg_cron, pg_repack, pg_squeeze, pg_partman, pldebugger, plprofiler, FDWs, wal2json, maybe pg_stat_kcache)

In the meantime, if you want to just create your own images, here are the steps which worked for me:

fork github repo - keep same name "postgres-containers"

copy only the main branch from upstream
after forking, rename your default branch to something other than main - for example you can call it testing-pg-hint-plan.

i think the build scripts use the branch name to determine some behaviors, like where to publish containers in your github account and whether to allow rebuilds if artifacts already exist. if the branch is named main then containers are not rebuilt without a version number change, and they are published to the package named postgresql. with other branch names, containers are published to the package named postgresql-testing. i myself am using testing branches at the moment in my personal github repo.

create a fine-grained personal access token	1. name "postgres-containers-gha-pat"
2. only select the "postgres-containers" repo
3. allow "read and write" access to Administration and Contents
4. allow "read-only" access to Metadata and Secrets
5. save the token!
auth github cli with gh auth
create secret with gh secret set REPO_GHA_PAT and paste the personal access token that was created above
enable github actions for the forked repo
manually run the workflow named Continuous Delivery - it should succeed

confirm that packages have been published in github container registry via your own repo with docker images for the latest minor releases of all supported Postgres major versions

pull a docker image from github container registry - eg. docker pull ghcr.io/ardentperf/postgresql:latest

test a local build

clone my github forked repo down to my local machine: git clone https://github.com/ardentperf/postgres-containers
cd postgres-containers/Debian/16/bookworm
docker build -t pgtest1
docker run -de POSTGRES_PASSWORD=jeremy pgtest1

install pip-tools (we will need the pip-compile utility)

pip install pip-tools

add a simple extension from the PGDG apt repo

cd postgres-containers/Debian
nvim Dockerfile.template
add the final line (pg-hint-plan) below:

apt-get install -y --no-install-recommends \
                "postgresql-${PG_MAJOR}-pgaudit" \
                "postgresql-${PG_MAJOR}-pgvector" \
                "postgresql-${PG_MAJOR}-pg-failover-slots" \
                "postgresql-${PG_MAJOR}-pg-hint-plan" \
        ; \

run ./update.sh
run git diff and confirm that Dockerfile has been updated in each subdirectory for all supported Postgres major versions, and for both supported Debian distros (stable - currently bookworm, oldstable - currently bullseye)
choose a version to test: cd 16/bookworm
build with the updated Dockerfile and run the image to test locally

docker build -t pgtest2
docker run -e POSTGRES_PASSWORD=jeremy pgtest2

add -d if you want to run detached

use psql to connect to the database
select * from pg_available_extensions
create extension pg_hint_plan
After confirming that your local test succeeded, push only the Dockerfile.template change back to your github fork and let CI build and publish your images in the github container registry.

git add postgres-containers/Debian/Dockerfile.template
git commit -m "adding my extension"
git push
in the github UI, go to Actions and manually trigger the workflow named Automatic Updates - this will run update.sh

i disabled this scheduled action after i finished creating my images; i don't need it running daily when i'm not actively working on the images anymore

in the github UI, go to Actions and manually trigger the workflow named Continuous Delivery - this will run a build and publish the new containers to the github container registry

Test running the container from the registry

docker pull ghcr.io/ardentperf/postgresql-testing:17
docker run -e POSTGRES_PASSWORD=jeremy ghcr.io/ardentperf/postgresql-testing:17

if you need to modify any postgres parameters, add -c parameter to the end of the run command. for example: docker run -e POSTGRES_PASSWORD=jeremy ghcr.io/ardentperf/postgresql-testing:17 -c shared_preload_libraries='pg_stat_statements,pg_hint_plan'

this was cobbled together from some notes and might have mistakes... but hopefully it helps. :)

Thank you very much for these very detailed instructions :-)


need a better way to detect our kernels

https://github.com/twosigma/beakerx/blob/master/beakerx/js/src/extension.js#L71
here we need different behavior for our kernels.
this isn't the right way.

Also added messages in JS console :


code about illumination estimator

In the illumination estimator, the paper mentions that 1×1 convolution is followed by 9×9 convolution, but the convolution kernel of the next convolution after 1×1 convolution is set to 5×5 in the code. May I ask what the correct convolution kernel is set to

5×5 is correct.
9×9 is a typo, I forgot to revise that, sorry.


TDecay Parameter Fixing and Limits

This is a reminder to myself that this still needs to be done at some point. The limits and fixing work if fitting a TSingleDecay or TDecayChain, but not a full TDecay.

This is done, but I'm trying to figure out a way to make it better.


Gateway: concepts/gateway.md

This article is waiting to be claimed. concepts/gateway.md

/accept

/delay-reset

/delay-reset

目录调整，该章节合并，详情见 #251


V0.8.1 breaks tests that use atomWithSuspenseQuery and MSW 1.3.2

Hey guys after bumping to use v0.8.1 some of our tests don't seem to work while using atomWithSupenseQuery from jotai (2.6.0) and server from msw (1.3.2) to mock our api calls. This is a test we have:
  it('when has no data show fallback message', async () => {
    server.use(rest.get(`http://api/events`, (req, res, ctx) => res(ctx.json([]))));

    renderWithProviders(<Component />);

    expect(await screen.findByText("title")).toBeInTheDocument();
    expect(await screen.findByText("description")).toBeInTheDocument();
  });

As of bumping from 0.8.0 to 0.8.1 this test no longer works as the server.use override no longer gets called and the test renders the component with old data from the other previous tests

I don't think I can troubleshoot from this snippet. Would you be able to create a minimal repro?

@kalijonn apologies, have spent some more time on this and it was an issue with our cache setup.


I want to have a function like dispatchgroup, What can I do in moya.

I want to wait a group requests all done in moya.

You wouldn't implement this in Moya instead whatever object uses your network abstraction layer would be responsible for waiting for all request to be fired.


Automated Deployment to APPUiO Cloud

Summary
As product owner
I want to have automated deployment to APPUiO Cloud
So that I can have fast feedback on the development.
Context
Enhance the GitHub Actions to deploy to APPUiO Cloud:

Preview deployments for PRs
Deployment to production on tagging

Out of Scope
No response
Further links
No response
Acceptance Criteria

When pushing a Git release tag, the app should be deployed to production
Given existing deployment, when pushing a commit to master, then production deployments shall be updated while keeping currently deployed version.
Given an existing branch, when PR is created, then build a new image, deploy a preview instance with generated URL and post a notification in the comments
Given an existing PR, when PR is closed, then purge the PR-specific preview instance and delete the image.

Implementation Ideas
No response

Deployment to production on tagging

I've made the experience that only doing deployments on git tags may not cover all cases. For example, there could be a simple DNS change or just upscale in replica, for which a new tag would have to be made.
I propose to run deployments on any commit in master. If there wasn't a change that impacts the deployment, then nothing happens anyway. WDYT?

Yes, that's a good approach :+1:

Revisiting this topic again.
Do we really want to deploy to production via pipeline in this repository? Every other APPUiO cloud component is managed via Project Syn. I could imagine that we may want to prefer to maintain production instance with GitOps / Commodore component, while having a Review-App-workflow with pipelines for preview deployments.
If this sounds reasonable, I would propose the following implementation:

Create a helm chart in appuio/charts repository. (In fact, I started already on it, couldn't help myself: https://github.com/appuio/charts/pull/380)
Create a Helmfile deployment in this repository that deploys the Chart for previews
Commodore component (maybe https://github.com/appuio/component-control-api/?) reuses also the Helm chart for generating deployment manifests.

I think using the stack described above provide a good-enough compromise of GitOps and Review-Apps.

I'm OK with the proposed process, it's good enough for now.
Although I'm not a big fan of it, I prefer to have everything of an application at the same place: application code, deployment artifacts, pipelines. With the proposed workflow everything is scattered around: code is here, helm chart is in separate chart repo, deployment is in commodore component and the actual deployment is in the tenant repo: 4 places to look for things.

You raise good points and I understand them very well. I just thought deploying production here would be inconsistent to how we manage Zones with Syn usually, with the exception of the portal.
The other way could confusing as well: engineers asking themselves where the deployment is coming from, how to scale up or change an image tag, configure oauth... Instead of adjusting values in the usual Commodore places, they'd have to come to this repository just for the portal. Besides, there may be a point soon where we need to configure secrets, and having to encrypt them here with SOPS is a much bigger operational "break" or antipattern than what Syn/Vault provides.
Let's have a team discussion to decide. Moving the chart to this repository is easy should we decide for full review-app workflow.

We discussed it in the team today and came to the following conclusion:

Frontend previews are set up and teared down using Pull Requests as initially proposed
Production deployment is managed via Commodore / Syn using Git tagged releases as that's the preferred method for the engineers operating the cluster.
There will be a long-running integration environment that is deployed via GH actions by pushing to master. That way we have a stable pre-production environment to test things out in-depth before releasing it.

A question came up how we decide to deploy the backend part of the control-api. Is the frontend being paired with a Preview deployment of the backend? Or do we develop backend features first and frontend always uses the integration environment of the backend...?
We don't have answers yet, but they will be needed later.


Bug - Make sure HealthKit is asking permission from user

Hi Brittany, I can look into this.

Great! Thanks!


fix: Unique schema names for nested models (#3134)

Description

After confirming its a nested model and not past the max_nested_depth, append the nested model's name to the unique_name for a name different from the parent.

I'm unsure if this is the best place or way to handle this. It will change the schema title for all nested models.
Before this patch, the MCVE of #3134 would give the following response schemas.

app.get_logsLogfileResponseBody
GetLogsLogfileResponseBody
GetUsersUserResponseBody
GetUsersUser_0ResponseBody

After this patch, it would give the follow.

GetLogsLogfileResponseBody
GetLogsLogfileUserResponseBody
GetUsersUserResponseBody
GetUsersUser_0LogfileResponseBody

Closes
Closes #3134

Thanks. Feel free to continue your contributions, they are much appreciated 😄

@litestar-org/members would this be considered breaking against any potential downstream openapi generators depending on what "was" there? I'm up in the air here... If not we can merge.

I'm thinking if we should generate a separate schema here in the first place. If we were to have a ref instead of an in-line schema, this issue wouldn't even exist. I think we've talked about this before but I'm not sure what we determined the best course of action would be. @guacs, @peterschutt?

I'm thinking if we should generate a separate schema here in the first place. If we were to have a ref instead of an in-line schema, this issue wouldn't even exist. I think we've talked about this before but I'm not sure what we determined the best course of action would be. @guacs, @peterschutt?

I think inlining would be better as well. I think the final decision was to inline everything as much as possible except for DTOs, but I think we should just go ahead and inline DTOs as well.

the DTO creates a new msgspec Struct for the repeated models

Yes it does.

If so, would it be feasible to ensure that we only create a DTO once per model?

It would have to be conditional on the DTO config. For a given model, the transfer model for the DTO backend will be the same if the DTO configs are the same. However, if the configs are different (except for the code-gen option), i.e., different inclusions/exclusions, then the transfer models will be different.

If it's not feasible, then I think this PR is good to go.

Yes, I'm OK with this. Given the current behavior, it is surely a bug that we are trying to name a nested transfer model the same as its parent transfer model.
However, I don't think the current behavior of producing a transfer model for every domain model we encounter is right, and we should look to improve it.
As @provinzkraut mentioned, for this case it would be ideal to use a ref to the User schema for LogFile.user, and in general I agree that we should aim to use the least amount of component schemas as necessary to represent the data. However, if the dto config for LogFile modifies the nested user representation at all then we'd need to produce a different transfer model/schema in that case, and we are right back here.
We could create some sort of backend cache where the dto backend for a model is cached against the (DomainModelType, dto_config_instance) tuple, b/c the same type with the same config would produce identical backend instances/transfer models. I think we'd have to modify how we handle nested models in the backend for this though.
Currently, we allow configuring nested models via dotted syntax on the dto configs and we handle that within the same DTO backend. E.g.,:
class LogfileDTO(DataclassDTO[Logfile]):
    config = DTOConfig(exclude=["user.name"])

For this, within the same DTO backend that handles LogFile, we recursively create a transfer model for User that has no name field after filtering out any nested configuration from the dto config. What we might be able to do is when we encounter a nested model, instead create a whole new DTOConfig object for it from the parent config object (which would be `DTOConfig(exclude={"name"}) in this case) and use a whole new backend instance to create the nested model. Then we could cache that backend using the (User, dto_config) pair as cache key, and any time we encounter a User object with the same config, reuse the transfer model that has already been produced. We'd still have to do some gymnastics to swap out the nested schema to a component reference when the dto backend produces its schema, but this should give us a path to doing that because the backend would be able to keep a reference of any time it has used a nested model from within the cache.

@litestar-org/members would this be considered breaking against any potential downstream openapi generators depending on what "was" there? I'm up in the air here... If not we can merge.

Good point - we've been bitten by changing these names before: https://github.com/litestar-org/litestar/issues/2804
@ssenior45 apologies for the random ping. Any chance you'd be able to comment on this as a known user of code gen tools, would this PRs changes be an issue for you.
@chris-telemetry - also, sorry for random ping. Are you using code gen also? (I ask b/c you were tagged in the issue I've linked above).

@litestar-org/members would this be considered breaking against any potential downstream openapi generators depending on what "was" there? I'm up in the air here... If not we can merge.

Good point - we've been bitten by changing these names before: #2804
@ssenior45 apologies for the random ping. Any chance you'd be able to comment on this as a known user of code gen tools, would this PR's changes be an issue for you.
@chris-telemetry - also, sorry for random ping. Are you using code gen also? (I ask b/c you were tagged in the issue I've linked above).

I think @cofin's team had also faced an issue with the changes in the naming.

@litestar-org/members would this be considered breaking against any potential downstream openapi generators depending on what "was" there? I'm up in the air here... If not we can merge.

Good point - we've been bitten by changing these names before: #2804
@ssenior45 apologies for the random ping. Any chance you'd be able to comment on this as a known user of code gen tools, would this PR's changes be an issue for you.
@chris-telemetry - also, sorry for random ping. Are you using code gen also? (I ask b/c you were tagged in the issue I've linked above).

We are not using it, thanks for pinging me though! I don't think this change will cause issue for us. But this stuff is always weirdly tricky!

@litestar-org/members would this be considered breaking against any potential downstream openapi generators depending on what "was" there? I'm up in the air here... If not we can merge.

Good point - we've been bitten by changing these names before: #2804
@ssenior45 apologies for the random ping. Any chance you'd be able to comment on this as a known user of code gen tools, would this PR's changes be an issue for you.
@chris-telemetry - also, sorry for random ping. Are you using code gen also? (I ask b/c you were tagged in the issue I've linked above).

I think @cofin's team had also faced an issue with the changes in the naming.

It's been a while since I looked at this, but we do/did have a workaround that we can use, so I think we are good. Thanks for checking.

@litestar-org/members would this be considered breaking against any potential downstream openapi generators depending on what "was" there? I'm up in the air here... If not we can merge.

Good point - we've been bitten by changing these names before: #2804
@ssenior45 apologies for the random ping. Any chance you'd be able to comment on this as a known user of code gen tools, would this PR's changes be an issue for you.
@chris-telemetry - also, sorry for random ping. Are you using code gen also? (I ask b/c you were tagged in the issue I've linked above).

I think @cofin's team had also faced an issue with the changes in the naming.

It's been a while since I looked at this, but we do/did have a workaround that we can use, so I think we are good. Thanks for checking.

NP - thanks for responding!

Is there an update on this topic?I would be really happy if the PR is finally merged.

@peterschutt Seems like this is good to merge, right?
And we'll come back later and fix up things as discussed above.

@peterschutt Seems like this is good to merge, right?
And we'll come back later and fix up things as discussed above.

Last time we changed the schema names there was blowback from users of codegen tools which was a bit of an undertaking to repair. From people that have been asked for feedback as known users in this thread, one is not using code gen, one says maybe but they have tooling to work around it, and @cofin  was mentioned but has not given input. So I just don't know. Also the PR is already approved by 2 maintainers and I'm not actively blocking it - I'm also not certain enough to merge it myself.

@peterschutt Seems like this is good to merge, right?
And we'll come back later and fix up things as discussed above.

Last time we changed the schema names there was blowback from users of codegen tools which was a bit of an undertaking to repair. From people that have been asked for feedback as known users in this thread, one is not using code gen, one says maybe but they have tooling to work around it, and @cofin was mentioned but has not given input. So I just don't know. Also the PR is already approved by 2 maintainers and I'm not actively blocking it - I'm also not certain enough to merge it myself.

Sorry for the delay.  @ssenior45 and I have been working on the same project.  We do have a workaround so changes here won't impact us.  I think we are good to merge this if we are all ok with the changes.

Thanks @cofin.

Also the PR is already approved by ~2~ 3 maintainers and I'm not actively blocking it

Also the PR is already approved by 2 maintainers and I'm not actively blocking it - I'm also not certain enough to merge it myself.

Yeah, I also wasn't sure with all the stuff going on, so I just wanted to check in with you again before merging :)
But it seems like @cofin was faster :P


Remove list /i and /e feature

Changes made:

Removed ListCommandParser
Removed unused fields in ListCommand and ColumnManipulatorCommandParser which were previously used by ListCommandParser
Updated unit tests for RC4HDB parser class

Note: Any input entered after the list command will now be ignored.
To be completed:

Update documentation in UG for removed feature

Codecov Report

Merging #270 (a4add16) into master (9e758c0) will increase coverage by 4.54%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #270      +/-   ##
============================================
+ Coverage     64.06%   68.60%   +4.54%
- Complexity      839      885      +46
============================================
  Files           139      138       -1
  Lines          2905     2886      -19
  Branches        294      291       -3
============================================
+ Hits           1861     1980     +119
+ Misses          938      798     -140
- Partials        106      108       +2

Impacted Files
Coverage Δ

...b/logic/commands/residentcommands/ListCommand.java
100.00% <ø> (ø)

...commandparsers/ColumnManipulatorCommandParser.java
89.18% <ø> (-3.27%)
:arrow_down:

...n/java/seedu/rc4hdb/logic/parser/Rc4hdbParser.java
91.66% <100.00%> (ø)

...gic/parser/commandparsers/UnbookCommandParser.java
91.30% <0.00%> (-8.70%)
:arrow_down:

...4hdb/storage/residentbook/JsonAdaptedResident.java
100.00% <0.00%> (+1.63%)
:arrow_up:

.../main/java/seedu/rc4hdb/commons/util/FileUtil.java
81.48% <0.00%> (+3.70%)
:arrow_up:

...logic/commands/residentcommands/FilterCommand.java
89.28% <0.00%> (+4.28%)
:arrow_up:

...ava/seedu/rc4hdb/model/venues/booking/Booking.java
42.85% <0.00%> (+14.28%)
:arrow_up:

...ava/seedu/rc4hdb/model/venues/UniqueVenueList.java
33.33% <0.00%> (+16.66%)
:arrow_up:

src/main/java/seedu/rc4hdb/model/VenueBook.java
62.06% <0.00%> (+20.68%)
:arrow_up:

... and 7 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

The UG has been updated accordingly. For the DG, only one of the user stories related to this feature needs to be modified. I will make the change along with my other changes to the DG for v1.4.


Task: Add "Council on Environmental Quality" in footer below "Contact", above address

Describe the task
Now that the footer design is a little different to work more within USWDS constraints, "Council on Environmental Quality" no longer appears above the "730 Jackson Pl NW" line. Would be good to add a "Council on Environmental Quality" line of text above "730 Jackson Pl NW". Note, keep the logo and "Council on Environmental Quality" at the very bottom of the footer as is.
Subtasks

[ ] @janelien confirm, update design, "With USWDS Tokens" section designs currently have "730 Jackson Pl NW" directly under "Contact"
[ ] Dev add "Council on Environmental Quality" text to footer below "Contact" and above address to footer

Additional context

This is ready for QA:
https://d2zjid6n5ja2pt.cloudfront.net/justice40-tool/c48959/en/

Works for me!


Set metadata to Py3 only + Remove Universal Wheel

I see not inclusion of deps + support in code for Python 2
Lets remove making a universal wheel then + flag in setup.py that this code is Python 3 only

If there is ment to be Python 2 support I apologize.

Definitely not meant for py2.
In addition to this, I propose to add python_requires='~=3.3' in setup.py, motivation is the same.
ping @HonzaKral


New argument to set exportability of the certificate

Adding a new argument to specify the location of the scripts. README updated with this info. Spec tests added. Tests use a different certificate thumbprint.The test certificate is spec/testCert.pfx
This is a combined pull it contains two features:
#45 (new argument to specify a directory to store the scripts) and #46 itself (flag to set the exportability of the certificate key).

Hi, can someone review these changes? @dalen , @apenney , @oranenj , @jfryman , @carlossg

@oranenj please review the code after the changes you requested.
Thanks in advance

This seems fine to me on a general level. Someone else will have to merge though, as I can't say I'm very familiar with the domain specifically.

Do you know who can merge and when can it be merged?

Would have preferred two separate PRs, but merging anyway


Feature/add tools

It is great that we can add this code in the tools module 💯

Yes, it's been long overdue
On Wed, 21 Feb 2018 at 13:54 Melisa Bok<EMAIL_ADDRESS>wrote:

It is great that we can add this code in the tools module 💯
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/iesl/openreview-py/pull/82#issuecomment-367431691,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFRliaek2kW1MZIXF0jtuk80lMKaoHHPks5tXGZngaJpZM4SOJED
.


BUG: Correctly treat large integers in MMIO (fixes #6397)

Integers up to native 'int' bit size are now written and read correctly.
Out of range integers now throw an OverflowError rather than too
silently overflow. This fixes #6397.

LGTM, merged. Thanks @jotasi

Great and thanks for your help @rgommers.

You're welcome. Keep them coming:)
despite the label on the original bug report, this wasn't quite an easy-fix in the end:)


New-SSHSession "A connection attempt failed ..."

Hello,
I've been experienced some issues with using the command New-SSHSession to connect to hosts in the other side of the world. Pings to the host are 160-180ms which confirms longer connection time.
Using the following command gives the following error;
New-SSHSession -ComputerName ### -Port 22 -AcceptKey:$true
New-SSHSession : Connection failed to establish within 10000 milliseconds.
At line:1 char:1
+ New-SSHSession -ComputerName ### -Port 22 -AcceptKey:$true
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationTimeout: (Renci.SshNet.SshClient:SshClient) [New-SSHSession], SshOperationTimeoutException
    + FullyQualifiedErrorId : SSH.NewSshSession

Using following command gives the following error;
New-SSHSession -ComputerName ### -Port 22 -AcceptKey:$true -ConnectionTimeout 100 -KeepAliveInterval 100 -OperationTimeout 100
New-SSHSession : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has fa
iled to respond
At line:1 char:1
+ New-SSHSession -ComputerName ### -Port 22 -AcceptKey:$true -Connection ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Renci.SshNet.SshClient:SshClient) [New-SSHSession], SocketException
    + FullyQualifiedErrorId : SSH.NewSshSession

(Credential parameter removed for testing purposes)
Testet with PuTTY, working fine.
Any idea what is causing this?
$PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
4      0      -1     -1

I would say check the logs on the linux host and do a PCAP to see if it shoes any response not shown.
Sent from my iPhone

On Jun 25, 2019, at 3:58 AM, Oliver Karstoft<EMAIL_ADDRESS>wrote:
Hello,
I've been experienced some issues with using the command New-SSHSession to connect to hosts in the other side of the world. Pings to the host are 160-180ms which confirms longer connection time.
Using the following command gives the following error;
New-SSHSession -ComputerName <IP_ADDRESS> -Port 22 -AcceptKey:$true
New-SSHSession : Connection failed to establish within 10000 milliseconds.
At line:1 char:1

New-SSHSession -ComputerName <IP_ADDRESS> -Port 22 -AcceptKey:$true

  + CategoryInfo          : OperationTimeout: (Renci.SshNet.SshClient:SshClient) [New-SSHSession], SshOperationTimeoutException
  + FullyQualifiedErrorId : SSH.NewSshSession

Using following command gives the following error;
New-SSHSession -ComputerName ### -Port 22 -AcceptKey:$true -ConnectionTimeout 100 -KeepAliveInterval 100 -OperationTimeout 100
New-SSHSession : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has fa
iled to respond
At line:1 char:1

New-SSHSession -ComputerName ### -Port 22 -AcceptKey:$true -Connection ...

  + CategoryInfo          : InvalidOperation: (Renci.SshNet.SshClient:SshClient) [New-SSHSession], SocketException
  + FullyQualifiedErrorId : SSH.NewSshSession

(Credential parameter removed for testing purposes)
Testet with PuTTY, working fine.
Any idea what is causing this?
$PSVersionTable.PSVersion
Major  Minor  Build  Revision

4      0      -1     -1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

update: i could ssh to target server. have to use FQDN instead of IP and it works well.
thanks all for your advices.


Updating variable and async call

updating variable with missing character ( '_') and adding GetAwaiter().GetResult() to the async call in the sync method
#52486

@eddynaka : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for updating with the missing _, adding @cijothomas to confirm if he wants .GetAwaiter().GetResult() used in lieu of the existing code.

Thanks :)

#sign-off

Thanks for helping to improve the docs, this should get picked up for merge in the next few hours and go live by 3 PM today. (Redmond time)

Signing off again as the GitHub automation should have picked up the sign-off and changed the PR label to ready-to-merge

#sign-off


add ci

Looks good. just don't quite understand why db-generated isn't run before the typecheck if we defined that dep in the turbo.json

Yep. Didn't feel like diving into it more right now but can be revisited later


⚠ Bofrost.lu has degraded performance

In 76643b2, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1259 ms

Resolved: Bofrost.lu performance has improved in bf5a8f5 after 6 minutes.


add: YadlaMani

Description
I have added my info in a json format in a the file and added that json file to the contributors list
Changes Proposed
Added the following JSON object in the public/data folder:
{
"name": "Mani Yadla",
"location": "Hyderabad",
"bio": "I am currently pursuing B.Tech in CVR College of Engineering. Technology excites me and I am always in awe of the change it drives in the world. Certain skills that I have worked with include Data Structures and Algorithms (C++), Web Development (HTML, CSS) & Linux OS. And what I might lack in skills I make up for with my determination to learn. I am passionate about problem-solving and enjoy participating in competitive programming contests.",
"avatar": "https://github.com/YadlaMani.png",
"portfolio": "https://github.com/YadlaMani",
"skills": ["Full stack Web Development", "DSA", "MERN Stack"],
"social": {
"GitHub": "https://github.com/YadlaMani",
"Twitter": "https://twitter.com/mani_yadla",
"LinkedIn": "https://www.linkedin.com/in/yadla-mani"
}
}
Added my JSON filename (YadlaMani.json) to the array of filenames in the ProfileList.json file, like this:
["filename1.json", "filename2.json", "YadlaMani.json"]
Checklist

[ X] I have read and followed the Contribution Guidelines.
[X ] All new and existing tests passed.
[X ] I have updated the documentation to reflect the changes I've made.
[X ] My code follows the code style of this project.
[X ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers
Hope you will merge

@YadlaMani Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


[ the new NetworkID field] (Version 1.11.0)

https://github.com/XRPLF/rippled/releases/tag/1.11.0
hi team, In the new version, I noticed that the NetworkID field has been added. could you explain in detail how I can use it ?

I now submit transactions that are all on the mainnet，does it apply as well？

https://github.com/XRPLF/rippled/blob/develop/src/ripple/core/impl/Config.cpp#L500-L510
Network ID for mainnet is 0, testnet is 1, devnet is 2. So the new network ID field should not be included on any txns to those networks.

got it thanks~

@oeggert can we create/add some documentation about this on xrpl.org?

https://github.com/XRPLF/rippled/pull/4459
hi, I've noticed some changes to account_info，this seems to add a new account_flags field, Is this still supported for "Flags"？

@xiongjiabing - for questions unrelated to the new NetworkID field, it is preferable to open a new Issue, instead of commenting on this existing one.
The Flags field is still supported. account_flags is only there for convenience, and you can use it instead of Flags if it provides the information that you want. Details in https://github.com/XRPLF/rippled/issues/2457

copy that


puzzled in Action Batches demo

https://github.com/jruizgit/rules/blob/master/docs/py/reference.md#action-batches
`
with ruleset('expense'):
# this rule will trigger as soon as three events match the condition
@when_all(count(3), m.amount < 100)
def approve(c):
print('approved {0}'.format(c.m))
# this rule will be triggered when 'expense' is asserted batching at most two results
@when_all(cap(2),
          c.expense << m.amount >= 100,
          c.approval << m.review == True)
def reject(c):
    print('rejected {0}'.format(c.m))

post_batch('expense', [{ 'amount': 10 },
{ 'amount': 20 },
{ 'amount': 100 },
{ 'amount': 30 },
{ 'amount': 200 },
{ 'amount': 400 }])
assert_fact('expense', { 'review': True })
`
when I delete cap(2):
rejected None
rejected None
rejected None
after changing c.m to c._m,  it will be ok:
rejected {'expense': {'amount': 400}, 'approval': {'review': True}}
rejected {'expense': {'amount': 200}, 'approval': {'review': True}}
rejected {'expense': {'amount': 100}, 'approval': {'review': True}}
is this a inner mechanism? or something wrong?

I am no expert on this library, just poked around a little:
This has to do with the fact that you are passing a context (c.expense), which is a Closure obj type.
When the C engine sees this, returns a dictionary and it is stored in self._m member of that object. Alternatively, when it is an event, it happens that it is stored in a list, inside self.m member.
Why this happens exactly is faily complicated because requires diving into the C extension itself...


affected/package: go get panics on multi-module repository with circular module dependencies

Summary
The module github.com/sylr/rafty has a sub module https://github.com/sylr/rafty/tree/master/distributor/consistent. Each module requires the other. The repo currently has no semantic git version tags.
The go.mod for the consistent module has this requirement:
sylr.dev/rafty v0.0.0-20230125111348-4424dd2cf508

The go.mod for the rafty module has this requirement:
sylr.dev/rafty/distributor/consistent v0.0.0-20230125105721-bee3f99a9fe5

I verified both git hashes exist in the repo. I also verified that go build works fine in the repo.
What version of Go are you using (go version)?

go version go1.19.2 darwin/arm64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
Josephs-MacBook-Pro:binarysearch jlorenzini$ go get -v sylr.dev/rafty@latest
panic: internal error: can't find reason for requirement on<EMAIL_ADDRESS>
goroutine 1 [running]:
cmd/go/internal/modget.(*resolver).updateBuildList.func1({{0x140000b6c30?, 0x140003d02e8?}, {0x140000b6150?, 0x140001ac3b8?}})
	/usr/local/go/src/cmd/go/internal/modget/get.go:1760 +0xf8
cmd/go/internal/modget.(*resolver).updateBuildList(0x140001ce400, {0x104c12510, 0x1400019a000}, {0x0, 0x0, 0x0})
	/usr/local/go/src/cmd/go/internal/modget/get.go:1765 +0x450
cmd/go/internal/modget.(*resolver).applyUpgrades(0x140001ce400, {0x104c12510, 0x1400019a000}, {0x0?, 0x1?, 0x104bf78a0?})
	/usr/local/go/src/cmd/go/internal/modget/get.go:1312 +0xc0
cmd/go/internal/modget.runGet({0x104c12510, 0x1400019a000}, 0x140001b8438?, {0x140001b4030, 0x1, 0x1})
	/usr/local/go/src/cmd/go/internal/modget/get.go:351 +0x3c8
main.invoke(0x104f02280, {0x140001b4010, 0x3, 0x3})
	/usr/local/go/src/cmd/go/main.go:225 +0x2f8
main.main()
	/usr/local/go/src/cmd/go/main.go:179 +0x7ac

What did you expect to see?
Go get should succeed.
What did you see instead?
Go get panics

Duplicate of #56494


Adding buddybuild status badge

We've recently launched buddybuild - which is a mobile iteration platform that ties together continuous integration, continuous delivery and an iterative feedback solution into a single, seamless solution.
We really liked Tab Dump on Github and wanted to offer you a free continuous integration system to make sure that your app always works!
This badge will tell you the latest build status of your app.
For more information, please email<EMAIL_ADDRESS>

No thanks


[cli] adding suppression for firehose log messages

to @jacknagz
cc @airbnb/streamalert-maintainers
Change

Adding additional log output suppression for Successfully sent * messages to Firehose* during tests to list of suppressed messages.
Updating the filter function to use fnmatch to make it a little more adaptable.

Coverage remained the same at 94.693% when pulling da0d77dec81bbdb6c1c6d3d4e48a2dee4721793b on ryandeivert-log-suppression-addition into c011f107405dc7d1fd837a0b804de572117bb28c on master.


prometheus_local_storage_chunks_to_persist includes

chunksToPersist in function loadSeriesMapAndHeads is incremented for every chunk read from the snapshot. even if it is a still open head chunk. That overestimates the number of chunks to persist

Once this is fixed, we probably want to change the heuristics for going into "graceful degradation mode". If the number of memory chunks exceeds the configured amount and there is a reasonable (but not necessarily large) number of chunks waiting for persistence, we should also go into "speedy" mode.

How soon can we fix these related issues?
Once that's done and #1318 merged we should be mostly ready for a RC of v0.17.0.

This is pretty low hanging fruit. I'll fix it ~this week.


Add a GraphQL API to search http events

Closes: #331

Codecov Report
Patch coverage: 71.29% and project coverage change: +0.12 :tada:

Comparison is base (f930357) 67.60% compared to head (8895a3f) 67.73%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #362      +/-   ##
==========================================
+ Coverage   67.60%   67.73%   +0.12%
==========================================
  Files          19       19
  Lines        2775     2882     +107
==========================================
+ Hits         1876     1952      +76
- Misses        899      930      +31

Impacted Files
Coverage Δ

src/graphql/export.rs
16.66% <0.00%> (-0.06%)
:arrow_down:

src/graphql/log.rs
87.09% <ø> (ø)

src/graphql/packet.rs
91.89% <ø> (ø)

src/graphql/timeseries.rs
87.50% <ø> (ø)

src/ingest/implement.rs
96.40% <50.00%> (-2.34%)
:arrow_down:

src/graphql/network.rs
82.04% <59.64%> (-3.03%)
:arrow_down:

src/graphql.rs
71.49% <92.85%> (+3.04%)
:arrow_up:

src/storage.rs
68.07% <92.85%> (+1.41%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

리뷰에서 말씀주신 부분 수정 완료했습니다.


Cvs writeto file

Observations from the review:
QueryData:
Under Querry Parameters tab query should be text type in frends UI, now it is an expression. Also, the value of the query parameter in the same tab should be text.
When updating existing task, frends will forget return type. This should be fixed, or highlighted in documentation. Now enum PostgreQueryReturnType replaced, with QueryReturnType and thus frends can no update return type correctly. Maybe just adding CSV to PostgreQueryReturnType.
QueryToFile:
QueryData has the option to write the result to file, so what is point having this task? If it exists just because it has more flexible options to decide what to write in CSV file, that should be highlighted in documentation.
Documentation is missing result description.
Unit tests
Unit test are missing set up the necessary code to set up used data structures in DB, thus tests will fail.
There is no test for QueryToFile or QueryData when the result is in CSV format.


Rename renko.js to Renko.js

Fixes the readme link to https://github.com/anandanand84/technicalindicators/blob/master/test/chart_types/Renko.js
Alternative approach was to update the readme link to https://github.com/anandanand84/technicalindicators/blob/master/test/chart_types/renko.js however the naming convention seems to imply that it should be Renko.js instead of renko.js

@balupton  Did you get a chance to test it? I dont have any test case for this, as I didn't find anything online. The only way I can check is get data from trading view by hovering over the bars which is too time consuming. any thoughts?

Will see about testing it. I'll be doing much the same. I've only found about 5 implementations of renko on GitHub in various languages, and not sure if any include tests.
My plan is accumulate a fair bit of tick data, publish it as a package, and then do fixtures up for what Trading View provides for the different time spans.

I havent used renko before. Maybe I'll implement in my charting package https://traderslab.in/ and you can tell if it is correct by looking visually comparing with trading view

@balupton I have fixed few issues in renko and tried in actual chart, attached the screenshot, I am not familiar with renko, can you verify if it looks correct.

Will verify over the coming week. Thank you for your efforts on this.


False positive on anything named *-app

False positive on internal library to a non-public project - reported as cpe:/a:app_project:app:3.3.0
<dependency>
  <groupId>${project.groupId}</groupId>
  <artifactId>REDACTED-app</artifactId>
  <version>${project.version}</version>
</dependency>

This CVE has to due with the Ethereum blockchain; my application has absolutely nothing to do with this once so ever; this is a library for some shared code for various applications built in this project. This seems to affect anything matching /^\S+-app$/ based on my testing.

Thanks for the report - I will sweep through all of the FP reports before the next release.


Add support for vendoring

We're currently using go list -json -m all to get all modules a given module depends on.
However, that doesn't work with vendoring:
$ go mod vendor
...
$ go list -json -m all
go list -m: can't compute 'all' using the vendor directory

Instead, we can use go mod vendor -v to list all vendored modules. For example, for cyclonedx-go:
$ go mod vendor -v
# github.com/bradleyjkemp/cupaloy/v2 v2.6.0
## explicit
github.com/bradleyjkemp/cupaloy/v2
github.com/bradleyjkemp/cupaloy/v2/internal
# github.com/davecgh/go-spew v1.1.1
github.com/davecgh/go-spew/spew
# github.com/pmezard/go-difflib v1.0.0
github.com/pmezard/go-difflib/difflib
# github.com/stretchr/testify v1.7.0
## explicit
github.com/stretchr/testify/assert
github.com/stretchr/testify/require
# gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c
gopkg.in/yaml.v3

Lines prefixed with #  denote modules as we'd see them with go list.
Lines following ## explicit are packages inside those modules, which we don't care about for now.

Delivered with v0.4.0


WIP: Allow storing xnd in plasma

Storing xnd objects in the Plasma store will allow us to share them between multiple processes on a machine, without copying.  This pull request creates a C wrapper around plasma (libplasma), creates a xndp object in libxnd that stores a reference to a plasma object and a type, and exposes a Python API to create xnd objects stored in plasma.
TODO
libplasma

[ ] expose plasma client

[ ] create
[ ] get
[ ] create

[ ] figure out how best to compile
[ ] expose from/to binary for object IDs

libxnd:

[ ] add init function that creates plasma object
[ ] add get function that retrieves object from plasma and creates xnd object
[ ] compile xndp only when arrow is included
[ ] rename xndp to pxnd

Python

[ ] create xndp object

Closes #4

Would you like to contribute the C API wrapper to Apache Arrow? I think we'd like to grow an official C API cc @robertnishihara @pcmoritz

@wesm Yeah, I am happy to develop that in Arrow instead of here.

Seems like a good idea to me :)

I am moving this to it's own repo for now https://github.com/plures/pxnd. It's still very much in flux/an experiment, but once it's more stable I am happy to move out the libplasma part to Arrow.


python scripts/download_weights.py

When I use this command：python scripts/download_weights.py，I get the following error.
tensorflow.python.framework.errors_impl.NotFoundError: Could not find directory gs://rl-infra-public/multi_game_dt**
Pls do you have deleted the file？Or maybe it's because I don't have access to Google Cloud
Hope to get your answer.python scripts/download_weights.py

Does this work? https://github.com/etaoxing/multigame-dt/issues/2#issuecomment-1497583406


fix example / remove buildNumbers use git commit hash instead

One of the tests failed:
[error] x can build endpoint extracting param body, and header
[error]  Timeout after 1 second (retries = 0, timeout = 1 second) (SyntaxSpec.scala:95)

👊  @lvauthrin

👍


Installation error with Anaconda 2.4 (Python 3.5)

OS X El Capitan + Julia 0.4
I have just upgraded to Anaconda 2.4 with Python 3.5. Then running Pkg.add("IJulia") gives
julia> Pkg.add("IJulia")
INFO: Initializing package repository /Users/xiaoweiz/.julia/v0.4
INFO: Cloning METADATA from git://github.com/JuliaLang/METADATA.jl
INFO: Cloning cache of BinDeps from git://github.com/JuliaLang/BinDeps.jl.git
INFO: Cloning cache of Compat from git://github.com/JuliaLang/Compat.jl.git
INFO: Cloning cache of Conda from git://github.com/Luthaf/Conda.jl.git
INFO: Cloning cache of Homebrew from git://github.com/JuliaLang/Homebrew.jl.git
INFO: Cloning cache of IJulia from git://github.com/JuliaLang/IJulia.jl.git
INFO: Cloning cache of JSON from git://github.com/JuliaLang/JSON.jl.git
INFO: Cloning cache of Nettle from git://github.com/staticfloat/Nettle.jl.git
INFO: Cloning cache of SHA from git://github.com/staticfloat/SHA.jl.git
INFO: Cloning cache of URIParser from git://github.com/JuliaWeb/URIParser.jl.git
INFO: Cloning cache of ZMQ from git://github.com/JuliaLang/ZMQ.jl.git
INFO: Installing BinDeps v0.3.19
INFO: Installing Compat v0.7.7
INFO: Installing Conda v0.1.8
INFO: Installing Homebrew v0.1.17
INFO: Installing IJulia v1.1.8
INFO: Installing JSON v0.5.0
INFO: Installing Nettle v0.2.0
INFO: Installing SHA v0.1.2
INFO: Installing URIParser v0.1.1
INFO: Installing ZMQ v0.3.0
INFO: Building Homebrew
INFO: Precompiling module JSON...
INFO: Precompiling module URIParser...
INFO: Precompiling module SHA...
INFO: Cloning brew from https://github.com/Homebrew/homebrew.git
Cloning into '/Users/xiaoweiz/.julia/v0.4/Homebrew/deps/usr'...
remote: Counting objects: 3811, done.
remote: Compressing objects: 100% (3655/3655), done.
remote: Total 3811 (delta 39), reused 522 (delta 22), pack-reused 0
Receiving objects: 100% (3811/3811), 3.27 MiB | 328.00 KiB/s, done.
Resolving deltas: 100% (39/39), done.
Checking connectivity... done.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  258k  100  258k    0     0  58185      0  0:00:04  0:00:04 --:--:-- 58194
==> Tapping staticfloat/juliadeps
Tapped 38 formulae (105 files, 432K)
HEAD is now at 4705b23 fzf: update 0.10.9 bottle.
HEAD is now at b178725 Merge pull request #83 from staticfloat/staging
INFO: Building Nettle
==> Installing dependencies for nettle: gmp
==> Installing nettle dependency: gmp
==> Downloading https://homebrew.bintray.com/bottles/gmp-6.0.0a.el_capitan.bottl
Already downloaded: /Users/xiaoweiz/Library/Caches/Homebrew.jl/gmp-6.0.0a.el_capitan.bottle.tar.gz
==> Pouring gmp-6.0.0a.el_capitan.bottle.tar.gz
🍺  /Users/xiaoweiz/.julia/v0.4/Homebrew/deps/usr/Cellar/gmp/6.0.0a: 15 files, 3.2M
==> Installing nettle
==> Downloading https://homebrew.bintray.com/bottles/nettle-2.7.1.el_capitan.bot
Already downloaded: /Users/xiaoweiz/Library/Caches/Homebrew.jl/nettle-2.7.1.el_capitan.bottle.1.tar.gz
==> Pouring nettle-2.7.1.el_capitan.bottle.1.tar.gz
🍺  /Users/xiaoweiz/.julia/v0.4/Homebrew/deps/usr/Cellar/nettle/2.7.1: 66 files, 1.7M
To relink: brew unlink nettle && brew link nettle
INFO: Building ZMQ
INFO: Building IJulia
INFO: Precompiling module Conda...
INFO: Recompiling stale cache file /Users/xiaoweiz/.julia/lib/v0.4/Conda.ji for module Conda.
WARNING: Module BinDeps uuid did not match cache file
===============================[ ERROR: IJulia ]================================

LoadError: __precompile__(true) but require failed to create a precompiled cache file
while loading /Users/xiaoweiz/.julia/v0.4/IJulia/deps/build.jl, in expression starting on line 2

================================================================================

================================[ BUILD ERRORS ]================================

WARNING: IJulia had build errors.

 - packages with build errors remain installed in /Users/xiaoweiz/.julia/v0.4
 - build the package(s) and all dependencies with `Pkg.build("IJulia")`
 - build a single package by running its `deps/build.jl` script

================================================================================
INFO: Package database updated

This is JuliaLang/julia#13458.  It is fixed in Julia 0.5, and hopefully in the next 0.4 release, but for now just close Julia, re-open it, and re-run Pkg.build("IJulia").

Thanks for the quick response! It solves the problem.


Add a new tag

Could you add a new 1.0.7 tag?
That way we can use composer without setting minimum stability to "dev".
I've been using this in some of my older projects and I think it is pretty stable!
(ps I realize there is no active development, the tag is mainly for cleaner composer.json for projects depending on this).

Done.


CU-grv6v1 Handling case when target_app_did is empty and added additi…

…onal logging in case of errors

Task linked: CU-grv6v1 Scripting: check and throw error in case the target_did or target_app_did is set in the api call, but one of their values is empty ("")


Remove of keyword in oprint.

This ensures of is not displayed within editors that use Merlin.
Eg. type foo = | Foo of int now correctly becomes type foo = | Foo int.

I was just thinking about it this morning.
Thank you!


ProcessMouseEvent seems to initialize MouseEvent incorrectly

In Application.ProcessMouseEvent, for the "view != null" case, there is this snippet of code:
                                var nme = new MouseEvent () {
                                        X = rx,
                                        Y = ry,
                                        Flags = me.Flags,
                                        OfX = rx,
                                        OfY = ry,
                                        View = view
                                };

I believe that OfX and OfY need to be zero here.

You are absolutely right because there isn't any grab view.


deep profile for running slow tests

@h1alexbel It's a good thing actually! However I suggest to keep in this PR only the changes relevant to the #101 issue. We can add this deep profile in a separate PR. What do you think?

Originally posted by @volodya-lombrozo in https://github.com/volodya-lombrozo/jtcop/pull/428#discussion_r1756828236

@h1alexbel Sure. Please, go ahead!


HDFS-16693. RBF: fix NPE in Quota

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

Thanks @WeisonWei for your contribution.  Can you add a UT to reproduce it?
If DFS_ROUTER_QUOTA_ENABLE=false,  doesn't getEachQuotaUsage return IOException?
Map<RemoteLocation, QuotaUsage> getEachQuotaUsage(String path)
      throws IOException {
    rpcServer.checkOperation(OperationCategory.READ);
    if (!router.isQuotaEnabled()) {
      throw new IOException("The quota system is disabled in Router.");
    }
   ...
}

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 29s

trunk passed

+1 :green_heart:
compile
1m  1s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 58s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 51s

trunk passed

+1 :green_heart:
mvnsite
1m  2s

trunk passed

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 17s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 47s

trunk passed

+1 :green_heart:
shadedclient
23m 43s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
0m 49s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 49s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 23s

the patch passed

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 41s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 58s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 26s

the patch passed

+1 :green_heart:
shadedclient
20m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
23m  0s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 51s

The patch does not generate ASF License warnings.

123m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4633/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4633

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 61805d2ecd50 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2ba93be85994a440b40bec87519af03f604790c5

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4633/1/testReport/

Max. process+thread count
2637 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4633/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


pkg_resources api is deprecated

When using the library in python 3.8.16 one sees this warning:
venv/lib/python3.8/site-packages/pronouncing/__init__.py:3
  /Users/justinblack/programming/punnily/venv/lib/python3.8/site-packages/pronouncing/__init__.py:3: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
    from pkg_resources import resource_stream

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

How about removing the usage of this deprecated pkg_resources api?

The import also isn't used. Please see https://github.com/aparrish/pronouncingpy/pull/65 to remove it.


Draft process for q# language file sync (Do Not Merge)

Draft process for the setup and workflow to sync files from qsharp-language repo to quantum-docs-pr.  Please comment as needed.
Once the process is confirmed, I'll create the necessary folders in quantum-docs-pr and Bettina can copy the files over.

Docs Build status updates of commit 1206d23:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 1206d23:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/Q-language setup.md
:warning:Warning
View
Details

articles/Q-language setup.md

Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 7, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#file-sync-structure' in 'Q-language setup.md'.
Line 8, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#stub-topics-in-quantum-docs-pr' in 'Q-language setup.md', did you mean '#stubbed-topics-in-quantum-docs-pr'?
Line 9, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#source-content' in 'Q-language setup.md'.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1329907:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/Q-language setup.md
:warning:Warning
View
Details

articles/Q-language setup.md

Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fcad719:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/Q-language setup.md
:warning:Warning
View
Details

articles/third-party-software.md
:warning:Warning
View
Details

articles/Q-language setup.md

Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

articles/third-party-software.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'quantum'.
Line 9, Column 0: [Suggestion-sensitive-language] Term 'white-list' is sensitive and should not be used in content or code. Usage: 'ms.topic: article-type-from-white-list'

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fd091ff:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/Q-language setup.md
:warning:Warning
View
Details

articles/third-party-software.md
:white_check_mark:Succeeded
View

articles/Q-language setup.md

Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Topic/debug syms

Please see individual commits for description.

Comment regarding debug_syms being per-request. This has tremendous effect on what kind of information is cached internally for each Symbolizer instance.

Can you elaborate? What is the big difference to what we are doing?

When thinking about the same ELF file with DWARF, we'd be processing and caching different parts of DWARF depending on whether, say, inline funcs are required or not, or whether source code info is requested. That's what I referred to.
But see below for where my confusion came from.

And it's also a decision that usually is not change mid-flight. Application either intends to do more expensive debug_syms mode, or sticks to simpler ELF symbol-based symbolization.

And in such cases nothing really changes for users, right?

So what confused me was the "per-request" part as opposed to "per-data source" part. But I just double checked the API and your commit, and it seems like that's exactly what you are changing this to, right? This is a property of each source of info, whether to provide more detailed info or not. And that makes sense to me.
And just to double check my understanding. In a scenario where user does two requests against the same ELF file abc.so as a source. If one request uses abc.so with debug symbols, and second using it without abc.so. What is being cached and how? Will process abc.so twice, in one case caching debug symbols info, and in another only ELF symbols? Or we'll try to be clever and reuse the same cached info?

Do you have a specific request from users to make this configurable per request?

No users requests. The existing design of making this flag per symbolizer is questionable, in my opinion. It has just been this way because it has always been this way.

I agree that with the setup where we have sources pointing to files/apks/etc, it makes sense to make this a property of the source, not the overall symbolizer entity.

As I mentioned in the commit message, it does not make sense to think of "debug information" or "debug symbols" as a global property, as that would imply that it pertains all formats in one way or another. Yet, the only format to which it applies is ELF. If we were to introduce a DWARF symbolization source, would we introduce a global "fallback to ELF" flag? I wouldn't think so, it would be a property of the source itself.

Agreed.

Comment regarding debug_syms being per-request. This has tremendous effect on what kind of information is cached internally for each Symbolizer instance.

Can you elaborate? What is the big difference to what we are doing?

When thinking about the same ELF file with DWARF, we'd be processing and caching different parts of DWARF depending on whether, say, inline funcs are required or not, or whether source code info is requested. That's what I referred to.

Gotcha. Keep in mind that code information and inlined function data is still a per-symbolizer thing. That is, they can't change between requests. Hence, conceptually that just falls under the umbrella of "whatever we cache for DWARF".

And it's also a decision that usually is not change mid-flight. Application either intends to do more expensive debug_syms mode, or sticks to simpler ELF symbol-based symbolization.

And in such cases nothing really changes for users, right?

So what confused me was the "per-request" part as opposed to "per-data source" part. But I just double checked the API and your commit, and it seems like that's exactly what you are changing this to, right? This is a property of each source of info, whether to provide more detailed info or not. And that makes sense to me.

Yep, the data source is provided on a per-request basis, so I used the two interchangeably.

And just to double check my understanding. In a scenario where user does two requests against the same ELF file abc.so as a source. If one request uses abc.so with debug symbols, and second using it without abc.so. What is being cached and how? Will process abc.so twice, in one case caching debug symbols info, and in another only ELF symbols? Or we'll try to be clever and reuse the same cached info?

We will be clever. We'd reuse (share) the same ElfParser instance in both cases, which includes all the cached ELF data structures. Once the DWARF request comes in we'd also cache the DWARF data on top of that. So from my perspective it's optimal with respect to caching: nothing is discarded and nothing is done multiple times.


Crate builder 0.25.0 released

https://github.com/describo/crate-builder-component/releases/tag/v0.25.0

Thanks for the pull request and i've moved the navigation emitter to the start of the method. That was a bug. Navigation is always emitted. It's up to the outer app to listen to it if it wants to. But if it does, it should probably set enableInternalRouting to false.
New version 0.25.1 published to npm.

Thanks, it works now!
I thought you pass the @id of the entity along with the navigation event, but it seems to be some kinfo internal id.
For example, when I navigate to this entity:
        {
            "@id": "http://nla.gov.au/nla.party-479603",
            "@type": "Person",
            "email"<EMAIL_ADDRESS>            "familyName": "Thieberger",
            "givenName": "Nick",
            "homeLocation": { "@id": "#country_Australia" },
            "name": "Nick Thieberger"
        }

I expected to get http://nla.gov.au/nla.party-479603 as the id argument, but I got od3upvwyduhee8yy5z34538e7z5m25ol
What is this id usable for? Could you maybe also pass the @id of the entity where we navigate to?

Yeah - that is an internal id and that's the one I use in the location because it saves me having to url encode the @id property and dealing with any of that complexity. Plus, it maps directly to internal entity representation. Anyway, I've just published 0.25.2 which also emits @id in the navigation event so you can use that if you prefer.

Thanks, it works great, published the new release: https://www.npmjs.com/package/@describo/crate-builder-component-react


Syncing the TP Scores on the Scores Sheet with the repo

Well, less work

Closed in Timwi/KtaneWeb@cde51c485f2a4dfdc99cacc802920e770794b262


⚠ Bofrost.es has degraded performance

In be4dd06, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1448 ms

Resolved: Bofrost.es performance has improved in 5c115a9 after 6 minutes.


How to config to Auto open list

Issue summary
I have a screen for select items
So, I want to auto display list when I open this scene.
Some one can help me?
Thank's a lot.
Library versions

Steps to Reproduce
(Write your steps here:)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots!)
Reproducible Code
(Paste exact code snippet and instructions to reproduce the issue.)

@0xngoubou sorry for the late response. Might have to add this when publishing a new version of the package. Thanks

I would be interested in this feature aswell

@0xngoubou sorry for the late response. Might have to add this when publishing a new version of the package. Thanks

I would be interested in this feature aswell

Is there any progress?

@0xngoubou sorry for the late response. Might have to add this when publishing a new version of the package. Thanks
Any Update?

@0xngoubou sorry for the late response. Might have to add this when publishing a new version of the package. Thanks

Any Update?

@HuzamMughals @vedatbozkurt Is there PR so I can merge and publish?


"Migrating to Up from Now"

(not a real issue)
We've been users of Up for a while now and have used all of the current lambda deployment implementations and Up has always treated us the best.
With that said, Now v2 was just launched and none of our apps work that are on it (because they were either Docker deploys or their new version just doesn't work because it does too much magic).
It's a good time to maybe write a blog post about migrating for many reasons.  Up is cheaper, works, and doesn't have the same current v2 limits.
Unrelated:

When are other events (SNS mainly) going to be supported if ever?

Thanks, @tj.  Been following you for years (esp back in your node days :P)

a lot of people seem frustrated with now v2 -> https://news.ycombinator.com/item?id=18407503

Yup, exactly. I enjoyed zeits stuff and was lambda is a comforting move. We had some stuff in production that went down many times and came running back to Up.  We want to use only up but use serverless for SNS based services.

Cool cool! Yeah I'll have to give the other FaaS stuff some thought, HTTP/apps is definitely only one tiny portion of this stuff, SQS, Kinesis, SNS, all kinds of awesome things to tap into on AWS. Sounds like they've kind of ruined their niche, in exchange for a tiny portion of what makes FaaS great

I didn't realize they were literally repurposing AWS Lambda as well hahah.... I was planning on repurposing pretty much everything in AWS but they're definitely going that route now. Not sure it makes sense to compete with a startup doing the same thing though, it's much harder to afford it without all that free $$, not making much as-is.   They really lost their user-base.  I mean, "Serverless" is already a thing.  Up is already a thing.  I don't see why they try to compete with Serverless when their first iteration has no support for anything BUT http events.  The docker deployments were their bread and butter.  In fact, I had apps that were too complex for Lambda and started going the Now + Docker route and next day the v2 announcement happened and I scrapped it.  Their Cloudflare partnership was pretty cool though.

@tj, one big difference between now v2 and Up is that now v2 pushes developers to decompose each route into an individual lambda, a la the Serverless framework as I understand it. In this way, it looks more like Serverless than Up to me.


IGNITE-1397 Load/consistency test framework

The branch is out dated. Up to date implementation at another branch. Will open new PR.