Support for derivedTypes (...mobileApps/{id}/microsoft.graph.win32LobApp/...)

I believe the conversion settings that generate the openApi description may not expand paths further for navigation properties of a derived type once a odata cast paths is encountered.
Any chance you can create a separate issue for the /contentVersions path and then assign it to @irvinesunday or me so this may be investigated/followed up further?
Originally posted by @andrueastman in https://github.com/microsoftgraph/msgraph-metadata/issues/423#issuecomment-1727280918

Initial issue: I want to upload win32LobApps with the graph sdk for dotnet. I describe my process here
That means, creating the mobileAppContent, creating the mobileAppContentFile and eventually committing the file. All of which described in my post, is not available in the sdk.
Through using the portal I figured out that I need to change the type in the url.
I tried extending the request builders with extension methods, but they are not extendable https://github.com/microsoft/kiota-abstractions-dotnet/issues/113, which is a bummer...
Eventually @baywet pointed me to the metadata.... https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/2073
I have no clue how to get these endpoints in the graph sdk, please help!
I needed these extensions for my app (and doing it this way defeats the purpose of using the sdk in my opinion.)
https://github.com/svrooij/WingetIntune/blob/30b5f76fbaa043de94be29c4c05b692b19540b0e/src/WingetIntune/Graph/GraphServiceClientExtensions.cs
and
https://github.com/svrooij/WingetIntune/blob/30b5f76fbaa043de94be29c4c05b692b19540b0e/src/WingetIntune/Graph/MobileAppsRequestBuilderExtensions.cs

@andrueastman I cannot assign anyone, but here is the new issue.

@baywet
Changing this setting to true for the Kiota-based conversion setting should suffice.

We will generate the expected contained nav. props defined on the target types of the type cast segments. See the below example path:

However, note that the number of paths will increase from 8,622 to 11,710 in v1.0 and 14,738 to 18,852 in Beta.
Do you think these changes will affect Kiota and the potential growth of SDKs significantly?

Thanks for the additional information here.
Kiota should handle the growth just fine. The SDKs I'm worried about, that's a ~50% growth.
Before we make any decision here, could we validate:

Whether we're ONLY expanding nav props defined on the target type (and nothing defined on the base type) ?
Whether we might have an inaccurate set of contains target true which might lead to over expansion? (lots of repeating segments at different places)

If this expansion is accurate (I suspect it isn't, and that we're probably talking about a lower growth), we might want to consider an alternative approach (leaving the setting to false, but adding some kind of annotation that'd mean "yes I really really want this one to be expanded").

I have done a diff in v1.0 between an OpenAPI files generated with ExpandDerivedTypesNavigationProperties = false vis-a-vis ExpandDerivedTypesNavigationProperties = true and I've picked up the below nav. prop as the major cause for the blowned-up paths:
directory/deletedItems

Removing the DerivedTypeConstraint from the directory/deletedItems nav. prop, the total paths just increase from 8,622 to 8,641
I need to investigate whether these type casts annotated under deletedItems are accurate or not.

The type casts are valid alright, but I think that containment for deletedItems is wrong and needs to be removed.

@svrooij I believe setting ContainsTarget=false for the deletedItems nav. prop. is the best route to take here.
These type cast paths, which we currently generate (with ExpandDerivedTypesNavigationProperties = false) will still be generated:

Expanding on those paths is what we will be limiting (as expected).

Thanks for investigating. As far as I understand the ContainsTarget true is technically correct there because these objects only live in this collection (no other way to access them). BUT once they are in this collection, you can't do anything other than list/cast them and delta on the collection (you have to restore the objects before you can do anything else on them).
So I think it's safe to "fix" the ContainsTarget to false.
With that in mind, would you mind submitting a PR with the setting being changed and the XSLT to fix this contains target please?

@irvinesunday technically this issue is not fixed by #442 it will need another pr to switch on the generation of the derived navigation


Remove the additional call during the login process to allow the login window to disappear

Currently when logging in the UI makes an additional call to api/session/isApplicationAdministration as soon as it receives confirmation from the API that the user is logged in. It will not close the login popup window until the response from this call is received.
The issue is that an improvement to the API to speed up the log in process itself is now returning the first call but leaving the API in a "locked" state for the user's security policy. Any subsequent calls to the API will stall until the lock has been removed via the async operation building the security policy.
This means the call to this additional endpoint is stalling for the time the policy is locked, thereby not progressing the user any further into the application.
If the UI did not make this call immediately, but rather closed the popup window and then progressed and made the call while it loaded the tree then it could allow users to possibly perform other actions.
No additional actions or endpoints are required to handle the "lock" its a built in feature to the API to just hold any calls while a policy is being updated.

I've been doing some investigation to the feasibility of this change and found that this should be doable. This was tested on branch feature/mc-9803 from MauroDataMapper/mdm-core.
Sign in dialog
When I've removed the api/session/isApplicationAdministration call temporarily from the login operation, the sign-in dialog closes pretty much immediately. This definitely gives the UX appearance of working faster.
Dependencies on isAdmin flag
The call was included as part of the login operation because checking the admin state is required in numerous components. However, for the most part I've found that there are simple workarounds:

Remove flag check completely - code wasn't even using it
Code could just call api/session/isApplicationAdministration when required, there is usually no need to depend on this at the start of your session.
Or depend more on the availableActions list for catalogue items - sometimes the checks are to determine if you have permissions to soft/permanent delete items

There are two small cases though which could require discussion:
Navigation Menu
The isAdmin flag is used on navigation menu to decide which links to display:

Because this is a key part of the layout, knowing the state of the user is pretty key and needed right at the start of the session.
My suggestion is to actually reduce this menu down. I don't believe we need every account setting section listed, instead just replace with a link to "My account settings" page (where the admin check could happen), and a "Log out" button. This could be considered a UX change as well - trying to reduce the complexity of the menu - but would need approval from @jamesrwelch before this change happened.
Allow permissions to change on catalogue items
A catalogue item with a availableActions array may include the update action, meaning the user can (among other things) view the user/group permissions of that item.
Question for @olliefreeman - if you are an admin, would this action always be returned by the backend? If so, the isAdmin flag check can be safely removed.

so yes that isApplicationAdministrator has to wait for the policy, i did try to pre-load it, but there are 2 issues with preloading

it may not be right due to container admins
that call has to be made on an unlocked policy, however the policy remains locked until the remaing parts of the policy are built, this was what i couldnt get around. If we unlock the policy nothing works, if we leave it locked theres no point prebuilding the application access as we still have to wait for the lock to remove

wrt update this actually relates to the ability to use the PUT call to update the object, isApplicationAdministrator is actually relevant to the "application" NOT the resource, so its presence shouldnt actually denote the ability to do actions on a resource.
There are 2 types of "admin" user who would not be able to affect a resource, which i'm not sure we're using yet.

User admin
UserGroup admin

These 2 roles allow users to add/remove users and groups, so they would need access to the admin pages.
Having said all that the isApplicationAdministrator endpoint is specifically to denote that the user has the role application_admin or site_admin in which case...yes they will have full access to ALL resources.
There is probably a piece of work to check who can access what wrt application roles, whcih could be done as part of the aforementioned "refactor of admin menu"

@jamesrwelch - After doing my refactoring I've found that the navigation menu isn't really an issue actually. What will happen now is:

Login endpoint returns with success
Login dialog is then closed
A notification is broadcast to other listening components that the login was successful
The header component picks this up and then call isApplicationAdministrator

The worst that will happen is that the user profile will appear in the header, then shortly update again after to show any admin related changes (display role, expand menu with more options etc). We've still maintained the speed update though.


Link metadata element inside ItemGroup/Compile items should (maybe) be supported

Hi,
I am working with the Typeprovider SDK. The template contains
<ItemGroup>
    <Compile Include="..\..\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fsi">
      <Paket>True</Paket>
      <Link>paket-files/ProvidedTypes.fsi</Link>
    </Compile>
    <Compile Include="..\..\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fs">
      <Paket>True</Paket>
      <Link>paket-files/ProvidedTypes.fs</Link>
    </Compile>
    .
    .
</ItemGroup>

when using paket to fetch the ProvidedTypes API from Github. Ionide cannot load a project with linked files. If a change the above to
<ItemGroup>
    <Compile Include="..\..\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fsi" />
    <Compile Include="..\..\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fs" />
    .
    .
  </ItemGroup>

The project does load fine.
In the msbuild docs the Link metadata for the ConpileItem is documented as

Link: Optional string. The notational path to be displayed when the file is physically located outside the influence of the project file.

This makes sense because the files are loaded from the paket-files subtree.
I can live without the Link metadata. I am just reporting the problem, so that the maintainers of the project system can decide if this should be supported.
Addendum
Silly me. The compile items
<ItemGroup>
    <Compile Include="..\..\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fsi">
      <Paket>True</Paket>
      <Link>paket-files/ProvidedTypes.fsi</Link>
    </Compile>
    <Compile Include="..\..\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fs">
      <Paket>True</Paket>
      <Link>paket-files/ProvidedTypes.fs</Link>
    </Compile>
    .
    .
</ItemGroup>

are generated by paket. So ionide need to be able support those when paket.dependencies contain
github fsprojects/FSharp.TypeProviders.SDK src/ProvidedTypes.fsi
github fsprojects/FSharp.TypeProviders.SDK src/ProvidedTypes.fs

and paket.references contain
File:ProvidedTypes.fsi
File:ProvidedTypes.fs

Should be fixed with 5.0


RTC.io plugin not getting opened.

Hi DamonOehlman,
I have updated new version of rtc.o extension, downloaded new version of screen share and running it with beefy. i took care of ssl and all. But the popup window to select the screen to be selected is not coming up.  I dont see any errors at server side, but client side.
here are the screenshots. Please help me.

Could you try going to http://<IP_ADDRESS>:9966/ instead of just localhost ?

@silviapfeiffer Going to http://<IP_ADDRESS>:9966/ won't work because screensharing requires HTTPS to operate.  In fact, with the inline installation it's even more restrictive as the published version of the plugin will only work if is being run from an *.rtc.io host.
@santhoshreddyk How are you doing your HTTPS proxying to your local dev server?  I dropped a gist online on Friday to help one of our team members make a setup similar to what you are doing now so that should help (proxying via nginx):
https://gist.github.com/DamonOehlman/dfe879ce2e282a86bc80
Additionally, I think you will probably need to put a local host entry for something like local.rtc.io for localhost.

@DamonOehlman
I tried the nginx configuration given by you. And changed my localhost to "localhost.rtc.io"
Still it says bundle.js and demo.css --> 404 error and nothing comes up.
Please suggest.

@santhoshreddyk ok, I think I see the problem now that I've taken a look again at the command you are using to run the demo.  Try running the demo with the following command:
beefy share-window.js:bundle.js

This is of course assuming that you are running beefy from within the examples directory as you did in the first instance.  Assuming npm works the same on windows that it does on my machine you should also be able to run the following from the screenshare directory (one above the examples directory) and have it work also:
npm run demo

This is made possible by a custom script specified in the package.json.  Let me know how you go.

@DamonOehlman : Thank you very much for instant reply. It works :)


Running Consumer Route of MDX Fails on Vite Plugin version of Remix

What version of Remix are you using?
2.2.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
use remix as a vite plugin, build an app with a tsx route that consumes mdx via the @mdx-js/rollup plugin and build. head to the mdx consumer route and it breaks with the error message
TypeError: t.jsxDEV is not a function
at o (http://localhost:3000/build/assets/test-1a250893.js:9:223)
at l (http://localhost:3000/build/assets/test-1a250893.js:10:578)
at io (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:68:19477)
at ja (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:70:43691)
at Da (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:70:39496)
at id (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:70:39427)
at $r (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:70:39287)
at Ni (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:70:35709)
at Ta (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:70:34665)
at E (http://localhost:3000/build/assets/entry.client-1dd82fdc.js:55:1562)
Expected Behavior
i expect it to not break
Actual Behavior
it breaks. here's the repo to repro: https://github.com/bronifty/migrate-remix-to-vite.git

It looks like mdx plugin is transpiling JSX into jsxDEV(...) instead of jsx(...) even for build command.
I tested your reproduction and setting mdx plugin's development option explicitly seems to solve the issue:
export default defineConfig((env) => ({
  plugins: [
   ...
    mdx({
      development: env.command === "serve",  /// <==== switch based on `vite dev` or `vite build`
      remarkPlugins: [
        remarkFrontmatter,
        remarkMdxFrontmatter,
      ],
    })
  ],
}));

If this is not really handled by mdx plugin itself, maybe it's worth mentioning in remix doc https://remix.run/docs/en/main/future/vite#add-mdx-plugin

it was tough following this thread but I checked the file you changed in the PR and it works thanks

Sorry about my comment derailing a bit too much...
Thanks for testing and providing the reproduction!

no problem thank you!

Fixed by #7911.


Are build for MacOS (M1) broken?

I get error
“openfortivpn-webview.app” is damaged and can’t be opened. You should move it to the Bin.
when trying to run the .app unarchived from arm64 dmg downloads.
This happens for at least 2 latest available releases.

They are not as far as I know. Did you run xattr as explained here?

Thank you! That indeed solved the problem.


"gear info / kill / shell / replay" throws exception rather than printing usage

fixed by
https://github.com/intel-hadoop/gearpump/pull/1150


Unknown unit type: bomber

The new version of the HoI4 converter seems to spam "unknown unit type: bomber" in the log. I haven't tried it yet in gameplay but it is pretty annoying.

It was a mod I used in Vic2 that had that unit type.

Which mod? We could make sure they actually get converted (I already added units from other mods to the list).

Ultimate Mod. It is an ambitious project of covering history in Vic2 from 1604 to 2023, I use it only to have a 1936 start to test.
The new unit types are Bomber, Carrier, Special Operation Infantry, Submarines and Transport Planes. No new technology invented.
I find it bad that old units in Vic2, however, simply vanish. They should get their modernized counterparts in a numerically reduced version.

Can you list out the names as they're presented in the units folder of the mod? Both filename and the name from inside the files, just in case.

Man, I'll just give you the files here, it'll be better.
bomber.txt
carrier.txt
specops.txt
submarine.txt
transport_plane.txt


Object Manipulation Instead of Re-Query

For some reason, every time a dump was created or deleted, the backend was being queried for ALL dumps. This causes a complete refresh in the DOM, causing slow load times and high internet usage. Also drains the battery a ton, due to ~4mb download and upload every time page is refreshed.
I have changed everything to local object manipulation, which is much more sensible. Objects will now be spliced and upshifted when removing/adding to object array. This will solve the DOM reload problem, will remove the un-discovered bug of high load times and alleviate extreme backend load/crashes.
In addition, the app now doesn’t do backwards array sorting and reverse index search. Uses indexOf(dump) which limits the backwards thinking we have to do. This makes more sense.
Closes #32
Look at how fast adding links is now:

#41 Needs to be pulled in before I can do this.

can this be pulled in now? #41 has been pulled

Nope. Now I can pull master into this, and continue this branch. Thanks!

This is ready.

Cool Looking good dude!


affected[].ranges[].type missing timestamp type

affected[].ranges[].type missing timestamp type
So we have:
https://github.com/cloudsecurityalliance/gsd-database/blob/main/2023/1001xxx/GSD-2023-1001657.json
"product_version": "prior to Jan 4 of 2023 (2022/01/04)",
"vulnerability_type": "XSS",
"affected_component": "https://app.zerossl.com",

as it's a service there is no good way to specify a version. But we know for sure it was vulnerable prior to the fix time, so this is actionable information (if you have any certs from them that were created before this time you should probably roll them over).
having a TIMESTAMP type in addition to SEMVER and GIT would solve this problem easily. Can I submit a PR to add this?
As we've seen there's a lot of vulns in a lot of services and we need to start documenting them.

@rsc @chrisbloom7 thoughts?

My main concern here is that this balloons the scope of OSV a little -- this is no longer about open source software (or packages), and it may be a case of trying to shoehorn a use case that may not fit OSV very well and end up with a worse experience overall.
Perhaps this is where GSD can help with defining a separate, more specialized scheme for these (which you've already done)?

I could go either way on this tbh.
On one hand, there's serious value in keeping OSV as lean and simple as possible. OTOH, a couple of these minor changes would vastly increase the versitality and allow machine readable parsing for things like services (URI based).
One of our goals with GSD is to avoid inventing new formats as much as possible, which is why expanding the scope of OSV just slightly would make our lives simpler. But, if it's valuable to the community, we could always use a more expansive format and provide API endpoints for consuming OSV.
Things like documentation IDs (e.g. SQL textbook with examples vuln to SQL injection, or a Stackoverflow post that is popular/widely used and vulnerable to an exploit) would clearly be out of scope for OSV, but are something we would like to cover in a machine-readable way.

OSV continues to be lean, this doesn't bloat it, we're not adding new data, we're adding a new category of data, for which we have a lot of need, for a recent example:
https://nvd.nist.gov/vuln/detail/CVE-2023-28858
sources:
https://github.com/redis/redis-py/compare/v4.3.5...v4.3.6 |
https://github.com/redis/redis-py/compare/v4.4.2...v4.4.3 |
https://github.com/redis/redis-py/compare/v4.5.2...v4.5.3 |
https://github.com/redis/redis-py/issues/2624 |
https://github.com/redis/redis-py/pull/2641 |
https://openai.com/blog/march-20-chatgpt-outage
which has the affected data of:
"affected": [
{
"vendor": "n/a",
"product": "n/a",
"versions": [
{
"version": "n/a",
"status": "affected"
}
]
}
]
ignoring that it needs redis-py in there, it would also be hugely helpful to list chat.openai.com as being vulnerable from time X to time Y, as per their blog entry listed in the CVE:
Open a subscription confirmation email sent on Monday, March 20, between 1 a.m. and 10 a.m. Pacific time.
In ChatGPT, click on “My account,” then “Manage my subscription” between 1 a.m. and 10 a.m. Pacific time on Monday, March 20.
Virtually everytime there is a cloud service issue, we're going to need a timeframe for vulnerability regardless of whether or not we can find an affected software/API/etc version.

The target audiences for OSV today (who want to leverage the schema + data to enable high quality automated vulnerability scanning + remediation of their package dependencies so that they can update), seem very different to what this change is trying to enable (someone who wants to know if they used a service at some URL while it was vulnerable so they can take appropriate remediation steps), in that a vulnerability scanner will have no way to make use of this data.
Adding this seems like an a bad fit for OSV, and I think a separate, more specialised mechanism targetd at this second target audience would be a better approach.

The target audiences for OSV today (who want to leverage the schema + data to enable high quality automated vulnerability scanning + remediation of their package dependencies so that they can update), seem very different to what this change is trying to enable (someone who wants to know if they used a service at some URL while it was vulnerable so they can take appropriate remediation steps), in that a vulnerability scanner will have no way to make use of this data.
Adding this seems like an a bad fit for OSV, and I think a separate, more specialised mechanism targetd at this second target audience would be a better approach.

That's fair. We've been trying to use OSV as the source of truth for GSD, and our scope is definitely larger than package ecosystem vuln scanners (e.g. bundler audit, yarn audit, etc) which is where these asks are coming from. Cloud services and documentation are both explicitly within the scope of the GSD. And less explicitly, any vuln data that would benefit from having machine-readable identifiers.
Definitely understandable having OSV cater to a specific use-case and stay strictly within that scope (it is in the name, "Open Source Vulnerability" after all). We'll have to revisit the source of truth for GSD so that we can use/serve OSV where possible, but be able to cover these other scopes.
Mainly, we want to avoid the standards issue, and have been trying to avoid creating a new format in a vacuum.

To clarify, the GSD project has been using the OSV data format to structure GSD data, and our scope is definitely larger than just the open source package ecosystem, we also include cloud services built upon and using open source (sometimes exclusively). We could currently use the “ECOSYSTEM” tag:
ECOSYSTEM: The versions introduced and fixed are arbitrary, uninterpreted strings specific to the package ecosystem, which does not conform to SemVer 2.0’s version ordering.
So we could simply use a timestamp tag, but we’d rather acknowledge a very common case and make the data easier to parse.
While we understand that OSV may want to stay open source focussed, we are disappointed by the refusal to include an additional keyword (“TIMESTAMP”) which adheres to the logic and behavior of the already existing “SEMVER”, “ECOSYSTEM” and “GIT” keywords.

Also a concrete example of why we need this: IBM Cloud advisories:
https://cloud.ibm.com/status/security
e.g. note the "start time" and "update time" in all of these:
IBM Cloud Kubernetes Service is affected by two containerd security vulnerabilities (CVE-2023-25153 and CVE-2023-25173)
Component: Kubernetes Service
Location: Sydney, Dallas, Tokyo, Frankfurt, Washington DC, Osaka, London, Sao Paulo, Toronto
Start time: 6 Mar 2023 2:15 AM
End time: N/A
Update time: 9 Mar 2023 9:16 AM
Type: Security bulletin
IBM Cloud Kubernetes Service is affected by two security vulnerabilities found in containerd where (1) a maliciously crafted image with a large file could cause a denial of service when importing an OCI image (CVE-2023-25153) and (2) supplementary groups are not set up properly inside a container which could bypass primary group restrictions in some cases (CVE-2023-25173).
A user action is required to verify that their cluster worker nodes are not exposed.
For information see the security bulletin.

This seems to be a duplicate of #62 should this or it be closed out?

they should be merged yah


Navigating through the months with a keyboard clashes with OS functionality

The current keyboard navigation for cycling between months clashes with OS functionality on a Mac. ctrl-left-arrow/right-arrow are used to flip back and fourth between your desktops.
This could be kinda confusing or at least make discovering existing keyboard navigation more difficult.
possible solution
Make the left and right chevrons tab stops so that when the calendar is thrown and the focus is on the current date of the current month the user can then shift-tab to select the right chevron and then shift-tab again to select the left
Your Environment

flatpickr version used: latest
Browser name and version: Firefox, Safari, Chrome
OS and version: macOS

Hi, any updates on this?
Thanks


Add IT support with security enabled cluster for SQL plugin in tar building workflow

Changes
Add IT support with security enabled cluster for SQL plugin in tar building workflow
Testing
https://github.com/opendistro-for-elasticsearch/opendistro-build/actions/runs/171539594

Should we add the respective team members to have look? Or just reply to their issue as an update?

I will update the issue and add the PR link.  That should be good enough


Fix text-break in IE and Edge Legacy

Fix #29319 again.
Correcting Backport #30932 to v4
word-break didn't support break-word value in IE and Edge Legacy
overflow-wrap is absent in IE/Edge Legacy (it's modern replace for word-wrap)
So we need to add back word-wrap: break-word for IE and Edge Legacy.

Thanks for the PR, but please always make sure CI passes.

@XhmikosR thanks, could you please clarify how should I proceed with Lint errors in files below?
/home/runner/work/bootstrap/bootstrap/js/src/button.js
/home/runner/work/bootstrap/bootstrap/js/src/modal.js
/home/runner/work/bootstrap/bootstrap/js/src/scrollspy.js

I didn't touch them, they're the same as current upstream v4-dev branch.

Those are not errors, they are warnings and unrelated. https://github.com/twbs/bootstrap/pull/31727/checks?check_run_id=1152664809#step:6:53

BTW I see why you got confused; GitHub changed something in regard to Actions and the Stylelint errors are not highlighted like the warnings or the parent failed commit. Either way it should be pretty trivial to fix, but for future reference better clone the repo locally so that you run the tests.

@XhmikosR thanks, I've fixed lint error and updated PR, please review.

@twbs/css-review can I have a review just so that we are safe please?

@XhmikosR I've added more detailed comments how .text-break rules works.

See #31793.


Return equivalent_ids?

For this query:
{
    "message": {
        "query_graph": {
            "nodes": {
                "n0": {
                    "id": "UniProtKB:P52788",
                    "category": "biolink:Gene"
                },
                "n1": {
                    "category": "biolink:ChemicalSubstance"
                }
            },
            "edges": {
                "e01": {
                    "subject": "n0",
                    "object": "n1"
                }
            }
        }
    }
}

Strider is returning nodes in the KG without equivalent identifiers:
{'PUBCHEM.COMPOUND:439533': {'category': ['biolink:ChemicalSubstance'],
  'name': '(+)-taxifolin',
  'attributes': []},
 'PUBCHEM.COMPOUND:65057': {'category': ['biolink:ChemicalSubstance'],
  'name': 'diphenylcyclopropenone',
  'attributes': []},

It would be extremely helpful in omnicorp and answercoalesce if we had the equivalent identifiers on these nodes.   I think (?) that strider already has this information?  If it doesn't, we can normalize after strider...

This is close to #153 if we're passing along ids provided by KPs, but Strider also looks up some information from the node normalizer. It already adds provenance information, so we can add these synonyms too, where possible.


Accessing item in list by div id after page load

Hi,
I'm trying to scroll to a certain position in the list on page load with the following:
var scrollTo = document.getElementById("groupId"); scrollTo.scrollIntoView();
This returns a JS error:
Uncaught TypeError: Cannot read properties of null (reading 'scrollIntoView')
I have tried to defer the above script but it doesn't seem to be able to access the element by id.
Any help greatly appreciated.

My bad. The above code was too high in the sequence so dom hadn't fully loaded.


Export data from alpha_group_significance

This came up on the forum.

This came up again on the forum.

and again on forum


Update the dropdown selected checkmark from black to white

Update the dropdown selected checkmark from black to white to contrast better with coloured dropdowns.
Here's what it looked like previously:

and now:

Note: SVG is not used directly and only exported to PNG (no need to optimize)
Fixes https://github.com/Microsoft/pxt-microbit/issues/1276
pxt-blockly PR: https://github.com/Microsoft/pxt-blockly/pull/118

Can we cleanout the sprites.svg?

How so? just like remove the inkscape meta data?
As mentioned in my note, SVG is not used directly and only exported to PNG so I didn't feel the need to optimize size.

Oops missed the note. Disregard.


Update Kafka Binder Configuration at runtime

I am using Spring Cloud Stream along with Kafka binders to connect to a Kafka cluster using SASL. The SASL config looks as follows:
spring.cloud.stream.kafka.binder.configuration.sasl.mechanism=SCRAM-SHA-512
spring.cloud.stream.kafka.binder.configuration.sasl.jaas.config= .... required username="..." password="..."
spring.cloud.stream.kafka.binder.configuration.security.protocol=SASL_SSL

My application would receive updated username and passwords periodically and I want to update the SASL Kafka configuration with the latest credentials at runtime. I need help with the same, I have tried googling and searched stackoverflow  but can't find any solution for this.

There is no reason to double post in SO and here. It's not going to make things any faster and actually creates a bit of confusion. Please give someone a chance to respond first.
Also, we generally do not use this issue tracker for questions.

Apologies for the confusion due to posting on SO as well, however I couldn't get any solution for this on SO and anywhere else. Some help on possible approaches to solve this would be appreciated.


Fix dependency problems preventing installing

Fixed #8
Tested CLI to work properly with the latest packages.
Also bumped the version so that PyPi 0.8 version doesn't get preference if you try to install patched version to virtualenv.
Any change to get a release? I can update the package on PyPi if needed - my username is miohtama.

@miohtama @c17r: Sorry for the extremely delayed response. Version 1.0 is now on PyPI. It has NO pinned decencies. There are also many bug fixes, a new suite of unit tests with over 90% code coverage, and official support for Python 2.7, 3.3, 3.4, and 3.5. With this new release, I will be able to respond more quickly to pull requests and other issues. Once again, I'm sorry for the delay. Thank you for your interest in daemonocle.


[BUG] Server Application error during page redirection after successful login.

Bug Report
After a successful login (with MFA), Server Application error occured during page redirection.
Tried the solution (driver.WaitForPageToLoad) in relation to https://github.com/microsoft/EasyRepro/pull/773/commits/f27f662f408320646f7a323a740da58a573dbf5c but it doesn't work in my end.
Browser I used is Firefox 73.0.1 (64-bit).
Issues should only be created for items related to covered functionality.
Not covered functionality, feature requests, and questions should use the Feature Request or Question templates.
EasyRepro Version

[ ] Microsoft Dynamics 365 Online Version 8.2 (8.2.x) (DB 8.2.x) online
[ ] Microsoft Dynamics 365 Online Version 9.0 (9.0.x) (DB 9.0.x) online
[ ] Microsoft Dynamics 365 Online Version 9.0.2 (9.0.2) (DB 9.0.2) online
[ ] Microsoft Dynamics 365 Online Version 9.1 (9.1.x) (DB 9.1.x) online

UCI or Classic Web

[x] UCI (XrmApp)
[ ] Classic Web (XrmBrowser)

Online or On Premise

[ ] Online
[ ] On Premise

Browser

[ ] Chrome
[x] Firefox
[ ] IE
[ ] Edge

Describe the bug

After a successful login (with MFA), Server Application error occured during page redirection.

Special formatting / display

Code to reproduce

Expected behavior

User should be redirected to the landing page after login (with MFA)
Screenshots

Additional context

As cited in https://github.com/microsoft/EasyRepro/pull/773/commits/f27f662f408320646f7a323a740da58a573dbf5c , root cause is in Webclient.cs -> Initialize mode
internal BrowserCommandResult<bool> InitializeModes()
        {
            return this.Execute(GetOptions("Initialize Unified Interface Modes"), driver =>
            {
                Thread.Sleep(10000);                --> This seems to work. Successful page redirection
                //driver.WaitForPageToLoad();  --> Not working on my end

                var uri = driver.Url;
                var queryParams = "&flags=easyreproautomation=true";

                if (Browser.Options.UCITestMode) queryParams += ",testmode=true";
                if (Browser.Options.UCIPerformanceMode) queryParams += "&perf=true";

                if (!uri.Contains(queryParams) && !uri.Contains(System.Web.HttpUtility.UrlEncode(queryParams)))
                {
                    var testModeUri = uri + queryParams;

                    driver.Navigate().GoToUrl(testModeUri);
                }

                WaitForMainPage();

                return true;
            });

Thanks @tristanperper,
like I write in comment in #777.
I have a different approach for some cases. I describe it in #774. I don't like to add extra time because the Tests are already taking too much. I have the idea of retry (if needed) or a global TimeFactor that can accelerate or slow the tests depending of the performance of the Client & the Environment.
What do you think?
br

Thanks @tristanperper,
like I write in comment in #777.
I have a different approach for some cases. I describe it in #774. I don't like to add extra time because the Tests are already taking too much. I have the idea of retry (if needed) or a global TimeFactor that can accelerate or slow the tests depending of the performance of the Client & the Environment.
What do you think?
br

Hi @AngelRodriguez8008 ,
Your idea of retry, is this sort of a page retry? It it works, then let us look at that kind of implementation.
Regards,
Tristan Perper

Sorry @tristanperper,
I was testing something in Firefox now & I remember that in Firefox (Manual Testing) I wasn't able to login with the OTC, just via SMS. Now is working different I don't get the SMS, the OTC works. I don't know exactly what is happening with Firefox.
Are you able to login manually with this both MFA possibilities?
Thanks & br

Sorry @tristanperper,
I was testing something in Firefox now & I remember that in Firefox (Manual Testing) I wasn't able to login with the OTC, just via SMS. Now is working different I don't get the SMS, the OTC works. I don't know exactly what is happening with Firefox.
Are you able to login manually with this both MFA possibilities?
Thanks & br

Hi @AngelRodriguez8008 ,
Yes I was able to login manually either SMS or OTC.
Regards,
Tristan Perper


Actually yes. GDPR means a lot of work if you need a lot of data. :-) But I like it, because privacy is supposed to work in a way people would expect. Anyway, I hope to find the time to work on open Symphony issues soon!

@michael-e I did it because of this comment
Did I misunderstood it ?

Yes, as a user, GDPR is good, and this is a good thing :+1:

Yes, I am afraid that you misunderstood my comment. Symphony did not output anything, so there is no sense in again making in output nothing. :-)

@michael-e Ok I see. So my new if does not have any purpose! (?)

Yes. It does not change anything. But I do not understand why it works even without your commit. I hoped that you would know. (I just tested it, but I don't understand it.)

But I do not understand why it works even without your commit.

I bet would be on those lines. If the field data table is empty, we skip it.
In 3.0.x, that check is still there (it got moved to another file tho).

@michael-e @fhamon I've rebased and removed 4dd0b168771362fa560c11e5c4a7539a1fb34b97 from the pr.


Placeholders not passed through to component templates

I'm still fairly new to the ins and outs of tcomb-form, so please bear with me if I'm being silly.
I am using custom templates to generate a form, which has manually set placeholders on some fields.
const FormModel = t.struct({
  // ...
  bio: t.Str,
  // ...
});

const formOptions = {
  fields: {
    // ...
    bio: {
      placeholder: 'A short description of yourself'
    },
    // ...
  }
};

In my custom form templates, I am logging the locals passed to the template, and it does not contain a placeholder property.
I manually traced through the tcomb-form code, and it seems that the placeholder is never passed down to the template, despite examples to the contrary on the documentation. Looking at Component.prototype.getLocals, it seems that the placeholder never gets passed! By altering the given lines to the following, placeholders begin to appear in my form:
  return {
    path: this.props.ctx.path,
    error: this.getError(),
    hasError: this.hasError(),
    label: this.getLabel(),
    onChange: this.onChange.bind(this),
    config: this.getConfig(),
    value: value,
    disabled: options.disabled,
    help: options.help,
    placeholder: options.placeholder
  };

Have I misunderstood tcomb-form, or is this a genuine bug?

Hi, I think you are referring to v0.4 docs.
Here the v0.5 docs: https://github.com/gcanti/tcomb-form/blob/master/GUIDE.md#templates.
Try with:
const formOptions = {
  fields: {
    // ...
    bio: {
      attrs: { // <-- this is the new API to handle attributes and events
        placeholder: 'A short description of yourself'
      }
    },
    // ...
  }
};

attrs are provided to input components by a decorator.
Since you are tracing the source code, if it can be helpful:
Decorator definition:
https://github.com/gcanti/tcomb-form/blob/master/src/components.js#L80
Decorator usage:
https://github.com/gcanti/tcomb-form/blob/master/src/components.js#L249
Retrieving the attrs:
https://github.com/gcanti/tcomb-form/blob/master/src/components.js#L273

Thanks for your quick response! I must admit I didn't check the version of the guide with respect to my local version of tcomb.
Not using attrs was indeed my mistake! Consider this issue closed :+1:


Enhance Logging for Debugging in sequence and train Functions

Description:
This PR addresses Issue #422 by improving the debugging experience for the sequence and train functions. It ensures that critical metadata (machine hostname and full command-line invocation) is logged at the start of the run.
Key Changes:

Added logging for:

Machine hostname using socket.gethostname().
Full command used to invoke the script (sys.argv).

Placed the new logs immediately after logging setup, ensuring they are captured even if the process fails early.

Applied the changes uniformly across both the sequence and train functions for consistency.

Hi @dhruvErry, thank you for your contribution.
In this case, we are already logging the machine hostname and the executed command at the end of the program's execution in our development version (dev branch) here.
For your PR to be incorporated, please modify it:

Open it against dev instead of main.
Refactor the existing log_run_report to be split into information that can be logged at the start of the run and at the end of the run, respectively.
Correspondingly modify when these logging functions are called in casanovo.py.

Thanks!


Fails running container on docker 1.8

Fails with the following error on docker 1.8.2 when attempting to run a
container.
Error: HTTP code is 500 which indicates error: server error - json: cannot unmarshal string into Go value of type int64

I'm guessing that this is a simple fix of passing a Number rather than String, but
I'm not sure where/what or this would be a PR. :+1:

Is this the same as #170?

It was actually a different issue, but totally my fault. Sorry about that!


Updates in support of up-spec Issue:  File Attachment Feature #114

Added proposed updates to uprotocol_options.protobuf, and high level file streaming details with notification to L2 readme.doc.

@urcorcoran what I recommend is to file an issue to describe the problem you're trying to solve and then we can discuss potential solutions. Furthermore the Files message has not been added to UAttributes, that is a simple change and fix so that they can be passed in the various event types (publish, notification, request, response)


Using DNNE.C99Type for enum does compile under windows but not linux

I currently do not have an idea why this works on windows but not in Linux.
If I defined a method parameter:
[UnmanagedCallersOnly]
 public static int FunctionCall([DNNE.C99Type("enum EnumTypeDefinition")] EnumTypeDefinition sparDefinition)

I defined the C99Type like this:
internal sealed class C99TypeAttribute : System.Attribute
{
    public C99TypeAttribute(string code) { }
}

it compiles with Windows but with Linux I get:
error G13FECB51: variable has incomplete type 'enum  EnumTypeDefinition'
A workaround would be not to use the type but integers of course but is a bit less readable

ok, I think I found the problem. There was a missing declaration. still I wonder why windows allows that.
[DNNE.C99DeclCode(@"     #include <stdbool.h>     enum EnumTypeDefinition     {         item1,        item2     };     ")]

still I wonder why windows allows that.

The issue here is MSVC considers the type to be forward declared at this point. Dropping the enum gets the error you are looking for. This relates to MSVC and its tenuous adherence to C99.
https://godbolt.org/z/9bPbvqxz8


Migrate from Akka to Pekko

References https://github.com/endpoints4s/endpoints4s/issues/1103.

I left only the necessary mentions of Akka.
TODO:

[ ] Fix sttp-client tests
[ ] Bring back cross(CrossVersion.for3Use2_13) for Pekko dependencies. Scala 3 is still experimental it seems.
[ ] Fix version policy

@julienrf I think this is ready for review. Still need to resolve version policy issues.

@julienrf Are we ready to merge?

@julienrf Are we ready to merge?

Absolutely! Thank you again for all the work :pray:

I left only the necessary mentions of Akka.
TODO:

[x]  Fix sttp-client tests
[x]  Bring back cross(CrossVersion.for3Use2_13) for Pekko dependencies. Scala 3 is still experimental it seems.
[x]  Fix version policy

Pekko team would prefer if you use the Scala 3 jars. We have seen no issues raised related to the Scala 3 jars.

Pekko team would prefer if you use the Scala 3 jars. We have seen no issues raised related to the Scala 3 jars.

I simply tried removing cross(CrossVersion.for3Use2_13) and the code did not work fine, did not investigate further. Just today noticed that Play 3 has a proper Scala 3 Pekko dependency, so that got me thinking that the issues are most likely on endpoints4s end. Your comment confirms this. So that is a good thing, means we can look into this in future PR 😄

Pekko team would prefer if you use the Scala 3 jars. We have seen no issues raised related to the Scala 3 jars.

I simply tried removing cross(CrossVersion.for3Use2_13) and the code did not work fine, did not investigate further. Just today noticed that Play 3 has a proper Scala 3 Pekko dependency, so that got me thinking that the issues are most likely on endpoints4s end. Your comment confirms this. So that is a good thing, means we can look into this in future PR 😄

Sounds good.

I realize now that it would be good indeed to use the Scala 3 artifacts of Pekko as it would allow us to publish our testkits also for Scala 3.

Hello, though I fully understand the migration to Pekko, would it be possible to support Akka as well? At least for the time being? Within the company I work we have about 150 micro-services that run mostly on Akka. With this migration we are now stuck on the latest released Endpoints4s version. Having both Akka and Pekko supported could make it easier to migrate from one to the other, instead of requiring a big-bang migration.

@bmeesters have a look at the comments above and the mention of https://github.com/endpoints4s/akka-http

Ah thanks @pjfanning I missed that, never mind then!

The code is in its own repo, but we did not publish a release to support the latest version of endpoints4s yet. I expect some work to be necessary in the release process because we want to release two artifacts (akka-http-server and akka-http-client) with two different version numbers.


Multiple outer joins to the same table with different criteria

I am writing a paginated report and would like union together multiple criteria.  The closest i have come to implementing this in one query is with outer joins and squeel.  I end up with something like:
Activity.joins{subject(SharedSpace).outer.space.outer}.
  joins{subject(Space).outer}.where{subject(Space).outer.user_id==current_user or subject(SharedSpace).outer.space.user_id==current_user}

This results in SQL that looks like:
SELECT "activities".*
FROM "activities"
    LEFT OUTER JOIN "shared_spaces" ON "shared_spaces"."id" = "activities"."subject_id" AND "activities"."subject_type" =   'SharedSpace'
    LEFT OUTER JOIN "spaces" ON "spaces"."id" = "shared_spaces"."space_id"
    LEFT OUTER JOIN "spaces" "subjects_activities" ON "subjects_activities"."id" = "activities"."subject_id" AND "activities"."subject_type" = 'Space'
WHERE
    "spaces"."user_id" =
67

This is almost correct but it is missing the criteria for "subject(Space).outer.user_id==current_user" which should be ""subjects_activities"."user_id" = 67".  So the following query seems to do what i need in SQL:
SELECT COUNT(DISTINCT "activities"."id")
FROM "activities"
    LEFT OUTER JOIN "shared_spaces" ON "shared_spaces"."id" = "activities"."subject_id" AND "activities"."subject_type" = 'SharedSpace'
    LEFT OUTER JOIN "spaces" ON "spaces"."id" = "shared_spaces"."space_id"
    LEFT OUTER JOIN "spaces" "subjects_activities" ON "subjects_activities"."id" = "activities"."subject_id" AND "activities"."subject_type" = 'Space'
WHERE
    "spaces"."user_id" = 67 or
    "subjects_activities"."user_id" = 67

Is there a proper way to do this with squeel?  If not, is there a way to union together multiple queries?
thx!

There's no "or" in Squeel DSL. You want ||. Also, you will want to enclose those two conditions in parens and unless you've got a current_user local variable, you'll probably want to use my{current_user}


fixes #13816 Modal dialog closes when dragging and releasing mouse button outside dialog

Fixes #13816.

 I did a diff between 3.2.0 and 3.2.1 and tracked the issue to this commit. I just upgraded our webjars to use 3.3.2-1, and it's still broken. I've added the hack below to fix this locally. Any thoughts?
.modal-backdrop {
    position: fixed;
    top: 0;
    right: 0;
    bottom: 0;
    left: 0;
    z-index: 1035;
}

@Jim-Horn This will be reverted by #15881.

Thanks Heinrich
Cheers, Jim


Error: Proxy output ip  does not match with provided one

The error I have encountered is: "Error: Proxy output ip socks5://<IP_ADDRESS>:50479 does not match with provided one"
I have been trying to run for_the_lulz.js with a proxy file, but I have failed. Why the error is occurred? What is the reason of it?
Update: proxies feature is not working... When I run the test_proxyflag.js with the same proxy it is working successfully but with se-scrapper not.

I'm having the same issue, did you find a solution?

same


feat(distr): add distribution authorization

Description
This PR adds an x/distribution specific Authorization to use with EVM extensions. It includes the msg url and the allowed list so smart contract developers are able to set multiple accounts for the transactions.
Closes: #XXXX

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] followed the guidelines for building modules
[ ] included the necessary unit and integration tests
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

https://github.com/Mergifyio backport ledger/v0.47.x


Error installing on windows

this is the log from installing it into C:\node
I got to the node cli.js install npm -gf command
the I got this a massive log which ends with these ERR! remarks
ERR! Error: ENOENT, The operation completed successfully.
ERR!  'C:\DOCUME~1\NJH\LOCALS~1\Temp\npm-1317934276992\1317934276992-0.3127990404609591\contents\package\package.json'
ERR! Report this *entire* log at:
ERR!     <http://github.com/isaacs/npm/issues>
ERR! or email it to:
ERR<EMAIL_ADDRESS>ERR!
ERR! System Windows_NT 5.1.2600
ERR! command "c:\\Documents and Settings\\NJH\\node\\bin\\node.exe" "c:\\Documents and Settings\\NJH\\node\\npm\\cli.js" "install" "npm" "-gf"
ERR! cwd c:\Documents and Settings\NJH\node\npm
ERR! node -v v0.5.7
ERR! npm -v 1.0.94
ERR! path C:\DOCUME~1\NJH\LOCALS~1\Temp\npm-1317934276992\1317934276992-0.3127990404609591\contents\package\package.json
ERR! code ENOENT
verbose exit [ 1, true ]

I can put it all if it would help but I didn't want to create a massively long post

duplicate of #1488


Move

Coverage decreased (-0.8%) to 53.386% when pulling a0e935af6249c9a65b7a4428ff759dc1fd024238 on move into b6834c3fe75fa43de82db151895bb018dda5ebd3 on master.

Coverage decreased (-0.8%) to 53.386% when pulling e52489f92f20d23e8ab0b7b4f2d47d4630e1aa8a on move into b6834c3fe75fa43de82db151895bb018dda5ebd3 on master.

Coverage decreased (-1.3%) to 52.902% when pulling 2d7fdd59bdcd05d41dcc6dc3b7ec00d84dc11ee3 on move into b6834c3fe75fa43de82db151895bb018dda5ebd3 on master.


Jokes support

Jokes support is added with crumb files.
The media also needs to be modified.
in crumbs.json, add jokes with this format:
"jokes":[{"id": 1, "joke": "Whats a good joke?", "answer": "this one!"}, {"id": 2, "joke": "This is another amazing", "answer": "Joke :D"}]

What's the point of sleep when you could just use setTimeout? Also, wouldn't sleep not work in the production version - utils aren't built.

Thanks for the PR, it would be better to generate a joke ID and then send it through send_joke, also instead of using async/setTimeout you can use Phaser timers:
scene.time.delayedCall(delay, callback, args, scope)


Mina daemon crashed (sandbox) - macOS Ventura 13 Docker

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions

Description
I cannot run a Mina node in sandbox mode using Docker. I'm following the dev docs specified here
Docker ver: 20.10.24
Docker compose: v2.17.2
docker run \
  --publish 3085:3085 \
  -d \
  --name mina \
  -e RUN_DEMO=true \
  -e MINA_PRIVKEY_PASS='' \
  minaprotocol/mina-daemon:1.3.0-9b0369c-bullseye-devnet

Is there a specific image I'm supposed to use for macOS? I suspect this is related to x86_64 issues running on ARM
Steps to Reproduce
See description, simply run the docker command
Expected Result
To run a sandbox node locally.
Actual Result
Running Mina demo...
Genesis State Timestamp for this run is: 2023-05-02T05:27:33Z
Rewriting config file from template daemon.json.template to /root/.mina-config/daemon.json
mkdir: cannot create directory '/root/keys': File exists
Contents of config file /root/.mina-config/daemon.json:
{"genesis": {"genesis_state_timestamp": "2023-05-02T05:27:33Z"},"ledger":{"name":"mina-demo","accounts":[{"pk":"B62qiZfzW27eavtPrnF6DeDSAKEjXuGFdkouC3T5STRa6rrYLiDUP2p","balance":"66000","sk":null,"delegate":null}]}}
2023-05-02 05:27:34 UTC [Info] Mina daemon is booting up; built with commit "8a582fd1d387917e26c6cb30f57052c54a4774e3" on branch "compatible"
2023-05-02 05:27:34 UTC [Info] Daemon will expire at "2024-12-10 14:00:00-07:00"
2023-05-02 05:27:34 UTC [Info] Booting may take several seconds, please wait
2023-05-02 05:27:34 UTC [Info] Reading configuration files $config_files
        config_files: [ "/var/lib/coda/config_8a582fd1.json", "/root/.mina-config/daemon.json" ]
2023-05-02 05:27:34 UTC [Info] Initializing with runtime configuration. Ledger name: "mina-demo"
2023-05-02 05:27:34 UTC [Info] Using the compiled constraint constants
2023-05-02 05:27:34 UTC [Info] Loaded genesis ledger from $ledger_file
        ledger_file: "/root/.mina-config/genesis/genesis_ledger_accounts_c178985d098781c62a16d307c27a561902b30ec8c63d904220eea597a635b35c.tar.gz"
Using block producer keypair private-key password from environment variable MINA_PRIVKEY_PASS
2023-05-02 05:27:45 UTC [Info] Cleaning up old epoch ledgers with genesis state $state_hash at locations $staking and $next
        state_hash: "3NLVjRoLJ6kJHoYCtDh2MgWSnNtY9m6M9FZJ1BxSW8vCaG3DodEk"
        staking: "/root/.mina-config/epoch_ledgercb7a310f-65e6-3c62-475c-c5c6fcb3ef58"
        next: "/root/.mina-config/epoch_ledger8f951439-867c-3dcd-f00a-122612494967"
2023-05-02 05:27:45 UTC [Info] Starting node as a seed node
Transaction_snark.system: 1.645m
2023-05-02 05:30:09 UTC [Info] Setting current protocol version to "2.0.0" from compile-time config
2023-05-02 05:30:10 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
        exn: {
  "commit_id": "8a582fd1d387917e26c6cb30f57052c54a4774e3",
  "sexp": [
    "monitor.ml.Error",
    [
      "Writer error from inner_monitor",
      [
        "Unix.Unix_error", "Broken pipe", "writev_assume_fd_is_nonblocking",
        ""
      ],
      [
        "writer",
        [
          [ "id", "5" ],
          [
            "fd",
            [
              [ "file_descr", "25" ],
              [
                "info",
                [
                  "child process",
                  [
                    "stdin",
                    [ "pid", "113" ],
                    [ "prog", "/proc/26/exe" ],
                    [ "args", [ "parallel-worker" ] ]
                  ],
                  "src/process.ml:62:17"
                ]
              ],
              [ "kind", "Fifo" ],
              [ "supports_nonblock", "true" ],
              [ "have_set_nonblock", "true" ],
              [ "state", [ "Open", "Empty" ] ],
              [
                "watching",
                [ [ "read", "Not_watching" ], [ "write", "Not_watching" ] ]
              ],
              [ "watching_has_changed", "false" ],
              [ "num_active_syscalls", "0" ],
              [ "close_finished", "Empty" ]
            ]
          ],
          [
            "monitor",
            [
              [
                [ "name", [ "id", "105" ] ],
                [ "here", [] ],
                [ "id", "105" ],
                [ "has_seen_error", "false" ],
                [ "is_detached", "false" ]
              ],
              [
                [ "name", "" ],
                [ "here", [ "src/lib/mina_lib/mina_lib.ml:1288:35" ] ],
                [ "id", "90" ],
                [ "has_seen_error", "false" ],
                [ "is_detached", "true" ]
              ]
            ]
          ],
          [
            "inner_monitor",
            [
              [
                [ "name", [ "id", "106" ] ],
                [ "here", [] ],
                [ "id", "106" ],
                [ "has_seen_error", "true" ],
                [ "is_detached", "true" ]
              ],
              [
                [ "name", "" ],
                [ "here", [ "src/lib/mina_lib/mina_lib.ml:1288:35" ] ],
                [ "id", "90" ],
                [ "has_seen_error", "false" ],
                [ "is_detached", "true" ]
              ]
            ]
          ],
          [ "background_writer_state", [ "Stopped_permanently", "Error" ] ],
          [ "background_writer_stopped", [ "Full", [] ] ],
          [ "syscall", "Per_cycle" ],
          [ "bytes_received", "326" ],
          [ "bytes_written", "0" ],
          [ "scheduled_bytes", "0" ],
          [ "scheduled_back", "0" ],
          [ "back", "0" ],
          [ "close_state", "Open" ],
          [ "close_finished", "Empty" ],
          [ "close_started", "Empty" ],
          [ "num_producers_to_flush_at_close", "0" ],
          [ "flush_at_shutdown_elt", [ "<opaque>" ] ],
          [
            "check_buffer_age",
            [
              [
                [ "writer", "<opaque>" ],
                [ "maximum_age", "2m" ],
                [ "bytes_received_at_now_minus_maximum_age", "0" ],
                [ "bytes_received_queue", [] ],
                [ "times_received_queue", [] ],
                [ "bytes_seen", "0" ],
                [ "too_old", "Empty" ],
                [
                  "for_this_time_source",
                  [
                    [
                      "active_checks",
                      [ "<opaque>", "<opaque>", "<opaque>" ]
                    ],
                    [ "closed", "Empty" ]
                  ]
                ]
              ]
            ]
          ],
          [ "consumer_left", [ "Full", [] ] ],
          [ "raise_when_consumer_leaves", "true" ],
          [ "open_flags", [ "Full", [ "Ok", [ "wronly" ] ] ] ],
          [ "line_ending", "Unix" ]
        ]
      ]
    ],
    [ "Caught by monitor (id 105)" ]
  ],
  "backtrace": [
    "Raised at Base__Result.ok_exn in file \"src/result.ml\", line 201, characters 17-26",
    "Called from Async_kernel__Deferred1.M.map.(fun) in file \"src/deferred1.ml\", line 17, characters 40-45",
    "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5",
    "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"
  ]
}
2023-05-02 05:30:10 UTC [Warn] Shutdown before Coda instance was created, not saving a visualization
  ☠  Mina Daemon crashed.

How frequently do you see this issue?
Always
What is the impact of this issue on your ability to run a node?
Blocker
Status
Error: Unable to connect to Mina daemon.
- The daemon might not be running. See logs (in `~/.mina-config/mina.log`) for details under the host:<IP_ADDRESS>.
  Run `mina daemon -help` to see how to start daemon.
- If you just started the daemon, wait a minute for the RPC server to start.
- Alternatively, the daemon may not be running the RPC server on (<IP_ADDRESS> 8301).
  If so, add flag `---daemon-port` with correct port when running this command.

Additional information
No response

Hey @azerella, thanks for posting this.
However I'll close it in favour of https://github.com/MinaProtocol/mina/issues/12089


Link updates

Docs Build status updates of commit d3dd3de:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/install-nuget-client-tools.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update Go interop image to go1.11

Fixes https://github.com/grpc/grpc/issues/16604,
updated the image, regenerated and pushed with tools/dockerfile/push_testing_images.sh.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,966,317      Total (=)      1,966,317

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,909,770      Total (<)     10,909,775

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

Doesn't this make things worse?  I don't claim to understand the test infrastructure, but I believe this Dockerfile is used for the ongoing interop tests which build grpc-go from HEAD.  For this purpose, using golang:latest, as it is before this change, seems to make the most sense to me.
My concern in #16604 is that for the compatibility test matrix, we currently enumerate the Go docker images as a matrix of  x .  The go versions supported by that script are 1.7 and 1.8, which will not be supported by new versions of grpc-go.  What we really want is not a matrix, but a flat list of images.  Newly created docker images for new versions of grpc-go should use Go 1.11 (or golang:latest maybe, if that gets captured when the image is created??), and we should be able to enumerate all the existing images in the client_matrix.py script.

Doesn't this make things worse? I don't claim to understand the test infrastructure, but I believe this Dockerfile is used for the ongoing interop tests which build grpc-go from HEAD. For this purpose, using golang:latest, as it is before this change, seems to make the most sense to me.

Personally I would go with this PR as I think this it's an improvement.
Note there are two parts to the interop client docker image build:

the base docker image - this is the part of the docker image that has a grpc interop client's dependencies, but not the actual interop client.
the full interop image with the actual interop client - on top of a base image with dependencies, we get the relevant grpc client into a container off of the base image, compile it, and commit that that container into a new image which has the actual compiled interop client - https://github.com/grpc/grpc/blob/master/tools/run_tests/dockerize/build_interop_image.sh#L119. This second piece is repeatedly rebuilt during tests to test the clients at HEAD.

The "base docker image" is built once, stored (cached) in dockerhub, and then fetched and reused repeatedly during tests... so there's no defined "re-build" time for this base docker image. If we rely on "latest" in the base docker image, then we could wind up in situation where the base image was built two years ago and includes a now-unsupported go version even though it used to be "latest". Forcing a certain version is IMO more explicit and easier to reason about.

Is the Dockerfile stored along with the docker image produced from it? Or does the Dockerfile just specify how to create the image, and we save only the image itself?

Only the docker image is cached in dockerhub. The dockerfile describes how to build the image, but there's no need to store it. Note that name of the docker image as stored in dockerhub includes the sha1 of the dockerfile, so in that way each dockerfile is exactly one-to-one with a cached docker image.

I'd really prefer for the regularly-running tests that build grpc-go from HEAD to use the latest golang version as well. Otherwise we'll have to increment it at every golang release (or eventually break). If there's any confusion, we should run go version at the start of all the tests so it's obvious what version of Go is stored in the docker image (and ideally name the image accordingly as well).

Ack. But note that using "latest" doesn't fix this because the built image's sha1 will never change and so it will cache hit indefinitely. Running go version and checking it against the latest go release could perhaps be done as a part of the go interop client invocation, but that check would need some way of knowing what the latest release is. One possible idea to automatically keep the go version up to date with the current year's release: maybe some kind of github bit could file an issue once per year, or perhaps even create a PR to update the go version once per year.

Only the docker image is cached in dockerhub. The dockerfile describes how to build the image, but there's no need to store it. Note that name of the docker image as stored in dockerhub includes the sha1 of the dockerfile, so in that way each dockerfile is exactly one-to-one with a cached docker image.

Interesting.  So for every Go release, we need to modify this file and build a new image?  Is this hashing part of how dockerhub works, or are we using that convention?
Another option could be to not install Go at all in the image and have it install Go at the start of each test run.  (This is how Travis works, and there's an open source script called gimme that makes it easy to install Go: just run gimme stable.)

@dfawley the change from golang:latest to golang:1.11 doesn't really change the fact that the go version will stay the same in the testing image unless the testing image is rebuilt and pushed - that's the way our testing framework currently works. Changing to 1.11 only triggers that change and makes it explicit that the go version is actually static (so it's an improvement).
This PR is only to upgrade go to 1.11 in interop tests, to mitigate the danger that interop tests will stop working soon (as suggested #16604).
We can discuss how interop testing should be done in the future separately from this PR, but please note that there are some limitations:

there is a lot of background of why things are setup the way they are (both historical reasons and experience what works and what does not).
we need to maintain consistency between languages - we can't have special behavior for each language because otherwise maintaining this will become a nightmare.
overhauling stuff means work and more work to then validate the new solution and fix unexpected problems. we don't currently have any bandwidth for any such work beyond what's absolutely necessary, so we need to be very careful in terms of what we sign up for. Help is welcome ;-).

Btw, I agree with some of the complaints about the interop backward compatibility matrix  - I will try to dedicate some effort to improving the backward compatibility matrix scripts.

Known failures: https://github.com/grpc/grpc/issues/16922

@jtattermusch all that sounds good.  Thanks for fixing this.  I'll file a new issue about the backward compatibility scripts since they will not work for our release in 7 weeks.


fix(wildcardtypes.spec.js): fix flaky wildcard test

Test did not wait long enough to handle a message but would assert immediately post publisher
confirm ack
fix #4

found an addition flaky test to address as part of this fix


Revisit JSON Path examples

There are two JSON Path examples that have been discussed on Slack, namely:
https://github.com/OAI/sig-workflows/blob/1e74716b3c137765f1c8b987ef547dd36981c0a0/versions/1.0.0.md?plain=1#L486
and
https://github.com/OAI/sig-workflows/blob/1e74716b3c137765f1c8b987ef547dd36981c0a0/versions/1.0.0.md?plain=1#L692
neither of which look correct. The contention is that this is the right syntax if pets is an object:
<EMAIL_ADDRESS>> 0)]
And if pets is an array:
<EMAIL_ADDRESS>> 0)]
And if you don't care whether its an object or an array:
<EMAIL_ADDRESS>> 0)]
With all expressions either being truthy or returning no match.
The lines highlighted should be revisited, checked to see if they are correct, and then remedial action taken as required.

Agree these need to be revisited. The aim should be to conform to RFC 9535. I'll try to carve out some time next week.
In both cases about, potentially the count function would be more suitable<EMAIL_ADDRESS>> 1] depending on how the response schema is structured of course. Specifying a sample response JSON for which the conditions are applied would also be advisable.
A related topic, is what do we do if the response content type is application/xml. Do we need to consider that and possibly add XPath? This is related to the issue on enhancing the requestBody capabilities in #152

Ok that makes sense now.  I had assumed that the original JSON Path spec was being implemented i.e. https://www.ietf.org/archive/id/draft-goessner-dispatch-jsonpath-00.html when I read the Slack comments. The query expressions seem to the main difference to the original Gössner approach.
What's the tooling landscape like? Is there wide adoption for the latest version? To me there's an argument for supporting both versions, as support for the script expressions above is very common.
Regards the point about application/xml I think there is a strong argument for including XPath.  It'll make life much easier for implementers and consumers IMHO.

Notes from SIG meeting on March 13th
To move this forward, we propose the following:

Amend the Criterion object type property to be either a string or an Expression Type Object (properties name and type)
The supported string (short hand) types would be as currently described plus the addition of XPath. The default version of XPath would be 3.1 and the default for JSON Path would be RFC 9535.
The Expression Type Object allows an author to deviate to a specific version (better suited to their tooling eco system)

- name: JSONPath
  version: draft-goessner-dispatch-jsonpath-00

- name: XPath
  version: xpath-30

The allowed version values will be enumerated for JSONPath and XPath


Proposal For Copy Writing

I just checked your project and i feel it is missing out some important details like faq, about us, contact us, privacy policy etc. If i you dont mind i am available and i can write it for you.
<EMAIL_ADDRESS>

You can write and send a Pull Request. I can approved it.

i will do that soon. just tell me little about your project. features and
benefits
On Mon, Apr 30, 2018 at 10:42 AM, Tolgahan ÜZÜN<EMAIL_ADDRESS>wrote:

You can write and send a Pull Request. I can approved it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tolgahanuzun/feroniobot/issues/5#issuecomment-385352959,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfjhQE6qEUOuT1PaWrvCNU7N9nnvd_9Yks5tttx-gaJpZM4TsNix
.


Add support for installing via CocoaPods

CocoaPods is currently not supported. For a wider option it should be added.

Work has been done to get this setup in 0472f44e4adbbab6d4598932a73c6b53cc4ff948. The problem currently is that FileKit has not been released with a new version since my fixes on it have been merged. See https://github.com/nvzqz/FileKit/issues/19 for further details.
Note that it is not possible to specify forks or specific commits in a .podspec file. If FileKit doesn't receive an update soon than an alternative solution is to create a fork of FileKit and make a release there.

This was fixed in 7ffe1af738250aca2af2ea6eab0eb8a1fa568f3b.


Enable Dependabot

There isn't a requirements.txt file for the Python dependencies so only GitHub Actions will be monitored and updated.

Waiting for #62 to be merged.

This is clearly unrelated, let's merge this. (#62 will fix the failing check)

But now we get a bunch of dependabot PRs and all their checks will be red, no?

Yeah. :/ So far we got only one, that's not a disaster. :crossed_fingers:


RTF support in compose window

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
6.308
Problem you are trying to solve
Generic plain text emails
Suggested solution
Composer needs support for bullet lists, number lists, font sizes, bold, italics, underline, embedded images, etc.
Screenshots / Drawings / Technical details
No response

Duplicate of #1745


[Feature] An option to set whether the toc is pinned by default

I want the toc to be pinned by default and hope the developer will consider adding an option.
Thanks!

This option has been added


Installation does not seem to work on Mac OS

nevovim V0.9.4
I used packer to install as per readme.  After running "PackerUpdate", I restarted neovim, than tried to run: :Codeium Auth and the response was:

the file ~/.cache/nvim/codeium.log does not exist.

Interesting, after I remove the calls for codeium.nvim to go back to the codeium.vim (the official version), after PackerUpdate command and nvim re-start, I get this:

It seems like packer is no longer maintained. Maybe you can try with lazy.nvim?


Is it possible to set max-width for scrollbar?

Everything works fine. Really good plugin!
Just wondering that is there a way to set max width for scroll bar?
Currently not quite sure how does the script to calculate the scroll bar width.

Duplicate of #125


Mongoose schema

Hi, instead of the mongodb package, I would like to use mongoose instead. I was wondering what would the mongoose schema be for the user model?

I just need oAuth authentication from one provider and mongoose taking care of my database. So I stripped away all the unnecessary code.
In the .env file I've got MONGO_URI, FACEBOOK_ID and FACEBOOK_SECRET filled.
The 'Sign in' button on the client points to /auth/oauth/facebook and I only have callback.js in the auth folder. So I click the button, the app goes to /auth/callback and then back to the index file.
I then tried replacing the Mongodb configuration with Mongoose. Here is my code for next-auth.functions.js file:
require('dotenv').load()
const mongoose = require('mongoose')

const User = require('./models/User')

module.exports = () => {
	return new Promise((resolve, reject) => {
		mongoose.connect(process.env.MONGO_URI).then(() => {
			return Promise.resolve({
				find: ({ id, email, emailToken, provider } = {}) => {
					let query = {}

					if (id) {
						query = { _id: MongoObjectId(id) }
					} else if (email) {
						query = { email: email }
					} else if (emailToken) {
						query = { emailToken: emailToken }
					} else if (provider) {
						query = { [`${provider.name}.id`]: provider.id }
					}

					return new Promise((resolve, reject) => {
						User.findOne(query)
							.then(user => resolve(user))
							.catch(err => reject(err))
					})
				},

				insert: (user, oAuthProfile) => {
					return new Promise((resolve, reject) => {
						new User(user)
							.save()
							.then(user => resolve(user))
							.catch(err => reject(err))
					})
				},

				update: (user, profile) => {
					return new Promise((resolve, reject) => {
						User.findByIdAndUpdate(user._id, user)
							.then(() => resolve(user))
							.catch(err => reject(err))
					})
				},

				serialize: user => {
					if (user.id) {
						return Promise.resolve(user.id)
					} else if (user._id) {
						return Promise.resolve(user._id)
					} else {
						return Promise.reject(new Error('Unable to serialise user'))
					}
				},

				deserialize: id => {
					return new Promise((resolve, reject) => {
						User.findById(id)
							.then(user => {
								if (!user) return resolve(null)

								return resolve({
									id: user._id,
									name: user.name,
									email: user.email,
									emailVerified: user.emailVerified,
									admin: user.admin || false
								})
							})
							.catch(err => resolve(err))
					})
				}
			})
		})
	})
}

Again note that there's no remove function. The reason is prior to implementing mongoose, the example still worked without the remove function and I don't need the option of users cancelling their account. This is my User model set up:
const mongoose = require('mongoose')
const { Schema } = mongoose

const userSchema = new Schema({
	name: String,
	email: String,
	facebook: {
		id: String,
		accessToken: String,
		refreshToken: String
	}
})

const Users = mongoose.model('user', userSchema)

module.exports = Users

I derived this schema from looking at the database directly and seeing what information was being inserted.
When I run npm run dev it says the code has compiled successfully in the terminal. But when I go to localhost:3000,  I get:
This site can’t be reached
localhost refused to connect.
So the server won't start.
After console logging in several places to see where the problem is, if I put a console log in the next-auth.config.js file:
module.exports = () => {
	return nextAuthFunctions().then(functions => {
                console.log(functions)
		return new Promise((resolve, reject) => {
			...
		})
	})
}

I don't see functions logged in the terminal when the code runs. So the functions promise isn't being resolved. Can someone please help with this issue? Here's a link to my code

Never mind I've solved the issue and it's working correctly. Thank you for the awesome package!

I' facing the same issue, could you share how you solve this, thank you in advanced.

Hi @serjt12, I don't remember but here's the repo where I encountered this problem.

Thanks a lot for your answer, I checked your repo but it was having the same issue, thanks anyway...

I made the assumption that you wanted a solution that involved this next-auth module. I recently updated my app and eventually decided to just stick with passport.js without next-auth. Here's the repo if you're interested in going that route.

Thank you very much @edward-hong  I really appreciate your answer, I will check it out...


Add tests for render_final_params and local and remote script runner command construction

This pull request adds unit tests for render_final_params function which we were lacking (we did have various integration and end to end tests, but not unit ones).
It also adds more command construction unit tests for local and remote shell script runners.
Background / Context
I started to work on this issue - https://github.com/StackStorm/st2/issues/4649#issuecomment-487611846.
First step was adding unit tests which were lacking which supposed to fail before I fix the bug. But after digging in and adding unit tests, I simply couldn't reproduce the original issue.
Tests pass and the code itself looks correct. I'm still not sure why this issue happened on CICD (it could be consistently reproduced and there are logs), but for now we at least have some more unit tests we were lacking before.
I will do some more digging in, but for the time being, I can't replicate it locally using latest master (it could be related to an issue in older version, we did make some param util changes and fix in v3.0.0 albeit unrelated ones).

I also confirmed it on new cicd node which runs v3.0.0 and it works fine there. So likely issue related to v2.10.x.
Once this PR is merged, I will close #4649 as can't reproduce / already fixed.


Support new SLO API

Is your feature request related to a problem? Please describe.
The new Dynatrace SLO API started as a preview feature in version 204. Customers, who are part of the preview should be able to leverage the SLO API using Monitoring as Code. Furthermore, when the feature goes GA, we already support it in monaco.
Describe the solution you'd like
Add support for the new SLO API and add a configuration used for the all-configs integration test.

Hu @didiladi is SLO described on here? https://www.dynatrace.com/support/help/whats-new/preview-and-early-adopter-releases/

Hi @163a. The documentation on SLOs is not yet linked on dynatrace.com, but it will be soon.
If you are already interested in the SLO functionality, you can already take a look here: https://www.dynatrace.com/support/help/how-to-use-dynatrace/service-level-objectives/
It will be GA soon.


GeoIP Error Metric

Issues #1548 and #1512 highlight areas for improving GeoIP error handling and failure visualization. After consulting with @bbockelm, we’ve determined that implementing a new Prometheus metric to track GeoIP failures would be ideal. This metric would include several labels:

network, representing the client’s network.
source, indicating whether the error originated from the client or the server.
project, for identifying which project the error relates to.

The overall objective is to generate a ranking of errors by project, allowing for better insight into the frequency and distribution of GeoIP failures.

@patrickbrophy and I chatted quickly:

error_source is repetitive; let's change it to just source.
Let's propagate the information about the source and project down the call stack in a context object.


Update ProtobufConfig/version to 3.18.0

By process of elimination, version 3.18 is the lowest version (after 3.10) that resolves #1713.

you probably want to do the same here: https://github.com/ShiftLeftSecurity/codescience-schema/blob/master/proto-bindings/build.sbt#L11


Can I scrape metrics from VMs using GMP?

Hi,
I couldn't find an answer to my question anywhere in the docs. If I am missing something, please guide me.
Is it possible to scrape metrics from GCE's VMs with GMP?
If yes, where should I start looking?
If no, then what is the preferred way to scrape prometheus metrics exposed in VMs so I can access them in Google Monitoring?
Thanks in advance.

In theory you should be able to run GMP on GCE as a drop-in replacement for your Prometheus server, although we only tested it in Kubernetes environments.
Assuming you are running in a non-containerized environment, you can run it on GCE following instructions here: https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-unmanaged#gmp-binary
Wanna give it a try?

Hi,
Thanks for response. I already did it this morning. I can confirm that GMP Prometheus binary works fine on VM.
Cheers.

Great to hear! Thanks.

So to sum up the way is to install GMP Prometheus on VM and not to use Kubernetes Prometheus to monitor VMs. Am I right?

By "Kubernetes Prometheus" do you mean kube-prometheus? If so, yes kube-prometheus is for Kubernetes environments only. If you are running on GCE, installing GMP on VM is the right way to go.

Yes. Great. Thanks for claryfying.


Dart revamp

Thanks, @a14n !
Look okay, @BanzaiMan ?

This has been deployed to staging. Could you test it? If it goes well, we can merge and deploy later this week. Thank you!

I tried running with this and I'm getting a pile of pain
See https://staging.travis-ci.org/kevmoo/shelf/builds/559094
I'd expect each task to have a separate job – but no luck.
Also: just blank output.
Any ideas, @a14n ?

@kevmoo Ah, sorry about that. There was another component that needed to be deployed before dart_task could be recognized as a matrix dimension. This is done now. Please push a new commit to test. Thanks.

Looking waaaay better – https://staging.travis-ci.org/kevmoo/shelf/builds/559143
Still now output, though.
Going to try one more quick, too.

The log display issue is most likely due to our ongoing development. I suspect it'll get better in a few hours.

I wish there was a way to show the task on this page – https://staging.travis-ci.org/kevmoo/shelf/builds/559143
...not sure if that's a feature request for travis or what...

The task display would be a separate PR for travis-web once we ship this.

https://staging.travis-ci.org/kevmoo/shelf/builds/559250
I'm trying to get the build matrix to work w/ dart_task and having no luck.
Help?

I think the issue is with staging state and not with this PR. I made a quick test some minutes ago and it was worked as intended.

https://staging.travis-ci.org/a14n/dart-rational/builds/559162
The build matrix was ok. There were some failing jobs but due to my codebase.

The build matrix was ok. There were some failing jobs but due to my codebase.

I'm breaking with allow_failures in https://staging.travis-ci.org/kevmoo/shelf/builds/559250
...that's what I meant by matrix...

It looks like matrix expansion for dart_task has been removed from staging... @BanzaiMan can you confirm ?

@kevmoo @a14n it was. It's been fixed now.

@BanzaiMan thanks
Staging looks more stable now and my tests are ok ( @kevmoo I also test allow_failures with https://staging.travis-ci.org/a14n/dart-rational/ )

@a14n @kevmoo Would you like to perform any more test?

it's ok for me.

I'm a bit nervous.
I've been trying to run the existing Dart angular2 tests (some of our most complex) against staging without clear results.
See https://staging.travis-ci.org/kevmoo/angular2/
VS https://travis-ci.org/dart-lang/angular2

@kevmoo Looks like our messages crossed paths. We are having problems with staging at the moment, and we are looking into it. I'll hold off deploying until we resolve this and you have another look at your results.

Thank you!

@kevmoo OK. Staging is back. Please check your results.

Rerunning now - https://staging.travis-ci.org/kevmoo/angular2/builds/559295

@kevmoo Looks like your build needs some user input.

@kevmoo Looks like your build needs some user input.

Yup. Which is weird. Because this "just works" on the stable branch. I wonder if the install content-shell logic that @nex3 moved around got broken some how...

The content_shell_dependencies_install fold in which the user input occurs has not been changed in this PR. That's really strange. Perhaps something specific with staging ?

It is not clear to me why the difference manifests this way, but it appears that the production and staging have different Precise images. Production https://travis-ci.org/dart-lang/angular2/jobs/215658287#L23 vs Staging https://staging.travis-ci.org/kevmoo/angular2/jobs/559296#L23

We can roll it out to Production, test it quickly, and revert if the problem manifests there.

I tested the build script with the docker image (https://docs.travis-ci.com/user/common-build-problems/#Running-a-Container-Based-Docker-Image-Locally) and the apt-get command does appear to go through.
If we cannot agree on how to deploy this, I will revert his, so that we can test more thoroughly.

@BanzaiMan If you want to roll the dice, I'm happy to try.
I can rerun https://travis-ci.org/dart-lang/angular2/builds/215658286 immediately to see if it stays green.

...are you going to be around for a while to do the rollback if things blow up?

We should also make sure we align with un-reverting the docs - https://github.com/travis-ci/docs-travis-ci-com/commits/gh-pages/user/languages/dart.md

@kevmoo OK. Let's try. I'll deploy around 17:30 UTC (12+ minutes from now).

@kevmoo Deployed to production.

Rerunning https://travis-ci.org/dart-lang/angular2/builds/215658286
On Tue, Mar 28, 2017 at 10:30 AM, Hiro Asari<EMAIL_ADDRESS>wrote:

@kevmoo https://github.com/kevmoo Deployed to production.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/travis-ci/travis-build/pull/1001#issuecomment-289844861,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCilJu4597c7jOli3l-0mC5wp55g5yks5rqUPFgaJpZM4MnUKn
.

https://travis-ci.org/dart-lang/angular2/jobs/215658287 Got past the dependency installation phase.

This makes me nervous: https://travis-ci.org/dart-lang/shelf/jobs/216033195
Where this works: https://staging.travis-ci.org/kevmoo/shelf/builds/559992

@kevmoo https://travis-ci.org/dart-lang/shelf/builds/216033193 seems to have incorrect matrix configuration. (It should have 30=6x5 jobs, but only shows 6.)
Could you try pushing a new commit to this branch?

@BanzaiMan - done
https://travis-ci.org/dart-lang/shelf/builds/216039265
🤞

Hmm. This is strange. I'll look into this.

Weird!
Same commit – https://staging.travis-ci.org/kevmoo/shelf/builds/560030
So staging is doing the matrix correctly. But it's not working on master. 😕

same here https://travis-ci.org/a14n/dart-rational/builds/216040112
no matrix expansion

Sorry. The closed source part had not been deployed to production yet. I did so now.
Please push another commit. Thank you for your patience!

Here we go again: https://travis-ci.org/dart-lang/shelf/builds/216042341

The result is ok for my test (https://travis-ci.org/a14n/dart-rational/builds/216041592)

Looks much better. 28=6x5+1-3 jobs in the matrix.

I think I did this one correctly -
https://travis-ci.org/dart-lang/shelf/builds/216043979
So far so good...
On Tue, Mar 28, 2017 at 11:00 AM, Hiro Asari<EMAIL_ADDRESS>wrote:

Looks much better. 28=6x5+1-3 jobs in the matrix.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/travis-ci/travis-build/pull/1001#issuecomment-289853790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCilKvTgJHzGEUC8CN-840KRLa3U0vks5rqUrZgaJpZM4MnUKn
.

For showing dart_task in the build matrix page, you'd want something like this PR: https://github.com/travis-ci/travis-web/pull/339.

For showing dart_task in the build matrix page, you'd want something like this PR: travis-ci/travis-web#339.

@BanzaiMan I'm happy to do this... should I?
Also – can we get the docs refreshed? https://github.com/travis-ci/docs-travis-ci-com/commits/gh-pages/user/languages/dart.md

This seems like an unrelated break - https://travis-ci.org/dart-lang/shelf/jobs/216043982

See https://github.com/travis-ci/docs-travis-ci-com/pull/1066 for docs update.

@kevmoo https://travis-ci.org/dart-lang/shelf/jobs/216043982 shows a failure with xvfb-run command.

@BanzaiMan https://github.com/travis-ci/travis-web/pull/1024 😄


CIS-5.2.12 missing from centos-7-level-1-scored-v2-1-0.yaml

Even though it is in centos-6-level-1-scored-v2-0-1.yaml as well as in centos-7-level-1-scored-v2-0-0.yaml.  Checked CIS benchmark v2.1.0 and v2.1.1, 5.2.12 is present.

Thanks for the report.

Pull request 50 added

PR 56 merged in hubblestack_data fixes this


Updated owner value

Updated PM owner

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

@CelesteDG - as a reminder, Microsoft employees need to use the private repo for future content updates. Thanks.

@Jak-MS - D'oh! Thank you for the reminder. I forgot to update the URL to add the private bit. Thank you for merging this in.


Fix ChatBedrock to enable "test_stop_sequence" integration test

Add stop attribute to ChatBedrock and ChatBedrockConverse classes to fix the standard "test_stop_sequence" integration tests.
tests/integration_tests/chat_models/test_standard.py::TestBedrockStandard::test_stop_sequence FAILED
tests/integration_tests/chat_models/test_standard.py::TestBedrockUseConverseStandard::test_stop_sequence FAILED

Hello @3coins, is anyone working on this issue right now? If no, may I take it?

@Forma-Lin
Plz feel free to work on this. Let me know if I can help with anything to get you started. Assigned the issue to you.

@3coins
Hi, I setted up the project following the CONTRIBUTING.md, and run integration test. But the results seems wired. I got lots of tests failed and I cannot find the standard "test_stop_sequence" integration tests in the output. Is there something else I should set up before running integration tests?

@3coins
My teammate have submitted a PR, and want to kindly invite you to review it.
The PR address is: https://github.com/langchain-ai/langchain-aws/pull/290


Add Better Dres from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of Cooper, to add Better Dres to CKAN.
Mod details:
name = /mod/1974/Better%20Dres
author = Cooper
abstract = I mod to expand Dres to make it more interesting
license = MIT
Homepage = https://discord.gg/Br8Y6yE
description = Dres is too boring in this game I hope I can improve that by adding on to it.
Complete work so far.
-Fixed Dres orbit to allow easier journeys
Future plans.
-A small moon or too
-A very, Very, VERY thin atmosphere.

Want to help? here is the mod discord: https://discord.gg/Br8Y6yE
Please direct questions about this pull request to Cooper.

#rebuild

#rebuild

4182 [1] FATAL CKAN.NetKAN.Program (null) - /tmp/CdFileMgr/a88c758a-7f2e-41.tmp is not a valid ZIP file: Error in step EntryHeader for BetterDres/BetterDres/BD_DistantObjectEnhancement.cfg: Exception during test - 'Compression method not supported'

Version from Dec 2018 is labeled 'Final Release", there's no forum thread. Probably not going to be able to get this archive fixed.


bumping marathon to 1.4.3

https://github.com/mesosphere/marathon/releases/tag/v1.4.3
High Level Description
Bugfix release
Changes from 1.4.2 to 1.4.3
Fixed Issues

MARATHON-7267 Enforce validation for pod container names
[DCOS-14890] Fix default scheme for HTTP health checks in pods
[DCOS-14303] Fix issue in which Marathon would fail to launch if hostname is not resolvable (but still specified from the command line)

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

nothing to rebase.. restarting the test

It appears to be an issue  with https://github.com/dcos/dcos/blob/1.9.1/packages/dcos-launch/buildinfo.json#L10-L11
which looks incorrect on 1.9.1
@mellenburg

@adam-mesos the fix for this is on PR https://github.com/dcos/dcos/pull/1579
let me know how you want to handle this... I'm not sure if you want me to wait for that to merge or ?

@kensipe can you please rebase this now (#1579 landed)?

The pyinstaller failure should be no longer applicable now.
@kensipe  - can you please do rebase from master and push this again. I'd like to include this in the next merge.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

I cannot push to this PR / branch (since I am not an admin/super-user).
Will require @kensipe  to update this.

Several CI failures still need investigating


Passing properties trough java opts breaks bootstrap

Passing a --java-opt breaks bootstrap on the current master branch, after sbt clean cli/pack:
Example behaviour:
λ gaborpihaj [Workspace/private/coursier] at master
→ modules/cli/target/pack/bin/coursier bootstrap io.get-coursier:echo:1.0.1 -o echo
λ gaborpihaj [Workspace/private/coursier] at master
→ ls -l echo
-rwxr-xr-x  1 gaborpihaj  staff    18K 11 Feb 18:43 echo

Broken behaviour:
→ modules/cli/target/pack/bin/coursier bootstrap --java-opt -Dfoo=bar io.get-coursier:echo:1.0.1 -o echo

Cannot find default main class. Specify one with -M or --main.

That originates from https://github.com/xerial/sbt-pack/pull/118/files, that makes the sbt-pack based launcher pass the -D options to Java rather than the launched application. The coursier launcher itself, once packaged, is fine.

Indeed, after publishing the package locally and assembling it with the stable coursier it started working. @alexarchambault thanks for the help!