Ntrada update

Ports for services:

Identity - 5004
Reports - 5005
Notifications - 5006
Students - 5007
Events - 5008
Comments - 5009
Reactions - 5010
Statistics - 5011
Friends - 5012
Posts - 5013
MediaFiles - 5014
Organizations - 5015
Mailing - 5016

In ntradaUpdate branch we have now a template for endpoints for almost all our microservices:

Downstream endpoints should be consistent with the diagram: https://app.diagrams.net/#G1BsP1sv_9fAmCtE4uVDHizcFcp7TqqvXc#{"pageId"%3A"9VrkRtQQe1OaMDu59Q1v"}
Upstream endpoints now are generally based on downstream endpoints, in the future it will be necessary to adjust them to the general documentation for all teams (that one incomplete and not frozen yet)
For some endpoints attributes "bind" and "claims" needs to be set in the suitable way, it was not taken into account by me, also please pay attention to the fact that "auth" is set as true in every place

update .net to 8.0

Ports for services:

Identity - 5004
Reports - 5005
Notifications - 5006
Students - 5007
Events - 5008
Comments - 5009
Reactions - 5010
Statistics - 5011
Friends - 5012
Posts - 5013
MediaFiles - 5014
Organizations - 5015
Mailing - 5016

At this moment of development this issue will become inactive.


Support for valve source engine bsp file format

more information can be found at https://developer.valvesoftware.com/wiki/Source_BSP_File_Format

This is far too niche for the Ghidra team to support.  It would make for a nice 3rd party Ghidra extension though.


Question: how stable is it to round-trip code?

I'm experimenting on using bytecode to add programmatic breakpoints in pydevd (https://github.com/fabioz/PyDev.Debugger/).
The use case is getting the existing bytecode, adding some code to activate the pydevd breakpoint and then save it back (I'm trying to migrate from the existing code which does that but fails on some corner cases).
i.e.: something as:

b = bytecode.Bytecode.from_code(code_to_modify)
# modify to add new instructions at breakpoints ... something as:
b.insert(i, Instr("LOAD_GLOBAL", '_pydev_stop_at_break'))
b.insert(i + 1, Instr("LOAD_CONST", stop_at_line))
b.insert(i + 2, Instr("CALL_FUNCTION", 1))
b.insert(i + 3, Instr("POP_TOP"))
new_code = b.to_code()

On my experiments it seems to be working well, but I was wondering if you know of any corner case where doing so would not be safe or if something else would need to be taken into account for such a round-trip to work.
p.s.: Sorry for using the tracker to ask a question, I wasn't sure what was the appropriate channel here.

This is a perfectly legitimate use case of bytecode and any issue your encounter doing this would be a bug.
@thautwarm if I remember correctly you use bytecode to modify constants and probably do a lot of round tripping as a consequence, can you comment on this too.

@MatthieuDartiailh Yes, I did a lot of this sort of stuffs..
I don't see any corner case that would break, if any it must be a bug and should be solved.
@fabioz For your use case, there might be something to be take care.

If you're using Python < 3.6, be cautious about  lineno of an Instr.
Python 3.6 begins to support negative line number delta, so in 3.5 or lower versions, when inserting new instructions, you should guarantee that the linenos are monotonically increasing along instructions.

Besides, I recommend you to generate new instructions via a generator, instead of performing multiple insertions(it is inefficient if you insert for multiple times).
def gen(instrs):
   yield from (instrs[i] for i in range(1, i)
   yield instrs[i]
   yield Instr("LOAD_GLOBAL", '_pydev_stop_at_break')
   yield Instr("LOAD_CONST", stop_at_line)
   yield Instr("CALL_FUNCTION", 1)
   yield Instr("POP_TOP")
   yield from (instrs[i] for i in range(i, len(instrs))

A global name _pydev_stop_at_break might be rare enough and users will not write down such a name, but still, it is not well encapsulated or hidden well from users.
If the bytecode modified by debugger will not be dumped into .pyc file, you might consider insert a constant function instead of loading it from globals(loading from globals also requires you to initialize the variable in each module).
 Instr("LOAD_GLOBAL", '_pydev_stop_at_break')

->
  def pydev_stop_at_break(...):
     ...
  Instr("LOAD_CONST", pydev_stop_at_break)

I used to have this demand so I asked for this feature, thanks to @MatthieuDartiailh for kindly reviewing and accepting this.

Thank you for the feedback.
@thautwarm I'm actually using that only with Python 3.5 onwards and I'm converting the list to a double linked list (so that multiple insertions are efficient and to have a nicer API as iterating/changing items at the same time is a bit more straightforward), so, 1 and 2 are already ok, and thanks for the tip on the LOAD_CONST, I'll take a look into using that.


feat: add support for optional context

This allows specifying custom, comma-separated context variables on command-line.
Example usage:
cargo run -- install.md /etc/os-release sgx,git

context variables are delimited by ; in markdown preceding the OS-release filter variables
cc @platten

@rvolosatovs awesome, thanks for your help with this!

@rvolosatovs This seems useful. However, I'm wondering if we could just reduce all the /etc/os-release stuff to just these variables. For example cargo run -- install.md $(cat /etc/os-release) ... Also, should optional context enforce the key/value pair semantics?

We went through a few iterations of this and we discovered that we need 2 distinct groups here. Within the groups we need an OR relationship, but we need an AND across if either is specified.
Just using variables was my initial proposal as well, but consider the case of Debian-like OS with kvm or sev:

ID=debian
ID_LIKE=debian
CONTEXT=kvm,sev (where , is an OR)

The filter is actually  (CONTEXT=kvm || CONTEXT=sev) && (ID=debian || ID_LIKE=debian)
In order to avoid the rabbit hole of adding logical operator support here, went with simple solution of having 2 distinct groups of filters

Or for an even simpler example. We have install instructions in the document for installing from git OR from crates.io. We need to be able to account for both of these use cases as separate tests.
If this gets approved, I would like to patch to filter out cut of the shell prompt, with surrounding whitespace, dangling whitespace at the end of the string, and blank lines.


Add Start/End time on QAA submission page

We need to add two new inputs in this section -

The fields on the payload to the API should be startTime and endTime
The format should look like 12:00:00

Here is PR
https://github.com/savantly-net/franchise-manager/pull/109


Isolate the ensemble part and expose it to users

Right now the ensemble part is not isolated from hyperparameter search. Sometimes the ensemble part fails due to OOM. Users would like to use a more powerful machine to finish the ensemble part using a pickled automl object. #801
Suggestion: put the ensemble part in a separate function and expose it to users.

Can you provide some hints on where you would start? I am evaluating if I'm able to contribute on this

Can you provide some hints on where you would start? I am evaluating if I'm able to contribute on this

The ensemble part is located in https://github.com/microsoft/FLAML/blob/63d350d4c8cae5f5bdd686a97e737013fbd9641d/flaml/automl/automl.py#L3625-L3746


[#2523] Add reference enricher for conditions

Introduces the @Reference enricher with support for conditions. Future reference types will come in subsequent PRs, but I've outlined them over on the issue #2523

A thought, with core "link-to-thing" syntax we have `@{link type}[{linked ID}]{Custom Label}. I would suggest following that here which would suggest the condition identifier being in square brackets instead of curly braces and instead using curly braces for custom label text.
@Reference[condition=invisible]{Fancy Invisible}

Swapped the brackets and added support for custom labels like suggested.

We might need to do some reconciliation between this work and the work in #2475. In the latter, for example, we have translation strings for the condition tooltips because the data-tooltip API doesn't allow for an asynchronous lookup into a compendium. I'd rather we didn't have two 'sources' for where condition text comes from though.
Unifying them is not too difficult: If we want to use translation strings, we can have the enricher use them instead (we wouldn't use @Reference for this though) or, if we want to use compendium content, we can subclass the TokenHUD and call game.tooltip.activate ourselves after pulling the condition page's text from the compendium.
So I guess the question comes down to the merits of translation strings vs. compendium content. The former is inherently localisable, while the latter is not, and would require an additional module like Babele to be translated, but there might be other advantages and disadvantages that I have missed.

We might need to do some reconciliation between this work and the work in #2475. In the latter, for example, we have translation strings for the condition tooltips because the data-tooltip API doesn't allow for an asynchronous lookup into a compendium. I'd rather we didn't have two 'sources' for where condition text comes from though.

Is the text from Zhell's PR only being used in the description of the created active effects? Or does core use the CONFIG.statusEffects.description value elsewhere? If it is only used for active effect description then the PR is already overwriting toggleActiveEffect which can load the description from the compendium if necessary.

Unifying them is not too difficult: If we want to use translation strings, we can have the enricher use them instead (we wouldn't use @Reference for this though) or, if we want to use compendium content, we can subclass the TokenHUD and call game.tooltip.activate ourselves after pulling the condition page's text from the compendium.

For now this is just creating a link to the reference journal page, not pulling any text from the journal itself. The future version will display a tooltip of the journal page content, but at that point we'll need to decide just how much extended descriptions we want to stick into the translations, especially when this expands to things like skill or ability descriptions which are even longer.

Is the text from Zhell's PR only being used in the description of the created active effects? Or does core use the CONFIG.statusEffects.description value elsewhere? If it is only used for active effect description then the PR is already overwriting toggleActiveEffect which can load the description from the compendium if necessary.

Core does not make any alternate use of description, currently, of any of the "not-effect-data-objects" in CONFIG.statusEffects, other than their becoming the description of the effect of course. I override the method because core replaces statuses entirely, and we want more than one status in some cases.

Is the text from Zhell's PR only being used in the description of the created active effects? Or does core use the CONFIG.statusEffects.description value elsewhere? If it is only used for active effect description then the PR is already overwriting toggleActiveEffect which can load the description from the compendium if necessary.

It's just used for the description, but we probably want to use it for tooltips in the TokenHUD too. There are multiple ways we can pull the text from the journal page in any case, that's not really the issue.

For now this is just creating a link to the reference journal page, not pulling any text from the journal itself. The future version will display a tooltip of the journal page content

I guess what I'm suggesting is that the tooltip seems like the most useful part of this to me, and that linking to the journal page itself is less useful (except as a way to pull the tooltip text). We probably still want a @Reference enricher, but not necessarily for conditions specifically. I can easily imagine them working like our passive skill enrichers work currently, for example.
So if we only care about the tooltip, is a journal page the best place to get it, or should we use a translation string? Having had a bit more time to think about it, I think the main cons with the translation string comes from cases of nested conditions. The unconscious condition references the incapacitated condition, for example. If you've already clicked on the unconscious condition and brought up the journal page, you can then click the link to incapacitated in that journal page to jump straight to it. If we want to accomplish the same thing with a translation string, we might have to embed HTML in the translation string, which isn't great, or write some bespoke condition tooltip code, and the user will have to utilise the locked tooltip functionality in order to access the nested condition, which is not very discoverable currently.


Consider addding the ability to download specified saved collections instead of all of them

Provide us a use case of the feature
Imagine if we have the bunch of thousands saved posts. I usually try to add in custom saved collections by grouping the post type. We may have dozens of saved collections. That said, we wouldn't want to download them all. I just interested in with a few collections. It would be a really nice UX!
(I couldn't find any information in the doc, so I opened the feature request here.)
Describe the solution you'd like
Old way:
$ instaloader :saved  # downloads all collections

Proposed way:
$ instaloader --saved  # downloads all collections
$ instaloader --saved=foo, bar, baz  # downloads the only 'foo, bar, baz' collections

If the feature request is accepted, would you be willing to submit a pull request?
Not sure, I usually don't have a time. :(
Additional context
:saved command flag a bit weird for me. We may want to change :foo flag usages to --foo ones, in order to comply with Unix CLI standards. Wdyt?

Thanks for sharing your ideas here.
For downloading saved items of a certain collection only, there is already #544; hence, we close this issue.

Thanks! Actually, I have seen that issue. I created a new one because this is slightly different from it. I pointed here to show multiple tags use, and I also proposed flag usage change, i.e. from :saved to --saved. What do you think? Should we continue from there? 🤔

This answer is a mistake. @Dentrax 's idea is good.


Lazy Insertion

Constructing an entity while the world is running isn't very ergonomic right now and the naive way of doing it can lead to almost no parallel systems (Accessing each storage required for construction mutably, so it blocks all other systems using that storage). A better approach is something like an "initialization" system where it is possible to insert a flag component that signifies that a certain component should be inserted. For example:
struct Position { x: f32, y: f32, z: f32 };
struct InitPosition;
struct InitPositionSystem;
impl<'a> System<'a> for InitPositionSystem {
    type SystemData = (
        Entities<'a>,
        WriteStorage<'a, Position>,
        ReadStorage<'a, InitPosition>
    );
    fn run(&mut self, (entities, positions, inits): Self::SystemData) {
        for (entity, _) in (&*entities, &inits).join() {
            positions.insert(entity, Position { x: 0.0, y: 0.0, z: 0.0 });
        }
    }
}

I feel like this could be abstracted over a bit by allowing some sort of lazy insertion method for the world. So instead of having to set up all this for an initialization system, you could just do something like:
impl<'a> System<'a> for SomeSys {
    type SystemData = (
        LazyInsert<'a>,
        Entities<'a>,
    );
    fn run(&mut self, (lazy, entities): Self::SystemData) {
        for entity in (&*entities).join() {
            if ... { // some condition to insertion or something
                lazy.insert::<Position>(entity, Position { x: 0.0, y: 0.0, z: 0.0 });
            }
        }
    }
}

This would put the component into some queue in the world, so then once the world is maintained it inserts the components.

Is adding an entity (as opposed to a component) also affected by this slowdown?
let mut world: World;

// ...

impl System for ... {
    fn run(&mut self, entities: Entities) {
        if ... { // some condition to insertion or something
            let new_entity = world.create_entity().build();
        }
    }
}

Well, you are unable to actually get the world in a system, so entities can only be created atomically with the EntitiesRes struct.


Support "envelope encryption" AKA HLS-AES-128 in DASH

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.3.9
Please ask your question
Does shaka player support the AES Envelope encryption done in Azure Media Service (AMS) V2?
I am using Dash manifest with Envelope Encryption for Live stream. It's working in AMS player but in Shaka.

I'm not familiar with envelope encryption in Azure.  Can you provide a link to documentation?  I may be able to help you figure out how to configure the player for it.  My guess is that your app may need to configure network response filters in the player to unwrap or decrypt something.

Hi @joeyparrish , I think this may be help you.
https://learn.microsoft.com/en-us/azure/media-services/latest/stream-streaming-policy-concept#clear-key-common-encryption-cenc

We were using Dot net SDK for Azure Media Services for Livestream and VOD. There is a content key available in Azure media Services along with other Content protection ways such as Clear Key, Play ready, etc.
We were using the Envelope Encryption from the beginning.
Previously we were using HLS format for Livestreaming, now we want to use the Dash format also. But I believe the encrypted video is not working. Below I mentioned the response screenshot for manifest request.
When we are using the HLS format, the request for Key will be triggered from shaka and we were modifying and sending the Bearer token with request via our App.
But in Dash format the Key request has not being triggered. I don't know what I was missing.
Creating Envelope Key via SDK
https://learn.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.mediaservices.client.contentkeycollection.create?view=azure-dotnet#microsoft-windowsazure-mediaservices-client-contentkeycollection-create(system-guid-system-byte()-system-string-microsoft-windowsazure-mediaservices-client-contentkeytype)
ContentKey Enum
https://learn.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.mediaservices.client.contentkeytype?view=azure-dotnet
Response from Manifest Request has this.

If I'm understanding this correctly, it seems that envelope encryption is Microsoft's name for what Apple (frustratingly) calls simply "AES-128".  I'm going to start using Microsoft's term for it for clarity, since all modern DRM uses the AES-128 block cipher, and envelope encryption is distinct from those DRM schemes.
Envelope encryption is AES-128 in CBC mode applied to the entire stream, with keys delivered in the clear.
Common encryption DRM is typically done in one of two modes: AES-128 in CTR mode (CENC), or AES-128 in CBC mode with a pattern of skipped blocks (CBCS).  In either case, there are clear bytes and encrypted bytes in each encrypted segment, and we don't encrypt the entire stream.
These three modes (CENC, CBCS, and Envelope encryption) are all mutually incompatible.  CENC and CBCS both get fed to the browser encrypted, where the CDM uses a DRM license to decrypt.  CENC and CBCS have to be decrypted differently, but by the same basic infrastructure.  Envelope encryption gets a clear key and gets decrypted by the player with WebCrypto APIs before feeding it to the browser.  The browser only ever sees clear content.
This envelope encryption is supported by Shaka Player in HLS, but this is the first I've heard of it being used for DASH.  The same decryption code could be triggered to support it.  We just need to modify the DASH parser to get the necessary information and signal it to the rest of the player.
I'm going to convert this into a feature request.  My team doesn't have time to work on this right now, but we are always accepting PRs and happy to provide guidance.

Thanks for the help @joeyparrish .

@Ravi-79 can you provide a stream to implement this? Thanks!

Related to https://github.com/Dash-Industry-Forum/dash.js/issues/1993

@Ravi-79 I created https://github.com/shaka-project/shaka-player/pull/5656 to add this new funcionality

Hi @avelad , Can I have a documentation or steps to implement the AES-128 decryption in our custom application.
Like for HLS adding the token in KEY request, for PlayReady / Widevine updating the token in License request, how we can decrypt the AES-128 /Envelope Encryption

Decryption of segments is handled internally.  If you need to add a token to the key request, you can do that for DASH exactly as you would for HLS, by registering a request filter.

Thank you @joeyparrish


mobile browser support

the keypress event does not appear to work on mobile browsers so I have replace it with the keyup event.
this is working on firefox mobile 42 and the native browser on sailfish 2.0

originally I changed this to use keyup, but on further testing found that that does not always work. It is due to the fact that autosuggest in mobile browsers can get in the way (http://stackoverflow.com/a/18007731/98078). So I've converted this to use the input event instead. This does mean that horsey will only work on IE9 and greater. However the current IE support is questionable as click to select does not actually work (in any version I have tested).


winrm throws ECONRESET

var winrm = require('nodejs-winrm');
winrm.runCommand('mkdir D:\winrmtest001', '172.XX.208.XX', 'SCVMM\Administrator', 'XXinXXntXX', 5986);\
When trying to reach the above system, it takes so much time, giving ECONRESET error.  The above system requires VPN to get connected.
Do let us know.

What is the output of winrm id

I am not at all getting ID
I am getting below error after waiting for 2 minutes.
But with pywinrm its working.

Hello
How are you?


Admin check does not work properly in Powershell 6.1 preview 4

Using Powershell 6.1 preview 4, the command fails the admin check - even though it's being run as administrator:

Running the same command in Powershell 5 admin works fine. Not a big deal but worth updating the admin check for newer Powershells.

Hey @mikemaccana, I just downloaded the PowerShell 6.1 RC1 and couldn't reproduce the issue anymore. I hope this is fixed!


Feature/add spring config

Overview

Adds spring cloud config client to the course-management microservice to support externalizing configuration. This will come in handy once we deploy to the cloud and need to manage configuration easily.
closes #6.
New config server microservice: https://github.com/puffproject/config-server
New configuration repo for public config: https://github.com/puffproject/cloud-configuration
This change is a

[ ] Bug fix
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that will change exisiting functionality)
[ ] Documentation update

Description

Add spring-cloud-starter-config dependency + spring-cloud-dependencies dependency manager. (Simplifies things for eureka later)
Updates actuator endpoints to also include refresh: Allows to refresh configuration just by hitting an endpoint.
Added the @RefreshScope annotation on Swagger config class. Annotation can be used anywhere updateable config values are injected.
Added bootstrap.yml files to local spring cloud config details for connecting with the config server (bootstrap is loaded before application files)

Motivation/Links

This supports the DevOps principle of externalizing configuration in applications. With this we can securly pull configuration from the config server when deploying to the cloud. It also allows refreshing of the configuration on-the-fly instead of having to redeploy.
How was this tested?

Automated tests pass. Also manually tested connection between microservice & config server works. Automated intergration tests to follow.
Todos

[x] Ensure unit tests pass
[ ] Update documentation for changes (if necessary)
[x] Delete stale branch after merge

Codecov Report

Merging #17 (d71143b) into master (72c145e) will decrease coverage by 0.38%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #17      +/-   ##
============================================
- Coverage     77.86%   77.47%   -0.39%
  Complexity      120      120
============================================
  Files            24       24
  Lines           402      404       +2
  Branches         12       12
============================================
  Hits            313      313
- Misses           76       78       +2
  Partials         13       13

Impacted Files
Coverage Δ

...nagement/configuration/KeycloakSecurityConfig.java
0.00% <0.00%> (ø)

...courseManagement/configuration/Swagger2Config.java
95.00% <ø> (ø)

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 72c145e...d71143b. Read the comment docs.


How to get raw Data from onMessage in typescript.

i didn't see any documentation about how to get raw data from user message or friendRequest clearly.
plz help me find this out. thx man

You can try to call wechaty.puppet.messageRawPayload(msg.id)

thx


JSDoc dependency breaking build

the dependency of jsdoc should change from "^3.4.0" to "~3.4.0" in version 1.1.0
JSDoc introduced babylon in 3.5.0 which is producing errors when building on older node versions.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hi,
we do encounter the same problem. I just looked a bit more into the issue:
The dependency of JSDoc is written as ^3.4.0 which also includes 3.5.0. ( Can be calculated here in case one is unfamiliar with semver ).
As jsdoc released the first 3.5.0 package on 2017-07-10T02:26:25.790Z, we run into issues during doc creation now, as npm is installing jsdoc 3.5.x.
It would be nice if it were possible to use ~3.4.0 as its dependency.
Best Regards
~Mydayyy

Yep I'll try to fix this asap

Please let me know if version 2.1.1 fix it for you all.

Hi,
the problem is fixed on our side! Thanks you so much for your quick reaction!
Best Regards
~Mydayyy

I can confirm that the issue is resolved!
Thank you for your quick fix!


Week 1 Blog

I am opening issues to track any missing assignments. I don't at all mean this as "chastising" I am just curious to see if this is a helpful way to track work for completion.
https://github.com/Open-Source-Studio-at-ITP/Syllabus#assignment

[x] @alicehgsun
[x] @camilleweins
[x] @doodybrains
[ ] @guillemontecinos
[ ] @Hbentzur
[ ] @ilanabonder
[x] @jameshosken
[x] @js6450
[x] @linzhangcs
[x] @lunaog
[x] @muji786
[x] @NHibiki
[x] @nicolaspe
[ ] @tinkrmind
[x] @vince19972
[x] @WenheLI

I was in waitlist for that class, so I didn't come. I'll complete it asap. Thanks!

Completed here https://github.com/Open-Source-Studio-at-ITP/Syllabus/pull/99


App-specific user management

see https://github.com/Azure/azure-mobile-apps-ios-client/issues/44

Hi there, please have a look at the Readme section for the future of Azure Mobile Apps. Closing this issue for now. Thanks!


Reading files from S3

Hi David!
Trying to create an endpoint in an Express server like this:
app.get('/textract', function(req, res, next) { 	textract("https://s3.amazonaws.com/testbucket1a2b3c/test.pdf", function(error, text) { 		console.log(error); 		res.end(); 	}); });
Console returns [Error: File at path [[ https://s3.amazonaws.com/testbucket1a2b3c/test.pdf ]] does not exist.]
What does this mean exactly? Textract only works with local files? (in this case my file is uploaded to S3). Thanks!

Yep, only local files.

OK, thanks. Any plan to make it work with remote files?

That seems a bit like scope creep on a singularly focused module.  But I can consider adding such a thing.  It probably makes more sense as something wrapped around textract instead of embedded within.  The files would still need to be written locally.

Alright, thanks. Looking forward to your implementation. Apache Tika is very complicated to install, and yours is the only good text extractor that's written in node as far as I know.

Doing some refactoring and think I'll include this.  Will be a few days.

Awesome. I've implemented textract in an order form for translation agencies (clients upload documents and the app returns the number of words & pricing) and it works very well. All the files are stored in an AWS instance for now and textract is in the same instance as well. I will refactor the app to S3 when it's ready. If it helps, here's how I plan to use textract:

Client uploads a file to S3 (I use ng-file-upload: https://github.com/danialfarid/ng-file-upload)
Endpoint runs textract with path = S3 path and returns estimates

textract was born out of the contracting work I did that involved uploading resumes, extracting the text from them, loading solr with the resume text for searching, and tossing the resume itself into S3.  So that all sounds familiar. =)
Working through a set of enhancements over the next few days.  This'll be one of them.


Can we expect the a pinch to zoom functionality in the charts

When there is a pinch in or pinch out event performed on the chart  then the chart x and y axis to be scaled or zoomed.

I don't currently have any plans to implement this feature, it would be quite a lot of work. I'm definitely happy to accept pull requests though.


ModuleNotFoundError: No module named 'nc_library'

1)Error while running  gds-loopmirror notebook for loop mirror reflector
(ModuleNotFoundError: No module named 'nc_library')
2)Error while running microdisk notebook
(FileNotFoundError: [Errno 2] No such file or directory: '/home/haima/Downloads/MEEP_collection/jupyter-meep-master/notebooks/Microresonators/data/microresonators'
)

Thank you. I'll check it out


Add async API via Project Reactor

In addition to the blocking interface, offer an async API that either uses Project Reactor or allows apps to adapt an async API to it.
Reference: https://projectreactor.io

@cgillum: it appears you may have more context on this one? Not immediately sure how to label this one.

This is a feature request by the Dapr project to add new functionality to the core Durable Task Java APIs.

Thanks. @kaibocai please look to triage this request with the DF Java team :)

Add related issues https://github.com/microsoft/durabletask-java/issues/3, https://github.com/microsoft/durabletask-java/issues/2

FYI, the dependency on Project Reactor is being reconsidered in the Dapr community in favor of CompletableFuture. See https://github.com/dapr/java-sdk/issues/964


Create a package updates

Docs Build status updates of commit 118445a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-dotnet-cli.md

Line 78: [Warning] Tab name dotnet CLI is not approved. Tab names are case-sensitive. See https://aka.ms/ConceptualTabs for details.
Line 78: [Warning] Tab name MSBuild is not approved. Tab names are case-sensitive. See https://aka.ms/ConceptualTabs for details.
Line 78: [Warning] Tab dotnet-cli is not approved. Tab IDs are case-sensitive. See https://aka.ms/ConceptualTabs for details.
Line 78: [Warning] Tab msbuild is not approved. Tab IDs are case-sensitive. See https://aka.ms/ConceptualTabs for details.

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

Docs Build status updates of commit ab6f316:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-dotnet-cli.md

Line 78: [Warning] Tab name MSBuild is not approved. Tab names are case-sensitive. See https://aka.ms/ConceptualTabs for details.
Line 78: [Warning] Tab msbuild is not approved. Tab IDs are case-sensitive. See https://aka.ms/ConceptualTabs for details.

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

Docs Build status updates of commit e316607:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-dotnet-cli.md

Line 78: [Warning] Tab name MSBuild is not approved. Tab names are case-sensitive. See https://aka.ms/ConceptualTabs for details.
Line 78: [Warning] Tab msbuild is not approved. Tab IDs are case-sensitive. See https://aka.ms/ConceptualTabs for details.

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

Docs Build status updates of commit 64890dd:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).

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

Docs Build status updates of commit 879d6d2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/TOC.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning
View
Details

docs/index.md
:warning:Warning
View
Details

docs/reference/msbuild-targets.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/TOC.md

Line 0: [Warning] Invalid file link:(~/creating-a-package-msbuild.md).

docs/create-packages/creating-a-package-dotnet-cli.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).

docs/index.md

Line 0: [Warning] Invalid file link:(~/release-notes/).

docs/reference/msbuild-targets.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

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

Docs Build status updates of commit b6e767c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/TOC.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning
View
Details

docs/index.md
:warning:Warning
View
Details

docs/reference/msbuild-targets.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/TOC.md

Line 0: [Warning] Invalid file link:(~/creating-a-package-msbuild.md).

docs/create-packages/creating-a-package-dotnet-cli.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).

docs/index.md

Line 0: [Warning] Invalid file link:(~/release-notes/).

docs/reference/msbuild-targets.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

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

Docs Build status updates of commit b212c79:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/TOC.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:warning:Warning
View
Details

docs/create-packages/includes/choose-package-id.md
:warning:Warning
View
Details

docs/index.md
:warning:Warning
View
Details

docs/reference/msbuild-targets.md
:warning:Warning
View
Details

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/TOC.md

Line 0: [Warning] Invalid file link:(~/creating-a-package-msbuild.md).

docs/create-packages/creating-a-package-dotnet-cli.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

docs/create-packages/includes/choose-package-id.md

Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md).
Line 12: [Warning] Invalid file link:(~/create-packages/reference/package-versioning.md#semantic-versioning-200).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).
Line 14: [Warning] Invalid file link:(~/create-packages/consume-packages/dependency-resolution.md#dependency-resolution-with-packagereference).

docs/index.md

Line 0: [Warning] Invalid file link:(~/release-notes/).

docs/reference/msbuild-targets.md

Line 16: [Warning] Invalid file link:(~/create-packages/creating-a-package-msbuild).

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

Docs Build status updates of commit 917a553:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/create-packages/creating-a-package-msbuild.md
:white_check_mark:Succeeded
View

docs/create-packages/includes/choose-package-id.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/reference/msbuild-targets.md
:white_check_mark:Succeeded
View

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


Intelligent Snippets's error in neovim

# -*- coding: utf-8 -*-

import os
os.path.join([a], [filename])

when i enter ctrl +j on '[a]', neovim show error message:

This is how I tried to reproduce:

Touch an empty Python file and open it in NeoVim (or Vim).
Type up to os.path.j and then use <C-X><C-U> to trigger Kite's autocompletion.
Type <C-Y> to accept ...(<a>, <filename>) and jump back to the first snippet ([a]).
Type <C-j>.  As expected this jumps to the next snippet ([filename]).

So I wasn't able to reproduce the error.
Please could you tell me what commit your Kite vim plugin is at?
Do you get the error every time?

I use kite vim plugin' s version is 1.0.61, neovim's version is 0.5.0.
I get the error every time.

If you input a char on first snippet ([a]), and type C-k, then the error occur.

I get that too.  Thanks for the tip.

It seems to depend on whether the character you type has any potential completions (e.g. x) or not (e.g. y).

Please could you try the fix in #259?

I try #259,

Do you type 1 immediately after accepting the join() completion with <C-Y>?  In other words, when the first snippet is selected?
When I do that, and then type <C-j>, it works as expected.

^@ is a null byte.  I don't know why you're seeing this.

when I type c-n, the join([a], [filename]) is autocomplete, I don't type c-y.


update kontent sdk to kontent.ai

Hi Ilesh. I don't seem to have write access to the repo so here a PR from my fork.
There didn't seem to be much to do there, the package.json already specified the newer kontent.ai api but a few of the components were still asking for the old one. Got it working on the Content Tool App environemnt and it looks to be working fine, translated a bunch of stuff.
The other changes were a dead end, I'll explain in more detail in the ticket.

👷 Deploy Preview for leafy-pothos-d8d40e processing.

Name
Link

🔨 Latest commit
1f2747ca9880eb6a24e173c618600e174fd4fcd6

🔍 Latest deploy log
https://app.netlify.com/sites/leafy-pothos-d8d40e/deploys/6491c599d38fdf00082b4f11


es-data log4j2.properties java.nio.file.AccessDeniedException

The cluster seemed to work fine but after a while, one of the es-data container fails to launch with the exception:
Exception in thread "main" org.elasticsearch.bootstrap.BootstrapException: java.nio.file.AccessDeniedException: /elasticsearch/config/repository-s3/log4j2.properties
Likely root cause: java.nio.file.AccessDeniedException: /elasticsearch/config/repository-s3/log4j2.properties
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)

Seems like the repository-s3 plugin is the culprit there. Are you doing snapshots to s3? I haven't run into this yet. What happens if you delete the pod and let it recreate?

Hi I'm not doing snapshot. Cluster seems stable now.

Going to close this for now, please post back if it comes up again.


Fix #1746, Validate EVS Register inputs first.

Describe the contribution
Fixes #1746
Move the validation of inputs to be the first thing for CFE_EVS_Register
Testing performed
Build and run unit test
Expected behavior changes
No impact to behavior
System(s) tested on
Ubuntu 20.04
Contributor Info - All information REQUIRED for consideration of pull request
Alex Campbell GSFC

This is intended behavior so no change needed.


fix wait_for_pipelines debug

rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED
to better assist in debugging the chains error introduced with https://github.com/openshift-pipelines/pipeline-service/pull/985
@yashvardhannanavati @arewm @lcarva FYI

merging (upgrade test still a known perm fail that we will either disable or find someone to triage)

@yashvardhannanavati @arewm @lcarva
note our simple chains smoke test in test-pipeline-service-deployment-ocp-414 passes here
I'll merge this and rebase https://github.com/openshift-pipelines/pipeline-service/pull/985 so we can hopefully see what is happening in the test over there.

Thank you so much @gabemontero for all the help!


Unable to start OPAL Server or Client on privileged ports

I'm getting following error when running OPAL on port 443 as Fargate containers
Can't connect to ('<IP_ADDRESS>', 443)

Only non-privileged ports (>=1024)  are supported.

You can start OPAL on another port (e.g 7766) in the container and have the container map 443 to it.

Hey @ojecborec, thank you for taking the time to report the issue and submit a PR! We appreciate your contribution and the effort you put into troubleshooting and proposing a solution.
In general, it's best practice to run containerized services on non-privileged ports (>=1024), and these ports can then be mapped to any desired port externally. Running services on higher port numbers is standard and secure, and it aligns well with AWS Fargate's expected setup.
For Fargate setups specifically, it's common to place services behind an Application Load Balancer (ALB) or similar load balancer, which handles TLS termination and directs traffic to your container without requiring the container itself to bind to privileged ports. This setup not only simplifies security configurations but also helps maintain scalability and flexibility for routing traffic securely. Here’s a relevant Reddit post discussing the advantages of using an ALB in front of Fargate. AWS's Fargate documentation also provides further details on how ALBs are integrated for secure load balancing.
Additionally, OPAL is designed to use HTTP, so assigning it to port 443 could create confusion for users expecting an HTTPS connection by default. This is another reason we recommend using a load balancer setup for TLS handling.
If your specific use case requires OPAL to listen on port 443, you could create a custom Docker image that inherits from the official opal-server or opal-client image and then adds the necessary permissions. This allows you to customize the container while keeping security and configuration aligned with your specific needs.
Below is an example of a custom Dockerfile that incorporates your proposed change:
# Start with the official OPAL server or client image
FROM opal-server:latest  # Or `opal-client:latest`, depending on your needs

# Install any extra dependency you need
RUN apt-get install -y libcap2-bin

# Set permissions to allow binding to privileged ports
RUN setcap 'cap_net_bind_service=+ep' /usr/local/bin/python3.10

# Expose port 443 if still needed
EXPOSE 443

This Dockerfile extends the official opal-server or opal-client image with your required permissions. You would then be able to deploy this custom image to Fargate if necessary.
At this time, we are not planning to allow OPAL to run on privileged ports in the official OPAL images, as we want to maintain security and alignment with standard container practices. Therefore, we will close the PR and this issue. However, your feedback has been helpful, and we encourage you to reach out if you have other suggestions or if we can clarify any other details around setting up OPAL in similar environments.
Thank you again for your contribution!


Jsantos/wildfly

Description
add wildfly system tests
Check list
Your PR is not ready to be reviewed? Please save it as a draft :pray:

[ ] Follows the style guidelines of this project (See how to easily lint the code)
[ ] CI is passing
[ ] There is at least one approval from code owners

Yes to all? Feel free to merge it whenever you want :heart:

Don't mind about ruby failures. You can merge it when you want !


ROX-11909: save kuttl JUnit XML to artifacts

Description
Prow can display tests that fail in its JUnit panel. e.g. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/branch-ci-stackrox-stackrox-master-merge-go-unit-tests/1550162970292523008
For Prow to display tests that fail in its JUnit panel it needs files in JUnit XML format copied to $ARTIFACT_DIR. This PR does that for openshift-4-operator-e2e-tests, which are run via kuttl.
Checklist

[x] Investigated and inspected CI test results
~- [ ] Unit test and regression tests added~
[x] Evaluated and added CHANGELOG entry if required
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed

Verified in CI that artifacts are in place, see ci/prow/openshift-4-operator-e2e-tests

/retest

/retest

/retest

/retest

/test openshift-newest-operator-e2e-tests
/test openshift-oldest-operator-e2e-tests

And let's see whether this actually works in the operator jobs :-)

Unfortunately:
****
**** 09:54:36: final post completed
****
Traceback (most recent call last):
  File "/go/src/github.com/stackrox/stackrox/scripts/ci/jobs/openshift_newest_operator_e2e_tests.py", line 16, in <module>
    final_post=FinalPost(handle_e2e_progress_failures=False),
  File "/go/src/github.com/stackrox/stackrox/.openshift-ci/runners.py", line 83, in run
    raise hold
  File "/go/src/github.com/stackrox/stackrox/.openshift-ci/runners.py", line 57, in run
    self.run_test_set(test_set)
  File "/go/src/github.com/stackrox/stackrox/.openshift-ci/runners.py", line 113, in run_test_set
    raise hold
  File "/go/src/github.com/stackrox/stackrox/.openshift-ci/runners.py", line 104, in run_test_set
    test_set["post_test"].run(test_outputs=test_set["test"].test_outputs,
AttributeError: 'OperatorE2eTest' object has no attribute 'test_outputs'

/test openshift-newest-operator-e2e-tests
/test openshift-oldest-operator-e2e-tests

/test openshift-newest-operator-e2e-tests
/test openshift-oldest-operator-e2e-tests

/test openshift-newest-operator-e2e-tests
/test openshift-oldest-operator-e2e-tests

It would be nice to have an example of a failed kuttl test result in the PR description as proof of work.

Let's see how https://github.com/stackrox/stackrox/pull/3362 goes

Failure cases.

@porridge thanks for testing 👍  Merging the PR


⚠ GitLab Server has degraded performance

In 345c3b5, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11714 ms

Resolved: GitLab Server performance has improved in 4d1f76a.


How to set action urls?

How to set correct routes to comment create, thumbs-up and thumbs-down actions, because default values are related to page, where widget is called?

You can see all default routes here: https://github.com/ogheo/yii2-comments/blob/master/src/Bootstrap.php
to access them you have to call for example: comments/default/create.
You can also overwrite them in your main.php config file.

Thanks!


[Biome] Found 0 error and 0 warning

Describe the bug
Biome finds no error and warnings in my code when launched via vite-plugin-checker, whereas it finds some when launched via npm
Reproduction
vite.config.ts
            checker({
                biome: true,
                typescript: true,
                enableBuild: true,
                overlay: true,
                terminal: true,
            })

biome.json is located in the same folder as vite config.
Running the following npm command outputs errors:
biome lint --write ./src

Whereas running npm start, outputs :
[Biome] Found 0 error and 0 warning

Expected behavior
Since biome finds errors when run via npm script, I'd expect the same error output from vite-plugin-checker's integration of biome.
The number of diagnostics exceeds the number allowed by Biome.
Diagnostics not shown: 92.
Checked 155 files in 38ms. No fixes applied.
Found 1 error.
Found 111 warnings.
lint
Some errors were emitted while running checks.

System Info
System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 3.20 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.7.0 - /opt/homebrew/bin/node
    npm: 10.8.2 - /opt/homebrew/bin/npm
    pnpm: 9.8.0 - /opt/homebrew/bin/pnpm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 129.0.6668.101
    Safari: 17.6
  npmPackages:
    vite-plugin-checker: ^0.8.0 => 0.8.0

Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Closing, I do not reproduce. Most likely an issue with biome config


Exception after reload

When running my app with your service worker on mobile (as standalone app) I get an error in the developer console. On desktop it works just fine.
Though, the app seems to work. Don't know if that error is critical.
I configured the HTMLToCache property to use /dashboard as value.

The second error seems to be a chrome issue: http://stackoverflow.com/questions/33328579/service-worker-throwing-an-neterr-file-exists-error

The first error sometimes appears but doesn't seems critical as everything's working for now. I'm not sure how can I reproduce it, nor why Response is said to be used although it shouldn't as I use clone. So I'm open to ideas but I don't know why this error randomly occurs.

Alright, thx for clarification.

I close this issue as it's not really an issue actually. It's a bit weird and annoying but otherwise it doesn't cause any trouble.

I'm glad #3 fix this issue.

great! Glad to hear. Will update my script.


Base

Test of pull request successful. Add some basic text, colors, and change the width. Made containers for links to other pages.

Thanks, Myles! I don't see your photo on the site yet; could you add it or remove the jpeg file from this commit? Also, you should use Photoshop or ImageMagick to compress your images so that they download faster. I typically like to see images like this in the 200KB zone instead of 2MB.

I'm on it!

Hopefully everything is fixed from that last pr, also added some color and a nav bar.

Work on last pull request

oh-- also, don't forget to deploy a version and share the link!

Done!

http://bosticc-step-2020.appspot.com/ here is the link

my b! didn't mean to close it

LGTM

Is onf supposed to be there still?


Unreferenced static images from /resources/images folder are not processed in bud

[x] I've read the guidelines for Contributing to Roots Projects
[x] This request isn't a duplicate of an existing issue
[x] I've read the docs and followed them (if applicable)
[x] This is not a personal support request that should be posted on the Roots Discourse community

Description
Since migrating from laravel mix to bud the asset building process is somewhat improved I guess and images or other static resources referenced in asset files are included automatically in the public folder. What I noticed however is that images located in resources/images which have no reference are not included.
Steps to reproduce

Clone the repository
Install all dependencies and build requirements, fire up a dev server
Add an image to the resources/images folder
Load this image via the asset directive in a template

<img class="block w-auto h-6" src="@asset('images/company-mark.svg')" alt="company logo">

Rebuild the assets manually yarn build

Expected behavior:

There should now be a folder in the public directory for images and the manifest.json file should reference the actual path.

Actual behavior:

The images are not processed

Reproduces how often: [What percentage of the time does it reproduce?]
Versions
HEAD
Additional information
I looked at the old Laravel mix implementation and noticed a difference with the folders.
Line in question:
https://github.com/roots/sage/blob/master/bud.config.js#L24
changing this from assets/images to resources/images fixes the problem

thanks for reporting this! would you mind submitting a PR with that fix?


Added IEEE list, moved mathscinet

Integrate IEEE list in merge script (if it is not kept separate in JabRef any more).
mathematics.csv can be automatically compiled, but MathSciNet does not always stick to ISO, so AMS list should have higher priority.

@all-contributors please add @jlaehne for content


Trouble installing torch-scatter

I am having trouble installing torch-scatter on my local machine. I have a old cpu (9 years or so) and a 970gpu.
I installed torch via
pip3 install torch torchvision
and
python -c "import torch; print(torch.version)"

1.0.1.post2
python -c "import torch; print(torch.cuda.is_available())"

True

nvcc --version

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Tue_Aug_11_14:27:32_CDT_2015
Cuda compilation tools, release 7.5, V7.5.17

gcc --version

gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

So good so far, i hope. After adding the PATH and CPATH as suggested in the 'install' documentation, I do
$ git clone https://github.com/rusty1s/pytorch_scatter
$ cd pytorch_scatter
$ python setup.py install
with the following output
running install
running bdist_egg
running egg_info
writing torch_scatter.egg-info/PKG-INFO
writing dependency_links to torch_scatter.egg-info/dependency_links.txt
writing top-level names to torch_scatter.egg-info/top_level.txt
reading manifest file 'torch_scatter.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'torch_scatter.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
running build_ext
building 'torch_scatter.scatter_cuda' extension
gcc -pthread -B /home/j-pc-ub/anaconda3/envs/masterthesis/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/torch/csrc/api/include -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/TH -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/THC -I/usr/include -I/home/j-pc-ub/anaconda3/envs/masterthesis/include/python3.7m -c cuda/scatter.cpp -o build/temp.linux-x86_64-3.7/cuda/scatter.o -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=scatter_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++11
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
/usr/bin/nvcc -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/torch/csrc/api/include -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/TH -I/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/THC -I/usr/include -I/home/j-pc-ub/anaconda3/envs/masterthesis/include/python3.7m -c cuda/scatter_kernel.cu -o build/temp.linux-x86_64-3.7/cuda/scatter_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --compiler-options '-fPIC' -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=scatter_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++11
/usr/lib/gcc/x86_64-linux-gnu/5/include/mwaitxintrin.h(36): error: identifier "__builtin_ia32_monitorx" is undefined
/usr/lib/gcc/x86_64-linux-gnu/5/include/mwaitxintrin.h(42): error: identifier "__builtin_ia32_mwaitx" is undefined
/home/j-pc-ub/anaconda3/envs/masterthesis/lib/python3.7/site-packages/torch/lib/include/c10/Half-inl.h(21): error: identifier "__half_as_short" is undefined
3 errors detected in the compilation of "/tmp/tmpxft_00000ea0_00000000-7_scatter_kernel.cpp1.ii".
error: command '/usr/bin/nvcc' failed with exit status 2
Any suggestsions?

I seperate this into two comments becasue its two approaches:
I also tried simply installing via pip install torch-scatter. This gives no errors, but  doing
python -c "import torch; import torch_scatter"
Traceback (most recent call last):
File "", line 1, in
File "/home/j-pc-ub/Documents/installs/pytorch_scatter/torch_scatter/init.py", line 3, in
from .mul import scatter_mul
File "/home/j-pc-ub/Documents/installs/pytorch_scatter/torch_scatter/mul.py", line 3, in
from torch_scatter.utils.ext import get_func
File "/home/j-pc-ub/Documents/installs/pytorch_scatter/torch_scatter/utils/ext.py", line 5, in
import torch_scatter.scatter_cuda
ModuleNotFoundError: No module named 'torch_scatter.scatter_cuda'

I tried several other approaches, but i believe the main issue lies in the
/usr/bin/nvcc ... call. Any ideas what could be causing this and how to get rid of the problem?

Have you tried to google the error message? (e.g. https://github.com/NVIDIA/nccl/issues/29)
It seems solvable by adding the following CXX flags:
-D_MWAITXINTRIN_H_INCLUDED
-D_FORCE_INLINES
-D__STRICT_ANSI__

Yes i looked at that. But i have
nvcc --version:
Cuda compilation tools, release 7.5, V7.5.17
Is that an issue. I am upgrading my whole cuda world right now to see what happens next.
If this doesn't help i will look more int ot he CXX flags

I've never tested it with CUDA 7.5. Hopefully CUDA 8 might fix this issue.

success with cuda 9.2! Thanks anyways!


Patch 1

Some suggested changes to the grammar, based on my experience (and to some degree personal preference):

Factor out delimiter tokens into hidden rules. There's not really any reason to have the parser produce these tokens.
Marked the top-level rules as compound-atomic. I am intuiting here that you do not want to allow whitespace within a read geometry string. You don't really need this since you did not define a WHITESPACE rule but I think it's good to use it anyway because 1) it shows intention and 2) it future-proofs you in case you add a WHITESPACE rule later.
Organized the rules into a structure that mirrors the parse tree they produce.
Removed some unnecessary parens and changed {0,1} to ?.

Are single-end geometries allowed? If so you probably want to change frag_desc to:
frag_desc = { read_1_desc ~ read_2_desc? }

Hi @jdidion,
These are great; thanks! Currently, I'm iterating on the improved-grammar branch, so I'll try and follow some of these suggestions there as well.  At the current time, single-end geometries aren't supported yet (we are building out the use-cases as we need them), but I don't see any principled reason they shouldn't be supported, so we should work toward that.


Fix the presence change

Make sure the setPresence call has the right parameters so that it does update correctly :)

code for reference:
https://github.com/DV8FromTheWorld/JDA/blob/master/src/main/java/net/dv8tion/jda/core/managers/impl/PresenceImpl.java#L92-L96

#483 @WalshyDev You got ninjad

@binaryoverload is it a ninja if that one is older? Also that doesn't fix the setStatus ;)

@WalshyDev It's not older xD He opened it after yours

Whoops... thought this was a Issue at first
Gonna drop my PR then...
Can you fix the setStatus one to use the 3-arg setStatus?


Intermittent missing invocations of console commands

Hello,
I wanted to know if anyone has experienced missing invocations of some of their console commands? I have an EventBridge setup to run each minute, invoking my artisan Lambda, running schedule:run... this is working for the vast majority of jobs.
There are some commands that seem to never get run (even though they work fine using the sls invoke -f artisan --stage prod --data "artisan:command").
Here is an example of a job that should be called hourly - you can see some random gaps.

I have checked other jobs that are more frequent, and they seem to be running on schedule (every 2 minutes) without gaps... and I have another job that is scheduled daily() that never gets invoked.
I have changed the EventBridge to use the cron(* * * * ? *) rule instead of the rate(1 minute).
Any help would be appreciated - thanks!

Oh wow that is weird! It might be worth asking the AWS support about this?
And on my side I've never seen this but I don't use events like this too much, only on smaller projects and I don't check their logs enough I'm afraid.


Release 0.5.0 (6)

Release 0.5.0 (6) to main.

@manh-t There are still some wip tickets with 0.5.0 milestone. Are we moving them to 0.6.0?

@luongvo yes, we will move undone tickets to 0.6.0, and I'm going to announce them to the Slack channel 🙇


[Issue-1161] - TP - flattening menu structure to remove hard-coded menu groupings

the first step towards achieving #1161 (the ability to customize the menu structure)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/380/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/337/


Display descriptions of outputs

It would be nice if the description of outputs, if present, would be displayed in the UI somehow. Currently in the finished job view we have a nested list under the "Result" section, which looks like this (without the bullets):

Results folder

ODT

(This is for the DTBook to ODT script.) The "ODT" option also has a discription: "The output braille file.". Quite simple in this case but it could contain more text. It would be nice if this was incorporated in the UI. Perhaps it could be done by making the outputs appear more like the options in the job form view, i.e. with a little triangle before the items to make them fold.

The descriptions of the outputs aren't available via the webservice (or point me to where I'd find them?)
E.g.
This is a successful job with results
<job href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094" id="1a4ed219-4d21-47a4-be35-d0d0bbb66094" status="SUCCESS">
<nicename>EPUB 3 Validator</nicename>
<script href="http://<IP_ADDRESS>:49152/ws/scripts/epub3-validator" id="epub3-validator" input-filesets="epub3">
<nicename>EPUB 3 Validator</nicename>
<description>Validates a EPUB.</description>
<version>2.0.3</version>
</script>
<messages progress="1.0">
<message content="Running EPUBCheck" level="INFO" portion="0.8" progress="1.0" sequence="18" timeStamp="1678209648735"/>
</messages>
<log href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/log"/>
<results href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/result" mime-type="application/zip">
<result from="port" href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/result/port/html-report" mime-type="application/zip" name="html-report" nicename="Validation report">
<result file="file:/Users/marisa/Library/Application%20Support/pipeline-ui/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/output/html-report/html-report.html" href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/result/port/html-report/idx/html-report/html-report.html" mime-type="application/vnd.pipeline.report+xml" size="1828"/>
</result>
<result from="port" href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/result/port/ace-report" mime-type="application/zip" name="ace-report" nicename="Accessibility report">
<result file="file:/Users/marisa/Library/Application%20Support/pipeline-ui/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/output/ace-report/ace-report.html" href="http://<IP_ADDRESS>:49152/ws/jobs/1a4ed219-4d21-47a4-be35-d0d0bbb66094/result/port/ace-report/idx/ace-report/ace-report.html" mime-type="application/vnd.pipeline.report+xml" size="157"/>
</result>
</results>
</job>

and this is the script that it used
<script href="http://<IP_ADDRESS>:49152/ws/scripts/epub3-validator" id="epub3-validator" input-filesets="epub3">
<nicename>EPUB 3 Validator</nicename>
<description>Validates a EPUB.</description>
<version>2.0.3</version>
<homepage>
http://daisy.github.io/pipeline/Get-Help/User-Guide/Scripts/epub3-validator/
</homepage>
<option desc="Either a *.epub file or a *.opf file." mediaType="application/epub+zip application/oebps-package+xml" name="epub" nicename="EPUB" ordered="true" required="true" sequence="false" type="anyFileURI"/>
<option default="false" desc="Check the compliance to the EPUB accessibility specification using the [DAISY Ace](https://daisy.github.io/ace) tool. To use this option, check [how to install Ace](https://daisy.github.io/ace/getting-started/installation/) on your system. Note that this option is only available for zipped EPUBs." name="accessibility-check" nicename="Enable accessibility check" ordered="true" required="false" sequence="false" type="boolean"/>
</script>
``

D'oh. Forgot about that. That's obviously an issue that needs to be addressed first. It seems like something we can perfectly do in a backward-compatible way.

Blocked on https://github.com/daisy/pipeline-framework/issues/187.

This is now possible to implement with engine version 1.14.13.

This seems ok to me now, I think the UI was already looking for nicename on the results elements and is now using it automatically.

Nice!

Fixed by https://github.com/daisy/pipeline-ui/pull/144

Doesn't seem to be fixed after all. In the case of the DTBook to ODT script, the finished job view still contains:
Results

Results folder

ODT

but the description "The output braille file." is missing.

Oh ok yes I see, we need to parse the XML to get the desc element. Sorry I thought it was coming from nicename. Schedule this for the next milestone?

Yes sounds good


[plan-permalink] Move plan slugs to plan templates

@davisagli it's my go-to when cornered in a situation like that.
In particular, .update(foo=F('bar__baz')) doesn't work (can't update an F with a join apparently), and explicitly loading the objects into memory and saving them doesn't work because of parler not working right in migration files with the faked-out models.

@davisagli I think this is ready to go, once you've had a chance to review it and/or test it out functionally.

I tested this locally. The migration ran as expected, but the button to go from the product page to the plan page is linking to http://localhost:8080/products/npsp/3.149/null even though the Plan is associated with a PlanTemplate that has a slug.

I tested this locally. The migration ran as expected, but the button to go from the product page to the plan page is linking to http://localhost:8080/products/npsp/3.149/null even though the Plan is associated with a PlanTemplate that has a slug.

@wlonk can you take a look at this?

@jgerigmeyer yes, it's enqueued, I'm just working on the logging issues first :)

I'm guessing that the slug is not being passed through from its new location to the serializer correctly.

@davisagli great to hear; can you clarify what the misconfiguration was, so that we can spot it and better avoid it if someone else lands there?

@wlonk I thought I had created the slug but I hadn't, simple as that 😒

Hah, well, that'd do it!


Manifest file path should not be hard code

Hi, this project is a good idea!  But the hard code File androidManifest = project.file('src/main/AndroidManifest.xml') will cause some problems when my project structure is different from AS project. For example the project migrated from eclipse. Maybe you can choose a more configurable method.

Thanks for the heads-up!


Add Cesium as Bower dependency

GitHub user @mixxen provides Cesium as a bower dependency and keeps it relatively up-to-date. I've added it as a dependency in bower.json to ease development for the client.
See https://github.com/mixxen/cesiumjs

Looks good to me!

Do we create a new version? What's the procedure in terms of the bower repository?

Yup, I believe we'd create a new release on Github, which would automatically sync up with bower.

Ok, we should do that after we process all the pull requests / issues i made today, right?

@BGR360 yup, I think that would be the best time to do it.


--force option not recognized at cli

Neither -o nor --force are recognized as CLI options for swagger project generate-test, but the rest of the overwriting functionality is there and working.

@noahdietz, a quick question, so when you do generate-test -o, do you need to add anything after that, I mean like generate-test -o true, or something?

@elsapeng no, the existence of the option in the CLI should indicate true and the absence should make the flag false by default


Revert "Undo revert of refactored code"

Reverts nodegit/promisify-node#7

That undo breaks more than just nodegit. We'll need better testing and probably figure out a better way to determine what methods to promisify. https://github.com/nodegit/promisify-node/pull/7#issuecomment-133080244


Review impact of static local functions on existing rules

https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-8#static-local-functions

I don't think any rules need to be updated to account for this. However, we have some sections of code that scan methods for all variable names (to avoid conflicts), and this code will need to be updated to account for the scoping changes brought in by C# 8.


fix(executor): Ignore not existing metadata. Fixes #5656

@alexec Hi alex，should this fix be cherry-picked into v2.12？We also face this issue with v2.12


File Extraction Issue

Can't Extract the Zip file. It make not responding error. And can't even view the zip file.

what happen ?

When I try to extract the file it throws a not responding error. My OS is windows 11. But it worked in ubuntu virtual machine.


Add seconds counter in timesheet duration field when tracking time

a suggestion to include seconds in the duration field on timesheets page --> 00:00:00
This could could be added to provide some better immediate visual feedback that the tracking has started, the 00:00 duration was a bit confusing at first since it only shows hour/minutes.

Sorry I totally missed this issue! Adding seconds is actually something I thought about earlier. I will test to see the effects of this.
I think I will only add the seconds on the "running" timer though.

Will look like this.

Will create a PR for it

Merged. Thanks for the suggestions again @ThomasRoest


Rxjs 6.0 support

Added rxjs 6.0 support with breaking compatibility.
Now:
only angular 6 is supported.
typescript 2.7.2 got from github, because of no tag in npm typescript repo for version >=2.7 and < 2.8
used nodejs 10.0.0 and npm 6.0.0
possible bugs are not known.

Hellow, I found that you use the previous version of RxJS but on our project we migrating to the angular 6.0. Would you mind add this migration to your library? Your library is realy important for our project and it will be annoyingly to remove it, because of small incompatibility!

Hi @new-inventor, you can use release 3.0.0 with support of @angular v6 and RxJS ^6.0.
Waiting for your feedback.

Thank you for your upgrade. I'll test it as soon as possible.


Install in LIBRARY_PREFIX

Fix #30

@sdebionne can you re-open this PR against the upstream feedstock in https://github.com/conda-forge/pybind11-feedstock please?

@ax3l Sure do, that was my original intention.


Insecure Randomness in ws 1.x

See https://snyk.io/vuln/npm:ws:20160920
Solution: Update to v2.x

Or update to https://github.com/websockets/ws/releases/tag/1.1.2 if you want to stay at v1

It's already picking it, closing https://github.com/maxogden/websocket-stream/blob/master/package.json#L29.

However, this update will be installed automatically from minor release update in<EMAIL_ADDRESS>I don't know if this a issue in snyk, because it should be solved after update node_modules.

Yes it's a problem with snyk, 1.1.2 is safe to use.


[feat] Improve the color styling for lightmode on the opening screen

Make the colors more agreeable to what we have for darkmode – i.e. make custom styles that look good for this page that is shown when no projects are in Onlook.

Hi @drfarrell !
Can you please assign this to me ?
From what I understand, I'll need to style the UI for app/src/routes/projects/ProjectsTab/Create/ChooseMethod.tsx to align more with what is present for the Dark Theme. Do correct me if required.
Best Regards

Hey @Kabiirk , yes precisely. There are examples of design token uses that handle both dark and light mode. Our design tokens are defined here:
https://github.com/onlook-dev/onlook/blob/827287e23c694d6b998025bfabc3ddf0ae9067a0/app/src/index.css#L5

Thanks, I'll start working on it & share something soon.

Hi !
Just a Sit Rep: I'm still working on this, will make a PR in some time.

Thanks for the update @Kabiirk !

Hi guys !
Do I need to add new  design tokens to index.css ? I've only made changes to app/.../Create/ChooseMethod.tsx since I assume this change only affects a very specific state of the projects page (when there are no projects), It's going to be only once in the app.
I tried multiple color combinations & found these to be the most optimal:
Option 1:
Here, I stuck to your original theme, which I think looks good both in light & Dark mode. I just modified the relative color ratios (ratio between blues in New Onlook project wasn't the same as the teals in Import existing project, so I made them more 'harmonious' to each other by making the bg-blue a bit darker).

Light

Dark

Option 2:
I thought the above changes were 'too few' for the PR, so I imposter-syndrom-ed myself & made a different color scheme 🙃
Since Gray usually denotes secondary buttons/text etc, I used them as the same, & retained blue as the 'primary' color (primay colors in index.css tokens are white, secondary & tertiary are too close to each other, so I did not use those).

Light

Dark

Let me know which you think is better & I'll proceed with the PR.

@drfarrell , please give your input. If possible, recommend if we have an existing token. Otherwise I think it makes sense to add once if we need to.

@Kabiirk the colors should be more of a "light-mode" inversion of the dark mode colors. So if the spectrum of colors is 50-950 with
50 100 200 300 400 500 600 700 800 900 950
Then you can probably get pretty close by just flipping the spectrum the other way around for light mode.
950 900 800 700 600 500 400 300 200 100 50
So if something is dark:teal-800 in dark mode, you can assign in teal-200 to get light mode.
This isn't perfect, but will get you closer to what the colors should look like in light mode. Try making these cards feel "light" by first inverting the number for that class in light mode, and then choosing adjacent numbers until it "feels" lighter, because the current configuration is too dark against the white background.

Hi @drfarrell ,
Thanks for the pointers ! I followed the "inversion" approach (with modifications) for a better colors in Light & dark mode.
Option 1

Option 2

Let me know which one you like, & I'll make the PR.

@Kabiirk option 2 looks much better yes. Can you plz make the PR? I can review it


Errors

When running docker-compose up, getting these errors:
`#docker-compose up
Creating devstack_mysql_1
Building front
Step 1 : FROM nginx
---> 0d409d33b27e
Step 2 : RUN rm -f /etc/nginx/conf.d/*
---> Using cache
---> b2eb6f3730ce
Step 3 : RUN apt-get update && apt-get install -my   supervisor   curl   wget   php5-curl   php5-fpm   php5-gd   php5-memcached   php5-mysql   php5-mcrypt   php5-sqlite   php5-xdebug   php-apc
---> Running in 380a58213fb9
Err http://httpredir.debian.org jessie InRelease
Err http://httpredir.debian.org jessie-updates InRelease
Err http://httpredir.debian.org jessie Release.gpg
Could not resolve 'httpredir.debian.org'
Err http://httpredir.debian.org jessie-updates Release.gpg
Could not resolve 'httpredir.debian.org'
Err http://nginx.org jessie InRelease
Err http://nginx.org jessie Release.gpg
Could not resolve 'nginx.org'
Err http://security.debian.org jessie/updates InRelease
Err http://security.debian.org jessie/updates Release.gpg
Could not resolve 'security.debian.org'
Reading package lists...
W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie/InRelease
W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-updates/InRelease
W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease
W: Failed to fetch http://nginx.org/packages/mainline/debian/dists/jessie/InRelease
W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie/Release.gpg  Could not resolve 'httpredir.debian.org'
W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-updates/Release.gpg  Could not resolve 'httpredir.debian.org'
W: Failed to fetch http://nginx.org/packages/mainline/debian/dists/jessie/Release.gpg  Could not resolve 'nginx.org'
W: Failed to fetch http://security.debian.org/dists/jessie/updates/Release.gpg  Could not resolve 'security.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
Package php5-fpm is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Unable to locate package supervisor
E: Unable to locate package curl
E: Unable to locate package wget
E: Unable to locate package php5-curl
E: Package 'php5-fpm' has no installation candidate
E: Unable to locate package php5-gd
E: Unable to locate package php5-memcached
E: Unable to locate package php5-mysql
E: Unable to locate package php5-mcrypt
E: Unable to locate package php5-sqlite
E: Unable to locate package php5-xdebug
E: Unable to locate package php-apc
ERROR: Service 'front' failed to build: The command '/bin/sh -c apt-get update && apt-get install -my   supervisor   curl   wget   php5-curl   php5-fpm   php5-gd   php5-memcached   php5-mysql   php5-mcrypt   php5-sqlite   php5-xdebug   php-apc' returned a non-zero code: 100`

Either the Debian source is down or your box isn't connected to the internet. Have you tried again since opening the issue?

Yes the container had no connection.  I had to edit /etc/NetworkManager/NetworkManager.conf and comment out "dns=dnsmasq" to get connections working


Allow python/R bindings to use an external libxgboost

Would it be possible to change the R/python bindings so they can use precompiled xgboost libraries? In conda, as an example, we distribute the standard libraries separate from the python and R bindings, since users rarely need all of them. An example patch for the python bindings can be found here, though it should be modified to make it more generic: https://github.com/conda-forge/xgboost-feedstock/blob/master/recipe/0001-conda-Unbundle-libxgboost.-dll-dylib-so.patch
Xref: https://github.com/conda-forge/xgboost-feedstock/pull/47

It would be very useful for distribution purpose.  I rewrote the Python setup.py script recently, would you like to take a look and see how can we find the library dynamically?

There are specializations in R package to make it comply to CRAN policy, for examples stdout/stderr is forbidden, some math functions are replaced.  Particularly CMake is no usable.

For Python package this is done in: https://github.com/dmlc/xgboost/pull/6362

Awesome! Thank you Jiaming 😄

Thanks!

Handling the last bit of the associated conda-forge patch in PR: https://github.com/dmlc/xgboost/pull/10643


APIView: updates needed for rename of Cadl to TypeSpec

I created an APIView with the language property set to TypeSpec to see what impact this would have on the web side:

[ ] Language dropdown needs TypeSpec added and should remove "Cadl".
[ ] Create review language dropdown. Replace Cadl with TypeSpec. Update terminology.
[ ] Add Revision. Replace Cadl with TypeSpec.

For all above cases, APIView should internally recognize that any existing APIVIew's labeled Cadl should be treated as TypeSpec.
I also tried adding a TypeSpec revision on top of a Cadl revision and this worked mostly fine. The only issue is that adding a rev on top of the TypeSpec one would not give you a language dropdown, but that would presumably be fixed when the above are addressed.

A few questions about how far the rename should go, specifically as relates to the LanguageService
will the file extensions also be renamed i.e .cadl to .typeSpec and will this need to be backward compatible with the existing name.  //cc @praveenkuttappan @maririos

The *.cadl file extension is renamed to *.tsp
Do we use that anywhere?

The *.cadl file extension is renamed to *.tsp
Do we use that anywhere?

https://github.com/Azure/azure-sdk-tools/blob/7c10ce5ef4641263b81e775aa181d82750a83da1/src/dotnet/APIView/APIViewWeb/Languages/CadlLanguageService.cs#L19

Ah, well, to whatever extent that is used, APIView probably continue to recognize Cadl as TypeSpec and *.cadl as *.tsp.


announce version with addon: mariadb

sorry, i'm a bit lost of writing ruby test cases.

No worries. Addons don't get their #announce invoked, so we'll have to figure something out if we are to do something about it. It's getting late here now, but I'll take a look at this some time next week.

Can we just announce the version installed when we install it?

I added a command to announce this at the end of the addon invocation. See @940fd45.

@940fd45 is incorrect as it announces the mysql client version not the server version.


Can no longer run under WSL

Under 1.53.3, OmniSharp-roslyn can no longer load solutions containing more than a single project under WSL. I have bisected this to c88ed904 introduced in #1820
The example solution I've been testing on is this repo, building in Visual Studio.
cd /mnt/c/code/external/omnisharp-roslyn
bin/Debug/OmniSharp.Stdio.Driver/net472/OmniSharp.exe -v > output

Log from commit c88ed904: https://pastebin.com/raw/GnfrtYrn
Log from previous commit 319d9cbf: https://pastebin.com/raw/dD5RgMsi
The important difference is that in c88ed904, the server only loads a single project and then stops.

I forgot to mention an extremely important detail - running bin/Debug/OmniSharp.Stdio.Driver/net472/OmniSharp.exe -v by itself results in a full server output - all projects are loaded as expected. However, when stdout is written to a file (> outfile) or when the server is started as a stdio job with outputs captured then the above failure occurs.

thanks for tracking down the commit.
To be honest, this is something we never paid any attention to support - loading Windows paths from WSL? I didn't even realize it's possible 😀
anyway let's cc: @JoeRobich who introduced this change for telemetry purposes in VS Code

The error occurs the 2nd time this line is reached: src/OmniSharp.Host/Services/DotNetCliService.cs#L140 - the server hangs, waiting for the dotnet --info process to finish (the first dotnet --info completes normally).
The changed behaviour is due to src/OmniSharp.MSBuild/ProjectFile/ProjectFileInfo.cs#L119.

Running this external process is clearly a WSL issue, and I've run into it before - we can't run tests via OmniSharp-roslyn in OmniSharp-vim either, as they are also run as external dotnet ... commands. And adding workarounds for running the Windows server from the WSL filesystem may not be desirable (although I personally do most of my work in this environment and I certainly hope to continue using OmniSharp-roslyn in this way).
However, in this case the change is purely for VSCode telemetry, which we make no use of in OmniSharp-vim (or presumably other clients), and in fact it slows down initialisation of OmniSharp-roslyn. I have added crude profiling (adding DateTime.Now around this block ) and started the server a few times - first at c88ed90 and then with this change to src/OmniSharp.MSBuild/ProjectFile/ProjectFileInfo.cs#L119:
// var dotNetInfo = dotNetCli.GetInfo(Path.GetDirectoryName(projectInstance.FullPath));
var dotNetInfo = DotNetInfo.Empty;

Before the change it takes 20-21 seconds for this block to load the projects of OmniSharp.sln. After the change it takes 15-16 seconds. This is significant, for extra information that we are not interested in.
Is it feasible to add a command line flag to disable this lookup? Perhaps it makes even more sense to make it an opt-in feature rather than opt-out, as only VSCode is interested in these results?

yep that is a good suggestion, in fact we can feature flag the entire changeset from that PR


Added CSS variables support

I added option of converting color to CSS variable. With this functionality #123abc can become
 --persian-blue: #123abc;
I figured that with this change the version of extension should be bumped, so both Release Notes in README.md and version in package.json reflects that.
Note: Path to .gif file points to master, so it's not displayed correctly in README.md of my branch. It will work just fine after merging.

I just merged your feature branch into master and published the new version of the extension to the VS Code market place.
Thanks for the contribution :)


PP-6147: Decrypt field level encryption fields

WHAT
Two things:

Adds some decryption middleware which, when enabled, will decrypt any card
data in the request.
Amends server side validation so that, when enabled, card data will not be
populated in the response

The commit messages have some more details.
HOW
The most important thing to check is that this doesn't break the existing
infrastructure before we merge it - the end-to-end tests should be more than
enough to cover that.
PP-6147 won't be done until we've tested this in the new PaaS environment,
which requires some additional changes in pay-omnibus. We could wait for that
testing to happen before merging this if we wanted.

@mrlumbu mentioned that I got one of the test names backwards - I think I've fixed that in f0dbfeeb

We've run the end-to-end tests against this PR, tested it manually intest (to check that the AJAX call works with x-www-form-url-encoded), and tested it manually in the paas environment with Field Level Encryption.
We're pretty confident the code works now, so as long as people are happy review wise this is good to go.


Dotfiles Support

Is your feature request related to a problem? Please describe.
Daytona doesn't have an option to import users configuration into workspaces automatically. E.g. neovim/vim config files.
Describe the solution you'd like
Dotfiles, that are set by the user and automatically installed into all projects, would solve this and allow the user to customize their experience while developing.

I can't use this tool because of vim environment is not available as an IDE option. And I don't like to install vscode just for using this tool.

I can't use this tool because of vim environment is not available as an IDE option. And I don't like to install vscode just for using this tool.

@bububa no need to install VS Code. You can run daytona ide and set Terminal SSH as the default IDE. This will connect your terminal to created workspaces which allows you to easily run vim.

@Tpuljak does this option sync my local nvim setting through ssh?

@Tpuljak does this option sync my local nvim setting through ssh?

It doesn't automatically. From what I can see, you could sync your config to the remote host using the Transfer.nvim plugin (https://www.reddit.com/r/neovim/comments/17n1mkn/neovim_plugin_for_synchronization_with_remote/).
We can explore if Daytona could do this for the user automatically as well in a separate issue.


Use system API to get default font name

Use system API to get default font name instead of setting a constant value.
These are the default font name for each culture:

Language
Default font name

日语（Japanese）
Meiryo

韩语（Korean）
Malgun Gothic

繁体中文（Chinese (Traditional)）
Microsoft JhengHei

简体中文（Chinese (Simplified)）
Microsoft YaHei

希伯来语（Hebrew）
Gisha

泰语（Thai）
Leelawadee

See my blog for more details:

Windows 系统的默认字体是什么？应用的默认字体是什么？

It's very strange that the AvaloniaUI doesn't provide a way to get the default font name for each culture. Maybe I could try a PR for that.

It does NOT mean to get the system's default font, but the default font prefered by this app. For example:

Has this PR #37

Without this PR

It's better when using JetBrains Mono with Microsoft YaHei UI as fallback font.

I've already escalated this issue to Microsoft for further attention. You can reference the reported issue here:

https://github.com/dotnet/wpf/issues/6164

It appears the root of the problem stems from using a Chinese application on an OS where English is the default language setting. Specifically, when attempting to render a Chinese character using the Segoe UI font, the anomaly you're observing occurs.

问题源于在英文作为默认语言设置的操作系统上使用中文应用程序。具体来说，尝试使用 Segoe UI 字体渲染中文字符时，会出现您所观察到的异常现象。
这个问题还挺难处理的。因为如果判断应用当前的系统语言，会得到英语，然而英语下的默认字体却不是微软雅黑。

After setting the system display language to English, I confirmed through breakpoint verification that the Segoe UI font was indeed applied. The rendering effect is as demonstrated in the image below. It's also worth noting that the Visual Studio interface has adopted the same font rendering effect.

I prefered to use Microsoft YaHei UI as the default font for this app on Windows platforms and ignore the system settings.
Users can change this from Preferences menu if they do NOT like the default one.

I agree.