[NEW]: Binance mishandled funds and violated securities laws, according to SEC lawsuit

Date
2023-06-05
Description
The world’s largest cryptocurrency exchange Binance and its founder Changpeng Zhao are accused of misusing investor funds, operating as an unregistered exchange and violating a slew of U.S. securities laws in a lawsuit filed by the SEC.
Filed in the U.S. District Court for the District of Columbia, the Securities and Exchange Commission lawsuit on Monday lists thirteen charges against the firm — including commingling and divert customer assets to an entity Zhao owned called Sigma Chain.
Binance is a Cayman Islands limited liability company founded by Zhao and the charges are familiar to practices uncovered after the collapse of the second largest cryptocurrency exchange, FTX, last year.
The lawsuit lays out the extent to which the firms owners knew of the alleged legal violations: “Binance’s CCO bluntly admitted to another Binance compliance officer in December 2018, “we are operating as a fking unlicensed securities exchange in the USA bro.”
Links
https://apnews.com/article/crypto-binance-treasury-sec-stocks-ba3ce6c0086d36650e97e80a1ba780b1
https://nos.nl/artikel/2477867-amerikaanse-beursautoriteit-start-fraudezaak-tegen-cryptoplatform-binance (Dutch national news)
https://cointelegraph.com/news/sec-sues-binance-in-us-district-court-for-unregistered-securities-operations
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
Sander van Kasteel
Personal link
https://mastodon.online/@SuitedUpDev

Thanks, https://web3isgoinggreat.com/?id=sec-files-complaint-against-binance


⚠ api.piste.gouv.fr healthcheck has degraded performance

In f85e685, api.piste.gouv.fr healthcheck (https://api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 4693 ms

Resolved: api.piste.gouv.fr healthcheck performance has improved in 13f4887.


Decomp bag biomass amounts for sample analysis

Customer: Lindsey Ruhl, Vermont
Lindsey called to say that the amount of biomass they have ground up from their T0 samples is about 8-10 grams and she was wondering how much sample we needed for the C:N analysis. She allocated 6.5 grams to the ashless weights and NIR, with the rest going into the scintillation vials for C:N. I told her to put the rest of the sample into a scint vial for C:N, but in the future to prioritize samples for C:N analysis over the ashless weights. This is something that Resham directed us to do with some of our smaller samples.
Do we have any numbers for the minimum amount of sample needed to accomplish each of these analyses? For example, do we need a full 20 ml sample for the NIR, or would it be ok with 2 grams? I don't know if these need to go in the protocol, but they would be nice to have.
I'm also a little concerned about this site going forward. If they only have ~10 grams of sample from the T0 bags, they're probably going to have really small amounts of biomass by T3.

@ethansweep Ethan - this is a great response.
I am going to tag the rest of the on-farm hotline squad so everyone is comfortable with this, since I have got other questions about sample size.  @brianwdavis @elhenriq @aidabagheri @annabirnbaum
And Lindsey emailed me as well, and this was my response:
Sample priority:
NIR - a single sample (T0-A or B) 5 grams
C/N - scint vial - analysis only takes about a thimble full of sample (~10 mg)
Ash 1 gram bag - (ash can take as little as 0.5 grams, or even less)
Then save any remaining in archive.
Samples can be pretty small and still have enough for everything. 8 to 10 grams is more than enough to do all analysis. No one should be overly concerned about sample size - even as the bags start decomposing. To successfully get both CN AND Ash we still only need less than a gram per sample.


v3.5.0 : Added functionality for attribute query and response filtering

Can one of the admins verify this patch?

ok to test

retest this please

retest this please


Modify COC Page to Update Spamming Rule

Pre-Submission Checklist

[X] Your pull request targets the staging branch of freeCodeCamp.
[X] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[X] You have only one commit (if not, squash them into one commit).
[X] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[X] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[X] Tested changes locally.
[X] Closes currently open issue (replace XXXX with an issue no): Closes #15208

Description

Modified the COC page to update the spamming rule to include the over posting (i.e posting pictures every minute) of images, video and text. The rule will be updated to: "Spamming includes posting off-topic messages to disrupt discussions, promote a product, solicit donations, or flood discussions with consecutive large pictures, videos, streams, and text."

this is the original request for the modification https://github.com/freeCodeCamp/freeCodeCamp/issues/15208

@jrliv Thanks a lot for the pull request and
:sparkles: congrats on your first contribution to freeCodeCamp! :sparkles:

@raisedadead Awesome! Thanks!


Feature: use Musicmanager option for gmsearch

gmsearch uses mobileclient, which doesn't work if you have 2-factor authentication enabled, but the same functionality can be provided by musicmanager and oauth.

Music Manager can't get All Access library tracks, so it doesn't provide the same functionality. Also, you can use an app-specific password for the Mobileclient unlike the Webclient.


ascan of Cryostream700 at XPD does not wait for move completion

When using the Cryostream700 as a positioner in ascan, the scan routine does not wait for each move of the CS700 to complete.

There was a stray break inside of this while loop: https://github.com/NSLS-II/ophyd/blob/master/ophyd/runengine/runengine.py#L156 which was causing the scan routine to not actually wait for anything to complete.
This was a problem on the XPD workstation only. This change to the source code of ophyd was not checked in to git so we have no one to blame!  Suffice it to say that the cryostream can now be scanned.


Fix broken ExportToLdadAction

In 18.1.1-3, the damagepath plugin was throwing errors when using the contextual menu on products pointing to the ExportToLdadAction, which had been removed. I removed the appropriate lines from plugin.xml to rectify this error.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add gcsweb

This is a VERY simple webserver that offers selected GCS buckets for browsing.
The HTML is pathetic, but it seems to work (it's as fast as the GCE-hosted
browser (which is not fast), but far less pretty).
This is just the main.  There's no test for it.  The HTML needs help.  There's no Dockerfile or Makefile.

This change is

recomputing cla status...

CLA is failing because of multiple authors.  Need manual override.  This should be moved from contrib to its own repo, though.

cncf CLA was complaining about you before the multiple authors....

@foxish this is a problem though, that the pinger is assuming (and posting) that the cncf failure is because @thockin didn't sign....

@foxish can we make the cla pinger clean up stale messages?

@eparis Yes, I'll add the stale comments cleanup to the CLA munger. But in this case, @thockin did sign and is authorized. It's the other author of a particular commit, @nebril who hasn't.

@eparis Oh I see what you mean, it's pinging the wrong person. Will open an issue for this.

@foxish but the pinger is still yelling at thockin.  i think we need to look at the status
thockin authorized, but 1 other problem
and output some more useful message.

@eparis Yeah, just saw that. You're right, we should do something smarter. I don't know if there is a way to get the commit author's name who hasn't signed the CLA from the status. I'll ask the LF folks about this. Else, we might want to do a manual check among all commit authors.

@thockin do you want me to look at this PR? or do you want to reopen it somewhere else? (maybe under k8s.io?)

Jeff,
What think about moving it to test-infra ?
On Fri, Sep 30, 2016 at 1:20 PM, Jeff Grafton<EMAIL_ADDRESS>wrote:

@thockin https://github.com/thockin do you want me to look at this PR?
or do you want to reopen it somewhere else? (maybe under k8s.io?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/contrib/pull/1276#issuecomment-250842625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVJv-LVaSctKdG5K_akVkW9x1jj4sks5qvW8EgaJpZM4I-pSb
.


Feature/better alertmanager interface

Reopening Leon's pull request from my branch so I can make changes as necessary. Also added one commit to make it work right.

This change works well together with https://github.com/canonical/alertmanager-operator/pull/13

@sed-i Development paradigms have changed a lot in the last 3 weeks. Are we sure we want the consumer emitting events instead of updating the databag and relying on relation_changed?

@sed-i Development paradigms have changed a lot in the last 3 weeks. Are we sure we want the consumer emitting events instead of updating the databag and relying on relation_changed?

The use of custom events and StoredState is the most simple and concise solution I found to the challenges encountered.
Relying on relation_changed being handled by the consumer charm means that implementation detail of alertmanager-operator side would be implicitly coded in prometheus. I would rather abstract it away with interfaces using the alertmanager library.
Can we take a deeper look into this via issues against alertmanager?

moving back to https://github.com/canonical/prometheus-operator/pull/48 and closing this one


Improve zstd-sys/build.rs: Add fallback to thin lto and -Oz, and enable LTO only for clang-like compiler

Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

@gyscos Can you review this PR please?

@gyscos Pinging

Unfortunately I'm not sure is_flag_supported does its job: it seems that for some versions of gcc, it will accept a flag, even though this flag leads to a non-working compilation.
I'm still trying to figure out how to safely enable any form of lto on GCC that will work on both recent gcc version, older gcc version used in cross (gcc 9), and the gcc used in the windows-gnu target...

Unfortunately I'm not sure is_flag_supported does its job: it seems that for some versions of gcc, it will accept a flag, even though this flag leads to a non-working compilation.
I'm still trying to figure out how to safely enable any form of lto on GCC that will work on both recent gcc version, older gcc version used in cross (gcc 9), and the gcc used in the windows-gnu target...

Perhaps we should just compile a simple hello-world with lto to see if that works?
If it can be compiled, then it's likely it would work.
I can try implementing that in this PR.

Actually, do we need to turn on O2 manually? What's the advantage vs letting cc pick the optimization level?

Actually, do we need to turn on O2 manually? What's the advantage vs letting cc pick the optimization level?

It's only turned on if feature "thin" is enabled.
Using -O2 probably generates smaller code than -O3 (or even -O1 sometimes).

I realize it's only when none of Oz or Os works (not sure when that happens),

I remember that gcc doesn't support -Oz and only -Os?

Unfortunately I'm not sure is_flag_supported does its job: it seems that for some versions of gcc, it will accept a flag, even though this flag leads to a non-working compilation.
I'm still trying to figure out how to safely enable any form of lto on GCC that will work on both recent gcc version, older gcc version used in cross (gcc 9), and the gcc used in the windows-gnu target...

I checked Build::is_flag_supported and it actually attempts to compile the file with the flag provided.
I think the problem lies in this line, where it does not check the exit status of the command and assumes that if the stderr is empty, everything works as expected.

@gyscos I've opend https://github.com/rust-lang/cc-rs/pull/757 which might help fix the LTO issue in zstd.


Verification Service blog (2.15) has links to deleted FAQs

Where to find the issue
The blog announcement for CWA Version 2.15:

https://www.coronawarn.app/en/blog/2021-12-20-cwa-2-15/ "Corona-Warn-App simplifies certificate checks when booking tickets"
https://www.coronawarn.app/de/blog/2021-12-20-cwa-2-15/ "Corona-Warn-App vereinfacht die Zertifikatsprüfungen bei der Ticketbuchung"

Describe the issue
The blog articles contain links to FAQ articles which have been deleted (see PR https://github.com/corona-warn-app/cwa-website/pull/2734).

https://www.coronawarn.app/en/blog/2021-12-20-cwa-2-15/ "Corona-Warn-App simplifies certificate checks when booking tickets", links to deleted articles:

https://www.coronawarn.app/en/faq/#val_service_no_valid_dcc "Why do I get the message that there is no suitable certificate?"
https://www.coronawarn.app/en/faq/#val_service_result "Why is my certificate not verifiable or not recognized?"

https://www.coronawarn.app/de/faq/#val_service_result "Warum ist mein Zertifikat nicht prüfbar oder wird nicht anerkannt?"

The deleted article anchors #val_service_no_valid_dcc and #val_service_result are redirected to #val_service_basics, however the redirected anchor does not contain the answers to the questions from #val_service_no_valid_dcc and #val_service_result. https://www.coronawarn.app/en/faq/results/#val_service_basics provides no further technical details about the online verification service at this time.
Suggested change
Remove the references in blog/2021-12-20-cwa-2-15/ to #val_service_no_valid_dcc and #val_service_result.

PR #2746 is submitted to resolve this issue.


Update point-in-time-restore-overview.md

@normesta
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Update join.mdx

Let's make our optional steps have a boundary so people can ignore to follow the required steps. @Nixon-Samuel


fix: Wrap relayer address in GMPHandler object

Description
closes: #XXXX

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (96c089c) 16.10% compared to head (671e789) 16.10%.

:exclamation: Current head 671e789 differs from pull request most recent head 36b099f. Consider uploading reports for the commit 36b099f to get more accurate results

Files
Patch %
Lines

app/gmpmiddleware/handler.go
0.00%
5 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #345      +/-   ##
==========================================
- Coverage   16.10%   16.10%   -0.01%
==========================================
  Files          78       78
  Lines       18769    18770       +1
==========================================
  Hits         3022     3022
- Misses      15594    15595       +1
  Partials      153      153

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to handle processEventErrorHandler errors inV2

Looks like V1 had a way to handle processEventErrorHandler errors, but V2 error handling looks like it only allows handling the error part.
Not sure how to handle the below error message, we would like to reduce noise in our logs.
[WARN]  bolt-app Authorization of incoming event did not succeed. No listeners will be called.
[ERROR]   An incoming event was not acknowledged within 3 seconds. Ensure that the ack() argument is called in a listener.

I do have a PR https://github.com/slackapi/bolt-js/pull/1883 but happy to learn how to handle it :)

Hi @moizjv, thank you for your question. We apologize if the documentation was unclear. Only the global app.error() error handler was enhanced in v2, while the additional handlers such as processEventErrorHandler were introduced in v3. Therefore, you'll need to upgrade to the latest version to use these additional handlers. Once you've upgraded, the code provided in the documentation should work as expected.

Thanks again for writing in! Let me close this issue now!

Ohh I see :) thanks that makes sense.

@seratch Sorry to ping you on ticket again, but looking into https://github.com/slackapi/bolt-js/blob/main/src/App.ts#L79-L109 i dont see option for processEventErrorHandler that is mentioned in documentation here , am I missing something ?


Imported Works do not display a date uploaded

When a file is imported it is not showing a date uploaded on My Work Listing.

The importer is likely not putting the information into the correct field. Or the display is not showing the other metdata field that is not the system date.

This is actually related to how Active Fedora parses attributes during update_attributes.  It is storing a string for a date field, which causes the field to get into solr incorrectly.
class loaded by import
irb(main):005:0> gw
=> #<GenericWork id: "7w62f831t", head: [#<ActiveTriples::Resource:0x3fc98b38fde4(#<ActiveTriples::Resource:0x007f931671fbc8>)>], tail: [#<ActiveTriples::Resource:0x3fc98ad189ac(#<ActiveTriples::Resource:0x007f9315a31358>)>], depositor: "cam156", title: ["11_Mapping.bam"], date_uploaded: "2016-11-29T19:19:17.809+00:00", date_modified: "2016-11-29T19:19:17.809+00:00", state: nil, owner: nil, label: "11_Mapping.bam", relative_path: nil, import_url: "https://dl.boxcloud.com/d/1/Y3rf2AiSx0qFIGeNTaUUbk...", part_of: [], resource_type: [], creator: ["Cole, Carolyn A"], contributor: [], description: [], keyword: ["bam4"], rights: ["http://creativecommons.org/licenses/by-nc-nd/3.0/us/"], rights_statement: [], publisher: [], date_created: [], subject: [], language: [], identifier: [], based_near: [], related_url: [], bibliographic_citation: [], source: [], proxy_depositor: nil, on_behalf_of: nil, arkivo_checksum: nil, access_control_id: "2f153c8c-b9ec-4197-8dbd-7510f18de26d", representative_id: "n8p58pf458", thumbnail_id: "n8p58pf458", admin_set_id: nil, embargo_id: nil, lease_id: nil>
irb(main):007:0> gw.date_uploaded.class
=> String

class created by upload into the system
irb(main):005:0> gw2
=> #<GenericWork id: "kpr76f389n", head: [#<ActiveTriples::Resource:0x3fc98913a154(#<ActiveTriples::Resource:0x007f93122742a8>)>], tail: [#<ActiveTriples::Resource:0x3fc9891221a8(#<ActiveTriples::Resource:0x007f9312244350>)>], depositor: "cam156", title: ["Boardingpass_WW761.pdf"], date_uploaded: "2017-01-27 13:23:22", date_modified: "2017-01-27 13:23:22", state: nil, owner: nil, label: nil, relative_path: nil, import_url: nil, part_of: [], resource_type: ["Article"], creator: ["Cole, Carolyn A"], contributor: [], description: ["boarding pass"], keyword: ["boarding"], rights: ["https://creativecommons.org/licenses/by-sa/4.0/"], rights_statement: [], publisher: [], date_created: [], subject: [], language: [], identifier: [], based_near: [], related_url: [], bibliographic_citation: [], source: [], proxy_depositor: nil, on_behalf_of: "", arkivo_checksum: nil, access_control_id: "cced4e73-a07b-430e-8f2e-0a4428fa203d", representative_id: "0cf95j992s", thumbnail_id: "0cf95j992s", admin_set_id: nil, embargo_id: nil, lease_id: nil>
irb(main):006:0> gw2.date_uploaded.class
=> DateTime

Created a ticket for a longer term fix (https://github.com/projecthydra/active_fedora/issues/1199) but just planning to parse the date for import


End process

Is it possible to end the spawned process?

@Cwright017 yes, you can kill process group of you spawned process with electron-sudo. this package very helpful tree-kill


Xiaomi Multimode Gateway - compiled MultiPAN RCP firmware (EZSP Firmware: <IP_ADDRESS> build 0)

Hello,
If it seems to be worthwhile to incorporate into this project, see my repo at https://github.com/zalatnaicsongor/MGLGWFW
Instructions:

download script.sh to /data/script.sh
The baud of the multipan RCP firmware is 115200, the EZSP version is "Firmware: <IP_ADDRESS> build 0"
Install the Silicon Labs Multiprotocol addon in HA or use a standalone cpcd instance
execute the script, I tested it on the latest custom version of the firmware.

Home Assistant setup:

Currently due to some weird bug in the openmiio_agent code, cpcd does not connect through the serial proxy provided by openmiio_agent, to work around the issue, use ser2net /data/ser2net -d -C '7000:raw:0:/dev/ttyS2:115200 8DATABITS NONE 1STOPBIT'
Note: ser2net is downloaded by the firmware update script
Configure the Silicon Labs Multiprotocol addon with the following options:

device: /dev/ttyS2
baudrate: "115200"
flow_control: false
autoflash_firmware: false
cpcd_trace: true
otbr_enable: true
otbr_log_level: debug
otbr_firewall: true
network_device: {gatewayIP}:7000
stdout_trace: true

ZHA should automatically discover the socket created by the multiprotocol addon, for zigbee2mqtt use tcp://core-silabs-multiprotocol:9999

Configure the Silicon Labs Multiprotocol addon with the following options:

device: /dev/ttyS2

I can't save add-on config with Device '/dev/ttyS2'
Failed to save add-on configuration, Device '/dev/ttyS2' does not exist in Silicon Labs Multiprotocol (core_silabs_multiprotocol). Got {'device': '/dev/ttyS2', 'baudrate': '115200', 'flow_control': False, 'autoflash_firmware': False, 'cpcd_trace': True, 'otbr_enable': True, 'otbr_log_level': 'debug', 'otbr_firewall': True, 'network_device': '<IP_ADDRESS>:7000', 'stdout_trace': True}

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.8


[feat] warn if svelte not found in dependencies or peerDependencies

This allows vite-plugin-svelte to detect which libraries are Svelte libraries

duh. thank you!

wow Github playing tough, @Conduitry you need to approve as well since you requested changes, else we can't merge 😅

doesn't stop you if you're an admin I guess :laughing:


Quest cannot be started: "Error execution reverted: level not found"

level = 1
questV2.start_quest(quest_contract, my_heroes_id, attempts, level, private_key, w3.eth.getTransactionCount(account_address), gas_price_gwei, tx_timeout)
What is the level? Tried it with the current level of the hero, but this didn't work and currently I don't know what I need to enter there.
Error Message is always: "Error execution reverted: level not found"

Ok, still not sure what exactly the level value is for, but it is a step further now.
Sadly a new issue:
quest.start_quest(quest_contract, my_heroes_id[0], attempts, level, private_key, w3.eth.getTransactionCount(account_address), gas_price_gwei, tx_timeout)
  File "/home/pat/environments/dfk/bot/dfk/quests/quest_v2.py", line 11, in start_quest
    return quest_core_v2.start_quest(quest_address, hero_ids, attempts, level, private_key, nonce, gas_price_gwei,
  File "/home/pat/environments/dfk/bot/dfk/quests/quest_core_v2.py", line 77, in start_quest
    tx = contract.functions.startQuest(hero_ids, quest_address, attempts, level).buildTransaction(
  File "/home/pat/environments/dfk/lib/python3.8/site-packages/web3/contract.py", line 878, in __call__
    clone._set_function_info()
  File "/home/pat/environments/dfk/lib/python3.8/site-packages/web3/contract.py", line 883, in _set_function_info
    self.abi = find_matching_fn_abi(
  File "/home/pat/environments/dfk/lib/python3.8/site-packages/web3/_utils/contracts.py", line 163, in find_matching_fn_abi
    raise ValidationError(message)
web3.exceptions.ValidationError:
Could not identify the intended function with name `startQuest`, positional argument(s) of type `(<class 'int'>, <class 'str'>, <class 'int'>, <class 'int'>)` and keyword argument(s) of type `{}`.
Found 1 function(s) with the name `startQuest`: ['startQuest(uint256[],address,uint8,uint8)']
Function invocation failed due to no matching argument types.

ok, so I guess in the start_quest function it must be my_heroes_id and not my_heroes_id[0] .
So back to original error: "web3.exceptions.ContractLogicError: execution reverted: level not found"

setting level to 0 solved the issue.

Yeah I think this referred to the level of the profession quest not the hero.


Added back "display: none" properties on the automate/import screen

Fixes #8098

@eclarizio please verify

:+1: Looks good


Classes with the same fully-qualified name are included in two different libraries

Hi, in org.ektorp.parent-1.5.0, classes with the same fully-qualified name org.apache.commons.logging.LogFactory are included in two different libraries, i.e., org.slf4j:jcl-over-slf4j:1.6.4 and commons-logging:commons-logging:1.1.1.
According to "first declaration wins" class loading strategy, only the class in org.slf4j:jcl-over-slf4j:1.6.4 can be loaded, and that in commons-logging:commons-logging:1.1.1 will be shadowed.
By further analyzing, your project expects to invoke method <org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()> in commons-logging:commons-logging:1.1.1. As it has been shadowed, so that this method defined in org.slf4j:jcl-over-slf4j:1.6.4 is actually forced to be referenced via the following invocation path:
<org.ektorp.android.http.AndroidHttpClient$Builder: org.apache.http.conn.ClientConnectionManager configureConnectionManager(org.apache.http.params.HttpParams)> D:\testcase\TestProject\Ektorp-org.ektorp.parent-1.5.0\org.ektorp.android\target\classes
<org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager: void <init>(org.apache.http.params.HttpParams,org.apache.http.conn.scheme.SchemeRegistry)> D:\cEnvironment\repository\org\apache\httpcomponents\httpclient\4.3\httpclient-4.3.jar
<org.apache.commons.logging.LogFactory: org.apache.commons.logging.Log getLog(java.lang.Class)> D:\cEnvironment\repository\org\slf4j\jcl-over-slf4j\1.6.4\jcl-over-slf4j-1.6.4.jar
<org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()>

Although both of these two conflicting classes contain the referenced method (with the same signature), they have completely different implementations. This issue will not lead to runtime crashes, but it can introduce inconsistent semantic hehavior by changing the control flows and data flows.
Solution:
Adjust the declaration order of org.slf4j:jcl-over-slf4j:1.6.4 and commons-logging:commons-logging:1.1.1 in pom,xml to load class org.apache.commons.logging.LogFactory in commons-logging:commons-logging:1.1.1.
Dependency tree-----
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ org.ektorp.android ---
[INFO] org.ektorp:org.ektorp.android:jar:1.5.0
[INFO] +- org.ektorp:org.ektorp:jar:1.5.0:compile
[INFO] |  +- org.apache.httpcomponents:httpclient:jar:4.3:compile
[INFO] |  |  +- org.apache.httpcomponents:httpcore:jar:4.3:compile
[INFO] |  |  - commons-codec:commons-codec:jar:1.6:compile
[INFO] |  +- org.apache.httpcomponents:httpclient-cache:jar:4.3:compile
[INFO] |  |  - (org.apache.httpcomponents:httpclient:jar:4.3:compile - omitted for duplicate)
[INFO] |  +- commons-io:commons-io:jar:2.0.1:compile
[INFO] |  +- org.slf4j:slf4j-api:jar:1.6.4:compile
[INFO] |  +- org.slf4j:jcl-over-slf4j:jar:1.6.4:runtime
[INFO] |  |  - (org.slf4j:slf4j-api:jar:1.6.4:runtime - omitted for duplicate)
[INFO] |  +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.7:compile
[INFO] |  +- com.fasterxml.jackson.core:jackson-core:jar:2.6.7:compile
[INFO] |  +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.7:compile
[INFO] |  |  +- (com.fasterxml.jackson.core:jackson-annotations:jar:2.6.7:compile - version managed from 2.6.0; omitted for duplicate)
[INFO] |  |  - (com.fasterxml.jackson.core:jackson-core:jar:2.6.7:compile - omitted for duplicate)
[INFO] |  - (net.sourceforge.findbugs:annotations:jar:1.3.2:compile - omitted for duplicate)
[INFO] +- com.google.android:android:jar:<IP_ADDRESS>:provided
[INFO] |  +- commons-logging:commons-logging:jar:1.1.1:provided
[INFO] |  +- (org.apache.httpcomponents:httpclient:jar:4.0.1:provided - omitted for conflict with 4.3)
[INFO] |  +- org.khronos:opengl-api:jar:gl1.1-android-2.1_r1:provided
[INFO] |  +- xerces:xmlParserAPIs:jar:2.6.2:provided
[INFO] |  +- xpp3:xpp3:jar:1.1.4c:provided
[INFO] |  - org.json:json:jar:20080701:provided
[INFO] +- org.mockito:mockito-all:jar:1.8.5:test
[INFO] +- junit:junit:jar:4.8.2:test
[INFO] - net.sourceforge.findbugs:annotations:jar:1.3.2:compile
Thanks!
Best regards,
Coco

Code snippet of <org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()> in org.slf4j:jcl-over-slf4j:jar:1.6.4 (loaded version):

Code snippet of <org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()> in commons-logging:commons-logging:1.1.1 (shadowed but expected to invoke method):

....
As a result, method this conflicting method included in commons-logging:commons-logging:1.1.3 deals with completely different cases, which changes the control flows and data flows. So being forced to use this method in org.slf4j:jcl-over-slf4j:jar:1.6.4 may lead to inconsisitent semantic behaviors.

@helun May I pull a request to fix it? 8)
Thanks again.

@rayzhang0603
May I submit a PR to fix this problem?
Thanks again for your attention.

@HelloCoCooo you should @ the developer of this project :)

@rayzhang0603 Sorry for that...

Hi @HelloCoCooo
Maybe I did not understand. If so please tell me.
It seem to me that your issue is related to your runtime classpath.
I don't get why it needs to be fixed in Ektorp.
Only you can control your application classpath.
If your application classpath somehow depends on maven dependencies, you should be able to exclude whatever you dislike, or even reorder them.
I hope this helps.

@YannRobert
Thanks for your quick reply.
These two libraries (org.slf4j:jcl-over-slf4j:1.6.4 and commons-logging:commons-logging:1.1.1) containing conflicting class are introduced by Ektorp, we can  control my own application classpath, but I cannot revise Ektorp's dependencies.
As in Ektorp ,  httpcomponents  depends on commons-logging rather than org.slf4j:jcl-over-slf4j, when httpcomponents is forced to reference to the class org.apache.commons.logging.LogFactory in org.slf4j:jcl-over-slf4j:1.6.4 due to dependency conflicts (first declaration wins), the code hehaviors will change.
The better solution is to reverse the declaration order in Ektorp's pom file.
May I submit a PR to fix this problem?
This fix will not affect other libraries or classes.
Thanks again.
Best,
Coco

Sure, you can submit a PR.
Maybe your PR will help to understand.
But please try to change your own project, exclude any transitive dependencies about logging from Ektorp, and include the depencencies you want instead.
I am still not convince that this is an issue that concerns Ektorp build.

@YannRobert Ok. I understand.
Maybe the semantic hehavior changes are not harmful to Ektorp.
Then I can close this issue.
Thank you.

@YannRobert
Hi, a lots of issues are caused by this conflicting class:
https://github.com/search?p=3&q=org.apache.commons.logging.LogFactory&type=Issues
If you discover unexpected code behaviors due to such conflicting class, feel free to reopen this issue,
I still happy to fix it.


Add incident reporting platform backend API and OONI Run v2 backend API

Add initial version of the incident management CRUD, the OONIRun CRUD and a small geolocation helper for the probes.
Also some refactoring. #676
https://docs.google.com/document/d/1TdMBWD45j3bx7GRMIriMvey72viQeKrx7Ad6DyboLwg/

Cherry-picking to master done as discussed.

Okay @FedericoCeratto, also https://github.com/ooni/backend/pull/678/commits/77759dad1f740b902b86a7ae5502a2fee174b017 is LGTM 🐳 and I'd say we can cherry-pick it as well. This leaves us with one last commit to review. I will continue my review tomorrow. Thank you!

1.0.58~pr678-94  deployed on -test and FSN

This PR is also related to https://github.com/ooni/backend/issues/630


ANN/ANN.h missing

#include <ANN/ANN.h> is used by lib/python3.10/site-packages/annlib_adaptbx/include/annlib_adaptbx/ann_adaptor.h, currently itself included by DIALS indexing.
The lib/libann.so (built by annlib_adaptbx using the annlib sources) and share/cctbx/annlib_adaptbx/include/ANNSELF_INCLUDE/ANN.h from the build/ folder are included, so it looks like it's mostly a simple case of just being missed. I've never worked out the reason for the ANN/ANNSELF_INCLUDE duplication for headers (duplication except the #define guard, and namespace), but copying them both into the share/cctbx/annlib_adaptbx/include folder might be sufficient?
I don't know what the state of this was when https://github.com/conda-forge/cctbx-base-feedstock/issues/12, but that implies it was missing and most of it seems to actually be included now.

I think #12 was about a declared dependency that wasn't actually required. Vendoring ann is probably not the preferred solution since that's already a separate conda-forge package (https://github.com/conda-forge/ann-feedstock)

Hmm, this makes it a little more complicated, because IIRC you aren't supposed to vendor other libraries and I don't know what differences the annlib_adaptbx-compiled version of ann has (other than being v1.1 instead of v1.1.3).
ann also does a lib/libann.so, so that means that this package is clobbering, if installed afterwards.

Clobbering lib/libann.so is not desired so we can probably rename the library and related linking.
@nksauter and @phyy-nx What else uses annlib?

Annlib is used in labelit, possibly dials 1D-FFT, and for various ad-hoc
nearest neighbor applications in XFEL.
It should be treated as a required dependency for XFEL.
Nick
On Mon, Apr 4, 2022 at 10:29 AM Billy K. Poon @.***>
wrote:

Clobbering lib/libann.so is not desired so we can probably rename the
library and related linking.
@nksauter https://github.com/nksauter and @phyy-nx
https://github.com/phyy-nx What else uses annlib?
—
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/cctbx-base-feedstock/issues/46#issuecomment-1087823392,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ24VXCDHD52SHLC33K3TTVDMRG7ANCNFSM5SPPZIOA
.
You are receiving this because you were mentioned.Message ID:
@.***>

What does the annself_include variant actually do? Can this be a separately named library and use upstream libann?

The two instances represent two distinct algorithms:  nearest neighbors
with or without inclusion of self.  The source code has to be copied and
edited to provide both algorithms. --Nick
On Mon, Apr 4, 2022 at 11:29 AM Nicholas Devenish @.***>
wrote:

What does the annself_include variant actually do? Can this be a
separately named library and use upstream libann?
—
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/cctbx-base-feedstock/issues/46#issuecomment-1087878116,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ24VXGGAKY6CEC6DJ7CH3VDMYHHANCNFSM5SPPZIOA
.
You are receiving this because you were mentioned.Message ID:
@.***>

So ANN/ANN.h is included now?

No, I just renamed the library to avoid clobbering. The modules directory from bootstrap.py has annlib which will have that header. Or do you want me to put a copy into ${CONDA_PREFIX}/share/cctbx/annlib_adaptbx/include/ANN?

I think that'd be the best option; if you want to use ANNSELF_INCLUDE/ANN.h, then you have already added that exact path to the include search paths - but without copying the files in there also you only have the header files to make use of 50% of the symbols compiled into libann_cctbx.
The headers are also included in conda-forge/ann, but then you need to be careful to constrain versions to match the one that cctbx uses internally (and would have a different set of symbols for binaries linking to libann than in ones linking to libann_cctbx).
Since the symbols are being included in this package anyway, it seems to make sense to include the headers to use them.

I'll make another PR later today to add that.

Awesome, thanks!

The headers should now be available in ${CONDA_PREFIX}/share/cctbx/annlib_adaptbx/include/ANN on unix and %CONDA_PREFIX%\Library\share\cctbx\annlib_adaptbx\include\ANN on Windows.


DJANGO_SETTINGS_MODULE doesn't point to a settings file

Description

In manage.py, line 10, the environment variable DJANGO_SETTINGS_MODULE doesn't point to a settings file.
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "cc_licenses.settings")
Reproduction

Check if you don't have a DATABASE_URL key in the virtual environment.
Run any management command, such as manage.py runserver
See error.
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

Expectation

It is expected that it should point to the local settings file.
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "cc_licenses.settings.local")
Environment

Device: Laptop
OS: Ubuntu 20.04 LTS

Resolution

[x] I would be interested in resolving this bug.

we can use dotenv to read environment variables from .env

we can use dotenv to read environment variables from .env

Hi @pratikdaigavane
Please refrain from working on untriaged issues.

Hi @pratikdaigavane
Please refrain from working on untriaged issues.

@sp35 oh sorry, my bad.

@sp35 oh sorry, my bad.

Hey @sp35  Can i work on this this Issue?

Hey @sp35  Can i work on this this Issue?

@ayushmankumar7 I am not a part of CC but issues with label "🚦 status: awaiting triage" are not available for work. From what I know this repo isn't ready for community contributions yet. To stay updated about this repo join the cc-dev-licenses channel on CC's Slack server.

@ayushmankumar7 I am not a part of CC but issues with label "🚦 status: awaiting triage" are not available for work. From what I know this repo isn't ready for community contributions yet. To stay updated about this repo join the cc-dev-licenses channel on CC's Slack server.

@dravadhis  Thanks for the info. Sure, would love to join the community!

@dravadhis  Thanks for the info. Sure, would love to join the community!

Now that this is ready for work shall I take this up @TimidRobot?

Oh my bad, I probably missed there was an example local.py which was there in my mind when I created the issue.

I'll work on adding developer instructions that include creating local settings file.
@TimidRobot I see it's already there.
(cc_licenses)$ cp cc_licenses/settings/local.example.py cc_licenses/settings/local.py


Make installation instructions more comprehensive

It was pretty tricky to work out what to do... Hopefully these instructions help someone. Feel free to modify or rewrite anything I've written if you don't like it 😃

Coverage remained the same at 92.244% when pulling 3ee50d0c2066bb2734a81719220d187768b30a23 on Daniel15:patch-2 into f2fe21934cbff87cd054601ab724978bcef1be92 on joohoi:master.

<IP_ADDRESS>/24 is explicitly reserved for use in documentation (RFC 5737)
which is why I used that particular IP. I didn't want readers to mistake it
for an actual internal IP.
I'll take a look at the rest of your comments this week some time :)
Sent from my phone.
On Mon, Mar 19, 2018, 1:29 AM Joona Hoikkala<EMAIL_ADDRESS>wrote:

@joohoi requested changes on this pull request.
Thanks for the PR! I think this is really valuable information for the
users. However I feel that while the step 6 (adding NS and A recods) should
be added to the installation instructions, the other points should probably
be placed under a new title of Troubleshooting for clarity.
In README.md
https://github.com/joohoi/acme-dns/pull/64#discussion_r175355731:

+5) Confirm that acme-dns is working by performing a DNS lookup for one of the predefined records configured in the config.cfg file: dig @<IP_ADDRESS> auth.example.com. This should be logged in acme-dns' output:
+ +DEBU[0003] Answering question for domain                 domain=auth.example.com. qtype=A +

+If this request times out, ensure that port 53 is open in your firewall.
+
+6) On your domain's regular DNS server, add an NS record for auth.example.com pointing to ns.auth.example.com, and an A record for ns.auth.example.com pointing to <IP_ADDRESS> If using IPv6, use an AAAA record rather than an A record.
+
+7) Wait a few minutes for DNS changes to propagate
+
+8) Confirm that DNS lookups for the acme-dns subdomain works as expected: dig auth.example.com
+
+9) Call the /register API endpoint to register a test domain:
+```
+$ curl -X POST -d "{}" http://auth.example.com/register
The data for register endpoint can be left out if no whitelisting is
needed.
In README.md
https://github.com/joohoi/acme-dns/pull/64#discussion_r175356446:

@@ -111,14 +111,54 @@ Check out how in the INSTALL section.

Installation
+In all the commands listed below:
+- example.com is your domain name
+- auth.example.com is the subdomain you want to use for acme-dns
+- <IP_ADDRESS> is the public IP address of the system running acme-dns
I feel that in examples it would be better to use address in a private
address space defined by RFC 1918 https://tools.ietf.org/html/rfc1918
In README.md
https://github.com/joohoi/acme-dns/pull/64#discussion_r175356839:

+If this request times out, ensure that port 53 is open in your firewall.
+
+6) On your domain's regular DNS server, add an NS record for auth.example.com pointing to ns.auth.example.com, and an A record for ns.auth.example.com pointing to <IP_ADDRESS> If using IPv6, use an AAAA record rather than an A record.
+
+7) Wait a few minutes for DNS changes to propagate
+
+8) Confirm that DNS lookups for the acme-dns subdomain works as expected: dig auth.example.com
+
+9) Call the /register API endpoint to register a test domain:
+ +$ curl -X POST -d "{}" http://auth.example.com/register +{"username":"eabcdb41-d89f-4580-826f-3e62e9755ef2","password":"pbAXVjlIOE01xbut7YnAbkhMQIkcwoHO0ek2j4Q0","fulldomain":"d420c923-bbd7-4056-ab64-c3ca54c9b3cf.auth.example.com","subdomain":"d420c923-bbd7-4056-ab64-c3ca54c9b3cf","allowfrom":[]} +
+
+10) Call the /update API endpoint to set a test TXT record:
It could be useful to underline that the TXT content needs to be exactly
43 characters long. That's a common source of confusion.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/joohoi/acme-dns/pull/64#pullrequestreview-104868492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFnHX8SJ4Hf4TDrminw8l8l17ue7eEMks5tf2xMgaJpZM4Svqnd
.

<IP_ADDRESS>/24 is explicitly reserved for use in documentation (RFC 5737)

Awesome! That's completely fine in this case. TIL :)

@joohoi I moved some stuff around, let me know what you think of it now :)

A lot of people turn off DNS on their firewall (e.g. iptables, ufw, etc )
I think it would be a good addition to remind people to ensure port 53 is open.

LGTM! merging

Consider updating the systemd section to include this step:
"As of systemd 232 (released in 2017) you can edit /etc/systemd/resolved.conf and add this line:
DNSStubListener=no"
Otherwise the Stub Listener blocks ACME-DNS


cmd/cgo: Null pointer is accessed in C code, causing the stack to be destroyed

What version of Go are you using (go version)?

$ go version
go version go1.14.3 linux/amd64

Does this issue reproduce with the latest release?
YES
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/fananchong/.cache/go-build"
GOENV="/home/fananchong/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/fananchong/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build984316541=/tmp/go-build -gno-record-gcc-switches"

What did you do?

test.cpp:
#include <stdio.h>
#include <assert.h>
#include <string.h>
#include <stdlib.h>
#include "test.h"

class A
{
public:
    void release() { free(ptr); }

private:
    void *ptr;
};

void test_crash2()
{
    A *a = (A *)0;
    a->release();
}

test.h:
#pragma once

#if __cplusplus
extern "C"
{
#endif

    extern void test_crash2();

#if __cplusplus
}
#endif

main.go:
package main

/*
#include "test.h"
#include <stdlib.h>
#cgo LDFLAGS: -L. -ltest
*/
import "C"

import (
	_ "fmt"
)

func main() {
	C.test_crash2()
	select {}
}

build cmd:
gcc -I. -g3 -O0 -c test.cpp
ar cr libtest.a test.o
go build main.go

then run env GOTRACEBACK=crash ./main
the core dump is:
(gdb) bt
#0  runtime.raise () at /usr/local/go/src/runtime/sys_linux_amd64.s:165
#1  0x000000000044435b in runtime.dieFromSignal (sig=6) at /usr/local/go/src/runtime/signal_unix.go:729
#2  0x00000000004447ee in runtime.sigfwdgo (sig=6, info=0xc000009af0, ctx=0xc0000099c0, ~r3=<optimized out>) at /usr/local/go/src/runtime/signal_unix.go:943
#3  0x0000000000443264 in runtime.sigtrampgo (sig=6, info=0xc000009af0, ctx=0xc0000099c0) at /usr/local/go/src/runtime/signal_unix.go:412
#4  0x000000000045efc3 in runtime.sigtramp () at /usr/local/go/src/runtime/sys_linux_amd64.s:389
#5  <signal handler called>
#6  runtime.raise () at /usr/local/go/src/runtime/sys_linux_amd64.s:165
#7  0x000000000044435b in runtime.dieFromSignal (sig=6) at /usr/local/go/src/runtime/signal_unix.go:729
#8  0x00000000004444ea in runtime.crash () at /usr/local/go/src/runtime/signal_unix.go:821
#9  0x0000000000459c61 in runtime.fatalthrow.func1 () at /usr/local/go/src/runtime/panic.go:1175
#10 0x0000000000430637 in runtime.fatalthrow () at /usr/local/go/src/runtime/panic.go:1168
#11 0x0000000000430472 in runtime.throw (s=...) at /usr/local/go/src/runtime/panic.go:1116
#12 0x000000000044430a in runtime.sigpanic () at /usr/local/go/src/runtime/signal_unix.go:679
#13 0x000000000047fa06 in A::release (this=0x47fa06 <A::release()+20>) at test.cpp:33
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

What did you expect to see?
code is:
    A *a = (A *)0;
    a->release();

I expect this pointer to be 0, and the stack is not destroyed
What did you see instead?
#13 0x000000000047fa06 in A::release (this=0x47fa06 <A::release()+20>) at test.cpp:33
this pointer is 0x47fa06 and Backtrace stopped: previous frame inner to this frame (corrupt stack?)

The traceback the runtime prints when crashing looks fine:
$ GOTRACEBACK=crash ./main
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x47fcf6]

runtime stack:
runtime.throw(0x4b0e0c, 0x2a)
	/home/khr/go1.14.7/src/runtime/panic.go:1116 +0x72 fp=0x7fff21843310 sp=0x7fff218432e0 pc=0x430512
runtime.sigpanic()
	/home/khr/go1.14.7/src/runtime/signal_unix.go:679 +0x46a fp=0x7fff21843340 sp=0x7fff21843310 pc=0x44449a

goroutine 1 [syscall]:
runtime.cgocall(0x47f560, 0xc000053f38, 0x0)
	/home/khr/go1.14.7/src/runtime/cgocall.go:133 +0x5b fp=0xc000053f08 sp=0xc000053ed0 pc=0x40508b
main._Cfunc_test_crash2()
	_cgo_gotypes.go:43 +0x41 fp=0xc000053f38 sp=0xc000053f08 pc=0x47f511
main.main()
	/home/khr/gowork/issue41070/main.go:15 +0x20 fp=0xc000053f48 sp=0xc000053f38 pc=0x47f550
runtime.main()
	/home/khr/go1.14.7/src/runtime/proc.go:203 +0x21a fp=0xc000053fe0 sp=0xc000053f48 pc=0x432b9a
runtime.goexit()
	/home/khr/go1.14.7/src/runtime/asm_amd64.s:1373 +0x1 fp=0xc000053fe8 sp=0xc000053fe0 pc=0x45d491

(But it of course doesn't contain the C part of the stack.)
I can reproduce the gdb problem you're seeing. When run under gdb directly, the stack trace is even weirder.
I have similar, but not identical, problems with lldb trying to get backtraces.
Delve handles this just fine, although it also doesn't show the C parts:
(dlv) bt
0  0x000000000045f011 in runtime.raise
   at /home/khr/go1.14.7/src/runtime/sys_linux_amd64.s:165
1  0x000000000045cba2 in runtime.asmcgocall
   at /home/khr/go1.14.7/src/runtime/asm_amd64.s:640
2  0x00000000004050af in runtime.cgocall
   at /home/khr/go1.14.7/src/runtime/cgocall.go:143
3  0x000000000047f511 in main._Cfunc_test_crash2
   at _cgo_gotypes.go:43
4  0x000000000047f550 in main.main
   at ./main.go:15
5  0x0000000000432b9a in runtime.main
   at /home/khr/go1.14.7/src/runtime/proc.go:203
6  0x000000000045d491 in runtime.goexit
   at /home/khr/go1.14.7/src/runtime/asm_amd64.s:1373

Not sure why gdb/lldb can't backtrace the Go side. We do generate Dwarf, but maybe it's not sufficient to encode things like stack switches? Or maybe it is just wrong?
@thanm
gdb behavior can vary a lot by version. I used:
$ gdb --version
GNU gdb (Debian 9.1-3) 9.1
$ lldb --version
lldb version 9.0.1
$ dlv version
Delve Debugger
Version: 1.5.0
Build: $Id: ca5318932770ca063fc9885b4764c30bfaf8a199 $

Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I'm fairly certain that the stack has not been destroyed.  It's just that gdb has gotten confused.
Which version of gdb are you using?

gdb version:
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Please use thread <no> to switch to the thread of A::release.

The problem seems to be because we are calling runtime.(*sigctxt).preparePanic when the signal is raised by C code, in this case A::release.  This adjusts the registers saved by the signal handler to act as though the code calls sigpanic.  gdb is able to unwind past sigpanic to A::release, but it is unable to unwind any further.
The unwind info for sigpanic is:
00007324<PHONE_NUMBER>000024 00000000 FDE cie=00000000 pc=0000000000446b80..0000000000447037
  DW_CFA_def_cfa_offset_sf: -504
  DW_CFA_advance_loc: 23 to<PHONE_NUMBER>446b97
  DW_CFA_def_cfa_offset_sf: -464
  DW_CFA_advance_loc2: 1174 to<PHONE_NUMBER>44702d
  DW_CFA_def_cfa_offset_sf: -504
  DW_CFA_advance_loc: 9 to<PHONE_NUMBER>447036
  DW_CFA_nop
  DW_CFA_nop
  DW_CFA_nop
  DW_CFA_nop
  DW_CFA_nop

Interestingly this doesn't record any location for the saved value for rbp, and there isn't any such location in the CIE either.  gdb's info frame command reports
Stack level 1, frame at 0x7fffffffe348:
 rip = 0x44702c in runtime.sigpanic
    (/home/iant/go/src/runtime/signal_unix.go:703); saved rip = 0x483ef6
 called by frame at 0x7fffffffe348, caller of frame at 0x7fffffffe318
 source language unknown.
 Arglist at 0x7fffffffe310, args:
 Locals at 0x7fffffffe310, Previous frame's sp is 0x7fffffffe348
 Saved registers:
  rip at 0x7fffffffe340

which also does not list rbp in the list of saved registers.
I'm not sure but I think that the effect of this is that when gdb unwinds past sigpanic, it does not update rbp to the value saved on the stack.  Thus when it looks at the stack for A::release, it is looking at the wrong frame location.
I spot checked the unwind info of a couple of other Go frames, and they also don't record any information about where rbp is saved.  Perhaps that is a problem.
I don't plan to look into this any further myself.


how do I get this 1200 in 1 file working for my Chinese snes diy cartrage

Obviously, the support page for nested games does not provide support for this file and when I try to save it with default settings it says mapper 227 is not supported is there any fix? If you want to experiment here is the link to download it if you want
https://www.mediafire.com/file/vxoa4ve59kyw9er/1200-in-1+(J)+[p1].nes/file

See issue 67 as the same answer applies:
https://github.com/Myself086/Project-Nested/issues/67


Maya Create Render Creator fails for Redshift

Describe the bug
Maya + Redshift

Set current renderer to Redshift in Maya 2020 or Maya 2022
Avalon > Create.. > Create Render

Results in this error:

Source of issue is that the _set_renderer_option method does not exist on the CreateRender object.
It was originally added in this commit. It was removed in this commit, see here
Questions
@antirotor - Any particular reason this got removed? How would you like me to fix it?
We could either change it to:
            cmds.setAttr("redshiftOptions.imageFormat", 1)  # EXR

Or add the _set_renderer_option back in for the different renderers.

Also, additionally I'd like to bring up a question. Are we sure we want this Creator to change up the render settings directly? What if the User had already prepped the scene for a bit before creating the Render instance?
[cuID:OP-2253]

This is actually in process of refactoring (#2282) . Goal is to have these renderer settings in Settings UI and to be able to configure there what should be set by this creator and what not. I suppose that by default it will only force image formats and such things.


Fix incorrect step for disabling profiler

The documentation said to go to the Extensions page, but it should say WebJobs.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Remove sqlbindings from RC gallery

This PR removes the SQL Bindings extension as it will be only published in VSCode Marketplace.

FYI - you've been forgetting to update the metadata count at the bottom. If you ever add/remove an extension you need to update that as well.


jaxlib version is not compatible with JAX on Mac M2 chip

Description
I have jax and jaxlib both installed on a conda environment.
I receive the following error and can't find a way to fix the version incompatibility.
RuntimeError: jaxlib is version 0.3.25, but this version of jax requires version >= 0.4.6.
What jax/jaxlib version are you using?
jaxlib 0.3.25, jax 0.4.7
Which accelerator(s) are you using?
GPU, Apple (0x106b), arm64
Additional system info
3.9.13
NVIDIA GPU info
No response

Hi! Not a maintainer, but the project keeps the versions synced between jax and jaxlib, as per this JEP on versioning.
The minimum jaxlib version is given by this line for any point in the git history:
https://github.com/google/jax/blob/c2d6fcc0e6ab34c217ef1969ada30129c6f787cd/jax/version.py#L19
There's a version guard in place on jaxlib, which throws an error in case the located jaxlib is too old, producing the error you see. To fix (or rather, to assert a compatible jaxlib is installed), you can install the package with the CPU extra on Mac:
# for zsh, wrap square brackets in quotes to avoid shell interpretation
python -m pip install --upgrade "jax[cpu]"

Does that help?

Yes, the fix is to install a matching jaxilb.

the command: python -m pip install --upgrade (I am having GPU on my machine) doesn't upgrade the version for me. I tried to upgrade the version through Anaconda Navigator that was also not possible (the options are grayed out).

You can either install an up to date jaxlib via pip (pip install --upgrade jax jaxlib), or alternatively using the community-supported conda-forge build (https://github.com/google/jax#conda-installation). I'm not sure what version if any is available through Anaconda otherwise: we do not ourselves distribute JAX via Anaconda.


fix: retain space around inline code block

if the text starts or ends with a backtick.
Closes #41

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Looks good. Thanks @satyarohith!


Sync RWS app locker with local app locker

Depends on https://github.com/pebble-dev/mobile-app/issues/45

I might take a swing at this. Which of the RWS repositories exposes the app locker?

@NoahAndrews did you go anywhere with this?


Account for :INITIALIZE change

From https://github.com/rakudo/rakudo/commit/00cb3315c5c90b9f74d737aad560b909372ae69c
Reported in https://github.com/rakudo/rakudo/issues/2398

Thanks!


remove preview note

Contributes to #15175

@mairaw emailed you the book cover without the preview text.

Thanks @nishanil. I've added to the PR.


Test with click 8

Changelog / Overview
Bump dependencies. Since click 8 is released, I have tested it and seems to work. Also, the logger interface is so stable on rich that we can use any version >6.0.0.

Motivation
Essentially, the AUR package broke and I fixed it by changing these. Also, I have locally tested things and it seems to work. Also, I have added .gitattributes files so that LF is used everywhere even on Windows(no worries git handles it smoothly).
Explanation for Changes
I bumped the version in pyproject.toml and updated the lock file.
Testing Status
Locally tested.
Checklist

[x] I have read the Contributing Guidelines
[x] I have written a descriptive PR title (see top of PR template for examples)
[x] I have written a changelog entry for the PR or deem it unnecessary
[ ] My new functions/classes either have a docstring or are private
[ ] My new functions/classes have tests added and (optional) examples in the docs
[ ] My new documentation builds, looks correctly formatted, and adds no additional build warnings

Reviewer Checklist

[ ] The PR title is descriptive enough
[ ] The PR is labeled correctly
[ ] The changelog entry is completed if necessary
[ ] Newly added functions/classes either have a docstring or are private
[ ] Newly added functions/classes have tests added and (optional) examples in the docs
[ ] Newly added documentation builds, looks correctly formatted, and adds no additional build warnings

I think the doctest failures seem weird. How, didn't it happen before, and how does it happen how? And, the doctest failure seem's legit as we set the default log level to INFO, why didn't it happen before, maybe it was a bug in rich.


Which players page

As a user, I can:

[x] visualise a network of stakeholders: concentric circles of e.g. beneficiary, beneficiary's direct network, community support, statutory obligation of support, populated with legends of:
local authority, Public Health, police, NHS Trust, community leader

[ ] see that the size of stakeholders corresponds to the number of contacts they have

[ ] click to pop out different contacts summary info: job title, organisation and legend categorising type of role. E.g. Director of Children's Services, London Borough of Barnet, blue = local authority

[ ] see how different stakeholders connect to each other

[x] understand different categories of stakeholder

[x] select a contact and link to Who? view page

@philippaMAC can we please get a list of the following based on Barnet:

names of concentric circles
list of organisations / people and their corresponding circle

@astroash ecosystem concentric circles: young people > peers, family, school > health services > justice and social services > employment, community and local politics > culture
LB Barnet leaving care REACH team
LB Barnet Children's Services
Public Health
Police & Community Safety
Community partners

@philippaMAC Hello philippa! Would it be possible to know all the organisations' names that are involved in LB Barnet? Thanks a lot!

@rebecacalvoquintero @maxgerber
Data for Staying Close (example cluster, text in brackets indicates category for legend)
First concentric circle: Pelham (voluntary sector children's home), Florence road (local authority children's home), Warwick road (voluntary sector children's home), The Horizon (voluntary sector youth service), Broughton road (voluntary sector children's home), Garrick road (private sector children's home), The Ride (local authority youth service)
Second concentric circle: St Christopher's Fellowship Staying Close team (voluntary sector), MAC-UK team (voluntary sector), 8 other partners (can we use imaginary/sample/filler data for these please?), Children's Services - London Borough of Ealing (local authority), Children's Services - London Borough of Hounslow (local authority),
Third concentric circle: Department of Education Innovation Fund, Spring Consortium, West London Alliance

@rebecacalvoquintero @maxgerber
Data for Barnet (example cluster, text in brackets indicates category for legend)
First concentric circle: Education; YOT, Police,
Second concentric circle: Art Against Knives (voluntary sector), Woodside centre (local authority youth service), MAC-UK team (voluntary sector), REACH team (local authority team)
Third concentric circle: Gang Calling (local authority initiative), Barnet Council Councillors, CCG, Health Education England, Ofsted,
Teams:

REACH > 1 x service lead, 1 x manager, 4 x social workers, 2 x family practitioners, 1 x family therapist, 1 x clinical psychologist, 2 x educational psychologist, 1 x business support officer, 1 x education access officer
MAC-UK > 1 x Project Lead, 1 x Deputy Lead, 1 x INTEGRATE practitioner, 1 x Youth Consultant
REACH steering group > Director of Children's Services, Education Lead, MAC-UK CEO, CAMHS Lead, Public Health, Research in Practice independent evaluators

@rebecacalvoquintero @maxgerber
sample of how the different agencies/teams could connect in a visual way:

Hi @philippaMAC hope you're well, we're just going through the data you sent us for Barnet and wanted to double check that we put everything in the right place.
So, for the first concentric circle (which is peers and family) we will have: Education; YOT, Police.
For the second concentric circle (which is school community neighbourhood) we will have:
Art Against Knives (voluntary sector), Woodside centre (local authority youth service), MAC-UK team (voluntary sector), REACH team (local authority team)
For the third concentric circle (which is health housing employability safety we will have:
Gang Calling (local authority initiative), Barnet Council Councillors, CCG, Health Education England, Ofsted

For the organigram view, we have two REACH teams, should this be reflected in the "solar system" view with two seperate nodes?
Teams:
REACH > 1 x service lead, 1 x manager, 4 x social workers, 2 x family practitioners, 1 x family therapist, 1 x clinical psychologist, 2 x educational psychologist, 1 x business support officer, 1 x education access officer
MAC-UK > 1 x Project Lead, 1 x Deputy Lead, 1 x INTEGRATE practitioner, 1 x Youth Consultant
REACH steering group > Director of Children's Services, Education Lead, MAC-UK CEO, CAMHS Lead, Public Health, Research in Practice independent evaluators

Hi @maxgerber hope all's well with you.
For the concentric circles ... apologies, they are all out by one. Please see these amendments:
Peers and family: could we have a few 'pretend' nodes named e.g. 'parent', 'friends'. ?
School, community, neighbourhood: Art Against Knives (voluntary sector), Woodside centre (local authority youth service), MAC-UK team (voluntary sector), REACH service (local authority team)
Health, housing, employability, safety: REACH steering group (local authority team), Gang Calling (local authority initiative),
4th concentric circle (politics and culture): Barnet Council Councillors, CCG, Health Education England, Ofsted
Regarding the organigram teams, yes, the two REACH teams are different nodes in the solar system view, I've added these to the second and third concentric circle respectively.
Thanks!

@philippaMAC we need 10 minutes more , so sorry ...i will send you the link shortly ❤

https://hangouts.google.com/call/CkhteqIbobsHVZTKWo1QAAEI
@philippaMAC

@maxgerber strap line for REACH service: multi-disciplinary team to support young people and their families in Barnet


perf: reduce call count and data quantity for high use query

Description

This is the second most used query in our monitoring logs. We think we can improve performance by only using this in the page where it's used, and requesting only the required fields. This page doesn't need the user data of the current getCalls query.
Motivation and Context

We're approaching a proposal call deadline and are seeing high load levels. This may be a significant culprit.
How Has This Been Tested

Fixes

Changes

Depends on

Tests included/Docs Updated?

[ ] I have added tests to cover my changes.
[ ] All relevant doc has been updated

Its OK, but it could be a better (?) choice to add a new parameter to the existing useCall function instead of introducing a new useCalllsMinimalData function with almost identical implementation.
Example for this: includeTemplate parameter in useActiveTemplates.

Yeah, I followed all the places where useCallsData is used, and the only place that looked like it needed extra fields was the calls table.

Yeah, I followed all the places where useCallsData is used, and the only place that looked like it needed extra fields was the calls table.

Looks like xpress stuff that merged in since I did those checks also required extended data


allow short hex format

Hi, it's me again :laughing:
I just found out today, that the picker won't support short hex like #fff
to change this, i added
if ( hex && hex.length == 4 ) {
    hex = hex + hex.substr( 1 );
}

in hexToRgb to change the #fff to #ffffff.
When i'm not wrong, other short colors don't exist, you can only short them if they have 6 times the same char.
Greetings

Good catch, thanks! Just pushed a fix.


Entries should be sorted alphabetically

The current way works I guess, although from the contribution checklist:

Be sure to place your entry ALPHABETICALLY in the current list.

Less merge conflicts because of multiple prs with entries added at the bottom would be great.

This could be enforced by implementing #73 , creating a script that checks if entries are sorted


consider using BTreeSet instead of Vec for --ext

But.... got stuck trying to implement that. Clap is confusing.
Asked a question in their discussion forum: https://github.com/clap-rs/clap/discussions/5437

From the discussion, it looks like custom collection types are not supported in Clap, so skipping this for now.


Upgrade to 3.4.5

Changes Unknown when pulling 892b463e440ad3315b2de711d52b2fff92b450e5 on 3_4_5 into ** on master**.


Improve reliability

Added a bunch of safety checks in general.
Changed the way the listen function works a little bit to avoid mixing promises and callbacks.
Try every record available if the first one doesn't work.
The above one means it's decoding the lnurl in the listen function now.

I actually haven't tested this at all yet. I just wanted to give a heads up that I'm jabbing at the code a bit.
The commits should be easier to follow than the diff.
I looked at wireless-sats, the flow doesn't change much. Instead of a callback, the function now returns the decoded lnurl. handleLnurl takes that decoded url. Some errors returned are now an enum, for the most logical error cases.

Added a whole bunch of tests


Investigate init containers that recieve traffic

Copying conversation from slack:

Hi, Is there a way to tell istio side car to use plain text communications until all the replicas for the stateful set moves to running state. If init containers have some peering logic , the istio is sending TLS traffic to other pods though the other pod doesn't even have istio init container started yet.

Does that work without istio? I hadn't heard if anyone receiving traffic during init containers

Yes. It works without istio. It also works in istio 1.7.4 as it does plain text communication for all stateful sets. Both the pods belong to same stateful set. I am using the mongo db replica set chart. The peering logic is in the init container. Here is the chart used by me. It's not working in 1.7.5 and 1.8.1 https://github.com/helm/charts/tree/master/stable/mongodb-replicaset. The init container name is bootstrap in this chart. (edited)

We should investigate how this works, document it if it doesn't, and fix anything that needs to be fixed. One thing I am curious is that the pods should be not ready, so curious how it works without istio. With istio, i expect it to passthrough?

not stale


Why is the effect of the model rotated by 180 degrees around the y-axis and z-axis zoom -1 different?

z-axis zoom -1

rotated by 180 degrees around the y-axis

Can you add more details to your question?  Is this about the orbit-style camera manipulator?

@prideout Don't we have an API to enable normals flipping when a negative scale is applied?

Ah right, I was confused by the issue title.  To conform to the glTF specification, Filament automatically flips the face winding when the determinant of the transform matrix is negative.  This is useful when creating symmetrical models because you need to specify only half of the geometry.
This is a fairly standard feature so I would be surprised if we're deviating from other popular renderers.
@cjsliuj if this is a problem for you that does not exist in other glTF viewers (e.g. this one) then maybe you could attach an example model as a zip file.

Some links for more background on this feature:
https://github.com/google/filament/issues/1520
https://github.com/google/filament/issues/3001
https://github.com/KhronosGroup/glTF-Sample-Models/issues/273
https://github.com/KhronosGroup/glTF-Asset-Generator/tree/master/Output/Positive/Node_NegativeScale

I found change like this will fix the problem（Is this change appropriate?）:
original

after changed

We intentionally use a cofactor matrix as described here:
https://github.com/graphitemaster/normals_revisited

Thanks


Change to BSD license

Although #9 adds the MIT license header, I think we'll be better off with a BSD license for BpyBuild (Specifically BSD 3-Clause)
BSD is permissive like MIT, but with the following requirements:

Redistributions of source code (and binaries, but that's less of an issue for us) must contain the copyright notice, conditions list, and disclaimer
Names of the copyright holder(s) and contributors cannot be used to promote derivitive software without permission

Beyond those 2 additional requirements, this is almost identical to the MIT license, and is also compatible with MIT and GPL

I've reviewed the dependencies and all of our dependencies (the ones actually installed alongside BpyBuild, not dev dependencies for development) are MIT, so this license is compatible with BSD 3-Clause


Cookies are not passed to the redirect calls

In case you get a redirect , the cookie recieved from the first result should be passed the following ones.
By now they are getting lost.
The usecase I encountered:

POST to a login api , the api response provides a cookie
following the redirect issues a second call (get or post based on config) but the recieved cookie is not passed to this second call.
the redirect call recieves a new cookie which is not valid anymore

A possible workaround is to read the cookies from the first call issued and passing it to the next ones manually.
I suspect we should copy the cookies recieved from the response to the next request here:
https://github.com/softwaremill/sttp/blob/7e76fb5d83cae09b52e72e18195c442f65a881c6/core/src/main/scala/sttp/client3/FollowRedirectsBackend.scala#L73

Automatically propagating cookies can be a security issue, hence it's not enable by default. You can change that behavior by changing the sensitiveHeaders parameters of FollowRedirectsBackend, and removing Cookie (and possibly SetCookie) from the set. So sth along the lines should work:
val backend = new FollowRedirectsBackend(myBackend, sensitiveHeaders = HeaderNames.SensitiveHeaders - HeaderNames.Cookie)

@adamw What OP described is a different problem, the Set-Cookie: headers from the response of the Nth redirect need to be saved and added to the Cookie: header of the request for N+1th redirect onwards, but the FollowRedirectsBackend does not have built-in logic to handle this scenario.


Issue with vim-airline and tagbar

Hello,
I'm facing a curious issue with my vim since I use vim-airline. Each time I start vim with a file and that my first action is to find a part of a word, I obtain a error message asking me to press ENTER and then the cursor goes on one occurence I'm looking for.
I've installed only the following in my .vim directory:
pathogen : commit b9fb0dfd811004010f5f6903edef42d6004ebea2
tagbar: commit c6b473f5593a1cb9e567bb1a9a897f196f1f720a
vim-airline: commit f45ecdac15d99ed2354873a8b4d40432fd0a85a3
And stripped my .vimrc to
set nocompatible
call pathogen#infect()
call pathogen#helptags()
syntax enable
filetype plugin on
set ffs=unix,dos,mac
set lz
set laststatus=2
let g:airline#extensions#branch#enabled     = 1

If you need more information, tell me.
Regards

i can't reproduce.  which version of vim are you using?

Hello
I’m using RHEL6 @work, I will have a look to the version (normally it must be 7.2).
At home, I’m using Mac OS Yosemite, with vim version 7.3.
Sincerely,
Marc Carmier

Le 28 juin 2015 à 20:46, Bailey Ling<EMAIL_ADDRESS>a écrit :
i can't reproduce. which version of vim are you using?
—
Reply to this email directly or view it on GitHub https://github.com/bling/vim-airline/issues/749#issuecomment-116312726.

Is this still reproducible? On what Vim versions does that happen? Please show a screenshot of the error message.

closing for inactivity


📃:  Timer Application

:red_circle: Title : Timer-Application
:red_circle: Aim :  For setting time to complete tasks with title
:red_circle: Tech Stack Used : HTML, JS, CSS
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Ragini Mishra
What is your participant role? (Mention the Open Source Program name. Eg. GSSOC, SSOC, JWOC, etc.): GSSOC'24

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@Rags-Mishra go ahead. but it should not be a pomodoro timer.

Okay
On Wed, 12 Jun 2024 at 11:40, Avdhesh @.***> wrote:

Assigned #299
https://github.com/Avdhesh-Varshney/WebMasterLog/issues/299 to
@Rags-Mishra https://github.com/Rags-Mishra.
—
Reply to this email directly, view it on GitHub
https://github.com/Avdhesh-Varshney/WebMasterLog/issues/299#event-13126378152,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATZJQK5OPZHLX3CTRVEPBR3ZG7Q6VAVCNFSM6AAAAABJEXPUQ2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGEZDMMZXHAYTKMQ
.
You are receiving this because you were assigned.Message ID:
@.***
com>


Please make qredshift systemd-aware

On Debian testing (bullseye), the redshift package by default launches redshift via systemd. Specifically:
dilinger@e7470:~$ systemctl status --user redshift
● redshift.service - Redshift display colour temperature adjustment
Loaded: loaded (/usr/lib/systemd/user/redshift.service; enabled; vendor pr>
Active: active (running) since Wed 2021-02-17 22:08:37 EST; 2s ago
Docs: http://jonls.dk/redshift/
Main PID: 50863 (redshift)
Tasks: 5 (limit: 18799)
Memory: 3.0M
CPU: 56ms
CGroup<EMAIL_ADDRESS>└─50863 /usr/bin/redshift
Feb 17 22:08:37 e7470 systemd[1753]: Stopped Redshift display colour temperatur>
Feb 17 22:08:37 e7470 systemd[1753]: Started Redshift display colour temperatur>
Feb 17 22:08:37 e7470 redshift[50863]: Trying location provider geoclue2'... Feb 17 22:08:37 e7470 redshift[50863]: Using provider geoclue2'.
qredshift assumes that if redshift is running in the background, killing it will be enough. However, systemd immediately restarts it. So basically, systemd's redshift launcher and qredshift end up fighting (with somewhat hilarious results as my screen changes lots of colors).
The solution (for me) is to manually run systemctl stop --user redshift, but it'd be great if either qredshift learned how to do this, or if there was some kind of warning/notification to let users know that they'll need to do this.

Can you check if its fixed with the last version(1.5.3)?
Thanks for the report.

This appears to be working. I reinstalled the redshift package so that it had the default systemd settings, reinstalled qredshift, and it properly shut down and masked the redshift service. Thanks!


startAt and stopAt parameters not honored

Bug Description
When values for startAt and stopAt are passed to the SWT app, those values should define the time range of annotated timepoints.  As of now, at least in v4.1, these values seem to be ignored.
If you run the app with values for these parameters, the app will nevertheless process the entire video and produce annotations across the entire duration.
Reproduction steps
Specify startAt and/or stopAt parameters via a query string to SWT running as a web service, as with this query string: startAt=1237500&stopAt=1767000.  SWT still begins annotating at 0ms and continues to 1784500ms.
The asset used during testing: cpb-aacip-37-95w6mnpw
Expected behavior
No response
Screenshots
No response
Additional context
No response

Did a post-mortem on this because I knew that this error did not happen when I added the parameters. Turns out that _export_parameters(), an essential method for this, was removed after version v4.0. This somehow went unnoticed.


Document read_csv function

The current docs does not:

document the read_csv function at all, it only uses it in examples
does not explain the difference between read_csv and read_csv_auto

The old docs used to do the latter (which is a sufficient explanation as far as I'm concerned):
docs/archive/0.7.1/data/csv.md
93:`read_csv_auto()` is an alias for `read_csv(AUTO_DETECT=TRUE)`.

https://duckdb.org/docs/archive/0.7.1/data/csv

The current documentation no longer defines the options for CSV parsing. The table in 0.7.1 (https://duckdb.org/docs/archive/0.7.1/data/csv#parameters) has many deprecated field but we should have something like this in the current documentation.
cc @pdet


Failed to export an ONNX attribute 'onnx::Sub', since it's not constant, please try to make things (e.g., kernel size) static if possible

🐛 Bug
Describe the bug
It is not possible to export the trained model to onnx format. My model is a fasterRCNN, trained using PyTroch Lightning. After
light_model.to_onnx("model_lightnining_export.onnx",
                batch[0],
                export_params=True,)
                 input_names = ['input'],
                 output_names = ['output'],
                 dynamic_axes={'input' : {0 : 'batch_size'},'output' : {0 : 'batch_size'}})

The method crushes
RuntimeError: Failed to export an ONNX attribute 'onnx::Sub', since it's not constant, please try to make things (e.g., kernel size) static if possible

To Reproduce
1.Train the model
trainer = Trainer(max_epochs=10,
                      checkpoint_callback=False,
                      logger=False,
                      gpus=0,
                      resume_from_checkpoint = '/home/piotr/Downloads/epoch=4(1).ckpt'
                      )
trainer.fit(light_model, dm)

Generate an example batch:

i = 0
samples = [valid_ds[i] for i in range(i, i+2)]
batch, samples = faster_rcnn.build_infer_batch(samples)

Try to save the model using ONNX format

light_model.to_onnx("model_lightnining_export.onnx",
                batch[0],
                export_params=True,)
                 input_names = ['input'],
                 output_names = ['output'],
                 dynamic_axes={'input' : {0 : 'batch_size'},'output' : {0 : 'batch_size'}})

Expected behavior
The model saved successfully as ONNX
Desktop (please complete the following information):

OS: ubuntu 18.04

Okk, nevermind, I have found the solution. The error was due to the resnet, not due to the icevision.  I had to change                 opset_version, to 11
light_model.to_onnx("model_lightnining_export.onnx",
                batch[0],
                export_params=True,
                opset_version=11,
                input_names = ['input'],
                output_names = ['output'],
                dynamic_axes={'input' : {0 : 'batch_size'},'output' : {0 : 'batch_size'}})

Thank you @tugot17 for sharing the solution that you found. This will help other who might face a similar issue.


[Feature]optional slideTransform and slideIndicator

if slideTransform is null, use slideTransform: DefaultTransform(), is better.
and slideIndicator is not needed.
I put indicatorRadius: 0, instead.
            slideIndicator: CircularSlideIndicator(
              padding: EdgeInsets.only(bottom: 32),
              indicatorRadius: 0,
            ),

@UdaraWanasinghe Did you give up?

hey

That looks nice. Thank you for the suggestion. ;)


Contradicting kubectl apply documentation

Contradicting kubectl apply documentation
Problem:
The kubectl apply documentation here:
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply
Says that the -k flag should be used for a directory.
However the documentation here for the kubectl overview:
https://kubernetes.io/docs/concepts/configuration/overview/#using-kubectl
Suggests using the -f flag for a directory. Why is there a discrepancy?
Proposed Solution:
If -f is best practice for a limited use case this should be made clear in the documentation. Separately it should be clear that -f can be used for a directory, not just for a file.
Pages to Update:
One of the following pages should be updated or clarified:
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply
or
https://kubernetes.io/docs/concepts/configuration/overview/#using-kubectl

@SebStrug I recommend filing this issue against kubectl to clarify that -f can take a file, a manifest URL, or a local directory containing manifests. That change will cascade into the page at https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply
You can file that report using https://github.com/kubernetes/kubectl/issues/new?labels=kind%2Fbug&template=bug-report.md and then close this issue, referencing the URL of the replacement issue you logged.

Thank you @sftim
I have filed the issue here: https://github.com/kubernetes/kubectl/issues/896 , and will close issue.


240812 new 0186 web UI fix hm ipw dri16 dri32 channel

Description

Repairing of Channelbehaviour HmIPW-DRI16 / DRI32 by Loading the ChannelConfigPage the first time
Related Issue

#2736
Types of changes

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

Alternate Designs

Possible Drawbacks

Verification Process

Release Notes

Contributing checklist

[X] My code follows the code style of this project.
[X] I have read the CONTRIBUTING and LICENSE document.
[X] I fully agree to distribute my changes under Apache 2.0 license.

This PR does not seem to be created right. Have a look at the "Files changed" tab and the commits it includes. This seems to be way too much changes. So please update your fork, create a fresh new branch, cherry pick the commits that are relevant and resubmit please.

Sorry, I will never understand this GitTool.
The new Pull request is submitted. I hope, it is better...


HTML Comments not aligned properly after uncommenting

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:22:50.650Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

vsc-material-theme
Equ
1.0.2

beautify
Hoo
1.1.1

code-settings-sync
Sha
2.8.2

quokka-vscode
Wal
1.0.46

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

gitignore
cod
0.5.0

vscode-eslint
dba
1.2.11

githistory
don
0.2.3

vscode-html-css
ecm
0.1.7

vscode-npm-script
eg2
0.2.0

auto-close-tag
for
0.4.3

auto-rename-tag
for
0.0.14

code-runner
for
0.6.32

docthis
joe
0.4.7

vue
liu
0.1.5

ecdc
mit
0.10.3

vscode-autoprefixer
mrm
2.1.1

vscode-csscomb
mrm
4.0.1

vscode-scss
mrm
0.6.2

debugger-for-chrome
msj
3.1.7

vetur
oct
0.9.3

rewrap
stk
1.4.2

code-spell-checker
str
1.3.4

vscode-todo-highlight
way
0.5.8

better-align
wwm
1.1.6

Steps to Reproduce:

Add HTML

Line 1

Line 2

Comment a line

Line 1

Toggle the comment. Notice that toggled line is not properly aligned (there is an unwanted space before the opening
 tag and after the closing
 tag).

Line 1

Line 2

To further demonstrate the issue, repeatedly toggle the line comment on/off. Below is the result of toggling the same line on/off ten times.

Line 1

Multi-line comments are also affected. Below is the result of toggling the entire block of HTML on/off ten times:
            ```

I believe the expected behavior is for a toggled comment to restore the line's original alignment much like other toggled comments do. It appears that the issue is caused by space characters that are added when commenting () which are not removed when uncommenting (only  are removed).

Reproduces without extensions: Yes
Thanks!

Also happens with JavaScript and Lua. Didn't check with other languages.

Duplicate of #30804.


Document which property should be used for spring-cloud-gcp credentials

Follow up for #2364
Currently we document spring.cloud.gcp.credentials as the property, but we probably should mention that spring.cloud.gcp.sql.credentials would work as well. Or maybe we should just remove spring.cloud.gcp.sql.credentials.

We generally allow a product-specific property like spring.cloud.gcp.sql.credentials to overwrite the general spring.cloud.gcp.credentials.

Probably we can give an explanation in the README that both could works, and give an option of using each product specific application properties.


Multiple tooltips on single page on mobile are not working

When more than 1 tooltip is placed on single page and viewed ON MOBILE (you cannot reproduce this bug in chrome mobile emulator - you need real device) only first you interact with is working properly. Then when other tooltips are clicked, they are not opened.
Is some special key / id required for it to work properly?

Hey @Filipeue, I'll try and take a look at this, have you tested with both ios and android? which browsers?

I have tested it on OnePlus 7T Pro, Adnroid 10, Chrome 81.0.4044.138. Unfortunately I issue seem not to be present when using tool like Browserstack (https://www.browserstack.com/), no matter the browser or device I choose. So I tested it on my other device Android 5.0.1, same chrome version and the issue persited. Then iphone 10s Safari: issue NOT present.
So it seems to be android + chrome issue and to simulate you need real device preferably with newest Chrome.

Okay thanks @Filipeue, and by "interact" I assume you mean tapping the target?

yeah I meant tapping the target, but I have tested it on few more android devices with newest chrome and I cannot simulate the issue, so I am starting to think It has something to do with my chrome profile or something... really weird...
on 2 of my own devices I see the issue and everywhere else it is working just fine... after this finding the issue is not as important as it seemed, so if you choose to close it I can understand


Update dark.css

Dark theme input bar fix

Hi, I was really looking forward to try it but unfortunatelly it seems like I cannot build it correctly.
gulp pack:win32 is done without errors, but neither the build exe nor the installer version doesn't work - Messenger starts in processes list but the window doesn't show up.
But the same happens when I try to build master so it is something wrong with my packages.

If you would be able to build Your commit and run it, could You please upload the installer or the files somewhere? I'd really like to try it.
:smiley:

This is… not an update.

Okey :smile:
Today I was able to build it successfully. Looks quite decent for me. As a workaround works completely fine.

This is how it looks:

Thanks a lot :wink: I hope the author will fix it soon. It's not a big deal and there was already a several issues raised about it.

@Marox44 I am the author. I do not approve of this "update".

Closing


making rubocop comments and links to urls markdown compatible

I'm using rubocop config on hound and a comment from rubocop like this:
lib/customer.rb:16:81: C: Metrics/LineLength: Line is too long. [82/80] (https://github.com/bbatsov/ruby-style-guide#80-character-limits)
    raise "Please select a dish from the menu." if !restaurant.menu_include?(dish)
                                                                                ^^

interprets the link as having the title "82/20" and so in markdown it looks like this:
[82/80] (https://github.com/bbatsov/ruby-style-guide#80-character-limits)
I wonder if we could change the format slightly to make the output markdown friendly ...

What format do you suggest?

@alexdowad well how about:
lib/customer.rb:16:81: C: Metrics/LineLength: [Line is too long. 82/80] (https://github.com/bbatsov/ruby-style-guide#80-character-limits)
    raise "Please select a dish from the menu." if !restaurant.menu_include?(dish)

That would produce the following:
[Line is too long. 82/80] (https://github.com/bbatsov/ruby-style-guide#80-character-limits)
for no immediate loss of readability in the text version I think.  However equally one could just do:
lib/customer.rb:16:81: C: Metrics/LineLength: Line is too long. {82/80} (https://github.com/bbatsov/ruby-style-guide#80-character-limits)
    raise "Please select a dish from the menu." if !restaurant.menu_include?(dish)

or anything to just avoid the [...](...) format that does hyperlinks in markdown.  Personally I'd go for a consistent use of [Line is too long. 82/80] (https://github.com/bbatsov/ruby-style-guide#80-character-limits) throughout all cop responses in order to make most efficient use of space in automated rubocop posts on pull requests (e.g. via hound), but of course we also want to make sure that text interface users are happy ...
what would you prefer?

Just thinking about this some more:
I'm sure GH Markdown has some way to emit a literal [...] (...) (not a link). Do you know what it is?
An ideal situation would be if Hound can fix up their automated GitHub post code to preprocess the output of RC, and convert [...] (...) to a literal.
There are a lot of CLI tools whose output would not look good if you simply cut-and-pasted it into GH as Markdown. Because... their output is not Markdown. When pasting excerpts from my shell into GH, I always surround them with triple backticks, for this reason.
Likewise, the output of RuboCop is not Markdown. Any other program or tool which takes that output, and tries to use it as Markdown without doing any preprocessing or conversion, is faulty.
The problem should be fixed at its source, rather than patching it here. Therefore, I recommend that this issue should be closed. @bbatsov @jonas054

An alternative would be to add a new formatter which outputs Markdown, rather than plain text (which is what RC's default "simple text" formatter gives you).
@tansaku, are you interested in writing a new formatter? I can guide you through the process. I believe @bbatsov would be very happy to merge it into RC. Maybe the guys at Hound may also be interested?

Yeah, probably a new formatter would be the best option.

@alexdowad I would be interested in writing a new formatter, although I probably won't be able to get into it till the new year.
I'd also love to work up a formatter that gives a report in terms of numbers of offences by category, so it showed like:

9 Line Length offences click for details
3 indentation offences click for details

but that's another story :-)

@alexdowad I would be interested in writing a new formatter, although I probably won't be able to get into it till the new year.

It's easier than you think. But whenever you have time, that is fine.

thanks @alexdowad and @bbatsov I've been on holiday for two weeks - will get into this next week I hope


Adding travis integration

Fixes https://github.com/jacogr/atom-lcov-info/issues/18

Not 100% sure about 2 things -
(a) The language (i.e. Objective-C)
(b) The value since we don't (yes, it is inexcusable) testing/tests
The build at this point won't really do anything.

a) Objective C is just the travis way to run OSX builds (i.e. if builds on OSX and not (easily) on linux) then that is the way to make it happen in travis)
b) you really should have unit tests for this project (in fact that is how I was going to start contributing, until I noticed that they where broken)
I'm a big user of TDD and having travisCI really makes a massive difference (in fact that is the first think I've done at https://github.com/o2platform/atom-coffee-repl)


Unexpected token '<'  on the last version

Hello,
Are you aware of this ?
Uncaught SyntaxError: Unexpected token '<' (at lazysizes.min.js:7:1)
Because I have a Drupal 9 website which doesn't work with lazyload module and another one that work..and I don't find why.
Thanks for tips

ok I found the error. Come from the download link. So I re download from CDN instead of github and get the right JS file.
wget https://cdnjs.cloudflare.com/ajax/libs/lazysizes/5.2.2/lazysizes.min.js


removed need to flatten position_ids

I am brand new to Jax and einops, so this may be incorrect. However, I think I fixed the need to flatten position_ids, so that we can support batch sizes other than 1. This broke, apply_rotary_pos_emb, so I added the new dimension (b). Let me know if this is way off.

Gave it a spin, output and output dimensions are the same as before, lgtm


Use new installer to run cluster install job

Separates artifact generation into its own package
Adds necessary environment vars to job to create cluster

Awesome!
/lgtm

/lgtm


Atom 1.0 compatibility

Developed/tested on Atom 1.0.7 (OS X).
Fixes #14.
Fixes #15.
Fixes #16.
Fixes #17.
After this PR is merged we should be able to install the package into the latest version of Atom again :-)

Also, I don't see any warnings for #10 or #11, but technically @supergithubo fixed them before I made this PR :-)

when is this PR going to get pull?


Examples disabled in documentation

Since adding the sortable component (which brings in Shopify's Draggable library), Proton is no longer compatible out-of-the-box with Vuepress.
For the sake of having documentation, working examples of the component will be disabled until I can find a work-around.

so sad to hear that :(

will figure out an alternative! maybe vuepress isn't the right choice for us since we do need interactive demos of components

Would really love the ability to see examples, before pulling it into my project.

i developped a vuepress-plugin-docgen thst you can easy integrate to vuepress docs

I've made some progress on the new docs - getting rid of vuepress and rolling my own so we can have nicer examples :v:

Working on the design as I move forward with things.

Can push it on a branch or something i would like to help. I am not really satisfy about vuepress even with my plugin.
I would like really happy to help you

Gridsome/Forestry is also a good solution for documentation.


Multiple LABELs

Just noticed a slight inconsistency between whether you should use multiple LABEL instructions within a dockerfile
File: engine/reference/builder.md

An image can have more than one label. To specify multiple labels, Docker recommends combining labels into a single LABEL instruction where possible.

File: engine/userguide/eng-image/dockerfile_best-practices.md

An image can have more than one label. Prior to Docker 1.10, it was recommended to combine all labels into a single LABEL instruction, to prevent extra layers from being created. This is no longer necessary, but combining labels is still supported.

CC @mistyhacks

Thanks for pointing this out. The builder.md has gone out of date. It is not actually a file that is managed within this repo, but is in https://github.com/docker/cli/tree/master/docs/reference. It would be great if you would like to raise a PR there to make the language consistent with the language in https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#label.

OK, thank you. I have just taken at look in builder.md and seen that about a month ago you made a commit fixing this! (e49e1ea73) so I shall leave it as it is for now :)

Nice, I forgot about that! The commits in docker/cli eventually make it into the docker/docker-ce repo but this obviously hasn't happened yet for this particular fix. Once it is in docker/docker-ce for a release, it will automatically be updated in the docs.

Hi, I am curious what was done in 1.10 that can avoid extra layers from being created. I can't find any description on that.
When I run docker build, I still see every LABEL clause generates a layer, the ID of which is visible in the outputs of docker images -a.

Never mind. I found a very detailed article eventually. I'll put a link to it here in case someone else like me landed here from Google: https://windsock.io/explaining-docker-image-ids/