fix: allow unreplaced BSB22 commitment hint in solver

Related #504.
In order to enable running full test suite where we use commitments we need to have the commitment available for the solver. I don't know what is a good way to do this, but this patch allows to continue with #472.
First, I register the hint in frontend/r1cs init. This gives solver access to the hint when run in the same process as the compiler. The hint is private so it isn't possible to provide it manually.
We also check if either debug tag is set or we run as a Go test (i.e. the executable name ends in .test). Only so we have a dummy commitment (zero).
Otherwise, we return an error, as before.

so, right now we have a "CommitInfo" bits in the ... constraint/System --> so we know:
HintID                 solver.HintID

at solve time, in all constraint system.
Shouldn't the R1CS.Solve() and SparseR1CS.Solve() methods check
if (commitment) and !alreadyReplaced(commitment.HintID) {
replace with something
}

? (commitmnet could already be repalced by the groth16 / plonk prover). Or did that change it latest design cc @Tabaie  ?

so, right now we have a "CommitInfo" bits in the ... constraint/System --> so we know:
HintID                 solver.HintID

at solve time, in all constraint system.
Shouldn't the R1CS.Solve() and SparseR1CS.Solve() methods check
if (commitment) and !alreadyReplaced(commitment.HintID) {
replace with something
}

? (commitmnet could already be repalced by the groth16 / plonk prover). Or did that change it latest design cc @Tabaie  ?

Yes I think that makes sense. Ideally the prover replaces the hint using proving key, but if that hasn't happened the solver would put a fake hint there. That at least is my understanding of what this PR does.
One other thing we could do is to actually use the latter version of the hint in the api.Commit function and register that hint by default so that we get the fallback case for free.

so, right now we have a "CommitInfo" bits in the ... constraint/System --> so we know:
HintID                 solver.HintID

at solve time, in all constraint system.
Shouldn't the R1CS.Solve() and SparseR1CS.Solve() methods check
if (commitment) and !alreadyReplaced(commitment.HintID) {
replace with something
}

? (commitmnet could already be repalced by the groth16 / plonk prover). Or did that change it latest design cc @Tabaie  ?

Yes I think that makes sense. Ideally the prover replaces the hint using proving key, but if that hasn't happened the solver would put a fake hint there. That at least is my understanding of what this PR does. One other thing we could do is to actually use the latter version of the hint in the api.Commit function and register that hint by default so that we get the fallback case for free.

Actually this is exactly what this PR is doing. frontend package registers the hint, but we do not register it in the constraint.RegisterHints (so the hint is only available if the frontend package is imported).


✨ add Patch/PatchAll methods

Closes #29

[x] Add Patch method to apply JSON patch on record, both HTTP and WS strategy
[x] With All suffix to prevent user mistake (no suffix = single mutation, with suffix = the entire table)
[x] Updated WeatherApi
[x] Updated readme with code example
[x] Update official doc

Depends on #46

Hey @Odonno! There seems to be a merge conflict here, could you look into that?


White Screen When Editing/Typing In Landscape Mode

When editing a note inside Landscape mode the screen becomes white, not sure if this was ment to be but I just wanna let you know https://user-images.githubusercontent.com/108516353/183267376-c22dc393-cbc4-47fa-8bc3-bcd3a6880f00.mp4

Happens aswell when using the search button

You can check this thread #50 at the end, where we discuss this. The screen you're talking about is shown by the system by default, and not by the app. I found a way to disable it, but there won't be any space left if keyboard is shown (Check the image in thread #50).

Is it possible to turn the white into dark? Can get quite annoying when using dark mode and getting a flashlight in my face

I don't think that's possible, but I'll look into it.

I personally dont think it's a bad gui on landscape mode but it doesnt match dark mode, not a huge deal I barely use the app in landscape mode but just wanted to share what I found, ill look for more bugs and let you know if i find more or have any suggestions.

Thank you! Please also check current issues before creating new ones that could be a duplicate. :)

Okay, hope I dont forget to check

Though I have 1 more question, which IDE do you prefer to use? Im currently choosing between Android Studio or IntelliJ IDEA.

Definitely Android Studio if you're doing Android development only, otherwise IntelliJ.

Alright


Add option to display dropdown icon within typeahead that on click opens the custom popup template

Feature description:
This feature will allow to optionally display dropdown icon within typeahead that on click open the custom popup template. This will make the typeahead more intuitive since users will be tempted to click on it a see what data is available for selection. Sometimes there is only 2 or 3 records available for selection and if the users don't happen to type the right words they cannot see what data is in there, and get frustrated, unless they have this new option that when you click on the dropdown icon it will display pop template with the available data. Quickbooks Online typeahead works just like this and it is awesome, I am attaching picture for better understanding.
Steps to reproduce the issue:
Type something that doesn't exists on the typeahead data source and nothing will show up as expected. Now try to find out what data is available within the data source, and you will get frustrated because it doesn't exists a way to make the pop template show up to see the data source data with out any filtering.

Version of Angular, UIBS, and Bootstrap
Angular:
1.5.11
UIBS:
2.5.0
Bootstrap:
3.3.7

Any feedback on this, it is a very important feature that will enhance the typeahead!!!


IGNITE-11824 refactoring data structure page lock listener

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer can associate accounts here: https://gitbox.apache.org/setup/ )
or /scripts/apply_pull_request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is actual.


improve diff editor audio cue handling

fix #173256

LGTM as long as preloading the sounds doesn't play them all to the user at the beginning.

volume is set to zero

Thanks @meganrogge! ❤

@meganrogge I just installed 1.78! This is the VERY FIRST thing I tested seconds after downloading 1.78.
THANK YOU!!!!!!!!  🎉


M3SOSCF Implementation

This is an implementation of the Markovian Multiagent Monte-Carlo SOSCF based on CIAH. It is a powerful, albeit slow SCF algorithm that enables near-guaranteed convergence even in extremely difficult systems.
Publication: https://doi.org/10.1063/5.0159737

1825 changed files in 41 commits? Sounds like you need to rebase to pyscf master...

My apologies, I forgot to do so after merging the dev branch. I will close the PR and open another once the fork is properly rebased.

You don't need to open a new PR; just do the rebase and force push.


python311Packages.caldav: 1.3.8 -> 1.3.9

Description of changes
Diff: https://github.com/python-caldav/caldav/compare/refs/tags/v1.3.8...v1.3.9
Changelog: https://github.com/python-caldav/caldav/blob/v1.3.9/CHANGELOG.md

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 275361 run on x86_64-linux 1

1 package marked as broken and skipped:

home-assistant-component-tests.caldav

7 packages built:

calendar-cli
calendar-cli.dist
gtg
python310Packages.caldav
python310Packages.caldav.dist
python311Packages.caldav
python311Packages.caldav.dist


feat: preselected theme

This PR implements the ability to attempt to force the use of light/dark theme in the admin panel. While I am a big advocate for the benefits that dark mode can bring to UX, it does not always suit a clients branding needs.
Open to discussion on whether we consider this a suitable feature for the platform. Please feel free to add to this PR as needed.
TODO:

[x] Implement tests (I'm open to guidance on this from the Payload team as currently it doesn't look like it's possible to adjust the payload config file on the fly - meaning it can't be easily placed in the admin folder tests).

Thanks for writing that test @GermanJablo, I considered using admin-root but wasn't sure if it was appropriate. Looking forward to hopefully seeing this feature approved!

I considered using admin-root but wasn't sure if it was appropriate.

Actually, it's not ideal to look for a test suite where it more or less "fits". This sparked an internal discussion about how nice it would be to be able to modify the payload config dynamically at runtime for testing purposes 😊


Add scanner invariants

In this change I added three invariants to executions scanner. The first invariant checks that history exists, the next checks that the first event in history is valid and the last checks that if the workflow execution is open there is a current mutable state which points at it. In addition to defining these invariants I also fixed an off by one error in historyVersions. In addition this adds TreeID and BranchID to the executions written by scanner this will aid in debugging. Finally this diff makes sure the persistence iterator and blobstore iterator always return a valid execution so that way invariants checks can assume execution is valid form.

Coverage increased (+0.04%) to 68.268% when pulling e72f2a52761ceecc93707b4cf525456bf4c77eac on andrewjdawson2016:AddScannerInvariants into 83809d81d577f5e5a85523474ac82bede1baa23e on uber:master.


runtime: re-organize arch-specific files

Right now, there are a lot of arch specific files in the runtime
directory. Some of them quite small.
For example, for ppc64, all these files is ppc64 arch-specific:
arch1_ppc64.go, arch_ppc64.go, zgoarch_ppc64.go.
We can't remove zgoarch_ppc64.go and it' auto-generated
anyway. But we can combine arch1_ppc64.go and arch_ppc64.go
into one file though.
Any other ideas?
PS: This problem is brought up in https://golang.org/cl/14447.

Actually I guess this is just done. There will be other cleanup in the runtime but we don't need a bug open for all possible cleanup.


Appraisals cleanup

I modified the appraisal gemfiles manually at some point. This fixes that problem and also the problem whereby bundler was trying to install a version of rack that is incompatible with Ruby 2.1 and below.

👍


'make import' only imports the open drive file but no models

Hi guys, I have some problem with the command 'make import'. When I try to import my own map, which is created from RoadRunner,  by using make import, it only imports the open drive file, but no model was imported in the UE4 editor. In another word, it will generate a series of waypoints with an empty world.
Dose anyone know what happens here?
Thanks!

[2020.07.14-18.56.17:527][  0]LogCore: Error: Invalid input P=360.648926 Y=-nan R=0.000000 to FRotator::Quaternion - generated NaN output: X=nan Y=nan Z=nan W=-nan
I got this log message, but how could know where this error happens?

@marcgpuig since you are working on the import pipeline these days, could you take a look at this, please?
@ZhengZhongyuan11 could you prepare your map to be shared with @marcgpuig ?

@germanros1987 Yeah, it is available, but could you leave me your email address, so that I could send it to you?

Hi, @ZhengZhongyuan11
Can you send it to<EMAIL_ADDRESS>


Feature Request Integrate pos_pin in pos_order_cancel module

Every mainstream and reliable POS system for restaurants/retailers has strict controls for certain actions like applying discount or canceling an item after it has been sent to kitchen. Only a designated user e.g. a manager can perform these actions after punching his pin on POS screen.
You already have a module pos_pin which is integrated with pos_product_available_negative. Can we have same integration with pos_order_cancel module. When a user clicks 'Cancel' or 'Delete' button, a popup will come up with users who have a 'POS Manager' role. Upon selecting a user from popup, the manager will enter his pin, get verified and then cancel an item. The Refund/Cancellation report at back will have the name of user who authorized the cancellation.
I will be happy to sponsor this.

Hi,
we like to use services like bountysource.com, https://gitcoin.co/ for sponsoring issues. Do you use any of them?

Yelizariev. Thanks for getting back. I have just created an account on BountySource. I will create bounty. Please let me know what is the appropriate bounty value.
The module should have option to specify when the security popup should be triggered- any time during the order or after the order is sent to Kitchen.
Thanks

@ilmir-k Can I start the work?

Hello @passion342
We would be glad to help you.
We estimated the work required for this task and it will cost 780 usd.
Please let us know if it is ok for you. Thanks
cc @GabbasovDinar

Thanks @ilmir-k
I would love to $780 but unfortunately I can't pay that much at the moment. I can send $100 now. If someone else needs this functionality, they can contribute. Else, you can work on this when you feel time is right. Thanks for understanding

@passion342 It's ok. We can do as you offer. Thanks

Thanks @ilmir-k. I will send money. No obligations. You can work whenever you can. I was trying Bounty Source but unfortunately Paypal doesn't work in Pakistan. I will have to explore Bitcoin or Ethereum. Any other way to transfer money? Thanks

@passion342
We also use Payoneer service https://www.payoneer.com for payments. Did you use it? Does it work in your country?

Thanks. Yes- I use Payoneer.

This can be closed


[bug] Crashing when run from an alpine image

We are running into a crash when run in a pipeline on an m5.xlarge instance in docker alpine.   The terraform runs fine on a t3 instance through the same pipeline but not in m5 for some reason.
--- Stack trace ---
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xd02d21]
goroutine 8 [running]:
github.com/gruntwork-io/terragrunt/cli.runTerraformWithRetry(0xc0000c2000, 0x3, 0x0)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:487 +0x121
github.com/gruntwork-io/terragrunt/cli.runTerragruntWithConfig.func1(0xc0002d4510, 0x2)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:440 +0x2a
github.com/gruntwork-io/terragrunt/cli.runActionWithHooks(0xf56322, 0x9, 0xc0000c2000, 0xc0002d4750, 0xc0001c9bf0, 0x0, 0x44)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:451 +0x2ae
github.com/gruntwork-io/terragrunt/cli.runTerragruntWithConfig(0xc0000c2000, 0xc0002d4750, 0xc0000c2000, 0x0, 0x0)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:439 +0x2c7
github.com/gruntwork-io/terragrunt/cli.runTerraformInit(0xc0000c38c0, 0xc0002d4750, 0x0, 0x0, 0x0)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:632 +0xaa
github.com/gruntwork-io/terragrunt/cli.prepareNonInitCommand(0xc0000c38c0, 0xc0002d4750, 0x0, 0x0)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:575 +0x8b
github.com/gruntwork-io/terragrunt/cli.runTerragruntWithConfig(0xc0000c38c0, 0xc0002d4750, 0x0, 0x0, 0x0)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:430 +0x211
github.com/gruntwork-io/terragrunt/cli.RunTerragrunt(0xc0000c38c0, 0xf6082b, 0x15)
/go/src/github.com/gruntwork-io/terragrunt/cli/cli_app.go:327 +0x51b
github.com/gruntwork-io/terragrunt/configstack.(*runningModule).runNow(0xc000482500, 0x0, 0x0)
/go/src/github.com/gruntwork-io/terragrunt/configstack/running_module.go:238 +0x17a
github.com/gruntwork-io/terragrunt/configstack.(*runningModule).runModuleWhenReady(0xc000482500)
/go/src/github.com/gruntwork-io/terragrunt/configstack/running_module.go:201 +0x6a
github.com/gruntwork-io/terragrunt/configstack.runModules.func1(0xc0003a3b80, 0xc000482500)
/go/src/github.com/gruntwork-io/terragrunt/configstack/running_module.go:171 +0x51
created by github.com/gruntwork-io/terragrunt/configstack.runModules
/go/src/github.com/gruntwork-io/terragrunt/configstack/running_module.go:169 +0xe1

Weird. Any other differences  between the two? Different OS or same? What version of Terragrunt?

Same OS,  both are amazon linux 2 with docker installed.
TF version is 0.12.18
TG version is 0.21.10

They are both running on amazon linux 2 images via gitlab CI and both the same gitlab-runner configurations.      The only difference is the size/type of instances because 1 account has more jobs then the other so it is larger to handle higher concurrency, everything else is the same.

From the stack trace you posted, it seems to be hitting a nil pointer dereference here: https://github.com/gruntwork-io/terragrunt/blob/v0.21.10/cli/cli_app.go#L487
The only reference I see is out.Stderr, so that would imply out is nil. Depending on where the error happened in the RunShellCommandWithOutput method, it's definitely possible for it to return nil for the CmdOutput parameter. What's not clear is why it would return an error on one instance type but not another.
That said, it's worth updating the if-statement here to check out is not nil before trying to reference data in it. If we do that, it'll fix the panic, and might let us understand more about what the underlying error is. Do you have any interest in submitting a quick PR to tweak this if-statement?

I’ll take a look at it, my go code isn’t the greatest but I will look.   I looked at the logs more and it’s happening in the terraform init.

Including the command that caused the panic
[terragrunt] [/builds/terraform/aws/us-west-2/bless] 2020/01/09 00:04:18 Setting working directory to /builds/terraform/aws/us-west-2/bless/.terragrunt-cache/UmMlsotVX2PpKdWF9uY3Ok/vQS_ZBbJ1UkQsnbYsPThpRs
[terragrunt] [/builds/terraform/aws/us-west-2/bless] 2020/01/09 00:04:18 Initializing remote state for the s3 backend
[terragrunt] [/builds/terraform/aws/us-west-2/bless] 2020/01/09 00:04:18 Detected 2 Hooks
[terragrunt] [/builds/terraform/aws/us-west-2/bless] 2020/01/09 00:04:18 Running command: terraform init -backend-config=bucket=terraform-abcd -backend-config=dynamodb_table=terraform-lock -backend-config=encrypt=true -backend-config=key=us-west-2/bless/terraform.tfstate -backend-config=region=us-west-2
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xd02d21]
goroutine 23 [running]:


Modern public domain mobile-optimized CLOS MOP specification

I'm not sure how you want to incorporate that information, but as of 15 October 2017, my modern public domain mobile-optimized version of the CLOS MOP specification (chapters 5 and 6 of AMOP) quite solidly obsoletes all previous versions.

Thanks Jean-Philippe, will make the update!

Awesome!! Thank you!!


TSIG canonicalization

When doing a query with TSIG
client := dns.Client{...}
msg := dns.Msg{...}
...
client.TsigSecret = map[string]string{"FooBar": "abcd"}
m.SetTsig(client.tsig, dns.HmacMD5, 300, time.Now().Unix())
r, _, err = client.Exchange(m, server)

I will get the error "dns: domain must be fully qualified" (it is actually documented that it must be). If I add a dot at the end of "FooBar" to make it a FQDN, I will get the error "dns: no secrets defined".
This is because the configured name has uppercase characters, but the TSIG needs to be put in canonical wire format and so when a lookup is done in the TsigSecret map there is no match. If I lowercase the TSIG name to "foobar." it works fine.
To be honest I think this is unexpected. If a DNS library or server reads some TSIG configuration I expect it to be able to correctly parse a valid zone name. Meaning in this case "FooBar" is matched in a canonicalized way.
I think a change is justified:

Either update the documentation to say that the TSIG name should not only be FQDN, but also be presented in its canonical form.
I prefer to make the changes to convert the zonenames from TsigSecret to their canonical form such that it will match when looking up a TSIG secret given the TSIG owner name from the DNS packet. Not sure what the best way to do this, perhaps by having a method setTSIG that will do the canonicalization?
Something else.

What would be your preference?

There is no parsing going on as you just set things in a map, but making this more explicit in the docs seems like good plan. Took some RFC searching, but https://tools.ietf.org/html/rfc4034#section-6.2 actually defines "Canonical RR Form". (TIL)

the error returned should also include the name it used for the lookup to make things slightly more obvious

Yes I know the RFC ad 4034 talks about wire format when defining canonical form, not string format.

I made a PR to at least update the documentation.
https://github.com/miekg/dns/pull/574

closed via #574


question about local gas production

In the documentation it states: Local production of gas can be fed into the network at the lowest (125 millibar) level by using a power-to-gas (P2G) installation.
Power-to-gas in ETmoses produces hydrogen, correct? Than it cannot be just fed into the grid. (e.g. It should be mixed in the right concentration). So is this correctly been taken into account in the model and described  in the documentation?
Is this the only source that can feed into the network (no green gas producer)?
@Sanne512 Is this correct with your experience?
@JeroenvdLogt; @ThomBuijs FYI
@jorisberkhout For documentation on this

Power-to-gas in ETmoses produces hydrogen, correct?

Yes.

Than it cannot be just fed into the grid. (e.g. It should be mixed in the right concentration). So is this correctly been taken into account in the model and described in the documentation?

As discussed with @Sanne512 and in the sprint meeting for sprint 2, we treat hydrogen (and other gas) purely energetically at this moment. The mixing fraction, Wobbe index etc. are not taken into account right now.
Assigning @jorisberkhout to put this in the documentation (perhaps we can have an 'assumptions' section in the 'modelling' section of the gas-network page).

Added to the documentation in https://github.com/quintel/etmoses/wiki/Gas-network/c44e7f2c348b208d1ed655ea9a74f31960495eee. Closing.


Add /gif and /giphy commands

Make them active commands, so they can be executed
while the user is interacting.
eg.: when user types /gif hi; it is recognized and executed
(shows gif picker).

This will probably be scooped up and/or closed by the changes you do this week @tjerman ?


Do not use the relative path to ember-template-compiler

PR fo fix #88

@shamcode is it possible we can try path.relative(app.project.root, require.resolve()) first, then fallback to a simple require.resolve if the compiler is not truly available? I ask because back in July I heard from a few community members who bumped into a problem using require.resolve from their mono repo so we altered it and it solved a problem for those developers at the time
https://github.com/toranb/ember-cli-hot-loader/commit/fb0a91124d200480d62af5c164e03ab62a19d162

@toranb, this changed PR, now require.resolve works like a fallback. I think that this is exactly what is described in this comment and that ember-cli do when call app.import

One issue I found testing this manually with a bigger mono repo just now
    var npmCompilerPath = path.join('ember-source', 'dist', 'ember-template-compiler.js');
    var resolvedPath = require.resolve(npmCompilerPath);
    var npmPath = path.relative(this.project.root, resolvedPath);

The npmPath returns ../node_modules/ember-source/dist/ember-template-compiler.js because the node_modules directory is a symlink (pointing back to the parent folder to reuse/share node_modules installed at the top most level of the mono repo). I'm curious if you can think of any way to solve this given I've got a local node_modules folder... yet I get the ../node_modules path

Perhaps the solution will be to add the addon options templateCompilerPath, which will be used as the path to the ember-template-compiler.js. If this option is not specified, then use the default approach:
path.relative(app.project.root, require.resolve(npmCompilerPath));

Adding this option will preserve backward compatibility and add the ability to use this awesome addon in other specific environments.
What do you think about it?

ah I'm digging it actually - so configure it if you need to override the default sorta thing. Where would you override this exactly? command line, config env or something else altogether ?

I think config env will be more familiar to the community. For example, like this:
//my-app/config/environment.js
ENV['ember-cli-hot-loader'] = {
  templateCompilerPath: require.resolve('ember-source/dist/ember-template-compiler.js')
}

@shamcode I'm down for that - you willing to update the PR in that case? I can test it manually in a few apps I know work today to emsure backwards compat

PR updated

Awesome! I'll give this a look later today! Thanks again

@shamcode I had success using this in a mono repo (with the configuration below) and for existing hot reload apps I tested it was backwards compatible :)
I've published this on npm and it's available now using v1.2.0
  if (environment === 'development') {
    ENV['ember-cli-hot-loader'] = {
      templateCompilerPath: 'node_modules/ember-source/dist/ember-template-compiler.js'
    }
  }

I'll expand the README later next week to include an example for others to better grok this extension point. Thanks again for taking the time to unlock this configuration option!


Question about error handling during completion

I've been using bingo through emacs for one day and it works really well! There is only one minor
annoyance: completion sometimes displays warnings in the editor when bingo doesn't know how to handle a certain file position. The specific warning I'm talking about is
this is a definition, of func (*foo ).bar(_ invalid type, ...) error

Would it be better to log completion errors to stderr instead of returning them as
an error response? I can send a PR to do this, just wanted to ask first because there might
be a good reason to return them to the client.

Maybe this should also be fixed upstream. It doesn't really make sense to reject completion in definition context. If you are writing a method definition like
func (f *foo) bar

it should complete known method names in scope instead.

@fjl
Please try the latest version bingo

This is not fixed, I still see the same error even with the latest version of bingo.


Create gissv.txt

Please see www.gissv.org for more information.

Only registered students and teachers at the German International School of Silicon Valley get a @gissv.org address.  A school IT administrator controls this domain.


function AlbumListController doesnt work in 1.4

I was practicing the live lessons and found that I was unable to run 01_controller.html with Angular 1.4.8.
I had to replace the way function is defined. (I checked https://docs.angularjs.org/tutorial/step_02)
Replaced,
<script type="text/javascript">
	function AlbumListController($scope){
		$scope.albums = [
			...	];
	}
</script>

by
<script type="text/javascript">
	var albumsApp = angular.module( 'albumsApp', [] );
	albumsApp.controller('AlbumListController', function($scope){
		$scope.albums = [
			...	];
	});
</script>

Just adding a comment here hoping that it would help someone who encounters the same issue

@bhajanpreets
thanks for your comment i also faced the same kind of problem

Hi!
Yes, they changed Angular. You need to do the following now:
albumsApp.controller("AlbumListController", ['$scope', function ($scope) {
   // etc
}]);

You now have to declare which things you want injected when you add it to the module. Unfortunate change, but … survivable.
HTH!

I'll update the code for all the various samples.
Thanks for pointing that out!

i appreciate your concern. keep on the great work your doing
On Fri, Feb 26, 2016 at 3:32 PM, Marc Wandschneider <
<EMAIL_ADDRESS>wrote:

I'll update the code for all the various samples.
Thanks for pointing that out!
—
Reply to this email directly or view it on GitHub
https://github.com/marcwan/AngularJSLiveLessons/issues/1#issuecomment-189258232
.

I faced the same issue. I think it's also worth mentioning that in index.html you need to include the app's name in the html tag:

I have another issue. In lesson 5 you are creating the albumservice.js. When I follow this example (have created my own example provider for customers) with this code:
`(function () {
function customerProvider () {

	var customers = [
			{ name: 'Customer-1', address: '100, First Street', city: 'New York', country: 'USA', customer_since: '3/31/2016' },
			{ name: 'Customer-2', address: 'Hoofdstraat 1092', city: 'Amsterdam', country: 'Netherlands', customer_since: '1/31/2016' },
			{ name: 'Customer-3', address: 'Hertenbergstraat 10', city: 'Tervuren', country: 'Belgium', customer_since: '2/28/2016' }
		];

	this.getCustomers = function () {
		// Return a cloned object of customers
		return JSON.parse(JSON.stringify(customers));

		// This is also possible:
		// return customers;
	};
};

rfpApp.service("customerProvider", customerProvider);

})()`
I get the error message:
Error: customerProvider is undefined @http://localhost:8080/app/controllers/customerListController.js:20:3 h/<.instantiate@http://localhost:8080/js/angular.min.js:41:396
I guess my customerProvider also need to be defined differently because of the Angular change?? But how?

Hey Eugene,
Yah, I think it's the same problem; injection works differently now, so your last line should be:
rfpApp.service("customerProvider", [ customerProvider ]);

Give that a try.  You can look in the MEAN workshop samples there for how I declare services and template off those too.


Carthage build fails on XCode 10.2 Swift 5

Please let us know what version of Moya you are using, so we can better pinpoint and/or solve your issue.
Please wrap code blocks in backticks, like so:
Moya 12.0.1

Cartfile
github "Moya/Moya"

Carthage logs
*** Checking out ReactiveSwift at "4.0.0"
Build Failed
        Task failed with exit code 65:
        /usr/bin/xcrun xcodebuild -workspace /Users/user/Desktop/com/project/Carthage/Checkouts/ReactiveSwift/ReactiveSwift.xcworkspace -scheme ReactiveSwift-iOS -configuration Release -derivedDataPath /Users/user/Library/Caches/org.carthage.CarthageKit/DerivedData/10.2_10E125/ReactiveSwift/4.0.0 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/38/fytrk84151jfgntn774nrpzw0000gn/T/ReactiveSwift SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/user/Desktop/com/project/Carthage/Checkouts/ReactiveSwift)

Most probably since Moya is still fetching  ReactiveSwift 4.0.0 in the Cartfile
github "ReactiveCocoa/ReactiveSwift" ~> 4.0

Any plans to update to 5.0.0 that supports swift 5 ?

update  ReactiveSwift to 5.0.0

You mean I should put
github "ReactiveCocoa/ReactiveSwift" ~> 5.0

in the Cartfile right ?
If i put this and run
carthage update --platform iOS --no-use-binaries

carthage freezes when trying to build the schemes and uses 7GB of RAM.
I know I should report this issues to the carthage repository but shouldn't Moya upgrade ReactiveSwift to 5.0.0?

Moya has not been updated, so you should change the Cartfile.resolved,
github "ReactiveCocoa/ReactiveSwift" "5.0.0"

Can you please list the steps ?

Cartfile

github "Moya/Moya"

2. carthage update --platform iOS --no-use-binaries
3. Build Failed
4. Change togithub "ReactiveCocoa/ReactiveSwift" ~> 5.0 in the Cartfile.resolved
5. now what ?

I'm stuck here too...

@wassimseif

shouldn't Moya upgrade ReactiveSwift to 5.0.0?

We did! It's on our development branch for now (https://github.com/Moya/Moya/pull/1817).
If you really  need this change right now, you can fork the repo and rely on development branch. You can also use the branch on this repo, but we can't guarantee it will always be stable 😅

Ahh okay.
Will do!. Thank you for the help 👍


Add loading overlay with scrollbar for issues and PRs table

Related Issue

Closes: #

Description

How Has This Been Tested?

Screenshots (if applicable)

Type of Change

[ ] Bug fix
[ ] New feature
[ ] Code style update
[ ] Breaking change
[ ] Documentation update

@addiiillll : please fill description

@addiiillll : I don't see loader on the screen (at top) when I scroll down.


add time limit when transaction retry on the server

Ⅰ. Describe what this PR did
add time limit when transaction retry on the server
Provide configuration items in file.conf :
max.commit.retry.timeout=
max.rollback.retry.timeout=
default permanent.
The retry timeout period is determined by the user. If it is not configured or configured as a negative number, it will run permanently; if configured to 0, it will be removed from the retry list on the first detection.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #824 into develop will increase coverage by 0.05%.
The diff coverage is 73.33%.

@@              Coverage Diff              @@
##             develop     #824      +/-   ##
=============================================
+ Coverage      35.59%   35.65%   +0.05%
- Complexity       924      927       +3
=============================================
  Files            217      217
  Lines           8368     8383      +15
  Branches        1010     1012       +2
=============================================
+ Hits            2979     2989      +10
- Misses          5042     5049       +7
+ Partials         347      345       -2

Impacted Files
Coverage Δ
Complexity Δ

...o/seata/server/coordinator/DefaultCoordinator.java
49.67% <73.33%> (-2.47%)
17 <1> (+1)

.../java/io/seata/server/coordinator/DefaultCore.java
57.04% <0%> (-4.23%)
21% <0%> (ø)

...eata/server/store/FileTransactionStoreManager.java
55% <0%> (+2%)
15% <0%> (ø)
:arrow_down:

...ain/java/io/seata/core/rpc/netty/ShutdownHook.java
81.25% <0%> (+25%)
8% <0%> (+2%)
: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 4efce9b...6219aa7. Read the comment docs.

Plz add new config items to the nacos-config.txt too .

Plz add new config items to the nacos-config.txt too .

OK.

@XCXCXCXCX
It shoud be retry all the time until the rollback get success, this is the guarantee of final-consistency(BASE).
Stopping retries after a certain number of times may result in transactions not being rollbacked, which is contrary to the final consistency(BASE).
So is it necessary for this PR ?
If the rollback is not necessary to be executed, then why do you need distributed transaction of Seata?

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make  the transaction to be final consistency ?

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

If retry stop, how to make the transaction to be final consistency ?
I think it shoud allways retry, even if database down or application fails , unless  there is a manual intervention to make the transaction to be final consistency， not  stop retry automatically, must stop by manual-intervention.
In addition , without artificial judgment, how to know the cause of failure, it is too hasty to stop retrying automatically after several failures.

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

If retry stop, how to make the transaction to be final consistency ?
I think it shoud allways retry, even if database down or application fails , unless there is a manual intervention to make the transaction to be final consistency， not stop retry automatically, must stop by manual-intervention.
In addition , without manual judgment, how to know the cause of failure, it is too hasty to stop retrying automatically after several failures.

This value defaults to permanent retry. When the user determines that this cannot be recovered because of a physical failure, the user can stop the retry by configuring this value.

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

If retry stop, how to make the transaction to be final consistency ?
I think it shoud allways retry, even if database down or application fails , unless there is a manual intervention to make the transaction to be final consistency， not stop retry automatically, must stop by manual-intervention.
In addition , without manual judgment, how to know the cause of failure, it is too hasty to stop retrying automatically after several failures.

This value defaults to permanent retry. When the user determines that this cannot be recovered because of a physical failure, the user can stop the retry by configuring this value.

I have a suggest, the retry provides a configuration，it is up to the user to decide whether to retry permanently.
If not permanent try again, then we can modify the retry mechanism, don't use Java ScheduledThreadPoolExecutor, we can use the Time Wheel, using an Exponential Backoff way retry

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

If retry stop, how to make the transaction to be final consistency ?
I think it shoud allways retry, even if database down or application fails , unless there is a manual intervention to make the transaction to be final consistency， not stop retry automatically, must stop by manual-intervention.
In addition , without manual judgment, how to know the cause of failure, it is too hasty to stop retrying automatically after several failures.

This value defaults to permanent retry. When the user determines that this cannot be recovered because of a physical failure, the user can stop the retry by configuring this value.

I have a suggest, the retry provides a configuration，it is up to the user to decide whether to retry permanently.
If not permanent try again, then we can modify the retry mechanism, don't use Java ScheduledThreadPoolExecutor, we can use the Time Wheel, using an Exponential Backoff way retry

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

If retry stop, how to make the transaction to be final consistency ?
I think it shoud allways retry, even if database down or application fails , unless there is a manual intervention to make the transaction to be final consistency， not stop retry automatically, must stop by manual-intervention.
In addition , without manual judgment, how to know the cause of failure, it is too hasty to stop retrying automatically after several failures.

This value defaults to permanent retry. When the user determines that this cannot be recovered because of a physical failure, the user can stop the retry by configuring this value.

I have a suggest, the retry provides a configuration，it is up to the user to decide whether to retry permanently.
If not permanent try again, then we can modify the retry mechanism, don't use Java ScheduledThreadPoolExecutor, we can use the Time Wheel, using an Exponential Backoff way retry

I think this implementation is too simple, will affect the rollback of all transactions；
The retry can not stop (unless stopped manually), which is the basic guarantee for the final consistency.
If too many failures, the retry frequency can be reduced appropriately.

@XCXCXCXCX @zhangthen This requirement is what I proposed. The default should be a permanent retry. When a database downtime or a single-point application fails to start, you need to stop retrying.

If retry stop, how to make the transaction to be final consistency ?

If the physical failure of the database hangs, it is known that it cannot be started, and how to ensure consistency.

If retry stop, how to make the transaction to be final consistency ?
I think it shoud allways retry, even if database down or application fails , unless there is a manual intervention to make the transaction to be final consistency， not stop retry automatically, must stop by manual-intervention.
In addition , without manual judgment, how to know the cause of failure, it is too hasty to stop retrying automatically after several failures.

This value defaults to permanent retry. When the user determines that this cannot be recovered because of a physical failure, the user can stop the retry by configuring this value.

I have a suggest, the retry provides a configuration，it is up to the user to decide whether to retry permanently.
If not permanent try again, then we can modify the retry mechanism, don't use Java ScheduledThreadPoolExecutor, we can use the Time Wheel, using an Exponential Backoff way retry

I think this implementation is too simple, will affect the rollback of all transactions；
The retry can not stop (unless stopped manually), which is the basic guarantee for the final consistency.
If too many failures, the retry frequency can be reduced appropriately.

agree

@zhangthen @slievrly
So I think we can stop its retry through a management entry. When the user determines that a transaction cannot be recovered due to a physical failure, it can be marked with a new failure status (eg. CANCEL) and removed from the retrying list.
In addition, it is better to use Time Wheel for situations where there may be a lot of retry tasks.
@CoffeeLatte007

@zhangthen @slievrly
So I think we can stop its retry through a management entry. When the user determines that a transaction cannot be recovered due to a physical failure, it can be marked with a new failure status (eg. CANCEL) and removed from the retrying list.
In addition, it is better to use Time Wheel for situations where there may be a lot of retry tasks.
@CoffeeLatte007

I agree this solution.

@zhangthen @slievrly
So I think we can stop its retry through a management entry. When the user determines that a transaction cannot be recovered due to a physical failure, it can be marked with a new failure status (eg. CANCEL) and removed from the retrying list.
In addition, it is better to use Time Wheel for situations where there may be a lot of retry tasks.
@CoffeeLatte007

yes, i think use time wheel and  Exponential Backoff  is better for retry

@zhangthen Currently configured for permanent retry, this modification entry is reserved for higher-order users. After the webconsole is perfected, the console UI needs to join the manual stop retry button.


Fix sha sum for switchresx

Thank you for the contribution. It was merged directly as f1cd191c6d79c629b9c8a3fa315289a45fe4a5ce to keep commit history cleaner. Your contribution is still credited to you.


Support anti-affinity on openstack through terraform server group resource

Currently , Openstack deployment using terraform doesn't guarantee that VMs are not getting created on the same blade. This could  be a serious problem in case the all control nodes get hosted on the same blade. If the blade goes down or gets disconnected from the network, all control nodes will be gone. We need a mechanism to make sure that VMs are created on different blades.
With affinity/anti-affinity policy specification a user can specify if VMs could be co-located on the same machine or force VM to be created on different machines.
A general tutorial on anti-affinity on openstack :
http://dev.cloudwatt.com/en/blog/affinity-and-anti-affinity-in-openstack.html
Here is the link that describes  terraform support for affinity/anti-affinity on Openstack.
https://www.terraform.io/docs/providers/openstack/r/compute_servergroup_v2.html
Since CCS doesn't support zones in Openstack , this is the only way to guarantee anti-affinity.

+1 we have the exact same need!

In our fork we have added affinity for our control nodes. See above:)

@gtcno Would you be willing to make a PR if you've gotten this working?


[Rosetta] Add optional timestamp field to indexer response

This pull request adds an optional timestamp field to the indexer response type in the rosetta_models/block_transaction.ml file. This field is not part of the official spec and it's optional, only being included if the Rosetta node is run with the --include-timestamp flag.

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-nightly-me

@joaosreis looks like Rosetta integration tests are still breaking on compatible. Do you happen to know what is the reason? Can we again patch them before merging this one?


Cannot import pyCmpr

Thank you for your repository. I'm having trouble running it on Windows. When I try to import the library pyCmpr, I encounter an error stating: 'ModuleNotFoundError: No module named 'pyCmpr' command. Your assistance here is invaluable. Thank you in advance.

I encountered the same issue when trying to build and import the pyCmpr module on Windows. After some modifications to the CMake configuration, I was able to resolve the problem. I’ve forked the project, applied the necessary changes, and created a release that should work for you as well.
You can download the updated version from this link:
https://github.com/miragessee/Scyther/releases/tag/1.0.0
I hope this helps! Feel free to reach out if you have any further questions.


Cannot view or create review comments for PR

Extension version: 0.101.2024110711

VSCode Version: 1.96.0-insider (4a98be2738be4ad8647feb52d1e6845e06515dea, 2024-11-08T09:56:49.748Z)

OS: Windows 11 23H2

Repository Clone Configuration (single repository/fork of an upstream repository): fork of upstream repo

Github Product (Github.com/Github Enterprise version x.x.x): Github.com

Steps to Reproduce:

Open file changed in PR, add and then try to save a comment
Error notification appears "Creating comment failed: Error: GraphQL error: Fragment ReviewComment was used, but not defined"

In logs:
2024-11-08 17:00:51.377 [error] GitHubRepository+0> Error querying GraphQL API: GraphQL error: Fragment ReviewComment was used, but not defined. useAndDefineFragment
2024-11-08 17:00:51.881 [error] GitHubRepository+0> Error querying GraphQL API: GraphQL error: Fragment ReviewComment was used, but not defined. useAndDefineFragment
2024-11-08 17:00:51.881 [error] PullRequestModel> Failed to get pull request review comments: Error: GraphQL error: Fragment ReviewComment was used, but not defined

I was thinking it was duplicate of #6441 but that one verified as fixed, and commenting worked fine for me on Nov 6 (2 days ago, before that fix)

Also getting this same error as of today.

Same here, tried to use latest release and pre-release version with same error result.

Same here, getting exactly the same error. It just happened today and was working fine yesterday.

I'm getting something very similar:

@alexr00 seems to be one more regression in the new release (either v100 or v100.1)

I’m also encountering the same error since today.

Same exact issue/error since yesterday.

Same problem

same problem

same issue

Same issue

Same as #6467

Same issue

Same issue

getting same issue

Same issue. Upvote

I have the same problem, I tried to go back to 0.100 but then I get another error:

I have the same problem, I tried to go back to 0.100 but then I get another error:

0.98.0 worked for me

same

0.100.0 worked for me (arch linux).

same issue here as well.

0.100 worked. (mac silicon)

Same here, rolled back to 0.100.0 and the problem doesn't happen

Same issue on Arch

Same issue for me...

The same issue, rolled back to 0.100.1 worked on Mac intel

I had same issue on Windows 11 Pro

I had to go back to version 0.100.0


Update blocklist + improve performance greatly (200 times faster :rocket: )

Hello :wave:
Thanks for this nice gem!
I just started using it and saw a couple things to improve/update so here is a little PR with the following improvements:

Updated the blocklist to latest version of disposable-email-domains
Improve performance greatly (#include? is now 200 times faster :rocket:) by using a Set instead of Array + split instead of regexp. :warning: This is a slightly breaking change as the list is not longer an array but most method will still work, this is still better I believe. Please see below the benchmark comparing original vs new version.
Update outdated ruby version in travis.yml (here is the :heavy_check_mark:  green build)
The #include? method now really returns a Boolean as explained in the readme (instead of String or nil currently)
The list can now easily be edited to add missing domains or remove some (I also updated the readme with instructions and added a test for this case)
I also added support for subdomains, if a providers supports multiple subdomains, the gem will find now find it in the list.
Improved the rake task to automatically pull the submodule and update the ruby file
I bumped the version to 0.2 but let me know if you prefer something else
I also added the fix for Ruby 3 from #8

For people who wants to use this branch before it is merged, use this in your Gemfile:
gem 'disposable_mail', github: 'jarthod/disposable_mail', branch: 'update-list-improve-performance' # https://github.com/oesgalha/disposable_mail/pull/7

Benchmark results:
require './lib/disposable_mail/disposable'
require 'benchmark'

N = 10
emails = DisposableMail.list.map {|domain| "test@#{domain}"}

Benchmark.bmbm do |x|
  x.report("original") { N.times { emails.each { |e| DisposableMail.include?(e) } } }
  x.report("new") { N.times { emails.each { |e| DisposableMail.include2?(e) } } }
end

# > ruby benchmark.rb
# Rehearsal --------------------------------------------
# original   2.306290   0.003521   2.309811 (  2.309856)
# new        0.011054   0.000010   0.011064 (  0.011065)
# ----------------------------------- total: 2.320875sec

#                user     system      total        real
# original   2.209011   0.000000   2.209011 (  2.209096)
# new        0.010861   0.000000   0.010861 (  0.010884)

Great job ;)

For the record I just added the ruby 3 fix from #8 and #9 (thanks @mkrajewski90 and @Annedj).
I've been using this branch successfully for more than a year, any way to get this merged @oesgalha?
Thanks :pray:

@jarthod This branch seems to cause problems with Rails 6.1.

@tbsvttr what problem? I am currently using it on Rails 7.0 and have been using it on Rails 6.1 for a while before that.

@jarthod errors.add now only takes two parameters. Blew me up as I updated from Rails 6.0.X to Rails 6.1.X. Monkey patched it.

@tbsvttr ah ok, I'm using Mongoid instead of AR so maybe they probably kept the compatibility there. Can you share your monkeypatch for others maybe? If it doesn't break compatibilité with older version I'll update the branch.

@jarthod Where do you usually add the new domains to the existing list? Is it on initalization of the rails app or does it have to be added manually anytime we perform a check?

@IncSow With this branch it can be done at initialization yes, in my case I put it in my user.rb model file (at the top of the file not inside a method so it's only done once) simply because that's where I used it but an initializer will also work fine. Here is what I'm currently adding:
DisposableMail.list.merge %w(cnxingye.com threepp.com mailper.com acrossgracealley.com thichanthit.com tempmailin.com digital10network.com musiccode.me ryteto.me livinginsurance.co.uk onekisspresave.com norwegischlernen.info emailnax.com afia.pro aramask.com camplvad.com clout.wiki consultant.com devsquad.asia duscore.com finews.biz gufum.com hexi.pics introace.com lyft.live merepost.com realremedyblog.com socam.me tutuapp.bid vanturtransfer.com)

class User
# ...


Broken graph state after removing node

Bug report
cytoscapeobj.graph.remove_node(node) removes more nodes than just the node passed as the parameter. This also affects cytoscapeobj.graph.remove_node_by_id(node_id) which uses it.
https://github.com/cytoscape/ipycytoscape/blob/c72f39d5382711f22ffd1dfe0f5754602f63c9af/ipycytoscape/cytoscape.py#L287-L305
Issues seems to lie specificly in this call:
https://github.com/cytoscape/ipycytoscape/blob/c72f39d5382711f22ffd1dfe0f5754602f63c9af/ipycytoscape/cytoscape.py#L296
Code for reproduction

Open 'DAG example' notebook.

Execute all existing cells in order. The graph would look like this

Observe the list of existing nodes

cytoscapeobj.graph.nodes
_______________________
[Node(data={'id': 'n0'}, position={}),
 Node(data={'id': 'n1'}, position={}),
 Node(data={'id': 'n2'}, position={}),
 Node(data={'id': 'n3'}, position={}),
 Node(data={'id': 'n4'}, position={}),
 Node(data={'id': 'n5'}, position={}),
 Node(data={'id': 'n6'}, position={}),
 Node(data={'id': 'n7'}, position={}),
 Node(data={'id': 'n8'}, position={}),
 Node(data={'id': 'n9'}, position={}),
 Node(data={'id': 'n10'}, position={}),
 Node(data={'id': 'n11'}, position={}),
 Node(data={'id': 'n12'}, position={}),
 Node(data={'id': 'n13'}, position={}),
 Node(data={'id': 'n14'}, position={}),
 Node(data={'id': 'n15'}, position={}),
 Node(data={'id': 'n16'}, position={})]

Remove node with id n3 (the bottom-right child node in the left-most graph)

cytoscapeobj.graph.remove_node_by_id('n3')

The graph now looks like this:

Alternatively, you can remove the node from the list of nodes (which is what cytoscapeobj.graph.remove_node does internally) to the same effect:
cytoscapeobj.graph.nodes.remove(cytoscapeobj.graph.nodes[3])

Inspect the list of nodes

cytoscapeobj.graph.nodes
_______________________
[Node(data={'id': 'n0'}, position={}),
 Node(data={'id': 'n1'}, position={}),
 Node(data={'id': 'n2'}, position={}),
 Node(data={'id': 'n4'}, position={}, removed=True),
 Node(data={'id': 'n5'}, position={}, removed=True),
 Node(data={'id': 'n6'}, position={}, removed=True),
 Node(data={'id': 'n7'}, position={}, removed=True),
 Node(data={'id': 'n8'}, position={}, removed=True),
 Node(data={'id': 'n9'}, position={}, removed=True),
 Node(data={'id': 'n10'}, position={}, removed=True),
 Node(data={'id': 'n11'}, position={}, removed=True),
 Node(data={'id': 'n12'}, position={}, removed=True),
 Node(data={'id': 'n13'}, position={}, removed=True),
 Node(data={'id': 'n14'}, position={}, removed=True),
 Node(data={'id': 'n15'}, position={}, removed=True),
 Node(data={'id': 'n16'}, position={}, removed=True)]
...

JS console logs indicate an error immediately after running cytoscapeobj.graph.remove_node_by_id('n3'):

Uncaught (in promise) Error: Can not create second element with ID `n4`
Uncaught (in promise) Error: Can not create second element with ID `n4`
Uncaught (in promise) Error: Can not create edge `a1b4ae96-fe81-4363-ba59-23298b1a10e3` with nonexistant source `n4`

Is this the intended behavior?
Actual outcome
Nodes with ids "higher" than node requested to be deleted are getting removed=True on them and disappear from the graph.
Expected outcome
Maybe it would make more sense to make this optional, and only delete a single node by default?
Version Info

runtime environment: Binder (link above)

ipycytoscape version : 1.3.2
Python version: 3.7.12
JupyterLab version: 3.3.1

BTW, same error with edges:
In the same 'DAG exampe' notebook, run
cytoscapeobj.graph.remove_edge_by_id('n1', 'n3')

cytoscapeobj.graph.edges
_______________________
[Edge(data={'source': 'n0', 'target': 'n1'}),
 Edge(data={'source': 'n1', 'target': 'n2'}),
 Edge(data={'source': 'n4', 'target': 'n5'}, removed=True),
 Edge(data={'source': 'n4', 'target': 'n6'}, removed=True),
 Edge(data={'source': 'n6', 'target': 'n7'}, removed=True),
 Edge(data={'source': 'n6', 'target': 'n8'}, removed=True),
 Edge(data={'source': 'n8', 'target': 'n9'}, removed=True),
 Edge(data={'source': 'n8', 'target': 'n10'}, removed=True),
 Edge(data={'source': 'n11', 'target': 'n12'}, removed=True),
 Edge(data={'source': 'n12', 'target': 'n13'}, removed=True),
 Edge(data={'source': 'n13', 'target': 'n14'}, removed=True),
 Edge(data={'source': 'n13', 'target': 'n15'}, removed=True)]

Clearly, there is an issue calling remove method of ipycytoscape.cytoscape.Graph.nodes and ipycytoscape.cytoscape.Graph.edges (both of the spectate.models.List type)

Hey @ktaletsk, thanks for opening the issue and sorry for taking a while to reply to it.
The person who contributed this code was @MridulS, maybe they're interested in picking this up? Or just chiming in.
But anyway, that's a great found! Thank you very much for contributing with the issue, lately I haven't had much time to hack on ipycytoscape, but this issue is definitely up in my list.
I can try to help you if you're interested in tackling. I saw you're in LA? I'm here for the week! If you want we could even meet in real life.
Cheers.

Yeah this doesn't look right, thanks for the report.
I don't have much bandwidth for this right now but I can get back to this in a couple of weeks :) Feel free to submit a PR to fix this if you get the time before that.

@marimeireles @MridulS here are some findings upon debugging the issue

It only manifests itself if widget is rendered. Consider these 3 examples based on the code from the test suite:

Initial setupfrom ipycytoscape.cytoscape import Edge, Graph, Node, CytoscapeWidget
data = {
    "nodes": [
        {"data": {"id": "0"}},
        {"data": {"id": "1"}},
        {"data": {"id": "2"}},
    ],
    "edges": [
        {"data": {"source": "0", "target": "1", "weight": "1"}},
        {"data": {"source": "0", "target": "1", "weight": "2"}},
        {"data": {"source": "1", "target": "0"}},
        {"data": {"source": "1", "target": "2"}},
        {"data": {"source": "2", "target": "0"}},
    ],
}

Create graph, removed node. Works as expectedgraph = Graph()
graph.add_graph_from_json(data)
graph.remove_node_by_id("0")
graph.nodes
>> [Node(data={'id': '1'}, position={}), Node(data={'id': '2'}, position={})]

Same thing, but inside the CytoscapeWidget object. Still workswidget = CytoscapeWidget()
widget.graph = Graph()
widget.graph.add_graph_from_json(data)
widget.graph.remove_node_by_id("0")
widget.graph.nodes
>> [Node(data={'id': '1'}, position={}), Node(data={'id': '2'}, position={})]

Exactly the same thing, but render the widget before deleting the node. Then we observer the bug behaviorwidget = CytoscapeWidget()
widget.graph = Graph()
widget.graph.add_graph_from_json(data)

# Render widget
widget

widget.graph.remove_node_by_id("0")
widget.graph.nodes
>>[Node(data={'id': '1'}, position={}, removed=True), Node(data={'id': '2'}, position={}, removed=True)]

With that, I think we should search for an error somewhere in the Jupyter widget.

It is not completely clear to me what's happening in CytoscapeView.removeNodeView and CytoscapeView.removeEdgeView

removeNodeView(nodeView: any) {
    nodeView.model.set('removed', true);
    nodeView.remove();
  }

I tried commenting out setting the model - the first line in the function - and the behavior was better, yet still incorrect. I was able to remove only the requested node from the list, and the state of the graph was as expected - no nodes with incorrectly set "removed: true". However, the widget was not updated automatically and I had to manually rerun the cell with the widget to get the new state.
I would like to continue debugging, but I have 2 issues:

What is the type of the nodeView input argument in CytoscapeView.removeNodeView? It is set to any which makes it impossible to inspect the methods of this object.
Who and where is calling CytoscapeView.removeNodeView?

@marimeireles @MridulS I would like to fix this issue, but I'm stuck. Could you give some feedback on my comment above?

I have run into this issue as well trying to update ipycytoscape widgets rendered in Jupyter. Removing any single node removes all the nodes rendered in the graph and sets each node to removed=True. Setting the nodes back manually to removed=False does not re-add them. Is there intention to address this bug?

I encountered the same issue and it's networkx related. After removing nodes, the networkx graph becomes invalid. Just run the code below (it's using networkx v3.3):
import networkx as nx

G = nx.path_graph(5)
nx.set_node_attributes(G, {i: i for i in range(5)}, 'idx')
G.remove_node(2)
idx3 = [i for i, node in enumerate(G.nodes) if G.nodes[node]["idx"] == 4][0]
print(G.nodes[idx3]["idx"])


There's a better pre-made mocha config that benefits 5.5.2 users immensely

Flump created another useful file for the community that we use now.
Some users go the Haxchi-less route (A few do at least) and so their only use of CFW would be Mocha. But Mocha brings the user back to the home menu after being launched which can be troublesome since the 5.5.2 browser exploit still isn't perfect. The user could also launch mii maker to get back into homebrew launcher, but there's a better pre-made mocha config that we use in the assistence channel now. With this config, it brings the user back into homebrew launcher after launching mocha. It also removes the need to ever see the config menu so you won't have to tell the user what config options to choose. This config can be provided in the file prep section which would go in SD:/wiiu/apps/mocha/
You can get the config here: https://www.dropbox.com/sh/gxkf72jia1adpyg/AADkYkaqVP-nf68Ng8Lvga6ha/CONFIGS FOR HAXCHI %26 MOCHA/Mocha/config.ini?dl=0

Ah, this would run the sig patches without relaunching, then I assume they could just exit the HBL to the system menu if desired?


Do not attempt to cast nil errors.

@bigkraig, this checks out in my cluster. Please review when you can.


Nexus Proxy url

I need to use our own Nexus proxy url instead of update center url. Currently I am getting below error. How to resolve?
Downloading: http://repo.maven.apache.org/maven2/org/jenkins-ci/tools/maven-hpi-plugin/2.2/maven-hpi-plugin-2.2.pom
Plugin org.jenkins-ci.tools:maven-hpi-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.jenkins-ci.tools:maven-hpi-plugin:jar:2.2: Could not transfer artifact org.jenkins-ci.tools:maven-hpi-plugin:pom:2.2 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): repo.jenkins-ci.org: Name or service not known: Unknown host repo.jenkins-ci.org: Name or service not known -> [Help 1]
[21:34:27][Step 1/1] [ERROR]

It can be specified by a Maven setting file which can be passed as an argument.
You can specify multiple update sites there.
But yes, you need to connect to Jenkins Maven Repo or its mirror if you want to run Custom WAR Packager. We do not mirror all our artifacts to Maven Central

Closing since there is no follow-up from the requester


Weird log levels - Possible update of log level from messages

A set of log messages that could be updated the levels of logs.

- Why this are warning?
- Maybe an info level?


false-positive home-check in inventory.xml if home was deinstalled

Installation of GI- or DB-Home check inventory.xml to ensure the same home is not already installed. If the home once existed but was deinstalled, the check might erroneously assume the home is still there because it ignores the REMOVED=T flag.

https://github.com/oravirt/ansible-oracle/pull/437


Salus does not apper in integrations

After installing salus in hacs, salus does'nt apper in integrations. Also triying with coping folder in custom components.

Solved: clean browser cache!


Add indicator of connected clients to browser UI

It would be nice to see what clients are connected to the browser viewer.
We could put something in the header, next to the logo/title maybe.
For now this could just say "N clients connected"

Technical approach

Update the Web Socket server (in startCollector.cjs) to send a message to the viewer client when a new non-viewer clients connect.

We handle client connections in the on('connected') event handler
This message sent to the viewer can be something like { type: 'NewConnection', serviceName: 'foo' }.
The serviceName data we pass can come from the path part of the WS connection request (i.e., ws://<IP_ADDRESS>/this-part-here)

Update the browser viewer Web Socket client (in CollectorClient.ts) to handle type: 'NewConnection' messages

We can increment a state-held count of connection which will be displayed on the front-end

Note: Web socket clients will not send a 'close' event to the server implicitly when they are terminated (e.g., refreshing the client browser app/reloading the node app).
Refreshing/reloading the app will cause a new WS connection to be made to the server.  The original WS connection will only be dropped when it times out on the server.
We should therefore ensure that multiple connections from an given serviceName are only counted once...

We also want to handle when clients disconnect, meaning that we might need to keep a record of all connections that a single serviceName has, and only decrement the number when they are all removed

E.g.,

🕸 Client A (website) connects with service name client-A
👀 Browser viewer "connected clients" count increments to 1
💻 Client B (node app) connects with service name client-B
👀 Browser viewer "connected clients" count increments to 2
🙎 User refreshes browser running client A
🕸 Client A (website) connects with service name client-A
👀 Browser viewer "connected clients" count stays at 2, but registers an additional client-A connection internally
🙎 User closes browser running client A
⏲ After a while, the first client-A connection is dropped due to unavailability of that socket
👀 Browser viewer "connected clients" count stays at 2 since there is still one other client-A connection and the client-B one
⏲ After another while, the second client-A connection is dropped due to unavailability of that socket
👀 Browser viewer "connected clients" decrements to 1, since there are no longer any client-A connections, only one client-B

I think that's how it woks anyway... i've gotten myself into all kinds of jams with socket based client management.

We can extend the current system filter drop down to:
a) Show connected clients (sources) and their connection status
b) Allow filtering of traces from these sources
Something like:


PURCHASE-1228, PURCHASE-1239, PURCHASE-1234, PURCHASE-1240, PURCHASE-1241: Fix spacing in ArtworkHistory component and make OtherWorks to spec

Bunch of small changes here that we discovered during our last QA session.
Links to the Jira tickets:

https://artsyproduct.atlassian.net/browse/PURCHASE-1228 (Add spacing between "Provenance"/"Exhibition History" sections)
https://artsyproduct.atlassian.net/browse/PURCHASE-1239 (Remove extra margin above nav bar)
https://artsyproduct.atlassian.net/browse/PURCHASE-1234 (Reduce spacing between "Provenance"/"Exhibition History" labels and their descriptions)
https://artsyproduct.atlassian.net/browse/PURCHASE-1241 (Only show 6 works in the "Other Works" sections)
https://artsyproduct.atlassian.net/browse/PURCHASE-1240 (Left-align titles in "Other Works" sections)

Left-aligned "Other Works"

Fixed line height on ArtworkHistory section

Note: Still investigating the odd spacing at the bottom of the ReadMore component, but will leave that for a separate ticket.

Fails

:no_entry_sign:
No CHANGELOG added.

  Generated by :no_entry_sign: dangerJS


Issue 593 | Client: deprecate stop in favor of cancel

Summary
Deprecate Job.stop in favor of Job.cancel

Btw @IceKhan13 we are going to need to update the catalog too, right?

@Tansito , right, once we cut new release we will need to update catalog


Entering two consecutive, space separated 'L'/'l' leeds to display and editor corruption

Issue Type: Bug
Just enter one of the two sequences:
L L
l l
The second L/l jumps to the left into the first, display is corrupted, editing and code parsing (e.g. for IntelliSense) are failing. If you use two spaces or a tab instead of a single space to separate the two Ls, everything is alright.
It is very annoying, e.g. writing in Java
JLabel lbl
and the line is corrupt. You have to replace the space with two of them or a tab to get working code.
VS Code version: Code 1.63.0 (7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e, 2021-12-07T06:26:56.179Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: Yes

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz (12 x 2904)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.90GB (10.53GB free)

Process Argv
--crash-reporter-id d899b93d-4007-4aa8-ac10-edf99c5d948b

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

language-x86-64-assembly
13x
3.0.0

gitlens
eam
11.7.0

php-debug
fel
1.22.0

php-pack
fel
1.0.2

remote-ssh
ms-
0.70.0

remote-ssh-edit
ms-
0.70.0

remote-wsl
ms-
0.63.13

java
red
1.2.0

vscodeintellicode
Vis
1.2.15

vscode-maven
vsc
0.34.1

Okay, it's a duplicate of #106583. I encountered the problem right after an update so I thought it must be new. I checked the last pages of the bug tracker but no entries more than a year in the past. Now I'm using the mentioned workaround. But it's disappointing that the wrong behaviour of the editor (e.g. wrong placing of caret after this ligature) won't be fixed.


Fixing Start-Container -Attach to respect TTY

This matches the behavior of the docker client, where TTY is queried from the container config.

LGMT


Shows gaps not present on my profile

When I generate the image for myself, there should be no gaps shown since April 2014, but I see 4 in 2022, 2 in 2021, 1 in 2019, 1 in 2018, 2 in 2017, and 1 in 2016. You can click back on my profile to verify - do note that sometimes Github messes up the history, and it recovers a few days later - so if you're caching too aggressively, that might be the issue.
Is this something you can fix?

Hi @ljharb !
I checked your profile and found that there are indeed the gaps you pointed out.

However, when I view the same contribution graph without logging into my GitHub account,  there are no gaps display😮:

So, I think this issue is related to the GitHub Access Token. Thank you for your feedback, I will find a solution and fix that.

Were you able to fix this?

To be honest, I don't know the exact cause of this problem yet...
I 'm not spending time on this project right now. When I get back into it, I will reopen this issue.

Understood. Any reason not to leave it open until then?


TSC Open Meeting: April 4, 2019

NOTE: This meeting is on Thursday at 9am - 10am PT, 5pm-6pm UTC
Zoom Meeting link: https://zoom.us/j/975841675
In order to give some more visibility into the topics we cover in the TSC meetings here is the planned agenda for the next meeting.  Hopefully this will allow people to plan to attend meetings for topics that they have an interest in.  And for folks who cannot attend they can comment on this issue prior to the meeting.  Feel free to suggest other potential agenda topics.
Proposed Agenda

Topic
Owner
Decision/NextStep

Review open PRs

Issues labelled review
@OAI/tsc

/cc @OAI/tsc Please add other items as you see fit

Are there minutes or a recording of this meeting?


can anyone explain me about "Copy the library (.a) you have compiled following the official documentation inside the exported Xcode project. You must override the 'your_project_name.a' file with this file." ??

I'm trying to add admob in ios but i'm confused what to do.
can anyone explain in details ??

https://github.com/atologist-pratik/CustomBuildForGodot


Scroll webview to top if unmatched fragment is #top

In the HTML Standard, section 7.11.9 “Navigating to a fragment” states that when looking for the indicated part of the document, if the fragment doesn’t match any element, but is the special value “top”, then the top of the document is indicated:

If decodedFragment is an ASCII case-insensitive match for the string top, then the indicated part of the document is the top of the document; return.

This PR updates the logic for webviews to follow the spec. Can be tested by putting a link to #top in a Markdown document and previewing the document.
cc @mjbvz

Thanks!


Test react-on-webpacker package

The babel preset needs to be refined, but the configuration swap works perfectly.

This change is

@Judahmeek @gscarv13 can you update this PR? I just updated https://github.com/rails/webpacker/pull/3224/files so we could have a demo of all the react stuff is in the package https://github.com/shakacode/react-on-webpacker
And we need some docs for that.

@Judahmeek can we get this updated ASAP.

@mrtnzlml @Judahmeek @tomdracz,
Is this PR still useful? Or should this:

Be within shakapacker
Be within documentation


Update index.html

Better use your "own" class name ;-)

Thank you, I didn't notice this detail :)


Paginate services

Paginate the /service endpoint

As I mentioned a few days ago: there's been no further discussion so I'm going to go ahead and close this PR.


Added class diagram example to README.md

I start with the README.md and then the documentation in gh-pages. Right now the README.md is finished. As for the class diagram positioning issue, still need more time to understand the code and identify the positioning issue with some examples.
The table code in markdown is reformated for readability. Preformated code is not indented since if indented, the rendered page also shows unnecessary indentation. And added a <p> tag to the first image to make it look better.
I have no access to the site where the other two example images are hold, so I put it in the docs/img directory, hope it's ok.

Images in docs/img is ok. Thx again! Merging!


Nice to have: horizontal speed plot in Grafana

During a summerstorm PD3EGE launched an 4fsk tracker. It would be really nice to re-view the horizontal speed in Grafana too.
https://grafana.v2.sondehub.org/d/HJgOZLq7k/basic?var-Payload=PD3EGE&from=1688545183000&to=now&orgId=1&refresh=1m
Thanks,

Could you raise this over at https://github.com/projecthorus/sondehub-infra please - thats the more correct location for grafana issues.


Mixin injection error on biomemakeover-FABRIC-1.19.3-1.7.1 relating to "taniwha"

I'm not sure exactly what that is, I'm guessing a library of some sort? It was referenced in the crash log and I found a jar for it inside this mod's jar. Reading the crash log, it seems to be related to a mixin injection not working. It crashes on loading.
Minecraft version 1.19.3
Java 17.0.3 from Eclipse Adoptium
Windows 10
+Many other mods (see log below)
Log file here: [LINK]

Yeah - That's my library.
Looks to be BM and another mod trying to do the same redirect in the CropBlock class.
If you happen to work out what mod that is, that would be very helpful in tracking it down, but I can look into it another time.
Thanks for the report.

I removed your mod for now. I'm not sure what tools there are to figure out what other mods are redirecting in that class. I have only very basic experience with Mixins.

This should be fixed in future versions.


Data loaders best practices guide

Create a best practices guide to data loaders

@awsankur  https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-s3-connector-pytorch/

https://aws.amazon.com/jp/blogs/aws/new-amazon-s3-express-one-zone-high-performance-storage-class/


Equinix Metal API errors aren't properly handled, causing panics

Feb 13 20:00:00 rhea scale[622512]: Work summary:
Feb 13 20:00:00 rhea scale[622512]: System("aarch64-linux") Small = 34642
Feb 13 20:00:00 rhea scale[622512]: System("aarch64-linux") BigParallel = 61
Feb 13 20:00:00 rhea scale[622512]: System("x86_64-linux") Small = 2934
Feb 13 20:00:00 rhea scale[622512]: System("x86_64-linux") BigParallel = 1
Feb 13 20:00:01 rhea scale[622512]: Creating: HardwarePlan {
Feb 13 20:00:01 rhea scale[622512]:     bid: 2.0,
Feb 13 20:00:01 rhea scale[622512]:     plan: "c3.large.arm64",
Feb 13 20:00:01 rhea scale[622512]:     netboot_url: "https://netboot.nixos.org/dispatch/hydra/hydra.nixos.org/equinix-metal-builders/main/c3-large-arm",
Feb 13 20:00:01 rhea scale[622512]: }
Feb 13 20:00:01 rhea scale[622512]: Creating: HardwarePlan {
Feb 13 20:00:01 rhea scale[622512]:     bid: 2.0,
Feb 13 20:00:01 rhea scale[622512]:     plan: "c3.large.arm64",
Feb 13 20:00:01 rhea scale[622512]:     netboot_url: "https://netboot.nixos.org/dispatch/hydra/hydra.nixos.org/equinix-metal-builders/main/c3-large-arm",
Feb 13 20:00:01 rhea scale[622512]: }
Feb 13 20:00:02 rhea scale[622512]: Creating: HardwarePlan {
Feb 13 20:00:02 rhea scale[622512]:     bid: 2.0,
Feb 13 20:00:02 rhea scale[622512]:     plan: "c3.large.arm64",
Feb 13 20:00:02 rhea scale[622512]:     netboot_url: "https://netboot.nixos.org/dispatch/hydra/hydra.nixos.org/equinix-metal-builders/main/c3-large-arm",
Feb 13 20:00:02 rhea scale[622512]: }
Feb 13 20:00:03 rhea scale[622512]: Error: failed to parse json, here's the raw content: Object {
Feb 13 20:00:03 rhea scale[622512]:     "errors": Array [
Feb 13 20:00:03 rhea scale[622512]:         String("The facility da11 has no provisionable c3.large.arm64 servers at the requested price"),
Feb 13 20:00:03 rhea scale[622512]:     ],
Feb 13 20:00:03 rhea scale[622512]: }
Feb 13 20:00:03 rhea scale[622512]: Caused by:
Feb 13 20:00:03 rhea scale[622512]:     missing field `hostname` at line 1 column 99
Feb 13 20:00:03 rhea scale[622512]: Location:
Feb 13 20:00:03 rhea scale[622512]:     src/device.rs:92:10

This is causing the service to fail with an exit code that can't be distinguished from a "real" error - when really this is more of an expected condition. It should be properly recognized and changed to either a success code or an exit code that we can filter in our monitoring for non-critical failures.

Another one:
Feb 13 19:40:00 rhea scale[615235]: Work summary:
Feb 13 19:40:00 rhea scale[615235]: System("aarch64-linux") BigParallel = 61
Feb 13 19:40:00 rhea scale[615235]: System("aarch64-linux") Small = 34677
Feb 13 19:40:00 rhea scale[615235]: System("x86_64-linux") BigParallel = 2
Feb 13 19:40:00 rhea scale[615235]: System("x86_64-linux") Small = 1846
Feb 13 19:40:01 rhea scale[615235]: Creating: HardwarePlan {
Feb 13 19:40:01 rhea scale[615235]:     bid: 2.0,
Feb 13 19:40:01 rhea scale[615235]:     plan: "c3.large.arm64",
Feb 13 19:40:01 rhea scale[615235]:     netboot_url: "https://netboot.nixos.org/dispatch/hydra/hydra.nixos.org/equinix-metal-builders/main/c3-large-arm--big-parallel",
Feb 13 19:40:01 rhea scale[615235]: }
Feb 13 19:40:01 rhea scale[615235]: Error: failed to parse json, here's the raw content: Object {
Feb 13 19:40:01 rhea scale[615235]:     "errors": Array [
Feb 13 19:40:01 rhea scale[615235]:         String("There aren't available servers at any facility"),
Feb 13 19:40:01 rhea scale[615235]:     ],
Feb 13 19:40:01 rhea scale[615235]: }
Feb 13 19:40:01 rhea scale[615235]: Caused by:
Feb 13 19:40:01 rhea scale[615235]:     missing field `hostname` at line 1 column 61
Feb 13 19:40:01 rhea scale[615235]: Location:
Feb 13 19:40:01 rhea scale[615235]:     src/device.rs:92:10
Feb 13 19:40:01 rhea systemd[1]: hydra-scale-equinix-metal.service: Main process exited, code=exited, status=1/FAILURE


Babywise & Nick2bad4u custom trims

I've created some simple trims and organised the readme in a way to show the default trims and my trims in a different section, i thought it looked nice for the main page and format could be reused for other contributors to keep the main page readme nice and neat
I will be adding more trims in the future (the readme table under the babywise section has spacing placeholders for future additions)
If future contributors use the table format i've used, try not to exceed 7 columns or the table will not fit correctly (depending on username length -> see readme for reference)

Thank you for this! Will take a look through, but at first glance looks very well put together!

Thank you!, i also just added all of the trims that Nick2bad4u added in his issue request, i've committed onto this branch to combine the work

Thanks again for this! And sorry it took so long. I'm working on something to make it a little easier to see (and upload trims) going forward. :)

No worries! haha sounds good :P, I don't have much experience with runescape plugin dev yet, but I might be able to help out if you need a hand. I'm always happy to help and learn some new things along the way! :) I'm in school for computer science, and the semester is almost over so i'd be more than happy to lend a hand. Im most comfortable in C++ and C#, but ive done a little java and javascript dev as well.
I did already start adding a few new trims locally on my branch while I was waiting for you to approve it, so i might have another pull request with trims coming in again shortly haha

dang, nice job with the website!

Haha, thank you! Just wanted to get something up to try and remove some pain. No longer need to create your own examples. :)
I'm sorry you spent so much time doing it!
But also, feel free to contribute if you see an issue/improvement. Or reach out if you need a hand with plugin dev. :)

all good haha, I had fun with it :), was actually looking forward to submitting some more :P so i was lookin at ur new instructions ;)
Thanks! Will do! I have a few plugin ideas floating around, i'll reach out when i come up with something concrete!

I would like to ask if you've got any tips or resources for learning node and react for webapps, I have a personal project im working on focusing on both but first i'm in the process of learning them. Ideally i want to deploy it using docker

Honestly, https://react.dev/learn is such a good resource. You'll be up to speed pretty quick.
I personally wouldn't spend a lot of time getting to know the ins and outs of JavaScript. It's stuff you can pick up as you go. I think just build simple apps, compare them to what others are doing and try to understand why.
For the most part, React is fairly simple. You just need to understand the 'lifecycles'. What causes a render, what is 'state', etc.
As for Node, I know barely anything. I just Google it as I go. :) Hahah.

haha alright, that helps, i have been focusing a bit too much on javascript learning, Thanks!

one more question, more about the custom trims, if i did add a markdown file inside of the "babywise" trim folder, would that be ok, or will that cause any problems for you? I love the website integration, but i wanted to also include a small readme inside my trims section just in case someone downloads the trims as a zip, it would have a structure similar to this image, just wanted to ask first

Won't cause any issues. It picks up .png, .svg, .jpg & .jpeg files. Everything else is skipped over. :)

sweet :)


Added example  python_reconstruct.py + Corrected python3.lark

This shows how one might handle a postlexer (more specifically the Indenter) while reconstructing. It also updates the stubs.
The changes to python3.lark are to make it actually work. I am not sure if these changes are complete, but without them, the recosntructed output has syntatic differences:

def test(a, b):  would become def test(a,b,/,)
{a:b, c:d, e:f} might become {c:b,**c,**d,e:f,}
for a in range(): might become for a, in range():

There might be more special cases, but the worst I think is fixed

Very nice!
There is a bug you would have noticed if you had tried to run the output.
actions[1:] turns into actions[1]

Very nice!
There is a bug you would have noticed if you had tried to run the output.
actions[1:] turns into actions[1]

Yeah, I should have attempted to run it. But I assume we will find more and more bugs of this kind while this grammar is in used. As you may have noticed, my recent interested in GrammarLoader and Reconstructur is fueled by https://github.com/MegaIng/syntax-extensions-base/ , which is a project that uses lark to exend the python grammar. I just finished the first proof of concept non-trivial extension: https://github.com/MegaIng/syntax-extensions-pep634/ . (well, 'finished').
Btw, what is your current stand on #808?

Yeah, I should have attempted to run it. But I assume we will find more and more bugs of this kind while this grammar is in used. As you may have noticed, my recent interested in GrammarLoader and Reconstructur is fueled by https://github.com/MegaIng/syntax-extensions-base/ , which is a project that uses lark to exend the python grammar. I just finished the first proof of concept non-trivial extension: https://github.com/MegaIng/syntax-extensions-pep634/ . (well, 'finished').
Btw, what is your current stand on #808?

I merged it, but github doesn't recognize it for some reason.

I merged it, but github doesn't recognize it for some reason.

Re #808, I don't stand anywhere yet, because I haven't read it deeply. It's a huge diff of code, in a part of the codebase that isn't well tested. So I just need to clear some time to really look into it.
Re syntax-extensions-base, that's pretty cool! I also wanted to write something like that, but never got around to it. Are you open to adding a syntax for code-blocks? How about shorter lambdas?
I mean something like:
@codeblock
def repeat(n, f):
    for _ in range(n):
        f()

repeat(10):
    print "this"

Re #808, I don't stand anywhere yet, because I haven't read it deeply. It's a huge diff of code, in a part of the codebase that isn't well tested. So I just need to clear some time to really look into it.
Re syntax-extensions-base, that's pretty cool! I also wanted to write something like that, but never got around to it. Are you open to adding a syntax for code-blocks? How about shorter lambdas?
I mean something like:
@codeblock
def repeat(n, f):
    for _ in range(n):
        f()

repeat(10):
    print "this"

Btw, have you seen my new project? https://github.com/erezsh/Preql

Btw, have you seen my new project? https://github.com/erezsh/Preql


How to get the total number of updates

Hi, could I get the total number of updates before the training starts? My model is transformer. Usually I use --max-epoch to control  when to stop training. Thank you!

Possibly not, it is calculated after the batching process, which depends on the sentence length of your corpus (and the --max-position threshold, --update-freq, etc.)


Is react-formio npm package still needed?

Hi guys,
I've been using the react-formio npm package (https://www.npmjs.com/package/react-formio) so far, but I noticed that there's a maintained one under @formio/react (https://www.npmjs.com/package/@formio/react).
For me it seems that https://www.npmjs.com/package/react-formio is not updated anymore.
Shouldn't this npm be removed or at least an information added on its npm page, that now https://www.npmjs.com/package/@formio/react should be used?

I am closing the issue as it was created too long ago and there is no new comments here. If the issue is not resolved, please reopen it. Thanks!

The question still remains. Shouldn't the  react-formio npm package (https://www.npmjs.com/package/react-formio) be removed or at least a note added there that there's a newer supported package?


chore(deps): update terraform terraform-ibm-modules/secrets-manager/ibm to v1.15.1

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/secrets-manager/ibm (source)
module
patch
1.15.0 -> 1.15.1

Release Notes

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.15.1
Compare Source
Bug Fixes

deps: update terraform time to latest for the deployable architecture solution (#153) (a843adf)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 1.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[SPARK-7212][MLlib]Add sequence learning flag

Adds a mineSequences bool parameter to FPGrowth to support mining of sequential patterns. Test case validated against R's arulesSequences.

Merged build triggered.

Merged build started.

Test build #35722 has started for   PR 6997 at commit 648d4d4.

Test build #35722 has finished for   PR 6997 at commit 648d4d4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #35761 has started for   PR 6997 at commit f04bd50.

Merged build triggered.

Merged build started.

Test build #35762 has started for   PR 6997 at commit 34ef8f2.

Test build #35761 has finished for   PR 6997 at commit f04bd50.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class FreqItemset[Item](val items: Array[Item], val freq: Long, val ordered: Boolean)
        s"Using output committer class $
        logInfo(s"Using user defined output committer class $
          s"Using output committer class $

Merged build finished. Test FAILed.

Test build #35762 has finished for   PR 6997 at commit 34ef8f2.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class FreqItemset[Item](val items: Array[Item], val freq: Long, val ordered: Boolean)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35828 has started for   PR 6997 at commit ce987cb.

Test build #35828 has finished for   PR 6997 at commit ce987cb.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class FreqItemset[Item](val items: Array[Item], val freq: Long, val ordered: Boolean)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35885 has started for   PR 6997 at commit 7c14e15.

Test build #35885 has finished for   PR 6997 at commit 7c14e15.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class FreqItemset[Item](val items: Array[Item], val freq: Long, val ordered: Boolean)

Merged build finished. Test PASSed.

LGTM. Merged into master. Thanks!


fix(ms-redis): allow passing complete redis options from client, remove keys

Released: v0.2.0 🎉
This has been released in v0.2.0!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i mocktory@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


Create a "Splitter" cell

This cell should take 2 children, fill the space it's given, and give a fraction of the space to its children. IT should let you configure the default split ratios, decide whether its a horizontal or vertical split, and whether its resizable.

Closed by #131 and #147