'npm start' returns syntax error in server.js

Hi, yesterday I met @timenolthof and he told me about the DIVA project, so I'm trying to get it running on my machine :)
After running npm start (and npm install before that) I get the following error message:
/foobar/diva-js-reference-3p-backend/src/server.js:32
    ...jwtDisclosureRequestOptions,
    ^^^
SyntaxError: Unexpected token ...

I think my 'node' is missing a module to digest the ... - spread syntax. I can't seem to find the correct module to handle it, could someone nod me in the right direction?
Thanks!
Stan

Hi Stan, the spread operator is only supported is only supported from node 8.2.1 and up and currently we use node version 8.6.0 for diva. Using that version might solve your problem.
Optionally, you could use something like nvm to manage node versions efficiently.
@koen92 we should add engine requirements to package.json for all diva projects (see for example http://www.marcusoft.net/2015/03/packagejson-and-engines-and-enginestrict.html ). I've created a ticket on the board.

Thanks, that did the trick!


Adds snow flakes! Happy Holidays

What's this PR do?
Adds snowflakes to the site!
Where should the reviewer start?
Snowflake.js !!
How should this be manually tested?
Do snowflakes epically spawn on your screen?
Screenshots (if appropriate)

NEVER MIND THERES A FATAL FLAW IN THE DESIGN. thanks @DFurnes

I think this is also something we'd definitely want to have a feature flag to enable/disable.

This also uses the ascii :snowflake: symbol now (and I added the feature flag per @DFurnes suggestion, its under "FUN" in dosomething settings)

Hokay :+1:


Connect account doesn't work - no help

Type: Bug
Under 'Get Started with C# Dev Kit', a 'Connect account' prompt appears.
Clicking the 'Connect' button does nothing.
To add insult to injury, 'Help' contains nothing with 'connect' nor 'account'.
In addition, under 'Accounts - sign in requested', clicking 'Sign in with Microsoft to use C# Dev Kit' does nothing.
VS Code version: Code 1.86.1 (Universal) (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:09:01.236Z)
OS version: Darwin x64 23.3.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz (12 x 3200)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 2, 2

Memory (System)
64.00GB (35.52GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

vscode-sqlite
ale
0.14.1

vscode-eslint
dba
2.4.4

vscode-docker
ms-
1.28.0

csdevkit
ms-
1.3.10

csharp
ms-
2.15.30

vscode-dotnet-runtime
ms-
2.0.1

vscodeintellicode-csharp
ms-
0.1.26

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.2.30

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Telemetry: Collect region information

Which area/kind this issue is related to?

/area registry
Issue Description

Currently, devfile metrics are set to the US based region associated with the segment servers.  To get a more accurate representation of where our users are based, we should infer the region from the Accept-Language header if set.

Region information can only be collected if the Accept-Language header is set.  The the only scenario that is currently supported  is if users view/list the contents from the index server.  If the header is unset, we decided to leave the country field unset as well.  If the header is set but the region can't be determined or if there's an error, we'll set a default country (US).


Replace CodeSystem for Vektis 821 with CodeSystem for Vektis 472

Looks good to me.
One optional improvement good be to add more text to the description. In the previous codesysem you had a reference to the 'source'. If possible, we could add a reference to https://www.vektis.nl/standaardisatie/codelijsten/COD472-VEKT ?

This would be better, but is up to the maintainer of the code system in ART-DECOR.


Re-enable geospatial component for ppc64 (for real this time)

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #43.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #43

xref: https://github.com/conda-forge/gz-common-feedstock/issues/34


Wrong FW reported in RNodeConf

Describe the Bug
RNodeConf reports incorrect FW version. This also prevents --auto-intstall upgrades
To Reproduce
Connect to RNode using RNodeConf (tested on 1.6.1 FW version 1.59). Reports version is, at this time, 1.70 and up to date.
Expected Behavior
Reports accurate FW Version
Logs & Screenshots
OLED display reports FW 1.59.
Issue on Linux:
rnodeconf 2.1.3
...
[00:47:37] Opening serial port /dev/ttyACM0...
[00:47:40] Device connected
[00:47:40] Current firmware version: 1.70
[00:47:40] Reading EEPROM...
[00:47:41] EEPROM checksum correct
[00:47:41] Device signature validated

Windows reports:
rnodeconf 2.1.3
...
[18:43:22] Opening serial port com15...
[18:43:26] Device connected
[18:43:26] Current firmware version: 1.59
[18:43:26] Reading EEPROM...
[18:43:26] EEPROM checksum correct
[18:43:26] Device signature validation failed

System Information
See above
Additional context
Issue discovered when tracking down Bluetooth bug. Debugging between the two is overlapping.

Ok, pardon the seemingly obvious question here, but I gotta ask, since I've done this myself a few times. Can you confirm that this is not occurring because you actually have another RNode connected to the system, that is using /dev/ttyACM0, and that the RNode you are intending to communicate with is on another port? I've done this before, where I completely forgot I had another RNode going off on a long USB cable somewhere, and was seriously scratching my head for a good while.
If that is not the case, something bordering on spooky is going on, because I currently have literally no clue how it would get a firmware version value of 1.70 from the device. It's pulling it via a command from the RNode device, and the value being read in the actual hardware is hardcoded into the compiled firmware.
So if it is indeed an issue with rnodeconf or the firmware itself, this is probably going to be an interesting one to hunt down.

Ahem. Never mind. I won't admit what happened, but it wasn't that I missed an RNode attached. All I can say is I do almost all my work through SSH.

Heh, we've all been there :) I once managed to drop an entire database. On the production server - not the local development copy. That required some fast thinking.

Oof. I've done some DOS undelete before, but that's a different level of "Oh no."


Weird in_memory behavior results in whole .hdf5 load at startup

Hello, can you just confirm me that the documentation is still up to date and this:

is still a valid in_memory declaration? (I correctly see it applied in the hyperparameters sumup that ludwig prints out prior to actually doing anything, but I just wanted to check)
I have only a single image input feature, and I also tried declaring that inside of the image feature (under preprocessing: in_memory: false) but every time I start the training it seems to be loading the whole .hdf5, disregarding the in_memory: false request.
I expected it to almost skip the .hdf5 loading, and just start training by loading each batch "just-in-time".
Documentation here https://ludwig-ai.github.io/ludwig-docs/user_guide/#image-features-preprocessing is not so clear on how to work it out, and the sample does not include all the default parameters like with many other features (which would include the in_memory correct declaration also).
Full disclaimer: I created the .hdf5 with a training that did not have in_memory: false, so if something is saved within the .hdf5 itself that prevents it to correctly doing the in_memory thing, that's the issue, but I don't have the resources to repro\retry a full .hdf5 rebuild right now

Your config should be correct. Let me look into this.

Aaaaand this does not happen anymore after reinstalling a whole lot of packages...
Might have been environment-related. Sorry for reporting this.

Oh... I found out why... I was setting in_memory: false as a global preprocessing parameter, and not as a parameter of the image: class.
Sorry for the inconvenience!
PS: this brings me more and more towards some system of a blocking error telling you that you tried to set a non-existent parameter

Yes that's what i was pointing out in my previous message :)
And again yes, as we are converging towards a more stable syntax for the config file, we are considering introducing some (ideally lightweight and sustainable) mechanism for pointing out errors in the model definition. Let me actually add a card in the project for this.


Id 802 convert terms of service to typescript

Jira Ticket: https://broadworkbench.atlassian.net/browse/ID-802
Summary of changes:

TermsOfService.js -> TermsOfService.ts
terms-of-service-alerts.js -> terms-of-service-alerts.ts

Why

More clarity on code related to auth, which will help with ID-720.

Covered as part of https://github.com/broadinstitute/sam/pull/1200


is Docker available on Fedora 32?

File: engine/install/fedora.md

Thanks for sharing this issue. As the issue is old, a lot has changed. The current supported versions have been updated in the topic.


Update timestamps columns to default to the current timestamp

Hi can i work on this ?

Of course you can! Fork and drop a PR in.


Suggestion: adding name space

Hi
Really appreciate your works. The Spectre is really easy to use and good looking!
Just a tiny suggestion, while I was writing WP plugin with Spectre, there might be some conflicts with the original theme style.css, even in the Admin page. I suppose you can have a namespace for Spectre.
Again, thank you very much for your great work
Clark

This has already been addressed (and closed) in issue #382

@clark-mu The solution is already provided: https://picturepan2.github.io/spectre/getting-started.html#variables-custom-prefix


Update client-go, glide

Description
Updates client-go to a pin from master which fixes a bug with InClusterConfig present in v0.3.0.
Specifically, we want this fix: https://github.com/kubernetes/kubernetes/pull/44221/files
Testing
Built a manual felix and calico/node and ensure that it functions properly when deployed as a DaemonSet on a GCE based cluster. #

CC @gunjan5 @robbrockbank

LGTM


When double-click is used to clear the search panel, subsequent searches produce no results

Steps to repro:

Launch the app and click OK in the splash screen
On the search panel, double-click in the search box to clear the default search text
Provide new location search in the search box.  Note that no search results are returned.

This issue may have been introduced with https://github.com/Esri/configurable-locator/commit/afa8bd0c1df19981ef38730978fb20a41a359f9f.

@MikeTschudi  Will you take a look at this?

App was programmed to permanently hide results after a double-click: results were present, but could not be seen

@MikeTschudi  -  This issue is now fixed.  After using double-click to clear the search panel, subsequent searches successfully return results.
However, with this latest change, double-clicking in the search box on the search panel now clears the search entirely: from the search panel and from the map.

Double-clicking the search box should clear the text from the search box and any search results on the search panel, but not clear the map or bottom panel.
Clicking the "X" on the search panel should clear everything: the search panel, the map (ripple, buffer, route, etc) and the bottom panel.

Created https://github.com/Esri/configurable-locator/issues/230 for this new behavior.


⚠ ClamAV has degraded performance

In 89b8d15, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 445 ms

Resolved: ClamAV performance has improved in 8e10916.


fix: add explanatory comment to doc file

I apologize for making such a small pull request immediately after you merged the larger one.
That said, I think that this is worth fixing. The merged pull request had an explanatory comment
for the new option in the README and in the config file. But I
carelessly forgot to add the same explanatory comment to the internal documentation file.
This pull request fixes that mistake. I think it's worth adding since some users will start with
the documentation rather than the README or the code.

Nice work. Thank you.


translate: make try_from_glib unsafe

A defunct implementation could lead to inconsistencies or UB due to
a valid Rust value being constructed from an invalid or undefined
(aka None) C value.
Fixes https://github.com/gtk-rs/gtk-rs/issues/462

Can you think of a case where this could cause actual unsafe behaviour without the implementation requiring an unsafe block? I think this here is actually safe.
The difference to the error checking trait from the other PR is that that one is called from unsafe code and is supposed to check things that following unsafe code relies on.

Can you think of a case where this could cause actual unsafe behaviour without the implementation requiring an unsafe block? I think this here is actually safe.

So far, we have only three real cases for this:

*Return to Result<*Success, *Error> conversion (in gst). A defunct function would interpret the return value incorrectly and could perform an operation when it should be prevented by the result. A buggy code could also do this kind of things, without the conversion being defunct, but the application developer would be mislead by the defunct.
While proceeding with this PR, I noticed that someone used this trait in the genum macro. The problem would be similar to the above. The enum specific conversion usually takes care of variants unknown to the bindings, so that shouldn't be a problem. But inconsistencies could arise in a transitively defunct implementation.
gst::ClockTime. A defunct implementation would be one that fails to identify the GST_CLOCKTIME_NONE value which is u64::MAX. This would be a valid large gst::ClockTime in Rust code, but once passed back to C, it would be considered as GST_CLOCKTIME_NONE, which would be inconsistent. We might not be talking about UB here, but it seems worth pointing out that this implementation requires extra care.

On the other hand, std::convert::TryFrom is not marked unsafe...

My little opinion here: an item is marked unsafe only if using it can panic. In rust, there should never be UB. If something doesn't go as expected and cannot be recovered, we panic. If TryFromGlib (or whatever the name) can introduce UB or panic, maybe it shouldn't be called as such.

What does panicking have to do with unsafe?
If the trait is unsafe or not depends on the guarantees it wants to uphold.  If the implementation uses unsafe code all this doesn't matter) implementation has to hold up more guarantees than what can be checked by the compiler, and otherwise would cause UB. I don't think that's the case here: it will either return a valid value or fail cleanly with an Err. What following code does with those values is their problem really.

So is there a point into making this unsafe?

So is there a point into making this unsafe?

That's the point of this discussion.
I gave it additional thinking while working on ClockTime & co in gstreamer-rs. As a reminder, GST_CLOCK_TIME_NONE equals u64::MAX. As we will able to use Option<ClockTime>, it's actually not a problem in Rust to embed u64::MAX in ClockTime. It could even silently occur before after an arithmetic operation for instance. The real problem is crossing ffi toward C. In a way, this is were any check should be performed. But I guess we don't really want a TryToGlib for this kind of stuff. So what should we do, panic?

I gave it additional thinking while working on ClockTime & co in gstreamer-rs. As a reminder, GST_CLOCK_TIME_NONE equals u64::MAX. As we will able to use Option<ClockTime>, it's actually not a problem in Rust to embed u64::MAX in ClockTime. It could even silently occur before, after an arithmetic operation for instance. The real problem is crossing ffi toward C. In a way, this is where any check should be performed.

Btw, does the new value API help here for getting a Option<gst::ClockTime> from/into a GValue?

But I guess we don't really want a TryToGlib for this kind of stuff. So what should we do, panic?

I would silently have it wrap to GST_CLOCK_TIME_NONE as it can't be represented by the original value, and other calculations overflowing would also map to NONE.

Btw, does the new value API help here for getting a Optiongst::ClockTime from/into a GValue?

I didn't look too closely, but it should help yes.

I would silently have it wrap to GST_CLOCK_TIME_NONE as it can't be represented by the original value, and other calculations overflowing would also map to NONE.

Then I guess the question how soon do we want to detect that:

Should things like ClockTime::from_nsecond return Option<ClockTime>? Probably not.
It's easy to implement for the checked_* op, but should a regular arithmetic operation return an Option?

I think it might be quite difficult a problem for users to debug: a ClockTime resulting from an operation that is treated as None when passed to C.

Maybe we should just log a warning in ToGlib in that case. At least, that would help users spot the problem.

Hmm I don't know!

Needs to be re-open on gtk-rs-core.


Why can't I undelegate my EOS?

The transaction fails everytime?

Could you please show the error?

Turns out I didn't have the CPU power.  I delegated a few EOS  fixed the issue.  Thanks for the reply, love the wallet keep up the good work...

From: tarassh<EMAIL_ADDRESS>Sent: Tuesday, November 13, 2018 3:45 AM
To: tarassh/fairy-wallet
Cc: chetlar; Author
Subject: Re: [tarassh/fairy-wallet] Why can't I undelegate my EOS? (#65)
Could you please show the error?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tarassh/fairy-wallet/issues/65#issuecomment-438183419, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ApTFVpXHFy-4HKIwAnbYuOb51ZPYf7hPks5uuoaPgaJpZM4YYgi8.


start ScreenStateService, drop when changing the theme.


Error in NERDTreeFind after changing directory

I do the following:

:cd /home/user/somepath
Open a file under /home/user/somepath
:NERDTreeFind
:cd /home/user/otherpath
Open a file under /home/user/otherpath
:NERDTreeFind

and I get this error:
Error detected while processing function <SNR>40_findAndRevealPath:
line   33:
E716: Key not present in Dictionary: setShowHidden

What I am trying here is to switch projects

Same here.

Ditto. :)

I can reproduce too:
cd anywhere_but_home
vim
:NERDTreeToggle # shows
:e $MYVIMRC
:NERDTreeFind

produces:
Error detected while processing function <SNR>38_findAndRevealPath:
line   33:
E716: Key not present in Dictionary: setShowHidden


reloader: implement windows support

See zine/server/Reloader.zig for more info.

This is some untested code that @marler8997 shared with me while streaming on Twitch.
https://gist.github.com/marler8997/5ce035b6fb8ec217c2caee5b95c4c622
It can be used as a starting point for implementing this feature.


Contribution guideline?

What's the proper way to submit a PWA for inclusion? Would you simply prefer a pull request with the proper code + svg added to the list, or just tickets that can be addressed?

Here’s a good example of such PR, but here’s also the list of conditions added to the readme.


Underline Keyboard Shortcut for Windows Terminal in Administrator mode missing in Win+X menu

Description of the new feature/enhancement
After selecting Windows Terminal as the default console application, the "Windows Terminal (Administrator)" entry in the Windows+X does not get any letter underlined for easy access, so I need to use arrow keys to select the entry or select using the mouse.
This option was enabled when using Command Prompt or PowerShell as the default console application.
To be precise I'm using the Spanish language in my Windows 11 and I got two entries when I selected Windows Terminal as the default console application:

"W_i_ndows terminal" -> Note that in this entry the letter i (in Windows) is underlined.
"Terminal Windows (Administrador)" -> None of the letters are underlined.

So, if I type: Win+X and letter "i", I launch the Windows Terminal with user privileges.
But there is no option if I want to launch the Windows Terminal with Administrative privileges.
As I said both Command Lines and Powershell had those options at least from Windows 10.
Proposed technical implementation details (optional)
Please to be consistent add an underline letter to the entry to launch Windows Terminal with administrative privileges. Any letter your team may seem fit.
NOTE: There are other means to launch a Windows Terminal with administrative privileges using keyboard shortcuts but what I asking here is about consistency in the Windows user interface.

What version of Windows are you on? I think this was fixed before the release version of Windows 11...

[image: image.png]
It is Windows 11-Pro and AFAIK it is up to date.
J.
El sáb, 20 nov 2021 a las 13:08, Mike Griese @.***>)
escribió:

What version of Windows are you on? I think this was fixed before the
release version of Windows 11...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/11793#issuecomment-974688947,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFY3AEOQH3GWNGMMVRZY223UM7PZ3ANCNFSM5IOFP6RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
J.

@jeansagi this is for reference only, using a 1033 keyboard layout (en-US) on Windows 11. win+x followed by a launches WT  with admin rights:

If you change the language on your system does it still not work? Might help narrow the problem. Thx!

This is what I actually got:

And as I said I'm on Spanish language more specifically Español (México) although I'm really living in Colombia ;) :

And Finally, I have a Latin-American keyboard layout:

So, if I understood @elsaco correctly the advice is to Install "English" language for testing if this way I get Windows Terminal in Administrative mode with a letter underlined?
J.

@jeansagi the idea is to find out if the issue persist with other languages. Sorry for any misunderstanding.

This is crazy, thanks for filing this. I can't believe the spanish translation doesn't have the hotkey associated with it, I could have swore those were generated automatically, but I suppose I was wrong. Lemme file an internal bug for this.

in Windows 11 Insider zh-CN (currently running 22504 here), the admin one has &A assigned, but the non-admin one does not have any accelerator assigned.

in Windows 11 Insider zh-CN (currently running 22504 here), the admin one has &A assigned, but the non-admin one does not have any accelerator assigned.

In windows 11 zh-CN (currently 22000.384 here), neither the admin one nor the non-admin one has accelerator assigned.

It would be nice to know when this will be addressed.
J.
El dom., 16 de enero de 2022 23:04, Chi Lei @.***>
escribió:

in Windows 11 Insider zh-CN (currently running 22504 here), the admin one
has &A assigned, but the non-admin one does not have any accelerator
assigned.
In windows 11 zh-CN (currently 22000.384 here), neither the admin one nor
the non-admin one has accelerator assigned.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/11793#issuecomment-1014118493,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFY3AEKVCO4XEBO4D35WOTTUWOINJANCNFSM5IOFP6RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Apparently 22523.1000 will have this fixed. I think that's available on the Insider's channel?

Apparently 22523.1000 will have this fixed. I think that's available on the Insider's channel?

Sadly, you can only download 22533.1001 now, which has a terrible language pack that users have to uninstall language pack to avoid bugs. See this link.

This is crazy, thanks for filing this. I can't believe the spanish translation doesn't have the hotkey associated with it, I could have swore those were generated automatically, but I suppose I was wrong. Lemme file an internal bug for this.
This is now MSFT:37128265

;)
No I don't have them yet...
El mar, 25 ene 2022 a las 13:06, ThemisterNaim @.***>)
escribió:

This is crazy, thanks for filing this. I can't believe the spanish
translation doesn't have the hotkey associated with it, I could have swore
those were generated automatically, but I suppose I was wrong. Lemme file
an internal bug for this.
This is now MSFT:37128265 https://task.ms/37128265
[image: zombomeme25012022190354]
https://user-images.githubusercontent.com/96649980/151033921-12196b39-4596-4561-a04e-8f1483530492.jpg
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/11793#issuecomment-1021466284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFY3AEIZASDGRH2N2CFT5KLUX3RDNANCNFSM5IOFP6RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
J.

:(
At least we are not alone... ;)
J.
El mar, 25 ene 2022 a las 13:07, ThemisterNaim @.***>)
escribió:

[image: zombomeme25012022190354]
https://user-images.githubusercontent.com/96649980/151033921-12196b39-4596-4561-a04e-8f1483530492.jpg
[image: image]
https://user-images.githubusercontent.com/96649980/151033979-5edfd245-7f82-4c00-a8f6-58b367d2eea4.png
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/11793#issuecomment-1021466708,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFY3AEJMPW6NXDXAUU3KVQLUX3RFDANCNFSM5IOFP6RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
J.

Now it is fixed, at least for me:

Perhaps it was the 1.12.10334.0 stable release upgrade.
If others got the fix, this should be closed.
Thanks a lot!!
J.

Thanks for confirming! If there are any other languages missing, we can all pile in on #12572.


update jwt library

dependabot alert  Authorization bypass in github.com/dgrijalva/jwt-go shows  is high severity - this library has been migrated to new repo, and no security fixes available  on this repo.
New repo is: https://github.com/golang-jwt/jwt - there are v3.2.1 and v3.2.2 versions which should fix the issue.  There are also v4.x versions, but will require work to determine comatibility

Yes if possible try to move to the 3.2.2 version of golang-jwt
Thanks in advance
Envoyé depuis Workspace ONE Boxer
Le 2 nov. 2022 09:53, John Grange @.***> a écrit :
dependabot alert Authorization bypass in github.com/dgrijalva/jwt-go shows https://github.com/ThalesGroup/sshizzle/security/dependabot/1 is high severity - this library has been migrated to new repo, and no security fixes available on this repo.
New repo is: https://github.com/golang-jwt/jwt - there are v3.2.1 and v3.2.2 versions which should fix the issue. There are also v4.x versions, but will require work to determine comatibility
—
Reply to this email directly, view it on GitHubhttps://github.com/ThalesGroup/sshizzle/issues/13, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOVF4T2XN35PCMGMAZDEVCTWGITZVANCNFSM6AAAAAARU2ZDZM.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Problem with cache restore between container and not containers steps.

Hello.
I use cache@v3 and I have problem.
I have workflow with multiple jobs.
In one job I create a cache:
      - name: Cache public/build
        uses: actions/cache@v3
        id: vendor
        with:
          path: |
            public/build
          key: ${{ runner.os }}-${{ github.sha }}-${{ github.run_attempt }}
          restore-keys: |
            ${{ runner.os }}-${{ github.sha }}-${{ github.run_attempt }}

The cache is created, in logs I see:
Cache saved with key: Linux-5e15781dd06305d712a2f088383b3b0deecb8bfc-1

I have two more jobs, in one (that is executed right after job when I created cache) cache is restored successfully but in another I see:
Cache not found for input keys: Linux-5e15781dd06305d712a2f088383b3b0deecb8bfc-1, Linux-5e15781dd06305d712a2f088383b3b0deecb8bfc-1

I tried to comment job when cache is used (I thought that cache can be used only once) but without effect. Cache is not restored.
I use ubuntu-latest. Jobs when I create cache and job when cache works are running in container but job when cache doesn't work I don't use container.
When I create test job:
 cache-test:
    runs-on: ubuntu-latest
    container:
      image: myrepo:my_tag
      credentials:
        username: xxxxx
        password: yyyyy
      options: --user 1001

    steps:
      - name: Clean workspace
        run: rm -rf *

      - name: Trust My Directory
        run: export GIT_CEILING_DIRECTORIES=/__w # only work before git v2.35.2

      - name: Checkout
        uses: actions/checkout@a12a3943b4bdde767164f792f33f40b04645d846

      - name: Cache public/build
        uses: actions/cache@v3
        id: vendor
        with:
          path: |
            public/build
          key: ${{ runner.os }}-${{ github.sha }}-${{ github.run_attempt }}
          restore-keys: |
            ${{ runner.os }}-${{ github.sha }}-${{ github.run_attempt }}
      - run: ls -lahrt public/build

Cache is working. Looks like when I create cache inside container it is not accessible if I use build on ubuntu-latest without container.
I found similar problem on stackoverflow: https://stackoverflow.com/questions/70761005/cache-created-in-ubuntu-latest-cannot-be-restored-in-docker-container

Some container do not support actions/cache properly. Look at https://github.com/actions/cache#pre-requisites for more details. There should be no problem in cache saving and restoring if a container supports actions/cache

@es1o Does that answer your question?

@es1o Closing this issue for now. You may re-open this if you want to ask more about this issue.


Minimal test

Can I use mavlink2rest to view a very simple message stream, e.g., just HEARTBEAT messages?
I am sending HEARTBEAT msgs via pymavlink:
import time
from pymavlink import mavutil

conn1 = mavutil.mavlink_connection('udpout:localhost:14550', source_system=1, source_component=1)

while True:
    conn1.mav.heartbeat_send(12, 3, 128, 21, 3)
    time.sleep(0.5)

When I try to recieve these using mavlink2rest nothing shows up:
./mavlink2rest-x86_64-unknown-linux-musl --verbose --system-id 255 --component-id 0 --connect udpin:<IP_ADDRESS>:14550

Is there some handshake that I am missing?

Hi @clydemcqueen thanks for checking it!
I was able to replicate the problem and will take a look into it. I was in a conference, thanks for your patience.

Hi @clydemcqueen, from my tests I got it working while using mavlink2rest with mavlink 1, the default for the project is 2.
./mavlink2rest --verbose --connect udpin:<IP_ADDRESS>:14550 --mavlink 1

@patrickelectric Thanks so much for tracking this down!
I was able to set mavlink wire protocol 2 messages by setting an environment variable:
import os
os.environ['MAVLINK20'] = '1'
from pymavlink import mavutil

A little funky (triggers E402 error from pycodestyle.py) but AFAICT this is the only supported way to specify mavlink wire protocol 2.
I'll close this out.

Hi Clyde, thanks for letting me know!


Service worker stops working in Safari after refresh

When I test Safari in Browserstack, I find that input() works fine at first, but stops working after I reload the page. I encountered the same problem while working on a generic synchronous communication library. It's not entirely clear but it seems like Safari service workers stop intercepting synchronous (or maybe all?) XHR requests after the reload. Can anyone with an actual Mac confirm this issue? Anyone know anything more?

Reloading itself doesn't cause the problem. Reloading while it's waiting for input from the user, or just not providing input until the request times out, seems to be what breaks things.


In HTTP query editor's network panel, request tab doesn't scroll.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹

Preview a query
In the default network panel position, head over to the request tab and try to scroll down.

Current behavior 😯
https://github.com/mui/mui-toolpad/assets/92228082/bbf3e043-f288-439a-bbad-6eeac67405d3
No response
Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
 System:
    OS: macOS 13.3
  Binaries:
    Node: 20.2.0 - ~/.nvm/versions/node/v20.2.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v20.2.0/bin/yarn
    npm: 9.6.6 - ~/.nvm/versions/node/v20.2.0/bin/npm
  Browsers:
    Chrome: 116.0.5845.187
    Edge: Not Found
    Safari: 16.4
  npmPackages:
    @emotion/react:  11.11.1
    @emotion/styled:  11.11.0
    @mui/base:  5.0.0-beta.15
    @mui/core-downloads-tracker:  5.14.9
    @mui/icons-material:  5.14.9
    @mui/lab:  5.0.0-alpha.144
    @mui/material:  5.14.9
    @mui/private-theming:  5.14.9
    @mui/styled-engine:  5.14.9
    @mui/system:  5.14.9
    @mui/toolpad: ^0.1.28 => 0.1.28
    @mui/toolpad-components:  0.1.28
    @mui/toolpad-core:  0.1.28
    @mui/toolpad-utils:  0.1.28
    @mui/types:  7.2.4
    @mui/utils:  5.14.9
    @mui/x-data-grid:  6.13.0
    @mui/x-data-grid-pro:  6.13.0
    @mui/x-date-pickers:  6.13.0
    @mui/x-date-pickers-pro:  6.13.0
    @mui/x-license-pro:  6.10.2
    @mui/x-tree-view:  6.0.0-alpha.2
    @types/react:  18.2.21
    react:  18.2.0
    react-dom:  18.2.0
    typescript:  5.2.2

can i take this up ?

Sure👍

Looked into this, seems the issue is with other tabs as well , only response tab scroll is working.
trying to find a proper fix.


rimraf is missing when building the package

hi @d-fischer,
rimraf was missing when I tried to build my package, so I had to npm install it.
the rimraf package is listed under devDependencies section, I think it's better to place it under dependencies or peerDependencies.

I see now that you already addressed it, so this issue can be closed.

Correct, this was fixed in 155e88b and released as v0.2.3 already.


fix: Update helm chart to use Release.Namespace

Update helm chart to use Release.Namespace instead of chart name.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.38%. Comparing base (0686a78) to head (168001f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #113   +/-   ##
=======================================
  Coverage   77.38%   77.38%
=======================================
  Files           3        3
  Lines         252      252
=======================================
  Hits          195      195
  Misses         56       56
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


@ in password not support

Describe the bug
Say a user with password passwd@123. Since @ in DSN can not be distinguished, it should be quoted as passwd%40123. However datadiff does not support quoted DSN currently.
After searching, I found that dsnparse 0.2.0 has support that kind of quoted DSNs.
please consider to upgrade the dependency version to “>0.2.0”.
https://github.com/datafold/data-diff/blob/be5256c738732ee20285dd6874bfa9c98c592e3f/pyproject.toml#L28

@qsliu2017 ty for reporting this!
There was an issue in 0.2.0 here https://github.com/datafold/data-diff/issues/616
We'll have to investigate/mitigate that if we bump the version up

@qsliu2017 What databases are you diffing? We recently fixed this for postgres: #812

@qsliu2017 What databases are you diffing? We recently fixed this for postgres: #812

oracle :(

Okay, I think this should be relatively easy to fix.

Same issue here

Workaround: use a job file

Hi @qsliu2017 and @DiogoParrinhaAM,
I'm sorry for the delay in following up on this. Thank you for raising this issue and for looking into potential solutions!
We made a hard decision to sunset the data-diff package and won't provide further development or support.
If that's of interest, over the past few months, we have rewritten the diffing engine in Datafold Cloud and solved many issues that existed in this package's diffing algorithm. Feel free to take it for a trial and contact us at<EMAIL_ADDRESS>if you have any questions.
-Gleb


React 16 | Segmented Buttons Toggle Not Working

For Segmented Buttons once clicked, state is not changing for subsequent clicks- Charts-Columns-Stacked Example

This is happening whenever we have 'pressed' attribute in segmented buttons. For eg: in Charts->ChartToolBar.js

Fixed - Although, pressed in react15 was working, in react16 made changes to pressed in segmented buttons


Avoid button overflow

Fixes #1824: Hide overflow when text doesn't fit in button.

you can do
overflow:hidden;
text-overflow: ellipsis;

which is nicer than just clipping the text

Wow, didn't know about text-overflow. Cool, just added it!


Add project version to config

Also incremented version to 0.1.1 for new release.

Thanks! Merged manually


Build refactor

@happykow Thoughts on this update?
I want to get the inline dockerfile out of the build config for the patch so we can run CI against it.
Eventually I think we should move the builds to a helm chart but I didn't want to get too ambitious for this update.

@strangiato I agree.
This has been something I wanted to do as well. Thanks for taking the time to do this!


How can I use just Phone Number Login?

I don't want the user to enter email id every time they login

Start by changing AuthStatus.PROFILE_AUTH to AuthStatus.PHONE_AUTH, then the user won't be required to use their Google Account to proceed. Then, instead of linkWithCredential, change to signInWithCredential; after, just take out everything from the _linkWithPhoneNumber function, and do your thing there!


Fixed duplicate line in TermControl (#732)

I deleted the duplicate line in TermControl mentioned in #732

Actually nothing, since the default value seems to be Stretch for both Vertical and Horizontal:

A horizontal alignment setting, as a value of the enumeration. The default is Stretch.
https://docs.microsoft.com/de-de/dotnet/api/system.windows.frameworkelement.horizontalalignment?view=netframework-4.8

So, I guess I can delete both lines and commit again?

Oh, then yea go ahead!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mKay00 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!


Select() to a custom value type with stats or ToPagedList()

Strong typed identifiers are the gift that keeps giving.

So far, this is "works on my box". Waiting for better repro steps for whatever the user issue was.

No recent activity, closing


⚠ Spryr has degraded performance

In 29f533b, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5472 ms

Resolved: Spryr performance has improved in 17b9c7e after 7 minutes.


Filter export to past _ years

Exported files now contain only the past _ years (configurable) plus old data that is still relevant (active conditions, medications, careplans). Procedures are not kept if old but if they have permanent effects they should add a "History of xyz" condition, a few of which are introduced here.
Also adds configurable options for exported file formats (fhir, ccda, html)

Looks great.


fix runtime symbol load issues for template

Variadic Template function reference is not seen in shared object in nm or objdump but if i place it in specific actions it works.
WIll refactor this, pushing change to avoid run time so load failures.

Let plan to move the template to the header later on instead of two same templates.


Implementation of VLAN in interface table

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version: 3.5.2
NetBox version: 2.3.2

Description
When seeing the interfaces on the device, you can't see the VLAN they are attributed to, a simple header in the table would allow for the person to view what VLAN is the interface connected to.
Example:
IMGUR

I think issue #2060 is related?

Yes, it seems that for now you going to have to manually edit the Description field

vlanS (plural) along with aggregation (e.g. LACP) would be useful.
That said when you get to this level it may arguably be better to pull this from switch APIs or integrate with config management tools (e.g. Ansible).

LACP associations are already shown in both the API as well as the UI

The v2.4 release will include an interface view which includes all assigned VLANs and IP addresses. VLANs aren't included in the device interfaces list because the table is busy enough as it is.


How install webchat for website

i cannot install webchat I've downloaded it... I've tried to paste the code on my squarespace website and it doesnt work.


Playing network stream with parameter

Hello,
I am using xZune and I am very happy with it. In VLC Player I can set parameter if I want to Play a Network stream. The parameter can be for example:
:avformat-format=mxg
It is possible to set this parameter in xZune if I want to Play a Network stream?
Thanks.

Try
LoadMediaWithOptions(Uri uri, String options);

AddOption(String option);

LoadMediaWithOptions() is working. Thanks for the fast answer.
Now I have to get the .net 3.5 sample working. I got some Errors if I try to compile it.

I know it...I changed some code to fix bug #32 ...
These code maybe have some wrong with .Net 3.5...
I'll fix it later.

I fix all wrong in  .Net 3.5 ...
Now you can compile xZune.Vlc for .Net 3.5 ...


pdf annotation

Not a issue, but idea.
PDF.js have a nice functionality in toolbar, so you can annotate .pdf with free hand tool and text tool. You can annotate and download annotated .pdf.
It can be usefull, if vaadin pdf viewer have this option.

I am looking for the annotation too. Could you indicate how I add it to your component? Keep up the great work! Thank you!!


Limit content of ~/.config/containers/libpod.conf

/kind bug
/kind feature
Description
A ~/.config/containers/libpod.conf file  is created at the first start of podman with the actual settings.
This file is not touched/migrated after then which causes problems when there is a libpod.conf from ancient versions. E.g. one with
cgroup_manager = "cgroupfs"

settings whose code path is not tested anymore and which causes problems in recent versions (e.g. #4704).
I suggest to either:

keep this file empty
comment out its content so that it documents the actual settings and gives user a template
like before but include .../libpod.conf.d/*.conf files where user configuration happens (like systemd-system.conf)

Output of podman version:
Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.1
OS/Arch:            linux/amd64

Already handled on master (actually made it into 1.6.3 as well I think)
On Wed, Dec 18, 2019, 05:56 Enrico Scholz<EMAIL_ADDRESS>wrote:

/kind bug
/kind feature
Description
A ~/.config/containers/libpod.conf file is created at the first start of
podman with the actual settings.
This file is not touched/migrated after then which causes problems when
there is a libpod.conf from ancient versions. E.g. one with
cgroup_manager = "cgroupfs"
settings whose code path is not tested anymore and which causes problems
in recent versions (e.g. #4704
https://github.com/containers/libpod/issues/4704).
I suggest to either:

keep this file empty
comment out its content so that it documents the actual settings and
gives user a template
like before but include .../libpod.conf.d/*.conf files where user
configuration happens (like systemd-system.conf
https://www.freedesktop.org/software/systemd/man/systemd-system.conf.html
)

Output of podman version:
Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.1
OS/Arch:            linux/amd64
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/4724?email_source=notifications&email_token=AB3AOCH4A2CJNRWHHP2ERTDQZH6VJA5CNFSM4J4JDXL2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IBJYAYQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3AOCGKO5U66UAYWA3YMSTQZH6VJANCNFSM4J4JDXLQ
.


Fix/AE console - modify reviewers assignment link is wrong

fix modify reviewers assignment link so that edge browser does not break

TMLR AE console in live has been fixed


Update PlatformExtensions.cs

The ToNsDictionary method has a bug. NSDictionary objects are immutable, and this method causes a crash at SetValueForKey (the error is this class is not key value coding-compliant for the key)
Credit to a StackOverflow answer for an elegant alternative https://stackoverflow.com/questions/36027542/xamarin-ios-convert-dictionary-to-nsdictionary
Description of Change
The NSDictionary is immutable so using an alternative means to create an NSDictionary and populate it with keys and values from an IDictionary.
Issues Resolved

fixes #

API Changes

None
Platforms Affected

All

Behavioral Changes

None
Testing Procedure

I didn't test this fix, but I did test setting a payload in a notification and hit the error described at the top. This issue was actually fixed before (see https://github.com/shinyorg/shiny/issues/15) so I'm sure the use of NSDictionary is the culprit here.
PR Checklist

[ ] Rebased on top of the target branch at time of PR
[ ] Changes adhere to coding standard

Thanks for the PR


check_lib_version can panic on deploy without informative message

The current method uses indexing to pull out the version of Cargo.toml. This can panic if the key is not present:
https://github.com/shuttle-hq/shuttle/blob/d4af3674de5f77477eda7febbbd7935add7f1672/cargo-shuttle/src/lib.rs#L257
If the Cargo.toml does not have a dependencies table or shuttle-service is not present then this expression panics. It would better to catch these and produce a readable error. Can use Document::get to do that.
The second question is whether shuttle-service = "0.4.0" is an error because there are no features specified. While adding this change should shuttle suggest that a feature needs to present?
I am happy to add this change ;)

I think shuttle-service = "0.4.0" should be correct, because that's how I think a user implemented service would specify the shuttle_service dependency.
@kaleidawave sure, you can make the change :smile:

We removed this check in 0.12, so closing this.


Refresh AS packages to latest version (<IP_ADDRESS>)

It is desirable to pick up the latest versions of the AS packages before v22 GA.
The following packages should be bumped to version <IP_ADDRESS>

Microsoft.AnalysisServices.retail.amd64
Microsoft.AnalysisServices.NetCore.retail.amd64

This is fixed in v<IP_ADDRESS>+ (when available)


[warning] failed package validation and/or copy for commit b6831d451915bf58ab60ae4dc31c490b909b06ce

Hi @conda-forge/napari-console! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid feedstock token

@conda-forge-admin, please rerender

Hi @conda-forge/napari-console! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid feedstock token


libc/newlib: Add support for compiler-rt runtime library

When Zephyr is compiled using LLVM toolchain, compiler-rt can be used as a runtime library instead of libgcc. Add support for compiler-rt in newlib's CMakeLists.

Friendly ping.

@keith-packard - I wonder if PicoLibC falls into the same boat as newlib with LLVM.
It looks as though -lgcc is hard-coded here
https://github.com/zephyrproject-rtos/zephyr/blob/7ac34d095790155d5769f7a22c0c6280fc465707/lib/libc/picolibc/CMakeLists.txt#L16

@keith-packard - I wonder if PicoLibC falls into the same boat as newlib with LLVM.
It looks as though -lgcc is hard-coded here
https://github.com/zephyrproject-rtos/zephyr/blob/7ac34d095790155d5769f7a22c0c6280fc465707/lib/libc/picolibc/CMakeLists.txt#L16
@semihalf-duda-patryk - would you be so kind as to re-run your test with PicoLibC instead of Newlib? If the same problem presents, it would be great to add a second commit to address the same issue with PicoLibC.

The line refers to situation in which picolibc is provided with toolchain. I don't have access to LLVM toolchain with picolibc.
I tried to use picolibc module, but there are symbol duplicates
ld.lld: error: duplicate symbol: __aeabi_memcpy4
>>> defined at aeabi_memcpy.S.o:(__aeabi_memcpy) in archive /usr/lib64/clang/17/lib/baremetal/libclang_rt.builtins-armv7m.a
>>> defined at memcpy.c:78 (/home/patryk/zephyrproject/modules/lib/picolibc/newlib/libc/machine/arm/../../string/memcpy.c:78)
>>>            memcpy.c.obj:(memcpy) in archive modules/picolibc/libc.a

ld.lld: error: duplicate symbol: __aeabi_memcpy8
>>> defined at aeabi_memcpy.S.o:(__aeabi_memcpy) in archive /usr/lib64/clang/17/lib/baremetal/libclang_rt.builtins-armv7m.a
>>> defined at memcpy.c:78 (/home/patryk/zephyrproject/modules/lib/picolibc/newlib/libc/machine/arm/../../string/memcpy.c:78)
>>>            memcpy.c.obj:(memcpy) in archive modules/picolibc/libc.a

ld.lld: error: duplicate symbol: __aeabi_memcpy
>>> defined at aeabi_memcpy.S.o:(__aeabi_memcpy) in archive /usr/lib64/clang/17/lib/baremetal/libclang_rt.builtins-armv7m.a
>>> defined at memcpy.c:78 (/home/patryk/zephyrproject/modules/lib/picolibc/newlib/libc/machine/arm/../../string/memcpy.c:78)
>>>            memcpy.c.obj:(memcpy) in archive modules/picolibc/libc.a

Looks like it needs more investigation.

It seems something is missing with this PR.
Per default, users cannot select Newlib with LLVM toolchain because of this line:
https://github.com/zephyrproject-rtos/zephyr/blob/65f029e1850090887317efa37fc37758c2bffa93/cmake/toolchain/llvm/generic.cmake#L20
so users should not be able to get in this situation. If locally changing this cache variable, then clang fails to pickup newlib headers.
So before this PR is merged, then I would like to have a bit more information on how this is intended to work for end-users.
Are there missing some commits related to this improvement ?

AFAIK Zephyr SDK doesn't provide LLVM toolchain with Newlib. I'm testing this PR with our own toolchain (it's vanilla LLVM with Newlib) and I'm using separate generic.cmake file.
Think about this PR as a one step to use LLVM toolchain with Newlib :smile:

AFAIK Zephyr SDK doesn't provide LLVM toolchain with Newlib.

Correct.

I'm testing this PR with our own toolchain (it's vanilla LLVM with Newlib) and I'm using separate generic.cmake file.

I was suspecting something like that.

Think about this PR as a one step to use LLVM toolchain with Newlib 😄

Yep, and the adjustment to test for GNU is cleaner, cause testing for llvm could cause confusion / risk of being removed simply because nothing in Zephyr itself supports the combination of llvm / newlib.

Friendly ping


HSEARCH-4940 Use "Jakarta Batch" instead of "JSR-352"/"Batch for Java" in POM and documentation of JSR-352 artifacts

https://hibernate.atlassian.net/browse/HSEARCH-4940
Hey Yoann,
From what it looks, we've missed the javax->jakarata update for a CDI (see [HSEARCH-4940 Make sure that batch beans are correctly registered within CDI]) 😔
I've updated that service file and bean names too, but with these changes EntityManagerFactoryRegistry emfRegistryin JobContextSetupListener is injected as JBeretEntityManagerFactoryRegistry (previously it was just null), which leads to failures since the PersistenceUnitAccessor#entityManagerFactory == null
The "fix" in HSEARCH-4940 Fallback to ActiveSessionFactoryRegistry makes the tests pass, but I'd still expect that the correct way to solve this would be to make PersistenceUnitAccessor#entityManagerFactory != null ...  Not sure how to get there though 😔😃 ...
besides the bug, do we want to change the java module names + packages for these modules or should we leave them as they are?
Opening as a draft since need a better fix for the bug ^

I've left the "incorrect" service file name as well. With JBeret upgrade the listener was added through CDI even though the reference was incorrect. They've added some code that would check if the bean is present by a reference in the bean manager and if not try to use the reference as a class name and lookup beans by that class. So we were ending up getting the listener through the CDI and as a result, working with the JBeret registry which led to test failures in the end.

Seems you need to update dependencies in the reports module:
[ERROR] Failed to execute goal on project hibernate-search-reports: Could not resolve dependencies for project org.hibernate.search:hibernate-search-reports:pom:7.0.0-SNAPSHOT: The following artifacts could not be resolved: org.hibernate.search:hibernate-search-mapper-orm-batch-jsr352-core:jar:7.0.0-SNAPSHOT (absent), org.hibernate.search:hibernate-search-mapper-orm-batch-jsr352-jberet:jar:7.0.0-SNAPSHOT (absent): Could not find artifact org.hibernate.search:hibernate-search-mapper-orm-batch-jsr352-core:jar:7.0.0-SNAPSHOT -> [Help 1]


feat(download): switch to download strategy for passing model files

BREAKING CHANGE: all path options have been switched to options
that can accept a remote URL or a JS source object (i.e. from require
or import).
Path options include: wakeword.filterPath, wakeword.detectPath,
  wakeword.encodePath, nlu.modelPath, nlu.metadataPath, and nlu.vocabPath.

These have been changed to wakeword.filter, wakeword.detect, etc.

- This commit also adds wakeword to the example.

Reasoning
I started to add wakeword to the example app and realized again that I would need to implement downloading and caching the model files in order to use the feature. We've used rn-fetch-blob for this in the past, but it turns out that it is no longer maintained. I spent a little time researching other libraries, including expo-file-system (which depends on expo core) and react-native-fs. Those libraries are behemoths that handle a multitude of use cases beyond what we need for this library. So, I went ahead and changed the options here to automatically download and cache the respective files, which simplifies the example app greatly. This will also simplify the tray and reduce its dependency size.
I'm not 100% confident in the Swift and Kotlin code I ended up with to download and cache the model files. I'm more happy with the Swift code because it downloads all of the model files in parallel before finally executing the builder. I think the Android side is synchronous, but it has the advantage of being very simple, and it doesn't seem to take very long to download and then initialize.

The strategy here has been switched to support either remote URLs or source objects (i.e. the return value of require('./filter.tflite'). Two options have also been added. One to indicate whether to download over cellular (allowCellularDownloads) and another to refresh the model files even if they are present in the cache (refreshModels).
I've also added the close calls on the i/o streams in Android.


Add index to rss_logs table: observation_id

Part of the Home Page Load Time Jubilee 2023

Thanks, Nimmo!


Support for TechnologyName property

Is it possible to show the TechnologyName property for the elements?
See a screenshot by DevExpress
For all common controls/elements there should be "MSAA" or "Web" or "UIA".
This is required in order to validate whether third party extensions for UIA (such as from DevExpress) are loaded.

Seems like that is a custom uia property. This is in general not a problem but unfortunately I do not have this DevExpress.CodedUIExtension assembly available to find the name/id of this property to add. Do you know if it's possible/allowed to send me that assembly?

Hi Toni and Roman,
Toni contacted us regarding this. Sure, we can share the mentioned assembly. You can download it from my comment in the https://www.devexpress.com/Support/Center/Question/Details/T549595/support-for-plain-uia-msaa-frameworks ticket.

Thanks for the link, I will investigate in it.


DCO check workflow added to repo

Description
DCO work flow is checked for new pull requests
Added DCO Check Workflow
Added CONTRIBUTING.md DCO Section
Issues Resolved
#14
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Good with me on 🍏

You can switch to using Maven released artifacts! Or a snapshot build, up to you.
https://github.com/opensearch-project/opensearch-plugins/blob/main/BUILDING.md#developing-plugins-for-opensearch


Update the JDK and Jenkins Core to the latest versions

Jenkins and plugins versions report

Environment

Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?
Using Azure VM with following specifications

OS : Windows server 2019 or 2022
Core : 4
Memory : 16 GB

Reproduction steps
Even a basic pipeline isn't getting kicked off because few of the plugins are demanding latest version of JDK or latest version of Jenkins Core. Along with this, the script for linux provides many features more than the windows one and our runner is a Windows, so please add the latest features and versions support for windows too.
Here I am  leaving a copy of my codebase here for reference - jfr_setup
Expected Results
The expecetd result was the same as  the screenshot provided in the README file of Jenkinsfilerunner. We have modified many things by far within a week but we are getting many errors one after another because of the version issues. Here I am sharing a short piece of log
WARNING	o.j.p.workflow.graph.FlowNode#persistSafe: failed to save actions for FlowNode id=2 java.lang.reflect.InaccessibleObjectException: Unable to make field private static final long java.lang.Throwable.serialVersionUID accessible: module java.base does not "opens java.lang" to unnamed module @[54](https://github.com/<Org-name>/bai_test_jfr_compatibility/runs/7739653449?check_suite_focus=true#step:3:55)f5f647 	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354) 	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297) 	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:180) 	at java.base/java.lang.reflect.Field.setAccessible(Field.java:174) 	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildDictionaryEntryForClass(FieldDictionary.java:176) 	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:142) 	at
Actual Results
Everytime we solve one issue regarding version another one pops up, so unable to share any particular issue. For the time being sharing the issues showed up the last time.
WARNING	o.j.p.workflow.graph.FlowNode#persistSafe: failed to save actions for FlowNode id=2 java.lang.reflect.InaccessibleObjectException: Unable to make field private static final long java.lang.Throwable.serialVersionUID accessible: module java.base does not "opens java.lang" to unnamed module @[54](https://github.com/<Org-name>/bai_test_jfr_compatibility/runs/7739653449?check_suite_focus=true#step:3:55)f5f647 	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354) 	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297) 	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:180) 	at java.base/java.lang.reflect.Field.setAccessible(Field.java:174) 	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildDictionaryEntryForClass(FieldDictionary.java:176) 	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:142) 	at
Anything else?

It's an sincere request to update the versions and release a new package if possible. If the underlying procedures to release a package then please provide the step by step guide on how to build package and use it locally, we will do the rest.
Please improve the documentation according to linux/windows both and many more tiny bits of information like how plugins gets picked up, how to update the latest plugins, commands etc because it was tedious to internal architecture.
Please add the steps on how to lunch the UI and use it properly.

Requesting help from the maintainers as well as @lucaspanjer @cris @cowboyd @vbehar @trondn @oleg-nenashev
Thanks

It should land after https://github.com/jenkinsci/jenkinsfile-runner/pull/640

#640 is merged, is anything else blocking a new release?
This is preventing us from testing with the same versions that we use in our Jenkins deployments.

Nothing was blocking except me being underwater with the personal and work stuff. I will try to release it ASAP

A colleague of mine just reported a plugin compatibility issue.
I told him to wait for this.
Is there anything we can do to assist?

@lhupfeldt good question. I think we should be okay, will try to release in the coming days.
The project needs more contributors and co-maintainers

@oleg-nenashev Any ETA on the release?

@oleg-nenashev Any issues with the release? Can we help?

looking forward for this!

same here, it becomes a blocking issue. I am sure, we all don't want pushing you @oleg-nenashev and understand you have other activities, but It would be good to clearly know whether this repository is abandoned or not.  It is important to know, if we should take actions to find a different solution or this repo is a perspective long-term solution. If yes, the regular upgrade and maintenance plan is the basic requirement.
What are your thoughts on this?

@mcambal The repository is not abandoned but I've been on a long sabbatical as it was announced in the developer mailing list and other channels (war in Ukraine, parenting and other personal reasons). I'm always interested in having co-maintainers, and everyone is welcome to participate in this project
Going back to the issue, it should be somewhat addressed in https://github.com/jenkinsci/jenkinsfile-runner/releases/tag/1.0-beta-31 . There are likely many issues with the release, and everyone is welcome to test it out and to share their feedback


Adopt changes to uDiscovery

uProtocol spec v1.6.0-alpha.4 introduced some breaking changes to the uDiscovery service interface.
These changes need to be adopted in up-rust.

closed via 0577c28d6aac46cbbf80e072b9f2e9aae7a227cc


Remove comments

Signed-off-by: Uilian Ries<EMAIL_ADDRESS>

Conan v1 pipeline
Failure in build 1 (f8fb2bc5aa93fe7399c8ad96a9bb288fab7c7311):
An unexpected error happened and has been reported. Help is on its way! :horse_racing:

Conan v1 pipeline
Failure in build 2 (3a2cd4433e1ea01774dd39fbf5a769fa167e32e7):
An unexpected error happened and has been reported. Help is on its way! :horse_racing:

Conan v1 pipeline
All green in build 3 (3a2cd4433e1ea01774dd39fbf5a769fa167e32e7):

zlib/1.2.11@:
All packages built successfully! (All logs)

Conan v1 pipeline
Failure in build 5 (3a2cd4433e1ea01774dd39fbf5a769fa167e32e7):

zlib/1.2.11@:
A timeout occurred when trying to process Conan test package. The infrastructure team has been notified and will take care of it.

Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability.


Generate versioned URLs in the docsite for the latest version

Currently the docsite keeps versioned URLs for all articles for old versions (e.g. https://docs.zeppelinos.org/docs/1.4.0/setup.html), but not for the latest one. As such, there is no way to link to an article fixed to the current version (for instance, when trying to link a doc from the CLI).

Fixed in new docsite


WARNING: Consider using -Interactive instead

Notice: if you use multi-factor authentication on your tenant, use
PowerShell
Connect-PnPOnline -Url https://yoursite.sharepoint.com -UseWebLogin

It prompts: "WARNING: Consider using -Interactive instead, which provides better functionality. See the documentation at https://pnp.github.io/powershell/cmdlets/Connect-PnPOnline.html#interactive-login-for-multi-factor-authentication" when running the command line. So which exactly do you recommend?
Thanks!

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

ID: 5e257652-6b19-287b-7f39-21c2a0909c09
Version Independent ID: 10c59abb-83b5-1ae4-2008-0a53e9ca952e
Content: PnP PowerShell Overview
Content Source: sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: pamgreen

Hello @Peter-Wxin
how are you?
Even though the PnP documentation articles are on this repository, I need to kindly redirect you to open PnP cmdlets issues/pull requests here, in that repository, where a member of the PnP community will be able to correct the article/review your PR with your feedback.
The documentation for PnP cmdlets is then synced from that repo into this one.
Thank you!


PROD-299/deck-completion-screen

Description
Updates in deck completion screen ui
What are the steps to test that this code is working?
1.Share button functionality
2.Next Deck functionality
Next Deck + arrow icon: next deck in campaign (if one exists) else
Next Deck + arrow icon: next any active deck  (if one exists) else
Go home (if no active deck exists)
Screen shots or recordings for UI changes

Also merge conflicts fyi @yash431garg

Also merge conflicts fyi @yash431garg

Just resolved them.

@yash431garg please add corresponding env var to preview only for now in Vercel. We will use a different link that is not yet ready in prod.

@yash431garg please add corresponding env var to preview only for now in Vercel. We will use a different link that is not yet ready in prod.

Done

@yash431garg build is failing

i added some design comments in vercel.
might be out of scope for this PR but can you investigate why going "Back" from the subsequent DeckInfo card deck screen goes home and not back to the previous deck completion screen? i would expect that the Back buton in this case would direct back to the previous deck. and since that deck was completed, it should show the deck completion screen.

i added some design comments in vercel.
might be out of scope for this PR but can you investigate why going "Back" from the subsequent DeckInfo card deck screen goes home and not back to the previous deck completion screen? i would expect that the Back buton in this case would direct back to the previous deck. and since that deck was completed, it should show the deck completion screen.

@Yihwan this is already been done in th other PR. You will be can test that in main or in the mentioned PR.
Ref: https://github.com/gator-labs/chomp/pull/524


Update scalaz-zio, ... to 0.6.1

Updates

org.scalaz:scalaz-zio
org.scalaz:scalaz-zio-interop-cats

from 0.6.0 to 0.6.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

Codecov Report

Merging #172 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #172   +/-   ##
=======================================
  Coverage   97.72%   97.72%
=======================================
  Files          15       15
  Lines         176      176
  Branches        2        2
=======================================
  Hits          172      172
  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 8533178...0cef671. Read the comment docs.


create unit tests for terraform client

will be useful and should be merged to js-sdk soon too

Status Update:
Happy path tests were implemetd here https://github.com/threefoldtech/owncloud_deployer/commit/a5f727beb019aa0ab389d85597d30611c7a232e5

Status Update:
Initial sad path tests were implemented here https://github.com/threefoldtech/owncloud_deployer/commit/13d5890959a6c710a3e3252c80738af4ebc85c59


Change git-checkout depth default to 1

Deep cloning can cost a lot of time on a per-dev-cycle basis. This changes the default depth to 1 — and it can still be adjusted to any number on a per-build-config basis as needed.

I went looking to see if anything sets depth: today, and the only ones that do, argon2 and ffmpeg, use it to set depth: 1.
We might find some other builds that fail because they'd assumed a depth >1 in their build, and we won't find them until we bump their epochs or do a world-rebuild. That seems pretty unlikely though, and the fix is to just change depth: 50 again (and remember that's a thing we might want to do).
+1


tor is apparently built without libseccomp, breaking its Sandbox setting

Describe the bug
L: Running Tor with sandbox enabled will make it emit the message [warn] This version of Tor was built without support for sandboxing. To build with support for sandboxing on Linux, you must have libseccomp and its necessary header files (e.g. seccomp.h).
Steps To Reproduce
Steps to reproduce the behavior:

Put this in configuration.nix:

{
  services.tor = {
    enable = true;
    settings.Sandbox = true;
  };
}

nixos-rebuild switch
journalctl -u tor.service

Expected behavior
Tor shouldn't complain about missing libseccomp, and the sandbox setting should make it sandbox itself.
Additional context
AIUI, seccomp does syscall filtering, so it might be possible to reproduce similar functionality with systemd's per-unit syscall filter, but uh, Tor's own sandbox would be more appropriate, as it would have a filter that's customized to Tor's needs specifically, and also work when calling manually (especially relevant on non-NixOS platforms), or with custom systemd units.
Notify maintainers
@thoughtpolice @joachifm @prusnak
Metadata

system: "aarch64-linux"
host os: Linux 5.15.67-hardened1, NixOS, 22.11 (Raccoon), 22.11pre411613.7e52b35fe98
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.11.0
channels(root): "nixos"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

According to tor/default.nix:
# sandbox is broken on aarch64-linux https://gitlab.torproject.org/tpo/core/tor/-/issues/40599

L: Oh, alright. Didn't actually check the Nix file, sorry.  Seems like latest release (0.4.7) doesn't have the fix yet ‒ commits from https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/574/commits haven't arrived in https://gitlab.torproject.org/tpo/core/tor/-/commits/release-0.4.7/src/lib/sandbox/sandbox.c yet.


include the name of the calling method in RPC errors

Include the name of the calling method in RPC errors.

(TBR)


[Catalog] Missing Descriptions

Catalog items are missing descriptions
Contributor Resources
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

I want to work on this issue .  can you assign this issue to me.


feat: support styling for heading link

This PR enhances the documentation by adding clickable anchor links to each heading (h1 & h2).
Currently, while anchor links are generated via rehypeAutolinkHeadings, they are not accessible due to missing styles. This makes it difficult for users to obtain direct links to specific headings, hindering navigation and sharing.
Below is the example scenario, where I wanted to share useSidebar. Which as mentioned, is already a valid link but had no entry point.

Thanks so much for ShadCN!! ❤

oh thanks. that looks great. do you think we could make the heading itself clickable? easy?

oh thanks. that looks great. do you think we could make the heading itself clickable? easy?

@shadcn Updated!


The current release is broken with the latest parsedown version

25 Days ago, the internal structure of some elements was changed. This broke this library in multiple places.
The fix for it was added 9 Days ago, but this is not yet available over composer.
That means, the latest versions of parsedown and parsedown-extra are not compatible. I realize that the current 1.8 release of parsedown is a beta release, but it doesn't say that it's incompatible anywhere.

That means, the latest versions of parsedown and parsedown-extra are not compatible.

The latest release of Parsedown is 1.7.1, a stable version of 1.8 hasn't yet been released:

I realize that the current 1.8 release of parsedown is a beta release, but it doesn't say that it's incompatible anywhere.

I hate to be that guy, but... like... it's marked as a pre-release. I'm not sure what you expect? A pre-release almost certainly going to have issues in it – the whole point in labelling it like this is to distinguish it from a stable release.

As far as I know, composer and packagist should take note of the pre-release flag and won't auto-update anything.
For example:

I even tried locally cloning the repo you referenced this issue from, and Parsedown 1.7.1 (latest stable) is still being downloaded.

The fix for it was added 9 Days ago, but this is not yet available over composer.

This is true, I'll probably release a similar beta for Parsedown-extra once the second beta for Parsedown goes out. This will be for the sole purpose of encouraging testing though, so people can file any bugs they find. Please don't rely on beta releases for stuff that you would like to work.
Generally the best way to avoid these kinds of stability issues is to avoid pre-release software. I'm a little stumped as to how you could have managed to install this accidentally, unless you're explicitly asking composer to install an unstable version?

but... like... it's marked as a pre-release.

Yes, you're right. However, composer did auto-update to the beta-release (for me and everyone in the linked issue).
The issue was actually that the composer-template for Craft CMS (which is the root-project) had "minimum-stability": "beta" in it's composer.json file, which caused it to update to the beta-release.
Sorry for causing any headache, I just found this today. Thanks for responding anyways! I'm closing this, as the problem is resolved.


Store tests seem to check wrong address

After performing the store, a load is performed from resultdata, while the store stores to testdata. Not sure what the intent is, but the current behavior doesn't actually check the result of the stores.

Hmmm, I'll take a look tomorrow. Thanks!

Fixed above. The la a0, resultdata is put into the wrong place:
# Move a0 to test data area.
la a0, testdata
li a5, 160
add a0, a0, a5

# Load data into v1 register group.
li t0, -1
vsetvli t1, t0, e8,m1,ta,ma
vle8.v v1, (a0)

+ la a0, resultdata
# -------------- TEST BEGIN --------------
li t0, 32
vsetvli t1, t0, e8,mf8,ta,ma
vse8.v v1, (a0)
# -------------- TEST END   --------------
- la a0, resultdata

# Load data into v1 register group.
li t0, -1
vsetvli t1, t0, e8,m1,ta,ma
vle8.v v1, (a0)

Thanks!

This might affect all the store types though, including strided and indexed.

I believe I've got them all.

Thanks!


Add bundle add command to the main man page

This command added in v1.15 was not present in the main man page.

Thanks!
@bundlerbot r+


[Python] Use Py3k compatible print operator: print "foo" → print("foo")

What's in this pull request?
Use Py3k compatible print operator: print "foo" → print("foo")
Resolved bug number: –

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test


4.0 grid layout not spanning properly on PC monitor.

http://v4-alpha.getbootstrap.com/examples/grid/

If you're referring to the second to last example, that's intentional—we're clearing a float to bump columns to a new line.

Then the grid doesn't make sense to me in version 4, a sum of 12 nested or
not, no longer renders inside the container neatly as it did. I have to use
a sum of 9 or 10 to get a horizontal alignment - but it had huge margins.
I've been using BS 3.x primarily for its grid.
From: Mark Otto<EMAIL_ADDRESS>Sent: Saturday, August 22, 2015 8:36 PM
To: twbs/bootstrap<EMAIL_ADDRESS>Cc: Ward305<EMAIL_ADDRESS>Subject: Re: [bootstrap] 4.0 grid layout not spanning properly on PC
monitor. (#17237)
If you're referring to the second to last example, that's intentional-we're
clearing a float to bump columns to a new line.

Reply to this email directly or view it on GitHub
https://github.com/twbs/bootstrap/issues/17237#issuecomment-133767695 .
<https://github.com/notifications/beacon/ANRxbM85zl7SmERIIV_8ygyqatvRzaXwks5
oqQ0IgaJpZM4Fwc1a.gif>
<https://contactmonkey.com/api/v1/tracker?cm_session=e6f83c14-608c-4471-9087
<EMAIL_ADDRESS>

Screenshot of the problem? I do see a difference in the column clearing example since v3, but a screenshot or two would help clarify what you're looking at.

I'm happy to be wrong - you guys are the experts - SEE attached screenshots - all of the examples that span more than "8" wide do not render 10 or 12 wide horizontally. These are just two. All of the examples behave this way.

Which OS and browser and browser version are you using?

Also @Ward305 what is your screen resolution?

Win7 Ultimate N - Firefox 28
Resolution 1920x1080

Could you try upgrading to a more recent version of Firefox and see if that solves the issue?

For test purposes - or as a 'fix'? - if 'fix' I'd rather stay with BS3.2 : )

As in "you're using a browser that about 1.5 years old to report a problem...let's see if the problem is with our code - though we can't reproduce at the moment - or with your browser..."

Sure - happy to temporarily update to test it.

Yes - rendering properly in Firefox 40.0.2 - > thought I got physically nauseous during that spyware update, so I'm deleting immediately for a rollback. Hope you can fix this!!! Love BS but love 28 more. Thanks.

This would suggest that the problem lies with Firefox 28. As we're not really going out of our way to ensure compatibility with very outdated versions of browsers, I'm afraid this is not going to get worked around at the Bootstrap end. /cc @mdo who may want to weigh in?

Understood - would completely agree for seriously outdated browsers like IE 8 - 9. FF 1 - 18etc.  - but FF28 not a relic and there are millions of us in the "refuse to update FF28 club"

Firefox 28 will probably meet your criteria for seriously outdated by the time V4 is actually released. It's still only in the alpha stages.

Not sure what you mean - "close to your criteria for seriously outdated by the time V4" - Meaning will be fixed for FF28 - or by time V4 is released FF28 will be too outdated?

Our support policy for Firefox is that we only support the latest Extended Support Release (ESR) version and the latest stable version, since Firefox is a modern evergreen self-updating browser. FF38 is currently the latest ESR. So FF28 is way too old for us to care about, some folks' Australis hatedom aside.

@Ward305 Could you give me some details or even better links why you not update? I am just very interested in those things. I do not know what you mean but are you sure you can not disable the spying with a setting or addon, I mean using such a old browser under windows is a security risk.

@nextgenthemes Presumably they dislike the Australis UI theme which Mozilla switched to in Firefox 29.

@cvrebert he was speaking of spyware

though I got physically nauseous during that spyware update, deleting immediately to feel better.

To me this not sounds like UI inconveniences, sounds more like Mozilla sending some data somewhere since 29+

@nextgentheses @cvrebert is correct. Firefox29 and > is less customizable and bloated with Firefox spyware. Since Bootstrap 4.x is not supporting the "real" Firefox I'm now looking for a new framework that, as they say in politics, is more 'inclusive'. I really don't get it, all the BS developers need to do is fix the one element to make it work. Weird.

@Ward305 So its both you not like Australis and some "Firefox spyware". Again could you give me details and facts about this supposed "Firefox spyware" as I am very curious. I am more and more thinking there is no such thing.

I don't think it matters to BS if is either is true... BS development has taken on the strategy of Steve Jobs. "I don't give them what they want, I give them what I think they want." Steve got away with it, a free framework can't.

This is a box-sizing problem. We're not including -moz in there, likely because of our Autoprefixer settings. I wonder if we should revisit that. I assume we're good to leave it given the low usage rates of v28, but could be worth diving into more.

Don't want to be combative - I really like BS - My main point is, why would I want to move to 4.x that will not properly render a 1 year old browser (F28) - when 3.x will render IE 8 - > how old is IE8? 6+ years old.
I get moving one from IE 8-9 support - but not 1+ year old browsers. Doesn't make good business sense to me.

Mozilla themselves no longer support Firefox 28; it doesn't get security patches or bug fixes.
Perhaps consider using Classic Theme Restorer or switching to a different Gecko-based browser.

@Ward305 Echoing what @cvrebert just mentioned, those version numbers increment very quickly via auto updates. If you don't update to get the latest performance, stability, security, etc changes, you're putting yourself in that position. Firefox autoupdates just like Chrome now, so there's significantly less risk to supporting those older versions (which according to caniuse.com is at 0.4% I think).

Again, this is not about me - it's about my visitors. Moving to BS 4.x will exclude many users from viewing my website properly.

@Ward305 Then don't move to v4. v3 will still be maintained for critical bug fixes and docs updates.

@Ward305 so you can not name any facts about your imaginative "Firefox spyware" Mozilla according to you supposedly build into Firefix with the 29 update, as I thought. Don't get me wrong I am glad if I hear up people not just taking everything without any thought. For example Stallman rightfully called Ubuntu out for having spyware build in and enabled by default. It sends all private desktop searches you make to Amazon (and maybe other Partys) and I am glad that are ppl who care about this things. https://fixubuntu.com/. Mozilla every since sends everything you search directly to google for search suggestions, I think enabled by default (Mozilla once had 40% of their funds came from google). But I am still not aware of anything like that that came with version 29.
So until you prove your claim about spyware in Firefox 29+ I think its totally ridiculous to sit on Windows 7 cough with a hopelessly outdated browser (about 1.5 years said patrick above) and then come up with the ridiculous critique of BS because you not like innovative change that totally makes sense (Australis).
The thing about the IE support is just the usage rate, not about how old the browser is, sadly more people use old IEs then people use somewhat old FF.
On top off all that cvrebert just gave you the ultimate solution: https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/, not sure if you deserve it though.

so, i think this conversation has now run its course...

Sadly it has run its course - going to learn another framework that me and my users can grow with - take care.

have fun

Alright, that was dick-ish all across the board @nextgenthemes and @patrickhlauke. Ease up on @Ward305. Regardless of the Firefox versioning and their policies, he's asking very valid and particular questions about our project. We have infinitely more context and knowledge than this person—acknowledge that and embrace it by being positive and helpful in all your comments.

@Ward305 To clarify, there's no immediate need to update to v4, for yourself or your users. v3 will be maintained moving forward so if you need those specific browsers supported, we've got you covered there.
In addition, I'd like to adjust our browser support to unofficially include the prefixes we need to fix that layout issue.

@mdo is there a timeframe for how long support for V3 will last? Curious what the EOL/EOM is for V3? If that's off topic for here though I can make a new issue if needed

Not yet @kkirsche. We'll solidify that once v4 is final. Until then, v3 will most assuredly be maintained :).

Again, this is not about me - it's about my visitors. Moving to BS 4.x will exclude many users from viewing my website properly.

If you really have so many v29 update refuser’s at visitors (I actually doubt that this "club" is that big) and are concerned about them having a wrong grid layout I would detect them and display a message to them about https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/ and encourage them to update, rather then switching the framework in this childish way. You would probably do them a favor because, as mentioned, v28 is not supported by Mozilla any-more and probably has a lot of holes for now very well known exploits, especially on windows, that is probably also on update refusal mode ;). Concerned about spyware but opening yourself up to all kinds of other stuff is pretty oxymoronic to me. Anyway I think I wasted my time here ...
@mdo And again I am the evil rude guy for my honest outspokenness. He has made up his mind anyway and now you give him what he wants, unofficial support and encourage others to use a insecure totally outdated browser ... OMG.  It happened b4, nobody is supposed to be a tiny bit rude here. Just accept every stupid decision and even help them out ... no matter if it makes sense or not, just be nice, never question and let them dig their own graves ...

@nextgenthemes You can make your point without telling someone they're being childish, ridiculous, etc. And if you don't like me being nice to someone here because you were rude, that's a-okay with me. I don't need any validation for how I choose to interact with another person.

He has made up his mind anyway and now you give him what he wants, unofficial support and encourage others to use a insecure totally outdated browser ... OMG.

You're mad I want to make sure millions of people have a minimally useable website when building on Bootstrap? The fix for the mentioned problem here is one line–-moz-box-sizing: border-box. Who cares that the browser is officially not supported? Basic layout stuff should be as in-tact as possible if we can help it easily enough.

 We're all people here trying to make stuff and I'll be damned if I let anyone's personal opinions on how to talk to people stop me from helping someone.

Just accept every stupid decision and even help them out ... no matter if it makes sense or not, just be nice, never question and let them dig their own graves ...

You might want to step back through some of our issues and PRs here. I regularly shut down ideas I don't agree with, punt folks to other more appropriate mediums, etc. We say no the vast majority of the time.

There's a lot we can't do here in our limited time we have for open source. We can, however, be welcoming and encouraging in our responses to everyone—especially folks like @Ward305 who is brand new to GitHub. We shouldn't be setting folks up to dig their own graves, we should be boosting them up.
If it's your prerogative to degrade people, be overly negative, etc, that's fine. If you don't like it, just leave. I have zero patience for folks being jerks to others here, especially brand new users, and want none of it in this community.

@mdo Thank you for the professional reply and explanation. Perhaps I should have framed my original inquiry as a concern for maximizing return visits to my website, rather than for "my browser". My initial thought was if 4 does not work in a relatively new browser, what other environments might it ALSO not work in. Now I get the feeling 4.x is being designed exclusively around Chrome and Chrome cloans ->FF29+. Which many users do not like to put it nicely. Only because they do not like the UI of course, not because Google or its cloans would ever tracks clicks, preposterous anyone would think that.
Jokes aside.. If I might ask one last question - is it possible for me to add "moz-box-sizing: border-box" myself? I only attend parties I'm invited to, so if not possible, no worries. Thanks again!

is it possible for me to add "moz-box-sizing: border-box" myself?

Yes, you could either tweak the Autoprefixer settings or manually add a -moz-prefixed copy of the box-sizing: border-box reset. It won't interfere with or break anything.

@Ward305 Yup, what @cvrebert said :).
And FWIW, whatever your preferences on specific browsers, you'll want to research some current browser trends, your own site's analytics, etc to find out what kind of browser support you need <3.

Never got around to making any changes here. Once we hit beta we'll audit this a little closer as folks star to use v4 in more production environments.


get vmid of current machine

I'm a total newb with regards to terraform, using terraform-provider-proxmox is my first attempt at it so there may be a terraform way to accomplish what I want.
In my cluster I use the vmid to assign a static ip address. So if test1 has vmid=123 then I use static ip <IP_ADDRESS>.
When creating a new machine (vmid=0) I'd like to have something along the lines of:
ipconfig0 = "ip=10.1.1.{vmid}/24,gw=<IP_ADDRESS>"

So is there way to get what I want, or make a vm in two steps and regenerate the cloud-init drive in stage two or something completely different?
Similarily, if vmid is 0 then how do you prevent terraform from forever recreating the machine? I currently have
lifecycle {
    ignore_changes  = [ vmid ]
}

but that doesn't seem right...
Thanks for providing this plugin, even if I can't get to nirvana it will still save me a lot clicking around in Proxmox.

Hey @kneufeld welcome to terraform!  :tada:   Glad to hear you're trying it out.
First, I just want to clarify that vmid here is going to be what we attempt to set the vmid to in proxmox.  If there is a VM that already exists with that vmid this will probably go poorly.  At best we'll throw an error, at worst, we'll alter that VM directly which may not be what you want.  Just a friendly warning to be careful with what already exists in your environment!   Also, it's worth noting that setting a vmid before 100 is not supported by proxmox as far as I know.
As you suspect, you'll need two steps here as you will not have access to the VM's computed vmid until after the machine is created if you use the proxmox_vm_qemu alone.  That first step though could simply be a local block like this:
locals {
  vms = {110 = {"name" = "vm110"}, 111 = {"name" = "vm111" }}
}

resource "proxmox_vm_qemu" "simpletest" {
  for_each = local.vms

  vmid = each.key
  name = each.value["name"]
  target_node = "testproxmox"
  clone = "pxtest-10-test"
  ipconfig0 = "ip=10.1.1.${each.key}/24,gw=<IP_ADDRESS>"
  disk {
    size = "50G"
    type = "scsi"
    storage = "local-lvm"
  }
}

That'll allow you to simply define the block in locals and then terraform will generate the rest!   Does this get close to what you're looking for?

Thanks for the reply.
Unfortunately it doesn't do what I'm looking for because you have to know in advance the vmid that you're creating. If you use vmid=0 the "next" one is chosen, which is what I want, and I want to use that unknown-vmid-at-apply-time in the resource block.

@kneufeld  I had a similar use case where I needed vmid to hit proxmox API to retrieve the dhcp assigned IP address without cloud-init set up. this provider outputs the proxmox API's qemu machine endpoint as proxmox_vm_qemu.<your_resource_name>.id which is like <proxmox_target_nname>/qemu/<vmid>.
You can cut out the vmid part by using terraform string functions.

mother in hell j'ai pas pensé
De: "akadoya"<EMAIL_ADDRESS>À: "Telmate/terraform-provider-proxmox"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Envoyé: Mardi 17 Novembre 2020 14:30:30
Objet: Re: [Telmate/terraform-provider-proxmox] get vmid of current machine (#254)
[ https://github.com/kneufeld | @kneufeld ] I had a similar use case where I needed vmid to hit proxmox API to retrieve the dhcp assigned IP address without cloud-init set up. this provider outputs the proxmox API's qemu machine endpoint as proxmox_vm_qemu.<your_resource_name>.id which is like <proxmox_target_nname>/qemu/ .
You can cut out the vmid part by using terraform string functions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ https://github.com/Telmate/terraform-provider-proxmox/issues/254#issuecomment-728663687 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ACJ2BS3TODYDGOE6XLX56I3SQHU5NANCNFSM4TVV4S4A | unsubscribe ] .

Thanks @akadoya for the suggestion but I think I'm not understanding something. When I try something like:
resource "proxmox_vm_qemu" "cloudhost" {
...
  vmd = proxmox_vm_qemu.cloudhost.id
...
}

I get terraform error
terraform plan
...
Error: Self-referential block

  on infra/cloudhost/cloudhost.tf line 19, in resource "proxmox_vm_qemu" "cloudhost":
  19:   vmid = proxmox_vm_qemu.cloudhost.id

Configuration for proxmox_vm_qemu.cloudhost may not refer to itself.

@kneufeld what you're asking is not possible with terraform in general, there is no way to reference to a "self" attribute in a terraform resource
https://www.terraform.io/docs/configuration-0-11/interpolation.html
referencing to self is possible only in a provisioner
a solution for your problem would be to create a "proxmo_vmid_qemu" resource to be used in a "proxmox_vm_qemu" but thir require some work on the proxmox-api-go and on this provisioner
if you dont mind the extra work, create an output like(remember also to set a placeholder ip config to some unused ip)
output "vm_id" {
  value = proxmox_vm_qemu.<your_resource_name>.vmid
}

and run the .tf again updating vmid and ip config manually

@mleone87 Thanks for that. Yeah, what I've been doing is starting to make a new vm in proxmox to see which vmid is "next". Then I pass that vmid as a variable to my cloudhost resource.
Thanks for everybody's help, closing.


Const correctness.

There are various places within the API/code that should be marked as const.
TODO/TASK: find those
First of all, this is better style. Second of all, it signals more clearly to API users what to expect, especially for language bindings with more strict const enforcement than C.

It also helps automatic ffi generators use the correct types. I have rust bindgen in mind.


ESC GA Blog

To do

Update per feedback
Add Engin demo
Add links to sync and vs code blogs

Moving this blog