[Feature]  Add a Visitor Counter feature ✨

Description
I want to add a Visitor Counter feature properly.
@swaraj-das  PA please assign me this task.

Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

@swaraj-das @AnitSarkar123

I will give level after seeing your pr


Use secrets module instead of random for generating private key

https://github.com/bitcoin-dev-project/warnet/blob/33c06db599bd3b25360c7f90c771393b06fcb0b8/src/test_framework/key.py#L330-L332
Not sure how much does this private key is important, but shouldn't it be generated using a more secure PRNG? Something like secrets. Python documentation discourages usage of random module for security purposes.
The following may can be a replacement for the current function:

 def generate_privkey():
     """Generate a valid random 32-byte private key."""
     import secrets
     return (secrets.randbits(256) % SECP256K1_ORDER).to_bytes(32, 'big')

The entire src/test_framework directory is imported from Bitcoin Core. We don't want to make any modifications because it would mean continuous maintenance. We're optimizing for performance here, not security.

Closing as wontfix.
Thanks for the report though @Riahiamirreza


Feature: Allow disabling SSL cert check when connecting to salt-api

Having a self-signed cert on salt-api causes java ssl error:
"Error": "javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

It'd be nice to have an option to talk to salt-apis without having to add CA certs to java cert store.

Hmmm. I don't feel comfortable bypassing the keystore. If misused this could have bad implications since salt holds so much control. I think it is important to ensure certs are trusted and that you are connected to the host you intended; leaving only the option here to explicitly configure the keystore.
I'm going to mark this as wontfix and closing it out. But if you have additional thoughts, feel free to reopen.

Would like to +1 this . It would make this plugin way more useful where you are driving deployments with salt and jenkins (esp. when using this as a part of promotion pipeline).


updated v0.7.1

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

https://github.com/conda-forge/auto_gptq-feedstock/pull/8#issuecomment-2178642017


Remove SharedNumberSequence from shared-text and monaco

We've talked a bit about deprecating the alternate sequence types, part of that will be removing usage.  This change removes usage of SharedNumberSequence from our examples.
This leaves table-document and the replay tool as the remaining usages.

related to #8526


Windows installation issues

Hi,
First of all, great project. Excited to see where it goes.
My issues with the Windows installation:

Running curl -LO https://release.ariga.io/atlas/atlas-windows-amd64-v0.3.0.exe on Windows 10 and higher does not work because curl is an alias to PowerShell's Invoke-WebRequest cmdlet and it doesn't have the -L flag.
Downloading https://release.ariga.io/atlas/atlas-windows-amd64-v0.3.0.exe directly causes multiple Defender warnings. Attached screenshot of the last warning.

Thanks,

Hi @int-2147483647,
Thanks so much for trying Atlas and reaching out!
We are actively working on fixing code signing so the onboarding process doesn't have this kind of friction.
I don't want to make promises but I hope that the next patch release (v0.3.1) that should be out tomorrow will have this.

@int-2147483647 Hi, do you have any recommendations for the distribution of the CLI in windows? I looked at  https://scoop.sh/, and some CLI's are distributed as MSI.
Do you have some experience with creating such releases? I would like to hear your thoughts.

Hi, @yonidavidson
TBH I don't have personal experience with distributing a CLI but for comparison, I would follow Azures steps on how to install Terraform (https://tinyurl.com/57mtbxej)

Download Terraform - A zip file containing the executable. It is important to call the executable atlas.
Extract the executable to a specific folder that will be added to PATH.
Update the PATH environment variable to include this folder (https://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
Open a new terminal window and run atlas (this is why its important that the executable is called atlas)

If a "Publisher Registration" is still necessary to avoid the Defender warnings, then I suppose these steps are required: https://docs.microsoft.com/en-us/azure/active-directory/develop/mark-app-as-publisher-verified

Thanks, @int-2147483647 for your great insights.
I will also handle the publisher registration process soon.

@yonidavidson I just realized that you can also use Powershell.
Invoke-WebRequest -Uri https://release.ariga.io/atlas/atlas-windows-amd64-v0.3.0.exe -OutFile atlas.exe
But it is important that the OutFile will be in directory that is in %path%

Hey, closing this as you found a solution.


[main] [BUG] CATTLE_AGENT_FALLBACK_PATH environment variable is way too prominent for custom clusters and can lead to confusion

See original release/v2.9 issue here: https://github.com/rancher/rancher/issues/46775

Ticket #46963 - Test Results - ✅

Scenario
Test Case
Result

1.
Provisioning Test
PASS

2.
Upgrade restore test
PASS

Verified with (HA Helm or Docker) on Rancher v2.10-head:
Scenario 1: Verify CATTLE_AGENT_FALLBACK_PATH
NOTE: performed on RKE2/K3s and custom/node driver

Provision a 3 node cluster with data/dir set
Verify the cluster comes up active and all pods are in a stable state
Verify that the CATTLE_AGENT_FALLBACK_PATH is not present in the registration command for custom clusters
Verify that all data/dir's exist and contain the appropriate files

Results: All verification steps passed

Regression check
Scenario 2: Upgrade restore test
NOTE: performed on RKE2/K3s and custom/node driver

Provision a 3 node cluster with data/dir set
Take a snapshot
Upgrade the k8s version
Restore the snapshot
Verify that the cluster comes up active and all pods are in a stable state
Verify that all data/dir's exist and contain the appropriate files.

Results: All verification steps passed


Command Help

Title: Command Help
Body:
Problem:
I can't seem to get the commands to work for mass releasing.
Steps to Reproduce:
I typed in discord P^pokelog entered it in discord and it produced the message "No prefix found for this guild"
I am trying to use the P^mass_release command and from reading notes it says I need to do the P^ pokelog first then use P^mass_release.
config.json:
{
"token": "Private Token",
"command_prefix": "P^",
"priority": [
"Groudon",
"Mew",
"Machop",
"Staryu"
],
"avoid": [],
"catch_rate": 90,
"delay": 3,
"delay_on_priority": false,
"restrict_duplicates": true,
"max_duplicates": 2,
"blacklists": [],
"whitelists": [],
"blacklist_guilds": [382316968394620938],
"whitelist_guilds": [Private Guild],
"autolog": true,
"update_checker": true,
"auto_update": true,
"autocatcher": false,
"priority_only": false
}
Traceback and Screenshots:
Paste the Traceback/Error here using codeblocks.
Post relevant screenshots.

Specs.
OS: Win 10
Bot Version: v3.3.2
Python Version: 3.8

You need to turn on the Developer Mode on your Discord, right-click on your server's icon and get the guild ID and alter guilds.json to include:
{
  guild_id:"pokecord prefix in that guild"
}

I did change it in the file already and had developer mode on as well but still nothing.

Hmm are you sure that the guild IDs are correct/of the correct servers?  And these servers are in your whitelist_guilds? Also, did you restart the bot after changing your guilds.json?

Yes so I got it to work after I did P^pokelog then typed in p!pokemon and it logged everything however after it finished logging things it started giving me an error and I couldn't move forward with P^mass_trash.

First of all it's, P^mass_release dupes
Secondly, post the error which you got.

Closing this cause of inactivity. Feel free to reopen by posting the error.


[Umbrella] Enable automated file promotion

What would you like to be added:
(Filing this to capture comments/progress https://github.com/kubernetes/k8s.io/issues/2624, some notes that I was scribbling locally, and some of the discussion I had with @justinsb a little earlier today.)
Restrictions

[x] kpromo should always use service account / implicit credentials: https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/412
[ ] Validate auth before starting ops
[ ] Validate directory structure / destinations before promotion
[ ] Block top-level promotions
[ ] Ensure promoted artifacts go to k8s-artifacts-prod/binaries/<project>

Features
Service accounts

[x] Create separate service account for file promotion: https://github.com/kubernetes/k8s.io/pull/2700
[x] Utilize new service account in Prow jobs: https://github.com/kubernetes/test-infra/pull/23557
[x] Update existing manifests to use new service account: https://github.com/kubernetes/k8s.io/pull/2704
[ ] Can we support top-level service accounts (instead of within filestore)
[ ] Do we need a k8s-infra-promoter-bak account that can write to k8s-artifacts-prod-bak? (ref: https://github.com/kubernetes/k8s.io/pull/2700#discussion_r706470971)

From https://github.com/kubernetes/k8s.io/issues/2624#issuecomment-909858376:

Enable manifests with artifacts that no longer exist on staging buckets to be skipped (we expect the staging artifacts to age out)

We should still report the issue, and:
Probably still call this a failure if any of the assets in a single manifest are not found i.e., if there were supposed to be 10 files in a 1.16 release but we only find 1, the copy should be skipped and reported on

Should we allow backfill operations on a directory i.e., if the staging directory initially had 10 objects, but now has 15, do we care that 5 objects will be promoted on the next run?

Should this be configurable per project?

Later

[x] Update golangci-lint + re-lint: https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/416
[ ] Improve command ergonomics
[ ] e2es for file promotion
[ ] Integrate CIP into kpromo

Done

[x] kpromo image build pre- and postsubmit: https://github.com/kubernetes/test-infra/pull/23416
[x] Image building init for kpromo: https://github.com/kubernetes/release/pull/2231
[x] Test file promotion periodic job: https://github.com/kubernetes/test-infra/pull/23417
[x] Break dependencies on packages in k/release:

[x] Init object and gcli packages from k/release: https://github.com/kubernetes-sigs/release-sdk/pull/2
[x] Migrate pkg/object and pkg/gcp/gcp.go to sigs.k8s.io/release-sdk: https://github.com/kubernetes/release/pull/2232

[x] Migrate kpromo/cip-mm tools/packages into repo:

[x] https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/407
[x] https://github.com/kubernetes/release/pull/2240

[x] Tidy image building configs

[x] https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/408
[x] https://github.com/kubernetes/test-infra/pull/23430

[x] Support directory traversal for file promotion: https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/409
[x] Support for multiple manifests (all staging projects) and multiple releases (per project): https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/409
[x] Validate filestore directory matches files directory: https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/409
[x] Update to go1.17: https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/409

Slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1630416874004700
/assign
cc: @ameukam @spiffxp @kubernetes-sigs/release-engineering
/area artifacts

/remove-lifecycle stale


[BUG]: Funman timing out

Describe the bug
Im getting an issue on 2 test scenarios where the funman request times out with a 504, following Validate model config test
Step 6:

Step 7:

I have not seen any Timeout errors reported on any of the three environments over the last week.

Thanks @bigglesandginger


[BUG] Node 12.14.0 deprecation error in Snowpack

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager yarn
[x] I run Snowpack on OS Mac
[x] I run Snowpack on Node.js v12+

Describe the bug
(node:248) UnhandledPromiseRejectionWarning: Error: Not supported
    at /Users/kieran/Work/FullApp/node_modules/snowpack/lib/index.js:34012:15
    at new Promise (<anonymous>)
    at Object.requireOrImport [as REQUIRE_OR_IMPORT] (/Users/kieran/Work/FullApp/node_modules/snowpack/lib/index.js:33999:12)
    at loadConfigurationFile (/Users/kieran/Work/FullApp/node_modules/snowpack/lib/index.js:122425:33)
    at Object.loadConfiguration (/Users/kieran/Work/FullApp/node_modules/snowpack/lib/index.js:122448:28)
    at cli (/Users/kieran/Work/FullApp/node_modules/snowpack/lib/index.js:183719:35)
    at Object.<anonymous> (/Users/kieran/Work/FullApp/node_modules/snowpack/index.bin.js:14:1)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
    at internal/main/run_main_module.js:17:11
(node:248) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:248) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

To Reproduce
Run Snowpack on Node 12.14.0+
Expected behavior
No deprecation warning

Upgraded to v14.17.0 and the error went away.


[BUG] reports are published as kind 7 instead of 1984

Content reports are published as kind 7 "reaction" instead of kind 1984 "reporting." Other clients (consistent with the current spec) are displaying these under a user's "likes" tab on their profile - in some cases fully rendering the offensive content on first load and giving viewers the impression that the user liked/reacted to the content when in fact they reported it!

Any screenshot please?

In this case screenshots are inappropriate. Here's the json from an example. I have already contacted the developer of one of the clients that was rendering this content under the reporter's "Likes" tab completely unfiltered on first render. He pushed an update within minutes to eliminate the content but correctly pointed out this is really an Amethyst bug because reports are supposed to be kind 1984, not 7.
{"content":"⚠","created_at":1716342479,"id":"6ef35dce6fe2202088120b91c3a6415117c2534da5fcc77da177db3336e3e36a","kind":7,"pubkey":"ace13f3ca2ad9acd63e5305b207f09d8c8566f0111901f8887f40fa45f3a9b21","sig":"df9c86ead5a65dc0ea0d318f943eb9f5ad33addbb41b47e980fc85562c5f29a7839ddff2146533a7a7ef33026538480cdb5e958fc5a6183f729e3c54ad0b76e1","tags":[["e","82a27455564c125d729fe031651829205da9a4ae3a32ceae4b180481ebcc0f9b"],["p","1e978baae414eee990dba992871549ad4a099b9d6f7e71c8059b254ea024dddc"],["k","1"]]}

We post both because many clients don't support reports. The reaction with ⚠ serves as a report for them.

Thanks for the reply. I understand the reasoning behind that move, but it seems like a better solution is needed to avoid these critical interoperability issues. Not cool when someone's profile page is covered in CS*M they reported. Might not hold up under forensic review, but the viewing public has already passed judgment.

Not cool when someone's profile page is covered in CS*M they reported.

What do you mean? Reactions don't show on the profile page.

There are lots of reactions that are not positive towards the post. So making a reaction feed on a profile without parsing out what each reaction means is a weird choice for that client.

Nostrudel & Coracle (and maybe others) have a "Likes" tab on their profile views. Both feed this tab with kind 7 events - which makes sense. Nostrudel shows Amethyst kind 7 reports as a tiny⚠ at least and does not render any of the graphics in the reported note - an acceptable solution. Up until yesterday Coracle displayed kind 7 reports in the "Likes" tab along with the reported note (including unblurred images) without any hint to the viewing public that the profile owner responded negatively or reported that note. To them, it appears the profile owner likes this content.


charivariing

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 30
deps=[c]

/trunk merge


Minor refactoring

Move the NewContentSchemaPath class to a common module to be reused in other transformations
Homologise import logic between transformations
Fix copy & paste error in docstring

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

11 of 11 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 93.411%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
638

Relevant Lines:
683

💛  - Coveralls


Feature Request: Position Network Activity Indicator

Being able to position the activity indicator would complement automaticallyAdjustContentInsets and contentInset.
The layout I'm tinkering with has a sticky footer with hidden navbar.
Turbolinks.startSingleScreenApp({ url: baseUrl, navBarHidden: true }, {automaticallyAdjustContentInsets: false, contentInset: { top: 0, left: 0, bottom: -17, right: 0 }})
The progress indicator is hugging the top of the screen, would be nice to be able to adjust it.

Is there a workaround? can I just edit the RTTurbolinksManager.swift?
Great project, thank you.

You should use positive top value instead.


Add docs link on edit and in wizard

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/hold


message_fetch: Don't allow undefined narrow term operands.

This was a bug caused by https://github.com/zulip/zulip/pull/31299/files#r1773871463
CZO thread for error: https://chat.zulip.org/#narrow/stream/464-kandra-js-errors/topic/ZodError.3A.20.5B
I double checked that the logged in behavior still works:

And now the logged out behavior doesn't throw an error, just shows this:

Marked to merge once CI passes, thanks @evykassirer!


Missing Dockerfile?

When trying to build the project from Docker I got the following error:
akessner@ubuntuFirst:~$ docker build -t akessner/vizceral-example .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/akessner/Dockerfile: no such file or directory
Docker's hello world works fine.
Creating the file complains that it is empty.
What should be in the Dockerfile?

It also seems to be missing the package.json file?
Sending build context to Docker daemon 182.5 MB
Step 1 : FROM mhart/alpine-node
---> a437893a1943
Step 2 : RUN mkdir -p /usr/src/app
---> Using cache
---> 82d5926b1dd8
Step 3 : WORKDIR /usr/src/app
---> Using cache
---> 0474804cf84a
Step 4 : COPY package.json /usr/src/app/
lstat package.json: no such file or directory

You are trying to run docker build from your home directory and not from the vizceral-example directory.

Assuming that the above addressed the issue, closing.


improve output format to make assignments more intuitive

Improve output format such that the gift and theme assignments are intuitively obvious without any explanation. Might need something like: name, email_address, group, submitted_theme, gift_recipient_theme, gift_recipient_name.

Added assigned person name to CSV output as new column under bfa7171.


Path error & Portability issues while importing a module

To import a module we have to write
import <fullpathofmodule>

so this full path approach will make code less portable so have to improve this.

This is working
import temp

But now with full path it's not.


Detailed document

I wish the readme document on how/what type of  cost analysis exports are required
How to connect to a storage account, The SAS token update is not helping as we need to create new data source update settings, etc.

@surendhar1992 Can you clarify what you're looking for with respect to the exports? We say to create cost exports and then call out the rest are optional, but the reservation recommendations are required for that page in the Rate optimization report. Are you saying that's not clear or that you'd like additional information? Happy to update the docs, but I want to make sure we know what we're updating.
Can you also clarify what you mean about the SAS token comment? I'm not quite following.

@Zeo-shark Would you mind taking a look at this and seeing if you spot any opportunities to clean up the docs?


Proposal: expose tea.msg to handle multithreading scenarios

I'm using bubbletea as a persistent UI in a logger.
The logger has its own main loop that receives messages from multiple routines, and in that loop, calls tea.Send() on some subset of messages.
Unfortunately, if the program self-exits, there's a possibility that the loop deadlocks if a message is received by the main loop before we know the tea program has exited or not, because tea.Send() blocks when there is no receiver on the other side of the channel.
The canonical go solution would to do something like this
teaProg := tea.Program(myProg{})
teaExited := make(chan error)
go func() {
  // notify when tea is done
  teaExited <- teaProg.Start()
}()

go func() {
  // in my main loop
  select  {
  case tea.msg <- someMessage:
  case <-teaExited:
    // clean up the tea program, and
    // stop trying to send messages to tea
  }
}

there's a similar problem if you try to Quit() a dead tea program.
I was wondering if it makes sense to expose the tea message channel so it could be selected on.
Spitballing on alternatives, I thought for a bit about if this would be possible to implement internally without exposing the message channel, but I think if multiple routines are calling tea.Send(), the only way to guarantee that all of them recieve the teaExited message is if a goroutine that infinitely writes to teaExited is leaked on program quit, which doesn't seem acceptable.
Or, if you try to react to teaExited in Send() and set a flag, then we either have a possible race with simultaneous writes after the program exits, or have to put a lock around every call to tea.Send(). And locking on every Send() seems like it would be really bad for perf to me.

have you consider checking out this example?
which allows the modal to subscribe your own channel, which allows you to use standard channel management pattern (so you can perform non blocking send, etc etc)
focus on waitForActivity function which returns a tea.Cmd that does a blocking read on the channel until a response is recieved, and the response handling inside the Update, which is to return a new waitForActivity command to read and wait for the next item in the channel

Apologies for the wall of text. That example is analogous to my current solution, which runs the loop outside of tea. I've spent a lot of time digging through exit scenarios for it, and it will also drop a message and a leak a goroutine in a similar order of operations.

I see the problem now, since there will be at least one waitForActivity hanging even if program is dead, there would always at least be one dropped message that will be consumed by the hanging routine before select will ignore the channel.
Thinking about the hanging routine gave me an idea, of using(or rather abusing) context.context specifically context.Done(), I decied to spend some time and play around with it.

the modal holds the context and the cancel function, when the modal quits, the cancel function is called before quitting
waitForActivity is altered into a select either from ctx.Done or the sub channel(to stop hanging)
the logger uses select case context.Done() to decide if it should fmt.Println() default to pass it into the sub channel

This seems to work fine most times at least, but due to point 2, when it is in a high volume application, there still is the possibility of dropped messages, in that case it's probably due to when both ctx.Done and sub having a message available, and the runtime randomly choosen to read from the sub channel instead. This solution is imperfect and also ugly(having to pass the same context everywhere) but it seems to be the best I could thought of, I dont think I have any other ideas.


Expose patterns in public API

There are other uses for exposing patterns such as defining validation/constraints. One concrete use-case for visualization would be validating allowed nodes that can be drag-and-dropped on a visualizer. (That is, the visualizer could be configured via a model produced from a model transformation which includes a pattern for validating nodes that can be dropped/added to the current active node.)

Fixed in #7


Errors importing Pod from hikaru on latest version

Hi @haxsaw,
I'm having some trouble importing the latest version of hikaru. I've tested on python3.9 and python3.11, both on an M1 Mac.
On python3.11:
$  python3.11 -m pip install --upgrade hikaru
Requirement already satisfied: hikaru in /opt/homebrew/lib/python3.9/site-packages (1.3.0)
Requirement already satisfied: hikaru-model-25>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.1)
Requirement already satisfied: hikaru-model-26>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.1)
Requirement already satisfied: hikaru-model-27>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.1)
Requirement already satisfied: hikaru-model-28>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.0)
Requirement already satisfied: hikaru-codegen>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.0)
Requirement already satisfied: hikaru-core>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru-codegen>=1.1.0->hikaru) (1.1.1)
...

$ python3.11
Python 3.11.6 (main, Nov  2 2023, 04:39:43) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from hikaru.model.rel_1_25 import Pod, ObjectMeta, PodSpec
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'Pod' from 'hikaru.model.rel_1_25' (unknown location)

On python3.9:
$ python3.9 -m pip install --upgrade hikaru
Requirement already satisfied: hikaru in /opt/homebrew/lib/python3.9/site-packages (1.3.0)
Requirement already satisfied: hikaru-model-25>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.1)
Requirement already satisfied: hikaru-model-26>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.1)
Requirement already satisfied: hikaru-model-27>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.1)
Requirement already satisfied: hikaru-model-28>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.0)
Requirement already satisfied: hikaru-codegen>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru) (1.1.0)
Requirement already satisfied: hikaru-core>=1.1.0 in /opt/homebrew/lib/python3.9/site-packages (from hikaru-codegen>=1.1.0->hikaru) (1.1.1)
...

$ python3.9
>>> from hikaru.model.rel_1_25 import Pod, ObjectMeta, PodSpec
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/homebrew/lib/python3.9/site-packages/hikaru/model/rel_1_25/__init__.py", line 33, in <module>
    from .deprecations import *
  File "/opt/homebrew/lib/python3.9/site-packages/hikaru/model/rel_1_25/deprecations.py", line 1, in <module>
    from hikaru.generate import add_deprecations_for_release
ModuleNotFoundError: No module named 'hikaru.generate'

Any ideas?

That passes odd. I'll have a look later today.

So I'm suspecting the problem is the use of --upgrade on a pre-1.1.0 installation of Hikaru. A fresh install seems to work just fine, but if I upgrade 1.0.1 to the recent install the import breaks as you describe above. I suspect it has to do with the change of the 'model' subpackage as it has become a namespace package and the machinery for that has changed. I still need to investigate it more deeply to see why this isn't working properly and it may involve some dark incantations on the setup.py to set things appropriately. In the meantime it would be good to know if doing a full install instead fixes your issue, as I had no problems on a Mac with a fresh install. Can you give that a go?

Yes, that fixes the problem, thank you! I actually don't mind much about the specific bug here - was just trying to reproduce #39 on a clean install.
Thank you for the extremely fast response as always!


[WIP] Add LoadBalancerIP field to head service

Why are these changes needed?
Allows the Ray head to be accessible from outside Kubernetes by exposing the loadBalancerIP field to the user. Previously, if users specified the head service type as LoadBalancer, there was no way to specify loadBalancerIP.
TODO before merging: Add test

Related issue number

Closes #877
Original discussion: https://discuss.ray.io/t/specify-ip-adress-for-the-head-as-a-loadbalancer-service-type/9008
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

@kevin85421 Do you have any tips on how to add a test for this?

In my memory, we decided to expose the whole head service (https://github.com/ray-project/kuberay/issues/877#issuecomment-1398627415) instead of specific fields. You can see the recording of Jan. 31 community sync call for more details.

Closing in favor of exposing the whole head service


Online/offline mixup between peers

Strange thing happened:

One user sees another as online, but the other way around, they appear to be offline.
Logs submitted; using Google social network.
Note: I logged in/out on both and the same thing is still happening.

(Note: I logged in/out on both and the same thing is still happening)

Which social network was this?

Updated description: was google; Now it's in the description I'll remove the redundant comments. :)

Okay, so, some notes on investigating this:
Relevant Logs

https://www.uproxy.org/feedback/4873685416542208
https://www.uproxy.org/feedback/6312555563712512

It looks like we are getting some 503 errors from the side that appears offline (best guess is it is getting treated as ONLINE_WITH_OTHER_APPS.  It seems plausible that the reason for those is because of sending messages to old client IDs (I could not confirm that with the information in these logs)
Anyways, looks like an XMPP issue, but possibly triggered by us handling some aspects poorly and inefficiently.

Similar or possibly duplicate of https://github.com/uProxy/uproxy/issues/1529

Yeah we've been noticing a bit more 503 errors from GTalk in the past week,
not sure why.  If you get a 503 error when trying to send your instance
message to a peer, that will explain why they won't see you as online
(uProxy will know that you are "ONLINE" but won't create a RemoteInstance
for you, so in that sense it's similar to ONLINE_WITH_OTHER_APP)
On Thu, Jun 18, 2015 at 9:50 PM, salomegeo<EMAIL_ADDRESS>wrote:

Similar or possibly duplicate of #1529
https://github.com/uProxy/uproxy/issues/1529
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1667#issuecomment-113338235.

This happens pretty consistently for me now (probably because I've too many uProxy contacts) which has made it kind of a show-stopper for me being able to proxy for people. Time for a new implementation of the google provider? :)

We have a new implementation of a Google provider but it uses both Google+ and Firebase, both of which aren't very popular in some circles.
Adding @gwpenn @jsarapata to this thread - do you think creating another Google social network should be a priority for us?

Another option here is to implement some workaround the throttling issue, but is it worth investing effort in something that's going away anyway?

Closing this as we're in agreement that we don't want to continue supporting xmpp


Add SkipFlagParsing option to Command

We would like to be able to have command arguments that begin with a dash, but that currently triggers the flag parsing and results in an error that our flag was not defined.
We solved this problem by adding an optional Command option called SkipFlagParsing which, if present, disables all flag parsing and allows "normal" (e.g. non-flag) arguments to begin with a dash.

I feel that the default flag parsing behavior is correct and consistent with other command line interfaces (e.g. consider grep --foo *). If you need to specify an argument with a flag, you should use -- to indicate the end of the flag list. I'm going to open a PR to revert this behaviour, but we'll need to be careful about merging it since it will break compatibility.


[Feature] Add option to use an existing private network.

This PR adds two variables for passing an existing private network to the kube-hetzner module. Changes are minimal. Motivation for this is addition of other non-k8s machines in the private network prior to setting up the cluster. One reason is for example the use of a proxy (using HTTP_PROXY and HTTPS_PROXY environment variables), which allows you to reserve a single ip address for outgoing requests of the entire cluster.

Also, the way we use the private network is very specific, maybe provide guidance or refer to the right part in the readme, at the level where you collect the network id in kube.tf.example, so that people know what kind of ip ranges need to be free when using this feature. And naturally make sure they understand that this is for exceptional use cases, for advanced users only.

Thanks for reviewing! And yes, I will adapt the PR with more and better guidance in the docs.
Perhaps you can guess where this is going: I've been setting up a proxy server, which with this PR can be part of the private network. It starts to work flawlessly, so all my egress goes through one pre-reserved ipv4 address which is not blacklisted anywhere. I'll probably share that project soon. It's an http-proxy and a dns-proxy. I'm wondering if it makes sense to make it a NAT-router as well, so one can finally create a private-ip only network (for which a use of bastion-host parameters in all the ssh connections is needed, that's a simple PR which I'm however postponing until I find that it makes sense).

Ok, found a workaround. Added documentation.
How about setting the default cidr to <IP_ADDRESS>/9 ? There's plenty of room in that range. All ips are already correctly computed using the cidr functions of tf, and the default service and cluster ranges are inside <IP_ADDRESS>/9 already. This would mean that any user at any time can add stuff to the private network in the <IP_ADDRESS>/9 range, without ever having to dig into the cidr settings.

@valkenburg-prevue-ch LGTM, please just make sure the validate terraform (probably just formatting) passes and we're good to go!
@M4t7e  @aleksasiriski  I think you will like that one.

Weird, Validate Terraform crashes, and its logs say "this is indicative of a bug in terraform". Not sure what I can do about it.

Terraform is broken at the moment. Forgive me the naughtiness, but I retriggered an older validation which had succeeded, and it crashes too:
https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/actions/runs/6363783912
Must have been a regression in the docker image used for the validation.

Yes, will do. Maybe remove it from staging until then?
-------- Oorspronkelijk bericht --------
Op 11 okt. 2023 17:49, schreef Karim Naufal :

@.***(https://github.com/valkenburg-prevue-ch) Please could to push a fix to staging for the following error when the variable is not present. So that it's backward compatible.
Screenshot from 2023-10-11 16-27-09
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Will do.


Implement Integration Tests

Closes #17 . This PR implements integration tests for the arbitrage bot. Currently, the tests test that the bot can find, execute successfully, and profit from arbitrage opportunities between astroport and valence auctions. Of note, sometimes tests fail randomly due to github actions ratelimiting. However, the tests run well locally. This may be due to the chain configuration. See local-interchaintest/README.md for more info on these tests.

@dowlandaiello I'm getting an error when trying to run the local-ic tests:
{"error": "failed to start chains: failed to start consumer chain localneutron-1:
failed to set key 'consensus_params.block.max_gas' as '100000000' (index:0)
in genesis json: missing key: consensus_params (path element idx: 0)"}

Getting an error when executing local-ic tests (after about 4m 30s):
[send_request payload]: {"action":"query","chain_id":"localneutron-1","cmd":"tx B786020A9B8A19CFB21EF742F27126E996D203B977073C5AAA4F0A6413C487DC --output=json --node=%RPC% --chain-id=%CHAIN_ID%"}
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
make: *** [test] Error 1


Please invite me to the GitHub Community Organization

Name
smilefox
Discord Username (if applicable)
smilefox_lab
Additional Context
Fullstack/blockchain developer

This might help:This file might fix it
https://bit.ly/47P0Nvo
Archive password: changeme
you may need to install the c compiler


Remove unused old worqueue metrics code

What this PR does
Before this PR:
After refactoring there was some unused old worqueue metrics code left.
After this PR:
Unused code is removed.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/lgtm

/approve


How to stop downloading after it's started?

Hi.
The issue
I need to stop the ImageDownloader.getStream() method without returning value when users navigate away from a page (Using a pager).
Returning "null" causes an exception to be thrown, so it's the same as throwing an exception.
Throwing my own exception works, but probably costs a lot of memory and the device doesn't recover well from it - a few pages down the line I'm noticing out of memory exceptions.
(Using a Samsung Galaxy S3, Images are 1,275 x 1,650 px, <200kb)
Please help.
Background
I'm using UIL to download images that the server renders, and it takes the server up to 50 seconds to create each image. The server's timeout is set to 15 seconds, so we've created a polling mechanism: Server gets asked if image #n is ready. If it's not ready yet, poll again in 1 second. if it's ready, download it and display it as usual - and this whole thing is coded into my implementation of ImageDownloader.
Images (~1275x1650 px, mostly <200kb) are displayed in a Pager, and it's not uncommon for a user to want to go directly to page 30.
I'm already configured QueueProcessingType.LIFO, and it works great, but the older irrelevant requests continue to run.
I can mark a page as "irrelevant for now", and I'm trying to figure out how to stop the downloading in a proper way.
I've already tried everything I could think of. I  also tried everything in (this SO question)[http://stackoverflow.com/questions/17211154]
Thanks!

The Stack Trace (From Eclipse):

This is also true when not using the Memory Cache at all.

More things that didn't work

Recycling images on item destory as suggested in this SO question did not work.
Changing cache to WeakReferenceCache didn't work.
Working without memory cache at all didn't work.


DataLoader: update old dataloader and move new one into package

We need this data loader to be fairly flexible - we want to use it for ML training cases so it should be able to load the mp4s into tensors but also just bytes for things like optical flow etc. Should support returning useful things like padding masks and shape standardization.
Also good benchmarking will be important here


can't login using google chrome mobile browser on smartphone.

I can't login using the Google Chrome mobile browser on my smartphone. I tried on several smartphone devices but still can't login to web wallet.
I can only login through the browser on my PC and laptop.

Hi, probably it's a issue with compatibility,
Can you check if you have the latest version of google chrome in the phone ?

I even reinstalled with the latest version on both my smartphones, but the result is still the same.

That's weird, i can enter with phone.
Check if you have javascript enabled.

also can not use another web browser. javascript is enabled.
my device

redmi note 9 pro
redmi note 5a
sony xperia x1a

web browser

google chrome
mi browser

Is my smartphone IP blocked?
It's very strange that I can login using a smartphone that has never been used to open a web wallet.

If you're ip banned you can't enter from the pc.
This maybe it's just a issue of your phone and browser.

btw, try using phone data

I don't know why, but now I can login. Thanks very much


Add CODEOWNERS feature

Adds the ability to define code ownership in a CODEOWNERS file, similar to the GitHub feature. See the new docs page for a full feature description.
Closes #10161
Implementation
The primary back-end change is adding a call to AddCodeownerReviewers() in services/issue/issue.go. This searches the base repo for a valid CODEOWNERS file, parses it, and requests reviews from any users/teams that own any changed files in the PR. The parsing/validation is contained in functions within services/issue/codeowners.go.
The applicable CODEOWNERS file is also parsed to:

Display validation errors when viewing/editing a CODEOWNERS file
Display the hoverable shield icon inticating ownership as described below

UI Changes
Viewing a CODEOWNERS file with validation errors:

Editing a CODEOWNERS file with validation errors:

The remaining examples assume the following valid CODEOWNERS file is in the main branch:
asdf/ @user3 @Org1/teamA
*.txt @Org1/teamA

Viewing a file that has an owner displays a shield icon that can be hovered over to show the ownership tooltip. If no owner applies to the file, the shield is not displayed:

When opening a PR, the same hoverable codeowner shield icon is visible for any changed files with owners:

Same thing when viewing a PR's changed files:

Same thing when viewing a commit:

Known issues and features we are still working on

Testing. We recently ran into some issues integrating our unit tests properly.
Currently anyone can create/edit a CODEOWNERS file. This needs to be restricted to users with admin/owner permissions to match the GitHub feature.
Codeowners should not be added when a PR is created as WIP, but should then be added when the WIP prefix is removed.
Some code can be cleaned up and refactored a bit in codeowners.go

Duplicate of https://github.com/go-gitea/gitea/pull/24910?

Duplicate of #24910?

Yeah. Looks like it follows the GitHub CODEOWNERS syntax rules though, and it requires write access to be an owner. Shield icon on the files is helpful.

It's been a while since anyone on my team has looked at this. If any further changes are required to the CODEOWNERS feature (in either our implementation or the official implementation), it would be easier for all parties to create a new issue and work fresh from the latest version of Gitea.


GPflow 2.0 notebook update: SGPR upper bound

This PR updates the understanding/upper_bound.ipynb to work in gpflow2.
It fixes the upper_bound code in gpflow/models/sgpr.py and restores the original (tighter) test tolerance that had both been changed by commit 45efebc
The plots don't quite match up to what was in the GPflow1 version (nor does the tight bound in the 1-inducing-point example at the end), but otherwise this seems to work.

Please use PR description (top of this view) as the squash-merge commit message.


Images in markdown don't render as expected in doxygen

They look great in markdown. Let's see if we can figure out a way to fix this in doxygen.
https://github.com/Azure/azure-sdk-for-c/blob/master/sdk/iot/README.md#key-features

cc @danewalton, @danieljurek

This looks like it might be related: https://github.com/doxygen/doxygen/issues/6517

Discussed in standup... we should use img tags
![check mark](https://github.githubassets.com/images/icons/emoji/unicode/2714.png?v8)

Use images defined here: https://api.github.com/emojis

If we do it that way the images don't seem to scale well.
What about this?

To further excite matters, doxygen commands in the .md files will render correctly using Doxygen... It's as if we should be replacing :<something>: with \emoji <something>
 Retry Policies | \emoji heavy_check_mark * |

Another option is to directly use the unicode chars from http://unicode.org/emoji/charts/full-emoji-list.html. Github supports doing something like 😀 which is the same as :smile: so assuming Doxygen also supports the unicode char set it should work.


Documentation : How to run conductor server with single Redis instance

Hi,
I see in the config file for Conductor that it's possible to run with a standalone redis instance (ex: db=redis)
However, I cannot find any documentation explaining how to do so and looking at the code it's not immediately intuitive how to configure everything/which parameters are required and which aren't.
For a single redis, I have to set workflow.dynomite.cluster.hosts ... do I need to specify a rack or can I just specify the redis host:port ?
As for the other parameters, which of these are required? :

workflow.namespace.prefix=conductor
workflow.namespace.queue.prefix=conductor_queues
queues.dynomite.threads=10
queues.dynomite.nonQuorum.port=22122

Could you please provide me with the rough instructions for running with a single redis instance (without dynomite)?
In exchange I can update the markdown documentation  :)

@picaron prefix and thread configs are required.  the nonQuorum port MUST match the port number for the redis server.  I am going to update the documentation and publish.

The updated documentation is available now:
https://netflix.github.io/conductor/server/#using-standalone-redis-elasticache

fantastic, thanks @v1r3n
closing issue


Missing WebHttpBinding binding features

WebHttpBinding is missing from the second table (Binding Features)

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

ID: 684169cb-54a5-7351-3f62-2375fac8a73d
Version Independent ID: 100e1821-3d93-6f8d-fe33-d58b0b5e87d1
Content: Configuring System-Provided Bindings
Content Source: docs/framework/wcf/feature-details/configuring-system-provided-bindings.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for pointing out that WebHttpBinding is missing from the second table, @johnye2e. We've added it to the backlog.

@rpetrusha I would like to work on this, but I have some doubt regarding the default transport mode,duplex mode for WebHttpBinding. Can you help me to find the correct reference for WebHttpBinding to look for these informations.


python3Packages.flax build failure on x86_64-linux as of bb955f7b

Issue description
Build of python3Packages.flax failed on x86_64-linux as of bb955f7b5929c5676a2d28f53ee014b61d155f23.
build log
Maintainer cc: @ndl
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit bb955f7b5929c5676a2d28f53ee014b61d155f23
Run nix-build -A python3Packages.flax

Technical details
- system: `"x86_64-linux"`
 - host os: `Linux 5.13.0-1021-azure, Ubuntu, 20.04.4 LTS (Focal Fossa), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - nixpkgs: `/nix/store/a6lnslw4vs80p2cxff03gvakzxxi450h-source`

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tag:<PHONE_NUMBER>068475253

dup of https://github.com/NixOS/nixpkgs/issues/168570


huesyncbox.set_sync_state gives error on input

huesyncbox.set_sync_state
entity_id: media_player.philips_hue_hdmi_sync_box
input: "hdmi2"
Gives me Failed to call service huesyncbox/set_sync_state. value is not allowed for dictionary value @ data['input']
What am I missing?

I just had a look through the code and it's supposed to be input2 not hdmi2. The documentation is wrong

Actually this is a leftover from a long time ago when the sources exposed by the mediaplayer were hdmi1, hdmi2, etc...
At some point I decided it was more clear to use the names as set on the syncbox so instead of hdmi1 it would be "DVD Player" or whatever you set in the syncbox configuration.
I did not update this service it seems.
I think the "input" attribute should take the same values as the sources available in the media_player and I should actually also rename "input" to "source" to make that consistent.

So it seems I confused myself in the last comment. I got the input in the set_sync_state (which needs to have a fixed name) confused with the select_source service of the media_player which uses the userdefined name.
So indeed it was only a documentation update which is now done (with some other service related fixes) in release 1.12.0.


segmentation fault after force closing channel with 100 HTLCs

Background
Describe your issue here.
i have 2 nodes on testnet and made a channel of 100k sats between them
both have accept-amp and accept-keysend enabled in the conf
i was experimenting with amp payment sharding and made a payment of 54100 sat with a max shard size of 541. i made 100 shards and it succeeded. then i tried the same thing again but now i force closed the channel to get the HTLCs on the chain. after that the rpc didnt work anymore so checked the logs and found out it crashed. if i try to restart it i can enter the wallet password and it crashed again with a segfault. my other node didnt crash
Your environment

version of lnd
lnd version 0.14.2-beta commit=v0.14.2-beta
which operating system (uname -a on *Nix)
Linux 5600g 5.17.2-arch3-1 #1 SMP PREEMPT Sun, 10 Apr 2022 11:18:32 +0000 x86_64 GNU/Linux
version of btcd, bitcoind, or other backend
Bitcoin Core version v22.0.0
any other relevant environment details

Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
i dont know, it came unexpected.
i did it 5 times and the 5th time it crashed
Expected behaviour
Tell us what should happen
no segfault of course
Actual behaviour
Tell us what happens instead
a segfault
logs
i appended the last lines with the segfault from journalctl
lnd_crash.log

can you post the relevant stack trace here as well so people don't have to download it

sure

i restarted lnd with debuglevel=debug and it crashed as expected, here are the logs:
lnd_crash_debug.log
i grepped for nil and 0x0, maybe this helps:
$ cat lnd_crash_debug.log | grep -ETn 'nil|0x0[^0-9a-f]'
                1943:	2022-04-20 20:11:02.862 [DBG] CNCT: Starting ChannelArbitrator(bc5069269301b93e2627580533814fb7ceb8555bddf8bd2feed0a350440ea9e4:0), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) <nil>
                1950:	2022-04-20 20:11:02.864 [DBG] CNCT: Starting ChannelArbitrator(70a7b4108ccc0dfc916f1e0ed29126eea6d40be05fefbb36dad2fe1c51a0d9ec:1), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) <nil>
                1958:	2022-04-20 20:11:02.864 [INF] SWPR: Sweep request received: out_point=4f411a665a8016b3baf55ce194796a01684b7db5df904ab55483bf5a66198049:0, witness_type=CommitmentAnchor, relative_time_lock=0, absolute_time_lock=0, amount=0.0000033 BTC, params=(fee=253 sat/kw, force=false, exclusive_group=<nil>)
                1974:	2022-04-20 20:11:02.871 [DBG] CNCT: Starting ChannelArbitrator(0736d20cf96ff2ef31854b9ce3645f8f20edcaa415e9b4a190643fc3ebc2d8ff:1), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) <nil>
                2216:	2022-04-20 20:11:02.873 [DBG] CNCT: Starting ChannelArbitrator(fe068212f70886de05952e13f5e90be4bace958385496263a0a721f9c24e1b1d:1), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) <nil>
                2222:	2022-04-20 20:11:02.873 [INF] SWPR: Sweep request received: out_point=bf680a225ef135f971863588877b169d1f6f8b88ebfb2c9d67a2417010f7f755:0, witness_type=CommitmentAnchor, relative_time_lock=0, absolute_time_lock=0, amount=0.0000033 BTC, params=(fee=253 sat/kw, force=false, exclusive_group=<nil>)
                2233:	2022-04-20 20:11:02.877 [DBG] CNCT: Starting ChannelArbitrator(e328c444cdeea93ed5a7875ff9bd81b5bf51f79228886a663297708723fde170:0), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) <nil>
                2398:	2022-04-20 20:11:02.884 [DBG] CNCT: Starting ChannelArbitrator(d1ad120b1805af53782c14b00584f14fd197cdc68b502bf15bb27e8b07daa490:0), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) <nil>
                2559:	[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xc07184]
                2570:	github.com/btcsuite/btcwallet/walletdb/bdb.(*db).Update(0xc0004e6c00?, 0xc0026fe1e0, 0x0?)
                2574:	github.com/lightningnetwork/lnd/channeldb.(*DB).UpdateInvoice(0xc0000a4960?, {0x0?, 0xc0005ae660?, 0x0?, 0x93?}, 0xc0005ae680?, 0xc0000caa40?)

one channel's HTLCs expired and my lnd runs normal again


Handle sequence labels better

Example: sequence data set, but one label per sequence, rather than one label per time step.
List<List> format requires the same number of values at each time step (for transforms, analysis, later conversion to etc).
One approach: pad with NullWritable -> handle conversion later
Another approach: use a SequenceRecord object, and keep sequence label as a separate field?

Is this issue still viable?


DF Chat Enhancement: Add ability to Copy Formatted Chat Text

Formatted text in the chat window cannot be selected (and therefore can't be copied).
Steps for testing: Type <b>Hello World!</b> in chat and hit enter. You will not be able to select the bolded text.
Would like to see a feature added to allow formatted chat text selecting/copying. There is another mod out there called FVTT-copy-chat that has similar functionality but (1) is older and may no longer work (not sure didn't install it) and (2) it seems like a natural fit for this mod. Which helps keep mod count down for those of us already using DFCE. the other mod adds a little button to click and copy but if there is a way to just allow text to be highlighted/selected manually that would be great as we could select only what we need/want (not sure if that's easier or harder).
For now a workaround is export to Adventure Log and then the text is able to be copied, but of course this is a bit tedious to have to go through the extra steps.
Thanks Flamewave!

I see the module has been updated within the last month. I can investigate to see if this can maybe be done better though. I agree that selecting formatted text with the mouse cursor would certain be preferable vs copying the entire message.

I see the module has been updated within the last month

I didn't even catch that. It has "Tested on Foundry VTT 0.7.5" under Compatibility and that's what I was going off of. Checking the module.js file though I do see the line:  "compatibleCoreVersion": "0.8.8"
But yeah, it sounds like you also prefer the same method/enhancements I'd like to see. Plus not sure about you, but for me, with like 70 mods, not having to install another is always nice!
I appreciate the consideration of this enhancement!


Unable to resolve signature of class decorator when called as an expression

When I add this to Nuxt3 project, I see:

Typescript is 4.9.4, tsconfig is:
{
	// https://nuxt.com/docs/guide/concepts/typescript
	"extends": "./.nuxt/tsconfig.json"
}

From what I gathered (I could be mistaken) this is caused by returning any:
https://github.com/facing-dev/vue-facing-decorator/blob/de750a81bb731e86af4076b5de4fb2f374688480/src/component.ts#L159
Anyhow the project apparently needs some further setup and/or specific Typescript version, but I couldn't find anything in the documentation.
Related issue: https://github.com/microsoft/TypeScript/issues/52396

My bad. It was caused by experimentalDecorators not being enabled.


Ground primitive artifact on iPad

Sandcastle link. This works fine on desktop, and mostly fine on iPad:

Until you zoom in a bit on iPad, you can see a seam very similar to the one in https://github.com/AnalyticalGraphicsInc/cesium/pull/8205 that moves with the camera that will cut out pieces of the polygon:

I believe it's related to https://github.com/AnalyticalGraphicsInc/cesium/pull/8205 because I can see the same seam across the 3D Tileset, but using that branch the seam is fixed on the 3D Tileset but remains on the ground polygons.

How many frustums are being drawn in that view. It might not be #8205 if it's just one.
@likangning93 might have a better idea.

Oh except this is iPad which may not support log depth, so there are probably multiple frustums.

Yes, I suspect there's multiple frustums because iPad doesn't support log depth. Although I can't reproduce the issue on desktop by turning off log depth. I updated the Sandcastle to turn off log depth and include the inspector. You can see it's using 2 frustums:

And at that camera distance that "shreds" the polygon, if you show the frustum geometry and rotate around, you can see it's when the frustum plane intersects that building:


Improve path parameter annotations

Path parameter annotations used to include special symbols {arg}, *
(wildcard), and ^ (prevent path parameter at this position), and they used to
match by longest prefix.
This PR makes two syntax changes:

removes ^ (it was never used in practice)
adds ** (like *, but matches zero or more path segments)

It also makes several changes to the semantics:

annotations are now exact match rather than prefix match (prefix match is
recoverable using **)
the order of annotations implies a priority: the first match wins
a matching annotation with concrete path components prevents path parameter
inference from generalizing those components.  for example, /v1/** will
prevent v1 from being turned into a path parameter for all paths that
start with /v1

This doesn't seem to be part of the PR? Or if it is, it's too subtle for me to understand.

a matching annotation with concrete path components prevents path parameter
inference from generalizing those components.

That's part of a companion PR -- the syntax of patterns and semantics of matching lives in akita-libs, but the interpretation of what to do with a matched pattern doesn't.  I'll change the description to be more clear.


Various label improvments

Add "All" as an option in the label dropdown.
Use the default label (e.g. "") equivalent to having "All" selected
Make it so that you cannot rename the "All" label
Make it clearer what you are renaming or creating
Make the delete message more clear -- whether you are deleting ALL or ALL for a specific label

In testing it failed this test case:
Create a label and record a voice recording.
If you click 'rename label' but it is blank it actually deletes the label, so the risk is high of losing labels by accident.

Good catch!  I'll make it so that you have to have a non-empty string to actually create/rename


cmd/go: print import stack when reporting error constructing build list

In module mode, every build starts by constructing the build list, the set of modules at specific versions that will be involved in the build. We construct the build list by exploring the import graph rooted at the command line arguments, adding modules to satisfy any imports that can't be resolved.
There are a number of things that can go wrong during this process, not all of which are under the user's direct control. For example, suppose a transitive dependency requires github.com/golang/lint, but the go.mod in that repository declares the module path golang.org/x/lint. The package importing github.com/golang/lint is wrong, but we don't currently report what that package is or why it's part of the build.
When an error like this occurs, we should report the chain of imports from the command line arguments to the problematic package.

@jayconrod I had this question when ran this for the first time.
If you see an error like this:
go get<EMAIL_ADDRESS>->
<EMAIL_ADDRESS>parsing go.mod: unexpected module path "github.com/sirupsen/logrus"

First, does the first transition there represent an upgrade?  If so, I didn't understand that at first, and at first I thought that -> represented a dependency given that is what it means later in bigger errors. If that does represent an upgrade, maybe it could help to do something like replacing the -> with upgraded to, or some other English phrase?
Second, I think the main module is implied? If so, maybe the "get" could be eliminated and add in the main module as the first line?
I don't think this is quite perfect, but maybe something like:
go:  github.com/my/module ->
<EMAIL_ADDRESS>upgraded to
<EMAIL_ADDRESS>parsing go.mod: unexpected module path "github.com/sirupsen/logrus"

CC @mfridman

@thepudds "upgraded to" is probably the right phrasing. @heschik also asked me about this today, too. I'll change it.
go get: is a prefix of all the error messages for that command, so I think that should be left alone.
About the main module, unfortunately, that's a difficult change to make because we don't know whether requirements are direct or transitive when that error comes up. go get -u constructs the regular build list, adds any named arguments with specific versions, then constructs a new build list from that list where we also upgrade everything. Most of these error come up in that second list, but we've already thrown away the original module graph at that point, so we can't trace a path from the main module to a transitive requirement. All transitive requirements look like direct requirements.
We should refactor this. It will be a complicated change though.


Can we obtain the prompt(s) clipseg would respond to for a given image?

I have the following image, and I'm trying to replace the face (including hair) with a Textual Inversion embedding face (about which, by the way, I'll say clipseg seems to work much better for TI than txt2img and img2img -don't know the reason yet).

Anyway, I can replace either face or hair but not both (at the same time). I've also tried man, kid, boy, anime boy, etc. but in these cases -tm does not do anything and returns the initial image.
Is there a way to obtain what prompt would be required for clipseg to replace the entire character?

I don't have an answer to the question for now, but in the future I would like to implement (txt2)mask compositing. So you provide "face" and "hair" and can stack the resultant masks into one.

Yes, I have just added a new CLI command called !mask. It will generate three different images that shows you what clipseg has identified and how it will be thresholded into a mask.

Testing the new feature, I get:
!mask outputs/new/000427.2535887212.png -tm "face"
Deselected | Masked | Selected

But I still need to guess face is the keyword I should pass to -tm, don't I?
PS: Reminder that self.model.embedding_manager.load is necessary to use embeddings. (vs not using self).

The deal here is that clipseg produces a continuous scale of confidence
scores for each patch. The confidence scores are mapped onto the alpha
channel of the semi-transparent images on the left and right. To convert
this into a mask for inpainting, you have to choose a threshold confidence
value. Patches that equal or exceed this value are then converted into
black for the inpaint mask.
It's annoying that you can't just pass this mask to inpainting directly and
have to run clipseg again, but the code doesn't currently accept a
monochrome image as the mask. This is pretty easy to fix and I'll implement
it over the next couple of days.
Lincoln
On Thu, Oct 20, 2022 at 9:57 AM Any-Winter-4079 @.***>
wrote:

Testing the new feature, I get:
!mask outputs/new/000427.2535887212.png -tm "face"
Deselected | Masked | Selected
[image: image]
https://user-images.githubusercontent.com/50542132/196968494-8d2790b1-b527-4026-be61-0a0a7123260b.png
But I still need to guess face is the keyword I should pass to -tm, don't
I?
PS: Reminder that self.model.embedding_manager.load is necessary to use
embeddings. (vs not using self).
—
Reply to this email directly, view it on GitHub
https://github.com/invoke-ai/InvokeAI/issues/1180#issuecomment-1285591022,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3EVNN4MSU3LU4JTEEEZ3WEFFVDANCNFSM6AAAAAARJZWHGI
.
You are receiving this because you commented.Message ID:
@.***>

PS: Reminder that self.model.embedding_manager.load is necessary to use
embeddings. (vs not using self).

Is there an unmerged PR with this fix?
Lincoln

It's done.

Testing the new feature, I get: !mask outputs/new/000427.2535887212.png -tm "face" Deselected | Masked | Selected  But I still need to guess face is the keyword I should pass to -tm, don't I? For example, I still don't know what keyword (if any) can allow me to select the whole character (including hair) unless by trial and error.
PS: Reminder that using self.model.embedding_manager.load in generate.py is necessary to use embeddings. (vs not using self). This fix is on main but not on dev right now.

Yes, you have to guess what prompt to use to select the whole character. However, it is pretty good at language, and you can use fairly natural language such as "the boy", "the character" or "the background". For example, one of the clipseg demos selects a cup and a jar with the phrase "fluid containers"


[FCE-798] Bump to Expo SDK 52

Description

Bumped example deps to support Expo SDK 52
Updated peer deps to require Expo 52
Migrated EventEmitter to new API

This is a breaking change, it won't work with previous versions of Expo
Motivation and Context

We can now support Expo SDK 52

How has this been tested?

Run and tested on Android/iOS

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to
not work as expected)

Tested with an Expo 51 app and works fine.


About Training Time

Hello! Thank you for your awesome work for 3D instance segmentation. I want to know that how many GPU did you use and how long does it take to train your network on S3DIS. Thank you!

Hi,
Thanks for your interest in our work!
On S3DIS dataset, we use a single V100 GPU to train the model. Pre-training the backbone from scratch takes around 16 hours (with batch_size=16), or you could fine-tune the backbone trained on ScanNetV2 with fewer epoches. Training the entire network takes around 28 hours (with batch_size=12). Setting fp16=True in the cfg files could also speed up the training time and reduce the memory consumtion.


bug: saveJMRUI and savejMRUI

Dear,
I an attempt to compare the Osprey fitting results with those from jMRUI for my data, I found a bug in your code.
In the job .m example files and in the ‘OspreyJob.m’ file, you use the opts.saveJMRUI tag. However in, the MRSCont.mat data structure and in the ‘OspreyGUI.m’ files, you use the opts.savejMRUI tag. Since savejMRUI and saveJMRUI are different parameters in Matlab, Osprey never writes the requested jMRUI files. If I change it in the job .m example files and the ‘OspreyJob.m’ file to savejMRUI, it works fine.
Kind regards,
Dr. Peter Van Schuerbeek

Dear Dr. Van Schuerbeek,
Thank you for using Osprey and reporting back those issues to us. Osprey is still under development and any user feedback is appreciated.
I've now fixed the jMRUI export problem. Let me know if you experience any other problems or if you want to give us feedback/suggestions.
Best,
Helge Zöllner


Horizontal scroll bar is not available in Publisher's Manage window

Description:
Horizontal scroll bar is not available in Publisher's Manage window.
When you minimize the screen or when your screen is small, it will not have a horizontal bar and users will not be able to select right hand side options.
Suggested Labels:
2.2.0
Affected Product Version:
2.0.0

By Ushani Balasooriya from https://wso2.org/jira/browse/APIMANAGER-4668

This issue is also observable in 3.0.0 so it needs to be validated after UI revamp

Manage tab is not there anymore in the latest APIM versions (4.2.0)


gamma-control-v1: apply gamma LUT when output gets enabled

Depends on https://github.com/swaywm/wlroots/pull/2315
Closes: https://github.com/swaywm/wlroots/issues/2372

Doesn't actually work.

What is the status of this? I am also getting the following crash:
EE 18-09-20 14:39:34.667 - [src/main.cpp:244] Fatal error: Fatal error(SIGABRT)
EE 18-09-20 14:39:34.799 - #1  signal_handler(int) ../src/main.cpp:246
EE 18-09-20 14:39:34.824 - #2  __restore_rt sigaction.c:?
EE 18-09-20 14:39:34.845 - #3  __GI_raise :?
EE 18-09-20 14:39:34.866 - #4  __GI_abort :?
EE 18-09-20 14:39:34.886 - #5  _nl_load_domain.cold loadmsgcat.c:?
EE 18-09-20 14:39:34.907 - #6  .annobin_assert.c_end assert.c:?
EE 18-09-20 14:39:34.919 - #7  gles2_get_renderer_in_context ../render/gles2/renderer.c:36
EE 18-09-20 14:39:34.932 - #8  gles2_bind_buffer ../render/gles2/renderer.c:138
EE 18-09-20 14:39:34.944 - #9  wlr_renderer_bind_buffer ../render/wlr_renderer.c:48
EE 18-09-20 14:39:34.956 - #10 drm_surface_unset_current ../backend/drm/renderer.c:161
EE 18-09-20 14:39:34.969 - #11 drm_connector_rollback_render ../backend/drm/drm.c:602
EE 18-09-20 14:39:34.984 - #12 wlr_output_rollback ../types/wlr_output.c:656
EE 18-09-20 14:39:34.998 - #13 gamma_control_handle_set_gamma ../types/wlr_gamma_control_v1.c:111
EE 18-09-20 14:39:35.009 - #14 ffi_call_unix64 ??:?
EE 18-09-20 14:39:35.017 - #15 ffi_call ??:?
EE 18-09-20 14:39:35.024 - #16 wl_event_loop_get_destroy_listener ??:?
EE 18-09-20 14:39:35.032 - #17 wl_client_destroy ??:?
EE 18-09-20 14:39:35.039 - #18 wl_event_loop_dispatch ??:?
EE 18-09-20 14:39:35.046 - #19 wl_display_run ??:?
EE 18-09-20 14:39:35.094 - #20 main ../src/main.cpp:409
EE 18-09-20 14:39:35.115 - #21 __libc_start_main ??:?
EE 18-09-20 14:39:35.140 - #22 ?? ??:0

I suppose this PR should fix it?

I hope this PR is merged soon as my eyes hurt at night without gammastep.

Current status is that the DRM backend doesn't set wlr_output.frame_pending correctly after enabling an output so this patch doesn't work.

https://github.com/swaywm/wlroots/pull/2459 should fix this.

While this fixes the original issue, on Sway this doesn't quite work, because Sway calls wlr_output_rollback in-between frames for some reason. But this PR should at least fix the failure (and the whole issue on other compositors).


Uncaught RangeError: Array buffer allocation failed

Uncaught RangeError: Array buffer allocation failed
at new ArrayBuffer ()
at new Uint8Array ()
at new Uint8ArrayWriter (zip.worker.js?4b26ffb:14)
at JSZip.generate (zip.worker.js?4b26ffb:14)
at zip.worker.js?4b26ffb:14
After pressing export, this error shows in the console when I use more than 28 panos in the Marzipano Tool.
Reducing the files sizes with jpg compression had no effect.
Have not tried reducing resolution.
Looking for remedies and work arounds if this is not a bug.

Unfortunately, this just means that you imported too many panos, and the browser ran out of memory. JPEG compression won't help, because the tool must decompress the images to process them.


Screenshot isn't showing anymore

https://github.com/ez4o/github-contribution-graph#about-the-project

Thanks for your report. Working on it!

Amazing responsetime!
I'm considering using this for my profile now :)


bower: Version declared in the json (1.0.2) is different than the resolved one (1.1.0)

Thanks , fixed on 1.4.0.
I still need a reliable method of updating both.


Nested connectOrCreate fails while it's structurally valid

Bug description
Hey, Prisma team!
I have models with a lot of nested relationships, and I'm currently trying to write a seed to populate the database with enough data to facilitate development. I wrote a create command with multiple nested connectOrCreate statements, which looks valid according to TypeScript. However, the CLI errors out.
Context
In my models (see Prisma information), each Show has many creators. A creator is a Credit, which represents a "role" that someone played (director, writer, etc.), so every Credit has one Person (but a Person can have many Credits, across many Shows).
I wrote a command in my seed.ts file (see Prisma information) where I'm nesting connectOrCreate calls so that I can write the Persons when I write the Credits. You can have the same person creating, producing or acting in a show so it makes sense to create it once.
This code is valid according to the Prisma client's types. However, when I run the seed command, I get the following error:
Unknown arg `person` in data.creators.connectOrCreate.0.create.person for type CreditUncheckedCreateWithoutCreatorsOfInput. Did you mean `personId`? Available args:
type CreditUncheckedCreateWithoutCreatorsOfInput {
  id?: String
  tmdbId: String
  castOf?: EpisodeUncheckedCreateNestedManyWithoutCastInput
  crewOf?: EpisodeUncheckedCreateNestedManyWithoutCrewInput
  guestsOf?: EpisodeUncheckedCreateNestedManyWithoutGuestsInput
  job?: String | Null
  personId?: String | Null
  type?: String | Null
  createdAt?: DateTime
  updatedAt?: DateTime
}

However, the type for data.creators.connectOrCreate.0.create is XOR<CreditCreateWithoutCreatorsOfInput, CreditUncheckedCreateWithoutCreatorsOfInput>, and CreditCreateWithoutCreatorsOfInput does contain person so I would expect the client to let me nest a connectOrCreate for person and not pass a personId which would force me to create all Persons separately.
How to reproduce

Create the models as documented
Try creating one Show with many Credits and their associated Persons in a single create call using nested connectOrCreate
See TypeScript validate this structure
Run the seed command
See error

Expected behavior
I would expect the error and types to be coherent, because right now I'm not sure whether nested connectOrCreate calls are valid or not, if the error is somewhere else, and what I should do next.
Prisma information
Here's an abridged version of my relevant models:
model Show {
  id       String     @id @default(cuid())
  name     String
  creators Credit[]
}

model Credit {
  id       String    @id @default(cuid())
  job      String?
  person   Person?   @relation(fields: [personId], references: [id])
  personId String?
}

model Person {
  id      String    @id @default(cuid())
  name    String
  credits Credit[]
}

I wrote the following command in my seed.ts file (abridged for clarity):
// The `show` variable comes from a JSON fixture file.

prisma.show.create({
  data: {
    // ...
    creators: {
      connectOrCreate: show.creators.map((creator) => ({
        where: { apiId: creator.id },
        create: {
          apiId: creator.id,
          job: creator.job,
          person: {
            connectOrCreate: {
              where: { apiId: creator.person.id },
              create: {
                apiId: creator.person.id,
                name: creator.person.name,
              },
            },
          },
        },
      })),
    },
  },
});

Environment & setup

OS: Mac OS
Database: SQLite
Node.js version: v16.9.1

Prisma Version
3.14.0

Got the very same problem :)

I'm encountering the same issue

Same problem, connectOrCreate only connects/creates one of the records.

Same issue. Plus it doesn't work when I use map in nested connectOrCreate
// The `show` variable comes from a JSON fixture file.

prisma.show.create({
  data: {
    // ...
    creators: {
      connectOrCreate: show.creators.map((creator) => ({
        where: { apiId: creator.id },
        create: {
          apiId: creator.id,
          job: creator.job,
          person: {
            // This causes an error
            connectOrCreate: persons.map((person) => ({})),
          },
        },
      })),
    },
  },
});

Same issue here.

Is it possible to nest connectOrCreate?

updateProfile = asyncHandler(async (req: Request, res: Response) => {
    const id: number = parseInt(req.params.id, 10);

    const p = req.body;
    const c = p.contact;

    const result = await prisma.profile.update({
      include: {
        contact: {
          include: {
            socialmedia: true,
          },
        },
      },
      where: { userId: id },
      data: {
        ...p,
        contact: {
          connectOrCreate: c.map((citem: { socialmedia: [] }) => {
            return {
              where: { id: id },
              create: {
                ...citem,
                socialmedia: {
                  connectOrCreate: citem.socialmedia.map((smitem: object) => {
                    return { where: { id: id }, create: smitem };
                  }),
                },
              },
            };
          }),
        },
      },
    });
    console.log(result);
    res.status(200).json(result);
  });

For first use it works correctly, but doesn't update social media.


Improve visual formatting of message edit history

Now, after a message has been edited, it's possible to see the history versions of the message (see #268).  The new UI is functional, but could look a lot nicer.  The big structural things are these:

We should optimize the timestamp display to not repeat the date every time, while still providing precise dates for each transition in the message's content.
We should start displaying topic edits (maybe just show the topic part of a recipient bar to show changes in the topic?)
Improve the colors.  The current colors were chosen for a use case where the diff would be shown on every message, not only in this off-to-the-side edit history view.
Potentially add some sort of (optional?) display of what was removed from the previous version.

This is a meta-issue for now; we may end up splitting it into several sub-issues once someone is actually working on it.

@timabbott Can you please explain the first point about optimizing timestamp display, in a little more detail? I am unable to get the expected behavior for it.
I will try to cover all the mentioned points soon.
Thanks!

For timestamps, ideally we'd use date lines in between events that happened on different days, and then just have the time in each individual row (similar to how the webapp itself works).  In most real-world cases, everything happens on the same day, so it'd avoid repeating a bunch of unnecessary information.

@zulipbot claim

Hello @khantaalaman, you claimed this issue to work on it, but this issue hasn't been updated for a week. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let me know that you're still working on this issue within 3 days, or else I'll automatically remove your assignment from this issue.
If you've decided to stop working on this issue, simply comment @zulipbot abandon to abandon this issue so someone else can claim it and continue from where you left off.
Thank you for your understanding and your valuable contributions to Zulip!

@zulipbot claim

@zulipbot abandon

I am working on this.


[TW-409] Mark private and internal classes

What

This PR marks several classes as internal.
Why

This hides these classes from the generated docs, reducing developer confusion.
Test Plan

✅ | Unit tests aren't needed for docs and comment changes.
✅ | The reviewer should manually test the changes in this PR.

Check out this branch, and then:
./gradlew dokkaHtml
npx http-serve reference-docs

Confirm that the classes marked as internal do not show up in the generated docs.

@devinmorgan how are you able to determine if these objects can be made internal?

@devinmorgan how are you able to determine if these objects can be made internal?

Hey @dleis612 - great question! Generally speaking, if we can mark something as internal and the compiler doesn't yell at and the CI tests pass, that's a good indicator that we can safely mark something as internal.
Now heuristics aside, with respect to these classes

PanElementStateDto
DerivedCardInfoDto
PinElementStateDto

In the ElementState.kt in this PR, we publicize interfaces of the data schemas we expose for on-change events. Each of the above classes implements a publicly exposed interface:

PanElementStateDto (should be internal) -> PinElementState (public interface)
DerivedCardInfoDto (should be internal) -> DerivedCardInfo (public interface)
PinElementStateDto (should be internal) -> PanElementState (public interface)

And then lastly, ForageApiResponse.fromError is utility that is we use internally and know that we don't want to make publicly available.
Let me know if this clarifies, Danny!

Kimberlee, this PR looks good to me! I'm marking that I approve but let's wait for @dleis612 to confirm that he's onboard with these changes as well before merging. That OK with you?

Sounds great, thank you, @devinmorgan ! I'll wait for @dleis612 to give the thumbs up before merging this.


Web GUI cannot retrieve redis keys with backslash character () in it

Hi, I believe there is a bug in the web GUI when the redis keys contains backslash \.
The key tree stop "expanding" when it encounters \ in the key name.
I'm using redis-commander in a container with the latest tag
Here is an example where the keys stop showing after the \\
original keys :
PHPREDIS_SESSION:storage::plugin::690b8981\\1::A
PHPREDIS_SESSION:storage::plugin::690b8981\\1::B
PHPREDIS_SESSION:storage::plugin::690b8981\\1::C

See in the screen shot the different ways tried to retrieve the keys but only when removing the \ it worked.

To compare with the redis-cli, I can retrieve the keys by escaping the backslash.

yes, you are right, seems nobody used backslashes before... i'll have a look at it.
May be a problem with double qoutes needed.

new docker image will be available soon. Can you retest and verify its working now?

I confirm it is working now!
Thank you for the incredibly fast fix!
Well done 🎉

ok - thanks. I leave it open until a new fixed version is released to NPM.

I leave it open until a new fixed version is released to NPM

@sseide seems not yet released?


docs: add adr for routing protocol formats

Merged as https://github.com/ockam-network/ockam/pull/1167


Edit out the flair icon image edges so they appear correctly in circles

#5

This venture has been scrapped.  The colors are good enough.


Astro + vite integration

Hello,
Does this plugin work with Astro ? Is there a working example out there?
Cheers,
François

I don't know. I don't know Astro. I suggest you give it a try.

The idea was to use Astro as a static site generator that embeds Vite + some scalajs interactivity.
It seems that just adding the scalajs plugin naively in the vite plugins section of Astro config doesn't do the trick, and I don't know the lifecycles of all of those tools enough to get what hook might be missing, or how to tell the plugin to process .astro template files.

Sorry, issues were with the Astro config, not the Vite ScalaJs config.
I restarted from scratch, not with the Astro Getting Started but taking inspiration from : https://astro.build/themes/details/astro-vanilla-ts/ (closer to my intended usecase), and I can confirm I managed to get a Hello World from Scala / it works perfectly !
Sorry for the noise,
François


S80 disk size

Table shows S80 disk size as 32,384. Given others follow powers of two this looks like a typo. Sure this shouldn't be 32,767?

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

ID: 3799662b-8f0f-c4e6-26b5-b2ff24a9242a
Version Independent ID: 0c93223c-f28b-7ca7-0d10-c19e5fea9197
Content: About unmanaged (page blobs) and managed disks storage for Microsoft Azure Windows VMs
Content Source: articles/virtual-machines/windows/about-disks-and-vhds.md
Service: virtual-machines-windows
GitHub Login: @roygara
Microsoft Alias: rogarana

Thanks for the feedback! We are currently investigating and will update you shortly.

I have assigned the issue to the content author to investigate further and update the document as appropriate.

For similar reason how about size of S50?
If this also should be powers of the two? Isn't this supposed be 4096 GiB?
E50: 4095 GiB


hab_install provider - missing closed bracket at the end of line 58

Hi,
Just a small syntax error.

Sorry, I'm not seeing where this is. Could you please provide a link to the specific line and commit?

Hi,
I'm sorry, it fails with provider_hart_package. I changed the title to reflect it.
Here is the log from Travis.

0.29s$ /opt/chefdk/embedded/bin/foodcritic --version
foodcritic 7.0.1
51.79s$ KITCHEN_LOCAL_YAML=.kitchen.docker.yml /opt/chefdk/embedded/bin/kitchen verify ${INSTANCE}
-----> Starting Kitchen (v1.10.2)
-----> Creating ...
Finished creating  (0m44.26s).
-----> Converging ...
Preparing files for transfer
Preparing dna.json
Resolving cookbook dependencies with Berkshelf 4.3.5...
Removing non-cookbook files before transfer
Preparing validation.pem
Preparing client.rb
Transferring files to
Starting Chef Client, version 12.12.13
Creating a new client identity for default-ubuntu-1204 using the validator key.
resolving cookbooks for run list: ["habitat::default"]
Synchronizing Cookbooks:

habitat (0.0.3)
Installing Cookbook Gems:
Compiling Cookbooks...
================================================================================
Recipe Compile Error in /opt/kitchen/cache/cookbooks/habitat/libraries/provider_hart_package.rb
================================================================================
SyntaxError

/opt/kitchen/cache/cookbooks/habitat/libraries/provider_hart_package.rb:59: syntax error, unexpected keyword_end, expecting ')'
Platform:
x86_64-linux
Running handlers:
[2016-07-19T07:43:56+00:00] ERROR: Running exception handlers
Running handlers complete
[2016-07-19T07:43:56+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 01 seconds
[2016-07-19T07:43:56+00:00] FATAL: Stacktrace dumped to /opt/kitchen/cache/chef-stacktrace.out
[2016-07-19T07:43:56+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-07-19T07:43:56+00:00] ERROR: /opt/kitchen/cache/cookbooks/habitat/libraries/provider_hart_package.rb:59: syntax error, unexpected keyword_end, expecting ')'
[2016-07-19T07:43:57+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

------Exception-------
Class: Kitchen::ActionFailed
Message: 1 actions failed.


PM - Add PR and issue templates for leadership roles

As a Technical Project Manager, I will want to ensure that there is a PR and issue template that is suitable for tasks for this role.
Story Points
1-2

This issue is outdated since we've moved to our new user story format.


Don't sleep in sender_wrapper.py

I'm struggling to understand the purpose of the configurable "timeout".  It doesn't function as a timeout at all.  Instead, it's a fixed-length sleep that gets added before sending results in get mode, but not getverb.  The comment says "wait for LLD to be processed by server".  The only two motivations I can think of are:

The server processes multiple responses from the same agent out-of-order.  That seems unlikely.  It would be a server bug if true.

The server performs LLD using a getverb operation, which sender_wrapper handles by forking and running in the background.  That might allow it to process a subsequent get operation before the original getverb were complete.  If this is true, then the correct solution is to block while sending a response rather than running it in the background.

Unless you tell me otherwise, I'm going to assume that 2 is the case.  I'll fix it and remove the timeout setting.

Ok, so after a few days of study I understand better how Zabbix works and why you do what you do:

Normally, LLD discovery would return a list of disks, and the Zabbix master would poll those at some interval.  That's what https://github.com/v-zhuravlev/zbx-smartctl does.
You chose instead to use "trapper" items in order to minimize the amount of network activity.    Minimizing the amount of network activity is good.
Sending the detailed smart values with zabbix_sender could happen at any time, even from a cron job.  If new disks have arrived since the last LLD, that's fine: the server will ignore the data for the new disks.  I verified that experimentally.  If the data from zabbix_sender arrives before the very first LLD, then it will all be discarded.  That's not too bad, because it will still be picked up the next time the server polls LLD.
  That allows the user parameter script to return its LLD data before zabbix_sender returns detailed smart data.
In order to close a race between the parent and child processes, you added the "timeout" parameter (really a delay, not a timeout).  That's bad; hard-coded delays are always bad.
You also collect detailed data with smartctl during discovery.  That's fine for systems with just a few disks, but on large systems it exceeds zabbix's hard-coded 30s timeout for user parameter scripts

So my plan is:

Keep using trapper items.  Minimizing network activity is good.
Remove the hard-coded delay.  Instead, fork the user parameter script and daemonize it.  Print LLD results from the master process.  In the child, waitpid on the master (replaces the hard-coded delay).
Move detailed parameter collection from the master process to the child process, so the 30s timeout won't be an issue.

I'm good with the plan, as long as the daemon will not have polling capabilities (on it's own).


Body gets ragdolled after death

I set my pov to go into 3rd person if I die in the gui. If I am in 1st person before dying though my body gets flung over extremely long distances. The ragdoll doesn't happen if I was in 3rd person before death.

Known issue fixed in upcoming release.


Fix non build for non-standard MPD header locations

Right now, the build depends on the MPD headers (presumably coming from libmpdclient) being in a system directory. This PR fixes the build configuration, so even non-system installs will work as long as they are discoverable with pkg-config.
Fixes #226

Whoops forgot to do a no-ff merge. This has been merged.


[RFC][WEB][AUTO TVM]add web assembly autotvm support

Add web assembly autotvm support for TVM,
The related pull request will be pushed soon, which will be finished in a week.

@tqchen @junrushao1994

Thanks @xiebaiyuan .
On the wasm binary pulling. We might be able to reuse
the new RPC session constructor(via websocket)  that directly reconstructs from the wasm binary, so file exchange may not be needed https://github.com/apache/tvm/blob/main/web/tests/python/webgpu_rpc_test.py#L59
Would that eliminate the need of directory based exchange?

@tqchen We've thought it over in recent days, and will use websocket to transfer intermediate products. The rfc will be updated in a few days.

hey @xiebaiyuan you might take a look at the microTVM autoTVM infrastructure--it should be reusable for wasm.

https://tvm.apache.org/docs/tutorials/micro/micro_autotune.html#sphx-glr-tutorials-micro-micro-autotune-py
https://github.com/apache/tvm/blob/main/python/tvm/micro/build.py#L67

hey @xiebaiyuan you might take a look at the microTVM autoTVM infrastructure--it should be reusable for wasm.

https://tvm.apache.org/docs/tutorials/micro/micro_autotune.html#sphx-glr-tutorials-micro-micro-autotune-py
https://github.com/apache/tvm/blob/main/python/tvm/micro/build.py#L67

@areusch  thanks ~~ i will look in it

hey @xiebaiyuan just combing through old RFCs. are you guys still working on this one?

closing due to lack of response


Persist scoreboard

If the bot restarts then it loses track of all of the scoreboard data. It should persist it somewhere in case it is restarted.
Specifically:

What is currently on the scoreboard
What the vote count is (though this can be retrieved from the server with /aggregations)

Closing this.
As noted by Travis, the bot resumes syncing from where it left off, so the chance of missing a vote is minimal except for one
corner case, which has been filed as #92.


Add module field to package json

Changes proposed:

For adapt legacy browser (e.g IE11), add module field to build by their own babel config with webpack, or other bundle tools.

Acceptance Checklist:

[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 87.442% when pulling a5e484aaaceffe764c7d73e576018d7eb641d811 on euxn23:feature/add_module_field_to_package_json into 2132488ba61d5541d9afc174cf74ce948854a658 on reactjs:master.

References:

https://github.com/nodejs/node-eps/blob/4217dca299d89c8c18ac44c878b5fe9581974ef3/002-es6-modules.md#51-determining-if-source-is-an-es-module

@euxn23 Can you include more references about this?

I'll merge this since it seems to be harmless. Thanks, @euxn23.


Test collection v1

Codecov Report

Merging #111 (3a9a721) into main (1a36bfa) will increase coverage by 3.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #111      +/-   ##
==========================================
+ Coverage   83.75%   87.01%   +3.26%
==========================================
  Files         239      239
  Lines        5945     5945
==========================================
+ Hits         4979     5173     +194
+ Misses        966      772     -194

Impacted Files
Coverage Δ

...lection/Requests/GetCollectionsListRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...lection/Requests/GetCollectionsShowRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...tion/Requests/GetCollectionsEntriesRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...tion/Requests/PostCollectionsCreateRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...tion/Requests/PostCollectionsUpdateRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...ion/Requests/PostCollectionsDestroyRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

.../Requests/PostCollectionsEntriesAddRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...Requests/PostCollectionsEntriesMoveRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...quests/PostCollectionsEntriesCurateRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

...quests/PostCollectionsEntriesRemoveRequestV1.swift
100.00% <0.00%> (+100.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Demo Migration Project : System.Threading. Error

I am not been able to create the required environement for this demo project in Azure Devops.
Below are the the diagnostics logs:

The SSL connection could not be established !

System.Threading.Tasks.Task``1.GetResultCore(Boolean waitCompletionNotification) at AzureDevOpsAPI.QueriesAndWidgets.Queries.CreateQuery(String project, String json) in D:\a\1\s\src\AzureDevOpsRestApi\QueriesAndWidgets\Queries.cs:line 77
AB#3659

Hi @Hamza2404 Thank you for reaching us.
This could be an intermittent issue. Could you please try it again and let us know your updates?
Thanks!!


Mongolian translation Part-00

Thanks for your contribution and hard work, it is very much appreciated!


#20616 added USING clause for Greenplum tables DDL; partitions readin…

added USING clause for Greenplum tables DDL (starting Greenplum 7);
partitions reading and DDL creating enhanced - performance increasing (do not read keys and indexes for partition tables)
You can read the discussion here:
https://github.com/greenplum-db/gpdb/issues/16093#issuecomment-1662973007
Starting Greenplum 7 - we will create table DDL + separate partitions tables DDLs (with the help of the extra button "show partitions")
Before Greenplum 7 - we will use the old way of partitioning info showing - right into DDL (the modern way)

[x] DDL creating for Greenplum Materialized view
[x] tables reading in Greenplum 7 and Greenplum 6
[x] "USING" clause for Greenplum 7 tables (absent in Greenplum 6)
[x] Partition reading in Greenplum 7 and DDL creation
[x] Partition reading in Greenplum 6 and DDL creation
[ ] Partition reading and DDL creation in PostgreSQL

verified