Design routes for API Controllers.

@PeterETschaekofske is working on the API controllers. To make the implementation easier, we should outline what routes go to what controllers.

Basic crud operations should all be under their own controllers (Everything common to IRepository<T, TKey>:

GetAsync(...): GET api/v1/<type>/{id}

example: ICourseRepository.GetAsync(...) maps to GET api/v1/course/{id}

AddAsync(...): POST api/v1/<type>
EditAsync(...): PUT api/v1/<type>/{id}
DeleteAsync(...): DELETE api/v1/<type>/{id}

For routes of the form api/v1/<typeA>/{id}/<typeB>, we either need to implement these on the controller for typeA or add a composite controller. I would recommend the second option as it's the cleanest implementation. For example:
ICampusRepository.GetCampusesForInstitutionAsync(...)

Would be implemented in a CampusInstitutionController with an action of
GET api/v1/institution/{id}/campuses

ICampusRepository extra methods:

GetCampusesForInstitutionAsync(...): GET api/v1/institution/{id}/campuses
AssociateCampusWithInstitutionAsync(...): PUT api/v1/institution/{id}/campuses/{campusId}
DissassociateCampusWithInstitutionAsync(...): DELETE api/v1/institution/{id}/campuses/{campusId}

ICourseRepository extra methods:
Institution Courses

GetCourseseForInstitutionAsync(...): GET api/v1/institution/{id}/courses

Student Courses

GetCompletedCoursesForStudentAsync(...): GET api/v1/student/{id}/courses/completed
MarkCourseAsCompletedForStudentAsync(...): POST api/v1/student/{id}/courses/completed/{courseId}
MarkCourseAsUncompletedForStudentAsync(...): DELETE api/v1/student/{id}/courses/completed/{courseId}
GetInProgressCoursesForStudentAsync(...): GET api/v1/student/{id}/courses/in-progress
MarkCourseInProgressForStudentAsync(...): POST api/v1/student/{id}/courses/in-progress/{courseId}
MarkCourseNotInProgressForStudentAsync(...): DELETE api/v1/student/{id}/courses/in-progress/{courseId}

Offerings

AddOfferingAsync(...): POST api/v1/course/{id}/offering/{offeringId}
RemoveOfferingAsync(...): DELETE api/v1/course/{id}/offering/{offeringId}

Requirements

AddSatisfiedRequirementAsync(...): POST api/v1/course/{id}/requirement/satisfies/{reqId}
RemoveSatisfiedRequirementAsync(...): DELETE api/v1/course/{id}/requirement/satisfies/{reqId}
AddPrerequisiteAsync(...): POST api/v1/course/{id}/requirement/prereq/{reqId}
RemovePrerequisiteAsync(...): DELETE api/v1/course/{id}/requirement/prereq/{reqId}
AddConcurrentPrerequisiteAsync(...): POST api/v1/course/{id}/requirement/prereq/concurrent/{reqId}
RemoveConcurrentPrerequisiteAsync(...): DELETE api/v1/course/{id}/requirement/prereq/concurrent/{reqId}

IInstitutionRepository extra methods:
Campuses

GetInstitutionsOnCampusAsync(...): GET api/v1/campus/{id}/institutions

Students

GetInstitutionsForStudentAsync(...): GET api/v1/student/{id}/institutions
EnrollStudentAsync(...): POST api/v1/student/{id}/institutions/{institutionId}
UnenrollStudentAsync(...): DELETE api/v1/student/{id}/institutions/{institutionId}

IMeetingRepository extra methods:
Offerings

GetMettingsForOfferingAsync(...): This one I'm not sure about. I feel like it could be either:

GET api/v1/course/{id}/offering/{offeringId}/meeting
GET api/v1/offering/{id}/meeting

It depends on where we want to scope the offering resource. I think it makes the most sense that an offering would always be associated with a course, thus we should use the first form. We should also modify the Offering model to include a Course and drop the link table. Thoughts @PeterETschaekofske @nchurchill ?

IProgramRepository extra methods:
Institution

GetProgramsOfferedByInstitutionAsync(...): GET api/v1/institution/{id}/programs

Student

GetProgramsForStudentAsync(...): GET api/v1/student/{id}/programs

Requirements

AddRequirementAsync(...): POST api/v1/program/{id}/requirement
RemoveRequirementAsync(...): DELETE api/v1/program/{id}/requirement/{reqId}

IRequirementRepository extra methods:
Course

GetRequirementsCourseSatisfiesAsync(...): GET api/v1/course/{id}/requirement/satisfies
GetPrereqsForCourseAsync(...): GET api/v1/course/{id}/requirement/prereq
GetConcurrentPrereqsAsync(...): GET api/v1/course/{id}/requirement/prereq/concurrent

Program

GetRequirementsForProgramAsync(...): GET api/v1/program/{id}/requirement

IStudentRepository extra methods
Program

RegisterForProgramAsync(...): POST api/v1/student/{id}/programs/{programId}
UnregisterForProgramAsync(...): DELETE api/v1/student/{id}/programs/{programId}


Add custom titlebar to default Cs and Cpp WinUI template

This change adds custom titlebnar to Cs and Cpp template. As a result, any hello world WinUI app created via the template has custom titlebar already applied to it. This provides a better experience for developers as default option takes care of styling of the window.  It works better with overall theming.
For example :
current hello world app in dark theme (notice the mismatch between app content and OS provided titlebar)

this is with custom titlebar applied (theme consistency extends till the titlebar area too)

This is a better experience right out of the box. Similar default is followed by MAUI and Template Studio projects.

just item templates or project templates too?

just item templates or project templates too?

oops. fixed it. now project templates and item templates both have it.

/azp run

/azp run


feat: Improve Symantec (broadcom) DLP

New docs were located allowing for a msg format based parser option in addition to the existing vps option.

:tada: This PR is included in version 2.25.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Split terminal should remain same width

Issue Type: Bug
Currently, toggle sidebar or using a tool like https://www.spectacleapp.com/ to resize VS Code will both make terminal have unequal width.
VS Code version: Code - Insiders 1.21.0-insider (a903bd38fbe9006c076d218ff69fe1ee0160f815, 2018-03-06T10:59:55.398Z)
OS version: Darwin x64 17.3.0

Thumbs up for this. Terminals should have same relative width when you resize the window. If I have 3 terminals and resize the window, they should remain 33% width each. It would be acceptable (I think) if manual terminal width change should cancel this behavior until you get back down to 1 terminal. That is, if I have 2 terminals and manually resize them so one is 25% of the width, I don't expect vs code to figure out what that should mean if I resize the window. But if I close one, and then split again, it should spit to 50/50 and keep the relative % width if I resize.

I'm probably being picky but adding on to @theigor's post I think the manual resize scenario should be considered.

I'll add another tidbit - this is especially annoying when I drag vscode from one monitor to another. Not only does it bungle all my terminals, but it seems that some output is word wrapped but some isn't so the whole thing becomes a mess and even when I resize it back, not everything that was word wrapped restores back. I end up with things like this:

@theigor if you're on mac/Linux this issue should fix the problem https://github.com/Microsoft/vscode/issues/23688, planning on working on that soon. It should work on Windows eventually but needs some changes inside Windows.

Sounds good. I'm seeing this on Windows right now.


How to switch configs based on architecture/machine?

I'm switching between three machines right now, macOS, Debian, and NixOS 18.03. How do you suggest I write my home.nix such that I can handle each system?
Right now I'm just maintaining a darwin branch for stuff that doesn't work on macOS. This seems to work for now but I'd rather have it automatically know which packages aren't compatible.

Typically this would be done by having separate "top-level" files for your different systems. I usually name these based on the hostname (and the username if I have multiple users on the system) like atlantis-rycee.nix, for example. Then for each user you can set up a symbolic link from ~/.config/nixpkgs/home.nix to the appropriate top level file.
So, in your case you might create three files

nixos.nix
debian.nix
darwin.nix

each of these would follow the format
{ ... }:

{
  imports = [ ./common.nix ];

  # Various options that are specific for this machine/user.
}

where the common.nix file contains configuration shared across the three systems. Of course, instead of just a single common.nix file you can have multiple ones, even one per program or service.
You can get some inspiration from the Post your home-manager home.nix file! Reddit thread.

@rycee

each of these would follow the format
{ ... }:

{
  imports = [ ./common.nix ];

  # Various options that are specific for this machine/user.
}

where the common.nix file contains configuration shared across the three systems. Of course, instead of just a single common.nix file you can have multiple ones, even one per program or service.

Will the options set in the common file be merged recursively with the options set in the host-specific file? Say, I want to have some default email for git but I want to use my work email when I am on my work machine? I guess the question is how the "imports" functionality implemented. My search of Nix documentation produced the recursiveUpdate function which seems to be designed for this use case but it looks like "imports" does not use it.


Reduce TTL for existing data

Hello BigGraphite team,
We would like to reduce the TTL for metrics. The original retention is 300s:30d,900s:2y and we would like to reduce it to 300s:30d,900s:1y.
Is this possible or would it fall into the same case as https://github.com/criteo/biggraphite/issues/575?
Thank you

It's not great but you can trick biggraphite. The TTLs are handled by Cassandra, so you can modify the default_time_to_live of the table in question, the retention will still officially be 2y but in practice data will be discarded earlier

@zerosoul13 did it work?

@geobeau Thank you for the follow-up. Our team didn't go through with the approach. It sounds safe, but I didn't want to risk any impact on the dataset.

How much data do you have? Another solution is to:

generate the new table for 1y
copy data from 2y to 1y (either via spark, sstableloader or a custom script depending on the size)
replace resolution in your metric


@font-face still doesn't work

Hello guys,
I am trying to use in my app new font with using the @font-face, but the app still cannot load them.
I use following setup:
application.rb
config.assets.paths << "#{Rails.root}/app/assets/fonts"
config.assets.precompile += %w(*.svg *.eot *.ttf *.woff)
app.css.scss
@font-face {
font-family: 'my_font';
src: font-url('Androgyne_TB.eot');
src: font-url('Androgyne_TB.eot?#iefix') format('embedded-opentype'),
font-url('Androgyne_TB.woff') format('woff'),
font-url('Androgyne_TB.ttf')  format('truetype'),
font-url('Androgyne_TB.svg#AndrogyneMedium') format('svg');
}
The fonts are stored in app/assets/fonts.
When I run the app and take a look at the app.css.scss, there is printed out this path to the fonts: src: url(/assets/Androgyne_TB.eot); etc. and when I put this URL into browser, then is this font offered my for download -> which looks the path is okay.
But the main problem - the font is still not displayed in my app.
Didn't has anyone the same problem and could help me with?
Thanks
(and I am sorry if I put this issue into the bad issue-channel)

Old ticket - but I am having the same issue.
My work-around here is the following:
@font-face {
    font-family: 'San Francisco Display';
    src: url(font-path('san-francisco/sanfranciscodisplay-bold-webfont.eot'));
    src: url(font-path('san-francisco/sanfranciscodisplay-bold-webfont.eot?#iefix')) format('embedded-opentype'),
         url(font-path('san-francisco/sanfranciscodisplay-bold-webfont.woff2')) format('woff2'),
         url(font-path('san-francisco/sanfranciscodisplay-bold-webfont.woff')) format('woff'),
         url(font-path('san-francisco/sanfranciscodisplay-bold-webfont.ttf')) format('truetype'),
         url(font-path('san-francisco/sanfranciscodisplay-bold-webfont.svg#San Francisco Display bold')) format('svg');
    font-weight: 700;
    font-style: normal;
}

It seems you need to use ' or " around the urls of your font files. Else it will not work.
So this final CSS is valid:
@font-face {
  font-family: 'San Francisco Display';
  src: url("/assets/san-francisco/sanfranciscodisplay-semibold-webfont.eot");
  src: url("/assets/san-francisco/sanfranciscodisplay-semibold-webfont.eot?#iefix") format("embedded-opentype"), url("/assets/san-francisco/sanfranciscodisplay-semibold-webfont.woff2") format("woff2"), url("/assets/san-francisco/sanfranciscodisplay-semibold-webfont.woff") format("woff"), url("/assets/san-francisco/sanfranciscodisplay-semibold-webfont.ttf") format("truetype"), url("/assets/san-francisco/sanfranciscodisplay-semibold-webfont.svg#San Francisco Display semibold") format("svg");
  font-weight: 600;
  font-style: normal;
}

Whereas this CSS here is invalid:
@font-face {
  font-family: 'San Francisco Display';
  src: url(/assets/san-francisco/sanfranciscodisplay-semibold-webfont.eot);
  src: url(/assets/san-francisco/sanfranciscodisplay-semibold-webfont.eot?#iefix) format("embedded-opentype"), url(/assets/san-francisco/sanfranciscodisplay-semibold-webfont.woff2) format("woff2"), url(/assets/san-francisco/sanfranciscodisplay-semibold-webfont.woff) format("woff"), url(/assets/san-francisco/sanfranciscodisplay-semibold-webfont.ttf) format("truetype"), url(/assets/san-francisco/sanfranciscodisplay-semibold-webfont.svg#San Francisco Display semibold) format("svg");
  font-weight: 600;
  font-style: normal;
}

I also validated this here:
https://jigsaw.w3.org/css-validator/validator
If real issue - please let me know. I will create a pull request.

I think this may still be a bug. I am pretty sure it is being caused by your dropping of .css.scss. As soon as I did this, font-url doesn't work in production. font-url is widely accepted as the way to load fonts in the asset pipeline across stackoverflow. Spent a good deal of time tracking this down.
I would revisit this if you guys insist on dropping the css.scss - I'm almost positive that broke font-url.
Anyway, the convention above does work as a workaround for now, so thank you @hendricius :
url(font-path( ))
Got the css.scss warnings after using @import instead if //= requires. //= requires was giving me problems all the time with compilation times due to caching bugs (sprockets?)


Line thickness flickering while moving the mouse

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
See attached video
https://user-images.githubusercontent.com/17641229/102982010-23f23f00-450a-11eb-9909-8d98263196e5.mp4
Expected behavior
No flickering
Versions:

Adapter version: 0.4.9
JS-Controller version:
Node version:
Operating system:

I suppose that is a highlighting function to indicate which line is pointed to with the mouse pointer.

Except that I don't highlight any lines as you can see in the video

As soon as the vertical indicator hovers a datapoint on any line it changes to bold and shows it's value in the tool tip. I might be wrong but that would explain it....

 The previous versions didn't do that and still showed the tool tip.

Yes, I agree.
Infect I was even more satisfied with hovering in FLOT where you could track just one line and got only it's values instead of getting displayed the value of any datapoints you just accross all lines.

Should gone now.

👍🏻


Input Icon

is there is a way to provide an icon for the input something like <InputAdornment /> in material UI input

Hi, yeah it would be really nice feature, so I will add it in the nearest release (alpha 12)

Hi, about your proposal. It would work for any version of material-ui-picker, because material-ui TextField has an ability to pass the icon to input
Please refer
<DatePicker
   InputProps={{
      endAdornment: (
        <InputAdornment position="end">
           <IconButton>  add_alarm  </IconButton>
        </InputAdornment>
     )
  }}
/>

Also I`ve add this example to the demo


[Feature] add support to sync tags

When i sync my fork with upstream repos, i also want to sync(create/update) tags.
Reasons:

Release tags can be used for lot of automation scenarios, like sending notifications on new release, etc.
give me holistic view of source code and its history.

If this feature request makes sense, i can contribute this feature.

Thanks for bringing it up. I know people have requested this feature in #95 but this is not a common use case. It only makes sense for merge method hardreset. I don't want to pack too much complexity or workload to pull atm.
I'm all ears if you have a way of doing it cleanly and doesn't add too much complexity/workload. 😃
The current alternative solution can be viewed at https://github.com/wei/pull/issues/95#issuecomment-617277025


Calibrating a Non-specific Digest Finds No Peptides

Running the Calibrate task with a non-specific digest failed to match any peptides, even after expanding its tolerance several times. I have insufficient information from the log to determine if there were matches but they failed to pass the FDR threshold. The search also runs unexpectedly quickly, but I do not know if the Calibrate task takes some shortcuts.
I know the sample has around 3000 good spectra and ~1250 reasonable peptide IDs from searching it with other tools.

Thanks for the report - @zrolfs can you comment on this?

Hi mobiusklein,
It sounds like the maximum number of missed cleavages wasn't changed to accomodate the non-specific digestion. For these digestions, each residue can be cleaved, so each if the max missed cleavage parameter is set to 2 (which is the default for fully-specific digestions), then the search will only include 3-mers and will run very fast. Let me know if this resolves your issue.

@zrolfs  I thought there was some "reasonable" default value set here for the max missed cleavages upon selecting the non-specific search. If you select non-specific search is the max missed cleavages still set at 2?

@rmillikin The functionality described is implemented in the search task, but not Calibration, GPTMD, or XL.

sounds good. maybe @bintiibrahim can change this with your guidance


Positioning Camera's is very difficult

Last week, it took me multiple hours to Exactly setup the Camera angle for a Model.
It's Try Reload Error.
Is there a way, that the Actual Camera Angle/all Useful params are dropped in the Console.
So it's possible to set the angle exactly as you want.
Grab the Vector / LookAtVector Zoom / Scale etc from the Console

OK. I'll add a special method to display this info on demand.


Unexpected end of JSON input while parsing near '...um-stream":"^1.0.2","'

...
ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-helper-function-name-621030ed/.npmignore'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-helper-explode-assignable-expression-927e0786/README.md'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-helper-call-delegate-d8bdcff5/README.md'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-template-002033d9/README.md'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-helper-bindify-decorators-42dc7978/README.md'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-plugin-transform-es2015-function-name-c21b36a2/README.md'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/babel-helper-function-name-621030ed/README.md'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/uglify-es-f00cb3af/lib/minify.js'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/uglify-es-f00cb3af/lib/mozilla-ast.js'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/uglify-es-f00cb3af/lib/output.js'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/webpack-cli-17cde3b2/.nyc_output/835b0d393ceec036662e3529b0272122.json'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/source-map-2a249e9a/dist/source-map.js'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/webpack-cli-17cde3b2/.nyc_output/880833224714cb8858ccb77724979101.json'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/webpack-cli-17cde3b2/.nyc_output/8bbb03eaf65ca83c7e494a62d105f8fc.json'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/webpack-cli-17cde3b2/.nyc_output/8f27269b188e61a59bbf5827de818c30.json'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/webpack-cli-17cde3b2/.nyc_output/9241e51b5c2cccf5e78e2246c0243746.json'
npm WARN tar ENOENT: no such file or directory, open '.../cezerin/node_modules/.staging/unicode-575fabd0/category/Nd.js'
npm ERR! Unexpected end of JSON input while parsing near '...um-stream":"^1.0.2","'
npm ERR!
From logs, I suppose, you run in parent or child folder.

Dear @sonufrienko
Yes, I run in Cezerin folder, I think this is because of internet restrictions in our country, Iran, I'll try with proxy to check.
If you have any idea please help, thanks.

@mkouchi

did node_modules folder create? Is it contains files or folders?
did dist folder create? Is it contains files or folders?

Hmm, restricting access to npmjs.com sounds unbelievable.

@sonufrienko
Restricting because of US sanctions, not internal filtering.
I fixed that by npm cache clean and runing again.
Thanks a lot.


Requests can hang indefinitely when using HTTP/2

Hi, I'm not sure if this has been reported before but I'm guessing it's related to #1276. I've set up a minimal reproduction here https://github.com/dlesl/reqwest_h2_hang_repro.
It's using an nginx server, serving http2 with TLS. A single Client is shared by 50 async workers making requests in a loop. Occasionally, this error is reported: source: hyper::Error(Http2, Error { kind: Proto(NO_ERROR) }).
Hitting Ctrl-C should gracefully shut down the workers, but after some time (~10-20 sec) this is no longer the case, and it just hangs, even after killing the nginx server. Setting a timeout causes the stuck requests to timeout eventually.

Occasionally, this error is reported: source: hyper::Error(Http2, Error { kind: Proto(NO_ERROR) }).

Does this happen randomly? Or after a certain amount of time?
In general, when do requests start to hang? Is it usually after receiving that error? Do you think it'd be possible to grab logs? You could do so with this:
[dependencies]
env_logger = "0.9"
tracing = { version = "0.1", features = ["log"] }

At the top of your main function:
env_logger::init();

And then set this environment variable:
RUST_LOG=reqwest,hyper,h2

I did a bit of "printf debugging" by adding trace statements everywhere and it looks like the requests that hang always start by checking out an existing connection. They get as far as here and never proceed. I added tracing::Span to Envelope so I could correlate what is happen on the connection's side, and found that the request never gets received here. However, perhaps interestingly, the Envelope is not dropped either. If I set a timeout, then the Envelope is dropped once the timeout is reached. So it somehow gets stuck waiting in a queue that never gets polled?

It's likely sitting in the channel waiting for the h2 connection to be ready, and the bug is in that library when a remote tries to shutdown a connection.


yarn audit vulnerabilities* fixed

Added
"resolutions": {
"glob-parent": "5.1.2",
"trim": "0.0.3"
},
Selective dependency resolutions, to address vulnerabilities found with yarn audit.

Codecov Report

Merging #30 (f9b88df) into main (9bc9836) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   92.00%   92.00%
=======================================
  Files           3        3
  Lines          50       50
  Branches       16       16
=======================================
  Hits           46       46
  Misses          4        4

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 9bc9836...f9b88df. Read the comment docs.


error when run xdpfw

i having issue when ran "sudo xdpfw" , error :
497: (71) r1 = *(u8 *)(r0 +72)
BPF program is too large. Processed 1000001 insn
processed 1000001 insns (limit 1000000) max_states_per_insn 213 total_states 32198 peak_states 4041 mark_read 324
libbpf: -- END LOG --
libbpf: failed to load program 'xdp_prog'
libbpf: failed to load object '/etc/xdpfw/xdpfw_kern.o'
Could not load XDP BPF program :: Argument list too long.
Error loading eBPF object file. File name => /etc/xdpfw/xdpfw_kern.o.
and i using debian 6.1.0-22-amd64 . i tried "make" again, but still error. help me , thank so much !

Hey!
Can you try decreasing the MAX_FILTERS constant here from 80 to something like 40, recompile, and try again?

thank so much. resolved

No problem and I'm glad that resolved the issue! I will be closing this issue for now.


Hl 1306 admin changes

Description :sparkles:
Some adjustments to make the admin panel more convenient when testing application batches and AHJO-integration.
Remove ssn from the employee page as it's not really needed there.
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:

Additional notes :spiral_notepad:

API branch is deployed to platta: https://kesaseteli-pr3048.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

API branch is deployed to platta: https://tet-pr3048.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3048.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr3048.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr3048.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tet-admin-ui-pr3048.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-pr3048.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe employer result is failed for https://kesaseteli-employer-pr3048.dev.hel.ninja :crying_cat_face::anger::boom::boom:

YOUTH branch is deployed to platta: https://tet-youth-ui-pr3048.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tet-youth-ui-pr3048.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr3048.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

API branch is deployed to platta: https://tet-pr3048.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr3048.dev.hel.ninja :rocket::rocket::rocket:

ADMIN branch is deployed to platta: https://tet-admin-ui-pr3048.dev.hel.ninja :rocket::rocket::rocket:

API branch is deployed to platta: https://helsinkilisa-pr3048.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr3048.dev.hel.ninja :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3048.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://tet-admin-ui-pr3048.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-handler-pr3048.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-pr3048.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe employer result is failed for https://kesaseteli-employer-pr3048.dev.hel.ninja :crying_cat_face::anger::boom::boom:

YOUTH branch is deployed to platta: https://tet-youth-ui-pr3048.dev.hel.ninja :rocket::rocket::rocket:


Ground at the Wintertodt camp ground has no texture

Describe the bug
When exiting Wintertodt cave the group surrounded the Wintertodt camp has no texture, inside the mini-game looks as intended.
To Reproduce

Enter Wintertodt mini-game
Exit back through the Doors of Dinh

Expected behavior
The ground to have texture
Screenshots

Environment (please complete the following information):

OS: Windows 10
RuneLite version: v1.7.26

@tpolito  i've been to wt recently with HD plugin enabled and i did not have this issue? can you please check again and close issue if fixed?


Improve Errors after breaking changes to DB

In beta we sometimes make breaking changes to the database. We should improve the user feedback when this happens

For now we can ignore this, because we won't be making any more breaking changes. Instead the DB will be migrated to a new format after some updates


Update profile information, contact information, and volunteer type forms

ProfileInformationForm.tsx, ContactInformationForms.tsx, VolunteerTypeForm.tsx**

Added component state, on change event handler, and form submission handler

CreateUserPassForm.tsx

Fixed bug in handleChange() function

Signup.tsx

Updated file documentation
Changed "is_student":boolean property --> "volunteer_type": string. It should be easier to keep track of the 3 different types of users (general, student, healthcare provider) using this property instead compared to a boolean. (FOR ARI)
Added further conditions render the correct forms based on the signupData state

Nice job!


Issues/380 failing acceptance tests

:warning: DO NOT MERGE YET, still in progress :warning:
This PR is to resolve a number of spec/features/ spec failures.

Locally, all of the specs in features/specs/ are now passing. Waiting to see how they do on TravisCI.


Fix a typo

According to the context. The word should be "underspecified" meaning "insufficient".

NOTE: Please check the “Allow edits from maintainers” box below to allow
reviewers fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.

This change is

It's not clear to me that "underspec'd" means "underspecified" in this context.  "spec" is usually short for "specification," so although only slightly different, it could mean that the specification is currently insufficient.

@zhangxiaoyu-zidif Although I don't like the usage of "underspec'd," I've looked around and people do use that terminology. In any case, as a matter of policy, we shouldn't make statements in the documentation about the current state of something that is likely to change. Otherwise, we will accumulate a lot of outdated statements. Also, I think that sentence needs to be reworded slightly. My suggestion would be:
"HTTP server: The kubelet can also listen for HTTP requests and respond to a simple API call to submit a new manifest."

@chenopis Thank you for your help. You are welcome~

@zhangxiaoyu-zidif Thank you! =)


Redirects conflicts with RR7

Hello!
It looks like the way this package handles redirects is incompatible with the new version and produces server errors instead of throwing the response as the new changes expect.
I'm working on a project and we're migrating to RR7. The new type safety has made loader return data way more strict which is good but also requires us to throw any redirects from actions or loaders to fix typing issues.
Any assistance here would be greatly appreciated. Thanks!

Never mind I  missed this similar issue: https://github.com/forge42dev/remix-toast/issues/29


Setting Up Auth0

I just sucessfully setup auth0, I think this might help someone if he tries to do the same ,

follow all the steps given in the docs( https://data-tools-docs.ibi-transit.com/en/dev/dev/deployment/) with few changes
a. Use Auth0 instead of the IdP to do Single Sign On this option doesn't exist
b. It says to give http://localhost:9000 or whatever your application domain is, don't give localhost as your domain , for me it doesn't work, if you are starting with yarn start it is proxied to http://<IP_ADDRESS>:9966/ give that
c. make sure application type is machine to machine
d. in allow callback URL add http://<IP_ADDRESS>:9966/login too (so url with /login )
e. for auth token follow this and get the test token https://auth0.com/docs/api/management/v2/tokens

Hi @pranavpandey1998official, if you have suggestions for improving the documentation, we're open to pull requests to improve this.
Just a heads up, the IP address you've listed is likely just your localhost. If localhost is not working, there's probably some other issue preventing this. I would recommend not using the IP address for local development because often these are dynamically assigned (so next time you connect to your wifi network, you'll end up needing to change the IP address in the Auth0 settings).


error: RPC failed; result=22, HTTP code = 400

Getting a new issue when I try to run through the simple setup. I'm able to clone and run locally but can't deploy to Heroku. It may be something I'm doing wrong or misconfigured, but I've had success in the past deploying this template. Still love what you've done with this, just posting this in case others are having issues.
Setup (no errors):
$ git clone --depth=1 https://github.com/sahat/hackathon-starter.git myproject
$ cd myproject
$ git remote rm origin
$ npm install
$ heroku create
$ heroku addons:add mongolab
Then, pushing to heroku results in the following errors:
$git push heroku master
Counting objects: 177, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (169/169), done.
Writing objects: 100% (177/177), 902.75 KiB | 0 bytes/s, done.
Total 177 (delta 6), reused 177 (delta 6)
error: RPC failed; result=22, HTTP code = 400
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

Sorry, false alarm - had a RTFM issue

I am facing the same problem with the same project. Can you please share what solved your problem


Star Component MVP

Closes: https://github.com/near/near-discovery/issues/692
After talking with @thisisjoshford, we decided to just implement an MVP version of the requirements in the ticket. We'll build out the new developer profile page at a later time, so we added a Stars tab to the current profile page.
I created a generic component for actions like favoriting or starring that we can use going forward: SocialIndexActionButton. I copied most of the logic from mob.near's component and updated it a bit to make it more generic: https://near.org/near/widget/ComponentDetailsPage?src=mob.near/widget/N.StarButton
I also implemented a new notification type for the star action so you can be notified when someone stars your component (it won't notify you if you star your own component). While updating the notifications, I noticed there were some older notification components that we needed to flag as deprecated to avoid confusion.
I updated a few existing properties that were triggering errors in the console on the component details page too. EG: style={{ 'margin-top': 10px }} => style={{ marginTop: 10px }}. Also ended up applying some code formatting.

sweeeet! tysm @calebjacob ! :)


refactor: add MarketError

Add MarketError and convert all EthersErrors (ProviderError, SignerError) to MarketError
Note
Based on branch of PR #662.

Wouldn't it be better/safer to return a Result instead of converting to another exception?

@dryajov Well, that's an interesting yet difficult question to answer, as we've discussed in the past. Would you prefer that Result is returned here?
Given that there's only one place that catches MarketError as of right now, I don't necessarily see the benefit yet, however, if there were to be more call sites that would indeed need to catch a MarketError in the future, then I agree it could be beneficial.
If we changed to return a Result now, every existing call site would need to be updated, and likely, in most instances, the error returned in the Result would simply be logged. Otherwise, the function containing the call site would also need to return a Result, spreading it further up the stack. I'm certainly not opposed to the spread, but it would be a fair amount of change, so maybe it's a good idea if we (and others) agree on it before the work is undertaken?

If we changed to return a Result now, every existing call site would need to be updated, and likely, in most instances, the error returned in the Result would simply be logged. Otherwise, the function containing the call site would also need to return a Result, spreading it further up the stack. I'm certainly not opposed to the spread, but it would be a fair amount of change, so maybe it's a good idea if we (and others) agree on it before the work is undertaken?

Sure, if the change cascades too many other changes, it might not be worth it.
Overall I've since come around with the usage of result. I think the argument in are still valid (from both ends of the spectrum), but specifically to the ergonomics of result, things have improved (with ? and questionable). I believe that recent versions of chronos now also support ? in async code, which should make our async code a lot less verbose. All in all, results are easier to track and reason about.

Sure, if the change cascades too many other changes, it might not be worth it.

@dryajov I had a look at this, and I think for now, the changes this would introduce would be too many for the benefit. Perhaps we should create an issue and handle this another time?


Removed the stay connected text from footer #855

This pull request removes 'Stay Connected' text from the footer of the homepage. The text was no longer relevant and removing it simplifies the layout.

why it is not accepted?


kubernetes yaml for this docker image.

It would be good if the kubernetes yaml file for this image is documented somewhere. I am trying to use this with kubernetes and mount a persistent volume for the /home directory.

Below is the yaml
apiVersion: v1
kind: Pod
metadata:
  name: db2-angoca
  labels:
    tier: db2-database
spec:
  containers:
  - name: db2-angoca-container
    image: angoca/db2inst1:expc
    command: ["/bin/sh"]
    args: ["-c", "/home/db2inst1/sqllib/adm/db2start;while true; do echo hello; sleep 10;done"]
    ports:
      - containerPort: 50000
    securityContext:
      privileged: true


Mismatch between processing of typed data when signing and verifying

Describe the bug
The verification fails because of additional processing of typed data struct fields that is different between signTypedData and verifyTypedData
Link to Minimal Reproducible Example
No response
Steps To Reproduce
POC. The address should contain both uppercase and lowercase characters (according to standard formatting).
const signature = await signTypedData(rainbowkitConfig, {
  types,
  domain,
  primaryType: 'WalletData',
  message: {
    address,
  },
})

const verificationResult = await verifyTypedData(rainbowkitConfig, {
  address,
  types,
  signature,
  domain,
  primaryType: 'WalletData',
  message: {
    address,
  },
})

Running the above code, the signTypedData will pass, but the verification will fail.
However, if the address is modified only in the verifyTypedData call, it now passess. This implies some additional processing happening before signTypedData is called in viem.
What Wagmi package(s) are you using?
@wagmi/core
Wagmi Version
^2.5.20
Viem Version
^2.9.25
TypeScript Version
^5.3.3
Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Anything else?
Likely a Viem issue, due to the following code in viem/actions/wallet/signTypedData.ts:
const typedData = stringify(
  { domain: domain ?? {}, message, primaryType, types },
  (_, value) => (isHex(value) ? value.toLowerCase() : value),
)

Linking: https://github.com/wevm/viem/issues/2306

Better to track upstream on Viem


[FEATURE] Add ability to pass ClusterStateRequest object when requesting Cluster State

Is your feature request related to a problem?
Current SDK implementation of getting cluster state is implemented with defaults in the ExtensionRequest fetching the state from the ClusterService:
    TransportResponse handleExtensionRequest(ExtensionRequest extensionRequest) throws Exception {
        switch (extensionRequest.getRequestType()) {
            case REQUEST_EXTENSION_CLUSTER_STATE:
                return new ClusterStateResponse(clusterService.getClusterName(), clusterService.state(), false);

This does not work for use cases where the specific values to be returned are configured, such as in the AD Plugin:
        ClusterStateRequest clusterStateRequest = new ClusterStateRequest()
            .clear()
            .indices(AnomalyDetectionIndices.ALL_AD_RESULTS_INDEX_PATTERN)
            .metadata(true)
            .local(true)
            .indicesOptions(IndicesOptions.strictExpand());

        adminClient.cluster().state(clusterStateRequest, ActionListener.wrap(clusterStateResponse -> {

What solution would you like?
Either create a new transport action or modify the existing cluster state request action to take  a ClusterStateRequest object as a parameter.  The RestClusterStateAction class can probably called using the opensearch-java client with little overhead.
What alternatives have you considered?
Improving RestHighLevelClient to handle this case.  Not desirable as it's on a path for deprecation.
Do you have any additional context?
This is part of the AnomalyDetectionIndices component in the AD plugin.

The RestClusterStateAction class can probably called using the opensearch-java client with little overhead.

No, it can't.  Don't even try.  I did, and failed gloriously.
There's a TransportAction and the requests are writeable. This is trivial using transport.


[R] stringr binding for str_sub() silently mishandles negative start/stop values

Describe the bug, including details regarding any error messages, version, and platform.
I noticed some unusual behavior behavior when attempting to use negative start/end values (i.e. counting from the end of the string) when using str_sub() in  arrow. I've included a few examples below, contrasting how str_sub behaves with tibbles in R and arrow tables:
library(arrow)
library(tidyverse)
library(reprex)

str_tbl <- tibble(my_string = 'abcde')
str_tbl_a <- as_arrow_table(str_tbl)

# example #1: extract first through second-to-last characters from string

# works fine with a tibble
str_tbl %>% mutate(my_substring = str_sub(my_string, start = 1, end = -2))
#> # A tibble: 1 × 2
#>   my_string my_substring
#>   <chr>     <chr>
#> 1 abcde     abcd

# but with arrow: ruh-roh -- missing all characters
str_tbl_a %>%  mutate(my_substring = str_sub(my_string, start = 1, end = -2)) %>% collect()
#> # A tibble: 1 × 2
#>   my_string my_substring
#>   <chr>     <chr>
#> 1 abcde     ""

# example #2: extract third-to-last through second-to-last characters from string

# works fine with a tibble
str_tbl %>% mutate(my_substring = str_sub(my_string, start = -3, end = -2))
#> # A tibble: 1 × 2
#>   my_string my_substring
#>   <chr>     <chr>
#> 1 abcde     cd

# but with arrow: ruh-roh -- missing a character
str_tbl_a %>% mutate(my_substring = str_sub(my_string, -3, -2)) %>% collect()
#> # A tibble: 1 × 2
#>   my_string my_substring
#>   <chr>     <chr>
#> 1 abcde     c

# example #3: extract third-to-last through last characters from string

# works fine with a tibble
str_tbl %>% mutate(my_substring = str_sub(my_string, start = -3, end = -1))
#> # A tibble: 1 × 2
#>   my_string my_substring
#>   <chr>     <chr>
#> 1 abcde     cde

# but with arrow: bizarrely, this is also fine
str_tbl_a %>% mutate(my_substring = str_sub(my_string, -3, -1)) %>% collect()
#> # A tibble: 1 × 2
#>   my_string my_substring
#>   <chr>     <chr>
#> 1 abcde     cde

Created on 2024-09-05 with reprex v2.1.1
Note: the above reprex was created on an Ubuntu 22.04 system running R 4.4.1 and Arrow 16.1.0
Component(s)
R

Can confirm that I can replicate this with the dev version of Arrow too.
In our implementation of str_sub() there's a bit that looks like this:
    # An end value lower than a start value returns an empty string in
    # stringr::str_sub so set end to 0 here to match this behavior
    if (end < start) {
      end <- 0
    }

That might not be quite right, so we'll need to add some more tests and revisit the logic here.

@thisisnic totally agree that the snippet you point out is the culprit for the behavior in Example 1 above. I think the conditional logic could instead be changed to the following in order to avoid returning empty strings for negative values of end:
    if(end < start & end > 0) {
      end <- 0
      start <- 0
    }

Upon looking at the source code (sorry I hadn't taken the time to examine before), I think more problems in addition to this (but please correct me if I'm wrong!).
I believe the end argument in the C++ function utf8_slice_codeunits is exclusive, so won't include my_string[end] in the returned substring. For positive end values, this poses no issue, since in C++ is 0-based and R is 1-based, cancelling each other out. Note that for positive start values, the below snippet in the source code addresses this:
    # subtract 1 from `start` because C++ is 0-based and R is 1-based
    # str_sub treats a `start` value of 0 or 1 as the same thing so don't subtract 1 when `start` == 0
    # when `start` < 0, both str_sub and utf8_slice_codeunits count backwards from the end
    if (start > 0) {
      start <- start - 1L
    }

For negative start values, this isn't necessary, as noted in source comments above. But that leaves the issue of negative end values unsolved. This explains why in my Example 2 above arrow::str_sub fails to include my_string[-2] (i.e. only returns 'c' instead of the correct 'cd').
However, for just the [default] case when end == -1, this problem is incidentally fixed by this code:
    # In stringr::str_sub, an `end` value of -1 means the end of the string, so
    # set it to the maximum integer to match this behavior
    if (end == -1) {
      end <- .Machine$integer.max
    }

which explains why arrow::str_sub works fine (as in my Example 3 above) when end == -1, but not when end < -1 (which confused me at first).
I'm happy to create a MR that should fix this, with the warning that while I've been working with R for quite a while, I'm a total newb when it comes to the collaborative development side of things (@thisisnic thanks so much for your https://github.com/forwards/first-contributions tutorial!).

I'd love if you'd be happy to contribute a PR!  And don't worry, we're friendly around here - we don't expect everything t be perfect first time round (my PRs still aren't ;) ) and will help you through the process of become an arrow contributor!
Thanks for investigating this so thoroughly, and look forward to reviewing a PR! :D

OK, sounds good -- I'll write a PR for this!

Issue resolved by pull request 44141
https://github.com/apache/arrow/pull/44141


Empty protein_to_h5 function significance

Hi,
I've noticed there's this protein_to_h5 function and since I'm playing around with the code and considering adapting it to proteins, I was wondering why the function was left empty.
I believe any inputs could prove very valuable to me.
Many thanks!

Hi,
Thanks for your interest. I have tried some protein data (DESRES fast folding proteins) during development but the results were not good enough so I did not include them in the paper. The main challenges were limited data (different trajectories were sampled with different setups) and extremely long-time-scale folding events (only happens a handful of times over the ms-level trajectories).

Thanks for the timely answer!
Have you also tried with both corse-graining on and off? If so, what difference did it make?
Thanks a lot

I only tried CG with Calpha as CG-bead coordinates. The model can recover a decent contact map and folding/unfolding can be observed, but the time scale for the folding events is off.

Feel free to reopen if there are further questions.


boxShadow on TextInput alternates visible/hidden with each key typed on Android

Description
Very simple - when typing in a TextInput on Android, each alternate keypress seems to enable/disable the boxShadow style on the TextInput. This behaviour is not seen on iOS; there, the boxShadow stays visible as expected.
This affects Expo 52/React Native 0.76.
Steps to reproduce
Run the Snack in Android
React Native Version
0.76.3
Affected Platforms
Runtime - Android
Output of npx react-native info
info Fetching system and libraries information...
System:
  OS: Windows 11 10.0.22631
  CPU: (16) x64 Intel(R) Core(TM) i7-9800X CPU @ 3.80GHz
  Memory: 105.98 GB / 127.71 GB
Binaries:
  Node:
    version: 20.10.0
    path: C:\Program Files (x86)\Nodist\bin\node.EXE
  Yarn: Not Found
  npm:
    version: 10.2.3
    path: C:\Program Files (x86)\Nodist\bin\npm.EXE
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-242.23339.11.2421.12550806
  Visual Studio: Not Found
Languages:
  Java: 17.0.13
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.2
    wanted: latest
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.3
    wanted: 0.76.3
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs
No error - see the Snack.

Reproducer
https://snack.expo.dev/@albertsokol/android-boxshadow-bug-on-textinput
Screenshots and Videos
No response

@albertsokol I wasn't able to replicate it on the snack. Can you check?

@oddlyspaced hmm, really? It replicates for me in the snack on 2 separate devices. Are you definitely using the Android simulator, and set to Expo 52.0.0?

https://github.com/user-attachments/assets/a0079616-ac20-4d8f-806f-47cfcc0f500a

Thanks for the report! I will try to take a look at this soon. Seems likely something may be fussing around with the inputs background drawable.
Ad a temporary workaround, does it work if you wrap the input in a view with the shadow?

@NickGerleman Thanks for taking a look! Yeah, if the shadow is on a wrapping view and not on the TextInput itself, then typing in the TextInput does not affect the parent view shadow, it seems to work correctly.

This does not seem to repro for me, using RNTester playground in main branch build. Might have been fixed since 0.76? Worth retesting on 0.77 or nightly.
https://github.com/user-attachments/assets/41c50ce0-61bd-43fd-acde-df8f72c37e6c


Feat/pattern matching updated

Codecov Report

Merging #53 (e86870f) into master (6879684) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #53   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          214       216    +2
=========================================
+ Hits           214       216    +2

Impacted Files
Coverage Δ

result/result.py
100.00% <100.00%> (ø)


HTML source code not showing for index page

I'm submitting a...

[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

The source code is showing for all other pages except the index page on AWS. if we try to run it in the local system it's working fine

@darteam43 Can you provide more information about the packages being used and also the reproduction steps?


Fix RemoveListener bug

There seem to have a bad copy paste bug. I didn't personally encounter the bug but I noticed it in code and thought it should be fixed.

Looks good to me!

Thanks for the PR! :)


Parse Sano DTC format

Updates from Sano Genetics to parse Sano DTC format.

This looks great, thank you @apriha .


Resolve Missing Javadocs in App Configuration related modules

Please check the parent issue(#25635) for more information.

[x] azure-spring-cloud-starter-appconfiguration-config
[x] azure-spring-cloud-feature-management
[x] azure-spring-cloud-feature-management-web
[x] azure-spring-cloud-appconfiguration-config
[x] azure-spring-cloud-appconfiguration-config-web
[ ] spring-cloud-azure-appconfiguration-config
[ ] spring-cloud-azure-appconfiguration-config-web
[ ] spring-cloud-azure-feature-management
[ ] spring-cloud-azure-feature-management-web
[ ] spring-cloud-starter-azure-appconfiguration-config

Hi, @mrm9084 , could you please help to resolve this issue?

azure-spring-cloud-* has been updated.
spring-cloud-azure-* isn't active and around just in case of an emergency bug fix is needed in the old repos. Also, it will be overridden by what is in azure-spring-cloud-* once updated to 4.0. So, it will not be updated.

@chenrujun should this be considered complete?

@mrm9084 .

should this be considered complete?

OK.
Closing this issue now.


Place and Route for telescopic ota is not on grid and visually has design rule errors

@Lastdayends @arvuce22 @kkunal1408
I was looking through the result of the full flow on the telescopic_ota and I see a few things that we need to fix:

When we make a connection from new metal3 down to our metal2 pins we seem to be adding off-grid metal2 (not quite creating a short but definitely a design rule violation) A good example is the left side metal3 in the picture below.
We seem to be doing the same thing when we add metal2 pins. They don't seem to be on-grid. See (vinn, voutp,vbiasn) in the picture below.

Any thoughts on what is going on here. Do you need me to setup a reproducible testcase?

Hi Steven,
I guess the width or height of the building blocks is not integral times of
corresponding metal pitches, so shifting exists.
Yes, please give me a reproducible testcase so that I can look into it.
Yaguang
On Sat, Aug 3, 2019 at 1:27 PM Steve Burns<EMAIL_ADDRESS>wrote:

Any thoughts on what is going on here. Do you need me to setup a
reproducible testcase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ALIGN-2Danaloglayout_ALIGN-2Dpublic_issues_108-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAKIMLZV6GCWEN7ASND7TWVLQCXEZDA5CNFSM4II53WH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PTORQ-23issuecomment-2D517945158&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=5a_TgOPm15OE3Wbgalou2fxC9PwscWtD84N4unAAp-U&s=l8T-0AFAWAtEFdu9QDgFv_HABMAr1Fvbf08zlSPPiTY&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKIMLZTSOPZKNDBN5MCDWZLQCXEZDANCNFSM4II53WHQ&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=5a_TgOPm15OE3Wbgalou2fxC9PwscWtD84N4unAAp-U&s=xzbtINgFHDKXS9yVV33FRKLBHwoh4tF3qOvE1jUmH_E&e=
.

Hi Steven,
Is the reproducible testcase ready?
Yaguang
On Sat, Aug 3, 2019 at 1:37 PM Yaguang Li<EMAIL_ADDRESS>wrote:

Hi Steven,
I guess the width or height of the building blocks is not integral times
of corresponding metal pitches, so shifting exists.
Yes, please give me a reproducible testcase so that I can look into it.
Yaguang
On Sat, Aug 3, 2019 at 1:27 PM Steve Burns<EMAIL_ADDRESS>wrote:

Any thoughts on what is going on here. Do you need me to setup a
reproducible testcase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ALIGN-2Danaloglayout_ALIGN-2Dpublic_issues_108-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAKIMLZV6GCWEN7ASND7TWVLQCXEZDA5CNFSM4II53WH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PTORQ-23issuecomment-2D517945158&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=5a_TgOPm15OE3Wbgalou2fxC9PwscWtD84N4unAAp-U&s=l8T-0AFAWAtEFdu9QDgFv_HABMAr1Fvbf08zlSPPiTY&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKIMLZTSOPZKNDBN5MCDWZLQCXEZDANCNFSM4II53WHQ&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=5a_TgOPm15OE3Wbgalou2fxC9PwscWtD84N4unAAp-U&s=xzbtINgFHDKXS9yVV33FRKLBHwoh4tF3qOvE1jUmH_E&e=
.

Opened pull request #112 with this data. Look at the README.md in run.


[Kernel] Use CUTLASS kernels for the FP8 layers with Bias

FP8 biases work as of #5931
I am seeing speedup on Qwen2-7b, which has biases: https://docs.google.com/spreadsheets/d/1faYp80qbmOra3iRMHgga7dPiC6tWULpPQHN_5BfM7gs/

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

@cyang49 were you seeing higher performance with the CUTLASS kernels on Granite as well?

@cyang49 were you seeing higher performance with the CUTLASS kernels on Granite as well?

Yes. There was a slight increase in throughput from my tests.
BTW, I recall that even though the 4 linear layers of the transformer block all have bias, in vllm only 2 of them will go through the path where the bias add is fused. @tdoublep looked into that logic and may be able to provide more details.

@cyang49 Is it because of the code in RowParallelLinear here?
https://github.com/vllm-project/vllm/blob/b422d4961a3052c5b4bcfc3747a1ad55acfe7eb8/vllm/model_executor/layers/linear.py#L755-L769
I don't know why it's like this, but we can look into fixing that.

@tlrmchlsmth yeah it's exactly that code (which I guess is somehow related to TP>1).

I think we should do this at least: https://github.com/vllm-project/vllm/pull/6327


Improve efficiency of control flow algorithms

The previous CFA algorithm was causing out of memory errors. It was used in two cases, neither of which required all the information it was gathering. I've replaced it with two much smaller algorithms with vastly better space usage

Semantic Tests Passed


Add "Audio/Video Updates in Chrome 73" article

Target Live Date: ASAP

[x] This has been reviewed and approved by @jpmedley
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 4 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/08/chrome-69-media-updates.md#L288 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/02/chrome-73-media-updates.md#L261 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/02/chrome-73-media-updates.md#L145 - Line must be at most 100 characters
src/content/en/updates/images/2019/02/media-keys.jpg - Try to keep files below 500K, was 771K

@petele You're right. I should have done this before.

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/08/chrome-69-media-updates.md#L288 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/02/chrome-73-media-updates.md#L265 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/02/chrome-73-media-updates.md#L144 - Line must be at most 100 characters

:tada: This has been pushed live to https://developers.google.com/web/


Resession: [otter] No treesitter parser found for current buffer. Can't activate.

With this in my lazy config, seeing the #177 error again after an update. Only seems to happen in a session restored by 'stevearc/resession.nvim'
  {
    "jmbuhr/otter.nvim",
    event = "FileType",
    config = function() require 'otter'.activate() end,
    dependencies = {
      "neovim/nvim-lspconfig",
    },
    opts = {
      buffers = {
        set_filetype = true,
      },
    },
  },

Why are you calling otter.activate on config? Please use the standard way of doing something for a filetype (ftplugin or an autocommand) and don't mix it with the configuration.


[Fixes #246] Implementation of boundingBox.sphere parsing for 3D Tiles - Issue #79

Implementation of boundingBox.sphere parsing for 3D Tiles

Hi @mattiagiupponi , thank you for your help.  I just pushed the changes including the tests.


fix(deps): update kubernetes packages to v0.30.2

This PR contains the following updates:

Package
Type
Update
Change

k8s.io/apimachinery
require
minor
v0.29.2 -> v0.30.2

k8s.io/client-go
require
minor
v0.29.2 -> v0.30.2

Release Notes

kubernetes/apimachinery (k8s.io/apimachinery)
v0.30.2
Compare Source
v0.30.1
Compare Source
v0.30.0
Compare Source
v0.29.6
Compare Source
v0.29.5
Compare Source
v0.29.4
Compare Source
v0.29.3
Compare Source

kubernetes/client-go (k8s.io/client-go)
v0.30.2
Compare Source
v0.30.1
Compare Source
v0.30.0
Compare Source
v0.29.6
Compare Source
v0.29.5
Compare Source
v0.29.4
Compare Source
v0.29.3
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[x] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.22 -> 1.22.4

k8s.io/api
v0.29.2 -> v0.30.2

k8s.io/klog/v2
v2.110.1 -> v2.120.1

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (v0.30.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


using suppliers

Proposal fix for https://github.com/openzipkin/brave/issues/982
@jeqo WDYT ?

fyi I'm thinking we should settle whether this does or doesn't fix things soon, as I can help do a release today but not later this weekend as I'm out.

fyi I'm thinking we should settle whether this does or doesn't fix things soon, as I can help do a release today but not later this weekend as I'm out.

it definitely fixes the issue for me, just waiting for @jeqo to confirm he can reproduce the issue.

@jorgheymans I've tested your test project, but haven't managed to reproduce the issue :(
Just added some comments on the PR: https://github.com/jorgheymans/kafka-streams-supplier-testcase/pull/1

here is the stacktrace:
Exception in thread "streams-test-case-StreamThread-1" java.lang.IllegalStateException: This should not happen as headers() should only be called while a record is processed
	at org.apache.kafka.streams.processor.internals.AbstractProcessorContext.headers(AbstractProcessorContext.java:149)
	at org.apache.kafka.streams.processor.internals.ForwardingDisabledProcessorContext.headers(ForwardingDisabledProcessorContext.java:147)
	at my.KafkaConfig$1.transform(KafkaConfig.java:75)
	at my.KafkaConfig$1.transform(KafkaConfig.java:63)
	at brave.kafka.streams.TracingValueTransformer.transform(TracingValueTransformer.java:53)
	at org.apache.kafka.streams.kstream.internals.AbstractStream$1.transform(AbstractStream.java:119)
	at org.apache.kafka.streams.kstream.internals.KStreamTransformValues$KStreamTransformValuesProcessor.process(KStreamTransformValues.java:56)
	at org.apache.kafka.streams.processor.internals.ProcessorNode.process(ProcessorNode.java:117)
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:183)
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:162)
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:122)
	at org.apache.kafka.streams.processor.internals.SourceNode.process(SourceNode.java:87)
	at org.apache.kafka.streams.processor.internals.StreamTask.process(StreamTask.java:364)
	at org.apache.kafka.streams.processor.internals.AssignedStreamsTasks.process(AssignedStreamsTasks.java:199)
	at org.apache.kafka.streams.processor.internals.TaskManager.process(TaskManager.java:420)
	at org.apache.kafka.streams.processor.internals.StreamThread.runOnce(StreamThread.java:890)
	at org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:805)
	at org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:774)

The linenumbers in KafkaConfig (63 and 75) are a bit off from the testcase here because it's from my local project, but as you can see from below screenshot it's within the transformer:

for posterity we can open an issue to backfill test with help-wanted and a link to the stack trace and reproduce scenario.


Feature Request: Add Typescript definitions

I would like to use react-hammerjs in my typescript project, but it doesn't have any type definitions. It would be great if this project included one (either in the repo itself, or in https://github.com/DefinitelyTyped/DefinitelyTyped)

i found these, maybe they might do
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-hammerjs/index.d.ts


Retangle main.go

The version of lmt included in this repository is a bit out of date. This PR fixes that.

Thanks! Looks like I forgot to re-run it when renaming files..


Research and develop the new concept for the game in the new language

Even though nothing is ready yet, the game has gone through quite a development hell already. I'd started implementing it in Rust, then realized it was a bad idea, then spent 3 months figuring out which language to switch to, then made the switch based on my gut instead, effectively discarding the 3 months of experiments.
However, with the new language/technology of implementation, comes the new concept.

I've recently come to realize that the old concept is a bit stiff and would not be extremely fun to play as it was not randomized at all. The main difference of the old Rust prototype versus this new C++ one is that the new one is going to feature randomization everywhere, including the very creation of the world itself.
Think about randomizing everything: creating random rooms/locations, connecting them randomly, randomizing loot, game events etc.
More importantly, think about the setting/theme/genre/concept of the game itself. What is the player going to do here?  Or maybe you'd like to create a strategy game? Or a resource management game? Or a logic/puzzle game? Anything's possible. Think deeply about the concept itself.

Once there is an idea and I've reached any kind of conclusion, I should document it here before closing this issue and moving forward.

This issue is a blocker, meaning it prevents me from working on anything else before I make the decision here.

The decision has been made, even though it's not 100% detailed, a lot of issues are going to come up, I'm going to try and solve them when I get to them. The decision is as follows:

Use C++ as the programming language.
Use the following libraries: FTXUI for the TUI, Boost for parsing, string utilities etc. (Boost.Spirit and string utils mostly). Probably going to need a few more libraries, we'll see how things go.
Try using CMake's FetchContent functionality, see how it goes. If it doesn't work properly, use vcpkg.
Start by creating the same kind of prototype you've already created with other languages, but randomized: a few possible room types, a few possible object/entity/monster types, a few possible item types. Then try to mix and match them to create a functioning prototype. See how this goes and continue based on what comes of it.


FancyZones High GPU usage

Microsoft PowerToys version
0.86.0
Installation method
GitHub, PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce

✔ Expected Behavior
No response
❌ Actual Behavior
Lately I've noticed high GPU usage when using FancyZones. As soon as you drag the window for the first time, the GPU usage jumps to 18-25% and the usage values are still there. I work with graphics programs and the performance of the graphics processor is essential for me.
Is this a bug or a feature? Is it possible to check this?
Thank you
Other Software
No response

Please reopen - I'm seeing high GPU usage as well with no FancyZones activity going on. PowerToysReport_2024-12-26-22-10-05.zip


Notify enterprise on checks

Pull Request Checklist
Description

getting rid of dependency cycle (used this commit 2cebbdef163bf12d66b59e8b27aa58bd10559219)
changing the user on check.pp to $::sensu::user
adding Service['sensu-enterprise'] to $check_notify array

Related Issue
https://github.com/sensu/sensu-puppet/issues/827
Motivation and Context
Enterprise service is not reloading anymore
How Has This Been Tested?
tested this against our sensu-enterprise cluster and it works fine
General

[ ] Update README.md with any necessary configuration snippets

[ ] New parameters are documented

[ ] New parameters have tests

[ ] Tests pass - bundle exec rake validate lint spec

Hi @csoleimani Thanks for sending this patch!

Thanks @alvagante
You were able to functionally test in vagrant using the enterprise server?

@ghoneycutt actually not. Haven't had time yet, will do later. Code changes look legit.

@ghoneycutt Any hint of what values to use for FACTER_SE_USER and FACTER_SE_PASS to test Sensu Enterprise in Vagrant?

Tested better, this time, at least with the examples in tests/.
The PR fixes a dependency cycle issue with sensu-enterprise-dashboard-multi-api.pp and does not show any harm. +1 for me

Thanks! Rebasing these commits in PR #829

Released in v2.36.0


Release as apt package

Hello,
we are currently using the ros2 branch on a machine running ROS2 Foxy without any problems. We saw that the driver was formerly published as apt package and maintained on the ROS index. Is there any reason the driver isn't maintained and published anymore outside of GitHub? (Or is it and I just haven't found it?) Also is the ros2 branch meant as rolling branch or is it just the general branch for any ROS2 distro?

Alright, thanks a lot for the quick reply. I didn't know about the backwards compatibility part, thanks for clarifying.


Auto-restart frankenphp in worker mode on file changes (for Docker local development)

Describe you feature request
Opening an issue for this so it doesn't get forgotten. Discussion: https://github.com/dunglas/frankenphp/discussions/556
The custom solution I implemented was using lots of CPU so I had to disable it. It'd be great to have a built in way of handling this. Currently I'm restarting the container manually every time I make a file change 😵💫
Would it be difficult to add this to the container image as a --watch flag?

It's on my todo list!

Is there a forceful way to reload config, looks like php-server is blocking AdminAPI and no SIGHUP supported

Using frankenphp run -c Caddyfile allows API for reload

For the record, this feature is being developed in https://github.com/dunglas/frankenphp/pull/1013.

Since #1013 is merged - can this be closed here?


Change namespace to chat.llamas.cardlogic

This issue is for changing the source namespace / packages to use chat.llamas.cardlogic instead of com.foss.llamas.poker.

I have the tools to do this really easily. I'll wait until existing PRs are merged.

@TheDaemoness Do you think you could give them a review? :smile:


Image on Docker Hub is quite old

The official swarm image is now at v1.2.6, while this image is at v1.2.4. Although the difference is not big, the image is still 7 months old. I wonder if this is still active or not. Thanks

According to Docker Swarm - Functionality folded directly into native Docker, no longer a standalone tool Docker swarm is no longer provided as standalone tool. But of course you can build it on your own from source.

Thanks. I'm currently using the swarm shipped in the binary.


Simplify enabled checks for special domains

Reviewer:

Description:
Consistently disables all features on special domain names.
Steps to test this PR:

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

As mentioned on asana I'm going to wait until we have https://github.com/duckduckgo/duckduckgo-privacy-extension/pull/1363 that way we have a shared object for managing the tab loading status that can easily be accessed from Site.
We need to account for tab loading when checking for if we should apply the feature; if the tab has settled then we shouldn't apply protections to new tab pages.


Update features.md

Include updates from https://github.com/devcontainers/spec/pull/94, plus @jkeech's suggestions so far.
I can continue updating this PR if the one above has further updates.

Fixed some typos in the spec repo folks reported, but it's now merged!

Thanks @Chuxel!


Improve descriptoin in CONTRIBUTING.md

The description in CONTRIBUTING.md needs to improve to refer the to the development branch.
See #72 for justification.

I'm trying to consolidate some of the feedback on improving documentation. I've made some changes here.
Can you let me know if you think this is appropriate to address the issue?


Integrated Terminal eventually turn mouse pointer into 'Precision Select' instead of 'Normal Pointer' or 'Text Select'

VSCode Version: 1.26.1
OS Version: Windows 10 (10.0.17134.228)

Steps to Reproduce:

integrated terminal active.
input any command to integrated terminal.
swap/switch to another programs, I can't specify which condition will trigger the bug. But eventually I found mouse pointer is changed to Precision Select instead of Normal Select or Text Select. (name reference from Mouse properties window of Control Panel -> Mouse)

Does this issue occur when all extensions are disabled?: Yes/No

Yes

I can't capture the screenshot with Windows 10 function, the picture is excluded the cursor image. So there's no image to show you what happen.

I am running in the same issue (screenshot below)

VS Code version: 1.26.1
OS: Manjaro Linux (kernel 4.18.3)
Issue also occur with extensions disabled.

This happens when you alt+tab out of the window, the alt state isn't evaluated again when focus returns to the window.

Upstream: https://github.com/xtermjs/xterm.js/issues/1629

@Tyriar : This is happening for me normally

+1

Fixed by xtermjs/xterm.js#1636


[Migration] Fix disabled tests

This should be tests that are written in a more unit like fashion, and don't always set all expected nodes, elements, and types.

Hi @scheglov , do you know if the relevent tests are fixed? You don't mention which they are.

Yeah, I guess there were many of them while I was migrating the analyzer.
Search for 44522 in the analyzer.
We still have a few.


Add hotkey for feature "Open folder in Explorer" for current script

I failed to find hotkey for this useful feature in settings.
https://github.com/dbeaver/dbeaver/assets/33929221/564c6939-2278-4314-b4e1-a528d1686389

Thank you for request. We appreciate your activity!


ImageRegistrationMethod: different number of iterations per level

the finer resolution levels can get very slow.
(in the python API) would it be feasible to allow the user to specify different number of iterations per level.
This would make it easier to let the coarse level to fully converge, without exploding execution time in the fine level(s).
I think ANTs allows this.

minimum working example you could provide and propose where the change would be in the API?

Hello @dyollb,
Two part answer:
Theory/Philosophy
Generally speaking, the numberOfIterations is the maximal number of iterations. We should have named it maximalNumberOfIterations to make this clear. This parameter is a fail-safe, so that the optimization does not continue beyond a certain timepoint.
The expectation is that the optimization terminate because it satisfies a relevant termination criterion, not max iterations. These convergence criteria have to do with the change in the optimized function value, its magnitude, possibly in the X previous iterations (convergence window). If the termination was due to max iterations, you likely haven't reached the optimum.
Consequentially, as part of the "keep it simple" philosophy of SimpleITK a single max-iterations value is used for all levels of the pyramid. This is a design decision.
Workaround
You can take full control of the multi-scale registration process by implementing your own multi-scale solution. This is easy to do in SimpleITK and is implemented in this Jupyter notebook under the heading of multiscale_demons. You can easily modify the code to repeatedly use a single scale ImageRegistrationMethod with varying settings for each of the levels of the pyramid.

Hello @dyollb,
Two part answer:
Theory/Philosophy
Generally speaking, the numberOfIterations is the maximal number of iterations. We should have named it maximalNumberOfIterations to make this clear. This parameter is a fail-safe, so that the optimization does not continue beyond a certain timepoint.
The expectation is that the optimization terminate because it satisfies a relevant termination criterion, not max iterations. These convergence criteria have to do with the change in the optimized function value, its magnitude, possibly in the X previous iterations (convergence window). If the termination was due to max iterations, you likely haven't reached the optimum.
Consequentially, as part of the "keep it simple" philosophy of SimpleITK a single max-iterations value is used for all levels of the pyramid. This is a design decision.
Workaround
You can take full control of the multi-scale registration process by implementing your own multi-scale solution. This is easy to do in SimpleITK and is implemented in this Jupyter notebook under the heading of multiscale_demons. You can easily modify the code to repeatedly use a single scale ImageRegistrationMethod with varying settings for each of the levels of the pyramid.

Nice. Thanks


HTML Colours are not getting reflected in the report in TestNG 6.8 release

When we give HTMLcode in the Reporter.Log function, generally that particular colour will be reflected for whatever we have given in the HTML report we get, till TestNG 6.7 release but the color is not getting applied from TestNG 6.8 releases. We get some weird error messages if we give the HTML Color code. This is an important aspect which helps to filter the log report(emailable report) with different colours
Yes the issue persists in 6.8.5 also ..
Actually if we give a code "Reporter.log("
"+message+"");", we lll get the message in red color but it does not happen in 6.8 releases. it just prints the contents present in the reporter.log function instead of printing it in red....."Font Color tag given inside the reporter.log method "

Duplicate of #375


validate huge files last

When interacting with h2ogpt I regularly run into a situation where the base model is loaded just to realize a validation fails, e.g. local_files_only but missing a tokenizer, wrong folder for resume_from_checkpoint etc.
Everytime the base model loads it takes an considerable amount of time, just to fail fast after.
I propose to validate the smaller models first before loading the base model

It's certainly true that testing a setup on smaller model is good.  E.g. we often will do the following just to ensure code is working, etc.:

Use distilgpt2 as base model or if doing 8-bit or 4-bit etc., then use 6_9 model
Use epoch=0.001

Then one checks that things complete etc.  Bugs in peft mean one has to copy checkpoint pytorch bin file over to adapter model bin at end that is empty-ish.
Does this workflow make sense to you?
We could probably move the model loading to just before the Trainer() is called, but otherwise we cannot move it any more since that is just a HF class we use.  So, we have Trainer() validate the checkpoint before model is loaded.
We could add some checks that trainer does perhaps, if that's what you are thinking.

Good idea with the workflow. Maybe a sanity check for the folders and .bin files being present?

too complex in general


[BEAM-8824] Add support to allow specify window allowed_lateness in python sdk

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

retest this

retest this please

retest this please

Run Portable_Python PreCommit

retest this please

R: @robertwb @aaltay

retest this please

Run Python PreCommit

@robertwb I've addressed the comments, PTAL, thanks!

Yes, we should just add it to driver.process_elements.

Yes, we should just add it to driver.process_elements.

doing it in StreamingGroupAlsoByWindowEvaluator seems to be more consistent with Java behavior
https://github.com/apache/beam/blob/c2f0d282337f3ae0196a7717712396a5a41fdde1/runners/direct-java/src/main/java/org/apache/beam/runners/direct/GroupAlsoByWindowEvaluatorFactory.java#L206
should we just skip the trigger test with allowed lateness?

Gentle ping for another look.

I can buy the argument that we could be more consistent with Java (though that does mean that we'll be duplicating more code everywhere).

Run Python PreCommit

Run Python PreCommit

Run Python PreCommit

Run Python PreCommit

@robertwb I've moved the window filtering into trigger_driver.process_element() and it should look cleaner now, PTAL

Run Python PreCommit

Run Python PreCommit

Run Python PreCommit

@robertwb Hi Robert, would you mind take another look?

Run Python PreCommit

@robertwb updated according to comments, PTAL

@robertwb gentle ping.

@robertwb I've rebased and resolved the conflicts. Do you mind help to merge this PR?


XD-3709: Unique Domain Name for Module MBeans

JIRA: https://jira.spring.io/browse/XD-3709
Spring Integration has a (regression) bug that causes router MBeans to be
registered by the context MBeanExporter. Usually, Spring Integration components
are registered by the IntegrationMBeanExporter, if present.
This problem means that if more than one router sink is deployed with JMX enabled, deployment
fails with InstanceAlreadyExistsException.
This has been corrected in Spring Integration and will be available in 4.2.3.
However, the same issue would apply to user MBeans in custom modules.
The mbean-exporters XML currently adds a unique domain name to the integration exporter, but
leaves the context exporter with the default domain.
Tested with time | router --expression='''queue:foo''' (two streams) before and after.

LGTM.


TypeError

Code from Example. (Readme)
Give me an Error:

Looks like ViewPropTypes is not present in your react-native version, maybe you are using too old of a version of react-native.
Try updating react-native in your project.
Closing since this issue is external to this library.


Build Issue

Having problems with latest openrefine on debain when i run ./refine build as root or normal user I get errors below ?
[ERROR] Failed to execute goal on project server: Could not resolve dependencies for project org.openrefine:server:jar:3.2-SNAPSHOT: Failure to find edu.mit.simile:butterfly:jar:1.0.1 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
Regards

@webieseo oops, many thanks for reporting this - there was indeed a leftover reference to butterfly 1.0.1 that I have just removed (Travis did not pick up the issue because of dependency caching). Can you git pull, ./refine clean and ./refine again?

HI All,
That fixed it all working now excellent work can I just say big thank you to this project saved me hours of work. HAPPY NEW YEAR
Regards

The latest release still fails with this same error I suppose: Failure to find edu.mit.simile:butterfly:jar:1.0.1

@tuukka if you are using a released version (as downloaded from the GitHub release) then you should not need to use ./refine build, just ./refine should work out of the box. But it is true that you will have this issue when trying to compile OpenRefine from the corresponding git tag. Apologies for that! A new version should be released soon.

No worries, and thanks in advance!


Fix make lint to run govulncheck locally as well

Oops 💦
https://github.com/k1LoW/runn/actions/runs/5570516319/jobs/10174637026#step:7:87


Add music and photos to Jellyfin

What this PR does / why we need it:
Add music and photo path access to Jellyfin
Which issue (if any) this PR fixes:
Fixes #
Any other useful info:

:+1: Thank you!


[Beta] No 3.0.0-beta.7 release

Hi,
The README of the beta branch has this note at the top:

Important: Breaking changes were introduced in version 3.0.0-beta.7, please take a look at release details.

However, there's no tag or release for 3.0.0-beta.7.
Is this supposed to be an internal-only release?

Thanks for letting us know @mderriey, the package was published to npm a few weeks ago, I had the release as a draft and forgot to publish, should be there now


Remove jquery dependency from constraint.js

Description
The file constants.js has dependency on jquery only for using method $.extend, I change it to use vanilla method Object.assign instead.
I also took the time to apply const instead of var.
Object.assign - MDN

Cool.
Except that Object.assign is not supported by IE (even IE11).
The goal is to not require any polyfill for IE9+...

Mmm, the simplest solution is probably to ask Babel to take care of it by adding the right plugin: https://babeljs.io/docs/plugins/transform-object-assign/

All right!
I'll do it :)

@marcandre Sorry for the long time to code this hahaha.

Cool, thanks.
I replace the remaining (shallow) uses of $.extend


feat(devtools): update to devtools stable

note: react is a peerDep of devtools in v3, so we need to include as devDep for now

Thanks so much for this! I was off all last week so I wasn't doing much with computers, sorry. Do you mind rebasing this?


[feature req] tokenization of other languages

simsearch-rs totally fails on Korean text. How involved would it be to have it tokenize hangeul?
searching 던지(요) should match id 866 (name: -던지(요), but gives a top result of id 1527 (name: 에게로 【너에게로 다가간다】).
raw json
use std::{error::Error, fs};

use serde::{Deserialize, Serialize};
use simsearch::SimSearch;

#[derive(Debug, Deserialize, Serialize)]
struct Entry {
    id: i64,
    name: String,
    typical_example: String,
    translation: String,
    category_eng: String,
    category_kor: String,
}

fn main() -> Result<(), Box<dyn Error + 'static>> {
    let mut engine: SimSearch<i64> = SimSearch::new();

    let data = fs::read_to_string("./output.json")?;
    let entries: Vec<Entry> = serde_json::from_str(&data)?;

    for entry in &entries {
        engine.insert(entry.id, &entry.name);
    }

    let results = engine.search("던지(요)");
    let top_match = results[1];

    let entry = entries.iter().filter(|e| e.id == top_match).collect::<Vec<_>>();

    Ok(())
}

It seems to be caused by the levenshtein calculate algrithom from strsim, so I'd make a seperate test on it later.

Solved by https://github.com/andylokandy/simsearch-rs/commit/3b44b214977e8259aa15a07d9e5749e3ea233458


Hide fields in API

Make date fields read-only
Don't require all fields for user creation

Testing:
Get user list:
Make a GET request to /api/users/ and verify that fields such as modifiedAt do not appear in the json response
Create user:
Create a user by make a POST request to the /api/users/ endpoint with a payload similar to:
{
"email"<EMAIL_ADDRESS>"isStaff": false,
"lastName": "test",
"firstName": "test",
"isActive": false,
"organizationId": "{org id}"
}

Modify user
Make a PUT request to  /api/users/{UUID} for any user, using the same format as a GET request to /api/users/ returns
the ID field should not be editable (it won't cause a failure, but it will be ignored) - when we add a directive for error catching this will need to be updated

+1 after cleaning up a little bit of formatting, worked well


net_snmp: 5.7.3 -> 5.8

Motivation for this change
Fixes #51459 #48099
Wasn't able to get the perl modules working, but I may revisit it after this is merged.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@peterhoeg could you review/test?

@grahamcofborg  build net_snmp

Good to go?

@cyounkins, really appreciate the PR but haven't had the time to take a look.

This has now been merged once rebased, in https://github.com/NixOS/nixpkgs/pull/54616.


Package Vulnerabilities related to pm2

The package @pm2/agent depends on vulnerable versions of proxy-agent and semver.
The package @pm2/io depends on a vulnerable version of semver.
The package pm2 depends on vulnerable versions of @pm2/agent and @pm2/io.
The package degenerator depends on vulnerable versions of vm2.
The package pac-resolver depends on vulnerable versions of degenerator.
The package pac-proxy-agent depends on vulnerable versions of pac-resolver.
The package proxy-agent depends on vulnerable versions of pac-proxy-agent.
In total, there are 9 vulnerabilities, with 3 of them being moderate and 6 being critical.

Do you have any plan to send pull request?

Yes, I want to contribute
On Sun, Jul 23, 2023, 4:24 AM Foyzul Karim @.***> wrote:

Do you have any plan to send pull request?
—
Reply to this email directly, view it on GitHub
https://github.com/foyzulkarim/mern-video-streaming/issues/39#issuecomment-1646682689,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUXEHGNFCB4HMK36WPKUGBLXRRHIBANCNFSM6AAAAAA2UBJLT4
.
You are receiving this because you authored the thread.Message ID:
@.***>


JSX autocomplete breaks after certain prop types

Autocomplete for JSX stops working for me after I've added a prop with a string literal. So, this:
<MyComponent someProp=someVar anotherProp="Text here"

Completion works fine after someProp, but breaks after anotherProp.
I think it happened with other things than string literals too, but I'm not at my computer right now. I'll amend this issue with info about later if it still happens.

True, only works with {"Text here"} at the moment. Can be relaxed.

Works for me. Do you have the complete example?

@cristianoc let me try and put up a proper reproduction as soon as I'm by the computer again.

@cristianoc turns out it wasn't strings at all, I was just fooled by the complexity of the component I had when I found it. Instead, it seems to be variants with payloads and without wrapping {}. So, this:
@react.component
open Component

let make = () => <> <Component style=First("Text")  /> </>

Wrapping with {} makes autocomplete work again (<Component style={First("Text")} />), and variants without payloads does not break regardless of if they're wrapped or not. Reproduction here:
https://github.com/zth/rescript-editor-tooling-playground/blob/master/src/OtherComp.res

Thanks yes that's expected. Can be extended to support that too.

Out of curiosity, why is it expected?

Because that case is not covered yet.

Ah, right.

Done in https://github.com/rescript-lang/rescript-vscode/pull/214

Thanks, impressive turn-around @cristianoc!


Panning the map via script

Greetings,
would there be a way to pan the JavaScript VTS map programmatically? With Leaftlet and Google Maps, for example, this can be achieved with their panBy functions. The VTS C++ map has also a "Pan" function as part of its Navigation, but I couldn't find something similar from the JavaScript version. Have I managed to miss it both from the API documentation and code, or is it yet to be implemented? Or would there be there something else that achieves the same functionality?
Thank you.

Yes you can pan with position. I have updated documentation.

Thank you very much for the quick reply and demo! These solved the issue.