Why a real-valued scalar multiply a Hermitian matrix isn't be a Hermitian matrix?

Hello，I‘m new in cvxpy and I found a question when I coded.
Why a real-valued scalar multiply a Hermitian matrix isn't be a Hermitian matrix?
Like Y=1*X, while X = cp.Variable((3,3), hermitian=True).
Then, Y.is_hermitian() outputs False.
Could you help me?
Thanks a lot.

This is a great question. The answer is that symbolic properties like
is_hermitian aren’t as reliably inferred as properties like is_dcp. We can
easily update the code so that we check for real scalar multiplication
though. Thanks for catching this!
On Sun, Mar 3, 2024 at 10:47 PM Alfredo Amdahl @.***>
wrote:

Hello，I‘m new in cvxpy and I found a question when I coded.
Why a real-valued scalar multiply a Hermitian matrix isn't be a Hermitian
matrix?
Like Y=1*X, while X = cp.Variable((3,3), hermitian=True).
Then, Y.is_hermitian() outputs False.
Could you help me?
Thanks a lot.
—
Reply to this email directly, view it on GitHub
https://github.com/cvxpy/cvxpy/issues/2368, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRLIFCT4SS2A3HQSUZGQ53YWPVGHAVCNFSM6AAAAABEERB2WGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DKOBWGA4TOOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for your reply! I have already fixed my problem with adding other cvx functions. Hope your package become better!

@rileyjmurray would resolving this issue involve updating the logic here?
I ask because I am interested in fixing this issue


Commenting JSX makes line JavaScript instead of JSX breaking context aware commenting

In the following code:
const React = require("react");

export default () => (

    {/*
Hello World!
 */}

);

When testing with mxw/vim-jsx and pangloss/vim-javascript the line with the jsx comment is labelled a jsxChild. Combined with othree/yajs.vim (which has way nicer highlighting 👏 ) the line becomes javaScriptBraces. This means my context aware commenting plugin adds {/* */}, but upon requesting to uncomment does nothing, or worse, when requesting to toggle the comment, comments again, making it // {/* */} as it 'correctly' recognized the JavaScript syntax was not yet commented as {/* */} is only a comment in JSX.
Related issue tomtom/tcomment_vim#248 in tcomment that has some screenshots.
I know parsing JSX is a pain in the butt, let me know if there's anything else I can do to help. Commenting I'm noticing is quite frequently used in UI work.
Thanks for an awesome plugin 🙏 .

Hi @alextes, try to replace mxw/jsx with vim-jsx-pretty. It works well with the test case you provided.


[Chess.js] Implement rifle chess

Right-clicking allows the user to execute a valid capture without moving the capturing piece.
Capturing is obligatory: if you can make any capture, you must make one (just as in antichess).
One idea is to somehow separate out the mandatory capture rule so that one function can be used for antichess, rifle chess and any other variant with a mandatory capture rule.
Another idea is to allow the user to enable/disable the mandatory capture rule, so that there are two forms of rifle chess.

we are no longer implementing rifle chess


AWS: Use the SSH key fingerprint, not the AWS fingerprint

This is unfortunate, because it means we have two fingerprints,
although arguably the OpenSSH key fingerprint is much more common.
However, the OSX Mavericks version of ssh-keygen can't compute
the AWS fingerprint correctly (e.g. https://www.netmeister.org/blog/ssh2pkcs8.html)
So we can work on OSX Mavericks, we use the more common OpenSSH fingerprint.
Consequences of this:

we will re-upload every SSH key (no real problem there).
the same key will now have two different names for people that ran older k8s versions (confusing, but no real problem)
the fingerprint AWS displays will be different from the (SSH) fingerprint embedded in the name (confusing, but the AWS fingerprint is arguably the cause of the confusion)

Upsides: we should work on OSX Mavericks and generally much more robust.
If we moved these scripts e.g. to Go, we could compute the AWS key ourselves.  But I think for now it is more important to run on Mavericks than to compute the same fingerprints.
@iterion PTAL

LGTM, this change also works on El Capitan with the same caveats as above.
The two different fingerprints might be confusing, but I'm not sure people will really care or notice.

Blech. But LGTM.

Over to @quinton-hoole to finish.

LGTM, ok-to-merge.  Thanks Justin!


Not very elegant, but at least we avoid an ugly error box that has ap…

…parently no reason and no impact. @Luthaf  you'll love it ^_^

This works for me =) @rosecers, you had another error message for this, right?

@rosecers if you have a different error why don't you add it in this same PR? Or perhaps we could have a list of ignored errors from JSMol?

@rosecers if you have a different error why don't you add it in this same PR? Or perhaps we could have a list of ignored errors from JSMol?

This is the primary error that I get. I get another, very similar one, but coincidentally cannot recreate it. I'll make an issue next time I come across it.

Let's update the condition next time we find one of these errors


Azure resource group creation through ARM template fails

I have a template json file that has the following to create a resource group.
Basically I'd like to create the resource group from my build pipeline if it is not present. If it is present the step should do nothing.

{
"$schema": "https://schema.management.azure.com/schemas/2018-05-01/subscriptionDeploymentTemplate.json#",
"contentVersion": "<IP_ADDRESS>",
"parameters": {
"rgName": {
"type": "string"
},
"rgLocation": {
"type": "string"
}
},
"variables": {},
"resources": [
{
"type": "Microsoft.Resources/resourceGroups",
"apiVersion": "2018-05-01",
"name": "[parameters('rgName')]",
"location": "[parameters('rgLocation')]",
"properties": {}
}
],
"outputs": {}
}

And in my azure pipeline I have the following as a task

  - task: AzureResourceGroupDeployment@2
        displayName: 'Azure Deployment:Create Resource Group'
        inputs:
          azureSubscription: $(azureSubscription)
          resourceGroupName: $(resourceGroupName)
          location: $(location)
          csmFile: '$(System.DefaultWorkingDirectory)/**/container-resourceGroup-template.json'
          overrideParameters: '-rgName "$(resourceGroupName)" -rgLocation "$(location)"'

And I get this error

Checking if the following resource group exists: samplescalaservice1-rg.
##[error]Failed to check the resource group status. Error: {"statusCode":403}.
Finishing: Azure Deployment:Create Resource Group

What am I doing wrong please?

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

ID: cbb47179-04d1-7d43-23e0-6203a2bf9d6e
Version Independent ID: b84265b8-2c7d-6b0a-7f9f-b6332e4368db
Content: Deploy resources to subscription - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/deploy-to-subscription.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

Hi, I realized that my service connection from VSTS was not proper. After fixing that I am still stuck though.
That is because my pipeline task as detailed below tries to deploy to a resource group, the same group that it is actually trying to create.

task: AzureResourceGroupDeployment@2
displayName: 'Azure Deployment:Create Resource Group'
inputs:
azureSubscription: $(azureSubscription)
resourceGroupName: $(resourceGroupName)
location: $(location)
csmFile: '$(System.DefaultWorkingDirectory)/**/container-resourceGroup-template.json'
overrideParameters: '-rgName "$(resourceGroupName)" -rgLocation "$(location)"'

Removing the resourceGroupName: $(resourceGroupName) line from above fails because it is a required clause
I did not find a pipeline task for doing subscription level deployments, is there one?

Silly me, I didn't realize that pipeline tasks create a resource group if they do not find one!

@ArindamRayMukherjee Thanks for the regular updates on your findings and glad to know that you have self resolved your question(s). If there are further questions regarding this matter or feedback on the referred Azure documentation, please do let us know and we will gladly continue the discussion.

@ArindamRayMukherjee Closing this issue for now but If there are further questions regarding this matter or feedback on the Azure documentation, please do let us know and we will gladly continue the discussion.


Support S2i for Native builds

In order to manage the base image in use, you need to provide the properties:

For JVM: ts.global.s2i.quarkus.jvm.base.image
For Native: ts.global.s2i.quarkus.native.base.image

The way these properties are up to users. In the examples, we supply this configuration in the pom.xml as part of system properties (in the Maven failsafe plugin).
But we can provide a custom property by service in the test.properties file. For further information about how to customise the properties, go to the Configuration section.
Fix https://github.com/quarkus-qe/quarkus-test-framework/issues/206

LGTM.
Can you squash the commits?

Ops! Squashed.


Is there any animation-lib supports pixi.js?

I know some good animation-lib , e.g. http://mojs.io/ ,  http://animejs.com . But they only support css3 or svg.
Is there any animation-lib supports pixi.js?

GreenSock does.
https://greensock.com/docs/Plugins/PixiPlugin
Demo.
https://codepen.io/osublake/pen/qmXPMm

animejs supports js object (http://animejs.com/documentation/#JSobject).

Closing as a few good suggestions have been made :)


Add confirmation when saving a brew

Also add functionality to save a brew after the fact. Closes #70.

I like the look and feel of this so far, but the toast could be slightly bigger so it doesn't just disappear against the CTA button it's displayed on top of.


About page

Adds the about page with static content
Moves start pages into a base layout with an outlet for child routes
Made a separate issue for translating the other start page content

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


support extending from git

Environment

Operating System: Windows_NT
Node Version:     v16.19.0
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      extends
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/chrisfoss1/nuxt-extends-bug-repro
Describe the bug
In the nuxt config, adding a nuxt application via https:// to the extends key and then building throws the error:
ERROR  Failed to download template from https: Failed to download //github.com/madebyfabian/madebyfabian.git template info from https://raw.githubusercontent.com/unjs/giget/main/templates///github.com/madebyfabian/madebyfabian.git.json: 404 Not Found

Additional context
It appears to be trying to grab a template from https://github.com/unjs/giget.
https://nuxt.com/docs/guide/going-further/layers omits any examples with https://
According to https://nuxt.com/docs/api/configuration/nuxt-config#extends, https:// should be supported.
Although the provided reproduction uses a github repository, which is a supported provider with the github: prefix, I originally encountered this bug while trying to extend from a private repository on Azure.
Logs
No response

Direct URLs to a git repo are not currently supported, but I think an http provider would be quite useful (cc: @pi0). The current provider list can be seen here, and you can write your own provider for giget.

Could be that the docs are then outdated, since they say a https as a provider is allowed https://nuxt.com/docs/api/configuration/nuxt-config#extends

You're quite right, it does say that.

I would like to take a stab at this. Would the https url support github, gitlab, bitbucket, sourcehut and more, how do you see it working?

@hcmlopes I would suggest that it should support all git urls, regardless of the provider. As long as you type in the right url, e.g. https://github.com/madebyfabian/madebyfabian.git, it could be handled equally, or am I wrong on this?

@danielroe Should I create a PR to correct the docs on this or should we wait for an implementation by @hcmlopes (I would also offer to do one)

@hcmlopes I would suggest that it should support all git urls, regardless of the provider. As long as you type in the right url, e.g. https://github.com/madebyfabian/madebyfabian.git, it could be handled equally, or am I wrong on this?

I think you are right. But I was thinking this is a functionality from unjs/giget. In this case do I have to make a PR there?
@danielroe maybe you can just point me in the right direction in regards to that

When extending configuration, layers, and templates with giget, we use tarball only to download their latest snapshot (can be generalized to any unsupported provider https://github.com/unjs/giget/issues/10). We probably need a git built-in provider to support git: and git over HTTPs. Upstream issue: https://github.com/unjs/giget/issues/84

IIRC it is also viable to use a package with a direct git repo link. That way, subdependencies should be installed too.

I was able to achieve this by creating a personal access token & GIGET_AUTH env variable.
This is explained in the doc:

I've solved this problem gitlab. The error 406 downloading the archive from gitlab, is in the giget package. I creaeted a PR with a fix to this library
https://github.com/unjs/giget/issues/97

406 issue related to GitLab (rate limiter), should be fixed in the latest version of giget. (you can get the fix using npx nuxi upgrade --force)
More info about using auth is available in giget docs
You can track the git: protocol support via https://github.com/unjs/giget/issues/84, however, it is currently a low priority considering the complexities involved. If you have a use-case that requires git protocol please share your use-case in the linked tracker to prioritize 👍🏼


speed of sound term

From @jmsull,

When I look at the MB expression (eqn 67) for the baryon velocity, there is a speed of sound term that is proportional to delta_b that is missing in Callin/Dodelson (and Bolt). Shouldn't we have that?

I should get to the bottom of this...

Tangentially related - this paper argues that CLASS and CAMB are both wrong in the baryon EoMs (and that MB is not consistent with itself between eqn 30 and 67). I have not looked through the details but the changes presented in the conclusion would seem to take next to no effort to implement.

And coming back to the original question, the sound speed term is just dropped in Dodelson because he reuses the cdm eqns (in which the first moment of boltzmann has (p/E)^2 terms dropped) but with the additional photon coupling term. So the assumption of doing this is that baryons are cold and have no sound speed just like cdm. The reason given for keeping it in MB is that even though cs_b << 1, at high enough k it is still important (baryons are not totally cold).

We should insert the c_s^2 k^2 \delta_{b} term into the current hierarchy!. This is a really nice catch! I'll add a c_s function in ionization.jl. We can get the matter and radiation temperature out of both RECFAST and Peebles, which I hope to finish by the end of this week (it's slightly involved as RECFAST internally calculates a background, and I need to adapt that to our bg).
The Pookkillath paper is a lot of fun, and we should definitely make those photon/baryon Boltzmann equations an option. It looks to be very subdominant, so I think we can safely put that off for some time.

Should close this when we finish adding it in.

I added a spline for this to IonizationHistory in #44, cs2b(x) seems to match roughly with CLASS at intermediate times (1st attached), but something is happening at high redshift, and we also do not have reionization (2nd attached). I will open a new issue for reionization.

Both of these issues are qualitatively fixed in 43954ae - the high and low redshift disagreement in csb^2 was due to the previous expression (which I got out of MB) neglecting time evolution of mean mu, which is relevant early on and during reionization.
There is still some offset and numerical wiggling going on around the transition to reionization at the level of 2% - warrants further checking but I think this is ok for now(?).

Quick plot attached, bottom is csb2_Bolt/csb2_CLASS. nr is the no-reionization model.


Bots (or just PMCs) appear to have a busy hands issue

Need to figure out when this occurs and if there's any pattern.

Originally written by chomp

e.g.: here's a bit with his primary on his back and nothing in his hands. he was walking around.

Attachments

image.png (1215 KiB)

Originally written by chomp

Here's another one:

Attachments

image.png (1361 KiB)

Originally written by chomp

Do they have a working primary weapon? This can happen if their weapon is in the red state and the bot stays where it spawns.

Originally written by Barlog_M

potentially fixed with https://dev.sp-tarkov.com/SPT-AKI/Server/commit/0d78bc22f081bb560b52e36d663b1c31bf949136
needs alot of testing.

Originally written by Kaeno

ran a few raids, couldnt find this happening at all, closing

Originally written by CWX

[Exception] : NullReferenceException: Object reference not set to an instance of an object
BotCalledData.method_0 (EFT.IPlayer callerEnemy, EBotEnemyCause cause) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
BotsGroup.AddEnemy (EFT.IPlayer person, EBotEnemyCause cause) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
Aki.Custom.Patches.CheckAndAddEnemyPatch.PatchPrefix (BotsGroup __instance, EFT.IPlayer player, System.Boolean& ignoreAI) (at <1c769b03ba124d1f83fe2ff2d968cc41>:0)
(wrapper dynamic-method) BotsGroup.DMD<BotsGroup::CheckAndAddEnemy>(BotsGroup,EFT.IPlayer,bool)
BotMemoryClass.method_7 (DamageInfo damageInfo) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
BotMemoryClass.GetHit (DamageInfo damageInfo) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
EFT.BotOwner.method_9 (DamageInfo damageInfo, EBodyPart bodyType, System.Single damageReducedByArmor) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
EFT.Player.ApplyDamageInfo (DamageInfo damageInfo, EBodyPart bodyPartType, EBodyPartColliderType colliderType, System.Single absorbed) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
EFT.Player.ApplyShot (DamageInfo damageInfo, EBodyPart bodyPartType, EBodyPartColliderType colliderType, EArmorPlateCollider armorPlateCollider, GStruct389 shotId) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
BodyPartCollider+PlayerBridge.ApplyShot (DamageInfo damageInfo, EBodyPart bodyPart, EBodyPartColliderType bodyPartCollider, EArmorPlateCollider armorPlateCollider, GStruct389 shotId) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
BodyPartCollider.ApplyHit (DamageInfo damageInfo, GStruct389 shotID) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
EFT.ClientGameWorld.ShotDelegate (GClass2988 shotResult) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
EFT.Ballistics.BallisticsCalculator.method_2 (System.Single simulationTime) (at <eb2fa4f85a644d9c9c29454abd168831>:0)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
Class357:UnityEngine.ILogHandler.LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
EFT.Ballistics.BallisticsCalculator:method_2(Single)
EFT.Ballistics.BallisticsCalculator:ManualUpdate(Single)
EFT.GameWorld:BallisticsTick(Single)
EFT.GameWorld:DoWorldTick(Single)
EFT.GameWorldUnityTickListener:Update()

Originally written by Kaeno

seems to be not fixed needs looking into further

Originally written by Kaeno

I got this too. I had set AI_Amount to "Horde" and have never seen this bug before...

Attachments

2024.02.21_22-20-40_<IP_ADDRESS>.28744 traces.log (576 KiB)

Originally written by All_Heil_Lord_Ppepe

Looking at the previous attached log, I think this may be the originating error:
2024-02-21 15:25:50.371 -07:00|<IP_ADDRESS>.28744|Error|Default|
EXCEPTION: System.Exception: In response to http://<IP_ADDRESS>:6969/client/game/bot/generate: Value cannot be null.
Parameter name: key
  at Class259+Struct16`1[T].MoveNext () [0x00083] in <44fa49c177bb44f5a3c6ba5995413b84>:0

This appears while trying to convert the response from generate to a Profile[] array. Bad data coming back from the server maybe?

Originally written by DrakiaXYZ

Some updates:

The exception in my previous comment is unrelated, it's caused by invalid bot inventory data when money is spawned in bot wallets.

I've opened https://dev.sp-tarkov.com/SPT-AKI/Modules/pulls/84 which should fix the exception Kaeno saw, as it results in OnEnemyAdd no longer being called for bots that have been disposed

However I don't believe this fixes the underlying issue of bots not being properly spawned/disposed, resulting in a bot that just stands there and can't be killed. Have been unable to reliably reproduce that particular issue, and as far as I can tell, there are no uncaught exceptions that were leading to it happening

Originally written by DrakiaXYZ

Issue appears to be resolved

Originally written by chomp


[Compute] Could not find member 'securityProfile' on object of type 'Properties

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug

az cloud set -n AzureCloud --profile 2019-03-01-hybrid
az vm create -g fy -n vm --image win2016datacenter --admin-username clitester --admin-password PasswordPassword1!

returns
Could not find member 'securityProfile' on object of type 'Properties

The request body contains "securityProfile": {}. It appears that the old version of Compute does not accept this field even it is an empty dict. It will be fixed on 5/4/2021.
To Reproduce

Expected behavior

Environment summary

Additional context

VM


Electron Daemon at startup making all electron based apps run really quickly

I had this in mind, and I remember opening an issue:
https://github.com/electron/electron/issues/12732
They didn't respond that much.

This module is for use when developing Electron apps, not for production.

Sorry, I'm working on sth I call #UserStoryHub, I don't know how else to make my ideas reach industry.
In the hub ideas would compete, so the industry will know the top needs of people.
Thank you for your time.


Chef Core maintainers: ++fujin

per https://github.com/chef/chef/pull/2710#issuecomment-73626709
I have a Fedora environment at work currently (fleet of about 250) so would considering putting myself forward for those if I end up maintaining a lot of Redhat-specific crap.

:+1:

:+1:

:+1:

werd

:thumbsdown:
Good thing my opinion doesn't count :)

@damm I introduced you to Chef after learning Merb with you, via the Feather project. I showed you a home in a community that did not exist. You've made your own choices - but they do not affect me, nor Chef, and I'm thankful I'm able to put our time together behind me.
I don't know where we ever went wrong, but I consider the time we worked together to be the worst possible examples of job-security through obfuscation, malpractice and worse; I was thankful to see you relieved of your post.
I hope to never inherit an installation tainted by you again. I have blocked you on all communication mediums. I will aggressively give a negative character reference toward you in the event I that I am requested of one, although this seems extremely unlikely.
Please feel free to avoid any direct communication with me in the future. I would not mind if you disassociated yourself with the project entirely, including giving up your squatting on the Supermarket.
Good day,
--aj

As one of the oldest contributors to Chef, and a current contributor, with (so far) universal support (including mine) - AJ should absolutely be a maintainer.
As a community, we have a code of conduct, we have multiple governance documents, and plenty of ways to work together - and to work through our issues.


Any plans on focus system?

Hello, nice to see some open source projects in this area. Working right now with React and smart tv:s and built to multiple smart tv platforms and consoles (playstation). If I have time over I can see if I can contribute. One thing that I always thinks of is the focus system. Web is really good at mouse interaction but keyboard navigation is lacking. Is that something you are planning to look into?
Best regards

Nice @EloB
I'm planning two draft proposals for keyboard navigation:

Using a Navigator component ( import reactTV, { Navigator } from 'react-tv';
Compose all components with handlers for keyboard navigation when asked.

Anything that you want to help on ReactTV or talk about the future release. I'm available for talk :octocat:

Nice :)
I just discovered this by Dan Abramov shared this on twitter. My current customer uses smart tv:s. So built some apps so I know the struggle of building performant apps in this area.
When I have time I will look into the codebase and see if I can contribute with something. A tip for Orsay is to add weinre. I don't know if there is any debugger for Orsay but I used that with good result (script debugger doesn't work but you can atleast reach a console and element tab).
A good way to find documentation for Orsay is to use the archive.org wayback machine. Their new site doesn't always show everything about "legacy platform" and I found some lost information when using that method.
Also add this to babel (if that is used) is a good win for performance. :)
"env": {
  "production": {
    "plugins": [
      "transform-react-constant-elements",
      "transform-react-inline-elements"
    ]
  }
}

When I have time I will look into the codebase and see if I can contribute with something.

Sure, I'll be happy to help.

Orsay is to add weinre

I didn't know. Thanks for sharing it.
About babel and Reactive framework, I'm studying more other options and possibilites, even hacks hehe. :octocat:

@EloB you can install legacy Samsung SDK and debug Orsay app with chrome dev tools on emulator.
Emulator has many differences with real TV and some weird bugs, but it more useful than weinre.
@raphamorim i have several good examples on implementing dpad focus system for react.

Please share with me this examples, I just started work on it :D

@DChinin Thanks for the info. We are currently not using emulators. They feel far from the end result. We are working realtime on the hardware and shares keystrokes from your desktop keyboard to the tv:s.
I will definitely but that on my mind when I can't figure out some bugs :)

I recently developed a test app to a samsung tizen tv and created a wrapper around the js-spatial-navigation to work as react components. It was my very first contact with both tv and react so it is pretty simple, but works 😄.
I found the spatial navigation a neat solution to the navigation problem (as it use the position of the components in the screen to select where to move the focus). It certainly isn't the best solution in performance but it make so much easier to create navigable stuff.

@dead We have done the same but we discovered a bad thing that browsers scroll focused elements into view even in overflow: hidden containers. There isn't any good way to prevent that scroll into view action.

@EloB yeah, we had to cancel out this scrolling by setting scroll{Top,Left} to 0 for all parents of focused element, but that breaks performance.
I think the right way to do focus managements is not using dom apis, since the (custom)renderer knows all the elements that are focusable at the moment, it can hold focus state.

What about a navigation based on a component hierarchy like the one on BBC-TAL?
With some base components (i,e: vertical and horizontal layouts, grid layout and focusable items) you can compose whatever you need.
I believe that is more deterministic than the js-spatial navigation (based on trigonometric calculation, if remember ) and will have a better performance.
In the other hand I have a little experience with React components and I'm not sure how easy will be to propagate the key events from @raphamorim Navigator to the focused item, and from the item to its parents.

@idmitriev We do the same with the scrollTop/scrollLeft but they are known props that triggers reflows as you said... :( https://gist.github.com/paulirish/5d52fb081b3570c81e3a

@EloB
You can prevent this by simple disabling the elem.focus() in the js-spatial-navigation (browser focus).
But now If you want a scrollable list or something like that you will need to implement a ´ScrollableItemList` component in react that handle the scrolling.

@dead Probably modern browsers might have implemented like that but it's a non standard. What I seen on the actual devices (Tizen/Orsay/Ps4) have been problematic.
https://developer.mozilla.org/en-US/docs/Web/Events/focus
focus event is not cancelable.

@dead Or did I get you wrong? Is it possible to disable the element.focus() but still have all the other action working?

A bad thing with js-spatial-navigation is the keyCodes are hard coded. Made a PR for that https://github.com/luke-chang/js-spatial-navigation/pull/20 but that repo seems dead. It's not part of NPM either...

It is possible to disable the elem.focus() and it should still work (the sn: events will be fired).

Had a quick look at js-spatial-navigation source, seems like there is a CustomEvent triggered on element focus\blur.
But this won't work with react's synthetic event system because does not support dispatching CustomEvents.

More navigation stuff 😄
https://github.com/dead/react-key-navigation
It is similar to the BBC TAL. Use the hierarchy to navigate.

Some good info:
https://medium.com/netflix-techblog/pass-the-remote-user-input-on-tv-devices-923f6920c9a8
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS_for_TV/TV_remote_control_navigation

@EloB I'm made a draft of a first navigation interface. Can you give some review?
Issue Here -> https://github.com/raphamorim/react-tv/issues/63


Problem with Database if using prefix

Step to reproduce :

Installing Magento 2 with a database prefix like mg2_
Install Product Attachment with setup:upgrade

Explaination :

Magento is trying to find index lizardmedia_product_attachment but during the installation Magento named it {prafix}lizardmedia_product_attachment. So it's not found

Solution to avoid the problem:

Replace the following lines :

in Setup/InstallSchema.php line 125 : $setup->getTable(Attachment::MAIN_TABLE),
in Setup/InstallSchema.php line 129 : $setup->getTable(Attachment::MAIN_TABLE),

@Feyks thank you for reporting this issue. We dont use prefixes, so we didnt meet such an issue. I will fix it quickly.

#6

@Feyks PR is ready and it will be reviewed soon. You can also take a look at #7

@Feyks fix is shipped with new release 1.0.4. Please let me know if now you can install module.

I ll try to install wheni ll rebuild my magento docker.  Seeing the updated code, i think i won't have any trouble.
Thanks for your time and your module.

@Feyks have you tried?


Next.JS 13 App Dir Favicon Not Displaying

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d19oqxloeeub82
AWS Region
us-east-1
Amplify Hosting feature
Not Applicable
Describe the bug
The favicon added to the root of a NextJS 13 app-dir project does not display when deployed.
Expected behavior
As per the docs, the favicon with the name of 'icon.png' placed in the root dir should display as the favicon.
Reproduction steps

Create a new NextJS 13 project with the app-dir enabled.
In the app dir, add an icon with the name icon.{png, svg,etc...}
Build locally and observe the icon is displayed in the head.
Deploy to amplify, and observe the icon is not available.

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @SamKomesarook 👋🏽 thanks for raising this issue. I'm not able to reproduce the behavior you're seeing. Here is what I did:

create a Next.js app using version 13
create an app directory
enable the app directory by adding experimental : {appDir: true} to the next.config.js file
create a layout.js
create a page.js
add the icon.png to the app directory.
serve the app locally to confirm the icon is visible
deploy to Amplify

I'm able to see my icon in the head locally and after deploying to Amplify.
Can you check your Network tab and see what response is being returned for the icon's GET request?

@hloriii I should have been more specific, I can see it in the source head, however it is not actually displayed in the browser tab. Can you see the icon in your test example?

@SamKomesarook I can see the icon being displayed in the browser tab for my app. Can you provide a screenshot to highlight what you're seeing in your hosted app and a screenshot of what you're expecting to see from your local app?
Here is my bare bones app using the app directory feature so you can see: https://main.d3e6hxeizdoy.amplifyapp.com/

Thank you for the example! From looking at your example, the href for your link is within the _next/static folder, while ours is a local reference, which breaks when deployed... This is likely a NextJS issue. I appreciate your help!


Markup distribution updated

Description
Please include a summary of the change and which is fixed.

Add A
Fix B

How has this been tested?
Please describe the tests that you ran to verify your changes.

[ ] UnitTest
[ ] Benchmark

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (3d7de32) 90.44% compared to head (a0baa8b) 90.44%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #504   +/-   ##
=======================================
  Coverage   90.44%   90.44%
=======================================
  Files         127      127
  Lines        4335     4335
  Branches      695      695
=======================================
  Hits         3921     3921
  Misses        273      273
  Partials      141      141

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


Useless and ugly point hover preview in exit confirmation dialog

From what I understand, @ikarago has enabled "keyboard accelerators" (fancy MS speak for shortcut), so you can press Y or N on the keyboard to select the corresponding action. Since Windows 10 1803, the SDK displays a tooltip with the accelerator by default unless overridden. You're right, it does look ugly and I can think of a few different changes:

Replace the tooltip. I personally see no point in having a tooltip at all for a simple "Yes" or "No" button if it just repeats the label unless the tooltip clarifies the action such as "Discards the current document" for when you hover on "Yes". This may raise a bigger question about wording these options better for the sake of UX clarity. Microsoft discourages Yes/No/Cancel options in favor of descriptive ones like Discard/Save. I'll make a separate issue for that one.

Make the keyboard accelerator actually appear on the right side of the button in lighter text for better discoverability. Here's an example:

It would then make more sense to remove the tooltip.

Is this more to your liking? :)

I don't like Y/N in general, but in this way it looks better👍

Great for discoverability! And what happens when you hover? Did you get to change the tool tip?

I have been able to hide the tooltips for now, as I'm not sure if it would be better UX if the ToolTip explains the option or just not show up at all (as all needed info is already in sight)

Yeah the tool tip would be redundant I think

I've redone the wording of the dialog. What do you think @MarcAnt01?

I like it, good work @ikarago


Contract spec: host function API version

The change https://github.com/stellar/rs-stellar-contract-env/pull/120 renamed host functions. This is fine and we're still iterating and I'm not upset about it but it broke existing wasm blobs (eg. those embedded in tests) that expected the old host function names to exist.
This revealed / reveals a thing I think we should probably encode in contracts: the host function API version they were compiled against. Not because I expect we'll multi-version the API surface or anything -- I expect long-term we'll commit to a strictly backward-compatible API unless there are dangerous bugs -- but because I think @jonjove spent a while hunting the bug and it would be better to give concise diagnostics for such mismatches (new contract running on old host, or compatibility break for whatever reason) during contract instantiation rather than failing inscrutably during execution.
So I think we should have "the version of the host you were compiled against" as metadata pasted into yet another custom section in the wasm (or in the spec section if you can include it there, I don't care).

💯 It should be trivial to include this in a custom section we just need to decide how we version the host API. For example, will this be a hard coded constant we manually bump? or automatically generated somehow by the host API macros?
This is also one reason why the CLI has an inspect sub-command, so that we can quickly pull up info about a WASM file and we can expose this information there. In the SJC prototype we would output the imports (dependencies) too, and we can add that to inspect that should help with debugging.

it would be better to give concise diagnostics for such mismatches (new contract running on old host, or compatibility break for whatever reason) during contract instantiation

Actually, the host VM could do this today without introducing any version meta into WASM files. We could add validation into the host VM that compares the required imports with the available imports and displays a well formed error stating exactly which imports are missing. Ideally the host isn't erroring generically in this situation.

❯ stellar-contract-cli inspect --file target/wasm32-unknown-unknown/release/example_udt.wasm
File: target/wasm32-unknown-unknown/release/example_udt.wasm
Functions:
 • add (val, val) -> (res)
Env Meta: AAAAAAAAAAAAAAAB
 • Interface Version: 1


Use ETags when sending files to reduce traffic

With this PR files (e.g. an image) that are requested by the file URL of the server, are sent to the client with an ETag attached in the response header.
With this PR I don't intend to add ETags to Parse.Query responses from the server or something else directly related to Parse. According to your comment this might already work if I understand it right.
Parse.Files are retrieved by Parse.Queries. But the file, e. g. an image, is retrieved by the file URL that we can get from the Parse.File object. So if we then request the file from the server by the file URL and the server fetches the file data e. g. from the local mogodb, it will send the file contents without attaching an ETag, thus sending the file again and again even if it wasn't modified. By attaching ETags, the files won't be sent over and over again.
I hope I could help you.

FYI, this looks good to me, but i just don't have enough knowledge of etags and express to have the confidence to test and merge.

@flovilmart any thoughts on this one?

Not really, but they are enabled at large, so they could be enabled externally also.
I has a conflict too.

well, I can resolve the conflict at the command line no problem.
the change from res.end to res.send doesn't seem like a problem.  just read the docs.
make a call please: close or I'll resolve and get it in.

what worries me is that the etag header is not only on the files, but on all responses. (as it seems) so....


Add kubernetesCRD labelSelector/ingressClass

Add the option to match labelSelector/ingressClass for kubernetesCRD provider
The dashboard ingressRoute need the matching labels/annotation

Humm...  I'am kindly new to kubernetes but it seems that  kubernetes.io/ingress.class is deprecated since 1.18

Are there any  updates ?


Added a bug-reporting.html page that directs people to crash-reporting.html

phantomjs 2.1.1 writes out:

Please read the bug reporting guide at
http://phantomjs.org/bug-reporting.html and file a bug report.

The page just says that it has moved to crash-reporting.html and provides a link.
This is modelled on http://phantomjs.org/contributing.html

Thanks! Landed!


TypeError: Cannot read properties of undefined (reading 'path')

Describe the bug
Using Netlify as CMS - I am the user, not the developer. Developer unavailable at this time.
Trying to upload a .pdf to the Media section of our CMS. Keeps supplying me with an error message. No longer shows me the other pieces of media that were in there, like images and other pdfs.
To Reproduce
Expected behavior
I should be able to upload .pdfs or images. But keeps coming up with this error message (see screenshot below).
Screenshots

Applicable Versions:

Decap CMS version<EMAIL_ADDRESS>Git provider: proxy
Browser version: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>

CMS configuration
local_backend:
  url: https://hybridcloud.hpecorp.net/api/v1
  allowed_hosts:
    - hybridcloud.hpecorp.net
backend:
  name: proxy
  proxy_url: https://hybridcloud.hpecorp.net/api/v1
editor:
  preview: false
media_folder: public/assets
public_folder: assets
collections:
  - name: Top Navigation
    label: Top Navigation
    folder: contents/nav/topmenu
    create: true
    slug: "{{year}}-{{month}}-{{day}}"
    fields:
      - label: Top Nav Title
        name: top_nav_title
        default: Top Nav - Do Not Change
        widget: string
      - label: Top Nav List
        name: top_nav_list
        widget: list
        fields:
          - label: Title
            name: title
            widget: string
          - label: Link
            name: link
            default: "#"
            widget: string
          - label: Has Sub Menu
            name: has_sub_menu
            widget: select
            default: Yes
            options:
              - Yes
              - No
          - label: Open in New Tab
            name: open_in_new_tab_menu
            widget: select
            default: No
            options:
              - Yes
              - No
          - label: Is Mega Menu
            name: is_mega_menu
            widget: select
            default: No
            options:
              - Yes
              - No
    publish: true
    type: folder_based_collection
    sortable_fields:
      - top_nav_title
    view_filters: []
    view_groups: []
    editor:
      preview: false
  - name: sub_nav
    label: Sub Navigation
    folder: contents/nav/submenu
    create: true
    slug: "{{year}}-{{month}}-{{day}}"
    fields:
      - label: Top Navigation Title
        name: title
        widget: relation
        collection: Top Navigation
        search_fields:
          - top_nav_list.*.title
        value_field: top_nav_list.*.title
      - label: Sub Menu Level 1
        name: sub_menu_1
        widget: list
        fields:
          - label: Title
            name: title
            widget: string
          - label: Link
            name: link
            widget: string
          - label: Has Sub Menu
            name: has_sub_menu
            widget: select
            default: No
            options:
              - Yes
              - No
          - label: Open in New Tab
            name: open_in_new_tab_menu
            widget: select
            default: No
            options:
              - Yes
              - No
          - label: Sub Menu Level 2
            name: sub_menu_2
            widget: list
            fields:
              - label: Title
                name: title
                widget: string
              - label: Link
                name: link
                widget: string
              - label: Has Sub Menu
                name: has_sub_menu
                widget: select
                default: No
                options:
                  - Yes
                  - No
              - label: Open in New Tab
                name: open_in_new_tab_menu
                widget: select
                default: No
                options:
                  - Yes
                  - No
    publish: true
    type: folder_based_collection
    sortable_fields: []
    view_filters: []
    view_groups: []
    editor:
      preview: false
  - name: footer
    label: Footer
    folder: contents/nav/footer
    create: true
    slug: "{{year}}-{{month}}-{{day}}"
    fields:
      - label: Site Resources
        name: site_res
        widget: list
        fields:
          - label: Title
            name: title
            widget: string
          - label: Link

...

@drensing it seems that the error is from the about us section, but you did not provide a config for it. Please update the issues description with that.

Thank you.
I connected with one of our developers here who seems to know what the issue is and can fix it.


Console messages emitted from Jest's beforeAll hook do not cause failOnConsole to fail the test

HI! First of all, thank you for this library, it was a godsend for us when cleaning up our messy unit test report :)
I think I have found a bug that caught us off guard, though. It seems that if the console is used in beforeAll (it might be other Jest hooks too, I just have not confirmed) it doesn't cause the tests to fail.
Our configuration:
failOnConsole({
  shouldFailOnWarn: true,
  shouldFailOnError: true,
  shouldFailOnAssert: true,
  shouldFailOnDebug: true,
  shouldFailOnInfo: true,
  shouldFailOnLog: true,
  silenceMessage: m => {
    // This error is removed in React 18 because it is misleading, so suppressing until we upgrade: https://github.com/reactwg/react-18/discussions/82
    if (m.includes("Can't perform a React state update on an unmounted component.")) {
      return true;
    }
    return false;
  }
});

An example which will emit the following error:

  beforeEach(() => {
    jest.useFakeTimers();
  });

  // `beforeAll` is the cause of the warning, it should be `afterEach` but this illustrates the issue
  beforeAll(() => {
    // Emitted here, but test PASS
    jest.runOnlyPendingTimers();
    jest.useRealTimers();
  });

  it('Emits a warning which correctly fails the test run', () => {
   // This is the same sequence of commands and they also result in a Jest warning. This time tests will FAIL
    jest.runOnlyPendingTimers();
    jest.useRealTimers();
    jest.useFakeTimers();
  });

Please take a look at this code sandbox: https://codesandbox.io/s/jest-fail-on-console-hooks-7rut79?file=/src/index.test.js
Unfortunately, even though Codesandbox supports Jest and the tests run, it doesn't seem to allow us to use any of the fake-timer controlling features due to this bug: https://github.com/codesandbox/codesandbox-client/issues/513. Hopefully, this example is easy enough to reproduce locally.

Thanks for the detailed issue report.
Unfortunately, I'm not sure that we can do something about this 😬
Indeed, we are using beforeEach/afterEach to setup/teardown this plugin logic for each test:
https://github.com/ValentinH/jest-fail-on-console/blob/main/index.js#L85-L99
As far as I know, they run after beforeAll so too late in your case.
Conceptually, I'm not sure we could make a test fail because this run before all tests. Therefore, which test should be failed in that case?
That being said, we could at least update the README to explain this limitation.

@ValentinH in this case I would be ok with not knowing which test failed. The most important thing would be that it fails at all. But I agree it might not be possible with the current architecture.

A related use-case - we're relying on silenceMessage to silence some annoying warning mesages. Sometimes, those warning messages are emited during beforeAll - at the moment, jest-fail-on-console is unable to silence those messages for us.
It would be great if that aspect (at least) could be fixed 🤞

Silencing might work if we also register our interceptors in a beforeAll call. Today, we only do it in a beforeEach. Would you be willing to test this and submit a PR if it works?
However, I'm still not sure if failing tests if we see that a non-silenced console is called could be done for the reasons I shared above.

@ValentinH registering the inceptors in beforeAll did help 👍 - see https://github.com/ValentinH/jest-fail-on-console/pull/39
I had issues running the tests locally on main after a yarn install (i.e. before making changes) so I'm unable to check whether the changes impact any tests.
yarn run v1.22.5
$ jest tests/index.test.js
 FAIL  tests/index.test.js
  jest-fail-on-console
    × errors when console.error() is called (27 ms)
    × does not error when console.error() is called but shouldFailOnError is false (23 ms)
    × does not error when console.error() is called and skip test by test file path returns true (23 ms)
    × does not error when console.error() is called and skip test by test name returns true (22 ms)
    × errors when console.assert() is called with a failing assertion (22 ms)
    × does not error when console.assert() is called with a passing assertion (22 ms)
    × does not error if message is silenced with `silenceMessage` (23 ms)
    × does not error if message is silenced with `silenceMessage` based on console method (23 ms)
    × does not error if message is silenced with `silenceMessage` based on group context (23 ms)
    × does not error if message is silenced with `silenceMessage` based on nested group context (23 ms)

  ● jest-fail-on-console › errors when console.error() is called

    expect(received).toEqual(expected) // deep equality

    Expected: StringContaining "Expected test not to call console.error()."
    Received: "'.' is not recognized as an internal or external command,·
    operable program or batch file.·
    "

      21 |     const { stderr } = await runFixture('error')
      22 |
    > 23 |     expect(stderr).toEqual(expect.stringContaining('Expected test not to call console.error().'))
         |                    ^
      24 |   })
      25 |
      26 |   it('does not error when console.error() is called but shouldFailOnError is false', async () => {

      at Object.<anonymous> (tests/index.test.js:23:20)

  ● jest-fail-on-console › does not error when console.error() is called but shouldFailOnError is false

    expect(received).toEqual(expected) // deep equality

    Expected: StringContaining "PASS tests/fixtures/error-disabled/index.test.js"
    Received: "'.' is not recognized as an internal or external command,·
    operable program or batch file.·
    "

We've just hit this issue as well. We merged a PR that didn't catch the React errors that were being logged before the tests started. Now, we're seeing numerous errors during test runs.
The errors occurred before Jest executes beforeEach, which resets the errors it has caught.  Then when it runs the afterEach, no errors are reported.

The most important thing would be that it fails at all.

I agree with this, I'd rather have no errors than caring if it's tied to a specific test case.  While we'll resolve our current React/jest issues, I'd like to prevent this happening again altogether.
I have a branch that seems to resolve the issue (no tests yet).  The way it works is it overrides each console implementation immediately once setup, then in the beforeAll it flushes the console calls out, then business as usual.
Does this change work for you @ValentinH?

If the tests are still passing, I'm fine with this change.

PR is up with a test.


Removing references to a maven build within the contributing file

Right now, the CONTRIBUTING.md file is not relevant to the current project.  This PR resolves this issue and documents the steps that should be taken to validate a bugfix.

Resolves #110


C-like: Made all comments greedy

This fixes #2679.
The problem was that multiline comments in C-like weren't greedy. This usually isn't a problem because a non-greedy first grammar rule behaves amlost as if it was greedy with one exception: greedy rematching.
Basically, previously matched tokens have to be overwritten by greedy tokens but non-greedy tokens can't do that. This then results in the token stream seen in #2679:

I also had to make a minor adjustment to Coffeescript because the tests failed. The problem there was that the delimiter token was matched before comment which meant that the lookbehind group of the comment pattern didn't accept. This is a general problem with greedy rules and lookbehinds that cannot be fixed without ES2018 lookbehinds (#1708).

@RunDevelopment I'm good to release a new version later this evening. Is there anything else you want to get merged for it?

Nope. All other PRs need further work and/or offer little immediate benefit to our users.
I'll make you the changelog.


Is there any way to pass url variables to schema?

I'm trying to pass URL to my schemas thru a variable like in the image below, isn't there any way to do this? If some day we change the base url we would have to change all the project this would be very inconvenient, i hope there is a solution for this problem :)

I am not sure if I get your question correctly,
but Open-API spec dont allow having variables in schema
However for servers the spec do allow having variables. Some call them as Server Templating
RapiDoc supports server-templating
check out this example which demonstrate this https://mrin9.github.io/RapiDoc/examples/server-vars.html
the open-api spec for the above example is here https://github.com/mrin9/RapiDoc/blob/master/docs/specs/server.yaml


Something to investigate maybe

>>> from decksite.data import match as ms
>>> from shared import dtutil
>>> ms.insert_match(dtutil.now(), 28744, 0, 28745, 2, None, None, None)
Before BEGIN ([])
After BEGIN (['insert_match'])
Before COMMIT ([])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/discord/decksite/decksite/data/match.py", line 36, in insert_match
    db().commit('insert_match')
  File "/home/discord/decksite/shared/database.py", line 103, in commit
    committed = self.open_transactions.pop()
IndexError: pop from empty list

I was adding a match manually and this happened which feels wrong.

This is because I'm not in app context so I have nowhere to store my ongoing transactions rather than a bug that affects prod.
def db() -> Database:
    if has_request_context():
        ctx = request
    elif g:
        ctx = g
    else:
        ctx = Container() # Fallback context for testing.
    if not hasattr(ctx, 'database'):
        ctx.database = get_database(configuration.get_str('decksite_database'))
    return ctx.database

It also happens post-COMMIT so the INSERTs were run fine.


chore: split stable and experimental packages into groups

This is a WIP to use multiple lerna.json files to group packages.

@dyladan should this be closed ?


Update index.html

@limaleandro1999   thnx for contributing , try this year aswell with updated repo and make sure to follow me and star this repo so that you don't miss updates regarding the new changes and issues during Hacktoberfest 2020.


Add EventStore Testcontainer

Add PR for feature EventStore to Testcontainer: #730

The module configuration looks good, thanks. Unfortunately, it follows the old approach. I will finalize the new module API next week. Do you mind if we wait until #729 is done? Then we do not have to migrate afterwards again.

It's ok. You can add this module to old version too and also after #729 is done I can add it again to new version. Because the structure was unknown for the new version and there was no test, I implemented it on the previous structure.

I try to add this feature with new style of project.


typos in maddr32 & msubr32?

according to the desc,

Description: This instruction multiplies the lower 32-bit content of Rs1 with that of Rs2, subtracts the lower 32-bit multiplication result from the lower 32-bit content of Rd, then writes the final result (RV32) or sign-extended result (RV64) back to Rd. The contents of Rs1 and Rs2 can be either signed or unsigned integers.

the intrinsic functions of msubr32 sound more like
intXLEN_t __rv__msubr32(int32_t a, int32_t b);

instead of
int32_t __rv__msubr32(int32_t a, int32_t b);

to me (the same for maddr32). Did I get something wrong?

The description of RV64 is for writing a result with a signed 32-bit range into a 64-bit register. However, the return type of the intrinsic function does not need to match the 64-bit register result that has a signed 32-bit range. Most of the time, using int32_t as the return type will let a compiler generate more efficient code than using int64_t as the return type. Because if the following use of the returned result is in the type of int32_t, no extra instructions will be generated. Otherwise, the int64_t type data needs to be processed into a int32_t data by a compiler with extra instructions which are unnecessary.


Ensured gasPrice can be set to 0

It should be possible to set the gasPrice to  0 if desired but the current implementation doesn't allow it. This commit fixes this behaviour.

Easy peasy - thanks for the contribution!


Menu: Logo needs to be updated to current vector image.

currently the older png logo is being shown.

Still seeing this across the game. by removing the "f_auto" tag this isn't an issue:

still occuring after latest build 6:30pm friday


Is this extensiv

Hi, I'm interesting to know if you're evaluated the flexibility of this approach to other kind of body joints annotations, such as the common 21-joints.
Thank you in advance.

Yes, just change the parameter to joints_num=21 and joints_dim=2/3  in every file.


Add tests for deletec

Add tests for deletec
Add (some) tests for TaAssistParser
Fixed some test cases in addc
Fixed deletec bug

Codecov Report
Base: 55.34% // Head: 58.53% // Increases project coverage by +3.18% :tada:

Coverage data is based on head (f5f60ee) compared to base (2eb33f7).
Patch coverage: 90.47% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #154      +/-   ##
============================================
+ Coverage     55.34%   58.53%   +3.18%
- Complexity      470      499      +29
============================================
  Files           102      102
  Lines          1852     1857       +5
  Branches        203      203
============================================
+ Hits           1025     1087      +62
+ Misses          764      710      -54
+ Partials         63       60       -3

Impacted Files
Coverage Δ

src/main/java/seedu/taassist/model/Model.java
100.00% <ø> (ø)

...du/taassist/logic/parser/DeletecCommandParser.java
71.42% <66.66%> (+71.42%)
:arrow_up:

...ava/seedu/taassist/logic/commands/AddcCommand.java
100.00% <100.00%> (+26.92%)
:arrow_up:

.../seedu/taassist/logic/commands/DeletecCommand.java
100.00% <100.00%> (+100.00%)
:arrow_up:

...c/main/java/seedu/taassist/model/ModelManager.java
77.01% <100.00%> (+10.73%)
:arrow_up:

...va/seedu/taassist/logic/parser/TaAssistParser.java
58.62% <0.00%> (+3.44%)
:arrow_up:

.../seedu/taassist/model/moduleclass/ModuleClass.java
86.95% <0.00%> (+4.34%)
:arrow_up:

src/main/java/seedu/taassist/model/TaAssist.java
86.66% <0.00%> (+6.66%)
:arrow_up:

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Close #125.


QR code logo everywhere (also in extensions)

Customizable QR logo has been merged in https://github.com/lnbits/lnbits/pull/1955
So far it is shown only on few place. Let's make it appear everywhere in LNbits and also in all LNbits extensions.

Duplicate of https://github.com/lnbits/lnbits/issues/1949


doc: new guide to deploy on Cloud Run

Also refactored the existing guide to create containers to make both
look similar.
Fixes #226. Part of the work for #202

/cc: @grant FYI


Add curl 8.8.0

Based on https://github.com/bazelbuild/bazel-central-registry/pull/2233
but provides platform specific defaults

macOS builds on Bazel 6.x are stuck waiting for remote cache after success. Force-submitting.


[Regression] The property [SpecializedProperty System.Collections.Generic.List`1[[System.Int32]].Count():System.Int32] is not marked as FieldProperty but implemented interface member has such attribute

After updating from 1.11.2 to 1.12.0 our project is failing to build wherever List.Count is accessed with compilation error:
Error		Error: The property [SpecializedProperty System.Collections.Generic.List`1[[System.Int32]].Count():System.Int32] is not marked as FieldProperty but implemented interface member has such attribute    at Bridge.Translator.MemberReferenceBlock.VisitMemberReferenceExpression()
   at Bridge.Translator.MemberReferenceBlock.EmitConversionExpression()
   at Bridge.Translator.ConversionBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitMemberReferenceExpression(MemberReferenceExpression memberReferenceExpression)
   at ICSharpCode.NRefactory.CSharp.MemberReferenceExpression.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.BinaryOperatorBlock.VisitBinaryOperatorExpression()
   at Bridge.Translator.BinaryOperatorBlock.EmitConversionExpression()
   at Bridge.Translator.ConversionBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitBinaryOperatorExpression(BinaryOperatorExpression binaryOperatorExpression)
   at ICSharpCode.NRefactory.CSharp.BinaryOperatorExpression.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.ForBlock.VisitForStatement()
   at Bridge.Translator.ForBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitForStatement(ForStatement forStatement)
   at ICSharpCode.NRefactory.CSharp.ForStatement.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.Block.<DoEmitBlock>b__64_0(AstNode child)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Bridge.Translator.Block.DoEmitBlock()
   at Bridge.Translator.Block.EmitBlock()
   at Bridge.Translator.Block.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitBlockStatement(BlockStatement blockStatement)
   at ICSharpCode.NRefactory.CSharp.BlockStatement.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.ForeachBlock.VisitForeachStatement(Nullable`1 replaceAwaiterByVar)
   at Bridge.Translator.ForeachBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitForeachStatement(ForeachStatement foreachStatement)
   at ICSharpCode.NRefactory.CSharp.ForeachStatement.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.Block.<DoEmitBlock>b__64_0(AstNode child)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Bridge.Translator.Block.DoEmitBlock()
   at Bridge.Translator.Block.EmitBlock()
   at Bridge.Translator.Block.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitBlockStatement(BlockStatement blockStatement)
   at ICSharpCode.NRefactory.CSharp.BlockStatement.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.VisitorMethodBlock.VisitMethodDeclaration(MethodDeclaration methodDeclaration)
   at Bridge.Translator.VisitorMethodBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitMethodDeclaration(MethodDeclaration methodDeclaration)
   at Bridge.Translator.MethodBlock.EmitMethodsGroup(List`1 group)
   at Bridge.Translator.MethodBlock.EmitMethods(Dictionary`2 methods, Dictionary`2 properties, Dictionary`2 operators)
   at Bridge.Translator.MethodBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.ClassBlock.EmitStaticBlock()
   at Bridge.Translator.ClassBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.EmitBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.Emit()
   at Bridge.Translator.Translator.Translate()
   at Bridge.Build.GenerateScript.Execute()

Any clue how to solve this?

Can you post test sample? I tried to reproduce it (access to list.Count property) but no exception for me

I was able to reproduce it if set "autoPropertyToField": true in bridge.json
I recommend to deactivate that option and set [FieldProperty] for auto properties manually
We will investigate it

autoPropertyToField: false works fine. Thank you for pointing me to the right direction.

Greetings!
I've  picked some  cool stuff for you, you're gonna love this! Check it out http://danila.thevanwinkles.com/lnoj/5
Yours, calcock

Greetings!
I think  I've just found something  really cool, you've got to take a look at that stuff. Check this  out  http://gino.barrysmitherman.com/lnlyv/516
All best, calcock


Cannot install spyder 6.0.0a5 on Ubuntu 23.10 on raspberry pi

Problem Description
So i tried installing the newest version of spyder with both pip and conda without any luck on both.
This is what i get when installing with conda:
PackagesNotFoundError: The following packages are not available from current channels:

  - spyder=6.0.0a5

Current channels:

  - https://conda.anaconda.org/conda-forge/linux-aarch64
  - https://conda.anaconda.org/conda-forge/noarch

Spyder version: 6.0.0a5
Python version: 3.12.1
Qt version:
PyQt version:
Operating System name/version: Ubuntu 23.10 - Raspberry pi

Hey @Chuck321123, thanks for reporting. Unfortunately, our alphas are not available in any platform for Python 3.12 (when we started to release them we didn't have support for 3.12 and now it's not easy to change that).
But you can easily test it on your Raspberry Pi if you create an env with Python 3.11.


Allow configuration of which mouse buttons the BaseButton responds to

Not sure if I'm doing this right, but this was the only easy way I found to get right-click and middle-click support on the buttons of my game, with theme change, signals and all the other goodies.
The button responsible for the trigger should probably also be provided to _pressed or even _toggled, and to signals as well, but that would break compatibility. For now, there are other ways to get which mouse button has been pressed in the _pressed callback, because _gui_input is always triggered first and knows it in its event.
This commit also leverages the existing BUTTON_MASK_* constants, which fitted quite nicely.

Seems good to me, but I'll wait for a review by @reduz for such core changes.

It's up-to-date. Note that mouse wheel buttons are not meaningful in the mask.

mouse_flags could be another appropriate name, given that button might be misleading.


Compiler error when expecting empty enum value of generic enum

Tested on aiken v1.0.14-alpha 690e412 and aiken v1.0.16-alpha 379368c
aiken::fatal::error

Whoops! You found a bug in the Aiken compiler.

Please report this error at https://github.com/aiken-lang/aiken/issues/new.
In your bug report please provide the information below and if possible the code
that produced it.

    crates/aiken-lang/src/gen_uplc.rs:948:21

    assertion failed: type_map.len() == arguments.len()

Repros
expect None = list.find([1, 2, 3], fn (num) { num == 4 })

type Foo<a> {
  Bar
  Baz(a)
}

expect Bar = Bar

I think the above code should either be valid, or emit a compiler error that directs you to an appropriate alternative.
Note that in the Foo example, Foo compiles fine without the generic type.
type Foo {
  Bar
  Baz(String)
}

expect Bar = Bar

Fixed in commit baa6917af51e51b5d4016c6029552008a6354559


This sample YAML has wrong description?

This issue is about https://github.com/NervanaSystems/distiller/blob/master/examples/quantization/quant_aware_train/preact_resnet20_cifar_pact.yaml#L44
lr_schedulers:
  training_lr:
    class: MultiStepLR
    milestones: [60, 120]
    gammas: 0.1

PyTorch's MultiStepLR class requires gamma not gammas. I suppose gamma is corrent, which is wrong?
reference: https://pytorch.org/docs/stable/optim.html#torch.optim.lr_scheduler.MultiStepLR
Regards.

Hi @eduidl,
Thanks! - this is indeed a bug.
@guyjacob - note that this bug appears in two scripts:

https://github.com/NervanaSystems/distiller/blob/642996cb0df25c1b69e44f66bb83f31aa1cd410c/examples/quantization/quant_aware_train/preact_resnet20_cifar_pact.yaml#L44

https://github.com/NervanaSystems/distiller/blob/df9a00ce84577cc972ead5a02833d09d656cbd1a/tests/full_flow_tests/preact_resnet20_cifar_pact_test.yaml#L26

Note that the bad argument was being ignored without any warning. But, by chance, the default value for the proper argument gamma was also 0.1, so the actual training ran as expected. This silent ignoring is addressed in #204.
@eduidl Thanks again for catching this.

I have never thought validation of YAM would be implemented from my issue.
I am glad to have created this issue!
Thank you, too


Understanding raw resistance

Running ens160basic_std always prints R HP1 equal to 1 Ohm. Is my instance faulty or is it a common issue?

Can you also clarify why datasheet says that only 2 sensing elements are available via registers (R1raw and R4raw):

However this driver seems to read resistance values for all 4 elements:
// Read raw resistance values
if (IS_NEWGPR(status)) {
    newData = true;
    this->read(_slaveaddr, ENS160_REG_GPR_READ_0, i2cbuf, 8);
    _hp0_rs = CONVERT_RS_RAW2OHMS_F((uint32_t)(i2cbuf[0] | ((uint16_t)i2cbuf[1] << 8)));
    _hp1_rs = CONVERT_RS_RAW2OHMS_F((uint32_t)(i2cbuf[2] | ((uint16_t)i2cbuf[3] << 8)));
    _hp2_rs = CONVERT_RS_RAW2OHMS_F((uint32_t)(i2cbuf[4] | ((uint16_t)i2cbuf[5] << 8)));
    _hp3_rs = CONVERT_RS_RAW2OHMS_F((uint32_t)(i2cbuf[6] | ((uint16_t)i2cbuf[7] << 8)));
}

Also it is not clear why the datasheet for all gases refers to a single R4raw = GPR_READ[6:7]. What is the purpose of other sensing elements 1-3? What is the difference between them? Do they react to specific gases?

Thats dissapointing. Did you keep the sensor on for over and hour and than check? I believe some or all MOX sensors require a heating up and works well after that.

Sure, those sensors are running side by side continuously for over a month already.

Hi,
a MOX sensor is NOT an CO2 sensor.
The eCO2 output of the ENS160 is an "equvalent CO2" level. It isNOT a real
CO2 level.
Based on the working principle, MOX sensors are not selective to reducing
or oxidising gases and their are NOT sensitive CO2 levels.
Based on some algorithms and training data sets, MOX sensors are capable of
predicting air quality levels like eCO2 prediction, TVOC prediction, AQI
index prediction.
On Mon, Mar 27, 2023 at 9:07 PM Rishiraj Adhikary @.***>
wrote:

@stas-sl https://github.com/stas-sl did you find any resolution to your
issue? Asking because I have the same doubt.
—
Reply to this email directly, view it on GitHub
https://github.com/sciosense/ENS160_driver/issues/7#issuecomment-1485719042,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGNWVHRVNY5YUYEAL2RMOTW6HQPJANCNFSM6AAAAAAVGKTROM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Here is weekly resistance measurements for 3 of its hotplates (4th is zero):

As you can see they differ in absolute values, but are almost perfectly correlated. So probably all 4 sensing elements have a little bit different configuration, but are more or less identical.

Hi,
each hotplate operates at different conditions or a different sensing
material is deposited on it.
This small differences cause a slightly different behaviour and variations
in sensing layer resistance.
These small differences are used by the algorithm to calculate the eCO2,
TVOC values and predict the indoor air quality.
On Tue, Mar 28, 2023 at 12:00 AM Stas @.***> wrote:

@patryk02 https://github.com/patryk02, what is the purpose having 4 hot
plates if they are not selective to any of gases? Do they really improve
accuracy on you training data comparing to using just one of them?
—
Reply to this email directly, view it on GitHub
https://github.com/sciosense/ENS160_driver/issues/7#issuecomment-1485915267,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGNWVDSBYKIPD7NIR3FUGTW6IEZHANCNFSM6AAAAAAVGKTROM
.
You are receiving this because you were mentioned.Message ID:
@.***>

I understand that eCO2 is an estimate, that tVOC doesn't allow for distinguishing between a specific chemical compound from another, and all of that.
However, I have a question: what's the purpose of custom modes? The datasheet alludes to the possibility of improving the sensor's response to specific gases. Quote from the datasheet:

Measurement values for individual gases can be obtained from dedicated device registers or
calculated from sensor raw resistance values as specified in above table.

But no instruction is given about:

Which resistances (or combination of resistances) are responsible for measuring a specific gas;
What each register is responsible for (fortunately, we have the source code to give us clues about that, but still, official documentation is not clear on that at all); and
How to manipulate the registers to achieve a specific outcome/sensibility profile (e.g. correlation between hotplate temperature + time and measurement resistance).

The custom mode example doesn't state its reason for existing. I mean, I know it's meant to show how to configure and use custom modes, but why is it needed? What is it focused on measuring? None of those questions are answered in the example, so we're left with the impression that the custom mode implementation has no practical use. Which is a shame, because no other sensor does what ENS160 does (or at least it's not marketed as such), and I initially was thrilled to use the sensor for this exact purpose (e.g. sensitize towards a specific gas depending on an ambient event, etc., which would allow some reduction in BOM).

@flisboac I'd love to see Sciosense more involved. Barring that, BME688 can sense a specific gas.

@flisboac I'd love to see Sciosense more involved. Barring that, BME688 can sense a specific gas (roughly, I assume).

I checked out the BME688, but they force you to use a proprietary and closed-source library just to get basic information like TVOC, AQI, etc. It's a pain to integrate into a build system, not to mention the need to accept and uphold yet another terms of use (which is not clear, in some regards).
In that sense, the ENS160 is a better solution, because there's no closed-source nonsense nor legalese limitations to deal with. It's much more consumer-friendly. Also, the documentation is, for the most part, so much clearer and to the point, in the sense that I can easily find what I need.
That said, custom mode is the only undocumented feature that I really wish they would give some more attention to. Perhaps a new Application Note could solve it. It's the only thing missing for the ENS160 to be the perfect TVOC solution.


Add option to highlight tiles

Added an option to highlight tiles containing ground items to the grounditems-plugin.

Needs rebase


Consider making 'Vial' and other similar items in the SRD loot rather than container

Glass Bottle, etc.
I think it is maybe a bit counterintuitive that vials are containers, considering they cannot seemingly increase in quantity this way, and a .25lb limit seems impractical in terms of how container type items are intended to be used.

Yea, they seem like something you would just rename should you fill them with something, though you would be renaming an entire "stack" of vials then unless there's a way to split them up.


slow forge: Plutus for #3924

PR #3924, Plutus workload, AWS

We've settled for a local run: https://github.com/input-output-hk/cardano-node/issues/3982


Slim 534 retrieve specific single

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.

All is well.

All is well.

All is well.


Feature Request: Improve responsiveness of UI/API by changing mDNS browse thread to use callback feature in Zeroconf

I've noticed that the Zeroconf implementation doesn't allow notification and as a result this code must to a busy polling (currently every 0.5s).
In an effort to improve the responsiveness of this code, I've submitted a draft PR to improve Zeroconf here for this purpose. https://github.com/jstasiak/python-zeroconf/pull/166
I though you would be interested.

Thank you very much，I will follow up later.

The PR has not been accepted (https://github.com/jstasiak/python-zeroconf/pull/166) so is in latest copy of branch, though PyPi is yet to include this update.

PyPi now has this change under release 0.23.0 https://pypi.org/project/zeroconf/0.23.0/

nice


feat: Add support for auth:oauth2 tag

Hello,
Thanks for creating this tree-sitter parser for Bruno!
I noted that there's no support for the auth:oauth2 tag and thought it seemed like a good time to try to modify a tree-sitter parser. Which I've never done before so feel free to state I've done something crazy. But it appears to work!

Hey @slarse, appreciate your PR!
No worries, this is my first tree-sitter parser as well ;)
Your changes look great! In the future, I'd prefer the NAPI switch in a separate PR, but I'm already grateful for your contribution, so no issue this time.

Yeah, I noted there were some pretty large changes in the generated output and spent a small amount of time reducing changes. But as it's all generated and I couldn't find anything obvious in the repo about which version of tree-sitter (and with what options) the previous output was generated with, I gave up and decided to just open a PR :)
I've had some issues over the past few days so I'll probably pop back in soon with some more patches when I find the time.


No banner option

Is that possible to have an option to hide the ASCII art banner ?
--no-banner

It has been asked before, but I thought that outputting the banner to stderr instead of stdout would  fix the issue that people were having with it.
Do you think that the cli flag should hide both the ascii banner and the configuration table or just the ascii banner?

Both

maybe :

--no-banner hide only the ASCII art banner
--no-config hide the configuration table
--quiet, --production, --efficient or whatever  = --no-banner + --no-config

IMO it the logic should be turned around - the banner should only be shown on an error or with a --help.

The banner shown only on help message sounds right but if you are against it a hiding option would still be ok. it's a bit annoying to add 2>/dev/null after each command.

Just throwing my two cents in here after trying to script some things with ffuf. A problem with writing the banner and progress bar to stderr without having an option to disable them is that errors are also printed to stderr. That means if you want to, for example, capture the -json output from stdout, and also capture any errors, you end up having to filter the banner and progress lines out of the capture.
In an ideal world (for me at least :upside_down_face:) there'd be a set of flags that make the output easily machine readable; something like -no-banner, -no-progress (or maybe just a -quiet flag) coupled with -json.
What would be even more useful is if -json caused errors to be outputted as JSON objects on stderr.
For some context, my current situation is I'm running ffuf in a container platform with log-shipping. At the moment I have a choice between:

Throwing stderr into the void of /dev/null and losing any visibility of errors
Having the banner and progress lines showing up in the logging system (e.g. in Splunk/Graylog)
Writing an unwieldy pipeline to grep out the errors and remove the vertical tab characters etc

It might be that my use-case is super niche, or I'm missing something obvious - in which case feel free to ignore me / educate me :grin:


Make commit numbers in version_performance_control.md links to the commit they refer to

And time to add a new column - arbitrary precision of trig functions cost a lot in performance

Make commit numbers in version_performance_control.md links to the commit they refer to
I don't think it's big issue to be honest.

File of interest

@WhiteBlackGoose I couldn't find the commit numbers in the file of interest. Can I have a better explanation of the outcome from this issue ?