text:
Implement dbt snapshot

See https://docs.getdbt.com/docs/building-a-dbt-project/snapshots
Possible reference to implement this feature:
https://github.com/dbt-labs/dbt/tree/develop/plugins/postgres
https://github.com/dbt-labs/dbt-spark/blob/master/dbt/include/spark/macros/materializations/snapshot.sql

@hovaesco it may be a while until that PR gets merged.  I noticed that other features that use the merge statement have been re-written here (i.e. incremental materialization).  Would it be acceptable to take the same approach here?

In order to have atomic merge incremental strategy, we do require MERGE statement support in Trino. My belief is that the only acceptable solution. Do you refer to other incremental strategies?

Do you refer to other incremental strategies?

Hey thanks for taking the time to respond.  Just so I'm on the same page, what do you mean by incremental strategies?
On my end I was referring to how trino overrides this merge statement for incremental models.

https://docs.getdbt.com/docs/building-a-dbt-project/building-models/configuring-incremental-models#about-incremental_strategy

At this moment dbt_trino only supports append incremental models. See https://github.com/starburstdata/dbt-trino/blob/master/dbt/include/trino/macros/materializations/incremental.sql
We have an open PR for adding the delete+insert strategy. However to be able to test it, we need to expand the test setup with iceberg and delta.
I actually concur with @p11o that we could implement this feature using delete+insert but still would suggest getting above two PR's in first.

Now that both merge and delete+insert is merged there are no blocker for this ticked?

@retrry exactly, snapshot will likely land very soon on dbt-trino.

Could you release dbt-trino 1.2.2 with snapshot support?

Sure, we'll release it tomorrow, sorry for the delay.

@retrry here you go https://github.com/starburstdata/dbt-trino/releases/tag/v1.2.2

@hovaesco thanks!

authors: findinpath hovaesco mdesmet p11o retrry


text:
Stardog cannot write on the persistent volume

When using the default configuration, stardog does not have the permission to write ont he persistent volume. This is because the persistent volume is owned by root and stardog doesn't use run with the root user by default.
STARDOG_HOME '/var/opt/stardog/' is not writeable by the current user

A workaround is to run stardog as root:
  securityContext:
    enabled: true
    runAsUser: 0
    runAsGroup: 0
    fsGroup: 0

A better solution would be to use the busybox init container, not only when the cluster is enabled, to change the permissions before stardog starts.

If it helps, this problem was gone the moment we tried "storage type : azurefile" required by AKS for #74

source: gharchive/issue

authors: fungiboletus pcompieta

repo: stardog-union/helm-charts

license_type: permissive

license_source: github-api


text:
Updated some stuff.

refer to the commits for more insights.

Gaming

source: gharchive/pull-request

authors: lambdagg xtrm-en

repo: stardust-enterprises/yanl

license: ISC


text:
feat(icon): export icons for compose

This PR exports the following icons in the Teams theme:

bold
code-snippet
emoji
italic
link
meeting-new
number-list
quote
sticker
table
underline

Also, please take a look into the screener changed, and ensure that only the new icons are added and there is no regression to the previos icons.

@kuzhelov I think it shows as stardust-ui:master because I'm merging from my Fork. I'm not an "official" contributor so I couldn't create a branch within the main fork.

@joheredi, now this omission is fixed :)

Submitting a new PR against master

authors: joheredi kuzhelov mnajdova

repo: stardust-ui/react

license: MIT


text:
Update swagger to mention that page-state param should be URL encoded

When larger page sizes are involved the pageState tends to come back with characters that should be URL encoded like +. Just to be safe, mention in the swagger docs that page-state param should be URL encoded to avoid any potential issues.

No longer needed due to changes introduced in https://github.com/stargate/stargate/pull/1041

repo: stargate/stargate


text:
Issues using the google store plugin

I am trying to use a bucket defined in GCS, but I am having some issues. I am using the shield boshrelease version 7.0.0.
This is the relevant configuration defined in the Shield manifest:
      stores:
        local:
          plugin: fs
          config:
            base_dir: /var/vcap/store/backups
            bsdtar: bsdtar
        db_postgres-gcp:
          plugin: google
          config:
            prefix: "/db/postgres"
            bucket: "pe-backups"
            json_key:
              type: "service_account"
              project_id: "XXXXXXXXXXXX"
              private_key_id: "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
              private_key: |
                  -----BEGIN PRIVATE KEY-----
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                  -----END PRIVATE KEY-----
              client_email: "pe-backups-bucket@XXXXXXXXXXXXXXX.iam.gserviceaccount.com"
              client_id: "11111111111111111111111"
              auth_uri: "https://accounts.google.com/o/oaquth2/auth"
              token_uri: "https://accounts.google.com/o/oauth2/token"
              auth_provider_x509_cert_url: "https://www.googleapis.com/oauth2/v1/certs"
              client_x509_cert_url: "https://www.googleapis.com/robot/v1/metadata/x509/pe-backups-bucket%40XXXXXXXXXXXXXXXX.iam.gserviceaccount.com"

The storage gets defined in Shield, and I can see it defined with all fields using the command line shield -k stores, but then:

The web interface is not able to render the storage section, it does not show errors, it just keeps loading the storages forever (I have tried with Chrome and Firefox). It works when those GCS storages are not defined, so it seems that it is not able to render some of the config fields.
After having defined a job to use the previous storage, it fails with this error:

Validating environment...
=========================
SHIELD_OP ... found
SHIELD_STORE_PLUGIN ... found
SHIELD_STORE_ENDPOINT ... found
SHIELD_TARGET_PLUGIN ... found
SHIELD_TARGET_ENDPOINT ... found
OK

Validating TARGET plugin `postgres`...
======================================
✓ pg_host      127.0.0.1
✓ pg_port      5524
✓ pg_user      shieldadmin
✓ pg_password  admin
TASK FAILED!!  shield worker 2 failed to execute the command against the remote agent 10.230.30.70:5444 (Process exited with: 10. Reason was:  ())
✓ pg_database  shielddb
OK

Validating STORE plugin `google`...
===================================
Error trying parse --endpoint value as JSON: invalid character '\n' in string literal

EXITING 10
WORKER FAILED!!  shield worker 2 failed to parse JSON response from remote agent 10.230.30.70:5444 (EOF)

I am trying to get a backup of the shield database, I think it should be possible, but maybe not ...
Anyway, the only place where the char \n appears is in the private_key field. I have tried defining it as a single line string with \n but I got the same error. I have not had enough time to fully investigate it, maybe I am doing something wrong defining those fields, but it seems to me that both issues (web interface and client trying to use the storage) they have some relation, because it seems in these cases json data has to be parsed.
Thanks!

@jriguera currently you've got json_key as more YAML; but instead try a string of the JSON key.

@drnic I have tried:

Using yaml pipe for multiline text:

        db_postgres-gcp:
          plugin: google
          config:
            prefix: "/db/postgres"
            bucket: "pe-backups"
            json_key: |
                {
                  "type": "service_account",
                  "project_id": "XXXXXXXXXXXXXXXXXX",
                  "private_key_id": "XXXXXXXXXXXXXXXXXXXXXXXXXXX",
                  "private_key": "-----BEGIN PRIVATE KEY-----\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\nXXXXXXXXXXXXXXXXXXXXXXX\n-----END PRIVATE KEY-----\n",
                  "client_email": "pe-backups-bucket@XXXXXXXXXXXXXXXX.iam.gserviceaccount.com",
                  "client_id": "111111111111111111111111",
                  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
                  "token_uri": "https://accounts.google.com/o/oauth2/token",
                  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
                  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/pe-backups-bucket%40XXXXXXXXXXXXXXXXXXXXXX.iam.gserviceaccount.com"
                }

The bosh deployments finished properly (I think it shouldn't), but the storage does not get defined in shield. In the log file post-start.stdout.log appears:
Creating a new store named 'db_postgres-gcp'
{"name":     "db_postgres-gcp",
 "plugin":   "google",
 "endpoint": "{\"prefix\":\"/db/postgres\",\"bucket\":\"pe-backups\",\"json_key\":\"{\n  \\"type\\": \\"service_account\\",\n  \\"project_id\\": \\"XXXXXXXXXXXXXXX\\",\n  \\"private_key_id\\": \\"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\",\n  \\"private_key\\": \\"-----BEGIN PRIVATE KEY-----\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXX==\\n-----END PRIVATE KEY-----\\n\\",\n  \\"client_email\\": \\"pe-backups-bucket@XXXXXXXXXXXXXXX.iam.gserviceaccount.com\\",\n  \\"client_id\\": \\"1111111111111111111111\\",\n  \\"auth_uri\\": \\"https://accounts.google.com/o/oauth2/auth\\",\n  \\"token_uri\\": \\"https://accounts.google.com/o/oauth2/token\\",\n  \\"auth_provider_x509_cert_url\\": \\"https://www.googleapis.com/oauth2/v1/certs\\",\n  \\"client_x509_cert_url\\": \\"https://www.googleapis.com/robot/v1/metadata/x509/pe-backups-bucket%40XXXXXXXXXXXXXXX.iam.gserviceaccount.com\\"\n}\n\"}"}
{"error":"Error 400 Bad Request"}

Ofc, I changed the keys, but I kept the \\n, so it seems all especial chars are escaped.

Using jq with  cat PE-TE-DE-b2e7b24eac28.json  | jq '. | @json' The json file has a json credentials from GCP.  The output is a text with escaped json.

        db_postgres-gcp:
          plugin: google
          config:
            prefix: "/db/postgres"
            bucket: "pe-backups"
            json_key: "{\"type\":\"service_account\",\"project_id\":\"XXXXXXXXXXXXXXX\",\"private_key_id\":\"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\",\"private_key\":\"-----BEGIN PRIVATE KEY-----\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXX==\\n-----END PRIVATE KEY-----\\n\",\"client_email\":\"pe-backups-bucket@XXXXXXXXXXXXXXX.iam.gserviceaccount.com\",\"client_id\":\"111111111111111111111111111\",\"auth_uri\":\"https://accounts.google.com/o/oauth2/auth\",\"token_uri\":\"https://accounts.google.com/o/oauth2/token\",\"auth_provider_x509_cert_url\":\"https://www.googleapis.com/oauth2/v1/certs\",\"client_x509_cert_url\":\"https://www.googleapis.com/robot/v1/metadata/x509/pe-backups-bucket%40XXXXXXXXXXXXXXX.iam.gserviceaccount.com\"}"

And also it does not get defined, in the log file post-start.stdout.log I see:
Creating a new store named 'db_postgres-gcp'
{"name":     "db_postgres-gcp",
 "plugin":   "google",
 "endpoint": "{\"prefix\":\"/db/postgres\",\"bucket\":\"pe-backups\",\"json_key\":\"{\\"type\\":\\"service_account\\",\\"project_id\\":\\"XXXXXXXXXXXXXXX\\",\\"private_key_id\\":\\"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\",\\"private_key\\":\\"-----BEGIN PRIVATE KEY-----\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\\nXXXXXXXXXXXXXXXXXXXXXXXXXXQ==\\n-----END PRIVATE KEY-----\\n\\",\\"client_email\\":\\"pe-backups-bucket@XXXXXXXXXXXXXXX.iam.gserviceaccount.com\\",\\"client_id\\":\\"111111111111111111111111\\",\\"auth_uri\\":\\"https://accounts.google.com/o/oauth2/auth\\",\\"token_uri\\":\\"https://accounts.google.com/o/oauth2/token\\",\\"auth_provider_x509_cert_url\\":\\"https://www.googleapis.com/oauth2/v1/certs\\",\\"client_x509_cert_url\\":\\"https://www.googleapis.com/robot/v1/metadata/x509/pe-backups-bucket%40XXXXXXXXXXXXXXX.iam.gserviceaccount.com\\"}\"}"}
{"uuid":"b8ce564c-450f-451b-9b49-f8892ec4c98a","name":"local","summary":"","plugin":"fs","endpoint":"{\"base_dir\":\"/var/vcap/store/backups\",\"bsdtar\":\"bsdtar\"}"}
{"error":"Error 400 Bad Request"}

Note that one new line appears (just the one for the local storage).
Any ideas?

Do the SHIELD logs from around the time that the post-start fires shed any light on why SHIELD issued the HTTP 400 response?

authors: drnic jhunt jriguera

repo: starkandwayne/shield

license: mit

license_source: bigquery


text:
Test old branch

Type
Enhancement, Bug fix

Description

Added a new test file Security3030Test.java for testing security-related functionality.
Made enhancements and bug fixes in DirectoryBrowserSupport.java, including the addition of a new static boolean ALLOW_TMP_DISPLAY and a corresponding pattern TMPDIR_PATTERN, a new method hasTmpDir to check if a file is a temporary directory, and updates to several methods to use getOpenOptions instead of getNoFollowLinks.
Updated serveFile method in DirectoryBrowserSupport.java to check if a file is a temporary directory and send an error response if it is.

Changes walkthrough
Relevant filesTests

Security3030Test.javaAddition of new security tests

test/src/test/java/jenkins/security/Security3030Test.java

A new test file Security3030Test.java was added. This file contains   tests for security-related functionality.

+330/-0

Enhancement

DirectoryBrowserSupport.javaEnhancements and bug fixes in DirectoryBrowserSupport

core/src/main/java/hudson/model/DirectoryBrowserSupport.java

Added new static boolean ALLOW_TMP_DISPLAY and a corresponding   pattern TMPDIR_PATTERN. - Added a new method hasTmpDir to check if a file is a temporary   directory. - Updated several methods to use getOpenOptions instead of  getNoFollowLinks. - Updated serveFile method to check if a file is a temporary directory   and send an error response if it is.

+37/-12

 ✨ Usage guide:
Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:
/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:
[pr_description]
some_config1=...
some_config2=...

  Enabling\disabling automation

When you first install the app, the default mode for the describe tool is:

pr_commands = ["/describe --pr_description.add_original_user_description=true"
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:

pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

type: the PR type.
summary: the PR summary.
walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

  Custom labels
The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].
If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

Main topic:performance - pr_agent:The main topic of this PR is performance
New endpoint - pr_agent:A new endpoint was added in this PR
SQL query - pr_agent:A new SQL query was added in this PR
Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

  Inline File Walkthrough 💎
For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page.
This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are:

'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.
true: A collapsable file comment with changes title and a changes summary for each file in the PR.
false (default): File changes walkthrough will be added only to the "Conversation" tab.

  Utilizing extra instructions
The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
[pr_description]
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

/review

/describe

/analyze

repo: starkhorn/jenkins


text:
Migrated compiler to per-crate plugin queries

Stack:

#6843 ⬅
#6842
#6841
#6840
#6839
#6838

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

repo: starkware-libs/cairo


text:
wip

Stack:

#2256 ⬅
#2255
#2254

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

repo: starkware-libs/sequencer


text:
chore: change sequencer_node_handle type to Vec to support multiple handles

Stack:

#2572 ⬅
#2571
#2555
#2554
#2553

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

authors: nadin-Starkware reviewable-StarkWare


text:
feat(toasts): add link to transfer log

Add on each transfer-toast a link to the Account menu with the transfer-log expanded.

[x] Changes have been done against master branch, and PR does not conflict
[x] New unit / functional tests have been added (whenever applicable)
[x] Test are passing in local environment
[ ] Docs have been updated

This change is

Add on each transfer-toast a link to the Account menu with the transfer-log expanded.

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated

:tada: This PR is included in version 1.0.0-dev.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: CarmitKl dan-ziv

repo: starkware-libs/starkgate-frontend


text:
Move Case_Type to columns

We should have columns like Confirmed , Confirmed_Since_Previous_day, Recovered and Recovered_Since_Previous_day for each entry. It will allow aggregating the data without using the Case_Type as filter or slicer, reducing the confusion.

@chrisvoncsefalvay do you agree?

we should move this to a separate table

@tfoldi this will be a breaking change for existing tableau vizes. I realize a lot of other folks are also using the data. Would be great to notify the tableau users of this change. I am trying to gather these changes here: https://community.tableau.com/thread/334105. Could we update the thread with any breaking changes? or tag me and I can help.

I plan to do it in separate table / flow, without impacting we have today.

Because this would break too many things at once, we are not currently doing this. Thanks for everyone's comments and contributions.

authors: chrisvoncsefalvay nkamkolkar tfoldi


text:
At first it works, but then...

Help me pls, at first launch that all works good, but then i disabled option for rdp in "My computer" and now i cant connect to terminal...why?
That's some screen's, all settings is good, but i can't connect to terminal across static IP.

One more thing...across  RDPCheck.exe - connecting successfully, but not from client terminal

i disabled option for rdp in "My computer" and now i cant connect to terminal...why?

Because.

Because.

No-no, then i turned it ON again
Я потом включил обратно, забыл это указать

Try to reinstall it.

Try to reinstall it.

У тебя есть вк\телега? Можешь дать контакт?
Я пробовал переустанавливать, не помогло.

Make sure you reinstalled it correctly (run uninstall.bat and then install.bat).

Make sure you reinstalled it correctly (run uninstall.bat and then install.bat).

Yes, it was correctly, 100%

One more thing...across RDPCheck.exe - connecting successfully, but not from client terminal

Then you have a problem in port mapping / firewall - software one or hardware - router/switch.

Then you have a problem in port mapping / firewall - software one or hardware - router/switch.

Port working correctly, i checked it

If RDPCheck works without issues, there is some networking problem at your side. Either you're entering wrong IP into the client, or something else.
I cannot help you in this question.

Either you're entering wrong IP into the client, or something else.
I'm entering same IP like at first time, when all worked fine.

Since RDPCheck works, this is actually not RDP Wrapper issue, and should not be discussed here.

authors: Olegtopchiy binarymaster

repo: stascorp/rdpwrap


text:
sbt-slicer reports wrong gitversion

sdg-slicer reports wrong gitversion (which actually is the one of dg) and, therefore, symbiotic refuses to start.
$ symbiotic arbitrary.c
7.0.0-dev-llvm-11.0.0-symbiotic:f45c4f36-dg:ccbc3536-sbt-slicer:85c8cb48-sbt-instrumentation:62c48199-klee:18c7586d
ERROR: The version of 'sbt-slicer' is different than expected (expect b'85c8cb48' but got b'ccbc3536')
If you are aware of this, you may use --no-integrity-check to suppress this error
$ symbiotic  --version
version: 7.0.0-dev
LLVM version: 11.0.0
symbiotic            -> f45c4f3636652c0ba7aef8858ab0e794d62e0e26 (Release)
dg                   -> ccbc3536de659896c4ecac7f4b619733b14b5b9a (Release)
sbt-slicer           -> 85c8cb482fecdd065329a55551bae93af2408c7b (Release)
sbt-instrumentation  -> 62c481990db07679f3e3e0e086d5c27a6d28f757 (Release)
klee                 -> 18c7586df9317383b3268a76bec5874883f6182d (Release)
$ llvm-11.0.0/bin/sbt-slicer --version
ccbc3536
$ llvm-11.0.0/bin/llvm-slicer --version
ccbc3536

Yup, the problem is that it takes the version from libdgllvmslicer.so because it uses its cmd parsing capabilities.

Yup, the problem is that it takes the version from libdgllvmslicer.so because it uses its cmd parsing capabilities.

authors: lzaoral mchalupa

repo: staticafi/symbiotic


text:
Comment by Mike on toc

avatar:
Score: 0.00
I hate this stinking thing

just a test of sentiment score


text:
Make owner optional during cw_ownable initialization.

matches the semantics of the package where owner is optional. without this change, instantiating a contract with an optional owner and this package isn't easily done as my previous change made OWNERSHIP a private state variable.

@larry0x if you wouldn't mind taking a look at this once you have a chance. sorry for all the small changes. integrating this with DAO DAO's staking contracts

repo: steak-enjoyers/cw-plus-plus


text:
Call to a member function getDefault() on bool

/var/www/html/projectname/vendor/o2system/spl/src/Exceptions/Abstracts/AbstractException.php
     */
    public function __construct($message, $code = 0, array $context = [], \Exception $previous = null)
    {
        if (class_exists('O2System\Kernel', false)) {
            $classInfo = new SplClassInfo($this);
            $classNameParts = explode('\\', $classInfo->getClass());
            $classParameter = strtolower(end($classNameParts));
            $classLanguageDirectory = dirname($classInfo->getFileInfo()->getRealPath()) . DIRECTORY_SEPARATOR . 'Languages' . DIRECTORY_SEPARATOR;

            if (false !== ($exceptionKey = array_search('Exception', $classNameParts)) OR
                false !== ($exceptionKey = array_search('Exceptions', $classNameParts))
            ) {
                if (isset($classNameParts[ $exceptionKey - 1 ])) {
                    $classParameter = $classNameParts[ $exceptionKey - 1 ];

                }
            }

            $this->view = strtolower($classParameter . '_' . $this->view);
            $languageFilename = strtolower($classParameter) . '_' . language()->getDefault() . '.ini';
            $languageKey = strtoupper($classParameter . '_exception');
            language()->loadFile($classLanguageDirectory . $languageFilename);

            $this->header = language()->getLine('E_HEADER_' . $languageKey);
            $this->description = language()->getLine('E_DESCRIPTION_' . $languageKey);
            $message = language()->getLine($message, $context);
        }

        parent::__construct($message, $code, $previous);
    }

    // ------------------------------------------------------------------------

    /**
     * AbstractException::getHeader
     *
     * Gets exception header.
     *
     * @return string
     */
Arguments
"Call to a member function getDefault() on bool"

Ada yang bisa bantu masalah di atas ?
Saya menggunakan laravel versi 5.8
Di bawah ini adalah konfigurasi saya
$config['api_key'] = env('RAJAONGKIR_KEY');
$config['account_type'] = env('RAJAONGKIR_ACCOUNT_TYPE','starter');
$rajaongkir = new Rajaongkir($config);

Bisa run composer update seharusnya sudah bisa solved..

authors: riskidev steevenz

repo: steevenz/rajaongkir


text:
globalOutputFormat typo, broke global output format

fixes #89
Don't have a good way to write a test to cover this because of the way the helpers are registered.

Work like a charm, thanks for fixing that fast :)

authors: MauriceMohlek jasonmit

repo: stefanpenner/ember-moment


text:
Add CocoaPods podspec for a future version.

Adding this now will allow users to install the HEAD version directly from your repo.
Once you are ready to tag an actual release version, this copy can be updated for the chosen version number and be added to the CocoaPods spec repo. You can then bump the one in your repo to a unit higher, so that when users install from HEAD, they will have a higher version number than the released version.

I’ve added you to the specs repo btw, so you can push the spec once you release a version :)

Oh great, thanks!

authors: alloy steipete

repo: steipete/PSStackedView


text:
Account.GetNativeBalance() method

Close #24

+1

authors: bartekn nullstyle

repo: stellar/go-stellar-base


text:
Horizon Documentation

Added instructions on how to ingest historical data from stellar-core into horizon.

Added some thoughts/explanation inline here: https://github.com/stellar/go/pull/763/files

repo: stellar/go


text:
Auth Next: Add simpler require_auth alternative

require_auth is already pretty simple (as only a single vector of args is needed), but we can do better. For the cases when an address simply needs to authorize the call with all the args we can provide a no-args version of this method. This can be done in two layers:

In host introduce a host fn with no arguments to require auth for all the input arguments. This is also useful as a contract size optimization.
In SDK we can also provide a way to annotate functions as requiring auth of all args for a given addres. This can be done either via simple code generation of env.require_auth or even with some metadata (which would be more useful for the contract interoperability)

One more thought is to go for even deeper support for this and provide some special syntax for the cases when there is only a single address that needs to authorize all the invocation arguments. This is likely to cover a lot of the contracts. Also, unlike the invoker that had similar semantics, this would still be compatible with Auth Next, as require_auth would still be called under the hood.

Reopening this to track the potential additional work - the PR added only the host-side support.

repo: stellar/rs-soroban-env


text:
Fix unsoundness in RawVal::get_tag

What
Fix a soundness bug in RawVal::get_tag and add a test case that it stays fixed.
Why
While working on https://github.com/stellar/rs-soroban-env/pull/767 I was flummoxed by an error in RawVal::get_tag.
This function does an unsafe cast from u8 to Tag. It does so by using three marker Tags: SmallCodeUpperBound, ObjectCodeLowerBound, and ObjectCodeUpperBound. It assumes that u8's between 0 and SmallCodeUpperBound, and between ObjectCodeLowerBound and ObjectCodeUpperBound are valid, and does a transmute if so, like this:
    const fn from_u8(tag: u8) -> Tag {
        const A: u8 = Tag::SmallCodeUpperBound as u8;
        const B: u8 = Tag::ObjectCodeLowerBound as u8;
        const C: u8 = Tag::ObjectCodeUpperBound as u8;
        if !((tag < A) || (B < tag && tag < C)) {
            return Tag::Bad;
        }
        unsafe { ::core::mem::transmute(tag) }
    }

The assumption is not true though and there are gaps in the Tag discriminants that result in creating Tags that don't exist, which leads to segfaults if those Tags are used.
The main thing this patch does is add a test case that ensures that the conversion from u8 to Tag is correct for all u8s. It does this by using the int-enum crate as a dev-dependency, which uses a proc macro to create the conversion code. A test case compares the hand-coded conversion to the macro-coded conversion. This ensures the hand-coded conversion is correct while not pulling the int-enum crate as a dependency for contracts.
It also:

Extracts the actual conversion from RawVal to Tag::from_u8, putting the conversion closer to the converted type.
Fixes the conversion for the two missing cases. The comments in this code indicate it is somewhat perf sensitive, but not critically so. The new cases will add a couple of branches or a jump table - I haven't checked the output.

I investigated changing the discriminants of Tag so there are no gaps but it isn't easy to change:

The soroban-test-wasms must be rebuilt, and they currently do not build.
Tags are part of the ABI anyway and someday will not be able to change ever.
It seems best to future-proof this code anyway.

These tests will ensure that if somebody does remove the gaps in Tag prior to launch, adds more Tags, or otherwise changes how the conversion is done, then the conversion function will stay correct.
Note also that the new Tag::from_u8 function is public, creating a way to test whether a u8 is a valid Tag. I need this ability in a test case of https://github.com/stellar/rs-soroban-env/pull/767.
Known limitations
Would be nice to get rid of the two gaps in the Tag discriminants.

Nice catch. I would like to actually eliminate the gaps though, as it is perf sensitive (and obviously a bit of a footgun in terms of logic). Why aren't the test wasms building?

User error - I didn't realize I had to pair a compatible local sdk with the test wasms build.
It's fixed now. The PR removes the discriminant gaps. It still extracts the conversion function to a Tag::from_u8 and makes it pub, and adds a test using the int-enum dependency.


text:
graph_log_likelihood unit test

This PR adds a unit test for graph_log_likelihood. I also found and fixed a wrong sign bug in graph_log_likelihood, this had the effect of:

decreasing demo classification accuracy from 78% to 67%: it now matches the papers reported accuracy of 67%
demo embeddings TSNE are now less well separated and appear less visually similar to the paper

So in terms of accuracy it matches the paper better, but in terms of TSNE plot it matches the paper worse. TSNE is very parameter dependant and I couldn't find the paper's parameters so this is a less reliable metric than classification accuracy.
See #1135 and equation 4 of https://arxiv.org/pdf/1710.09599.pdf

Why does using this "incorrect" loss function give a better result?

I think we may have accidently stumbled across a better loss function.
Running this code:
from matplotlib import pyplot as plt
import numpy as np

# expected walk value for one node pair
e = 5

# potential values of sigma in range (0, 1)
# lets see which sigma gives the lowest loss
sigmas = np.linspace(0.0001, 0.9999, 1000)

# graph log llikelihood function when there's no edge
loss_1 = np.abs(-e * np.log(sigmas) - np.log(1 - sigmas))
loss_2 = np.abs(e * np.log(sigmas) - np.log(1 - sigmas))

plt.title("Graph Log Likelihood Loss")
plt.plot(sigmas, loss_1)
plt.ylabel("loss")
plt.xlabel("sigma")
plt.show()

plt.title("Custom Loss")
plt.plot(sigmas, loss_2)
plt.ylabel("loss")
plt.xlabel("sigma")
plt.show()

Gives:

The local minima of the custom loss (my old buggy graph log likelihood loss) is roughly the same as the graph log likelihood but it looks to me that the custom loss local minima will be easier to find with gradient descent bc it's gradient doesn't flatten out so much.

repo: stellargraph/stellargraph


text:
add link to paper

This PR adds a reference to the watch your step paper into the demo.

I think this has already been done

What hinted at this being done? I don't see it fixed on develop? https://github.com/stellargraph/stellargraph/blob/develop/demos/embeddings/watch-your-step-embeddings.ipynb

authors: huonw kieranricardo


text:
toothpick.locators.NoFactoryFoundException

Hello!
I my android application sometimes has crash:
toothpick.locators.FactoryLocator.getFactory + 21 (FactoryLocator.java:21)
--
  | toothpick.ScopeImpl.lookupProvider + 329 (ScopeImpl.java:329)
  | toothpick.ScopeImpl.getInstance + 58 (ScopeImpl.java:58)
  | toothpick.ScopeImpl.getInstance + 49 (ScopeImpl.java:49)
  | com.b2b_logist.smarttracker.presentation.ui.history.HistoryNewsListener__Factory.createInstance + 12 (HistoryNewsListener__Factory.java:12)
  | com.b2b_logist.smarttracker.presentation.ui.history.HistoryNewsListener__Factory.createInstance + 8 (HistoryNewsListener__Factory.java:8)
  | toothpick.InternalProviderImpl.get + 96 (InternalProviderImpl.java:96)
  | toothpick.ScopedProviderImpl.get + 31 (ScopedProviderImpl.java:31)
  | toothpick.ScopeImpl.getInstance + 58 (ScopeImpl.java:58)
  | toothpick.ScopeImpl.getInstance + 49 (ScopeImpl.java:49)
  | com.b2b_logist.smarttracker.presentation.ui.history.HistoryBinding__Factory.createInstance + 15 (HistoryBinding__Factory.java:15)
  | com.b2b_logist.smarttracker.presentation.ui.history.HistoryBinding__Factory.createInstance + 8 (HistoryBinding__Factory.java:8)
  | toothpick.InternalProviderImpl.get + 94 (InternalProviderImpl.java:94)
  | toothpick.ScopeImpl.getInstance + 58 (ScopeImpl.java:58)
  | toothpick.ScopeImpl.getInstance + 49 (ScopeImpl.java:49)
  | com.b2b_logist.smarttracker.presentation.ui.history.HistoryFragment__MemberInjector.inject + 11 (HistoryFragment__MemberInjector.java:11)
  | com.b2b_logist.smarttracker.presentation.ui.history.HistoryFragment__MemberInjector.inject + 8 (HistoryFragment__MemberInjector.java:8)
  | toothpick.InjectorImpl.inject + 23 (InjectorImpl.java:23)
  | toothpick.Toothpick.inject + 163 (Toothpick.java:163)
  | com.b2b_logist.smarttracker.presentation.ui._base.BaseFragment.onCreate + 44 (BaseFragment.kt:44)

Inject look like this:
    override fun onCreate(savedInstanceState: Bundle?) { // BaseFragment
        Logger.forThis(this).debug()
        super.onCreate(savedInstanceState)
        retainInstance = true
        Toothpick.openScopes(
                App::class.java.canonicalName,
                MainActivity::class.java.canonicalName,
                MainActivity::class.java.simpleName,
                this.javaClass.canonicalName).let {
            it.installModules(module)
            Toothpick.inject(this, it) // BaseFragment.kt:44
        }
    }

Toothpick can't inject field that identified in SessionModule. Session module installs in MainActivity
    override fun attachBaseContext(newBase: Context?) { // MainActivity
        Logger.debug()
        super.attachBaseContext(newBase)
        // di
        Toothpick.openScopes(App::class.java.canonicalName, this.javaClass.canonicalName).installModules(SessionModule())
        Toothpick.openScopes(App::class.java.canonicalName, this.javaClass.canonicalName, this.javaClass.simpleName).let {
            it.installModules(SmoothieAndroidXActivityModule(this), ActivityModule(this))
            Toothpick.inject(this, it)
        }
    }

That I'm doing wrong?

Hi @Riningan ,
there are a few things :

App::class.java.canonicalName --> do not use the class names here. Use the application object and the activity objects themselves as name. When an object has a lifecycle and you want to create a scope that has the same lifecycle, use this object as a name for the associated scope. Not a class name.  --> TP.openScopes(application, this)
I don't understand why you have 3 levels of scopes. Are you trying to create a scope that survives the activity rotation ? If so, please have a better look at the example, you have to create a scope annotation, and use the classname of this scope annotation as the name of the second scope. You will also use the scope annotation to annotation things your session module.
I would recommend to open the scopes, store the result in a variable, use the scope to install the 2 modules (you can pass an array/varargs of modules). And last, inject(this) using this scope.
also, as you seem to be using a retained fragment, I am not sure exactly of what you are trying to achieve with the scopes: do you really want to have 4 different scopes ? Try to stick to 3 scopes for now, if you really need a scope that surives the activity, otherwise, 2 is good.
finally open HistoryNewsListener__Factory, line 12. Look at the class that is injected. Check if a factory was generated, maybe you forgot to annotate the type to make it injectable.

Re-open as needed, but I would suggest to take more time to go through the docs and examples first.

Hi @stephanenicolas ,
Thanks about help. But I have a question about second advice. How I can annotate class of third party? This class I using in session scope.

You can't annotate a class if you don't have the code..
But you can create a binding in the scope where you want it to leave, a binding with a provider seems best in this case.

Can you help me? I don't understand how create provider class in my case.
I need to store this field in presenter (session) scope
val router = Router()
val cicerone = Cicerone.create(router)
bind(Router::class.java).toInstance(router)
bind(NavigatorHolder::class.java).toInstance(cicerone.navigatorHolder)

If I understand you, you mean create:
@SessionScope
class ThirdPartyProvider @Inject constructor() {
    fun getSomethinkThirdParty() : SomethinkThirdParty = SomethinkThirdParty()
}

and inject like this?
@Inject
lateinit mThirdPartyProvider ThirdPartyProvider

I need to store this field in presenter (session) scope

If the above sentence means that you want it to be a Singleton on the session scope, you should do something like this:
@SessionScope @Singleton
class SomethinkThirdPartyProvider : Provider<SomethinkThirdParty> {
    override public get() = SomethinkThirdParty()
}

Then install a module on that Scope with the following binding
bind(SomethinkThirdParty::class.java).toProvider(SomethinkThirdPartyProvider::class.java)

And then you should be able to inject the same instance anywhere using that scope or any child scope:
@Inject
lateinit var SomethinkThirdParty somethinkThirdParty

Thanks a lot!

authors: Riningan dlemures stephanenicolas

repo: stephanenicolas/toothpick


text:
Updated for Django 1.7+.

Removed deprecated model-utils dependency in favor of built in Manager.from_queryset and removed query.having.

Thanks for this, couple points:

Can you undo the README change and version change?
What happens to SQL queries with a HAVING clause?

Sure, removed the readme change and the version change.  As for query.having I looked into it and it was apparently removed in 1.9 which is why it was failing for me.(https://github.com/django/django/commit/afe0bb7b13bb8dc4370f32225238012c873b0ee3) .
As commented in the code
In Django 1.9 the query.having property was removed and the
    # query.where property will be truthy if either where or having
    # clauses are present. In earlier versions these were two separate
    # properties query.where and query.having

Perfect, thanks so much!

authors: cordery stephenmcd

repo: stephenmcd/django-postgres-fuzzycount


text:
Upgrade 404 page

@williamgrh

#271


text:
VGA Image Aliasing

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
When displaying raw images in the VGA resolution, there are visible aliasing artifacts.
Steps to Reproduce

Run the ZED mini camera node with VGA resolution.
Display the /zedm/left/image_rect_color or /zedm/left/image_rect_gray in rviz2.
Observe...

Expected Result
RealSense screenshot with 640x480 resolution - notice virtually no aliasing artifacts on the edge.

Actual Result
Screenshot from ZED Mini with VGA resolution.

ZED Camera model
ZED Mini
Environment
OS: Ubuntu 20.04
CPU: Intel i7
GPU: Quadro RTX 3000
ZED SDK: 3.8.2

Anything else?
No response

Thanks.


text:
BUG: can start update twice

Describe the bug
If an update is available it's possible to click the "UPDATE ALL" button, etc. again after starting the update process already.
To Reproduce
Steps to reproduce the behavior:

Start update
Wait for it to start the tasks
Start update again
Update starts again

Expected behavior
Prevent user from starting updates simultaniously.
Desktop (please complete the following information):

Launcher version 1.0.0-rc.15

Node (please complete the following information):

OS: Ubuntu 22.04
Affected service: Updates

Was fixed at some point

repo: stereum-dev/ethereum-node


text:
feat: run external commands on a file under the cursor

By doing "g:" on a file a prompt asks us which command to run on the current file under the cursor. This is helpful when we want to run a quick command like file or ldd.

Seems like there is no need to merge this pr the same thing can be accomplished by putting this in your config:
vim.keymap.set("n", "g:", function()
  vim.ui.input({ prompt = 'command: ', completion = "shellcmd" }, function(input)
    if input == "" then
      return
    end
    local file_path = oil.get_current_dir() .. oil.get_cursor_entry().name
    if file_path == "" then
      return
    end
    vim.api.nvim_command(":! " .. input .. " \"" .. file_path .. "\"")
  end)
end, { desc = "Run custom commands on the entry under cursor" })

I was looking for a way to do this and found this PR, this is actually super useful. I vote for
this to be added upstream. It's true that with a very simple function you can add the functionality, however
this just plays nicely with the kind of workflow that oil gives you, and I think it would make sense to add it.
If someone comes across this, add this to also handle when you abort the ui.input. In those cases it returns nil and it would crash. And wrapped it in a autocmd to only add the keymap in an oil buffer
vim.api.nvim_create_autocmd({ "FileType" }, {
    pattern = { "oil" },
    callback = function()
        vim.keymap.set("n", "g:", function()
            vim.ui.input({ prompt = "command: ", completion = "shellcmd" }, function(input)
                if input == "" or input == nil then return end
                local file_path = oil.get_current_dir() .. oil.get_cursor_entry().name
                if file_path == "" or file_path == nil then return end
                vim.api.nvim_command(":! " .. input .. ' "' .. file_path .. '"')
            end)
        end, { buffer = 0, desc = "Run custom commands on the entry under cursor" })
    end,
})

authors: omer-biz rafamadriz


text:
Generate the GUIDs with NewId library

Hello,
It might be useful to generate the GUIDs with this library: https://github.com/phatboyg/NewId
Thanks

When #24 is implemented, this will be possible with a custom provider rather than built into the library,

authors: lnaie stevejgordon

repo: stevejgordon/CorrelationId


text:
Netlify build notifications

I need some way to be notified when the Netlify site fails to build. I don't think I want to add a pull request check, because Netlify takes forever to pick up GitHub's webhooks and build the site. I would rather be reactive.

It emails me now :)

repo: stevenpetryk/mafs


text:
limit:60 not working

Hey!
So regardless of what number I put over 33, it always returns only 33 images. The user account has 143 images currently. I've added the JS part of it hiding the ID and token.
var userFeed = new Instafeed({
    get: 'user',
    userId: ID,
    accessToken: 'token',
    resolution: 'low_resolution',
    limit: 60,
    sortBy: 'most-recent',
    template: '
{{caption}}{{likes}}
'
});
userFeed.run();

Thanks for the help!

For anyone with the same issue, and for whom the -1 hack didn't work. I have written a short script that provides a hack for this limit, but of course in exchange for more API calls.

Regarding the above, the API is now much cleaner, and can filter and fetch by tags.

@d4nyll would you be able to show me how to fetch by tags and not limited to user? i tried the setting shown in the documentation but that yielded zero images:

i'm fairly new to all this so could be missing something obvious. any help is appreciated, thanks!

I can only ever get a max of 20 images no matter how big a number I put

my understanding is that instagram limits sandbox users to the most recent 20 posts, no more.  starting in june you have to be approved as an "app" to get out of sandbox, where you can then specify scope.

Hi there,
Like @FranciscoG I'v tried to submit my "app" and this is what I get :
I want to display my Instagram posts on my website. >>"You do not need to submit for review for this use case [...]By using a client in sandbox mode, you can still access the last 20 media[...]"
I don't understand : instagram don't allow me to submit my app, so how can I get out of sandbox mode ??

you don't have to be out of sandbox mode if all you want to do is display your 20 most-recent posts.  leave your "app" in sandbox mode, don't specify scope, and you will be able to display your 20 most-recent.

but what I have to do if I want to display more then 20 posts ? in fact I want to display ALL my posts not only the last 20 !

you can't, as far as i know. instagram requires you submit as an app to display more than 20, and they're not approving your usage type.  not unless by displaying your posts you gave created a new user experience which is greater than just your website (aka an app or branding experience).
if it's just to display posts solely on your website, all you get is 20.  period.


text:
After trying for half-a-day, STILL CANT get "Load More" to work...

When I comment out my "Load More" code, my feed renders just fine. But once I add the "Load More" code, my feed disappears :(
I've included my code as an image file (it would render correctly when I typed it in).
(Note: I am a JS novice)
https://nofile.io/f/R1rC7scpobF/instafeed.js+code+snippet.png

I believe if you Instagram API Client is in sandbox mode, they don’t support loading more images anymore.

authors: msarit stevenschobert


text:
Update constants.js

test123

permissions testing for making pull requests

repo: stevezease/tailwind-converter


text:
Fix compile error with questa, for issue #242

This PR fixes #242 by using a deferred constant. It shouldn't change anything except allowing to compile the package with Questa, which failed before.

Thanks for fixing!

authors: stnolting tmeissner


text:
:seedling: Update konflux CEL from backplane-2.8 to main

This PR:

/cc @haoqing0110

/lgtm
/approve


text:
ACM-8257 Fix issue with suggestion selection of marked text

related bug: https://issues.redhat.com/browse/ACM-8257

/lgtm

@zlayne Did you investigate if this behaves the same for all OCP versions (and therefore PF versions) that we run on? Just wondering if it's always been broken, or something that behaves a little differently depending on PF version.

@KevinFCormier Yes, we have discovered this has been present since the searchbar rewrite (2.7). The issue occurs when the user clicks directly on the marked/highlighted text as seen in the attached image (user clicked in the Config in ConfigMap).
Using the previous event.target.innerText returns the element where the event started. In this case, the innerText is Config not ConfigMap. (We use the  element)
Using event.currentTarget.innerText returns which element the event was attached to or the element whose eventListener triggered the event. So this contains the entire text of the suggestion.
The issue was in how I was handling the JS event, and to my knowledge, the Patternfly version shouldn't matter.

@zlayne Great! Thank you for confirming.

@KevinFCormier Yes, we have discovered this has been present since the searchbar rewrite (2.7). The issue occurs when the user clicks directly on the marked/highlighted text as seen in the attached image (user clicked in the Config in ConfigMap).
Using the previous event.target.innerText returns the element where the event started. In this case, the innerText is Config not ConfigMap. (We use the element) Using event.currentTarget.innerText returns which element the event was attached to or the element whose eventListener triggered the event. So this contains the entire text of the suggestion.
The issue was in how I was handling the JS event, and to my knowledge, the Patternfly version shouldn't matter.

/cherry-pick release-2.8

/cherry-pick release-2.7

authors: KevinFCormier zlayne

repo: stolostron/console


text:
ACM-10319 Add cluster update risk column to BatchUpgradeModal

/test unit-tests-sonarcloud


text:
Release 3.14.1

Gatekeeper community upstream 3.14.1 release

/override dco

repo: stolostron/gatekeeper


text:
fix RELIABILITY and SECURITY Vulnerabilities

Signed-off-by: haoqing0110 qhao@redhat.com

/assign @zhiweiyin318

/approve
/lgtm

/test e2e


text:
Using Storybook in a project with Wix's react-native-navigation?

I can't get it working... has someone tried it?

It does work :)
Give me few minutes for an example.

This doesn't seem to be working for me. When installing React-Native-Navigation to your project, it requires you to do stuff in Xcode:

But my react app was a create-react-app so there's no xcode project to open. Did you follow those instructions above by going into Xcode?

Yes, I don't know if RNN supports CRNA. I'll quickly ask around.

@SuttJ so RNN doesn't support CRNA.

Alright. I appreciate you taking the time to find out, thanks!
On Jun 19, 2017, at 7:27 AM, Gytis Vinclovas <notifications@github.commailto:notifications@github.com> wrote:
@SuttJhttps://github.com/suttj so RNN doesn't support CRNA.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/storybooks/storybook/issues/1151#issuecomment-309412826, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AcE9L6T07i644slpYlHBBHw9FOXtZytaks5sFlsUgaJpZM4NpjyH.

Take me some times to understand why Storybook stops on splash screen...
Just in case, I create a repository with correct configuration.
https://github.com/Charlynux/nativestorybook

With RNN@v2
const StorybookUI = getStorybookUI({ port: 7007, onDeviceUI: true })
Navigation.registerComponent('storybook.UI', () => StorybookUI)
Navigation.events().registerAppLaunchedListener(async () => {
  await Navigation.setRoot({
    root: {
      component: {
        name: 'storybook.UI',
      },
    },
  })
})

export default StorybookUI

This still seems to blow up when adding the StorybookUI as another tab in RNN app rather than a single screen app

authors: Charlynux Gongreg SuttJ gianko kdawgwilk nenti

repo: storybooks/storybook


text:
Styles no longer imported after updating to v4.0.0-alpha - Angular 6

Bug or support request summary
After updating to Angular 6, Storybook stopped working. Based on the advice in this Issue I updated to 4.0.0-alpha.3 This fixed my error and the Storybook server was running again, however now my styles (and fonts) aren't showing up.
I also tried updating to the latest version 4.0.0-alpha.7 but I get a giant list of errors similar to this:
Module not found: Error: Can't resolve 'react-dom' in '/Users/KS185325/Projects/nui-angular/node_modules/velocity-react' (Mentioned in 3602)
Steps to reproduce
I followed the Angular getting started. Everything was working fine until I updated Angular and then updated Storybook.
Versions

angular 6.0.0
storybook/angular 4.0.0-alpha.3
storybook/addon-actions 4.0.0-alpha.3
storybook/addon-knobs 4.0.0-alpha.3

Loading css problem probably is due to #3593. I start to use storybook just recently so I don't know whether react-dom was a explicit dependency. I had to install react, react-dom@16.0.0 manually.

Alos should be related to #3491

authors: KolbySisk igor-dv wuyuanyi135


text:
Backgrounds addon has overlapping element

Hello Everybody,
i first wanted to thank you a lot for this project 👍
Describe the bug
I've just followed the install guides for the react view layer and added the backgrounds addon.
I see that this element is overlapping the iframe and creates a white background:

If i remove the background-property or delete the element completely, i can see and switch the background as expected.
To Reproduce
Steps to reproduce the behavior:

Follow: https://storybook.js.org/docs/basics/guide-react/
Follow: https://github.com/storybooks/storybook/tree/master/addons/backgrounds

Expected behavior
I should see the background "twitter" (#00aced) as it is set as default in the storybook config file and should be able to switch the backgrounds
Screenshots
Before

After

Code snippets
My Entry point file looks like this:
import React from 'react';
import { storiesOf } from '@storybook/react';
import { Button } from '@storybook/react/demo';

storiesOf('Button', module)
  .add('with text', () => (
    <Button>Hello Button</Button>
  ))
  .add('with some emoji', () => (
    <Button>😀 😎 👍 💯</Button>
  ))

System:

OS: macOS High Sierra (v10.13.2)
Device: Macbook Pro 2018
Browser: Chrome
Framework: react
Addons: Background
Version: ^5.0.0

Additional context
My Setup is as follows:
// .storybook/config.js
import { configure, addParameters } from '@storybook/react';

function loadStories() {
  require('../stories/index.js');
  // You can require as many stories as you need.
}

addParameters({
  backgrounds: [
    { name: 'twitter', value: '#00aced', default: true },
    { name: 'facebook', value: '#3b5998' },
  ],
});

configure(loadStories, module);

// .storybook/addons.js
import '@storybook/addon-backgrounds/register';

My Dependencies:
  "devDependencies": {
    "@babel/core": "^7.3.4",
    "@storybook/addon-backgrounds": "^5.0.0",
    "@storybook/react": "^5.0.0",
    "babel-loader": "^8.0.5"
  },
  "dependencies": {
    "react": "^16.8.4",
    "react-dom": "^16.8.4"
  }

Best Regards!

Forget it it was a Chrome plugin, i just now double checked it on FF and it worked, sorry for the fuzz.


text:
feta(a11y): add 'incomplete' tab

Issue: https://github.com/storybooks/storybook/issues/5782
What I did
Add 'incomplete' tab in a11y addon
Fix cra-kitchen-sink example (turn on addon)
How to test

Is this testable with Jest or Chromatic screenshots?
no
Does this need a new example in the kitchen sink apps?
yes
Does this need an update to the documentation?
no

Tested -- works great!

authors: Armanio shilman


text:
Update NHibernate to 5.0.0

And cover all breaking changes.

completed with https://github.com/stoveproject/Stove/commit/eb3d74da9482bc8fe6edb163d47ae2b43788b78d

repo: stoveproject/Stove


text:
Add enhanced CKEditor 5 plugin

Add new CKEditor 5 plugin that works with the latest version of Strapi without bugs and based on enhaced build of CKEditor.
By submitting this pull request, I promise that:

[x] I have read the contribution guidelines thoroughly.
[x] I ensure my submission follows each and every point.

Should I change something?

Should I change something?

repo: strapi/awesome-strapi


text:
Refactoring for RPC "Feature"

Requires testing. What would a test look like for this? Manually setting the config to enable RPC, running the node, and running RPC commands? I see there are already RPC tests of some kind, but they seem to be more like unit tests rather than the "Is RPC running" kind of tests that this seems to require.

Generally if all the integration tests are passing RPC is tested.
The integration tests depend on RPC working correctly.

authors: dangershony mikeolteanu

repo: stratisproject/StratisBitcoinFullNode


text:
No prebuild binary found

please add a prebuild binary

Here you go :)
https://github.com/stratumfarm/derocli/releases

repo: stratumfarm/derocli


text:
Rename misleading test client argument name

Description
This PR renames the asserts_errors of our user-facing test clients to assert_no_errors as proposed in #3580. The old option is still available but will raise a deprecation warning.
Also, before this PR, only the Django test client had tests. Now, all test clients share the tests. (That's why this PR is a little bigger than one might expect).
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

Fixes #3580

Summary by Sourcery
Rename the asserts_errors argument to assert_no_errors in test clients for clarity, add shared tests for all clients, and document the change with a release note.
Enhancements:

Rename the asserts_errors argument to assert_no_errors in test clients to better reflect its purpose, while maintaining backward compatibility with a deprecation warning for the old argument.

Documentation:

Add a release note documenting the renaming of the asserts_errors option to assert_no_errors in test clients, highlighting the backward compatibility and deprecation warning.

Tests:

Add shared tests for all test clients, including AIHOTTP, ASGI, and Django, to ensure consistent behavior across different environments.
Introduce tests to verify the deprecation warning for the asserts_errors argument and the functionality of the assert_no_errors option.

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

The AIHOTTP, ASGI, and Django test clients' asserts_errors option has been renamed to assert_no_errors to better reflect its purpose.
This change is backwards-compatible, but the old option name will raise a deprecation warning.
Here's the tweet text:
🆕 Release (next) is out! Thanks to @NucleonJohn for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)

Maybe we should consolidate the test clients in the future (we have private ones in the tests folder :D)

Yeah, I think that's a great idea. I didn't even know we had a public test client because it doesn't appear to be documented and did not really have tests. Our internal test client is much more capable and could be a good basis for a unified test client.

authors: DoctorJohn botberry

repo: strawberry-graphql/strawberry


text:
Renamed package from use-wait to react-wait

npm gave me the name react-wait (thanks to them) and I changed the name. Also updated the version with improvements.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: f streamich

repo: streamich/react-use

license: Unlicense


text:
Publish *.spkg during new releases

Publish *.spkg during new releases to allow import of Protobuf messages
substreams.yaml
imports:
  sink_kv: https://github.com/streamingfast/substreams-sink-kv/releases/download/v0.1.2/substreams-sink-kv-v0.1.2.spkg

modules:
  - name: kv_out
    kind: map
    inputs:
      - map: map_example
    output:
      type: proto:sf.substreams.sink.kv.v1.KVOperations

This is now automated.

authors: DenisCarriere maoueh

repo: streamingfast/substreams-sink-kv


text:
node ssl_server.js & fails

I'm following the installation instructions from the README file, and I get to the following step:
node ssl_server.js &

which fails:
$ node ssl_server.js
module.js:338
    throw err;
          ^
Error: Cannot find module '<streamium_directory>/ssl_server.js'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

should that instruction be:
node ssl_peerjs.js

instead?

I had the same problem.  I think the suggested change is correct.

There doesn't seem to be any activity on this repo. Closing

repo: streamium/streamium


text:
🛑 EAM Maara is down

In 07f8436, EAM Maara (http://eam.maaracorp.com:8081/web/base/logindisp?tenant=EAM) was down:

HTTP code: 0
Response time: 0 ms

Resolved: EAM Maara is back up in 988d816.

repo: streamlined-scs/upptime


text:
Add tutorial: Azure Blob Storage

Currently there is not a Knowledge Base tutorial for Azure Blob Storage.
I'm interested in contributing a new tutorial for Azure Blob Storage to the docs and creating a PR for this change.
Should be very similar to the existing S3 tutorial (creating a bucket + file, provisioning access keys, adding to secrets, etc.).

For both of your submitted issues, if you're willing to write these tutorials up we'd be happy to review them!

authors: randyzwitch sesi

repo: streamlit/docs


text:
Refactor RefCard and ComponentCard to resolve React hydration errors

📚 Context
This PR addresses React hydration errors caused by nested anchor tags in the RefCard and ComponentCard components.
🧠 Description of Changes

ComponentCard:

Implements conditional rendering to use a div with an onClick handler for navigation when children contain <a> tags. Retains the original <a> tag wrapper when no child anchor tags are present.

RefCard:

Similar conditional rendering approach as ComponentCard, switching between a div and Next.js's Link component based on the presence of child anchor tags.

Added a utility function (scripts/contains-anchor.js) to check if children contain an anchor tag and used in both updated components above.

Revised:

Current:

💥 Impact

Size:

[ ] Small
[x] Not small

🌐 References

Contribution License Agreement
By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.

Thiago and I have talked about this PR (but not sure when it will get resolved exactly). I removed the final commit and merged in main to make it current and avoid conflicts. If Thiago goes with this approach, we can update the headers at the end or as a follow. :)

I was just trying to edit some docs locally after months and I found the hydration errors painful when refreshing the API reference page. This PR makes the development experience better like #914. Any chance we could merge this or get an idea of what the blockers are? 😄

authors: sfc-gh-dmatthews snehankekre


text:
Separate LocalData and ThreadLocalAccessor from stats logger

Motivation
It's only a code cleanup since static inner classes break the OOP design
and lead to a lot of direct accesses to the private fields and repeated code.
Modifications
Separate LocalData and ThreadLocalAccessor from
DataSketchesOpStatsLogger. Then use their public methods to access the
private fields.
Documentation
Check the box below.
Need to update docs?

[ ] doc-required
(If you need help on updating docs, create a doc issue)

[x] no-need-doc
(Please explain why)

[ ] doc
(If this PR contains doc changes)

This PR doesn't modify any existing logic. The related code might be fixed in future.

repo: streamnative/kop


text:
[tools] - Remove unused MonoDevelop.Debugger

PR Details
Description
This PR removes unused tool from stride project.

Thanks !

authors: Eideren Jklawreszuk


text:
Resize "Add Asset Pop-Up"

PR Details
The "Add Asset Pop-Up" does not have a height limit
Before:

After:

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] I have built and run the editor to try this change out.

Will these changes be consistent across different resolutions? It seems like this change only has an effect since the height was hard coded before to account for the list size so the scroll bar would have been available if any items were added in the future.
If it is not consistent across different resolutions or scales then I think we should consider that as a fix instead.

Sorry for not being more specific earlier!
Yes, this is a fix!

authors: Doprez minktusk


text:
Crash using VT and Dynamic Surrondings

Random crash while walking on the map...
crash-log: https://gist.github.com/vpontin/8c3e0621ef01ca6b1e153d6ebca0c75e
Using MC 1.12.2, Forge 14.23.2.2613, VanillaTweaks 1.2.5 and DynamicSurrondings 3.4.9.2
Also reported on DS side, https://github.com/OreCruncher/DynamicSurroundings/issues/238

It is something to do with dynamic surroundings

Ok. Waiting @OreCruncher reply on DS issue

Actually it looks like the self planting capability provider is responding that my emoji capability belongs to it.  If the provider returns non-null it means it supports the capability, which in this case it obviously does not.

authors: OreCruncher strikerrocker vpontin

repo: strikerrocker/VanillaTweaks


text:
Improve Docker support for ARM

Currently our Docker image is built for amd64. We should figure out a way to also support ARM, since it is not uncommon for users to want to run Stringer on a Raspberry Pi or the like. Having very little experience with Docker, I'm not sure how to proceed with this, but it might require creating a second image that people can pull for ARM devices.

@guidopetri pinging you on this one. Even if you don't have time to make a PR, it would be super helpful if you could outline the steps I could take to point me in the right direction.

@guidopetri thank you! We're running on CircleCI, so we should be able to take advantage of ARM support there.

I started a PR here to track this work

With the second bullet point done, I'll see about setting up the docker image build via CircleCI next. I'm not super familiar with it so it may take me a moment.

Thanks @guidopetri! I'm pretty familiar with CircleCI, so let me know if you get stuck on anything there. I suspect I'll have to configure it with a couple of env variables to publish to docker.

Also, in case you haven't come across it already, CircleCI provides an orb for Docker stuff.

#1092 should close this issue :)

Thanks for all your work on this @guidopetri!

authors: guidopetri mockdeep

repo: stringer-rss/stringer


text:
add Stack stack.yaml

This is a configuration file for Stack (generated with "stack init" and only
tested with version 1.1.2).
I keep hitting problems trying to maintain a global package collection (via
cabal) that works for the projects I have open and frequently break it,
preventing me from testing something in Striot. Using Stack, I believe I can
maintain an isolated collection of libraries (and GHC) and so avoid this
problem.
I have not tested this yet with a more modern Stack version but I shall
(I have had problems with the format of stack.yaml files generated by newer
Stack versions not working with 1.1.2… but hopefully it's better at backwards
compatibility than forwards)

Hi @adam-cattermole sorry I only saw your comment now, after merging. I hadn't considered the containers and the GHC version there at all, but it would make sense to keep them aligned. Shall we see whether using :8.6.3 in the container causes problems? I'll do some testing.

No problem - I didn't realise it had been merged!
I cannot imagine that :8.6.3 will make any difference to the build at all (I think I might have tried building with it before), but let me know whether there is any change.

authors: adam-cattermole jmtd

repo: striot/striot


text:
cocoapod Stripe 6.2.0 : duplicate symbols while linking

Hello,
I installed the cocoapod Stripe 6.2.0 to use the PaymentKit framework.
When I compile the project, without any code using PaymentKit, I get errors in the linking phase :
duplicate symbol OBJC_CLASS$_PTKView in:
[...PATH...]/Build/Intermediates/season.build/Debug-iphoneos/season DEV.build/Objects-normal/arm64/PTKView.o
[...PATH...]/Build/Products/Debug-iphoneos/libStripe.a(STPPaymentCardTextField.o)
duplicate symbol OBJC_METACLASS$_PTKView in:
[...PATH...]/Build/Intermediates/season.build/Debug-iphoneos/season DEV.build/Objects-normal/arm64/PTKView.o
[...PATH...]/Build/Products/Debug-iphoneos/libStripe.a(STPPaymentCardTextField.o)
duplicate symbol OBJC_CLASS$_PTKCard in:
[...PATH...]/Build/Intermediates/season.build/Debug-iphoneos/season DEV.build/Objects-normal/arm64/PTKCard.o
[...PATH...]/Build/Products/Debug-iphoneos/libStripe.a(STPPaymentCardTextField.o)
duplicate symbol OBJC_METACLASS$_PTKCard in:
[...PATH...]/Build/Intermediates/season.build/Debug-iphoneos/season DEV.build/Objects-normal/arm64/PTKCard.o
[...PATH...]/Build/Products/Debug-iphoneos/libStripe.a(STPPaymentCardTextField.o)
ld: 4 duplicate symbols for architecture arm64

forget it. My mistake, obviously.

repo: stripe/PaymentKit


text:
Store dates in UTC

Task Description
All dates that we store in DB should have UTC time zone. The example is UserEntity.lastUpdated.
This task will have to be carried out against the issues/1649 branch.
Tasks
The following tasks will need to be carried out:

[ ] Set the JVM default timezone to UTC within application startup
[ ] Check that all dates stored in UTC
[ ] Convert dates to UTC if needed

Task Relationships
This task:

Is a sub-task of: #1649

Help

Our chat
Points of contact:

@carlspring
@sbespalov
@steve-todorov

@carlspring Can I work on this issue? If so, could you clarify how to run the database locally to check the timezone?

@carlspring I would like to help with this one... if it's still up for grabs 😃

Go for it!

authors: AricMonary SolangeUG carlspring sbespalov

repo: strongbox/strongbox


text:
Added uzbek language

I began to translate into Uzbek

Thanks @WebStyle !  In case you haven't seen https://strongloop.com/strongblog/express-goes-global/ we are going to soon have professional translations for some languages.  Since Uzbek is not among them, we will gratefully accept your contribution.
We had to restructure the repo somewhat to accommodate the professional translation handoff, but I think we can probably merge this... @hacksparrow is there any reason why we can't merge this now?  Or should we wait til merging the i18n branch?

@crandmck I wanted to stabilize the i18n branch first.
I am getting "WebStyle wants to merge 7 commits into strongloop:gh-pages from unknown repository". @WebStyle did you delete your repo? I am not sure what's going on.

Duplicate of #514. Closing this.

authors: WebStyle crandmck hacksparrow


text:
Officially support Angular 16

https://blog.angular.io/angular-v16-is-here-4d7a28ec680d
We should see if we support everything that is new there:

[ ] ESBuild + Vite
[ ] Experimental Jest support
[ ] Add "jest" as an option for stryker init when the user chooses angular.

We cannot support the official Angular jest way of working until https://github.com/angular/angular-cli/issues/25434 is implemented.

repo: stryker-mutator/stryker-js


text:
Changing label on AppGroup Queue

This change allowed this metric to function when having multiple Rails applications running on the same server.
Related to issue - https://github.com/stuartnelson3/passenger_exporter/issues/8

@phenom5886 I have a very similar patch I had to roll when we added an additional queue - it would be the following diff instead - how do you feel about that?  We are running this in production currently and I would love to get this upstreamed by @stuartnelson3.  If you like this you can either pull it into this PR or I can roll a separate PR from my fork.  Thoughts?
diff --git a/main.go b/main.go
index a7f7512..5db7da9 100644
--- a/main.go
+++ b/main.go
@@ -53,6 +53,7 @@ type Exporter struct {

        // App metrics.
        appQueue         *prometheus.Desc
+       appGroupQueue    *prometheus.Desc
        appProcsSpawning *prometheus.Desc

        // Process metrics.
@@ -110,6 +111,12 @@ func NewExporter(cmd string, timeout time.Duration) *Exporter {
                        []string{"name"},
                        nil,
                ),
+               appGroupQueue: prometheus.NewDesc(
+                       prometheus.BuildFQName(namespace, "", "app_group_queue"),
+                       "Number of requests in app group process queues.",
+                       []string{"group", "default"},
+                       nil,
+               ),
                appProcsSpawning: prometheus.NewDesc(
                        prometheus.BuildFQName(namespace, "", "app_procs_spawning"),
                        "Number of processes spawning.",
@@ -159,6 +166,8 @@ func (e *Exporter) Collect(ch chan<- prometheus.Metric) {
                ch <- prometheus.MustNewConstMetric(e.appQueue, prometheus.GaugeValue, parseFloat(sg.RequestsInQueue), sg.Name)
                ch <- prometheus.MustNewConstMetric(e.appProcsSpawning, prometheus.GaugeValue, parseFloat(sg.Group.ProcessesSpawning), sg.Name)

+               ch <- prometheus.MustNewConstMetric(e.appGroupQueue, prometheus.GaugeValue, parseFloat(sg.Group.GetWaitListSize), sg.Group.Name, sg.Group.Default)
+
                // Update process identifiers map.
                processIdentifiers = updateProcesses(processIdentifiers, sg.Group.Processes)
                for _, proc := range sg.Group.Processes {
@@ -214,6 +223,7 @@ func (e *Exporter) Describe(ch chan<- *prometheus.Desc) {
        ch <- e.currentProcessCount
        ch <- e.appCount
        ch <- e.appQueue
+       ch <- e.appGroupQueue
        ch <- e.appProcsSpawning
        ch <- e.requestsProcessed
        ch <- e.procStartTime

hey @stuartnelson3 - I know you aren't so actively working on this or maintaining this project but I think we have a couple of changes (mine or @phenom5886 ) - mine is in production today and I'd really love this upstream to be the source of truth.

Ah, I missed this ages ago and never got back to it!
I'm more than happy to add these changes.
@daveworth would it be sufficient to merge this PR for you? Or do you need your patch as well?

I've tested the changes in this PR (not the patch by @daveworth ) and it seems to work fine. (This was tested in my dev env not in production).

ah - and I missed your response @stuartnelson3
I need my patch if that's possible - I think it would also solve @phenom5886 's issue.  Would you like a separate PR for that?  I can make that happen later today. /cc @rwky

@daveworth sorry for the long delay, yeah open a separate PR and we can move this ahead.

@stuartnelson3 - done in #13!  Thank you!


text:
Absences, tardies + discipline incidents not displayed on school overview page.

This data is displayed on the student profile page, but right now, no school overview page in production has any of these events.
I think this is a data issue because it's only in production.
Is this the same issue as #673? I'm confused.

@erose Yes, I think this is a duplicate of #673.  My initial understanding is that no students should have any absences, tardies or discipline incidents yet since school doesn't start until Thursday :)  So I believe the profile pages are calculating the year cutoff incorrectly, leading to the inconsistency between the two views.
It could be a data issue, and you could verify that by picking one student that has a disrepancy and then seeing what's in the database via a Rails console.  This issue won't show up the same way in development though since the data is artificially generated, but a useful comparison for debugging might be the profile page for https://somerville-teacher-tool-demo.herokuapp.com/students/42 and then how that student looks on the overview: https://somerville-teacher-tool-demo.herokuapp.com/schools/brn#range%3Adiscipline_incidents_count%3A3%3A6, which I suspect is the same bug.

Oh, of course. Brain fart --> I forgot that overview page displays for the current school year only.

authors: erose kevinrobinson

repo: studentinsights/studentinsights


text:
How should we handle errors?

Here’s a scenario:
I’m running dox | doxie --output. It makes no sense, because doxie.output concatenates and prints the output of chunks. But the chunks only have data, and no output – you need something like doxie.template to render output.
So doxie.output would like to tell the user something like
[doxie.output] Warning: Output is empty. Perhaps you’ve forgotten to render
your comments? http://npm.im/doxie.template might put you on the right track.

It’s easy on the command line – just output this to stderr. But how about the programmatic API? Perhaps instead of the current simple data handling we should switch to something like:
import doxie from 'doxie-core'

const myData = [
  {isPrivate: false},
  {isPrivate: true},
  {isPrivate: false},
];

doxie([])(myData);

//» {
//»   chunks:  [
//»     {data: {isPrivate: false}},
//»     {data: {isPrivate: true}},
//»     {data: {isPrivate: false}},
//»   ],
//»   error: null,
//» }

CC: @stoeffel

:+1:

Thanks! Closing this then – we keep rolling this in #4.

authors: stoeffel tomekwi


text:
:lock: rm some secret info

update demo notebook

@stulzq can u help me merge this pr, this pr remove some information about my company assets

Ok

authors: stulzq warjiang

repo: stulzq/azure-openai-proxy


text:
Python 3.12 support

Would it be possible to support python 3.12?

Hi @david-zwicker
Sure, just became available.

Thanks! That's a lightning-fast response!

authors: david-zwicker styfenschaer

repo: styfenschaer/rocket-fft


text:
Docs generating duplicates

Something about the way we are organizing things is causing JSDoc to create multiple copies of the same documentation within a module. I suspect it has something to do with how we are grouping things under modules.

Addressed by #37

repo: styled-components/polished


text:
Order of CSS injection

Just hit a problem:
const SVG = styled.svg`
  line {
    stroke-width: 1px;
  }
`

const Horizontal = styled.g`
  line {
    shape-rendering:crispEdges;
  }
`

const Vertical = styled.g`
  line {
    stroke-width: 1.5px;
  }
`

export default () => (
  <SVG>
    <Horizontal>
      <line x1={0} y1={0} x2={width} y2={0}/>
    </Horizontal>
    <Vertical>
      <line x1={0} y1={0} x2={width} y2={height}/>
    </Vertical>
  </SVG>
)

Because Horizontal and Vertical get rendered before SVG, and I'm only injecting the styles on render, ._compile_from_Vertical line {} appears before ._compiled_from_SVG line {}. They have the same specificity of course and so SVG wins.
Injected source should be in the same order it is written, not in the order it's rendered.

The above demo works now because of #29 but this one doesn't:
import styled from 'styled-components'

const Outer = styled.div`
  padding: 1rem;
  p {
    color: red;
  }
`

const Inner = styled.div`
  p {
    color: blue;
  }
`

const AlternateInner = styled(Inner)`
  p {
    color: green;
  }
`

export default () => (

    {/* This causes AlternateInner to be rendered, then Inner */}
    <AlternateInner/>
    {/* Then outer gets rendered, overwriting both of them */}
    <Outer>

This should be red

      <Inner>

This should be blue

      </Inner>
      <AlternateInner>

This should be green

      </AlternateInner>
    </Outer>

)

If you drop the initial <AlternateInner/> it works:
export default () => (

    <Outer>

This should be red

      <Inner>

This should be blue

      </Inner>
      <AlternateInner>

This should be green

      </AlternateInner>
    </Outer>

)

This is... going to be a pain to fix.

Simpler example not using descendant tag selectors since those are going to hurt no matter what:
const Outer = styled.div`
  padding: 1rem;
  color: red;
`

const Inner = styled.div`
  color: blue;
`

const AlternateInner = styled(Inner)`
  color: green;
`

export default () => (

    <AlternateInner/>
    <Outer>
      This should be red
      <Inner>
        This should be blue
      </Inner>
      <AlternateInner>
        This should be green
      </AlternateInner>
    </Outer>

)

Again, commenting out <AlternateInner/> makes it work.

Ah, I think componentDidUpdate will fire in the right order. So maybe we have to defer injection of the CSS until that point.

So maybe we have to defer injection of the CSS until [componentDidUpdate]

Hmm, sounds like that might introduce flashes of unstyled content?

I just implemented it, it doesn't seem to. I think we're good.

The idea being that if you called styled(X) then Xs styles are injected before your own. That's the same guarantee composes gives you in CSS Modules.

Wouldn't that break in this case?
const Comp = styled.something`
styles: here;
`;

const SomeOtherComp = styled(Comp)`
styles: overridden;
`;

// …

<SomeOtherComp>
  <SomeComp />
</SomeOtherComp>

Nope, that should be fine.

Interesting, by fixing the more complex case we break the original case :/
Test cases:
const SVG = styled.svg`
  line {
    stroke-width: 4px;
  }
`

const Vertical = styled.g`
  line {
    stroke-width: 1px;
  }
`

export default () => (
  <SVG>
    <line x1={10} y1={10} x2={90} y2={10}/>
    <Vertical>
      <line x1={10} y1={10} x2={90} y2={90}/>
    </Vertical>
  </SVG>
)

const Outer = styled.div`
  padding: 1rem;
  color: red;
`

const Inner = styled.p`
  color: blue;
`

const AlternateInner = styled(Inner)`
  color: green;
`

export default () => (

    <AlternateInner/>
    <Outer>
      This should be red
      <Inner>
        This should be blue
      </Inner>
      <AlternateInner>
        This should be green
      </AlternateInner>
    </Outer>

)

If we inject the CSS during componentWillReceiveProps we get CSS injected as Components get rendered:

If we wait until componentDidUpdate we get:

So... I think we need to actually go off the source order of the style.tagName calls then inject the CSS into that spot. Having a separate style tag for each one would work, but 😱😱😱

Mind you, the only reason that SVG example breaks is because there are two descendant tag selectors (which is not good practice), so I'm going to ship the version that works for const AlternateInner = styled(Inner) (i.e. componentDidUpdate).
I did just confirm that if the styles have the right specificity then the picture is right for both examples:

I did that by repeating the class selectors N times where N is the order of their definition. But we can't do that in production, so we have to insert rules out-of-order. Glamor can't do that at the moment, and I'm a bit worried about the pef implications (one rule injected at the top could invalidate A LOT of styles). But if I can figure out some other approach I will.

Woo, found a manual escape hatch:
const Vertical = styled.g`
  && line {
    stroke-width: 1px;
  }
`

This generates .xxx.xxx line which lifts its specificity above .yyy line (from SVG above), so tbh I think this is "good enough" to consider this option closed.
In fact you can actually use && { some: thing; } to target the element itself (not just descendants). In case you have some greedy rules outside (like html p) which would override a styled.p with a single class name. This is great, since we don't have to design good JS to cover bad CSS, we can just give folks a way to generate even worse CSS 👍

&& ≈≈ aphrodite/important – I like it!

So this didn't stay solved for long. I found that server-side rendering wasn't firing the componentDidMount, so we can't use that to inject.

https://gist.github.com/Robbiesmo.com

authors: Robbiesmo geelen mxstbr

repo: styled-components/styled-components


text:
createGlobalStyle continuously adding to the server sheet.

Environment

npx envinfo --system --binaries --npmPackages styled-components,babel-plugin-styled-components --markdown --clipboard
System:

OS: macOS 10.15.5
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 593.47 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh

Binaries:

Node: 12.18.2 - ~/.nvm/versions/node/v12.18.2/bin/node
Yarn: 1.19.1 - ~/.yarn/bin/yarn
npm: 6.14.5 - ~/.nvm/versions/node/v12.18.2/bin/npm

npmPackages:

babel-plugin-styled-components: 1.10.7 => 1.10.7
styled-components: 5.1.0 => 5.1.0

Reproduction

Steps to reproduce
Don't create a new ServerStyleSheet on each request, and watch the global styles mount up.
Actual Behavior
This is user error, but I'm posting for interest.
Context: we had a SSR-ing React application which uses styled-components. It powers https://www.sky.com/watch, amongst other pages.
const assetsHost = getAssetsHost();
const sheet = new ServerStyleSheet(); // created outside the function which is called to actually render the app.

export const renderApp = ({ App, config, appName, contextCookies = {} }) => (ctx, next) => {
  const statsFile = path.resolve(__dirname, '../../../dist/loadable-stats.json');

  const extractor = new ChunkExtractor({
    statsFile,
    entrypoints: [appName],
    publicPath: assetsHost
  });

  const component = (
    <ChunkExtractorManager extractor={extractor}>
      <StyleSheetManager sheet={sheet.instance}>
        <App
        etc.

App goes on to generate HTML and pass back to client etc..
The above code clearly doesn't follow the readme which suggested creating a new ServerStyleSheet on each page render, but interesting this came in as rising response time on the NodeJS app

Digging through that led to an increase in HTML size:

And trusty web archive led us here: view-source:http://web.archive.org/web/20200914232107/https://www.sky.com/watch
The main highlight here being the 31953 attempts to colour the background white:
body{background-color:white;}/*!sc*/
--
  | data-styled.g32027[id="sc-global-czvqin31953"]{content:"sc-global-czvqin31953,"}/*!sc*/

The last release we did which caused this to creep up starts using createGlobalStyle, but the offending code had been around in production way before that.
A fix is landing shortly to create a fresh sheet each time, but in the meantime, is it expected that createGlobalStyle would continuously add to the same sheet, if a fresh sheet isn't instantiated each time?

This is expected behaviour based on the reproduction steps:

Don't create a new ServerStyleSheet on each request, and watch the global styles mount up.

It's required that each render (so each request) has its own ServerStyleSheet 😅


text:
プロクシが x-forwarded-for ヘッダを付けるようにした

プロクシ経由でアクセスされるとバックエンドからはリモートアドレスが見えないので、このヘッダを使って元のリモートアドレスを通知する。

関連：https://github.com/su-its/ams-backend/pull/91

repo: su-its/ams-frontend


text:
False Positive with Running App Services

We are using JobScheduler in our app and it seems it's flagged as a container service:
com.google.android.datatransport.runtime.scheduling.jobscheduling.JobInfoSchedulerService
I know we can add it to the list of appServices but it seems like something that should be ignored by default.
Here:

Since it's running and I didn't add it to appServices, then it falsely thinks we are running a container.

@blundell  Thanks once again. I will have a look on this along with other bugs you reported.

authors: blundell su-vikas

repo: su-vikas/conbeerlib


text:
Option to add base URL to collection

It would be a nice feature to have the possibility to add a base URL to a collection. Like "https://example.com/"
Then you could just add:
"/docs"
"/users"
etc. in each request.

That's what environments and variables therein for. 😉
Create a new environment, add a variable baseURL and set its value to https://example.com.
Then set this environment to be active via its burger menu.
Then, in your request, reference the variable by writing {{baseURL}}.
For me, this works with the second time you make the request. The name of the variable (including the braces) should turn green then.

authors: krokand metawops

repo: subasraj/flashpost-support


text:
LSP-rust-analyzer broken on NixOs

LSP-rust-analyzer is appears to be broken on NixOS.
I set up my rust environment in a nix-shell, with all the necessary tools including rust-analyzer. However, when launching sublime, I am met with this error:

I'm attributing this to LSP-rust-analyzer downloading its own binary instead of using the one in PATH. Is there any way for this behavior to be changed?

When you installed LSP-rust-analyzer, were there some installation errors in the Sublime Text console(ctrl+`) ?
Can you remove and install LSP-rust-analyzer again and can check the console for errors?

I'm attributing this to LSP-rust-analyzer downloading its own binary instead of using the one in PATH. Is there any way for this behavior to be changed?

In LSP-rust-analyzer.sublime-settings, you can override the start command:
{
	"command": [
		"${storage_path}/LSP-rust-analyzer/rust-analyzer"  // change the path to your local rust-analyzer
	],
}

But I would not recommend overriding the command
because there is no guarantee that this LSP-rust-analyzer
version is compatible with rust-analyzer you have locally, so you may run into a different issues somet

The first error is from EasyClangComplete. Maybe try removing/disabling it (LSP-clang should work better anyway) and then checking if that solves the problem.

heres the logs when starting sublime with it disabled:
Unable to start subprocess for rust-analyzer
Traceback (most recent call last):
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/windows.py", line 273, in start_async
    transport = create_transport(transport_config, transport_cwd, session)
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/transports.py", line 265, in create_transport
    process = start_subprocess()
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/transports.py", line 253, in start_subprocess
    return _start_subprocess(config.command, stdin, stdout, subprocess.PIPE, startupinfo, config.env, cwd)
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/transports.py", line 339, in _start_subprocess
    cwd=cwd)
  File "./python3.3/subprocess.py", line 819, in __init__
  File "./python3.3/subprocess.py", line 1452, in _execute_child
FileNotFoundError: [Errno 2] No such file or directory: '/home/makemake/.cache/sublime-text/Package Storage/LSP-rust-analyzer/rust-analyzer'

Unable to start subprocess for rust-analyzer
Traceback (most recent call last):
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/windows.py", line 273, in start_async
    transport = create_transport(transport_config, transport_cwd, session)
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/transports.py", line 265, in create_transport
    process = start_subprocess()
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/transports.py", line 253, in start_subprocess
    return _start_subprocess(config.command, stdin, stdout, subprocess.PIPE, startupinfo, config.env, cwd)
  File "/home/makemake/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/transports.py", line 339, in _start_subprocess
    cwd=cwd)
  File "./python3.3/subprocess.py", line 819, in __init__
  File "./python3.3/subprocess.py", line 1452, in _execute_child
FileNotFoundError: [Errno 2] No such file or directory: '/home/makemake/.cache/sublime-text/Package Storage/LSP-rust-analyzer/rust-analyzer'

@makemake-kbo
Can you verify that this binary file exist /home/makemake/.cache/sublime-text/Package Storage/LSP-rust-analyzer/rust-analyzer ?
The file must exist if LSP-rust-analyzer installs successfully.

@predragnikolic
looks like it is
file /home/makemake/.cache/sublime-text/Package\ Storage/LSP-rust-analyzer/rust-analyzer
/home/makemake/.cache/sublime-text/Package Storage/LSP-rust-analyzer/rust-analyzer: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=4cb9801d931e886ce8110ee6af8892ce8c77f2c7, with debug_info, not stripped

ls -la /home/makemake/.cache/sublime-text/Package\ Storage/LSP-rust-analyzer/
total 43376
drwxr-xr-x 2 makemake users     4096 Feb 26 12:48 .
drwxrwxr-x 7 makemake users     4096 Feb 26 12:48 ..
-rwxr--r-- 1 makemake users 44402448 Feb 26 12:48 rust-analyzer
-rw-r--r-- 1 makemake users       10 Feb 26 12:48 VERSION

maybe related to permissions (the makemake user is not the one used when starting from ST)?

Maybe found the cause:
https://nixos.wiki/wiki/Packaging/Binaries

Downloading and attempting to run a binary on NixOS will almost never work. This is due to hard-coded paths in the executable.

Other editors faced the same issue in NixOS
https://discourse.nixos.org/t/nix-shell-and-rust-and-rust-analyzer/13940/2
I do not understand or know NixOS to suggest a solution to you.

Thank you all for the useful info! If i find a solution ill come back and post it.

authors: makemake-kbo predragnikolic rchl

repo: sublimelsp/LSP-rust-analyzer


text:
Are you planning to support golang as a supported WASM lang ?

asked on discord but no one was around, so asking here :)
so far i really like the architecture of suborbital. Its elegantly simple ( SUFU) for sure...

Yes! Go support is certainly planned, likely via the TinyGo project.
There is already a Subo issue to support building it: https://github.com/suborbital/subo/issues/6

repo: suborbital/reactr


text:
Add binaries to sat/constd releases with GoReleaser

Adds Linux and Darwin amd/arm64 binaries to the releases with GoReleaser
Adds a new workflow to release the binaries
Updates actions to v3 if available
Adds Go mods caching to speed up actions

LGTM!

authors: arbourd cohix

repo: suborbital/sat


text:
Implements TAP TODO directive

Fixes #219 as discussed with @awlayton

Please revert all the whitespace changes - that's a part of this project's style.

@ronkorving wrt test/comment.js failing - what version of node are you using? It passes for me on my OSX machine.

I've tried on both Node 4.3.0 and 5.6.0, and comment.js fails. I'll make a separate issue in a bit.
Re. whitespace, it may be useful then to add a http://editorconfig.org file. That would make it much easier to contribute.

All whitespace changes have been reverted.

As mentioned in #219 , a very warm and welcome +1 for this.

(fixed the test/comment.js tests in 40be68520fedee580462bfaa7e91651154a65bea btw)

Appreciated :) (to both of you)

Shouldn't you also add a test.todo since there is a test.skip?

+1 on test.todo (and the associated documentation)

👍

@ljharb Done 👍

authors: awlayton axit-joost gabrielcsapo ljharb ronkorving

repo: substack/tape