Rviz crashes when visualization marker contains nan in values

Describe your issue here and explain how to reproduce it.
Local_Planner_SITL-Land-Rviz-kill.zip
Playback uploaded rosbag file
then set fixed frame to local_origin and visualize /path_waypoint topic (type - visualization::Marker) alone.
When it contains nan in the points value,
Rviz crashes with following message
rviz: /build/ogre-1.9-B6QkmW/ogre-1.9-1.9.0+dfsg1/OgreMain/include/OgreAxisAlignedBox.h:252: void Ogre::AxisAlignedBox::setExtents(const Ogre::Vector3&, const Ogre::Vector3&): Assertion `(min.x <= max.x && min.y <= max.y && min.z <= max.z) && "The minimum corner of the box must be less than or equal to maximum corner"' failed.
Aborted (core dumped)

where the topic contents are
---
header:
  seq: 387
  stamp:
    secs: 39
    nsecs: 464000000
  frame_id: "local_origin"
ns: ''
id: 387
type: 4
action: 0
pose:
  position:
    x: 0.0
    y: 0.0
    z: 0.0
  orientation:
    x: 0.0
    y: 0.0
    z: 0.0
    w: 1.0
scale:
  x: 0.02
  y: 0.0
  z: 0.0
color:
  r: 1.0
  g: 0.0
  b: 0.0
  a: 1.0
lifetime:
  secs: 0
  nsecs:         0
frame_locked: False
points:
  -
    x: -0.0114045487717
    y: -0.039681263268
    z: nan
  -
    x: -0.0114045487717
    y: -0.039681263268
    z: nan
colors: []
text: ''
mesh_resource: ''
mesh_use_embedded_materials: False
---

Your environment

OS Version: Ubuntu 18.04
ROS Distro: Melodic
RViz, Qt, OGRE, OpenGl version as printed by rviz:[ INFO] [1571970533.066781595]: rviz version 1.13.5
[ INFO] [1571970533.066812126]: compiled against Qt version 5.9.5
[ INFO] [1571970533.066817226]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1571970533.074023763]: Forcing OpenGl version 0.
[ INFO] [1571970533.657846107]: Stereo is NOT SUPPORTED
[ INFO] [1571970533.657907318]: OpenGl version: 4.6 (GLSL 4.6).

If source build, which git commit?
commit e49a5448f2a763dcba2963a7e87e627b6db6d1b6

It's interesting that a lot of similar issues (with malformed messages) popped up recently.
I filed a fix in #1440. Could you please verify this for your use case?

@rhaschke It is working, I'm getting warning messages instead of rviz crash
[ WARN] [1572019736.235473679,<PHONE_NUMBER>00]: Marker '/1458': invalid point[0] (-0.03, -0.14, nan)
[ WARN] [1572019736.235518609,<PHONE_NUMBER>00]: Marker '/1458': invalid point[1] (-0.03, -0.14, nan)
[ WARN] [1572019736.332717967,<PHONE_NUMBER>00]: Marker '/1459': invalid point[0] (-0.03, -0.14, nan)
[ WARN] [1572019736.332755887,<PHONE_NUMBER>00]: Marker '/1459': invalid point[1] (-0.03, -0.14, nan)
[ WARN] [1572019736.428963777,<PHONE_NUMBER>00]: Marker '/1460': invalid point[0] (-0.03, -0.14, nan)
[ WARN] [1572019736.429001977,<PHONE_NUMBER>00]: Marker '/1460': invalid point[1] (-0.03, -0.14, nan)
[ WARN] [1572019736.523704624,<PHONE_NUMBER>00]: Marker '/1461': invalid point[0] (-0.03, -0.14, nan)
[ WARN] [1572019736.523748744,<PHONE_NUMBER>00]: Marker '/1461': invalid point[1] (-0.03, -0.14, nan)
[ WARN] [1572019736.619853312,<PHONE_NUMBER>00]: Marker '/1462': invalid point[0] (-0.03, -0.14, nan)
[ WARN] [1572019736.619893252,<PHONE_NUMBER>00]: Marker '/1462': invalid point[1] (-0.03, -0.14, nan)


The select component pops up with the phone touch screen the selection line cannot disappear automatically after selection

Bug type
Component
Component name
select
What happened?
Select component pops up on the phone touch screen, and cannot automatically disappear in 6.0.7 after selection
Expected behavior
Want to disappear automatically after selecting, this is valid in 6.0.6
Reproduction link
https://try.mudblazor.com/snippet/rY_BDgFBDIbvXkLTExdewIiICImNhA1HKdswUV2ZnUnw9GZjcVnhoKf-6dfm62aTkNWOo1vumr0kZEsW3nmYsJzZpXzxBh89-BgQUoOFd1b3CDPashhcW3-oeIQVOUsal6qmU57AfgNivc9PPZ8iKoENDlqYXh2p5gUFh22E7hc8sUeGBV8qttd9gTG8XxjZgrbCmUHvAteZP4ka7XnwYjWO_qs-Yc31B_cFUzZXuX52LwkokRr5sRX5u_qQI_xB_Q4
Reproduction steps

...
Relevant log output
No response
Version (bug)
6.0.7
Version (working)
6.0.6
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Android
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think this issue solved with last dev version. If it still occurs after new version, please re-open it.


Advised as per @nathanhammond.
I was using master in an attempt to extract out some common logic in my parent application into an in-repo engine, followed the guide in the README, and got stuck on the error: Asset manifest does not list any available bundles in asset-loader#loadBundle.

Unsure if this is exactly the issue, but seems like something we should figure out.

Mentioned this briefly in slack, but this error actually seems to be happening because we hit this code path for lazy engines even when the Engine isn't being lazy. Will need a reproduction in order to investigate further.
That said, we likely should run any of the asset-manifest stuff as an optimization if it is just going to be empty anyway.

Just ran into this with our application, so I'll dive into it.

So after looking into it, turns out the issue was not having the right version of ember-resolver 😆 . Just make sure you have version ^2.1.0.
Anyway, do we want to keep this issue open to address optimizing the asset manifest generator work?

I think we should open a different issue for that. They're free.


README and/or INSTALL file

There is not readme or installation documentation in the repository. There is a readme which is only relevant to the nette framework.

I added a skeleton of readme. Please, feel free to modify it.


need better history recall (a la matlab or csh)

add numbered prompts
then enable matlab / csh like history syntax to recall & execute code

eg:
http://tomecat.com/jeffy/tttt/cshhistory.html

reopened.

#3019


Revisit camel-quarkus bootstrap

After thinking a little bit more about supporting Quarkus Command Mode  I think we should revisit the way we do bootstrap camel-quarkus (naming is purely indicative):

embedded (core)

routes are added to the camel context directly
context need to be programmatically configured

main

routes and configuration classes are managed by camel-main
support for command line
support for configuration through properties

static (aka lightweight)

routes are added to the camel context directly
some limitation may happen
context need to be programmatically configured

We can then provide main and static behaviour through extensions so depending of the end user need we may achieve different optimization or behaviours without cluttering the code too much.

embedded (core)

routes are added to the camel context directly

... by the user

context need to be programmatically configured

... by the user

main

routes and configuration classes are managed by camel-main
support for command line
support for configuration through properties

static (aka lightweight)

routes are added to the camel context directly

By whom?

some limitation may happen
context need to be programmatically configured

... by the user? Which aspects of the context for example?

We can then provide main and static behaviour through extensions so depending of the end user need we may achieve different optimization or behaviours without cluttering the code too much.

My standpoint is the same as in the past when we were introducing the main: If 80+% of Camel Quarkus users will be supposed to add dependency X, then the dependency should be present by default and the users do not need to know about the fine tuning unless they know what they do. Requiring a decision from the end users will cause unnecessary cognitive load and confusion.
Having said that I vote for configuring core vs. main via application.properties rather than via dependencies.
My very naive initial attitude to main vs. static is that we should have only one of them, probably only static. "some limitation may happen" could be presented as limitations of Camel Quarkus rather than a limitation of the single "static" mode. If ppl. need more flexibility they should be advised to choose another Camel platform.

I think you get this wrong as my proposal is to revisit the boostrap in general so if you don't have main as extension, then camel will still start the camel context and will still auto discovery routes as it does today, what it will lacks is some bits that are supported by camel main which you cna leverage by adding the main extension.
static initit cane become the default only if it does not break other runtimes i.e. camel-k so I'd say the default should be what would for for the majority and you should opt for the static and more optimized options if you are conscious about what you are doing.

I think you get this wrong as my proposal

Could you please edit your proposal and clearly split

Current state
Problems with the current state
Proposed state
Pros/cons of the proposed state

@ppalaga updated the issue

provide a default "bootstrap item" that start the camel context
So this is the same as the CamelMain.start() currently ?

User that need specific component/context configuration can use CDI (we probably need to support the concept of customizer with CDI beans).
How can we support this customizer with CDI beans ? provide the BeanConfigurationBuildItem in the user's application code ?

I just introduce the quarkus.camel.bootstrap.enabled option and the user can disable the bootstrap in the extension and will do the configuration and boot the camel context by themselves. Do you think it make sense ? or we have to provide the mandatory default bootstrap ?

provide a default "bootstrap item" that start the camel context

So this is the same as the CamelMain.start() currently ?

Except it does not use camel-main

User that need specific component/context configuration can use CDI (we probably need to support the concept of customizer with CDI beans).

mh, probably we don't need it as we fire CDI events so one can listen and react to them.

How can we support this customizer with CDI beans ? provide the BeanConfigurationBuildItem in the user's application code ?
I just introduce the quarkus.camel.bootstrap.enabled option and the user can disable the bootstrap in the extension and will do the configuration and boot the camel context by themselves. Do you think it make sense ? or we have to provide the mandatory default bootstrap ?

The default bootstrapper should be marked as optional so developers can provide an alternative one if they want a custom boostrap logic

`mh, probably we don't need it as we fire CDI events so one can listen and react to them.

This looks like to add a similar CdiEventNotifier in camel context during the building time ?

yeah, something like that but we need to think a little about it

Thanks for the update, @lburgazzoli , it makes much more sense to me now.
Could you please confirm/deny/explain the following?

According to your proposal, our non-core extensions will depend on camel-quarkus-core (rather than camel-quarkus-main), right?

Our existing itests should in theory either (a) work with the proposed changes as long as they do not use camel.* properties or (b) work with the proposed changes if the camel-quarkus-main dependency is added.

Which of the three options ("core only", "main", "main-static") is the one that will meet the needs of 80% of users?

Can we make core-deployment smart enough to decide whether main or main-static is needed and add one of those as necessary?

According to your proposal, our non-core extensions will depend on camel-quarkus-core (rather than camel-quarkus-main), right?

correct

Our existing itests should in theory either (a) work with the proposed changes as long as they do not use camel.* properties or (b) work with the proposed changes if the camel-quarkus-main dependency is added.

correct

Which of the three options ("core only", "main", "main-static") is the one that will meet the needs of 80% of users?

this is very hard to answer as there's many way to use camel, using main to create a standalone camel application is certainly one option but you can also use some little camel from smallrye-reactive-messaging or when you need some small integration capabilities in your application.
I think that nowadays it is likely common to require some integration capabilities so I believe having a core that helps setting up things but give you freedom to i.e. provide your own main is the most sensible choice we can make.

Can we make core-deployment smart enough to decide whether main or main-static is needed and add one of those as necessary?

I think there have been some discussion on quarkus side to have a way to add additional artefacts depending on some conditions but I'd rather start with something simple and less magic and see how it goes.

@ppalaga are the info here good enough to start working on the implementation ?

One more question: main-static will have no support for the camel.* properties?

Additional note, there is an issue about move component auto configuration as part of standard component life-cycle which would make revisiting the bootstrap process even more appealing as configuring components/languages/etc with be available out of the box with less overhead

@lburgazzoli is there any update on this issue ?

I'm workign on a big refactor :)


[Proposal] Use web app manifest as single source of truth

Currently, developers when packaging PWA to TWA should duplicate web app manifest properties in build.gradle file, that has a different format.
What about using manifest.webmanifest file as single source of truth and generate build.gradle from it? This should improve the DX (Developer Experience).

This is something we considered previously. The bottom line was that the fields cannot be used straight from the Web Manifest, and use the same format.
As an example, while a Web Manifest accepts red or blue to specify a background_color, Android will require the color to be specified as #FF0000 or #0000FF.
Having said that, we are looking into how we can generate an Android Project from a Web Manifest, without having to mess around with build.gradle. I'll update this issue when this moves forward.

@andreban Just found https://github.com/GoogleChromeLabs/llama-pack. ;)

That's the project I mentioned above. It's a work in progress, but it is public now. Issues and PRs are welcome!

I created an issue on llama-pack to discuss this: https://github.com/GoogleChromeLabs/llama-pack/issues/11

:tada:


"react-native.cmd start --port" doesn't affect "adb reverse" port

Description
When using "react-native.cmd start --port X" it still calls "adb reverse" with port 8081..
Additional Information

React Native version: 0.39
Platform: Android
Operating System: Windows

Pull request welcome!


Download entry contents for offline use

Maybe I have overlooked a configuration option but the feeds are scanned only for entry names - without downloading the contents. This may be fine for always-online 3G devices but is not useful for WiFi-only devices which are often used offline (subway, train). Could you please add such option to the feed management?
Flym has an option to read the contents upon synchronization.
Munch 0.42 from F-Droid

You can sync the feeds from the context menu and it will save all of the feeds with their respective articles offline.


cortanavcds crashes in any other locale then en-US

TripStore.cs parses date using US format, but still uses default locale.
Parse the date using US locale:  DateTime.Parse("05/05/2015", new CultureInfo("en-US"))

Hey, With the update to the master branch a few days ago, this issue should be resolved. Date handling has been adjusted to initialize without using parsing, and date handling within the xml file has been improved to be locale agnostic. (You may want to uninstall and reinstall the app in case an older data file is left over, i didn't implement any upgrade code).
Date entry in the UI should use your own locale for converting dates (ie, if your region customarily uses YYYY-MM-DD, that should work) and it should use your locale's date formatting when providing text to cortana.

Great, thanks.


Update SessionManager.php

Redundancy

This repo is read only please close this. Also, laravel is not accepting pull requests of this nature.


Drop 3.8 support, fix admap1 url

drop support for python 3.8
fix admap url
add back fetch tests


Add shell commands ui

Is the IndexView even being used right now since the UI is deployed separately and these shell commands coming from the deploy config for that?

@kwm4385 we might not be using it for our special static build, but in general (i.e. other Singularity users), IndexView is in use

:+1:

@wsorenson Since Eric is going to be doing work on shell commands, it would make sense for us to merge these UI components into the main branch. Sound good?

Can now redirect to the output file when a command launches.

@kwm4385 Can we just completely hide the options stuff if you've selected a command that doesn't define any?

We should also make sure to only show this if a task is running under the Singularity executor.

I assumed the field we are looking at to determine if the task is running on the singularity executor is data.task.taskRequest.deploy.customExecutorCmd being something like /usr/local/bin/singularity-executor. Let me know if this isn't the case.

(merged into #515)


Build failures

Tried to deploy a create-react-app on amplify, but it seemed amplify did not build the artefacts successfully due to 'build' folder nonexistence. But I had npm run build in the script.
My project structure:

Script:

Error:

Where did I make mistakes?

Hi 👋, thanks for opening! While we look into this...
If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.
Lastly, please make sure you've specified the App ID and Region in the issue!

Hi, there.
What is

Hi 👋, thanks for opening! While we look into this...
If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.
Lastly, please make sure you've specified the App ID and Region in the issue!

Hi, there. I don't think your reply is regarding my question since there seems nothing related to domains.  Also, what is App ID and where can I find it?

Hello, you can find your appId by going to your amplify apps selecting the specific app giving you issues, then going to general on the left side. There you should see an appArn on the center-left side of the screen. The appId is after apps/

I was able to find your appId in the logs.  Seems like the error is that you've accidentally set your baseDirectory to .frontend/build instead of frontend/build in your amplify.yml.  You don't have a folder named .frontend but do have one named frontend.


Issue with Enum-type attributes randomization

Hello,
I'm trying to randomize an enum-type attribute (it's been mentioned in the manual that Enum and IntEnum are supported by PyVSC). When I try this example from the manual:
class my_e(Enum):
  A = auto()
  B = auto()

@vsc.randobj
class my_s(object):

    def __init__(self):
        self.a = vsc.rand_enum_t(my_e)
        self.b = vsc.enum_t(my_e)
inst = my_s()

Then this error happens in the last line: TypeError: int() argument must be a string, a bytes-like object or a number, not 'my_e'.
However, with IntEnum (instead of Enum), it works but seems like doesn't actually do the randomization, below code doesn't randomize the enum (inst.a), but it does randomize the uint8 attribute:
from enum import *
import vsc

class my_e(IntEnum):
  A = auto()
  B = auto()

@vsc.randobj
class my_s(object):

    def __init__(self):
        self.a = vsc.rand_enum_t(my_e)
        self.b = vsc.enum_t(my_e)
        self.c = vsc.rand_uint8_t()
inst = my_s()
inst.randomize()
print('{}{}{}'.format(inst.a, inst.b, inst.c))

I think I'm missing something here... Could someone please explain this behavior?
Thanks,
Hodjat

Hi Hodjat,
Thank you for pointing this out. There actually was an issue with support of plain (non-IntEnum) enumerated types. Also, enumerated types in general were not being properly biased for randomization, and the distribution was off. I've corrected both of these issues with a9d7d1a. I also created PyPi release 0.0.3 from this.
Thanks again for the report and testcase!
Best Regards,
Matthew

Thank you Matthew.


Specified --control-plane-machine-count=3 but only one master node was created

The rendered yaml show that the replicas of KubeadmControlPlane is 3. But only 1 machine and 1 ibmvpcmachine were created.

The same issue opened for cluster-api and we have the same log error in the pod capi-kubeadm-control-plane-controller-manager
https://github.com/kubernetes-sigs/cluster-api/issues/4027

The same issue opened for cluster-api and we have the same log error in the pod capi-kubeadm-control-plane-controller-manager
https://github.com/kubernetes-sigs/cluster-api/issues/4027


Bug 1905640: fix(e2e): Fix subscription manual approval flaky test

The current Subscription manual approve e2e test has an extra Apply
code that needs to the InstallPlan being updated twice by accident.
This causes the test case to be flaky.
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/approve
/lgtm

/cherry-pick release-4.6

/bugzilla refresh

/retest


error in ekf.cpp

Hi
I've read the code and it seems like I've found a bug in the velocity calculations at
lines 361-362:
https://github.com/PX4/ecl/blob/337cdcc59a2df1f5e395c4c27d69748227e90bbd/EKF/ekf.cpp#L361-L362
but _state.vel in Earth frame. I  think you should rotate gravity vector and compensate from full velocity vector.

Hi @asoharev ,
The rest of the state velocity vector is compensated here https://github.com/PX4/ecl/blob/337cdcc59a2df1f5e395c4c27d69748227e90bbd/EKF/ekf.cpp#L359 using rotated acceleration (https://github.com/PX4/ecl/blob/337cdcc59a2df1f5e395c4c27d69748227e90bbd/EKF/ekf.cpp#L350).
Then the gravity is removed: _state.vel(2) is in earth frame, as well as _gravity_mss (1g constant). I don't see where the mistake is.

I'm sorry, my fault. I understand, EF = NED.
Before I'd met earth frame as ECEF only (https://en.wikipedia.org/wiki/ECEF) and thought that's generally accepted.
Thanks for your  answer!

@asoharev No problem, I agree that it could be quite confusing, I understand why you thought it was wrong then :)


What IDE/tool is used to develop the Azure Maps Code Samples?

This issue is for a: (mark with an x)
- [ ] bug report
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

Information on IDE/tool used to develop the Azure Maps Code Samples provided in this repo.
For example, how was the single page application interactiveSearch.html (under Tutorials) developed?
Is it possible to use Visual Studio 2019, and if so how?
Is it possible to use VS Code, and if so, what extensions?

OS, Browser and Version?

Windows 10 2004
Firefox

Mention any other details that might be useful
Thank you.

The full code sample site was created in Visual Studio 2019, but mainly because of the one click option to deploy to Azure. You don't need anything fancy to create HTML pages. In fact, open up notepad on your computer, copy in the source code to the interactiveSearch.html file and save the file with an "html" extension. Then double click on the file to open it in a browser and you will see that app running.
Visual Studio code is a good option if you are looking for an IDE. If you are looking for something basic and don't need deployment and other automation tools, try out Notepad++. Its a great light weight editor that's fast. I use it all the time to manipulate data files.

Rick, thank you for your response.  I in fact have that sample running successfully, with my own subscription ID.
My question rather is how that HTML page was created.  You mention it was created using VS 2019.  What project type was used?
I see an AzureMapsCodeSamples.csproj file in the repo, but given that the sample is an HTML file, I am not sure that is the correct item.  I am well versed in VS and C#, but not in creating HTML/JS apps.
Thank you again.  Regards.

The code sample project is a VS2019 solution. I used the "ASP.NET Web Application" project template for the whole site. For html pages, they are simple flat files. Simply add ".html" to a file. I f you look through the file types when adding a new file, there should be a html file template which is really basic. Here is a video: https://www.youtube.com/watch?v=PgqqTXbseRM

OK, got it, thank you so much.  Regards.


Updating debug package to fix security fix for NPM Audit

https://www.npmjs.com/advisories/534

Duplicate of #256


[1.11.2-0.14.1] Lots of recipe errors at startup

Do I need to be worried about these?
https://gist.github.com/kreezxil/97234f7de4943fb4ae674552225691aa#file-fml-client-latest-L2889-L4394

seems something went wrong with the JEI versions as I compiled against a different version, you should be fine it just means you wont be able to view JEI recipes right now with some of my machines.

Ah hang on a second, i didnt finish reading the log when I sent that, did the game crash?

... I once again didn't finish reading before I sent that message aswell, your crash was due to com.raoulvdberge.refinedstorage.apiimpl.network.node.NetworkNodeGrid.onCraftingMatrixChanged(NetworkNodeGrid.java:207) so refined storage was the issue in this case.

 You reclose this as I just wanted to respond. :)

github automatically closed it ;)

But yea, i'm uploading a build right now to fix the errors.


[feaLib] inline lookup is not exported

Consider the following feature file:
@FIGURES_DEFAULT = [zero one two three four five six seven eight nine];
@FIGURES_INFERIOR = [zero.subs one.subs two.subs three.subs four.subs five.subs six.subs seven.subs eight.subs nine.subs];

feature subs {
    lookup INFERIOR {
        sub @FIGURES_DEFAULT by @FIGURES_INFERIOR;
    } INFERIOR;
} subs;

feature sinf {
    lookup INFERIOR;
} sinf;

I get the error: Unknown lookup INFERIOR which seems to suggest that feaLib doesn't export lookups defined inside a feature for use elsewhere.
cc @brawer

I believe that's not an issue. If a lookup is meant to be used by more than one feature, then you should move it outside of the scope of features and make it stand-alone.
If makeotf does it otherwise, maybe it's wrong...

well, if makeotf does that way, I guess we should also do it that way (despite for me it's counterintuitive, as it would make things clearer to define that as standalone lookup)

Such syntax is used in feature files of Adobe's open-source fonts, e.g.here.

@anthrotype writing a feature as
feature abcd {
    lookup ABCD {
        sub a by a.alt;
    } ABCD;
} abcd;

is not less valid than writing it as
feature abcd {
    sub a by a.alt;
} abcd;

The former actually makes more explicit what goes on behind the scenes.

of course. I meant for clarity's sake, if that lookup ABCD is also used elsewhere, then it would be better defined outside the scope of feature abcd.

I mean
lookup ABCD {
    sub a by a.alt;
} ABCD;

feature abcd {
   lookup ABCD;
} abcd;

feature efgh {
   lookup ABCD;
} efgh;

instead of
feature abcd {
   	lookup ABCD {
        sub a by a.alt;
    } ABCD;
} abcd;

feature efgh {
   lookup ABCD;
} efgh;

anyway, mine is simply a stylistic concern. The issue as reported by @adrientetar remains that feaLib should handle these named lookups defined within the scope of a feature block the same way that makeotf does (i.e. "scope-less").

Agree. Working on a fix.

By the way, the spec is silent about scoping; see https://github.com/adobe-type-tools/afdko/issues/98.

Up until AFDKO 1.5 or so, it was ONLY possible to define a lookup INSIDE a feature block, and then refer to such lookups in subsequent features. So from the very beginning, the lookup keyword had only the global scope.
I proposed that AFDKO adds the ability to define lookups outside of feature blocks because that method gave better clarity over the order of lookups, which is relevant. The original method obscured it a bit.
But in both methods (which can be mixed), the scope is global, and should be treated as such.
There are TONS of existing sources which have definitions like this:
feature ss01 {
lookup ss01 {
sub a by b;
} ss01;
} ss01;
feature salt {
lookup ss01;
} salt;
and feaLib should treat them the same as:
lookup ss01 {
sub a by b;
} ss01;
feature ss01 {
lookup ss01;
} ss01;
feature salt {
lookup ss01;
} salt;
Note that only the first example is valid FEA from AFDKO 1.0 oneards. The 2nd example is only valid in AFDKO 1.6+ or so, but there are many many source fonts that only use the 1st type of syntax.

Yes, I think that's what's implemented now.

Thanks, I just wanted to clarify that the global scope of lookup names is by design, not by accident. I believe that class or markclass names are also global in scope.
I do agree though that the FEA spec could be more clear about this.


Breaking stripped logs into firewood produces firewood and the stripped log

As per title. If a log is stripped using an Adze and broken into firewood with an axe, the broken log will drop firewood and the log itself

I think this was an unexpected interaction between AT and a mod that removes the firewood crafting recipe and forces it as an in-world interaction between an axe and a piece of stripped log. I believe this issue can be closed


Badge property and Map Control not working on Android

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
badge,
After updation of flet==0.25.dev3717 the badge property is added to every controls and i tried it .it works fine on Windows but,It was not working on Android
Map,
The map Control works fine on both windows and android before updating flet==0.25.0.dev3717.but after update its only work on Windows not on Android
Code sample
Code
[Paste your code here]

To reproduce
1.Fix the badge property to work on Android
2.Fix the Map to work on Android
Expected behavior
Badge and map wants to work on Android properly
Screenshots / Videos

Captures
[Upload media here]

Operating System
Windows
Operating system details
windows 11
Flet version
0.25.0.dev3717
Regression
Yes, it used to work in a previous Flet version (please specify the version in additional details)
Suggestions
No response
Logs
Logs
[Paste your logs here]

Additional details
It works on flet==0.24.1

Can you share your requirements file?
Make sure you set the right Flet version in it.

@ndonkoHenri
flet==0.25.0.dev3717
websockets==14.0
requests==2.32.3
pytz==2024.2
this is my requirements.txt

@ndonkoHenri
Not only badge , the map Control also not working as we expected on Android

Hello Siva-Rajan-R,
I have the same problem with map on Android.
The app works correctly on Linux and web, but nothing is displayed on Android (map frame always gray).
Have you found a solution ?
I have no requirements.txt , do you think I need to add websockets==14.0 or requests==2.32.3 or other ...
or any permission ?
Thanks,
JC

@JCxOx
You don't need to add the websockets==14.0 or requests==2.32.3 or other It was an bug on packaging the flet team will resolve it as soon as possible. We need to wait for it🙂 and also don't forgot to add flet build apk --include-packages flet_map while building an apk , in future.

Hello Siva-Rajan-R,
Thanks for the advices, I am not familiar with specific Android setting.
I will wait for the new flet version.
JC

Please retry with the new flet v0.25.0.
It should be fixed now.

Hello ndonkoHenri,
I have updated the new version (with $ pip install flet)
Now my flet version is 0.25.0   (no more 0.25.0.dev3750)
But unfortunatly nothing works !
Even the desktop version has an error : AttributeError: module 'flet.map' has no attribute 'MapConfiguration'
Maybe I didn't update flet correctly...
Thanks,
JC

Hello,
After removing the map.MapConfiguration( ... )  line, I put the initial_center=    and   initial_zoom= outside and that works on the desktop computer (linux).
But the Android is still not working.
I build the APK with the following command : flet build apk --include-packages flet_map
The building process is OK : Successfully built your .apk for Android! ....
But on my Android phone, there is many error :
Traceback (most recent call last):
File "", line 47, in
File "", line 222, in run_module
File "", line 142, in _get_module_details
ImportError: No module named main
With the previous flet version (0.25.0.dev3750) that was Ok, no error ... but no map ...
Thanks for your help,
JC

Should be fixed now. Please re-build the app.

Hello,
I have updated flet with :$ pip install flet --force-reinstall
and re-built the App :$ flet build apk --include-packages flet_map
but the same error appears :
Traceback (most recent call last):
File "", line 47, in
File "", line 222, in run_module
File "", line 142, in _get_module_details
ImportError: No module named main

I will suggest you create a new venv and install Flet from scratch, making sure to modify the flet version in your requirements/pyproject file to the latest equally.

Ok thanks, I will try asap,


API Endpoint "keys" delete method not allowed (405)

Expected Behavior
documentation for the 'knife exec' states that using knife exec and the desired api method we should be able to accomplish plenty of tasks.
Documentation for the chef api shows that the endpoint /users/USER/keys/KEY has the following methods available (GET, PUT, DELETE)
I'd expect to be able to delete an ssh key by executing:
knife exec -E 'puts api.delete("users/USER/keys/key")'
Current Behavior
when executing the command I receive the following error:
ERROR: Method Not Allowed
Response: 405 Method Not AllowedMethod Not AllowedMethod Not Allowedmochiweb+webmachine web server
Steps to Reproduce (for bugs)

first ensure you have a key for a user by using:

knife exec -E "puts api.get('users/USER/keys')"
you should see a list of keys

Try to delete the key by using the name of the key:

knife exec -E "puts api.delete('users/USER/keys/KEY')"
the key won't be deleted and the error shown is:
ERROR: Method Not Allowed
Response: <title>405 Method Not Allowed</title>
Method Not Allowed
Method Not Allowed

<address>mochiweb+webmachine web server</address>```

## Your Environment

* Chef Server Version: 12.17.15
* Total/free RAM and disk space: 16gb, 6GB
* Operating System and Version: RHEL 7.4
* If upgrading, previous Chef Server version:
* Running in a container? No

It appears that we only implemented 'GET' for user keys. See: https://github.com/chef/chef-server/blob/master/src/oc_erchef/apps/oc_chef_wm/src/oc_chef_wm_named_key.erl#L71, we seem to have skipped that. I'm not sure why; it seems like an oversight, and a missing piece for full functionality.

After allowing the 'DELETE' method in oc_erchef, user is able to delete the named keys using knife tool but the same is failing in the pedant tests.
Allow DELETE method - https://github.com/chef/chef-server/commit/c1aa9768bc4964aa81b425eac2da814bbe6f218f
Pedant test - https://github.com/chef/chef-server/compare/shahid/key-delete-api#diff-70f9e095036d84cdf45878f96c0a2fc22eaef82a2c94ef57bce8422a3b4c62d0
Pipeline result - https://buildkite.com/chef/chef-chef-server-master-omnibus-adhoc/builds/1985#3cef946c-844e-43e3-8895-aba23076d4ae
After discussion with @PrajaktaPurohit , the change is not as straightforward as it seems for a couple of reasons users are independent of orgs , there isn't a notion of using a key for user from only within the orgs. so while it should be ok to perform the necessary rest operations /user/username/key/keyname it might not be the right thing to do for /org/orgname/user/username/key/keyname.It appears that this might be happening due to knife not being able to differentiate between those paths.
Knife Working Screenshot -

Pedant Failing with bad signature -

After allowing the 'DELETE' method in oc_erchef, user is able to delete the named keys using knife tool but the same is failing in the pedant tests.
Allow DELETE method - https://github.com/chef/chef-server/commit/c1aa9768bc4964aa81b425eac2da814bbe6f218f
Pedant test - https://github.com/chef/chef-server/compare/shahid/key-delete-api#diff-70f9e095036d84cdf45878f96c0a2fc22eaef82a2c94ef57bce8422a3b4c62d0
Pipeline result - https://buildkite.com/chef/chef-chef-server-master-omnibus-adhoc/builds/1985#3cef946c-844e-43e3-8895-aba23076d4ae
After discussion with @PrajaktaPurohit , the change is not as straightforward as it seems for a couple of reasons users are independent of orgs , there isn't a notion of using a key for user from only within the orgs. so while it should be ok to perform the necessary rest operations /user/username/key/keyname it might not be the right thing to do for /org/orgname/user/username/key/keyname.It appears that this might be happening due to knife not being able to differentiate between those paths.
Knife Working Screenshot -

Pedant Failing with bad signature -

@ezequiels Thank you for creating this issue. Looks like you are trying to delete the user's default key, that operation is not permitted. https://github.com/chef/chef-server/issues/2240 tracks updating the docs with that info.
For operating against the global end point like the /users endpoint our recommendation is to use commands like
** USER COMMANDS **
knife user create USERNAME DISPLAY_NAME FIRST_NAME LAST_NAME EMAIL PASSWORD (options)
knife user delete USER (options)
knife user edit USER (options)
knife user key create USER (options)
knife user key delete USER KEYNAME (options)
knife user key edit USER KEYNAME (options)
knife user key list USER (options)
knife user key show USER KEYNAME (options)
knife user list (options)
knife user reregister USER (options)
knife user show USER (options)

In this particular case knife user key delete username keyname(other than default) knows to hit the global /user end point rather than in the context of an org like /organizations/orgname/users.
Although looking at the code it may seem like adding support to the DELETE method is all that we need to do, in terms of the context, it would mean that a user key can be deleted within a reference of an org. That could cause some unwanted side-effects since a user's key is a global object that can exist outside of an org.
If you need to use the knife exec command for automation, a workaround that can be used is updating the chef_server_url in knife.rb to http://hostname instead of http://hostname/organizations/orgname/
Or if you wanted to delete any user key other than default from the command line:
root@api:/vagrant# knife exec -E 'api.delete("/users/myuser/keys/user33")' --server-url https://<hostname>

Closing this issue for now. Please feel free to reopen or open a new issue if the workarounds do not work fo you.


EVP_DigestSignInit tries to initialize engine even though it was specified as null

I have successfully compiled OpenSSL with the enable_fips flag  on Windows with the WIN32A target.  I should note that WIN64A fails to build with errors in the makefile which I haven't had time to go figure out.
The resultant openssl.exe operates fully and passes all tests from the nmake tests command.
I have an application which provides signing services
I am attempting to utilize EVP_DigestSignInit with the following call:
if (EVP_DigestSignInit(mdcxt, NULL, EVP_sha3_384(), NULL, privateKey) != 1)
{
    // handle error
}

This generates the following exception:
Exception thrown: read access violation.
e was 0x88004700.
and here's the stack:
libcrypto-3.dll!ENGINE_init(engine_st * e) Line 94	C
libcrypto-3.dll!int_ctx_new(ossl_lib_ctx_st * libctx, evp_pkey_st * pkey, engine_st * e, const char * keytype, const char * propquery, int id) Line 240	C
libcrypto-3.dll!EVP_PKEY_CTX_new_from_pkey(ossl_lib_ctx_st * libctx, evp_pkey_st * pkey, const char * propquery) Line 374	C
libcrypto-3.dll!do_sigver_init(evp_md_ctx_st * ctx, evp_pkey_ctx_st * * pctx, const evp_md_st * type, const char * mdname, ossl_lib_ctx_st * libctx, const char * props, engine_st * e, evp_pkey_st * pkey, int ver, const ossl_param_st * params) Line 67	C
libcrypto-3.dll!EVP_DigestSignInit(evp_md_ctx_st * ctx, evp_pkey_ctx_st * * pctx, const evp_md_st * type, engine_st * e, evp_pkey_st * pkey) Line 386	C
Encrypt&SignServer.exe!ESSCommandsClass::Sign(std::basic_string<unsigned char,std::char_traits<unsigned char>,std::allocator<unsigned char>> x, unsigned int dataLen, unsigned short sessionID) Line 335	C++

My question is why is e anything but NULL?

Which version of OpenSSL are you using?

How was privateKey created? The value of e will either come from an explicit ENGINE that you pass in to the EVP_DigestSignInit call or it will use an ENGINE that was already associated with the pkey if there is one.

I'm using OpenSSL 3.0.10, sorry I had intended to write that originally.
The private key was fetched from a PEM file through BIO_new_file(, "r"); and PEM_read_bio_PrivateKey.
There is no engine associated with this key as it's a plain private key.
I've searched high and low to figure out how to use an engine in this context and I'm none the wiser.   Could you give an example of default engine being configured in the config file?

Could you give an example of default engine being configured in the config file?

See this page, and in particular the "Engine Configuration" section
https://www.openssl.org/docs/man3.0/man5/config.html
You might want to examine the state of privateKey in a debugger and determine whether privateKey->engine or privateKey->pmeth_engine are set.

Ah, therein lies a rub.    An EVP_PKEY* cannot be examined in a debugger because evp_key_st is an opaque type.    I don't think privateKey->engine or privateKey->pmeth_engine should be set since this is a plain private key.
However, it's obvious that those values are being set with random data.

Here's what *pkey looks like in do_sigver_init:

I don't see any data from the PEM file in that pkey

On first glance that key looks completely screwed. Could it be corrupted?

In fact it has a ref count of 0 which is invalid (possibly this is a use-after-free?)

We were able to use this key when we were using 1.0.1m.

I think the code:
key_bio = BIO_new_file(<path>, "r");
private_key = PEM_read_bio_PrivateKey(key_bio, &private_key, 0, NULL);

Doesn't properly read a PEM private key.

We were able to use this key when we were using 1.0.1m.

It's almost certainly not the underlying key data that is corrupt, but the in memory representation of it (so the fact that it worked in 1.0.1m is not the point). It is very likely that something in your application is causing it to become corrupted in some way.

Doesn't properly read a PEM private key.

It might be useful to look at the key in the debugger immediately before PEM_read_bio_PrivateKey returns. You should at least see the references field be a value that is >= 1.


Added a new machine learning course

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Not a duplicate
[ ] Included author(s) if appropriate
[ ] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

Alphabetize!
Be sure to check the output of Travis-CI for linter errors. Alphabetical order and spacing are the most common problems.


[Popper] Better collision prevention

Feature request
When using align="start" or align="end" the alignment may flip abruptly when a collision happens. Sometimes this introduces just another collision, which neither uses the available space efficiently, nor keeps the preferred alignment intact.
For example, when using align="start" side="right" the desired behaviour would be:

If align="start" results in a collision, try align="center"
If align="center" does not resolve the collision, try align="end"
If align="end" does not resolve the collision, revert to align="start"

Current behaviour:
https://user-images.githubusercontent.com/8441036/111156630-a5ec8400-859e-11eb-906a-3fc953ce4a10.mov

For example, when using align="start" side="right" the desired behaviour would be:

If align="start" results in a collision, try align="center"
If align="center" does not resolve the collision, try align="end"
If align="end" does not resolve the collision, revert to align="start"

IMO the desired behavior is to try and remain as close to the intended placement while avoiding the collision, so rather than re-aligning to a completely different value, offset such that the popper is against the edge.
For example, Popper.js with a middle-right placement:
Normal

Hitting bounds

Facing a similar situation here with a dropdown component that is align="start" and side="bottom". In my case, this opens the content from the left side. As the viewport gets smaller and a collision happens, it moves over to align="end", but since the position of the trigger is very close to the start of the viewport, it overflows outside the window.
I would expect that it would stick no further than the start edge. This way I could limit the size of the content, and potentially involve scrollbars when that's ok if the screen is of smaller size than necessary for my content.
CodeSandbox
Here I'd expect that it would then subtract the overflowing amount and push it to the preferred side (start/end).
Hope this makes sense.


cda.pl extractor stopped working

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.06.14. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.06.14

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue
Extractor for cda.pl just stopped working.

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl --verbose 'http://www.cda.pl/video/4816766c'
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'http://www.cda.pl/video/4816766c']
[debug] Encodings: locale UTF-8, fs UTF-8, out None, pref UTF-8
[debug] youtube-dl version 2016.06.14
[debug] Python version 2.7.9 - Linux-3.16.0-4-amd64-x86_64-with-debian-8.5
[debug] exe versions: avconv 2.6.9, avprobe 2.6.9, ffmpeg 2.6.9, ffprobe 2.6.9
[debug] Proxy map: {}
[CDA] 4816766c: Downloading webpage
WARNING: unable to extract default url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 676, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 342, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/cda.py", line 94, in _real_extract
    self._sort_formats(formats)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 863, in _sort_formats
    raise ExtractorError('No video formats found')
ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Description of your issue, suggested solution and other information
It worked just fine before. Maybe something changed on cda.pl page? (previous ticket: #8805)

You're right. CDA has changed their codes.


Add degit example to README.md

Fixes #18

Hi @JayaKrishnaNamburu, I'm not sure I understand the change you requested... I already added the degit line just as you mentioned: npx degit fidisys/react-native-boilerplate
Do you want me to remove the git clone line?

Here is the syntax for using degit , i am assuming my name as the project name.
npx degit fidisys/react-native-boilerplate jkrishna

Oh I get it now. It's missing the directory name, will fix ASAP


Control from commandline

Love the look of this player. Super simple and stylish! :heart:
Would it be possible to add a few options to be able to control the player from the command line. E.g.

Play/pause
skip next/prev track
skip ahead/back x seconds

Hi @PhilT,
I'm glad you liked spectrum! :smile:
Let me know if I understood you correctly: it would be something like, for example, executing "spectrum --skip-next" and that would send a media command to skip to next song in the main instance of spectrum, is that right?
I have to do a little research about IPC mechanisms and think about how to properly use it in this application (for example, what should be done when multiple spectrum processes are running, and other corner cases like that).
But yes, I think it is possible. I'll mark this issue as enhancement and focus on this as soon as I finish the issue #25 (this one is costing me much more time than I had planned :sweat_smile:).

Yes exactly! https://github.com/cmus/cmus does exactly this.
No problem. Indeed playlists are nice :)


Update nodejs

New deployments of nodejs are failing, and we need to update to nodejs10:
https://cloud.google.com/functions/docs/migrating/nodejs-runtimes

This was fixed by https://github.com/google/turbinia/pull/595 and https://github.com/forseti-security/osdfir-infrastructure/pull/2


Warnings on context.log after context.done is called

It's very easy to mess up async patterns when using callbacks. We should emit a warning if we see any activity via context.log after context.done() has been called.

Reviewing a support case where the problem was they were mixing async and callbacks and was causing code to not work as expected.  I think this may help but I'm wondering why it didn't work for them.  I know it's a larger problem, but wondering where this warning shows? In otherwords - if we emit this warning does it show in app insights traces? Kusto? The Portal?


Use shallow fetch depth

Set fetch limit to a depth of 1 for our pipelines as they're just building off of one commit. Saves disk space at least. Might save time.
PR Checklist

[x] Closes #10803
[x] I work here
[ ] Blends.

See also: https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops&tabs=yaml#shallow-fetch

Audit:

Before 26s - 97.81MB objects (62910) - deltas 48417
After 28s - 68.16MB objects (15527) - deltas 10150

x64 release:

Before 21s
After 40s
(same other things)

x86 release:

Before 25s
After 27s
(same other things)

Compared.... PR 11819 (before) and PR 11851 (after)
So looks like unless the server gets choked up for whatever reason... its about 10% slower to complete checkout (2 secondsish) and saves about 30MB of transfer (30%) to the build agent. I think that's fine to turn it on as +10% time at 2 seconds for -30% transfer at 30MB over many, many builds is nice.


Increment version for storage releases

Increment version for storage releases

Can one of the admins verify this patch?


Adding og:image parameter to single

Would be nice to add teh meta of:image to the single post so the cover image can be the image highlight when sharing the post
Read:
https://discourse.gohugo.io/t/display-first-image-in-post-in-link-preview/10541

The open graph metadata is already in the theme and supports all three image variants. Are you saying it isn't working?

 Idk

I'll have a look tomorrow againand close this

It does look, idk why it didnt before, soz


please update podman in RHEL extra's more often

Hi,
Ref. https://github.com/containers/libpod/issues/3044
The same issue applies now in RHEL 7.7...
The current available version of podman is 1.4.4-4 and we preferably want to have the latest(v1.6.3) since the newer ones have important bug fixes for running rootless podman.  If i want to convince my developers to switch completely to podman from docker, then we need a more frequent update release on podman and necessary dependencies...
Thank you in advance for the help!
TAGS: @fatherlinux

RHEL7.8 version of Podman will match the RHEL8.2 version.  Sadly this will probably be the final release other then CVE fixes, since RHEL7 will be entering its next level of support, which is just security fixes.

Hmm, that is unfortunate!
Does podman/buildah have an online rpm-repository where I could download from? I have googled for this without any success. That would partially solve our problem.

You can run newer podman inside of a container quay.io/podman/stable which would get you a newer version.
You would need to run this in a --privileged container with the hosts podman or docker.

Hmm, that is sadly not a good solution for us.
Shame that there is no own repository... It would make it a lot easier for our developers to change.

@jonasbartho Moving to RHEL8 you will get latest podman every three months.  RHEL7 is probably not a great place for developers at this point, since it is almost 7 years old.

Ok thx!


Dark mode should be more consistent

Let's try implementing these: https://m2.material.io/design/color/dark-theme.html
Background should be dark, foreground should be light

i mean yea but like i feel like we are getting into stage of life where everything is going dark and for the 'lets try implementing this ' its possible but think about this we need thousands or people to do this

Hi - who is @laith2026? Are they a member of the EPS community?

I'm not part of the EPS community, so I wasn't aware of any potential issue. If there is indeed a problem, I apologize sincerely.

No problem at all. Can you please elaborate on your comment? (The website is currently in dark mode). What does "thousands of people to do this" mean?

What I mean is the app already has a good theme, and it doesn't need any changes.

Users have been requesting to change this ui. We originally kept the center dark and bg light, and now they are requesting a darker bg with brighter center. Header bars could also use some refreshing

Yes i agree also you coud use some padding for help and yes make the background lighter if thats possible

@ajosan25 could you try this out just by changing the CSS var colors?


Add empty calculateBounds to DisplayObject, remove Bounds.updateID references

Description of change
Since DisplayObject uses DisplayObject.calculateBounds, it should at least provide an empty implementation to be overwritten in child classes like Container.
Also there was two places in which bounds.updateID++ was used, which is a property that doesn't actually exist on bounds (anymore?). This just causes that property to be created and set to NaN and it thus was a silent error.
Pre-Merge Checklist

[ ] Tests and/or benchmarks are included
[ ] Documentation is changed or added
[ ] Lint process passed (npm run lint)
[ ] Tests passed (npm run test)

Oh, I saw that too, I forgot to make a PR!

@ivanpopelyshev The bounds IDs are tracked elsewhere. This code was trying to update a updateID on the Bounds object.
Bounds IDs are actually tracked on DisplayObject in DisplayObject._boundsID and DisplayObject._lastBoundsID.
I removed two instances of Bounds.updateID++, which was the only two places in the entire code base to even refer to that property afaik.

Maybe it should be this._boundsID++ instead of this._bounds.updateID++ though.
I just removed it because I assumed it wasn't needed, since it's essentially a NOOP right now and there was no apparent issues...

It should probably be this._boundsID++ like in Container:
https://github.com/pixijs/pixi.js/blob/1de41d78b2bb694261f7057f48f5758c863b1898/packages/display/src/Container.js#L414
I'll fix that in a second.

Codecov Report

Merging #6304 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #6304   +/-   ##
=======================================
  Coverage   77.57%   77.57%
=======================================
  Files         186      186
  Lines       10083    10083
=======================================
  Hits         7822     7822
  Misses       2261     2261

Impacted Files
Coverage Δ

packages/display/src/Bounds.js
91.04% <ø> (-0.05%)
:arrow_down:

packages/display/src/DisplayObject.js
94.59% <100%> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

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

https://github.com/pixijs/pixi.js/blob/bca4b623a532c79a890d34158ed8228244224d89/packages/display/src/DisplayObject.js#L216
You increase boundsID, but transform not necessarily will be updated.

Its like that because we dont yet have code to track bounds, but we think that they are not updated if updateTransform wasnt called :)

DisplayObject._currentBounds appears to be another unused property.


Queue containing a message type not expected

Hi,
Every now-and-then I get the following error (in the OnError event).
Do you either have an idea where this comes from, or a suggestion where I can start debugging?
Thanks,
Erik
Queue containing a message type not expected [http://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer].
Stacktrace:   at TableDependency.Messages.MessagesBag.AddMessage(Message message)
atTableDependency.SqlClient.SqlTableDependency1.<>c__DisplayClass63_0.<WaitForNotifications>b__0(Message m)    at System.Collections.Generic.List1.ForEach(Action1 action)    at TableDependency.SqlClient.SqlTableDependency1.d__63.MoveNext()

Which Sql Server DB version are you using?

Hi Christian,
I am using Microsoft SQL Server Developer (64-bit) locally, version 12.0.5207.0 (SQL Server 2014 SP2).
Best regards,
Erik

Hello,
I am also receiving this error message.  I am using SQL Server Express 2012 on my local machine.  Is there a solution for this?  Here is the stack trace i received.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()    at TableDependency.SqlClient.SqlTableDependency1.DropDatabaseObjects(String connectionString, String databaseObjectsNaming)
at TableDependency.TableDependency`1.Stop()

I'm facing same issue, i'm using sql server developer 2016

I believe this error is occurring when the computer goes to sleep.  I have an assumption that this is due to it running the SQL Server locally and the local instance of SQL server goes to sleep or becomes idle.  Not exactly sure what the local instance does when the computer goes to sleep.
I am going to put the database on a production SQL server and see if the problem still continues.  I still see there being an issue though.  If for some reason the server crashes, needs to be taken offline for updates, or possibly even nightly backups occur and my assumption is correct an application could get in a state where it wont be able to access the connection again until it is restarted.
I will comment again once I move the database and do some further testing.

It is as lucusP320 commented on Mar 12 "I believe this error is occurring when the computer goes to sleep".

lucusP320 --> You are very smart!


Merging Develop into Master 2.12.2020 - Added Enforced TLS page, updates to sign in with apple,

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


feat: RT Kernel

ill need to make a new repo with the proper RTKernel pacakges, using audinux for that didnt work out as well as i expected.

duplicate


Added BlazorNavigationManagerExtensions

BlazorNavigationManagerExtensions is a simple set of extensions for the Navigation Manager to simplify its usage for things we are likely to do in most of our Blazor applications. It currently supports an overload to the NavigateTo method where you can specify query string parameters and a Reload method that force loads the current page. The goal would be to add methods that people need so that all the needs for the Navigation Manager are in one place.

Thanks! Released in https://github.com/AdrienTorris/awesome-blazor/releases/tag/v2020.W35.


Enhance Service Bus binding to enable calling service APIs

Issue to track enhancements to the Service Bus binding to enable use of SDK APIs from the .NET Worker binding targets.

With #1535 wrapping up, I can't wait to see this issue worked on, and finally have future parity to be able to be able to use Isolated Worker SDK across the board 🤞

🍾 when it's on NuGet


libwebp-base 1.3.2

To fix CVE-2023-4863:
Changelog: https://chromium.googlesource.com/webm/libwebp/+/refs/tags/v1.3.2/ChangeLog and https://chromium.googlesource.com/webm/libwebp/+/refs/tags/v1.3.2/NEWS
CMakeLists.txt: https://chromium.googlesource.com/webm/libwebp/+/refs/tags/v1.3.2/CMakeLists.txt
Actions:

Add -DCMAKE_INSTALL_DATADIR=%LIBRARY_PREFIX% ^ to bld.bat (following the c-f recipe; without it the build fails on win64)
Reset the build number to 0
Remove obsolete patches
Replace pin_compatible by pin_subpackage like conda-forge did
Add "libsharpyuv" to libraries for testing
Fix indentation for selectors in test/commands

Notes:

libwebp 1.3.2 is also waiting for review  https://github.com/AnacondaRecipes/libwebp-feedstock/pull/8

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:16: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:16: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:16: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:16: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found


Evaluate flate2

Looks like flate2 is more safe than libflate.

I'm now working my way through libflate, reporting sometimes and fixing the issues I discover:
https://github.com/sile/libflate/issues/29
https://github.com/sile/libflate/issues/31
https://github.com/sile/libflate/issues/33
I couldn't get any bugs out of miniz_oxide (the Rust backend for flate2) with a fuzzer, including when fuzzing with libdiffuzz. I have to admit that reasoning about the unsafety in miniz_oxide is beyond my abilities, but it doesn't look very reassuring. Issues like https://github.com/Frommi/miniz_oxide/issues/14 also don't instill confidence.
I can vouch for the safety of https://github.com/image-rs/inflate because I've purged all but one unsafe blocks in it, and then found and fixed the bug in the remaining unsafe block together with the maintainer. But last time I checked it was even slower than libflate.

I'm done cleansing libflate of unsafe blocks. It only has one, which I've verified to be sound. Another one has been punted into a separate crate, where the implementation is heavily based on a stdlib function. So I can vouch for the safety of libflate as well, starting with version 0.1.25.
Also, I've since discovered a heap buffer overflow in miniz_oxide and likely also miniz, and would advise against using them if safety is a concern.

Nice! Than I will force the minimum libflate version.

I believe this issue should be revisited. The Rust backend for flate2 called miniz_oxide is now 100% safe and forbids unsafe code. It is also 2.5x faster on decompression than libflate.
There is still some unsafety in flate2, so I'd suggest using miniz_oxide directly. This would improve performance, provide compiler-guaranteed safety and reduce the number of dependencies.

Thanks. I will try it out.

I've switched to flate2, but not to miniz_oxide directly. Since I need gzip support.


refactor: editor context menu injection logic

Types

[x] 🎉 New Features
[x] 💄 Code Style Changes

Background or solution
https://user-images.githubusercontent.com/17701805/159426603-da5f2d0c-5630-4717-9fb7-92f4f0ab78e5.mp4
fixes: #694
Changelog

refactor: editor context menu injection logic

Codecov Report

Merging #695 (b19f479) into main (134a19c) will increase coverage by 0.05%.
The diff coverage is 55.22%.

@@            Coverage Diff             @@
##             main     #695      +/-   ##
==========================================
+ Coverage   58.63%   58.69%   +0.05%
==========================================
  Files        1209     1209
  Lines       74737    74779      +42
  Branches    15505    15522      +17
==========================================
+ Hits        43824    43890      +66
+ Misses      28176    28155      -21
+ Partials     2737     2734       -3

Impacted Files
Coverage Δ

packages/core-browser/src/monaco/index.ts
100.00% <ø> (ø)

packages/editor/src/browser/index.ts
73.61% <ø> (-0.37%)
:arrow_down:

packages/editor/src/browser/menu/editor.context.ts
65.93% <55.22%> (+43.71%)
:arrow_up:

...xt/src/browser/services/file-tree-model.service.ts
53.83% <0.00%> (-0.60%)
:arrow_down:

packages/core-browser/src/common/common.command.ts
100.00% <0.00%> (ø)

packages/keymaps/src/browser/keymaps.service.ts
63.24% <0.00%> (+0.28%)
:arrow_up:

...ages/file-service/src/node/file-service-watcher.ts
72.88% <0.00%> (+1.69%)
:arrow_up:

packages/file-service/src/browser/watcher.ts
100.00% <0.00%> (+4.34%)
:arrow_up:

...es/src/browser/userstorage/user-storage.service.ts
71.91% <0.00%> (+14.60%)
:arrow_up:

Continue to review full report at Codecov.

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


Failing CloudInit and Kubelet setup during worker node startup

Recently in the past day all EKS clusters I create via @pulumi/eks's new eks.Cluster are failing to start up worker nodes. One symptom is that some or all of the nodes fail to join the EKS cluster.
A snippet of the log is pasted further below. The code used to create the cluster, which was working properly last week, is here:
import * as fs from "fs";
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as eks from "@pulumi/eks";
import * as k8s from "@pulumi/kubernetes";
import * as YAML from "js-yaml";

//
// Configuration
//
let config = new pulumi.Config("eks-cluster");
const environment = config.require("environment");
const vpcSubnetIds = config.require("subnet-ids").split(",");

let splunkConfig = new pulumi.Config("splunk");

//
// Actions to perform at the startup of any worker node in the cluster
//
const userData = `set -o xtrace
echo "Starting UserData for the EKS worker nodes"
yum install -y epel-release
yum update -y
yum install -y \
  jq \
  yq \
  cifs-utils \
  nfs-utils \
  nfs-common \
  nfs4-acl-tools \
  portmap \
  screen \
  vim \
  mountpoint \
  base64 \
  bind-utils \
  coreutils \
  util-linux
VOLUME_PLUGIN_DIR="/usr/libexec/kubernetes/kubelet-plugins/volume/exec"
mkdir -p "$VOLUME_PLUGIN_DIR/fstab~cifs"
cd "$VOLUME_PLUGIN_DIR/fstab~cifs"
curl -L -O https://raw.githubusercontent.com/fstab/cifs/master/cifs
chmod 755 cifs\
`

// Create the Kubernetes cluster and all associated artifacts and resources
const cluster = new eks.Cluster(environment+"-eks-cluster", {
    vpcId             : config.require("vpc-id"),
    subnetIds         : vpcSubnetIds,
    instanceType      : "m4.4xlarge",
    nodePublicKey     : config.require("worker-ssh-key"),
    nodeRootVolumeSize: 250,
    desiredCapacity   : 3,
    maxSize           : 5,
    minSize           : 1,
    nodeUserData      : userData,
    deployDashboard   : false,
});

// Write out the kubeconfig file
export const kubeconfig = cluster.kubeconfig;
cluster.kubeconfig.apply(kc => fs.writeFileSync("./config-"+environment+".kubeconfig.json", JSON.stringify(kc)))

// Write the kubeconfig to a location in S3 for safe keeping
cluster.kubeconfig.apply(kc => {
  let s3Kubeconfig = new aws.s3.BucketObject("kube_config/config-"+environment+".json", {
    bucket: "sdp-helm",
    content: JSON.stringify(kc),
  })}
);

// Allow SSH ingress to worker nodes
new aws.ec2.SecurityGroupRule("ssh-ingress", {
    type: "ingress",
    fromPort: 22,
    toPort: 22,
    protocol: "tcp",
    securityGroupId: cluster.nodeSecurityGroup.id,
    cidrBlocks: [ "<IP_ADDRESS>/0" ],
});

The journalctl output on one of the hosts shows the following problems:
failed to run Kubelet: could not init cloud provider "aws": error finding instance i-0f016b7e718a12801
Failed to start Apply the settings specified in cloud-config.
Unit cloud-config.service entered failed state.

Nov 06 01:06:13 ip-10-10-3-24.tableausandbox.com systemd[1]: Starting yum locked retry of update-motd...
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com update-motd[5484]: Yum database was locked, so we couldn't get fresh package info.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: Started yum locked retry of update-motd.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: Starting yum locked retry of update-motd.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: One of the configured repositories failed (Unknown),
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: and yum doesn't have enough cached data to continue. At this point the only
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: safe thing yum can do is fail. There are a few ways to work "fix" this:
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: 1. Contact the upstream for the repository and get them to fix the problem.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: upstream. This is most often useful if you are using a newer
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: distribution release than is supported by the repository (and the
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: packages for the previous distribution release still work).
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: 3. Run the command with the repository temporarily disabled
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: yum --disablerepo=<repoid> ...
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: 4. Disable the repository permanently, so yum won't use it by default. Yum
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: will then just ignore the repository until you permanently enable it
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: again or use --enablerepo for temporary usage:
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: yum-config-manager --disable <repoid>
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: or
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: subscription-manager repos --disable=<repoid>
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: 5. Configure the failing repository to be skipped, if it is unavailable.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: Note that yum will try to contact the repo. when it runs most commands,
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: so will have to try and fail each time (and thus. yum will be be much
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: slower). If it is a very temporary problem though, this is often a nice
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: compromise:
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: Cannot find a valid baseurl for repo: amzn2-core/2/x86_64
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: Could not retrieve mirrorlist http://amazonlinux.us-west-2.amazonaws.com/2/core/latest/x86_64/mirror.list error was
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: 12: Timeout on http://amazonlinux.us-west-2.amazonaws.com/2/core/latest/x86_64/mirror.list: (28, 'Resolving timed out after 5515 milliseconds')
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: Nov 06 01:06:18 cloud-init[4927]: util.py[WARNING]: Package upgrade failed
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: Nov 06 01:06:18 cloud-init[4927]: cc_package_update_upgrade_install.py[WARNING]: 1 failed with exceptions, re-raising the last one
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[4927]: Nov 06 01:06:18 cloud-init[4927]: util.py[WARNING]: Running module package-update-upgrade-install (<module 'cloudinit.config.cc_package_update_u
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: cloud-config.service: main process exited, code=exited, status=1/FAILURE
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: Failed to start Apply the settings specified in cloud-config.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: Unit cloud-config.service entered failed state.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: cloud-config.service failed.
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com systemd[1]: Starting Execute cloud user/final scripts...
Nov 06 01:06:18 ip-10-10-3-24.tableausandbox.com cloud-init[5517]: Cloud-init v. 18.2-72.amzn2.0.6 running 'modules:final' at Tue, 06 Nov 2018 01:06:18 +0000. Up 155.71 seconds.
Nov 06 01:06:20 ip-10-10-3-24.tableausandbox.com cloud-init[5517]: Cluster "kubernetes" set.
Nov 06 01:06:20 ip-10-10-3-24.tableausandbox.com systemd[1]: Reloading.
Nov 06 01:06:20 ip-10-10-3-24.tableausandbox.com cloud-init[5517]: Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.
Nov 06 01:06:20 ip-10-10-3-24.tableausandbox.com systemd[1]: Reloading.
Nov 06 01:06:20 ip-10-10-3-24.tableausandbox.com systemd[1]: Started Kubernetes Kubelet.
Nov 06 01:06:20 ip-10-10-3-24.tableausandbox.com systemd[1]: Starting Kubernetes Kubelet...

...

Nov 06 01:08:22 ip-10-10-3-24.tableausandbox.com kubelet[5645]: F1106 01:08:22.657450    5645 server.go:233] failed to run Kubelet: could not init cloud provider "aws": error finding instance i-0f016b7e718a12801
Nov 06 01:08:22 ip-10-10-3-24.tableausandbox.com systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Nov 06 01:08:22 ip-10-10-3-24.tableausandbox.com systemd[1]: Unit kubelet.service entered failed state.
Nov 06 01:08:22 ip-10-10-3-24.tableausandbox.com systemd[1]: kubelet.service failed.
Nov 06 01:08:27 ip-10-10-3-24.tableausandbox.com systemd[1]: kubelet.service holdoff time over, scheduling restart.

We dug into this offline. It turns out that the root cause here is that some worker nodes were being created in public subnets and had no route to the EKS API server. This was because the subnetIds argument to the eks.Cluster contained both public and private subnets, and this list is passed verbatim to the CF template that boots the worker nodes. I am investigating whether or not eks.Cluster can and should automatically filter out these public subnets or whether we ought to expose an additional argument s.t. the user can restrict the subnets in which workers are created.

This was due to incorrect EKS networking setup. Had workers deploying to public subnets. Fix is to only put workers on the private subnets.


:mega: looking for contributors

This project is currently looking for contributors.
Drop a note, or ping, if you are interested.

/? sbom conda

https://www.google.com/search?q=sbom+conda
https://pypi.org/search/?q=sbom+conda&o=

conda envs can contain Conda and also Python packages.
mamba is faster than conda.

https://github.com/mamba-org/mamba

the miniforge installer ships conda and mamba with -c conda-forge as the default channel

https://github.com/conda-forge/miniforge

pixi is faster than pip and IIRC mamba and thus conda, too
https://prefix.dev/

pixi

src: https://github.com/prefix-dev/pixi
docs: https://pixi.sh/latest/
docs: https://pixi.sh/latest/features/environment/#structure

https://github.com/prefix-dev/rip

"UV in Pixi" > "Benchmarking rip and uv"
https://prefix.dev/blog/uv_in_pixi#benchmarking-rip-and-uv

https://github.com/astral-sh/uv/issues/1572#issuecomment-1949979306

pixi is replacing rip with uv
https://github.com/astral-sh/uv/issues/888

uv

src: https://github.com/astral-sh/uv/
docs:
docs: https://github.com/astral-sh/uv/blob/main/PIP_COMPATIBILITY.md#pip-check

conda/conda-lock:
https://github.com/conda/conda-lock/issues/615
conda/conda-content-trust:

src: https://github.com/conda/conda-content-trust
docs:
docs: https://docs.anaconda.com/pro/security/
TUF package signatures for conda packages
verify_signature()
https://github.com/conda/conda-content-trust/blob/main/conda_content_trust/authentication.py#L253
Conda Security Practices >

"Enabling conda signature verification"
https://docs.anaconda.com/pro/security/#enabling-conda-signature-verification

conda install "conda>=4.10.1" "conda-token>=0.3.0" conda-content-trust
conda token set --enable-signature-verification <YOUR_PRODUCT_TOKEN>

Conda version 23.10+ uses libmamba as the default solver, which bypasses signature verification. If you are using conda 23.10 or later, you must configure your .condarc file to use the classic environment solver by running the following command:
conda config --set solver classic

https://github.com/mamba-org/mamba/issues/3283
https://github.com/conda/conda-content-trust/issues/123

docker build builds containers from Dockerfiles with BuildKit.
docker scout sbom: https://docs.docker.com/reference/cli/docker/scout/sbom/
builtkit supports build-time SBOMs:
https://github.com/moby/buildkit/blob/master/docs/attestations/sbom.md :

By default, only the final build result is scanned - because of this, the resulting SBOM will not include build-time dependencies that may be installed in separate stages or the build context. This could cause you to miss vulnerabilities in those dependencies, which could impact the security of your final build artifacts.
To include these build-time dependencies from your Dockerfile, you can set the build arguments BUILDKIT_SBOM_SCAN_CONTEXT and BUILDKIT_SBOM_SCAN_STAGE to additionally scan the build context and other build stages respectively.

podman also supports build-time SBOMs:
podman build --sbom
https://docs.podman.io/en/stable/markdown/podman-build.1.html#sbom-preset

“syft-cyclonedx”, “trivy-cyclonedx” [|| spdx]

CycloneDX SBOM specs

https://github.com/CycloneDX/cyclonedx-property-taxonomy/blob/main/cdx/python.md
https://github.com/CycloneDX/cyclonedx-property-taxonomy/blob/main/cdx/poetry.md
https://github.com/CycloneDX/cyclonedx-property-taxonomy/blob/main/cdx/pipenv.md
[ ] conda.md
[ ] pixi.md
[ ] conda-lock.md

"CycloneDX Python SBOM Generation Tool"
https://github.com/CycloneDX/cyclonedx-python?#cyclonedx-python-sbom-generation-tool :

Conda as a package manager is no longer supported since version 4.
However, conda's Python environments are fully supported via the methods listed above. See the docs for an example.

[ ] DOC: what does this mean?

this project is not about any python specifics.
python specifics are managed by https://github.com/CycloneDX/cyclonedx-python.

Conda provides package, dependency, and environment management for any language

therefore, the vision is to have a tool that can generate a SBOM all "package, dependency, and environment management" conda does.
this project is not about podman/docker/docker build. it is about conda.


If delivery fails when calling deliver_later, log the error

So you can see that something went wrong

This will be handled by the strategy


Parse binary-prefixed byte values

This adds the ability for bytefmt to correctly parse byte values when the caller specifies binary-prefixed byte values (kiB, MiB, etc.). I notice internally you're doing math in terms of base 2 (1KB == 1024 vs. 1000), so this fortunately doesn't require any other changes than making the regexp allow for an i to be in the unit prefix.
The impetus for this change is that we use numeral.js in our frontend, and bytefmt in a Golang CLI. Numeral.js makes the distinction between base-10 and base-2 (as in, 1000 is 1KB but <1KiB), and if we use its default value formatting, this change allows users to directly copy a value off the UI and have bytefmt correctly understand it. Without this change, it fails to parse.

Hi, @mjlangan, thanks for the contribution! Sounds reasonable to me, and I'll prioritize this for the CF Diego team to evaluate soon. Have you signed a CLA for the Cloud Foundry Foundation yet, or do you belong to a GitHub org that is covered by a corporate CLA?
Thanks,
Eric, CF Diego PM

@emalm Yes, I just submitted a corporate CLA to cover submissions by my team here at the Allen Institute for Artificial Intelligence. Sorry for the delay, kept forgetting to scan it and send it :)

Hey, @mjlangan, thanks for submitting the CLA! Could you please publicize your membership in the "allenai" GitHub organization so that @cfdreddbot can connect that to the corporate CLA? Instructions for publicizing that membership are in https://help.github.com/articles/publicizing-or-hiding-organization-membership/.
Thanks,
Eric

@mjlangan Let me try closing and re-opening the PR again to see if Dreddbot picks up on your organization membership now.

This makes the current units suffix confusing though. not sure what to do about that. @emalm thoughts ?

@jvshahid yeah, I think this at least gives bytefmt better interoperability with the "correct" binary prefixes. Let's add a story to document the bytefmt idiosyncrasy of using the decimal prefixes to mean binary quantities (or do it as part of pulling in this PR if we are so inclined).


Update client may cause "new header has a time from the future" chain error

Crate
relayer

Summary of Bug
@mircea-c has reported that the following errors are seen once in a while when updating the sifchain client (07-tendermint-395) on cosmoshub:
Oct 11 09:13:03.057 DEBUG ThreadId(42) [cosmoshub-4] simulated gas: Err(
    0: #033[91mGRPC call return error status status: InvalidArgument, message: "failed to execute message; message index: 0: cannot update client with ID 07-tendermint-395: failed to verify header: inval
id header: new header has a time from the future 2021-10-11 13:12:56.673817244 +0000 UTC (now: 2021-10-11 13:12:51.047099028 +0000 UTC; max clock drift: 5s): invalid request", details: [], metadata: Meta
dataMap { headers: {"content-type": "application/grpc"} }#033[0m

After looking at the sif chain configuration (client created with clock_drift = 5sec) and comparing block times (5-6 sec on sif, 7-13 sec on hub), the following seems to be the issue.
Here is an example (- is 1 sec, b are blocks on sif, B are blocks on the hub).
	   1:ev 2:clUpdate
           |    |  |
           |    | 3: fetch header (h)
           v    v  |
b----b-----b----b-----b----b      (sifchain 5/6 sec blocktimes)
                |  | 4: simulate/ send Tx
                |  v
B-------B------------B------B     (cosmoshub 7-13 sec)
        ^       |
        | 5: create context with latest header (H)
        |       |
        v       v
        <-------> 6: check that h.timestamp - drift < H.timestamp (aka now)

The steps are:
1 - an IBC event that requires a clientUpdate
2 - hermes starts to build the client update message and
3 - fetches the header h from sifchain (this happens for the header at event height + 1)
4 - sends a simulate request to the hub (can happen on send_tx as well)
5 - the chain receives the request and creates a context with the latest header H on the hub
6 - the client handler is called with that context and the message. Among other things it checks that the h.timestamp is not "in the future", i.e. H.timestamp + client_state.clock_drift > h.timestamp
(one 13 sec example on the hub:
h:7969646 - ts:16:31:24
h:7969647 - ts:16:31:37
)
One problem is that the clock_drift of 5 sec is not enough for clients of sifchain on the hub. But it might be appropriate for clients of sifchain on other chains. This in itself is a hint on the difficulty of sizing this properly. Also changing the configuration alone is not enough to fix the issue, it would require new clients, connections and channels to be created, and applications to switch to these.
The other solution is to make hermes' update client code more robust. This issue is to investigate and if possible fix this on hermes side.
cc @adizere @romac
A number of ideas were mentioned, hermes could maybe perform the H.timestamp + client_state.clock_drift > h.timestamp check when updating tendermint clients, or drop the tx on the specific tx simulate (or tx_send()) error ( (to be picked by the clear packet mechanism or retries for channel/ connection handshake).

Version
all

Steps to Reproduce
We should be able to reproduce this with local setup, create two chains with different block times, create client with small clock_drift values.

Acceptance Criteria
Ideally this error should never be seen with correct headers. Impact on hermes operation should be minimal with "bad" headers, e.g. one that is in the long future.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Maybe the total clock_drift value when creating a client needs to consider the worst case, i.e. it should be:
src_chain.clock_drift + dst_chain.clock_drift + dst_chain.block_time
meaning we need to have a separate block_time configured per chain, unless we can estimate it via some query(?).
cc @milosevic for help here.

We recently added an on chain parameter for this (so relayers could use that value).

Could you please provide more details on this?

But to take this into account on chain for the light client, we would need to add a new parameter to the ClientState?

This would be the local chain block time to be added to the client state drift....
if !untrustedHeader.Time.Before(now.Add(maxClockDrift).Add(selfBlockTime)) {
assuming i read the code correctly and now is the latest block time on this chain.

You can add a static wait time before submitting the header to the counterparty. This may still occassionally run into problems and its a bit brittle, but it is trivial to do and will work 99% of the time.

I think we may as well wait for the next block since nothing can proceed if client update fails and it is as trivial as waiting for a fixed duration.

Thanks Zarko!
It makes sense although I have some doubts on the math, isn't it?:
h.time + clock_drift_A < H.time - clock_drift_B - chainB.average_block_time
which means that herems could check before the update:
h.time + clock_drift_A + clock_drift_B + chainB.average_block_time < H.time
For this purpose I was proposing creating the client with a "clock_drift" of
clock_drift_A + clock_drift_B + chainB.average_block_time

note that clock_drift becomes misleading now but we are stuck with this per .proto file

So the check would be: h.time + client_state.clock_drift < H.time, and exactly what the on-chain handler does.
Now the question is what do we do in hermes if this check doesn't hold. The cause could be:

the drifts and block times were not estimated/ configured properly
the header is in fact a bad header which is in the future

We could drop the header and return error. In most cases the effect will be that the event that triggered the update will be re-processed and will result in an update with a header at a different height.
Another alternative is to create instead the client with drift clock_drift_A + clock_drift_B and if the check fails:

wait for next block H' on B (*)
check again h.time + client_state.clock_drift < H'.time and drop the header if it fails

This one is tempting at first look as it avoids adding yet another configuration parameter and the pain of coming up with a good value. But...
(*) the thread/ worker may block for a long time if chains don't have a heartbeat which is probably fine from a functional pov. We could also limit the time to some big value. But in this case we would not be able to catch some cases of in-the-future header.
In either implementation we would alert the user that an in-the-future header was seen so the proposer's clock can be checked.


Remove Mailchimp Popup and add Popup maker popup

Mailchimp popup is hardcoded into WP theme, but WP Popup maker is working on Staging now, so it's time to switch it over.
Two things to do:

QA on Popup Maker on Staging for "Email Signup" Popup
Remove Mailchimp theme
Deploy Popup maker

Rob – before you move it over, can you check in with me to make sure that it's ready on staging before launch?
Search will probably keep the Mailchimp plugin because it's not on Wordpress.

@little-wow Heya. Just checking in about the version on staging being good to go.
Also one note: this popup will use a different cookie from the mailchimp popup in the theme, so we will get reports from people who previously subscribed via or dismissed the theme-based popup that a pop-up is showing again. We can't do anything about that, we'll just have to be sympathetic to people reporting it.

The MailChimp code has been removed from the theme and deployed.
The new popup has been copied over to Live and activated.


UnboundLocalError: local variable 'feature' referenced before assignment

**To whom it may concern,
I was trying to use fluff to plot a dynamic heatmap. I ran the following code:**
fluff heatmap -f Merged_peaks_MACS0.10_noPeaklistinput_CallpeaksbyRep12345_02062018.bed -d A.bed B.bed C.bed D.bed -C k -k 6 -g -M Pearson -o Merged_peaks_MACS0.10_noPeaklistinput_CallpeaksbyRep12345_02062018_Rep12only_k6
And got the following errors:
Is there a way to solve this?
Warning: Running fluff with too many files might make you system use enormous amount of memory!
Pearson distance method
Loading data
Error loading data in parallel, trying serial
Error: local variable 'feature' referenced before assignment
Traceback (most recent call last):
File "/home/ceang/anaconda3/envs/biofluff/bin/fluff", line 4, in
import('pkg_resources').run_script('biofluff==2.1.3', 'fluff')
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/pkg_resources/init.py", line 658, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/pkg_resources/init.py", line 1438, in run_script
exec(code, namespace, namespace)
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/biofluff-2.1.3-py2.7.egg-info/scripts/fluff", line 9, in
args.func(args)
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/fluff/commands/heatmap.py", line 147, in heatmap
fragmentsize, dynam, guard)
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/fluff/commands/heatmap.py", line 125, in load_data
fragmentsize, dynam, guard)
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/fluff/fluffio.py", line 183, in load_heatmap_data
result = track.binned_stats(tmp.name, bins, split=True, rpkm=rpkm)
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/fluff/track.py", line 162, in binned_stats
for feature, min_strand, plus_strand in self.fetch_to_counts(in_track):
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/fluff/track.py", line 469, in fetch_to_counts
for feature, features in self._get_features_by_feature(track):
File "/home/ceang/anaconda3/envs/biofluff/lib/python2.7/site-packages/fluff/track.py", line 523, in _get_features_by_feature
yield feature, features
UnboundLocalError: local variable 'feature' referenced before assignment

I have tried to reproduce the error, but I can't. Can show me the top few lines of the input files (peaks and data files). Does it depend on one of the data files (A, B, C or D.bed) or does any one of these files result in this error? Do you have minimum example that you can give me?

Closing due to inactivity, feel free to re-open if necessary.


openPicker() not working

openPicker() not working with the last updated release

ohhh my god. I will fix it soon.

duplicate #122


Xcode12 support

XCTestCase.recordFailure(..) method has been deprecated on Xcode12+ and it will cause compile error on Xcode12.

To avoid that, added @available block.
In the future, XCTestCase. recordFailure(..) should be replaced with new API, XCTestCase.record(_:).
Video
https://developer.apple.com/videos/play/wwdc2020/10687/
Document
https://developer.apple.com/documentation/xctest/xctestcase/3546549-record

you can use this code instead of just checking if you are on macosx 10.13
if #available(OSX 10.13, *) {
        testCase.recordFailure(withDescription: "\(name): \(failure.reason)", inFile: failure.file, atLine: failure.line, expected: false)
    } else {
        let location = XCTSourceCodeLocation(filePath: failure.file, lineNumber: failure.line)
        let issue = XCTIssue(type: .assertionFailure, compactDescription: "\(name): \(failure.reason)", detailedDescription: nil, sourceCodeContext: .init(location: location), associatedError: nil, attachments: [])
        testCase.record(issue)
    }

please it's very important to merge this pr and create a new release, because some project needed to run on Xcode 12 and on macOS Big Sur like XcodeGen

Hey @kylef - any word?

These changes would render Spectre test failures as successes with the Xcode reporter in many cases. This change won't be accepted in its current state, this must be fixed before this change can be considered.


Add Client constructions

Add the client constructors according to the guidelines for all clients in the library

duplicate of https://github.com/microsoft/typespec/issues/3661