python312Packages.reflex-chakra: 0.6.1 -> 0.6.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.reflex-chakra is: Chakra Implementation in Reflex
meta.homepage for python312Packages.reflex-chakra is: https://github.com/reflex-dev/reflex-chakra
meta.changelog for python312Packages.reflex-chakra is: https://github.com/reflex-dev/reflex-chakra/releases/tag/v0.6.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.2 with grep in /nix/store/4p9l0yhssh35zzx8n47d1q9bpkv57hzp-python3.12-reflex-chakra-0.6.2
found 0.6.2 in filename of file in /nix/store/4p9l0yhssh35zzx8n47d1q9bpkv57hzp-python3.12-reflex-chakra-0.6.2

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.reflex
python311Packages.reflex-chakra
python312Packages.reflex
python312Packages.reflex-chakra

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4p9l0yhssh35zzx8n47d1q9bpkv57hzp-python3.12-reflex-chakra-0.6.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.reflex-chakra https://github.com/r-ryantm/nixpkgs/archive/571e4a8dd2f344d6ebe31ae4dc60d28fcf1c88cc.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/571e4a8dd2f344d6ebe31ae4dc60d28fcf1c88cc#python312Packages.reflex-chakra

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4p9l0yhssh35zzx8n47d1q9bpkv57hzp-python3.12-reflex-chakra-0.6.2
ls -la /nix/store/4p9l0yhssh35zzx8n47d1q9bpkv57hzp-python3.12-reflex-chakra-0.6.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 8 packages built:

python311Packages.reflex
python311Packages.reflex-chakra
python311Packages.reflex-chakra.dist
python311Packages.reflex.dist
python312Packages.reflex
python312Packages.reflex-chakra
python312Packages.reflex-chakra.dist
python312Packages.reflex.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 351633

x86_64-linux

:x: 2 packages failed to build:

python311Packages.reflex
python311Packages.reflex.dist

:white_check_mark: 6 packages built:

python311Packages.reflex-chakra
python311Packages.reflex-chakra.dist
python312Packages.reflex
python312Packages.reflex-chakra
python312Packages.reflex-chakra.dist
python312Packages.reflex.dist


UCO should hint at Facet associations

Background
At present, any instance of a Facet is freely associable with any instance of a UcoObject.  This is in support of duck typing, where being a Foo implies having behaviors like a Foo, but having behaviors like a Foo does not necessarily imply being a Foo.  However, at present, UCO has no encoding of this.  "Foo" has no association with "FooFacet" stronger than any other "BarFacet" - e.g., uco-observable:File and uco-observable:FileFacet are as strongly related by structural design as uco-observable:File and uco-observable:URLFacet.  The string pattern-matching is clear, but would not cover cases where Facets should be associated with non-matching name patterns, like uco-identity:Person and uco-identity:SimpleNameFacet.
There is a mechanism to express this in OWL.  For File and FileFacet, this block of Turtle states that "If a thing is a File, there exists one FileFacet linked with hasFacet."
uco-observable:File
	rdfs:subClassOf [
		a owl:Restriction ;
		owl:onProperty uco-core:hasFacet ;
		owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ;
		owl:onClass uco-observable:FileFacet ;
	] ;
	.

(Syntax can be reviewed by checking for ObjectExactCardinality in OWL 2 Web Ontology Language Mapping to RDF Graphs.)
Adding this encoding does not cause data where there's a File with no FileFacet to be declared invalid.  OWL's open-world assumption leaves it fine to not record a FileFacet.
SHACL is not an appropriate mechanism to make such an expression.  This statement of existence can be represented with sh:qualifiedValueShape, but there's nothing being constrained, except the uniqueness of the specific facet type (i.e, no File can have two different FileFacets).  Specific facet type uniqueness is left out of scope of this proposal, and requires resolution of Issue 595.  The present proposal intends only to hint an inheritable association.
Requirements
Requirement 1
UCO SHOULD hint the Facet classes associated with any UcoObject subclass.
Requirement 2
The hinting mechanism MUST support arbitrary Facet associability---that is, if a pattern association is not present (like a "Foo" and "FooFacet" being related by suffixing), hard-coding an association should be possible.
Requirement 3
The hinting mechanism MUST NOT impede other abilities to associate Facet instances with UcoObject instances.
Risk / Benefit analysis
Benefits
This proposal helps to remove some of the obfuscation caused by housing properties in Facets rather than directly on UcoObjects.  Before this proposal, the tie between a File and the fileName property are as strong as the tie between a File and a latitude value.
Adoption of this proposal enables focused discovery of properties entailed by Facets from parent classes.  For instance, the CASE JSON-LD Stubs repository shows a stub for uco-observable:ArchiveFile here.  The Facet hinting in this proposal enables linking in the directly associated ArchiveFileFacet, as well as the parent class's FileFacet.  Both associations were drawn from the "Foo"/"FooFacet" pattern-match, which will be part of the implementation this proposal begins.
Reviewing the Facet hints also provides an opportunity to review Facets that have no current associated UcoObject subclass, clearing up currently unclear and/or forgotten use cases.
Risks
This proposal brings more OWL structural syntax into UCO.  This risk and syntactic complexity increase is suggested as acceptable because the need is believed inappropriate to meet with SHACL.
Concerns with accidental inference capabilities have been noted by some UCO Ontology Committee members.  The restriction illustrated in the proposal background has the following inferential effects:

On a File, if there are two FileFacets linked with hasFacet, the two FileFacets are inferred to be the same individual.  This is actually in line with previously expressed, but not yet encoded, understandings that "Specific" Facet classes are meant to be unique in typing on their "Host" objects.  (Again, a universal SHACL review mechanism for this uniqueness is deferred until after Issue 595 is adopted.)

On any non-File UcoObject instance, if there are two FileFacets linked with hasFacet, the two FileFacets are NOT inferred to be the same individual.  While not desirable, this is consistent with the current state of UCO.  (This would also be resolved after Issue 595.)

If a File has no FileFacet linked with hasFacet, there is NO automatic creation of a FileFacet node.
  (This would happen if owl:allValuesFrom were used.)
If some non-File thing has a FileFacet linked with hasFacet, the thing is NOT inferred to be a File.  (This would happen if a certain owl:equivalentClass construction were used.  The owl:Restriction used in this proposal is only "if", not "only if" or "if and only if".)

Last, while the "Foo"/"FooFacet" pattern will generate many of the owl:Restrictions, several Facet classes don't match this pattern, and will require manual attention and association.  A comment following this proposal will list the known non-mechanically-associable Facets subclasses.
Competencies demonstrated
The key competency generated in this proposal is support for mechanical discovery of properties of UcoObjects ("domain objects") that have been obscured by separation into Facets.  The JSON-LD stubs repository, especially with its ArchiveFile demonstration, is left as the demonstration of this new competency.
Solution suggestion

Generate the owl:Restrictions noted in the background for all "Foo"/"FooFacet" pairs.  Do so by importing the script facet_cardinalities_ttl.py.

This proposal is not suggested to wait for the entire resolution of hinting currently-unassociated Facets.

Adapt facet_cardinalities_ttl.py for an idempotent usage process - namely, not generating owl:Restrictions if it already exists in UCO.

This is slightly complicated by owl:Restrictions being syntactically required to be blank nodes.

Integrate the adapted facet_cardinalities_ttl.py into CI, to catch when a new "Foo"/"FooFacet" pair is added but an owl:Restriction is forgotten.

The test update is likely to be:  Generate a graph of new owl:Restrictions, and fail the test if any are generated, with a gentle suggestion to copy them in.

Coordination

Tracking in Jira ticket OCUCO-325

[x] Administrative review completed, proposal announced to Ontology Committees (OCs) on 2024-09-19
[x] Requirements to be discussed (informally) in OC meeting, 2024-09-26
[ ] Requirements to be discussed in OC meeting, 2024-10-24

[ ] Requirements Review vote has not occurred

[ ] Requirements development phase completed.
[ ] Solution announced to OCs on TODO-date
[ ] Solutions Approval to be discussed in OC meeting, date TBD
[ ] Solutions Approval vote has not occurred

[ ] Solutions development phase completed.
[ ] Backwards-compatible implementation merged into develop for the next release
[ ] develop state with backwards-compatible implementation merged into develop-2.0.0
[ ] Backwards-incompatible implementation merged into develop-2.0.0 (or N/A)
[x] Milestone linked
[ ] Documentation logged in pending release page
[ ] Prerelease publication: CASE develop branch updated to track UCO's updated develop branch
[ ] Prerelease publication: CASE develop-2.0.0 branch updated to track UCO's updated develop-2.0.0 branch

These Facet subclasses do not follow the "Foo"/"FooFacet" name pattern with the state of CASE 1.3.0 [sic.].

action:ActionArgumentFacet
action:ActionEstimationFacet
action:ActionFrequencyFacet
analysis:ArtifactClassificationResultFacet
core:ConfidenceFacet
identity:AddressFacet
identity:AffiliationFacet
identity:BirthInformationFacet
identity:CountryOfResidenceFacet
identity:EventsFacet
identity:IdentifierFacet
identity:LanguagesFacet
identity:NationalityFacet
identity:OccupationFacet
identity:OrganizationDetailsFacet
identity:PersonalDetailsFacet
identity:PhysicalInfoFacet
identity:QualificationFacet
identity:RelatedIdentityFacet
identity:SimpleNameFacet
identity:VisaFacet
location:GPSCoordinatesFacet
location:LatLongCoordinatesFacet
location:SimpleAddressFacet
observable:AccountAuthenticationFacet
observable:AntennaFacet
observable:CompressedStreamFacet
observable:DataRangeFacet
observable:EXIFFacet
observable:EncodedStreamFacet
observable:EncryptedStreamFacet
observable:ExtInodeFacet
observable:ExtractedStringsFacet
observable:FilePermissionsFacet
observable:FragmentFacet
observable:MftRecordFacet
observable:NTFSFilePermissionsFacet
observable:PathRelationFacet
observable:PropertiesEnumeratedEffectFacet
observable:PropertyReadEffectFacet
observable:SendControlCodeEffectFacet
observable:StateChangeEffectFacet
observable:TwitterProfileFacet
observable:UNIXFilePermissionsFacet
observable:UNIXVolumeFacet
observable:ValuesEnumeratedEffectFacet
observable:WhoisContactFacet
observable:WindowsVolumeFacet
observable:X509V3ExtensionsFacet
tool:BuildFacet

I am all for having some sort of hinting to associate potential or likely connections between particular UcoObject classes and certain Facets.
It is kind of late as I am reviewing this so I am not 100% confident in my read of the semantic logic and inferencing implications of the proposed approach but these two issues would be my main concern that any solution must avoid:

If a File has no FileFacet linked with hasFacet, there is NO automatic creation of a FileFacet node.

If some non-File thing has a FileFacet linked with hasFacet, the thing is NOT inferred to be a File. (This would happen if a certain owl:equivalentClass construction were used. The owl:Restriction used in this proposal is only "if", not "only if" or "if and only if".)

If you have verified that these are not issues with the proposed approach then my main concerns are assuaged.
If the following is the only real semantic issue then I agree that this is not a deal-breaker and is likely worth eating in order to get the hinting:

On a File, if there are two FileFacets linked with hasFacet, the two FileFacets are inferred to be the same individual. This is actually in line with previously expressed, but not yet encoded, understandings that "Specific" Facet classes are meant to be unique in typing on their "Host" objects. (Again, a universal SHACL review mechanism for this uniqueness is deferred until after Issue 595 is adopted.)
On any non-File UcoObject instance, if there are two FileFacets linked with hasFacet, the two FileFacets are NOT inferred to be the same individual. While not desirable, this is consistent with the current state of UCO. (This would also be resolved after Issue 595.)

I am all for having some sort of hinting to associate potential or likely connections between particular UcoObject classes and certain Facets.
It is kind of late as I am reviewing this so I am not 100% confident in my read of the semantic logic and inferencing implications of the proposed approach but these two issues would be my main concern that any solution must avoid:

If a File has no FileFacet linked with hasFacet, there is NO automatic creation of a FileFacet node.

If some non-File thing has a FileFacet linked with hasFacet, the thing is NOT inferred to be a File. (This would happen if a certain owl:equivalentClass construction were used. The owl:Restriction used in this proposal is only "if", not "only if" or "if and only if".)

If you have verified that these are not issues with the proposed approach then my main concerns are assuaged.

The verification is in this Gist.


ADSB low flying near me reporting

I wish to find a magic way for my existing ADS-B feed to create and (preferably e-mail me) a daily report, including aircraft ID, speed, heading, date, time, altitude, etc., of any aircraft lower than 1000 ft that my device receives.
I want this because I am tired of helicopters making my house shake since I live under their approach to a local airport.
I am not a coding or pi expert; therefore, a more straightforward and easier-to-implement solution is preferred.
Thank you, Michael

You asked this question a few months ago.  The response is still the same: this would be custom work, feel free to get in touch if you would like to pay to have it done.

Thank you for replying.
Enjoy your weekend.
Michael Del Greco
@.***
56 Woodland Drive
Woodland Park, NJ 07424
On Friday, October 25th, 2024 at 11:12 AM, Paul Eastham @.***> wrote:

You asked this question a few months ago. The response is still the same: this would be custom work, feel free to get in touch if you would like to pay to have it done.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Logging with apex/log

Nice logger with support for multiple handlers. Swapped out the gorilla logger for this one and added in logging for the stages of a job.

[Current coverage][cc-pull] is 65.78%

Merging [#77][cc-pull] into [master][cc-base-branch] will increase coverage by 0.07%

@@             master        #77   diff @@
==========================================
  Files            14         15     +1
  Lines           589        602    +13
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            387        396     +9
- Misses          153        157     +4
  Partials         49         49

Powered by Codecov. Last updated by [498e1aa...8232368][cc-compare]
[cc-base-branch]: https://codecov.io/gh/snickers/snickers/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/snickers/snickers/compare/498e1aa5171a8981069a4a76f2a070837ead8eb0...82323686f0a161299ad029677372362c8027ba2b?src=pr
[cc-pull]: https://codecov.io/gh/snickers/snickers/pull/77?src=pr

thanks for that @blainsmith, do you think we should log the steps of a given job even if they don't fail?


Reflection warning, com/rpl/specter/impl.cljc:330:25 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, com/rpl/specter/impl.cljc:345:25 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, com/rpl/specter/impl.cljc:349:9 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, com/rpl/specter/impl.cljc:665:14 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, com/rpl/specter/impl.cljc:890:3 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, com/rpl/specter/macros.clj:9:6 - call to java.lang.IllegalArgumentException ctor can't be resolved.
Reflection warning, com/rpl/specter.cljc:601:7 - call to java.lang.IllegalArgumentException ctor can't be resolved.
[...]

Minor stuff, but it's a bit noisy when reflection is "on" on the parent project.
I didn't test the cljs side of things.

In order to merge this in I'll need a contributor agreement signed. I sent one over to the email listed in your Github profile.

Done

Merged, thanks for the contribution.


Different versions of model viewer in the same DOM

I’m thinking of a scenario where I would want to dynamically add a model-viewer element on a customer’s website, not knowing if that website already has a model-viewer script tag in its DOM.
(Note: I'm talking about the script tag to import model-viewer, not the model-viewer tag itself).
Also, if that website already has a model-viewer script tag in its DOM, now the issue would be the version of the existing model-viewer script tag. (Assuming that I need to work with a specific version of model-viewer).
If a model-viewer script tag is already in the DOM and we try to include our own model-viewer script tag, the CustomElementRegistry will throw an exception, because the "model-viewer" custom element name is already in the registry. Thus, the model-viewer version used will be the one of the existing script tag.
The only solution I can think of to be able to use a specific version of model viewer in my dynamically added HTML on a customer's website would be this:
Have a custom distribution of model-viewer with a different custom element name (ex: my-model-viewer).
This way, there would be no conflict in the CustomElementRegistry when trying to include my own script tag, and by using a my-model-viewer tag, also making sure to use the specific version I need.
Does that make sens? Could it have some side effect I'm not aware of?
Is there any better solution to this problem?
Thanks

@fivelive thanks for reporting!

Have a custom distribution of model-viewer with a different custom element name (ex: my-model-viewer).

I think this is probably the most pragmatic approach. There is a future feature called Scoped Custom Element Registries that might give you a better option someday, but for now I would recommend that you just have a custom build that uses a specialized tag name.
Another thing you could try, if are willing to make a custom build and you want to get fancy, is something like this:
let number = 1;
let tagName = 'model-viewer';

while (customElements.get(tagName != null) {
  tagName = `${tagName}-${++number}`; // Try model-viewer-2, model-viewer-3, model-viewer-4 etc.
}

customElements.define(tagName, ModelViewerElement);

But in practice, you are probably safe 99% of the time if you just pick a unique tag name like <mycompany-model-viewer>.
That said, the main areas (that I can think of) that could cause problems are the following:

If you do anticipate that more than one <model-viewer> is on the page, keep in mind that right now model-viewer.js is a very large JavaScript bundle, and the end-user probably won't be very happy to view a website where they have to download it twice. We have plans to make this better (e.g., #931 , #337 ), but for now you would have to manually optimize the bundle to mitigate this issue.
If our code ever attempts to count the number of <model-viewer> elements on the page, it will probably do so either by keeping track of connectedCallback/disconnectedCallback invocations, or by counting constructor calls, or by doing document.querySelectorAll('model-viewer'). If you load two different <model-viewer> implementations on the page, they probably won't be able to correctly account for each other. We plan to use the number of instances to decide how to do rendering under the hood (see #995), and we might choose the wrong optimizations in cases like this.
Our caching mechanism will be sharded by the number of distinct bundles that bring in the <model-viewer> module graph. This means that if you load both model-viewer-1.js and model-viewer-2.js,  <model-viewer-1 src="Astronaut.glb"> and <model-viewer-2 src="Astronaut.glb"> will cause the Astronaut.glb to be loaded and cached twice. This is bad both in terms of network usage and device memory usage.

There are probably other caveats, and I'll try to document them for you if I think of them. In general, it should be feasible for you to define multiple, different tags for ModelViewerElement, and we will try to support that in case there are bugs. However, I would strongly encourage you to consider the performance consequences of loading multiple model-viewer.js bundles on a given page! We have seen iOS Safari crash after loading just a few models at once (due to low memory ceiling) and there is nothing we can do to fix that for you when it happens.

Waouw! Thanks @cdata for this complete answer, you really helped here.
Yes, if you ever see any other downside, do not hesitate to share it.
Thanks again!


Adds blog for SigV4 support in clients

Signed-off-by: Harsha Vamsi Kalluri<EMAIL_ADDRESS>Description
Adds a new blog entry for SigV4 support in OpenSearch clients.
Issues Resolved
Closes #1176
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

I think we should add some verbiage to the article mentioning that this won't allow for access to OpenSearch serverless, and that to connect to that, you would need to follow the instructions here: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-clients.html#serverless-java

I think the article is missing Go, and it ends with a request to contribute issues to the python repo, but it may be better to send people to the project site (https://github.com/opensearch-project).

I think the article is missing Go, and it ends with a request to contribute issues to the python repo, but it may be better to send people to the project site (https://github.com/opensearch-project).

Good catch. Added that info.

Hi @natebower @krisfreedain I've fixed DCO and updated the publish date to 12/13. This should be good to go.


How to get Webpack to compile TypeScript from node_modules?

I've just created 2 new.projects. I wanted to share code between them with npm. I added dependency in package.json like "common-ui": "git@github.com:someorg/common-ui.git#develop". This repo has a simple file structure with some interfaces and images. I realized that files are not loaded. There was an error 'You may need an appropriate loader to handle this file type'. So I run npm run eject to change webpack config. I tried with editing babel loader like this:
            // Process application JS with Babel.
            // The preset includes JSX, Flow, TypeScript, and some ESnext features.
            {
              test: /\.(js|mjs|jsx|ts|tsx)$/,
              include: paths.appPath,
              loader: require.resolve('babel-loader'),

I tried to include all the files. Now I'm getting 'SyntaxError: ...Unexpected token' when I try to import TypeScript class.
How to fix this?

@kamil-cledar you can try setting up your project similar to this repository: https://github.com/anthanh/lerna-react-ts-transpile-modules. As far as I'm concerned, this is only supported in CRA 3.x at the moment.


wechaty掉了，但是watchtower一直显示alive。

左侧是wechaty；右边是watchtower

早上看到，昨晚wechaty断了，但是watchtower没侦测到。
而且用0.65的版本挂token，但是wechaty断了，每次都需要重新扫码。导致即使restart container也连不上微信。

After a lot of experiments, I find the reason why I need to scan the QRcode every time when the code start. It is because my wechat account is registered by a foreign phone number. When I change to the native phone number, It can be used. Wechat seems like make some specific rules for the foreign account. Wasted a lot of time, hopefully this experience can save other users time.


drivers: flash_sam: fix flash_sam_write_page

According to Atmel SAM datasheet when writing data to the latch buffer
"32-bit words must be written continuously, in either ascending or
descending order. Writing the latch buffer in a random order is not
permitted." To enforce the requirement we need to call a memory barrier
instruction after copying every word of data to the latch buffer. In
the absensce of __DSB() call the ARM processor is free to change order
of AHB transfers. This has caused the driver to occasionally corrupt
data programmed in the flash.
Also assure cache coherency before triggering flash write operation.
Fixes #37515

Looking at the datasheet, I have found this in section 11.1.5:
When accessed by the Cortex-M7 processor for programming operations, the QSPI and internal Flash address spaces must be defined in the Cortex-M7 memory protection unit (MPU) with the attribute 'Device' or 'Strongly Ordered'. For fetch or read operations, the attribute ‘Normal memory’ must be set to benefit from the internal cache.

Good catch. I overlooked this paragraph. In any case from the functional point of view it should make no difference if we define memory region with the attribute 'Device' or 'Strongly Ordered' or use __DSB() instruction. The end effect should be the same.

The MPU currently configures the flash region in writethrough mode (so I guess the cache clean operations are not necessary)

Yes, I'll remove the cache clean. I'm only not clear if (and how) I need to make sure that the memory is written before we trigger the flash write by  writing to EEFC_FCR register. Merely calling __ISB() is probably not good enough. Well, taking into account that this part has been working fine so far it may be best not to touch it.


Camera perspective icons not working properly after manually changing camera position and orientation.

Steps to reproduce

Use camera perspective icons, it works normally.

Manually change camera orientation, position, and zoom using the mouse's right and left buttons and the wheel in the visualizer window.

Use camera perspective icons again and click on them multiple times.

(I've tried with different models, and the error can be reproduced in all of them)
Expected result
After manually changing the camera position and orientation, the buttons should work exactly as before manually changing them.
Actual result
After manually changing camera position and orientation, if you click on the perspective icons, the model is not positioned as expected.
For example, if I manually position the camera as in the next screenshot:

And then, I click the perspective button to see the model from above, this is what I get:

If I click the button multiple times, or I try clicking any of the other buttons, the camera changes its position and orientation weirdly until the model disappears.

Environment and GUI version

Opensim version: 4.4-2022-05-17-cc0a2cf
OS: Windows 10 Pro 64 bits
Display: 15.6” 1920x1080

This was verified fixed in later beta builds


Rails: Support reloading of classes in development

At the moment changing a method in a class descending from ContentfulModel::Base requires full reload of Rails environment.
Example:
class TestModel < ContentfulModel::Base
   self.content_type_id = 'test'

   def title
      "This is the title!"
   end
end

# eg. in "rails console"
irb(main):001:0> TestModel.first.title
=> "This is the title!"

Changing the #title method:
....
def title
   "New title?"
end
....

And then reloading:
irb(main):002:0> reload!
Reloading...
=> true

irb(main):003:0> TestModel.first.title
=> "This is the title!" # Would have expected "New title?" here

The problem that is breaking reloading is that mappings are not readded if the class is redefined:
https://github.com/contentful/contentful_model/blob/b286afd939daae87fdeb1f320f43753dcaae3144/lib/contentful_model/base.rb#L123
If I override this method to return false, the class gets reloaded fine in development.
class TestModel < ContentfulModel::Base
   # ....
  def self.mapping?
    false
  end
end

This happens because the rails environement persists class variables like entry_mapping, and that mapping contains a reference to the old version of the model.
I don't know if that helps.

Here is how this problem can be fixed
module MyApp
  class Application < Rails::Application
    config.to_prepare do
      ContentfulModel.configuration.entry_mapping.each do |content_type_id, model|
        ContentfulModel.configuration.entry_mapping[content_type_id] = Object.const_get(model.to_s)
      end
    end
  end
end

It is still an expiemintal solution I am keeping an eye on it in my current project.
And if it will work I will send a PR with a more generic fix

@dlitvakb Do you still need more information in order to understand how to improve this? This has been one of the most frustrating parts of using this library :(


Add GAX error details attribute

The details attribute provides easy access to deserialized error
details. Previously, API custom error types were only accessible
by inspecting the gRPC error, and then only availabe in serialized
form.
Fixes
https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1438

Codecov Report

Merging #89 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
- Coverage   98.64%   98.61%   -0.03%
==========================================
  Files          20       20
  Lines        1767     1803      +36
==========================================
+ Hits         1743     1778      +35
- Misses         24       25       +1

Impacted Files
Coverage Δ

spec/google/gax/grpc_spec.rb
100% <100%> (ø)
:arrow_up:

lib/google/gax/grpc.rb
100% <100%> (ø)
:arrow_up:

lib/google/gax/errors.rb
100% <100%> (ø)
:arrow_up:

spec/google/gax/bundling_spec.rb
99.69% <0%> (-0.31%)
:arrow_down:

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 fd59665...a3305df. Read the comment docs.


InstallUpstreamKernel.py: fix initrd file string

Parse the initrd file name correctly for kexec to use the proper
initrd file, in a case where we have 2 initrd file with same kernel
release version, the existing script choses the last file, this code
will make sure it uses the exact initrd file for kexec
Signed-off-by: Abdul Haleem<EMAIL_ADDRESS>

I have an example on my CI test system
Before this fix
initrd_file = con.run_command("ls -l /boot/initr*-%s*" % kern_rel_str)[-1].split(" ")[-1]
[root@ltc-zz1b-lp2 linux]# ls -l /boot/initr*-5.6.0-rc7+*
-rw------- 1 root root 28297305 Mar 27 08:37 /boot/initramfs-5.6.0-rc7+.img
-rw------- 1 root root 19106779 Mar 25 08:42 /boot/initramfs-5.6.0-rc7+kdump.img
initrd_file = '/boot/initramfs-5.6.0-rc7+kdump.img'
kexec fails as the initrd file was wrong
After this fix
initrd_file = con.run_command("ls -l /boot/initr*-%s.img" % kern_rel_str)[-1].split(" ")[-1]
[root@ltc-zz1b-lp2 linux]# ls -l /boot/initr*-5.6.0-rc7+.img
-rw------- 1 root root 28297305 Mar 27 08:37 /boot/initramfs-5.6.0-rc7+.img
initrd_file = '/boot/initramfs-5.6.0-rc7+.img'
kexec works fine as the string is parsed correctly

console logs
consolelogs.txt

@sathnaga do you have any suggestions here ?

is self.cv_SYSTEM.goto_state(OpSystemState.OFF) required.

Yes this is required, after a CI run the system will be in inconsistent state and so the system needs reboot for a next fresh run


Split Build all task (with/without tests)

Not sure about this one. Don't really want to clutter the build list too much
If you are building an executable it will not build the tests
If building a library, Xcode builds the tests always

I knew little about Xcode's behavior, and was proposing this based on the CLI interface of SwiftPM.
On Windows, some packages may build, but there tests are not ready yet.  In order to verify whether a package can be built, it's necessary to not build the tests, which are already known to be broken.

I'm going to close this. If you really want to build without tests you can always create a tasks.json entry


add script to automatically add everything to "Issue" project

first step of #388

add every issue to the "to do" column
add every pull request to the "review in progress" column

worked fine :)


Presenter notes in Google Hangout

Hi - currently if I do presentation mode while in a Hangout, the presenter notes are shown in the hangout as well. Would be nice to fix this so the notes are shown to just me and only the full screen slides are shown in the Hangout. My company uses Google CFM (Chrome For Meetings) in all of our conference rooms. Thanks.

I'not familiar with how Hangouts/CFM works. If you clone your slideshow by pressing 'C', and share the new window using Hangouts/CFM, you can put your old window in presenter mode and not share that.

Great idea! Just tried it today and it works well.. thanks!

@gnab Hello, as a side issue - is there a way to get a pointer (or the mouse cursor) to mirror between the presenter view and the cloned view? So that I can have my cloned window shared with the audience in a Google meeting - while viewing the presenter mode in another window - yet still be able to point to things in my window and they can see my pointing in theirs? If that makes sense??


WindowDesc should not be reusable

Currently WindowDesc can be theoretically reused, but this is broken; if this was actually done it would cause the reuse of window ids, which would be a bug.
Relatedly, there was a separate issue  raised in  zulip by @crsaracco wanting to pass a channel  into a WindowDesc, which seems like a very reasonable use case.

This issue is actually harder than I initially thought, because Command requires things to be cloneable, which means we would have to do something tricky to make WIndowDesc single-use.


Unable to connect to tableau server using TableauServerClient python library

I am trying to sign into TSC with the following:
tableau_auth = TSC.TableauAuth(name, password, site_id=site_id)
server = TSC.Server('http://10az.online.tableau.com', use_server_version=True)
print(server.version)
# Sign in
server.auth.sign_in(tableau_auth);

I am getting this error message.  I have never got this message before when trying to sign into the server with TSC
SSLError: HTTPSConnectionPool(host='10az.online.tableau.com', port=443): Max retries exceeded with url: /api/2.4/serverInfo (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))
Does anybody have an idea why this is happening?

I think you have connected to a Tableau Server enabled SSL. You need to verify and make your client program trust the SSL certificate.
Firstly you need to make sure you use the right url.
Secondly, if you want to skip verification of SSL cert, you can simply use
server.add_http_options({'verify': False})

I'm going to close this based on age, but if you are still having trouble please reopen with the latest details.


add lang attribute to  tag

tell the browser what language we're using.
Some content might be in another language and this sometimes triggers the auto-translate option in Chrome.

Thanks!


Documentation fix: set_disabled refers to required attribute.

Noticed this while reading through the documentation yesterday. I think this was a copy and paste error from the set_required directly above it.

Coverage remained the same at 86.824% when pulling db59a842451c1f761d7ed6abce2f0468bc73d1c1 on percipient:doc-fix into d7b6a36a90ca5a249710c1493ece224e20b9eaff on dyve:develop.

Thx


[GitHub] Update GitHub issue/PR labels

This is my proposal on how we should update labels on GitHub so that they are more useful and readable. I don't need help with the operation itself, but would like some feedback before i start :slightly_smiling_face:
https://docs.google.com/spreadsheets/d/1WYt0IHc2N5pWhMSfN7vlFaXgssV_pdAlL0UxAo5yblE/edit?usp=sharing

This looks great to me. Thanks for the work.


Add Use cases to Developer Guide

assign a tag to the company with the company name as the tag

What does this mean?

since currently the company doesn't have any relation to the tag, the tag used by event and contact person is not associated to the company if I don't assign it.


Loading symbol while waiting for data?

Is there any way to render a loading template (or a basic loading spinner) while data is being loaded? I suppose it should be a trick regarding some DataTables callback, but I have no clue. Any suggestions please?

+1, Perhaps i'll submit a PR for this soon.

+1 Would love to have this feature.

+1

+1

+1

I ended up needing to hide the table while it was hiding so I started a spinner, tracked the collection the table uses, then on tracker change, stop the computation and clear the spinner. This switches the session var so the template unhides the table and shuts off the spinner.

:+1:

Closing as duplicate of #130


The use cases of Lambda CI?

(Warning: rant and rave ahead.... )
I found this repo weeks ago where I was struggling building a CI-like project with Amazon Lambda. This repo is great, definitely. Your wonderful lambci saved me 100 hours by providing helpful tips and examples (especially the LambdaCI layer). Thank you!
However, it downed upon me that it might be better to switch to Amazon ECS or other docker-based systems. It's also worthwhile to try CircleCI / TravisCI. The reason behind this: AWS lambda is designed for stateless, lightweight tasks, while CI is stateful and usually IO-heavy. Even with the lambci project, devops still have to spend lots of time on overcoming the limitations imposed by AWS lambda, such as:  read-only file system, very counter-intuitive requirements of placing python modules inside the deployment package, etc.... Time is costly. I would rather pay for ECS or subscribe to a CircleCI plan than spending time on Lambda walkarounds.
I believe you guys must have very good reasons to stick to Lambda for CI. Demonstration of lambci's use cases would be highly appreciated.

Sounds like AWS CodeBuild does exactly what you want: https://aws.amazon.com/codebuild/
LambCI is useful for any domain in which you're not limited in the ways you list (although I'm confused about your "placing the python modules inside deployment package" statement – you can just install them with pip in your LambCI build).
I disagree with some of your other statements: Besides caching (which you can do on S3), your CI should not be stateful. Statefulness introduces reproducibility issues into your build process. Also, Lambda excels at I/O – speeds are very fast from S3 for example – so I'm not sure what you're referring to there.
The one big difference between LambCI and other CI offerings is performance – especially with parallel processes. You can split your build into 1000 different steps and run them all in parallel and have it finish in seconds. You can't do that with any other CI system that I'm aware of (unless you build your own cluster)
However, I'm certainly not advocating that you use LambCI if it's not right for your project – and that goes for any system you want to run on Lambda too.

Thanks a lot
I am particularly intrigued by the S3 part. I am curious about how S3 plays a role in LambCI (or any CI system that is based on Lambda)
Could you please elaborate how we can do caching on S3?
What is cached here? (the HEAD commit, a git branch, or the build artifacts) ?
The reason for asking this dumb question is, as far as I know, Lambda does not allow mounting S3 as part of Linux file system, so we cannot manipulating S3 in the same way as a local file. Such design makes S3-based file I/O very inconvenient....

Besides caching (which you can do on S3)
Lambda excels at I/O – speeds are very fast from S3 for example

sorry for the confusion made by me in the original post
by mentioning

very counter-intuitive requirements of placing python modules inside the deployment package

I was referring to the fact that, after installing python modules with pip , those python packages are located under ./venv/site-packages folder of the deployment package , but AWS' deployment package spec requires those packages located under the root folder of the deployment package, so that whenever making a build, I have to move the folders of those python packages.
Of course, this is just a single line  of mv command in my CI script of making a new AWS Lambda deployment package


[5.5] Pass request object to register create method

laravel: https://github.com/laravel/laravel/pull/4172

See comment on corresponding PR.


Tab controls

The tabs should be accessed by pressing on them instead of just using command 1, 2, and 3.

It looks like this requires click event handling on the tabs. This should make #11 an easy fix.


Events functions

Be careful, you didn't changed everywhere the name of the function! (documentation for example)

you commited changes in other files that are not related to this release (layout.ejs)

Waiting for your changes so :p

It's good ! ^^


Pixel gap between adjacent UI grid cells

Bevy version
11.2
Relevant system information
INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1.1666666666666667
INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce GTX 970", vendor: 4318, device: 5058, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "535.98", backend: Vulkan }

What you did
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .run();
}

fn setup(mut commands: Commands) {
    commands.spawn(Camera2dBundle::default());

    commands
        .spawn(NodeBundle {
            style: Style {
                display: Display::Grid,
                grid_template_columns: RepeatedGridTrack::min_content(2),
                margin: UiRect::all(Val::Px(4.0)),
                ..Default::default()
            },
            background_color: BackgroundColor(Color::PINK),
            ..Default::default()
        })
        .with_children(|commands| {
            for color in [Color::GRAY, Color::DARK_GRAY] {
                commands.spawn(NodeBundle {
                    style: Style {
                        display: Display::Grid,
                        width: Val::Px(160.),
                        height: Val::Px(160.),
                        ..Default::default()
                    },
                    background_color: BackgroundColor(color),
                    ..Default::default()
                });
            }
        });
}

What went wrong
The vertical pink line seems to be related to the margin, as it doesn't appear with a zero margin. But varying values of width and height for the cells also make the gap disappear. Maybe related to #7712, although not a regression (I tested the sample on 11.2 and it works).

Yep, replicates on main.
The example needs to be recreated in Taffy, if anyone feels like doing some work.

Yep, replicates on main.
The example needs to be recreated in Taffy, yrns want to carry on with this?

I can try, sure.

I thought this might be a bug in Taffy's rounding but I was unable to reproduce the issue. The following test (which is intended to be the original layout above, with the scale factor pre-applied to the styles):

   <div style="width:<PHONE_NUMBER>67px; height:<PHONE_NUMBER>67px">

   <div style="width:<PHONE_NUMBER>67px; height:<PHONE_NUMBER>67px">

Results in the following gapless layout:
TREE
└──  FLEX [x: 0    y: 0    width: 383  height: 196 ] (NodeId(4294967300))
    └──  GRID [x: 5    y: 5    width: 373  height: 186 ] (NodeId(4294967299))
        ├──  LEAF [x: 0    y: 0    width: 186  height: 186 ] (NodeId(4294967297))
        └──  LEAF [x: 187  y: 0    width: 187  height: 186 ] (NodeId(4294967298))

However, I have remembered that Bevy isn't currently using Taffy's rounding. So I don't think a bug in Taffy's rounding would even affect Bevy.

We could try switching Bevy back to using Taffy's rounding now that the bugs with that have been fixed (would need to bump minimum Taffy version to 0.3.13). But looking at the Bevy code, it looks like we're currently scaling values after rounding:

I suspect such code is liable to cause issues like this even is rounding is performed correctly. I believe the pixel-grid snapping really needs to be the last step in the process if it is the effectively eliminate gaps.

FWIW, I could not reproduce in Taffy either. This is what I get in Bevy (11.2, taffy 0.3.10) for comparison:
TREE
└──  FLEX [x: 0    y: 0    width: 1252 height: 1361] (1v1)
    └──  GRID [x: 4.6666665 y: 4.6666665 width: 373.33334 height: 1351.6666] (4v1)
        ├──  LEAF [x: 0    y: 0    width: 186.66667 height: 186.66667] (2v1)
        └──  LEAF [x: 186.66667 y: 0    width: 186.66667 height: 186.66667] (3v1)

I suspect such code is liable to cause issues like this even is rounding is performed correctly. I believe the pixel-grid snapping really needs to be the last step in the process if it is the effectively eliminate gaps.

This makes sense. I made the change and it seemed to work, branch here: https://github.com/ickshonpe/bevy/tree/round-after-scaling
This means we either need support in Taffy for scale factor so it can apply the scaling before it does the rounding or we need to carry on performing the rounding ourselves, I think?


clean up wallet implementations for bip44 and daedalus

The previous implementation tried to accommodate both models, however this made the code very unstable and more complicated. In this PR we try to define a unified interface for what a wallet should provide (the traits Wallet and Account in cardano::wallet::scheme) and we provide specific functions and behavior for the BIP44 Wallet and the Daedalus Wallet.

note: this will break compilation in the wasm bindings, I am currently working on the update. Users should not see changes in the APIs.


Consume page code should be colored

From Bri - can we add color to the code snippet? Is it possible to hardcode color values since we know exactly what we'll be generating? I think it takes away from the modern design-- there's something just off about it.

We've gotten no additional feedback about this. Closing.


Multiline for ExpensiTextInput

Details

Fixed Issues
Fixes #4625
Tests

QA Steps

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Looks good. One thing I noticed is that the Copy for email Input is wrong. It accepts multiple comma-separated emails or phone but the text says Invite a colleague to your workspace?

I didn't modify anything related email input. This PR's only concern is making new input work with multiline prop.

I didn't modify anything related to email input.

I know. I was just asking maybe a correction can be made, as it's just text. Anyways, it's fine.

@parasharrajat oh, sorry, I misunderstood 😅
I don't mind changing the text as collaborators suggestion

At first glance, it seems like the gap between the textarea label and the value is too large. Here is a regular text input for reference:

And from what I see above:
But maybe that's just my eyes playing tricks on me?
Otherwise can you confirm that the value of the color matches the same text color as text inputs? It appears to be black in the screenshots:

Input color was black, changed to themeColors.text (#0b1b34)
There was a small extra gap between label and input (and I guess it only appears on iOs, maybe because it doesn't support textAlignVertical="top"), so I solved using spacing.pv0.

Also iOs doesn't support numberOfLines prop and on iOs, input height will be as high as its content.
Here is the result

The default height of the textarea feels a bit too tall IMO:

Could we make that shorter?

Sure, I'll update in an hour

@shawnborton - Anything else you'd like to see here?

@AndrewGable code changes in ios folder is not required neither related. I think Pod automatically updated. Do u want me to revert it?

Can you confirm these changes happen on main? If so, yes we can commit them. Otherwise let's not include them in the branch.

@kakajann mind updating your screenshots so I can see if my requested changes were applied? Thanks!

Latest change: 5 lines

Looks good, thanks!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

This has been deployed to production and is now subject to a 7-day regression period.
If no regressions arise, payment will be issued on 2021-09-08.  :confetti_ball:


Remove in-place mutation in DefaultBoxGenerator

This replaces in-place mutation with more backend compiler-friendly one. In-place ops generally cause problems for TVM, so we want an input model to be as pure as possible.
A related issue https://github.com/apache/tvm/issues/10050

@masahi I will merge once the CI passes.


Reactions

Remake "Likes" to "Reactions" in Timeline.
Consider changing default votes to reactions as well.

THis script can be used to display selector - https://codyhouse.co/demo/stretchy-navigation/edit.html

It would be really nice if votes/likes/reactions could be undone and/or changed.


BUG-Table control -- on_add not recognized unless on_delete present

Description
Table created by a table control with on_add, but not on_delete will not have add capabilties
How to reproduce
A code fragment
from taipy import *;
...
md="<|{data}|table|on_add=on_add_fn|>

Or a sequence of events:

Click this button
Set that control to that value
...

Expected behavior
Description of what would be the expected outcome.
Screenshots
When available and relevant, screenshots better help show the problem.
Runtime environment
Please specify relevant indications.

OS: [e.g. Linux, Windows] and version
Browser: [e.g. Chrome, Edge, Safari] and version
and any other relevant information.

DUPLICATE


Adds method to determine section key path for fetched results controller...

..., similar to SQKFetchedTableViewController implementation.

Great stuff, as the example only has one section I forgot about this use case. Ta bud.


Question about add checklist

This responder seems to provide a way for us to add checklists.
i have currently set this up so that there are two commands associated with creating checklists
however neither of these appear to work / appear in pyosbot help commands.
yaml looks like this now:
    add_remove_checklist:
      - editor_response:
          only: editors
          command: editor response
          template_file: editor_response.md
          data_from_issue:
            - reviewers-list
            - author-handle
      - package_accepted:
          only: editors
          command: package accepted
          template_file: package_accepted_template.md
          data_from_issue:
            - package-name

i'm curious what i'm doing wrong with setting these up.
this issue is where i'm testing things

The "add/remove checklist" responder is meant to add a checklist in the body of the issue.
If you just want to create a comment with a checklist that can be done with a regular "basic command" responder where the template is a checklist, this comment will be created by the bot, so only people in the organization will have permission to edit it (check items). So it's ok for editors & EiCs checklists.
There is another responder (reviewer_checklist_comment) that will edit the comment of the user to add a checklist, so the user can update it. It was created to have the reviewers checklist editable by the reviewer so now there's no need to invite them to the joss organization before hand.


Example in API reference is broken

I just followed the example, the only thing I changed was the read_events_blocking to read_events, and now, when executing the program, it throws the following error:
'Error reading events: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }
Even if changing it back to read_events_blocking it still doesn't work, and the error percists.
Code:
async fn inot() {
    if let Some(mut home_dir) = dirs::home_dir() {
        let folder_name = "Google Drive";
        home_dir.push(folder_name);
        let mut inotify = Inotify::init().expect("Error initalizing inotify");

        inotify
            .watches()
            .add(home_dir, WatchMask::MODIFY | WatchMask::DELETE)
            .expect("Failed to watch file");

        let mut buffer = [0; 1024];
        let events = inotify
            .read_events(&mut buffer)
            .expect("Error reading events");

        for event in events {
            println!("{event:?}");
        }
    }
}

Using the example code from the github works perfectly fine. The code from the Docs doesn't, as written down above:
https://docs.rs/inotify/latest/inotify/
use inotify::{
    Inotify,
    WatchMask,
};

let mut inotify = Inotify::init()
    .expect("Error while initializing inotify instance");

// Watch for modify and close events.
inotify
    .watches()
    .add(
        "/tmp/inotify-rs-test-file",
        WatchMask::MODIFY | WatchMask::CLOSE,
    )
    .expect("Failed to add file watch");

// Read events that were added with `Watches::add` above.
let mut buffer = [0; 1024];
let events = inotify.read_events_blocking(&mut buffer)
    .expect("Error while reading events");

for event in events {
    // Handle event
}

Thank you for opening this issue, @Chaqua! I'm trying to understand, if there's a problem that needs to be addressed within this repository.

You said above:

I just followed the example, the only thing I changed was the read_events_blocking to read_events

And then:

The code from the Docs doesn't, as written down above:

It's not clear to me, whether the unchanged example from the documentation ever worked for you. Can you confirm whether this is the case or not?

when executing the program, it throws the following error: 'Error reading events: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }
Even if changing it back to read_events_blocking it still doesn't work, and the error percists.

It's very weird and surprising, that it persists after a restart. Are you sure that you were running the version of the code you expected to run? Can you reproduce this reliably?

Sorry for not expressing it clearly.
What I meant is, that on the Docs.rs webpage (docs), there is the following code:
use inotify::{
    Inotify,
    WatchMask,
};

let mut inotify = Inotify::init()
    .expect("Error while initializing inotify instance");

// Watch for modify and close events.
inotify
    .watches()
    .add(
        "/tmp/inotify-rs-test-file",
        WatchMask::MODIFY | WatchMask::CLOSE,
    )
    .expect("Failed to add file watch");

// Read events that were added with `Watches::add` above.
let mut buffer = [0; 1024];
let events = inotify.read_events_blocking(&mut buffer)
    .expect("Error while reading events");

for event in events {
    // Handle event
}

Which doesn't work for me. Even after rebooting, it doesn't. The code you provide on the github here works perfectly fine tho.
I am running Linux: 6.8.1-arch1-1

Thank you for reporting back. Let's reopen this issue then, to track that the example needs to be fixed or removed.
If somebody wants to look into it, that would be welcome. But I'd also be happy to merge a pull request that just removes it, maybe referencing the example in the repository.

I encountered a similar error when investigating a codebase that uses this library: findex.
It similarly uses a pattern like the one in the documentation, except uses read_events(), the non-blocking function variant.  As it turns out, this does throw an Error: Resource temporarily unavailable with std::io::ErrorKind of WouldBlock.  In that project, it just logs the errors as warnings, but it can get obnoxious when this happens very frequently and fills up log files on disk.
From the Rust docs for std::io::ErrorKind:
/// The operation needs to block to complete, but the blocking operation was
/// requested to not occur.
#[stable(feature = "rust1", since = "1.0.0")]
WouldBlock,

So, when using the read_events() function for non-blocking behavior watching a directory, some operation is being performed that would result in blocking.  So, the error exception is thrown and caught by the match statement in the code calling read_events().
It looks like these errors can be silenced by doing something like in the example in the inotify::Inotify documentation for read_events():
let mut buffer = [0; 1024];
let events = loop {
    match inotify.read_events(&mut buffer) {
        Ok(events) => break events,
        Err(error) if error.kind() == ErrorKind::WouldBlock => continue, // <- Here they are ignored
        _ => panic!("Error while reading events"),
    }
};

Thank you for looking into this, @trinitronx!

Should now be fixed by mdgaziur/findex#52! :tada: :rocket:


Write Assertion.Signature if it exists and SigningCredentials were not used

#1476

Making the Saml2Assertion CanonicalString public is sufficient and more correct.


[OpenAI] Prepare beta.4 release

Made a few NIT changes
Update README, CHANGELOG

API change check
API changes are not detected in this pull request.


Add Support for Preconfigured Helm Repositories via Values File

Description
Currently, the Helm Dashboard UI requires manual input to add Helm chart repositories whenever a new cluster is spun up. This can become repetitive and inefficient for users who manage multiple clusters or frequently create new clusters. It would be beneficial if the repositories could be pre-configured via the values.yaml file during the initial setup, allowing the Helm Dashboard to automatically populate the UI with the predefined repositories. This would save time and reduce manual intervention.
Screenshots

Additional information
Proposed Solution:
Introduce the ability to define Helm repositories in the values.yaml file. These values would then be passed into the deployment as environment variables or mounted as a configuration file.
Application Reads Configuration:
The Helm Dashboard would read the Helm repository configurations either from environment variables or a file at runtime. The configuration could be handled using a ConfigMap in Kubernetes.

repositories:
    - name: "Komodor"
      url: "https://helm-charts.komodor.io"
    - name: "argo"
      url: "https://argoproj.github.io/helm-chart"

probably would need to think about the username and password fields as well.

Very nice suggestion, I like the idea.
Notes for implementation:

the open question is how to pass the list of repos to HD, cli options or env vars are not very suitable, and we don't have any config files
another question is that we internally have app per k8s context, easy to set for in-cluster setup, harder for local multi-cluster. Probably needs to have more complex structure of configuration.
app.Repositories.Add() needs to be called to add the repo, it has all the parameters needed

we can use init containers with http calls to provision repositories?
we can also utilize dynamic reloading feature. see - grafana helm chart provisions dashboards from configmaps.


CSV export to DigitalEksamen

CSV export would be useful in general

Use
remarks export --format "Examnumber;Grade" [filepath]
Assuming these are available properties.

38c24002ad64bc90ce822714732cb7d5662b0100
0027dc9505bb1c62cc97217df7a2acb54550e61d


issue with a accordion component

i am using framework7 last version , and my app hierarchy is like that :

vue router-view
vue children are loaded within router-view
one of those children is the root of framework7 app
when i navigate between "the root of framework7 which is a component" and any other component , the accordion animation start to stuck and act unexpectedly but it work good before navigation done .

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Cells do not merge in Markdown DITA or MDITA

Expected Behavior
I was trying to merge cells horizontally across columns in a table in Markdown DITA or MDITA.
Actual Behavior
I tried using both the sample Markdown DITA table from https://www.dita-ot.org/3.1/topics/markdown-dita-syntax-reference.html and an HTML table with colspan=2.
In both cases, the cell that is supposed to be merged to the right is rendered as a normal cell, and the cell to the right (that's supposed to be merged to the left) looks to be rendered as a normal cell or skipped.
Output:
Custom PDF transform (Transform sets top, bottom, left, and right borders for all table cells.):

Standard pdf2 transform:

Steps to Reproduce
Excerpt from topic.md:

Table title (HTML table with merged cells)

            First Header
            Second Header
            Third Header

            Table cell
            Merged cell

            Table cell
            Table cell
            Table cell

| First Header | Second Header | Third Header |
| ------------ | :-----------: | -----------: |
| Content      | *Long Cell*                 ||
| Content      | **Cell**      | Cell         |
[Table title (Simple Markdown table)]

Excerpt from mapgen_test-map1.ditamap:
<map id="mapgen_test-map">
    <title>Test of Markdown</title>
    <topicref href="test-md.md" format="md"/>
</map>

Excerpt from mapgen_test-map2.ditamap:
<map id="mapgen_test-map">
    <title>Test of Markdown</title>
    <topicref href="test-md.md" format="mdita"/>
</map>

Environment

DITA-OT version: 3.1.3 (including standard org.lwdita -- does not include com.elovirta.dita.markdown)
Operating system and version: Windows 7
How did you run DITA-OT? dita command
Transformation type: custom PDF transform and pdf2

Spanning is a MultiMarkdown feature, and that's what the documentation says it supports. This is critical for us at Nokia as well with co-authoring between DITA and Markdown.
Is there an extension point mechanism that we could do to patch our own fixes, or would we need to fork the lwdita repo and write our own hooks into the flexmark Java API?

Investigating a bit just for the format="markdown" and format="md" cases as mdita only supports simple tables:
For the first instance of the table present in HTML form in the Markdown file, this XSLT stylesheet "lwdita.jar/hdita2dita-common.xsl" needs to take column spans into account when matching th and td elements.
For the second instance of the table present in ASCII graphics layout, colspans are turned off by default in the "com.elovirta.dita.markdown.MarkdownReader" constructor. If you turn them on and disable append missing columns:
.set(TablesExtension.COLUMN_SPANS, true)
.set(TablesExtension.APPEND_MISSING_COLUMNS, false)
it works for the example on this issue.

This issue should be moved to this project: https://github.com/jelovirt/org.lwdita/issues
@jelovirt do you have the ability to transfer it there?

I added an issue there with just a reference to this one for now so it didn't get lost.

I'm getting a clearer albeit confusing picture now. There's a standard "mdita" format from the OASIS lwdita committee, which supports simpletable only, and there two others "markdown" and "md" which do support colspans with the modifications above. What's the difference between "markdown" and "md" formats? We've got writers and developers using both without us understanding the differences.

Adding reference to issue added by @kirkilj on the proper project: https://github.com/jelovirt/org.lwdita/issues/84
@kirkilj "markdown" and "md" are aliases for the same markdown to DITA parser so they are interchangeable.


Use new Context API in React 16.3

Update!
OK, a test release is on npm under the next tag.
npm install react-router@next react-router-dom@next

It's just those two packages for now, but please give them a try. Report any problems in this PR.
Continued...
Closes #5901.
~This will obviously not work on Travis until 16.3.0 is out.~ But I can confirm it works locally.
To play along at home, simply clone react in a parallel folder, yarn && yarn run build, and then copy over the files by hand back to this repo:
cp -a ../react/build/node_modules/react/* node_modules/react/
cp -a ../react/build/node_modules/react-dom/* node_modules/react-dom/

This is mostly a brute force approach. All the tests pass, but I'm doing whatever is necessary to get it to work. There may be some more radical refactors warranted with the new API. The new bitmask stuff is neato.
While not BC yet, I'm least keeping available the old context API hooks. I need to feature sniff unstable_createContext.
Outstanding stuff:

[x] ~Wait for a React release (duh)~
[x] ~<Redirect>, <Prompt>~
[x] ~Router#getChildContext references this.context.router~
[x] ~<Link>~
[x] ~React Router Native stuff~
[x] ~<= 16.2 compatibility~

16.3.0-alpha.0 was released with Context.provide/Context.consume replaced by <Context.Provider> and <Context.Consumer>.

Welp, that's a little bit of work to implement. But now I can get Travis to pass 👍

Yeah, the lack of an href-like attribute on React Native links makes testing where they will navigate to a bit convoluted. The above example could probably be a bit shorter because the history instance only really needs to be mocked if you're verifying the navigation happens.
I'm excited for 16.3. They also dropped by unstable_ prefix on createContext, so hopefully that is a sign of confidence.

OK, I added in create-react-context to polyfill for React <= 16.2. I used that to downgrade back to the current stable release, which ensures RRN is in sync.
Lerna's hoisting, combined with the symlinking between packages, was causing two versions of React to sneak into the tests. I'm not sure how best to fix that, but the easiest thing is to run against the stable version. It ensures we're backwards compatible as well.
I think we're good to go now. Just need a review and some feedback on how this turned out.

Just so others are aware of the plan/goal here: I'm holding off on merging this into master until we get our next release out. There are a lot of useful things queued up and this change is large enough that I don't want to poison the well on what should be a high quality release.
Afterwards, I'll look to getting this merged and released as a prerelease to allow for everyone to test it and give feedback. I'm most nervous about the component tree changes (a bunch more of stuff will show up with this in place!) and unintended consequences too.

@timdorr can we try it? Is there any prerelease?

You can check out this PR and build it locally.

@timdorr any outstanding issues left for this PR?

OK, got this all updated. It can go into master now that 4.3.0 is out, though I'd like to get some sort of approval from others first. I am thinking of doing a 4.4.0-alpha.0 release directly from this branch to make it easy for others to try out.

OK, these are pushed on the next tag. So:
npm install react-router@next react-router-dom@next

It's just those two packages, but give them a whirl and let me know what you think or any issues you run into.

I can confirm that upgrading to 4.4.0-alpha.1 fixed my application's issues with routing not properly working when using the new context API in my code.
My app was organized something like this:
<HashRouter>
  <AppThatUsesNewContextProviderAPI>
    <Route path='/' exact component={ HomePageThatConsumesNewContext } />
    ...
  </AppThatUsesNewContextProviderAPI>
</HashRouter>

When using<EMAIL_ADDRESS>navigation actions would properly trigger the URL hash to update, but the component rendered would not change. After upgrading to 4.4.0-alpha.1, the issue has gone away and my app works again. Thanks folks!
+1 to get this into mainline :)

This PR doesn't specifically fix that. Make sure you're using React 16.4 if you're using the new context API with the release version of this library.

@timdorr I'm trying to test this with no luck, the API changes in some way? There is some docs on the needed changes? withRouter still works? RouterContext/Provider should i put somwhere? Thanks!

No API changes needed. The only thing is a new RouterContext export, but it should be fully BC, even with legacy Context.

@timdorr do you have any info on how long you want to keep this in alpha before getting ready to release it?

Hey @timdorr, is there any way you can push an update for an alpha branch of the react-router-config to include the alpha branch of react-router? I was trying to test these changes, but unfortunately we use react-router-config and I believe it's using the non alpha version of react-router.


Reinstalled VsCode because files would not save unless closing file

Version 1.19.3
Commit 7c4205b5c6e52a53b81c69d2b2dc8a627abaa0ba
Date 2018-01-25T10:36:34.867Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
After updating to latest version the issue started arising. The files only save after closing file and prompt to confirm whether to save or not pops up

@bpasero I have solved the issue. An extension named Blank Line at the End of File which has to do with saving a file and adding a blank line was the cause of the error so I uninstalled it and the editor is working fine again


add att.txt

Topic: att
Relative: supPerson

Reviews in this chain:
└https://github.com/dukeofcool199/revup/pull/38 added sup.txt
　└https://github.com/dukeofcool199/revup/pull/39 add att.txt

#
head
base
diff
date
summary

0
872f99e0
75cd0c39
diff
Jan 3 13:27 PM
1 file changed, 1 insertion(+)


Support bit-string in PostgreSQL

Provide parsers, serializers, tests and docs for the for https://www.postgresql.org/docs/current/datatype-bit.html
As an example, see the string types support in PostgreSQL https://github.com/userver-framework/userver/blob/develop/postgresql/include/userver/storages/postgres/io/string_types.hpp

Added in 65a44366d0792cf6f965c34df3afa3c8430b96b8


Make it possible to manually sort skills?

This would require a restructure from the ground up.

No. I don't care.


tslib discussion

Per @StrahilKazlachev request:
We need to settle how we want to handle TS helpers in codegen.
When compiling to ES5 -- or even ES6 (e.g. decorators) -- TS makes use of a few helper functions, for example __extends when using class inheritance in ES5, __rest when using rest properties, __decorate when using decorators.
By default, used helpers are emitted at the top of each output file (only helpers used in that file, of course).
Aurelia is made of many files and it really adds up to a lot of redundant code. Even more so if we use __awaiter or __generator, which are large.
Fortunately, Typescript has two options to address this problem:
--noEmitHelpers does what it says. The generated code won't run unless your provide helpers in some way (likely a set of global variables).
--importHelpers imports the required helpers from tslib at the top of generated file. Module tslib is distributed and maintained by MS.
I think the importHelpers solution is the simplest, is maintained by MS (when there's a new helper or one needs changing), optimizes with bundlers like Webpack or Rollup and works along other TS code compiled with importHelpers (e.g. app code or other libs).
The main drawback that @EisenbergEffect doesn't like is that this means Aurelia would have an external dependency on tslib, whereas today it has none.
I would point out that all serious projects today use a bundler and that if someone doesn't want to use tslib, it's easy to map the name to another arbitrary module, even one distributed with Aurelia if we really want to go this route.

I think I'm ok with the dependency on tslib. How large is it?

@EisenbergEffect The whole thing is 200 lines, 10K, before minification and gzip. Quite small:
https://github.com/Microsoft/tslib/blob/master/tslib.js
There's even a smaller one when targetting es6.

I use tslib in my aurelia projects, it really cuts down on code size and makes the transpiled code much more readable since you don't have to scroll through 50 lines of helpers otherwise emitted for say an async *.
It now works out of the box with both the 0.19.x and 0.20.x forks of SystemJS.


Admin Panel ?

does the staff have the ability to delete reservations if necessary also why is there not an admin panel?

https://github.com/BryanTheLai/RestaurantProject/commit/86c059ea9a1ccaf693ae710a38a5c1f87a50be1f
Just uncomment that part, most of the main panels has the delete function commented.


Add pyside2-uic (executable) and pyside2uic (module)

Fix https://github.com/mottosso/Qt.py/issues/141

I realize I need to add a test to this. Will try to do that later this evening.

I added a test which compiles an the already existing ui in tests.py (qwidget.ui) into a .py file (output.py):
# -*- coding: utf-8 -*-

# Form implementation generated from reading ui file 'qwidget.ui'
#
# Created: Sun Sep 18 13:22:20 2016
#      by: pyside2-uic  running on PySide2 2.0.0~alpha0
#
# WARNING! All changes made in this file will be lost!

from PySide2 import QtCore, QtGui, QtWidgets

class Ui_Form(object):
	def setupUi(self, Form):
		Form.setObjectName("Form")
		Form.resize(235, 149)
		self.gridLayout = QtWidgets.QGridLayout(Form)
		self.gridLayout.setObjectName("gridLayout")
		self.lineEdit = QtWidgets.QLineEdit(Form)
		self.lineEdit.setObjectName("lineEdit")
		self.gridLayout.addWidget(self.lineEdit, 0, 0, 1, 1)

		self.retranslateUi(Form)
		QtCore.QMetaObject.connectSlotsByName(Form)

	def retranslateUi(self, Form):
		Form.setWindowTitle(QtWidgets.QApplication.translate("Form", "Form", None, -1))

I'm both importing this and I'm creating the Ui_Form class. But I'm not sure on how I should run this... and assert its functionality. Any suggestions?

I'm not sure on how to assert this functionality. Any suggestions?

I'm not sure on how to assert this functionality. Any suggestions?

Compile something you are familiar with and know the outcome of. Then just == them.
Have a look at this for example.

Jotting down this here since I can't find anything on the pyside2uic.compileUi class anywhere online:
def compileUi(uifile, pyfile, execute=False, indent=4, from_imports=False):
    """compileUi(uifile, pyfile, execute=False, indent=4, from_imports=False)

    Creates a Python module from a Qt Designer .ui file.

    uifile is a file name or file-like object containing the .ui file.
    pyfile is the file-like object to which the Python code will be written to.
    execute is optionally set to generate extra Python code that allows the
    code to be run as a standalone application.  The default is False.
    indent is the optional indentation width using spaces.  If it is 0 then a
    tab is used.  The default is 4.
    from_imports is optionally set to generate import statements that are
    relative to '.'.
    """

Compile something you are familiar with and know the outcome of.

The problem is I've never compiled anything before so I'm not familiar with what the output should be like.
In this case, I think we should be able to assume the output is proper and that it all works. But I'd like someone to confirm that.

I could do a hard reset to my first commit: https://github.com/mottosso/Qt.py/pull/142/commits/410d1f8966a2c30a1de314dfedf6b50a9e3212dd
or we could just merge this as-is.

I could do a hard reset to my first commit: 410d1f8

It's an option, but we would lose out on the conversation. No harm one way or the other, I'll leave it up to you.

I'll just merge this :)


ARROW-13686: [Python] Update deprecated pytest yield_fixture functions

Replace 'pytest.yield_fixture' with 'pytest.fixture' as the former is marked as deprecated by pytest.

Thanks @edponce !


test(rust): fix flaky tests from ockam_api::auth

Related to https://github.com/build-trust/ockam/issues/4046
ockam_api::auth tests that were stopping and starting a worker with the same name were failing on CI. I couldn't reproduce this in my local env. To fix this, I've refactored the tests so the recreated worker has a different name from the stopped worker.

@mergifyio rebase


How to use with serialport?

how to use with serialport? it need  node env. I want the electron-builder don't resolve serialport such as webpack externals

here is the demo that I use serialport with vue-cli:
https://github.com/Minori-ty/vue-cli-vue3-electron-serialport.git
you can see the config in the vue.config.js

Duplicate https://github.com/cawa-93/vite-electron-builder/discussions/657


apple_sdk_11_0.stdenv: replace extraBuildInputs with CF from 11.0 SDK

Description of changes
This can result in swift-corefoundation being included even when a derivation uses apple_sdk_11_0.stdenv directly, which may result in hard to debug compiler errors (unless you just happen to know cryptic compiler errors means the 10.12 and 11.0 SDKs have been mixed).
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

This one uses the current stable branch, which should be the same as master (and have most paths cached, so the build is quick). It should show that NIX_CORRFOUNDATION_RPATH is being set in the cross build.
$ MY_NIXPKGS_DIR=github:NixOS/nixpkgs/nixos-23.05 nix build  --override-input nixpkgs "$MY_NIXPKGS_DIR" -L github:eliasnaur/nix-lib64-rpath --system x86_64-darwin # or --system aarch64-darwin

This is the output I get.
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/402cc3633cc60dfc50378197305c984518b30773' (2023-03-28)
  → 'github:NixOS/nixpkgs/81ed90058a851eb73be835c770e062c6938c8a9e' (2023-06-08)
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> unpacking sources
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> unpacking source archive /nix/store/r6z6rf7bw82ks7d1p3rn9y5k9mcvhfjs-1q78588ywpkj2x4qrh27lcp4wn37yppb-source
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> source root is 1q78588ywpkj2x4qrh27lcp4wn37yppb-source
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> patching sources
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> updateAutotoolsGnuConfigScriptsPhase
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> configuring
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> no configure script, doing nothing
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> building
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> CC armv6l-unknown-linux-musleabihf-gcc
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> NIX_COREFOUNDATION_RPATH: /nix/store/1ds96f193bdf7f3kz295rwf66q90vi71-swift-corefoundation-unstable-2018-09-14/Library/Frameworks
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> NIX_LDFLAGS: -rpath /nix/store/ykm0y2f4h2h280v0b0cl4b806d2l137s-demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf/lib
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> installing
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> post-installation fixup
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> shrinking RPATHs of ELF executables and libraries in /nix/store/ykm0y2f4h2h280v0b0cl4b806d2l137s-demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> checking for references to /private/tmp/nix-build-demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf.drv-0/ in /nix/store/ykm0y2f4h2h280v0b0cl4b806d2l137s-demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf...
demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf> patching script interpreter paths in /nix/store/ykm0y2f4h2h280v0b0cl4b806d2l137s-demonstrate-lib64-rpath-armv6l-unknown-linux-musleabihf (edited)

This test case demonstrates the issue. It’s mostly theoretical, but the idea is to avoid mixing SDKs at all to save having to troubleshoot cryptic build failures in the future.
Given test.nix
{ flake ? "github:NixOS/nixpkgs/nixos-23.05", pkgs ? (builtins.getFlake flake).legacyPackages.x86_64-darwin, ... }:

pkgs.darwin.apple_sdk_11_0.stdenv.mkDerivation {
  pname = "test";
  version = "test";
  buildInputs = [ pkgs.darwin.apple_sdk_11_0.frameworks.IOKit ];
  dontUnpack = true;
  dontBuild = true;
  installPhase = ''
    mkdir -p $out/bin
    cat <<-PROGN > $out/bin/vars
    #!/bin/bash
    echo NIX_CFLAGS_COMPILE: $NIX_CFLAGS_COMPILE
    PROGN
    chmod a+x $out/bin/vars
  '';
}

$ nix build --impure --expr 'import ./test.nix { }' && ./result/bin/vars | grep "swift-corefoundation-unstable-2018-09-14"
# Should yield something like:
NIX_CFLAGS_COMPILE: -F/nix/store/9dw29sl9gsl8090cf6qkmhj2pprl3z5z-apple-framework-CoreFoundation-11.0.0/Library/Frameworks -frandom-seed=8jlsd4n2sw -isystem /nix/store/skgy80h81jcd1cq53zpy5b8fcx8mlfxd-libcxx-11.1.0-dev/include -isystem /nix/store/m8q0nis3rksxgdz0887ih8vyfsa0n1y5-libcxxabi-11.1.0-dev/include -isystem /nix/store/ar6k6z685qzcvw4kxf6zyv7alx468paj-compiler-rt-libc-11.1.0-dev/include -iframework /nix/store/24szwa3c5sxbvxd999xg7b53cnn37zm0-apple-framework-IOKit-11.0.0/Library/Frameworks -iframework /nix/store/9dw29sl9gsl8090cf6qkmhj2pprl3z5z-apple-framework-CoreFoundation-11.0.0/Library/Frameworks -isystem /nix/store/8vsm3nrvvwm65gkvhv14wccfqhy1q7aj-libobjc-11.0.0/include -iframework /nix/store/1ds96f193bdf7f3kz295rwf66q90vi71-swift-corefoundation-unstable-2018-09-14/Library/Frameworks -isystem /nix/store/skgy80h81jcd1cq53zpy5b8fcx8mlfxd-libcxx-11.1.0-dev/include -isystem /nix/store/m8q0nis3rksxgdz0887ih8vyfsa0n1y5-libcxxabi-11.1.0-dev/include -isystem /nix/store/ar6k6z685qzcvw4kxf6zyv7alx468paj-compiler-rt-libc-11.1.0-dev/include -iframework /nix/store/24szwa3c5sxbvxd999xg7b53cnn37zm0-apple-framework-IOKit-11.0.0/Library/Frameworks -iframework /nix/store/9dw29sl9gsl8090cf6qkmhj2pprl3z5z-apple-framework-CoreFoundation-11.0.0/Library/Frameworks -isystem /nix/store/8vsm3nrvvwm65gkvhv14wccfqhy1q7aj-libobjc-11.0.0/include -iframework /nix/store/1ds96f193bdf7f3kz295rwf66q90vi71-swift-corefoundation-unstable-2018-09-14/Library/Frameworks

$ nix build --impure --expr 'import ./test.nix { flake = "github:NixOS/nixpkgs/pull/234863/head"; }' && ./result/bin/vars | grep "swift-corefoundation-unstable-2018-09-14"
# Should return nothing


ImprovementReturn meaningful error message when show column stats column name doesn't exist.

The error message was not good for not exist column while show column stats:
MySQL [hive.tpch100]> show column stats `lineitem` (l_extendedpric);
ERROR 1105 (HY000): errCode = 2, detailMessage = Unexpected exception: null

This pr show a meaningful message:
mysql> show column stats `lineitem` (l_extendedpric);
ERROR 1105 (HY000): errCode = 2, detailMessage = Column: l_extendedpric not exists

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.65 seconds
stream load tsv:          534 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.1 seconds inserted 10000000 Rows, about 343K ops/s
storage size:<PHONE_NUMBER>0 Bytes


Add isLocale() method

I find myself doing if('en' === app()->getLocale()){} a lot and therefore I've written a helper myself.
/**
 * @return bool
 */
function is_locale($locale)
{
    return app()->getLocale() === $locale;
}

Why still send a PR?

There are similar checks for the environment (app()->environment('staging') and app()->isLocal())
I think more users would like this helper
app()->isLocale('en') looks cleaner and is more Laravelish

Please only modify one place, not every line in the file.


Could not obfuscate Use different salt

when trying to obfuscate a web address with a hyphen in it, it returns
2016-06-15 13:27:36.955 Impl.[47263:1595477] Could not obfuscate: http://xxx-xx.xxxxxxxx.xxx/ - Use different salt
any ideas how i can get around this ?
works fine with all my other variables which dont have special characters.

Add as many classes as you want and for each class added, you increase the chance of obfuscating significantly.

yep that did the trick, i miss read the documentation.


Working fix for #108

Currently console only reads input from stdin. However a ReadWritePair option has already been added. Unfortunately only writing works for ReadWritePair. This PR adds functionality for a custom input source.
See issue #108
See other (I think incomplete) pr addressing this issue: #123
This would complete the work of #93
Therefore the following lines have been changed:

https://github.com/console-rs/console/blob/51425fca70702b74ea64b29984da103a5bcbc7bc/src/term.rs#L291
https://github.com/console-rs/console/blob/51425fca70702b74ea64b29984da103a5bcbc7bc/src/term.rs#L617
https://github.com/console-rs/console/blob/51425fca70702b74ea64b29984da103a5bcbc7bc/src/term.rs#L623
https://github.com/console-rs/console/blob/51425fca70702b74ea64b29984da103a5bcbc7bc/src/term.rs#L343
https://github.com/console-rs/console/blob/51425fca70702b74ea64b29984da103a5bcbc7bc/src/term.rs#L278

ReadWritePair was also modified. Previously it required an input source of type Read (enables reading of bytes)
This has been changed to an iterator over Keys because Keys are a cross platform solution. Else we would need to parse the input differently depending on the os of the user. Now the user has a nice interface for defining his own input source.
Functionality may be expanded in the future to support more keys, or to automatically convert something like Key::Char('\n') to Key::Enter or at least warn the user.
This pr should be a good start adding an essential feature.
Please take a look at the commits from last to newest. They contain a description of what has been changed.

This PR looks generally promising but has significant conflicts against master.


huge PR from the MITRE submission

@kwalcock -- this is so overdue I am not planning on splitting it (BUT I can if you tell me you want me to!!)
@kwalcock there are currently 2 failing tests -- both in the TestUnicode and I don't remember any more how that was supposed to be fixed.  I dug into it a bit and indeed we're just slurping up the unicode.... if you remind me what actually worked before (I think my approach didn't, right?) I can work on it or you can if you want (that would be great!)

FWIW I'm looking at this now.

It's definitely failing on Travis, but it says it passes on my computer.  However, if I run it in the debugger, it seems to end the test early.  Something strange is going on.

The test sentence in that file was no longer producing the events that were being tested or any at all for that matter.  That might not be a good thing itself.  I made up a different sentence, but the unicode characters are being incorporated into the entities that are found.  That's what we're trying to avoid.  The    "unicode-icons" rule is still there, but it doesn't seem to be working.

Do you expect us to review all this? :)
Did you regenerate the iteration 2 results? Did they look the same? If so, I propose to merge.

Yep, about the same! Woohoo!
And yes, please review all 51 files, line by line is preferable
On Mon, Jun 11, 2018 at 6:17 PM Mihai Surdeanu<EMAIL_ADDRESS>wrote:

Do you expect us to review all this? :)
Did you regenerate the iteration 2 results? Did they look the same? If so,
I propose to merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/329#issuecomment-396434892, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFIniTn5CEZL8VVoawi1HeUu6t25dPc8ks5t7xacgaJpZM4UhlT5
.

I'm crossing my fingers and will endeavor to check out the details a little at a time.

P.S.  I'll work on that unicode issue, of course.  I agree that rules are not the best place for it to happen.


Reducing log noise of Validar

Could this log message be reduced to debug, or removed altogether?
https://github.com/Fody/Validar/blob/master/Fody/ModuleWeaver.cs#L69

will remove and push

pushed


GH-1591: Apply BackOff in DARP with Batch Listener

Resolves https://github.com/spring-projects/spring-kafka/issues/1591
BackOff was ignored for batch listeners (not recoverable).

move code from SeekToCurrentBatchErrorHandler to ListenerUtils
call from both STCEH and DARP
also clear the thread state (in both) if a batch fails and subsequently succeeds

I will do the backports - conflicts are expected

Back-ported to 2.5.x, 2.4.x, 2.3.x.


Different optional for Ident in class property when has private name

Describe the bug
There is a different behaviour for Ident when it's a private class property vs a regular class property. I think maybe optional can be removed on Ident? Shouldn't that be a higher level concept (ex. part of the parameter or class property and not the ident like how TypeScript represents its AST... I feel like the same should be done for type_ann too)?
Input code
export class Response {
  #a?;
  b?;
}

Config
No response
Playground link
https://play.swc.rs/?version=1.3.50&code=H4sIAAAAAAAAA0utKMgvKlFIzkksLlYISi0uyM8rTlWo5uVSUFBOtLcG0UkgqhYAQ0CvSikAAAA%3D&config=H4sIAAAAAAAAA1WQvW7DMAyE9z6FoTmoCw8ZsrbIlilPQCh0w0J%2FICkgRuB3jyTHcbqJ3%2FF04N0%2Fus78iTWH7l6eZUjAgvyaC5EpKNwKMTolFMuU1OxWVaVKyhkbmRfBKPAvajWhDF%2FDYFbOEGSM7N8TsuAPjhTwGPnbgciR0F3k%2Be8rihGsvvkKIp8i6zlmtljDrqpJDn2P4j%2Fl2qfFstsMnIOSb7uQNXpQsuYpz%2F8ucDFK3RvBSb2tcePjJTvc6qqVLFfuzbZEgcZp9TZEclqdrav5AeQIxLB6AQAA
Expected behavior
Probably just remove optional from ident or both should be true.
Actual behavior
{
  "type": "Module",
  "span": {
    "start": 0,
    "end": 41,
    "ctxt": 0
  },
  "body": [
    {
      "type": "ExportDeclaration",
      "span": {
        "start": 0,
        "end": 41,
        "ctxt": 0
      },
      "declaration": {
        "type": "ClassDeclaration",
        "identifier": {
          "type": "Identifier",
          "span": {
            "start": 13,
            "end": 21,
            "ctxt": 2
          },
          "value": "Response",
          "optional": false
        },
        "declare": false,
        "span": {
          "start": 7,
          "end": 41,
          "ctxt": 0
        },
        "decorators": [],
        "body": [
          {
            "type": "PrivateProperty",
            "span": {
              "start": 27,
              "end": 31,
              "ctxt": 0
            },
            "key": {
              "type": "PrivateName",
              "span": {
                "start": 27,
                "end": 29,
                "ctxt": 0
              },
              "id": {
                "type": "Identifier",
                "span": {
                  "start": 28,
                  "end": 29,
                  "ctxt": 0
                },
                "value": "a",
                "optional": false
              }
            },
            "value": null,
            "typeAnnotation": null,
            "isStatic": false,
            "decorators": [],
            "accessibility": null,
            "isOptional": true,
            "isOverride": false,
            "readonly": false,
            "definite": false
          },
          {
            "type": "ClassProperty",
            "span": {
              "start": 35,
              "end": 38,
              "ctxt": 0
            },
            "key": {
              "type": "Identifier",
              "span": {
                "start": 35,
                "end": 36,
                "ctxt": 0
              },
              "value": "b",
              "optional": true
            },
            "value": null,
            "typeAnnotation": null,
            "isStatic": false,
            "decorators": [],
            "accessibility": null,
            "isAbstract": false,
            "isOptional": true,
            "isOverride": false,
            "readonly": false,
            "declare": false,
            "definite": false
          }
        ],
        "superClass": null,
        "isAbstract": false,
        "typeParams": null,
        "superTypeParams": null,
        "implements": []
      }
    }
  ],
  "interpreter": null
}

Version
1.3.50
Additional context
No response

I don't remember the correct reason, but removing Ident.optional is a very complex task.
Actually, there was no concept like BindingIdent, but I introduced it to reduce size of Ident.
While introducing it, I tried removing Ident.optional

This has been resolved.


Australia Bank Account Number Type incomplete

It seems that the "Australia Bank Account Number" type hasn't been fully setup with its keywords.
It might have been copied from other countries such as the US details (usa account) which is not relevant.
It would be great to have the Australian keywords such as Bank Account Number, Bank Account, Account Number, Savings Account, BSB, and so on.

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

ID: 0c16b548-1fc9-2765-3e8a-7559be41fd9d
Version Independent ID: 7fe5f4ba-e53d-d86d-4ab9-64e872e33069
Content: What the sensitive information types look for - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/what-the-sensitive-information-types-look-for.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

Hi @caiodaruizcorrea-avanade
Thank you for engaging with the community here for the docs.
I know the product teams are always looking for user feedback and feature requests on how to make Office 365/Microsoft 365 better. They keep a close tab on user feedback and it would be awesome if you could add your voice in UserVoice.
You might find others have made a similar request that you can add to, or you can open a new one. Let us know here if you do so we can up-vote your request.
Thank you for your contribution to make the docs better! Much appreciated!


Will these labs be updated for the new version of the course and as there is no longer an azure pass for this, will any lab requiring azure be removed?

Module: 00
Lab/Demo: 00
Task: 00
Step: 00
Description of issue
Repro steps:

All labs were updated and released over the last month.  We are ironing out a few bugs still; but overall the labs are revamped for the updated version of the course and OD.


feat: add disablePinchToZoom prop

Hi!!, thanks for creating this amazing library. I needed a prop to dynamically disable the pinch to zoom feature, so I made it,
I Had I problem running "yarn" because of the bootstrap script, I don't know exactly why. I think it may be because I'm on windows and because of that I could not test it on the example project (I tested it on my personal project where I use this library). also because I'm on windows I cannot test it for iOS the feat is super simple so it should not be a problem but yea.....

okay this is embarrassing I found a strange bug which allowed you to pinch to zoom even with the PinchGestureHandlerwith the enabled prop set to false, so I implemented it in another way (similar to how the disableVerticalSwipe prop was implemented) I
pushed a commit with the fix everything should work perfect now, sorry.

Thank you for this wonderful PR, I was exactly in need of it, I was getting ready to develop it.
The only thing I want to point out is that the disablePinchToZoom declaration in the index.d.ts file was missing.

@pavelbabenko @vonovak @kanzitelli @troZee can you accept this PR?

I think this file is auto generator at the time of "compiling" the library.

Added pinchEnabled prop in v0.2.4