Question about KL term

Hi,
Thank you for the great work! I am a novice in RL and have been using this repository to learn RLHF. I have a small question regarding the KL term on line 72 in the ppo_trainer.py file
https://github.com/tatsu-lab/alpaca_farm/blob/7ae83ae8e839a86c2c819112a242e7f2442af490/src/alpaca_farm/rl/ppo_trainer.py#L72-L73
According to equation (8) in https://arxiv.org/pdf/1707.06347.pdf, the KL penalty term is D_KL(p_ref, p). Based on the definition of KL, shouldn't line 72 be torch.clamp(ref_logprobs - logprobs, min=0.0)? I'm a bit confused about why it's torch.clamp(logprobs - ref_logprobs, min=0.0)... this seems to penalize sequences that have high likelihood if scored by ref_policy?

Hi, thanks for your question. I believe there's a misunderstanding.
In the current RLHF implementation, the local KL term in the original PPO algorithm isn't included in the objective.
Rather a global KL term (between the current policy model and the starting SFT model) is included to penalize the policy from deviating far away from the SFT policy. See Equation (2) in this paper. This is the (Monte Carlo estimate of the) KL being implemented in the code you quoted.
Note the implementation maximizes the reward, which in turn (partly) minimizes the KL through the penalty term. This means logprobs - ref_logprobs is encouraged to be low, which then means sampled sequences are encouraged to have high ref_logprobs. This makes sense, as the reward model is trained on samples generated from the initial SFT model, and thus it's most suitable to rate samples close to this distribution.


Animation on "fill" uses line color

I'm trying to get a filled area to have it's opacity transitioned on "show" and "hide", just like lines and points.

Note: there's a good chance I'm doing something wrong here

options: {
    transitions: {
      hide: {
        animations: {
          area: {
            type: "color",
            properties: ["fill"]
          }
        }
      }
    }
  }

Expected Behavior
On hide transition, area opacity is animated
Current Behavior
On hide transition, area color is changed to line color, then area opacity is animated
https://user-images.githubusercontent.com/10779424/129047891-b1aeb863-b31a-48b9-b1a0-dfa16f63c6cb.mp4
Possible Solution
Tried using the "from" and "to" attributes but that looks to have no effect.
Steps to Reproduce
There's a sandbox that you can try out here
Context
There doesn't look to be any way to animate an area in/out
Environment

Chart.js version: v3.5.0
Browser name and version: Chrome v91
Link to your project: https://codesandbox.io/s/dank-star-v3qpk

I don't think the animator supports sub-objects, so if the fill option is defined as object it can't be animated.
In that simple case (probably not your real use case), you could use backgroindColor or lineBackgroundColor to define the fill color and animate that.
https://codesandbox.io/s/frosty-shape-sp5co

Genius!
I'm guessing for some this might be a problem for folks with different colors above/below the line but, for me, lineBackgroundColor: color and fill: true does the job :+1:


Question: How to use uv with poetry on CI?

Is it possible to use uv to speed-up poetry install on CI?

for now:
poetry export > requirements.txt
uv venv
uv pip install -r requirements
poetry install

We'd need to add support for reading Poetry's dependency format, I'm not sure if we will.
Related:

#1650

for now:
poetry export > requirements.txt
uv venv
uv pip install -r requirements
poetry install

This works, but poetry export > requirements.txt creates UTF16-LE file, while uv pip install -r requirements.txt expects UTF-8, so I manually need to re-save it in UTF8. It is not a problem, but would be cool if uv would detect input file encoding...

for now:
poetry export > requirements.txt
uv venv
uv pip install -r requirements
poetry install

Do not redirect stream from poetry export, use -o flag to specify output file (it properly handles user messages and the actual dependency output).

As of https://github.com/astral-sh/uv/pull/2633 we support reading this directly.


IdpMetadataParser doesn't handle multiple IdP certificates

I'm facing a situation where IdP has two certificates during a transition period. In this situation IdpMetadataParser gets the other fingerprint from what is used in the response and authentication fails.
I think IdpMetadataParser should be robust and verbose regarding IdP metadata so that in these kind of situations users will know what happened and how to address the situation with any particular IdP. Also I think Settings should be able to store the relevant data for all IdPs. What do you think?
This pull request seems do the trick but has been rejected: https://github.com/onelogin/ruby-saml/pull/290
It has some extra stuff for handling the validation as well which is nice (but secondary to the parsing of the metadata). Also parsing one certificate is just a subset of parsing multiple certificates so the code could use some refactoring regarding that.
Should I make a pull request or are you already putting your hands on the reject button? 😃

Im ok with the fact of extending IdpMetadataParser in order to be able to parse more than 1 certificate.
But I dislike the change proposed on #290 where we had 2 new attributes for the settings:
idp_certs and idp_cert_fingerprints. What happened with the old idp_cert and idp_cert_fingerprint?
I did a proposal to be used on those transition periods:
https://github.com/onelogin/ruby-saml/issues/266#issuecomment-215268465

IdpMetadataParser returns a settings object from parse so I guess the settings have to have some new attributes for the multiple certificates?
Thinking of alternatives...
If we reuse the same attributes and do something like return an Array for idp_cert and idp_cert_fingerprint that would potentially break stuff. That could be of course put behind an option like options[:enable_multiple_certs] so that the users would then take the Array into account. Of course ruby-saml would then have to internally handle the array values as well.
Another option would be to store them in the parser instance, which feels like the wrong place.
Any suggestions?

For this kind of complexity is why we currently does not support multi certs,.
take also in mind that is possible to have certificates related to signatures and others related to the encryption process, so at the end if we want to cover all the SAML implementation, we will need thousand of settings, and is against the goal of keep the toolkit simple.

Ideally you need to keep around two lists of certificates - one for signing and one for encryption. If the metadata contains only one certificate, used for both, its just populated into both lists. Toggling support for multiple certificates by settings and checking value types is all pretty much meaningless.
The fact that the gem not support multiple, or separate certificates for different purposes is a problem in itself. Its a basic security measure to not share keypairs for different operations.

Speaking of #290.
The 2 new fields was created in order to avoid breaking changes. It would be very confusing if idp_cert returns a single cert sometimes, and an array some other time.
I have also deliberately avoided changing existing code too much, for 2 reasons:

If the PR was rejected, I could continue to rebase my branch and get the latest updates with minimal conflicts.
If the PR was accepted, handling multiple certs is the norm, and we can deprecate and eventually remove the existing code for handling single cert.

Related issue: https://github.com/onelogin/ruby-saml/issues/346

Azure's latest practice on this, makes this issue very relevant: https://azure.microsoft.com/en-us/documentation/articles/active-directory-signing-key-rollover/
I am not sure about the best way forward, but if one modified the "idp_cert=" setter in the saml settings to make sure it stores this as an array with a single element that might help the backward compatibility of #290 ?

I will do some research and try to find a global solution for all the toolkits.
The php and python versions are able to read a cert from settings but also from files. I will implement a solution to unify toolkits and also for solve rollover.
Expect it to be released at the end of september.

Thank you!

Is there any update on this issue. We need to parse a metadata file to integrate with ADFS 2.0 and the xml file has multiple certificates. We are not able to create a valid SAML Request because of this.

Sorry, this feature is not ready yet, but meanwhile, you can always parse it manually and set the right values to the settings.

So get the Cert from the metadata file and set it as the following?
settings.idp_cert = 'long certificate string'

Yes, using the settings.idp_cert
And yes, is compatible with ADFS 2.0 or 3.0, but with the right settings on both sides (ADFS and ruby-saml).  Review the nameid format and the authn context request values.

Thank you.

@pitbulk is this feature ready yet? I'm running into the same issue with ADFS having multiple certs due to the Auto Certificate Rollover feature within ADFS.

Sorry just saw your comment on my other issues post. Guess I'll just monkey patch for now. Thanks!

Would love an update on this! @pitbulk, do you still plan to have a toolkit wide solution to this problem? Unfortunately, as an SP, you don't have too much control over what different IdPs hand you.

Yes, I plan to provide a solution for that, but atm, I'm working on other tasks at Onelogin :(

Can I pay money to accelerate this feature?

@vincentwoo I started to implementation the desired functionality on the php-saml because I fill more comfortable with that language.
Later I will ask for reviews of the provided solution and later port to the rest of toolkits, starting with the ruby-saml toolkit.
I think the approach will be very similar to 290 but without supporting multiple fingerprints. But also register the "use" of the cert (signing/encryption) in order to support specific x509cert for each process.

That functionality is ready on php-saml (now on test phase). Soon I will port that to this toolkit.

I started the development on ruby-saml, you can follow on that PR:
https://github.com/onelogin/ruby-saml/pull/389

The PR #389 is ready.
@vincentwoo @angelicas @demonmind @erlingwl @davelooi @tomilaine want to review and test if matches your expectation?


Fork from openstack/doc8

The OpenStack foundation moved to Github. The doc8 repo is now available at https://github.com/openstack/doc8/ .
Maybe consider to get the "display line length" patch merged upstream?

Ooh thanks for the heads-up! I'll re-fork this when I find the time. The OpenStack contrib process is not something I see myself wanting to put the effort into going through in the foreseeable future, but if anyone else wanted to / was better placed to, I'd happily help

Oh, that looks like fun :-|
On Wed, Apr 20, 2016 at 07:49:37AM -0700, Kristian Glass wrote:

Ooh thanks for the heads-up! I'll re-fork this when I find the time. The OpenStack contrib process is not something I see myself wanting to put the effort into going through in the foreseeable future, but if anyone else wanted to / was better placed to, I'd happily help

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/doismellburning/doc8/issues/1#issuecomment-212456550

--

And that's why I have this fork ;)


@PlatformIO Library Registry manifest file

Description

This library in Web Registry: http://platformio.org/lib/show/225/HardwareSerial_RS485
Specification: library.json
Library Manager: http://docs.platformio.org/en/latest/librarymanager/index.html

Dear Valeros,
thank you for your interest in this software library and the contribution you propose.
I am willing to add the .json file that you propose top add.
Could you, however, briefly explain in what environment and for what purposes this .json file is used (maybe provide a few lines that can be added to the documentation).
And secondly, what the purpose and effect is of exclude "extras" in line 9. The extras directory contain an example of the boards.txt file that the user has to adapt (see https://github.com/MichaelJonker/HardwareSerialRS485/wiki/user-adaptations).
Omitting this directory from the distribution invalidates instructions that are shipped with the distribution.
Sorry for my delayed reply. I did not receive many reaction until recently (i.e. until a bug was fixed with the library manager of the Arduino IDE)

PlatformIO now allows the use of the existing library.properties file as an alternative to adding a library.json file:
http://docs.platformio.org/en/latest/userguide/lib/cmd_register.html#description
I think that it makes sense to only have a single metadata file because it's less maintenance. library.properties works for the Arduino IDE and PlatformIO so it's the logical choice.

In fact, this library is already in the PlatformIO library registry (not added by me):
https://platformio.org/lib/show/225/HardwareSerial_RS485


TouchBar Buttons

Add The Toolbar Buttons For Episodes On macOS To The TouchBar For Supported Macs.

Completed In Release: v1.3.2
Commit: https://github.com/markydoodled/DW-Episode-Guide/commit/a001db9698d432ce6e4947e09b3d80a70a9acd89


[WIP] Getting Involved / Contributing

Join KubeRay community

Join Ray's Slack workspace, and search the following public channels:

#kuberay-questions (KubeRay users): This channel aims to help KubeRay users with their questions. The messages will be closely monitored by the Ray/KubeRay maintainers.
#kuberay-discuss (KubeRay contributors): This channel is for contributors to discuss what to do next with KubeRay (e.g. issue, pull request, feature request, design doc, KubeRay ecosystem integration). All KubeRay maintainers & core contributors are in the channel.

Have KubeRay questions?

Ask the question in the #kuberay-questions slack channel.
Ask the question in the #ask-raybot (A ChatGPT-like chatbot) slack channel.
Open an issue in this GitHub repository. Issues with detailed reproduction instructions will be given priority in resolution. The following points are good for reproduction scripts:

Make sure the script is the minimal reproduction script.
It will be great if the issue can be reproduced on a local Kind cluster.

Want to contribute code to KubeRay?
1. Document fix
Open a PR to fix it (example: #1046).
2. Simple bug fix
The definition of a "simple bug" is a bug that has only one solution and is easy to understand (example: #1039). Open a GitHub issue to describe the issue, and open a PR to fix it.
3. Complex bug fix
The definition of a "complex bug" is a bug that has multiple solutions and each has different tradeoffs.

Case 1: If there is a solution that is significantly better than all the other solutions, you can open an issue to describe the bug and draft a pull request that includes a comparison of the solutions in the PR description (example: #1043).

Case 2: If there is no clear standout solution among the available options, open an issue to describe the bug and discuss the possible solutions with the maintainers before drafting a PR.

Take #874 as an example, the community decided to close this PR and in favor of another solution, #1040. By staying in touch with the community, you can often prevent such situations from occurring in the first place.

4. New features for existing components
Open an issue to describe the feature and its use cases. It would be great to work on it after discussing it with maintainers.
5. New component
Open a REP (Ray Enhancement Proposal) PR to the ray-project/enhancements repository to propose your idea.
6. KubeRay ecosystem integration

Case 1: If no code change is needed for the KubeRay repository, you can choose either:

Add a document in the Kubernetes component repository, and open a PR to add the document link to the KubeRay ecosystem section (link1, link2).
Add a document in the KubeRay repository (example: Prometheus & Grafana).

Case 2: If a code change is needed for the KubeRay repository, please open an issue and discuss it with maintainers before drafting a PR. This will make the process much faster.

Tip for implementation: In general, KubeRay does not allow 3rd-party component-specific code leaks. However, there may be exceptions in cases where industry standards require it. For instance, KubeRay includes some Prometheus-specific code.

Tip for documentation: Users with basic Kubernetes experience and without any context with KubeRay and the 3rd-party component should be able to follow the document and reproduce the result on their local Kind clusters.

How to get the PRs to be reviewed?

Pick a good GitHub issue: Make sure whether this issue is needed for the community or not.

Is it a good time?: KubeRay will have a 1-week feature freeze for each release. During that time, all pull requests for new features will not be reviewed. In addition, if the KubeRay/Ray communities plan to refactor some components recently, the related pull requests may not be reviewed in a timely manner. Join the Slack channel and keep in touch with the community!

Testing Kubernetes operators can be challenging, and even though KubeRay has unit tests, Kubernetes control plane simulation tests, configuration tests, and end-to-end tests, it can still be difficult to ensure full coverage. In many cases, maintainers may need to manually clone a contributor's fork and test the pull request during the review process, which can be time-consuming. The following tips can help make your pull request easier to review.

PR description: A detailed pull request description can help maintainers understand why this change is needed, why you made certain decisions, and which aspects you took into consideration (example: #938).

Test: Please add tests for the PR, and make sure the tests will not introduce flakiness. If you also manually test the PR, please provide detailed instructions for maintainers to test on their environments.

Implementation: Developing an open-source project is very different from developing an in-house product. KubeRay needs to fulfill all use cases for tens of companies and their Kubernetes distributions. Hence, the philosophy for KubeRay is:

Empower users to configure the feature and provide them with good default values.
Enforce a configuration only when considering backward compatibility, different use cases, and different Kubernetes distributions.

Tagging issues with a good first issue label may help the new contributors to get started. For example, documentations are usually good first issues.

@kevin85421 can we port this into a readme on the main kuberay page and than close this issue?


Add option to skip starting a game session after it's created.

Sometimes, a game needs to create a game session but not to start it immediately.
For example, while waiting for players to join, the game session should be in state EOnlineSessionState::Pending, and when all the players have joined we can finally start the session which changes it's internal state to EOnlineSessionState::InProgress.
Currently, the node CreateAdvancedSession creates a game session immediately starts it.
So, I added the parameter bStartAfterCreate to the CreateAdvancedSession node (set to true by default so it doesn't break current implementations).

If bStartAfterCreate is set to true, the game session will be created and also started immediately.
If bStartAfterCreate is set to false, the game session will be created but not started.

Now, to start a game session I added the node StartAdvancedSession.
I didn't add a node to end a game session because such functionality already existed but was deprecated in b68199b1aad. However if needed, I can create another PR to re-enable the node EndSession.

I added the PR: https://github.com/mordentral/AdvancedSessionsPlugin/pull/32

Will fully review this in the next couple of days, UE5 launch is currently in the way


Ensure consistent layer tooltip

References and relevant issues
Closes https://github.com/napari/napari/issues/6435
Description
In this PR I ensure that when mousing over a layer in the layer list the tooltips are consistent.
The layer name is always shown, which covers the case of long names which might be elided in the list (the linked issue). If there is a file name and the other info, it's also shown. Here's an example of a long layer name (but all layer names are shown):

Also, I add a small amount of logic to format the tooltip better, so that when something is missing the spurious punctuation seen on live, e.g. with empty Points, is eliminated.
Live

this PR:

Question 1:
this issue: https://github.com/napari/napari/issues/1251
here could make the tooltip show the whole path rather than just the filename.
Personally, I'm fine with just the filename, but it's an option.
Question 2:
The status bar shows the layer_base  which is the filename (when available) when mousing the canvas. Frankly, I think this should show the layer name, which this PR makes possible.
One can have multiple layers from the same file after all!

here could make the tooltip show the whole path rather than just the filename.

I think this could go wrong. Maybe we should have an "info" or "properties" dropdown that opens a dialog with full info and/or metadata of the layer. For abnother PR though :P

Frankly, I think this should show the layer name,

Uhm, I think they're both important... but maybe the name is the more immedately useful information, and you need more you can check the layer tooltip. So I agree with you, unless putting both is an option despite the real estate.

here could make the tooltip show the whole path rather than just the filename.

I think this could go wrong. Maybe we should have an "info" or "properties" dropdown that opens a dialog with full info and/or metadata of the layer. For abnother PR though :P

Yes, a get info or Get properties widget for layers would be very nice to have. Most image/video software has something like that. It would summarize the basic layer properties, including source, scale, shape, etc. and metadata. I think this is somewhat similar to @andy-sweet metadata plugin?

Frankly, I think this should show the layer name,

Uhm, I think they're both important... but maybe the name is the more immedately useful information, and you need more you can check the layer tooltip. So I agree with you, unless putting both is an option despite the real estate.

I think both would be rough, especially for layers that display more then just a coordinate...
Anyhow my mental model is that layer list shows the layers and would have the higher level info of the file name. The canvas shows the layer data, so mousing over the canvas should give the layer associated. Layer names have to be unique--I think--while file names need not, and multiple layers can come from the same file.
I think changing the status bar willl/would be a followup PR--should be trivial now--to make decision making easier.

I think this is somewhat similar to @andy-sweet metadata plugin?

I think it's a lot easier to do than that plugin; at least to start with we can just print out, not allow modification. It should also be a modal dialog I think, so it doesn't stick around nor clutter up the widgets.

Layer names have to be unique--I think--while file names need not, and multiple layers can come from the same file.

yup, I agree!

Is this ready to merge?

I don't have anything to add...
I think a similar homogenization of info for the status bar would be a followup.


Greece was stuck in Dodecanese on communist Greek win

I'm not sure how it happened, but in my game the communist Greek government ended up controlling all of Greece's starting territory without any cores while regular Greece was stuck in Dodecanese. I'm guessing this never should have happened in the first place, but there should probably be an event that reunites the two Greeces if they have the same government type.

Communist Greek should turn into Greece. UK should keep the Dodecanese till Greece is in peace and non communist.


Support for Ruby 2.7

The current code base doesn't seem to support Ruby 2.7 despite it being part of the test suite matrix. In some testing locally (Ubuntu 20.04) I am unable to run the test suite command locally (bundle exec bake test). The issue comes from a syntax error in it.rb:
sus/lib/sus/it.rb:50: syntax error, unexpected ')' (SyntaxError)
    add It.build(self, ...)

According to the article here  regarding the addition for argument forwarding, as of 2.7 positional arguments are not supported. I ran into this when I was attempting to add Phlex to a project and was running into a similar error. In an effort to allow Phlex to be 2.7 compatible I ran into sus not being 2.7 compatible.
It seems odd that Github actions isn't failing the test suite which leads me to think its a local issue. I have a fix for it.rb locally that is passing tests that I'm happy to submit a PR for. However, the tests:external seem to be failing due to a similar issue in the console gem.

TIL Ruby 2.7.3 supports positional arguments but 2.7.2 does not. Happy to submit the PR to give support back to 2.7.2 but understand if this isn't wanted.

Ruby 2.7.x where x < 6 has security issues. So, I'm hesitant to invest a lot of energy into maintaining support for older releases 2.7 - especially that it will be EOL soon.
I don't have a really strong opinion about it, but I am happy with the current level of support. If it's causing you a significant pain, I'm willing to consider it, but can you tell me more details about your pain point and the scope of your fix?

I don't think it is a big enough issue to warrant fixing here. Bumping up a few minor versions to remedy the issue seems simple enough. I was initially thinking I needed to move to Ruby 3 - which still may not even be a big deal. For what it's worth to fix the issue requires patching Sus::Context module in it.rb:
was:
	module Context
		def it(...)
			add It.build(self, ...)
		end
	end

To give support to 2.7.2 (and likely even 2.6):
	module Context
		def it(*args, **kwargs, &blk)
			add It.build(self, *args, **kwargs, &blk)
		end
	end

Ah yep that's totally reasonable patch. However, to your point, I think it's better to move to v2.7.6 - thanks for your thoughts and considerations..


Handler for other file types to upload documents

It would be great if importer can be used to upload documents to GeoNode.

@ahmdthr this is what we expect to happen once this geonode-importer will be officially published and configured inside GeoNode. We don't have plan to adopt it for documents yet, but this is what I wish will happen soon.

@giohappy I will contribute for the documents. Any resources or pointers will be greatly appreciated. Is there any mailing-list or chat channels for geonode-importer for developers? Thank you.

@giohappy I will contribute for the documents. Any resources or pointers will be greatly appreciated. Is there any mailing-list or chat channels for geonode-importer for developers? Thank you.

The best will be through issues once this repo will be moved under GeoNode

Is there any timeline for the move to GeoNode? I will try to implement the document upload irrespective on geonode-importer. Wish me luck.

@ahmdthr Could you explain what's your goal? If it's having an API for the upload of documents, it's already available. I thought you meant to replace with an implementation on top of geonode-importer

Yeah, the goal is to have a common API for all async uploads. I know the document upload endpoint was recently added, but I want to have this with geonode-importer

@giohappy I simply wanted to refer to your earlier comment on geonode's document creation PR (https://github.com/GeoNode/geonode/issues/10270#issuecomment-1314191880) We are planning ahead and considering geonode-importer as an official module for geonode. It would be great if we can share resources or any hints for the document upload, I will attempt extending it for the document upload now. Thanks.


RT-195: Refactor/home text

New content
For in-complete submissions
You need to complete your monthly update. Complete (x) supply chains by Friday 22 January 2021.
For completed submissions
Your monthly update is complete. All supply chains have been completed for this month.
Changes

Update summary as per latest content
Tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a091949). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage        ?   97.68%
=======================================
  Files           ?       52
  Lines           ?     3455
  Branches        ?        0
=======================================
  Hits            ?     3375
  Misses          ?       80
  Partials        ?        0

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 a091949...fea6501. Read the comment docs.


startScanning returns -1

When using startScanning() function, -1 will be returned for each result
But it logs well on android studio when a barcode is detected
I'm using version 3.0.0

Can you provide a repo to reproduce this issue?

@thegnuu sorry it turns out I'm not using the callback properly ^_^"

Yep, this might result into some errors ;)
Glad you found the solution :)


As this is broken, point users to the working shivammathur/homebrew-php tap

As:

this tap doesn't work anymore,
but still is the top hit in Google,

maybe we could save lots of users several hours of time each, by putting a link in the README to point them to the tap that works perfectly fine out of the box:
Homebrew tap for PHP 5.6 to 8.1:

https://github.com/shivammathur/homebrew-php

Hi!
Thank you for your interest in this repository. Unfortunately, this repository will now be archived with no further actions. We are sorry for the inconvenience.
Why are we closing this repository? This repository was only meant as a temporary measure, not a permanent one. Its only purpose was to ease the transition, considering that formulae from the homebrew-core tap are removed almost the day they became unsupported by the vendor. We needed a few more months to allow us to upgrade the code base of the various projects we have. But it was always with the intention of doing those upgrades, not by relying on a repository to keep old php versions artificially alive. We do not condone the use of deprecated software that could lead to serious security vulnerabilities.
Why are we not redirecting to another repository? Redirecting to another repository could be interpreted as an endorsement of said repository. If we were to do such a thing, we would not do it without vetting it first. And we do not wish to put the time and energy required in a vetting process of a third party repository. As the reason why a vetting process would be required, consider this. Before installing a software library on all our developer computers from an untrusted source, we would need to make sure that this software library is free from any malicious code (Trojan, ransomware, etc.), both in the repository itself and in the packaged binaries (the homebrew bottles, if any).
Thank you for your understanding.

Hi!
Thank you for your interest in this repository. Unfortunately, this repository will now be archived with no further actions. We are sorry for the inconvenience.
Why are we closing this repository? This repository was only meant as a temporary measure, not a permanent one. Its only purpose was to ease the transition, considering that formulae from the homebrew-core tap are removed almost the day they became unsupported by the vendor. We needed a few more months to allow us to upgrade the code base of the various projects we have. But it was always with the intention of doing those upgrades, not by relying on a repository to keep old php versions artificially alive. We do not condone the use of deprecated software that could lead to serious security vulnerabilities.
Why are we not redirecting to another repository? Redirecting to another repository could be interpreted as an endorsement of said repository. If we were to do such a thing, we would not do it without vetting it first. And we do not wish to put the time and energy required in a vetting process of a third party repository. As the reason why a vetting process would be required, consider this. Before installing a software library on all our developer computers from an untrusted source, we would need to make sure that this software library is free from any malicious code (Trojan, ransomware, etc.), both in the repository itself and in the packaged binaries (the homebrew bottles, if any).
Thank you for your understanding.


Add spec: must not contain broken links

One-liner change

Merged, patched, pushed, and published. Thanks!


Ability To Nest Labels for Archiving

I love your tool for archiving a user at work. The user leaves we back up their account using GYB and then we restore to an archive user. Problem I have is that I have to do a restore with a custom label then move all their labels under a parent label so that they stay containerized IE User A has a label called Client A when restored it goes to label User A > Client A. This would help a lot for archiving users and keeping their email under a single label but still the same hierarchy as their mailbox. Is there any way to do this?

ohh maybe i need to archive all the users email first to a label in their mailbox then backup that mailbox then restore? Would that be a better way? that is still more work for me and would love to have the option of creating a parent label that all email goes under when restored!

You could do it at the source mailbox as you suggested, by nesting all of the labels under one master label.
GMail's native import tool (GMail -> Settings -> Accounts and Import -> Import mail and contacts) also does this, putting all of the labels under one label<EMAIL_ADDRESS>which you could rename afterwards.

I just ended up using Gmail migration tool in Admin Tools and migrating their content to another mail box and arching the email there. It retains all the emails and labels

Hi guys, is there any way to backup sub-labels? eg I have a label called Offices that has 5 messages in it but also 4 sub-labels that also contain messages. Can these sub-labels be backed up and maintained?

Hi,
I trying to update GYB to adding a NEST Label (parent label) on --action restore
Step 1 :  Adding one parser option :
parser.add_argument('--label-prefix',
                        action='append',
                        dest='label_prefix',
                        help='Optional: On restore, all labels will additionally receive \
  this prefix label. For example, "--label-prefix gyb-archive" will become main label of all \
  uploaded labels with a gyb-prefix label.',
                        default=[])

Step 2 : Adding Nest label to the request if it's input by the user
[..................]
 if not options.strip_labels:
           sqlcur.execute('SELECT DISTINCT label FROM labels WHERE message_num = ?', (message_num,))
           labels_results = sqlcur.fetchall()
           for l in labels_results:
                      # TODO TUROK LABEL PREFIX BEGIN
                      if options.label_prefix:
                                 labels.append(options.label_prefix[0] + "/" + l[0])
                      else:
                      # TODO TUROK LABEL PREFIX END
                                 labels.append(l[0])
if options.label_restored:
[..................]

Result on destination Mail is "correct" about gMail categorisation
Label are well placed under one parent label
Email are all categorized on the good destination nested label
==> But email are all marked as "Read" even if they were unread on the source
I don't see any trace of on the main.py app, Where please does this is set to "read"/"unread"
There is this information stored and updated?
Thanks =)


fix document path

:tada: This PR is included in version 1.2.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can't build local-cluster on Apple M1 / aarch64-darwin

When I clone the repo (commit 7f2d59) and I try to build on macbook pro (Apple M1 Max) I get this error:
$ nix build .#plutip:exe:local-cluster
error: flake 'git+file:///Users/aljosa/plutip' does not provide attribute 'packages.aarch64-darwin.plutip:exe:local-cluster', 'legacyPackages.aarch64-darwin.plutip:exe:local-cluster' or 'plutip:exe:local-cluster'

I've tried just adding the system:
$ git diff
diff --git a/flake.nix b/flake.nix
index c117ade..899cfae 100644
--- a/flake.nix
+++ b/flake.nix
@@ -17,7 +17,7 @@
   outputs =
     { self, bot-plutus-interface, nixpkgs, haskell-nix, iohk-nix, ... }@inputs:
     let
-      defaultSystems = [ "x86_64-linux" "x86_64-darwin" ];
+      defaultSystems = [ "x86_64-linux" "x86_64-darwin" "aarch64-darwin" ];

       perSystem = nixpkgs.lib.genAttrs defaultSystems;

but the build still failed:
nix build .#plutip:exe:local-cluster
warning: Git tree '/Users/aljosa/plutip' is dirty
[35.1 MiB DL]

trace: To make project.plan-nix for plutip a fixed-output derivation but not materialized, set `plan-sha256` to the output of the 'calculateMaterializedSha' script in 'passthru'.
trace: To materialize project.plan-nix for plutip entirely, pass a writable path as the `materialized` argument and run the 'updateMaterialized' script in 'passthru'.
[1/142/731 built, 418 copied (1729.1 MiB), 596.4 MiB DL] building ghc-8.10.7 (buildPhase): "inplace/bin/ghc-stage1" -hisuf hi

[1/142/731 built, 418 copied (1729.1 MiB), 596.4 MiB DL] building ghc-8.10.7 (buildPhase):      - Module.holeUnitId

error: builder for '/nix/store/11w2dbc4smn5wk8m1cwmqhwij56vbi36-scrypt-lib-scrypt-0.5.0.drv' failed with exit code 1;
       last 10 log lines:
       > /nix/store/qc4fzcja2bs760vsqcsc6v28imjwy0wi-clang-wrapper-11.1.0/resource-root/include/mmintrin.h:525:12: error:
       >      error: invalid conversion between vector type '__m64' (vector of 1 'long long' value) and integer type 'int' of different size
       >         return (__m64)__builtin_ia32_psubw((__v4hi)__m1, (__v4hi)__m2);
       >                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       >     |
       > 525 |     return (__m64)__builtin_ia32_psubw((__v4hi)__m1, (__v4hi)__m2);
       >     |            ^
       > fatal error: too many errors emitted, stopping now [-ferror-limit=]
       > 20 errors generated.
       > `clang' failed in phase `C Compiler'. (Exit code: 1)
       For full logs, run 'nix log /nix/store/11w2dbc4smn5wk8m1cwmqhwij56vbi36-scrypt-lib-scrypt-0.5.0.drv'.
error: 1 dependencies of derivation '/nix/store/g3qa4xpwa7yy4frl9badw4q9v9bgd59n-cardano-wallet-core-lib-cardano-wallet-core-2022.7.1-config.drv' failed to build
error: 1 dependencies of derivation '/nix/store/122w813h0w6ax6vv5yp2gmc1gl6j75in-cardano-wallet-core-lib-cardano-wallet-core-2022.7.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/fww6kpyzb55aj06zwz7wjxp5hzdy6v4i-plutip-lib-plutip-0.2-config.drv' failed to build
error: 1 dependencies of derivation '/nix/store/dlzl67xscd8qcf2dkwbmy69rj9c26sma-plutip-lib-plutip-0.2.drv' failed to build
error (ignored): error: cannot unlink '/private/tmp/nix-build-prettyprinter-lib-prettyprinter-1.7.1.drv-0/prettyprinter-1.7.1': Directory not empty
error: 1 dependencies of derivation '/nix/store/w36k7jbigxm1ir162ml76wrk4ink0v2v-plutip-exe-local-cluster-0.2.drv' failed to build

The building ghc-8.10.7 is suspicious to me, maybe we can circumvent the problem by using the nix binary caches.
Unfortunately the branch is still using our own fork of haskell.nix, making the iohk caches useless.
We already have an upgrade in progress, using the upstream haskell.nix, but it's still unfinished... (it is working with CTL, but tests are failing, and with the lack of funding, no one has started working on a fix yet)
https://github.com/mlabs-haskell/plutip/pull/164


Version string still says 9.0.0

https://github.com/aws/amazon-freertos/blob/5068f430f8139725a7280e936c406106d0ba8964/lib/include/task.h#L47

This version string is incorrect – thank you for pointing it out. It has been noted and will be corrected.

This has been updated in commit 6620031aed80bd411c87baeef501ac884cfd1b1a.


[Popup window] extra line showing in the wrong place

Instructions: Replace the template text and remove irrelevant text (including this line)
Describe the bug

To Reproduce
minimal vimrc:
let g:win_list=[]

function! VimCloseWin(winid, result) abort
    if !empty(g:win_list) && a:winid == g:win_list[0]
        call remove(g:win_list, 0)
    endif
endfunction

function! ShowPopup()
    let l:str="Something is wrong about popup window"
    let l:level='WarningMsg'
    let l:win=popup_create(l:str, {'line': 3+len(g:win_list)*3,'col': &columns-strlen(l:str)-3,'time': 5000,'tab': -1,'zindex': 200,'highlight': l:level,'border': [],'callback': 'VimCloseWin',})
    call add(g:win_list, l:win)
endfunction

set nocompatible

nnoremap ,pw :call ShowPopup()<cr>

filetype plugin indent on
syntax on

vim -u minimal_vimrc

call ShowPopup()

Expected behavior
Show popup windows at the right top and disappear after 5s
Screenshots
If applicable, copy/paste the text or add screenshots to help explain your problem.
Environment (please complete the following information):

Vim version

VIM - Vi IMproved 8.1 (2018 May 18, compiled Jun  4 2019 08:52:13)
Included patches: 1-1461
Compiled by zhengxiaobin
Huge version without GUI.    Please check your 'ambiwidth' setting, it may need to be "double".  Check how the line drawing characters show up in your terminal.

thx,
when ambiwidth=single:

when ambiwidth=double

8.1.1459 and 8.1.1460 should fix this.

@mattn But my vim version is >= 8.1.1461.

Then, it may be an issue of your font. On my Windows, it works fine for me.

FYI, ambiwidth is not an option to control width of ambiguous width. it is an option to specify for telling vim how your terminal handle ambiguous width as half or double.

It looks that it works as expected when you set abmiwidth properly. Closing.

Then, it may be an issue of your font. On my Windows, it works fine for me.

my vim is running on ubuntu OS, huge version without GUI.
and I use ssh client(xshell) to connect ubuntu OS


Show the user which .driftignore line is invalid

Description
Simple UX in warnings
Today driftctl only displays which resource is concerned by the error, like:
WARN[0017] unable to parse line, invalid length, got 1 expected >= 2 line=github_repository.
It would be easier for the user if it read sth like:
WARN[0017] unable to parse line, invalid length, got 1 expected >= 2 line=63
Example

add an invalid line to your .driftignore
run driftctl

Today driftctl only displays which resource is concerned by the error, like:

We display the full line which can't be parsed, we can add the line number


V1-first documentation

Long living (merging ETA: 2023-11-30), collaborative branch for making the documentation teach the V1 design (see #578) first.
Feedback and commits welcome at any time. Please avoid force-pushing.
Preview: https://vike-v1-staging.lourot.dev.

🚀 Neat.

Please avoid force-pushing.

👍  (Now that Vike's code is increasingly collaborative, I'll stop force pushing on non-brillout/* branches.)

commits welcome

Just made one. Feel free to object to any of my (future) commits.

I did the following:

Sounds good. I'll have a look at it once I'm done with that feature request.

(I managed to fix the flaky test; we should get much less false CI failures. I also have an idea about the failing CloudFlare tests when we hit CF's API rate limit.)

Staging preview: https://vike-v1-staging.lourot.dev/

docs: fix copy-paste mistakes and typo

🙏

I think https://vike-v1-staging.lourot.dev/header-file is now really good and I now consider it done. (Finally 😅 it wasn't easy to find explanations that is both succint and clear 🙂). But let me know if you feel something's missing / not good in there.

The overall navigation structure LGTM now. (It isn't perfect but I think it's good enough for now.)
I will now review the docs changes on a page-by-page basis. I expect it to be mostly about proofreading and, therfore, to be fairly quick.

Getting there 🙂

This now LGTM.
@AurelienLourot Let me know if my latest changes are ok with you. I'll then implement the deprecating warning for the current design and release. Let's prepare the release tweets for Monday.

LGTM 🚀

🙏
Let me release the new version and I'll then merge.

@AurelienLourot Huge thanks for the PR 🙏 it has been a massive help.

Amazing work by @AurelienLourot thanks a lot, and thanks @brillout for all the hardwork.

Everything is ready. Let's merge tomorrow at noon before the release tweet.


Recheck throws error Error: write EPIPE

What is the problem?
import { check } from 'recheck';

await check('^(a|a)*$', '');

gives:
[Running] node "/home/userA/code/projectA/regexTest.js"
node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:917:11)
    at Socket._write (node:net:929:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at /home/userA/code/projectA/node_modules/recheck/lib/main.js:2:20
    at new Promise (<anonymous>)
    at FA.request (/home/userA/code/projectA/node_modules/recheck/lib/main.js:1:1513)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Node.js v18.12.1

It is like this in 4.4.2 and 4.4.3 but in 4.4.1 it works.
How to fix the problem?
No idea.
Related issues
None.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS"
node v18.12.1
I had a colleague test this as well and they had the same result, but they are also on the same kind of machine.
Is it something in the code changes in 4.4.2 that could cause this?

Thanks. I can reproduce the bug on linux machine.
4.4.2 has no big change on the source code, so I guess some dependencies are wrong.

I can suggest setting the environment variable RECHECK_BACKEND=worker as a temporary solution? (or RECHECK_BACKEND=pure) Performance may be degraded, but it may solve the problem.
(See the document.)
I need more time to investigate the root cause.

@makenowjust great, maybe add a test case running all the tests also on Ubuntu in your Github tests?

I tried the dirty patch sed -i.bak 's/"ignore"/"inherit"/' node_modules/recheck/lib/main.js, and the following error messages are shown after the patch.
recheck/packages/recheck-linux-x64/recheck: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by recheck/packages/recheck-linux-x64/recheck)
recheck/packages/recheck-linux-x64/recheck: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by recheck/packages/recheck-linux-x64/recheck)

That is, the bug is probably caused by libc being too new in the built environment. Indeed, we use ubuntu-latest on CI, and the version of ubuntu-latest was updated by the release of 4.4.2. We should fix the version of CI environment.
@thernstig Almost cases are tested here, but some cases are skipped because of preventing too slow to run CI. This case seems very special, so we cannot catch it in the CI.

@makenowjust maybe you could for the main flow of just doing this would want to test on more versions?
import { check } from 'recheck';

await check('^(a|a)*$', '');

i.e. just run such a test case on multiple versions of e.g. Ubuntu. But I realize that is maybe a rare case that it would break, so possibly not worth it.

CI environment versions are updated. Could you download a new binary from here, put it to node_modules/recheck-linux-x64/recheck, and try it?
@thernstig The CI takes 7-13 minutes, and I feel it is too slow. I wouldn't add more CI tasks if at all possible.

@makenowjust seems to work.

Thank you. I am going to publish a new version tomorrow.

Close. The new version is published.


Refactor/processing memories

Summary by Entelligence.AI

Refactor: Simplified and restructured the memory processing code for better maintainability and performance.
New Feature: Introduced a new MemoryStatus enum to track the status of memory processing, enhancing visibility into the process.
Refactor: Updated the memory widgets display logic to handle individual memories instead of a list, improving UI responsiveness.
Refactor: Optimized the processMemoryContent function by rearranging the message processing loop, enhancing efficiency.
Refactor: Overhauled the backend memory processing functions, adding new features for memory management and improving existing CRUD operations.
Style: Minor style adjustments in the message_event.py file.
Chore: Removed unnecessary print statements and imports in the endpoints.py and plugins.py files, decluttering the codebase.

i'm here 👀


What is .pkl format? What all it contains?

Hi,
I have depth images in .bmp format.
Is that I have to convert my images to .pkl format? or is there any way to use the images directly?

Hi,
We saved  frames of depth images in data/sample_img.pkl and saved frames of position coordinates in data/sample_pose.pkl
sample_img.pkl is a list of image frames .
e.g.  sample_img <- [ [ image_1 ] ,  [ image_2 ], ... , [ image_t ] ].
each image_i has a shape of (width, height)
Please see detailed information in example.ipynb
You can use images directly in any format, but you need to stack them to create a list of image frames. For example:
import joblib
import matplotlib.pyplot as plt
img1 =  plt.imread('image1.bmp')
img2 =  plt.imread('image2.bmp')
img_frames = [[img1], [img2]]
joblib.dump(img_frames, 'image_frames.pkl')

Hi,
Thank you for the prompt reply. This worked.
In case any wants to use it for multiple files, then the code below should work.
import joblib
import cv2
import glob

X_data = []
file_lists = glob.glob("/home/ankit/Home_Cloud/Proband/Proband20/Fg_depth/*.bmp")
for files in sorted(file_lists):
    if files.endswith(".bmp"):
        image = cv2.imread(files)
        X_data.append(image)
        joblib.dump(X_data, 'image_frames.pkl')

It would be nice to add this info to the readme file.


chore(main): release 0.3.1

Auto generated release
0.3.1 (2024-12-20)
Miscellaneous Chores

deps: bump serde from 1.0.215 to 1.0.216 (#77) (fa1a85c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.1
:sunflower:


Remove Lib/ dir

Seem to be leftover from a refactor sometime maybe?

see https://github.com/RustPython/RustPython/pull/775#issuecomment-478933532


Fix failure on Python3.5

And also fix failing tests.
This is a fix for #53

I have actually taken a minute to address all unicode issues I came across: abb21e445050cd23dbcdb034deabee47ae1991b1


Create organization on user signup

Description
An organization should be created on request to /account-request by doing this we can deprecate the createOrganization() mutation on the global admin portal and move to the support staff clicking a button to create an org instead of reentering the information.
Proposed Solution

Create organization, Okta groups and the first user in the admin group on sign-up/ form submit

User in Okta should not receive an invitation and should not be able to sign in to the application
organization.identity_verified should equal false on creation

Add a line the top of the email sent via /account-request to say "This organization was created in Simple Report and the admin needs their identity verified. After Identity verification the organization can be enabled by going to {link to pending org table} and marking the org with the matching external ID"

Additional context
Sparkle must be notified before this feature goes live to coordinate the release and retraining of the support staff. It would be best to feature flag this feature to avoid the changeset from sitting in a PR

Fabulous! If we can get updated materials to support folk in the next couple of days, I think we should start rolling this out over the weekend or on Monday.


Validate aggregate report via UI

aggregate reports have been ran on entiredata set but they need to be verified:

[x] deploy branch of pub-ui that includes making aggregate reports public
[x] Reports 3 and 4 don't seem to be working. @wpears @PatrickHSI
[ ] validate the aggregate reports look ok

Issue with reports 3 and 4 fixed by @PatrickHSI via https://github.com/cfpb/hmda-pub-ui/pull/302/commits/e9820331c2be2b0d12276a5cd22b54d7613f5c7e

There will need to be a small code change to pub-ui when data is pushed to the prod bucket, https://github.com/cfpb/hmda-pub-ui/issues/303

@wpears @omnipresent07 in the applications by tract and loans purchased by tract table, the header row list the order as (state/county/tract), but the geographies are listed as (county/state/tract). We should change the header to county/state/tract for consistency.

@wpears mentioned report 1 and 2 had duplicated rows at times.
Reports 1 and 2 have been re-run and should not have the duplicated records in them any more. The root cause is a multitude of NA in State and/or County and implementation of Q604

@wpears reports look fine now, the labels on tables 1 & 2 still need to be changed, though.

@chynnakeys The tables have been fixed, but the newest code just hasn't been deployed


Function signature cut off on tab-completion

I was playing aroung with this minimal config setting up neovim 0.5 for rust development.
I have got it to a pretty good working state, however when I tab-to-complete, the documentation is cutting off the function signature. It comes up alright when I get the documenation on vim.lsp.buf.hover().
Is this a known issue?
Here is what I see when I <tab>:

And here when I press K with the cursor over the function which triggers hover():

The documentation is not the same as hover information in LSP spec.
So I can't solve it. Sorry.

So you are saying this is coming from the lsp server or is a bug in the lsp client, so neovim?
But this is cut-off documentation is not a problem other completion plugins like completion-nvim, just with compe.

LSP has textDocument/hover request.
LSP has textDocument/completion request (the returned value includes CompletionItem[] and it can be have a documentation

The textDocument/hover provides more detailed information than textDocument/completion's documentation. (includes VSCode)
Most LSP client uses textDocument/completion's documentation for completion-menu's documentation.

Okay thank you, then I will open an issue over at the rust-analyzer repo, if the problem lies in what comes back as textDocument/completion.

So just to nail down where the problem is here.
When I do the same with a minimal config and use completion-nvim with the same lsp server, neovim version, etc. I do get the correct documentation on completion:

So I guess that that extension is using hover even on auto completion.

Yes. completion-nvim uses textDocument/hover in completion.
I think it is not general behavior. completion-nvim specific things.

Yes. completion-nvim uses textDocument/hover in completion.
I think it is not general behavior. completion-nvim specific things.

Thank you for clearing that up and btw thank you for your work on this in general!


Modified files remain marked in Atom after repo is commited

In Atom 1.8.0-dev-435dcc7, modified files remained marked as modified (e.g. coloured in the tabs and in tree view) even after a commit.
To reproduce: edit some files, commit the repository, go back to atom. The modified files remain coloured. Expected result is for them to lose their git status and revert back to unmodified.
This is on OS X 10.10.5

Note that after doing another commit, the files that were previously marked become un-marked, and only the files from the last commit remain marked.

This issue is directly related to the /atom/tree-view repository, would you file this over there and close this?

This is interesting though:

Note that after doing another commit, the files that were previously marked become un-marked, and only the files from the last commit remain marked.

@ZombieHippie I wasn't sure if it was, because I don't know which Atom package is responsible for marking files with their git status. For example, it also affects the tabs, as they also color the files the same way. So it didn't seem like just tree view to me.
But if you still want me to post it there instead, I will.

@adambuczynski , oops, you're right! The tree-view uses the provided from a core function.

@ZombieHippie Seems to be fixed now since 1.9.0-dev-77dea79, so I'll close this

This issue has returned in 1.9.0-dev-c4d4e0f

+1

Haven't seen it happening anymore. Seems fixed in 1.10.0-dev-672cf6d

This is a bit of a jojo issue. It has crept up again in 1.10.0-dev-748dbcd.
I won't close it anymore until it's properly looked at, because it might only be happening under certain circumstances that I'm not noticing.

+1
Add files, commit, push -- files will just stay marked in the tree view, the tabs stay colored, and the line number / gutter area shows lines as edited. Both command line and ctrl-shift-B shows "nothing to commit, working directory clean".
Restarting atom fixes the issue temporarily, until the next commit.

in 1.10.0-dev-5533365, it seems that changing a single file in a repository marks ALL (non-ignored) files as modified. Committing the change clears everything (correctly).

Tested again using 1.10.0-dev-0708140.
It seems the #12159 PR did indeed fix this, so I think this issue can be closed.

Yes I haven't had it happen anymore, will close it again.


str accessor inconsistencies #4334

[x] Closes #4334
[x] Tests added
[x] Passes isort . && black . && mypy . && flake8
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

Great, this looks good, thanks @mathause

@mathause Great! Can you merge when tests pass?

Thanks @mathause


Issues with Webpack cause by flux-standard-action

I'm using redux-promise and recently I updated my application from Babel 5 to Babel 6 and I'm running into issues building with Webpack.

ERROR in ./~/flux-standard-action/lib/index.js
Module build failed: ReferenceError: [BABEL] node_modules/flux-standard-action/lib/index.js: Unknown option: node_modules/flux-standard-action/.babelrc.stage

The error is caused by flux-standard-action, which in my case is only used by redux-promise.
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     ├──<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>
It seems to have been fixed (according to this ticket) in version 0.6.1. Can you update the dependency to 0.6.1?

I see @shinnn has a pull request for this already. https://github.com/acdlite/redux-promise/pull/26

@juancarlosfarah Yes, still waiting the @acdlite's review and merging.

Fixed in 0.5.2


Convention about Camera and Ray

Hi Jason,
Thanks for the work! I am interested in trying "CAMERAS AS RAYS" in our ongoing project. After quickly checking the codes, it seems we can use cameras_to_rays to convert pytorch3d cameras to PxP rays, and rays_to_cameras_homography to get the cameras back (with intrinsics). I was wondering:

Should we use cameras_to_rays and rays_to_cameras_homography for training? Should we keep the default flags, e.g., use_plucker=True?
All the cameras are assumed to be NDC Pytorch3D camreas?

Any clarification is much appreciated!
Best,
Jianyuan

Hi Jianyuan!
Yes, default flags should be good. We always train with a 16x16 set of rays with Plucker coordinates. Just a heads up, when converting rays to cameras using rays_to_cameras_homography, I believe that the output will actually give you inverse focal length, so just do 1 / the focal length that it gives you.
Our code assumes all cameras are NDC Pytorch3D cameras.


onSearchChange does not provide filtered results

Current Behavior
I have a table that I'm tracking a selected item but not the built in row selection code.  I'm using the rowClick code to track which item has been clicked on and selected and using some styling to highlight the row.
I've hooked into the onSearchChange event, but I have no way to know whether the displayed results still show the item that was selected prior to filtering.
Desired Behavior
It would be great to have some way to see what is actually displayed in the table.  Ideally as part of the callback arguments.
Unless I'm missing something obvious...

Tech
Version

Material-UI
^3.9.2

MUI-datatables
2.0.0-beta.59

React
16.6.0

browser
Chrome (latest)

Looking for such capability as well.

Sounds reasonable @rossknudsen can you propose your API change in a reply and let's see how it looks


Is there an example app?

I'd really like to see Chrome Custom Tabs in action. Is there a an example app available for demoing purposes?

isn't this the github for the sample app?

Sorry, I should have specified: Is the example app available for download / in the Play Store?

Valid request. Closed in favor of: https://code.google.com/p/chromium/issues/detail?id=541600


Fork and rename the project to zeek-kafka

Contributor Comments
This renames the project to zeek-kafka from metron-bro-plugin-kafka.  Many of the changes in this PR are based off of other plugins, such as Johanna's PostgreSQL writer, and establishes some basic governance.
TODO

[x] Run end to end
[x] Address this feedback

In searching around I found this stackexchange answer. Not sure yet if this indicates any specific action we should take to update copyrights, etc.

In searching around I found this stackexchange answer. Not sure yet if this indicates any specific action we should take to update copyrights, etc.

Looks like https://github.com/SeisoLLC/zeek-kafka/pull/1#pullrequestreview-560513472 answers this question.  Will add to TODO

e2e tests are now working.

In searching around I found this stackexchange answer. Not sure yet if this indicates any specific action we should take to update copyrights, etc.

Looks like #1 (review) addresses this statement. Will add to TODO

Read through section 4 of the license a few times and did some googling; I think e5e6990 should work, what do you think @ottobackwards?  The ASF intentionally leaves out any copyrighting from their recommended notice, but 4b requires notification of modification, and this open source stackexchange post seems to indicate that adding a copyright notice is sufficient.

In searching around I found this stackexchange answer. Not sure yet if this indicates any specific action we should take to update copyrights, etc.

Looks like #1 (review) addresses this statement. Will add to TODO

Read through section 4 of the license a few times and did some googling; I think e5e6990 should work, what do you think @ottobackwards?  The ASF intentionally leaves out any copyrighting from their recommended notice, but 4b requires notification of modification, and this open source stackexchange post seems to indicate that adding a copyright notice is sufficient.

I'm also considering a CI step to ensure that any modified files since the last commit to hit main have a copyright by the zeek-kafka contributors, what do you think?

I'm also considering a CI step to ensure that any modified files since the last commit to hit main have a copyright by the zeek-kafka contributors, what do you think?

@JonZeolla I think we are in agreement right?

@JonZeolla I think we are in agreement right?

I was also considering an old copyright.  I say we do that before merging this if we're going to

I was also considering an old copyright.  I say we do that before merging this if we're going to

Ok, per our conversation I also updated the license headers to be the typical apache 2.0 now that is no longer an asf project

Ok, per our conversation I also updated the license headers to be the typical apache 2.0 now that is no longer an asf project

Is this ready for review?

Is this ready for review?

Not yet, let me wrap up CI and double check my work.

Not yet, let me wrap up CI and double check my work.

Ok @ottobackwards this is good for review now

Ok @ottobackwards this is good for review now

@ottobackwards feedback addressed, back to you

@ottobackwards feedback addressed, back to you

GitHub support got back to me and they are opening an internal issue with the Actions team, but they expect that after merging this PR GitHub Actions will be enabled and start running for this and future commits/PRs.

GitHub support got back to me and they are opening an internal issue with the Actions team, but they expect that after merging this PR GitHub Actions will be enabled and start running for this and future commits/PRs.


FlaggedStorage changes

Related issue: https://github.com/amethyst/amethyst/issues/978
Uses a ComponentEvent enum instead of 3 separate channels.

This change is

Meh, conflict again :(

bors r=WaDelma
Thanks for all the reviews!


Use today date while adding a scheduled transaction in the future

Adding a scheduled transaction in the future results in the error "Historical rates for the requested date are not available - please try another date or contact<EMAIL_ADDRESS>Because of this issue, paired transactions are not created.
Please use today date instead date in the future.
The rates will be adjusted automatically when the transaction is marked as "Checked".

That makes sense. Thanks for reporting it.
We just released it. See commit


Update README

Just a reminder about the OSX install section in the README, seems to be outdated ?
I saw that assh was merged in homebrew (Homebrew/homebrew/pull/48815) and brew install assh is now functional.

I fully switch to assh, congrats it's really nice :heart:

Yep, I forgot to update the README.md, thank you !


[PRM-804] - Fixed bug on JS upload initial setup

https://user-images.githubusercontent.com/53828896/146422686-2a9c9b1a-6848-489a-b9ab-2ca7df0bfc72.mov
https://user-images.githubusercontent.com/53828896/146422693-dcb1c577-7dae-4839-b920-676c76bd2f9d.mov


Asset paths not generated for inline styles

Version
3.0.0-beta.2
Reproduction link
https://codesandbox.io/s/wz6989r7r5
Steps to reproduce
Run the sandbox and check generated source

What is expected?
Correct image link be generated
What is actually happening?
It is as is with '@' in URL

This is tracked in https://github.com/vuejs/vue-loader/issues/1113


Context, memory and changelog

Describe the bug
Revisions: It's hard to know exactly what is going on here, but It seems that the prompt does not have access to recent changes. This makes it a super frustrating experience, where I do changes in the code and then on the next prompt the ai overwrites all the work I have done. It is also not possible to commit changes and revert the sometimes insane changes the ai does. When I asked it to read back a variable from a file, it gave an old value, I asked it to check again and it said the same. When I then asked it to tell me the time of the last change it suddenly realised there was a newer version of the file.
Memory: The model seems to ignore our previous conversation. I had just managed to convince it that the correct rotation of an element was Math.PI and not -Math.PI, it took some effort to make it understand that, but it finally did. But then in the next prompt it insisted that the wrong rotation was the correct one, and without asking it makes a lot of changes to the code and by that deleting a lot of working code.
In general it seems to be brute forcing its way forward, being really inconsiderate of the work that has been done and destroying a lot of work in its path. This results in a very frustrating experience, where you constantly have to redo what you already have spend a lot of time fixing. I have also tried to give instructions to ask before doing changes to a file, but without memory or context that means I have to include it in every prompt.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-2beet3
Steps to reproduce
You really just have to use the software and try to make something a bit more complex than a one-pager.
Expected behavior
Not destroying everything in ints path.
Be considerate of resent changes.
Remember previous instructions.
Ask before doing changes.
Be able to commit and reverse changes. (I guess this should be a feature request)
Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

I see there is a feature request for reverting changes: https://github.com/stackblitz/bolt.new/issues/35

I experience exactly the same behavior and this is really frustrating. Please make some improvements.


decode command

allow url list argument as with encode

done but still needs work, not in scope of this ticket


Add Protocol Errors

Fixes #385 by adding specific protocol execution and results errors.

Tips

Comment "pre-commit.ci autofix" to have pre-commit.ci atomically format your PR.
Since this will create a commit, it is best to make this comment when you are finished with your work.

Checklist

[ ] Added a news entry

Developers certificate of origin

[x] I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

pre-commit.ci autofix

pre-commit.ci autofix

@ijpulidos since this PR addresses #385, would you be willing to offer your feedback on this one?

@hannahbaumann since you're working in detail on protocols, would you be willing to offer feedback on our choices here?


#5275 Template library [unitaryhack]

Summary
Proposed template library, that Closes #5275 .
Details and comments
I am currently actively working on this, please let me know if it requires reformatting.

all templates have now been added to the library

please let me know if there is a need for any additional commits or changes to the current proposal :)

hi @mgg39 it looks like you have some linting issues, you should be able to fix these by running tox -eblack

Hi @javabster ! Thank you so much for your help! I changed the ran tox -eblack, added the .py extension, and eliminated the s from templates (hopefully everywhere in the files) . Hopefully there won't be any issues now :)

Thank you very much @mgg39 for your contribution!
A few comments:

The templates (like other parts of the qiskit code) should have tests. Currently, the tests for the templates are here:
https://github.com/Qiskit/qiskit-terra/blob/main/test/python/circuit/test_templates.py
Now, this test should check the templates in the new Template Library.
However, there should be a minor correction: all the templates should be equal to identity, except of the Clifford templates which should be equivalent to identity (up to a global phase).

Currently the picture of the circuit of the template appears as a comment in the code, but not in the documentation of the template. It should be moved in a way such that it will appear as part of the documentation.

Hi @ShellyGarion !
I am quite new to test driven development. Could you give me some guidance on how the testing file should look like? I am unsure of where to start.
Also where exactly is the relevant documentation where I should add the pictures?

Please see the contributing guidelines about tests, code style, documentation and release notes:
https://github.com/Qiskit/qiskit-terra/blob/main/CONTRIBUTING.md

Thank you @1ucian0 , I am currently going through the testing materials to design the relevant tests. I agree that the pull request should probably stay in draft whilst I design these.

Hi @mgg39, how is that going?

Hi @mgg39, how is that going?

Hi @1ucian0 , sorry completely forgot about this with the new semester. Will try to finalise it this week :) Thank you for your patience!

hi! could I have some guidance of what elements might be missing still or breaking the checks?
Thank you in advance

Hi @mgg39 it looks like you have some conflicts, try fixing those first and then let's see if theres any CI issues. Also if your work is ready for review you can covert it to a regular Pr instead of a draft one 😄

hi! I believe the remaining conflict is associated with a slightly moved indentation at the end of " qiskit/circuit/init.py "

hi @mgg39 I resolved the merge conflict but you'll probably need to run make black again to sort out the indentation issue

hopefully they are resolved now!


Goland IDE Ctrl+S not surport

Use Goland to save a .go file with Ctrl+S ,not reload the program.

This is Jetbrains issue, it doesn't saves the file as most code editors and IDEs do; using the Operating System's calls. I think Jetbrains added an option that you can disable this behavior and use the standard operating system's method, if you find that setting and play with it, it will work :), post an issue at jetbrains if you can't find the option.

thank you,i had solved the problem by uncheck the  option [ ] use "safe write" (save changes to a temporary file first) in the goland behavior setting

You're welcome, this is useful information that we can put in our README as well. Have fun!


New design Heaviside pipeline

There are a few minor bugs I found so far:

In new_design_car_time_opt.m  - the model class created as Heaviside does not recognize S as a field.
one must use problem_options.dcs_mode = "Step", since "Heaviside" is not recognized, this should be fixed.
new_design_friction_blocks_stewart - simulating with Heaviside, one of the subproblem becomes infeasible for some reason - is it again maybe a bad initialization for the complementarity variables? (one may also look did it converge with the old implementation, just to isolate bugs)

**nurkanovic ** commented Jun 18, 2024

I am not sure yet how to resolve, if one wants to use PSS with the Heaviside reformulation, but calls the Heaviside model by creating the model object.
One way it to support both options if it does not make code to complicated, or to just throw an instructive error (e.g. when trying to put in an S into an Heaviside).

**nurkanovic ** commented Jun 18, 2024

I am not sure yet how to resolve, if one wants to use PSS with the Heaviside reformulation, but calls the Heaviside model by creating the model object. One way it to support both options if it does not make code to complicated, or to just throw an instructive error (e.g. when trying to put in an S into an Heaviside).

My view on this is RTFM :sweat_smile:. If a user uses the wrong class without reading even the top level documentation and gets Unrecognized property 'S' for class 'nosnoc.model.Heaviside' and doesn't immediately go to the docs I don't think that user can be saved.

new_design_friction_blocks_stewart - simulating with Heaviside, one of the subproblem becomes infeasible for some reason - is it again maybe a bad initialization for the complementarity variables? (one may also look did it converge with the old implementation, just to isolate bugs)

This is not a bug per se, but it is the fact that cross_comp_mode=3 and cross_comp_mode=4 were flipped. I need to check the Stewart version away.

What confused even me, that the commented code in the examples was suggesting that this is a valid path. :|

Hmm well that is definitely something we should avoid then. Strictly speaking the point is that the Heaviside DCS reformulation should take a PSS or a Heaviside model, and theoretically one could directly formulate  a PSS as an equivalent Heaviside model but that takes some thought.


Change to the newer prng interface of numpy and static type checking

The general idea of this pr is to move the random number interface we have been using from the legacy numpy one, to the 'new' one that was proposed years ago. In addition, a wide spread change to the type hinting of the package as mypy is used to hunt down small incongruencies in type hinting.

There are still somethings to do in the future, such as behavior around ppopt\solver_interface with some of the functions not able to take in optional arguments, mostly quadprog.


delayed-open task is platform specific

Problem:
https://www.npmjs.com/package/open
How it (is supposed to) work
on win32 uses start
on darwin uses open
otherwise uses the xdg-open script from freedesktop.org
"scripts": {
"delayed-open": "sleep 5 && open http://localhost:9000"
}
Solution: switch to https://www.npmjs.com/package/opener
Why
Because Windows has start, Macs have open, and nix has xdg-open. At least according to some guy on StackOverflow. And I like things that work on all three. Like Node.js. And Opener.
{
"scripts": {
"test": "opener ./test/runner.html"
},
"devDependencies": {
"opener": ""
}
}

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/33418196-delayed-open-task-is-platform-specific?utm_campaign=plugin&utm_content=tracker%2F32095848&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32095848&utm_medium=issues&utm_source=github).

closing as won't fix.  See https://github.com/cmelion/generator-ng2-webpack/issues/13.


Fix chaos code example column limit

Code example are displayed in boxes limited to 120 columns

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

@cBrauge : Thanks for your contribution! The author, @motanv, has been notified to review your proposed change.

Thank you @cBrauge for your contribution! We merged it in via the private Azure repo (so I could test the change on staging server...a definite improvement :-))


Upgrade to Polkadot-sdk v1.3.0

I think you should apply these changes not only to Cargo.dev.toml but also to all other Cargo.toml files.

This is no longer necessary because they recently updated all the Cargo.toml files to use the workspace dependencies
(https://github.com/open-web3-stack/open-runtime-module-library/pull/960) .


SQS Connector

closes #3

This looks like its till a work in progress.  Let me know if you are ready for a review.


program crashes with more than 6 instances

does anyone knw how to have 20+ instances of form/wpf instances got working at the same time?
when i got 6-10 the program crashes (svhost stop working) without any message, so i presume is the memory access violation issue.
thanks!

I didn't try over than 4 different cameras. But if it really It is a very big problem. Which version do you use in libraries?

the ones on the nuget packages

Did you look at the system memory usage after launching that much streams? I think this issue could be caused by the computer, not able to decode that many streams rather than a Vlc.DotNet issue.
Did you try launching 20+ Vlcs playing on your computer at a time?

nah the computer has 16GB of memory, the app usesbetween 4 to 8 GB... it looks more a memory leak or fragmentation problem

Yeah, but it might be a video memory issue or something like that. Does VLC show the same issue?

@xpachin , The problem is about CPU.

I've already using 8 different instances at the same time without problems. It consumes about 45% of the CPU of my laptop.

I'm closing this since there was no answer from original poster. Please try with libvlc 3.0 and reopen if this is still an issue.


Feature/rename ssclj #313

Initial changes for changing the service context for the clojure resources from "ssclj" to "api".

This PR should not be merged until the full functionality has been tested.  (However all of the defined unit tests pass.)

Connected to #313

Agreed with @st to merge this and then merge into other branches (and resolve issues) afterwards.


iOS 17 mobile example simulator crash.

Bevy version
v0.12.0-dev(de8a6007b7df5bd961511cd321344157fb4b531f)
What you did
Try to build the mobile example with XCode and launch it on the simulator.
What went wrong
It crashed with the next messages:
-[MTLDebugRenderCommandEncoder validateCommonDrawErrors:]:5775: failed assertion `Draw Errors Validation
Fragment Function(fragment_): the offset into the buffer _naga_oil_mod_MJSXM6K7OBRHEOR2NVSXG2C7OZUWK527MJUW4ZDJNZTXG_memberfog that is bound at buffer index 6 must be a multiple of 256 but was set to 448.

Additional information
https://github.com/bevyengine/bevy/assets/3709476/6ee2129e-d124-46b7-b247-c6af7b0ed487

started failing with https://github.com/bevyengine/bevy/pull/9865

@mockersf I am still encountering this one in bevy 0.12 in the simulator
-[MTLDebugRenderCommandEncoder validateCommonDrawErrors:]:5775: failed assertion `Draw Errors Validation
Vertex Function(vertex_): the offset into the buffer view that is bound at buffer index 0 must be a multiple of 256 but was set to 640.
Fragment Function(fragment_): the offset into the buffer view that is bound at buffer index 0 must be a multiple of 256 but was set to 640.

#12	0x0000000101c10220 in wgpu_core::command::render::_$LT$impl$u20$wgpu_core..global..Global$LT$G$GT$$GT$::command_encoder_run_render_pass_impl::ha922faef1c5c2345 at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-core-0.17.1/src/command/render.rs:1781
#13	0x0000000101c81944 in wgpu_core::command::render::_$LT$impl$u20$wgpu_core..global..Global$LT$G$GT$$GT$::command_encoder_run_render_pass::h6d7a155b479d705b [inlined] at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-core-0.17.1/src/command/render.rs:1199
#14	0x0000000101c818ec in _$LT$wgpu..backend..direct..Context$u20$as$u20$wgpu..context..Context$GT$::command_encoder_end_render_pass::h38258374e186109a at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.17.2/src/backend/direct.rs:1943
#15	0x0000000101c884ec in _$LT$T$u20$as$u20$wgpu..context..DynContext$GT$::command_encoder_end_render_pass::h33cb942cfb280fe6 at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.17.2/src/context.rs:2796
#16	0x000000010172e240 in core::ptr::drop_in_place$LT$wgpu..RenderPass$GT$::h94089a08f17621ab [inlined] at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/ptr/mod.rs:497
#17	0x000000010172e23c in core::ptr::drop_in_place$LT$bevy_render..render_phase..draw_state..TrackedRenderPass$GT$::he48cdc860fa6f676 at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/ptr/mod.rs:497
#18	0x000000010173516c in _$LT$bevy_core_pipeline..core_2d..main_pass_2d_node..MainPass2dNode$u20$as$u20$bevy_render..render_graph..node..Node$GT$::run::h261dc56d4d96381a at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_core_pipeline-0.12.0/src/core_2d/main_pass_2d_node.rs:80
#19	0x0000000101a1c584 in bevy_render::renderer::graph_runner::RenderGraphRunner::run_graph::hea019bad1f27a6e5 at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_render-0.12.0/src/renderer/graph_runner.rs:190
#20	0x0000000101a1c918 in bevy_render::renderer::graph_runner::RenderGraphRunner::run_graph::hea019bad1f27a6e5 at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_render-0.12.0/src/renderer/graph_runner.rs:197
#21	0x0000000101a1b6b4 in bevy_render::renderer::graph_runner::RenderGraphRunner::run::h1a13fe247870123a at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_render-0.12.0/src/renderer/graph_runner.rs:63
#22	0x0000000101934d50 in bevy_render::renderer::render_system::hf8fec1d16f936ffe at /Users/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_render-0.12.0/src/renderer/mod.rs:33

the cargo config file added in #10178 to the mobile example is now needed: https://github.com/bevyengine/bevy/blob/latest/examples/mobile/.cargo/config.toml


How to reset sync?

Hi, I was trying to tidy my omnivore notes on obsidian and noticed that after deleting some files locally, after syncing those files were not being restored.
Is there a cache or some configuration on obsidian that marks some notes as downloaded and as such can no longer be downloaded?

I cannot recreate this problem. Everytime I delete a file locally and execute the "Resync all articles" command, the note is created again.

I can't either, what's the wrong?
Only the first sync will create the folders and files
Then it doesn't work

#248
I found the same question now
he noticed that, you have to change your sync filter firstly, then you can sync once successfully
It's now a bug, and I can reproduce it steadily. Just choose sync filter to be "in:all" and don't change it
Luckily, there exist a method to avoid this bug now.


Rock 1.0.22 - batch two

added AST printer
fixed an error where the auto-generated Enum values() would crash if the enum elements are binary operations
support function call with arguments on tuples

this is now supported: (o1, o2, o3) someFunction(someArgument)

improved obfuscator

@fredrikbryntesson


Corrupted idIndex and $loki value

Issue #881 clearly shows the problem and it's still not fixed.
Basically the idIndex gets duplicate references and update throws a "Trying to update a document not in collection" error

I'm wondering why this happened, since a lot of things of this library is buggy, I did a lot of research about the source code, if there're more detailed scenario about the issue, we may find the solution.
For my case, all the data with duplicated key are the same, they are simply inserted twice, what about your case?


[FEATURE] @FromEnum(Enum.class)

Feature Description
Generated Class with fields based on Enum
This feater request appears from my question in StackOverflow
Basically that feature would allow creating a class with fields from enum class and if @Data or @Setter and @Getters are set, mark those fields as privet and generate setters and getter for them
Usage Code prototype:
Definition
public enum JwtFields {
    userId,
    country,
    sessionId,
    anyOtherField
}

@FromEnum(JwtFields.class)
@Data
public class JwtDeserialised {
    private String someAdditionalCutomFieldIfIwant
}

Usage:
String userId = jwtDeserialisedInstance.getUserId();
String anyOtherField = jwtDeserialisedInstance.getAnyOtherField();
String someAdditionalCutomFieldIfIwant = jwtDeserialisedInstance.GetSomeAdditionalCutomFieldIfIwant();

Target Audience
Anyone who using Enums as keys to avoid mistyping strings, and later need to deserialise that enum into proper class with sets and gets.

Why not taking the opposite direction: define your fields in the class and the use @FieldNameConstants(asEnum = true) to generate your enum?

We've implemented this, but as @janrieke showed, in the opposite direction: Make the class (and not an enum naming the 'fields').
Note also that the way you want it implemented requires resolution, i.e. is an extremely complex feature.

Thank you, guys! Awesome! another way around is also perfectly suited to me!


[1.12rc4] docker stats do not show info with NetworkDisabled=true

Steps to reproduce the issue:

start a container with NetworkDisable=true.
start docker stats

docker run do not expose NetworkDisable in any argument; To reproduce the issue, use the API directly. I use docker-py:
    response = client.create_container(
                "centos",
                command="sleep 100",
                network_disabled=True,
            )
    client.start(response['Id'])

Describe the results you received:
CONTAINER           CPU %               MEM USAGE / LIMIT       MEM %               NET I/O             BLOCK I/O           PIDS
adec7b0de828        --                  -- / --                 --                  -- / --             -- / --             --

So, no real output from docker stats for this particular container
Describe the results you expected:
More infos ;-)
Output of docker version:
Client:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:        Wed Jul 13 03:28:51 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:        Wed Jul 13 03:28:51 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 28
 Running: 2
 Paused: 0
 Stopped: 26
Images: 75
Server Version: 1.12.0-rc4
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 128
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host null overlay bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.954 GiB
Name: moby
ID: HFSP:6PBA:U5F4:5ZV7:EH7F:7OKJ:3ALL:PXGV:RWTY:F2RQ:JDCF:YTUW
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 28
 Goroutines: 57
 System Time: 2016-07-25T08:38:34.478361286Z
 EventsListeners: 2
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
I'm on Docker for Mac, I did not try on other OS.
Additional information you deem important (e.g. issue happens only occasionally):
Only tried on 1.12rc4.
When using the API endpoint (I tested with docker-py), the endpoint never returns any info.
Also, it is issue #25000.

The problem was already present with server/client 1.10.3 (tested on Fedora 24)

Thanks for testing the release candidates, and for reporting!

@GuillaumeDerval @thaJeztah The error case could also be invoked with docker daemon -b none and docker run -d busybox top. I created a PR #25905 to address this issue. Please let me know if there are any issues.


.dump - UnboundLocalError exception when GPS Data in text form is converted to bytes

Hi,
Firstly thanks for the awesome work on this library, which is perfect for the project I'm working on.
Just a heads up that if you try to write strings (I know, probably a dumb idea, but one I assumed to be correct at first) to the GPS Latitude/Longitude/Altitude Key EXIF fields using .dump, the following exception is thrown:

Traceback (most recent call last):
File "H:/files/Exif project/Exif_test.py", line 244, in
main()
File "H:/files/Exif project/Exif_test.py", line 50, in
process_images(data_list, difference)
File "H:/files/Exif project/Exif_test.py", line 130, in
write_exif_2_photo(entry, current_file, photo_exif_dict, photo_time)
File "H:/files/Exif project/Exif_test.py", line 190, in
photo_exif_bytes = piexif.dump(photo_exif_dict)
File "C:\Users\Alex.Liggett\AppData\Local\Programs\Python\Python36-32\Lib\site-packages\piexif_dump.py", line 74, in dump
gps_set = _dict_to_bytes(gps_ifd, "GPS", zeroth_length + exif_length)
File "C:\Users\Alex.Liggett\AppData\Local\Programs\Python\Python36-32\Lib\site-packages\piexif_dump.py", line 341, in _dict_to_bytes
offset)
File "C:\Users\Alex.Liggett\AppData\Local\Programs\Python\Python36-32\Lib\site-packages\piexif_dump.py", line 247, in _value_to_bytes
four_bytes_over = new_value
builtins.UnboundLocalError: local variable 'new_value' referenced before assignment

Happy to supply more information if it will help, but I suspect its something fairly straightforward.
Cheers
Alex

I probably have the same issue. My broken field is GPS['GPSHPositioningError']. iPhone treats this field as Ascii (type 2). So when we load exif data, this field is collected as Ascii (for example, b'65/1' for me). When we dump it, it tries to dump this Ascii field as it was Rational (type 5). Because in _exif.py this field is described as Rational.
We should probably either dump fields with the same type we loaded them or fix wrongly loaded types to canonical ones during dump (or right after load). Loading field by one rules and dumping by others is a way to errors.
Traceback (most recent call last):
  File ".\resize.py", line 105, in <module>
    byte_exif = piexif.dump(exif)
  File "C:\Program Files\Python37\lib\site-packages\piexif\_dump.py", line 74, in dump
    gps_set = _dict_to_bytes(gps_ifd, "GPS", zeroth_length + exif_length)
  File "C:\Program Files\Python37\lib\site-packages\piexif\_dump.py", line 341, in _dict_to_bytes
    '{0} in {1} IFD. Got as {2}.'.format(key, ifd, type(ifd_dict[key]))
ValueError: "dump" got wrong type of exif value.
31 in GPS IFD. Got as <class 'bytes'>.

Exif data in binary contains each data type. "load" uses it.
On the other hand, to "dump" exif data, it needs some reference to convert value into binary. I use object in _exif.py that was made from the specification(http://www.cipa.jp/std/documents/e/DC-010-2012_E.pdf).
To fix type, we need very tricky code.
b'65/1' or [some format that we can't unpredictable] or [other type and format] ->  (65, 1)
"dump" should doubt type data that contained in exif binary? I think no.
iOS should fix it to allow specification.

Exif data in binary contains each data type. "load" uses it.
On the other hand, to "dump" exif data, it needs some reference to convert value into binary. I use object in _exif.py that was made from the specification(http://www.cipa.jp/std/documents/e/DC-010-2012_E.pdf).
To fix type, we need very tricky code.
b'65/1' or [some format that we can't unpredictable] or [other type and format] -> (65, 1)
"dump" should doubt type data that contained in exif binary? I think no.
iOS should fix it to comply with the specifications.