Add "all" button to date range options for Inquiry report

placed somewhere where you will proactively have to select to minimize unnecessary crashing.

I simulated this functionality by setting the 'from' date to 1800 and not entering any other criteria. The server a few times, but I was able to get it working intermittently by increasing the memory available for the server.  On the times the server was able to handle the request, the browser itself crashed when trying to render all of the inquiries in the grid.
Based on this behavior I recommend that we forgo this functionality and potentially look into creating an upper limit for the number of records returned.  I don't think this scenario is common enough that we absolutely have to limit the number of results, and the production server itself should be able to handle the requests, but if we notice crashes as people are using the dashboard we might need to implement a limit.
@bchiaruttini are you OK with leaving the 'All' button off of the dashboard?

@n-devr In thinking more about this, there is really only one test case in which the ALL functionality is needed.  Is it possible in the inquiry report, that when a specific child is selected, then the ALL button appears along side the FY buttons?  this would allow us the info I am looking for, without ever returning more than 100 or so inquiry records.

The "All" button is now implemented and deployed to develop - ready for review whenever you have a moment.

@n-devr, tested and all looks good.  I did however find one other area where this functionality of the ALL button would be very helpful.  In the placement report, if a source is selected (whether placement, disruption, etc.), the ALL option should appear. I am sorry I did not identify this earlier so I can open a new story if preferable.  thanks.

No worries @bchiaruttini - we can track it as part of this story.  I'll just add a task for it here:

[ ] Add an ALL button in placements reports, visible when a source is selected

Actually @bchiaruttini I do have a question as I'm looking into a fix for this.  You mentioned a "source" being selected, but you listed "placement types" as examples - which dropdown selection should the ALL button respond to?

@n-devr In placement report, the field that it should cue off of is "source" and/or "additional source" to display the ALL option.  And perhaps this is irrelevant, but I was just attempting to highlight that the behavior should be the same whether the sub-type of placement, match, disruption or legalization is selected.

Got it, thanks for clarifying.  I read those as different options that might be in the Source field so I just wanted to make sure I was listening for changes on the right dropdown.  If I understand correctly, the ALL button should appear if any options are selected in either the "source" or "additional source" dropdowns.

@n-devr  yes correct, thanks!

@bchiaruttini the ALL button is now working on the placement report search form and is ready for testing on develop.

@n-devr  tested and looks good to push to production in next batch. thanks.


In effect disabling bidi for imagined speed improvements is the wrong thing to do.

What did you expect to happen?
I expected doom to behave properly with respect to bidi text.
What actually happened?
Auto paragraph directionality is messed up. It is limited to left-to-right.
Describe your attempts to resolve the issue
The following should be removed from core.el.
Default vanilla bidi emacs settings are the right settings. Don't mess with them.
Remove all bidi stuff from core.el.
In specific, all of:
;; Disable bidirectional text scanning for a modest performance boost. I've set
;; this to `nil' in the past, but the `bidi-display-reordering's docs say that
;; is an undefined state and suggest this to be just as good:
(setq-default bidi-display-reordering 'left-to-right
              bidi-paragraph-direction 'left-to-right)

;; Disabling the BPA makes redisplay faster, but might produce incorrect display
;; reordering of bidirectional text with embedded parentheses and other bracket
;; characters whose 'paired-bracket' Unicode property is non-nil.
(setq bidi-inhibit-bpa t)  ; Emacs 27 only

The imagined  "Optimizations" optimization for latin users at the expense of bidi languages is
the wrong trade off. It points to mono-cultures-of-the-mind.
See https://www.youtube.com/watch?v=kqIZb80OIKE
Steps to reproduce
Write some bidi text in a buffer.
System Information
All systems

I'm sorry that it adds an extra step for RTL language users. I may reconsider this later, but for the moment I don't intend to change this default. If Emacs addressed its performance deficits, then I wouldn't have to make such exclusionary decisions, but it makes enough of a demonstrable difference that I must defend it -- as Emacs' performance issues is among my highest priorities for Doom.
Fortunately, however, it's a simple thing to reverse:
;; add to $DOOMDIR/config.el
(setq-default bidi-display-reordering t
              bidi-paragraph-direction nil
              bidi-inhibit-bpa nil)

And there is also work on a bidi module that will reactivate bidi and then some.
I'll close this for now, but will post here again if/when I revisit the topic.

@mohsenBanan I'd appreciate any feedback you can offer on the bidi module, I think it's in a good place, but I rely on other people to find issues with farsi (or other arabic derived scripts)

@iyefrat  I don't see a doom module called bidi. Please expand about what you mean.

@iyefrat -- Sorry about my previous question.  I did not notice  " And there is also work on a bidi module that will reactivate bidi and then some. " at first.
Let me look into that. I'll follow up later.

@iyefrat  (CC: @hlissner ): I looked at the bidi-module. It is a good thing. It is needed as it fills a need.
I had built something similar for myself and a general solution is called for.
But, I don't think that framing it as just a doom-module is the right thing to do. To maximize social benefit, it is better to first create a melpa bidi-mode++ package and then bring that over and config it as a doom-module.
Also, the scope of some of what you are doing is broader than bidi. It is multilingualization in general and it overlaps
things like https://github.com/laishulu/emacs-smart-input-source ...
My suggestion is that we continue such discussions on https://lists.gnu.org/mailman/listinfo/emacs-bidi and bring the likes of Eli and others into the picture ...
Also, I have a menu that goes with my equivalent of your bidi minor mode that could be useful for some ...
What are your thoughts about all of this?

@mohsenBanan I think that you are generally right, but unfortunately I don't have much free time these days (hence the delayed response), so I can't really say when I'll be able to continue on this subject properly. A few points in the mean time:

The bidi module is small as is, and a lot of the font stuff is to get doom's font system to play nice with bidi text. Emacs by default seems to use a perfectly fine (non-monospace) font for Hebrew at least, so I need to check what parts are relevant for vanilla emacs before bringing it up on the mailing list.

It's true that some of the things in the module are broader than bidi and could be better organized. A while back I looked into sis.el and I think I was dissatisfied with it, but I can't remember why. I'll give it a proper look when I have more time.


Dataverse support for Dynamics 365 F&O On Prem

It is not documented anywhere on the compatibility level/support of Dataverse with Dynamics 365 F&O On-Prem. We can avoid a lot of confusion if it can be called out on any of the Microsoft docs.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 39b247a8-1e40-07d0-f44b-46f3f362a02d
Version Independent ID: 09725d7e-90ea-f6a9-3edb-28ff4bcc7510
Content: Microsoft Power Platform integration with finance and operations apps - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/power-platform/overview.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @Sunil-Garg
Microsoft Alias: sunilg

Bug 834380 has been logged to address this issue.

Thanks for your feedback. We have passed this feedback onto the product team for consideration.


Cyk1337 patch 1

PR types

PR changes

Description

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: KB-Ding:x: cyk1337You have signed the CLA already but the status is still pending? Let us recheck it.


Migrate label-studio host to new machine

Hi, I have a self-hosted label-studio instance on a machine which I'm now realizing is barely powerful enough. Now, I'd like to move my instance to a new remote machine, is there any way to do this without losing all my projects and labeled images?
I don't know if this may change things but I'm using local cloud storage.

@AndreaBrg yes, it's possible. What DB do you use?
You need to copy LS Database folder (you can find the path at the LS startup) on the new host. If you use postgres, you have to copy DB data too.

@makseq I copied over entire /label-studio/ folder to the new installation while using the same external PG database. But still projects doesn't show up in the new instance.

LS write the DB path at startup

Check whether it's the same where you copied your files?


Fix/handle model already loaded

Describe Your Changes

Handle when model is already loaded!

Fixes Issues

Closes #1476

Closes #1475.


Please update this article

Add a note about CAS Role only servers not responding properly, because they Proxy to MBX role.
Please provide a link to validate CAS Role only servers using: Get-Services MSEX*
Link:  https://social.technet.microsoft.com/Forums/exchange/en-US/c1e40b84-6d85-4f32-b202-d880b89bd7a3/strange-behaviour-testservicehealth-and-exchange-server-2013?forum=exchangesvrgeneral

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3ed853f0-84a5-d959-9acc-465888cf19cc
Version Independent ID: 57c7ffb5-cd83-4dfc-60eb-797210fd6ac3
Content: Test-ServiceHealth (exchange)
Content Source: exchange/exchange-ps/exchange/server-health-and-performance/Test-ServiceHealth.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

@chrisda Please merge this PR #4473 . Thanks

@dariomws306  Thank you very much for the contribution and updating the documentation with PR. @DynamitePLF Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


ninja_workdir: Add top-level binding to set working directory

Add a binding that the build manifest generator can use to tell ninja the working directory to use for the build.  This allows a command like
$ ninja -f /path/to/some/build.ninja

to work, regardless of the caller's working directory, if build.ninja has the binding.

@jhasse while working on #1251 I realized that the proposed ninja_workdir setting is useful on its own.  This PR adds it.
The Linux / test job is failing in CI, but I don't see what this PR's changes have to do with it.

Search the log for error:.

Thanks for the PR btw! I'm still not 100% sure if this is the best approach.

@jhasse thanks.  I updated the PR to fix the clang-tidy diagnostic.  CI is now clean.

The use-case in the initial comment isn't strong enough on its own IMHO.

The use-case in the initial comment isn't strong enough on its own IMHO.

Fair enough.  I'll continue discussion over in #1251.

Closing for now.  As discussed above, this may not be worthwhile on its own.


feat: enable/disable use of history in chat context

Issue #, if available: #306
Description of changes:
Allows customers to disable chat history context usage without affecting the recording of chat history for logging purposes. This setting is implemented on a per workspace level.
The updated UI elements on the create workspace workflow further explain the setting to the users and it is enabled by default to retain existing functionality.
I have tested the changes.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

After review the best path forward would be to make it easier to create a new session instead of allowing no-history in conversation.
Closing in favour of https://github.com/aws-samples/aws-genai-llm-chatbot/issues/283


Needs Arthur Ding

Should have a big picture of Arthur ding to tie the site together.

Arthur is the motif of the site. I wonder what he would think about this...


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in cb674ae.


Hosting QMOF Data on MPContribs

This is to kick off a discussion on how to best handle the QMOF data and how to store the QMOF data all in one place. Currently, data is being pulled from your Dropbox, but I think that a better solution would be to have all QMOF-relevant data hosted on MPContribs, and then we can use the MPContribs Python client to fetch the QMOF data in mofdscribe.
It's a bit clunky, but the following code will automatically fetch all the structures and tabulated data for every MOF in the QMOF Database, and it takes about 10 seconds to run.
from mpcontribs.client import Client
from pymatgen.core import Structure

# Instantiate the MPContribs client
apikey = "MyAPIKey" # this is a user's MPContribs API key
client = Client(apikey=apikey, host="contribs-api.materialsproject.org")

# Get the full set of contributions for the QMOF Database project
# Note: The structures returned here are unique identifiers and need to be fetched separately
qmof_entries = client.contributions.get_entries(
    project="qmof", _fields=["identifier", "data", "structures"]
).result()["data"]

# Parse out the tabulated data for each MOF. These are things like bandgap, PLD, etc.
data = [qmof_entry['data'] for qmof_entry in qmof_entries]

# Parse out the unique structure IDs
structure_ids = [entry["structures"][0]["id"] for entry in qmof_entries]

# Get the CIF strings for each structure ID
structure_data = client.structures.get_entries(
    id__in=structure_ids, _fields=["name", "cif"]
).result()["data"]

# Convert CIF strings to structures
structures = [Structure.from_str(entry["cif"], fmt="cif") for entry in structure_data]

This would replace a lot of the code in the __init__ for QMOFDataset() but would naturally update with the QMOF Database. On the user's side, the only that would need to change are: 1) They would need to install the mpcontribs-client package (can be an optional dependency); 2) They would need to provide their MPContribs API key when they instantiate the QMOFDataset().
What are your thoughts on something like this? If you think this is a good idea, I can work on a PR. The largest piece of work to get done would be to get all the missing data/labels on MPContribs (e.g. the adsorption data) as well as any other new info you've stored in the QMOF Database (e.g. the graph hashes and such), which I can coordinate with an appropriate JSON file.

I guess the only remaining thing is to figure out how to keep it updated (and then, in the longer term, what is the best way for me to help to also display some of the data)

Sounds good. I have a Jupyter notebook that takes in your data on Zenodo and my data on Figshare, organizes it all, and uploads to MPContribs. [I will finalize the MPContribs upload today so it's all up before the pre-print is online]. I can share that with you and then it should be fairly straightforward for either of us to update with any new data. In terms of displaying data, that's a bit up to you and what you'd like/not like to be involved with. It would be nice to have data visible on the Materials Project. If you were interested in getting involved with that, we can add you to the MP web repo and work together to display some of the data, e.g. isotherms. However, that's something I personally wouldn't be able to get involved with for a few months, most likely.

. If you were interested in getting involved with that, we can add you to the MP web repo and work together to display some of the data, e.g. isotherms. However, that's something I personally wouldn't be able to get involved with for a few months, most likely.

yea, I'd like to get involved. I also do not have a ton of time but could invest 1h/week or so atm

closing this as (at least the first iteration) is solved, thanks again! Will soon come back with an update as I got through all the QMOFs now.


"Choose new match" then "search for match" discards old match, but doesn't add new one

(3,3 rc 1 / Windows 10 1809 / Chrome 79.0.3945.117)  After running reconciliation, if I "choose new match" then "search for match", put in a specific Q-number to search for, then select it, the old match is discarded but the new match isn't added, and the row goes into the "reconciliation = none" facet

Tested in 3.3 and works in Chrome and Firefox.
Tested in 3.4 (trunk) and works in Chrome and Firefox.
Closing as not reproducible.


Text pair metadata

Codecov Report
Attention: Patch coverage is 84.61538% with 2 lines in your changes missing coverage. Please review.

Project coverage is 95.73%. Comparing base (a307df8) to head (e89f1ec).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

src/pie_modules/document/processing/text_pair.py
84.61%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #121      +/-   ##
==========================================
- Coverage   95.76%   95.73%   -0.03%
==========================================
  Files          61       61
  Lines        5048     5061      +13
==========================================
+ Hits         4834     4845      +11
- Misses        214      216       +2

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


[DOC]: Add name for action menu on App Analytics page

What do you want to do?

[ X] Request a change to existing documentation

Tell us about your request.
OpenSearch 2.1.x
Application Analytics page
https://opensearch.org/docs/2.1/observability-plugin/app-analytics/
"Get started" says "To get started, choose Observability in OpenSearch Dashboards". It was not obvious to this naive new user that Observability was under the hamburger menu in the top left of the page, under OpenSearch Plugins. This could be made more explicit. I don't know what our usual term for the hamburger menu is, but something like:
"To get started, choose Observability in the top left (hamburger) menu under Plugins."
Is there anything else you'd like to add?
Perhaps review other pages to see if there is a similar issue. This is especially important because (as far as I can tell), there is no overview of Dashboards usage.
The start page https://playground.opensearch.org/app/opensearch_dashboards_overview#/ makes it seem as though the only options are Dashboard and Discover, which leads the user to believe that everything will be found as options under those....
Am I the only new user to not notice that there's lots of good stuff under the hamburger menu?

@macrakis: I think the term I see most commonly used is "Action menu".

Alternatives to hamburger:

Menu Icon
Menu


fix(safe-claiming-app): correct title color

What it solves
Correct title color of claiming widget

@liliya-soroka: Merging this without QA as it only changes the text color and nothing else.


article on remote docker host

Very cool :).  I glanced through and this seems useful to me -- adding container PMs.
ping @taylorb-microsoft @enderb-ms @PatrickLang
Note:  for this article to show up in the left nav, add it to the TOC in virtualization/windowscontainers

Great article!


Zstandard support?

Hi @jbms . Would it be possible to support Zstandard in neuroglancer?
There are a number of JavaScript ports available:
https://facebook.github.io/zstd/
In particular, these one seems to have been maintained within the last year:
https://www.npmjs.com/package/zstddec
https://www.npmjs.com/package/@oneidentity/zstd-js
At Janelia we're thinking of moving data from N5 to Zarr under Zstandard comrpession.

It should already be supported.


Does not allow ->() to be used in a module

Input
→ View on sorbet.run
# typed: strict
module Bar
  extend(T::Sig)

  sig { returns(T.proc.params(a: T.untyped, b: T.untyped).void) }
  def hello
    -> (a,b) { a + b }
  end
end

Observed output
editor.rb:7: Method lambda does not exist on Bar https://srb.help/7003
     7 |    -> (a,b) { a + b }
            ^^^^^^^^^^^^^^^^^^
  Did you mean to `include Kernel` in this module?
    https://github.com/sorbet/sorbet/tree/master/rbi/core/kernel.rbi#L1715: Did you mean: Kernel#lambda?
    1715 |  def lambda(&blk); end
            ^^^^^^^^^^^^^^^^
Errors: 1

Expected behaviour
No issues to be displayed.

This is expected behavior. See https://github.com/sorbet/sorbet/issues/2236

This is something we could model more precisely, but it's going to be a lot of work for comparatively little benefit. You can already work around this problem by using include Kernel in the body of your module, like the error message suggests.

@jez I think this particular case is a little different, though, since this is actually valid Ruby code being flagged as invalid by Sorbet.
For example:
module Bar
  def hello
    -> (a,b) { a + b }
  end
end

class Foo < BasicObject
  include ::Bar
end

Foo.new.hello # is ok
Foo.new.hello.(1, 2) #=> 3

I think the problem is that Sorbet desugars -> to lambda but lambda happens to be a Kernel method, thus causing the error in Sorbet. However, at runtime -> has slightly different semantics than Kernel.lambda, so the code is actually valid.
But I see the point @aisamanra is making, that it might be way more hassle to model this precisely. I just wanted to point out that this is not exactly the same case as #2236, though.

What about desugaring -> as Kernel.lambda?
module Bar
  def hello
    Kernel.lambda { |a, b| a + b }
  end
end

class Foo < BasicObject
  include ::Bar
end

puts Foo.new.hello # is ok
puts Foo.new.hello.(1, 2) #=> 3

And it typechecks.

Nice idea! can you make a PR with it?


Tor general error when connecting clearnet hosts in hybrid mode

Your environment

version of lnd:6e2214fd0fc04adff705141b17482550bee58cde + tor workaround
Linux murphy 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
bitcoind 22.0

Steps to reproduce
lncli connect ...@<IP_ADDRESS>:9735
Expected behaviour
connecting to node
Actual behaviour
Tor general error

I can be the one to blame here:
I modify lncfg/address.go to make it possible to start LND with my config.
Lnd is instructed to connect via clearnet to clearnet targets (that's why tor general error very much surprise me here).
diff --git a/lncfg/address.go b/lncfg/address.go
index afb4188dd..b9c52b4bc 100644
--- a/lncfg/address.go
+++ b/lncfg/address.go
@@ -232,7 +232,7 @@ func ParseAddressString(strAddress string, defaultPort string,
 		// Otherwise, we'll attempt the resolve the host. The Tor
 		// resolver is unable to resolve local or IPv6 addresses, so
 		// we'll use the system resolver instead.
-		if rawHost == "" || IsLoopback(rawHost) ||
+		if rawHost == "" || IsLoopback(rawHost) || true ||
 			isIPv6Host(rawHost) {

 			return net.ResolveTCPAddr("tcp", addrWithPort)
--

Even if the issue is due to my nasty workaround, I'd appreciate an advice for an alternative. Maybe downgrading lnd or rolling back something will fix either "tor general error" or config validation issues? (Preferably both)

If you don't already know: that patch you applied will end up leaking all your DNS queries over clearnet. If you've upgraded to master (not considered to be stable, not a tagged release) then you'll be unable to downgrade.
I recommend reviewing your lnd.conf and also ensuring that your tor daemon is reachable over the specified control port.

I don't really care for dns leaks.
The problem is, I have no idea how to satisfy lncfg in my config file with current tip of the master branch. That is, I can review but the only way to fix it for me will be trial and error. I don't grok the nature of the problem.
Sorry for bothering y'all, but I'm running lnurl-pay.me on master branch (sometimes patched), and I assume there aren't too many people as reckless as me, and my battle-testing is beneficial for lnd. So we both lose if I'm unable to run the master's tip, and I want to continue to do that.

I think you might be affected by an issue which is fixed in this PR: https://github.com/lightningnetwork/lnd/pull/6376. Are you able to give it a spin to confirm the fix?

Or can you at least post your config so we can take a look to spot potential problems?

externalip=<IP_ADDRESS> triggers "tor general error" on config validation (with bare master, also with PR #6376, but not with my workaround).
I SUSPECT that tor general error on connect'ing a clearnet target while in skip-proxy-for-clearnet mode is of the same nature, but triggered in some other code. I haven't tested it yet, though.

tlsextradomain=vds.sw4me.com
enable-upfront-shutdown=1
tor.v3=1
tor.privatekeypath=<redacted>
tor.active=1
tor.skip-proxy-for-clearnet-targets=1

bitcoin.active=1
bitcoin.mainnet=1
bitcoin.node=bitcoind

autopilot.active=0

nat=false
rpclisten=localhost:10009

alias=lnurl-pay.me
color=#0020FF

externalip=<IP_ADDRESS>
externalip=<IP_ADDRESS>
bitcoin.minhtlc=1000
bitcoin.basefee=0
bitcoin.feerate=25

protocol.wumbo-channels=1
db.bolt.auto-compact=true
db.bolt.auto-compact-min-age=480h
db.batch-commit-interval=1s
caches.reject-cache-size=200000
caches.channel-cache-size=80000
blockcachesize=83886080

gc-canceled-invoices-on-startup=1
wallet-unlock-password-file=/srv/lnd/data/.lnd/pw

max-cltv-expiry=8064
accept-keysend=true
accept-amp=true
bitcoind.estimatemode=ECONOMICAL

workers.read=200
caches.reject-cache-size=200000
caches.channel-cache-size=80000
healthcheck.chainbackend.interval=10m
ignore-historical-gossip-filters=0

healthcheck.chainbackend.attempts=20
; The number of times we should attempt to check our tor connection before
; gracefully shutting down. Set this value to 0 to disable this health check.
healthcheck.torconnection.attempts=3

; The amount of time we allow a call to our tor connection to take before we
; fail the attempt. This value must be >= 1s.
healthcheck.torconnection.timeout=10s

; The amount of time we should backoff between failed attempts to check tor
; connection. This value must be >= 1s.
healthcheck.torconnection.backoff=30s

; The amount of time we should wait between tor connection health checks. This
; value must be >= 1m.
healthcheck.torconnection.interval=1m

Okay, I think for some reason the IP address <IP_ADDRESS> cannot be resolved properly by Tor.
But since you're using the tor.skip-proxy-for-clearnet-targets=1 config, it shouldn't be.
Can you try if this patch fixes things for you?
tor.diff.txt

@guggero it fixes config validation, but the issue with connecting to clearnet manually remains:
lnd@murphy:~$ lncli connect 03ee58475055820fbfa52e356a8920f62f8316129c39369dbdde3e5d0198a9e315@<IP_ADDRESS>:9734
[lncli] rpc error: code = Unknown desc = tor general error

Ok, we tracked down the issue. There was a regression merged into the master branch of btcd which has been resolved.  Once #6376 is updated, this issue should be resolved.
Alternatively, if you want to try out the fix sooner, then you can run this command:
go get -v github.com/btcsuite/btcd@074266215c26f8c4731330abb515f92b905f8dfa
go mod tidy

Then build as normal, and things should be resolved.

@Roasbeef thanks, it helped (I haven't really checked whether it skips tor for clearnet targets, though)

I encountered the same error in this issue: "tor general error". But not with the the lncli openchannel command using the --connect argument. I was able to work-around the error by using the lncli connect command first then using the openchannel command again but without the --connect flag.


Kong routes requests to targets deleted

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
2.8.2
Current Behavior
Delete target <IP_ADDRESS>:50787  and add target <IP_ADDRESS>:50787 for one upstream.
But the request maybe route to <IP_ADDRESS>:50787.
Check the db:target, it only one entity:<IP_ADDRESS>:50787.
After I  try add <IP_ADDRESS>:50787 and remove <IP_ADDRESS>:50787 from admin api, but still  maybe route the request to <IP_ADDRESS>:50787.
The Kong cluster have tow node. One of them has this problem.
Expected Behavior
All nodes can be update correctly when operate the upstream from the Admin api.
Steps To Reproduce
There is a probability that it cannot reproduce stably.
Anything else?
Some configure:
worker_consistency = eventual
worker_state_update_frequency = 20
db_update_frequency = 5
db_update_propagation = 0
db_cache_ttl = 0

db: PGSql
I find some issue: 8757

This issue has reappeared recently. It is likely to occur when removing many of targets at the same time.

@locao Insights?

Hi @altnti, thanks for your report.
This issue was fixed in #10384 and was released in Kong 3.2.2. As we don't have plans for new Kong 2.x releases, the fix was not backported.
If this issue is happening frequently, we recommend that you upgrade your Kong installation to the latest version. If you plan to stick with Kong 2.x longer, you can apply the fix in #10384 to the release/2.8.x branch and build Kong using the supplied instructions in DEVELOPER.md file.

Awesome!  Thank you. @locao


Update Redis version to 7.0.4

Resolves https://github.com/IBM/operator-for-redis-cluster/issues/56

Thanks for the PR @4n4nd! Are you still seeing the slots issue you mentioned in the ticket? I would assume there are several commands we need to ensure are working with this change. Also we need to determine the migration/upgrade path for our users to get to this new version. Do we want to support 6.x and 7.x for a time? I think we have to do it this way bc we can't guarantee users' clients/applications are ready for 7.x.

Are you still seeing the slots issue you mentioned in the ticket?

I am not, the radix dependency update seems to have fixed it

I would assume there are several commands we need to ensure are working with this change. Also we need to determine the migration/upgrade path for our users to get to this new version.

I was successfully able to perform a rolling update from 6.2.x to 7.0.x just by updating the node container image.

Do we want to support 6.x and 7.x for a time?

I think we could do that. Once some initial tests are done on 7.0.x, I don't think it would be that difficult to maintain support for it. Are there any specific tests that you'd like me to perform on this?

I think we could do that. Once some initial tests are done on 7.0.x, I don't think it would be that difficult to maintain support for it. Are there any specific tests that you'd like me to perform on this?

I think a good place to start would be ensuring all the commands sent through DoCmd, DoCmdWithRetries, and PipeAppend work properly. I would think we'd see error messages in the logs on failure, but it's possible some errors are squelched. This is probably an opportunity to beef up our integration/e2e tests (if needed) as just bringing up a redis cluster executes most of these commands. Scaling will cause most of the others to be invoked.
❯ grep -Ehor '\.PipeAppend\(.*\)|\.DoCmd\(.*\)|\.DoCmdWithRetries\(.*\)' --include='*.go' | sort | uniq
.DoCmd(ctx, &keys, "CLUSTER", "GETKEYSINSLOT", slot.String(), batch)
.DoCmd(ctx, &rcv, cmd, args...)
.DoCmd(ctx, &resp, "CLIENT", "SETNAME", cnx.clientName)
.DoCmd(ctx, &resp, "CLUSTER", "COUNTKEYSINSLOT", slot.String())
.DoCmd(ctx, &resp, "CLUSTER", "FAILOVER")
.DoCmd(ctx, &resp, "CLUSTER", "FORGET", id)
.DoCmd(ctx, &resp, "CLUSTER", "MEET", ip, port)
.DoCmd(ctx, &resp, "CLUSTER", "NODES")
.DoCmd(ctx, &resp, "CLUSTER", "REPLICATE", primary.ID)
.DoCmd(ctx, &resp, "CLUSTER", "RESET", ResetSoft)
.DoCmd(ctx, &resp, "CLUSTER", "SETSLOT", slot.String(), action, node.ID)
.DoCmd(ctx, &resp, "CLUSTER", "SLOTS")
.DoCmd(ctx, &resp, "CLUSTER", args...)
.DoCmd(ctx, &resp, "CONFIG", "GET", pattern)
.DoCmd(ctx, &resp, "CONFIG", args...)
.DoCmd(ctx, &resp, "DEL", keys...)
.DoCmd(ctx, &resp, "INFO", "SERVER")
.DoCmd(ctx, nil, "FLUSHALL")
.DoCmdWithRetries(ctx, &resp, "MIGRATE", args...)
.PipeAppend(radix.Cmd(nil, "CLUSTER", "RESET", mode))
.PipeAppend(radix.Cmd(nil, "CLUSTER", "SETSLOT", slot.String(), action))
.PipeAppend(radix.Cmd(nil, "CLUSTER", "SETSLOT", slot.String(), action, nodeID))
.PipeAppend(radix.Cmd(nil, "FLUSHALL"))

I was successfully able to perform a rolling update from 6.2.x to 7.0.x just by updating the node container image in the RedisCluster CR.
Did you have data in the cluster? If not, we should definitely test that.

Did you have data in the cluster? If not, we should definitely test that.

Just added a bunch of keys manually and tested the update. All the keys successfully migrated to the updated cluster.
Cluster configuration was: 3 primaries and 2 replication-factor. Updated from version 6.2.x to v7.0.4

I think a good place to start would be ensuring all the commands sent through DoCmd, DoCmdWithRetries, and PipeAppend work properly.

I'll check the redis changelogs to see if any of the commands you listed were updated or not

I just brought up a 7.x cluster for testing and so far things look good. I did see this warning in the logs though. Will investigate.
rediscluster-rc-node-for-redis-mhw7v redis-node I0914 20:23:02.779987       1 log.go:16] 20:M 14 Sep 2022 20:23:02.779 * No cluster configuration found, I'm 28d90c9c229d417102bc774a847307eb01083c5e
rediscluster-rc-node-for-redis-mhw7v redis-node I0914 20:23:02.873994       1 log.go:16] 20:M 14 Sep 2022 20:23:02.873 * Running mode=cluster, port=6379.
rediscluster-rc-node-for-redis-mhw7v redis-node 20:M 14 Sep 2022 20:23:02.873 # Server initialized
rediscluster-rc-node-for-redis-mhw7v redis-node 20:M 14 Sep 2022 20:23:02.873 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memor
y = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

Changes that might affect operator behavior:
CLUSTER-

https://github.com/redis/redis/blob/7.0/00-RELEASENOTES#L547
https://github.com/redis/redis/blob/7.0/00-RELEASENOTES#L130
https://github.com/redis/redis/blob/7.0/00-RELEASENOTES#L285 <- could be an issue later
CONFIG
https://github.com/redis/redis/blob/7.0/00-RELEASENOTES#L291

@cin any luck with this PR?

Hey @4n4nd, sorry for the delay. I was out unexpectedly on Thursday and Friday.

No worries! Please take your time. I hope everything is going well for you.

I think the main thing that needs to change here is maintaining support for 6.x.

Yeah, since we are not making any changes to the operator, I think we could just add another Dockerfile (Dockerfile.node.6.2.x) which can be removed once Redis v6.2 is EOL in August 2023.

I'm not sure how they should be named off-hand. Will need to think about that...open to suggestions...

I had one suggestion. Since Redis Node images are essentially Redis images, we could just tag them as whatever Redis version they are. That way we could maintain builds for both.
Example: node-for-redis:7.0.4 and node-for-redis:6.2.7
Maybe we could also re-tag some older images to match this naming convention. wdyt?

Actually the node image contains code (see pkg/redisnode). It's responsible for configuring and managing Redis (among other things). I've never actually looked at it closely. That said, we'll need to version the image w/the github tag as well. So I think we should do something like node-for-redis:x.y.z-7.0.4 and node-for-redis:x.y.z-6.2.7, where x.y.z is the github tag.

Maybe we could also re-tag some older images to match this naming convention. wdyt?

I wouldn't worry about re-tagging any images bc they align with the helm charts. We'll definitely want to bump the minor version with this change though.

So I think we should do something like node-for-redis:x.y.z-7.0.4 and node-for-redis:x.y.z-6.2.7, where x.y.z is the github tag.

I think this is a good idea. We would have unique images for any operator code changes as well as any redis updates.

@cin I updated the release workflow. Could you please give it a look?

@cin tested and updated the Makefile with your suggestion.
I am not very familiar with skaffold, but you could pass the version as make container-node REDIS_VERSION_6=6.2.6 to build a specific version.

I just noticed the build info strings. build.go and the corresponding set call here.
So the way this is being done now will not have the right REDIS_VERSION listed in the logs when it starts. Not the biggest deal but it'd be confusing. Should we maybe just allow the user to call the Makefile w/REDIS_VERSION? If they don't set it, we default it to 6.2.7. If they do set it, let it go through and at least try to build the image, etc. They'd have to call the makefile again to build another version, but I think that's fine (given that we'll have automation building both). Thoughts?
We also need to update the image in the helm chart. Right now, we don't have a Redis version override; but in order to default the image properly, we'll need it. You can still get this to work now but simply specifying the tag but we should make it as easy as possible on users of the operator.
Nitpicking here, but I think we should swap the github tag and redis version in the image tag name. I just looked at how we've done this in other projects, and we used the following format: node-for-redis:7.0.4-x.y.z. Sorry, I should have looked that up before posting about it.

Oh, appVersion. Should it have the Redis version? Not sure if the linter will like that too...

I just noticed the build info strings. build.go and the corresponding set call here.

taking a look 👀

Should we maybe just allow the user to call the Makefile w/REDIS_VERSION? If they don't set it, we default it to 6.2.7. If they do set it, let it go through and at least try to build the image, etc. They'd have to call the makefile again to build another version, but I think that's fine (given that we'll have automation building both). Thoughts?

Yeah, I think letting the users set REDIS_VERSION would be the simplest solution. For the default value, I would want to keep it to 7.0.4 since we want new users to start with a newer version of Redis (6.2 will EOL in August 2023).

We also need to update the image in the helm chart. Right now, we don't have a Redis version override; but in order to default the image properly, we'll need it. You can still get this to work now but simply specifying the tag but we should make it as easy as possible on users of the operator.

What if we use the latest tag as default in the helm charts? Anyone running in prod would want to fix it to a version any way and users who are trying out the operator won't care as much. If we do this, we will have one less value change on every redis version update.

Nitpicking here, but I think we should swap the github tag and redis version in the image tag name. I just looked at how we've done this in other projects, and we used the following format: node-for-redis:7.0.4-x.y.z. Sorry, I should have looked that up before posting about it.

No worries 👍 I can just make the changes.

I would want to keep it to 7.0.4

Fair enough.

What if we use the latest tag as default in the helm charts?

I've never been a fan of using latest for anything. :) It can be convenient at times, but it always ends up biting you somewhere down the line. Also, check out the other comment I made about the appVersion. These things impact each other, so it complicates things a bit.

I just noticed the build info strings. build.go and the corresponding set call here.

The linter didn't seem to mind it. So, I updated the Makefile to make it consistent with the release.yaml. wdyt?

@cin any luck with this PR?

Hey @4n4nd. Sorry I got pulled into some other things and haven't had a chance to get back to this since last Thursday. There's one place that needs some cleanup that I know of offhand though and it's defaulting the chart image. As it stands right now, the user would always have to override the tag in order to set the node-for-redis image properly. I think it's good after that (but will need to test to make sure).

@cin sorry for the delay. I couldn't really come up with a perfect solution.
How about we stick to 7.0.x as default and add a release_v6.yaml github workflow that builds node images for Redis v6.x updates? This way we would have support for both versions and once Redis v6 is EoL, we could remove the workflow yaml file.

@4n4nd I'm sorry for the delay; I thought I responded to this. I think I'm okay with breaking out v6 into a separate workflow. This will simplify things a good bit especially as you mentioned when v6 is EOL. I think we should also look into fixing up the Makefile for this as well (not the biggest issue but will is nice to have it usable). There's probably a cleaner way to do this but something like this maybe could work.


"ignis logging" Configuring the IgnisLogger

logging.logreader.txt
Testing Ignis "ignis_logging.ipynb" tutorial using qiskit master branch.
Name                        Version                   Build  Channel
qiskit-aqua                    0.5.6                    pypi_0    pypi
qiskit-ibmq-provider      0.3.2rc1               pypi_0    pypi
qiskit-ignis                     0.2.0                    pypi_0    pypi
qiskit-terra                     0.9.0                    pypi_0    pypi
Problem: Tutorial ignis_logging.ipynb fails when using log_reader.read_values() function.  The ignis configuration file  "USER HOME DIR"/.qiskit/logging.yaml  parameters do not seem to be taken into account.
file_logging: true		# Enables/disables file logging (true/false)
log_file: ignis_test_log.log	# Name of the file log
max_size: 1000000		# Max file size (in bytes).
max_rotations: 5		# Max number of file rotations
Please note that specifying the log file to the log_reader works fine # log_reader.read_values("ignis_test_log.log")

Thanks @patdenim for submitting this. Which OS are you trying ? Can you specify the full path of your logging.yaml file ? Thx

Hi Eli, i'm running Windows10 and the path of the file is in my case c:\users\PatrickMensac.qiskit\logging.yaml
from what i could test, the logging.yaml seems correctly parsed by  ignis_logging.py

Eli, i guess that the problem seems to come from the re.compile() from ignis.logging.py  in get_log_files() function.
I could made it working by commenting the re.compile() line

Thks
Patrick

Thanks Patrick for looking at this. Let me check this first before applying a change. I'll try to tend to this during the weekend.

Hi Patrick, I've tested it on Linux, it works fine. Maybe there is an issue with how the regular expression is interpreted or matched in Windows. I'll check this on Windows next.
The point of this regular expression check is to retrieve only the file names which comply with the naming convention of the file rotation.

Hi Eli,
This seems to be related to the backslash "" in windows ... and replacing "" by  2 "\" works ...
m = re.compile(os.path.abspath(os.path.abspath(file_name)).replace("\\","\\\\") + r"$|" + os.path.abspath(os.path.abspath(file_name)).replace("\\","\\\\") + r".\d+$")
That should also work for Linux ...
Patrick

Hi Patrick, you are correct. I've checked this both on Linux and Windows and it works. I'll open a change request to apply this. Thanks!


checkOverflow: click problem && add lock events

some click events did not work with checkOverflow=true

Looks good, thanks


"Entity Framework Core with ASP.NET Core MVC" link points to Razor pages EF tutorial

Issue description
On the main docs page the "Entity Framework Core with ASP.NET Core MVC" link points to Razor pages EF tutorial. As this is the main docs page, there is no option to edit and open a PR directly i'm afraid
I guess the link path is intentional as the preferred method for new development is Razor pages, but opened this issue for discussion.
I think it may be more beneficial to maintain the link to the MVC tutorial, and then direct the user with a prominent banner on the MVC overview that they should prefer Razor pages?
Otherwise it is confusing for the user that they have been directed to the Razor pages tutorial 🤔

@wadepickett  can you fix this?


azidentity: az-cli resource does not include trailing slash, leading to auth-tokens being rejected by Microsoft Fabric SQL Endpoints

Bug Report

import path of package in question: github.com/Azure/azure-sdk-for-go/sdk/azidentity
SDK version: v1.5.1
output of go version: go version go1.22.1 darwin/arm64

What happened? Entra auth tokens generated by the az-cli auth-method are rejected by Microsoft Fabric SQL endpoints.

What did you expect or want to happen? Similar tokens generated by the C# Azure Identity SDK are accepted.

How can we reproduce it? Attempt to use the 'sqlcmd' executable to run queries against Microsoft Fabric SQL endpoints. 'sqlcmd' is a Go executable, using the azidentity SDK. For example, running the following on MacOS should attempt az-cli auth:
az login
sqlcmd -G -S <fabric sql endpoint>.datawarehouse.fabric.microsoft.com -Q 'SELECT 1;'

Anything we should know about your environment.

If I patch azidentity to include a trailing slash in the resource we pass to the az-cli after stripping off the /.default suffix the auth tokens are accepted by Microsoft Fabric SQL endpoints:
diff --git a/sdk/azidentity/azure_cli_credential.go b/sdk/azidentity/azure_cli_credential.go
index b9976f5fed..01e3557023 100644
--- a/sdk/azidentity/azure_cli_credential.go
+++ b/sdk/azidentity/azure_cli_credential.go
@@ -113,8 +113,11 @@ func (c *AzureCLICredential) GetToken(ctx context.Context, opts policy.TokenRequ
 // defaultAzTokenProvider invokes the Azure CLI to acquire a token. It assumes
 // callers have verified that all string arguments are safe to pass to the CLI.
 var defaultAzTokenProvider azTokenProvider = func(ctx context.Context, scopes []string, tenantID, subscription string) ([]byte, error) {
+       resource := scopes[0]
        // pass the CLI a Microsoft Entra ID v1 resource because we don't know which CLI version is installed and older ones don't support v2 scopes
-       resource := strings.TrimSuffix(scopes[0], defaultSuffix)
+       if strings.HasSuffix(resource, defaultSuffix) {
+               resource = strings.TrimSuffix(resource, defaultSuffix) + "/"
+       }
        // set a default timeout for this authentication iff the application hasn't done so already
        var cancel context.CancelFunc
        if _, hasDeadline := ctx.Deadline(); !hasDeadline {

I really don't know if this is a Fabric bug or an azidentity Go-SDK-bug, but the C# SDK when used in similar manner includes a trailing slash in the resource.
Specifically, this test C# program generates an Entra token with an aud claim of https://database.windows.net/:

Click me
using Dapper;
using Microsoft.Data.SqlClient;

var server = Environment.GetEnvironmentVariable("SQL_ENDPOINT");
var connString = $"Server={server};Authentication=Active Directory Default; Encrypt=True;";

using var sqlConnection = new SqlConnection(connString);

sqlConnection.Open();
Console.WriteLine("Connected successfully!");

foreach (var o in sqlConnection.Query("SELECT 1;"))
{
    Console.WriteLine(o);
}

(Note that Microsoft.Data.SqlClient version 5.2.0 isn't working for me in this test, so I used 5.1.5)
And this test Go program generates an Entra token with an aud cliam of https://database.windows.net (note the missing slash), which doesn't work against Microsoft Fabric (unless I used my patched version of azidentity):

Click me
package main

import (
   "database/sql"
   "flag"
   "fmt"
   "os"

   _ "github.com/microsoft/go-mssqldb"
   "github.com/microsoft/go-mssqldb/azuread"
)

func main() {
   var host string
   var database string
   var query string

   flag.StringVar(&host, "host", "", "SQL endpoint")
   flag.StringVar(&database, "database", "", "SQL database")
   flag.StringVar(&query, "query", "", "SQL query")
   flag.Parse()

   if host == "" {
   	errAndExit("missing flag -host")
   }
   if database == "" {
   	errAndExit("missing flag -database")
   }

   connString := fmt.Sprintf("server=%s;database=%s;fedauth=ActiveDirectoryDefault;", host, database)

   db, err := sql.Open(azuread.DriverName, connString)
   if err != nil {
   	errAndExit("opening db: %s", err)
   }
   defer db.Close()

   _, err = db.Exec(query)
   if err != nil {
   	errAndExit("running query: %s", err)
   }

}

func errAndExit(format string, a ...any) {
   fmt.Fprintf(os.Stdout, format, a...)
   fmt.Fprintln(os.Stdout)
   os.Exit(1)
}

Thanks for opening this issue. We can't solve this problem in azidentity because the resource/scope must be exactly correct. Adding a trailing / in all cases would create the problem you're experiencing for other clients. The caller, in this case go-mssqldb, is responsible for passing the correct scope. go-mssqldb apparently trims trailing slashes in all cases; I opened https://github.com/microsoft/go-mssqldb/issues/197 to track fixing that.

go-mssqldb is passing the scope https://database.windows.net/.default. The azidentity SDK is trimming this to https://database.windows.net. Is the expectation that the service-endpoint should be accepting the slash-less version?

The problem isn't really the service's behavior, though a change there could prevent it. All v2 default scopes like foo/.default have an equivalent v1 resource like foo, so the rule for converting between the two is to add or remove /.default. https://database.windows.net/ is apparently the correct v1 resource in this case, making the corresponding v2 scope https://database.windows.net//.default, and that's what go-mssqldb should specify. The fact that the service doesn't accept https://database.windows.net suggests https://database.windows.net/.default is similarly invalid. But it could in principle accept both resource/scope pairs, with and without the extra /, and that would prevent this problem.

Thanks for your help! I'll see if I can get some clarity on the service end of things.


Some menuseparators are double tickness when using display scaling.

When using Windows display scaling some menuseparators are too thick.
Below image is taken at 150% display scaling. I see this at 125% as well.

With 100% display scaling the menus render correctly.
Firefox: 70.0 64-bit & Nightly 64-Bit
OS: Windows 10 64-bit 1903 18362.418
Resolution: 1920x1080p (native)

This should be fixed now, could you confirm? Was just able to reproduce #2 so I'm working on that at the moment.

Can confirm that the menuseparators are the correct thickness on both light and dark now.


fix: use transient_local qos for route

Related Issue(required)
Resolves #119
Description(required)
fix subscriber qos for route
Review Procedure(required)
Make sure that the qos of all route subscribers is set to transient_local.
ag "create_subscription<autoware_auto_planning_msgs::msg::HADMapRoute>\(" ./ -A 3

Related PR(optional)

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read commit-guidelines
[ ] Assign PR to reviewer

If you are adding new package following items are required:

[ ] Documentation with description of the package is available
[ ] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@wep21
If there are any omissions, please let me know. :bow:

@mitsudome-r This modification has not been merged into upstream, but can I proceed to merge? Or, I have to wait to merge until porting has been done?

@mitsudome-r cc: @1222-takeshi
I think porting is finished so can I merge now?

@taikitanaka3 I asked mitsudome-san and he said we can start to merge remaining PRs.


How to run the tests

I'm trying to run the test suite locally, but I'm missing the testAuth.json file.
What should this file look like?
Once I get it working, I'd be happy to update CONTRIBUTING.md with setup details for those who come after.
❯ npm i && npm t

><EMAIL_ADDRESS>test /Users/z/git/forks/node-github
> mocha

(node:63796) DeprecationWarning: child_process: options.customFds option is deprecated. Use options.stdio instead.
module.js:472
    throw err;
    ^

Error: Cannot find module './../testAuth.json'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/z/git/forks/node-github/test/activityTest.js:14:16)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at /Users/z/git/forks/node-github/node_modules/mocha/lib/mocha.js:152:27
    at Array.forEach (native)
    at Mocha.loadFiles (/Users/z/git/forks/node-github/node_modules/mocha/lib/mocha.js:149:14)
    at Mocha.run (/Users/z/git/forks/node-github/node_modules/mocha/lib/mocha.js:306:31)
    at Object.<anonymous> (/Users/z/git/forks/node-github/node_modules/mocha/bin/_mocha:348:7)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:427:7)
    at startup (bootstrap_node.js:151:9)
    at bootstrap_node.js:542:3
npm ERR! Test failed.  See above for more details.

He tells you in the README. https://github.com/mikedeboer/node-github/blob/master/README.md#create-test-auth-file

Thanks, @gscott. I've changed the title of this issue to reflect the larger goal: getting the tests passing in a development environment.
So far..

[x] Create a GitHub personal access token
[x] Create testAuth.json
[ ] ???

@kaizensoze when I run npm test I'm seeing the following message from nearly every test:
  28) [activity] should successfully execute PUT /repos/:owner/:repo/subscription (setRepoSubscription):
     Uncaught AssertionError: { [Error: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}]
  message: '{"message":"Not Found","doc == null
      at /Users/z/git/octokit/node-github/test/activityTest.js:456:24

Is there something else I need to set up first? Is it necessary to create an application authorization rather than a personal access token?

It looks like the tests are specifying the type of each parameter (like String for owner):
client.repos.addCollaborator(
    {
        owner: "String",
        repo: "String",
        username: "String",
        permission: "String"
    },
    function(err, res) {
        Assert.equal(err, null);
        // other assertions go here
        next();
    }
);

When I add {debug: true} to the client, I can see that it's actually injecting those (invalid) values into the request URL:
❯ mocha test/reposTest.js
(node:17439) DeprecationWarning: child_process: options.customFds option is deprecated. Use options.stdio instead.

  [error] { [Error: Invalid value for parameter 'permission': String]
[error]   defaultMessage: 'Bad Request',
[error]   message: 'Invalid value for parameter \'permission\': String',
[error]   code: '400',
[error]   status: 'Bad Request',
[error]   headers: undefined } { url: '/repos/:owner/:repo/collaborators/:username',
[error]   method: 'PUT',
[error]   params:
[error]    { permission:
[error]       { type: 'String',
[error]         required: false,
[error]         validation: '^(pull|push|admin)$',
[error]         invalidmsg: '',
[error]         description: '`pull` - can pull, but not push to or administer this repository, `push` - can pull and push, but not administer this repository, `admin` - can pull, push and administer this repository.',

cc @mikedeboer any tips on getting these test running?

I'm having the same issue.  Validation is failing.

@kaizensoze Any ideas?  I must be doing something wrong, but I can 't see what it is.  I've created testAuth.json with a valid token and I'm running node lib/generate.js before running npm test.

I spent some time digging into this today. From what I can tell, the hand-coded tests were all replaced with generated stubs in https://github.com/kaizensoze/node-github/pull/20. I don't see anything since then that suggests the generated tests were ever passing.
cc @gr2m

Yeah, those generated stubs need to be re-customized on a per-endpoint basis using nock unless there's something better.

@zeke and I started adding a first test via https://github.com/octokit/node-github/pull/5. I’m not sure what the current state of merging the fork with the main project is


Sampler failing when setting skip_transpilation to True

Describe the bug
When setting skip_transpilation to True in transpilation_settings in the run method of the Sampler, jobs fail randomly. For example, evaluating a 6 qubit Bell state circuit with no parameters failed twice in 1000 trials (job ids of the jobs which failed were cdd3msvhc7fs715q3t10 and cdd3s52auedvlnhhqc0g). When a job fails, an AlgorithmError is raised which prevents the program from continuing.
Steps to reproduce
from qiskit import IBMQ
IBMQ.load_account()
from qiskit_ibm_runtime import Session, Sampler
from qiskit.circuit import QuantumCircuit

qc = QuantumCircuit(6)
for i in range(6):
    qc.h(i)
for i in range(0,6,2):
    qc.cx(i,i+1)
qc.measure_all()

with Session(backend='ibmq_qasm_simulator') as session:
    sampler = Sampler(session=session)
    for iteration in range(1000):
        if iteration%25==0:
            print(f"Iteration {iteration} completed")
        job = sampler.run(
                            [qc], [],
                            run_options={"shots": 1024},
                            transpilation_settings={"skip_transpilation": True}
                          )
        result = job.result()

Expected behavior
Evaluates all 1000 circuits without failure
Suggested solutions
To prevent the program from breaking, I added a patch which resends a job when it randomly fails, and also prints the job id, in case I want to view the error log. This doesn't solve the core problem but at least allows the program to continue. The patch was:
class RetrySampler(Sampler):

    def __init__(self, *args, max_retries: int = 5, **kwargs) -> None:
        super().__init__(*args, **kwargs)
        self.max_retries = max_retries

    def run(self, circuits, parameter_values, **kwargs):
        result = None
        for i in range(self.max_retries):
            try:
                job = super().run(circuits, parameter_values, **kwargs)
                result = job.result()
                if result is not None:
                    return job
            except:
                if i != self.max_retries-1:
                    print(f"Sampler job with ID {job.job_id} failed... Starting trial number {i+2} for this iteration")
                pass
        if result is None:
            raise RuntimeError(f"Runtime job failed! Maximum number of retries {self.max_retries} exceeded")

where then we replace Sampler with RetrySampler in the above code.
Additional Information

qiskit-ibm-runtime version: 0.7.0rc3
Python version: 3.10.4
Operating system: macOS Monterey 12.6 M1 2020

Update
This issue can also occur when skip_transpilation is set to False. Further, other errors may randomly arise. Below is the updated version of the patch which catches these other errors.
import signal, time

from qiskit_ibm_runtime import Sampler
from qiskit.providers import JobStatus

def timeout_handler(signum, frame):
    raise Exception('Iteration timed out')

class RuntimeRetrySampler(Sampler):
    """RuntimeRetrySampler class.

    This class inherits from Qiskit IBM Runtime's Sampler and overwrites its run method such that it retries calling it
    a maximum of 'max_retries' consecutive times, if it encounters one of the following randomly occuring errors:

    * A Sampler error (in this case "Job.ERROR" is printed)
    * A timeout error where the job either remains running or completes but does not return anything, for a time larger
      than 'timeout' (in this case "Job.CANCELLED" is printed)
    * A creation error, where the job fails to be created (in this case "Failed to create job." is printed). Usually
      this error occurs when the server is overloaded with jobs, so in this case we wait before retrying.
    """

    def __init__(self, *args, max_retries: int = 5, timeout: int = 3600, **kwargs) -> None:
        super().__init__(*args, **kwargs)
        self.max_retries = max_retries
        self.timeout = timeout
        signal.signal(signal.SIGALRM, timeout_handler)

    def run(self, circuits, parameter_values, **kwargs):
        result = None
        for i in range(self.max_retries):
            try:
                job = super().run(circuits, parameter_values, **kwargs)
                while job.status() in [JobStatus.INITIALIZING, JobStatus.QUEUED, JobStatus.VALIDATING]:
                    time.sleep(5) # Check every 5 seconds whether job status has changed
                signal.alarm(self.timeout) # Once job starts running, set timeout to 1 hour by default
                result = job.result()
                if result is not None:
                    signal.alarm(0) # reset timer
                    return job
            except Exception as e:
                if 'job' in locals(): # Sometimes job fails to create
                    if job.status() not in [JobStatus.DONE, JobStatus.ERROR, JobStatus.CANCELLED]:
                        job.cancel()
                    if i != self.max_retries-1:
                        print("\nSomething went wrong...")
                        print(f"Job ID: {job.job_id}. Job status: {job.status()}.")
                        print(f"\n\nERROR MESSAGE:\n{e}\n\n")
                        print(f"Starting trial number {i+2}...\n")
                else:
                    print("\nSomething went wrong...")
                    print(f"Failed to create job.")
                    print(f"\n\nERROR MESSAGE:\n{e}\n\n")
                    print(f"Starting trial number {i+2}...\n")
                    time.sleep(15) # Usually this error happens when there is a job overload, so we wait before retrying
                signal.alarm(0) # reset timer
        if result is None:
            raise RuntimeError(f"Program failed! Maximum number of retries ({self.max_retries}) exceeded")

Update
Here is the patch updated such that it works for the Estimator too (i.e. the retry logic here is common to both the Sampler and the Estimator)
import signal, time
from abc import ABC

from qiskit_ibm_runtime import Sampler, Estimator, Session
from qiskit.providers import JobStatus

def timeout_handler(signum, frame):
    raise Exception('Iteration timed out')

class RetryPrimitiveMixin:
    """RetryPrimitive class.

    This class inherits from Qiskit IBM Runtime's Primitives and overwrites its run method such that it retries calling it
    a maximum of 'max_retries' consecutive times, if it encounters one of the following randomly occuring errors:

    * A Primitive error (in this case "Job.ERROR" is printed, and the job is cancelled automatically)
    * A timeout error where the job either remains running or completes but does not return anything, for a time larger
      than 'timeout' (in this case the job is cancelled by the patch and "Job.CANCELLED" is printed)
    * A creation error, where the job fails to be created because connection is lost between the runtime server and the
      quantum computer (in this case "Failed to create job." is printed). If this error occurs, the patch connects the user
      to a new Session (to be handled with care! also, this will unfortunately put the next job in the queue).
    """

    def __init__(self, *args, max_retries: int = 5, timeout: int = 3600, **kwargs) -> None:
        super().__init__(*args, **kwargs)
        self.max_retries = max_retries
        self.timeout = timeout
        self.backend = super().session._backend
        signal.signal(signal.SIGALRM, timeout_handler)

    def run(self, *args, **kwargs):
        result = None
        for i in range(self.max_retries):
            try:
                job = super().run(*args, **kwargs)
                while job.status() in [JobStatus.INITIALIZING, JobStatus.QUEUED, JobStatus.VALIDATING]:
                    time.sleep(5) # Check every 5 seconds whether job status has changed
                signal.alarm(self.timeout) # Once job starts running, set timeout to 1 hour by default
                result = job.result()
                if result is not None:
                    signal.alarm(0) # Reset timer
                    return job
            except Exception as e:
                print("\nSomething went wrong...")
                print(f"\n\nERROR MESSAGE:\n{e}\n\n")
                if 'job' in locals(): # Sometimes job fails to create
                    print(f"Job ID: {job.job_id}. Job status: {job.status()}.")
                    if job.status() not in [JobStatus.DONE, JobStatus.ERROR, JobStatus.CANCELLED]:
                        job.cancel()
                else:
                    print("Failed to create job.")
                print(f"Starting trial number {i+2}...\n")
                print(f"Creating new session...\n")
                signal.alarm(0) # Reset timer
                super().session.close()
                self._session = Session(backend=self.backend)
        if result is None:
            raise RuntimeError(f"Program failed! Maximum number of retries ({self.max_retries}) exceeded")

class RetrySampler(RetryPrimitiveMixin, Sampler):
    pass

class RetryEstimator(RetryPrimitiveMixin, Estimator):
    pass

I'm going to close this issue since it doesn't seem to be related to skip_transpilation. The stability of Qiskit Runtime service has improved greatly since 1H of 2023.
@luciacuervovalor if you encounter other failures, please create new issues or contact support.


Possibility to customize column headers and add columns.

The tracing generated by our system has a specific syntax.
e.g. 2016-04-05T07:32:03.268567;{DHCPS};04;{0b18.0b5c};IP-address is '<IP_ADDRESS>', subnet mask is '<IP_ADDRESS>';Server.cpp(445)
It would be nice to be able to customize the column header (Line,Date,Time,PID,Process and Message)
with own keywords. Also the possibility to add extra columns would be nice. e.g. TID column, trace originator etc.
The .dblog files requires a specific syntax : "DebugView++.exe	File Identification Header, DebugView++ Format Version 1" as indicated by the first line in a .dblog file.
Can something be done to define your own set of columns with your own header name(s) ?

Thanks for you suggestion, right now this kind of thing it not possible. It will become possible once we implement #191 however, we don't have any plans / deadlines for this yet.


Fix some deprecation warnings and white spaces.

The deprecation warning is for [a] concatenation.
Also fix a bug/weird use of &&

Thanks!


refactor(vote): reorganize read and write for migrate completed polls

we should open a new merge, this one seems botched


add support for calendars other than Gregorian

When I initially started Jiff, my plan was always to stick to the Gregorian calendar. And I planned this even though Temporal specifically supports non-Gregorian calendars. Temporal has blazed a trail that shows how to support non-Gregorian calendars by effectively defining a mapping between non-Gregorian and ISO 8601 calendars (where ISO 8601 is basically equivalent to the Gregorian calendar), and then doing operations in ISO 8601 space. IIRC, there are some assumptions they make about calendars (like, numeral day 1 is always the first day of the month), but otherwise most everything is calendar independent.
My feelings on this have largely remained unchanged. I would prefer not support non-Gregorian calendars and instead point users toward other libraries, like icu_calendar, that specialize in this sort of thing.
It is possible my feelings could be changed on this matter in the future, but I think I'd want at least a few criteria to be satisfied first:

Some very compelling use cases are provided.
There aren't any plausible work-arounds external to Jiff.
A strong abstraction barrier can be defined between most of the datetime arithmetic in this library and the details of non-Gregorian calendars.
It can be an opt-in feature so that the vast majority of users that don't need this don't have to pay for it.

FWIW, temporal_rs is currently planned to be a full implementation of the specification with non-gregorian calendar support.


[slides] chapter rnn modern

Job d2l-zh/PR-901/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-901/


Adapt to HQ homepage

📝Changed routes:

/

(view full size)

Commit 5a2c45420dc7e8891b7e87c003584b73b7953bd7 (https://summer-git-hc-36.hackclub.dev).

Wow, summer of making is going on the homepage omg!! also the background image really improves the site I've been thinking of what could go there as it was a bit bland


Clarify macaroon type

Some users might not be aware of the implications of having a macaroon in their DNS records, so a warning seems highly appropriate.
Clarification about this was already requested in #5

Indeed. Thank you!


Blog post: Private team snapshots

@hyu : I'm done the initial draft here. Just pending screenshots/gifs of some of the improvements in https://app.clubhouse.io/windmill/epic/7991/snapshots-ux-improvements

General comment: I'm not sure that this blog post will resonate with someone who's not already sold on snapshots. A more persuasive format might be:

brief recap of what snapshots are/why they're great
...and we've added this functionality that unlocks this feature for a whole new swath of users
why [private] snapshots are especially awesome when used on your team
toward our Tilt Cloud vision.

I cosign @maiamcc's feedback. Some additional points:

Did you see Dan Miller's earlier blog post, Solving the Laggy Human Shell? He writes:

Introducing Tilt Snapshots

A snapshot is a link that you can send to someone that will allow them to interactively explore your current Tilt state. This is useful for async debugging and adding context to bug reports. They look like pretty much just like Tilt, but frozen in time. Here’s an example:

Now, I'm not going to claim that people are such close followers of the Tilt blog that they would be like, "Hey, didn't you already launch this feature?!" But, I know the context and feel mild embarassment that we might come off like we have goldfish memory!
This is another reason that I really like Maia's framing of "...and we've added this functionality that unlocks this feature for a whole new swath of users" There's also compelling story we can tell here about our product development process, where we listen to customers and incorporate their feedback. (AND one more power move would be to address this challenge, "Wait, isn't 'private' snapshots an obvious feature?" — Aka, we could speak to the fact that we've spent the intervening time since Dan Miller's post in October really building out our team platform. So Private Team Snapshots is the culmination of a lot of cool features coming together.)

2. We should be careful with using the term "DevEx"...that is a useful internal shorthand for the customer we want to target.  But not everyone self-identifies as “DevEx”. That term might even be a turn off, like “Huh? I’m a tech lead / engineer / devops, not ‘DevEx’…this must not be for me.”

@hyu @maiamcc : Thanks for the feedback. I'm going to get Dan B to review https://github.com/tilt-dev/tilt.build/pull/673 within the next week or so, and then this one afterward. So we can be aligned on the messaging in both places. Hopefully that should dovetail nicely with work wrapping up by Han? (For https://app.clubhouse.io/windmill/epic/7991/snapshots-ux-improvements.)

@maiamcc : I chatted briefly with Dan about this. (And also https://github.com/tilt-dev/tilt.build/pull/673/.) At least this week, Dan is focused on other priorities.
@hyu is focused on carving out next steps for snapshots and I will be supporting them. See https://app.clubhouse.io/windmill/story/8486. So I think we don't have to publish this blog post anytime soon, and we can roll this blog post into that process. I'll comment further on https://github.com/tilt-dev/tilt.build/pull/673 though, as I don't want that one to get stale.


App does not show files contained in .arc file after opening

Copy of ArcExplorer previously working stopped working after accepting some kind of update popup that involved New Donk City Hall.
Occurring on a Windows 11 Home, version 10.0.22621 Build 22621
Attempted fixes:

Restarting computer
Deleting and reinstalling ArcExplorer 1.4.4
Making sure the .arc file is valid (17,600,800,616 bytes and a good 13.0.1 MD5 hash)
dumping a new .arc file
deleting %localappdata%/ArcExplorer

Video of this happening: https://github.com/ScanMountGoat/ArcExplorer/assets/70489680/b315d2bd-0eba-405f-b034-58a0288a8bf2
Some other screenshots:

Do you get any errors when opening the arc file? Your data.arc is probably fine if you verified the checksum. The only thing I can think of is that the hashes got messed up somehow. If you delete the hashes.txt file from %localappdata%/ArcExplorer, it should download the latest file the next time you open the application.

I did not get any errors, and we tried deleting the entirety of the %localappdata%/ArcExplore folder, which should have included the hashes.txt file

Are you able to see the files on one of the more recent 1.4.x versions in releases? I would also check that the hashes.txt file is correct.

I have confirmed that the hashes.txt file was included in the deletion. What would you like me to do with the 1.4.x files?

Check with a text editor like notepad that the hashes.txt file looks ok. I would also try with 1.4.0, which you can download from releases.


Right-Click on handle results in connection bug

Describe the Bug
When a user right clicks a handle (don't ask me why, but it happened), then react flow starts showing a connection. The user isn't dragging, but a connection follows the cursor from now on. Even left or right clicks won't help to undo it.
Your Example Website or App
https://reactflow.dev
Steps to Reproduce the Bug or Issue

The bug can be reproduced on the project's website. Visit https://reactflow.dev
Right click on any node output handle

Expected behavior
Right click shouldn't do anything and be ignored
Screenshots or Videos
https://user-images.githubusercontent.com/13085980/150882143-0e92b7d1-1dcb-4756-b07f-c55fe7410962.mp4
Platform

OS: Linux
Browser: Chrome
Version: 96

Additional context
No response

Hey @andys8
thanks for the report! Crazy that no one has noticed this before :D We'll have a look!

Thank you!


[WIP] adding node selector to snr daemonset

ECOPROJECT-1747
Adding a node selector which will allow preventing SNR daemonset to run on a specific node.
This functionality is required for use cases where we would like to disable SNR (for example Node maintenance).

/test ?

/test 4.12-openshift-e2e

/lgtm
Giving others a chance to review as well, feel free to unhold
/hold

/retest


Generate row frames with columns in Window Fuzzer

WindowFuzzer now generate k-rows frames with column boundaries, e.g., ROWS BETWEEN c1 PRECEDING AND c2 FOLLOWING.
These frames are supported in the Window operators, so extension of WindowFuzzer to cover them was added in too.

@kagamiori : PTAL.

The "Presto Fuzzer" job failure was caused by this issue: https://github.com/facebookincubator/velox/issues/10740.
The failed unit test in "Linux Build / Ubuntu debug with resolve_dependency" was not caused by this change.


When rebuilding stanc3 from source, main.o is rebuilt unnecessarily

Description:
When using stanc3 built from source with cmdstan (STANC3=path/to/stanc3 in make/local), every time there is a change in the stanc3 compiler, main.o is recompiled.
This only affects developers not the users but it is unnecessary.
Current Version:
v2.23.0

good catch!

Cant replicate anymore. Closing.


Fix typo in german translation

This just fixes a small typo in the newly added option to ignore HTTP-cache when fetching feeds.
Seems as if dutch was used by accident.

Can you please regenerate the bundled file as well? (run go generate)


add web2 suite and fix web2 on all platforms

First off: thank you for this amazing cookbook, it's been a great help to us!
This pull request will:

add a test suite for icingaweb2
add debian wheezy as a platform to test
fix some quirks I had with setting up icingaweb2 on the given platforms (ran into some problems on debian and ubuntu with apt keys, mismatching versions, missing nagios user, ...)

More details in the separate commits. Let me know if I need to change anything.
ps: I tried creating an account on https://accounts.icinga.org to open a bug issue (as directed in README.md) but I never received the e-mail with validation code. I tried with 2 different mail addresses and tried revalidating both (accounts named Zhann and Zhann_) but no luck. So my apologies for the direct pull request.
EDIT: Issue #9257

Please get in touch at<EMAIL_ADDRESS>providing details on your username / email address. I'm sure we'll find a solution.

@dnsmichi finally received the mail after some delay. I edited my original comment with a link to the corresponding issue.

@Zhann :+1:  thanks for your contribution!


Include distributed tracing

Include guidance on not insalling all instrumentation, only those you actually use

Discussed in last Ref Arch meeting, no concerns expressed. Landing


Content negotiation and response validation assumes incorrect schema for validation

Description
In an API written in OAS v3 (which supports content negotiation), when an operation has two different response mimetypes and one of them is not json-compatible, the validation assumes application/json. This entails some errors on the validation.
Expected behaviour
The validation should honor the API specification and use the schema of the associated content type. One should be able to have an operation that can respond application/json and application/octet-stream according to the Accept header.
Actual behaviour
When the operation initializes its mimetype and finds that the operation can produce more than one type, it assumes that it is application/json. However, if the implementation's response is not json or does, the validation will fail.
Steps to reproduce

Create an API with an operation that can respond two different content types where one of the types is not json-compatible, like application/json and application/content-type. For example:

---
openapi: 3.0.2
info:
  title: example
  description: example
  version: 0.0.1
paths:
  /api/files/{id}:
    parameters:
      - name: id
        in: path
        description: File identifier
        required: true
        schema:
          type: string
    get:
      summary: Fetch file metadata or contents
      description: ...
      operationId: app.api.files.get
      responses:
        '200':
          description: File contents or metadata
          content:
            application/json:
              schema:
                type: object
            application/octet-stream:
              schema:
                type: string
                format: binary

Implement the operation while honoring the Accept header. For example:

import os

from flask import request, send_file

def get(*, id):
    # Content negotiation
    best = request.accept_mimetypes.best_match(['application/json',
                                                'application/octet-stream'],
                                               default=None)
    if best == 'application/json':
        return {'id': id, 'metadata': {'key': 'value'}}, 200

    elif best == 'application/octet-stream':
        tmp_file = tempfile.NamedTemporaryFile(mode='w+b')
        tmp_file.write(os.urandom(32)) # 32 random bytes
        tmp_file.flush()
        tmp_file.seek(0)

        response = send_file(tmp_file, mimetype='application/octet-stream')
        response.direct_passthrough = False
        return response, 200

Run connexion with response validation enabled.

Request the operation from a client using the Accept header to request
application/octet-stream. In the example above, it will fail with a
UnicodeDecodeError: 'utf-8' codec can't decode byte while trying to
interpret the binary contents as json.

Additional info:
After some analysis, I have identified some potential sources that produce this behavior.
First, it seems that
connexion.operations.abstract.AbstrsactOperation.get_mimetype incorrectly
assumes that the mimetype is application/json when the operation does not
produce json for all its responses (according to connexion.utils.all_json.
This makes the ResponseValidator have an incorrect mimetype field. Then,
ResponseValidator.is_json_Schema_compatible is confused by this and eventually
the ResponseValidator.validate_response calls json.loads, which fails and it
is interpreted as a validation error.
Output of the commands:

python --version
Python 3.7.1

pip show connexion | grep "^Version\:"
Version: 2.2.0

Thanks @dojeda  - I'm working on adding handlers by content-type here: #760
Please take a look - It should enable working with octet-streams, and adding custom validation for various content-types.

Thanks for the pointer, I'll take a look to that branch this week.

Fixed since https://github.com/spec-first/connexion/pull/1591


tokio 1.0 support

Looks like tokio 1.0 is out. Not sure yet about 0.3 compatibility, but might be time to add support.

I want to get #94 in before I release 0.7.

It's done.


MintME coin wallet issues

I get this error when transferring MintME coin out to another wallet.
ERROR: An unexpected error has occurred. Please restart & update MintMe Coin wallet.
The error was: Invalid data format: Missing passphrase
What can I do??

You simply need to retry to proceed with your transfer or restart your wallet.


update screenshots on devtools homepage

Just replacing the slightly old screenshots with fresh ones. This should be good to go.

Build fail probably related to the DNS attack:
$ git fetch --no-tags --depth=1 origin +refs/pull/3758/merge:
fatal: unable to access 'https://github.com/google/WebFundamentals.git/': Couldn't resolve host 'github.com'
[info] build failed (exit code 1)

Yah, not too worried about the build failing right now. It looks like you changed a bunch of images out and added new ones, did you delete the old ones if they're not being used?

Old screenshots have now been deleted.

STOP YOUR SPAM!!!!!!!!!!!!!!!!
2016-10-21 16:06 GMT-04:00 Pete LePage<EMAIL_ADDRESS>
Yah, not too worried about the build failing right now. It looks like you
changed a bunch of images out and added new ones, did you delete the old
ones if they're not being used?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/WebFundamentals/pull/3758#issuecomment-255453277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqo0tn-xQiOf7YRGoxuacwb6PcAroiPks5q2RtLgaJpZM4KdiCk
.

STOP YOUR SPAM!!!!!!!!!!!!!!!!
2016-10-21 16:54 GMT-04:00 Kayce Basques<EMAIL_ADDRESS>
Old screenshots have now been deleted.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/WebFundamentals/pull/3758#issuecomment-255462739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqo0t2NyrHRhwxmXU4jxXyEWKwzC0B2ks5q2SaTgaJpZM4KdiCk
.


Incomplete translation on page 404

The phrase is not translated on page 404.
Highlighted in red on the screenshot.

Thanks for reporting @Statium but this is just something that will generally occur as changes are made in the project. We generally do not delay releases for translations to catch-up, otherwise it gets hard-to-manage and can cause a knock-on delay effect.
Thank you though for offering the RU translations very quick, They will likely be part of the next release, or a sooner patch.


small issue downloading the .net runtime

when the runtime is not found the link to download it points to the .net runtime when it really needs the asp.net core runtime and desktop runtime.
I installed booth then it worked. thanks.

Hello and welcome!
The plan down the road is to eventually have a full fledged installer that will fetch the appropriate package, as well as fixing the old link for the guys who hate installers. We will get there someday!


Article is Get out of post target because date condition unit is per day

Maybe cannot specify to created hour,minute level.
So, we must add filter logic after query successed.

No problem


Update the activity starter documentation

Update this to mach the component upgrade to permit more keys, and make additional examples.

Documentation updated.


[branch-2.0][improvement](jdbc catalog) Change JdbcExecutor's error reporting from UDF to JDBC

Proposed changes
pick #35692
In the initial version, JdbcExecutor directly used UdfRuntimeException, which could lead to misunderstanding of the exception. Therefore, I created a separate Exception for JdbcExecutor to help us view the exception more clearly.

run buildall

run buildall


Required ruby version >= 2.1.0

Once this gem use required keyword arguments it doesn't work with ruby < 2.1.

Sorry that I took so long to answer!
I'm only using keyword arguments for the client initialization. I don't mind removing it, if it would help  you.

If you want provide ruby 2.0.0 compatibility, you only need to pass default values on those keyword arguments.
But once keyword arguments are supported with default values in ruby > 2.0.0 and with no default values in 2.1.0, you should always include this in .gemspec
spec.required_ruby_version = '>= 2.0.0'
This away you avoid someone with  ruby < 2.0.0 || < 2.1.0 installing the gem successfully.

I added compatibility for ruby 2.0 and set the required ruby version in 63b39bb9b94c990dfa55c2fe65b5e936d59dfa9d.


Admin Functionality

Brother project looks great but when i am logging into app as admin i dont get feature like add product or etc whats the problem here can you help me.

This project is no more supported.


Not so much a bug, but getting bash: sudo: command not found in azure cloud shell bash

working on this page.
https://azurearcjumpstart.io/azure_arc_jumpstart/azure_arc_k8s/aks/aks_terraform/
Describe the bug.
in the "Connecting to azure arc" section, uploading bash file to azure cloud shell.
when running the file, getting bash: sudo: command not found
searched the web on this error, and pretty much what I'm seeing is If the script is run in the user home directory, it should work.
the script is in my home dir;  I've even reset my cloud shell account (creating new storage account /etc)
NOTE:  I'm doing this is azure gov cloud. however, I've tried the same steps in my commercial sub with the same error

@jwaltireland can you please share a screenshot?

I tried to use that script.  i've abandoned trying to get that script to work in azure cloud shell.  just used this page's info and got it connected to arc:
https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/quickstart-connect-cluster?tabs=azure-cli

@jwaltireland : I did run a deployment now and it completed without any errors.
Based on your error message, looks like you executed another script.


Suggestions:  https://www.techpowerup.com/nvcleanstall/

https://www.techpowerup.com/nvcleanstall/
also enable tweaks of MSI-X and HDMI audio  timeout.

Is there any benchmarks of nvcleanstall which demonstrate notable change against regular install?


Added RBAC filtering middleware to keystone-paste.ini.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

:+1: Okay to merge when tests pass.

ok to test


Feature Request - Custom DNS Settings

Please add a feature to add our own custom DNS-over-HTTPS on the settings in addition of the current options.
Screenshot
https://i.imgur.com/4y03ckH.jpg

https://github.com/aniyomiorg/aniyomi/issues/612


Added marshalling to main thread messages sent from native side

This commit adds marshalling of messages sent from native side to be executed on main thread

Thank you for this PR, @Kofhein.
Could you please update AUTHORS too? Also, it's unclear whether we can contribute this software to flutter/engine, but do you agree to delegate all rights related to this PR to Sony?

@HidenoriMatsubayashi , AUTHORS updated, yes, I agree

Thank you, Kofhein.


moto.dynamodb2.update_item fails when an attribute name in ConditionExpression contains .

How to reproduce the issue?
Call .update_item() with a ConditionExpression that references an ExpressionAttributeName containing dots. Working unittest example below. The #second =<EMAIL_ADDRESS>causes the condition_op here to fail. I've confirmed this works against AWS Dynamo.
import unittest
import boto3
from moto import mock_dynamodb2

def conditionally_remove_nested_attribute(table, record_id, email_like_str):
    table.update_item(
        Key={"id": record_id},
        UpdateExpression="REMOVE #first.#second, #other",
        ExpressionAttributeNames={
            "#first": "first",
            "#second": email_like_str,
            "#third": "third",
            "#other": "other"
        },
        ExpressionAttributeValues={":value": "VALUE", ":one": 1},
        ConditionExpression="size(#first.#second.#third) = :one AND contains(#first.#second.#third, :value)",
        ReturnValues="ALL_NEW",
    )

class TestDynamoCondition(unittest.TestCase):
    @mock_dynamodb2
    def test_conditionally_remove_nested_attribute(self):
        dynamodb = boto3.resource("dynamodb", region_name="us-east-2")
        table_name = "Test"
        dynamodb.create_table(
            TableName=table_name,
            KeySchema=[{"AttributeName": "id", "KeyType": "HASH"}],
            AttributeDefinitions=[{"AttributeName": "id", "AttributeType": "S"}],
        )
        table = dynamodb.Table(table_name)

        email_like_str =<EMAIL_ADDRESS>        record = {
            "id": "key-0",
            "first": {
                email_like_str: {"third": {"VALUE"}},
            },
        }
        table.put_item(Item=record)

        expected = {
            "id": "key-0",
            "first": {},
        }
        conditionally_remove_nested_attribute(table, "key-0", email_like_str)

        assert table.get_item(Key={"id": "key-0"})["Item"] == expected

if __name__ == "__main__":
    unittest.main()

Expected
.update_item() parses the attribute references split by #, such that when {"#second"<EMAIL_ADDRESS>expression parsing does not split the .com from the string and cause the attribute to not be found.
Actual
botocore.errorfactory.ConditionalCheckFailedException: An error occurred (ConditionalCheckFailedException) when calling the UpdateItem operation: A condition specified in the operation could not be evaluated. is raised due to parsing failure caused by splitting nested attributes on .
Version
❯ pip show moto
Name: moto
Version: 2.2.6

❯ pip show botocore
Name: botocore
Version: 1.21.37

❯ pip show boto3
Name: boto3
Version: 1.18.37

Hi @jgoist-ff, welcome to Moto! Thanks for raising this issue and for providing a reproducible test case - that's much appreciated.


With the fastest CPU in the world, one plot takes 2 hours to finish

I'm using AMD EPYC 7H12 64-Core 2.60Ghz, Here are some results with different thread settings for a single plot to finish:
System is Windows Server 2019, Ram is 1TB, first hard drives is latest Intel NVME enterprise 3.84TB, second drive is set with 120GB RAM disk. (four exact same systems)
-r 4, takes 3 hours, CPU usage is about 2%
-r 6, takes 2 hours, CPU usage is about 3%
-r 8, takes 1.5 hours, CPU usage is about 3%
-r 10, takes 1.2 hours, CPU usage is about 4%
-r 12, takes 1.5 hours, CPU usage is about 5%
-r 32, takes 6-7 hours, CPU usage is about 30%, system becomes very slow on everything, include access any RAM or NVME drives even without any read or write.
-r 64, takes more than 12 hours, CPU usage is about 40%, system becomes very slow on everything, include access any RAM or NVME drives even without any read or write.
with -r 10, I run another instance of the plotter, the system becomes immediately very slow, even the CPU usage is less than 6%.
It seems the plotter is not compatible with such high end CPU, or the plotter has some serious flaws, so sadly surprising. With official Chia plotter, I can mange to plot around 64 plots per day with 6 NVME drives with this CPU. Anybody have this kind of experience? any help would be greatly appreciated.

Someone ran MadMax on a 192 cores/384 threads with success and posted the results on Youtube (~1 minute per plot). So I don't think the issue here is related to the plotter. There are some reports on slow plotting on Windows Server (#378, ... ).
My 6 core, 10 years old cpu with pcie 2.0 nvme and 16GB ram can make a plot in ~55 minutes using Mad Max on Ubuntu 21.04 (~ 7 Hours using official plotter). So try Ubuntu if you can. You can install it on USB flash drive without touching your Windows OS disk.

I've run the plotter on a 32C/64T Xeon system. The issue I had was if I ran it with -r 32 or -r 64, the CPU utilisation was only about 50-60%. This was because it was a dual socket system: to improve times, I ran one plotter on one CPU and one on the other CPU. I achieved this by using numactl, but that's a linux thing. It's possible you have the same problem because some Epyc chips use CCXs, which bundle 4 cores together in a compute unit. I don't have any experience with that particular CPU, but I can tell you that the plotter does scale with more cores - it should not take that long.

Someone ran MadMax on a 192 cores/384 threads with success and posted the results on Youtube (~1 minute per plot). So I don't think the issue here is related to the plotter. There are some reports on slow plotting on Windows Server (#378, ... ).
hi, my computer hardware is quite close to yours, i use Ubutun 20.04, however i can only get 2hours for one plot. can you please show your setup for plotting? including the ubutun disk and nvme formating setup. thx!

hi, my computer hardware is quite close to yours, i use Ubutun 20.04, however i can only get 2hours for one plot. can you please show your setup for plotting? including the ubutun disk and nvme formating setup. thx!
You can find it here:
https://github.com/madMAx43v3r/chia-plotter/discussions/452#discussioncomment-912683
OS is EXT4, Temp1/2 and D XFS with CRC off.

hi, my computer hardware is quite close to yours, i use Ubutun 20.04, however i can only get 2hours for one plot. can you please show your setup for plotting? including the ubutun disk and nvme formating setup. thx!

You can find it here:
#452 (comment)
OS disk FS is EXT4, Temp1/2 and D XFS with CRC off.

thx, how to turn off CRC In Ubuntu? I'm new to Linux.

mkfs.xfs -f -m crc=0 /dev/nvme0n1p1

thx, how to turn off CRC In Ubuntu? I'm new to Linux.

As far as I know, you can not just turn it off, you have to reformat the disk/nvme, the command provided by mcsham will do that for you. Be aware that it will format your drive without any confirmation. back up important data, then use that command.

In my testing on dual xeon system, crc had zero impact on performance, so no reason to disable it.

有人在 192 核/384 线程上成功运行了 MadMax，并将结果发布在 Youtube 上（每个图约 1 分钟）。所以我认为这里的问题与绘图仪无关。有一些关于 Windows Server 上缓慢绘图的报告（#378，...）。
我的 6 核、10 年老 cpu 和 pcie 2.0 nvme 和 16GB ram 可以在 55 分钟内使用 Ubuntu 21.04 上的 Mad Max（使用官方绘图仪 7 小时）绘制一个绘图。因此，如果可以，请尝试使用 Ubuntu。您可以将其安装在 USB 闪存驱动器上，而无需接触 Windows 操作系统磁盘。

please give me the lin,thanks

有人在 192 核/384 线程上成功运行了 MadMax，并将结果发布在 Youtube 上（每个图约 1 分钟）。所以我认为这里的问题与绘图仪无关。有一些关于 Windows Server 上缓慢绘图的报告（#378，...）。
我的 6 核、10 年老 cpu 和 pcie 2.0 nvme 和 16GB ram 可以在 55 分钟内使用 Ubuntu 21.04 上的 Mad Max（使用官方绘图仪 7 小时）绘制一个绘图。因此，如果可以，请尝试使用 Ubuntu。您可以将其安装在 USB 闪存驱动器上，而无需接触 Windows 操作系统磁盘。

please give me the link,thanks

https://www.youtube.com/watch?v=dQRBmKCDV7E


Cross to close windows not displayed under GNOME 3.1X

It looks like a Gnome "feature" :
https://stackoverflow.com/questions/8691025/qt-qdialog-and-gnome-3-how-to-display-the-close-button-title-bar-and-make-it-mo

I could not found anything in gconf-editor: Desktop > Gnome > Shell > Windows:

May be this could help:
http://blog.pitonyak.org/node/18

Yes I saw this hack, but its a very dirty one...
It's not a bug, it's a gnome 3 feature. :)


Footer block

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #6
Test URLs:

Before: https://main--walgreens--hlxsites.hlx.page/
After: https://footer-block--walgreens--hlxsites.hlx.page/

I've added a function in scripts that will update relative links.


fix assert in ObjTypeSpecFldInfo::GetFixedFieldIfAvailableAsFixedFunction

Assert isn't valid, as there isn't always a guarantee about equivalence. Instead, we should do a check in the API.

Do you have a test case for this?

Sure, I've added one.

We dont have polymorphic inlining for apply targets.
We collect fixed field info at workitem creation for polymorphic inlining only if the method properties are at equivalent slots in their owner object types.

By (2), the assert makes sense. We should, however, not call TryOptimizeCallInstrWithFixedMethod from InlineApplyWithoutArrayArgument if applyTargetInfo is null.

Makes sense. I'll make that change.