Cannot change type or rename attribute((unused)) arguments using key bindings

9.2 / windows 10
I think the title is the issue I'm coming across,
I have a function table where they all have the same prototype, but the first argument is unused in most of the functions and will be undefined4 param_1.  I cannot ctrl+l or l that argument when it is unused.
I can edit the signature and change there successfully, and then the key bindings work again on the bad argument.
I can edit another argument and then the key binding work again on the bad argument.

https://github.com/NationalSecurityAgency/ghidra/blob/2b08598dbabe6a9c911e712bd928e5f84fb00ee8/Ghidra/Features/Decompiler/src/main/java/ghidra/app/decompiler/ClangVariableDecl.java#L53
returns null instead of a ghidra.program.model.pcode.HighParam, guess restoreFromXML isn't called for param_1 until something changes in the other params

https://github.com/NationalSecurityAgency/ghidra/blob/2b08598dbabe6a9c911e712bd928e5f84fb00ee8/Ghidra/Features/Decompiler/src/main/java/ghidra/app/decompiler/ClangVariableDecl.java#L53
returns null instead of a ghidra.program.model.pcode.HighParam, guess restoreFromXML isn't called for param_1 until something changes in the other params


Will Lammps give the wrong results for finite T?

The energy function is labeled get_potential_energy_from_lammps but internally uses lmp.interactive_energy_tot_getter(). All our tests are at 0K so I don't think the problem simply hasn't come up yet, but I suspect this needs to be lmp.interactive_energy_pot_getter()

Bump

I don't know when this got fixed, but now it's pointing to the right function


weaving in practical guide from moz study groups

I'm really excited about this project and would love to help development here.
Perhaps it's already been suggested, but there's also a little outline for an Open Science Utility Belt or Primer, developed by @BillMills.
Would love to help or add a label to this issue but sadly I that isn't an option, maybe because I'm not a core contributors; anyway, great work!

Thanks @auremoser haven't seen that yet! Don't have a label for it, but it definitely belongs to our "Check out what's already there" issue #5 !

Cool, let us know how we can help. We've developed a template for curriculum on gh-pages that we used for our working open curriculum:
repo
homepage/site
lesson handout example
I also forked it for Space Apps 2016, and of of our community members did the same for his github account. Super easy, happy to help adapt that when you're ready with your outline. :) No pressure though.

yes, we used your great WOW resource extensively for our PERSONAS, Code of Conduct etc. (@kaythaney suggested it also already: #30).
But this gh-pages fork is very cool. Actually, creating a website is one of our future goals (#16) ;-).

Hurray!

@auremoser, I think you're WOW course is under CC-BY, however we want to have all our stuff under CC0 (https://github.com/OKScienceDE/Open_Science_101#license) to make it as open as possible. So we can't just fork your gh-pages, but we'll definitely put it to our ideas collection! Thanks again!

Oh I'm sorry, @aleimba, but thanks for considering it.


Missed score -> Bayes factors in one function

Might want to wait on merging this in since I may make additional changes.

I think I've made all the changes I planned on to this; feel free to rebase. Once we're both comfortable with the docs and API in this repo, I'll tag a version, and push to NPM as part of broader release prep.

No other changes currently planned on my end, aside from a final readthrough of docs- care to rebase and prep this for merge?
My goal is to consolidate this (and have a tagged NPM version pushed) by Wednesday, in tandem with the credible sets example in LocusZoom. One more feature pending for the annotation track, but otherwise I'm currently in the polish and unit testing / review phase on both sides. I can move sooner or later depending on how formal a release we want to push out.

I added a little more description of the method under docs/method/, which was the easy part.
The other changes are a little more complicated. You may want to check out this branch specifically locally to see what changed before merging in.
I made an attempt to get the paths for everything to work correctly whether viewed on github or viewed from the docs/ folder, which was the main issue. But I don't think it quite worked out for the timings link. The symbolic link doesn't resolve for some reason (though it seems to work fine in another test repo of mine, so I'm not sure what the difference is here.) Don't know of a solution other than just moving the file under docs/ instead of test/timings/.

Should have said - if you're happy with these changes, go ahead and merge in, I think this should do it from my end. You should also have commit access to this branch if you want to make any changes and then rebase this back onto develop/master.
When you've got things all patched and ready on Weds, we could send to Mike/Goncalo for a final look before shipping it off, probably on Thurs or Friday.


Add input prefix and suffix

What
Adds prefix and suffix elements to the input component.
Why
A number of local and departmental design systems (GOV.UK Publishing Components, HMRC, MOJ and ONS) are using prefixes and suffixes to indicate currencies and measurements.
Examples
Prefix
HTML

    Amount

    £
    <input class="govuk-input" id="input-with-prefix-attribute" name="amount" type="number">

Macro
{% from "input/macro.njk" import govukInput %}

{{ govukInput({
  "label": {
    "text": "Amount"
  },
  "id": "input-with-prefix-attribute",
  "name": "amount",
  "type": "number",
  "prefix": {
    "text": "£"
  }
}) }}

Suffix
HTML

    Weight

    <input class="govuk-input" id="input-with-suffix-attribute" name="weight" type="number">
    kg

Macro
{% from "input/macro.njk" import govukInput %}

{{ govukInput({
  "label": {
    "text": "Weight"
  },
  "id": "input-with-suffix-attribute",
  "name": "weight",
  "type": "number",
  "suffix": {
    "text": "kg"
  }
}) }}

Fixes https://github.com/alphagov/govuk-frontend/issues/1915

This work was reviewed by the Working Group in June, see https://github.com/alphagov/govuk-design-system/pull/1269#issuecomment-654282576 for their comments.

Implements the design for very narrow viewports. It only kicks in at 320px so I think that it's most likely to be seen by users who zoom in on a mobile device. I've tested this using the 'Aa' zoom button on iOS Safari:

I've also tried to increase text scaling on Android Chrome but it mainly seems to work for text like paragraphs and headings, it doesn't do anything for form elements for instance. I'll raise a separate issue to investigate that.
Tested on
✅ IE8 (See commit for details)
❓ IE9 (Doesn't support flex so some borders are incorrectly removed, however number of IE9 users is abysmally small so I'm not worried about it)
✅ IE10
✅ IE11
✅ Windows 10 Edge 84
✅ Android 10 - Samsung galaxy S20: FF, Chrome, Samsung Internet
✅ Android 6 - Galaxy S7: FF, Chrome
✅ iOS 13 - iPhone XS: Safari
✅ iOS 11 - iPhone 6S: Safari and FF
✅ iOS 9 - iPhone 6S: Safari and FF
❓ iOS 8 - iPhone 6S: Safari and FF (Things aren't quite correctly aligned, probably a flex issue)
❌ iOS 7 - iPhone 5: Safari (Things aren't quite correctly aligned and the suffix drops onto next line - but this is way outside our support matrix and the component is still usable)
✅ MacOS Safari 13.1
✅ MacOS Firefox 80.0 with inverted colours
✅ MacOS Chrome 84
✅ Windows 10 Firefox 80.0
✅ Windows 10 Edge 84

We want to hold off merging this until we're ready to start on 4.0.

I'll also need to draft something for the changelog, will do that shortly

Minor, but can we have at least one example that does not use an input width modifier? This will allow us to verify that the input is unconstrained and 'full-width' by default.
Possibly most of the examples should omit the width modifier? In the same way the National Insurance Number examples are 'full-width' even though in real world usage you'd expect them to be constrained… most of the examples should probably combine the minimum number of 'features' possible? Although we would then want some examples that show that they do combine properly…

@36degrees I don't know if you saw the feedback from @christopherthomasdesign which the change with the width modifiers was in response to?
But maybe we mainly shouldn't use the width modifiers in the review app as the examples are out of context anyway..? Let me know if you have any thought on that. Definitely happy to include some examples without width modifiers in either case.

@36degrees I don't know if you saw the feedback from @christopherthomasdesign which the change with the width modifiers was in response to?

Yep, I did – and completely agree for the examples in the Design System.

But maybe we mainly shouldn't use the width modifiers in the review app as the examples are out of context anyway..? Let me know if you have any thought on that. Definitely happy to include some examples without width modifiers in either case.

I think generally we use examples that are focused on only the specific feature, and don't 'enable' anything else – for example, the National Insurance Number examples don't include the spellcheck attribute, the example that enables isPageHeading doesn't also add a class to style it (though I think we might be missing some examples for each label size!)

That all makes sense 👍
However if you remove the width modifiers altogether you end up with this that to my eye looks pretty strange (I hadn't realised this up until point either):

Or is it just me and they actually look okay like that? I've been staring at them for so long over the past weeks that I can't tell anymore 😆

That all makes sense 👍
However if you remove the width modifiers altogether you end up with this that to my eye looks pretty strange (I hadn't realised this up until point either):

Or is it just me and they actually look okay like that? I've been staring at them for so long over the past weeks that I can't tell anymore 😆

Do these end up showing in a 2/3 column grid?

Do these end up showing in a 2/3 column grid?

They get constrained by the grid so like I said I think we're okay.

Massive thanks for all the amazing work by @simonwhatley and his team on this component 🎉🙏


Include JDK 21 in default EA list

Similar to:

https://github.com/oracle-actions/setup-java/issues/28

PR proposed:

https://github.com/oracle-actions/setup-java/pull/52

JDK 21-ea is now the latest-and-greatest EA release.
https://github.com/oracle-actions/setup-java/commit/97e07b6a4da03199135682817687f2ae49ecc6c9
Resolved via #52


Consider parameterized structs

You might find it convenient to use:
struct State{T}
    st::Array{T,1}
    ope::Op
end

rather than having hardcoded real and complex types. (Note also that you don' need a trailing ; after the definition.

I just made the changes you suggested. It looks much cleaner know. Thank you for the suggestion!

I will try to do the same with State and State Sparse, altough I think it is more complicated

You can try something like this:
using SparseArrays

struct Op
    n::Int
end

struct State{T<:AbstractVector}
    st::T
    ope::Op
end

julia> st1 = State(spzeros(3), Op(4))
State{SparseVector{Float64, Int64}}(3-element SparseVector{Float64, Int64} with 0 stored entries, Op(4))

julia> st2 = State(zeros(3), Op(4))
State{Vector{Float64}}([0.0, 0.0, 0.0], Op(4))

julia> st3 = State(zeros(Complex{Float64},3), Op(4))
State{Vector{ComplexF64}}(ComplexF64[0.0 + 0.0im, 0.0 + 0.0im, 0.0 + 0.0im], Op(4))

There are several packages that have some ideas about this. For example FillArrays.jl

Just done this as well. Much appreciate your advice!  :)
I will finally try to remove the necessity for a State_fixed struct, but this case is a little bit different, as I would porbably need to add an optional argument in the construction of the Struct and make bigger changes to some methods.

I was able to build the whole program with just a single Struct for State. I fusioned State and State_fixed with a mutable struct like this:
`mutable struct State{T<:AbstractVector}
st::T
ope::Op
nume::Union{Int64,Missing}
end
function State(st,ope;nume=missing)
return State(st,ope,nume)
end`
Once again, thanks for remarking this issue. I will rewrite the examples in the following days. Hopefully the package is much clearer now.

Great to hear. The last fusion is not as clear of an advantage as the others.  When you go from immutable to mutable, you lose some safety and lose some chances for the compiler to optimize behind the scenes. But, sometimes the flexibility is worth it.

I didn't know about that. I will look into these problems and see wheter or not to use mutable structs.
This is my first project with Julia, so I find really helpful all your feedback!

I ended up going back to unmutable structs.  Once again, really appreciate your advice.
I will close this issue now.


Support ssh url as destination

git copy git-copy git@github.com:cybertk/git-copy.git
/usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:867:in `scheme=': Invalid scheme format<EMAIL_ADDRESS>(Addressable::URI::InvalidURIError)
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:795:in `block in initialize'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:2302:in `call'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:2302:in `defer_validation'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:792:in `initialize'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:135:in `new'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/addressable-2.4.0/lib/addressable/uri.rb:135:in `parse'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/git-copy-0.2.1/lib/git-copy.rb:12:in `copy'
	from /usr/local/var/rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/git-copy-0.2.1/bin/git-copy:30:in `<top (required)>'
	from /usr/local/var/rbenv/versions/2.2.3/bin/git-copy:23:in `load'
	from /usr/local/var/rbenv/versions/2.2.3/bin/git-copy:23:in `<main>'

git remote add mirror git-copy git@github.com:cybertk/git-copy.git then git push --mirror works fine.


text looks crappy on IE9 (svg)

Win7 Home Premium, 64-bit, 6.2 (Build 7600)
IE 9.0.8112.16421 (update 9.0.12)
Beer's Law Lab 1.0.0 (renderer:svg)
See attached screenshot. Text looks awful.

we no longer support IE9, closing


Can't create an order

Hi! i tried to create an order based on your examples, but i got an error.
My code:
 const hitbtc = require('hitbtc-node-sdk');
 hitbtc.auth(APIKey, SecretKey);

/* or Market order */
orderParamsObject = {
    symbol: "ETHBTC",
    side: "sell",
    type: "market",
    quantity: 0.063

};

hitbtc.createNewOrder(orderParamsObject)
    .then(orderRequest => console.log(orderRequest))
    .catch(orderError => console.log(orderError));

Error:
querystring.js:43
return str.replace(/[!'()*]/g, function (c) {
^
TypeError: str.replace is not a function

Hi! Thank you.
I guess the issue fixed.
https://github.com/oleg6k/hitbtc-node-sdk/commit/3630c66c13697b00776b5db3004253a395d8c022


Fluid examples: tests don't run on Linux

On Linux:
git clone https://github.com/microsoft/FluidExamples.git
cd into any example
run start test

 npm run test fails on Linux/WSL ~/Code/fluid-projects/FluidExamples/brainstorm/node_modules/puppeteer/.local-chromium/linux-686378/chrome-linux/chrome: error while loading shared libraries: libXcursor.so.1: cannot open shared object file: No such file or directory

Closing this old issue.


Use enqueueMap/Unmap instead of enqueueWrite/Read when interesting

For future me
Possible speed optimisation and API simplification on host<->device memory copy:
Current data transfer between host and device is done using enqueueWriteX() and enqueueReadX(), with X as Buffer or Image. Their call and usage can be observed in cleGPU::WriteMemory() and cleGPU::ReadMemory()
Possible improvement to consider: replace Write/Read with Map/Unmap.
These allows to map a memory object on a device to a memory region on the host (and reverse), this could provide some speed improvement compare to read/write operations according to various sources.
The second bonus is that device-to-host or host-to-device are treated the same way, hence a single function would take care of both options.
usage to read device memory into host array:
device_mem_ptr =  queue.enqueueMapBuffer(device_mem)         // equivalent for Image
std::memcpy(host_mem_ptr, device_mem_ptr, sizeof(host_mem))  // invert host_mem_ptr and device_mem_ptr for write
int queue.enqueueUnmapMemObject(device_mem, device_mem_ptr)

Though we now replace 1 operation (read or write) by 3 (map, copy, unmap), we could have a relevant speed gain (from "OpenCL in action" book).

Not urgent, but to do at some point because ... why not more speed :clown_face:
EDIT:
More into the difference here, Read/Write imply data movement from and to OpenCL Buffer while Map/Unmap gives access to the underlying data of the Buffer without copy.
Read/Write is more efficient for small data when copy cost is smaller than enqueuing operations as Map/Unmap require more actions.
Some benchmark could tell us when is it worth it to switch from one to an other automatically.

Operation have been introduced in the code, yet further testing is required to understand usage and how to gain speed from it.
For now,
Current hypothesis is we should not Map and Unmap memories to re-Map it after:
push() -> map / copy to device / unmap
pull() -> map / copy to host / unmap

But only map/unmap once per usage:
push() -> map / copy to device / return the mapped pointer
pull(map pointer) -> copy to host / unmap

This would change the processing structure and is going out of the scope of the development for now.
Issue will be closed for now.


Build files because of missing code

I have built the files because of missing code in the latest version.
The code was already available in the src files, but not in the dist files.

@denniszon thanks


Electron segfaults under glibc 2.28 on arch linux (how to fix!)

Description
This isn't a nativefier issue per se, but rather an issue with how electron was compiled for linux and the new glibc 2.28 on arch linux
If you upgrade glibc you will get a segmentation fault when you launch any app created with nativefier, but you can fix it by patching it with the older version
Steps to reproduce issue
pacman -S glibc
npm i -g nativefier
nativefier https://medium.com
./medium-linux-x64/medium

Details
Resolution:
pacman -S patchelf
cd [your nativefier app]
mkdir glibc
curl -O https://archive.archlinux.org/packages/g/glibc/glibc-2.27-3-x86_64.pkg.tar.xz
tar -xJf glibc-2.27-3-x86_64.pkg.tar.xz -C glibc
patchelf --set-interpreter glibc/usr/lib/ld-linux-x86-64.so.2 [nativefier binary]
patchelf --set-rpath $(pwd):$(pwd)/glibc/usr/lib [nativefier binary]

This should allow your nativefied app to launch again.

Are you nativefying a public website?
Yes

Feature request? Have you looked at nativefier --help to see if an existing option could fit your needs?
No

Full nativefier command used to build your app:
nativefier --name Plex https://app.plex.tv/desktop

Version of Nativefier (run nativefier --version): v7.6.7

Version of node.js (run node --version): v8.11.2

OS: Arch Linux

Error message / stack trace (if any): segmentation fault

<Error message / Stack trace here>

On sites that include a file selection prompt you need to also downgrade icu, lib32-icu, and libxml2.

Thanks for the workaround 👍👍👍. That's https://github.com/electron/electron/issues/13972 . We're not going to do anything about it, just wait for Electron to fix it.

I was also able to fix this by updating to glibc 2.28-4. It seems like the issues were revered in the commit here: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/glibc&id=f2aaaac68876f6959c62ea09dcdda5d441bf4ff7
Links to packages that I updated to fix this:
http://arch.mirror.square-r00t.net/testing/os/x86_64/glibc-2.28-4-x86_64.pkg.tar.xz
http://arch.mirror.square-r00t.net/testing/os/x86_64/lib32-glibc-2.28-4-x86_64.pkg.tar.xz

@unfw This is the real fix, thanks!
wget http://arch.mirror.square-r00t.net/testing/os/x86_64/glibc-2.28-4-x86_64.pkg.tar.xz
pacman -U glibc-2.28-4-x86_64.pkg.tar.xz

glibc will be updated this way and there will be no problems anymore.

glibc-2.28-4 is now the default on Arch. This should be closed.


Track GitOpsCon '23 & Open Source Summit

This issue tracks the work for GitOpsCon '23. It was moved from KubeCon to Open Source Summit.
The North America edition will take place on May 8-9, 2023, in Vancouver, Canada.
https://events.linuxfoundation.org/cdcon-gitopscon/program/cfp/
CFP Closes: Friday, February 10 at 11:59 PM PST

Ingo to create a meeting for this week with the team.

All CFPs have been sent, so nothing else to do here from our side. Done and closed.

Both talks have been prepared and done, so this task can be closed now.


Update kubeslice-cli-demo.mdx

fix command

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Upgrades
[x] Documentation Update

Description
Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.
UI accessibility checklist
If your PR includes UI changes, please utilize this checklist:

[ ] Semantic HTML implemented?
[ ] Keyboard operability supported?
[ ] Color contrast tested?

[optional] What gif best describes this PR or how it makes you feel?

@priyank-upadhyay  - I am merging this.


RB-2.0 include/OpenColorIO/OpenColorAppHelpers.h

While compiling Olive with a build of OpenColorIO that was built from the RB-2.0 branch, I ran into an issue fixed by https://github.com/AcademySoftwareFoundation/OpenColorIO/pull/1324/commits/0eee77a61d14153053e643e5ec6cf32c84d03f29 in master:

Yes, I could have tried to override CMAKE_CXX_FLAGS to remove -Werror, which is set by CMake by default, but I don't know exactly how many flags are a part of CMAKE_CXX_FLAGS by default (I only modify CMAKE_CXX_FLAGS_[build type] if I need/want to modify the compiler flags, since I know exactly how many flags are a part of it by default, which is evident in the compiler flags in the screenshot above).

Thanks @elsandosgrande to report the problem. The fix already exists in master and that's a candidate for integration in RB-2.0.

Is there any sort of timeframe for it, or is everything still being worked out?

There are steps to follow before communicating any dates such as TSC approval, TSC content approval, back-port & merge of all selected pull requests, etc.
In case the build break is blocking for you, the fix is only to remove the extra ;

Yeah, I've already removed it; I was just wondering how long it might take for changes to be made to a release branch. It also helps to know when to undo the change so as to avoid the conflict in the Git repository, though that's not that big of an issue.
Thanks for the reply!

Fixed by PR #1378


Wrong case for filename

FoundryVtt 11.315 on Linux over Browser
Simbul's Cover Calculator 2.0.0
I get a 404 error on the file modules/simbuls-cover-calculator/scripts/modules/Migration.js
I've checked the module directory and it contains a migration.js file - so its a error on the case sensitity of the filename. Renaming it fixed the error.
The filename casing of the file inside this git repository seems correct.

Thanks, I thought I had fixed the release already but seems like the zip wasn't updated. I've created a new release to fix this issue


APEXCORE-592 Returning description field in defaultProperties during apex cli call get-app-package-info

@bhupeshchawda @tushargosavi Kindly review the changes.
Value returned Earlier
"dt.application.CouchBaseAppOutput.operator.couchbaseOuput.port.*.QUEUE_CAPACITY": "32768"
Value returned Now
"dt.application.CouchBaseAppOutput.operator.couchbaseOuput.port.*.QUEUE_CAPACITY": {
"value": "32768",
"isFinal": false,
"scope": "TRANSIENT",
"description": "Specify queue capacity for all output ports"
},

Please see my comments in JIRA.

As it is not the recommended implementation, please close this PR and open the new one with the required changes.


refactor: Use collect_breaking_versions from v2 directly in PG

Part of #638
Follow-up to #991
Pretty straightforward: instead of visiting the previously built v1 definition structure, we defer to Language::collect_breaking_changes as the definitions overlap - the breaking changes are defined as versions in which the syntax items may be evaluated differently, which means that these are exactly the versions that will be referenced for the conditional syntax item evaluation in the parser/lexer.

Thanks @OmarTawfik for the review!


Working example of securing WCF communication please

CreateClientAsync isn't being called when I follow this example.

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

ID: 35d1ffc2-b8c3-fbaf-edc4-6c378089c327
Version Independent ID: 081f8fa0-285d-ec0d-feaf-9449a90077a2
Content
Content Source
Service: service-fabric

@mattcowen Thank you for the valuable feedback. We are investigating the issue.

@mattcowen I have assigned this issue to the content author to investigate and update the doc as required.

@mattcowen
What you are trying to achieve?
Are you getting any exception?
WcfCommunicationClientFactory internally uses CommunicationClientFactoryBase. which in turn maintain client caching. We create client if client is not valid or not present in cache.

I was following the example with SSL for WCF but if you follow the docs it doesn’t work.
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-secure-communication-wcf
Regards
Matt
mob.<PHONE_NUMBER>0
email. mattcowen<EMAIL_ADDRESS>From: suchiagicha<EMAIL_ADDRESS>Sent: 19 March 2018 18:13
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Matt Cowen<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Working example of securing WCF communication please (#5164)
@mattcowenhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmattcowen&data=02|01||e93d5b1187d64c6f5c6e08d58dc516ef|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636570799981414645&sdata=onYjoOSWlUoqTDAWauN50Hm0m4ncY%2Fz2ckUWDmNbHg8%3D&reserved=0
What you are trying to achieve?
Are you getting any exception?
WcfCommunicationClientFactory internally uses CommunicationClientFactoryBase. which in turn maintain client caching. We create client if client is not valid or not present in cache.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F5164%23issuecomment-374312539&data=02|01||e93d5b1187d64c6f5c6e08d58dc516ef|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636570799981414645&sdata=%2BVSwH4sUzs24VthXmwSOkVIfS2mktoXlSbgY6KMgsIM%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGuQF6riq-Z0g1WIbn0Y-dYJ86cDeJKQks5tf_U6gaJpZM4SYOz6&data=02|01||e93d5b1187d64c6f5c6e08d58dc516ef|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636570799981570885&sdata=%2F4CWHzcj0qhEKe%2Bm%2B3mvQmSqZoxP6WmD%2FfXpraEIkeo%3D&reserved=0.

@mattcowen
Could you provide the exception you are seeing while using wcf in secure mode?

#please-close
Please re-open if you have further questions.

@mattcowen We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Remove macro or rename?

Hey, I made a macro in your MineMenu but wanted to rename it and delete a category but then I saw there is no way to do that. Or maybe I just missed it but I didn't find anything to delete category or rename a macro.
I would love to see those 2 things being added to your mod (if that doesn't exist already and I just missed it). Love your mod, thanks!

Hold Shift, when clicking the menu button in order to edit and/or delete it.


⚠ gorzdrav.org has degraded performance

In 3baa856, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 1562 ms

Resolved: gorzdrav.org performance has improved in 138bcff.


Validation Errors when publishing to the Windows App Store

Describe the bug
Validation errors when validating MRTK app for the Microsoft App store:
Failed:

Binary analyzer
Supported APIs
Debug configuration (The binary UnityRemotingWMR.dll is built in debug mode.)

To reproduce

Make a simple MRTK app
Build
Package for Microsoft Store
Run validation test

Expected behavior
Should pass the validation test
Screenshots
See summary file attached
Your Setup (please complete the following information)
ValidationResult.txt

Unity Version 2018.4.11f1
MRTK Version v2.1
VS 2017 & 2019

Target Platform (please complete the following information)

WMR immersive

Additional context

How are you building your app for the store? If you package it as a Master build, it should strip out the development binaries (like UnityRemotingWMR.dll you mention above).

How are you building your app for the store? If you package it as a Master build, it should strip out the development binaries (like UnityRemotingWMR.dll you mention above).

A lot less fails when using Unity 2019.2.11f1 and VS2019:
ValidationResult2.txt

Build from Unity
Open in *.sln in VS 2019
Publish/Associate App with thre
Publish/Create App Packages (choose option "Microsft store as ...")
Create for x64 only
Run local validation test

Update, we just received this feedback from Microsft Store certification:
API GetFileVersionInfoA in version.dll is not supported for this application type. UnityPlayer.dll calls this API.
API GetFileVersionInfoSizeA in version.dll is not supported for this application type. UnityPlayer.dll calls this API.

What does your "Select and configure packages" page look like (I got here via Create App Packages, but I assume there's a similar page via the other paths)? The architectures you're building should all be configured for Master (what you set in Unity doesn't matter here, just what's set in Visual Studio):

Yes, that's exactly the same as I had set in both versions.

fixed by changing .net compatibility

fixed by changing .net compatibility

How exactly? I have same issue.

Same issue here with Unity 2019.4.25


JS: Arrow Functions

Basic arrow function tutorial.

@SergioGutierrezVillalba
Hey, can you remove the .vscode/settings.json file and add it to the .gitignore?
Also - can you explain the latin-1 change?

I changed utf8 to latin-1, because I got this error when trying to start the application:

I have added the commit with utf8 codification and vscode removed and added to gitignore.


Add logging to signals

Fixes #195
Adapts the logging from original ophyd, puts debug messages into signal subscriptions, value changing and value reading. Logs include the device name, timestamp, old value and new value

As discussed with @coretl , this PR has been split off into https://github.com/bluesky/ophyd-async/pull/275 and https://github.com/bluesky/ophyd-async/pull/277


Anyone using this?

Is anyone using this? Would like som guidance of how to make it work.

What guidance do you need? This should still work. Although I have some improvements and notes yet unpublished.

To begin with just how to run it :)
When I execute run.py:
$ sudo python3 run.py Traceback (most recent call last):   File "run.py", line 27, in <module>     fan = Calima("58:2B:DB:01:D5:33", "04243571")   File "/home/homeassistant/.homeassistant/pycalima/pycalima/Calima.py", line 51, in __init__     self.conn = ble.Peripheral(deviceAddr=addr)   File "/usr/local/lib/python3.5/dist-packages/bluepy/btle.py", line 391, in __init__     self._connect(deviceAddr, addrType, iface)   File "/usr/local/lib/python3.5/dist-packages/bluepy/btle.py", line 439, in _connect     raise BTLEDisconnectError("Failed to connect to peripheral %s, addr type: %s" % (addr, addrType), rsp) bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral 58:2B:DB:01:D5:33, addr type: public Exception ignored in: <bound method Calima.__del__ of <pycalima.Calima.Calima object at 0x76a0f890>> Traceback (most recent call last):   File "/home/homeassistant/.homeassistant/pycalima/pycalima/Calima.py", line 55, in __del__     self.conn.disconnect() AttributeError: 'Calima' object has no attribute 'conn'

The error is a bit hidden in the trace. The interesting redout from your error is bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral 58:2B:DB:01:D5:33
Does running
sudo python3 cmdline.py -m 58:2B:DB:01:D5:33 -p "04243571" work reliably for you?
As for hassio integration. I don't run hassio myself, but it shouldn't be to hard creating a custom component as described here. Especially look at the example sensor. From there you would include pycalima and use the getters to fill the entity state.
Eg in the update function,
fan = Calima("Mac","pin")
self._state = fan.getState()

It's probably a bit more than this, but it should be the essence of it.

Wrong button...

That gives me:
$ sudo python3 cmdline.py -m 58:2B:DB:01:D5:33 -p "04243571" Traceback (most recent call last):   File "cmdline.py", line 134, in <module>     main()   File "cmdline.py", line 80, in main     fan = Calima(mac_address, pincode)   File "/home/homeassistant/.homeassistant/pycalima/pycalima/Calima.py", line 51, in __init__     self.conn = ble.Peripheral(deviceAddr=addr)   File "/usr/local/lib/python3.5/dist-packages/bluepy/btle.py", line 391, in __init__     self._connect(deviceAddr, addrType, iface)   File "/usr/local/lib/python3.5/dist-packages/bluepy/btle.py", line 439, in _connect     raise BTLEDisconnectError("Failed to connect to peripheral %s, addr type: %s" % (addr, addrType), rsp) bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral 58:2B:DB:01:D5:33, addr type: public Exception ignored in: <bound method Calima.__del__ of <pycalima.Calima.Calima object at 0x76a3b370>> Traceback (most recent call last):   File "/home/homeassistant/.homeassistant/pycalima/pycalima/Calima.py", line 55, in __del__     self.conn.disconnect() AttributeError: 'Calima' object has no attribute 'conn'
Do I need to somehow reset the fan if I had connected it to my phone previously?

What platform are you using? Can you see the fan using sudo hcitool lescan?

Ok back to this project:
I now have something working.
running: sudo python3 cmdline.py -m 58:2B:DB:01:D5:33 -p "04243571"
gives me most of the return values except for two:
sudo python3 cmdline.py -m 58:2B:DB:01:D5:33 -p "04243571" Device Name:  PAX Calima Model Number:  10 Serial Number:  0000000 Hardware Revision:  01.00 Firmware Revision:  01.03 Software Revision:  01.05 Manufacturer:  PAX Alias:  Pax Traceback (most recent call last):   File "cmdline.py", line 134, in <module>     main()   File "cmdline.py", line 110, in main     print("Factory Settings Changed: ", fan.getFactorySettingsChanged())   File "/pycalima/pycalima/Calima.py", line 174, in getFactorySettingsChanged     return bool(unpack('<I', self._readUUID(CHARACTERISTIC_FACTORY_SETTINGS_CHANGED))) struct.error: unpack requires a buffer of 4 bytes
outcommenting print("Factory Settings Changed: ", fan.getFactorySettingsChanged()) it moves on to:
sudo python3 cmdline.py -m 58:2B:DB:01:D5:33 -p "04243571" Device Name:  PAX Calima Model Number:  10 Serial Number:  0000000 Hardware Revision:  01.00 Firmware Revision:  01.03 Software Revision:  01.05 Manufacturer:  PAX Alias:  Pax Traceback (most recent call last):   File "cmdline.py", line 134, in <module>     main()   File "cmdline.py", line 111, in main     print("Mode: ", fan.getMode())   File "/pycalima/pycalima/Calima.py", line 177, in getMode     v = unpack('<H', self._readUUID(CHARACTERISTIC_MODE)) struct.error: unpack requires a buffer of 2 bytes
outcommenting print("Mode: ", fan.getMode()) as well gets me to the end of the script:
sudo python3 cmdline.py -m 58:2B:DB:01:D5:33 -p "04243571" Device Name:  PAX Calima Model Number:  10 Serial Number:  0000000 Hardware Revision:  01.00 Firmware Revision:  01.03 Software Revision:  01.05 Manufacturer:  PAX Alias:  Pax Fan Speed Settings:  Fanspeeds(Humidity=2250, Light=975, Trickle=975) Sensors Sensitivity:  Sensitivity(HumidityOn=1, Humidity=2, LightOn=0, Light=2) Light Sensor Settings:  LightSensorSettings(DelayedStart=0, RunningTime=5) Heat Distributor:  HeatDistributorSettings(TemperatureLimit=25, FanSpeedBelow=0, FanSpeedAbove=2100) Boost Mode:  BoostMode(OnOff=0, Speed=0, Seconds=0) Led:  0000 Automatic Cycles:  0 Time:  Time(DayOfWeek=6, Hour=11, Minute=7, Second=22) Silent Hours:  SilentHours(On=1, StartingHour=22, StartingMinute=0, EndingHour=6, EndingMinute=0) Trickle Days:  TrickleDays(Weekdays=1, Weekends=1) FanState(Humidity=53, Temp=26.75, Light=30, RPM=968, Mode='Trickle ventilation') FanState(Humidity=53, Temp=26.75, Light=30, RPM=967, Mode='Trickle ventilation') FanState(Humidity=53, Temp=26.75, Light=30, RPM=964, Mode='Trickle ventilation') FanState(Humidity=53, Temp=26.75, Light=30, RPM=963, Mode='Trickle ventilation') FanState(Humidity=53, Temp=26.75, Light=30, RPM=960, Mode='Trickle ventilation')

Looks like the characteristics have different lengths. Do you mind running the command below and paste the output?
sudo python3 cmdline.py -m your_mac -p "your_pin" -s

Disregard that. It's staring me right in the eyes. I will try and patch in soon!

Awesome thanks.
Btw I was running on a RPI 3B+, now moved to a RPI Zero W.
The patch seemed to work.


Update store_failures.md

What are you changing in this pull request and why?

In the docs for data tests, there's a note to clarify that store_failures replaces previous failures for a given test. This note is missing from the docs for the store_failures resource config, so this PR adds it.
Checklist

[x] Review the Content style guide so my content adheres to these guidelines.

@martanthony thank you so much for opening this PR and contributing to the dbt docs!
@matthewshaver what do you think about these proposed changes?


XML Parsing Error on Published Page

https://bottlecaps.de/rr/ui presents an XML parsing error instead of the actual page.
Firefox Screenshot:

Probably you'll need to add the input that created the error !

That unclosed link element causing the XML parsing failure, <link rel="stylesheet"..., does not originate from https://bottlecaps.de/rr/ui. It must have been inserted on the client side, presumably by some browser plugin, or possibly even by malware. Also it refers to some service running on port 51991 on your local machine. You might want to check what that is, and who is doing this.


wit-bindgen: 0.8.0 -> 0.9.0

Diff: https://github.com/bytecodealliance/wit-bindgen/compare/wit-bindgen-cli-0.8.0...wit-bindgen-cli-0.9.0
Description of changes
Update wit-bindgen to the latest release.
https://github.com/bytecodealliance/wit-bindgen/releases/tag/wit-bindgen-cli-0.9.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Hi @figsoda
Please help me review and merge this PR. Thank you so much!


UI-Schema Status Spec

As of right now there is no defined spec to be able to drive status information for a given stack or resource from a GUI perspective. It would be useful to add keys to the existing ui-schema.yaml file that can be used for this purpose.
We can leverage the types from the array of conditions within the conditionedStatus key defined in status.

The design for this has been merged to master in #930.  The design 1-pager can be found at https://github.com/crossplaneio/crossplane/blob/master/design/one-pager-stack-status-spec.md.
@displague or @suskin, I'm hoping to include this in v0.4 so consumers of Crossplane can start using it after that release.  I think the Stack Manager doesn't actually have to be updated though to deal with these new fields because the ui-schema.yaml files are completely opaque to the SM.
Perhaps reasonable support here would be to update some of the existing stacks to include ui-schema.yaml files for their CRDs, and define some resourceConditionPaths for them? Let's follow-up with @rathpc to clarify.

@jbw976 https://github.com/crossplaneio/sample-stack/pull/4 Is ready to go
Since this is a 2 line PR, we can easily create this for the other Stacks.
In a conversation with @rathpc earlier, he pointed out that UIs could fallback to the CRD printcolumn defined conditioned status, so this may not be necessary.

I've created the following PRs on the GCP, Azure, and AWS Stacks to provide the base ui-schema.yaml (#751) for those stack CRD files and to define that the resources in these stack should take advantage of the Crossplane Runtime "Ready" conditioned status:

https://github.com/crossplaneio/stack-aws/pull/50
https://github.com/crossplaneio/stack-azure/pull/42
https://github.com/crossplaneio/stack-gcp/pull/63

/CC @rathpc @jbw976 @suskin @turkenh @thephred

All of @displague PRs have been merged into their respective master branches and should be included in the v0.4 release timeline.


fail to train joint_alignment_translation model with fp16

🐛 Bug
joint_alignment_translation example causes a gradient explosion error when training it with fp16 option.
(https://github.com/pytorch/fairseq/tree/main/examples/joint_alignment_translation)
To Reproduce
I use 8 A100s or 8 V100s for training with cudatoolkit 11.3.
I tried both older and latest versions of fairseq. torch 1.8.2 and latest, tried both python 3.8 and 3.9.
Code sample
I only followed the given instructions in the README.md
Expected behavior
training to converge
Environment

fairseq Version 1.0 and 0.10.2
PyTorch Version 1.8.2 and 1.10.2
OS (e.g., Linux): Ubuntu 20.04
How you installed fairseq (pip, source): install from source and pip repos
Build command you used (if compiling from source):
Python version: 3.8.12 and 3.9.7
CUDA/cuDNN version: 11.3.1
GPU models and configuration: A100 or V100
Any other relevant information:

Additional context
I tried large batch, grad clipping, scaling learning rate and so on, but all failed.
But without --fp16, it works

This seems to be an old issue, which I have not seen any solutions.


Add SSL Certificate to sepal.io

Site not secure: sepal.io

Looks like this is in the works already: https://github.com/openforis/sepal/blob/c2007b23956e8a7be388c5a7625ce33d499f86d5/docs/architecture-diagrams.pdf

We had a security certificate renewal issue. We are working to manually update the certificate.


Possible TODOs:

[x] wait for the next NumPy release, which should have Python 3.12 wheels (I think this makes sense to do, and I believe upstream is working hard on this) -- if we'd prefer to delay 3.12 wheels to 1.11.3 let me know below
[ ] the CI/wheel infrastructure was updated/backported, so decent chance we may see some surprises with [wheel build] -- I may decide to do that here once rather than a bit later to reduce likelihood of a surprise during the release process proper (the net resource cost could be a fair bit higher if only discovered during rel process and then I need to patch/start over)
[x] should we try to wrap up gh-18781? my impression from taking a stab at this in gh-19034 is that it is a can of worms because of potential f2py involvement...
[x] we still have some open PRs with backport label--may be able to get some of those merged while we wait a little on NumPy 3.12 wheels and so on
[ ] I feel like I may be missing a Cython stdout build bug of some sort that was affecting networkx or scikit-image? Maybe it is dealt with by something here, but that may be good to confirm, or maybe I'm just misremembering.

Backports Included so far:

gh-18644
gh-18785
gh-18790
gh-18804
gh-18810
gh-18825
gh-18831
gh-18859
gh-18896
gh-18937
gh-18985
gh-18999
gh-19025
gh-19027
gh-17918
gh-18809
gh-19004
gh-19034
gh-19054

Some fun failures in CI, adding WIP to title for now.

wait for the next NumPy release, which should have Python 3.12 wheels (I think this makes sense to do, and I believe upstream is working hard on this) -- if we'd prefer to delay 3.12 wheels to 1.11.3 let me know below

I think it's best to wait here, shouldn't take much longer.

If time permits, could this recent fix https://github.com/scipy/scipy/pull/19004 also be included?

If time permits, could this recent fix https://github.com/scipy/scipy/pull/19004 also be included?

Yup, already on my list. I imagine we may have a few more shims before this gets merged.

Unless and until we get the DeprecationWarnings with numpy 1.25 down to zero on the 1.11 branch, I think we should lower the maximum numpy version here from 1.28 to 1.27, see this comment.

I think we're going to hit 0 warnings, there's just the 4-line patch in gh-19034 left to review.

Surveying some of the CI failures (if only to keep myself organized):

GitHub Actions musllinux: tools/wheels/cibw_before_build_linux.sh: line 8: can't create --nightly/LICENSE.txt: nonexistent directory

this may require me to cherry-pick a subset of gh-18889, where nightly-related variable handling shims were applied to tools/wheels/cibw_before_build_linux.sh fairly recently

GHA build with gcc-8 on Linux:  ERROR Missing dependencies:   Cython<3.0,>=0.29.35   pybind11<2.11.0,>=2.10.4   wheel<0.41.0

we can probably just pin the Cython version in .github/workflows/linux_meson.yml for this job and move on; it disables build isolation on a release branch

(Intentional) setup.py build/wheel install on windows with Python 3.10-- error LNK2001: unresolved external symbol wrap_PyUFunc_getfperr and maybe warnings could be related WARN: could not find library 'sc_cephes' in directories

not sure here just yet, but IIRC Cython 3.0.0 with setup.py is asking for trouble, and perhaps we can just pin that in this job and still provide what conda-forge still needs for residual Windows + setup.py usage?

Linux meson "pre-release": No matching distribution found for numpy<1.28.0

I think a pip --pre type pre-release install is not finding a NumPy nightly wheel with a version that isn't 2.0.0-something--I'm inclined to just let that one keep failing--trying to support the 2.0.0-dev series on the maintenance branch sounds like a recipe for unsustainable trouble

Linux 32-bit: need to backport gh-18809

I tried to apply those smaller patches along with another batch of backports detailed in the updated original comment above. I can already see that the gcc-8 job will require a few more version pins I think. Skipping cirrus for now, those jobs were already passing.

Maybe also remind me--do we want to wait for a stable release of NumPy that has wheels for 3.12 or are we content with the pre-release 1.26.0b1 already out? Ideally stable I suppose, right?

There is only one CI failure left, and it is an unrelated datasets internet connectivity issue, so that's progress for the regular CI. The next thing I'll try is a test wheel build on this branch--I want to confirm no surprises, and I'm perhaps slightly skeptical that the 3.12 wheels will "just build" without a tweak or two (i.e., pre-release req for NumPy somewhere perhaps, etc.).

Yeah, I can already see a wheel failure trying to use numpy-2.0.0.dev0, which is wrong, so some shims needed still, though could be quite minor.

In case it helps and you didn't see it: https://github.com/numpy/numpy/issues/23808#issuecomment-1678677094 and the comment a bit higher about PIP_PRE may be useful.

Summary of observed issues with Python 3.12 wheels so far:

musllinux

1 test failure: TestFractionalMatrixPower.test_al_mohy_higham_2012_experiment_1 at scipy/linalg/tests/test_matfuncs.py:559 may need a tolerance bump for relative max diff of 7.29361661e-12
44 warnings of the form: python3.12/multiprocessing/popen_fork.py:66: DeprecationWarning: This process (pid=6332) is multi-threaded, use of fork() may lead to deadlocks in the child.

Cirrus Linux ARM: datasets connectivity issues were observed with another Python version; also a brownout warning re: exceeding our free limit stopped some jobs--I'll try restarting, I need to see if there's a 3.12 issue here.

The other jobs, including the other 3.12 wheels, appear to have worked "ok" (I didn't inspect them for similar warnings, but I'm assuming we can live with those in our first 3.12 iteration).

@rgommers I thought of one more question--do we want to tackle: https://numpy.org/doc/stable/release/1.25.0-notes.html#compiling-against-the-numpy-c-api-is-now-backwards-compatible-by-default
That might be one thing too many to do here (a pyproject.toml readjustment), increasing the likelihood of a mistake by a bit too much perhaps, but on the other hand we do intend to take advantage of that at some point?

@IAlibay pointed out that when switching to that 1.25+ approach for MDA, there were some snags with conda-forge cc @h-vetinari perhaps.

@IAlibay pointed out that when switching to that 1.25+ approach for MDA, there were some snags with conda-forge

If there are issues with conda-forge packages, could you please open an issue on the respective feedstock and ping me there?
Note that conda-forge still builds for the lowest (NEP29-compatible) numpy by default, we haven't switched to the 1.25+ approach yet (and we haven't discussed, much less figured out, how we'll do that).

Thanks @h-vetinari - To clarify the issue that @tylerjereddy mentions isn't with the scipy feedstock but pretty much the following:

much less figured out, how we'll do that

We're in the middle of trying to do the jump from using oldest compatible and working out that it appears to be a much harder task than anticipated (at least my naive understanding of the conda-forge machinery is completely defeated).
I'm happy to raise an issue on the scipy feedstock if it's the right place to initiate the conversation on "how do we do this", but if it seems like this is already on your radar and I'm not sure there's much I can contribute to the solution.

If you're talking about MDA in conda-forge, then please don't change the numpy setup on your own. I get that people are eager to change, but none of this is necessary right now. In any case, let's take this discussion elsewhere. Please open an issue on the MDA feedstock (or the numpy one).

I'd leave a change to building against numpy 1.25.x for the next minor release, not a bug fix release. Things are set up well now, and I don't think we have much to gain from doing it in 1.11.2

All 39 CI jobs, including 3.12 wheel builds, are now green, so I'm inclined to merge here pretty soon. I'll probably do another quick scan of the diff, but that's about it unless other concerns are raised soon.
Then I'll start the release process either today or tomorrow.


Fix native code

In my case, the output contains function () { [native code] } so that it's invalid to be read by the browser.

Can you make a unit test for the failure? Typically this means you're trying to encode something that can't be serialized.


Full hierarchy in 'Default Location' dropdown not presented to user

Please verify that this bug has NOT been raised before.

[x] I checked and didn't find a similar issue

Describe the bug*
When choosing a default stock location for a part or category, the hierarchy of stock locations is not visible in Platform UI whereas it was in Classic UI.
Based on the hierarchical way in which stock locations can be set up in InvenTree, I set up all my stock locations with the location itself not including details of its parent locations.
For example, I have two stock locations with the name "B01", but one is a child of Drawer Unit 1 and one is a child of Drawer Unit 2. This has always worked well in Classic UI due to the way that the full location hierarchy is always visible.

In Platform UI, the hierarchy is hidden, and I am presented with two apparently identical options of "B01" or "B01", with no additional information to help me decide which one I need to select.

I have tried to illustrate the differences in behaviour in this short clip. First, the expected behaviour in Classic UI, followed by the new behaviour in Platform UI.
https://github.com/user-attachments/assets/5945129b-43d2-4292-9bfb-72f971afa480
Steps to Reproduce

Add a new part category
Select the Default Location dropdown box
Begin to type the name of a location
In Platform UI, filtered results of search may be indistinguishable from one another.

Expected behaviour
The hierarchy of stock locations is presented to the user as it is in Classic UI.
Deployment Method

[x] Docker
[ ] Package
[ ] Bare metal
[ ] Other - added info in Steps to Reproduce

Version Information
Version Information:
InvenTree-Version: 0.16.5
Django Version: 4.2.15
Commit Hash: 6e37f0c
Commit Date: 2024-10-07
Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-5.10.0-27-amd64-x86_64-with
Installer: DOC
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.1.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'InvenTreeCurrencyExchange', 'slug': 'inventreecurrencyexchange', 'version': '1.0.0'}, {'name': 'InvenTreeLabel', 'slug': 'inventreelabel', 'version': '1.1.0'}, {'name': 'InvenTreeLabelMachine', 'slug': 'inventreelabelmachine', 'version': '1.0.0'}, {'name': 'InvenTreeLabelSheet', 'slug': 'inventreelabelsheet', 'version': '1.0.0'}, {'name': 'DigiKeyPlugin', 'slug': 'digikeyplugin', 'version': '1.0.0'}, {'name': 'LCSCPlugin', 'slug': 'lcscplugin', 'version': '1.0.0'}, {'name': 'MouserPlugin', 'slug': 'mouserplugin', 'version': '1.0.0'}, {'name': 'TMEPlugin', 'slug': 'tmeplugin', 'version': '1.0.0'}, {'name': 'Brother Labels', 'slug': 'brother', 'version': '0.9.0'}]
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

Chris, it looks like the form rendering for a "location" has not been fully implemented (or is differently implemented) in the new interface. I've added this to the next release milestone so it doesn't get forgotten.
This should be a pretty simple fix - is it something that you are interested in contributing to?

We renamed that command to invoke dev.frontend-server. Looks like the docs are out of date, I'll issue a PR to fix that!


Question: Behavior of Voyager with missing derivatives

When a derivative corresponding to the specified 'Quality' prop is missing, how does Voyager handle this situation? Does it fall back to a default quality level, or is there error handling that comes into play?
Thank you for your time

Hi @Solcany , it picks the closest available derivative to the desired quality, using the scheme described here: https://github.com/Smithsonian/dpo-voyager/blob/b8d21678cc5c6b68063fa790ff0f7e64ee07b937/source/client/models/DerivativeList.ts#L51

Thank you for your time @gjcope


useQueries.js:60 Uncaught TypeError: Cannot read property 'substring' of undefined

Version
2.8.1
Test Case
sorry none
Steps to reproduce
with the router provided by withRouter do router.push("your route")
once on the new route click the back button
Expected Behavior
no error
Actual Behavior
error in title is raised
nb this does not occur if I use an object as a parameter ie
  router.push({pathname,query})

actually I lied it seems to be happening with the object form too

What version of history are you using? What exact pathname are you attempting to push?

Closing due to lack of a repro. Sounds like something might be messed up with your node_modules or an incorrectly installed version.


Horizons server cannot initialize with TickProfiler installed

Whenever we try to start up our FTB Horizons server (running on SpongeForge version spongeforge-1.12.2-2503-7.0.0-BETA-2710) with TickProfiler enabled, it crashes on the first few seconds of initialising and throws this into console. This behavior only occurs when TickProfiler is installed on the 1.12 version, and not on 1.10.2 (we have it working flawlessly on our SF3 server and it's a god send on there).
SpongeForge Version: spongeforge-1.12.2-2503-7.0.0-BETA-2710
TickProfiler Version: TickProfiler-1.12-0.0.1
If it helps, we also use Pterodactyl to sort our servers into containers.

Must be a sponge thing again. I am running default forge for H3 no issues.

Further testing in a fresh SpongeForge server (only tickprofiler as an external plugin/mod, everything else was in Horizons III) shows TickProfiler functioning normally. Perhaps there is a discrepancy in the live version.
I’ll let you know if we find something later

Could be a file permissions issue or something else preventing LibLoader from working. Does Pterodactyl make the mods folder a read only volume?
There should be a file called # LibLoader.jar in your mods folder. If there isn't, try manually creating it by extracting LibLoader.jar from inside of TickProfiler's jar, then renaming it to # LibLoader.jar.

I apologise for the delays in a reply, but we have found the following out:

Pterodactyl does not make the folder read only when the server is running
We tried your fix with # LibLoader.jar but to no avail - same error as before
The error specifically states that Forge can't lock the base of our container, so I'm not sure what's going on there
We have other "mixin" mods (mods that don't originate from the pack itself) working just fine, so we don't think it's the Tickprofiler mod's fault.

However, I am now out of ideas to try to fix it... and the fact that a fresh spongeforge server running on my local machine works fine baffles me.

Running normal JDK and java security permissions?
On Nov 2, 2017 15:28, "Tom Harrison"<EMAIL_ADDRESS>wrote:

I apologise for the delays in a reply, but we have found the following out:

Pterodactyl does not make the folder read only when the server is
running
We tried your fix with # LibLoader.jar but to no avail - same error
as before
The error specifically states that Forge can't lock the base of our
container, so I'm not sure what's going on there
We have other "mixin" mods (mods that don't originate from the pack
itself) working just fine, so we don't think it's the Tickprofiler mod's
fault.

However, I am now out of ideas to try to fix it... and the fact that a
fresh spongeforge server running on my local machine works fine baffles me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MinimallyCorrect/TickProfiler/issues/86#issuecomment-341577016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACnJtowY-coq6pGBQQcLR_yHP7uS97FQks5sykIfgaJpZM4QNfnK
.

Normal JDK and Java security settings

Alright, we've been tearing our heads out over this, and we finally got it working. Turns out that it was because TickProfiler was being loaded as an extramod through forge (using parameter --mods="" and it did NOT like that at all. Took us having to test over the course of a few days (due to other projects being thrown in the mix as well) but we now know it works fine.
Sorry for keeping you in the dark @nallar


The connection to the server was refused

What happened:
Ran kubectl get node -o wide after installing k3sup on my Mac using the IP Address of my Raspberry Pi node, and got this error:
The connection to the server x.x.x.x:6443 was refused - did you specify the right host or port?
What you expected to happen:
List of node details.
How to reproduce it (as minimally and precisely as possible):
Follow the install steps as outlined here: https://medium.com/@alexellisuk/walk-through-install-kubernetes-to-your-raspberry-pi-in-15-minutes-84a8492dc95a.
Enable all connections via ufw to the Pi, and enable SSH server mode using sudo raspi-config.
Anything else we need to know?:
Environment:

Kubernetes client and server versions (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T21:51:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Cloud provider or hardware configuration:
Pi 4B in SSH server mode, and MacBook Pro
OS (e.g: cat /etc/os-release):

MacOS Catalina
Pi 4B OS:
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

@LemonSpike hopefully you figured this out.
My guess is this was an issue with requiring the cgroup kernel parameters on the Pi. K3s might have failed to start because they were missing. Looks like Alex updated the guide recently as well.
/triage support
/close


At high tps show more interesting tx

Story
Currently when there is even moderate load (>10 tps), the latest transactions display becomes not very interesting.
Instead we can sample transactions to highlight interesting activities:

Contract deployments
Large transfers
Tx to popular contracts
etc

This becomes a more and more pressing issue as we get bridge and other regular transactions on the chain.
As a regular user who monitors the transactions in the network, I want to see less of the automatic transactions on the dashboard and see more transactions relevant to the developers.
Possible solutions:

Group transactions by the account id even if they are in different blocks (implementation hint, there are GROUP BY and DISTINCT helpers in SQL). There is a relevant discussion in #255
Filter out "noisy" accounts (e.g. bridge). It is simple, but it might be misleading and not solving the problem in a generic way. (it might confuse bridge devs /cc @nearmax @ailisp)

@corwinharrell It might be great if we have some view from the UX/design perspective as well.
@vgrichina What do you think?

I think the best solution for the dashboard is too remove TXs entirely. Users should not expect to see there transaction on the dashboard, or even TX list page, as at sufficiently high TPS, this will be highly unlikely (potentially even when grouping by account).
In etherscan, users know they need to find their account first, or look up the TX hash directly to see its status. We will need to handle this in a similar way, as we will have the same problem of too many TXs for the users to sift through.
For users that want to monitor TXs out of curiosity, they can use the TX list page, or look through recent blocks.
Perhaps we can group by account on this page to make it slightly more digestible.

@frol I think we should show heatmap a-la GitHub on home page.
One square – one block / minute / hour / day (depending on user choice).
You click on the square – see transactions/blocks in it.


Artifacts on the last slide with Firefox

Hi,
I'm having artifacts on every style except the wheel. They appear when I slide to the last div.
Here's an example with the demo: http://i.imgur.com/7tyqf54.png
Disappears when scrolled through the page.
My user agent : Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/20100101 Firefox/44.0
Regards.

Hello, i have this problem too in FF 44.0.2 Win 10 Pro

Very strange. I tested all of the themes on my demo template in Firefox 43 & 44 on OS X with no problems. This might be a Windows specific issue. Can you try replicating this on the demo template to help isolate any other factors?

Same problem. Anything we can do to help?

I'll take a look from a Windows machine as soon as I get a chance.

I am able to replicate this using CrossBrowserTesting.com to run Windows 10.
The issue is occurring on Firefox 41-44, at least, but does not occur in Chrome.
This is likely GPU related, since it's occurring on the 3D transform themes and not the flat wheel transform theme.

Simply adding a transparent outline seems to prevent the artifacting. I assume this is like the old zoom CSS trick for IE that would ensure elements rendered properly.
.flipster__item { outline: solid 1px transparent; }

Updated Demo
This temporary fix should work while we dig further into this issue.

Feel free to contribute by seeing if this is a documented issue anywhere else, and if there are any stylesheet adjustments we can make (other than the outline hack) to resolve the issue. It seems to be strictly related to Firefox's handling of 3D transforms and transitions/animations. I found some old Mozilla bugtracker references to similar issues, but those were all apparently resolved in 2011/2012.

Very strange. I tested all of the themes on my demo template in Firefox 43 & 44 on OS X with no problems. This might be a Windows specific issue. Can you try replicating this on the demo template to help isolate any other factors?

.flipster__item { outline: solid 1px transparent; }
it work!!

Hi! Unfortunately, it didn't help in my case:

Problem was in filter: blur

This repository is going into very-low-maintenance mode and declaring backlog bankruptcy


Only works in current directory

I had to process.chdir() to my target directory in order for bower-license to work; it'd be nice if it behaved more like npm-license in that regard.

+1

Hi Guys,
There is an enhancement version available in order to have the flexibility about the project directory.
One can try the following package:
https://github.com/amittkSharma/bower-license-tracker
This is also published on NPM:
https://www.npmjs.com/package/bower-license-tracker
Thanks and regards
Amit


Too much different colors

Design Feature Request
Summary
When browsing, I felt a bit overwhelmed by the many background color shifts.
There are (bgcolor, fontcolor, fancycolor):  (white-black-yellow), (turquoise-white-aubergine), (blue-white-purple), (black-white-yellow), (purple-white-aubergine). Especially the toggeling between dark and light style is irritating.
Motivation
Using less color shifts within a single page or assigning meaning to the colors could lower the mental load experienced when browsing the site.
Unresolved Questions

Get more feedback about how others feel about this.

Yes! +1 to this. Somehow, the site just doesn't feel 'serious' as a result of this. The colors are too bright and the contrast is way too much  to scroll down comfortably.

I agree, and frankly the color choices leave me a bit confused because they don't really seem to have a common theme so the entire page looks mighty awkward in my opinion. Would definitely rethink the color palette. The text offset from the background rectangle also looks strange, but maybe that's just me.

The text offset from rectangle bugs me as well. If there's a box, there should be things in that box maybe?

It looks slightly better on a mobile layout from a quick view from the developer tools, but along with the font its super jarring and hard to read.

hey! thanks for filing.
at this time we're not looking to remove the colors wholesale from the website. it is true though that some pages may have unfortunate color combinations, and we are open to hearing that feedback! if you could be specific about which pages you'd like to see changed and to what (giving the existing styles for sections)- we'd be very open to working on improving that! thanks :)

http://beta.rust-lang.org/ on the main page, the green, pink (... red?), and weirdly light-dark gray don't mesh very well. The black on yellow on white of "Rust in production" (no header links?) is way out of place. The colors in general are too light and don't carry much "weight" to them and feel way too comical with the font. Contribution page suffers from a weird Neopolitan ice cream scheme. There's others but that's my tl;dr basically.

FWIW we've discussed this in the office today and this seemed to be the most glaring issue most of us had with the new site. IMO just using one consistent backdrop would look much better than this, there's just way too much change in contrast.

@jonas-schievink 100% agree

thanks for the feedback. if you'd like to open a PR to reaarange some of the color backdrops on other pages that'd be great and i can give feedback on the PR directly.
as i said previously, wholesale removing the colors is not currently up for discussion. closing this, and will give feedback on specific suggestions in PRs.

I think most of the colours are fine, but the parts with the white text on top of pink/purple are pretty hard to read

@TheZoq2 Yeah, but that's https://github.com/rust-lang/beta.rust-lang.org/issues/408

I understand this issue is closed, but I did not not want to bombard the repo with yet another issue when this one is fitting. I tweaked these before finding the relevant issues, so the header underline change is more fitting to be discussed in #408, and is not the focus of the following screenshots.
Instead of removing the colors wholesale, we could try reducing the palette to be more in the spirit of the stable website while keeping the wonderful flexibility of the new layout :)
The following uses white, grey, and re-uses blue from the current stable website;

^ unsure about using the blue for the full background, but was curious to see what it looked like re-used.

For the sake of showing different pages using their own variations reduced palettes:

Background switches from white to grey then back to white:

This one uses both purple and green, rather than only one:

Not final proposed colors, more so proof of concept of less variation on individual pages.

hey folks, this issue is closed. i am locking this, as there should not be continued conversation on this.


Update manage-groups.md

Removed opening and closing quotes

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/6158


[BD-46] docs: refactoring Table on docs site

Description

check pages in Guides and Foundations and update styles for tables;
replace deprecated Tables with existing ones in Paragon.

Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[x] Does your change adhere to the documented style conventions?
[x] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[x] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @PKulkoRaccoonGang!
When this pull request is ready, tag your edX technical lead.

@PKulkoRaccoonGang 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

:tada: This PR is included in version 21.0.0-alpha.7 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adding ability to send error object to notify()

In short, this pull request is to assist with error reporting, and diagnostics.
After the 2.0 upgrade, a number of plugins I use stopped working. Unfortunately, while I would see the notification message to check 'Developer tools', there was no further output or logs available.
After looking through the source, I found that some catch blocks would output the error to console.error, but others would not. Rather than modifying all the catch blocks, I opted to add an additional parameter 'error', to the notify method. If present, the error is logged to the console. I then just modified the catch block to pass the error reference.
Please do not be bashful with your feedback, and thank you so much for this incredible tool.

BTW, I wanted to add a test for the modifications, but I was not quite clear on asserting calls to the console. If someone can provide me some guidance, I would be more than happy to add theses tests.

@albinekb I modified the parameter as you suggested. Are these changes what you were thinking?

Excellent, thank you so much!

I created a corresponding PR in hyper-site, which updates the API description for 'notify'.
https://github.com/zeit/hyper-site/pull/47

Thank you for your valuable help 🙏
Great work and a good thing that you made another PR for our documentation 💯


Switch ContainerSSH license to Apache-2.0/CC-BY-4.0

Switch ContainerSSH license to Apache-2.0/CC-BY-4.0
The IP policy of the CNCF requires projects to use the Apache-2.0 license for code and the Creative Commons Attribution 4.0 International License for documentation. Therefore, we should switch the ContainerSSH license to these licenses in anticipation of (hopefully) getting accepted for CNCF sandboxing.
Benefits

Easier adoption to CNCF.
Legal safety around trademarks and patents.

Drawbacks

The code is no longer "free to copy-paste", you need to observe the license.

By contributing to this repository, I agree to the contribution guidelines.

Decision approved with 4/4 working group votes.


YFT Physic broken after export (vanilla props)

Hello !
Blender version : 4.0
Sollumz version : 2.3.1
I noticed something about yft concerning my issue here [YFT Punch bag Physics] :(https://discord.com/channels/899043946142003240/1188083773150089338)
i used prop_garden_chimes_01 vanilla props as reference and there is something weird : if you export this props from CW, import it in blender, you change nothing, you export it, put it in game, it's broken and it have the same "behavior" than my props (the physics seems broken, like in the video i shared on my post).
Here the 2 xml : the original one (just exported from CW) and the same props after sollumz export
prop_garden_chimes_01.yft.zip
May someone can take a look if you are able to see what is broken during the export ?
if yes let me know (here or feel free to ping me on discord)
Thank a lot for your help !

Is the "original one" meant to be truncated? Other than that the only thing I see difference is the omission of the  section right in the skel declaration.

i noticed that the RestoringStrength value is seted to 0 when you import/export it in sollumz instead of 500 for example. I'm not really comfortable with this kind of troubleshooting so i might be wrong. For info even if i set it back to 500 the issue is still here so i guess there is something else

Looking at your first video, it does seem related to restoring strength. Sollumz incorrectly imported/exported rotation and restoring strengths, but this should have been fixed since 2.3.1: f01e89895003514521f5ceecf2a6f40f4307b40d. Can you try import/export on latest Sollumz?

I mean latest commit, Download ZIP option in the main repo page. Both will show 2.3.1 in the version field.

Confirmed that the issue are only the Transforms in the physics LOD1. Sollumz is calculating them incorrectly.

i had the same problem but with cars, when i export the values change xml and the car move on wrong positions


feature(tests): for Button.vue, CheckboxButton.vue

for Button.vue, CheckboxButton.vue

Update your local copy witht the latest updates as the PR is trying to revert them now.


Web - IOU's are being paid before account B pays them

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open account A and click on FAB > Request money > Enter an amount > Paste account B's email > click on request money
Click on the IOU card preview on account A
Go to account B and open the IOU and observe by waiting for a few seconds

Expected Result:
IOU's should not say paid before account B pays them.
Actual Result:
IOU's are being shown as paid before account B pays them.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.39-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/7bf0106c-8863-4d05-976a-b661a7efa3f5
https://github.com/Expensify/App/assets/93399543/8aa1765b-22d4-4acc-9ceb-b299a7896a21
Expensify/Expensify Issue URL:
Issue reported by: React JS development and Quality Assurance (GH @Nathan-Mulugeta)
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689152559795319
View all open jobs on GitHub

Sorry for the delay in triage, I will do it tomorrow

I cannot reproduce this

No response in slack. Closing. Please reopen if you can reproduce


New files added for AWS Security Hub lab

Issue #, if available:
Description of changes:
Readme updated
LabGuide added
Images directory added
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks @PierreLiddle


Input required: ConnectedServiceNameARM when deploying test resources with federated auth

The Deploy test resources task fails with Input required: ConnectedServiceNameARM, for example, when UseFederatedAuth: true.

Same problem for go - azservicebus. I see these pipelines both set CloudConfig, so I guess we're missing some service connection configuration there.

This will be resolved with https://github.com/Azure/azure-sdk-for-go/pull/23240, merging in two weeks (I am out next week).

Closing this issue as it's resolved for the nightly pipeline live tests. I will open a similar issue in azure-sdk-tools tracking this issue as it pertains to sovereign clouds, as that will be a common change.


(macOS) Build instructions are missing doxygen as requirement

Building the framework on macOS fails due to missing doxygen. Installation via brew fixes this and should be mentioned in the README.

I'd like to see doxygen not be a requirement, is this possible @pasin ?

I think it's possible.

Track : CBL-2218


registry_secret_name usage without registries config

Hi there!
I am currently setting up the lacework proxy scanner to scan our on premise harbor registry. I would like to set this up with the lacework proxy scanner helm chart from this repository.
I am not sure, if there is a problem with the handling of the config.registry_secret_name value or if I maybe don't really understand this, hopefully someone could help me here. :)
From the docs (https://docs.lacework.com/onboarding/integrate-proxy-scanner) I assumed, that I can either set the value config.registries or config.registry_secret_name and not both at the same time. So I want to set only the config.registry_secret_name. The problem I am encountering is, that when I provide a secret with the registries config in it and name it, e.g. "lacework-proxy-registries", and set the name in the config.registry_secret_name value, there will be no volume for the registries in the pod as the helm templating is setting not adding this when config.registries is not set.
My example values.yaml:
config:
  static_cache_location: /opt/lacework
  scan_public_registries: true
  lacework:
    account_name: <our account>
    integration_access_token:
      existingSecret:
        name: lacework-proxy-scanner-access-token
        key: LACEWORK_PROXY_SCANNER_ACCESS_TOKEN
  default_registry: <our harbor registry URL>
  registry_secret_name: lacework-proxy-registries

I forked this repo and tried to change the behaviour within this Pull request, just in case I understand all correctly and not missing something, that could fix the behaviour, right? https://github.com/lacework/helm-charts/pull/160

Hi! Thanks for the bug report, I'm working on releasing a new Helm chart based on #160 .

https://github.com/lacework/helm-charts/pull/162 Should have the fix to this issue.

Thanks @michael-zhou-lw !


feat: sierra class hash calculation

Resolves task 3 of #313:

support computing class hashes of Cairo 1 contracts

With this PR the library is capable of calculating hashes for all 3 types of contract classes in existence.
Note that in this PR I'm hard-coding to use the Pythonic JSON formatting for the ABI to match the class hash calculated from the official cairo-lang CLI, just to make sure we're doing it right, but that's not necessary. In a future PR we should make the formatting plug-able with a AbiFormatter trait, allowing users to specify how the ABI should be formatted, including not uploading ABI at all (VoidFormatter?).


Feature Request: Custom Videos for Config

It would be nice if it would be possible to specify a Custom YT-Link or even better Directly stream it from the server.
As a little Extra, i would ask for a Language button for the User and Maybe Language Specific Videos that would be Awesome.
Otherwise, Nice work, I appreciate you for sharing it with us.

You can use the integrated HTML as a template and change the YT links to suit your requirements. then supply it as the custom HTML in the Settings page. I'll leave the second part for the actual dev to comment on.

Indeed, this is possible via the Custom HTML !

Hi,
I'm sorry, but I'm not smart enough to do this properly.
If I just take the tips.html and paste it into the custom HTML, then I get some strange alignment
Could you be so kind to provide me with the right snippet where I change the links?

Hi,
I'm sorry, but I'm not smart enough to do this properly. If I just take the tips.html and paste it into the custom HTML, then I get some strange alignment
Could you be so kind to provide me with the right snippet where I change the links?

I see.
At this stage for your use case and what you are trying to achieve I would recommend going to YouTube, clicking « Embed » on the video you want and playing around with that instead of trying to copy that template. It uses JavaScript and it’s all over the place with styling, although i suppose you could try going a few divs down.


Change the carousel template to flex message

Pull Request Test Coverage Report for Build 589

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 96.262%

Totals

Change from base Build 585:
-0.03%

Covered Lines:
220

Relevant Lines:
226

💛  - Coveralls


Enable View More for videos block on homepages

 Add a view more option to video section where it appears on site


Stop installing nginx in Docker

@JayH5 pointed out that the upstream django-bootstrap container already has nginx installed.
I'm pretty sure we could stop using the specific django.conf in this repo and just use the upstream one. But not sure enough to make that change yet.

This helps get up and running for MOMZA-775.


bf: MD-989 try next sentinels after I/O timeout errors

This fixes an issue that causes other sentinels not to be tried after one of them fails with an I/O timeout.
The root cause is that the code attempts to abort early if the error is of one of the types generated by the context module, in this case, context.DeadlineExceeded, but it doesn't check that the error comes from the context argument provided to the function. Since the network layer also uses context to manage timeouts, it returns the same type of error, which is mistakenly assumed as coming from the passed context.
The fix consists of checking whether the ctx object passed to the function is in error state to abort early, and continue trying the next sentinels otherwise.
The commit that introduced the early abortion on context error and caused this regression is:
https://github.com/redis/go-redis/commit/63392a363ad7dce4c1b5aae60d1207104664371b

I am curious about the v versions, whats the branching and versioning scheme we follow here?

@anurag4DSB the v9.7 branch is the latest stable branch in go-redis upstream repo at this time.


This just stopped working

This extension just stopped working for me today. It's worked brilliantly in the past. I'm not sure if anything's changed on my end. Curious if you know of particular settings or updates that don't play nicely with this. Or just in general, any way of figuring out what's happened.

Hi @tandrewnichols, last update shouldn't have caused the problem. This extension might crash with others since it analyses the page content, can you try to disable other extensions? Can you also check if there is any error in the console?
Thanks, and sorry for the trouble!

I did check the console already, nothing there. I haven't added any new extensions recently. Meaning, it was working with the setup I have now, and then stopped working (unless one of my other extensions updated behind the scenes maybe). I'll try disabling a few to see if I can figure anything out. I've tried this in Chrome Canary version 57.0.2939.0 canary (64-bit) and in regular Chrome version 54.0.2840.98 (64-bit), in case that makes a difference.

I disabled every other plugin I had and reset the default options on json-viewer, and I'm still getting regular json (the way the browser normally displays it without a plugin). It's like json-viewer isn't intercepting it. I've tried a couple other json view plugins as a test, and they are working correctly.

Ok, can you do a last test? Disable and enable the extension. If it doesn't fix the problem, can you share an example of page you are trying to highlight?
Thanks for the debugging.

I've tried that already, as well as removing and reinstalling the plugin. Not sure I can share the page I'm trying to highlight. It's running on localhost.
For background, my common use case for using this plugin is in development of the website of the company I work for. We have a development feature that returns the json used to render the page instead of the page itself (for internal/admin users). The page I'm looking at now is 11.9KB as json. I can give you a sample snippet of the json if that would be helpful, but . . . I don't see how it would be. I mean, json is json right?

Something else just occurred to me. I think the plugin is attempting to do something because I also installed "JSON Formatter" to use in the mean time until I figure out the issue with this, and if I have both of those plugins turned on at the same time, JSON Formatter does add it's normal buttons to the top of the page, but it doesn't format the JSON. You have to click "Raw" and then click back to "Parsed" to get it to format. When only JSON Formatter is on, it comes up parsed right away. So this plugin is doing something to the payload (because it prevents the other plugin from rendering correctly).
Is no one else having any issue with this? I wonder if particular Chrome settings could be a problem...

A little more information on this. A colleague and I just discovered that this extension works fine when used at the root of a domain (e.g. for us localhost:8000), but not on any path (e.g. localhost:8000/foo). He's having the same experience with the plugin, btw. Which still doesn't necessarily mean it's an issue with the plugin, as we are both working on the same site.

:+1: am said colleague

I wonder if I'm experiencing something with the same root cause. Extension fails spuriously for me, but I've narrowed it down to the situation where the JSON in the document is actually split (for reasons I still haven't managed to understand) over two text nodes.
Though I'm not sure why Chrome decides to split the text sometimes (it's not a length thing, it seems to depend on the content), it seems like a reasonable thing for it to do. Since they're adjacent text nodes, each node has the same wholeText attribute - I might submit a pull request to cater for this situation by comparing adjacent nodes.
Anyway - if you guys think this might be the issue you're facing, open up devtools on a page that fails, and see how many elements are listed in document.body.childNodes. If it's more than 1, there's your problem.

Following up on the above, here is a pull request: https://github.com/tulios/json-viewer/pull/133

I'm having the same issue. I'm working with the Guild Wars 2 API, and for example this data does not always get parsed with json-viewer. It takes a couple of refreshes before json-viewer picks it up. Basically it works half the time whereas it used to work every time.

@Archomeda, the next time it fails can you save the response? @benvan created a PR to fix this problem and we can use this payload to further test the PR.
Thanks for all reports, it will be really nice to fix this :)

@Archomeda, in addition to saving the response, please check the number of
text nodes that were created by the browser as detailed a few comments
above. This will let us know if it is the exact same problem - I would
hazard a guess that the conditions in which a response gets split on
display might vary between browser installations
On Fri, 13 Jan 2017, 08:23 Túlio Ornelas<EMAIL_ADDRESS>wrote:

@Archomeda https://github.com/Archomeda, the next time it fails can you
save the response? @benvan https://github.com/benvan created a PR to
fix this problem and we can use this payload to further test the PR.
Thanks for all reports, it will be really nice to fix this :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tulios/json-viewer/issues/126#issuecomment-272387003,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXqDfefrMK-9h_RPtK4YFR0FClLmKjlks5rRzSMgaJpZM4LEsrg
.

I was about to respond with about how this endpoint is not the only endpoint it's failing on, and that it even fails on the root endpoint. And that only outputs:
["v1","v2"]

But, then I thought this was kind of odd. Especially since I compiled the PR and tried to see if it was fixed. It was not. Then I went to check if I had any conflicting extensions. And apparently I have, since Incognito worked correctly.
I installed this extension recently, and this seems to be the cause of my issue. Or rather, the setting to replace all emojis with EmojiOne is causing a conflict.
Sorry for the confusion I caused since my issue is essentially a different problem. I assumed mine was the same when I saw this issue here.

If other extensions change the body it will prevent json-viewer to highlight, the current implementation is super strict about which content should be highlighted, it only highlight "blank" pages from chrome. Basically pages with one pre node or, recently, one text node. If you have any ideas for this check feel free to share, @benvan PR will greatly improve this.

@benvan @tulios I've just checked on a page where this plugin doesn't work for me, and document.body.childNodes only has 1 element (a pre). Also, just to rule it out, the extension does not work in Incognito mode with all other plugins disabled. As I mentioned before, it does still work on the root page (/), but not on any page with a path (/foo).

@tandrewnichols can you provide the payload so I can debug what is happening?

@tandrewnichols can you check the number of nodes inside the pre?

@tandrewnichols it would be great to see the json body that breaks it for you. If it's sensitive data, you might find the following script useful which redacts all text content into x and 9 while preserving structure and length:
cat broken.json | sed -e 's/null/0000/g' -e 's/undefined/000000000/g' -e 's/[a-zA-Z]/x/g' -e 's/[0-9]/9/g' > broken_and_redacted.json

It doesn't seem like there should be anything different between my working and non-working pages, but I've created this gist: https://gist.github.com/tandrewnichols/8e37e24ddcc6f8f38c5b28de0470babe
Note that (again) the working one is always on /, while every other path produces non-working json (though not always identical to what's in that gist), regardless of other variables within that json (as far as I can tell).
I actually am not sure if there's anything sensitive, and as it's like 2000+ lines (when formatted), I decided to go ahead and "redact." Nice trick, btw.

@tandrewnichols Thanks for the data. I've had a dig around, and it's a bug that stems from json-viewer getting confused with the part of your payload that has a large blob of stringified json in the json (it's line 1197 of your gist)
@tulios The bug is in wrapNumbers - it produces incorrect json. I'll spend the next 20 minutes to see if I can fix it

Simple breaking example:
  "broken": "{\\\"99\\\"}"

}```

It looks like the wrapNumber function is fairly fragile - it breaks here because triple backslash is used which it doesn't expect. I wonder if there's a less fragile approach to retrieving the original numbers? I could imagine one alternative being a normal JSON.parse, followed by a traversal down the tree, peering into the original string every time a number is encountered. In the case where the numbers differ, and offset can be incremented so that the pointer in each source stays in sync.

Any thoughts?

So is it trying to parse that string as JSON? The triple slashes occur when we have (I know, I know) stringified JSON inside stringified JSON, but rendering the whole string as a string seems sufficient. I don't think it needs to be parsed.

You're right, it doesn't need to be parsed.
The reason it actually gets parsed is because json-viewer appears to have
a feature which attempts to display numbers in json as they were originally
written. That is, it attempts to prevent 0.0 being turned into 0 by
JSON.parse
I've only just looked at the source, so take this with a pinch of salt, but
the way json-viewer does this is by operating on the string representation
before it gets parsed, turning numbers like 0.0 into the string "0.0". Of
course, it shouldn't do so if that number exists inside a string. That
check appears to be broken, and it functions by tracking open and close
quotes in the unparsed json.
On Fri, 13 Jan 2017, 19:31 Andrew Nichols<EMAIL_ADDRESS>wrote:

So is it trying to parse that string as JSON? The triple slashes occur
when we have (I know, I know) stringified JSON inside stringified JSON,
but rendering the whole string as a string seems sufficient. I don't think
it needs to be parsed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tulios/json-viewer/issues/126#issuecomment-272526383,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXqDTygKEd7XwlcOq0qpXpWQGjWZ2y1ks5rR9ETgaJpZM4LEsrg
.

Fixed: https://github.com/tulios/json-viewer/pull/134

Version 0.16.2 is out, I'll keep this open until it is properly rolled out. Many thanks for the discussion and debugging!
@benvan JSON can be used between two backend systems, let's say one in Java and another one in C++, both languages support higher number and when visualizing their payloads we shouldn't apply the limitations of javascript since they are not using javascript anyway. There is no max number in the JSON definition but on the languages using JSON.

Ah, you're right - that's a very good point :)

same thing just happened to me for what looks like another reason and in my case it was the ghostery extension that was breaking json-viewer. White listing my development site in ghostery didn't fix it and I had to use the following other extension to prevent ghostery to run when I am hitting the api I am working on: https://chrome.google.com/webstore/detail/extension-automation/ghopjgdkodchjclkkfdekhjfomdbakkb


Translate Hooks API Reference

Hi @fozg I see that this PR has been in Draft for a while. I wonder if you have finished it yet?

hi @Ryan-LT, It's quite a long page so I'm still working on it, I'll change this PR to Ready when I completed, thanks.

@Ryan-LT it's ready!


cockpit_portal: add API page to space navigator

Instead of it being in the AYS portal by default.
A default portal installation shows a page not found currently.

due to that fact that the portal code, more specifically the nav.wiki page, is part if the sandboxing which means that a service cannot write to it unless it is  part of the build process , and so adjusting it in the ays service would not work;
my suggestion to this issue is adjusting the code in the build method of cockpit in cuisine which will include both the ays build and a normal cockpit install


Body copy should be updated to 16px for non-listing copy

Especially relevant for sub pages

This was fixed with Tina's css updates


Migrate to Galactic

All code (except for orca_driver) compiles and runs on Galactic
Simulations mentioned in the README were tested and mostly work, though they can be improved

Fixes https://github.com/clydemcqueen/orca3/issues/11