Add Article for Hello World in COBOL

Check out the code: TheRenegadeCoder/sample-programs#90

Hey @jrg94
Can I write this article?
If yes, can you tell me what are the contents that you are looking for in this article?

Yup! Here's the code you would be writing about: https://github.com/TheRenegadeCoder/sample-programs/blob/7682891c83b76aba3bf863366683a66b04a1b0c7/archive/c/cobol/hello-world.cbl
Here's the general template that we use: https://github.com/TheRenegadeCoder/sample-programs-website/blob/master/templates/CODE_ARTICLE_TEMPLATE.md


backup: use fixed sizes for concurrency and flush threshold

PR: https://github.com/cockroachdb/cockroach/pull/68105
From release notes:

RESTORE no longer dynamically reads from the kv.bulk_ingest.batch_size cluster setting to determine its batch size. If the value is updated, RESTORE jobs need to be PAUSEd and RESUMEd to adopt the updated setting. [#68105][#68105]

Closing issue - no user facing docs required here.


chore: HDH-84 update cert pages

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

@ravilach there are a few placeholders in the branch, please update the content before merging the PR.

Preview environment: https://hdh.pr.harness.io/pr-836

Preview environment: https://hdh.pr.harness.io/pr-836

LGTM


IDVA6-1102 Nav bar for mobile view fixed

Link to Jira:
https://companieshouse.atlassian.net/browse/IDVA6-1102
Changes:

Script and stylesheet to fix the menu in mobile mode added

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


[FEATURE] Provide a convenient way to generate an export with a specific desired identifier.

Is your feature request related to a problem? Please describe.
I am writing a macro which should, among other things, export an identifier specified in the macro call. I can't seem to find a way to do this. In particular, function bodies are not allowed to export identifiers, so it seems I need to use the $$ts builtin macro, but if I write e.g.
$$ts!(`export const ${name} =  ${desired_value};`)

the identifier is mangled presumably for hygienic reasons. I suspect that I could use $$raw to do this, but it is hard to find good documentation on how to use factory.createExportAssignment or factory.createExportDeclaration. If you think it's best to do this with $$raw rather than add a facility for exporting, I respect that but if you have any pointers to information about how to use the Compiler API for something like this they would be welcome.
Describe the solution you'd like
I could imagine several designs, but I think the easiest to use would be another flag on $$define which specifies whether to export the definition, defaulting to false. Another possibility would be an "unhygienic" option to $$ts. Yet a third option would be an explicit $$export built-in macro.
Describe alternatives you've considered
I believe these are covered above.
Additional context
If a PR would help make this happen I am willing to try even though I am almost completely unfamiliar with the TypeScript Compiler API. But for this, I'd need an indication of the desired design for allowing exports. And if you have any suggestions for useful resources to get intformation about the TypeScript API it would be appreciated.

I think it's a good idea to add such an option to the $$define macro, it's a simple change if you know the compiler API so I've gone ahead and added it :)
There isn't really much documentation on the typescript transformer API, it's mostly tinkering with it and seeing what works and what doesn't, but here's a good starting point: https://github.com/itsdouges/typescript-transformer-handbook
The typescript AST playground is also really good for experimenting and seeing what data each node/symbol/type has: https://ts-ast-viewer.com/#code/FAYw9gdgzgLgBADzgXjgJgNzCA
The next version will be coming very soon but in the meantime, you can use the $$raw version:
function $export(name: string, value: unknown) {
   $$raw!((ctx, name: ts.Expression, value: ts.Expression) => {
      if (!ctx.ts.isStringLiteral(name)) throw ctx.error(name, "Expected a string literal.");
       return ctx.factory.createVariableStatement([ctx.factory.createToken(ctx.ts.SyntaxKind.ExportKeyword)], ctx.factory.createVariableDeclarationList([
         ctx.factory.createVariableDeclaration(name.text, undefined, undefined, value)
     ], ctx.ts.NodeFlags.Const));
   });
}

Thanks for the quick turnaround and for the upcoming update! I'll give the raw version a try.

Hmm, when I add
// From the creator of ts-macros; temporary until next release
function $export(name: string, value: unknown) {
   $$raw!((ctx, name: ts.Expression, value: ts.Expression) => {
      if (!ctx.ts.isStringLiteral(name)) throw ctx.error(name, "Expected a string literal.");
       return ctx.factory.createVariableStatement([ctx.factory.createToken(ctx.ts.SyntaxKind.ExportKeyword)], ctx.factory.createVariableDeclarationList([
         ctx.factory.createVariableDeclaration(name.text, undefined, undefined, value)
     ], ctx.ts.NodeFlags.Const));
   });
}

$export!("fred", 3)

to my file (as well as the necessary imports), and execute tsc, I get:
/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:118051
              throw e;
              ^

Error: Debug Failure. Unhandled SyntaxKind: VariableStatement.
    at pipelineEmitWithHintWorker (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:112071:13)
    at pipelineEmitWithHint (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:111615:9)
    at pipelineEmitWithComments (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:115399:7)
    at pipelineEmit (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:111564:7)
    at emitExpression (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:111548:7)
    at emitExpressionStatement (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:113077:7)
    at pipelineEmitWithHintWorker (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:111759:20)
    at pipelineEmitWithHint (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:111615:9)
    at pipelineEmitWithComments (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:115399:7)
    at pipelineEmit (/home/glen/code/typocomath/node_modules/.pnpm/typescript@5.1.6/node_modules/typescript/lib/tsc.js:111564:7)

Guess I should just wait til the next release? (It's totally OK for me to wait, just posting this info in case it's helpful to you. Thanks again.)

The snippet I provided is incorrect because currently to make it work you have to return an array literal from the $$raw function, which will no longer be the case in the next update, sorry! Here's the code which works in the current version:
function $export(name: string, value: unknown) {
   $$raw!((ctx, name: ts.Expression, value: ts.Expression) => {
      if (!ctx.ts.isStringLiteral(name)) throw ctx.error(name, "Expected a string literal.");
       return [ctx.factory.createVariableStatement([ctx.factory.createToken(ctx.ts.SyntaxKind.ExportKeyword)], ctx.factory.createVariableDeclarationList([
         ctx.factory.createVariableDeclaration(name.text, undefined, undefined, value)
     ], ctx.ts.NodeFlags.Const))];
   });
}

Ah, so there is a hitch. If testExp.ts contains this definition of $export and the call:
$export!('fred', 7)

and the contents of testImp.ts are:
import * as tst from './testExp.js'

console.log('Fred is', tst.fred)

then the combination fails to compile, with the error:
src/testImp.ts:3:28 - error TS2339: Property 'fred' does not exist on type 'typeof import("/home/glen/code/typocomath/src/testExp")'.

3 console.log('Fred is', tst.fred)
                            ~~~~

Found 1 error in src/testImp.ts:3

So I guess TypeScript doesn't ever find out about the export -- you did say in the documentation that the transform takes place after the typechecking stage. Any way around this snag, or should I just give up on the idea of the macro generating the export? Obviously I need to be able to use the exported symbol from other TypeScript modules... Thanks for your thoughts.

So I guess TypeScript doesn't ever find out about the export -- you did say in the documentation that the transform takes place after the typechecking stage.

Yeah, the transformer alone cannot do anything because by the time it's run the error is already registered, however, there is a way around this and I'm planning on solving this exact issue really soon!

All right, we will be watching for future releases. Thanks for all of your help.

Version 2.4.0 adds a new transformer that fixes this issue!
If you have any questions feel free to start a discussion or create an issue!


Project Status

About Project Status
I noticed the following about the project:

Last commit: November 21, 2022
Last release: May 31, 2022
Open PRs: 6 (latest from November 9, 2022, unmerged)
Open issues: 39 (latest from February 22, 2024, no replies; previous from November 29, 2023, no replies)

Given this activity, is the project still being actively maintained?

AFAIK, Nick bowed out at 2023. Before that, he suggested us moving to Astro.

Astro looks nice but trying to find the real difference from Astro, Astro + Svelte and SvelteKit as it is easier to keep up to date with one toolset than many.


Pull Request for Class Mediator Samples

Hi
Please review and commit
Thank You
Erandi

Hi Chathurika,
When you commit the custom mediator, please do not commit target folder, .classpath, .setting .project files. You can mention in the read me where and how to build. If you want you can have the org.wso2.carbon.custommediator-0.0.1-SNAPSHOT.jar file outside the target folder.

Hi Chathurika,
Class mediator cannot be built in Java 8. Can we mention that it should be Java 7 in Read me.

Hi Chathurika,
Please remove CustomClassMediator.java~ file in wso2-qa-artifacts/products/wso2_ESB/product_features/features/mediators/extension_mediators/class_mediator/esb500_classmediator_1/org.wso2.carbon.custommediator/src/main/java/org/wso2/carbon/custommediator.
and

Hi Chathurika,
In esb500_classmediator_1,  ClassProxy_1.xml,
<proxy xmlns="http://ws.apache.org/ns/synapse"        name="ClassProxy_1"        transports="http https"        startOnLoad="true"        trace="disable">    <description/>    <target inSequence="class_seq_1">       <endpoint>          <address uri="http://<IP_ADDRESS>:9793/services/**OrderAcceptService**/"/>       </endpoint>    </target>    <publishWSDL uri="http://<IP_ADDRESS>:9793/services/**OrderAcceptService**?wsdl"/> </proxy>
The above proxy endpoint and publishWSDL uri should be changed since the aar deployed in App server is deployed as http://:/services/OrderInfoAccept?wsdl

Also please mention in the Readme, once you copy the org.wso2.carbon.custommediator-0.0.1-SNAPSHOT.jar  ESB server should be restarted for changes to be affected. May be you can change "ESB server should be up and running" in to ESB server should be restarted, up and running

** Please double check this for the other sample esb500_classmediator_2 as well it also have the same issue in .
Thanks

Please remove the .classpath  .project  .settings , ~ files and target folder.
Thanks

Hi Chathurika,
Sample 2 doesnt work for me and giving an error.  ERROR_CODE = 0, ERROR_MESSAGE = Error occured in the mediation of the class mediator. please check that.
Also in sample 2, esb500_classmediator_2 README  - sequences: class_seq_1.xml should be changed as  - sequences:** class_seq_2.xml**
Thanks

Merging Chathurika's artifacts


Add official API for fading out unused code

Add an api that other extensions and languages can use to grey/fade out unused code and variables. JS/TS already implements this using a proposed API
/cc @jrieken @dbaeumer

Current Proposed Design
Use diagnostics to power this feature:
/**
 * Additional metadata about the type of diagnostic.
 */
export enum DiagnosticTag {
	/**
	 * Unused or unnecessary code.
	 */
	Unnecessary = 1,
}

export interface Diagnostic {
	/**
	 * Additional metadata about the type of the diagnostic.
	 */
	customTags?: DiagnosticTag[];
}

This approach works well because there are often quick fixes associated with unused code.
Alternative Proposal
Design a new API that allows more generic semantic coloring. Perhaps something similar to DiagnosticCollection
enum HighlightingKind {
    Unused,
}

class Highlight {
    kind: HighlightingKind;
    range: Range;
}

class HighlightCollection {
    // like a diagnostic collection of highlights
}

This approach would require that we also introduce a new "silent" DiagnosticSeverity that does not render anything in the  editor.

How does this work with existing language servers that already generate warnings for unused variables? Does the region become grayed out, or do squigglies have precedence, or are both rendered? Is the behavior the same if a language server has a setting that allows the severity of warnings to be increased to errors or decreased to some other severity?

@mattacosta This will not effect existing behavior; warnings and errors for unused variables will remain the same. The current proposed api is opt-in and just adds supplemental information to a diagnostic which tells vscode to also render it as faded/grey

Another proposal would be a semantic highlights provider (pull instead of push model). So something like this:
enum HighlightingKind {
    Unused,
}

class Highlight {
    kind: HighlightingKind;
    range: Range;
}

interface HighlightProvider {
  provideHighlights(document, range, token): ProviderResult<Highlights>
}

I know the title specifically mentions "fading out unused code", but it seems to me that this would be a more general API. Would it be appropriate to also include something like Deprecated as a DiagnosticTag or HighlightingKind which could have its own associated styling?

@mjbvz Roslyn sees to use a pull-model (http://source.roslyn.io/#Microsoft.CodeAnalysis.EditorFeatures/Implementation/Classification/SemanticClassificationUtilities.cs,2ef4a2c8d3e1fe6f,references) but @DustinCampbell might know more about it

The Visual Studio editor uses a pull model in it's ITagger stuff. The code you referenced is from the Roslyn infrastructure to support the VS editor.
FWIW, we've found the VS editor's pull model to be very advantageous. Computing semantic highlighting can be very expensive. So, it's nice to be able to...

Compute highlights asynchronously and then provide a notification when they are ready.
Only provide highlights for the current view port (along with some lines above and below) rather than the entire view.

Weighing in on the gray/faded decision—the current behavior of removing syntax highlighting is confusing because the concern of whether code is used is distinct from whether it's syntactically valid. A common process for me is

Write unused code.
Observe that its syntax is valid.
Use the code.

and completely graying out the code blocks at the second step.

@DustinCampbell Is the CustomTags value on diagnostics used at all for colorization of unused variables in VS? That's what I based the current proposed vscode API off of but I don't know how VS actually uses customTags

The CustomTags property can be used for information that might be interesting to a consumer that's inspecting the diagnostic (for example, a code fix that responds to that diagnostic). In VS, the presentation layer looks for "Unnecessary" among the CustomTags to decide whether the span should be "faded" (not grayed) -- which is orthogonal from colorization and diagnostic severity.

Thanks @DustinCampbell. Our current greyin-out serves the same purpose as fading-out in VS. I'm going to switch us over to use fading out too, grey out was just easier to introduce to start
@jrieken Looks like VS is handling unused fade-out separately from general semantic coloring. Any opposition to doing this as well on our side? That way we don't have to get into implementing generalized semantic colorization just yet. Using diagnostics also makes sense from a language implementer perspective, at least for js/ts

Looks like VS is handling unused fade-out separately from general semantic coloring. Any opposition to doing this as well on our side?

Unsure, looks like a one-off API and we shouldn't shy away from doing the real thing (not saying it must be you and me implementing it 🤣)

I support @jrieken here. Reasons are:

this introduces three phases in which color change which will simply be more disturbing for the user (instead of two)
since we neither have CustomTags nor semantic coloring we should try to go for the more general approach. I can imagine that VS introduced CustomTags and later on semantic coloring. If semantic coloring would have been first may be VS would have never used CustomTags to influence coloring (I agree it is a guess). So the real question here is if there is something that can be achieved with CustomTags which can't be achieved with semantic coloring.

Thanks @DustinCampbell. Our current greyin-out serves the same purpose as fading-out in VS. I'm going to switch us over to use fading out too, grey out was just easier to introduce to start

👍

So the real question here is if there is something that can be achieved with CustomTags which can't be achieved with semantic coloring.

Probably anything that requires presentation of a custom UI element. For example, if for some reason you wanted to show the peek widget along with a diagnostic containing a specific tag. Stuff like that can't be done with semantic coloring.

I think unused code is a common enough case that it could be handled by a more targeted Api.
If we use a general semantic coloring API for unused variables, TS for example will have to maintain:

A set of invisible diagnostics for the unused symbols. These diagnostics would be used for code actions and hovers
A set of semantic coloring locations corresponding to each unused symbol

Not terribly difficult to implement but every language that has unused code support will have to re-implenent the same thing. It's also going to be more chatty in terms of extension communication
I understand that a more general API is preferable but still feel that having some semantic colorizations tied to diagnostics makes sense in cases like unused variables or invoking a deprecated api

/cc @rchande

I reviewed some existing vs code language implementation and believe they would be able to easily adopt a CustomTags type property. Most already show unused variables as warnings. For what it's worth, intellij also seems to be using diagnostics for their dead code highlighting.
Other types of tags we could consider adding in the future:

Deprecated
Experimental / platform specific
Redundant (probably the same as unnecessary)
Uninitialized

The important part is that these potential tags would provide both a colorization modifier and hover information that tells users exactly why the colorization is occurring and how to fix it.

@mjbvz I'm not sure if I entirely follow. As I understand it, your proposal is to modify the definition of an LSP diagnostic in order to reuse the diagnostic provider, but I don't see a reason why a language service, with its own custom definition of a diagnostic, couldn't just send them to its own highlighting provider which would in effect just pass-through the relevant data.
In general though, my primary concern with the diagnostic approach is that it may not work well for certain languages and/or situations. For example, it's entirely reasonable for unused code within a preprocessor directive to not have a diagnostic at all, since there is nothing inherently wrong, or for a diagnostic span to not cover the same area that should be faded.

Yes they could. There are a few problems with this approach however:

Language services now have to maintain both diagnostics and highlights. How this is implemented may not be consistent
The colorization and diagnostics can get out of sync
It's more chatty
We don't have a story for generalized semantic coloring yet and solving it is complex

Even in the preprocessor case, I believe we still would want to provide some sort of feedback to users on why a piece of code is faded out (and optionally quick fixes and other tools to fix this). Using diagnostics lets us to that

Another concern is that the analysis to determine the symbol kind of identifier (semantic highlighting) and where a piece of code or not is very different and the latter is potential much more expensive.

Agreed.
I also wanted to add that as more and more tags are added, you are also asking the code that generates the diagnostics to perform more and more potentially complex tasks. All for an editor that may not even support fading (or some other yet to be added feature) in the first place.

@mattacosta: To be clear, I was arguing that faded code detection should be part of diagnostic analysis. Semantic highlighting is an orthogonal feature. However, deciding that something should be faded often happens during diagnostic analysis. For example, it would be during diagnostic analysis that an unnecessary cast would be identified. That could be a warning, error, ignored, etc. However, the presentation in the editor should be that it's faded.

@DustinCampbell The way I see it, semantic highlighting can have many possible triggers. In the case of unused variables or an unnecessary cast, I agree that diagnostics should be one of those triggers, but we should avoid using tags on a bunch of (probably hidden) diagnostics as the sole trigger. For example, someone may want to trigger semantic highlighting on a symbol that has no diagnostics attached to it. In this case, it wouldn't make sense to add a diagnostic with a tag just so the editor can find it later, because the highlighter could run it's own logic to find it.


[Feature] Support setting sub-addresses of VM network interface

What would you like to be added:
Support setting sub-addresses of VM network interface

https://github.com/yunionio/dashboard/pull/6910


Reorder "Library skeleton project" to 3rd in the list for create-svelte

Describe the problem
I've been seeing reports of users mistakenly choosing "Library skeleton project" because it's 2nd on the list in create-svelte, resulting in confusion.  Moving it to be 3rd should help people avoid this mistake.
Describe the proposed solution
Changing the template name from libskeleton to skeletonlib sorts it out 😉
Alternatives considered
No response
Importance
nice to have
Additional Information
Happy to submit the PR from my fork where I tested it.  If so- would the PR warrant a changelog?

I don't have strong thoughts about the change itself - but, yes, any change that results in user-visible changes should have a changeset, because it's the presence of the changset that marks a package as needing to have a new release cut. Otherwise the change would just sit unreleased until the next change with a changeset happened.

The order was bugging me quite a bit. I personally would find a PR very welcomed


support jsonrpc

#11

Improvents for current example are welcome.
https://github.com/reagento/dataclass-rest/blob/master/examples/json_rpc.py


Feature Request - Ability to sort repository lists on Dashboard

It would be nice if we could sort these lists A-Z.
Also, another nice thing would be to have the option to prioritize the non-fork repositories in the list.
Image for reference:

Regarding the non-fork repos, you get those when you click the 'Sources' tab

👎 I don't really see the usefulness of A-Z sorting. Just use the search if you're looking for something specific. That list is mostly useful to quickly go to recently active repos.

Also, another nice thing would be to have the option to prioritize the non-fork repositories in the list.

Click "Sources".


"My requests" not visible when total number of BAR_Requests > Data Row Limit canvas app setting

When the building access app stores more than 2000 requests (or reaches the data row limit setting for the canvas app), any requests above the threshold are not shown in the "My requests" section of the building access app. On closer inspection (via the powerapp "Monitor" feature) it looks like ALL requests are being returned before it is filtered and when the number of rows breach the data row limit threshold, the additional rows are truncated. When opening the app in edit mode, we can see some delegation warnings, even though SharePoint is supposed to support delegation. Is there anything we can do to resolve this in setup/config without amending the code or is there a bug?

Tried a few different ways to get more data but working with MS they seem to think its the volume of data in BAR_Requests thats causing our issue.
We have 3 time slots, AM, PM, Full Day and each booking creates three records. at the moment we have 124K records and when a user withdraws the booking it only updates the one record and not the other two.
We're going through and trimming the data at the moment and wanted to share part of the flow that i'm using to do it.
{     "inputs": {         "host": {             "connection": {                 "name": "@parameters('$connections')['shared_sharepointonline']['connectionId']"             }         },         "method": "get",         "path": "/datasets/@{encodeURIComponent(encodeURIComponent('https://domain.sharepoint.com/sites/BuildingAccess'))}/tables/@{encodeURIComponent(encodeURIComponent('8ec97f6e-fcf0-4348-be95-aec457b711db'))}/items",         "queries": {             "$filter": "Created le '@{addDays(utcNow(), -180, 'yyyy-MM-dd')}'"         },         "authentication": "@parameters('$authentication')"     },     "runtimeConfiguration": {         "paginationPolicy": {             "minimumItemCount": 500         },         "staticResult": {             "staticResultOptions": "Disabled",             "name": "Get_items0"         }     },     "metadata": {         "flowSystemMetadata": {             "swaggerOperationId": "GetItems"         },         "operationMetadataId": "cb6782d0-9753-49ec-a716-219b08b5b8b4"     } }


Some changes and questions about chunks in preparing data and saving data in separate files

I found out when saving data in separate files (trial_) there will be errors as the function doesn't have the switch_data to continue so I made some changes and also there are some parts that need to be updated

@RoonakR Do you want to review my additions before merge? Otherwise we can merge


[Improvement][AMS]:  log file should contain log level higher than current level

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
currently,   ams-info.log contains info level log only.   the log file should contain logs which level higher than the current level.
How should we improve?

the log file should contain all logs which level higher than current file log level.
the log file whose file size is usually small should be rolling by file size, meanwhile whose file size is usually bigger should be rolling by date. ( error log rolling by file size,  info log rolling by day, disable debug log in default)

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Subtasks
No response
Code of Conduct

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

In my opinion, we should provide these log files：

ams-error.log: log fetal and error messages and rolled with file size
ams-info.log: log fetal/error/warn/info messages and rolled by day
ams-debug.log log fetal/error/warn/info/debug messages and rolled by day and default to be disabled

All logs need to be output to a file instead of console.

But, this may result in large info and debug log files.

According to my operation and maintenance experience, you will need all kinds of log information when tracing a problem, separate level layout makes this quiet hard.

@hameizi if the ams-info.log file has too many results, that could only mean that should log so many logs at the INFO level.

I think the backend thread shouldn't log to the INFO log at each schedule.   The INFO log is only triggered by user actions, the backed thread log nothing if anything is ok and if something is wrong write WARN or ERROR logs.

I support that ams-info.log contains all fetal/error/warn/info logs, which brings great convenience when we have to know what happened before the error.

ams-error.log: log fetal and error messages and rolled with file size
ams-info.log: log fetal/error/warn/info messages and rolled by day
ams-debug.log log fetal/error/warn/info/debug messages and rolled by day and default to be disabled

Based on the previous discussion, do we define log files like this?

resolve this issue in #701


Google Gemini Support

What would you like to be added:
Support for Recently launched Google Gemini
https://ai.google.dev/
Why is this needed:
Gemini is the latest AI Model from Google. It is a direct competitor of OpenAI's GPT
Anything else we need to know?

I think we need to use https://www.nuget.org/packages/Google.Apis.Aiplatform.v1beta1 when we start implementing this

@HavenDV Google Gemini doesn't have any C# SDK yet, we need to use their REST APIs. I have started working on it. I should have it completed within 2-3 days.

I'm inclined to believe that it exists, it's just not documented.
You need to take a closer look at this, there are recent changes here:
https://github.com/googleapis/google-api-dotnet-client/tree/main/Src/Generated
https://raw.githubusercontent.com/googleapis/google-api-dotnet-client/main/Src/Generated/Google.Apis.Aiplatform.v1beta1/Google.Apis.Aiplatform.v1beta1.cs
Even if it turns out that this is not the case, you can also first check if there is an openapi/swagger specification here, and use that for automatic generation using NSwag/Kiota


Fix Sketch Palettes for Sketch 53

#77  – I'm able to load, save and clear palettes again ONLY for document colors.
Sketch appears to have removed app.globalColors, still figuring out the proper replacement for this.
But at least some if it is working again.
EDIT – Global assets/colors is also fixed.

And global colors + gradients is also fixed.

@andrewfiorillo Let me if any edits are needed + how you want to bump the version number.

@mathieudutour thanks for the suggestions and a moment of your valuable time!

@kristof  @mathieudutour thanks for all of your help getting this fixed up! Really appreciate it.

Amazing guys @kristof @mathieudutour @andrewfiorillo , thanks a lot for fixing this so fast!


Fixing jsdoc parsing of functions that are defined over multiple lines (Fixes #410)

As it was implemented, the jsdoc parser would look only the first non-blank line immediately preceding a function declaration. However, the line that was set as the beginning of a function declaration was where the opening bracket ({) was. This is insufficient for functions whose definitions span multiple lines. For example, this declaration would not find the comments above it:
/**
 * Clones rows
 **/
cloneWithRows(
       dataBlob: Array<any> | {[key: string]: any},
       rowIdentities: ?Array<string>
   ): ListViewDataSource {
...
}

With this change, the parser will first check if we have a closing parenthesis. If we do and don't have a matching open parenthesis we continue moving up the lines until we find it. Then we set previous line to be the line before that, the true beginning of the function declaration.

Forgot to make a branch and ended up adding in some extra docs to this PR too...however they're getting rendered depends on the original commit (03a562f). Just an FYI about the second commit.

Also, I did complete the CLA.

Looks good to me!

Thanks, this landed a few days ago!

Thanks, it is now in the repo!


singularity: Ensure DeployID < 50 chars.

Previously the tests passed because of an off by one error due to
Singularity spec being strictly less than 50, i.e. max = 49.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

  Generated by :no_entry_sign: Danger

@nyarly @alrs I'm merging this now to get sous re-deployed asap.

Codecov Report

Merging #396 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #396      +/-   ##
==========================================
+ Coverage   65.68%   65.71%   +0.02%
==========================================
  Files         144      144
  Lines        8157     8157
==========================================
+ Hits         5358     5360       +2
  Misses       2344     2344
+ Partials      455      453       -2

Impacted Files
Coverage Δ

ext/singularity/deployer.go
69.71% <100%> (ø)
:arrow_up:

lib/auto_resolver.go
88.05% <0%> (-1.5%)
:arrow_down:

ext/docker/image_mapping.go
75.49% <0%> (+0.87%)
:arrow_up:

Continue to review full report at Codecov.

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


Validity of contact data throughout the update loop

I'm using the Unity plugin of MuJoCo (3.1.1) on Windows. I noticed that the contents of data->contact is different depending on when in the update loop of a given frame I get the value. Getting it between mj_step1 and mj_step2 (during the control stage) results in erratic noise added to the force signals within the contact structs. Getting it after step2 has no such issues.
As step1 performs kinematic calculations, I would not have expected contact data to be altered.

In this figure, "Ctrl" stands for logging the contact force value after step1, and "Post" refers to logging it based on the previous turn's step2 . Magnitude of sum of vectors returned by mj_contactForce is plotted (for all contacts with the ground during a locomotion scenario).
Is this behaviour expected? If yes, are there other non-kinematic elements of data that will not be the same as the previous frame's step2 left them?
Let me know in case its expected to be an issue with the Unity plugin, in which case I can start investigating it closer.

Answering my question based on explanation from @erez-tom:
The problem was simply due to querying the contact indices after step1 as well. At that point there will be contacts that have never seen a step2 before (i.e. ones that just occurred at that step1). These will have unreliable data, so even though there may be some contacts that will be the same when queried at the previous step2 and the current step1, this won't work for all contacts.
The contact data should be processed/stored after the previous step2 and used for calculations if needed after step1. Alternatively we could always store mjData, run step2 get the contact information, then restore mjData.


Use operator   @beginWith  error

When  I send a request_uri is "/index.php?act=seller_center&op=statistics&rand=24954191" and my rule is "SecRule REQUEST_URI "@beginswith /index.php?act=store"
"id:1004,phase:1,pass,nolog,
ctl:ruleRemoveById=949110" but rule id 1004  that his uri is not match the "/index.php?act=seller_center&op=statistics&rand=24954191"，and I found the request I send has match the rule that his id is 1004  why？ The operator beginwith is not a exact match？

The rule is looking for act=store while the generate url is act=seller_center so why you think it would match?

@void-in  you can  see https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/806


Add Support for Laravel 11.x

Update dependencies to support Laravel 11.x
Remove PHPUnit because i think its not needed anymore since Pest ist used for the tests.

Thanks!


Do not fail but warn when Optional and Default are used redundantly

Motivation:
Armeria currently raises an exception when a user creates an annotated
service with redundant use of Optional and Default:
// No need to use Optional because 'value' is always present.
@Get("/foo/:value")
public String foo(@Param Optional<String> value) {}

// No need to use @Default because 'value' is always present.
@Get("/bar/:value")
public String bar(@Param @Default("defVal") String value) {}

// Optional and @Default were used together. 'value' will always be present.
@Get("/baz")
public String baz(@Param @Default("defVal") Optional<String> value) {}

We could relax a little bit and just warn so that the server starts up
anyway because it wouldn't harm and it would give a user less surprise.
Modifications:

Log a warning message instead of raising an exception when a redundant
usage of @Default and Optional was detected.
Clean up the warning message a little bit so it is easier to
understand.

Result:

Better UX

Example warning messages:
10:43:38.030 [main] WARN  c.l.a.server.AnnotatedValueResolver - Optional is redundant for path variable 'var1' because the value is always present.
10:43:38.031 [main] WARN  c.l.a.server.AnnotatedValueResolver - @Default is redundant for path variable 'var1' because the value is always present.
10:43:38.032 [main] WARN  c.l.a.server.AnnotatedValueResolver - @Default was used with 'java.util.Optional<java.lang.String> value'. Optional is redundant because the value is always present.

Thanks for reviewing!


Develop

@dylanpoe Develop branch is not valued, so I can not catch what do you want to do. sorry.

I think dylanpoe had submitted to the wrong repo. Seems he wants to submit to containerOPS.

@dylanpoe Since I do not know why you want to merge a non-valuable branch into master, I am going to close it, If you have some idea, please create a issuse first.


Monkey patch elasticsearch-env file so it parses on busybox.

While elasticsearch docs do mention a requirement on bash, so far we haven't had issues running on busybox. https://github.com/elastic/elasticsearch/pull/49612 unfortunately broke compatibility at the syntax level.
This might give motivation to install bash into our image if it continues, let's try once to hack around it and see how far it gets us. At the same time, I see some movement to support busybox in https://github.com/elastic/elasticsearch/pull/52519 so it could work out fine in the end.
Fixes #3042

I'm tempted to simplify this as all the detection is moot since we are in a fixed image we control..

oops spoke too soon.. the error about thai segmentation pops up late.

[2020-03-25T06:29:14,994][ERROR][o.e.x.c.t.IndexTemplateRegistry] [zipkin-elasticsearch] error adding index template [ilm-history] from [/ilm-history.json] for [index_lifecycle]
java.lang.UnsupportedOperationException: This JRE does not have support for Thai segmentation
	at org.apache.lucene.analysis.th.ThaiTokenizer.<init>(ThaiTokenizer.java:70) ~[lucene-analyzers-common-8.4.0.jar:8.4.0 bc02ab906445fcf4e297f4ef00ab4a54fdd72ca2 - jpountz - 2019-12-19 20:16:38]
	at org.apache.lucene.analysis.th.ThaiTokenizer.<init>(ThaiTokenizer.java:63) ~[lucene-analyzers-common-8.4.0.jar:8.4.0 bc02ab906445fcf4e297f4ef00ab4a54fdd72ca2 - jpountz - 2019-12-19 20:16:38]


Bdd test

Added bdd.yml

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


No License inside Jar file

Hi team,
We are planning to use dropwizard-guice for an application but our build has a Nexus IQ scan that checks for License inside the jar and it fails complaining about it. But I do see on Maven central that the  dropwizard-guice carries Apache license. So is there any plan to move license text inside jar files?

If there was something like this in the pom would Nexus IQ pick that up?

Cant say until it is scanned. So shall I change it in my fork or dw-guice team will do it in next release?

Can you try that on your fork and if it fixes the issue I'll cut a release with that change

Unfortunately I am not allowed to fork any public repo in my work machine, neither I can send that jar from another machine. That is because nexus IQ scan is hosted in work network and I would need this modified artifact on my work machine. For now we will not use dw-guice, so closing this issue.


AWS Regions with more than ~100 RDS instances do not return all the metrics

Hi,
I'm testing this exporter and works fine but, for regions with a lot of RDS instances (more than ~100), the exporter fo not return metrics to all of the instances.
I concluded that this can happen for one of two reasons:

Exporter code needs to be tuned to wait that all the info returned by the API request  is stored on the var(maybe need a sleep time or something similar)
Rate limit by AWS on API requests.  I can’t find on AWS SDK RDS the docs what is the limit for these requests. Using the AWS CLI I can get the data for all the RDS.

@ArturSantosTDX
I've released v0.5.4 includes your contribution. Thanks!
https://github.com/chaspy/aws-rds-engine-version-prometheus-exporter/releases


Manage poll results

As a developer i want to have an ability to manage (get) polls results
Description
Add ability to:

get poll result of current poll (Ability to get poll result is aviable only if poll status is completed)

Implement:

all necessary entities for getting poll result (poll result, question result, etc)
changes for existing entities connected poll results (poll, etc)
liquibase scripts to update database with tables and data required for new entities
all necessary repositories to manage poll results
all necessary services to manage poll results
controllers (api implementation)  to manage poll results using existing API interfaces
all necessary tests to check new functionality

Follow the design
Epic #162
ZenHub Epic
Acceptance Criteria
Ability to manage (get) polls results

Already closed


Not able to access my postgres data after running project

I've created .env file
TIPG_NAME="OGC Features and Tiles API - Krishna"
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/postgres

I'm not able to see my layers in collection
and when I click on collection, I'm getting following error

@krishnaglodha can you enable debug
TIPG_DEBUG=TRUE
and show the content of /rawcatalog
also the content of /collections/public.countries/queryables

Hi , response of /rawcatalog is added as attachment
rawcatalog.json.zip
and response for /collections/public.countries/queryables is as follows

[geom](https://geojson.org/schema/MultiPolygon.json)
ABBREV: string
ABBREV_LEN: number
ADM0_A3: string
ADM0_A3_AR: string
ADM0_A3_BD: string
ADM0_A3_BR: string
ADM0_A3_CN: string
ADM0_A3_DE: string
ADM0_A3_EG: string
ADM0_A3_ES: string
ADM0_A3_FR: string
ADM0_A3_GB: string
ADM0_A3_GR: string
ADM0_A3_ID: string
ADM0_A3_IL: string
ADM0_A3_IN: string
ADM0_A3_IT: string
ADM0_A3_JP: string
ADM0_A3_KO: string
ADM0_A3_MA: string
ADM0_A3_NL: string
ADM0_A3_NP: string
ADM0_A3_PK: string
ADM0_A3_PL: string
ADM0_A3_PS: string
ADM0_A3_PT: string
ADM0_A3_RU: string
ADM0_A3_SA: string
ADM0_A3_SE: string
ADM0_A3_TR: string
ADM0_A3_TW: string
ADM0_A3_UA: string
ADM0_A3_UN: number
ADM0_A3_US: string
ADM0_A3_VN: string
ADM0_A3_WB: number
ADM0_DIF: number
ADM0_DIFF: string
ADM0_ISO: string
ADM0_TLC: string
ADMIN: string
BRK_A3: string
BRK_DIFF: number
BRK_GROUP: string
BRK_NAME: string
CONTINENT: string
ECONOMY: string
FCLASS_AR: string
FCLASS_BD: string
FCLASS_BR: string
FCLASS_CN: string
FCLASS_DE: string
FCLASS_EG: string
FCLASS_ES: string
FCLASS_FR: string
FCLASS_GB: string
FCLASS_GR: string
FCLASS_ID: string
FCLASS_IL: string
FCLASS_IN: string
FCLASS_ISO: string
FCLASS_IT: string
FCLASS_JP: string
FCLASS_KO: string
FCLASS_MA: string
FCLASS_NL: string
FCLASS_NP: string
FCLASS_PK: string
FCLASS_PL: string
FCLASS_PS: string
FCLASS_PT: string
FCLASS_RU: string
FCLASS_SA: string
FCLASS_SE: string
FCLASS_TLC: string
FCLASS_TR: string
FCLASS_TW: string
FCLASS_UA: string
FCLASS_US: string
FCLASS_VN: string
FIPS_10: string
FORMAL_EN: string
FORMAL_FR: string
GDP_MD: number
GDP_YEAR: number
GEOUNIT: string
GEOU_DIF: number
GU_A3: string
HOMEPART: number
INCOME_GRP: string
ISO_A2: string
ISO_A2_EH: string
ISO_A3: string
ISO_A3_EH: string
ISO_N3: string
ISO_N3_EH: string
LABELRANK: number
LABEL_X: number
LABEL_Y: number
LEVEL: number
LONG_LEN: number
MAPCOLOR13: number
MAPCOLOR7: number
MAPCOLOR8: number
MAPCOLOR9: number
MAX_LABEL: number
MIN_LABEL: number
MIN_ZOOM: number
NAME: string
NAME_ALT: string
NAME_AR: string
NAME_BN: string
NAME_CIAWF: string
NAME_DE: string
NAME_EL: string
NAME_EN: string
NAME_ES: string
NAME_FA: string
NAME_FR: string
NAME_HE: string
NAME_HI: string
NAME_HU: string
NAME_ID: string
NAME_IT: string
NAME_JA: string
NAME_KO: string
NAME_LEN: number
NAME_LONG: string
NAME_NL: string
NAME_PL: string
NAME_PT: string
NAME_RU: string
NAME_SORT: string
NAME_SV: string
NAME_TR: string
NAME_UK: string
NAME_UR: string
NAME_VI: string
NAME_ZH: string
NAME_ZHT: string
NE_ID: number
NOTE_ADM0: string
NOTE_BRK: string
POP_EST: number
POP_RANK: number
POP_YEAR: number
POSTAL: string
REGION_UN: string
REGION_WB: string
SOVEREIGNT: string
SOV_A3: string
SUBREGION: string
SUBUNIT: string
SU_A3: string
SU_DIF: number
TINY: number
TLC: string
TLC_DIFF: string
TYPE: string
UN_A3: string
WB_A2: string
WB_A3: string
WIKIDATAID: string
WOE_ID: number
WOE_ID_EH: number
WOE_NOTE: string
featurecla: string
fid: number
scalerank: number

Interesting, it might be a lower/upper case issue 👀

Yup,
But I’m more interesting in knowing how can I connect my PG to it
Thank you,
Krishna G. Lodha
Personal email : @.***
Office email : @.***
On 19 Jun 2023 at 11:52 AM +0530, Vincent Sarago @.***>, wrote:

Interesting, it might be a lower/upper case issue 👀
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

But I’m more interesting in knowing how can I connect my PG to it

sure, I'll try to see if I can find if there is a bug somewhere ;-)

Thanks :)
Once sorted, I can start contributing to few leaflet.js related issues :D
Thank you,
Krishna G. Lodha
Personal email : @.***
Office email : @.***
On 19 Jun 2023 at 11:54 AM +0530, Vincent Sarago @.***>, wrote:

But I’m more interesting in knowing how can I connect my PG to it
sure, I'll try to see if I can find if there is a bug somewhere ;-)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@krishnaglodha https://stackoverflow.com/questions/20878932/are-postgresql-column-names-case-sensitive is interesting
Looking at https://github.com/developmentseed/tipg/blob/main/data/countries.sql, the columns are set to be in lower case, so I'm not sure why yours are in uppercase type 🤷
do you get the same error for public.landsat_wrs ?
also what is your system info?

Hi @vincentsarago , I'm not able to fetch public.landsat_wrs

Also as of now I'm not able to connect to database, thus not sure how case sensitivity is handled.
System  : Macbook pro M1 max

@krishnaglodha it's pretty hard for me to debug 🤷
I assumed you were using docker but looking at the postgres url you shared in https://github.com/developmentseed/tipg/issues/80#issue-1760440764 it seems you're trying to connect to your local postgres.
Looking at your rawcatalog, you don't have public.landsat_wrs (because it's one table that we load into the postgres we set when using docker-compose 😅 ) but you have public.raster_columns, you should be able to access it.
As for the countries table, I'm not sure how you ingested it into your postgres database but there is def something wrong with the column (maybe @bitner has an idea)

I think the countries table it is referring to is from local storage not PG

@krishnaglodha I have no idea what's going on I'm sorry
can you try with other tool like pg_tileserv or pg_featureserv to see if they work

yeah pg_tileserv works fine

Can you confirm If I'm taking correct steps https://we.tl/t-wruLsjZ8p0

thanks for the video,
everything looks good.
can you tell which version of postgres you are using?

I'm on postgreSQL 14

Issue is with M1 I guess , it works fine in Intel ?


Page refresh doesn't work on IE

I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?
Bug Report

What is the current behavior?
refreshing a page on IE gives (Cannot GET /route.)
accessing the  index.html page works fine
Examplem accessing the following links:
http://localhost:3000/index.html works on IE
http://localhost:3000/#/pages/dashboard doesn't work on IE, works on chrome

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

using IE, open http://localhost:3000/index.html or http://akveo.com/ng2-admin/index.html
refresh the page
you will get an error (Cannot get route ...)

What is the expected behavior?
page refresh successfully

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0 final release
Browser: [IE 10, 11, 12  ]

Please gentlemen, any solutions? workarounds for this issue?
Thanks in advance.

any help from anyone?
any pointers to solve this issue?
Thanks again.

hello after a long investigation, page refresh works fine in IE, the problem I was facing was with my server (Weblogic 12c),
the server wasn't configured to run HTML5 routing.
my apologies, please close this.


Failing to scrape Argentine inflation data

Describe the bug
Collecting 'ar, cpi' data currently failing
(That's Argentina, consumer price index inflation)
This used to work, so it's probably the source that has changed (e.g. moved URL).
We have no paying customers using Argentinian data, so not urgent.
To Reproduce
This is run as a series of cronjobs. See errors here:
https://github.com/FullFact/nso-stats-fetcher/actions
Expected behaviour
No errors.

I’ve just pushed a fix to improve the logging slightly, so we can see what’s going wrong. Here’s the error that’s reported:

requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://apis.datos.gob.ar/series/api/series/?collapse=month&collapse_aggregation=avg&ids=148.3_INIVELNAL_DICI_M_26&limit=5000&representation_mode=percent_change_a_year_ago&format=json

Works for me locally, so I guess apis.datos.gob.ar is blocking based on IP address, something like that. It might be enough to change the user-agent, I don’t know, but would probably require a bit of fiddling about.

Changed the user agent; didn't fix the problem (so removed it again).

Mm, kk.
We could proxy the requests, using proxy.fullfact.org… I suspect that would do the trick.


Support AppSync conflict detection

Requests

https://serverless-stack.slack.com/archives/C01HQQVC8TH/p1633616327303900

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


fatal error: color/color.hpp: No such file or directory

hi jpcima,
I'm trying to compile your object for pd-vanila on a Raspian stretch Patchbox O.S Real time, and i get the following error due to a missing library:
$ make
[ 19%] Built target visu_common
[ 28%] Built target sgvisu_tilde
[ 38%] Built target ogvisu_tilde
[ 47%] Built target Fl_Knob
[ 57%] Built target wfvisu_tilde
Scanning dependencies of target visu_gui
[ 61%] Building CXX object CMakeFiles/visu_gui.dir/src/gui/w_dft_spectrogram.cc.o
/home/patch/spectros/pd-visualization/src/gui/w_dft_spectrogram.cc:8:27: fatal error: color/color.hpp: No such file or directory
#include <color/color.hpp>
^
compilation terminated.
CMakeFiles/visu_gui.dir/build.make:86: recipe for target 'CMakeFiles/visu_gui.dir/src/gui/w_dft_spectrogram.cc.o' failed
make[2]: *** [CMakeFiles/visu_gui.dir/src/gui/w_dft_spectrogram.cc.o] Error 1
CMakeFiles/Makefile2:252: recipe for target 'CMakeFiles/visu_gui.dir/all' failed
make[1]: *** [CMakeFiles/visu_gui.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
any clue where I could find this color.hpp file?
thanks in advance

Hi @erreubequis  The color package is available as a submodule repository.
This command should be able to fix your build : git submodule update --init

Hi! The build was inmediatelly succesful with your command, worked straight forward.
The 3 objects are working very goood and the response are great under a RP3+ on a RT kernel.
I'm wondering if there is a way to visualice the objects into the patch and not on a separate window.
Merci.

No these visualizers are designed to operate as external windows, and it is a feature.
They can't be easily rewritten as patch UI elements.
It's the same case as GEM, running as a separate window.
As far as I'm aware, it's not possible to embed a native window into the canvas.
As oscilloscope and spectrum as concerned, you could certainly write some equivalent displays using Pd directly. IIRC, I think one is documented in the Pd docs.

Ok I understand.
I´m very much interested in the waterfall to work on some SDR project.
Right now I can work prety good with it, and start to adapt to the needs of the project.
The main issue I see with the windows its that they open on random places each time I open the patch for the first time in the session and many times overlapped. Some short of coordenades / window dimension to be understand by X11.
thanks for the fast answers!

Ok. dou you need special ability to set window geometry and position from the pd patch?

yes, this will be ideal so everytime the patch gets started remembers that positions.
For the last ideal setup,I wont be using the Windows Manager (xfce) as I´m starting the pd patch before the windows manager starts

On 26 Jul 2019, at 15:15, JP Cimalando<EMAIL_ADDRESS>wrote:
Ok. dou you need special ability to set window geometry and position from the pd patch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/jpcima/pd-visualization/issues/1?email_source=notifications&email_token=AD7YYV435RJ2W4VPOPGCWRDQBL2FPA5CNFSM4IGGFBN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD24RO7Q#issuecomment-515446654, or mute the thread https://github.com/notifications/unsubscribe-auth/AD7YYVYLBORNS3IGTOIQZIDQBL2FPANCNFSM4IGGFBNQ.

I've implemented an ability to do such setup.
It works as indicated on the picture:

when the window is ready to accepting configuration, the 1st output is banged (DSP must run)
in reaction, following messages can be sent:

position X Y, set window position
size X Y, set window size
border B, enable/disable the window frame (1:on 0:off)

This ensures the synchronization such that messages are sent in good timing. Otherwise, it can be ignored; for example, during the loadbang time, if messages go when it's not yet finished starting.

Hallo Jpcima, that seems perfekt.
Are you as the wfvisu does not have an output, are you planing to make the commit for this upgrade? thanks!

Apologies that I made a mistake here.
I had pushed only at the mirror due to configuration error.
Now, it must be synchronized. (at the head commit b303c45)
(the mirror is located at bitbucket: https://bitbucket.org/jpcima/pd-visualization/src/master/)

Hi! no worries, i was trying to guess the issue.
I got this problem after the pull
$ make
[ 62%] Built target visu_common
[ 62%] Built target sgvisu_tilde
[ 62%] Built target ogvisu_tilde
[ 62%] Built target Fl_Knob
[ 62%] Built target wfvisu_tilde
[ 62%] Built target tfvisu_tilde
[ 62%] Building CXX object CMakeFiles/visu_gui.dir/src/visu~-gui.cc.o
/home/patch/spectros/pd-visualization/src/visu~-gui.cc:13:20: fatal error: fftw3.h: No such file or directory
include <fftw3.h>
                ^

compilation terminated.
CMakeFiles/visu_gui.dir/build.make:62: recipe for target 'CMakeFiles/visu_gui.dir/src/visu~-gui.cc.o' failed
make[2]: *** [CMakeFiles/visu_gui.dir/src/visu~-gui.cc.o] Error 1
CMakeFiles/Makefile2:289: recipe for target 'CMakeFiles/visu_gui.dir/all' failed
make[1]: *** [CMakeFiles/visu_gui.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
getting close!

It's in package libfftw3-dev.
After some time, I've decided to drop the kft FFT in favor of FFTW, considering FFTW has become faster and KFR devs did not answer issues.

hi again jpcima,
i'm getting closer:
$ make
[ 62%] Built target visu_common
[ 62%] Built target sgvisu_tilde
[ 62%] Built target ogvisu_tilde
[ 62%] Built target Fl_Knob
[ 62%] Built target wfvisu_tilde
[ 62%] Built target tfvisu_tilde
make[2]: *** No rule to make target '/usr/lib/arm-linux-gnueabihf/libSM.so', needed by '../visu~-gui'.  Stop.
CMakeFiles/Makefile2:289: recipe for target 'CMakeFiles/visu_gui.dir/all' failed
make[1]: *** [CMakeFiles/visu_gui.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
Any clue about this? I'm checking on different forums but not get a solution.

This is libsm-dev. Most likely, it's pulled from FLK, I don't use this library directly.
You can determine this by debian's package search engine located at https://packages.debian.org/. (search in package content)

great thanks| i didnt search there
A few installs and makes before I reached to
$ make
[ 62%] Built target visu_common
[ 62%] Built target sgvisu_tilde
[ 62%] Built target ogvisu_tilde
[ 62%] Built target Fl_Knob
[ 62%] Built target wfvisu_tilde
[ 62%] Built target tfvisu_tilde
[ 62%] Linking CXX executable "../visu~-gui"
[ 62%] Built target visu_gui
Scanning dependencies of target visu_jack
[ 62%] Building CXX object CMakeFiles/visu_jack.dir/src/jack-main.cc.o
/home/patch/spectros/pd-visualization/src/jack-main.cc:5:23: fatal error: jack/jack.h: No such file or directory
#include <jack/jack.h>
^
compilation terminated.
CMakeFiles/visu_jack.dir/build.make:62: recipe for target 'CMakeFiles/visu_jack.dir/src/jack-main.cc.o' failed
make[2]: *** [CMakeFiles/visu_jack.dir/src/jack-main.cc.o] Error 1
CMakeFiles/Makefile2:326: recipe for target 'CMakeFiles/visu_jack.dir/all' failed
make[1]: *** [CMakeFiles/visu_jack.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

libjack-dev or libjack-jackd2-dev, depends which version is used

Yes!
Make succesfully done and now windows respond to coodenades and can be set perfect.
As you read from my novice writing and doubts this is prety new to me, but thanks to your help and support now its working!
I would like to dig into the color schemes, lets see if i dont break it.
Muchas gracias Jpcima!


Delete smoe instances

Destroy my instances since they are no longer in use

Can one of the admins verify this patch?


Missing API doc links

It seems not to be linked existed API docs like findAll on SUMMARY.md.
Is it intentionally?
If not  so, I'll create a pull request😃

It's not intentional, so a pull request would be great! 🙂


errCode->-1001msg

Your questions.

Environment.

Mobile model: 模拟器
Mobile system:Android
Dev platform: darwin/windows/linux
Node: 8.x.x
Npm: 5.x.x

What do you think may be caused by the analysis of the problem.

Reappearance of the problem (It's best to have a screenshot).


See if we can improve installation flow for editable vs non-editable mode.

improve dependencies installation flow.
atm, the internal dependencies are installed using the [external] tag during pip install, to avoid overwriting editable installs with non-editable installs.
It would be better to fix this in code with the setup.py file. We detect if the setup.py was called in editable mode, we simply remove the local dependencies (these should have been installed manually in that case).
This would make this transparent for the user, which is beneficial imo.
Even better would be to auto-install the dependencies in editable mode as well, but I haven't managed to get that working in the past.
cf. https://github.com/open-mmlab/mmsegmentation/blob/main/setup.py

using this we should be able to catch if install is in editable mode or not. If in editable mode, don't install airo-mono dependencies because we want to have those editable as well and they would be overwritten by a non-editable install afaik. If not, we add the other dependencies (not sure how this would work for pypi releases though, because it installs the packages using local source code).

To summarize:
Proposed developer installation
we want the installation for developers (in an existing conda env) to look like this:
git clone git@github.com:airo-ugent/airo-mono.git
cd airo-mono
pip install -e airo-camera-toolkit -e airo-dataset-tools -e airo-robots -e airo-spatial-albegra -e airo-teleop -e airo-typing

Ideal user installation
For users, the ideal installation would be with pypi, e.g:
pip install airo-camera-toolkit airo-dataset-tools airo-robots airo-spatial-albegra airo-teleop airo-typing

Propsed user installation
But for now we don't have releases, so it would be e.g.:
pip install 'airo-robots @ git+https://github.com/airo-ugent/airo-mono@main#subdirectory=airo-robots'
pip install 'airo-camera-toolkit @ git+https://github.com/airo-ugent/airo-mono@main#subdirectory=airo-camera-toolkit'
...

Where the [external] is not needed anyone, because if we detect the install is non-editable, we add the dependencies to install_requires like so:
 f"airo_typing @ file://localhost/{root_folder}/airo-typing",

yes but to create releases, I think we also need to avoid these
  f"airo_typing @ file://localhost/{root_folder}/airo-typing",
because I think that will fail if you donwload a wheel from pypi

I was wondering whether creating pypi releases might solve the problem with editable installs as well? Say we run
pip install -e airo-spatial-albegra
pip install -e airo-robots

With this in the airo-robots setup.py:
install_requires=[..., "airo-spatial-algebra >= 0.2.0"]

Then I believe pip might detect that this is satisfied and might not uninstall the already existing editable version?
If this is the case, shouldn't we just pursue releases on pypi instead of customizing our setup.py (further)?

hm I'm not sure, I had the feeling that pip overruled an editable install, but we would have to test. Maybe we should try it out on a separate branch? we could modify the setup.py of a few packages, create wheels, publish them on pypi and see how it goes

Spent some time thinking/trying around. Below is a summary
current situation
What we now have are three ways to install packages from the mono repo:

editable, local install through pip  install -e for each script
non-editable, local install through the use of direct links in the setup.py files
non-editable, remote install by using pip's ability to install the setup.py files from git repos (bundled in this script )

The non-editable installs currently use an addional extra_requires arg in the setup.py since pip overwrites editable installs when installing from a direct link, which is confusing.
Furthermore, the use of direct links (the file @  specifiers used in the setup.py for the internal dependencies), creates some issues when updating(was encountered during the IRM course), see here.
Actually I have slightly abused these direct links with file paths to be able to specify internal dependencies without building releases for the packages. Next to the aforementioned issue with the stale wheels, this will also break wheels that are built in regular fashion using setuptools. So I think we need to abandon them in favor of a proper way to deal with our local dependencies.
proposed solution

setup.py now lists both internal and external dependencies, as usual.

for local, editable installs, you install them in the proper order or in a single line using pip install -e.
For non-editable installs, you use wheels. These wheels can be released on PyPI or in another place(such as locally on your desktop), in which case you use pip install --find-link (see here).
We provide a script and/or CI workflow to  build all wheels (which can then be uploaded to github/PyPI)
@Victorlouisdg  what do you think? (note I skip version management in this analysis, though both are slightly related as they are typically handled by the same tools)
Alternatives could be:

use manager that is more powerful, such as poetry and can handle internal path dependencies vs external wheel dependencies.
use dynamic setup.py code to detect if we are in editable mode, and to filter out the internal dependencies if that is the case. This would still not allow to release packages though.

The proposed solutions sounds great, less customization and basically no regression in ease of use (expect for the non-editable local installations, which should be rarely needed).

We provide a script and/or CI workflow to build all wheels

Ideally this be should be something close to python -m build.
To install all packages in editable mode, I guess the command would be this?
pip install -e airo-typing -e airo-spatial-algebra -e airo-dataset-tools -e airo-robots -e airo-teleop -e airo-camera-toolkit

We provide a script and/or CI workflow to build all wheels

Ideally this be should be something close to python -m build.

Indeed, and then do this for each package.

To install all packages in editable mode, I guess the command would be this?
pip install -e airo-typing -e airo-spatial-algebra -e airo-dataset-tools -e airo-robots -e airo-teleop -e airo-camera-toolkit

Indeed, though I think you only need to pass the -e flag once.
Directly installling from github will then be no longer supported and we will have to modify the current install script. Only thing to keep in mind is that the direct install allowed to install from any commit ID, whereas this will now only work with a git clone and editable install (though this is what happens behind the scenes anyways)

also need to change the testing workflows, now each package is installed isolated, but this will no longer work unless wheels are built each time. For now I think it's easier to simply install all packages first from local files and to only then run the tests. Alternative is to first build distributions for each package once and to then start running tests for each package and its dependencies.

The current pattern of installing with direct references is not allowed if you want to publish your package that depends on airo-mono on PyPi:

Public index servers SHOULD NOT allow the use of direct references in uploaded distributions. Direct references are intended as a tool for software integrators rather than publishers.
https://peps.python.org/pep-0440/#direct-references

This will be fixed once we publish the airo-mono packages on PyPi.


add doc build to ci pr checks

I would like to add this for all extension repos, what do you think? @cqc-alec

Had to add an additional file to handle the exit error code in the workflow.


Use GitReleaseManager for creating release notes

Rather than using the ReleaseNotes.xml file.  GRM can also be used for creating the release on GitHub and uploading the attachments.

can we postpone this to milestone 3.0.1 ? :smile:


Added serde support, clone and fixed several code smell

Hi,
With this pull request, I am solving these issues:

#24
#23
#16

and several other code smells.
Cheers,
Luca

I deleted the edits since it was a bit of a mess to rebase with the latest edits, I am remaking them now from scratch.


Bump GitHub runners

Why
Currently used macOS runner is deprecated:

https://github.com/signalfx/splunk-otel-go/actions/runs/3394998999/jobs/5644295223
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners

What
Bump the GH runners to the current "-latest".

Codecov Report
Base: 81.46% // Head: 81.08% // Decreases project coverage by -0.37% :warning:

Coverage data is based on head (3b19f17) compared to base (75fa713).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1575      +/-   ##
==========================================
- Coverage   81.46%   81.08%   -0.38%
==========================================
  Files          63       63
  Lines        2638     2638
==========================================
- Hits         2149     2139      -10
- Misses        441      449       +8
- Partials       48       50       +2

Flag
Coverage Δ

Linux
81.08% <ø> (ø)

Windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...n/github.com/lib/pq/splunkpq/internal/connector.go
51.75% <0.00%> (-5.03%)
:arrow_down:

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

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


Failed goose db migration does not cause RPM upgrade to fail

The migration in the following upgrade snippet failed and the RPM transaction proceeded and eventually succeeded. This means that Traffic Ops was successfully upgraded but without the migrations.
The failed migration can/should cause the RPM transaction to fail. In order to fail the transaction, I believe we need to capture the return code of the goose command that failed, pass that up to where the spec file is executing, check for non-zero, and exit if non-zero. This will need some testing, but it should theoretically cause the transaction to be rolled back.
...
Shutting down Traffic Ops

Restoring config files.

Migrating database...
goose: migrating db environment 'production', current version:<PHONE_NUMBER>3037, target:<PHONE_NUMBER>0333
2016/04/21 21:22:59 FAIL<PHONE_NUMBER>0000_unique_email.sql (Received #1062 error from MySQL server: "Duplicate entry<EMAIL_ADDRESS>for key 'tmuser_email_UNIQUE'"), quitting migration.
Seeding database...
Successfully migrated the database.

Upgrade complete.

Run /opt/traffic_ops/install/bin/postinstall from the root home directory to complete the update.

To start Traffic Ops:  service traffic_ops start

To stop Traffic Ops:   service traffic_ops stop

  Cleanup    : traffic_ops-1.4.3-2456.70beeb69.x86_64                                                                                2/2
duration: 80(ms)
Installed products updated.

Updated:
  traffic_ops.x86_64 0:1.5.0-3027.8d600a8e

Complete!

close, non repro, will be fixed with 2.0 install super process


Updated Supported platforms (README)

Hi folks,
thanks for bringing flutter to the raspberry pi! I use it for a hobby project.
It works even on the pi3 model B (requires to use swapfile due to limited memory).
Just wanted to let you know :)

To @taka-okayama


Tagged queries should not ignore their boosting factors

Solr-redis queries with tags used for highlighting ignore boosting factors. And the fact that you use highlighting on field matches or not should not affect the scoring.
For example: query ({!redis command="smembers" key="some:random:bucket"}fieldName)^0.3 score matching documents with [{"score": 1.2},{"score": 0.90000004},{"score": 0.90000004},{"score": 0.6}]. Everything seems to be fine here.
However, when using tag on same query ({!redis command="smembers" key="some:random:bucket" tag="tagName"}fieldName)^0.3 scores for the same documents become [{"score": 4},{"score": 3},{"score": 3},{"score": 2}]. And that is not something you expect to happen when using highlighting.

I have already linked redis and why I can't get any response doc.

@LiquckTeng It sounds like you are trying to report a different problem or ask for help?  If so, please open another issue and remove your comment here.


Question: Tokenizer used for RoBERTa model?

I'm trying to integrate Vokenization with BERTScore and I'd like to get clarification on which tokenizer is being used for the pretrained RoBERTa + VLM model. Is it roberta-base or bert-base-uncased?

Thanks. I am using bert-base-uncased for  BERT + VLM (on Wiki) here, and use roberta-base for RoBERTa + VLM (on Wiki).

Perfect, thanks for the quick reply!


[BUG] When i wanna play Roblox It's Freezing and then it says it Crashed. What can i do?

Acknowledgement of preliminary instructions

[ ] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
I use bloxstrap with Framerate Limit and Old Textures.

Does this happen only with Bloxstrap? https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


Add support for date range

Would be great to support recognition of date ranges like '12th - 13th April 2019', 'April 12-13', ...

@igo I believe this is a duplicate of #262. Could you close this issue and vote up #262 instead? This comment of mine already links your issue to #262, so hopefully, when support is implemented, your suggested examples of date range strings will be taken into consideration.

I think this would be very useful.
What I would expect as output from search_dates would be like:
'12th - 13th April 2019' -> [('12th', datetime.datetime(2019, 4, 12, 0, 0)), ('13th April 2019', datetime.datetime(2018, 4, 13, 0, 0))]
'Aug - Sept 2018' -> [('Aug', datetime.datetime(2019, 8, 4, 0, 0)), ('Sept 2018', datetime.datetime(2018, 9, 4, 0, 0))]
I think that this is different than #262 . What is needed here is to change the RELATIVE_BASE of the first date ('12th') to be equal to the full date object found in the input string ('13th April 2019').


Configure Keycloak worker thread pool to be aligned with JGroup thread pool size

This prepares the setup for the next upcoming load test where we align the Keycloak workers.
@kami619 - please review the docs and test in a single cluster with 100_000 sessions, 200 ups sustained load 100 pod kills (like the previous run where we saw the spikes).
Thanks!

@ahus1 do you a run based off of the latest changes, if not I think the changes look good from the results we had from yday.

Do you think we need a run based off of the latest changes, if not I think the changes look good from the results we had from yday.

@kami619 - I think we're good to merge this one. We should just let everyone know that we now restrict the number of Keycloak worker threads. We might lift that later with the next Infinispan upgrade to 200.


change data type + default value of updatefreq to Numeric

Currently the module supports setting the alias attribute "updatefreq" to an empty string. However, this causes Puppet to alter the affected alias on every Puppet run:
Notice: /Stage[main]/Opnsense/Opnsense_firewall_alias[test_alias]/updatefreq: updatefreq changed 0.000000 to '' (corrective)

This happens because OPNsense expects only numeric values for "updatefreq":
https://github.com/opnsense/core/blob/6ca0e5b58f2049d09d9776fbce31cfd785dfeea9/src/opnsense/mvc/app/models/OPNsense/Firewall/Alias.xml#L70-L72
Empty strings are still accepted, but are internally converted to 0 by OPNsense.
So in order to solve this, this PR does two things:

change the accepted data type from "Float" to "Numeric" (to align it with OPNsense' data type)
change the default value from an empty string to 0 (the default value that is internally enforced by OPNsense)

This change is fully backwards-compatible, because it just sets the same value that is already enforced by OPNsense. However, an alias that was previously relying on the old default value (empty string) will see the following change on the next Puppet run:
Notice: /Stage[main]/Opnsense/Opnsense_firewall_alias[test_alias]/updatefreq: updatefreq changed '' to 0

All following Puppet runs will be completely silent. :)
(Side note: This behaviour seems to be newish, it probably started in OPNsense 22.7 and I'd assume that it is related to the phalcon/PHP upgrades. In older versions of OPNsense an emptry string for "updatefreq" was actually written to config.xml and not replaced with a 0.)

The initial acceptance test failure is unrelated to this PR:
Failure/Error: vmhostname = LitmusHelper.instance.run_shell('hostname').stdout.strip
[...]
"stderr"=>"bash: hostname: command not found\n"

https://github.com/andeman/puppet-opnsense/actions/runs/3837663303/jobs/6533223983
This seems to be related to the (dead) CentOS 8 test container. I've modified the acceptance test to use the (maintained) Rocky 8 container instead (which includes the hostname command). Rocky aims to be binary-compatible with RHEL 8, so this should not make any difference.
@andeman Feel free to review/merge :)


Simple layer

rips out RRMNL for something much smaller. I should maybe keep the socket stuff split out to avoid including socketio unnecessarily

rips out RRMNL for something much smaller.

what's the cost/benefit of having this logic in here vs using an upstream package, if they are functionally equivalent?

The upstream package includes a lot more code/logic over what is essentially a fetch helper in an attempt to cover every possible use case. I think there is space for a something like this that is way more minimal, but covers the 80% case.
RRMNL also is badly packaged/published. We are pinned to an old version b/c the author is using the babel runtime transform, but not including babel runtime or corejs as dependencies because "it bloats the bundle". i.e. is broken by default but it's being called working as intended so IDK

also this is now better tested than the upstream one :P

I think the API for a general package we could stick in relay-tools should probably be:
import { NetworkLayer } from 'relay-runtime'
import { createFetch, createSubscribe } from 'relay-network-layer'

NetworkLayer.create(
  createFetch(opts),
  createSubscribe(otherOpts)
)

thanks :) and having this as a separate network layer package? does it make sense?

I was thinking of renaming this to 'relay-network-layer' and having the useAuthToken bit just be a side feature. WDT?

might make more sense. I don't have big vesting on this so my suggestions are totally non binding :) I'll let you guys decide!

did you not like my relay-fetch as a library name? https://github.com/4Catalyzer/relay-fetch

It's also good :P i already had the work here. we can put it where ever. I mostly like that relay-network-layer is available on npm and feels more canonical than RMNL, in a petty sort of way.

okay, relay-network-layer does in fact sound better

gtg?

I feel like this might be simpler without observables.

I was thinking the observables were required but I guess if we are always using the builtin Network.create it'll coerce the Promise to an observable. The real reason for the observable is the abort logic tho.

idk how Relay converts it, the result from an abort is you complete the observable without having sent a value, with a Promise, that's a bit ambiguous

okay, that makes sense. that's definitely worth adding a comment to note

notes addressed!


Fix config.json interpretation

As outlined in https://github.com/kubernetes/kubernetes/issues/119941, the implementation is more specific than a regular glob match. Updating the docs to reflect that.
Fixes https://github.com/kubernetes/kubernetes/issues/119941
PTAL @njgibbon

/retitle Fix config.json interpretation
(avoiding Markdown in commit messages)

Rebased, PTAL @kubernetes/sig-docs-pr-reviews

Em... this is a dilemma. Sounds to me that the code is being fixed because it is not working as documented. At the same time, we are fixing the docs to be more accurate wrt to code implementation.
Even if the docs should be updated, we need to confirm whether it is something "new" in v1.29 and retarget this to dev-1.29 branch if answer is positive.

Okay, doubled checked the issue at k/k. This is something to be clarified at docs side.
/lgtm
/approve
Sorry for mistaking this as a code issue.


Allow env vars

This PR changes the behavior of the action by allowing access key ID, secret access key, and region to be read from environmental variables. The goal is to be able to use this action through OIDC to login instead of hardcoded values.
I'm not entirely sold on making key id and access key not required, I can see how keeping them required but passing empty values could work.

Any chance we can discuss this PR? Being able to use OIDC represents a significant improvement in the security posture.

Looks good. But this repository's CI is a failure now.
I will fix it in #14. Please wait for it.

I'm done. Please rebase again.

any updates? would love to start using this action

Thank you!


Swarming task panics and cancels build

Type of Request
bug
Infrastructure Environment
LUCI
What is happening?
Occasionally, the swarming task panics with an out of range error
panic: runtime error: slice bounds out of range [33554436:16406]

I've only seen this on https://chromium-swarm.appspot.com/bot?id=flutter-devicelab-mac-26.
See Raw Output of these tasks:
https://chromium-swarm.appspot.com/task?id=6779820e086f0e10
https://chromium-swarm.appspot.com/task?id=677660c60af4dd10
https://chromium-swarm.appspot.com/task?id=67732f3234e9fd10
https://chromium-swarm.appspot.com/task?id=67731ed09eaa5110
Note: Rich Output does not show the step it actually stopped on or the error. It only says "Build infra failed"
Steps to reproduce
No response
Expected results
I expect builds to complete

Does this log give any insight to you @vashworth ? https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8757363686798032481/+/u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Trigger_dialog/l_debug
Considering this is a bot specific issue, do you notice anything suspicious on the testbed? @kentnguyen99

Does this log give any insight to you @vashworth ? https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8757363686798032481/+/u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Trigger_dialog/l_debug
Considering this is a bot specific issue, do you notice anything suspicious on the testbed? @kentnguyen99

@keyonghan I don't think the step you linked is related to why it panics.
If you look at the Raw Output for the swarming task, you can see that it actually got past that step - but they're not shown in the Rich Output.
[I2024-01-31T10:06:16.649444-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Trigger_dialog/l_debug"}
[I2024-01-31T10:06:16.649553-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Trigger_dialog/execution_details"}
[I2024-01-31T10:06:16.650153-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Trigger_dialog/stdout"}
[I2024-01-31T10:06:18.399367-08:00 2499 0 options.go:227] dropped 1 items over 19.683688564s
[I2024-01-31T10:06:18.651953-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Dismiss_dialog/l_debug"}
[I2024-01-31T10:06:18.652001-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Dismiss_dialog/execution_details"}
[I2024-01-31T10:06:18.652615-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Dismiss_dialog/stdout"}
[I2024-01-31T10:06:18.668674-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Query_TCC_db__2_/l_debug"}
[I2024-01-31T10:06:18.668825-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Query_TCC_db__2_/execution_details"}
[I2024-01-31T10:06:18.669569-08:00 2499 0 butler.go:395] adding stream                               {"stream":"u/Prepare_iOS_device/Dismiss_Xcode_automation_dialogs/Query_TCC_db__2_/stderr"}
...

Also, it does not always stop of the same step (if you see other examples I linked), so I don't think it's related to a specific step

Let me follow up with LUCI team to see if they have any insight.

I checked the system log on mac-26 and everything looks normal, nothing suspicious on machine.

@vashworth do you still see this issue only on mac-26? (Somehow I didn't get any useful info from the LUCI team yet).

Reached out to LUCI team for advice on this issue.

@vashworth LUCI team indicated that this issue is a mac kernl bug, per:  https://github.com/golang/go/issues/61060#issuecomment-1645615671

@vashworth LUCI team indicated that this issue is a mac kernl bug, per: golang/go#61060 (comment)

Is there anything actionable we can do? This isn't a big problem right now because this bot in question is a staging bot. However, if it were to happen on a prod bot or on multiple bots, it could be a big issue since it causes quite a few failures.


Odd -Wnonnull-compare warning when enabling expression decomposition

While compiling my project with -DASSERT_DECOMPOSE_BINARY_LOGICAL=ON with MinGW-w64 GCC 13 I got several occurrences of the following warning:
In file included from cpp-sort/include/cpp-sort/detail/config.h:72,
                 from [...]:
libassert-src/include/assert.hpp: In member function 'constexpr decltype(auto) libassert::detail::ops::land::operator()(A&&, B&&) const [with A = bool&; B = const char (&)[50]]':
libassert-src/include/assert.hpp:295:47: warning: 'nonnull' argument 'rhs' compared to NULL [-Wnonnull-compare]
  295 |          LIBASSERT_GEN_OP_BOILERPLATE(land,   &&);
      |                                               ^
libassert-src/include/assert.hpp:268:45: note: in definition of macro 'LIBASSERT_GEN_OP_BOILERPLATE'
  268 |                 return std::forward<A>(lhs) op std::forward<B>(rhs); \
      |

It appears in a lot of translation units that happen to include <assert.hpp> (unsure whether it comes from use or include alone), and ultimately it doesn't feel like it comes from my own code directly. The line in the config.h above is just #include <assert.hpp>. The warning points to the following part of the code:
#ifdef ASSERT_DECOMPOSE_BINARY_LOGICAL
 LIBASSERT_GEN_OP_BOILERPLATE(land,   &&);
 LIBASSERT_GEN_OP_BOILERPLATE(lor,    ||);
#endif

I haven't managed to produce an MRE yet and can't totally rule out the fact that it might still come from my own code.

I can reproduce! https://godbolt.org/z/KW51jhcqe
I tried a bunch of stuff without any luck, then I added an optimization flag and it reproduced 😅

I don't think this error should come from any libassert code alone. Do you have the lowercase assert alias turned on by chance?

No, I'm not interested in the lowercase macro, so I haven't enabled the option.

I think I found the culprit in the timsort implementation:
CPPSORT_ASSERT(len2 != 0 && "comparison function violates its general contract");

The number of characters matches the one mentioned in the error.

To give an idea of how I did things, the CPPSORT_ASSERT macro is basically implemented as:
#if defined(CPPSORT_USE_LIBASSERT)
#    define CPPSORT_ASSERT(...) ASSERT(__VA_ARGS__)
#else
#    define CPPSORT_ASSERT(...) assert((__VA_ARGS__))
#endif

I guess that I will have to turn that into something along the lines of:
#if defined(CPPSORT_USE_LIBASSERT)
#    define CPPSORT_ASSERT(condition, message, ...) ASSERT(condition, message, __VA_ARGS___)
#else
#    define CPPSORT_ASSERT(condition, message, ...) assert(condition && message)
#endif

I lose the nice property of being able to pass expressions along the lines of foo<A, B>(5) to the condition and have it just work, but I don't think there's a way to get the both of best world there.
Also fun fact, prepending a unary + to the string literal silences the warning:
int main() {
    bool b = true;
    ASSERT(b && +"foo");
}

I don't know whether anything should or could be done on the libassert side.

Thank you! Interesting issue. ASSERT(b && +"foo"); is a good trick.
I think it is possible to do stuff on the libassert side. I think an if constexpr could be used in libassert::detail::ops::land::operator() to suppress the non-null warning when B is a string literal. In principle it's better to pass the message separately but this is a common pattern so it may be reasonable to go a little extra distance to support it.

I see how it would be possible, though I'm unsure how valuable it is and how many subtle issues it can cause. That said it would fully make ASSERT a drop-in replacement for people like me who only intend to use libassert as an opt-in for additional diagnostics.
I guess the other solution would be to give a "recipe" in the documentation to do what I did above - I might be wrong, but I doubt I'm the only one who would try to use it as an opt-in replacement for assert like that 😛


Problem with the download button

I have tested the script in both Firefox and Chrome, but I have a small problem and that is that the download button "does not work"

First, are there any exceptions or error logs printed in the developer console? To view this I recommend disabling the script in your userscript manager and instead pasting it into the console while on the Plex web app. Any exceptions not from Plex itself, or log messages beginning with [USERJS Plex Downloader] would be helpful. Please redact any IP addresses or values for X-Plex-Token=XXXXXXX if you post these.
Second, visit https://app.plex.tv/desktop/#!/settings/manage-library-access and click on the account that is sharing this library with you, and check if it says "Downloads Allowed" under the "You have access to" section. If it does not, that may be the issue, but I would still like to add a feature where it tells you that is the reason why it is not working.

Yes, I have access to 3 Plex servers, mine and 3 others.
But it only lets me download on my server, not on the others. And I bought Plex Pass

I've already tried several ways, and it only lets me download things from my own server on the same network. But not from other Plex servers
Do you have telegram or something?

You can contact my telegram @taxicat.

Issue was determined to be a typo in a XPath when parsing Plex resources that could cause downloads to use the wrong URI.


Implement --schema-export

Can simply store the /meta as a file.

Schema export is actually not implemented.


Media Keys - Windows

Search a possibility to use media keys to iterate with player.
Have implementation, but doesn't work on windows..
😄

I discovered the problem. I had a key registered in a google!
Sorry..


If docker-compose.yml has more than 1 services is it possible to attach node debugger to the node service?

Hi, I found all the examples I can find all have one problem, the docker-compose.yml only has one service. In a real scenario, which docker-compose.yml has more than one services I don't know how to attach debugger the node service. I don't know how to set remoteRoot?  Or is it possible to attach node debugger to the node service?

If you have a node service and other supporting services like DB, redis etc, then it really doesn't matter. You are just concerned about the Node service and its port mapping and its volume mapping. remoteRoot will be the folder where the code is residing inside the container

I did have one node service and other supporting services. But I just can't attach the debugger to the node service. Can you show me how to do that?
My docker-compose.debug.yml looks like this
version: '3'
services:
  nginx:
    ...
  node:
    build: ./node
    links:
      - mongo:mongo
      - redis:redis
    ports:
      - 3000:3000
      - 9229:9229
    volumes:
      - ./node:/app
    command: node --inspect bin/www
  mongo:
     ...
  redis:
    ...

This is my folder looks like:
├── .vscode
│   ├── launch.json
├── docker-compose.debug.yml
├── docker-compose.yml
├── nginx
│   ├── Dockerfile
│   ├── README.md
│   └── nginx.conf
├── node
│   ├── Dockerfile
│   ├── README.md
│   ├── app
│   ├── app.js
│   ├── bin
│   ├── node_modules
│   ├── package.json
│   ├── public
│   ├── views
launch.json is this:

        "configurations": [
            {
                "name": "Docker: Attach to Node",
                "type": "node",
                "request": "attach",
                "port": 9229,
                "address": "localhost",
                "localRoot": "${workspaceRoot}",
                "remoteRoot": "app"
            }
        ]

When docker-compose -f docker-compose.debug.yml up I saw this
Debugger listening on ws://<IP_ADDRESS>:9229/ce75a092-f013-4981-86b6-a86ff3900514
But the debugger said "cannot connect to runtime process"

In your case the launch.json should be
     "localRoot": "${workspaceRoot}/node",
     "remoteRoot": "/app"

Also for command: node --inspect bin/www make sure you are giving the starting js file for your app

I tried that too, it didn't work. And I have verified the node server did start.

Hi sorry I found the reason!
In my node Dockerfile I used the latest node FROM node, while my vscode still use node 6 so I change node's Dockerfile to  FROM node:6-alpine. Then it worked!
Thanks a lot!

@qiulang , If you need to use the latest version then change the command to command: node --inspect=<IP_ADDRESS>:9229 index.js and it should work. I just tested the same on the latest node version

Yes indeed! But can you tell me why that works? What does inspect=<IP_ADDRESS>:9229 mean here ?

@qiulang This means that you are starting Node with the "Inspector protocol" instead of the older V8 Protocol, which Node 6.4+ now uses for debugging.

@tarunlalwani Hi sorry to bother again. I still can't make the preLaunchTask works as you taught me at stackoverflow. The vs-code still complained the same error as I hit before "Debugging with legacy protocol because Node.js version could not be determined (Error: connect ECONNREFUSED <IP_ADDRESS>:9229)". Of course, if I start docker in a separated terminal it works.
{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "args": [],
    "tasks": [
        {
            "taskName": "start_node_compose",
            "command": "/bin/bash",
            "args": [
                "-c",
                "docker-compose -f docker-compose.debug.yml up -d && sleep 10"
            ]
        }
    ]
}

Closing due in activity.


feat: add new @changesets/write package to separate writing changesets

This PR adds a new package @changesets/write which does the inverse of @changesets/parse.
It basically just extracts the writeChangesets function used in @changesets/cli so it can be re-used.

Hey! Thanks for this.
We initially didn't do this because writing a changeset is simple enough that reimplementing it isn't really a cost, and having it as a library implies it's doing something fancier than it is.
What's the reason for wanting this as a package as opposed to just using the code yourself?

PR otherwise looks fine, so happy to merge + release

We initially didn't do this because writing a changeset is simple enough that reimplementing it isn't really a cost, and having it as a library implies it's doing something fancier than it is.

Makes sense. I guess since we already have the @changesets/parse we've abstracted reading the changesets, why not abstract writing them too?

What's the reason for wanting this as a package as opposed to just using the code yourself?

We need a way to programmatically create a changeset (our use case is to integrate the renovate bot into our monorepo, and there needs to be a way to generate a changeset for the diff that the renovate bot creates).
It seemed odd that we had to duplicate the same logic that @changesets/cli itself was doing. Plus we wanted to have the nice things that it already does automatically, like human-id, integration with prettier, etc.

Looks like the changes were merged in but didn't close this PR.
I'll close it now.


Paladin Horses

Paladin´s horses are different from the mount panel and the actual spell to summon them.
Working on checking each mount name for the spell ID

Fixed on v1.2.1


Diff by ref

Adds the option to generate a diff by ref rather than cloning the contents. This substantially reduces the amount of work done when diffs are serialized and then discarded (for application on the other side of a network connection) rather than applied locally

Blocked on release of new version of nanoserde with the following https://github.com/not-fl3/nanoserde/pull/87

New version is out now, getting it ready for merge


LIFX Example integration

Feature Request

create a example integration for LIFX light bulbs using the NEEO SDK, using the https://github.com/NEEOInc/neeo-community-adapter

CoS

add LIFX implementation as illustration example

I added an LIFX example on neeo-sdk-examples Github. you can see the pull request here.

Thanks @GeertWille for the first working version. I think the following (minor) features might improve the adapter:

Discrete Power commands for a single lamp (Power on / Power off)

@GeertWille maybe you know more - there is currently no other option to control the LIFX lamp but communicate with the public REST (cloud) API? Like can we communicate directly with the LIFX lamp?

@neophob what do you mean exactly with the Discrete Power commands for a single lamp? There is a power toggle button right now for every bulb?
Yes it is possible to use the lan-api though I didn't find a good node implementation of it yet that's why I started with the Cloud API. I'll take a look or I can write a node implementation for the lan-api myself or if you find a good one let me know ;).

@GeertWille This one looks interesting. https://github.com/MariusRumpf/node-lifx

@nklerk Cool, I'll try to make time and make an example ;)

@GeertWille @nklerk sounds interesting. the local lan protocol might be easier to implement - we dont need an API key. and it looks like discovery is also supported.
@GeertWille: with "Discrete Power commands" I mean a power on/off button. for example you want to power on your lights when a sensor triggers - then the power toggle is not the best option if you want to ensure the lights are on

thanks @nklerk and @GeertWille, will be included with the next release!


Is this github the same for azureinstances.info ??

I like to modify some errors and add some products but I don't see the repo.
regards!

Nope - looks like that project started with the code from this one but changed it heavily. Not sure it is open source. If you do find it please drop a comment here for anyone else who might find this thread. :) Good luck!