Improve Docs Please

I've been trying for ages to understand your readme's "Getting  Started" and "Basic Usage" sections, but It doesn't say anything about needing to install and use Composer.
I had to google everything on how to setup my LAMP-stack with memcached and get composer installed... I'm still stuck though...
I had to guess all this from googling the "composer require tfranek/webuntis" line...
There's nothing else to go by... Not even a hint....
The docs doesn't say anything on how to include/require this, where the config-array should be placed...
This NEEDS clarification, AND examples.
All my efforts just end up in an  HTTP ERROR 500
Please improve the docs, and please explain like I'm 5, so other noobs like me can use this too :)

I'm sorry, but the goal of the documentation is not to explain the php essentials like composer or installing extensions, there are plenty of good references out there. If you have set up composer correctly, and also have an composer.json the only thing you need to do is to write the console command mentioned in the installation. But if you have any questions or problems, you can DM me on twitter or write me an email<EMAIL_ADDRESS>because this doesn't belong into the github issues.

Sure. I know you'll have to draw the line somewhere regarding the noobproofing, but you could just add single lines for "make sure you have composer installed", "Make sure you have PHP installed and that memcached is installed and working correctly"  etc. this would make it easier for anyone to Google their way to a solution :)
Sendt fra min Samsung Galaxy-smarttelefon.
-------- Opprinnelig melding --------Fra: Tobias Franek<EMAIL_ADDRESS>Dato: 09.06.2017  00:42  (GMT+01:00) Til: TobiasFranek/webuntis<EMAIL_ADDRESS>Ko: pigleet<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Emne: Re: [TobiasFranek/webuntis] Improve Docs Please (#2)
I'm sorry, but the goal of the documentation is not to explain the php essentials like composer or installing extensions, there are plenty of good references out there. If you have set up composer correctly, and also have an composer.json the only thing you need to do is to write the console command mentioned in the installation. But if you have any questions or problems, you can DM me on twitter or write me an email<EMAIL_ADDRESS>because this doesn't belong into the github issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/TobiasFranek/webuntis","title":"TobiasFranek/webuntis","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/TobiasFranek/webuntis"}},"updates":{"snippets":[{"icon":"PERSON","message":"@TobiasFranek in #2: I'm sorry, but the goal of the documentation is not to explain the php essentials like composer or installing extensions, there are plenty of good references out there. If you have set up composer correctly, and also have an composer.json the only thing you need to do is to write the console command mentioned in the installation. But if you have any questions or problems, you can DM me on twitter or write me an email<EMAIL_ADDRESS>because this doesn't belong into the github issues."}],"action":{"name":"View Issue","url":"https://github.com/TobiasFranek/webuntis/issues/2#issuecomment-307247266"}}}

I have added some lines to the README, the Requirements are clearer now (you dont really need memcached) and i added an link plus an sentence to the composer part in the installation. I hope i resolved this issue, if you have any further questions or feature requests for specifically this package, please submit another issue.


feat: add marisa-trie

We have a small local catastrophe in one of custom components. 3.12 upgrade left us without per-compiled wheel for marisa-trie.
https://github.com/DurgNomis-drol/ha_toyota/issues/258
I did fix that with cross-system QEMU build for aarch64, but armv?l is not supported by that.
https://github.com/pytries/marisa-trie/pull/101
https://github.com/pytries/marisa-trie/pull/102
https://github.com/piwheels/piwheels/issues/346
Maybe this is the correct place to provide a wheel for 32-bit Raspberries?

@vermut Reverted, see for context: https://github.com/home-assistant/wheels/pull/712


Plural rules for pasta

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#13515

Thanks!


⚠ ClamAV has degraded performance

In 2161135, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 1c18ac4.


Fix CInferMDir

This fixes a bug in CInferMDir revealed by #260 with some style fixes.
@ucbjrl Can you try this branch?

It passes Jenkins tests (i.e., fixes earlier chisel-testers failure reported with #260)


Failed to extract manifest from APK: ProcessException: The command failed

I have just created one project in VS studio for flutter, and when i try to run the project, i'm getting error.
Error :
Failed to extract manifest from APK: ProcessException: The command failed
Command: D:\SDK_NEW\sdk\build-tools\29.0.3\aapt dump xmltree E:\button_click_demo\build\app\outputs\flutter-apk\app.apk AndroidManifest.xml.
Exception: Problem building Android application: see above error(s).
I have created flutter project from android studio and got same error, can someone please give me solution for this issue, i'm stuck with this error since last 2 days.
Please find the screen shot of error which i'm getting
https://prnt.sc/vuxqk8

Try below :

flutter clean

then do next :

In the android studio 'File->Invalidate Caches/Restart'.
After that run your application.

Tried the same, but still getting same error. @hello-addweb

When i open android module separate, it's working fine. But when i run as flutter project it's giving me this error.
So can you please provide any other solution which can work in my case? @hello-addweb

@MohiniThakkar1995
There's similar open issue describing your case, 50677
Please follow-up there for updates and any questions.
Closing this as duplicate.


Issue with two docker_services and iptables

We have followed the examples of how to run two containers as two different systemd services, but we are having trouble getting the networking to work and I worry that there might be a bug.
# JENKINS: create the on-demand systemd socket for jenkins
docker_service 'jenkins' do
  graph '/var/lib/docker-jenkins'
  host 'unix:///var/run/docker-jenkins.sock'
  action :start
end

# SONAR: create the on-demand systemd socket
docker_service 'sonar' do
  graph '/var/lib/docker-sonar'
  host 'unix:///var/run/docker-sonar.sock'
  action :start
end

# JENKINS: download the jenkins image
docker_image 'jenkins' do
  host 'unix:///var/run/docker-jenkins.sock'
  repo 'REPO/NAMESPACE/jenkins'
  tag node['jenkins_version']
  action :pull
end

# SONAR: download the sonar image
docker_image 'sonar' do
  host 'unix:///var/run/docker-sonar.sock'
  repo 'REPO/NAMESPACE/sonar'
  tag node['sonar_version']
  action :pull
end

# JENKINS: run the jenkins container
docker_container 'jenkins' do
  host 'unix:///var/run/docker-jenkins.sock'
  repo 'REPO/NAMESPACE/jenkins'
  tag node['jenkins_version']
  restart_policy 'always'
  container_name 'jenkins'
  user 'jenkins'
  volumes ['/var/lib/jenkins:/var/jenkins_home']
  port '8443:8443'
  action :run
end

# SONAR: run the sonar container (if not running)
docker_container 'sonar' do
  host 'unix:///var/run/docker-sonar.sock'
  repo 'REPO/NAMESPACE/sonar'
  tag node['sonar_version']
  restart_policy 'always'
  container_name 'sonar'
  port '9443:9443'
  env [
    "SONARQUBE_JDBC_URL=#{node['sonar_jdbc_url']}",
    "SONARQUBE_JDBC_USERNAME=#{node['sonar_jdbc_username']}",
    "SONARQUBE_JDBC_PASSWORD=#{node['sonar_jdbc_password']}",
  ]
  action :run
end

They both come up. And they are both running.
% docker -H unix:///var/run/docker-jenkins.sock ps
CONTAINER ID        IMAGE                                                         COMMAND                  CREATED             STATUS              PORTS                                         NAMES
d24d56b3942d        REPO/NAMESPACE/jenkins:1.642.1-PATCH   "/bin/tini -- /usr/lo"   5 minutes ago       Up 5 minutes        8080/tcp, 50000/tcp, <IP_ADDRESS>:8443->8443/tcp   jenkins

% docker -H unix:///var/run/docker-sonar.sock ps
CONTAINER ID        IMAGE                                             COMMAND             CREATED             STATUS              PORTS                              NAMES
29e9ab136376        REPO/NAMESPACE/sonar:5.3   "./bin/run.sh"      6 minutes ago       Up 6 minutes        9000/tcp, <IP_ADDRESS>:9443->9443/tcp   sonar

But both daemons seem to be using the same IP address:
% docker -H unix:///var/run/docker-sonar.sock inspect sonar | grep -i ipaddr
            "SecondaryIPAddresses": null,
            "IPAddress": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",

% docker -H unix:///var/run/docker-jenkins.sock inspect jenkins | grep -i ipaddr
            "SecondaryIPAddresses": null,
            "IPAddress": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",

And this is messing up the iptables routing.
% iptables -S DOCKER
-N DOCKER
-A DOCKER -d <IP_ADDRESS>/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 8443 -j ACCEPT
-A DOCKER -d <IP_ADDRESS>/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 9443 -j ACCEPT

I can only route to one at a time.  I can stop one. Then the other works (routes). If I bring up the stopped one, I can not get to it (route to it) - until I stop the other one - then it works (routes).
My apologies if this is user error and not an “issue”, but I wanted to bring it up in case this was a bug.

According to the docs there is a small chance of a network collision
https://docs.docker.com/v1.8/articles/networking

When Docker starts, it creates a virtual interface named docker0 on the host machine. It randomly chooses an address and subnet from the private range defined by RFC 1918 that are not in use on the host machine, and assigns it to docker0.

You can set the bip on the docker_service resource to prevent a collision. In the future we may handle this case in the library, but that work around should suffice for now.

The issue appears to be both docker_service resources are using the same docker bridge docker0. At the moment I can't come up with a quick workaround for this issue.
In order to run two instances of docker_service with networking capabilities, we need to manually create custom bridges as assign each one to a docker_service.
https://docs.docker.com/v1.8/articles/networking/#docker0

Can this be done using the ``docker_networkLWRP? I was looking at it, but was unable to get it to work withdocker_container``` the way README indicates.

I haven't worked with docker_network much yet, but from a quick overview it doesn't appear it creates the same kind of bridge as docker0.
root@service-systemd-multi-ubuntu-1504:~# brctl show
bridge name	bridge id		STP enabled	interfaces
br-62a09963414c		8000.024237ea5e17	no
br-afec8f9163b6		8000.0242b1a6891a	no
docker0		8000.0242b8629114	no		vetha775b54
							vethb8d93a9
root@service-systemd-multi-ubuntu-1504:~#

I feel like the reason one would start multiple services - would be to use the services to manage the docker daemon (containers), and do so separately from other services/daemons/containers. So I think this is an important issue to fix (or document if there is a way to was easily do so via the LWRPs).

@michaelajr I went over the docker_network resource. You'll need to create a new network and then link the container to that network. If you want jenkins and sonar separate, then you will create two networks.
Here is an example of a multi-network layout with multiplate containers tied to them. https://github.com/chef-cookbooks/docker/blob/master/test/cookbooks/docker_test/recipes/network.rb
Hope this helps!

@chasebolt Thank you for the help. Will look this over and implement.

Closing but feel free to comment if you need additional assistance.


Pin remark and remark-lint versions

Pin the versions of the remark packages so notifications are sent with new releases, and users can be kept more up to date.

This change is

The CI build status is all green, merging!


Include sets a built in type for a variable

The ability for a list of words or numbers or anything to be randomly chosen for a variable.

Resolved in 1ee57f4


tools: add yoda runtime tools for windows env

Support below batch commands for Windows:

configurate-network
runtime-install
runtime-op
upgrade

Checklist

[x] npm test passes

Restart a Jenkins build on: https://ci.rokid.com/view/Yodaos/job/rokid-ci-yodart-unit-tests/1381/console.


[QUESTION] Latest libSkiaSharp.so

Hello, where can i find the latest libSkiaSharp.so file as its not attached to the github release?

Just want to check why you are looking for the .so directly?
If you are using .NET and just want to use it, it is actually available on nuget:

https://www.nuget.org/packages/SkiaSharp.NativeAssets.Linux
https://www.nuget.org/packages/HarfBuzzSharp.NativeAssets.Linux

There is also one with out the fontconfig dependency:

https://www.nuget.org/packages/SkiaSharp.NativeAssets.Linux.NoDependencies

Ah thanks, i didn't know there was a package for the linux dependencies.

Closing this as you should be able to use the NuGet. Feel free to reopen (or a new one) if there are issues.


How To/How To:  Install a free NPSP org

https://www.salesforce.org/trial/npsp/ or https://developer.salesforce.com/signup and install NPSP from https://install.salesforce.org/products

https://docs.google.com/document/d/1U9ic4Vcr0L0bh2PJ2BnqS8yRYdmqZp_7vtcJxl1VetE


Create help pages for NETSDKxxxx error messages

High-traffic errors (# of F1 queries from VS)

[ ] NETSDK1045
[ ] NETSDK1004
[ ] NETSDK1064
[x] NETSDK1079
[x] NETSDK1071
[x] NETSDK1005
[ ] NETSDK1080
[x] NETSDK1022
[x] NETSDK1073
[x] NETSDK1013
[ ] NETSDK1007
[ ] NETSDK1050
[ ] NETSDK1060
[x] NETSDK1059
[x] NETSDK1047
[ ] NETSDK1046

Error messages created within the last 6 months (no traffic stats yet)

[ ] NETSDK1127
[ ] NETSDK1128
[ ] NETSDK1129
[ ] NETSDK1130
[ ] NETSDK1131
[ ] NETSDK1132
[ ] NETSDK1133
[ ] NETSDK1134
[ ] NETSDK1135
[ ] NETSDK1136
[ ] NETSDK1137
[ ] NETSDK1138
[ ] NETSDK1139
[ ] NETSDK1140
[ ] NETSDK1141
[ ] NETSDK1142
[ ] NETSDK1143
[ ] NETSDK1144
[ ] NETSDK1145
[ ] NETSDK1146
[ ] NETSDK1147

Closing as duplicate of #20656

Closing as duplicate of #20656


Desktop-version

In the pull request, I built a responsive desktop version portfolio using CSS flexbox and grid to style my Html elements.

Hi @joskalenda, please, I have made the changes you can change and review it. thanks

Hi @amejid, please the submission button is showing review pending pleas update the button. thanks

@amejid, @joskalenda, please update the submission button for me. thanks

Hey @david30-maker, I have already made the submission seconds after I did the review, kindly try refreshing the page. 🙂

@amejid, thanks I have submitted it again, please review it for me. thanks

@amejid, @joskalenda please review the code for me please. thanks


[BUG] Change detection broken in v38+

Is there an existing issue for this?

[X] I have searched the existing issues

Does this issue exist in the latest version?

[X] I'm using the latest release

Describe the bug?
When using a v38.0.0 (and all v38+ versions) version of the action, we no longer get any changed files. When using v37 and below, it functions properly.
To Reproduce
Example use that works on 37, but not 38:
      - uses<EMAIL_ADDRESS>        with:
          fetch-depth: 0
      - name: Get changed files
        id: changed-files
        uses: tj-actions/changed-files@v37
        with:
          dir_names: true
          dir_names_max_depth: 1
          json: true
          files: |
            *-service
            xyz
          files_ignore: |
            ignore-me
            test

For example, steps.changed-files.outputs.all_changed_files is > 0 in v37 and always 0 in v38.
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
The action has no breaking changes when upgrading to v38+
Relevant log output
# v37
Run tj-actions/changed-files@v37
  with:
    dir_names: true
    dir_names_max_depth: 1
    json: true
    files: *-service
  xyz

    files_ignore: ignore-me
  test

    separator:
    include_all_old_new_renamed_files: false
    old_new_separator: ,
    old_new_files_separator:
    files_from_source_file_separator:

    files_separator:

    files_yaml_from_source_file_separator:

    files_ignore_yaml_from_source_file_separator:

    files_ignore_separator:

    files_ignore_from_source_file_separator:

    path: .
    quotepath: true
    diff_relative: true
    dir_names_exclude_current_dir: false
    escape_json: true
    fetch_depth: 50
    skip_initial_fetch: false
    since_last_remote_commit: false
    write_output_files: false
    output_dir: .github/outputs
    output_renamed_files_as_deleted_and_added: false
    recover_deleted_files: false
    recover_files_separator:

    recover_files_ignore_separator:

    token: ***
    api_url: https://api.github.com
changed-files
  Using local .git directory
  Running on a pull_request (synchronize) event...
  Retrieving changes between fc9df36f2e933208006714078a8dc5921a74a0b6 (staging) → 5da9b728f458ba58a83c834a22f51b9fd8dee912 (fix-changed-files-logic)
  All Done!
changed-files-patterns
  All Done!

# v38
Run<EMAIL_ADDRESS>  with:
    dir_names: true
    dir_names_max_depth: 1
    json: true
    files: *-service
  xyz

    files_ignore: ignore-me
  test

    separator:
    include_all_old_new_renamed_files: false
    old_new_separator: ,
    old_new_files_separator:
    files_from_source_file_separator:

    files_separator:

    files_yaml_from_source_file_separator:

    files_ignore_yaml_from_source_file_separator:

    files_ignore_separator:

    files_ignore_from_source_file_separator:

    path: .
    quotepath: true
    diff_relative: true
    dir_names_exclude_current_dir: false
    dir_names_include_files_separator:

    escape_json: true
    fetch_depth: 50
    skip_initial_fetch: false
    since_last_remote_commit: false
    write_output_files: false
    output_dir: .github/outputs
    output_renamed_files_as_deleted_and_added: false
    recover_deleted_files: false
    recover_files_separator:

    recover_files_ignore_separator:

    token: ***
    api_url: https://api.github.com
changed-files
  Using local .git directory
  Running on a pull_request (synchronize) event...
  Retrieving changes between fc9df36f2e933208006714078a8dc5921a74a0b6 (staging) → bee1102f9570f2cf06d1b8fb341acf96d7b3491e (fix-changed-files-logic)
  All Done!
changed-files-patterns
  All Done!

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@houserx-jmcc I'll recommend upgrading v38.0.0 to the latest release v38.2.0 to verify that the issue hasn't been resolved.
Let me know if the issue still persists and I'll reopen the issue

NOTE: The full logs need to be included in the bug report. This can be generated by re-running the workflow in debug mode

When using a v38.0.0 (and all v38+ versions)

Yes, the issue has been confirmed on the latest version. I will add debug logs soon.

Perfect that helps. Thanks

Appreciate the quick fix! Great action 🙏🏻

💯Thanks for your support


Initial storage development document.

Updated storage.md to include steps to setup hostPath storage using
the hostpath-provisioner.
Added hostpath-provisioner.yaml to make it easy to setup the hostpath
provisioner.

Signed-off-by: Alexander Wels<EMAIL_ADDRESS>

@davidvossel Used the hostpath provisioner you found in here.

Alright, I figured the fact that I put this in the 'devel' part of the tree, was enough, I will put in some disclaimers noting the fact this is for the development environment only with a single node.

With other words, is the image download part of the PVC provision step or afterwards, when the PVC is bound, and therefore maked as ready to be consumed by pods?

it's a race between the VM trying to bind an empty PVC and CDI attempting to populate the PVC with data.
I'm working with CDI right now to address this using a CRD object to orchestrate the data import. KubeVirt will have tight integration with that CRD object allowing users to specify it as a volume source instead of a PVC. That integration will handle the race gracefully.

@davidvossel What am I missing at this point for this to move forward? So I can address it.


BUGFIX: Adjust DoctrineEventStorage commit retry attempts

Background:
With #288 and #287, the eventstore table will be write-locked for other processes during commit. To reduce the amount of failed write attempts due to DeadlockExceptions from other processes, the retry attempts are increased. The backoff is reduced to 1.2 so that the maximum interval is only about twice as long as before.

Ah, so basically those three are one change? Without #288 no need for #287 and thus not for this one? Then maybe I should combine them into one PR instead?

@kdambekalns probably, yes.
#288 should not be merged without #287, so those should definitely be in a single PR. #289 is technically not necessary for those changes, but makes more sense when combined with those. I guess a single PR makes sense. 👍

The initial numbers were more or less random. And I'm wondering now: Is there any specific reason for the new numbers?
25 attempts seem a bit much at first sight. Also it won't be "about twice as long as before" since every attempt costs time as well (which is not considered in the backoff calculator).
Having written that.. I really don't know. And I assume the former backoff was too short for you and that's why you changed it!?

@bwaidelich yeah, the former backoff was too short. However, the new numbers are also pretty random. We just put those in and they seemed to work so we stuck with them.
I'm actually not even sure if we need that many retries anymore. I guess I'll have to take another look at this. After all, the commit is from early 2020 :)

After all, the commit is from early 2020 :)

Huh? Did we miss it that long or was that in a private fork?

@bwaidelich nah, we were stuck on an older release of the eventsourcing package for quite a while so never got around to update those patches. They were in a public fork: https://github.com/netlogix/Neos.EventSourcing/commits/release/sport/Classes

Ok, now this "depends" on #288 (and #287 has been merged into that.)

I agree that 25 reattempts seems a bit much. Not sure that's really a necessity in the given case, never came across a scenario where a commit would fail so often and then succeed.
Increasing the attempts and reducing the exponent also seems to only flatten the curve, so it's like an optimization for reducing effective latency until the commit succeeds (trying more often and waiting less on each single attempt)?

To reduce the amount of failed write attempts due to DeadlockExceptions from other processes, the retry attempts are increased

Sounds a bit counter-intuitive to me. I would expect more attempts in a tighter loop (together with the table locking) to increase the amount of failed write attempts?


How dose the seed number influence the results?

Thanks for providing Chai-1 which is remarkable.
I have an question regarding the seed number used in the predict_structure.py script (line 44) in the example directory. Why is this number set to 42? How dose  it influence the results? Will increase the number also increase the prediction performance? If yes, how should I choose a proper seed number (for example when prediction antibody-antigen interaction)?
Thanks a lot!

Will increase the number also increase the prediction performance?

Nope. Please start from here and then ask LLMs further questions.
In short - if you are fine with 5 samples, don't change it.


Use host port 0 when setting up PortBindings

Fixes #4395
See also https://github.com/docker/for-mac/issues/5588

@rnorth Have you heard anything from the Docker team on this one? I am seriously worried thwt this may break unexpectedly...

@bsideup not yet.

I'm going to move this back to draft as we still don't have a clear steer on whether this is safer. We're still broken in some local DinD use cases, which is a bad thing, and I'm wondering if there's another way to tackle this (e.g. an opt-in configuration setting that applies this workaround).

I would say, this fix does not make it worse. Instead of increasing our own complexity, I'd opt for implementing it in a straightforward way and be prepared to revert this in the future in case Docker would break compatibility. But I would not design directly for this eventuality.
We had to deal with certain breaking changes in Docker, especially in their desktop distributions, in the past already and it will happen again in the future, but this should not paralyze us or make us overly defensive.

Any update on this? Still failing for me on mac with docker desktop 4.7.1 (77678)
Tried testcontainers 1.16.3 and 1.17.1


[Event Request] codeunit 452 "Report Distribution Management" - OnElseCaseGetDocumentLanguageCode

Can we please get the following event?
procedure GetDocumentLanguageCode(DocumentVariant: Variant): Code[10]
var
    SalesInvoiceHeader: Record "Sales Invoice Header";
    SalesCrMemoHeader: Record "Sales Cr.Memo Header";
    ServiceInvoiceHeader: Record "Service Invoice Header";
    ServiceCrMemoHeader: Record "Service Cr.Memo Header";
    SalesHeader: Record "Sales Header";
    PurchaseHeader: Record "Purchase Header";
    ServiceHeader: Record "Service Header";
    Job: Record Job;
    DocumentRecordRef: RecordRef;
Is
begin
    if DocumentVariant.IsRecord then
        DocumentRecordRef.GetTable(DocumentVariant)
    else
        if DocumentVariant.IsRecordRef then
            DocumentRecordRef := DocumentVariant;

    case DocumentRecordRef.Number of
        .....

        //+NEW
        else
            begin
                IsHandled := false;
                OnElseCaseGetDocumentLanguageCode(DocumentRecordRef, IsHandled, LanguageCode);
                if IsHandled then
                    exit(LanguageCode);
            end;
        //-NEW
    end;
end;

[IntegrationEvent(false, false)]
local procedure OnElseCaseGetDocumentLanguageCode(DocumentRecordRef: RecordRef; var IsHandled: Boolean; var LanguageCode: Code[10])
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Add URL hash capability

This add the capability to handle hashes in the URL and have it be available in the state.

Codecov Report

Merging #177 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #177      +/-   ##
==========================================
- Coverage   99.56%   99.55%   -0.01%
==========================================
  Files          20       20
  Lines         229      227       -2
==========================================
- Hits          228      226       -2
  Misses          1        1

Impacted Files
Coverage Δ

src/reducer.js
100% <ø> (ø)
:arrow_up:

src/util/normalize-href.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Make direct links to docs site

PR looks good. What do you think about appending ↗ for external links?

PR looks good. What do you think about appending ↗ for external links?

I'm of two minds - it should be done in CSS, not explicit markup, but github markdown doesn't directly allow this. Plus it seems to expect a space between the link and the "icon".  In this age of hypertext, I don't think being on an external site is that big a deal anymore.

Good with no icon 👍


Can not save github token

Can not save github token

I think it is caused that your account is in unstable status because of your previous attempt removing your account.
Your account seems to be alive now, even though your file system had been already removed.
If you need a new account, I temporarily open the singning up process. Just tell me.

This issue cannot reproduce. so i close it.


Update Yoga.podspec: fixes archiving for Mac Catalyst

Hi
Summary:
When I tried to archive macos catalyst app in Xcode I got errors:

This PR fixes archiving by linking PrivateHeaders in yoga.framework

Prev PR here https://github.com/facebook/react-native/pull/42159
Changelog:
[IOS] [FIXED] - fixed archiving for Mac Catalyst
Test Plan:
Try archive react-native tester app for macos catalyst in Xcode

Hi @kesha-antonov, thanks for opening the issue.
Setting the Header search paths for Yoga fixes the issue but it is not the right fix. The problem with Catalyst is that it stores the headers in the wrong folder when archiving for Mac Catalyst. The right fix is to set the right folder for the Public haders, similarly to what we did for Fabric.
Could you either:

Try to apply a similar fix to yoga and archive again to verify that it works
or
Create a reproducer using this repo so I can try it myself and provide the right fix, please? 🙏

Hi @kesha-antonov, thanks for opening the issue. Setting the Header search paths for Yoga fixes the issue but it is not the right fix. The problem with Catalyst is that it stores the headers in the wrong folder when archiving for Mac Catalyst. The right fix is to set the right folder for the Public haders, similarly to what we did for Fabric.
Could you either:

Try to apply a similar fix to yoga and archive again to verify that it works
or
Create a reproducer using this repo so I can try it myself and provide the right fix, please? 🙏

Hi,
yeah, I tried what you propose but it doesn't work unfortunately
I'll make reproduction

Hmm
What you proposed work with ReproducerApp https://github.com/kesha-antonov/react-native-mac_catalyst_archiving_issue_05_02_2024
I'll try again with our app

The difference that in repro app Search Paths are correct by default.

@cipolleschi I've made the repro here: https://github.com/kesha-antonov/react-native-mac_catalyst_archiving_issue_05_02_2024

Hi @kesha-antonov, thanks for spending the time on this and sorry for the late reply.
I'm investigating the issue using your reproducer (thank you again for preparing it, it is super helpful).
You are right in saying that the problem is with Private headers rather than public ones.
I'm so confused because building for Release works properly but Archive fails... and AFAIK, the archive command will first build for release and the create the package... so, it is very unclear and weird that one works and the other doesn't... :/

I think I found the actual issue... If we look at the step done for building:

Build for Release
Archive

Basically, Archive does not create a folder for PrivateHeaders and does not symlink it, but I could not find how to specify that not with Xcode and not with Cocoapods.
I think this could be a bug in Xcode or in Cocoapods, to be honest.

As a workaround, while we investigate this issue, I think we can move forward with this fix (I verified too that it works).
I hope we could fix this properly (or that Cocoapods/Apple) will fix it for us

I think I found the actual issue... If we look at the step done for building:
| Build for Release | Archive |
| --- | --- |
|  |  |
Basically, Archive does not create a folder for PrivateHeaders and does not symlink it, but I could not find how to specify that not with Xcode and not with Cocoapods.
I think this could be a bug in Xcode or in Cocoapods, to be honest.

Thanks for the explanation. Didn't look at the logs there
I hope that Apple will fix it if it's Xcode's
issue


Out of memory

Loading, please wait...

    <!-- use rawgithack to retrieve the correct url for nft marker (see 'pinball' below) -->
    <a-nft
        type='nft' url='./aframe/examples/image-tracking/nft/trex/trex-image/trex'
        smooth='true' smoothCount='10' smoothTolerance='0.01' smoothThreshold='5'>
        <a-entity
            gltf-model='./trex/scene.gltf'
            scale="5 5 5"
            position="150 300 -100"
            >
        </a-entity>
    </a-nft>
	<a-entity camera></a-entity>
</a-scene>

Loading, please wait...

	<!-- use rawgithack to retrieve the correct url for nft marker (see 'pinball' below) -->
	<a-nft type='nft' url='./aframe/examples/image-tracking/nft/trex/trex-image/trex' smooth='true' smoothCount='10'
	 smoothTolerance='0.01' smoothThreshold='5'>
		<a-entity gltf-model='./trex/scene.gltf' scale="5 5 5" position="150 300 -100">
		</a-entity>
	</a-nft>
	<a-entity camera></a-entity>
</a-scene>

Hello,
Check that you are serving your NFT marker correctly. It is a bit of a cryptic error message but this happened to me when it couldn't load the marker.

Hi.
I tryed to use your example in README as "Image tracking", but it's not wroking. Loop loading and eat much browser memory.
What should I do now?

mee to

Hi @Sadji0 @gushenjie please note that issues are for reporting bugs, and getting input from people on how they might be able to be resolved. Please use the 'Discussions' for general support (https://github.com/AR-js-org/AR.js/discussions). Thanks!

Fully used the official demo to run, always reporting errors

https://topvision-cv.com/rtc/AR.js/aframe/examples/image-tracking/nft-video/index.html

Hello,
Check that you are serving your NFT marker correctly. It is a bit of a cryptic error message but this happened to me when it couldn't load the marker.

Fully used the official demo to run, always reporting errors

i solve it use nodejs start


Fix panic in AST rewriter when (*SelectStatement).Condition == nil

The AST rewriter tries to assert nil to be an influxql.Expr and thus causes a panic. This patch checks that the field is not nil before running the rewriter.

The appveyor failure does not seem to have to do with my PR:
==2084==ERROR: ThreadSanitizer failed to allocate 0x80000 (524288) bytes of DenseSlabAllocator (error code: 1455)
FATAL: ThreadSanitizer CHECK failed: gotsan.cc:6498 "((0 && "unable to mmap")) != (0)" (0x0, 0x0)
FAIL	github.com/influxdata/influxdb/tsdb/engine/tsm1	122.440s

Squashed.


Avoiding data copy in S3 PutObject flow?

My application layer is already allocating a memory buffers to which it copies/creates data. Optimally, I would like to serialize and send this data to S3 without having to allocate (and copy to) another buffer in the process. Is there an easy way to avoid buffer allocation and data copy in PutObject flow?
As far as I understand it, in order to use PutObject on an already-in-memory data, I need to create an IOStream from some streambuf object. SDK does offers creating a PreallocatedStreamBuf (so one unnecessary copy is saved) but only from an Aws::Utils::Array, which always allocates its own buffer.
Ideally for me, SDK would expose another kind of PreallocatedStreamBuf that takes a pointer of a memory buffer with no additional overhead, or another kind of Array which can be constructed with a preallocated buffer. In any case, buffer ownership should remain at application layer (which also needs to release it later).
One solution can be to change my application layer to allocate its buffers only via AWS SDK Arrays but I don't really like this solution because my application already has its own memory management and also I would have to change too many layers and APIs along the way.
I can probably do the tedious work of deriving another streambuf myself but I was wondering if I was missing something or maybe there are future plans to expose such API?
Help would be appreciated. Thanks!

This issue has been around for some time, see #64.    Several people have said write your own streambuf without pointing to one that works.  (Have you implemented one, crusader-mike, or did you just read that somewhere?)    Best solution I've found is given in #533.
Found that my solution leaks; have narrowed it down to the code in posted in #533, suspect version of SDK I'm using leaks.

Have you implemented one, crusader-mike, or did you just read that somewhere?

from #533:

I had to spend a day or so before I got minimal version right

;)

Have yet to see one that works with the AWS SDK for PUT of a large file to S3.
So, let's see it.

Don't want to deal with HR about making company property public. It isn't hard -- just read related docs carefully.

Complex enough to be considered IP but simple enough that it's not hard.   I'm calling BS.   Your HR department isn't scanning ASK SDK issues web site for proprietary stream buffer implementations.
You could point to any existing StreamBuf implementation online -- there's several that claim to be complete and correct; why should people have to write their own streambuf implementation? -- and show how it's supposed to work with AWS SDK.   Maybe I'm doing something wrong.    As it stands, people are still having trouble getting it working and your comments are not helpful.
Boost version I posted works.   Nothing proprietary about showing code someone else has written with AWS SDK examples.

We could  just add an extra constructor to preallocated stream and array if you would like.

You could point to any existing StreamBuf implementation online -- there's several that claim to be complete and correct

We both know how to use google.... ;-) I had to do some bugfixing in one of these implementations lifted off internet.

Maybe I'm doing something wrong.

@taddygrrr I didn't see any leaks in my program (and we moved terrabytes of data already). So, yeah -- chances are you are doing smth wrong. "Whether it is complex enough to be considered an IP" is another sort of conversation I'd like to avoid to have with HR -- those guys aren't technical and it won't go well for me.
(Side note: In case if you think I am paranoid -- just read your contract carefully. Most people would never sign a typical IT job contract if they weren't under pressure of "having to make a living". At least I wouldn't.)

It's also worth noting that AWS hasn't posted a complete example showing how to do a PUT of a large  buffer to S3.   Instead, they show how to upload a file.  That works well.
Read the comments on the referenced tickets.   @JonathanHenson has suggested a simpler interface on a ticket that's been open since January 3rd, 2016,  #64.    I'm asking for some follow up.

The iostream interface can’t be undone, and I take complete responsibility for that design flaw. But in the very near future, we’ll be providing an interface that will make sure you don’t have to ever touch one again if you don’t want to. Basically we have a stream_buf implementation that will run your simpler interface implementation for you automatically.
Sent from my iPhone

On Mar 24, 2018, at 1:31 PM, Tad Yeager<EMAIL_ADDRESS>wrote:
It's also worth noting that AWS hasn't posted a complete example showing how to do a PUT of a large buffer to S3. Instead, they show how to upload a file. That works well.
Read the comments on the referenced tickets. @JonathanHenson has suggested a simpler interface on a ticket that's been open since January 3rd, 2016, #64. I'm asking for some follow up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I hear you, @JonathanHenson -- I burned on iostreams long long (like 15 years?) ago, can't stand them since then (funny to hear this from a diehard C++ fan, isn't it?). That library is a walking can of fat worms. It is better to avoid it at all costs.  :-)

What I'd like to see is a Aws::AmazonStreamingWebServiceRequest::SetBody(const char *, int64_t).
Take a pointer to my buffer, wrap it however you need without copying the contents, and don't make me jump through hoops.
Thanks.

@JonathanHenson - great, we're looking forward these changes.
Since I opened this ticket, let me just update:
I eventually used Boost's boost::interprocess::bufferstream and initialized it with my own pre-allocated buffer. Works great for me.
As a side note: If you want to avoid 3rd party like Boost, the approach of using std::basic_stringstream as mentioned in the opening comment of #64 (Aws::StringStream), although less neat, can also be OK IMHO, although it's implementation-specific, so this should be checked for the specific std libs.
At a first glance (and as some forums suggested) I thought there might be a problem using stringstream for data (because of NULL terminating chars) but I found that if you set the size of the buffer explicitly (as in the example there) it handles it with no problem for my uses (unlike a simple string itself).
Thanks for all the responses.

@amirkope - Note that I did try StringStream and stream->rdbuf()->pubsetbuf(), but that didn't work, and I wasted time tracing through the VS 2015 implementation to find that pubsetbuf() calls the private setbuf(), which does nothing.
Since I was working on a last-minute requirement that had to be merged that day, there was no time to download and understand the Boost stuff, much less worry about getting permission to use it, so I bit the bullet and accepted the performance overhead of the extra copy, even though it tears me up inside.  :-)

<oops didn't get a mail update for the last comment !? >
@LarryMarg - as I mentioned in my previous comment the StringStream worked for my (Linux) setbuf() implementation, sorry it didn't work for yours :-/
I feel your pain :-) it also bothered me a lot... But I had the chance to first make a relatively quick (though extensive and ugly) solution only for one (the busiest) flow, in which I changed the initial memory allocation of the data and replaced it with a respective allocation of Aws::Utils::Array. This enabled me to later construct an Aws::Utils::Stream::PreallocatedStreamBuf from it and then an Aws::IOStream without the unnecessary data copy.
Handling the busiest flow gave me the peace of mind to continue evaluating the Boost solution and test it more carefully. Eventually I reverted and implemented the Boost solution with minimal changes to my code...
Hope you'll also find peace of mind eventually :-)
Cheers

Hi, I'm not sure there is anything more to add to this thread so I'll be closing it.
If anybody is still having this kind of issue, please open a new one, it'll just be easier to follow up to.


Hub_Role_stack_Name

Describe the bug
Attempting to add a 2nd AWS Account to an existing IAMBIC configuration
Traceback (most recent call last):
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/bin/iambic", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/iambic/main.py", line 475, in setup
    ConfigurationWizard(repo_dir, is_more_options=is_more_options).run()
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/iambic/config/wizard.py", line 1933, in run
    self.configuration_wizard_aws()
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/iambic/config/wizard.py", line 1302, in configuration_wizard_aws
    self.configuration_wizard_aws_accounts()
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/iambic/config/wizard.py", line 1103, in configuration_wizard_aws_accounts
    self.configuration_wizard_aws_account_add()
  File "/Users/michael.woodside/repos/devops-iambic-controls/venv/lib/python3.11/site-packages/iambic/config/wizard.py", line 914, in configuration_wizard_aws_account_add
    create_spoke_role_stack(
TypeError: create_spoke_role_stack() got an unexpected keyword argument 'hub_role_stack_name'

To Reproduce
Steps to reproduce the behavior:
Launch iambic setup, select AWS, then AWS accounts.
next in the wizard select add AWS account, and provide the details of the Identity, Account #, name, region, and finally the Role ARN (Optional).
select proceed then crash
Expected behavior
Spoke role be created for accessing the 2nd account from the primary hub account.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS M2 v13.3
Version -- Latest Release

Also every time the setup fails, it appends the Hub account information to the variables section over and over and over again.

Was able to manually create a SpokeRole and add the account to the configuration as a work around.

Thanks for letting us know, we'll start looking into this ASAP.


Error While Running Demo

Hi @davesnx. Thanks for sharing this work.
I am trying to run the demo unsuccessfully.
I have cloned the demo from this repo and followed the steps from the readme after running it out of the box did not work.
Here is the reproduction: https://github.com/idkjs/styled-ppx-master-demo
I have run yarn global add @davesnx/styled-ppx @ahrefs/bs-emotion and added "ppx-flags": ["@davesnx/styled-ppx/styled-ppx", "@ahrefs/bs-emotion"] to bsconfig.json.
Upon running yarn run re:watch I get the following compiler error which I am not able to resolve:
➜  styled-ppx-master-demo [master]yarn run re:watch
yarn run v1.22.0
warning package.json: No license field
$ bsb -make-world -w
bsb: no work to do.
bsb: no work to do.
bsb: no work to do.
>>>> Start compiling
[1/3] Building src/index.reast
FAILED: src/index.reast
/Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/bs-platform/lib/bsc.exe  -w -30-40+6+7+27+32..39+44+45+101 -color always -bs-jsx 3 -ppx /Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/@davesnx/styled-ppx/styled-ppx -ppx /Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/@ahrefs/bs-emotion  -o src/index.reast -bs-syntax-only -bs-binary-ast /Users/prisc_000/Downloads/styled-ppx-master-demo/src/index.re
sh: /Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/@ahrefs/bs-emotion: is a directory

  We've found a bug for you!
  /Users/prisc_000/Downloads/styled-ppx-master-demo/src/index.re

  Error while running external preprocessor
Command line: /Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/@ahrefs/bs-emotion '/var/folders/dz/xzttny_14gs2lgxcvl5lm5680000gn/T/camlppx947ec0' '/var/folders/dz/xzttny_14gs2lgxcvl5lm5680000gn/T/camlppx74f477'

FAILED: subcommand failed.
>>>> Finish compiling(exit: 1)

Any guidance would be appreciated. Thank you.

If I add yarn add --dev @ahrefs/bs-emotion-ppx per the ahrefs/bs-emotion readme at bs-emotion-ppx and change bsconfig.json's ppx-flag to
  "ppx-flags": ["@davesnx/styled-ppx/styled-ppx", "@ahrefs/bs-emotion-ppx/bin/bs-emotion-ppx"],

I get the following compiler error:
➜  styled-ppx-master-demo [master*]yarn run re:watch
yarn run v1.22.0
warning package.json: No license field
$ bsb -make-world -w
[37/37] Building src/ReactDOMRe.cmj
[5/5] Building src/Css.cmj
[8/8] Building src/Emotion.cmj
>>>> Start compiling
[2/4] Building src/index.reast
FAILED: src/index.reast
/Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/bs-platform/lib/bsc.exe  -w -30-40+6+7+27+32..39+44+45+101 -color always -bs-jsx 3 -ppx /Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/@davesnx/styled-ppx/styled-ppx -ppx /Users/prisc_000/Downloads/styled-ppx-master-demo/node_modules/@ahrefs/bs-emotion-ppx/bin/bs-emotion-ppx  -o src/index.reast -bs-syntax-only -bs-binary-ast /Users/prisc_000/Downloads/styled-ppx-master-demo/src/index.re

  We've found a bug for you!
  /Users/prisc_000/Downloads/styled-ppx-master-demo/src/index.re 12:45

  10 │   font-size: 30px;
  11 │ |}];
  12 │ module Component = [%styled {| margin-left: -10px |}];
  13 │ module Link = [%styled.a {| color: #454545 |}];
  14 │

  Unsupported delimiter

FAILED: subcommand failed.
>>>> Finish compiling(exit: 1)

So it looks like maybe that is going in the right direction but it still isn't compiling. Thanks again

Hey @idkjs,
Thanks for opening the issue, I created a demo that works successfully: https://github.com/davesnx/try-styled-ppx
It's not needed to add bs-emotion-ppx as a ppx here.
I pushed the demo with an unsupported feature, negative numbers: module Component = [%styled {| margin-left: -10px |}];. I already fixed that in master.

Thanks for working demo and note on negative numbers. Will watch the other issue for updates. Peace to you.

Thanks to you, I did a few improvements to the docs!
Let me know in discord, Thanks!

Glad to help!


No changes being saved or green flash when trying to save changes

For some reason any changes I make in the bytecode don't save no matter the file, there is no green flash either

We can't help you without more information


Changes made to sandbox that allows it to work with ContentBundle v0.2.0

will close #64

dublicated issue fix


add yarn serve option in package.json

This PR adds http-server as dev dependency in order to facilitate testing, and add the serve shortcut option to run it.

What is wrong with yarn run start? It even automatically reloads the page when you change the code?
It's a feature of rollup (https://rollupjs.org/)

Oh indeed!
I first tried <IP_ADDRESS>:8082 which doesn't work, but <my hostname>:8082 does.
I don't really understand the black magic under this. 🤔


Unable to load https url via. loadUrl

mainWindow.loadUrl(som https url) fails :(
When i load my dev app at http://localhost:4000 I have no problems -> everything works!
But when i change the url to https://our.production.env.com I get these error:
[5931:1114/161056:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: crt.ssl.com
[5931:1114/161056:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for xxx.xxx.com failed err=-8179
node : v0.12.7
electron: v0.31.0
3.16.0-53-generic #72~14.04.1-Ubuntu, x86_64 x86_64 x86_64 GNU/Linux
My dev team using OSX have the same versions of node and electron - everything works fine here, so I guess it is a linux problem.

Thats because of not following up on incomplete certificate chains on linux, it was fixed sometime back https://github.com/atom/brightray/pull/156 . I suggest upgrading your electron version on linux to v0.34.x.

Ohh.. Thanks a lot :) - now auto updater fails - så I will compile from master branch now - that issue has been fixed here :)


The START payload can only contain one volume

Right now the we can only specify one ceph volume to be attached to an instance at start time, which seems a little restrictive as you can Attach as many volumes as you like at runtime.  It also means that if you boot from volume you cannot attach a second ceph data volume to that instance at creation time.
We should be able to do something like
start:
  ...
  storage:
    -  id: 67d86208-000-4465-9018-fe14087d415f
        boot: true
    -  id: 67d86208-111-4465-9018-fe14087d415f
        boot: false

In order to support the OpenStack block-device-mapping-v2 as per issues #387 and #373 I need this to be a list of StorageResources objects, not just one StorageResources object.

	// Storage contains all the information required to attach or boot
	// from storage for the new instance.
	Storage []StorageResource `yaml:"storage,omitempty"`

Looks fixed!


Files are all 1k

All downloaded files seem to be 1k mp4s.
Retriving: httpsfrontendmasters.comcourseslinting-asts/Code_Transformation_and_Linting_with_Abstract_Syntax_Trees/Introduction
Video URL: http://placehold.it/500x500
...
Downloading: Introduction
Downloading: ./Download/https://frontendmasters.com/courses/linting-asts//0-0Code_Transformation_and_Linting_with_Abstract_Syntax_TreesIntroduction.mp4

-rw-r--r--  1 me  staff   1.1K Jul 14 10:38 0-0Code_Transformation_and_Linting_with_Abstract_Syntax_TreesIntroduction.mp4

Indeed that is a dirty workaround when the crawler failed to get the video element in the page, it just returns a dummy link (http://placehold.it/500x500) to prevent the script from breaking. The image is exactly 1k in size.
I have to close the issue for now and the new script may come soon. Refer issue below, https://github.com/li-xinyang/OS_FrontendMaster-dl/issues/24#issuecomment-315275295


[SchemaRegistry] Update swagger and enable live testing

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests-weekly

/azp run net - schemaregistry - tests
/azp run net - schemaregistry - tests-weekly

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests-weekly

I am still curious if we have confirmation that the service has rolled out to all the public and gov clouds at this point.

@jsquire I have no idea. I was only given the green light to use the test resources template that JS used to do their live testing. So, I grabbed that and modified it. Then, I had to update to the new swagger to access the newer API version appropriately for testing. I don't have service details like that.

/azp run net - schemaregistry - tests

/azp run net - schemaregistry - tests-weekly


Improve coverage on channel and version for dotnet-install scripts

Fixes #2509
cc/ @JohnRusk @WernerMairl
See if this would have been enough to not make the docs a giant pain the neck! lol :grinning: We can mod further if this wouldn't have put the right info in your hands.

Hi @GuardRex  That's certainly a big improvement.  I think, if I was installing today from these new revised instructions, I would still get stuck on two things:

Which values am I allowed to pick, for those things such as branch name or a two-part version number.  I.e. what is the current set of allowable values AND what human-friendly version number do they map to (if the mapping is not direct).  Build numbers are a classic one like that, since I found it impossible to ever figure out how to specify 1.1.1. in the form of a build number.
What are the valid combinations of those values - e.g. for channel and version.

Perhaps the idea way to address the above would be to have a table, listing all the official releases that have been released so far, and the combination of channel and version necessary to install them. First column of the table would be 1.0.0, 1.1.1, 1.1.2 etc.  Any such table may need to be co-ordinated with the resolution of the "version numbering issues" as per https://github.com/dotnet/cli/issues/3773  - i.e. the table I propose would need to make it very clear whether its talking about .NET Core version, tooling version or what ever.

@JohnRusk @WernerMairl Thanks for that excellent feedback. I agree that we need more here.
I spent some time today with the install script (the Windows version from the release/2.0.0 branch) just to see if it does what I think it will do 🤔.
[All links below have the base URL of https://dotnetcli.azureedge.net/dotnet/Sdk/.]
Script: Set the Channel
-Version defaults to latest.

Version
Link

latest
Cannot download: 1.0.4/dotnet-sdk-1.0.4-win-x64.zipDownloading legacy link: 1.0.4/dotnet-dev-win-x<IP_ADDRESS>.zipor it states "1.0.4 is already installed"

coherent
FAIL (with LTS See Note*)

1.0.0
Cannot download: 1.0.0/dotnet-sdk-1.0.0-win-x64.zipDownloading legacy link: 1.0.0/dotnet-dev-win-x<IP_ADDRESS>.zip200 Ok

1.0.1
Cannot download: 1.0.1/dotnet-sdk-1.0.1-win-x64.zipDownloading legacy link: 1.0.1/dotnet-dev-win-x<IP_ADDRESS>.zip200 Ok

1.0.3
Cannot download: 1.0.3/dotnet-sdk-1.0.3-win-x64.zipDownloading legacy link: 1.0.3/dotnet-dev-win-x<IP_ADDRESS>.zip200 Ok

1.0.4
Cannot download: 1.0.4/dotnet-sdk-1.0.4-win-x64.zipDownloading legacy link: 1.0.4/dotnet-dev-win-x<IP_ADDRESS>.zip200 Ok

2.0.0-preview2-006502
2.0.0-preview2-006502/dotnet-sdk-2.0.0-preview2-006502-win-x64.zip

2.0.0-preview3-006607
2.0.0-preview3-006607/dotnet-sdk-2.0.0-preview3-006607-win-x64.zip

2.1.0-preview1-006626
2.1.0-preview1-006626/dotnet-sdk-2.1.0-preview1-006626-win-x64.zip

*Note: A -Version of coherent fails with anything except a -Channel set to a branch:

Channel
Version
Link

release/2.0.0-preview2
coherent
2.0.0-preview2-006502/dotnet-sdk-2.0.0-preview2-006502-win-x64.zip

release/2.0.0
coherent
2.0.0-preview2-006479/dotnet-sdk-2.0.0-preview2-006479-win-x64.zip

Helpful version pages
.NET Core Runtime and SDK download archive
.NET Core Releases
.NET Core SDK (contains .NET Core 1.0 and 1.1)
.NET Core 1.0.5 runtime (LTS) and .NET Core 1.1.2 runtime (Current)
Observations
So the script settings do make sense (thus far 😅) ...

-Channel
Result

Current, LTS, and 1.0
I do expect to get 1.0.4 SDK, which has .NET Core 1.0.5 (i.e, latest of 1.0) and .NET Core 1.1.2 (i.e., latest of 1.1). The 1.0.5 runtime and the 1.1.2 runtimes are in there.

release/2.0.0
I get the preview3 SDK.

release/2.0.0-preview2
I get the preview2 SDK.

master
The wild one! That's 2.1.0-preview1-006626 right now, and that's bleeding edge bits.

What I find a little unsettling about this is that these values of Current and LTS are referring to the SDK in the same place you're setting values of 1.0 and 2.0, which have more direct meaning for your request.
With Current and LTS, you're NOT asking for a "Current SDK" or "LTS SDK" ... To quote the great [@]davidfowl, "That's not a thing. You just made that up!" :grinning:
The terms "Current" and "LTS" don't have any tangible meaning with regard to the SDK ... 1.0.4 SDK has BOTH 1.0.5 (LTS) and 1.1.2 (Current) inside of it. The prior SDK ... 1.0.3 SDK has BOTH 1.0.4 (the prior LTS) and 1.1.1 (the prior Current) inside of it.
The -Version results are ok as well. Although, it looks like some things moved around a bit (i.e., "legacy link" language). Setting an explicit value (e.g., 2.0.0-preview3-006607) brought the specific version right down (when you know of course what to ask for and it exists).
Now, none of that is new or very shocking or anything. The point here is just to get on to your, @JohnRusk, points on (a) what can be provided to each option, and (b) what combos are good/useful; then to your, @WernerMairl, points on the most common use cases and how coherent fits into the picture.
My gut tells me that listing the specific versions (all of them) will get heavy as time goes by. They may utterly depreciate versions, which would be tough to maintain. On the other hand, .NET needs some love with new users. Not showing a clear table (or tables) of values as you suggested could be downright harmful! The suggested use cases should be spelled out clearly for the really obvious downloads that devs will want to configure the script for. I totally agree.
Let me chew on this for a bit. We're definitely moving the right direction to get some very helpful guidance in the doc. Think that over :point_up: ... that :book: BOOK I just wrote 😏 ... and let me know your thoughts.

That's an awesome bit of analysis @GuardRex!
Several points come to mind:

Your list of "cannot download" errors reminds me of my own attempts to find some way, any way, to install my desired version (which was 1.1, at that time). To me, it just felt like fruitless guessing when I was doing that.
What about solving this issue not by making a new list, but instead by including the relevant script command lines in at least one of the existing lists? E.g. add a column, called "script command line" or something, and put into it the script to install each version.  The column could be added to one or more of these tables:

https://github.com/dotnet/core/blob/master/release-notes/download-archive.md
https://www.microsoft.com/net/download/linux  (particularly important here, because the main tables don't mention the scripts, and when you see the bit about scripts at the bottom, you can't relate it back to the particular version that you want)
https://www.microsoft.com/net/download/core#/runtime

This issue is loosely related to https://github.com/dotnet/cli/issues/6345 in which I've argued that its confusing that there are script-based and non-script based ways to install the framework, and they all do different things, and the places that document them tend to either talk only about the scripted ones or only about the non-scripted ones, with very few places mentioning both, and no page ever describing the differences.  The above suggestion about adding a column to an existing table would help.

to install my desired version (which was 1.1, at that time)

... so part of whatever we do with this topic, it should reinforce the point that the .NET Core versions are embedded within the same SDK. The versions are different numbers and representing different things but sure do sound similar making it slightly confusing. This will improve a bit with 2.0 generally, but it won't change what we'll have to figure out here for this topic to clarify.

instead by including the relevant script command lines in at least one of the existing lists

Great idea ... and I took a look at the issue u opened ... excellent. [@]mairaw saw that and this, and she'll help here when we have some kind of decent draft text in place. AFAIK those three pages you cited are owned by the dev team ... not by the docs cats. However, [@]mairaw has :sparkles: magic powers :sparkles:, so something may happen.
For the changes here, I'm approaching this from the standpoint that nothing will change elsewhere and that we can't link to anything that will make the options for -Channel and -Version clear only by virtue of linking. We'll prob end up using some/all of the links that I listed in the Helpful version links section :point_up:, even if they're only listed down in a See also section.

@JohnRusk @WernerMairl Slight delay on working on this one. We have some high priority tasks we need to burn through. I think I'll be back on it ~July 7. Stand-by! ... and have a great weekend! :sunny:

@JohnRusk @WernerMairl ei ei ei ... I was just about to get back into this and one more priority issue hit. Stand-by ... I'll get back to this asap.

@JohnRusk @WernerMairl I did have time to look at this and work on it today. We're dogged here a bit by my desire to not show specific versions of things given how they're packaged. We also have some legal factors affecting the language used here.
I definitely feel that https://www.microsoft.com/net/core/support was left out of the presentation, so I mention their doc on support because it so clearly explains what the dev should expect from the two channels LTS and Current. I added some text and example versions to show possible values that can be provided to -Channel and -Version.
I also tried to address the definition of coherent here by saying that this should be a more stable (tested) combination of packages than what latest has to offer.

Nice!  Your addition of the explanation about "e.g. 1.0.x where x is the patch release" looks like it addresses the specific problem that I originally had.  That should prevent other people from having the same problem.

@guardrex I'm trying this today, to install shared-runtime only version 1.1.2.  I'm right back in the same situation as before, in that nothing works.

@JohnRusk I'm sorry to hear that. By "nothing works," you mean u can't get the install script to install the tooling?
I recently had luck using the defaults and only supplying the version to the rel/2.0.0 branch
... and it :sparkles: JustWorks:tm: :sparkles:!
https://raw.githubusercontent.com/dotnet/cli/release/2.0.0/scripts/obtain/dotnet-install.ps1

dotnet-install.ps1 -Version <CLI_VERSION>

... where CLI_VERSION = 2.0.1-servicing-006924

I specifically need 1.1.2, on Linux, and nothing that I tried would work.
On 24/08/2017 1:18 PM, "Luke Latham"<EMAIL_ADDRESS>wrote:

@JohnRusk https://github.com/johnrusk I'm sorry to hear that. By
"nothing works," you mean u can't get the install script to install the
tooling?
I recently had luck using the defaults and only supplying the version to
the rel/2.0.0 branch
... and it ✨ JustWorks™ ✨!
https://raw.githubusercontent.com/dotnet/cli/release/2.0.0/scripts/obtain/dotnet-install.ps1
dotnet-install.ps1 -Version <CLI_VERSION>
... where CLI_VERSION = 2.0.1-servicing-006924
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/pull/2516#issuecomment-324505378, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYsDvvLv2v7pdsEQsAZmAf9LKAQMtq42ks5sbM9RgaJpZM4OHOZ3
.

Ok, it's all good now (*)
I'm not sure what I was doing wrong before (maybe I was using the 2.0 script to try to install 1.1.2???) In any case, now, this sequence of commands works fine:
1.wget https://dot.net/v1/dotnet-install.sh

chmod 700 dotnet-install.sh
source dotnet-install.sh --shared-runtime --version 1.1.2

(*) Except for this unrelated issue where it was failing on Ubuntu: https://github.com/dotnet/cli/issues/7588


tsscan nit scan for Japan DVB-S/S2 (124E/128E)

Trying to make this work.
First of all problem 1: There's no lnb config for SkyPerfect LNB, which is operated like this
124/128 switch: 124: 40kHz tone 128: no tone. (22kHz is enough from foreign DVB card).
There's no band switch.
LO is 11200MHz.
So ignoring satellite switch stuff for now.
Their NIT is broken, so when --nit-scan retunes, I think it chooses wrong delivery system (S instead of S2)
tsscan -n --debug=10 --japan -f<PHONE_NUMBER>0 -s 23303000 --lnb L11200 --polarity horizontal -m "8-PSK" --delivery-system "DVB-S2" --fec-inner "3/5"
tsscan: Debug[10]: debug level set to 10
tsscan: Debug: ====> tsscan -n --debug=10 --japan -f<PHONE_NUMBER>0 -s 23303000 --lnb L11200 --polarity horizontal -m 8-PSK --delivery-system DVB-S2 --fec-inner 3/5
tsscan: Debug: loading XML file /usr/bin/tsduck.lnbs.xml
tsscan: Debug: loading XML file /usr/bin/tsduck.lnbs.model.xml
tsscan: Debug: starting discarding frontend events
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter0/frontend0
tsscan: Debug: 1 DTVProperties:
tsscan: Debug: [0] cmd = 2 (DTV_CLEAR), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: starting discarding frontend events
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter0/frontend0
tsscan: Debug: 9 DTVProperties:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 6 (0x00000006)
tsscan: Debug: [1] cmd = 3 (DTV_FREQUENCY), data = 1413000 (0x00158F88)
tsscan: Debug: [2] cmd = 4 (DTV_MODULATION), data = 9 (0x00000009)
tsscan: Debug: [3] cmd = 8 (DTV_SYMBOL_RATE), data = 23303000 (0x01639358)
tsscan: Debug: [4] cmd = 9 (DTV_INNER_FEC), data = 10 (0x0000000A)
tsscan: Debug: [5] cmd = 6 (DTV_INVERSION), data = 2 (0x00000002)
tsscan: Debug: [6] cmd = 13 (DTV_ROLLOFF), data = 0 (0x00000000)
tsscan: Debug: [7] cmd = 12 (DTV_PILOT), data = 1 (0x00000001)
tsscan: Debug: [8] cmd = 1 (DTV_TUNE), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: got 10000 packets
tsscan: Debug: got table id 0x00 on PID 0x0000
tsscan: Debug: got 10000 packets
tsscan: Debug: got table id 0x46 on PID 0x0011
tsscan: Debug: got table id 0x46 on PID 0x0011
tsscan: Debug: got table id 0x40 on PID 0x0010
tsscan: Debug: got 10000 packets
tsscan: Debug: got 10000 packets
tsscan: Debug: got table id 0x46 on PID 0x0011
tsscan: Debug: got table id 0x46 on PID 0x0011
tsscan: Debug: got 10000 packets
tsscan: Debug: got 10000 packets
tsscan: Debug: got 10000 packets
tsscan: Debug: got table id 0x42 on PID 0x0011
tsscan: Debug: * tuning to --delivery-system DVB-S --frequency 12,523,000,000 --symbol-rate 23,303,700 --fec-inner auto --polarity horizontal --modulation 8-PSK
tsscan: Debug: starting discarding frontend events
tsscan: Debug: one frontend event discarded
tsscan: Debug: one frontend event discarded
tsscan: Debug: one frontend event discarded
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter0/frontend0
tsscan: Debug: 1 DTVProperties:
tsscan: Debug: [0] cmd = 2 (DTV_CLEAR), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: starting discarding frontend events
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter0/frontend0
tsscan: Debug: 7 DTVProperties:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 5 (0x00000005)
tsscan: Debug: [1] cmd = 3 (DTV_FREQUENCY), data = 1923000 (0x001D57B8)
tsscan: Debug: [2] cmd = 4 (DTV_MODULATION), data = 9 (0x00000009)
tsscan: Debug: [3] cmd = 8 (DTV_SYMBOL_RATE), data = 23303700 (0x01639614)
tsscan: Debug: [4] cmd = 9 (DTV_INNER_FEC), data = 9 (0x00000009)
tsscan: Debug: [5] cmd = 6 (DTV_INVERSION), data = 2 (0x00000002)
tsscan: Debug: [6] cmd = 1 (DTV_TUNE), data =<PHONE_NUMBER> (0xFFFFFFFF)
* Frequency: 12,523,000,000 Hz H, strength: 39%
tsscan: Debug: no input signal lock after 5000 milliseconds
tsscan: Debug: * tuning to --delivery-system DVB-S --frequency 12,568,000,000 --symbol-rate 23,303,700 --fec-inner auto --polarity vertical --modulation 8-PSK
tsscan: Debug: starting discarding frontend events
tsscan: Debug: one frontend event discarded
tsscan: Debug: one frontend event discarded
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter0/frontend0
tsscan: Debug: 1 DTVProperties:
tsscan: Debug: [0] cmd = 2 (DTV_CLEAR), data =<PHONE_NUMBER> (0xFFFFFFFF)
tsscan: Debug: starting discarding frontend events
tsscan: Debug: finished discarding frontend events
tsscan: Debug: tuning on /dev/dvb/adapter0/frontend0
tsscan: Debug: 7 DTVProperties:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 5 (0x00000005)
tsscan: Debug: [1] cmd = 3 (DTV_FREQUENCY), data = 1968000 (0x001E0780)
tsscan: Debug: [2] cmd = 4 (DTV_MODULATION), data = 9 (0x00000009)
tsscan: Debug: [3] cmd = 8 (DTV_SYMBOL_RATE), data = 23303700 (0x01639614)
tsscan: Debug: [4] cmd = 9 (DTV_INNER_FEC), data = 9 (0x00000009)
tsscan: Debug: [5] cmd = 6 (DTV_INVERSION), data = 2 (0x00000002)
tsscan: Debug: [6] cmd = 1 (DTV_TUNE), data =<PHONE_NUMBER> (0xFFFFFFFF)
* Frequency: 12,568,000,000 Hz V, strength: 40%

.. etc

So it will keep failing.
If you tell me how I can capture some sample TS from above tuning line (using tsdump or whatever?) I can provide a sample file with NIT.

I was able to capture some TS with PSI data in it.
test.zip
The problem is in satellite delivery system descriptor in NIT:
When run with --japan, it shows the delivery system as ISDB-S
* NIT Actual, TID 64 (0x40), PID 16 (0x0010)
  Version: 8, sections: 1, total size: 945 bytes
  - Section 0:
    Network Id: 10 (0x000A)
    Network information:
    - Descriptor 0: Network Name (0x40, 64), 8 bytes
      Name: "スカパー!"
    - Descriptor 1: ISDB System Management (0xFE, 254), 2 bytes
      Broadcasting flag: 0 (Broadcasting)
      Broadcasting identifier: 7 (Satellite advanced narrow-band using 27 MHz bandwidth in 12.2 to 12.75 GHz band)
      Additional broadcasting id: 0x01 (1)
    Transport Stream Id: 12308 (0x3014), Original Network Id: 10 (0x000A)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 33376 (0x8260), Type: 0x01 (Digital television service)
      Service id: 33399 (0x8277), Type: 0x01 (Digital television service)
      Service id: 33409 (0x8281), Type: 0x01 (Digital television service)
      Service id: 33415 (0x8287), Type: 0x01 (Digital television service)
      Service id: 33428 (0x8294), Type: 0x01 (Digital television service)
      Service id: 33442 (0x82A2), Type: 0x01 (Digital television service)
      Service id: 33711 (0x83AF), Type: 0x01 (Digital television service)
    - Descriptor 1: Satellite Delivery System (0x43, 67), 11 bytes
      Orbital position: 128.0 degree, east
      Frequency: 12.52300 GHz
      Symbol rate: 23.3037 Msymbol/s
      Polarization: linear - horizontal (0)
      Delivery system: ISDB-S
      Modulation: Advanced narrow-band CS digital broadcasting (10)
      Inner FEC: Advanced narrow-band CS digital broadcasting (10)

When run without, it shows up as DVB-S:
* NIT Actual, TID 64 (0x40), PID 16 (0x0010)
  Version: 8, sections: 1, total size: 945 bytes
  - Section 0:
    Network Id: 10 (0x000A)
    Network information:
    - Descriptor 0: Network Name (0x40, 64), 8 bytes
      Name: "|.....!"
    - Descriptor 1: unknown (0xFE, 254), 2 bytes
      0000:  07 01                                      ..
    Transport Stream Id: 12308 (0x3014), Original Network Id: 10 (0x000A)
    - Descriptor 0: Service List (0x41, 65), 21 bytes
      Service id: 33376 (0x8260), Type: 0x01 (Digital television service)
      Service id: 33399 (0x8277), Type: 0x01 (Digital television service)
      Service id: 33409 (0x8281), Type: 0x01 (Digital television service)
      Service id: 33415 (0x8287), Type: 0x01 (Digital television service)
      Service id: 33428 (0x8294), Type: 0x01 (Digital television service)
      Service id: 33442 (0x82A2), Type: 0x01 (Digital television service)
      Service id: 33711 (0x83AF), Type: 0x01 (Digital television service)
    - Descriptor 1: Satellite Delivery System (0x43, 67), 11 bytes
      Orbital position: 128.0 degree, east
      Frequency: 12.52300 GHz
      Symbol rate: 23.3037 Msymbol/s
      Polarization: linear - horizontal (0)
      Delivery system: DVB-S
      Modulation: 8-PSK (2)
      Inner FEC: unknown (10)

but when tsscan is invoked with --japan, it tries to retune using DVB-S delivery system instead of DVB-S2 (and fails).
It's not "really" ISDB-S in the sense that 124/128 is closer to normal DVB-S2 and using standard 8PSK and not TC8PSK like ISDB-S (BS110) does.
Anyway, I suspect this should be fixed somehow in tsscan by forcing S2 when modulation is 8PSK and --japan is specified.
... Yeah

Hi,
The option --japan is a "synthetic" option, ie. a shortcut for several individual options (including --isdb) which can be useful to process Japanese streams. Please RTFM for more details.
The problem with ISDB is that this is a fundamentally broken standard. Unlike ATSC, it is neither independent nor consistent. It reuses part - but not all - of DVB. Worse, in some cases such as the satellite delivery descriptor, it reuses the same descriptor as DVB with slightly different layouts and semantics. This difference of interpretation of the same structure is the reason for your problem.
When you analyze an ATSC stream, you find ATSC-defined tables and you know for sure that this is an ATSC stream. When analyzing an ISDB stream, it looks like a DVB stream at first. Some specific descriptors may indicate at a later time evidences of ISDB but usually too late. This is why, DVB being the default, you need to specify --isdb  (or some synthetic option which includes it) to tell TSDuck to use ISDB interpretations of ambiguous structures.
I know that some Japanese satellites are not ISDB-S. If you want an accurate interpretation of their signalisation, you need to specify the right set of options, excluding --isdb.

I think you missed the part where the NIT on that satellite is broken, and specifies DVB-S delivery system with 8PSK modulation, which is not a possible combination.
Initial tune with tsscan succeeds, when it goes to next channel following NIT, there's no way to force it to use S2.
tsscan -a 1 -n --debug=10 --default-charset=ARIB-STD-B24 -f<PHONE_NUMBER>0 -s 23303000 --lnb L11200 --polarity horizontal -m "8-PSK" --delivery-system "DVB-S2" --fec-inner "3/5"
1st run:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 6 (0x00000006)
once it discovers NIT:
tsscan: Debug: * tuning to --delivery-system DVB-S --frequency 12,523,000,000 --symbol-rate 23,303,700 --fec-inner auto --polarity horizontal --modulation 8-PSK
result:
tsscan: Debug: [0] cmd = 17 (DTV_DELIVERY_SYSTEM), data = 5 (0x00000005)
^ this is incorrect.

Ok, so you confirm that this is a DVB and not an ISDB network.
If the NIT is broken, ie. inconsistent delivery system and modulation, there is nothing we can do. We cannot do any automatic fix.
You wrote that the delivery system is incorrect because the modulation is 8PSK and that TSDuck should fix the delivery system. But you write this because you know that this should be the right fix in that specific situation. But it could also be possible that the delivery system is actually DVB-S and the modulation is incorrect. After all, DVB-S is always QPSK and a careless operator may not care to set it. So, in practice, there is no absolute reason to decide in favor of fixing the delivery system or fixing the modulation.
The NIT is broken. There are several possible ways to "fix" it. So, you just can't use it to scan the network. Sorry, but the operator is to blame, not TSDuck.

Yep, right.
Network is not isdb but ARIB STD-B10 tho i suppose that doesn't matter at
this point. There's a bunch of isdb-like descriptors and it really WAS
DVB-S at first, then all the channels moved to S2 but i guess they never
updated the NIT for hysterical reasons.
The modulation is actually correct and I can tune all the transponders with
TSReader in S2/8PSK mode.
Which also had the same bug with retune, but after I provided the nit
samples a year or two ago, he also made an exception for this particular
network.
Anyway, the only reason i wanted to scan because I didn't want to manually
map SID -> channel number +av pid for a dvr service app, but i found out
all i needed to provide was the freq/polarization and sid, which was easy
enough to massage from tspsi output.
If you don't think it's worth making an exception/something for this
particular config (like if --Japan and (optional?) orbital == 124 or 128
and modulation = 8psk tune it as s2, then never mind and close this bug.
Since i solved my original requirement for scanning anyway, i don't care if
it's fixed or not, and it's unlikely anyone else will come across this
problem again.
On Wed, Jul 29, 2020, 02:19 Thierry Lelegard<EMAIL_ADDRESS>wrote:

Ok, so you confirm that this is a DVB and not an ISDB network.
If the NIT is broken, ie. inconsistent delivery system and modulation,
there is nothing we can do. We cannot do any automatic fix.
You wrote that the delivery system is incorrect because the modulation
is 8PSK and that TSDuck should fix the delivery system. But you write this
because you know that this should be the right fix in that specific
situation. But it could also be possible that the delivery system is
actually DVB-S and the modulation is incorrect. After all, DVB-S is always
QPSK and a careless operator may not care to set it. So, in practice, there
is no absolute reason to decide in favor of fixing the delivery system or
fixing the modulation.
The NIT is broken. There are several possible ways to "fix" it. So, you
just can't use it to scan the network. Sorry, but the operator is to blame,
not TSDuck.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tsduck/tsduck/issues/622#issuecomment-665166854, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDM5WAHAOFHRKLINQOVC7LR54BZBANCNFSM4PKL3WHA
.

Closing, thanks for feedback.


OpenAI embedding  store Milvus  Error

When I use the embedding api of openai to store the embedding to milvus, there will always be an error. I suspect it is caused by the size of data transfer. However, I have looked at the grpc setting and it should be called Problem.

rpc setting：

But I did not transfer objects that exceeded this limit

Hi @caopengan

I suspect it is caused by the size of data transfer.

Did you try persisting only a single small embedding to test this theory?
Does it happen on adding embedding or on search as well?
Might be a configuration issue.

Hi @caopengan

I suspect it is caused by the size of data transfer.

Did you try persisting only a single small embedding to test this theory?
Does it happen on adding embedding or on search as well? Might be a configuration issue.

Sorry, I have already fixed this issue, because the local debugging uses the proxy server reason, I will close this issue


adding an optional title to notifications, only used if sent

Hey there,
I've just added a very simple check to see if the title has been sent as part of the data object, use it instead of the default appName, this gives a little bit more flexibility to anyone trying to send a notification to Android.
Thanks!
Mo

Hi @tawakol,
Thanks so much for your contribution! 💯
We've merged and published it under version 1.0.41 of the Pushy Cordova SDK.


byte index 19 is not a char boundary; it is inside '»'

Using 0.4
When writing:
[« Blurry Eyes »][blurry_eyes] est assez représentatif de
ce peut faire le bassiste (cliquez sur [le lien][blurry_eyes], elle n’est pas intégrable).

I got this error:
thread 'main' panicked at 'byte index 19 is not a char boundary; it is inside '»' (bytes 18..20) of `[« Blurry Eyes »][blurry_eyes] est assez représentatif de
ce peut faire le bassiste (cliquez sur [le lien][blurry_eyes], elle n’est pas intégrable).

« Pieces », Une jolie balade :

<div class="embed-video"><iframe src="https://www.youtube.com`[...]', src\libcore\str\mod.rs:2102:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

After some try, it seems that using  » inside a [] is causing the error.
Note that the space before » is a non-breakable space.
I've tried:

space»][link_ref] -> working
][link_ref]nbsp» -> working
nbsp"][link_ref] -> working
nbsp»][link_ref] -> broken

Thank you for filing this detailed report!
I will look into this bug immediately.

The bug appeared to be multi-byte spaces inside link labels. We normalize all spaces to regular spaces, but made some error in calculating the right index (and would end up in the middle of another multi-byte character). If it wasn't for », we wouldn't crash but fail to recognize the link.
There's a fix for this, but review capacity seems to be very limited at the moment. I hope we can get it merged soon.
Thanks again for your report :-) These things really help make the project more robust.

Thank you for your analysis!

We normalize all spaces to regular spaces

Only for internal use I presume? The nbsp is still output?

Correct!


Script related: UNCONDITIONAL_CALL and FALL_THROUGH edges seems wrong

Hi,
When using SimpleBlockModel() class, each CALL instruction is also treated as controlflow jump and therefore, we get a new edge with the called function as destination of the edge. But then, we also have a FALL_THROUGH flowtype with the destination as the next instruction. This seems not right as CALL is like a unconditional jump and therefore, there should not be a fall though edge.
Ideally speaking, the next basic block starting from the next instruction after the CALL instruction should have an incoming edge from the called function (more technically, the last basic block containing RET of the called function). So, am I missing something?

The current block models are not single execution flow block models.  The models are meant to be extended for different purposes with other types of models where this flow behavior could be factored in.
In order to have the models work as you would like the blocks in the called function would need to be duplicated since the function could be called by multiple locations.  The return block would then need to be linked back to both call locations.  Unless the models are also changed to duplicate the blocks, just changing the flow links would not be correct.
For a single static flow block model, the flow of the blocks could be traversed and the call/fall-thru collapsed as you wish, or the model could be extended to do the collapsing within the model.

Hi, I understand. As per my need, I could do it by following the call and creating an artificial return edge per call. I also liked the that control-flow has type info (e.g. TERMINATOR), which helped a lot to have a very precise info.


Update to Swift 5

Use Swift 5 syntax for:

NSNotification.Name
UIEdgeInsetsMake
UIViewAnimationOptions
UIKeyboard keys
UIViewAnimationCurve
UIWindowLevelNormal
UIControlState

Implemented in version 2.0.19


Add new technique: OAuth token leakage

Adding a highly used technique when attacking SaaS application that implement OAuth.

This is awesome! Agree on the name, perhaps ""Hijack OAuth flows" to keep it simple, leakage makes it sound passive.

I agree that "Hijack OAuth flows" seems more appropriate for the name! As for the examples, I can add the below disclosed bug bounty reports and maybe add more references from PortSwigger. What do you think?

HackerOne - OAuth redirect_uri bypass using IDN homograph attack resulting in user's access token leakage

HackerOne - Stealing Users OAuth authorization code via redirect_uri
PortSwigger - OAuth 2.0 authentication vulnerabilities
PortSwigger - Hidden OAuth attack vectors


Caching to disk not working

Kingfisher doesn't cache images to disk for me. It seems like there's a problem in KingfisherManager.downloadAndCacheImageWithURL:
line 188: targetCache.storeImage(image, originalData: originalData, forKey: key, toDisk: options?.cacheMemoryOnly ?? true, completionHandler: nil)
here toDisk: options?.cacheMemoryOnly ?? true will return false if options?.cacheMemoryOnly == false. Doesn't seem like expected behaviour from the flag description =)

@bistrform What's your version of Kingfisher? It should be already fixed here https://github.com/onevcat/Kingfisher/pull/224/files

I didn't verify the exact version, just have it as a pod in my project (without specifying the exact version in the podfile). Sorry for bothering in this case, something wrong at my end.


Added helm-docs for generating chart parameters documentation

What kind of change does this PR introduce?
feature/ docs update
What is the current behavior?
Currently, users had to navigate through the values.yaml file to locate Chart parameters.
This PR helps address the issue raised here https://github.com/supabase-community/supabase-kubernetes/issues/3.
What is the new behavior?
With this update, the Chart parameters documentation is now available in README.md.
A helm-docs template (README.md.gotmpl), has been added for generating the README from values.yaml.
Additional context
The comments in values.yaml have been updated to use the helm-docs syntax.
To sync values.yaml with README.md, execute the following command:
helm-docs -t README.md.gotmpl -o README.md -b for-the-badge.

To make changes to the base README, modifications should be made to README.md.gotmpl.
A live example of the updated README is available here

Just bumped chart version to 0.1.3.
Should fix ct-lint action failure.


Fixes #3303

Description (required)
Fixes Nearby Crashes when options menu is clicked #3303
What changes did you make and why?
Initialize bottom-sheet-behavior in onViewCreated
Tests performed (required)
Tested betaDebug on Android 9

Codecov Report

Merging #3304 into 2.12-release will decrease coverage by <.01%.
The diff coverage is 0%.

@@               Coverage Diff               @@
##           2.12-release   #3304      +/-   ##
===============================================
- Coverage          6.52%   6.52%   -0.01%
===============================================
  Files               270     270
  Lines             11641   11643       +2
  Branches            909     909
===============================================
  Hits                760     760
- Misses            10821   10823       +2
  Partials             60      60

Impacted Files
Coverage Δ

...commons/nearby/fragments/NearbyParentFragment.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@neslihanturan True, but I was hoping if that could be done in a separate PR. The initViews() function should have been done in the fragments onViewCreated anyways. What do you think?


Remove redundant "details" element from XML report

It only contained the test name and failure message, both of which are already reported elsewhere in the XML.
Based on discussion in https://github.com/pixielabs/cavy-cli/issues/24#issuecomment-679429883
As I said in that conversation, I'm only testing with TeamCity, so I'd be interested if there are other parsers of these reports where this would be a problem.

On second review of the JUnit schema we were using to structure our XML,  I'm happy to remove the details element as it's not required and, as you say, the information is repeated elsewhere 👌

Included in release v2.2.0 today :)


Add Doughnut-biotool and move eu_cbm_hat

Insert URLs to the project here:
https://github.com/NFrancart/doughnut-biotool

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.

@NFrancart


CB-11987 - Appending the profile and topologies query parameters into the Token Integration URL

The Knox team introduced a very useful usability improvement on the Knox side to display certain elements only in the General Proxy Information section on the Knox Home page  (using pre-defined profile names) as well as we added the ability to filter topologies we display. To be able to do it on the client-side (i.e. without any server-side config), this can be achieved by adding the appropriate query parameter in the homepage's URL: https://host:port/gateway_path/homepage/home?profile=token&topologies=cdp-proxy-token
In this change, I added the missing query parameters into the previously created Token Integration link.

Older versions of Knox will just ignore the query params?

@keyki - yes, they will, so there is no issue in previous versions.
On the other hand: this link is available for <IP_ADDRESS> and above (see minVersion) and limited to ENVs, where OJDBC_TOKEN_DH entitlement is set.

Thanks, @keyki !


[Device Support Request] TS0601 by _TZE204_s139roas Miucda/Avatto temp sensor

Problem description
I bought Miucda/Avatto ZigBee E-ink temperature and humidity sensor. I was able to connect it to ZHA, but it does not show any readings.
Solution description
I would like to be able to read temp, humidity and battery level from this device
Screenshots/Video
Screenshots/Video
![Screenshot 2024-10-07 at 12 05 06](https://github.com/user-attachments/assets/67696a17-bc07-494f-a691-6aa0dc1ed862)

Device signature
Device signature
    "signature": {
      "node_descriptor": {
        "logical_type": 2,
        "complex_descriptor_available": 0,
        "user_descriptor_available": 0,
        "reserved": 0,
        "aps_flags": 0,
        "frequency_band": 8,
        "mac_capability_flags": 128,
        "manufacturer_code": 4417,
        "maximum_buffer_size": 66,
        "maximum_incoming_transfer_size": 66,
        "server_mask": 10752,
        "maximum_outgoing_transfer_size": 66,
        "descriptor_capability_field": 0
      },
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0051",
          "input_clusters": [
            "0x0000",
            "0x0004",
            "0x0005",
            "0xef00"
          ],
          "output_clusters": [
            "0x000a",
            "0x0019"
          ]
        }
      },
      "manufacturer": "_TZE204_s139roas",
      "model": "TS0601"
    },

Diagnostic information
Diagnostic information
[Paste the diagnostic information here]

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
No response

Hi @ArturZurawski , I'm triaging them too. Please test the quirk also #3503

Seems to be working. Thank you.


alarm: fix uncaught error if no scroller (Bangle 1)

This PR seems to fix the following. Tested in the Bangle.js 1 emulator on the Web IDE.
Just tried on emulated Bangle.js 1 and got:
Uncaught Error: Can't read property 'scroll' of undefined
 at line 20 col 1070 in alarm.app.js
...mMenu,10,e,index,undefined,scroller.scroll,group)
                                      ^
in function "onchange" called from line 3 col 106
...onchange)a.onchange(a.value);Bangle.touchHandler==u&&d.draw(...
                              ^
in function "select" called from line 1 col 22
a?d.move(a):d.select()
                     ^
in function "d" called from line 1 col 3
d()
  ^
in function called from system
>

Looking at the git blame it seems to have been around since 2023-11-14.
Originally posted by @thyttan in https://github.com/espruino/BangleApps/issues/3604#issuecomment-2397608781

Thanks! Good spot - yes, we don't use a scroller on Bangle.js1 because we can't scroll just part of the screen


[Admin] Publish

Docs Build status updates of commit f1061a4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/includes/office-js-api-models.md
:white_check_mark:Succeeded
View

docs/outlook/autolaunch.md
:white_check_mark:Succeeded
View

docs/overview/core-concepts-office-add-ins.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fix a bug with delegate/async SSL

Motivation:
This bug could occasionally cause SSL handshakes to time out, because the server-side handshake would fail to resume its event loop.
Modification:
Async delegate SSL tasks now lower their NEED_TASK status after they have executed, but before they run their completion callback.
This is important because the completion callback could be querying the handshake status.
This could cause the task delegator thread and the event look to race.
If the event look queries the handshake status first, it might think that it still needs to delegate another task.
If this happens, the delegator find a null task, and then fail to resume the event loop, causing the handshake to stall.
Result:
This data race no longer causes handshake timeouts.
This is the bug that has been causing me tons of trouble on #11517
Note that existing tests already cover this scenario, just not very likely.

@chrisvest is this a recent regression or something that has existed from the beginning?

@johnou This regressed in 4.1.66 (specifically #11460) and you are only impacted if you use delegate task executors, e.g. with SslContext.newHandler(ByteBufAllocator, String, int, Executor).

@johnou This regressed in 4.1.66 (specifically #11460) and you are only impacted if you use delegate task executors, e.g. with SslContext.newHandler(ByteBufAllocator, String, int, Executor), and you are using OpenSSL or BoringSSL.

Yep, we were one of the first to adopt it. Thanks for the info!


support setting the log level via env var

introduce env var to set the minimally output log level
remove some of the compile-time guards for debug log messages (careful, some LOG_DBG can be expensive, they are always executed)

(internal ref CE-10329)


Import Cue points and such from VirtualDJ Database

Cue Points import works in the latest commits that i may or may not have pushed yet (sry)
Cue Loop Points coming soon


Issues in examples

When we removed LIST DIRECTORY CONTENTS, the examples https://github.com/Lartu/ldpl/blob/ldpl4/examples/fileOrFolder.ldpl and https://github.com/Lartu/ldpl/blob/ldpl4/examples/files.ldpl where broken.

I see these examples where removed, but the rest have been wonderfully fixed by @Saeuissimus, so I'm closing this issue. Thanks again, @Saeuissimus!


Adjust sidebar width

It would be great to have a way to make the sidebar wider or narrower.  Perhaps a preference in the .json file?

I also have some long channel names and opened https://github.com/erroneousboat/slack-term/pull/35 to allow setting the sidebar width in the config file.