Updating source code doesn't auto compile

npm start will start the server and run the react app. But if I edit the source code it doesn't update on the browser even I refresh the page (In your Udemy course it update the browser on refresh) . How to fix this ? (I need like nodemon for node)

@pankaja92 can you give a bit more context? what version of node do you have? did you run npm install? when you edit your source code, is the node server running?

Same problem from me. I have node v8.9.3 and I have run npm install. To update the code, I had to ctrl+c in cmd and rerun npm run start.

Same issue for me. Node 8.11.1, Npm 5.6.0


move the kernel headers and extras images to os repo

Signed-off-by: Sven Dowideit<EMAIL_ADDRESS>initially moving the kernel image builds into the os repo from https://github.com/rancher/os-images/pull/114
later will contemplate if they should move to os-kernel.
see https://github.com/rancher/os-images/pull/114

Do you really want to do this in two steps? Can we just move directly to os-kernel and change the services to not download from GitHub.

yeah, i do want to do this in 2 steps - I'm not totally convinced that adding image building to every repo is worth it.


Exchange rate as worker task

@SchrodingersGat I hope this is the way it was intended to be run as a task.
I added a generic function to run task either by the worker cluster or as a blocker.
Let me know what do you think.
Now anybody can add a method to the InvenTree/tasks.py file and run it using the worker cluster simply with:
from InvenTree.tasks import run_task

# 'blabla' method needs to be implemented in InvenTree/tasks.py
run_task('blabla')

I've tested it with update_exchange_rates method and it runs fine both by the cluster and as blocker.

@eeintech what's the intended use here? The currency rates are already updated periodically by the background worker, and I think it is better to leave the process "blocking" here so that the server responds with the latest values.

Maybe update_exchange_rates is not the best use for it but, as said in the PR description, this is a helper function to make it easy to run tasks from anywhere? That way when more and more tasks methods are implemented, there wouldn't be too much overhead in each call.
I guess you are suggesting a way to force use of blocking vs using the cluster?

Is this functionally different from the existing offload_task function?
https://github.com/inventree/InvenTree/blob/529742b5203005d5d71921c1ee32cd1bc540af4d/InvenTree/InvenTree/tasks.py#L54

@SchrodingersGat I guess I kinda overlooked offload_task however I think this one will error out if:

function defined by taskname does not exist
if there are no workers running, it might just stay in the queue forever and the user won't know

In run_task I am handling those two checks:

if the task function does not exist or is not found in tasks.py, user gets a warning
if workers are not running, the task is run synchronously

Do you want me to re-use offload_task and add the checks there?

if workers are not running, the task is run synchronously

This would be a good addition to the offload_task function, to ensure that the function does actually get run even if the background worker is not active.

if the task function does not exist or is not found in tasks.py, user gets a warning

Makes sense to add to offload_task too.

@SchrodingersGat Take a look at the updated offload_task code which includes the two checks. Now running update_exchange_rates synchronously using force_sync option :+1:
Should be good to merge, I'm actually starting to look how can we use workers for distributor API, starting with Digi-Key.
Digi-Key unfortunately does not provide any permanent token so I'm hoping we can get a worker to keep on refreshing the token in the background every hour or so and don't have to go through the app authorization phase again.

Yeah this looks pretty solid now! Thanks @eeintech


only show first lib match to reduce vverbose output noise

closes #1174
results in

Checklist

[ ] No CHANGELOG update needed

[ ] No new tests needed

[ ] No documentation update needed

overall, i think this is a great solution!
some nits about wording and rendering...

there's only one match, so the comment isn't very relevant
does a typical user know what a "lib" is and how its relevant? could we get away with not actually referencing "lib"? e.g.:
open process (3 matches, only showing first)
...

we should not display the "namespace" row for lib rules

Great points, I'll address these.

How about this?

beautiful

now looks like this:


GBA fast forward above 2x

I have changed the fast forward to 8x and 10 and tried each gba port. They seem to top out at 2x fast forward. Any way to be able to increase the speed further?

Not that I'm aware of unfortunately.  It's either a limit of the mgba core or a limit of the hardware.


openapi2cscontroller POST requestBody name of property not reflected

example of yaml
  /docs:
    post:
      tags:
        - docs
      operationId: createdoc
      responses:
 ... not inculded for brevity
      parameters: []
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                someName:
                  format: binary
                  type: string

generated c#:
public async Task<ActionResult<int>> DocsPostAsync(IFormFile body) {...}

expected:
public async Task<ActionResult<int>> DocsPostAsync(IFormFile someName) {...}

can you please fix ?

seems like a dup of #2293


FAQs line appears in Contact Us Modal even if there are no FAQs

See https://thor.dosomething.org/us/campaigns/shower-songs as an example
Refs: #6062 and #6091

May need to view as a non-admin to see the line?

just verified with @katiecrane ^ being an admin blocks this bug from happening on thor, however on local it doesn't make a difference for me. just pulled the latest changes ~5 minutes ago

For me it was happening only for non-admins, but I just submitted a PR to fix it for all users


fix add homeAccountId  tolowercase in updateOutdatedCachedAccount

the getAccountKeys() get the key in lowerCase so we  have to set the homeAccountId to lowerCase() to match both.

any news?


📦 Install default g++ instead of specific version

Installing the default version should more closely emulate what end users of this library would experience. G++ 4.8.x was last updated in 2015, and the current major version is 9.x.

The default version of the g++ package in the Travis CI ubuntu-toolchain-r-test apt repo is 5.4.0, which is only about a year (2016) more current than v4.8 (2015). It's still an iterative improvement over hard-coding a dependency on a g++ version that is becoming less likely to match what end-users will actually have installed.


Why can't we watch Dtube videos directly on esteem-surfer?

It would be great to watch dtube videos directly in esteem (as in busy.org) instead of opening the browser!
I also notice that I can watch them on android version

@em3di for security reasons we limited video (iframe) resources to youtube and vimeo like steemit does. We are doing same on new version of mobile app.


[txservice] Hotfix: remove intermediary type TransactionError

The Problem

The Solution

Checklist

[ ] Test manually on test-ui using remote chains.
[ ] Run load tests.
[ ] Update documentation if needed.
[ ] Update CHANGELOG.md.

Not sure if this is ready to merge, last time I got in trouble by merging one of your PRs prematurely. Go ahead and merge when it's ready.


added instruction to install cssmin

The CSSMin compressor code supports all the cssmin implementations out there.
If you're using the python one, you might want to use [your very own implementation](import cssmin), using cssmin functions directly rather than calling a binary.
Thanks a lot for the suggestions!


[bug] Only one workload is included in compose output

Describe the bug
If I have a score.yaml file which defines two workloads, only one workload is included in the output of score-compose
To Reproduce
Steps to reproduce the behavior:

Create a score.yaml file like the following:

apiVersion: score.dev/v1b1

metadata:
  name: app

service:
  ports:
    api:
      port: 80
      targetPort: 3000
    frontend:
      port: 8080
      targetPort: 3000

containers:
  api:
    image: api:latest
  frontend:
    image: frontend:latest

run score-compose:

services:
  app:
    image: frontend:latest
    ports:
      - target: 3000
        published: "80"
      - target: 3000
        published: "8080"

Expected behavior
Both containers should be created and ports should be applied to the correct container.
score-helm seems to work correctly:
containers:
  api:
    image:
      name: api:latest
  frontend:
    image:
      name: frontend:latest
service:
  ports:
    - name: api
      port: 80
      targetPort: 3000
    - name: frontend
      port: 8080
      targetPort: 3000
  type: ClusterIP

Desktop (please complete the following information):

OS: macOS Ventura 13.0
Version: score-compose 0.1.0 (build: 2022-10-17T09:17:36Z; sha: ef20200fa8357ef8dbffbed38f3de53ebdc2d9c2)

@williamoverton Just had a chat with Eugene and this is actually a feature. score-compose does not support more than one container per workload. Feel free to reach out to him to discuss this in more detail. Will close the issue for now.

Aiming to solve this in https://github.com/score-spec/score-compose/pull/46 which should ensure services get setup for all containers 👍


create download button to download metadata in blocks

Fixes #3222

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

I created a hyperlink tag in the Blockdetails component to act as a download button
I created a helper that returns the URL from the block metadata

Verification
The below screenshots show how it works
See download button and click on it

Receive the prompt to download file

view file after downloading

@prmsrswt I need help with the markdown link check? I do not understand why it is failing

@Oghenebrume50 Sorry, please ignore this error first. I opened a pr to fix it in https://github.com/thanos-io/thanos/pull/3282.

@Oghenebrume50 Sorry, please ignore this error first. I opened a pr to fix it in #3282.

Hi thank you, there seems to be other test failing now though, and I do not think they are related to the markdown links, I also have zero idea how to fix them.

Everything works fine now once I merged the new changes from master into the branch,  I also updated the screenshot of how the json file looks when viewed. @prmsrswt @yeya24


[Bug]: fix android studio beta checkver & updateurl

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
android-studio-beta
Expected/Current Behaviour
Android Studio Beta version is very old, about a year
Steps to Reproduce
scoop install versions/android-studio-beta
Installing 'android-studio-beta' (2<IP_ADDRESS>) [64bit] from 'versions' bucket
android-studio-2<IP_ADDRESS>-windows.zip (952,8 MB) [===============================================================================] 100%
Checking hash of android-studio-2<IP_ADDRESS>-windows.zip ... ok.
Extracting android-studio-2<IP_ADDRESS>-windows.zip ... done.
Linking ~\scoop\apps\android-studio-beta\current => ~\scoop\apps\android-studio-beta\2<IP_ADDRESS>
Creating shortcut for Android Studio Beta (studio64.exe)
'android-studio-beta' (2<IP_ADDRESS>) was installed successfully!
'android-studio-beta' suggests installing 'android-clt'.

Possible Solution
Update checkver regex
Update download urls
Scoop and Buckets Version
Current Scoop version:
d285bb08 (HEAD -> master, tag: v0.4.1, origin/master, origin/HEAD) chore(release): Bump to version 0.4.1 (#5924)

'main' bucket:
9952f90b6 (HEAD -> master, origin/master, origin/HEAD) supabase: Update to version 1.163.6

'extras' bucket:
ece511d3f (HEAD -> master, origin/master, origin/HEAD<EMAIL_ADDRESS>Fix hash (Closes #13184)

'versions' bucket:
189be6cbe (HEAD -> master, origin/master, origin/HEAD) okular-nightly: Update to version 4834

Scoop Config
scoop config

last_update        scoop_branch scoop_repo
-----------        ------------ ----------
27.04.2024 1:28:26 master       https://github.com/ScoopInstaller/Scoop

PowerShell Version
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.4.2
PSEdition                      Core
GitCommitId                    7.4.2
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
No response

+1


Fix Text in README

PR Description 📜
I have changed this sentence in README:

This open source repository contains collection of games build on basic tech stacks in web development . Use your creativity and build your own game and contribute to the repository by making PR

to:

This open source repository contains a collection of games built on basic tech stacks in web development. Use your creativity, build your own game and contribute to the repository by making a PR

Fixes #607
This PR is part of GSSoC'23.

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.

Thank you soo much for contributing to our repository 💗

Thank you @Sriparno08 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @Sriparno08 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Fix issue 673 trailing spaces of cell values lost

@larshp This fix is rejected because of lint check:

Statement does not exist in ABAPv702(or a parser error), "IF".

Concerned code is:
      IF contains( val = <fs_sheet_string>-string_value start = ` ` )
            OR contains( val = <fs_sheet_string>-string_value end = ` ` ).

I guess that "contains" predicate function was added in 7.02? Or am I wrong? Thanks.

@larshp Urgent. Coming back to adding = abap_true to IF contains( ... ) (predicate function), I get a short dump/syntax error in my 7.52SP0/7.52SP1 systems (optionally could be solved by wrapping with boolc (IF boolc( contains( ... ) ) = abap_true ).:

Yup, HANA1909, same error.

@AndreaBorgia-Abo Could you check the corrective PR #812 please? (it sounds just stupid to have overcomplex statement IF boolc( contains( ... ) ) = abap_true for now, but works at least/until confirmation by @larshp)

Thanks @AndreaBorgia-Abo 😀 (I'm feeling less guilty 😓)


chore(master): release 1.1.91

:robot: I have created a release beep boop
1.1.91 (2023-06-26)
Miscellaneous

deps: update pnpm to v8.6.4 (429bf72)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.91 :sunflower:


refactor: Simplify sessions conversions queries

Description & motivation
Similar to #82. To avoid 'Resources exceeded during query execution: Not enough resources for query planning - too many subqueries or query is too complex.' errors.
Checklist

[x] I have verified that these changes work locally
[n/a] I have updated the README.md (if applicable)
[n/a] I have added tests & descriptions to my models (and macros if applicable)
[x] I have run dbt test and python -m pytest . to validate exists tests

I was going for whoever writes the most CTEs wins, but I guess we can do it your way

Right, I'll try and top up the CTEs elsewhere for parity :)


Remove deprecation warnings from marshmallow

This PR removes the RemovedInMarshmallow4Warning warning by updating the code to the new interface of marshmallow.Field.
It was necessary to wrap parameters (load_from, data_key, dump_to) into a dictionary to give to the parameter metadata.

Related to https://github.com/inveniosoftware/invenio-app-rdm/issues/1112

LGTM. tests should pass after #206 has been integrated and this branch has been rebased

@utnapischtim or @rekt-hard: Do you mind rebasing the PR so we can merge.


fix: correct URL to view pipeline after publish

I referred below link to set correct repo name.
https://circleci.com/docs2/2.0/env-vars#built-in-environment-variables

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:b28775abca733a2f36b92ba198b8ed1717cc9144


[BEAM-4060] Add the pom.xml and pom.properties file to the artifact when publishing

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

I don't believe so since three people mentioned that it was important on the dev@ list.


Hybrid EKS cluster with windows and linux worker nodes

Hello,
We have an eks cluster which includes both windows and linux worker nodes.   I have the following questions:

Can I enable both Fluentd log engine for Linux worker nodes and Otel log engine for windows worker nodes?  If this is not supported, how can I index logs from both linux and windows worker nodes in the same EKS cluster?
I tried deploying the 0.41.1 version of the chart with the following values.yaml overrides:

logsEngine: otel
cloudProvider: "aws"
distribution: "eks"
autodetect:
prometheus: false
istio: false
agent:
enabled: true
securityContext:
windowsOptions:
runAsUserName: "ContainerUser"
fluentd:
securityContext:
runAsUser: 0
clusterReceiver:
enabled: true
logsCollection:
containers:
enabled: true
checkpointPath: "/var/addon/splunk/otel_pos"
image:
fluentd:
repository: <private_cache_repo>/splunk/fluentd-hec
otelcol:
repository: <private_cache_repo>/signalfx/splunk-otel-collector-windows
isWindows: true
nodeSelector:
kubernetes.io/os: windows
With the above overrides, The Splunk-otel container on windows fails to start with the following error:
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.
failed to try resolving symlinks in path "\var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log": CreateFile \var\log\pods\observability_splunk-logging-splunk-otel-collector-agent-hwwjb_c71ea1ae-4066-4d0b-80f5-0bfec70478e3\copy-old-checkpoint\8.log: The system cannot find the file specified.

Hi @vinitmasaun! I believe you need to have 2 deployments. One with isWindows: true and one with isWindows: false. Also, make sure to set clusterReceiver.enabled: false for one of the deployments.

@matthewmodestino provided the correct way to deploy the chart in the mixed environment, but it'll work for metrics and traces only. We don't support collection logs from Windows nodes at this point, this is coming soon.

We have docs for Windows here (should be probably moved to docs/advanced-configuration.md): https://github.com/signalfx/splunk-otel-collector-chart/blob/main/examples/README.md#deploy-for-k8s-cluster-with-windows-worker-node

Thank you Dmitrii.  Is there a timeline for when windows logs will be supported?  Is there an experimental branch that I could try out that has this support?
Ratings-Monitoring SNOW Requesthttps://spglobal.service-now.com/spg?id=sc_cat_item&sys_id=4ac3d42d1b9bf494966da977bc4bcbf7&sysparm_category=3a3dd38e1bdb78d4966da977bc4bcb2b
Regards,
Vinit Masaun
Mobile:<PHONE_NUMBER>
[signature_302861727]
From: Dmitrii Anoshin @.>
Date: Tuesday, January 11, 2022 at 8:53 AM
To: signalfx/splunk-otel-collector-chart @.>
Cc: Masaun, Vinit (Associated) @.>, Mention @.>
Subject: Re: [signalfx/splunk-otel-collector-chart] Hybrid EKS cluster with windows and linux worker nodes (Issue #351)
EXTERNAL MESSAGE
@matthewmodestinohttps://github.com/matthewmodestino provided the correct way to deploy the chart in the mixed environment, but it'll work for metrics and traces only. We don't support collection logs from Windows nodes at this point, this is coming soon.
—
Reply to this email directly, view it on GitHubhttps://github.com/signalfx/splunk-otel-collector-chart/issues/351#issuecomment-1010163041, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGNC5H5BJFIYOAVBWLXYW5TUVROBRANCNFSM5LVGTSEA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.

@vinitmasaun it's roughly 1 month away

@vinitmasaun it's roughly 1 month away

thank you!  Anxiously looking forward to it!

Hey, the Windows logs collection support is added in this PR and will be available in the next release


php 8.2 session error err_empty_response

php 8.2
apache
linux
$this->session = \Config\Services::session();
err_empty_response

We use GitHub issues to track BUGS and to track approved DEVELOPMENT work packages. We use our forum to provide SUPPORT and to discuss FEATURE REQUESTS.
If you think your issue is a bug, please choose "Bug report".
https://github.com/codeigniter4/CodeIgniter4/issues/new/choose


More strict parsing of initial line / http headers

Motivation:
Our parsing of the initial line / http headers did treat some characters as separators which should better trigger an exception during parsing.
Modifications:

Tighten up parsing of the inital line by follow recommentation of RFC7230
Restrict separators to OWS for http headers
Add unit test

Result:
Stricter parsing of HTTP1

/cc @violetagg


Windows executable path no longer valid

I'm walking through the install guide and I was attempting to download the pre-compiled Windows client, but I'm getting a 404 page not found error here: https://i.botox.bz/serverstatus-client.exe

Ooops, currently not at home, but this should work: https://github.com/BotoX/ServerStatus/blob/a8963041329fd3a1d84649422bfe679309da446d/clients/windows/client.exe?raw=true

Thank You!


Very crude test for running the bytecode VM

Compile a very simple program into bytecode, run it and compare the expected output.
For now it's not part of any automated test, so you have to run the file manually.
I'm not really satisfied with the way we now have to run natalie twice within the test: once to generate the bytecode and once to run it. This could simply be kept in an internal buffer. Once we run the VM internally, we should be able to inspect the stack instead of having to depend on printing the output. (So running 2+3 should result in the number 5 on the stack without having the need to print it).

I'm not really satisfied with the way we now have to run natalie twice within the test: once to generate the bytecode and once to run it.

I want to write a test where we require 'lib/natalie/compiler' and not have to shell out, and that's what I was about to do when I realized it was painfully slow to do that. That's why I started working on #1495.

I guess we're the first programming language implementation in history to make things slower by introducing a bytecode VM 😅


nixos/binfmt: run binfmt activation script after mounting /run

Motivation for this change
binfmt activation script creates /run/binfmt before mounting /run when system activation.
Things done
I added dependency to specialfs to binfmt activation script.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

@Mic92 @matthewbauer ping


Make operator aware of supervisor-specific runtime features

It might be beneficial for users if the operator somehow exposed some information supervisor has about the service it manages. An example could be labeling pods with their election status. So at some point some pod could have a label saying that the service here is a leader. That in order could be used in a selector of a Kubernetes Service resource to expose the leader service outside the cluster.
Another thing to expose could for example be a version of the service - it would be useful for the habitat-updater.
The information can be gotten through the HTTP gateway of the supervisor, but of course not everything would be needed to be exposed as labels on Kubernetes Pods.
Also, what needs to be taken into account that it is possible for those labels to change during the lifetime of a pod and so the operator should be careful not to clobber those labels after it created them.

Can we label pods differently that are managed by same StatefulSet?


fyi,  just tried to send you some coffee and here's what happened

#
thanks for the theme :) ... let me know if you fix your account at buymeacoffe.com<EMAIL_ADDRESS>

Very strange, I just tried it and it worked fine for me. The URL looks different though. Are you taken to https://www.buymeacoffee.com/n4ho5QX2l when you click it, or redirected elsewhere? I see your URL is https://www.buymeacoffee.com/thankyou/n4ho5QX2l. How did you get this URL; is this after you've clicked "Pay $x"?
Regardless, thanks for trying to show your support! Much appreciated.

Not sure what happened, but it worked this time :). Probably my goof.
Cheers
Brent
On Dec 31, 2018, 12:41 AM -0600, Muck<EMAIL_ADDRESS>wrote:

Very strange, I just tried it and it worked fine for me. The URL looks different though. Are you taken to https://www.buymeacoffee.com/n4ho5QX2l when you click it, or redirected elsewhere? I see your URL is https://www.buymeacoffee.com/thankyou/n4ho5QX2l. How did you get this URL; is this after you've clicked "Pay $x"?
Regardless, thanks for trying to show your support! Much appreciated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks so much for the coffees, I really appreciate it!


Added CODE_OF_CONDUCT.md file

fixes: Added CODE_OF_CONDUCT.md file
refered https://github.com/99xt/serverless-dynamodb-local/edit/v1/CODE_OF_CONDUCT.md

@amilabgunarathne Thanks 👍

Happy to have it bro👍
On Aug 22, 2017 8:55 AM, "Rumesh Eranga Hapuarachchi" <
<EMAIL_ADDRESS>wrote:

@amilabgunarathne https://github.com/amilabgunarathne Thanks 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/99xt/earnshark-sdk-dot-net/pull/16#issuecomment-323908869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXHXMXr7pTwNYUC9_KtkTk-Dk8pL4BrHks5sakoogaJpZM4O88AB
.

fixed #13


[PROPOSAL] api: Introduce OpenAPI generated Alertmanager API V2

The current Alertmanager API v1 is undocumented and written by hand.
This patch proposes a new Alertmanager API - v2. The API is fully
generated via an OpenAPI 2.0 [1] specification (see
api/v2/openapi.yaml).
Pros:

Generated server code
Ability to generate clients in all major languages
(Go, Java, JS, Python, Ruby, Haskell, elm [3] ...)

Strict contract (OpenAPI spec) between server and clients.
Instant feedback on frontend-breaking changes, due to strictly
typed frontend language elm.

Generated documentation (See Alertmanager online Swagger UI [4])

Cons:

Dependency on open api ecosystem including go-swagger [2]

Please be aware of the fact that this is a proof of concept implementation
and is not intended to be merged yet.
I am welcoming any kind of feedback, suggestions or proposals.
[1]
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
[2] https://github.com/go-swagger/go-swagger/
[3] https://github.com/ahultgren/swagger-elm
[4]
http://petstore.swagger.io/?url=https://raw.githubusercontent.com/mxinden/alertmanager/apiv2/api/v2/openapi.yaml

Link to Prometheus developers Google group discussion: https://groups.google.com/forum/#!topic/prometheus-developers/2CCuFTMbmAg

@stuartnelson3 @simonpasquier @brian-brazil @brancz @squat would you mind taking a look at this proposal? Most of these changes are either vendored or auto-generated code.
 All follow up commits are related to documentation, testing and basic refactoring.
Unfortunately GitHub collapses api/v2/api.go by default, which is the heart of the new API and not auto-generated.
Very much looking forward to your feedback. Let me know if you need a more detailed description for a code review. To understand the structure, the online Swagger UI of the Alertmanager API Spec is probably a good start.

Very much looking forward to your feedback. Let me know if you need a more detailed description for a code review. To understand the structure, the online Swagger UI of the Alertmanager API Spec is probably a good start.

This alone instantly makes me like it :)
Will take a look soon. I haven't looked at the schedule, but this might also be something worth discussing at the dev summit the day after promcon

Will take a look soon. I haven't looked at the schedule, but this might also be something worth discussing at the dev summit the day after promcon

Already added it to the list @stuartnelson3.

Thanks @brian-brazil for looking over this!

Might silencedby/inhibited by be something we wish to remove on performance grounds in the future?

Have you hit concrete performance issues in the Marker logic? Can you add some more details?

On the other hand apparently there's extra XSRF-related protections for PUT/DELETE that don't apply to POST

Can you reference some further documentation on this matter here?

The generatorURL may not actually be a URI, I'd leave it as a string.

In which cases is the generatorURL not a URI? If so, we should rename the parameter?

Matchers are strings in input, and structs as output. This is [in]consistent.

Are you referring to the GET /alerts?filter parameter?
According to the OpenAPI 2.0 spec:

Query parameters only support primitive types. You can have an array, but the items must be a primitive value type. Objects are not supported.

So we could represent matchers as an array of strings, but not as objects. What do you think? Representation as an array of strings sounds better than a single string to me.

Have you hit concrete performance issues in the Marker logic? Can you add some more details?

No, but I can imagine us wanting to remove this in the future if we changed the implementation. Once this is here removing it could be difficult.

Can you reference some further documentation on this matter here?

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#Functional_overview

In which cases is the generatorURL not a URI? If so, we should rename the parameter?

When the alertmanager client doesn't pass a URL. It shouldn't happen, but it's not as if we're validating it when it comes in. Renaming it would be a breaking change, and it is usually a URL.

Are you referring to the GET /alerts?filter parameter?

Yes.

Have you hit concrete performance issues in the Marker logic? Can you add some more details?

No, but I can imagine us wanting to remove this in the future if we changed the implementation. Once this is here removing it could be difficult.

I am voting for keeping the silencedby and inhibited properties for now with the risk that we might have to make a breaking change at some point when we refactor the Marker logic. Much of the current UI depends on it, which I would like to port over to API v2 as a follow up to this.
Any thoughts by others on this?

In which cases is the generatorURL not a URI? If so, we should rename the parameter?

When the alertmanager client doesn't pass a URL. It shouldn't happen, but it's not as if we're validating it when it comes in. Renaming it would be a breaking change, and it is usually a URL.

As this is only enforced by the API v2, we can include the validations once we port Alertmanager client and UI over to API v2, if the validations are not already auto-generated in the first place.

As this is only enforced by the API v2, we can include the validations once we port Alertmanager client and UI over to API v2, if the validations are not already auto-generated in the first place.

My point is that adding validation would be a breaking change, and I think that we shouldn't break it.

@stuartnelson3 @simonpasquier @brancz @squat friendly ping - PR looking for review.

Generally this looks good to me and a step forward in all directions. (I didn't review all the generated code, but parts of it and it seems reasonably readable should there ever be a problem)
That said there are still some instrumentation and structural TODOs, so I'll wait for that for a final review, but this is going in a great direction.

In case anyone else (like me) is wondering why this new API is based on the OpenAPI 2.0 spec when the 3.0.0 spec was released a year ago and the latest spec revision is OpenAPI 3.0.1:
Unfortunately, go-swaggercurrently does only support the 2.0 spec. See https://github.com/go-swagger/go-swagger/issues/1122 for details.
@mxinden Apart from that: Were there any other reasons that kept you from using the latest spec? Would you mind to share them? (Honest question, not a complaint!)

In case there are no objections I would like to delay adding proper instrumentation of the Alertmanager API v2 to a follow up PR. This PR is already big enough and there is some deeper refactoring necessary as prometheus/common/route.Router doesn't allow me to register a full handler (generated by Swagger) instead of individual endpoints.

I have addressed all outstanding TODOs.
@stuartnelson3 @simonpasquier @brian-brazil @brancz I would like to move forward here and merge into master. What are your thoughts?
This patch also touches the README.md, stating:

API v2 is still under heavy development and thereby subject to change.

Before merging I would like to squash these commits into one and rework the commit message.

Given the fact that the major version of the API changes, this breaking change seems acceptable to me.

This could break existing non-Prometheus clients of the AM, and some of them may not be running http servers to link to. It's intended primarily as a unique identifier of the source of an alert, that it is often also a URL that the user finds useful is secondary. What is the benefit of breaking this?

Introducing a v2 API sounds like the right opportunity to set this kind of thing straight. I think if we continue to call it "generatorURL" then it should be a valid URI, if we don't want this validation, then we should call it "generator" instead.

Also keep in mind that the old API, which we will continue to have to support for some time, has no such validation so non-URLs will get into the system.

I think generally I prefer the un-validated "generator", I would prefer a broken backlink over a non-accepted alert fired. And for non-Prometheus generators there could be non-URI cases as well for the generator I think (not sure this is something we would want to take into consideration though).

Something else is that this field name is exposed in notification templates and webhooks.

This could break existing non-Prometheus clients of the AM

We are not going to remove API v1 right away, thereby giving non-Prometheus clients time to migrate.

Also keep in mind that the old API, which we will continue to have to support for some time, has no such validation so non-URLs will get into the system.

The API v2 only validates client input, not server output. Thereby alerts with invalid generatorURLs created via API v1 can still be retrieved via API v2.

What is the benefit of breaking this?

It would remove the confusion of a user expecting a valid URI in a property called generatorURL. In addition when one clicks the Source button on an alert in the UI with an invalid generatorURL, that person is directed to an invalid page.
A user inserting an invalid generatorURL would get instant feedback via the API v2:
"message":"generatorURL in body must be of type uri: \"1234\""

Something else is that this field name is exposed in notification templates and webhooks.

Which makes me favour keeping generatorURL instead of using generator.

I'm favoring @brancz's position -- moving to generator would remove potential semantic confusion about a client using generatorURL for a different purpose, and not validating it would support that.
however, @mxinden does raise a good point, that the current UI assumes that the generatorURL is a URI. Maybe we can on the frontend parse generator into either a URI (which we link to), or if it's invalid, render it in the expanded 'Info' section?

Validating the generatorURL is not a breaking-change for any upstream Prometheus projects. It might be a breaking change for existing non-Prometheus clients of Alertmanager, but so far we are not aware of any (please correct me if I am wrong).
I am still advocating for introducing this maybe-breaking-change with the new Alertmanager API v2. It is a major API version bump, thereby a breaking change should not struck anyone by surprise. Given the scenario that there is a non-Prometheus client of Alertmanager that depends on generatorURL not being a valid URI, for short-term, that project could still use the API v1, for long term that project could leverage alert annotations instead.
Moving from generatorURL to generator would introduce two breaking changes. One in the ingestion structure, second in notification templates and webhooks. In addition it forces us to include extra logic in the UI to detect whether it is a valid URI.

Re the generatorURL discussion, I'd agree with @mxinden that we should keep generatorURL (as it doesn't require additional change to the Prometheus projects) and add validation for it. Also IIUC the API definition allows for generatorURL to be empty so clients that don't pass a valid URI value today can just drop the field and potentially use Annotations instead.

In principle all clients should be setting that field, it has a difference purpose to an annotation as the ultimate goal is to allow silencing based on it. I'm against things that would result in clients not setting that field.

as the ultimate goal is to allow silencing based on it.

For the record, this is tracked in #344. In that case, it is a free-form field and should be called generator. Templates could continue to expose GeneratorURL as an alias for Generator under the hood.

In that case, it is a free-form field and should be called generator.

@simonpasquier can you elaborate on that? Why can it not be a valid URI in that case?

I have addressed all outstanding comments.
Are there any objections or concerns left?
@brian-brazil with the above discussion, is the validation of generatorURL acceptable for you?

What exactly is the proposal to handle it? I can't quite figure out from the conversation.

The proposal is to validate that generatorURL is a valid URI in the  POST /alerts endpoint.

That breaks existing users, so we shouldn't do that.

@brian-brazil do you have any specific users in mind? Would it be possible for them to migrate to a valid generatorURL between the deprecation and the deletion date (multiple minor versions) of the API v1?

I'm not aware of anyone in particular, but as long as the v1 API exists I think we should keep them working on that api.

Maybe I have not been clear, sorry. This does not enforce validation on the API v1ingestion endpoint, only on the API v2 ingestion endpoint. The API v1 endpoint will still accept invalid generatorURLs.
@brian-brazil with that in mind, is the proposal acceptable for you?

@simonpasquier @stuartnelson3 does this PR look good to you as well?

:+1: for merging this version and iterate from there. Thanks!

:+1:

:+1:

merge at will, @mxinden !

:tada: :+1:

Thanks everyone for the repeated feedback and help!


Implement Rate Limit per Rest Client

Expected Behavior
Support a rate limit for each endpoint. BinanceFutures has a higher rate limit 300 per 10 seconds (30/s) against 5 messages per second from Binance.
Actual Behavior
There is a single rate limit per endpoint.
Potential Solution
N/A
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

Local deployment has a rate limit issue during warm-up
Too Many Requests, Content: {"code":-1003,"msg":"Too many requests; current limit of IP(XX.XX.XX.XX) is 2400

The lookback is around a week, and it requests minute-resolution data.


[BUG] ResourceManager.AppService error

Library name and version
Azure.ResourceManager.AppService 1.0.2
Describe the bug
Method - GetAppServiceCertificateOrdersAsync - failing
public static AsyncPageable GetAppServiceCertificateOrdersAsync(this SubscriptionResource subscriptionResource, CancellationToken cancellationToken = default)
The failure occurs seemingly after the certificate order data is returned. About 7 seconds after initiating the request.
Full exception:
{"data":"System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'resourceType')\r\n   at Azure.Core.ResourceType..ctor(String resourceType)\r\n   at Azure.ResourceManager.AppService.AppServiceCertificateOrderData.DeserializeAppServiceCertificateOrderData(JsonElement element)\r\n   at Azure.ResourceManager.AppService.SubscriptionResourceExtensionClient.b__103_2(JsonElement e)\r\n   at Azure.Core.PageableHelpers.PageableImplementation1.GetAsyncEnumerator(CancellationToken cancellationToken)+MoveNext()\r\n   at Azure.Core.PageableHelpers.PageableImplementation1.GetAsyncEnumerator(CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()\r\n   at IdstcAdmin.Controllers.ReportsController.GetAppServiceCertificates() in C:\git_idstc\IdstcAdmin\IdstcAdmin\Controllers\ReportsController.cs:line 901\r\n   at IdstcAdmin.Controllers.ReportsController.GetAppServiceCertificates() in
Expected behavior
Return app service certificate orders
Actual behavior
Exception:
specified argument was out of the range of valid values. (parameter 'resourcetype')
Reproduction Steps
var subscriptionId = Environment.GetEnvironmentVariable("SubscriptionID");
var credential = new DefaultAzureCredential();
var armClient = new ArmClient(credential, subscriptionId);
var resourceId = SubscriptionResource.CreateResourceIdentifier(subscriptionId);
var subscription = armClient.GetSubscriptionResource(resourceId);
var certOrders = subscription.GetAppServiceCertificateOrdersAsync();
if (certOrders != null) {
    await foreach (var certOrder in certOrders) {
        var blah = certOrder;
        }
}

Environment
Windows 11
dotnet 8.0.303

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

PR: #45343


update the working pr template

I would like to add a new workflow for pr template which check for screenshot in it
as the screenshot helps in better understanding of the working or the changes which has been done
I would really appreciate to contribute to this project

@priyanshaggarwal001 go ahead!

please review my pr request


adding page event to start searching for fields to update

some pages react to click event to open modular form|
this can be done by the user at any time not related to the page load
adding an option to identify the click event as part of the auto-fill configuration
will help catch the new HTML part and update it as expected
I hope I made it clear

Have you tried manual mode https://getautoclicker.com/docs/4.x/config-settings/start/

Manual mode is a workaround.
But the user expectations are for automation.
Hence the request to add trigger.
And having the context menu option as back up
On Wed, Aug 14, 2024, 09:39 Dharmesh @.***> wrote:

Have you tried manual mode
https://getautoclicker.com/docs/4.x/config-settings/start/
—
Reply to this email directly, view it on GitHub
https://github.com/Dhruv-Techapps/acf-docs/issues/404#issuecomment-2287967701,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANJVCJNKYSKROPWCEM5IEETZRL3SXAVCNFSM6AAAAABMOU7IQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBXHE3DONZQGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

To understand clearly you have set of actions which are automated but there is step in between which you like to perform manually and rest of steps should wait until this action is performed .

Not exactly,
I'll try to elaborate:
I use JIRA and I would like to automate particular form.
The problem,
This form is open as modular window by clicking on certain button.
The addon doesn't recognize the fields in this window automaticly.
Hence, it doesn't fill them.
(Note - Manual mode work as expected)
Suggested solution:
Adding event watching to catch the click on the button, as part of second
rule to trigger the first rule upon form opening
I hope I made myself clear
On Wed, Aug 14, 2024, 10:12 Dharmesh @.***> wrote:

To understand clearly you have set of actions which are automated but
there is step in between which you like to perform manually and rest of
steps should wait until this action is performed .
—
Reply to this email directly, view it on GitHub
https://github.com/Dhruv-Techapps/acf-docs/issues/404#issuecomment-2288014830,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANJVCJIJ4Q6VUWOZEY5ZFB3ZRL7NVAVCNFSM6AAAAABMOU7IQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBYGAYTIOBTGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

By default add-on find element on webpage and if it don't find it retry for 5 times with 1 sec interval and if it don't find even it stops the extension.
If you want the add-on to keep retrying to find the element even after 5 sec. You can set this under action settings to retry more than 5 times also increase / decrease the interval . If you want the extension to keep retrying you can set retry to -2

If you think It still don't solve your issue . Please record and share the video for reference.

Closing this issue as no response. Please reopen if you still face issue.


adding webhook demo

Adding a webhooks demo page:
http://localhost:8081/webhook
To see webhooks working in real time you do the following:

Create a new webhook that fires when a did is created:

Create a new did

See the webhook fire on the webhook page

Yea totally cool with changing the page layout, happy to go over it


How to use the update() function for a collection?

Sorry if this seems like a basic question.
I'm trying to figure out how to use the update() function because it's stated in the docs that it takes only one argument, the object to be updated itself -- http://lokijs.org/#/docs#update
After the object is passed in, it returns the document. Now I assume that adding updates to the returned object will automatically reflect in the collection?
I know we're using Mongo-inspired functions, but in Mongo, the update() function has three arguments. Is there something missing in the docs or is this really the way to do updates in Loki?
collection.update({GetGeoIPResult: {IP: '<IP_ADDRESS>'}}) = '<IP_ADDRESS>'

EDIT:
I saw in slide 6 here (http://www.slideshare.net/techfort/lokijs) that updates are optional, and we only do this to force a re-indexing of the collections.
How do I know Loki will update the documents I need in the following use case?

I poll a database every time interval for some data
The data that is returned to me is last modified a certain number of minutes ago
I save the results in my collection, inserting new data and replacing old ones

How does Loki know I want to replace a document with a more up to date one?

Hi @bizMD : the update() function works differently from the Mongo one. At the moment, you modify an object and pass it to the update() function, however the object is not returned, only the object in the collection is modified. This is in the majority of cases good enough, as the object you pass is a reference to the object in the collection.
If you are using clones, you need to retrieve the object again to make sure to be using the correct object.
On a side note: I want to change this behaviour to work more like MongoDB, but as update() is such a vital operation, this would cause major backward incompatibility, so it would cause a major version release (eg. v2.0)
It is possible we will in fact apply this change and release a v2.0 along with some other major changes.
As this is not a bug i'll close the issue, drop me a mail if you still need help with this.


[BUG] Error when enabling fp16 config with tasks involving FloatTensor Inputs such as Image Classification, Speech Recognition ...

Describe the bug
Following runtime error when enabling fp16 config with tasks involving FloatTensor Inputs such as Image Classification, Speech Recognition ...
Traceback (most recent call last):
  File "examples/cv_example.py", line 213, in <module>
    main()
  File "examples/cv_example.py", line 209, in main
    training_function(config, args)
  File "examples/cv_example.py", line 162, in training_function
    outputs = model(inputs)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/sourab/test/lib/python3.8/site-packages/deepspeed/utils/nvtx.py", line 11, in wrapped_fn
    return func(*args, **kwargs)
  File "/home/sourab/test/lib/python3.8/site-packages/deepspeed/runtime/engine.py", line 1616, in forward
    loss = self.module(*inputs, **kwargs)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/sourab/test/lib/python3.8/site-packages/timm/models/resnet.py", line 685, in forward
    x = self.forward_features(x)
  File "/home/sourab/test/lib/python3.8/site-packages/timm/models/resnet.py", line 673, in forward_features
    x = self.conv1(x)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/container.py", line 141, in forward
    input = module(input)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 447, in forward
    return self._conv_forward(input, self.weight, self.bias)
  File "/home/sourab/test/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 443, in _conv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Input type (torch.cuda.FloatTensor) and weight type (torch.cuda.HalfTensor) should be the same

This is happening because self.module.half()  is called in _configure_distributed_model when initializing DeepSpeedEngine object. For language model, this didn't create any issues as the input was LongTensor to embedding layers. For other modalities wherein FloatTensor is input, it is leading to above error. Please handle this scenario in forward call of DeepSpeedEngine model object.  I tried to convert inputs.half() and this fixes the issue but I feel this check and logic should be part of the forward call of DeepSpeedEngine model object.
To Reproduce
Steps to reproduce the behavior:

Official HF Accelerate cv_example.py script
Setting up DeepSpeed Zero-2 through command accelerate config. The output config yaml:

compute_environment: LOCAL_MACHINE
deepspeed_config:
  gradient_accumulation_steps: 1
  offload_optimizer_device: none
  offload_param_device: none
  zero3_init_flag: false
  zero_stage: 2
distributed_type: DEEPSPEED
fsdp_config: {}
machine_rank: 0
main_process_ip: null
main_process_port: null
main_training_function: main
mixed_precision: fp16
num_machines: 1
num_processes: 2
use_cpu: false

The resulting deepspeed config being:
{
    "train_batch_size": 128,
    "train_micro_batch_size_per_gpu": 64,
    "gradient_accumulation_steps": 1,
    "zero_optimization": {
        "stage": 2,
        "offload_optimizer": {
            "device": "none"
        },
        "offload_param": {
            "device": "none"
        },
        "stage3_gather_16bit_weights_on_model_save": false
    },
    "steps_per_print": inf,
    "fp16": {
        "enabled": true
    },
    "zero_allow_untested_optimizer": true
}

Run the script with below command with location to folder with images. Information on downloading images here. Output has the error stated above.

accelerate launch examples/cv_example.py --mixed_precision fp16 --data_dir /path/to/images/folder

Expected behavior
No errors.
ds_report output
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
 [WARNING]  please install triton==1.0.0 if you want to use sparse attention
sparse_attn ............ [NO] ....... [NO]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
async_io ............... [NO] ....... [OKAY]
utils .................. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/home/sourab/test/lib/python3.8/site-packages/torch']
torch version .................... 1.11.0+cu102
torch cuda version ............... 10.2
torch hip version ................ None
nvcc version ..................... 10.2
deepspeed install path ........... ['/home/sourab/test/lib/python3.8/site-packages/deepspeed']
deepspeed info ................... 0.6.5, unknown, unknown
deepspeed wheel compiled w. ...... torch 1.11, cuda 10.2

System info (please complete the following information):

OS: Ubuntu 20.04.3 LTS (Focal Fossa)
GPU count and types: 1 machine with x2 NVIDIA TITAN RTX each
Python version: Python 3.8.10

Launcher context
Are you launching your experiment with the deepspeed launcher, MPI, or something else?
Accelerate launcher which just triggers deepspeed launcher

Including similar issue raised in accelerate repo #443

Got the same error here. Seems like the initialization will ignore the fp16 setting in some cases.

Hello, any update on this?

Sorry for delay on this @pacman100, but is this now resolved in https://github.com/huggingface/accelerate/issues/443? I was just setting up the environment to repro this but now thinking maybe i don't need to?

I was able to repro the issue with the scripts above. This PR (https://github.com/microsoft/DeepSpeed/pull/2158) updates our fp16 config to allow auto-casting inputs to fp16. @pacman100 can you confirm this fixes your issue? I am not sure how to set this on the accelerate side.

Hello @jeffra , Thank you! 😄. This fixes the issue. Below is how one would set this on the accelerate to check.

DeepSpeed config zero2_fp16_inputs_auto_enabled.json like below:

{
    "fp16": {
        "enabled": true,
        "auto_cast": true,
        "loss_scale": 0,
        "loss_scale_window": 1000,
        "initial_scale_power": 15,
        "hysteresis": 2,
        "min_loss_scale": 1
    },
    "zero_optimization": {
        "stage": 2,
        "allgather_partitions": true,
        "allgather_bucket_size": 2e8,
        "overlap_comm": true,
        "reduce_scatter": true,
        "reduce_bucket_size": 2e8,
        "contiguous_gradients": true
    },
    "gradient_accumulation_steps": 1,
    "gradient_clipping": "auto",
    "steps_per_print": 2000,
    "train_batch_size": "auto",
    "train_micro_batch_size_per_gpu": "auto",
    "wall_clock_breakdown": false
}

accelerate config zero2_autocast_fix_test.yaml like below:

compute_environment: LOCAL_MACHINE
deepspeed_config:
  deepspeed_config_file: zero2_fp16_inputs_auto_enabled.json
  zero3_init_flag: false
distributed_type: DEEPSPEED
downcast_bf16: 'no'
fsdp_config: {}
machine_rank: 0
main_process_ip: null
main_process_port: null
main_training_function: main
mixed_precision: 'no'
num_machines: 1
num_processes: 2
use_cpu: false

run the  official 🤗 accelerate example cv_example.py with the below command:

accelerate launch --config_file zero2_autocast_fix_test.yaml examples/cv_example.py --data_dir  images

The output is below:
[2022-07-30 05:39:55,256] [INFO] [config.py:979:print]   zero_enabled ................. True
[2022-07-30 05:39:55,256] [INFO] [config.py:979:print]   zero_optimization_stage ...... 2
[2022-07-30 05:39:55,256] [INFO] [config.py:981:print]   json = {
    "fp16": {
        "enabled": true,
        "auto_cast": true,
        "loss_scale": 0,
        "loss_scale_window": 1000,
        "initial_scale_power": 15,
        "hysteresis": 2,
        "min_loss_scale": 1
    },
    "zero_optimization": {
        "stage": 2,
        "allgather_partitions": true,
        "allgather_bucket_size": 2.000000e+08,
        "overlap_comm": true,
        "reduce_scatter": true,
        "reduce_bucket_size": 2.000000e+08,
        "contiguous_gradients": true
    },
    "gradient_accumulation_steps": 1,
    "gradient_clipping": 1.0,
    "steps_per_print": inf,
    "train_batch_size": 128, "train_micro_batch_size_per_gpu": 64,
    "wall_clock_breakdown": false,
    "zero_allow_untested_optimizer": true,
    "compression_training": {
        "weight_quantization": {
            "shared_parameters": {
            },
            "different_groups": {
            }
        },
        "activation_quantization": {
            "shared_parameters": {
            },
            "different_groups": {
            }
        },
        "sparse_pruning": {
            "shared_parameters": {
            },
            "different_groups": {
            }
        },
        "row_pruning": {
            "shared_parameters": {
            },
            "different_groups": {},
            "different_groups": {
            }
        },
        "head_pruning": {
            "shared_parameters": {
            },
            "different_groups": {
            }
        },
        "channel_pruning": {
            "shared_parameters": {
            },
            "different_groups": {
            }
        }
    }
}
Using /home/sourab/.cache/torch_extensions/py38_cu102 as PyTorch extensions root...
No modifications detected for re-loaded extension module utils, skipping build step...
Loading extension module utils...
Time to load utils op: 0.00018715858459472656 seconds
epoch 0: 86.26
epoch 1: 86.91
epoch 2: 88.61
[2022-07-30 05:40:08,368] [INFO] [launch.py:318:main] Process 2217624 exits successfully.
[2022-07-30 05:40:08,369] [INFO] [launch.py:318:main] Process 2217623 exits successfully.

Excellent! Glad to hear this is resolved :) thanks for the tip wrt accelerate!


Whale Indexer continues to fail at block 3077

What happened:
The Whale indexer continues to fail at block 3077.
I have tried multiple restarts of the defid including a fresh installation.
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: 7d0918fea5533abc97320398d2ecceb49e6bd79f0c6aa200b51cbbd461ea707c - height: 3068
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: e102572a4d62f707bb426d8037577360b44705d0bd67a47b8a84f815fc0f5121 - height: 3069
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: 773058195ba3c40c7d59c083aff867b99c7fee4e392a443462722ab2bb56fc92 - height: 3070
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: 77df449c83deb3b57eb03457938700aae7c10112a627cadae5df6637bbe7eb35 - height: 3071
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: 063e6a6b472348fadede53f89ca034df7dba54fc7cd75cef57510cea416b11d6 - height: 3072
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: 7585ed1a5e2db2c3839bc0c50c8684a78a40adba132ecb3890b602d38a827aff - height: 3073
[Nest] 1  - 06/02/2022, 6:56:32 PM     LOG [RPCBlockProvider] Index - hash: 627f850f30e79455f4f3579bd85476400dd1d768c0317cec72d48008fd485dce - height: 3074
[Nest] 1  - 06/02/2022, 6:56:33 PM     LOG [RPCBlockProvider] Index - hash: 39ba4389833ec78e74f3405f79c6cd6ca009e0703708046e3f22c4d45bb9fee9 - height: 3075
[Nest] 1  - 06/02/2022, 6:56:33 PM     LOG [RPCBlockProvider] Index - hash: 4df2a81597abb56dd9a65582f547dddbcc332bd913ea1a7305c9684c585b9d8b - height: 3076
[Nest] 1  - 06/02/2022, 6:56:33 PM     LOG [RPCBlockProvider] Index - hash: fd8fc5b943fd05e80e0160ba8ae79d6047d2f1808c6226b73ef880a60aab0322 - height: 3077
[Nest] 1  - 06/02/2022, 6:56:33 PM   ERROR [RPCBlockProvider] failed exceptionally
[Nest] 1  - 06/02/2022, 6:56:33 PM   ERROR [RPCBlockProvider] TypeError: Cannot read properties of undefined (reading 'pubKeyHashPrefix')
[Nest] 1  - 06/02/2022, 6:56:33 PM     LOG [RPCBlockProvider] Cleanup - hash: fd8fc5b943fd05e80e0160ba8ae79d6047d2f1808c6226b73ef880a60aab0322 - height: 3077 - status: ERROR
[Nest] 1  - 06/02/2022, 6:56:33 PM     LOG [RPCBlockProvider] Invalidate - hash: fd8fc5b943fd05e80e0160ba8ae79d6047d2f1808c6226b73ef880a60aab0322 - height: 3077
[Nest] 1  - 06/02/2022, 6:56:33 PM     LOG [RPCBlockProvider] Index - hash: fd8fc5b943fd05e80e0160ba8ae79d6047d2f1808c6226b73ef880a60aab0322 - height: 3077
The whale tries to re-do the block over and over again but cannot continue.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Both, the defid and whale-api run in Docker.
defid version 2.8.0
whale version - multiple incl. latest and 2.45.2

/apps whale-api

I haven't seen this error before, could you provide us with more runtime information such as docker env or params used?

Sure!
Server type: root-server VPS
OS: Debian GNU/Linux 10 (buster)
Docker version 20.10.12, build e91ed57
docker run -v /home/defichain/data:/data -d --network=ocean --rm defi/defichain  defid -rpcallowip=<IP_ADDRESS>/16 -rpcbind=<IP_ADDRESS> -rpcuser=test-user -rpcpassword=test-password
docker run -d -p <IP_ADDRESS>:81:3000 --network=ocean --env WHALE_DEFID_URL=http://test-user:test-password@<IP_ADDRESS>:8554  ghcr.io/jellyfishsdk/whale-api

Network must be one of these:

--network=mainnet
--network=testnet
--network=devnet
--network=regtest

Probably your defid and whale-api "network" is mismatch. The undefined error looks like it couldn't figure out how to parse pubKeyHashPrefix properly given the network is different.

You can reference with docker-compose.yml for example

You are right!
By setting WHALE_NETWORK=mainnet the whale-api correctly indexes the block.
Thank you!

No worries, I have also created #1519 for us to properly detect the network and throw the correct error.
/close


new lexer request: toml (rust)

(Original issue 1150 created by alex_gaynor on 2015-09-20T14:59:31.660960+00:00)
It's now being used by rust for Cargo.toml so I noticed its absence.

(Original issue 1150 last updated on 2019-04-30T07:24:44.709110+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by tshatch on 2015-10-17T01:25:17.918128+00:00)
This is https://github.com/toml-lang/toml ? Looks easy.

(Original comment by borneo on 2017-11-08T14:27:22.944456+00:00)
Pipfile (https://github.com/pypa/pipfile) uses that syntax, too.

(Original comment by borneo on 2017-11-08T14:32:05.063924+00:00)
@tshatch by the way, here's a TOMLLexer https://github.com/tmm1/pygments.rb/blob/b98c252f782ebb3fa6187ca4b46cddeb99985719/vendor/custom_lexers/github.py#L365

(Original comment by Yeti on 2018-09-02T20:13:07.549008+00:00)
any progress/plans on this?

(Original comment by takluyver on 2018-09-02T20:21:11.177986+00:00)
The lexer @borneo mentioned above appears to be available on PyPI as pygments-github-lexers. Install that alongside pygments, and TOML syntax highlighting seems to work.

(Original comment by Freso on 2019-03-31T11:23:57.723050+00:00)
pyproject.toml as specified in PEP 518 is also in TOML.

(Original comment by Freso on 2019-03-31T15:37:20.197372+00:00)
PR at https://bitbucket.org/birkenfeld/pygments-main/pull-requests/807

(Original comment by Anteru on 2019-04-28T14:35:55.284113+00:00)
Add lexers for DASM16, Augeas, TOML, and Slash
Lexers copied unmodified from
https://github.com/liluo/pygments-github-lexers
which is available under a 2-clause BSD license (same as pygments),
copyright 2012 to GitHub, Inc.
Fixes #1391 and #1150.
→ <>

(Original comment by Anteru on 2019-04-30T07:24:44.628244+00:00)
Add lexers for DASM16, Augeas, TOML, and Slash
Lexers copied unmodified from
https://github.com/liluo/pygments-github-lexers
which is available under a 2-clause BSD license (same as pygments),
copyright 2012 to GitHub, Inc.
Fixes #1391 and #1150.
→ <>


listen on socket in addition to tls for amazon driver

Fixes #202.  This will listen on the default socket as well as tls for amazon.

LGTM


change session timeout to include checkboxes

Change description
changing the way session timeout is sending values due to incorrect data on checkboxes.
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/NFDIV-
Before merging a pull request make sure that:

[ ] tests have been updated / new tests has been added (if needed)
[ ] README and other documentation has been updated / added (if needed)

If this ticket will have any visible impact on users and is not behind a feature toggle, make sure that:

[ ] this ticket been reviewed by QA
[ ] the user story been signed off by the PO

Note that bug fixes, dependency updates and technical tasks do not directly impact the user experience and can be merged without QA and PO review.
If this user story cannot be immediately merged find a way to put it behind a feature toggle and get it merged.

closed due to
https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams#browser_compatibility

re opened because IE is dead and we dont need to support it


LUCI tests, for example ci/gotip-plan9-386
What did you see happen?
Example log:
=== RUN   TestOpenError
=== PAUSE TestOpenError
=== CONT  TestOpenError
    os_test.go:1830: Open("is-a-dir", 1) = _, "'/tmp/TestOpenError845272514/001/is-a-dir' permission denied"; want suffix "is a directory"
--- FAIL: TestOpenError (0.00s)

What did you expect to see?
Different Plan 9 file servers return different error strings (some arguably incorrect) when a process attempts to write to a directory. TestOpenError changed in CL 620157 to use a directory in /tmp instead of using the root file system. This may fail on Plan 9, depending on which file server is used to provide `/tmp'.
The test already has a special case for Plan 9's idiosyncratic error messages, but needs to allow for more possibilities.

Related Issues

testing/fstest: test that ReadDir on file returns error, or returns 0 entries if file is empty #44967
os: TestProgWideChdir failing on Plan 9 #10422 (closed)
os: TestRemoveAllWithMoreErrorThanReqSize is failing on Plan 9 and Windows #35117 (closed)
os: TestMkdirAll failing Plan 9 #23918 (closed)
x/build: os.TestUserConfigDir and os.TestUserCacheDir failing on plan9-arm with `permission denied` #62216 (closed)
x/tools/go/analysis/internal/checker: tests failing on Plan 9 because of dependence on numeric exit codes #68290 (closed)
test: bug369 failing on Plan 9 #9428 (closed)
x/tools/gopls/internal/regtest/misc: TestRenameFileFromEditor failures with `invalid argument` on plan9 #57111 (closed)
testing: test failes if leaving files without write permission in T.TempDir #40853
os: TestMkdirAll is broken on plan9 #23902 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


pre-route patterns

Hi,
I'm not sure if this is an even issue or a missing feature is, but is
(pre-route "/user/:username" {keys: [username]}
...)
supposed to work as expected? when I use this username is nil. I'm using noir 1.2.1
Cheers,
Stefan

This isn't a congomongo issue, right? :-)

sorry, wrong github tab ;) congomongo works fine so far!

Good to hear. :-)
-Steve


orb_advert_t fix

orb_advert_t changed to void * and checks changed to nullptr
The existing orb_advert_t use throughout the code sometimes tries
to treat it as a file descriptor and there are checks for < 0
and ::close() calls on orb_advert_t types which is an invalid use
of an object pointer, which is what orb_advert_t really is.

Initially I had changed the -1 initializations to 0 but it was
suggested that this should be nullptr. That was a good recommendation
but the definition of orb_advert_t had to change to void * because
you cannot initialize a uintptr_t as nullptr.

Hi Mark - sorry for being out of touch due to ICRA. I'll review and merge ASAP.

Applied via rebase, thanks!


Example in README doesn't work

@colinmcintosh
Example like
./slider-cli --satellite=goes-16 --sector=conus --product=geocolor -z=2

doesn't work, may RAMMB changes some image URLs

Checkout: https://github.com/colinmcintosh/SLIDER-cli/pull/8

This was fixed by #8. Thanks @oscaredel for the fix! Feel free to let me know if you are still having any issues.


Link

Docs Build status updates of commit 7b6dce6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/payroll/CAN18YETax.md
:white_check_mark:Succeeded
View

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


Clean up state tracking

Currently, there is a lot of overlap in the state tracked by various classes. Mostly, this is in the CurrentMode of the MainPage class, and various boolean fields in the VideoGridManager and VideoChannel classes.

I think there are similar issues here with #4: notably, the fact that playback events are handled by possibly multiple VideoChannel instances, which in turn may update central playback state. I think having VideoChannel's operate at a lower-level and having a centralized object managing the playback state is necessary to break this cyclic dependency, and would address much of the issues in #4.
Due to the asynchronous nature of the playback events, the flow would probably look like the following:

Playback event is received at the top level
The playback event is passed to the centralized playback controller, which, depending on the playback state, asynchronously invokes the appropriate functions in all the VideoChannels.
Once all of the VideoChannels have updated, the central controller propagates any state updates to the mainpage.


Unable to build a nixosConfigurations vm on darwin host

Steps To Reproduce
Given the following flake.nix file
{
  inputs.nixos.url = "github:NixOS/nixpkgs/nixos-23.05";

  outputs = {nixos,...  }: {
    nixosConfigurations.testvm = nixos.lib.nixosSystem {
      modules = [
        ({modulesPath, ...}: {
          imports = [(modulesPath + "/virtualisation/qemu-vm.nix")];
          nixpkgs.hostPlatform = "aarch64-linux";
        })
      ];
    };
  };
}

and flake.lock
{
  "nodes": {
    "nixos": {
      "locked": {
        "lastModified":<PHONE_NUMBER>,
        "narHash": "sha256-PEQptwFCVaJ+jLFJgrZll2shQ9VI/7xVhrCYkJo8iIw=",
        "owner": "NixOS",
        "repo": "nixpkgs",
        "rev": "4f77ea639305f1de0a14d9d41eef83313360638c",
        "type": "github"
      },
      "original": {
        "owner": "NixOS",
        "ref": "nixos-23.05",
        "repo": "nixpkgs",
        "type": "github"
      }
    },
    "root": {
      "inputs": {
        "nixos": "nixos"
      }
    }
  },
  "root": "root",
  "version": 7
}

when I try to build this nixos configuration as a vm with
nix build .#'nixosConfigurations.testvm.config.system.build.vm'

it fails due to a hash musmatch.
Am I missing something obvious ?
It seems like the error is due to a hash of something provided in nixpkgs that changed for some reasons for my build ; I tried to look for this hash in nixpkgs, but I didnt find where its defined.
Build log
error: hash mismatch importing path '/nix/store/pbd9fm3dhrcyx0i0n0dnrshxx05yw0ip-nixos-generate-config';
         specified: sha256:1rhgmgnld072vd64bm71wnq6p68bhm8nnf24jqxsjj5jjsyff3rl
         got:       sha256:00zm238xzazyjj23pd6zgr3n1am7arlr0hg7xh2zn8n5dk3cggg0
error: builder for '/nix/store/jnaypca5fp1f8pmkazssal7787jpyrqz-nixos-generate-config.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/9yv8jd7jdibp7src86pzahyz4n8bjgsi-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/hrv26x7pb0xdvj73m65awyavfwpk31pk-nixos-system-nixos-23.05.20230907.4f77ea6.drv' failed to build
error: 1 dependencies of derivation '/nix/store/qma8vc695xqc7q0vndhgdwnswsj8wjcs-nixos-vm.drv' failed to build

Additional context
Running the command above on a mac M1 configured with nix-darwin, through a linux builder (due to the system being aarch64-darwin and the vm being aarch64-linux)
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-darwin"`
 - host os: `Darwin 22.6.0, macOS 13.5`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.17.0`
 - channels($MYUSER): `"darwin, home-manager"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

If you need more context or if you need me to execute stuff, don't hesitate!
Thank you by advance for your help.

Facing similar problem here. Did you fix it?

Hi!
I just tried, and I don't have this issue anymore (with the exact same flake.lock as provided above I am able to run the command provided above without error).
Probably related to this, during today's test I realized that nix is going through a builder (the one I'm using comes from nix-darwin nix.linux-builder.enable = true) to build the vm described in the flake, and the builder vm running today on my host certainly received some updates since the time I opened this issue, which could explain why its working now with the exact same flake.lock. I guess this indicate the issue is not directly related to nixpkgs.
If you are using the same builder as me through nix-darwin, maybe the solution is just to upgrade it.
The version I'm using is the following:
      "locked": {
        "lastModified":<PHONE_NUMBER>,
        "narHash": "sha256-+Jlz8OAqkOwJlioac9wtpsCnjgGYUhvLpgJR/5tP9po=",
        "owner": "lnl7",
        "repo": "nix-darwin",
        "rev": "1e706ef323de76236eb183d7784f3bd57255ec0b",
        "type": "github"
      },
      "original": {
        "owner": "lnl7",
        "ref": "master",
        "repo": "nix-darwin",
        "type": "github"
      }

Since the issue is fixed for me, I'll close the issue, feel free to re-open it again if the idea above does not work for you!


Weird style on uploader

Yikes! That is ugly. It looks like it was caused by my "fix" for long links in comments: 0abf71e75228d4405a92b3d20d438f76b2bc76f5
This is fixed by e20c854e3ad0539a0511302c1331dd30537c32bc.
Thanks a lot: you've done me a big favor by pointing this out.

No problem ^^


Carriers: TextMap*Adapter (Java) vs DictionaryCarrier (C#)

After reading through https://github.com/opentracing/opentracing-java/issues/31 for about 5 times, I think I finally understand all statements and I agree with the current Tracer API. C# already has the same signature on ITracer so we should be good here. However, we currently do something else differently in C#.
Java uses two separate classes for representing a regular map/dictionary:
public final class TextMapInjectAdapter implements TextMap {
    private final Map<String,String> map;

    public TextMapInjectAdapter(final Map<String,String> map) {
        this.map = map;
    }

    @Override
    public Iterator<Map.Entry<String, String>> iterator() {
        throw new UnsupportedOperationException("TextMapInjectAdapter should only be used with Tracer.inject()");
    }

    @Override
    public void put(String key, String value) {
        this.map.put(key, value);
    }
}

public final class TextMapExtractAdapter implements TextMap {
    private final Map<String,String> map;

    public TextMapExtractAdapter(final Map<String,String> map) {
        this.map = map;
    }

    @Override
    public Iterator<Map.Entry<String, String>> iterator() {
        return map.entrySet().iterator();
    }

    @Override
    public void put(String key, String value) {
        throw new UnsupportedOperationException("TextMapInjectAdapter should only be used with Tracer.extract()");
    }
}

In C# we currently have just one type that handles both cases:
public class DictionaryCarrier : ITextMap
{
    private readonly IDictionary<string, string> _payload;

    public DictionaryCarrier(IDictionary<string, string> payload)
    {
        _payload = payload;
    }

    public IEnumerable<KeyValuePair<string, string>> GetEntries()
    {
        return _payload;
    }

    public string Get(string key)
    {
        string value;
        return _payload.TryGetValue(key, out value) ? value : null;
    }

    public void Add(string key, string value)
    {
        _payload[key] = value;
    }
}

What's the advantage of using two separate classes for this?
Since both classes could be used for Inject/Extract it seems like it's pretty easy for users to mess this up and get runtime exceptions.
Trace implementations have to support inject & extract for TEXT_MAP so there isn't a case where it would support just one version, right?
/cc @bensigelman @dawallin @yurishkuro

After reading through opentracing/opentracing-java#31 for about 5 times

so the reason things are a bit messy in Java is because you may have noticed during those 5 reads :-) that my original proposal for format was Format<R, W> and the method signatures were
inject(SpanContext, Format<?, W>, W carrier)
extract(Format<R, ?>, R carrier)

where ? stands for "don't care, I'm only restricting the other type".
The intention was to allow the carrier type to be asymmetrical for read and write operations, e.g. in Go we have TextMapReader and TextMapWriter interfaces instead of a single TextMap. IMO that would've been a much cleaner design. In contrast, when you have a single TextMap interface, the implementation that's wrapping something else has to either implement both directions of data flow, or be separated into two implementations as you've discovered. Problem with implementing both directions is that the carrier is usually a wrapper around some other data structure, like RPC Headers object, and depending on the context that underlying object may R or W but not both. E.g. in a server handler, you may be given headers as a Map, but it could be an immutable map that will throw exception if you try to write to it. So your adapter of that map into TextMap carrier is going to implement a write operation that is guaranteed to fail.
Why the dual-type Format did not take in Java - you'd have to read the thread. In a democracy you often end up with compromises. In Go the generics don't exist so we could not implement strong typing, but we could define the convention for carrier types, and that convention is based on dual R/W types for both text map and binary formats.
Someone mentioned earlier that in C# the <?> approach doesn't work (which is a bit surprising since it's the basic mechanism for covariance), and since things are moving towards singly-typed Formats I'd say your DictionaryCarrier is fine. I, in fact, also got burnt once by the duality in Java TextMap wrappers, since the wrong carrier does not get caught by the type system (as it would've been with dual R/W typed Formats).

thanks for your feedback, Yuri! I'll keep the current code then - if anyone has further comments/concerns feel free to open another issue.
@yurishkuro:

Someone mentioned earlier that in C# the <?> approach doesn't work (which is a bit surprising since it's the basic mechanism for covariance)

In C#, in and out keywords can be used to declare contra-/covariance rules on generics but to be honest, I don't know much about this topic. AFAIK it's not possible to keep a type constraint undefined in a concrete implementation. That's why it wasn't possible to have different LogField<T> types in a list (which we briefly tried in the logging topic).


minor fixes in the Russian localization

Hello, sir, earlier, I was developing an application for my master's thesis.
Thank you for your project.
Please consider minor changes in the localization in Russian.
Changed some formulations so that they sound true for Russian speakers.
P.S. I am a native

Hi f4ilfish,
Thank you for your contribution :)
best regards


How much gas fee in USD would erc721a approximately cost for 10K NFTs?

How much gas fee in USD would erc721a approximately cost for 10K NFTs?

@Vectorized Really appreciated your quick response. I am pretty new to this area so I don't fully understand what you're saying :). So, the total gas fee will be a bit more than 2812.5 USD if I mint 10K NFTs at a time via erc721a?

@Vectorized Also, it would be much appreciated if you elaborate on this formula: 10000 * 1875 * 50 * 3000 * 1e-9 = 2812.5 USD

First, calculate the amount of gas that will be used.
Gas used
    = Number of NFTs minted * Gas cost per transfer event
    = 10000 * 1875
    = 18750000

Then, to find out how much the transaction fee is:
Transaction fee
    = Gas Used * BASEFEE * Price of ETH in USD * Price of gwei in ETH
    = 18750000 * 50 * 3000 * 1e-9

The BASEFEE will fluctuate depending on network load.


Extract ProjectBehavior for project object delegation

Whenever you require the current project, use ProjectBehavior now.
Fixes #250

LGTM


Add google-advanced-search extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @pernielsentikaer and thank you for your feedback,
I think I need some help; I can't reproduce the error. In the code, I only iterate through all the values of the form to build the URL:
function buildSearchUrl(values: SearchParams): string {
  const searchParams = new URLSearchParams();

  Object.keys(values).forEach((key) => {
    const value = values[key as keyof SearchParams];
    searchParams.append(key, value);
  });

  return `https://www.google.com/search?${searchParams.toString()}`;
}

My test:
https://github.com/raycast/extensions/assets/2411263/2f5d6c36-6f3f-42d6-823d-88d97b14eeac
Thank you!

It seems like it was something in my end, it works as expected now

Thank you @pernielsentikaer!
Do you have any suggestion about the extension or the code? It is my first extension and mi first time using React + Typescript.
Thank you!

It's a fairly simple extension and it works as expected; I wouldn't change the code for this 🙂


feat: add stats_users configuration option for pgbouncer

What issues does your PR fix?

fixes #819

What does your PR do?
An (optional) parameter is added to the helm chart, that updates the stats_users configuration in the generated pgbouncer.ini file.
Checklist
For all Pull Requests

[x] Commits are signed off
[x] Commits have semantic messages
[x] Documentation updated
[x] Passes ct linting

For releasing ONLY

[ ] Chart.yaml version bumped
[ ] CHANGELOG.md updated

@thesuperzapper are you or somebody else available to review this PR please?

@thesuperzapper we are still interested in getting this merged. Is anyone available to review this?

@jbvaningen sorry for missing this!
We are currently trying to get airflow 2.9 working in a new release, so I guess this could be part of that.
Is this single config really all you need?
Is there anything else we should add or another way of doing this?


Support laravel 5.6

Could we get this pull request.

Done, thanks for the work.
On Mon, Feb 12, 2018 at 7:29 AM, Wayne<EMAIL_ADDRESS>wrote:

Could we get this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/backup-manager/laravel/pull/103#issuecomment-364837978,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiObaLHf_IKffMJOxSx3Pl0X_IcxY0Zks5tT9pUgaJpZM4R9O7o
.

--
Shawn McCool | Big Name
<EMAIL_ADDRESS>heybigname.com


Instead of storing the completion handler, we forward it instead.

Also, trampoline to main thread only if needed.
There is a chance of race condition happening. For example, in rare case when you receive 2 successive handle URL calls all within the current run loop frame, The first completion handler will be overridden and never be called.

Closing. See #91.


I have this issues when import this sample

Could not find method android() for arguments [build_6jeehw84ixk6hsv93igm3somo$_run_closure1@e6613db] on project ':library' of type org.gradle.api.Project.

Sounds like a gradle configuration issue, could you share your build.gradle files and project structure?


oauth

as a user I want to sign in with my social media account so that I can access healthsites easily
osm -
linkedin -
google -
twitter - done
facebook - done
during the sign on process I expect to be informed of the data healthsites will use from my account and how I can manage it.

so we are missing support for osm, linkedin and google oauth providers? and we should enable those?

We need to review how we want this process to work...
The OSM account will be the primary account.
It will will allow the user to write directly to OSM once #888 and #889 have been developed.
The idea of having the Twitter, Facebook and Linkedin accounts available achieve the following two objectives:

Easy authentication
Opportunities to share Healthsite locations into Social networks and request validations

They should be seen as secondary to the OSM account.
From the profile page, established following the initial registration, the user can choose to add additional profiles to the account.
https://healthsites.io/profile/sharehealthdata/
When a user wants to share a healthsite with Twitter/Facebook/Linkedin the system should detect which authentication method is active and either proceed or redirect back to profile/page and request activation.


Azure.Automation.AuditLogs requires all diagnostic logs settings to have auditing enabled

Description of the issue
Observed by @BernieWhite in #1718
There is a bug in Azure.Automation.AuditLogs. Which is if multiple diagnostic log settings are configured they all must have auditing enabled, which is not really a requirement.
Currently Automation account support up to five(5) diagnostics settings based on documentation.
We want to get to, auditing either through category or category group being configured at least once as bare minimal.
Some refactoring of the rule has to be done in order to achieve this.

@BernieWhite
I'd happily take it as I'm in kinda the same situation working towards #1690
Are you aware the same pattern existing in other rules as well or is it just Azure.Automation.AuditLogs that can come to your mind for now?