Question: <Model>RelationFilter and <Model>ScalarWhereInput vs. <Model>WhereInput

Hi,
While using the library and attempting to make deep where filter requests, I noticed that you can't filter on deeper than 1 relation on a model. I looked at the template for the schema generation and fiddled with it on my end like this:

Comment out <Model>RelationFilter and <Model>ScalarWhereInput
Tell <Model>Filter to use <ModelRelation>WhereInput instead of <ModelRelation>ScalarFilter
Tell <Model>WhereInput to use <ModelRelation>WhereInput instead of <ModelRelation>RelationFilter for one-to-one relationships

Then, testing locally with a GraphQL request like this:
query MyQuery {
  listEstates(where: {valuation: {mandate: {number: {equals: "1862"}}}}) {
    uuid
    valuation {
      mandate {
        number
      }
    }
  }
}

I was able to get the result I wanted, which is currently not possible with the library's current version. I thought to myself I may as well make a pull request since this is handy, but I figured there could be a reason as to why you deliberately designed things this way, so I'm asking here to see if it's worth considering?
Here are the added commits I'm using currently: https://github.com/maoosi/prisma-appsync/compare/main...Tenrys:prisma-appsync:main
The few changes I made probably broke other things but for now it seems to work just like I need it to.
I am pretty sure I found a bug with field.isUnique and <Model>WhereUniqueInput too... Prisma 4.8.0 doesn't actually let you use fields generated from relations, so I corrected that.

Thanks @Tenrys, yes that's worth considering! Assuming that it doesn't break any other existing relation filters.
It is getting quite difficult to test these types of changes manually, so I've started writing tests for the Prisma to GraphQL Schema conversion (see https://github.com/maoosi/prisma-appsync/issues/84). Once this is ready, it will be easier to test your changes on packages/generator/templates/schema.gql.njk and catch potential issues.
In the meantime, please feel free to open a PR - so that I can review and test the suggested changes.

Thanks @Tenrys, yes that's worth considering! Assuming that it doesn't break any other existing relation filters.
It is getting quite difficult to test these types of changes manually, so I've started writing tests for the Prisma to GraphQL Schema conversion (see https://github.com/maoosi/prisma-appsync/issues/84). Once this is ready, it will be easier to test your changes on packages/generator/templates/schema.gql.njk and catch potential issues.
In the meantime, please feel free to open a PR - so that I can review and test the suggested changes.

@Tenrys Quick follow-up question regarding your changes on packages/generator/src/compiler.ts.

I am pretty sure I found a bug with field.isUnique and WhereUniqueInput too... Prisma 4.8.0 doesn't actually let you use fields generated from relations, so I corrected that.

I've just tested this on my end (using 4.8.0) and Prisma DMMF still includes information on relations (but its only visible on fields with actual relations). See example console log below:
model User {
  posts  Post[]
}

// DMMF.Field
{
    name: 'posts',
    kind: 'object',
    isList: true,
    isRequired: true,
    isUnique: false,
    isId: false,
    isReadOnly: false,
    hasDefaultValue: false,
    type: 'Post',
    relationName: 'PostToUser',
    relationFromFields: [],
    relationToFields: [],
    isGenerated: false,
    isUpdatedAt: false
}

Am I missing something?

Maybe I explained myself incorrectly, but what I meant to say was that the generated input type for a <Model>WhereUniqueInput doesn't match the TypeScript type that Prisma generates under the same name, which creates an error.
Example:
# Generated GraphQL schema
input MandateWhereUniqueInput {
    number: String
    mandateCreatorUuid: String
    valuationUuid: String
}

// Generated Prisma TypeScript type
export type MandateWhereUniqueInput = {
  number?: string
  valuationUuid?: string
}

Which can cause an error like this if you try to use the extra field:

Also, I feel like I should explain myself regarding this commit: https://github.com/maoosi/prisma-appsync/commit/8ca17689b665aa78a00f82438af18f8555d91cc9
With Prisma schema definitions as such:
model Valuation {
  ...
  mandate     Mandate?
  ...
}

model Mandate {
  ...
  valuation          Valuation       @relation(fields: [valuationUuid], references: [uuid])
  valuationUuid      String          @unique
  ...
}

// Not sure if other fields are actually relevant for this bug

I got this generated ValuationWhereInput:
input ValuationWhereInput {
    ...
    mandate: MandateFilter
    ...
}

// References a one-to-many filter, which doesn't match the specified type of relationship

input MandateFilter {
    some: MandateScalarWhereInput
    every: MandateScalarWhereInput
    none: MandateScalarWhereInput
}

which prompted me to change the function, which gave me the appropriate results on my end.

Hey @Tenrys,
1/ Issue: GraphQL input WhereUniqueInput shouldn’t include Relation fields
# Generated GraphQL schema
input MandateWhereUniqueInput {
    number: String
    mandateCreatorUuid: String
    valuationUuid: String
}

You are right on this one, mandateCreatorUuid shouldn’t be part of MandateWhereUniqueInput and https://github.com/maoosi/prisma-appsync/commit/865c679cb9dcf798b5238cc83e9ba5d9a43b7243 seems to be the right solve.
2/ Feature: Support for deeply nested relation filters
Right now, you can already do something like:
# relation to one (only one author per comment)
listComments(
  where: {
    author: {
      username: { equals: "username" }
    }
  }
)

Or:
# relation to many (many posts per user)
listUsers(
  where: {
    posts: {
      every: {
        published: { equals: true }
      }
    }
  }
)

However, deeply nested relation filters aren’t supported yet. So the below will not work (yet):
listComments(
  where: {
    author: {
      # deeply nested relation filter
      posts: {
        every: {
          published: { equals: true }
        }
      }
    }
  }
)

listUsers(
  where: {
    posts: {
      every: {
        # deeply nested relation filter
        comments: {
          every: {
            message: { startsWith: 'hello' }
          }
        }
      }
    }
  }
)

From your example below, I believe the generated filter is correct as it is a one-to-many relation (many possible mandates can be associated to the same valuation):
# References a one-to-many filter, which doesn't match the specified type of relationship
input MandateFilter {
    some: MandateScalarWhereInput
    every: MandateScalarWhereInput
    none: MandateScalarWhereInput
}

However, what’s missing is the nested relation filter, because MandateScalarWhereInput does not expose deeply nested relation fields.
From what I understand, packages/generator/templates/schema.gql.njk seems to be an attempt on making it work.
I’ll finalise writing some test for nested relation filter queries and then review your PR accordingly. Thanks for submitting!

Quickly replying from my phone:

From your example below, I believe the generated filter is correct as it is a one-to-many relation (many possible mandates can be associated to the same valuation):

But I didn't define it as such in my Prisma schema, Valuation only has a single reference to a single mandate, not a list of mandates, and only one mandate can be assigned to one specific valuation as determined by the @unique directive.

The generated GraphQL Schema using the following Prisma Schema (this is the one used for Unit Testing) seems correct: https://github.com/maoosi/prisma-appsync/blob/main/tests/prisma/schema.prisma
Note that the below input Filter will be generated for all Models, regardless of whether it is required or in use:
input <Model>Filter {
    some: <Model>ScalarWhereInput
    every: <Model>ScalarWhereInput
    none: <Model>ScalarWhereInput
}

That said, it is possible that there is another issue related to this. Would you mind sharing your entire Prisma Schema so that I can replicate the issue?


support for indirect/flow counters

support for indirect/flow counters to read and reset counters

Verified following

PSA/PNA flow counters.
sample L3 LPM example


how to replace text in all pages of pdf？

here is the sample code for replace text in pdf use aspose-pdf.jar, it can only replace the first page of pdf.
public static void replaceTextOnAllPages() {   // Open document   Document pdfDocument = new Document("source.pdf");   // Create TextAbsorber object to find all instances of the input search phrase   TextFragmentAbsorber textFragmentAbsorber = new TextFragmentAbsorber("sample");   // Accept the absorber for first page of document   pdfDocument.getPages().accept(textFragmentAbsorber);   // Get the extracted text fragments into collection   TextFragmentCollection textFragmentCollection = textFragmentAbsorber.getTextFragments();   // Loop through the fragments   for (TextFragment textFragment : (Iterable<TextFragment>) textFragmentCollection) {     textFragment.setText("New Pharase");   }   pdfDocument.save("Updated_Text.pdf"); }
now I want to replace the text for all pages in pdf, how can I do?

@anyspa
The below line in the above code snippet is supposed to work for all pages:
pdfDocument.getPages().accept(textFragmentAbsorber);

Are you using the latest version and with a valid license? Can you please create a post in our official support forum along with your sample file so that we can test the scenario in our environment and address it accordingly.


Interp after ev does not work?

Seem like applying ev to a DG field (so all components are modified) and the doing an interpolation results in an error. For example, the following command does not work with the attached BP file:
pgkyl -f s1-recovery-dg-diff_f_0.bp ev "f0 -3.8 exp *" interp
(Unzip the file as github does not allow uploading bp files)
s1-recovery-dg-diff_f_0.bp.zip

I always thought it was necessary to interp first.
On Sun, 3 Nov 2019 at 05:43, Ammar<EMAIL_ADDRESS>wrote:

Seem like applying ev to a DG field (so all components are modified) and
the doing an interpolation results in an error. For example, the following
command does not work with the attached BP file:
pgkyl -f s1-recovery-dg-diff_f_0.bp ev "f0 -3.8 exp *" interp
(Unzip the file as github does not allow uploading bp files)
s1-recovery-dg-diff_f_0.bp.zip
https://github.com/ammarhakim/postgkyl/files/3801613/s1-recovery-dg-diff_f_0.bp.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ammarhakim/postgkyl/issues/1?email_source=notifications&email_token=AAQ6DKFWDLCTEVNC2AG7LCTQR3BOTA5CNFSM4JILKJA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HWOGGBA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQ6DKA2W5LJJE4XWWEW5BTQR3BOTANCNFSM4JILKJAQ
.

No need to interp first. For example, all I want to do is rescale the expansion coefficients and then do something with them. Here, in particular, I want to subtract them from another DG field and then compute sum of squares (L2 norm). Just rescaling all components via "ev" should not cause postgkyl to barf.

'ev' should now be passing metadata to the resulting data set so 'interp' can be used after 'ev'


azure-docs

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@5911224141 - Thanks for brining this to our attention. We will investigate it further and update you shortly.

@5911224141 - Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

@5911224141 -
Since we have not heard back from you we will now proceed to close this thread.
However if you can share additional information regarding the documentation you are referring and circle back on this thread , we will gladly reopen the issue and continue the discussion. Thank you.


Aggregate projection not being deleted when DeleteEvent is being fired and set as Async

Hey there . I'm currently trying to have the async daemon delete a projection row when a specific event is fired.
The projection row is correctly created but never deleted.
If i do change the projection lifecycle to ProjectionLifecycle.Inline. I can see the row gets deleted as part of the transaction when the delete event is being fired.
Marten version : 4.0.0-alpha.10
Here is the daemon setup :
storeOptions.Events.Daemon.Mode = DaemonMode.HotCold;

Here is the projection registration
storeOptions.Events.Projections.Add<InspectionsPendingViewProjection>(ProjectionLifecycle.Async);

  public class InspectionsPendingViewProjection : AggregateProjection<InspectionPending>
    {

        public InspectionsPendingViewProjection()
        {
            DeleteEvent<InspectionCancelled>((d) => { return true; });
        }

        public void Apply(InspectionPending view, InspectionRequested @event)
        {
            view.Id = @event.Id;
            view.Address = @event.Address;
        }

    }
 public class InspectionPending
    {
        public Guid Id { get; set; }
        public string Address { get; set; }
    }

I doubled checked that events are there in the mt_events table :

and this is the projection :

Also the daemon logs :

I might ask you to pull the latest the next time we're able to publish a Nuget (hopefully an RC), but otherwise, I'm closing this for now:(

@julienperignon I did make a change to the daemon internals in how it tracked progress to make the new tests pass that could maybe have caused some events to be skipped.


Expand table

Hi @hjalmers
I have a table like this. The user can expand all the rows in the table. But when the table is lazy loading and changes the page the rows not showing expanded. There is any configuration to do it?

Hi @mayraGL, not sure if I get what you’re trying to do but do you want to persist the state of the table rows i.e. which table rows are expanded when a user refreshes the table or uses pagination?
When you’re lazy loading the data you have two options:

Persist the state on the the server
Let’s say the user clicks on a row to get more details, if you make a server request to fetch the details using an id, you could toggle a property for that item and return the state from the server and use it to determine if the row should be expanded or not.

Persist the state in the client
Same as the first option but instead of persisting the state on the server you store it locally in a service or local storage etc. and next time you fetch data you use the id’s stored locally to determine if the row should be expanded or not.

If I remember it correctly there should be an option to do number 2 by specifying a unique id that should be used but I have to look it up when I have access to the code.
But did I get your question right?

@Hi @hjalmers. I tried to persist in the client like this but didn't works


Escape (somehow) invalid chars in tag content

I am trying to integrate a webservice not very well done, so I am receiving some xml like this:
<sometag> this is the tag content and has a < char </sometag>
without cdata.
When trying to parse this it throws invalid char error. Is there anything I can do?

You can escape the invalid XML into < or wrap the entire text node in CDATA which might be the easier thing to do.

But how do I get there in the first place. Imagine I have something like this.
  <root>     <childOne>Hello there</childOne>     <childTwo> I am retarded < ho ho ho (Frieza's laugh)</childTwo>   </root>
Now, before any parsing this is merely a string. How do I go about wrapping childTwo content in CDATA? or escape it's content.

I see that it is a problem @ybrodsky but I also see that it is a problem that xml2js can't do much about. I think xml2js requiring well-formed XML is not to much to ask of (after all, it is called xml2js, not random text with < and > 2js), so if you need to parse things that aren't XML you'll have to do some preprocessing. Sorry, but xml2js can't just handle every single case.

This was some time ago. After writing here I complained with the people who maintains that service and they replied: 'we chose to do it that way'. Like....wtf you chose to do it wrong?
No point discussing with that kind of people.
Anyway thanks for the follow up


[AMBARI-24059] Ambari Views auto create instance should support matching to all known stacks

What changes were proposed in this pull request?
The Ambari Views framework currently provides a mechanism to auto-create view instances when Ambari Services are added to a cluster.  The "stack-id" attribute in view.xml is used to configure the stack(s) that will match to a given view instance for auto-creation.  The current implementation provides support for using the wildcard character ("*") in order to match stack versions, but not stack names.  This means that the current implementation has a limitation in that a given view cannot be applied to multiple stack names (Examples: "HDP", "HDF", etc).
The current mapping in view.xml is as follows:
<auto-instance>
        <name>TEST_AUTO_INSTANCE</name>
        Test View
        <stack-id>HDP-*</stack-id>
:
    </auto-instance>

This patch introduces a minor change to the Ambari Views ViewRegistry in order to support a new wildcard ("") mapping for the "stack-id" attribute.  When "stack-id" is now configured to use "", the view defined in this view.xml will match to all known stacks deployed on the Ambari cluster.
The following is an example of the new value applied to the same example:
<auto-instance>
        <name>TEST_AUTO_INSTANCE</name>
        Test View
        <stack-id>*</stack-id>
:
</auto-instance>

This patch also adds a new unit test to verify this change, and some minor refactoring to the ViewRegistry unit test case.
How was this patch tested?

The ambari-server and ambari-views unit tests were run, and both suites pass completely with this patch applied.

Deployed a 3-node cluster with Ambari <IP_ADDRESS> and an HDF management pack.  After the deployment completed, I added a new service to the Ambari cluster that was configured with "*" in the service view's view.xml, and I verified that the associated view was auto-created, and that it was available via the Ambari UI.  I also verified that other un-related views could be created and are viewable via the Ambari UI.

Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2653/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2654/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2666/
Test PASSed.


No module named 'pearson_pdf'

joel@thinkpad-e580:~$ pip install pearson_pdf
Collecting pearson_pdf
  Using cached pearson_pdf-1.0.1-py3-none-any.whl (2.7 kB)
Requirement already satisfied: pillow in /usr/lib/python3/dist-packages (from pearson_pdf) (8.1.2)
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from pearson_pdf) (2.25.1)
Installing collected packages: pearson-pdf
Successfully installed pearson-pdf-1.0.1
joel@thinkpad-e580:~$ pearson_pdf
Traceback (most recent call last):
  File "/home/joel/.local/bin/pearson_pdf", line 5, in <module>
    from pearson_pdf import __main__
ModuleNotFoundError: No module named 'pearson_pdf'

it hasn't downloaded any code:
joel@thinkpad-e580:~/.local/lib/python3.9/site-packages$ ls | grep pearson_pdf
pearson_pdf-1.0.1.dist-info

for comparison:
joel@thinkpad-e580:~/.local/lib/python3.9/site-packages$ ls | grep flake8
flake8
flake8-3.9.2.dist-info

found it:
>>> find_packages()
['tests', 'pearson_pdf']
>>> find_packages(where="pearson_pdf")
[]

not fixed


Add back path-normalization

Path-normalization is needed on windows because inputOutputFilesMap and sourceFile.fileName have different slashes (forward vs backward).
Got removed in 9de85e0829936199cc5e4a372250e7c625e54452
Fixes #71

I'll cut a release after getting this merged.


Words are automatically being converted to lowercase

Words are automatically being converted to lowercase
This first happened on Windows about a month ago - thought it was a Windows specific issue. Suddenly started happening on OS X this weekend.
It doesn't happen in Safe Mode. I uninstalled atom-ctags and it still happened. Disabled most of the autocomplete plugins and it still happened
Steps to Reproduce
Think this GIF tells the story

Basically I am trying to Capitalize a word
As soon as I capitalize the word "Making" autocomplete seems to kick in and replace it with the lowercase version
It seems I can make other characters uppercase - just not the first character

Sorry to put this here since i know its prob a problem with some sub-package but i've tried disabling all I could think of (uninstalled atom-ctags as mentioned) with no change.
Versions
OS X 10.11.5
➜  atom --version
Atom    : 1.8.0
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1
➜  apm --version
apm  1.9.2
npm  2.13.3
node 0.10.40
python 2.7.11
git 2.8.3

You can try using the package-cop package to determine which one of your packages is causing the issue.


L515 Camera point_cloud and aligned_depth map frames drop (No stream match for pointcloud chosen texture Process - Color)

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ L515}

Firmware Version
(<IP_ADDRESS>.01)

Operating System & Version
{ Linux (Ubuntu 18.04)

Kernel Version (Linux Only)
(4.15.0)

Platform
PC

SDK Version
{ 2.53.1}

Language
{python }

Segment
{Robot}

Issue Description
I'm using the L515 realsense camera for recording into a rosbog the RGB images (topic: /camera/color/image_raw) with the associated point cloud(/camera/depth/color/points) or aligned depth map (Camera/aligned_depth_to_color/image_raw).
It works well but during a record of 1 min there is a kind of "Frame drop" and if the record is longer we got multiples frames drop approximately one per minutes.
First problem: When we are recording the pointcloud at first everything goes well, but at a random moment we got the message: No stream match for pointcloud chosen texture Process - Color and that cause like a 10 frames drop for the point cloud that means that for 10 rgb frames we don't have any point cloud that are taken.
Second problem but maybe related to the first one: When we record using the arg align_depth:= true we got the same problem but the only things that change is that we don't have any warning message
This is the parameters that we are using for the point cloud when we use roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
PARAMETERS

/camera/realsense2_camera/accel_fps: -1
/camera/realsense2_camera/accel_frame_id: camera_accel_frame
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: False
/camera/realsense2_camera/aligned_depth_to_color_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye2_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra2_frame_id: camera_aligned_de...
/camera/realsense2_camera/allow_no_texture_points: False
/camera/realsense2_camera/base_frame_id: camera_link
/camera/realsense2_camera/calib_odom_file:
/camera/realsense2_camera/clip_distance: -2.0
/camera/realsense2_camera/color_fps: -1
/camera/realsense2_camera/color_frame_id: camera_color_frame
/camera/realsense2_camera/color_height: -1
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: -1
/camera/realsense2_camera/confidence_fps: -1
/camera/realsense2_camera/confidence_height: -1
/camera/realsense2_camera/confidence_width: -1
/camera/realsense2_camera/depth_fps: -1
/camera/realsense2_camera/depth_frame_id: camera_depth_frame
/camera/realsense2_camera/depth_height: -1
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: -1
/camera/realsense2_camera/device_type:
/camera/realsense2_camera/enable_accel: False
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_confidence: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye1: False
/camera/realsense2_camera/enable_fisheye2: False
/camera/realsense2_camera/enable_fisheye: False
/camera/realsense2_camera/enable_gyro: False
/camera/realsense2_camera/enable_infra1: False
/camera/realsense2_camera/enable_infra2: False
/camera/realsense2_camera/enable_infra: False
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_pose: False
/camera/realsense2_camera/enable_sync: False
/camera/realsense2_camera/filters: pointcloud
/camera/realsense2_camera/fisheye1_frame_id: camera_fisheye1_f...
/camera/realsense2_camera/fisheye1_optical_frame_id: camera_fisheye1_o...
/camera/realsense2_camera/fisheye2_frame_id: camera_fisheye2_f...
/camera/realsense2_camera/fisheye2_optical_frame_id: camera_fisheye2_o...
/camera/realsense2_camera/fisheye_fps: -1
/camera/realsense2_camera/fisheye_frame_id: camera_fisheye_frame
/camera/realsense2_camera/fisheye_height: -1
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: -1
/camera/realsense2_camera/gyro_fps: -1
/camera/realsense2_camera/gyro_frame_id: camera_gyro_frame
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/imu_optical_frame_id: camera_imu_optica...
/camera/realsense2_camera/infra1_frame_id: camera_infra1_frame
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra2_frame_id: camera_infra2_frame
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra_fps: 30
/camera/realsense2_camera/infra_height: 480
/camera/realsense2_camera/infra_rgb: False
/camera/realsense2_camera/infra_width: 848
/camera/realsense2_camera/initial_reset: False
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/linear_accel_cov: 0.01
/camera/realsense2_camera/odom_frame_id: camera_odom_frame
/camera/realsense2_camera/ordered_pc: False
/camera/realsense2_camera/pointcloud_texture_index: 0
/camera/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
/camera/realsense2_camera/pose_frame_id: camera_pose_frame
/camera/realsense2_camera/pose_optical_frame_id: camera_pose_optic...
/camera/realsense2_camera/publish_odom_tf: True
/camera/realsense2_camera/publish_tf: True
/camera/realsense2_camera/reconnect_timeout: 6.0
/camera/realsense2_camera/rosbag_filename:
/camera/realsense2_camera/serial_no:
/camera/realsense2_camera/stereo_module/exposure/1: 7500
/camera/realsense2_camera/stereo_module/exposure/2: 1
/camera/realsense2_camera/stereo_module/gain/1: 16
/camera/realsense2_camera/stereo_module/gain/2: 16
/camera/realsense2_camera/tf_publish_rate: 0.0
/camera/realsense2_camera/topic_odom_in: odom_in
/camera/realsense2_camera/unite_imu_method:
/camera/realsense2_camera/usb_port_id:
/camera/realsense2_camera/wait_for_device_timeout: -1.0
/camera/rgb_camera/auto_exposure: False
/camera/rgb_camera/auto_exposure_priority: False
/camera/rgb_camera/exposure: 200
/rosdistro: melodic
/rosversion: 1.14.13 NODES
  /camera/
    realsense2_camera (nodelet/nodelet)
    realsense2_camera_manager (nodelet/nodelet) auto-starting new master
process[master]: started with pid [6516]
ROS_MASTER_URI=http://<IP_ADDRESS>:11311/ setting /run_id to 85635e46-bc12-11ed-943e-2c59e50350ac
process[rosout-1]: started with pid [6590]
started core service [/rosout]
process[camera/realsense2_camera_manager-2]: started with pid [6598]
process[camera/realsense2_camera-3]: started with pid [6605]
[ INFO] [1678102326.358122025]: Initializing nodelet with 8 worker threads.
[ INFO] [1678102326.885985000]: RealSense ROS v2.3.2
[ INFO] [1678102326.886034677]: Built with LibRealSense v2.53.1
[ INFO] [1678102326.886055621]: Running with LibRealSense v2.53.1
[ INFO] [1678102326.923774930]:
[ INFO] [1678102327.153499981]: Device with serial number f1151068 was found. [ INFO] [1678102327.153627180]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/video4linux/video0 was found.
[ INFO] [1678102327.153685332]: Device with name Intel RealSense L515 was found.
[ INFO] [1678102327.154625671]: Device with port number 4-3 was found.
[ INFO] [1678102327.154666429]: Device USB type: 3.2
[ INFO] [1678102327.159479408]: getParameters...
[ INFO] [1678102327.360047602]: setupDevice...
[ INFO] [1678102327.360108848]: JSON file is not provided
[ INFO] [1678102327.360152875]: ROS Node Namespace: camera
[ INFO] [1678102327.360226653]: Device Name: Intel RealSense L515
[ INFO] [1678102327.360288187]: Device Serial No: f1151068
[ INFO] [1678102327.360331749]: Device physical port: /sys/devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/video4linux/video0
[ INFO] [1678102327.360382122]: Device FW version: <IP_ADDRESS>
[ INFO] [1678102327.360448536]: Device Product ID: 0x0B64
[ INFO] [1678102327.360511192]: Enable PointCloud: On
[ INFO] [1678102327.360590164]: Align Depth: Off
[ INFO] [1678102327.360675361]: Sync Mode: On
[ INFO] [1678102327.360847291]: Device Sensors:
[ INFO] [1678102327.361707807]: L500 Depth Sensor was found.
[ INFO] [1678102327.365257533]: RGB Camera was found.
[ INFO] [1678102327.365524515]: Motion Module was found.
[ INFO] [1678102327.365632274]: Add Filter: pointcloud
[ INFO] [1678102327.366626651]: num_filters: 1
[ INFO] [1678102327.366656389]: Setting Dynamic reconfig parameters.
[ INFO] [1678102327.494830300]: Done Setting Dynamic reconfig parameters.
[ INFO] [1678102327.498622661]: depth stream is enabled - width: 640, height: 480, fps: 30, Format: Z16
[ INFO] [1678102327.501062923]: color stream is enabled - width: 1280, height: 720, fps: 30, Format: RGB8
[ INFO] [1678102327.501153952]: setupPublishers...
[ INFO] [1678102327.510460813]: Expected frequency for depth = 30.00000
[ INFO] [1678102327.604335297]: Expected frequency for color = 30.00000
[ INFO] [1678102327.663150045]: setupStreams...
[ INFO] [1678102327.727845113]: SELECTED BASE:Depth, 0
[ INFO] [1678102327.929416785]: RealSense Node Is Up!
[ WARN] [1678102327.931582246]:
[ WARN] [1678102327.931725496]: frame's time domain is HARDWARE_CLOCK. Timestamps may reset periodically.
[ INFO] [1678102477.668086942]: publishing unordered pointcloud.
[ WARN] [1678102515.212162012]: No stream match for pointcloud chosen texture Process - Color

Is someone have any idea for resolving that problem?

Hi @julienfal  You are correct that the message No stream match for pointcloud chosen texture Process - Color
coincides with frame drops, as advised at https://github.com/IntelRealSense/realsense-ros/issues/588#issuecomment-457890773 by the Intel RealSense team member who developed the ROS1 wrapper.
You could try defining a roslaunch instruction with a custom stream configuration that has a lower resolution and FPS to see whether this reduces the frequency of the warnings.  For example:
roslaunch realsense2_camera rs_camera.launch filters:=pointcloud depth_width:=640 depth_height:=480 depth_fps:=15 color_width:=640 color_height:=480 color_fps:=15
If you are using the pointcloud filter then you should not need to use align_depth:=true as the pointcloud should automatically map color onto the depth coordinates anyway.  Having both the pointcloud filter and align_depth enabled may cause performance issues.

Thank you for your quick response.
Yes of course we didn't enable the point cloud and align_depth at the same time.
However, the depth fps cannot be changed to less than 30 for this L515 camera.
We tried with your parameters but with 30 fps for the depth frame but we still have the frame drop.
Is another way to change the fps of the depth sensor, maybe with a python script ?

You are correct about the 30 FPS limit for the depth stream on the L515 camera.  My apologies, thanks for pointing that out.
The rate at which messages are published can be modified in ROS by setting a rate, though doing so may not be necessary for this particular problem.
https://roboticsbackend.com/ros-rate-roscpy-roscpp/#:~:text=ROS Rate explained,-Let's start with
Does performance after a minute of recording improve if you add initial_reset:=true to your roslaunch instruction to reset the camera at launch?
Does it improve if you add global_time_enabled:=true to enable Global Time?

It seems that after the initial_reset command now the point cloud is correctly publish during at least 53 sec and can go to 1 min without error but still have the error after that time ( I made the test approximately 10 times).
After doing a launch with the initial_reset I launch without that but the point cloud still good until 53 sec, we got that because we ran with the reset before ?
The global_time_enabled changes nothing to the problem.
if we can reach 1min 20 without any problem it would be perfect but I don't know if it's possible. I also tried that with a lower camera resolution but that changes nothing.

Are you recording the rosbag in ROS using the rosbag record function please?  This function has a parameter called --split that can be used to set a maximum recording duration or file size.  When that defined limit is reached, the recording is automatically closed and a new bag recording automatically starts and continues onwards until the next time that the limit is reached.
If having more than one bag file is acceptable to you then closing and re-opening the recording process may correct the loss of frames that you are experiencing at the one minute point and allow a longer period to be recorded across multiple bags.
Examples of --split commands for time and file-size are provided below.
--split

Split the bag when maximum size or duration is reached

$ rosbag record --split --size=1024 /chatter
$ rosbag record --split --duration=30 /chatter
$ rosbag record --split --duration=5m /chatter
$ rosbag record --split --duration=2h /chatter

Okay I'll try that, my command line for recording was : rosbag record -b 0 --duration=70 /topics

I tried and it stills dropping around 58 sec, do you think it could be an hardware problem in the camera? Like a setting to change?

It sounds like it could be a memory leak, where a computer's available memory capacity is progressively consumed over time during the running of an application until that application becomes unstable and then may freeze / crash.  You can test for a memory leak in Ubuntu by using a system monitoring tool such as htop to monitor available memory over time during the recording process to see if the free memory is declining.

It seems that the memory stays ok during all the process at first before starting the launch and the recording the memory is at 3.5G/15.6G and at during it goes to 4.20G/15.6G.
I'm stopping for today but I'll be able tomorrow to try other things. Thanks for all your answers today !

You are very welcome.  I look forward to your next update.  Good luck!

Hi!
A little Resume from yesterday : As you told me when I add initial_reset:=true the point cloud last at least 53 sec.
But I still don't know why it stopped.
All the test that we made yesterday was with these lines adding in the launch file

 /camera/rgb_camera/auto_exposure_priority: false
 /camera/rgb_camera/auto_exposure: false
 /camera/rgb_camera/exposure: 200

I made some test this morning when i try different launch file configuration here are my tests:
1st test: I remove all the 3 lines

Consequences: I don't have any frame drop for the point cloud but i can't have a stable frame fps even if I launch the camera with roslaunch realsense2_camera rs_camera.launch filters:=pointcloud color_width:=1280 color_height:=720 color_fps:=30 initial_reset:=true it looks like at first it stays at 30 fps for 3 sec and after it just goes to 15 fps naturally

2nd test: I just add   /camera/rgb_camera/auto_exposure_priority: false  in the launch file

Consequences: the Frame rate is now consistent when I want 30 fps it stays at 30 but I have the frame drop much more quickly like around 20 sec and even sometimes in less than 10 sec
If i try using 15 fps everything works well, no frames drop but i think 15 fps is too low for my application so i really need 30 fps

3th test: I just add  /camera/rgb_camera/auto_exposure: false   /camera/rgb_camera/exposure: 200  in the launch file

Consequences: The frame rate is stable at 30 fps but point cloud frame drop around after 53 sec

4th test: I just add  /camera/rgb_camera/exposure: 200  in the launch file

Consequences : Frame rate stable at 30 fps but point cloud drop and still good for 15 fps

5th test : I just add  /camera/rgb_camera/auto_exposure_priority: false
 /camera/rgb_camera/auto_exposure: false  in the launch file

Consequences: with 30 fps point cloud drop much more quickly around 25 sec, with 15 fps point cloud still good

All of this test was launch with the initial_reset:=true each time.
I don't really get it because normally the Camera should be able to run the point cloud with 30 fps according to the datasheet and I don't think that the problems come from my PC. Do you have other idea that I can test to see if that improve something ? It looks like setting manually the exposure in the launch file help already to stabilize the point cloud.

If depth and color streams are enabled and auto-exposure is enabled then it can result in a drop in FPS, such as a halving.  A fix for this is to set auto-exposure to manual and disable an RGB option called auto_exposure_priority.  This forces the SDK to try to maintain the FPS at a constant rate instead of being permitted to vary, as described at https://github.com/IntelRealSense/librealsense/issues/10051

When you say auto-exposure to manual it just putting that settings equal to False and after giving a manual exposure value? If yes I already tried that but still have the frame drop for the point cloud after 50 sec.

it seems that it can be a problem of exposure time because when I change the value of that this impact a lot the frame drop.
What is the best exposure time for 30 FPS ? Actually it is set to 200 and when i try to go to 400 i loose the consistent fps speed but i have the consistent point cloud and when i try to go lower to 200 I have the consistent fps speed but i still have the point cloud frame drop

Using a manual exposure can cause FPS to drop if the value is within a certain range, as described by a RealSense team member at https://github.com/IntelRealSense/librealsense/issues/1957#issuecomment-400715579

Depth exposure is not customizable on L515 lidar depth cameras like it is on the 400 Series stereo cameras as the L515 is a different camera technology.  L515 uses a short exposure time of <100 ns per depth point.
RGB exposure is customizable though and is '156' by default, so 156 would be the optimal exposure time for RGB.  With the 200 and 400 values that you are using, it sounds as though it is RGB exposure that you are configuring.

Hi @julienfal  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


fix(background): secondary color variable not available anymore

The color variable $secondary has been deleted in the commit with the hash 56be7d6 (marked as BREAKING_CHANGE).
This means that the following classes are no longer available in the entire CWF:

bg-secondary
btn-secondary (class is available, but does not provide a background color anymore)
text-secondary
border-secondary

However, these classes are still used in the package web-demo, but without the desired effect.
@gfellerph we need to discuss, how we want to deal with it.

@oliverschuerch replaced classes that still were in the demo. This color should not be used anymore (we have the grayscales as replacement). The secondary button intentionally has a transparent background to make it work on colorful backgrounds.


[help] Adding pathseg to Vue/Gridsome project

I know what I need (to add pathseg) as a node_module to my project, however, struggling to work out what's next.
I've installed the module but when trying to import or require it in a Vue file, I get error: 'window is not defined' inside pathseg.
What is it I'm missing?
TYIA

Hi @484-studio,
pathseg and tsParticles are not SSR libraries since they are client-side only.
Try reading here, that article explains how to add non-SSR libraries to a Gridsome project

That was much simpler than I thought - thanks so much!


Add main property to bower file

Fixes https://github.com/HubSpot/tooltip/issues/13

Thanks for using tooltip. I know developing on this project has been a bit delayed, so I'm planning a major update to the project in https://github.com/HubSpot/tooltip/pull/34 which will include this fix. If you don't mind, I'm going to close this PR in favor of that one as it will encompass a lot of changes.


Bind PopupMenu.get_current_index() to ClassDB  [3.2]

Addresses https://github.com/godotengine/godot-proposals/issues/790.  Retrieves current index mouse_over from PopupMenu and exposes it to the end-user.
Please let me know if I should also make relevant changes to the master branch and if it should be a separate PR.

Please let me know if I should also make relevant changes to the master branch and if it should be a separate PR.

In our development workflow, all new changes should go to the master branch in priority, as it's the one that will be used for all future Godot releases.
The stable 3.2 branch can then have the change cherrypicked by release maintainers, if it's deemed appropriate. The only exception is for changes which are specific to 3.2 and not relevant for 4.0 and later, but this is not the case. Could you redo the PR for the master branch?
See also our Git howto for the PR workflow to make sure that you don't get these "Merge branch ..." commits when updating your fork.

Yes, i can make the changes on the master branch, and submit it as another PR in case this one can still be useful for cherry picking to the 3.2 branch.

I've created a new PR which uses the master branch.  Closing this issue for now, although I'm still hopefully requesting a backport to 3.2   🙏


Flattr

There have been quite some flattrs for this repository, so you should create an account there and claim them: https://flattr.com/thing/2095203

Done, thanks. I'll try to figure out how this thing works and spend the points, if any, on other interesting open-source projects.

Wow, that was quick, thanks for being part of it!


Loading stream

Never loads. It says, "loading is taking longer than expected." (after about an hour)

What OS are you running?

@alynrockwood in addition to the OS, are you running this through the KCMA (the desktop app) or via a web browser - and if a web browser, which one? Are you able to open the debug console (in the app, Right-click, click on "Inspect element", and then select the "Console" tab) and check for errors? Likely suspects here are anything that says "701" or "Too many active connections".

I'm on Mac, running on Safari browser. The only thing I see in the Console
tab (in the pink highlight area) is the word "Fu"
On Mon, Nov 20, 2023 at 12:14 PM Paul Tagliamonte @.***>
wrote:

@alynrockwood https://github.com/alynrockwood in addition to the OS,
are you running this through the KCMA (the desktop app) or via a web
browser - and if a web browser, which one? Are you able to open the debug
console (in the app, Right-click, click on "Inspect element", and then
select the "Console" tab) and check for errors? Likely suspects here are
anything that says "701" or "Too many active connections".
—
Reply to this email directly, view it on GitHub
https://github.com/KittyCAD/modeling-app/issues/1088#issuecomment-1819486888,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEAZGH4SPK5HDPSKFUYU4ELYFOFVRAVCNFSM6AAAAAA7RHYUEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJZGQ4DMOBYHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

alyn let us know if you are still having issues but i think we are good here!


Always build the sha

The deployment just now (1.1.5) didn't go through because the tag pipeline ended up coming before the build - and therefore the re-tagging failed.
This ensure that we're always building the revision so that tags can't fail if they are scheduled before the corresponding build-sha has completed. While it does a duplicate build for that tag revision it's just safer.
I've tr-triggered the deployment for 1.1.5 and it should go through shortly.

I'll let you merge and re-tag this.

I'll just merge, no need for another deploy really.

Needed another tweak: staging deploys also tried to access the image before it was built. I've added a 10 min retry loop to ensure it doesn't fail if the build isn't done yet.


Update License

This PR updates the license information per our discussion in https://github.com/pangeo-forge/staged-recipes/pull/156#issuecomment-1188085479.

@cisaacstern, do you happen to know why the pangeo-bot is complaining about the validity of the recipe?

@andersy005, I think this is because there's a bug in this (old) backend where the bot only looks for recipes among changed files in the head ref, and doesn't understand that the recipe might be unchanged. For the purposes of this PR, you can just ignore the bot. We'll fix this in the forthcoming GitHub App backend.

thank you for the clarification! feel free to merge this


Separate build and source directories for Sphinx build

The source and build directories were the same under docs since it's matched to PySpark's and simple.
Looks our documentation dir is going to be a bit complicated than expected. This PR proposes to separate build and source directory. This matches to many projects like Pandas.

(I am trying to add Pandas' custom theme that resolves some issues. This PR makes easier for me to port that into Koalas)

I'd merge this. Thanks!

Thanks for close review always!


Timestamp Serialization Should Not Be Fixed to Nanoseconds

#272 ports some internal code to APIs, part of this is a TODO to make Timestamp serialization to be not fixed to nanoseconds.
When searching for prior issues, I found #17, but I am not sure if that is different or already resolved (since it indicates skipping fractional seconds).  @zslayton can probably confirm this.

So this means that if there exists sub-second precision, that precision is always nine digits (i.e. nanoseconds)?
Originally posted by @almann in https://github.com/amzn/ion-rust/pull/272#discussion_r643643079

Prior to #272, the binary reader/writer only worked with DateTime<_>, which represents its fractional seconds as nanoseconds. Both reading and writing had a TODO to support other levels of precision.
Now that we're supporting reading and writing Timestamps (which natively support setting/getting the precision), assuming nanoseconds on this code path no longer makes sense.


File error-handling.md - Translation  complete

File error-handling - Translation complete

Thanks! :D :beers:


Input Liabilities

Liabilities can just be an account. There will be rules to model the interest rate on a liability.


Incorrect resolution of SINK url

The dataflow module resolves the SINK url based on the keys of the output documents. This would result in a concurrency issue as the same entity group might be processed in different sink apps.
For example lets consider two resource instances with ids a278edbb-5fad-4395-bd74-f1599aca745e and 0dc143c1-d88e-4d07-afd0-1ce6973d8649 in organization a3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27 with two instances of aggregator in the pipeline.
If the accumulator produces the output documents with ids

k/a3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27/a278edbb-5fad-4395-bd74-f1599aca745e/external:bbeae239-f3f8-483c-9dd0-de6781c38bab/basic/basic-object-storage/object-rating-plan/object-pricing-basic/t/0001467759632668 (SINK Partition 0)
k/a3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27/0dc143c1-d88e-4d07-afd0-1ce6973d8649/external:bbeae239-f3f8-483c-9dd0-de6781c38bab/basic/basic-object-storage/object-rating-plan/object-pricing-basic/t/0001467759632668 (SINK Partition 1)

each of them gets processed by different instances of aggregator causing the aggregation for org a3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27 to happen in parallel and might result in concurrency issues.
Update:
@jsdelfino  has already submitted a pull request https://github.com/cloudfoundry-incubator/cf-abacus/pull/359 to address this problem

Pull request #359 adds the ability to optionally set on a dataflow two new functions (sink.keys and sink.times) that can produce sink partitioning keys/times separate from the dataflow's output keys/times.
That pull request also makes use of that new capability in the meter, accumulator and aggregator services to configure keys/times that will address the correct sink partitions.
Note that I have not been able to reproduce the problem reported in this issue, even with various combinations of our perf tests, and that's the main reason why it's just a pull request at this point (I understand the theory behind the concurrency problem described by Raj's but have not seen evidence of it). So, before merging pull request #359 the team will need to effectively show evidence of the problem, probably with a new specific test, and ensure that the changes actually fix it.

Pull request https://github.com/cloudfoundry-incubator/cf-abacus/pull/363 includes tests for running into concurrency issues and patch from pull request https://github.com/cloudfoundry-incubator/cf-abacus/pull/359 solves the issue.

Resolved with https://github.com/cloudfoundry-incubator/cf-abacus/commit/a4d28325ba8ab1d9d91ce9fcfeab7cea2fd08433


Add "Copy Line Reference" functionality

This PR adds tiny context menu for text editor with 1 option called "Copy Line Reference" which copies relative project path with line number of current cursor. E.g. "test/my_class.coffee:25".

Your idea of "Copy Line Reference" sounds good!
I'll merge this PR when a bug and coding style are fixed.

done

Really this?? https://github.com/pluff/atom-copy-path/commit/7625a53622dfaeda4653a8027ab52eeaa7e9e6a3#diff-6d186b954a58d5bb740f73d84fe39073R98

sorry, git refused to push first time. now it's ready.

Sure, no problem :smile:
LGTM, so merge it.


Don't error out on plugin err with json

We don't want to error out when there is a json unmarshal error since
the old way will cause this to error.
I'm also a little suspect of this new handling now that I've messed with it.
HTTP statuses other than 200 should only be used for protocol level issues, which don't really need to encode a json message since it can just write a string to the body.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix_plugin_error_handling" git@github.com:cpuguy83/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

ping @runcom

it can just write a string to the body

that string can be a json payload :smile:
This change LGTM.

make sense, LGTM


Mark Gpiox as Send and Sync

This is appropriate because we only ever perform atomic operations on
these registers.  This allows PXx to be Send + Sync.
Closes #249

Thanks for the review!  No preference on my end between you merging this with CI failures or rebasing after the CI fix.  Let me know.

Let's rebase then :)


Use empty renegotiate extension instead of SCSV for TLS > 1.0

This PR fixes https://github.com/openssl/openssl/issues/18790.
This is my very first OpenSSL PR, and day to day I don't write much C (and zero Perl) so I'd appreciate some careful review!
I've just emailed a signed CLA to the legal email now.
The idea here is:

The empty renegotiation SCSV exists only as an alternative to sending an empty renegotiation extension in client hellos, purely for backward compatibility with server TLS implementations that may not support extensions (SSL v3 & TLS 1.0).
OpenSSL however sends this SCSV instead of the extension for all initial client hellos.
This is allowed, but the backward compatibility benefits are irrelevant for connections > TLS 1.0, and other popular clients (at least BoringSSL and SSL) do not do this (they send the extension instead of the SCSV) so this creates a trivial way to fingerprint the client hellos of OpenSSL clients (and block them: see #19220)
This PR changes this, to send the empty extension instead of the SCSV in all client hellos with a minimum version > TLS 1.0.

https://github.com/openssl/openssl/issues/18790 has some discussion about the context and risks of this. I'm not well versed in that, but given that BoringSSL made the change in 2015 (https://boringssl-review.googlesource.com/c/boringssl/+/5143) and seems to have no issues doing this in all Chrome traffic, my assumption is those risks are very minimal.
Checklist

[ ] documentation is added or updated
[x] tests are added or updated

I didn't look at the code, but checking the minimum version is probably not what you want. The default security level doesn't allow TLS 1.0, even if the minimum is set to allow it. You probably need to check both.

@kroeckx you're absolutely right. https://www.openssl.org/docs/man3.3/man3/SSL_CTX_set_security_level.html is clear that for v3.3 the default security level is 2, and that level 1+ disallows all TLS <1.2.
That doesn't make this wrong as such (it'll just keep adding the backward compatibility in some cases unnecessarily) but it does mean we could tighten it quite a bit further to cover those cases too, and that would be a significant improvement.
It looks like ssl_security(s, SSL_SECOP_VERSION, 0, TLS1_VERSION, NULL) is the correct way to check that the current security level for a connection s allows TLSv1, is that right?
I'll update this PR to add that later today. It looks like this is going to take quite a bit more updating of the tests, which makes sense since it now affects far more cases, but that's interesting since many will have different results at each security level. Is there any different-security-level testing I need to be aware of for that? I understand the basic test framework I think but I'm not clear how all the CI jobs etc hook together, and it'd be useful to know how to run anything like that locally.

PR updated:

Now uses the security level in addition to the minimum TLS level, so the RI extension is used far more widely. RI is now sent in extension format for all cases except initial connection + TLS + SECLEVEL=0 + minimum version <= 1 (where it's sent as an SCSV) and TLS 1.3 (where it's not sent at all).
Updates various tests accordingly, making RI an expected default extension
Created separate tests in test_renegotiation to more directly cover the key various cases there:

SECLEVEL=0 with no minimum TLS sends RI SCSV.
SECLEVEL=0 but TLS1.2 minimum level sends RI extension.
TLS1.3 minimum level sends neither SCSV not extension.

CLA now verified too.

Indent fixed, now rebased & mergable on master.

This pull request is ready to merge


Disable background services that are stopped.

If we're going to stop services, we should disable them as well, so they are not restarted on reboot.
We can use the charmhelpers.core.host.service_pause function for this.

I'm gonna leave this up for now, but I'm not sure this is the correct solution. I'll be starting a discussion to root out what we need to do.

No longer relevant, the systemd unit files are under control of snapd, and are removed once they are snap removed.


[r2.7-rocm-enhanced] Merge in ROCm5.2 HIP include file changes from staging

jenkins: retest Ubuntu-GPU-single please

jenkins: retest Ubuntu-CPU please


cannot run demo

~/go/src/github.com/neighborly/grpc-auth/demo master
❯ make server
go run main.go services.go token.go validator.go -m server
# command-line-arguments
./main.go:43:94: too few values in struct initializer
./main.go:50:86: too few values in struct initializer
./main.go:57:62: too few values in struct initializer
./services.go:25:59: too few values in struct initializer
./services.go:26:54: too few values in struct initializer
./services.go:56:39: too few values in struct initializer
./services.go:68:37: too few values in struct initializer
make: *** [server] Error 2

libprotoc 3.6.0
go version go1.10.3 darwin/amd64

This is because of a recent change in protobuf Go generator. It generates more fields (all starting with XXX_) in each protobuf message. I'm fixing the demo now.

Resolved.

Should be resolved, not close...


Scheduled processes

Create a new system that allows for scheduled processes to be run every x number of seconds, minutes, hours, days, weeks, months, years etc.
Each of these processes should have a simple function behind it.
Ensure that any design taken allows for an IoC container with injectable services.

Use case - being able to run reports over the data storage entities.

Use case - data aggregation for in-application data.

These services should instead trigger a scheduled message to go into a queue - so add scheduling onto the queues system so messages can be popped onto a queue periodically.


Add configuration for test_auth

test_auth requires that a user exists with name 'irodsauthuser' and password ';=iamnotasecret'. This can be done as part of the configuration for testing along with configuring the univMSS script and whatnot

This should be documented in the README unless it is obvious to the user.

Which README are you referring to? Come to think of it, we should probably come up with some words about running the iRODS test suite somewhere...

In this repo's README. It can be in a separate markdown file within this repo if you feel that is better.
And yes, I agree we should have words that show how to run the test suite, etc.
All of that information should be in this repo. We can reference this repo from other places (e.g. docs.irods.org), but those other places do not need to go into much detail about how to run a test, etc.

Okay, I can make an issue for that.
For what it's worth, this feature in particular does not need any instructions unless you just wanted to note it for informational purposes. This occurs as part of the configure_irods_testing, which is called from the various scripts for running tests.

I created #91 for the documentation exercise. Closing this one.


Use NTLM Authentication when prudent

@schismo Knife winrm will currently only work with basic authentication which means that you are unable to authenticate with domain accounts. There are two things going on in this pull request.

If the user specified a username with a \ in it, assume that they are doing domain authentication and set basic to false. Basic will be set to true when a \ is not detected in the users name.

In order for this to work, https://github.com/schisamo/em-winrm/pull/4 needs to be pulled and closed.

Negotiate will mess up if you have gssapi install and negotiate enabled, but have an unsupported or broken implementation of gssapi. So if you are specifying credentials, clearly you do not want to do kerberos authentication, so disable it and your troubles will go away.

There is an open pull request on WinRM to provide an option to disable Gssapi in the negotiation stack. It does not need to be closed prior accepting this pull request as the added option will only help when your kerberos environment is funky. https://github.com/zenchild/WinRM/pull/19

@pmorton any chance you could isolate this in a branch?  It appears some of the commits from #10 are bleeding into this pull request.

Yes. I will close the existing pull requests and patch them to branches.
On Feb 22, 2012, at 6:50 PM, Seth Chisamore
<EMAIL_ADDRESS>wrote:

@pmorton any chance you could isolate this in a branch?  It appears some of the commits from #10 are bleeding into this pull request.

Reply to this email directly or view it on GitHub:
https://github.com/opscode/knife-windows/pull/9#issuecomment-4129801


Implement minimal support for composite primary keys

this is related to PL: https://github.com/javalite/activejdbc/pull/402


[process-agent] Get hostname from main agent via grpc

What does this PR do?
Connects to the main datadog agent via grpc to configure the process-agent hostname.
@DataDog/processes
Motivation

Faster inter-agent communication via gRPC
Consistent hostname values between agent

Additional Notes
Describe your test plan
Write there any instructions and details that should be tested during the QA.

@truthbk - Would you mind having a look at my Initial change set. Thanks!

@truthbk - Would you mind having a look at my Initial change set. Thanks!


Mock hypatia and s3 in tests

This PR creates mocks of Hypatia and our AwsS3Downloader client and uses those mocks to stub out the methods we use to access Hypatia/S3 in tests. With the intro of this PR, we can run Zenodotus tests without Hypatia/s3 access.
Instead of scraping media posts to get data for tests, we load that data with mocks. This is, as you might image, much faster. Testing time should drop from 15+ minutes to ~3-4 minutes, most of which will be spent transcoding media.
Closes https://github.com/TechAndCheck/zenodotus/issues/314
76 files changed??
Sorry, there are tons of files changed in this PR. Nearly every test in our suite has been touched up. But here are some descriptions of and entry points to different parts of this PR:
S3 mocking

This PR creates an S3 mock class that stands in for AwsS3Downloader in tests.

The mock uses s3 keys to look for matching media filenames. If it finds a matching filename in our test/mock_media directory, it returns it.

In test_helper.rb, we create a proc that's injected into each individual test file to stub out AwsS3Downloader with our AwsS3Mock. See these lines
Within each test (see, e.g., InstagramPostTest), we create an s3-mocking block that uses the proc mentioned in (2) to do the actual stubbing.

Hypatia mocking

This PR creates a Hypatia mock module stands in for Hypatia in tests.

The mock creates a hash that matches media post URLs to hypatia responses. When it receives a scrape request for a media post URL, it returns the corresponding hypatia response.

When Minitest imports the mock module into test_helper.rb, it runs the module's construct_typhoeus_hypatia_stub method, which reroutes Typhoeus requests headed to Hypatia to our mock.
All calls to Hypatia within tests are automatically mocked, so long as we have data for the URL the test tries to scrape from. If a URL isn't caught by the mock, we raise an exception

Testing instructions

bundle
rails db:migrate (pulls in a migration from the base post-screenshots branch)
rake test

Here's my testing output:
Finished in 189.883972s, 0.5635 runs/s, 1.5325 assertions/s.
107 runs, 291 assertions, 0 failures, 1 errors, 0 skips
Coverage report generated for Minitest to /home/grog/hub/zenodotus/coverage. 1097 / 1352 LOC (81.14%) covered.

One test, test_scrape_callback_works fails for me on this branch and in master. @cguess is looking into it.
Before merging

Update dev README

I do wonder if we should organize all the mock files into a test/mocks directory though. I know that would require modifying all the paths, but having the mock files at the root of test/ feels weird, and if we put them in test/mocks/ we could also just have test/mocks/data/ and test/mocks/media/ too.

This bothered me a bit, too :). Happy to change it. Luckily, I'll only need to adjust the file paths in test_helper.rb. The rest of the tests inherit mock access from that helper file

Since the after_all is the same for every media source, should we consider monkey patching the ActiveSupport::TestCase to automatically include that?
Ditto for   include Minitest::Hooks
@cguess I thought about that (or creating a new test class our tests could inherit from), but I think we have a few different types of test classes. Some inherit from ActionDispatch::IntegrationTest, some inherit from ActiveSupport::TestCase, etc

@oneroyalace that's totally fine and makes sense, disregard my idea.

It woooooorks! 🎉


Phone-Verification

#120 I have raised the pr. For OTP verification you have to either enable yourself in the firebase console or provide me with the credentials to modify it accordingly. Thank you.

@lakshyeahh you have to mention this issue in that PR.

Done Sir. Please look into it.

@lakshyeahh there are some issues with your code. any update?

yes sir
will update the pr by eod


automotive_autonomy_msgs: 3.0.0-1 in 'dashing/distribution.yam…

Increasing version of package(s) in repository automotive_autonomy_msgs to 3.0.0-1:

upstream repository: https://github.com/astuff/automotive_autonomy_msgs.git
release repository: https://github.com/astuff/automotive_autonomy_msgs-release.git
distro file: dashing/distribution.yaml
bloom version: 0.8.0
previous version for package: null

automotive_navigation_msgs
* Ported to ROS2 Dashing.
* Contributors: Joshua Whitley

automotive_platform_msgs
* Ported to ROS2 Dashing.
* Contributors: Joshua Whitley

@nuclearsandwich Thanks for the merge! Any insight as to why the build on the farm failed - http://build.ros2.org/job/Dbin_uB64__automotive_platform_msgs__ubuntu_bionic_amd64__binary/1/display/redirect ? The error message says that a file is missing but it looks like a temporary build file:
ERROR com.rti.ndds.nddsgen.Main Fail: com.rti.ndds.nddsgen.Main$ArgumentException: File /tmp/binarydeb/ros-dashing-automotive-platform-msgs-3.0.0/obj-x86_64-linux-gnu/rosidl_generator_dds_idl/automotive_platform_msgs/msg/dds_connext/AdaptiveCruiseControlCommand_.idl doesn't exist. Please make sure that you have specified the correct path.
I'm seeing this on another package too (ibeo_msgs) while many of them have built successfully.

Seems to have been fixed now.

Yeah it's a known issue (https://github.com/ros-infrastructure/buildfarm_deployment/issues/208) that I just haven't had time to dig into. I've only ever seen it when running builds via the ros_buildfarm scripts or jobs so it doesn't affect CI. The current mitigation is that the release manager for a distro (myself for Crystal and Dashing) to retrigger packages with interfaces until they pass.


IE9: weird navigation, possible solution inside

In IE9, pushstate is not available, and function navigate: function (path, absolute) causes weird behaviour when not using a hash.
When I want to go to "/contact", it will go to "#/contact" and doesn't take into account if you are not using the hash.
I think the solution must be (line 194 in source code):
window.location.href = window.location.href
.replace(/#$/, '')
.replace(new RegExp(this._hash + '.*$'), '') + (this._useHash ? this._hash : '') + path;
Thank you

The hash is a requirement to fake pushState functionality in IE9, so not using the hash and supporting IE9 is not an option at all.

Yep, I agree with @handijk.


metrics and tracing support for gin?

I noticed  these in the docs
If you pass an http.Handler to the weaver.InstrumentHandler function, it will return a new http.Handler that updates these metrics automatically, labeled with the provided label.

If you pass an http.Handler to the weaver.InstrumentHandler function, it will return a new http.Handler that traces an HTTP request every second.

what if I use gin or fiber?

Hi @dfang! Currently, Service Weaver doesn't have any first class support for gin or fiber.
Looking at the gin documentation, however, it looks like a gin.Engine implements the http.Handler interface? So, I think you should be able to use gin with weaver.InstrumentHandler. And for fiber, this adaptor might allow you to do the same?


Add Bitter Reach content

Elven ruin (something like this: https://perchance.org/fl-br-ice-cave )
Settlements

No time


install previously released version

Hi,
I want to manually install mxnet 0.9.5  on an ubuntu system.
But, the git in https://github.com/dmlc/mxnet/releases/tag/v0.9.5 may lack of several required package such as, cud, dmlc-core, mshadow, nnvm, ps-lite.
Therefore, I have tried download these packages from the most current version in https://github.com/dmlc/mxnet/tree/master/.
But, when I typed 'make'. The error showed up.
Would you please guide me how to install mxnet 0.9.5 manually?

git clone https://github.com/dmlc/mxnet.git
cd mxnet
git checkout v0.9.5
git submodule init
git submodule update

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


[PP] Oboe matching in MIMO

In French, the string "Hautbois" is both singular and plural.
So in MIMO it compares as prefLabel of both:

Oboe's family "Oboes"@en http://www.mimo-db.eu/InstrumentsKeywords/4164
Oboe as instrument "Oboe"@en http://www.mimo-db.eu/InstrumentsKeywords/4232

Currently the matching goes to the first, while the second is the correct one normally.
Maybe we should implement a workaround for this.

Maybe we should implement a workaround for this.

One heuristic could be: "always privilege the instrument over the family" when there are multiple match. Does it make sense?

Yes, could be good


BSON encoding for BinaryQuadraticModel

Codecov Report

Merging #235 into master will increase coverage by 0.06%.
The diff coverage is 96.96%.

@@            Coverage Diff             @@
##           master     #235      +/-   ##
==========================================
+ Coverage   93.71%   93.77%   +0.06%
==========================================
  Files          30       30
  Lines        1734     1767      +33
==========================================
+ Hits         1625     1657      +32
- Misses        109      110       +1

Impacted Files
Coverage Δ

dimod/binary_quadratic_model.py
98.26% <96.96%> (-0.08%)
:arrow_down:

Continue to review full report at Codecov.

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


Don't scrape metrics from coreDNS

What did you do?
Install from helm:
helm install coreos/prometheus-operator --name prometheus-operator --namespace monitoring
helm install coreos/kube-prometheus --name kube-prometheus --namespace monitoring
What did you expect to see?
Target up kube-dns
What did you see instead? Under which circumstances?

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
kubeadm

Screenshots:

For  curl http://<IP_ADDRESS>:9153/metrics , i have:
...
# HELP coredns_build_info A metric with a constant '1' value labeled by version, revision, and goversion from which CoreDNS was built.
# TYPE coredns_build_info gauge
coredns_build_info{goversion="go1.11",revision="eb51e8b",version="1.2.2"} 1
# HELP coredns_cache_hits_total The count of cache hits.
# TYPE coredns_cache_hits_total counter
coredns_cache_hits_total{server="dns://:53",type="denial"} 66
coredns_cache_hits_total{server="dns://:53",type="success"} 46
# HELP coredns_cache_misses_total The count of cache misses.
# TYPE coredns_cache_misses_total counter
coredns_cache_misses_total{server="dns://:53"} 13157
# HELP coredns_cache_size The number of elements in the cache.
# TYPE coredns_cache_size gauge
coredns_cache_size{server="dns://:53",type="denial"} 83
coredns_cache_size{server="dns://:53",type="success"} 17
# HELP coredns_dns_request_count_total Counter of DNS requests made per zone, protocol and family.
# TYPE coredns_dns_request_count_total counter
coredns_dns_request_count_total{family="1",proto="tcp",server="dns://:53",zone="."} 3
coredns_dns_request_count_total{family="1",proto="udp",server="dns://:53",zone="."} 13266
# HELP coredns_dns_request_duration_seconds Histogram of the time (in seconds) each request took.
# TYPE coredns_dns_request_duration_seconds histogram
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.00025"} 6664
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.0005"} 8392
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.001"} 9399
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.002"} 13023
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.004"} 13140
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.008"} 13152
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.016"} 13181
coredns_dns_request_duration_seconds_bucket{server="dns://:53",zone=".",le="0.032"} 13193
....

How can i add target for core-dns?
Thanks

Hello,
The default values in the helm chart are:
deployCoreDNS: false deployKubeDNS: true
it is needed in this case to override these values in helm install command I guess:
 helm install coreos/kube-prometheus --name kube-prometheus --namespace monitoring --set deployKubeDNS=false --set deployCoreDNS=true

From upgrade can i do it? Or delete/install only?

It will work with an upgrade

@mathieuherbert Many thanks

I do it, but invisible section kube-dns in targets and i see  in service discovery dropped.

@kolesoffac if you don't mind, please post your solution for any future users who may run into this issue :)

@squat
I add endpoint to service kube-prometheus-exporter-coredns:
"ports": [
      {
        "name": "http-metrics-coredns",
        "protocol": "TCP",
        "port": 9153,
        "targetPort": 9153
      }
    ]


Question: Using semaphore with bastion

Question
For our environments we have ssh bastion servers. Right now we have ssh configs in each users workstations defining the proxies. We need to use the same user for proxy as the ones we use to run playbooks. For each user there is a separate username. How can we achieve this through semaphore. I tried using ssh config in the semaphore host but the connection to the bastion server tries to use root user. Not the user that is used for playbooks.
Related to
Configuration

I'm not an expert, just a user, but I think the answer to your question is NOT in semaphore setup/config, but in ansible setup/config.
In ansible.cfg, you have options like: https://docs.ansible.com/ansible/latest/reference_appendices/config.html#netconf-ssh-config
Or, in inventory/group/play vars, you have options like: ansible_ssh_common_args: "-J<EMAIL_ADDRESS>Semaphore "just" calls tasks ( I'm using ansible as the prime example ) - you want to configure your tasks with bastion-traversal, not semaphore.


Import from typescript end point script is resolved to use "browser" export

Describe the bug
When I import a module that has exports of type "browser", "import", "require" in typescript file (endpoint). The browser version gets imported
To Reproduce
For example the jwt library @panva/jose has this kind of structure. You can include it in your package.json and test.

Please provide a more complete reproduction with code snippets.
Likely an upstream issue with Vite.

Hello,
I created a test app to verify here:
https://github.com/damischa1/svelte-kit-conditional-export
It was created with:
npm init svelte@next my-app
npm install
Then I created node_modules/test_exports module with conditional exports. The module function whereami is imported and executed in hooks.ts
Just run npm run dev and navigate to localhost:3000
Node is printing I am in BROWSER. Expected I am in NODE.
I am not sure if the conditional exports are something optional to support and should the support be in Vite or how...
I tried also changing the order of conditionals in node_modules/test_exports/package.json and the first options seems to be picked.

You should probably also add something at the top level of the package.json like:
          "browser": "./dist/browser.js",
          "main": "./dist/node.js",
          "module": "./dist/esm.js"

@benmccann packages like jose use such package.json:
"exports": {
  "./jwt/sign": {
      "browser": "./dist/browser/jwt/sign.js",
      "import": "./dist/node/esm/jwt/sign.js",
      "require": "./dist/node/cjs/jwt/sign.js"
    }
}

And import { SignJWT } from 'jose/jwt/sign' in an endpoint still imports the browser version.

@hgl I expected Vite to look at the top level. I'm not sure whether it would also look in an exports map like this. In any case, it's probably best to file this as an issue in the Vite repo. You can use this project as the base of a project to reproduce the issue without SvelteKit involved

I had replied to the closed duplicate issue #1657 with a possible workaround.  Here's some excerpts:
Change your import to import { SignJWT } from 'jose/dist/node/cjs/jwt/sign'
Here's a repo which works for me.
My browser shows:
This is my header
The JWT is: eyJhbGciOiJIUzI1NiJ9.eyJhIjoxLCJpYXQiOjE2MjMyNzY5Mjd9.LUkbcaLoUc_3hOAhjjaGc7AfhS9kIetKQ7rax1E11cs
This is my footer

You're right, of course.  I was just looking at the log, not where the message was coming from, which was immediately upon entry to the function in vite-plugin-svelte.  I'll do a little more investigating, then I'll open the issue in Vite with any updated information (unless someone else beats me to the punch).

@JBusillo I tried your test repo, and it worked flawlessly for me. I also found out why I initially couldn't get it to work: listing jose as a dev dependency was vital, which I missed. This is pretty strange, considering it shouldn't make any difference once the package is installed on the file system. Maybe Vite won't consider browser version for dev dependencies? But if so, it doesn't explain why importing jose/jwt/sign still fails in this case.

I filed a vite issue for this -- https://github.com/vitejs/vite/issues/3772

@benmccann It's probably a silly question, but I wonder why would endpoints go trough vitejs? I believe the code in vitejs pertaining to this issue is at:
https://github.com/vitejs/vite/blob/ce459e3ffee95bac4fbf79d204c8cf65f25c9924/packages/vite/src/node/plugins/resolve.ts#L641
It seems to make sense that vitejs only wants the browser version since the bundled code is meant to be run in browsers.

The related Vite issue was closed by a PR a while ago, so the original issue should be resolved - closing.


Multi-Factor Authentication missing from Users window

Select Multi-Factor Authentication from the navigation bar across the top of the Users window.

I was unable to find this option in the Azure AD > Users area. Has it moved?
Thanks,
Stefan

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

ID: 42fff764-77f2-2878-f27f-867c71d9a8fc
Version Independent ID: 669c3568-eedc-f959-01d6-fcde93b9daaa
Content: Configure app passwords for Azure AD Multi-Factor Authentication - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-app-passwords.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

Hi @jaggersystems , this is now called "Per-user MFA". I made a pull request to update the text here. https://github.com/MicrosoftDocs/azure-docs-pr/pull/178573

https://github.com/MicrosoftDocs/azure-docs-pr/pull/179059


Notebook design

Business case
🇬🇧
Several Insee survey (BdF & EdT) use a notebook as a mean to collect prices (BdF) or daily activities (EdT). Historicallys, a paper notebook was used, now we want to implement a web / mobile notebook.
🇫🇷
Pour collecter des prix ou des activités, des enquêtes (BdF ou EdT) utilisent des carnets. Historiquement les collectes étaient sous forme de papier mais il faudrait pouvoir proposer un format web pour ces objets.
Stack
here describe the impact on the product softwares, linking to related issues
DDI
impact of the business case on the DDI use
Pogues
link to project issues
Eno
link to project issues
Lunatic
link to project issues
Progress
describe progress
Release date
here we want to keep track of deadlines; and provide links to milestones

Wont be handled by us


chore: upgrade analyzer to 4.0.0

Description
Changes:

Bumps Dart SDK to 2.19.0
Bumps VGA to 4.0.0

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[X] 🗑 Chore

To be merged after https://github.com/flutter/holobooth/pull/436.

@alestiago is this still on your radar?


Add Farsi characters to command detection

In addition to Latin characters, packages like xetex enable users to have commands defined by e.g., Farsi characters. This pull request adds such characters to the list of characters that can form a command. This list requires extending to include all Arabic and maybe other language characters.

What if we just put \u00c0-\uffff there, rather than trying to special case all scripts? Or can you think of a non-ascii character that is commonly used to terminate a command name?

It makes sense to include everything and exclude the ones we don't need. For example, U+200E, U+200F, U+202B, and the rest of the RTL/LTR encoding characters should be excluded. Or not, as they are not visible, they won't change anything visually for the user.


Add Application plugin dependency to Tours plugin

Description of Changes
Added Application plugin dependency to Tours plugin.

Issue(s) Resolved

Partial fix for #16117
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
@mrclary

Hey @mrclary, thanks a lot for your help with this! The problem is much deeper and really has to do with the new way to load and register plugins.
I'm preparing a PR to fix it just now. I'm just thinking how to test that something like this doesn't happen to us again.

Closing in favor of #16130.


Icons are blurry in 1.44.2

Issue Type: Bug
Some icons in SCM panel appears blurry.
If i rollback to 1.43.2 then this issue goes away, if i upgrade back to 1.44.2 issue reappears.
Screenshot with side-by-side comparision:

Top: 1.43.2
Bottom: 1.44.2
Note that "Open File" and "Stage" icons are blurry, while file icons themselves do not look like they are affected by this.
Doesn't always reproduce, sometimes they are fine (not blurry), but after i reload vscode they become blurry anyway. This seems to reproduce less frequently (or doesn't reproduce at all) on section icons (i.e. "Changes" section in SCM panel) or on untracked files, e.g.:

Also reproducible in insiders build.
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T17:50:03.709Z)
OS version: Linux x64 4.4.0-146-generic
Extensions (7)

Extension
Author (truncated)
Version

vscode-language-pack-ru
MS-
1.44.0

cpptools
ms-
0.19.0

Go
ms-
0.14.1

shader
sle
1.1.4

vscode-lua
tri
0.12.4

cmake
twx
0.0.17

vscode-todo-highlight
way
1.0.4

(1 theme extensions excluded)

This is image from vscode insiders build with and without M symbol (on the right) indicating type of changes. Note that action icons aren't blurry without M symbol and blurry with it.
I suspect that icons are being placed somewhere in the missdle of the pixel (like when position is at x=123.27 or something) due to their alignment and this triggers anti-aliasing, but don't quote me on that.
M disappearing may or may not be another bug, idk. But this is how i make it disappear: in insiders build i don't have any extensions enabled, so when i start vscode with .cpp file already open (left open from previous launch), it suggests to install C++ extension, i immediately press Esc to dismiss popup and after this modification type icons in VCS somehow don't appear.

Might be OS-specific issue. On Windows adding display: inline-table; might or might not improve image quality, icons just stay blurry with or without it. However depending on ClearType settings, there might be some improvements, but not as drastic as on Linux. It still does some sort of anti-aliasing even if icon is supposedly at integer pixel position:

Part of the potential improvement is coming from LCD subpixel rendering, if grayscale is used instead, then icons just appear blurry as usual.

@misolori will let you decide if you want to merge this to https://github.com/microsoft/vscode/issues/86308

This isn't an icon issue, passing it to @joaomoreno

@misolori This is a consequence of using fonts as a means to render icons together with the subpixel anti-aliasing. It happens because of https://github.com/microsoft/vscode/blob/dc269a975e2cc5df96d8c02b00b25c37be5409c2/src/vs/base/browser/ui/codicons/codicon/codicon.css#L17-L17

Actually it seems the bug is that subpixel antialiasing isn't working sometimes, so the icons appear blurry then.

I can't reproduce in SCM, so closing the issue.

That M though. It also appears that there is a mix of grayscale and rgba anti-aliasing on different text elements which is quite interesting on its own, perhaps due to some transformations or opacity applied to said elements.
I'll recheck this issue in 1.51 when it is released.

No, it's still reproducible in 1.51:

There is obvious image quality improvement if display: inline-table; is added to .scm-view .monaco-list-row .resource>.name>.monaco-icon-label>.actions .action-label.codicon:

The issue is most apparent when (slight) grayscale antialiasing is used in system settings and less apparent when rgba (LCD) antialiasing is used. I guess because grayscale antialiasing is using gray to smooth lines and icons are also gray, this blurs the icons. When rgba antialising is used, smoothing is in different colors, so it's a colored blur which is less obvious, but it exists.


New rule: no-unused-dependencies

The thought here is that this rule would lint package.json itself and warn on any deps or dev deps that are not explicitly imported somewhere in the linted JS files.
This would be independently configurable for deps as well as dev deps, with the following example schemas:
[2, {
  "dependencies": false,
  "devDependencies": true
}]

[2, {
  "dependencies": {
    "enable": false
  },
  "devDependencies": {
    "ignore": ["something-side-effecty", "a command-line tool"]
  }
}]

Ideally, it would also not warn on unused dev deps that had a "bin" name that was explicitly referenced in any of the "scripts".

https://github.com/depcheck/depcheck does this and it's really useful - would be neat to have as an eslint rule though.

@ljharb Wonder if this might be a better fit for eslint-plugin-node?

This plugin already has rules that check package.json, and there's no JS project worth working on that doesn't use npm and node for packages/builds, so I'm not sure why it would need a node-specific plugin.
Separately, the current situation with shared configs and peer deps in eslint means there's an incredibly high barrier to adding a plugin to a shared config like airbnb's, so until that's fixed, there's a also a huge incentive to add needed rules to plugins we're already using.

my thinking is:
package.json linting occurs in no-unused-dependencies rule
no-extraneous-dependencies rule handles the import linting
a tool shared between both of these rules is a good idea, since they both need to load and parse package.json files
Where should this live?
This brings up the topic of caching, should it instead just try to leverage eslint's cache? How?

I would love to see a no-unused-dependencies rule. What's needed to make this happen?
I imagine the no-unused-dependencies rule would also need to verify an unused dependency is not a peer dependency of another dependency. I'm not sure if it would be possible to verify this without crawling package.json files for all dependencies.

Might be able to leverage depcheck to do much of the heavy lifting (unsure about perf impact of that, though)

This would be really great to have for monorepos that use yarn workspaces and lerna, to stop unnecessary package interdependencies creeping in 🤞

I would love to see a no-unused-dependencies rule. What's needed to make this happen?
I imagine the no-unused-dependencies rule would also need to verify an unused dependency is not a peer dependency of another dependency. I'm not sure if it would be possible to verify this without crawling package.json files for all dependencies.

Personally, I’d be happy as long as it checks the target package’s package.json and there’s an override. We currently use depcheck (mentioned above), and there are things in our toolchain it can’t cache, which we override with various settings to assure it that no, it really is used as a dep or dev dep or whatever; the same in an ESLint plugin would be a lot more convenient (whether it uses depcheck itself under the hood or not—I guess it wouldn’t need to if ESLint already parses everything, but I know roughly zilch about ESLint plugin development).

Luckily, I know a reasonable amount with ESLint plugin development, and as long as i find the time, i'll work on this. (i'm a co-worker of @haggholm)

Anybody looking for a full solution in 2024 should use https://knip.dev/, it’s quite effective at finding and dropping unused code.


Source file is missing tensorflow/lite/experimental/acceleration/configuration/configuration.fbs

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.12.0
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Only compiled flatbuffer header is available (i. e. tensorflow/lite/experimental/acceleration/configuration/configuration_generated.h).
We can not use this header in our monorepo, as using it mandates using specific version of flatbuffers library.
Standalone code to reproduce the issue
ls tensorflow/lite/experimental/acceleration/configuration/configuration.fbs

Relevant log output
No response

I was able to generate necessary file from configuration.proto.
It looks like this is the correct way to do things.


Add option to trim uuid v4 reserved bits

There are 6-7 reserved bits in uuid v4.  Add an option to enable trimming these prior to base62 encoding.  This will lead to ids that are shorter and ~20 chars in length.

instead of this i just added an option to decrease the number of bytes returned


sql codgen for RETURNING in keyword not generating return values

Version
1.23.0
What happened?
Here's my update query for postgres (version 14):
-- name: UpdateEmail :exec
UPDATE users SET email = $1
WHERE id = $2
RETURNING id;

After running sqlc generate, it generates the following code:

const updateEmail = `-- name: UpdateEmail :exec
UPDATE users SET email = $1
WHERE id = $2
RETURNING id
`

type UpdateEmailParams struct {
	Email string `json:"email"`
	ID    int64  `json:"id"`
}

func (q *Queries) UpdateEmail(ctx context.Context, arg UpdateEmailParams) error {
	_, err := q.exec(ctx, q.updateEmailStmt, updateEmail, arg.Email, arg.ID)
	return err
}

As you can see the updateEmail func only returns the error.
This behaviour is consistent across updates, deletes. For inserts, everything works fine.
Relevant log output
No response
Database schema
CREATE TABLE "follows" (
  "following_user_id" integer,
  "followed_user_id" integer,
  "created_at" timestamp
);

CREATE TABLE "users" (
  "id" bigserial NOT NULL UNIQUE,
  "username" varchar PRIMARY KEY,
  "password" varchar NOT NULL,
  "email" varchar NOT NULL
);

CREATE TABLE "accounts" (
  "id" bigserial PRIMARY KEY,
  "user_id" integer,
  "username" varchar,
  "role" varchar,
  "reputation" integer,
  "created_at" timestamp
);

CREATE TABLE "posts" (
  "id" integer PRIMARY KEY,
  "title" varchar,
  "body" text,
  "user_id" integer,
  "status" varchar,
  "created_at" timestamp
);

COMMENT ON COLUMN "posts"."body" IS 'Content of the post';

ALTER TABLE "posts" ADD FOREIGN KEY ("user_id") REFERENCES "accounts" ("user_id");

ALTER TABLE "follows" ADD FOREIGN KEY ("following_user_id") REFERENCES "accounts" ("user_id");

ALTER TABLE "follows" ADD FOREIGN KEY ("followed_user_id") REFERENCES "accounts" ("user_id");

ALTER TABLE "users" ADD FOREIGN KEY ("id") REFERENCES "accounts" ("user_id");

SQL queries
-- name: UpdateEmail :exec
UPDATE users SET email = $1
WHERE id = $2
RETURNING id;

-- name: DeleteUser :exec
DELETE FROM users
WHERE id = $1 RETURNING id;

Configuration
version: "1"
packages:
  - name: "db"
    path: "./db/sqlc"
    queries: "./db/query/"
    schema: "./db/migration/"
    engine: "postgresql"
    emit_json_tags: true
    emit_prepared_queries: true
    emit_interface: true
    emit_exact_table_names: false
    emit_empty_slices: true

Playground URL
https://play.sqlc.dev/p/3cc713d2b4673acd115b5494d5dcdb4554f45d81f85f745c15958f6b3ea1e77c
What operating system are you using?
Linux
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

This issue is resolved! Had to do just one change -

-- name: UpdateEmail :one
UPDATE users SET email = $1
WHERE id = $2
RETURNING id;

-- name: DeleteUser :one
DELETE FROM users
WHERE id = $1 RETURNING id;

Just add one or many instead of exec to return values.


How to add nuxt to an already existing project?

Is there an official guide on enabling nuxt for already existing projects?

This question is available on Nuxt.js community (#c2256)

Great, however I got a question,
So i got a project made with symfony4 and vuejs2 with webpack Encore
. The question is: How can i make nuxtjs working with symfony 4 and handle my .vue components ?
Thanks for your suggestions.


Hotfix track4 challenge

Description
Feat: add auxiliary scripts to test Track4

Fixes #
Where has this been tested?

Platform(s): Ubuntu 16.04
Python version(s): 3.5.5
Unreal Engine version(s): NA
CARLA version: overnight

Possible Drawbacks

This change is

Is this a hot fix ? there is two big scripts being added
no rendering mode and NPC agent


User should be able to get a multisig wallet's details based on wallet address

User should be able to get a multisig wallet's details based on wallet address.
Not only the balance and public keys (like any regular account) but also the requiredSignatureCount for that wallet and the list of members (no need for pagination now since multisig membership is limited to 20 accounts by default).

@jondubois Could you elaborate more on this issue?

I think this issue can be closed because the account list multisig-wallet-members already returns a list of members for a multisig account so it's already possible to get all necessary information.


Clicking the sidebar icon appends a nonessential parameter to the URL.

When the menu  button is clicked/tapped, ?uiSidebarLeft parameter is added to the URL.
Any fix for this?

I think, the purpose for that is, so the user can easily close the sidebar menu with the back button.  But you may disable it by setting uiTrackAsSearchParam to false. See https://gist.github.com/mcasimir/824b28d14ca1e09d03c6

Nope, even with that, I can not get rid of that parameter!

If I understand correctly, in that page he explains that to enable it you have to do it like this :

plus some other stuff.
So if you just omit that parameter :

it should not append the parameter to the url.  At least in my case, that's what it was doing before I included it because I wanted the back button functionality.