av stack submit incorrectly picks base branch

I have a repo whose base branch is main instead of master and when I try to submit I get the following output:
⇒  av stack submit
Creating pull request for branch main:
  - pushing to origin/main
error: failed to determine commits to include in PR: git rev-list: exit status 128

Which, when I enable debug logging, appears to be because av is calling git rev-list --reverse master..HEAD instead of main..HEAD
⇒  av stack submit --debug
DEBU[0000] enabled debug logging                         av_version=v0.0.11
DEBU[0000] git [rev-parse --git-dir]                     duration=19.341208ms repo=ops
DEBU[0000] loaded Git repo                               git_dir=.git
DEBU[0000] no configuration found
DEBU[0000] loaded repository metadata: {ID:MDEwOlJlcG9zaXRvcnk1OTI0MzM3Mw== Owner:color Name:ops}
DEBU[0000] git [for-each-ref --format %(refname)%00%(objecttype)%00%(objectname)%00%(upstream)%00%(upstream:track) refs/av/branch-metadata/**]  duration=21.988209ms repo=ops
DEBU[0000] found branch metadata refs                    refs="[{refs/av/branch-metadata/Import-datadog-namespace blob 3ea795847987533e9f34513c14d5dd67b2f0cd81  } {refs/av/branch-metadata/main blob ce210334cfe0357c59e73f869dd9d60fe6449269  }]"
DEBU[0000] git [cat-file --batch]                        repo=ops
DEBU[0000] parsed branch metadata: {"parent":{"name":"main","head":"6909b238020139f5f811262c1ffbd3a41352d757"}} => meta.data{BranchAlias:meta.BranchAlias{Name:"Import-datadog-namespace", Parent:meta.BranchState{Name:"", Trunk:false, Head:""}, Children:[]string(nil), PullRequest:(*meta.PullRequest)(nil), MergeCommit:""}, Parent:json.RawMessage{0x7b, 0x22, 0x6e, 0x61, 0x6d, 0x65, 0x22, 0x3a, 0x22, 0x6d, 0x61, 0x69, 0x6e, 0x22, 0x2c, 0x22, 0x68, 0x65, 0x61, 0x64, 0x22, 0x3a, 0x22, 0x36, 0x39, 0x30, 0x39, 0x62, 0x32, 0x33, 0x38, 0x30, 0x32, 0x30, 0x31, 0x33, 0x39, 0x66, 0x35, 0x66, 0x38, 0x31, 0x31, 0x32, 0x36, 0x32, 0x63, 0x31, 0x66, 0x66, 0x62, 0x64, 0x33, 0x61, 0x34, 0x31, 0x33, 0x35, 0x32, 0x64, 0x37, 0x35, 0x37, 0x22, 0x7d}} &meta.Branch{Name:"Import-datadog-namespace", Parent:meta.BranchState{Name:"main", Trunk:false, Head:"6909b238020139f5f811262c1ffbd3a41352d757"}, Children:[]string(nil), PullRequest:(*meta.PullRequest)(nil), MergeCommit:""}
DEBU[0000] parsed branch metadata: {"parent":{"name":"master","trunk":true},"children":["Import-datadog-namespace"]} => meta.data{BranchAlias:meta.BranchAlias{Name:"main", Parent:meta.BranchState{Name:"", Trunk:false, Head:""}, Children:[]string{"Import-datadog-namespace"}, PullRequest:(*meta.PullRequest)(nil), MergeCommit:""}, Parent:json.RawMessage{0x7b, 0x22, 0x6e, 0x61, 0x6d, 0x65, 0x22, 0x3a, 0x22, 0x6d, 0x61, 0x73, 0x74, 0x65, 0x72, 0x22, 0x2c, 0x22, 0x74, 0x72, 0x75, 0x6e, 0x6b, 0x22, 0x3a, 0x74, 0x72, 0x75, 0x65, 0x7d}} &meta.Branch{Name:"main", Parent:meta.BranchState{Name:"master", Trunk:true, Head:""}, Children:[]string{"Import-datadog-namespace"}, PullRequest:(*meta.PullRequest)(nil), MergeCommit:""}
DEBU[0000] git [symbolic-ref --short HEAD]               duration=20.74175ms repo=ops
DEBU[0000] finding subsequent branches for "Import-datadog-namespace"
Creating pull request for branch main:
DEBU[0000] git [rev-parse --symbolic-full-name main@{u}]  duration=19.571708ms repo=ops
DEBU[0000] pushing latest changes                        upstream=origin/main
  - pushing to origin/main
DEBU[0001] git [push --force-with-lease]                 duration=1.205279583s repo=ops
DEBU[0001] git [cat-file blob refs/av/branch-metadata/main]  duration=22.642417ms repo=ops
DEBU[0001] parsed branch metadata: {"parent":{"name":"master","trunk":true},"children":["Import-datadog-namespace"]} => meta.data{BranchAlias:meta.BranchAlias{Name:"main", Parent:meta.BranchState{Name:"", Trunk:false, Head:""}, Children:[]string{"Import-datadog-namespace"}, PullRequest:(*meta.PullRequest)(nil), MergeCommit:""}, Parent:json.RawMessage{0x7b, 0x22, 0x6e, 0x61, 0x6d, 0x65, 0x22, 0x3a, 0x22, 0x6d, 0x61, 0x73, 0x74, 0x65, 0x72, 0x22, 0x2c, 0x22, 0x74, 0x72, 0x75, 0x6e, 0x6b, 0x22, 0x3a, 0x74, 0x72, 0x75, 0x65, 0x7d}} &meta.Branch{Name:"main", Parent:meta.BranchState{Name:"master", Trunk:true, Head:""}, Children:[]string{"Import-datadog-namespace"}, PullRequest:(*meta.PullRequest)(nil), MergeCommit:""}
DEBU[0001] base branch is a trunk branch                 base=master
DEBU[0001] git [rev-list --reverse master..HEAD] failed: exit status 128: fatal: ambiguous argument 'master..HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'  duration=20.581042ms repo=ops
DEBU[0001] command exited                                duration=1.381650834s
DEBU[0001] fetched latest released version               latest=v0.0.11
error: failed to determine commits to include in PR: git rev-list: exit status 128
        exit status 128
        git rev-list
        github.com/aviator-co/av/internal/git.(*Repo).Git
                /home/runner/work/av/av/internal/git/git.go:68
        github.com/aviator-co/av/internal/actions.CreatePullRequest
                /home/runner/work/av/av/internal/actions/pr.go:161
        main.glob..func10
                /home/runner/work/av/av/cmd/av/stack_submit.go:57
        github.com/spf13/cobra.(*Command).execute
                /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:872
        github.com/spf13/cobra.(*Command).ExecuteC
                /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:990
        github.com/spf13/cobra.(*Command).Execute
                /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:918
        main.main
                /home/runner/work/av/av/cmd/av/main.go:115
        runtime.main
                /opt/hostedtoolcache/go/1.18.10/x64/src/runtime/proc.go:250
        runtime.goexit
                /opt/hostedtoolcache/go/1.18.10/x64/src/runtime/asm_arm64.s:1270
        failed to determine commits to include in PR

I can see there are two things that went wrong:

Looking at line parsed branch metadata, it seems that the parent of a topic branch is set to master instead of main. I'm not sure how this was set. Simple grepping the source code apparently doesn't have a hard coded master in the repository. I have no idea on this.
Looking at line pushing to origin/main, it seems that av-cli tries to push to main, which is wrong. https://github.com/aviator-co/av/blob/9b993bb53f138f6fe1af37605dacbbabd4f90ae7/internal/actions/pr.go#L107 suggests that the CLI assumes that "the upstream is where the branch should be pushed to", but probably this is not the case. Per git-core's documentation, https://git-scm.com/docs/git-branch/2.13.7#Documentation/git-branch.txt---track sets the upstream to where it's branching off e.g. main, so it's more consistent to use the upstream tracking branch as "the target branch that a PR should be merged to". This behavior is also consistent to git pull, which does merge the tracking branches into the local branch https://git-scm.com/docs/git-config#Documentation/git-config.txt-branchltnamegtmerge.

Additional note on this: av-cli's behavior that "pushing to the remote tracking branch" is the strategy you would get when you use push.default = upstream option as described at https://git-scm.com/docs/git-push#Documentation/git-push.txt-pushdefault. As you can see, the Git default option is simple, which does "pushing to the same name branch on the remote". Assuming that most of Git users wouldn't even know this option exist, following the default behavior would be safer option.

Actually, I feel like the repository has master and main branches at the same time. Can you check that?

Actually, I feel like the repository has master and main branches at the same time. Can you check that?

@draftcode sorry for the delay. It does not appear that this is the case:
⇒  git branch -a | rg "(main|master)"
  main
  remotes/origin/ecr-describeimages-pipeline-master
  remotes/origin/main
  remotes/origin/ryanking/tf-run-all-on-master

This was a repo that USED to have master as the default branch but we switched it. Could that be causing a problem?

Ohhhhh interesting. @draftcode.  I don't know how this is possible when there isn't a master branch at all.

I tracked the problem down to this line:
https://github.com/aviator-co/av/blob/9b993bb53f138f6fe1af37605dacbbabd4f90ae7/internal/git/git.go#L41
If you have a repo that had a previous default branch name. Like in my case our repo used to have a default branch named master, and then you switch to main, the output of the command git symbolic-ref refs/remotes/origin/HEAD will still point to the original branch name.
If I run the below command:
⇒  git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main
⇒  git symbolic-ref refs/remotes/origin/HEAD
refs/remotes/origin/main

Then you can see that my symbolic-ref has been updated correctly also.
Maybe this should have a check for this error case? Thanks!


[intermodule] Type / Act consistency check

I ran across this while doing a draft integration of clkmgr.
It seems like we should probably just add a type / act consistency check.
What do you think?
inside pwrmgr, the following end point is defined
    { struct:  "pwr_clk",
      type:    "req_rsp",
      name:    "pwr_clk",
      act:     "req",
      package: "pwrmgr_pkg",
    },

inside clkmgr, the following end point is defined
    { struct:  "pwr_clk",
      type:    "req_rsp",
      name:    "pwr",
      act:     "rcv",
    },

and finally, in top_earlgrey.hjson, this was defined
      'pwrmgr.pwr_clk'  : ['clkmgr.pwr'],

The actor inside clkmgr is not defined correctly (unless this is a supported case?), and the output RTL ends up looking like the following on clkmgr
      // Inter-module signals
      .pwr_i(pwrmgr_pwr_rst_req),
      .pwr_i(pwrmgr_pwr_rst_rsp),

Seems like there probably should have been an error check that failed somewhere.

Thanks for the report. I will add in the validation check :)
We could combine type and act into one field ,, req, rsp for req_rsp pair, src, dst for uni direction? For now, I will add checker in the validation .


Adding AudioStellar

Hey @csteinmetz1, great repo :D
I'm adding AudioStellar, an experimental sampler which uses AI to classify sounds in a 2D map.

Thanks!


A duplicate ServiceEntry in two different namespaces is causing issues

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[x] This is not a question about how to use Istio

Bug Description
I have two namespaces, dx-system and dx-prod, each containing a ServiceEntry. The ServiceEntry in the dx-system namespace has HTTP on port 1024 and TLS on port 443, defined as follows:
spec:
  exportTo:
  - '*'
  hosts:
  - cptawcwqy.fusionapps.ocs.oc-test.com
  location: MESH_EXTERNAL
  ports:
  - name: http-servicemesh-port-1024
    number: 1024
    protocol: HTTP
  - name: tls-origination-port-1024
    number: 443
    protocol: TLS
  resolution: DNS

Meanwhile, the ServiceEntry in the dx-prod namespace has only TLS on port 443:
spec:
  exportTo:
  - '*'
  hosts:
  - cptawcwqy.fusionapps.ocs.oc-test.com
  location: MESH_EXTERNAL
  ports:
  - name: tls-443
    number: 443
    protocol: TLS
  resolution: DNS

When I use curl from a pod in the dx-system namespace with the HTTP protocol, the calls fail with a 503 Service Unavailable error, while HTTPS calls work as expected.
HTTP/1.1
> Host: cptawcwqy.fusionapps.ocs.oc-test.com:1024
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 503 Service Unavailable
< content-length: 91
< content-type: text/plain
< date: Mon, 28 Oct 2024 02:48:57 GMT
< server: envoy
<
* Connection #0 to host cptawcwqy.fusionapps.ocs.oc-test.com left intact
upstream connect error or disconnect/reset before headers. reset reason: connection timeoutbash-4.4$

It seems that the ServiceEntry in the dx-prod namespace is being used even for requests originating from the dx-system namespace. If I add port 1024 to the ServiceEntry in dx-prod, HTTP calls work as expected, and no 503 Service Unavailable error occurs.
We only noticed this issue after upgrading Istio to 1.22.3, whereas in 1.21.2, the same configuration worked for both HTTP and HTTPS calls originating from the dx-system namespace.
Is adding port 1024 to the dx-prod ServiceEntry the correct fix for this issue, or should we take another approach? Is spec.exportTo = "*" causing the issue?
Version
client version: 1.15.1
control plane version: 1.22
data plane version: 1.22-dev (36 proxies)

Client Version: v1.24.3
Kustomize Version: v4.5.4
Server Version: v1.30.1

Additional Information
No response

Same as: https://github.com/istio/istio/issues/52546

@howardjohn I applied this to both the dx-system and dx-prod namespaces, but it didn't fix the issue.

I am also facing similar issue. Im trying to do TLS origination from egress gateway for all calls to one of our service hosted outside the cluster. Inside mesh uses http calls.
Similar to @iampratapak , I have 2 ns with SEs, one with 1024 http port and 443 port. Other one in second ns with 443 port alone.
With this setup Im getting 5xx reply for the http calls.
And when I delete the SE in second ns (that with 443 alone) the http calls start working.
The http call will continue working even if we re-create that deleted SE, so I guess the creation time of SE(s) here have something todo. As of now Im forcefully delaying  the creation of the SE in second ns as a workaround.
Is this the expected behaviour when there are duplicate SEs ?
I tried and got same behaviour in 1.22.3 and 1.22.6
bash-3.2$ ./bin/istioctl version client version: 1.22.6 control plane version: 1.22.6 data plane version: 1.22.6 (2 proxies) bash-3.2$


KeyError: 'data' after running downloader.py

Tried to run the test example provided from http://www.rldw.de/2015/04/using-the-instagram-api-with-python/ and encountered a KeyError: 'data' ??
When executing the downloader.py script i encounter the following issue:
File "downloader.py", line 58, in callAPI
maxtimestamp = current['data'][-1]['created_time']
KeyError: 'data'
Could you provide me some insights why it raises the error?
python: 2.7 / on mac terminal.

i also got the same error, did you find the solution for this ?

I encountered this problem in the past. This is most probably due to the fact that Instagram changed its API policy.
To make sure this really is the problem please check the following: Use the URL given below and replace the XXX at the end after client_id= with your client ID.
https://api.instagram.com/v1/tags/food/media/recent?count=40&max_tag_id=1165123837386404099&client_id=XXX
Then copy the whole URL and open it in your browser. If it gives you an error that says your access_token is invalid then your client ID is the problem.


Fixes to update fuels-rs on small values as single bytes

Description
This PR contains some necessary fixes to enable this https://github.com/FuelLabs/fuels-rs/pull/1163 to be merged.
1 - It guarantees that when the env var FORC_IMPLICIT_STD_GIT_BRANCH is used, no tag or rev is also used;
2 - It removes all warnings from the sway std-lib;
3 - It fixes reading predicates witness when it is only one byte.
Checklist

[ ] I have linked to any relevant issues.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book).
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[ ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

@hal3e did all the changes. Although I had to keep some of the fee methods.

@hal3e did all the changes. Although I had to keep some of the fee methods. Also not sure what happened to the branch: hal3e/tx-status-log-and-response. It was merged already?

It is not merged yet to the SDK's master. I am working on it. BTW can we merge this branch to sway master ? I need it in https://github.com/FuelLabs/sway/pull/5281


handle namespaces where all blocks are hidden

Fix for https://github.com/Microsoft/pxt-adafruit/issues/469


Improve Error Message From Running kubectl apply -f for PipelineRuns/TaskRuns

When creating PipelineRuns/TaskRuns that use generateName with kubectl, kubectl create must be used as a new run is created each time. However, it is a common mistake to run kubectl apply and get the following error message:
from server for: "STDIN": resource name may not be empty

For first time users, this is particularly confusing. It would be helpful to include a more descriptive error message to account for this scenario so users can appropriately handle the situation.
Expected Behavior
Error message suggesting to run kubectl create instead of kubectl apply.
Actual Behavior
from server for: "STDIN": resource name may not be empty

Steps to Reproduce the Problem

Create a TaskRun/PipelineRun using kubectl apply -f (Use any example under the examples folder).
Observe error message.

/kind bug

Making a note here that this actually appears to be an issue with kubectl itself regarding the error message. The problem is that kubectl apply hasn't accounted for this situation, and it's arguable that it should not have to.
The full error message is as follows:
error: error when retrieving current configuration of:
Resource: "tekton.dev/v1alpha1, Resource=taskruns", GroupVersionKind: "tekton.dev/v1alpha1, Kind=TaskRun"
Name: "", Namespace: "default"
Object: &{map["apiVersion":"tekton.dev/v1alpha1" "kind":"TaskRun" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "creationTimestamp":<nil> "generateName":"s2i-nodejs-run-" "namespace":"default"] "spec":map["inputs":map["resources":[map["name":"source" "resourceRef":map["name":"nodejs-ex-git"]]]] "outputs":map["resources":[map["name":"image" "resourceRef":map["name":"nodejs-ex-image"]]]] "serviceAccountName":"" "taskRef":map["name":"s2i-nodejs"] "timeout":"1h0m0s"] "status":map["podName":""]]}
from server for: "taskrun.yaml": resource name may not be empty

The error message retrieving current configuration of can be found in kubectl apply. It occurs during validation of the TaskRun or PipelineRun object, so it's outside of the control of Tekton as far as making the error message more user friendly. This would require some thinking on a way to make the kubectl apply error message account for Tekton.

Closing this and have opened corresponding issue for kubectl.


popovers: Extract user_profile_modal functions in separate module.

We had a lot of functions and click handlers that were only
involved with user profile modal and were not related to
popovers logic in any way. So we extract these functions
into a separate module user_profile.js.
Testing plan: Manually checking that behavior of user info modal remains same even after this.

Merged, thanks @m-e-l-u-h-a-n!  I think it's definitely correct to not block extracting a module on getting 100% test coverage (even if that is a good idea as a follow-up).


Why textarea visible?

I'm wondering the need to position absolute and 9999px to "hide" the fake element. Why not just display: none?
I did a little test and it works for me: https://jsfiddle.net/ay9kjb1v/
Maybe you already tried. Just asking.

We only use that fake element for data-clipboard-text.


pkg/reportingplugins/mercury: override encoded length to 96

Supporting https://github.com/smartcontractkit/chainlink/pull/9371
Do not merge.

This is included with #121


Reduce rate of Mesos offer logging (resolves #1078)

@arkal I clarified the logging statements and tested it. I think its good to merge, can you take a final look at some point before I do?

Looks good!


Add depend strategy for reflections

Describe the enhancement requested
Currently, when creating a reflection, dbt-dremio triggers it on dremio and instantly finishes the job if the trigger was successful. We would like to be able to configure a strategy that makes dbt wait for the completion of the reflection job on dremio, before marking it as successful and moving on to the next item in the dbt DAG. This would also allow us to get feedback on a reflection failure.
The configuration keyword could be strategy with the possible values depend or trigger, the later being the current and default value.
Justification for this enhancement
This feature would allow for better control and debugging of reflection jobs.

Hi there, any feedback for this issue?


Rename only applies on declaration and not on references

I've tested it in Neovim and in VSCode and got the same results, so I believe the issue is with rust-analyzer.
rust-analyzer version: rust-analyzer version: db2a7087b 2021-12-13 stable (also happens in rust-analyzer 0f8c96c92 2022-01-10 dev)
rustc version: rustc 1.57.0 (f1edd0429 2021-11-29)
When I have functions with certain macros the renames only renames the declaration and not the references:
For example:
async fn main() {
    let variable = hex::decode("0bd666ccf2c6ae927efd7b151eeb9b88422100f6e688b9e926fc1d2d03b0292e7491216ed39a267d3f8e21531ab83a30c6b0d15ec64fe1e3be00da2e13d5b181").unwrap();
    println!("{}", variable);

If I rename the variable here it works fine. But in this example bellow it just renames the declaration:
#[actix_web::main]
async fn main() {
    let variable = hex::decode("0bd666ccf2c6ae927efd7b151eeb9b88422100f6e688b9e926fc1d2d03b0292e7491216ed39a267d3f8e21531ab83a30c6b0d15ec64fe1e3be00da2e13d5b181").unwrap();
    println!("{}", variable);
}

Most likely an upmapping issue

Debugging this might be a bit annoying as it involves an attribute and our attribute infra for tests isn't that extensive, but
the renaming entry point is here(tests also live here), https://github.com/rust-analyzer/rust-analyzer/blob/62a13cce9b6356af0dfeeeb6add3432f0e76a19f/crates/ide/src/rename.rs#L76-L106 which calls into the actual rename infra here(this is what should care about identifiers inside macro invocations specially) https://github.com/rust-analyzer/rust-analyzer/blob/62a13cce9b6356af0dfeeeb6add3432f0e76a19f/crates/ide_db/src/rename.rs which uses the search module to figure out everything the identifier resolves to(this part should be correct I believe) https://github.com/rust-analyzer/rust-analyzer/blob/62a13cce9b6356af0dfeeeb6add3432f0e76a19f/crates/ide_db/src/search.rs
As an example test, here is one that makes use of our attribute test infra https://github.com/rust-analyzer/rust-analyzer/blob/62a13cce9b6356af0dfeeeb6add3432f0e76a19f/crates/ide/src/rename.rs#L1968-L1988
Note that this specific problem might not be visible with proc_test::identity

(Note that tests do not know about the standard library so println and friends don't work here)
One step first would be to check if putting the cursor on the to be renamed thing makes it highlight all occurences(in VSCode, or using find all references in whatever client), if it doesn't then its a search bug, not a rename bug.

I guess your hunch about the highlighting is right. It is not highlighting any of the references.

Then the search stuff here https://github.com/rust-analyzer/rust-analyzer/blob/62a13cce9b6356af0dfeeeb6add3432f0e76a19f/crates/ide_db/src/search.rs has a problem somewhere


merge from arlac77/npm-package-template

package.json

fix(engines): add >=12.16.1 remove >=12.16.0 (engines.node)

.travis.yml

chore(travis): (jobs.include)
chore(travis): add 13.9.0 remove 13.8.0 (jobs.include.node_js)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


zram-generator: cross-compiled zram-generator produces binaries for the host platform

Describe the bug
When building pkgsCross.aarch64-multiplatform.zram-generator the contained zram-generator binary is for execution by the buildPlatform such as x86_64 rather than aarch64.
Steps To Reproduce
Steps to reproduce the behavior:

nix-build '<nixpkgs>' -A pkgsCross.aarch64-multiplatform.zram-generator;
patchelf --print-interpreter result/lib/systemd/system-generators/zram-generator;
(optional) attempt to execute result/lib/systemd/system-generators/zram-generator on an aarch64.

Expected behavior
The produced zram-generator should be executable by aarch64 machines.
Screenshots
N/A
Additional context
N/A
Notify maintainers
@nickcao
Metadata

system: "x86_64-linux"
host os: Linux 6.1.12, NixOS, 23.05 (Stoat), 23.05.20230219.efc5989
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.13.2
channels(root): ""
channels(nagisa): ""
nixpkgs: /run/current-system/nixpkgs

Ah, a duplicate of https://github.com/NixOS/nixpkgs/issues/216276.


react-loadable-component fallback

For components that are not loaded by the platform, but by another component, no loader is displayed. We wish to be able to show a loader while react-loadable-component fetches all resources.

@kobiburnley we invested quite a lot in designing a correct solution for this issue and plan to solve it in the next Q.
It would be best if you could wait.

@odedcagan regarding the concern of including UI in the bundle: Adding the fallback doesn't mean the UI comes from the component bundle - it can still be passed from the hosting component.
Also, can you please share more specific timelines?

maybe even better via prop:
https://github.com/wix/react-module-container/commit/855931f97708cdcce91ab46e0c5eed167a346fc2


UI inconsistency

I would like to change the effect on hover of the github icon , because its causing Ui inconsistency.
https://github.com/user-attachments/assets/4f494b8e-cde7-4597-b7fa-d35060d6a956
I would like to work on this, assign me this under gssoc ext 24 and hacktoberfest-accepted

Hey @AE-Hertz👋! Thanks for raising this issue and demonstrating your interest in contributing to our project!🚀
We value your engagement and eagerly anticipate your contributions. Should you wish to get involved, please use the /assignme command to self-assign the issue.
This issue provides an excellent opportunity for us to enhance our project, and we're excited to have you join us! Please take a moment to review our CONTRIBUTING GUIDELINES before getting started.
If you have any questions or need assistance, feel free to reach out to us on LinkedIn.❤

/assignme

Hello @AE-Hertz! We'd like to inform you that the issue has been resolved and is now closed. We appreciate your understanding and look forward to your continued involvement with our repository!🤗
If you encounter any further issues, please don't hesitate to reach out to us on LinkedIn. Thank you for your support!❣
Happy coding!✨ We hope to see you again soon!❣


OpenAPI Error - run_temperature_description

I tried to parse a YAML file with Microsoft's OpenApiStringReader, but it threw an error. The YAML file was easily parsable last week without any issues.
{(Lin: 0, Col: 0, Chr: 0) - (Lin: 0, Col: 0, Chr: 0): The anchor 'run_temperature_description' already exists [#line=0]}
Also, the same issue with the run_top_p_description parameter exists.
I think one of these PR merges caused the issue.
https://github.com/openai/openai-openapi/pull/230
https://github.com/openai/openai-openapi/pull/228

Same. Common guys. You are a multi-billion dollar company with one product that is the API and you can't keep the openAPI-specs in a state that matches the specs?

Do you have any intention to address this problem?


[Backport 1.x] Add lifecycle support in opensearch container

Description
[Backport 1.x] Add lifecycle support in opensearch container
Issues Resolved
[Enhancement][OpenSearch] #395
Backport of PR#376
Check List

[x] Commits are signed per the DCO using --signoff

For any changes to files within Helm chart directories:

[x] Helm chart version bumped
[x] Helm chart CHANGELOG.md updated to reflect change

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for the backport PR @josephteddick, LGTM, I will allow the checks to pass and merge it.
Thank you


Remove unused Option en/decoding

Fixes #175

Agreed with @sgeisler, we might as well remove this.


Remove Claim dates from form add

As an analyst
I want the claim dates to be auto imported from the excel
So that I don't have to enter them in manually
Description:
Removing the claim dates from the form as we will auto import from the xls
Acceptance Criteria:

[ ] Remove the fields to manually enter in the claim dates when adding or editing the claims record
[ ] Claims view shows dates from the xls (see related ticket #2005)

Implementation Details

Hey team! Please add your planning poker estimate with Zenhub @VB-at-Bis @marcellmueller

Please add your planning poker estimate with Zenhub @rafasdc


Fixed #375

I addressed a dirty way to solve this problem as I'm not familiar with Jackson library and we have to get Wapo indexing now.

@Kytabyte Remove this line? It's redundant.

@borislin This is a Document field storing the document content string here

I came across a new bug while searching the collection with the index. Please leave this PR until I addressed this issue.

@Kytabyte No, the field you are referring to is this.

@borislin I see! Addressed!

@borislin can you do CR here? Let’s fix it correctly... no jank please...

@Kytabyte Are List<String> and 'Map<String, String>' new types for content in wapo v2? When I did the Jackson refactor, I don't think the original design supports these two types.

@borislin No, it's not a new feature. Actually, there is List<String> and Map<String, String> in original wapo collection but I didn't notice that because there may be only, say one or two paragraphs out of 10 documents have these structures. However, the JSON parser I used to use is not a recursive parser, so these Lists or Maps are treated as String so no errors raised.  So when Jackson recursively parse these files, the types are getting mismatched.

@Kytabyte I see. Can you add a custom deserializer for the Content class instead of using Object in a janky way?
Examples:
http://www.baeldung.com/jackson-deserialization
https://github.com/castorini/Anserini/blob/master/src/main/java/io/anserini/ltr/feature/OrderedQueryPairsFeatureExtractor.java#L35

@borislin Sure. Will do!

@borislin addressed CR!

@Kytabyte Did you test the PR against the v2 corpus?

@Peilin-Yang Yes. The number of indexed files/empty files is the same as the one from my original design now.


About

Updated About Page Design
Implemented Tailwind CSS for styling the About page, improving layout consistency and responsiveness.
Adjusted the team member section layout, including aligned images, text, and LinkedIn icons for better visual presentation.
Optimized the image and text alignment to match design requirements
Integrated custom CSS variables for consistent theme colors
Cleaned up redundant or outdated CSS in the project.
Resolved conflicts in src/app/globals.css and tailwind.config.ts.
Ensured all changes from the main branch were incorporated without affecting new updates on the About page.

Looks great! I noticed a styling issue with the images grid. The images look great on small and desktop screens. In between it looks like they aren't centered on the grid so might just need some additional breakpoint style or something. I attached some pictures to help.
Not a blocker for this PR though.

Ready to merge!
@galenom I created a ticket for your point about the items not being centered in the grid and assigned it to @geraxrodriguez . Asana link here: https://app.asana.com/0/1207992233793749/1208554811111884/f


Add new border-radius utilities

Fixes #36536
New border-radius utilities to combine .rounded-{top|bottom|start|end} with .rounded-{0-5|pill|circle}.

[ ] Probably need to modify https://github.com/twbs/bootstrap/blob/0a3864641b5cbd27a0b7eff153ef661f3eda3802/site/content/docs/5.2/migration.md?plain=1#L73

Live preview

@julien-deramond , I was about to ask/implement the very same features. Right now (v.5.2.0beta1) in order to achieve rounded-START-pill you can combine rounded-pill + rounded-END w/o rounded size

There was a release - downloaded installed - still the same error, at the beginning the radius is applied, and at the end on the right, but it should be on the left.


Create ca_certs job

Hey,
I want to add trusted certificates to a bosh, rolled out using bosh create-env.
I tried to achieve this using the runtime-config of os-conf-release:
The respective part of my runtime-config:
releases:
- name: os-conf
   version: 13
addons:
- name: os-configuration
  jobs:
  - name: ca_certs
    release: os-conf
    properties:
      certs: |
        -----BEGIN CERTIFICATE-----
        certificate1...
        -----END CERTIFICATE-----
        -----BEGIN CERTIFICATE-----
        certificate2...
        -----END CERTIFICATE-----

I also updated the manifest to enforce a redeployment. However, it does not work. When logging in to the bosh vm, I cannot find any files in /usr/local/share/ca-certificates/.
What am I doing wrong?

Sorry for the delay. Currently bosh create-env does not support the addons section. You would need to include the ca_certs job in the main instance group definition (alongside the director and nats jobs).
Once you have your director up and running, you should be able to execute the bosh update-runtime-config ... command with your existing config. Then your future instances will have these CA certs installed on them.


rename sources

do note use '-'
add prefix iob_cache_
module name should match
test should pass in the end

this is completed


fix: adjust column hiding

Description
Hide table columns when hidden is set to true.
Notes: remove isHidden in favour of hidden

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to change Viscosity value for certain locations and times to simulate liquid freezing?

What is the best way to change the viscosity level of the particles in time. I want to change it for the particles as a function of their time after their emission without affecting the rest of the system i.e particles.
e.g Particles freeze after being emitted to simulate additive manufacturing.
I canot find a functon to do that, how would I write one?

Currently all particles have the same viscosity value. So you would have to extend the framework and add a field which stores the viscosity coefficient per particle. This is quite simple:

Add a vector m_viscoCoeffs in Viscosity_Weiler2018.h
In Viscosity_Weiler2018.cpp each time m_viscosity is used, exchange this by m_viscoCoeffs[i]
Write a function to update m_viscoCoeffs. This could even be done in Python using our Python binding.

How do I populate the vector and then how do I know which index to increase the viscosity of? How do I know which index is for each particle for example? How many elements are pushed per step size?

You can take a look at the file SurfaceTension_He2014.h and how the field std::vector m_color; is used there. To identify the particle you can use its ID or its position.


Add way to blacklist / whitelist IP destination addresses

The default implementation of CORS Anywhere (server.js) does not restrict the target URLs. The ability to enforce restrictions based on the destination URLs has been requested in #67. Since I am going to add this to improve security, I should also do something with another glaring issue:
Normally resources from servers on localhost or a local private network are not really open to the web. CORS Anywhere is designed to allow any website to read public data from any other website (credentials are explicitly stripped). However, information in a private network is likely not supposed to be public information, so such requests should be rejected by default.
Implementation plan
Public API
Support a new option, dnsLookup, with the following signature:
@param {string} hostname - The host name of the server to which CORS Anywhere
  should connect. If a proxy was configured via the `getProxyForUrl` method,
  then this will be the host name of that proxy (since the proxy is responsible
  for access control).
@param {function(err, address)} callback - The callback to be called when the
  address has been resolved. The request can be rejected by passing a suitable
  value of "err".

To get the current behavior (i.e. allow any IP), use the following implementation of dnsLookup:
var dns = require('dns');
require('cors-anywhere').createServer({
  // ...
  dnsLookup: function(hostname, callback) {
    // This is the default behavior of lookupAndConnect in Node.js "net" module.
    dns.lookup(hostname, { hints: dns.ADDRCONFIG }, callback);
  },
  // ...
}).listen(port, host); // <--- Assuming that host/port are set elsewhere.

Implementation details in CORS Anywhere

The result of the lookup should be assigned to proxyOptions.target in the proxyRequest function.
This will still work fine for both HTTP and HTTPS, because the actual host name is set in the "Host" request header. Node.js's HTTPS/TLS/NET modules use this value for validating certificates (and SNI).

The implementation can look like this (replacing https://github.com/Rob--W/cors-anywhere/blob/143eff177c7e7d4bf241b83c57dd1e2c6378d53b/lib/cors-anywhere.js#L122-L123).
(and also using location.href instead of location at https://github.com/Rob--W/cors-anywhere/blob/143eff177c7e7d4bf241b83c57dd1e2c6378d53b/lib/cors-anywhere.js#L87)
if (!req.corsAnywhereRequestState.dnsLookup) {
  // Start proxying the request
  proxy.web(req, res, proxyOptions);
  return;
}
var targetUrl = url.parse(proxyOptions.target);
req.corsAnywhereRequestState.dnsLookup(targetUrl.hostname, function(err, address) {
  if (err) {
    // TODO: Should errors just be propagated, or should we support something like
    // err.statusCode, err.statusText and err.message to customize the HTTP response?
    proxy.emit('error', err, req, res);
    return;
  }
  targetUrl.host = null; // Null .host so that .hostname + .port is used.
  targetUrl.hostname = address;
  proxyOptions.target = url.format(targetUrl);
  proxy.web(req, res, proxyOptions);
});

Any updates on this? I'd much appreciate the ability to block request to the server's local area network, perhaps have it as the default behaviour. Thank you!


Beautify README.md

As of this moment, the readme file isn't ideal. Make it look better, please. The face of this project must be beautiful :)

should i update the README then??

@xenowits sure, go ahead


Add the game Rhythmic to the list

so that i could get a little advertisement

The reason we haven't merged this yet is because we were figuring out the minimum requirements to list a project here.
I think a good start would be expanding your project's README to include some amount of information on what the project is and its current state, maybe a screenshot or two, and having at least a downloadable release (via github releases). How does that sound?

Will do that, but at the state it is right now. its not really playable at all (gameplay wise, settings, etc) since i still have to learn on how to make the game know on what score you got, how to do gameplay elements and etc. but other then that i will expand the README to explain the game and the current state


UTF8 encoder based on the CoreCLR implementation

cc @KrzysztofCwalina, @jkotas, @shiftylogic
I took the CoreCLR implementation of the UTF8 encoder and fixed it up to fit the Span-based encoder signature with minimal refactoring. It is ~2x faster for the ASCII range than current https://github.com/dotnet/corefxlab/pull/1139.
@ahsonkhan Could you please run your perf tests on it?

Also, see my comments in https://github.com/dotnet/coreclr/pull/9187 . I think we should work towards having same workhorse method for here as well as in CoreCLR. We will be able to share any improvements made here with CoreCLR that way.

Looks good.
Just one question: do you think it would be possible to share the source with the corclr implementation? Even if it just meant to be able to easily copy and paste a whole file between these two repos.

do you think it would be possible to share the source with the corclr implementation?

Yes. It is what I am basically asking for in https://github.com/dotnet/coreclr/pull/9187. (The side-effect is that it will make the CoreCLR implementation faster.)

@ahsonkhan Could you please run your perf tests on it?

So, I ran my perf test and this implementation is indeed faster (faster than the current CoreCLR impl as well) :)

Given that the implementation is faster and similar in complexity/code length as the state I ended up reaching, it makes sense to use this over mine.
However, looking at the different encoder/decoders in System.Text.Primitives, how do we plan to share the implementations or keep them in sync? And if we aren't doing that, how do we go about maintaining them separately? I could imagine us having implementations that could diverge from CoreCLR (different signatures, other encodings).

how do we plan to share the implementations or keep them in sync?

Yes, we should try to use same the core encoding/decoding methods between the different places and avoid diverging them. Check the discussion in
https://github.com/dotnet/coreclr/pull/9187#discussion_r98521142

And if we aren't doing that, how do we go about maintaining them separately?

The low-tech solution to do that is to add a comment that if you change one copy, you should update other copy to match. I do not expect that the encoders/decoders will change that frequently, so it should work fine to do it that way.

LGTM.

@dotnet-bot test this please

The low-tech solution to do that is to add a comment that if you change one copy, you should update other copy to match. I do not expect that the encoders/decoders will change that frequently, so it should work fine to do it that way.

Can we add such a comment here so it is explicit? Also in CoreCLR?

@dotnet-bot test this please

@dotnet-bot test Windows Release  please

@dotnet-bot test this please

@dotnet-bot test this please

I am not sure why the CI keeps failing.

@ahsonkhan I do not see the tests that you have added running. When I run dotnet test in under tests\System.Text.Primitives.Tests, it just prints Starting test execution, please wait... without any signs of the tests running. How are you running these tests?

I believe that the latest VS 2017 build changes (PR #1151) have disabled System.Text.Primitives.Tests (along with some others). I think it is because System.Text.Primitives.Tests references xunit.performance.core.

Tests that reference xunit.performance.core can not be discovered and will not be run in either VS or the command line.

I created a separate local project and added an xunit project where I was writing/running these tests (along with the ref return method to code the TryEncode method).
So, currently, I don't think the tests are running. However, I did copy over your method implementation into my standalone app and ran my new tests against it.
There is an issue open for this, but I am not sure how to make progress on it yet (Issue #1155).

did copy over your method implementation into my standalone app and ran my new tests against it

Thanks!


VM: List.removeLast and List.clear leak memory

Using removeLast and clear does not always reduce the memory used by the list.
Should be about 10Mbyte, but uses 14Gbytes.
Here is an example program that uses O(n2) memory where it should only use O(n) memory:
main() {
  List all = [];
  for (int i = 0; i < 50000; i++) {
    List nums = [];
    for (int j = 0; j < i; j++) {
      nums.add(j);
    }
    for (int j = 1; j < i; j++) {
      nums.removeLast();
    }
    if (nums.length == 1) {
      int x = nums[0];
      nums.clear();
      nums.add(x);
    }
    all.add(nums);
  }
}

If the line nums.clear() is replaced by nums = [] then the memory use does not grow to 14Gbytes.

There is a cost to shrinking a list on removes.
It should definitely not be done on every remove, probably only when the list uses less than 25% of its capacity (which would require removing at least half the elements added since the last time the backing store grew). That still means that every remove gets an extra check (if (newLength * 4 < _buffer.length) _shrink();). It will probably still only shrink by half (shrinking exactly to the needed capacity would mean that a single add operation would grow it again). A check on every operation is not a big thing, but it's there.
If you ever fill the List to capacity again, you will have to regrow the buffer. Since it's impossible to predict the usage pattern, there will be sequences of operations that become slower if you avoid the memory leak.
One alternative is to only shrink lists on GC. When copying the backing store of a growable list, and the list is <25% used, shrink the list. That won't affect a lot of quick operations on the same list, but if it stays alive for GC, it gets compacted. If you run out of memory, there will be a GC.
For clear, it's probably safe to do something more drastic, but again, it can also just be done in preparation for using the list again, otherwise, why keep a reference to the list.

Yes, our initial plan is to use the 25% mark as a good time to shrink.  This should be asymptotically better than what we have now.  We don't expect a performance regression, but it's my opinion that a small constant-factor regression is acceptable to fix an asymptotically worse memory complexity.
Changing the shape and size of objects at GC time is not something I have great experiences with, so I think we want to avoid it.  The problem is that GC happens at a very unpredictable time from the POV of the optimizer, which can easily cause subtle bugs.  Other resizing and rewriting of objects can be tricky (see for example Array::MakeArray), but at least if it happens in a native call or special instruction you have some way to signal to the optimizer that 'interesting stuff happens here'.


Stage commits for 2.11 patch release

Issue #, if available:
Description of changes:
Cherry pick commits from mainline
Why is this change necessary:
How was this change tested:

[ ] Updated or added new unit tests.
[ ] Updated or added new integration tests.
[ ] Updated or added new end-to-end tests.
[ ] If my code makes a remote network call, it was tested with a proxy.

Any additional information or context required to review the change:
Documentation Checklist:

[ ] Updated the README if applicable.

Compatibility Checklist:

[ ] I confirm that the change is backwards compatible.
[ ] Any modification or deletion of public interfaces does not impact other plugin components.
[ ] For external library version updates, I have reviewed its change logs and Nucleus does not consume
any deprecated method or type.

Refer to Compatibility Guidelines for more information.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We identified new issues on unchanged lines of code. Navigate to the Amazon CodeGuru Reviewer console to view the recommendations to fix them.


support mkfs for userspace convertor

What this PR does / why we need it:
add an flag --mkfs for convertor, which make ext filesystem in the bottom layer, base layer is not required under this config.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Please check the following list:

[ ]  Does the affected code have corresponding tests, e.g. unit test, E2E test?
[x]  Does this change require a documentation update?
[ ]  Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ]  Do all new files have an appropriate license header?

@WaberZhuang  cc


FIX: Clear reply-to when channel is switched

@CvX I know you'll have the async in the test... but the chat float component waits on a promise to check the channels so... idk how else to do this shiz.

UX question: should it maybe save reply-to info in a message draft instead of just clearing it?

Yeah, that's a better idea isn't it

I ran into something adjacent to this just now: when you hit arrow up to edit your last message but then hit Esc to cancel it, it cancels the reply state, but doesn't clear the input. It feels like it should?

Yeah I can clear the input there!


Issue With Docker Deployment

Hello,
We upgraded jsreport.AspNetCore v2.1.0 and are getting an error that we have not gotten before.
According to the docs we need to run some special commands for Docker Linux container deployment. We have this in our dockerfile and it worked before but now we are getting an error.
https://jsreport.net/learn/dotnet-local#docker
RUN apt-get update && \
    apt-get install -y gnupg  libgconf-2-4 wget && \
    wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
    sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
    apt-get update && \
    apt-get install -y google-chrome-unstable --no-install-recommends

ENV chrome:launchOptions:args --no-sandbox

Command failed on instance. Return code: 100 Output: (TRUNCATED)...n-zero code: 100 Failed to build Docker image aws_beanstalk/staging-app: ces.list.d/google.list' && apt-get update && apt-get install -y google-chrome-unstable --no-install-recommends' returned a non-zero code: 100. Check snapshot logs for details. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03build.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.

Failed to build Docker image aws_beanstalk/staging-app: ces.list.d/google.list' && apt-get update && apt-get install -y google-chrome-unstable --no-install-recommends' returned a non-zero code: 100. Check snapshot logs for details.

It seems like the commands in the dockerfile are failing. Has anyone experienced this issue before?

Please use this command now.
RUN apt-get install -y --no-install-recommends libgconf-2-4 gnupg git curl wget ca-certificates libgconf-2-4 && \
    wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
    sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
    apt-get update && \
    apt-get install -y lsb-release google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst --no-install-recommends && \
    wget https://github.com/webnicer/chrome-downloads/raw/master/x64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb && \
    dpkg -i ./google-chrome*.deb && \
    rm google-chrome*.deb

ENV chrome_launchOptions_executablePath google-chrome-stable
ENV chrome_launchOptions_args --no-sandbox,--disable-dev-shm-usage

Thank you very much

Hi @pofider
We're still getting an error due to the dockerfile commands. Any ideas?
Command failed on instance. Return code: 100 Output: (TRUNCATED)...n-zero code: 100 Failed to build Docker image aws_beanstalk/staging-app: 64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb && dpkg -i ./google-chrome*.deb && rm google-chrome*.deb' returned a non-zero code: 100. Check snapshot logs for details. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03build.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
Failed to build Docker image aws_beanstalk/staging-app: 64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb && dpkg -i ./google-chrome*.deb && rm google-chrome*.deb' returned a non-zero code: 100. Check snapshot logs for details.

What base docker image you use?

Hi @pofider
We are using mcr.microsoft.com/dotnet/core/aspnet:3.1
Here is our whole dockerfile if that helps. I tried to get the error message from the logs but unfortunately I was not successful. I also tried to run the docker commands manually to get the error message but I couldn't figure out how.
Also we are using AWS Elastic Beanstalk Linux Docker environment.
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1

RUN apt-get install -y --no-install-recommends libgconf-2-4 gnupg git curl wget ca-certificates libgconf-2-4 && \
    wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
    sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
    apt-get update && \
    apt-get install -y lsb-release google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst --no-install-recommends && \
    wget https://github.com/webnicer/chrome-downloads/raw/master/x64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb && \
    dpkg -i ./google-chrome*.deb && \
    rm google-chrome*.deb

ENV chrome_launchOptions_executablePath google-chrome-stable
ENV chrome_launchOptions_args --no-sandbox,--disable-dev-shm-usage

EXPOSE 80

WORKDIR /tmp

COPY . ./

ENV ASPNETCORE_URLS=http://+:80

ENTRYPOINT ["dotnet", "HouseStayAPI.dll"]

You are missing the RUN apt-get update  at the top.

Thanks! I will add it and give it a try.

All good now! Thank you very much, sir.

Hi @pofider
Unfortunately, we are getting an error due to the jsreport commands in our docker file again. It seems like it is trying to downgrade google-chrome-stable and returning non-zero code.
We are running Docker running on 64bit Amazon Linux/2.15.3 w/ jsreport.Binary.Linux v2.9.0 & jsreport.AspNetCore v2.1.0 & jsreport.Local v2.2.3
We tried with jsreport.Local v2.3 as well and had the same issue.
Logs:
  2020-08-26 21:47:24 (86.0 MB/s) - 'google-chrome-stable_79.0.3945.130-1_amd64.deb' saved [62193324/62193324]

  dpkg: warning: downgrading google-chrome-stable from 85.0.4183.83-1 to 79.0.3945.130-1
  (Reading database ... 21194 files and directories currently installed.)
  Preparing to unpack .../google-chrome-stable_79.0.3945.130-1_amd64.deb ...
  Unpacking google-chrome-stable (79.0.3945.130-1) over (85.0.4183.83-1) ...
  Processing triggers for mime-support (3.62) ...
  dpkg: dependency problems prevent configuration of google-chrome-stable:
   google-chrome-stable depends on libxss1; however:
    Package libxss1 is not installed.

  dpkg: error processing package google-chrome-stable (--install):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   google-chrome-stable
  The command '/bin/sh -c apt-get install -y --no-install-recommends libgconf-2-4 gnupg git curl wget ca-certificates libgconf-2-4 &&     wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - &&     sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' &&     apt-get update &&     apt-get install -y lsb-release google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst --no-install-recommends &&     wget https://github.com/webnicer/chrome-downloads/raw/master/x64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb &&     dpkg -i ./google-chrome*.deb &&     rm google-chrome*.deb' returned a non-zero code: 1
  Failed to build Docker image aws_beanstalk/staging-app: /x64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb &&     dpkg -i ./google-chrome*.deb &&     rm google-chrome*.deb' returned a non-zero code: 1. Check snapshot logs for details. (Executor::NonZeroExitStatus)

Full dockerfile:
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1

RUN apt-get update

RUN apt-get install -y --no-install-recommends libgconf-2-4 gnupg git curl wget ca-certificates libgconf-2-4 && \
    wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
    sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
    apt-get update && \
    apt-get install -y lsb-release google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst --no-install-recommends && \
    wget https://github.com/webnicer/chrome-downloads/raw/master/x64.deb/google-chrome-stable_79.0.3945.130-1_amd64.deb && \
    dpkg -i ./google-chrome*.deb && \
    rm google-chrome*.deb

ENV chrome_launchOptions_executablePath google-chrome-stable
ENV chrome_launchOptions_args --no-sandbox,--disable-dev-shm-usage

EXPOSE 80

WORKDIR /tmp

COPY . ./

ENV ASPNETCORE_URLS=http://+:80

ENTRYPOINT ["dotnet", "HouseStayAPI.dll"]

Please use this in docker now.
# install chrome with deps, see https://github.com/jsreport/jsreport/blob/master/docker/full/Dockerfile
RUN apt-get install -y --no-install-recommends libgconf-2-4 gnupg git curl wget ca-certificates libgconf-2-4 && \
    wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
    sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
    apt-get update && \
    apt-get install -y lsb-release google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst libxtst6 libxss1 --no-install-recommends

Thank you very much, @pofider. We were able to deploy to the web servers successfully.
Unfortunately we are getting an error when trying to render a pdf on the servers now.
I saw --no-sandbox flag was in the old docker commands, should it be added to the new one too?
Failed to launch chrome![0827/220519.358298:WARNING:resource_bundle.cc(426)] locale_file_path.empty() for locale [0827/220519.361423:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md (1). caused by error

[Error] Microsoft.AspNetCore.Server.Kestrel: Connection id "0HM2AP9LLCT4F", Request id "0HM2AP9LLCT4F:00000004": An unhandled exception was thrown by the application. jsreport.Local.JsReportBinaryException: Error rendering report: instance has been daemonized and initialized successfully (pid: 228)rendering has finished with errors:A critical error occurred while trying to execute the render command (2). Failed to launch chrome![0827/220519.358298:WARNING:resource_bundle.cc(426)] locale_file_path.empty() for locale [0827/220519.361423:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md (1). caused by error (2):-> stackError:    at onCriticalError (/snapshot/jsreport/node_modules/jsreport-cli/lib/commands/render.js:302:19)    at /snapshot/jsreport/node_modules/jsreport-cli/lib/commands/render.js:256:14    at processTicksAndRejections (internal/process/task_queues.js:97:5)caused by error (1):-> stackError: Failed to launch chrome![0827/220519.358298:WARNING:resource_bundle.cc(426)] locale_file_path.empty() for locale [0827/220519.361423:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md    at Client.render (/snapshot/jsreport/node_modules/jsreport-client/lib/client.js)    at processTicksAndRejections (internal/process/task_queues.js:97:5)    at async startRender (/snapshot/jsreport/node_modules/jsreport-cli/lib/commands/render.js:319:24)    at async /snapshot/jsreport/node_modules/jsreport-cli/lib/commands/render.js:226:22    at async Commander.executeCommand (/snapshot/jsreport/node_modules/jsreport-cli/lib/commander.js:242:22)Remote stack: Error: Failed to launch chrome![0827/220519.358298:WARNING:resource_bundle.cc(426)] locale_file_path.empty() for locale [0827/220519.361423:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md    at onClose (/snapshot/jsreport/node_modules/puppeteer/lib/Launcher.js:348:14)    at Interface.<anonymous> (/snapshot/jsreport/node_modules/puppeteer/lib/Launcher.js:337:50)    at Interface.emit (events.js:323:22)    at Interface.close (readline.js:409:8)    at Socket.onend (readline.js:187:10)    at Socket.emit (events.js:323:22)    at endReadableNT (_stream_readable.js:1204:12)    at processTicksAndRejections (internal/process/task_queues.js:84:21)
   at jsreport.Local.Internal.LocalUtilityReportingService.RenderAsync(String requestString, CancellationToken ct)
   at jsreport.AspNetCore.JsReportMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

My bad, I removed the commands that set chrome launch path and args. I added them back and it is working again.
ENV chrome_launchOptions_executablePath google-chrome-stable
ENV chrome_launchOptions_args --no-sandbox,--disable-dev-shm-usage

Thank you for your help and for this library, @pofider.


Handle admin duplicates

I realized that after I mad the unpsecified admin fix that Mike suggested, it actually uncovered a small issue due to the synthetic example data in the hapi-schema DB.
The problem occurs when the admin.data dictionary is populated by querying taking all entries from the Admin1 and Admin2 tables. Then when attempting to create the admin 2 is_unspecified entries, those already exist for the synthetic example data, and there is a duplication error.
I tried to solve this in a way that could be useful for the future. That is, now the admin methods keep track of the codes that are inserted, and only use those to populate the data dictionary.
Some tweaks to this approach, or alternatives could be:

still populate the data dictionary with all entries from the table, but pass the added codes to the methods that create the unspecified entries
when constructing unspecified entries, check to make sure they are not duplicates
use a clean table without example data

I think it kind of depends how we're going to adapt the admin module and more broadly the pipeline for adding new data (rather than writing everything from scratch), which I have yet to wrap my head around. Anyway I would appreciate your thoughts Briar and Mike, thanks so much!

Thinking about it more, I probably should just created a make command in hapi-schemas that creates the DBs without the data. But again curious to hear everyone's thoughts.

Actually the empty tables are anyway needed for gender and age range - I'll just close this for now


Save streamed data

Description
This is a PR for a new sample addon that saves streamed data in individual files. It complements save.py in a way and allows to store all data passing through.
Documentation is in the addon.
Checklist

[ ] I have updated tests where applicable.
[X] I have added an entry to the CHANGELOG.

Here you go. I was wondering if I missed some cleanup or error handling. So far I have not noticed that it leaks file handles which would be a lot worse then just a little memory.


Freemoji Reloaded plugins sticker is not working properly

The sticker part of the freemoji plugin is not working, it sends but does not go to the other side

Same. I got;
error : 403 Forbidden
code : 50081
message : Cannot use this sticker
Note: I'm sure I have send link permission.

freemoji does not handle stickers at all.
freemoji COULD do with a rewrite in all honesty but yeah not atm
the cumcord one used to but it was very in depth and replicating it in shelter is kind of impractical sadly, especially animated ones which never worked on cc either.
I don't plan to add sticker support as is, if anyone wants to feel free to PR, if i rewrite it to take advantage of http interception maybe ill consider it but for now, wontfix


how to add another vue package ?

hello .
i want add vue-awesome-swiper on electron-vue but after install ( with npm install vue-awesome-swiper --save ) and add this code on my project , Error Compile print :

D:\electron-apps\nex1-vue2\node_modules\vue-awesome-swiper\src\swiper.vue:1 Uncaught SyntaxError: Unexpected token <

Even the simplest package can not be installed!
Why so complex?

I am facing the same issue, any solutions?
Node: v 8.9.1

My Node js Version is 9.2.0

Are you referring to installing a Vue plug-in?  This is done the same way as a non-electric environment. See the "Using a plug-in" section. https://vuejs.org/v2/guide/plugins.html#Using-a-Plugin
I might have misunderstood your problem so let me know.

It doesn't look like vue-awesome-swiper should be running into this issue anymore. But to answer your original question, you would have needed to white-list this module so that vue-loader would have been able to parse the templates files it once provided.
Docs: https://simulatedgreg.gitbooks.io/electron-vue/content/en/webpack-configurations.html


Revisit Source Maps

[x] Not all of ionic-angular has a source map

[x] Investigate cheaper source map options with original source

[x] Improve docs and show an example

Hi @jgw96
I have the same issue as @savanvadalia . I can see source-map folder for my app on mac but not on windows 7. (I am using "@ionic/app-scripts": "0.0.45"). This is seriously affecting productivity as our Ionic 2 development environment is on Windows 7 Enterprise.
Is there a solution yet to get source-maps working on Windows ?

@rajpat,
Yes, it should work in 0.0.47.
Thanks,
Dan

Have you guys got source maps working, finally?
I just downloaded the latest "ionic2-app-base", with the npm modules installed:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Still no source maps in Safari (running the app in ios Simulator).
What am I missing?
Thanks!

I started a new project yesterday (RC4) and source maps are now working, at
least using Chrome with either Ionic serve or the browser emulator (i.e.
debugging from VS Code) on Windows
My components are exactly the same version as yours....
"@angular/common": "2.2.1",
"@angular/compiler": "2.2.1",
"@angular/compiler-cli": "2.2.1",
"@angular/core": "2.2.1",
"@angular/forms": "2.2.1",
"@angular/http": "2.2.1",
"@angular/platform-browser": "2.2.1",
"@angular/platform-browser-dynamic": "2.2.1",
"@angular/platform-server": "2.2.1",
"@ionic/storage": "1.1.6",
"ionic-angular": "2.0.0-rc.4",
"ionic-native": "2.2.11",
"ionicons": "3.0.0",
"rxjs": "5.0.0-beta.12",
"zone.js": "0.6.26"
},
"devDependencies": {
"@ionic/app-scripts": "0.0.47",
"typescript": "2.0.9"
},
On 19 December 2016 at 03:07, olivermuc<EMAIL_ADDRESS>wrote:

Have you guys got source maps working, finally?
I just downloaded the latest "ionic2-app-base", with the npm modules
installed:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Still no source maps in Safari (running the app in ios Simulator).
What am I missing?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/driftyco/ionic-app-scripts/issues/431#issuecomment-267839537,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKK4Ks10dUy9sT4r7FhN2ROe7ZdEZAZ0ks5rJYRlgaJpZM4K2mBN
.

Apologies, should have been clearer about the issue.
The source map is generated (main.js.map) in the build/ folder, but apparently not loaded / considered by Safari. I also can't judge whether the created map is legit.
I do see statements in the main.js file:
//# sourceMappingURL=index.js.map
I may know enough about how source maps are loaded and correlated but it strikes me that one JS file can have multiple individual source map directives that essentially point to non existent files.

I've tried everything I can think of and everything I've found here to get source maps working in safari with ionic 3. Should this just work out of the box at this point? Debugging on iOS is very frustrating for me a present.


update example (simple_nve.py) and test it in CI

simple_nve.py needs to be updated as it crashes after so many steps.
simple_nve.py (and other examples) should be tested (CI)

@ahashibon

this was closed by PR #31


Does this library supports styled-components?

Looking at the docs, i am really excited to use this library but before using it i want to know if we can use styled-components(https://styled-components.com/) in it or not?

Please ask these kinds of questions in chat rather than opening an issue. https://gitter.im/callemall/material-ui

Have you tried it out? I would be interested in the answer. I would expect some issue with the master branch solved with the next one.

@oliviertassinari I can't see next branch? https://github.com/callemall/material-ui/branches/all

It's the v1-beta branch now.

@oliviertassinari  We still need !important at 1.0.0-beta.7?

@sergeyzwezdin Have a look at https://github.com/styled-components/styled-components/issues/860


Refactor image ownership

Follow-up to https://github.com/real-logic/aeron/pull/631.

https://travis-ci.org/real-logic/aeron/jobs/500250411
Race condition?

Those tests are fairly sensitive to starvation or resources. Just by their very nature.

@tmontgomery Any view on this?

Haven't reviewed it yet. But will try to get time to soon.

Sorry for the delay on this. I think we want to hold off on this. I want to do a more extensive adjustment to the Image handling and this only gets in the way.

I've done an initial pass at what I wanted in 0d484ec . I used some of the techniques in this PR. Any comments you have, @denizevrenci would be most welcome.


Why do we use this block code?

5df9.png">
when we creating snapshot of UIView, why do we check if it is a imageview or not, is it neccassary? I did not understand, and can it make performance slower, I suspect that. Thanks for your effort.

Its so they resize better. A normal snapshot just copies the rendered bitmap into a new UIView and is not a clone of the view. So if an image is upsized/scaled the image resolution can get weird and not look great

Thank you, got it


Fix Documentation - Nomic - Atlas Jupyter Notebook

Correction to Numic-Atlas Jupyter Notebook Docs

Yes, this is the correct fix. I've inserted the buggy link, the MongoDB Atlas but it is the Nomic Atlas.


Searching/linking functionality not working as expected

What I did so far:
Install Neuron on my Amazon Lightsail instance:
OS: Debian 10.5
curl -L https://nixos.org/nix/install | sh
. /home/admin/.nix-profile/etc/profile.d/nix.sh
nix-env -iA cachix -f https://cachix.org/api/v1/install
cachix use srid
nix-env -if https://github.com/srid/neuron/archive/master.tar.gz

Check if it's working:
neuron --version

It's <IP_ADDRESS>.
Build VIM from source
sudo apt update
sudo apt upgrade

Install prerequisites for VIM
sudo apt install libncurses5-dev libgtk2.0-dev libatk1.0-dev libcairo2-dev \
                          libx11-dev libxpm-dev libxt-dev python3-dev lua5.2 git

Remove old VIM and build a new one
sudo apt remove vim-tiny vim-common vim-gui-common vim-nox

cd ~
git clone https://github.com/vim/vim.git
cd vim

./configure --with-features=huge --enable-multibyte --enable-python3interp=yes \
                   --with-python3-config-dir=$(python3-config --configdir) --enable-gui=gtk2 \
                   --enable-cscope --prefix=/usr/local

make VIMRUNTIMEDIR=/usr/local/share/vim/vim82

cd ~/vim
sudo make install

Create symbolic links to VIM
sudo update-alternatives --install /usr/bin/editor editor /usr/local/bin/vim 1
sudo update-alternatives --set editor /usr/local/bin/vim
sudo update-alternatives --install /usr/bin/vi vi /usr/local/bin/vim 1
sudo update-alternatives --set vi /usr/local/bin/vim

To set VIM as default editor, open ~/.bashrc and add
export EDITOR=vim

Install vim-plug
curl -fLo ~/.vim/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim

Open .vimrc
vim ~/.vimrc

Fill .vimrc with:
let g:neuron_dir=expand("~/Documents/zettle/")

call plug#begin()
Plug 'junegunn/fzf', { 'do': { -> fzf#install() } }
Plug 'junegunn/fzf.vim'
Plug 'fiatjaf/neuron.vim'
call plug#end()

Reload and open .vimrc:
source ~/.vimrc
vim ~/.vimrc

In the command mode, run
:PlugInstall
:PlugUpdate

Create my Zettelkasten folder and make a few Zettels
mkdir ~/zettelkasten
cd ~/zettelkasten
touch neuron.dhall
neuron new -e
...
neuron new index -e

Now,
~/zettelkasten/
├ 28176420.md
├ 943814ae.md
├ c95d9e66.md
├ index.md
└ neuron.dhall
The problem is that when I open a zettel, say index.md, I see the following errors:
"index.md" 3L, 31B
Error detected while processing function <SNR>13 refresh_cache_callback_vim:
line	1:
E484: Can't open file /tmp/neuronzettelsbuffer
Error detected while processing function <SNR>13_refresh_cache_callback_vim[3]..<SNR>13_refresh_cache_callback:
line	4:
E909: Cannot index a special variable
line	6:
E121: Undefined variable: l:zettels
E116: Invalid arguments for function sort
line	13:
E121: Undefined variable: l:zettels
line	20:
E121: Undefined variable: l:zettels

Also, when I try to open another zettel by typing gzz, it opens a search window but other zettels are not shown like the drawing below

               +---------------------------------------------------------------------+
               |                                                                     |
               |                                  +-------------------------------+  |
               |                                  |                               |  |
               |                                  |                               |  |
               |                                  |                               |  |
               |                                  |                               |  |
               |                                  |                               |  |
               |      0/0                         |                               |  |
               |                                  |                               |  |
               |   Search Zettel:|                |                               |  |
               |                                  +-------------------------------+  |
               |                                                                     |
               +---------------------------------------------------------------------+

Another issue is that if I create a link from a zettel like [[943814ae.md]], place text cursor on it, and gzo, it says Word under cursor is not a known zettel!
What am I missing something here? Have I skipped an important plugin?

Issue resolved.
I re-read readme.md page, and found out that I didn't install silversearcher-ag. I installed it and rebooted my Lightsail instance. Now everything is working great as it's supposed to. Linking, backlinking, searching, you name it.

Thank you for fixing this bug!
(I'm joking a little but at the same time really thankful.)

Thanks! In fact, the reported problem still happen though not often. The stop-gap measure for me is reboot my instance, and I'm ok with that.


ci: Build for iOS.

FYI @Hywan ... at least we'll test that it builds.

Neat! Thanks, I appreciate!

How hard would it be to run the tests on iOS, instead of just building the binary?

Not sure! I've never done this!


add image gallery in steps

Component infos
Description
A simple image gallery to display multiple image in a step.
Page related
Will be used in how-to post view Page (#420)
Mockup

Build suggestion
Use the images array in the steps array.
Display the thumbnails in a flexbox. Thumbnails have a state active or inactive, which impact the opacity value. The image displayed on full size is the active one.

merged with #509


added mime types

Nice addition! Have you tried testing this exact code via Postman?

@star-nox notice this deployed on Railway (check it out here). Please test that production instance using Postman. The URL you can use in Postman will be https://flask-ai-ta-backend-pr-9.up.railway.app/<your_route>
Thanks!


Allow containers 0.7, as released with GHC 8.6.

After this is merged, a release or revision would be very handy, please.

Seems to be covered by #11 and already revised on Hackage.


Format fixes

A couple of fixes for the collectd config file

oh my thank you I totally zoned out on this sorry!


external-dns doesn't find the service

Hey,
I'm trying to get external-dns work with infoblox provider.
tried the exmple from the tutorial, but external-dns doesn't create records.
this is how my service looks like:
$ kubectl -n ingress describe service nginx-ingress-service
Name:			nginx-ingress-service
Namespace:		ingress
Labels:			k8s-svc=nginx-ingress-service
Annotations:		external-dns.alpha.kubernetes.io/hostname=prod.k8s.vcdcc.example.info
Selector:		pod=nginx-ingress-lb
Type:			LoadBalancer
IP:			<IP_ADDRESS>
Port:			http	80/TCP
NodePort:		http	31742/TCP
Endpoints:		<IP_ADDRESS>:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80 + 2 more...
Port:			https	443/TCP
NodePort:		https	32204/TCP
Endpoints:		<IP_ADDRESS>:443,<IP_ADDRESS>:443,<IP_ADDRESS>:443 + 2 more...
Session Affinity:	None
Events:			<none>

when I run the external-dns with the following flags ( + environment variables ):
$docker run registry.opensource.zalan.do/teapot/external-dns --kubeconfig="/root/config" --source=service --domain-filter=prod.k8s.vcdcc.example.info --provider=infoblox --txt-owner-id=ext-dns-k8s-prod --log-level=debug

I only get the following output, nothing in infoblox.
INFO[0000] config: &{Master: KubeConfig:/root/config Sources:[service] Namespace: AnnotationFilter: FQDNTemplate: Compatibility: PublishInternal:false Provider:infoblox GoogleProject: DomainFilter:[prod.k8s.vcdcc.travian.info] AWSZoneType: AzureConfigFile:/etc/kubernetes/azure.json AzureResourceGroup: CloudflareProxied:false InfobloxGridHost:infoblox.example.info InfobloxWapiPort:443 InfobloxWapiUsername:<user> InfobloxWapiPassword:<pwd> InfobloxWapiVersion:2.3.1 InfobloxSSLVerify:true InMemoryZones:[] Policy:sync Registry:txt TXTOwnerID:ext-dns-k8s-prod TXTPrefix: Interval:1m0s Once:false DryRun:false LogFormat:text MetricsAddress::7979 LogLevel:debug}
INFO[0000] Connected to cluster at https://master01.prod.k8s.vcdcc.example.info:6443
DEBU[0002] No endpoints could be generated from service default/kubernetes
DEBU[0002] No endpoints could be generated from service ingress/default-http-backend
DEBU[0002] No endpoints could be generated from service ingress/nginx-ingress-service
DEBU[0002] No endpoints could be generated from service kube-system/heapster
DEBU[0002] No endpoints could be generated from service kube-system/kube-controller-manager-prometheus-discovery
DEBU[0002] No endpoints could be generated from service kube-system/kube-dns
DEBU[0002] No endpoints could be generated from service kube-system/kube-dns-prometheus-discovery
DEBU[0002] No endpoints could be generated from service kube-system/kube-scheduler-prometheus-discovery
DEBU[0002] No endpoints could be generated from service kube-system/kubelet
DEBU[0002] No endpoints could be generated from service kube-system/kubernetes-dashboard
DEBU[0002] No endpoints could be generated from service kube-system/monitoring-grafana
DEBU[0002] No endpoints could be generated from service kube-system/monitoring-influxdb
DEBU[0002] No endpoints could be generated from service monitoring/alertmanager-main
DEBU[0002] No endpoints could be generated from service monitoring/alertmanager-operated
DEBU[0002] No endpoints could be generated from service monitoring/grafana
DEBU[0002] No endpoints could be generated from service monitoring/kube-state-metrics
DEBU[0002] No endpoints could be generated from service monitoring/node-exporter
DEBU[0002] No endpoints could be generated from service monitoring/prometheus-k8s
DEBU[0002] No endpoints could be generated from service monitoring/prometheus-operated
DEBU[0002] No endpoints could be generated from service monitoring/prometheus-operator

Thanks,
Robert

Can you check what the status field of your LoadBalancer service says? External DNS will only create a record for your LoadBalancer service if the status field is populated (e.g. by Kubernetes creating the ELB).

Not sure what you mean by status field of the Loadbalancer service. maybe this?
$  kubectl -n ingress get service nginx-ingress-service
NAME                    CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
nginx-ingress-service   <IP_ADDRESS>   <pending>     80:31742/TCP,443:32204/TCP   15h

I'm on premise, so I guess this applies only to public cloud providers, right? I'm not really aware of a way to let kubernetes create ELB on premise.

@nrobert13 ok, that's why it's not working: External DNS will just create DNS records to point to the service "External IP / Load Balancer" and in your case it's empty. You can either:

set the Ingress' status field manually
use the external-dns.alpha.kubernetes.io/target annotation as a workaround, see https://github.com/kubernetes-incubator/external-dns/blob/master/docs/faq.md#are-other-ingress-controllers-supported

Example of a properly filled status field (on AWS):
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  creationTimestamp: 2017-01-18T16:03:17Z
  generation: 2
  name: myapp
  namespace: default
  resourceVersion: "41632270"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/myapp
  uid: a003f57b-dd97-1234-8ee7-06af11f8e77b
spec:
  rules:
  - host: myapp.example.org
    http:
      paths:
      - backend:
          serviceName: myapp
          servicePort: 80
status:
  loadBalancer:
    ingress:
    - hostname: aws-1234-lb-123znwf3n9dgs-1728323123.eu-central-1.elb.amazonaws.com

@evaldasou  was saying in this issue that he could get the endpoints in DNS with the ClusterIP service and using the --publish-internal-services. I use the follwoing flags, but still can't get the Endpoints into my Infoblox with the external-dns.
--source=service --publish-internal-services --domain-filter=prod.k8s.vcdcc.example.info --provider=infoblox --txt-owner-id=ext-dns-k8s-prod --log-level=debug

@nrobert13 are you seeing the same log messages as before now that you've set --publish-internal-services?

@khrisrichardson , yes, the same messages. I expected external-dns to create records for the Endpoints in my ingress/nginx-ingress-service service,
$ kubectl -n ingress describe service nginx-ingress-service
Name:			nginx-ingress-service
Namespace:		ingress
Labels:			k8s-svc=nginx-ingress-service
Annotations:		<none>
Selector:		pod=nginx-ingress-lb
Type:			ClusterIP
IP:			None
Port:			http	80/TCP
Endpoints:		<IP_ADDRESS>:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80 + 2 more...
Port:			https	443/TCP
Endpoints:		<IP_ADDRESS>:443,<IP_ADDRESS>:443,<IP_ADDRESS>:443 + 2 more...
Session Affinity:	None
Events:			<none>

but instead still getting the following:
No endpoints could be generated from service ingress/nginx-ingress-service

running external-dns with the following flags:
--source=service --publish-internal-services --domain-filter=prod.k8s.vcdcc.example.info --provider=infoblox --txt-owner-id=ext-dns-k8s-prod --log-level=debug

The reason I asked if it was the same set of messages is because I was wondering if instead your domain filter was too restrictive. Does prod.k8s.vcdcc.example.info refer to an actual (sub)zone in Infoblox? If not you should try editing that string to be the longest string in common with an actual (sub)zone.

Does prod.k8s.vcdcc.example.info refer to an actual (sub)zone in Infoblox?

Yes!

@nrobert13 You last example has no ClusterIP nor Annotations. Can you double-check?

hey, sorry for the delay.
I thought external-dns will use the . for the records.
Anyways, I've got closer with the annotations, but still not as expected.
$ kubectl -n ingress describe service nginx-ingress-service
Name:              nginx-ingress-service
Namespace:         ingress
Labels:            k8s-svc=nginx-ingress-service
Annotations:       external-dns.alpha.kubernetes.io/hostname=prod.k8s.vcdcc.example.info
Selector:          pod=nginx-ingress-lb
Type:              ClusterIP
IP:                None
Port:              http  80/TCP
TargetPort:        80/TCP
Endpoints:         <IP_ADDRESS>:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80 + 2 more...
Port:              https  443/TCP
TargetPort:        443/TCP
Endpoints:         <IP_ADDRESS>:443,<IP_ADDRESS>:443,<IP_ADDRESS>:443 + 2 more...
Session Affinity:  None
Events:            <none>

now external-dns tries to create records, but not sure how. It tries to concat somethin in fron of the annotation I use, but seems to be an empty string. Should the annotation contain only the (sub)domain I want to add the record to, or the fqdn? either way, the output below doesn't look good.
DEBU[0006] Endpoints generated from service: ingress/nginx-ingress-service: [.prod.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS> .prod.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS> .prod.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS> .prod.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS> .prod.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS>]

INFO[0007] Would create A record named '.prod.k8s.vcdcc.example.info' to '<IP_ADDRESS>' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create A record named '.prod.k8s.vcdcc.example.info' to '<IP_ADDRESS>' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create A record named '.prod.k8s.vcdcc.example.info' to '<IP_ADDRESS>' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create A record named '.prod.k8s.vcdcc.example.info' to '<IP_ADDRESS>' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create A record named '.prod.k8s.vcdcc.example.info' to '<IP_ADDRESS>' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create TXT record named '.prod.k8s.vcdcc.example.info' to '"heritage=external-dns,external-dns/owner=ext-dns-k8s-prod"' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create TXT record named '.prod.k8s.vcdcc.example.info' to '"heritage=external-dns,external-dns/owner=ext-dns-k8s-prod"' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create TXT record named '.prod.k8s.vcdcc.example.info' to '"heritage=external-dns,external-dns/owner=ext-dns-k8s-prod"' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create TXT record named '.prod.k8s.vcdcc.example.info' to '"heritage=external-dns,external-dns/owner=ext-dns-k8s-prod"' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.
INFO[0007] Would create TXT record named '.prod.k8s.vcdcc.example.info' to '"heritage=external-dns,external-dns/owner=ext-dns-k8s-prod"' for Infoblox DNS zone 'prod.k8s.vcdcc.example.info'.

I'm trying this with v0.4.8 now but still the same issue.
$ kubectl -n kube-system describe services dashboard-external-dns
Name:              dashboard-external-dns
Namespace:         kube-system
Labels:            k8s-svc=dashboard-external-dns
Annotations:       external-dns.alpha.kubernetes.io/hostname=dashboard.dev.k8s.vcdcc.example.info
Selector:          k8s-app=kubernetes-dashboard
Type:              ClusterIP
IP:                None
Port:              http  8443/TCP
TargetPort:        8443/TCP
Endpoints:         <IP_ADDRESS>:8443
Session Affinity:  None
Events:            <none>

and getting this log:
DEBU[0002] Unable to associate dashboard-external-dns headless service with a Cluster IP
DEBU[0002] Generating matching endpoint .dashboard.dev.k8s.vcdcc.example.info with HostIP <IP_ADDRESS>
DEBU[0002] Endpoints generated from service: kube-system/dashboard-external-dns: [.dashboard.dev.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS>]

INFO[0003] Would create A record named '.dashboard.dev.k8s.vcdcc.example.info' to '<IP_ADDRESS>' for Infoblox DNS zone 'dev.k8s.vcdcc.example.info'.
INFO[0003] Would create TXT record named '.dashboard.dev.k8s.vcdcc.example.info' to '"heritage=external-dns,external-dns/owner=ext-dns-k8s-dev"' for Infoblox DNS zone 'dev.k8s.vcdcc.example.info'.

running with:
registry.opensource.zalan.do/teapot/external-dns:v0.4.8 --kubeconfig="/root/.kube/config" --source=service --publish-internal-services --domain-filter=dev.k8s.vcdcc.example.info --provider=infoblox --txt-owner-id=ext-dns-k8s-dev --no-infoblox-ssl-verify --log-level=debug --dry-run

In infoblox there's a subzone: dev.k8s.vcdcc.example.info
I see 2 problems:

tries to create the records with dash in front
tries to create the records with the IP of the node on which the pod is running instead of the pod ip ( using calico ),  the service resource doesn't have the node ip at all, not sure where's it coming from ...

yeah, that seems broken. Regarding your problems:

This is a bug in your version when the Pod has no spec.hostname set. Use v0.5.0-alpha.1 to mitigate this (In your case it will omit the beginning dot)
This is actually in the code. It takes the Pod's HostIP which seems wrong to me. The Pod IP should be fine and in case of hostNetwork: true should be the node IP. I created an issue: https://github.com/kubernetes-incubator/external-dns/issues/496.

thanks for the quick reply,
indeed,the version indicated fixes the first problem
 Endpoints generated from service: kube-system/dashboard-external-dns: [dashboard.dev.k8s.vcdcc.example.info 0 IN A <IP_ADDRESS>]

I set up a cluster on bare metal machines, but it doesn' work.
External IP still pending, and DNS Record changes nothing... Need help! 😭

I'm seeing the same issue in AWS:
time="2018-10-31T01:40:55Z" level=debug msg="No endpoints could be generated from service namespace/service-name"

Although I have the external-dns.alpha.kubernetes.io/hostname annotation in the service of type: LoadBalancer. I can also see:
status:
  loadBalancer:
    ingress:
    - hostname: ad30xxxxx.eu-west-1.elb.amazonaws.com

in the service status. I'm using the registry.opensource.zalan.do/teapot/external-dns:v0.5.6 image. The DNS for Ingress works fine with this image.

I also noticed that the annotation is missing from the kubectl.kubernetes.io/last-applied-configuration:
apiVersion: v1
kind: Service
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"service-name"},"name":"service-name","namespace":"namespace"},"spec":{"ports":[{"name":"service-name","port":80,"protocol":"TCP","targetPort":5000}],"selector":{"app":"service-name"},"sessionAffinity":"None","type":"LoadBalancer"}}
...

Is this normal?

/remove-lifecycle stale


[Doc] Document management VIP requirements

Is your doc request related to a problem? Please describe or add related issue ID.
Harvester may be deployed into some environments where routing to the Harvester hosts management interfaces is managed via software-defined networking. For example, a bare metal provider might provide their customer with an IP address that can be reassigned to a different host in real time.
In a scenario such as this, kube-vip's gratuitous ARP failovers will be ineffective, as the bare metal provider will still direct traffic to whatever IP address the "floating"/"reserved" IP is set to in their systems.
This can have adverse effects on a cluster. For example, if the bare metal customer purchases another server to join to the cluster, the new node will not be able to join, since it will send packets destined to the VIP, the bare metal provider will route to the OLD host that the VIP was on, and the OLD host will look at the IP address on the packets and say "that's not me" -- and it isn't, because kube-vip removed the IP address from the OLD host's interface, and it is now on a new host.
The customer must manually update the "Reserved IP" through their hosting provider in order to restore functionality when kube-vip fails over.
Describe the solution you'd like

Document these caveats when using a bare metal hosting provider so that Harvester operators are not taken by surprise. Also document how to identify which node the VIP failed over to so that they know what value to plug into their hosting provider's Reserved IP settings.

Note, there is a pre-existing Harvester issue RE: one such provider: https://github.com/harvester/harvester/issues/1181
And it's possible that if Harvester grew support for parameterizing the kube-vip configuration to use BGP that may also resolve the issue for some hosting providers: https://kube-vip.io/docs/modes/bgp/ -- but that is separate from this documentation issue.

cc @starbops too


screenshots in workbench part from the 1.46 release note are too small

Hello,
Just to report that in the latest 1.46 release note, the screenshots in workbench part are too small, which make people difficult to see the 1.46 features from a small screen.

Can you use your browser's context menu to view the image in a separate window/tab, then zoom it? The first image's dimensions are 1823px × 1270px

Yes, I know how to zoom in the images, but it needs extra actions.
All the other images are large enough and very clear except for workbench part.

updated


Error handling

This PR propagates issues occuring in Rust to JS. A new op wrapper is used to be able to catch errors. This wrapper is similar to dispatch_json in the Deno CLI.
Fixes #53
Fixes #26
Fixes #40
Fixes #63
Fixes #65

Nice work!


swift date and time don't displayed

New issue checklist

[x] I have read all of the README, documentation, and FAQ.

[x] I have reviewed the contributing guidelines. Confirmation: ____

[x] I have searched existing issues and this is not a duplicate.
General information
Library version(s):
iOS version(s): 9.3
Devices/Simulators affected: Iphone5
Reproducible in the demo project? (Yes/No): No
Related issues:

Bug information
I use the example of Swift. but the cell that displays the date does not appear
thnx

@trikiano - the swift demo project has been updated


Playing text is obstructed

I would just hide this

Thanks for the feedback. Issue should now be resolved in the latest update:
.tab-secondary-label {    visibility: collapse !important; }


Install tarball plugin from remote URL

The documentation for installing Helm plugins says that plugins may be installed by specifying the URL to a tarball:
You can also install tarball plugins directly from url by issuing helm plugin install https://domain/path/to/plugin.tar.gz

However, this does not seem to be the case:
$ helm --debug plugin install https://gitlab.com/api/v4/projects/59977310/packages/generic/helm-bump/0.0.1/bump.tar.gz
Error: Cannot detect VCS
helm.go:84: [debug] Cannot detect VCS

It would be nice to install plugins from a URL to a tarball but what is the intended behavior? It seems that plugins cannot be installed from tarballs according to #12684.
Helm version: version.BuildInfo{Version:"v3.14.4", GitCommit:"81c902a123462fd4052bc5e9aa9c513c4c8fc142", GitTreeState:"clean", GoVersion:"go1.21.9"}

Given the docs, this seems like a bug to me.
I see in the linked PR it seems to be required to detect the content type + file extension. Once into the details (save that for the PR), we may need to consider this a documentation bug (if there is a limitation, or if it is reasonable behavior to not expect tarfiles to be served as "application/octet-stream"; but that does seem reasonable to me now)