Branch is created, but PR is not

For example this repo: https://github.com/BlackDice/eslint-config/branches

I admit that this repo is bit special since package.json looks like this. Perhaps greenkeeper is silently failing there when creating PR because this is unexpected?
  "peerDependencies": {
    "eslint": "3"
  },
  "optionalDependencies": {
    "babel-eslint": "7",
    "eslint-plugin-babel": "3"
  },

It looks like the problem right now is that you don't have tests set up. And somehow we fail to recognise this. Therefore these branches are waiting for a status to be reported. I'll consider this a bug and we will look into this.

Ah I see, yea in this case adding tests did not make sense to me. It's interesting thou that for eslin-plugin-babel the PR was created, but not for others.

@FredyC That's because this was the only update that was not covered by your version range. For updates that are not in your version range we create your pull request right away. If new versions are covered by your version ranges, we usually only create a branch to see if your tests still pass.

Just found out about another branch in other project, that haven't got PR created. The tests for that branch has passed: https://travis-ci.org/BlackDice/b3-chief/builds/178032443

@finnp I'm seeing similar behavior on several repos, as of this weekend. For example, see the list for this repo. All branches are reporting statuses back (and passing).
I use exact versions and greenkeeper-keeper to keep up with the frequency of updates. This enables me to have more confidence that I'm using the same versions when going back in the history. Therefore, this is not a case where the update in the branch is already within the range defined in package.json.
Anything else that I need to check on my end? Any known issues on your end that might be causing this behavior?

@travi Thanks for the report. This was an issue that we fixed now. However the existing branches are not going to be handled by greenkeeper anymore. So please review these and delete or merge them accordingly. Sorry for the inconvenience!

Thanks for getting this resolved and for everything you guys are doing to continue to improve the service. It is incredibly helpful to us!

This is still happening for one of my projects. On circleci you can see the branch being created: https://circleci.com/gh/ohjames/rxjs-websockets
5 branches and yet not a single PR was created.

@ohjames Perhaps try Renovate instead? This project seems kinda abandoned and Renovate works very nicely.

@FredyC if it was abandoned wouldn't it be unlikely for them to spend the resources monitoring version upgrades and creating the branches etc. ?

@FredyC Tried out renovate, and it works, so switched all my projects off of greenkeeper. Thanks for the recommendation.


[BugFix] [InfluxDBSource] Resolve invalid SQL in initColumnsIndex method caused by direct QUERY_LIMIT appendage with 'tz' function.

recommit RP for [Bug] connector-influxdb module InfluxDBSource class's initColumnsIndex method, sql invalide when sql contains tz function cause by direct append QUERY_LIMIT #4231

Purpose of this pull request

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

@Hisoka-X Can you help figure out why there's no CI/CD?

@Hisoka-X Can you help figure out why there's no CI/CD?

It's alright now, just close and reopen the PR.

@zhengyuan-cn Please use mvn spotless:apply to format the code.

@zhengyuan-cn Please use mvn spotless:apply to format the code.

OK, formated

@Hisoka-X @ic4y @hailin0  all checks have passed,  please review code.

sorry , I accidentally clicked on the review request

@Hisoka-X I accidentally clicked on the review request

cc @hailin0


Removed a few unneeded allocations

This is the last commit from us targeting short lived object allocations.  I've separated this from the other commits because this line might warrant some discussion.
-    // create a new vector is critical, because currentAntecedents will change later
-    this.antNodes = new ArrayList<HGNode>(antecedents);
+    this.antNodes = antecedents;

When I look at the usages of this I don't see exactly why we need this new vector.  Is this comment still relevant?  This line creates a significant amount of objects during decoding which a. is slow, and b. causes a lot of garbage collection.  I can share some TLAB measurements for this method if anyone would like to dig into the details.  If there are any edge cases I'm missing we can leave this section as is.

This was merged into master.

You can automatically close a PR by adding This closes #<PR number> when committing to ASF Git.

@hsaputra, I'm familiar with that notation for issues, but pull requests should close automatically when git notices that the commit ID has become part of the history for master...

Ah no, I mean ASF has github integration that would allow automatic PR close when being merged.

I also think it's a bit strange this didn't auto-close.  I'll close it manually since it's merged.


Vertex colors and sRGB textures

I'm guessing you might have seen this coming but as I've been using normal_ext and its subtypes to preserve the vertex coloring of models, it almost seems like there's a little bit of bad behavior when it comes to HDR and sRGB flags. When comparing a stock material side by side with a normal_ext material, there is a massive difference in the shading. As the stock material is more or less the "correct" color (as close as it can be with HDR) the normal_ext material actually goes almost pitch black in more shaded areas. I'm quite certain I've seen some note of this somewhere, something something vertex colors being forced into the wrong color space or so, but I couldn't find it and as such I couldn't figure out a convenient workaround for this.
So the big question is, can this be fixed any way at all or am I going to have to scrape off the paintwork?  :/
Alternatively, I guess I could just not use HDR in cases like this, but you know.

I may have to get back to you on this after I get the chance to do some testing. The normal and normal_ext shader both handle the vertex colors the same way (or at least are supposed to and do seem to) so I suspect something else is at play here. If I can find what is causing the difference I will do my best to fix it.

Did some testing (finally, again sorry about the delays on a lot of these). I couldn't seam to spot any difference (with HDR rendering) between a normal_ext material with sRGB textures and vertex colors and a normal material.
However I did spot something that could unknowingly be causing a problem with vertex colors. The StaticallyLit flag in materials can cause conflicts with models that were munged with -vertexlighting set. This conflicts could create problems or inconsistencies within a model. As such I have removed the flag starting from the next release. (A bit of a radical step I know, I may roll it back if anyone thinks it was a mistake.) This is strictly a a material_munge change and as such any materials/models munged with any previous versions tools will continue to function the same as before ingame.
Not actually sure if it'll help fix your problem or not but it should remove a potential pitfall from Shader Patch's materials in any case.

Just closing a couple old issues that I'm no longer sure how to approach looking into. This just let's me see more clearly what I do still need to look into. Feel free to reopen (or create new issues) if any of them are still having an obvious impact.

Just closing a couple old issues that I'm no longer sure how to approach looking into. This just let's me see more clearly what I do still need to look into. Feel free to reopen (or create new issues) if any of them are still having an obvious impact.


Fixing academy callout

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


[BUG]: Drizzle-kit introspect doesn't pull correct defautl statement

What version of drizzle-orm are you using?
0.33.0
What version of drizzle-kit are you using?
0.24.2
Describe the Bug
During introspect tables that have default value set as  timezone('utc'::text, now()) are getting pulled without wrapped sql operator like so default(timezone('utc'::text, now())).notNull(), which is invalid typescript code
Expected behavior
expected default(sql`timezone('utc'::text, now())\`).notNull(),
Environment & setup
No response

do you have a workaround for this @L-Mario564 ?

do you have a workaround for this @L-Mario564 ?

Not at the moment, you have to manually fix it for now.

Was fixed in<EMAIL_ADDRESS>


Don't work in Container Cloud

Hi bro.
I want deploy mediasoup on containers cloud , but tried any example and your example but doesn't work , all example works on cloud server , but doesn't work on cloud container , I used all IP that could to access , like , podIP , hostIP , public ip , private ip , ip , ip ... but all of them doesn't work , in webrtc chrome log is shown the iceCandidate is on checking state then  disconnected
do you know how to solve my problem
these days I trying on azure container could , do you test your example on that?
best regard for you.
thanks a lot.

When ICE candidates get stuck in the "checking" state, it usually indicates that WebRTC is unable to establish a connection, likely due to incorrect network configurations or firewall restrictions.
Here are a few steps that could help solve your issue:

Public IP Binding: In containerized environments, especially with Kubernetes or similar orchestration, the internal pod IPs aren't publicly accessible. Ensure that you are binding Mediasoup to the correct public IP of the host or the public-facing load balancer in front of your container.

ICE Candidate Policy: Try adjusting the ICE candidate policy to ensure all types of candidates (host, relay, srflx) are gathered. In some configurations, the container might be gathering host candidates, which aren't reachable from the public internet.

Port Mapping & Firewall Rules: Check your container's port mapping. Mediasoup needs both UDP and TCP ports to be exposed for WebRTC to work. Ensure your cloud provider allows traffic on the necessary ports (default 443 TCP for HTTPS, 3016 for this app, and range from 10000 to 10100 TCP/UDP for WebRTC media).

Azure Specifics: When using Azure, ensure that your network security group (NSG) rules allow inbound/outbound traffic on the WebRTC ports. Azure often blocks traffic to certain ports by default, so you’ll need to explicitly allow the media traffic.

Docker Networking: Containers by default operate in a private network, and you need to map their ports to the host. If you're using Kubernetes or Docker Swarm, consider using hostNetwork or proper ingress controllers to expose the Mediasoup service.

Cheers.


chore: add deno deploy adapter

#640  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on  Graphite


Teach findAccessedStorage about global addressors.

All but the last commit are covered by: https://github.com/apple/swift/pull/16870.
The only new change here is to enable strict verification of formal access on global variables and add unit tests.
AccessedStorage now properly represents access to global variables, even if they
haven't been fully optimized down to global_addr instructions.
This is essential for optimizing dynamic exclusivity checks. As a verified SIL property, all access to globals and class properties needs to be identifiable.

@shajrawi please look at just the last commit in this PR: https://github.com/apple/swift/pull/16877/commits/d72c91a242e8ff53b8f78fff5d37c2fcc4fc4c07

@swift-ci test.

@swift-ci test source compatibility.

Build failed
Swift Test OS X Platform
Git Sha - d72c91a242e8ff53b8f78fff5d37c2fcc4fc4c07

@swift-ci test.

Build failed
Swift Test Linux Platform
Git Sha - d72c91a242e8ff53b8f78fff5d37c2fcc4fc4c07

Build failed
Swift Test OS X Platform
Git Sha - d72c91a242e8ff53b8f78fff5d37c2fcc4fc4c07

@atrick d72c91a LGTM!

re PR - I do see this problem on the OS X bots:
Assertion failed: (address->getType().is<SILBoxType>()), function findAccessedStorage, file /Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/swift/lib/SIL/MemAccessUtils.cpp, line 269.


New Updated termsrv.dll  <IP_ADDRESS>.18928 26.01.2018

After update my Windows 8.1 i have this DLL
termsrv.dll
<IP_ADDRESS>.18928
26.01.2018
Patch is not working

Duplicate of #418.


Add Delete Confirmation

Add a confirmation dialog for the delete command, command will only be executed upon user's confirmation.
This dialog is in the form of a Alert box in which the user selects yes or cancel, to further optimise for CLI could adapt it to prompt user type "y/n" instead, in future iterations
For unit testing, bypass user confirmation by setting isConfirmed to be true
Closes #34

LGTM for v1.2.
For v1.3, please:

Optimise implementation
Create unit tests and update existing ones where necessary (ensure CodeCov passes)

Thanks!


Unknown location (problem with geolocation)

Just came across wttr.in, and of course, it doesn't work (by default) for me (I did learn about all of the options when coming here).
Anyway:
$ curl wttr.in
>>>    _  _    ___  _  _
>>>   | || |  / _ \| || |
>>>   | || |_| | | | || |_
>>>   |__   _| |_| |__   _|
>>>      |_|  \___/   |_|
>>>
>>>   404 UNKNOWN LOCATION: Seattle47.4902, Washington, United States
>>>
----
Weather report: Oymyakon

[...]

 We were unable to find your location
 so we have brought you to Oymyakon,
 one of the coldest permanently inhabited locales on the planet.

It looks like the code sort of discovered (but didn't parse correctly) the location.

Same thing here!
404 UNKNOWN LOCATION: Budapest47.5636, Hungary

I can acknowledge it. It is a bug

Can acknowledge it. It shows the same pattern of the location.

Same for Bonn, Germany:
curl -s wttr.in/Бонн\?format=j1
Unknown location; please try ~50.735851,7.10066%

Yea it keeps happening. Pretty sure it's the server being overloaded. Annoying but not sure there is much they can do about it?

In this issue we have three different problems:

Real code bug reported by @2011 and confirmed by me.
The problem @alexeygumirov reported (Unknown location; please try)
Geolocation service overload, that happens because of 1 and that causes rejections.

The first bug is now fixed, and the tests are running now.
The second problem may occur again, when wttr.in goes beyond its daily queries capacity.
We doubled the capacity recently (it will be effectively increased since 1 March 2021),
and so the problem should not occur so often.
The third one will hopefully also disappear, because it was indirectly caused by (1),
that is fixed now

Thanks for the fixing. I don't see issue anymore. Everything is fine last days.

This bug was pretty nasty, it affected almost 100k users in these two weeks:
$ ... | wc -l
88573

Very good that we fixed it now. Thank you for reporting and thank you for the help


object pickup radius is too large

Describe the bug
A clear and concise description of what the bug is.
Expected behavior
A clear and concise description of what you expected to happen.
Video
If it's problem with AI behaviour, add video to help explain your problem.
Environment details:

OS: [e.g. windows 10 / linux debian 10.4]
Engine: [e.g. rehlds <IP_ADDRESS>2 / vanilla 8684]
GameDLL: [e.g. regamedll <IP_ADDRESS>9 / vanilla]
Metamod: [e.g. metamod-r / metamod-p / metamod]
Bot Version: [e.g. 4.1.566]
Game mode: [e.g. csdm / public / zombie]

Additionally, please provide list of AMX Mod X plugins: amxx plugins and list of Metamod plugins: meta plugins.
Additional context
Add any other context about the problem here.

Describe the bug A clear and concise description of what the bug is.
Expected behavior A clear and concise description of what you expected to happen.
Video If it's problem with AI behaviour, add video to help explain your problem.
Environment details:

OS: [e.g. windows 10 / linux debian 10.4]
Engine: [e.g. rehlds <IP_ADDRESS>2 / vanilla 8684]
GameDLL: [e.g. regamedll <IP_ADDRESS>9 / vanilla]
Metamod: [e.g. metamod-r / metamod-p / metamod]
Bot Version: [e.g. 4.1.566]
Game mode: [e.g. csdm / public / zombie]

Additionally, please provide list of AMX Mod X plugins: amxx plugins and list of Metamod plugins: meta plugins.
Additional context Add any other context about the problem here.


Bitcoins lost, Not a sign of it now..

Hi
Operating System: Win 8.1
MultiBit Version: 0.5.18
Steps to replicate the problem: I was goin to trsnfer 0.31 BTC to localbitcoins, then when I looked on the site I saw there was no "incoming transactions". So I went back to MultiBit and checked the transaction history, and the transaction was there, but a white triangle and no loading... So I decided to "Reset Blockchain and transaction" and after that, thetransaction is totally gone, just like that. They have to be somewhere, and I really hopes for some help, advice etc.
I will be that glad if you can help me with this guys!

Problem solved, It was just the time to go and then " Reset blockchain and transactions again:)

Thanks for the update and glad it all worked out.
Closing.


XML host example

Hello, could you provide an XML host example, the documentation for XML is rather limited and i tried several things but couldnt enable JS highlighting. This is my case:
 <Module Name="Main">
<![CDATA[
   var obj = {};
   obj.car = { Name: 'car', HP: 135};
   obj.drive = function(car){...}
]]></Module>

Hi, unfortunately XML isn't one of the host languages currently. I'll leave this issue open as a to-do because it would be good one for a future update


tx_dist based rate estimation

Coverage increased (+0.8%) to 83.412% when pulling 15ae3b97678622a03f88dc5ad80f23d9c2730d30 on tdaede:fast_rdo_3 into 924a99999fdff2ce73b0e67cd9497437936068e1 on xiph:master.

I expect you will include the bdrate change by this commit? I think that will help us to figure out how this new feature impacts and when to enable it.
Also, some brief of how algorithm works will help us learn new thing as well.

It's still an enormous hit on video: https://beta.arewecompressedyet.com/?job=master-2019-03-04_132251-7ccee27&job=fast_rdo_3-2019-03-04_132256-c7eb04e
I'm going to try retraining it on objective-1-fast.

Retrained, it's still bad: https://beta.arewecompressedyet.com/?job=fast_rdo_3-2019-03-04_163321-32c0d25&job=master-64cf7a982a69b2461d9db1d5ab184eedb765992b
Quite likely the imprecision at low tx_dist.

OK, I disabled it at all speed levels and added the ability to enable it via speed_test. I think I will push it as is.


Update Steering Committee Members

Reflecting request from Kay
@kaywilliams, thanks for helping establish the SCITT Community and the general SCIIT efforts.

I can still only comment, not approve, but it looks good to me.

That should be fixed now!


Create GraphOperation interface

This interface will implement the Operation interface and the GraphOperationValidation interface.
This will then be implemented by all 'Graph' Operations, currently these:
AddElements - Graph
AddElementsFromFile - Graph
AddElementsFromHdfs - Graph
AddElementsFromKafka - Graph
AddElementsFromSocket - Graph
AddNamedView - Graph
AddSchemaToLibrary - Graph
AddStorePropertiesToLibrary - Graph
CountAllElementsDefaultView - Graph
CountGroups - Graph
DeleteNamedView - Graph
ExportToOtherAuthorisedGraph - Graph
ExportToOtherGraph - Graph
GenerateElements - Graph
GenerateObjects - Graph
GetAdjacentIds - Graph
GetAllElements - Graph
GetAllNamedViews - Graph
GetDataFrameOfElements - Graph
GetElements - Graph
GetElementsBetweenSets - Graph
GetElementsInRanges - Graph
GetElementsWithinSet - Graph
GetGraphFrameOfElements - Graph
GetJavaRDDOfAllElements - Graph
GetJavaRDDOfElements - Graph
GetJavaRDDOfElementsInRanges - Graph
GetRDDOfAllElements - Graph
GetRDDOfElements - Graph
GetRDDOfElementsInRanges - Graph
GetSchema - Graph
GetSetExport - Graph
GetWalks - Graph
ImportJavaRDDOfElements - Graph
ImportRDDOfElements - Graph
SampleElementsForSplitPoints - Graph
SummariseGroupOverRanges - Graph
ToEntitySeeds - Graph
ToVertices - Graph

This will be done as part of develop-2.

This is not going to be done.  The OperationValidation interface can be implemented by the Handlers themselves.


Fixed invalid memory reference in ARTED/preparation/prep_ps.f90

Thank you for fixing the problem, @yhirokawa san.


PLAT-75756:  Updated Scrollable to scroll by page keys when the pointer is over without any focused node.

Checklist

[x] I have read and understand the contribution guide
[x] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
The UX for the page navigation for VirtualList and Scroller component is updated, so those components should scroll 2/3 of the component's height by page up/down keys when the pointer is over the component and there is no item or scroll button is focused.
Resolution
Since the component should scroll by keydown of page keys without no focused node inside, it cannot catch an event if the keydown event handler is added to the node belongs to it. And, to check if the key event occurs when the pointer is over the component, we need to track the position of the pointer since we have no way to get the current position of the pointer in keydown handler.
To resolve these conditions, module-level event handlers for keydown and mousemove are added to document. mousemove handler keeps tracking the position of the pointer, and keydown handler informs the right component (a list or a scroller) that it should handle the key input.
Additional Considerations
To minimize any impact by event handlers and to be safe in prerendering, module-scope handlers are added.
Links
PLAT-75756
Comments

Hmm... Is it better to update a native version code also to match with JS version?

@0x64 - I've also rebased this on feature/ui-update and retargeted the PR in order to land this with the rest of the UX/GUI visual and behavior changes.


Filter by @MethodOwner won't work in test_run_rules

@Test
@MethodOwner(owner = "owner")
public void t1(){
System.out.println("1");
}
test_run_rules=OWNER=>owner
result in screenshot

Appears only in integrated development environment at the end of program, while report generated correctly, won't fix


CASSANDRA-18732 Baseline Diagnostic vtables for Accord

Accord PR: https://github.com/apache/cassandra-accord/pull/89


requestMatches() returns only one match

Hi there, I wonder how to return multiple matches using requestMatches() method. I didn't see any limit or offset parameters to be passed in. All it does now it returns an array of a single match object. Any possibilities to return more matches at the time?

OK, never mind, found the problem, looking through the code found that matches_requested is responsible for how many matches to return. Wasn't straight forward though.


johndanz/ch13561/issue-with-pl-s-not-looking-correct

https://app.clubhouse.io/augur/story/13561/issue-with-pl-s-not-looking-correct
fixed %s and values to take into account short/long positions and shares being sent.

looks like I can loose more than I'm trading. This trade is for multiple orders on the book.

The 2 screenshots above actually look correct to me. You can lose more than it costs you because we are talking about the position you will gain and it's potential max profit and loss. So from the examples above:
SELL 0.0061 shares @ .19 = 1 - .19 = .81 * 0.0061 = ~0.00494
BUY 0.006 shares @ .4 = .4 * 0.006 = 0.0024


can't adjust the size of the video display

the video plays in full screen and cant seems to adjust the size

windows 11.
it happens in reviewer only..
Anki 23.10.1
i disabled all addons and tried with only this addon on.

scrolling works fine... just that there is no way to make it small... probably have to add some codes in the styling for  scaling... like max width or max height

but i dont understand why it scales properly after disabling the addon and looks zoomed up with addon enabled

had to manually add it ...
can you make the addon to automatically add that parameter ?


Add systemd service file to use iota-pm as a daemon

I've wrote this systemd service file for my own use, and thought it can be useful for others.
The hardcoded IPs could be easily exported to a file in /etc/default/iota-pm and source it from there, haven't done it because that precise location changes from distro to distro using systemd.
Also notice the use of iota user as best practice.

Thanks for the contribution!


Generate JSON Schema automatically

We need to generate the JSON schema automatically from the source code for this repo instead of from Lumin Runtime.
Please have @ddubrow review

jest --json shall do the job


Created upload of profile picture.

This PR is for an upload Profile Picture as per #116
The image manipulation is through a new composer package "intervention/image" and is handled in an event.
As per #151 there is also a hires version of the image that is accessible by clicking the profile picture on the public profile view.

Before you potentially merge this I'd like to add perhaps a file size restriction (5mb?), and then delete the original uploaded image as well.

I'm rethinking the event firing - I don't like that the file name is being updated in the model potentially before the listener has executed

I think I'm there


Sphixn 6: Broken Logos and facicons

Sphinx 6 removes the logo and favicon html template variables.
These have been deprecated since sphinx 4 in favor of logo_url and favicon_url.
This will need to be resolved before the 1.2.0 release.

logo_url is fixed in https://github.com/readthedocs/sphinx_rtd_theme/pull/978/files

@Blendify did you ever see a deprecation warning about this change in your projects?
I'm wondering because it's reported that people haven't seen the deprecation warnings: https://github.com/sphinx-doc/sphinx/issues/11062

@Blendify did you ever see a deprecation warning about this change in your projects?
I'm wondering because it's reported that people haven't seen the deprecation warnings: sphinx-doc/sphinx#11062

I have never seen any warnings. I only realized when doing some testing for my projects before we upgraded versions.

I agree btw that this is a high-priority for the 1.2.0 roadmap - stuff breaks if we don't fix it. There's no idea in shipping the theme if logos and favicons disappear.. can't make that a known issue :)


UI: Ensure (all) experiments which can have their status updated, get their status updated.

What's changing
This PR fixes a UI bug where the status of an experiment is updated each time the page/route is navigated away and back to.
The experiments are loaded once to populate the table, then we mainly deal with updating the running jobs.
The change here just aligns the experiment and running job status when their IDs match. It's a short term/easy fix to keep the change small.
How to test it
Steps to test the changes:

Start Lumigator and the UI
2.Upload a dataset and create an experiment, then fairly quicky...
Navigate to datasets, then back to experiments - as the experiments table renders it shouldn't change from 'created' to 'pending' it should already show 'pending'

Additional notes for reviewers
A cleaner potential solution would probably look at how the experiments are updated in a single place.
I already...

[ ] Tested the changes in a working environment to ensure they work as expected
[ ] Added some tests for any new functionality
[ ] Updated the documentation (both comments in code and product documentation under /docs)
[ ] Checked if a (backend) DB migration step was required and included it if required

Closing in favour of https://github.com/mozilla-ai/lumigator/pull/542


Expand secure boot test to cover supported images on ARM

Reasons for exceptions to this test:
Debian 10 & 11 don't support secure boot on ARM.
Debian 12 supports secure boot on ARM and is currently working but it it's not enabled with the FAI build infra we're using for cloud images. Waiting to hear from Debian on whether they'll enable it upstream, otherwise we will do it and remove the exception.
Windows server 2012 core is working but difficult to test because the powershell secureboot cmdlet for checking if secure boot is enabled is not included by design on server core. It's EOL in less than 2 months anyway.
Rocky, RHEL, and SLES don't have signed shims for ARM. I've included a link to a ticket for tracking in the comments.

/lgtm


Bug in selecting todo item

if you delete all items and then add another one, and then click on checkbox of that item, it will add another one with same name.

This seems to be fixed by now.


Add prototypes & other fixes to address `gcc -Wall' warnings

After fixing the sources to build with ia16-elf-gcc, I
have also rebuilt and updated the TINYASM.EXE binary using
DeSmet C (3.1h).

I'm impressed that you managed to remove the obscure DeSmet C warnings! Thanks!

BTW your executable didn't worked with the provided test.bat file. I recompiled it again locally.

Hello @nanochess,

I'm impressed that you managed to remove the obscure DeSmet C warnings! Thanks!

Thank you!  I guess the real credit goes to GCC --- it is definitely a lot more bloated than DeSmet C, but its diagnostic messages are a bit clearer. :)

BTW your executable didn't worked with the provided test.bat file. I recompiled it again locally.

I will try to look into why the executable produced on my end is not working properly.  Thank you!

Hello @nanochess,
It turns out that I had omitted to apply the [http://www.desmet-c.com/ver_31n.shtml](3.1N patches) to DeSmet C.  Thank you!


Release 0.1.0

[x] merge all outstanding PRs
[x] ensure the versions have been bumped (check with doit)
[x] ensure the CHANGELOG is up-to-date

[x] move the new release to the top of the stack

[ ] validate on binder
[ ] validate on ReadTheDocs
[ ] wait for a successful build of main
[ ] download the dist archive and unpack somewhere (maybe a fresh dist)
[ ] create a new release through the GitHub UI

[ ] paste in the relevant CHANGELOG entries
[ ] upload the artifacts

[ ] actually upload to npm.com, pypi.orgcd dist
twine upload *.tar.gz *.whl
npm login
npm publish jupyrdf-jupyter-forcegraph-$VERSION.tgz
npm logout

[ ] postmortem

[ ] handle conda-forge feedstock tasks
[ ] validate on binder via simplest-possible gists
[ ] bump to next development version
[ ] bump the CACHE_EPOCH
[ ] rebuild yarn.lock
[ ] update release procedures with lessons learned

[ ] make the docs main panel bigger on full screen

[ ] remove or clean up the jupyterlab compat table

[ ] push mamba as recommended install mechanism

[ ] fill out how it works

[ ] add uninstall for mamba/conda

[ ] investigate better links and  signature in python API docs

[ ] fix npm link on readme


OCILIB and multithreaded server

Hello.
I have simple multithreaded server based on Crow framework (maybe someone is familiar to).
The architecture is very simple - there is a url, which server handling going in to Oracle throught OCILIB, make select and return result on client side. On each connection server creates a thread.
So I done stress test to my server and got a problem. I use jmeter and when I put 1 virtual user (which mean 1 thread) it is ok, and server handle it easy with any amount of load. But when I put 2 virtual users in my test (that is mean that there are 2 threads now) I got oracle unhandeled exception "ora-24550 signal received unhandled exception" and my server crashes.
Here it is the realization of select method of my data access object:
std::string Dao::selectData(std::string select) {

	std::string answer;

	try
	{
		Environment::Initialize();

		Connection con(db, schema, password);
		Statement st(con);
		st.Execute(select);

		Resultset rs = st.GetResultset();

		while (rs.Next())
		{
			answer.append(rs.Get<ostring>(4) + " - " + rs.Get<ostring>(6) + "\n");
		}
	}
	catch (std::exception& ex)
	{
		answer.clear();
		answer.append(ex.what());
	}

	Environment::Cleanup();

	return convertStringToUTF8(answer);
}

I got feeling that it must be different realization with OCILIB, if connection to Oracle creating from threaded program, and I use example which is works only with one threaded program.
Can you help me to build right solution for my needs?

@vrogier, thank you.


Allow (Fine-Grained) Port Configuration for Notebooks

VSCode launches notebooks using ipykernel_launcher with a command like this:
/home/username/bin/python3.8 -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9010 --control=9006 --hb=9005 --Session.signature_scheme="hmac-sha256" --Session.key=b"72dc9cca-e641-445a-9ceb-3ca5433dc8c0" --shell=9007 --transport="tcp" --iopub=9011 --f=/home/username/.local/share/jupyter/runtime/kernel-v2-3617206EN99MmVys9xf.json

There are four port numbers that get passed: stdin, control, iopub and hb(heartbeat). However there are no settings for Jupyter notebooks in VSCode to control the port assignment. The port assignment or the full command should be editable.

Setting "--control=9991" in jupyter.jupyterCommandLineArguments  does not work on VSCode v1.77.3
Setting "--NotebookApp.port=9999" in jupyter.jupyterCommandLineArguments  does not work on VSCode v1.77.3

Thanks for filing this issue,

Can I ask why you would like to control the ports used?
Currently its not possible to hardcode the ports, as the ports could be in use, e.g. if you run two kernels, then the ports you define in some setting will be used and the kernel will fail to start.

What we could do is try to start the ports from a pre-define port number, i.e. if you state 9050 as the starting port we could start generating ports from there, e.tg. 9050, 9051, 9052, 9053 and for the next notebook, use 9054, and so on. and when a kernel is shutdown we re-cycle the ports and start from 9050.
But before we go with that, I'd like to understand the need for this.

Thanks @DonJayamanne
My own use case is to keep certain ports clear for other applications that are finicky about ports. Since the Jupyter ecosystem has that ability it's frustrating to not have that control when using VSCode. Having the ability to set a starting port number should sufficient as long as the launcher can picks all four ports beyond the base number, as you suggested.
Cheers!

Out of curiosity, what option do you use to configure the port for the python kernels
Is it via cli or config file, please could you provide the coding name or cli argument used

I prefer to launch each kernel with its own options. So command line argument like --control=9991 are my preferred way.

What I meant was, how do you configure the ports today in Jupyter notebook/lab?

Thank you for this feature request, however there haven't been enough upvotes on this issue, hence closing this for now.


Enable storage server to serve https

Enables https on storage server by setting  storage-https-enabled flag and passing storage-cert-path.

storage-https-enabled is a bool, defaults to false
storage-cert-path is a directory containing tls.crt (certificate) and tls.key (private key).  It can be a Secret volume in k8s env.

@kvmw Thank you very much for your PR.
This topic came up in the Flux dev meeting a few weeks ago, so I created a RFC to formalise what we believe an implementation should look like. Some details are still up for debate, so I would ask you to engage on that PR in case you agree/disagree with the approach.
Once the RFC is in an implementable state, this PR could be the source controller implementation.


Add daemon flags for swarm join --swarm-join

- What I did
This fix tries to address the issue raised in #24087 to add a daemon flag --swarm-join, so that daemon could join a swarm cluster at startup. This should help with automation.
- How I did it
Additional flags
--swarm-join
--swarm-join-listen-addr
--swarm-join-advertise-addr
--swarm-join-token
have been added.
- How to verify it
An integration test has been added for test.
- Description for the changelog
Add --swarm-join,  --swarm-join-listen-addr, --swarm-join-advertise-addr, --swarm-join-token so that docker daemon could join a swarm cluster at startup time.
NOTE: This PR introduced multiple flags for docker daemon. The documentation will be updated if the naming of those flags are OK'ed.
This fix fixes #24087.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Thanks but things are still being figured out for these flags. See #24430 and #24237

Thanks @tiborvass. I didn't know #24430 and #24237 before. Will subscribe those two PR's for update. I think we can put this PR on hold for now.

@yongtang looks like this needs a rebase
also ping @aluzzardi PTAL

Thanks @thaJeztah @aluzzardi the pull request has been rebased. Please let me know if there are any issues.

ping @aluzzardi @diogomonica PTAL!

Not sure if we want this functionality in the first place. Seems like it has a few obvious drawbacks:
In particular:

The swarm-token needed to join the cluster is now visible as an argument to the daemon on ps
The swarm-token is written to disk on every engine that is configured this way.
If the remote administrator removes this node from the cluster, on the next reboot this will join as a new node automatically.

@diogomonica In general, the ability to pre-configure an engine to join a swarm (to me) looks like a nice feature; that way it's more easy to automate setup. I had the same concerns though about the token (I mentioned having an option for one-time tokens a while back, which would make this less of a security issue, as the token would be invalidated after first use)

@thaJeztah let's imagine that we do have a one-time token. Now what? If you have to individually configure a different swarm one-time token on each of your engines, how is that any different from simply running docker swarm join on each of your engines? (or calling the API)?

@diogomonica it would allow me to generate a list of tokens up-front, to use for joining nodes.

It's still a bit weird to have a flag that's only valid the first time it's used.
If someone takes the flag away is it expected to leave the swarm?

@thaJeztah and you would have to configure each daemon with their own manually configured one-time token?
Also, how would you do auto-scaling? Since tokens are one-time use, now instead of having one command/configuration to add new nodes, you have to dynamically inject tokens.
Additionally, how many tokens would you generate? If you generate 100 one-time tokens, and there is a big spike in the autoscaler and it needs to spin up 1000 machines, what happens then?

Tokens end up in your .bash_history, so having them automatically invalidated could still be useful (but it's a separate discussion)

I'm a definite 👎  on this one.
We already do have a flag on the daemon to set the default advertise addr.
Everything else just gets weird.

Following the discussion, it looks like this change won't be accepted, so I'll close this. I'll open a more generic issue to make improvements w.r.t. automated setup of a Swarm, so that we can discuss options.
Sorry for that @yongtang, thanks so much for your work on this


IPv6 Support

Is your feature request related to a problem? Please describe.
We are using a IPv6 only kubernetes cluster hosted by a third party. Would it be possible to make cadence listen on v6 addresses for all the ports?
Proposed Solution
Would you accept PR for this?

Hi @StarAurryon , could you describe the proposed solution? We would love to accept PRs for those improvements.

The first things I saw is that bindOnIP does not support IPv6 addresses. And if we don't provide this entry in the yaml file, it choose not to listen on all interfaces but on the first ipv4 which is <IP_ADDRESS>. So we are stuck with v4 for now (history, frontend, worker, etc).
In the same way specifying [::]:9090 for metrics fall back to Ipv4.
{"level":"info","ts":"2021-11-02T16:48:22.419+0100","msg":"Listening for GRPC requests","service":"cadence-matching","address":"<IP_ADDRESS>:7835","logging-call-at":"rpc.go:106"}
{"level":"info","ts":"2021-11-02T16:48:22.495+0100","msg":"Add new peers by DNS lookup","service":"cadence-frontend","address":"cadence.cadence.svc.k8s","addresses":"[fd00:3:40:1:3::161:7933 fd00:1:40:1:3::19d:7933]","logging-call-at":"clientBean.go:321"} {"level":"info","ts":"2021-11-02T16:48:22.496+0100","msg":"Add new peers by DNS lookup","service":"cadence-frontend","address":"cadence.cadence.svc.k8s","addresses":"[fd00:1:40:1:3::19d:7933 fd00:3:40:1:3::161:7933]","logging-call-at":"clientBean.go:321"}
There are no error for ringpop. So I believe, but correct me if I'm wrong, we just need to parse IPv6 correctly.
I'm starting to write something on my own to see if there is more errors after this.

Sounds good. That sounds trivial. But I would encourage you to test it out first, following this instructions: https://github.com/uber/cadence/blob/master/CONTRIBUTING.md

I just tested my ~3 lines fix on my K8S cluster. It is working like a charm on production for a trial activation workflow.
Basically, what the fix is doing:
`-       hostAddress := fmt.Sprintf("%v:%v", d.getListenIP(), d.config.Port)

  hostAddress := net.JoinHostPort(d.getListenIP().String(), strconv.Itoa(d.config.Port))

         grpcAddress := fmt.Sprintf("%v:%v", d.getListenIP(), d.config.GRPCPort)

          grpcAddress := net.JoinHostPort(d.getListenIP().String(), strconv.Itoa(d.config.GRPCPort))`

And allowing IPv6 with ip.To16() check in the config file.
I will make a PR in the coming days.

Just a simple question : When will I see my fix in the Docker packages on Dockerhub?
At first, I did this PR in order to be lazy and not maintain my own builds ;-)

Just a simple question : When will I see my fix in the Docker packages on Dockerhub?
At first, I did this PR in order to be lazy and not maintain my own builds ;-)

I just made a 0.22.4 patch release. I wanted to include this but  I wasn't able to cherry-pick this commit into 0.22.x or 0.23.x release branch for v0.22.4 or 0.23.0 release.
https://github.com/uber/cadence/tree/0.23.x
https://github.com/uber/cadence/tree/0.22.x
Because the code change you made on top of files that don't exist in any of the two branches.
Would you mind waiting until 0.24.0 ?
If not you can make another PR for merging into any of the release branch and I will review it again.

No worry, that was just to know. I don't have any issue with my current build.
Thanks again for merging me. Have a nice day.


Make Signer Trait more flexible on asn1 formating

The js_signer mod formats signature as asn1 in the rust code, because the current TypeScript implementation does not do the asn1 formatting.
However, there is a posibility that some JavaScript signer already includes the asn1 formatting. We should provide the flexibility to disable the asn1 formatting in the Rust code.

Instead of having the single JsSigner::new, we can make the change to have two public constructors
impl JsSigner {
    // The JS function should be of type
    // `(input: Uint8Array) => Promise<Uint8Array>`.
    // The JS function returns the raw signature, which contains exactly 64 bytes.
    pub fn new(js_function: JsFunction) -> Self {
          todo!()
    }
    // The JS function should be of type
    // `(input: Uint8Array) => Promise<Uint8Array>`.
    // The JS function returns the signature in ASN1 format.
    pub fn new_with_asn1(js_function: JsFunction) -> Self {
          todo!()
    }
}

This sounds reasonable.


Update conference-best-practices.md

Changed the starting para to make it more streamlined.
Enhanced a few sentences to be grammatically correct
Minor other changes

@robcube looks like only the auth users can merge this.

leaving the merge to @CathPag

Great improvements! (...and sorry for the delay!)


[0.9.x] [KOGITO-1927] [cherry-pick] Add load_default_config option for testsand updated pipelines to use …

…it for tests
cherry-pick from https://github.com/kiegroup/kogito-cloud-operator/pull/270
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

tests passed


Segmentation fault on program exit

I'm having segfaults after using a simple empty debug callback, on program exit on glow 0.13:
            gl.enable(glow::DEBUG_OUTPUT);
            gl.debug_message_callback(|_source, _etype, id, severity, message| { });

This happens when my program exits due to an error (not caused by a panic). It seems like this was fixed recently, yet I'm having the issue on the latest version of glow. This is the debugger trace:
(lldb) run
Process 102361 launched: '...' (x86_64)
INFO<PHONE_NUMBER>06 OpenGL 4.6, (Core Profile) Mesa 23.2.1-arch1.2
INFO<PHONE_NUMBER>09 window size: 1456x1058
Process 102361 stopped
* thread #4, name = 'foobar:sh0', stop reason = signal SIGSEGV: invalid address (fault address: 0x20)
    frame #0: 0x0000000000000020
error: memory read failed for 0x0
(lldb) bt
* thread #4, name = 'foobar:sh0', stop reason = signal SIGSEGV: invalid address (fault address: 0x20)
  * frame #0: 0x0000000000000020
    frame #1: 0x00005555556531a4 foobar`_$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..FnMut$LT$Args$GT$$GT$::call_mut::h923ad6372d86c0d3(self=0x0000555555d59720, args=(u32, u32, u32, u32, &str) @ 0x00007fffe95fb7c0) at boxed.rs:2014:9
    frame #2: 0x000055555565734f foobar`glow::native::raw_debug_message_callback::_$u7b$$u7b$closure$u7d$$u7d$::h71d3628e04cf41b5 at native.rs:3113:9
    frame #3: 0x000055555565150a foobar`std::panicking::try::do_call::h439efb1ac5fe7501(data=" \x97\xd5UUU") at panicking.rs:504:40
    frame #4: 0x00005555556547db foobar`__rust_try + 27
    frame #5: 0x000055555565148f foobar`std::panicking::try::h01a7f4768dd62b95(f=<unavailable>) at panicking.rs:468:19
    frame #6: 0x000055555565143a foobar`std::panic::catch_unwind::hf0c312082775ca11(f=<unavailable>) at panic.rs:142:14
    frame #7: 0x0000555555657260 foobar`glow::native::raw_debug_message_callback::h10fe80b2552a55f9(source=33352, gltype=33361, id=1, severity=33387, length=201, message="Shader Stats: SGPRS: 16 VGPRS: 8 Code Size: 76 LDS: 0 Scratch: 0 Max Waves: 16 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 Outputs: 0 PatchOutputs: 0 DivergentLoop: 0 InlineUniforms: 0 (CS, W64)", user_param=0x0000555555d59720) at native.rs:3109:19
    frame #8: 0x00007ffff5508228 radeonsi_dri.so`___lldb_unnamed_symbol10428 + 168
    frame #9: 0x00007ffff54ac184 radeonsi_dri.so`___lldb_unnamed_symbol9517 + 52
    frame #10: 0x00007ffff52d2080 radeonsi_dri.so`___lldb_unnamed_symbol2926 + 160
    frame #11: 0x00007ffff5a3f553 radeonsi_dri.so`___lldb_unnamed_symbol19728 + 323
    frame #12: 0x00007ffff5a9c180 radeonsi_dri.so`___lldb_unnamed_symbol20175 + 560
    frame #13: 0x00007ffff52d1c1d radeonsi_dri.so`___lldb_unnamed_symbol2924 + 333
    frame #14: 0x00007ffff531ca0c radeonsi_dri.so`___lldb_unnamed_symbol4215 + 28
    frame #15: 0x00007ffff7bf99eb libc.so.6`___lldb_unnamed_symbol3598 + 731
    frame #16: 0x00007ffff7c7d7cc libc.so.6`___lldb_unnamed_symbol4045 + 7

Thanks for the bug report! Could you make a small test case that we could use to check the drop order? Maybe the callback is being dropped too early for some reason.

@cloudhead would you mind checking if #274 helps with this? I'm guessing the callback fires after the context is dropped which causes the problem here, so maybe the fix is to unset the callback like that PR does.

Ah yes, sorry for dropping the ball, I couldn't easily reproduce it with a smaller codebase and then gave up. Will try that PR.

Yes, I can confirm #274 fixes this issue!

Awesome, thanks for confirming!


Wednesday (2019-02-06) tasks

Here are a few things that I will be doing today

[ ] Fix broken links to Figures and Sections in fecundity text
[ ] Go through Tables and make sure that everything is working properly (e.g., formatting)
[ ] send hake assessment to US JTC member's supervisor for review

Feel free to assign me other tasks as well.

I need to do the fecundity sensitivity section and fill in missing refs to it. For some reason, it appears that my commit 55c8887bf057e12c27d1f9ee1f56d3a62dbb1536 has been undone somehow!

I'll work on updating remaining section 2 text, and will commit often as most of this will go quickly I think.

[ ] Section 2 text complete - Aaron to do.

After that we have to update sections:

[ ] 3.1 Modeling History
[ ] 3.5 Model Uncertainty
[ ] 3.6 Reference Points
[ ] 3.7 Model Projections
[ ] 3.9 Retrospective Analysis

Of course, the whole thing will need a second/third/etc pass through.  I'd like to have the above sections at least gone through a first pass before Kelli/Aaron send to Owen later today.
Also, make sure the updated acknowledgement section pertaining to Ian seems reasonable (first two sentences):
[We thank the authors of previous assessments whose work remains an influential part of this assessment.
In particular, we thank Ian Taylor for his insightful comments and continued assistance with
questions relating to Stock Synthesis, the r4ss package, and hake population dynamics in general.]

@cgrandin it just hasn't been merged it looks like. It says I am two commits behind you and one ahead. What should we do?

It's ok, I cherry-picked the commit and re-committed just now. Should be fine if you merge

Kelli, your network graph looks like this:

So you should merge aaron and I in. I'm just checking to see if this is how you are doing it as we aren't using pull requests

Yep, merge anyone in who has stuff that you don't. Then others can merge you into theirs.
I'll do the weight-at-age description stuff, #524.

Got it!

Looking at the network graph before you merge helps, since someone probably already merged everyone else's in and so you usually only have to merge one person at that point

Yes merge until you only see your name on your graph.

Right, and towards the end when we commit small text edits we all become merginators!

On Feb 6, 2019, at 9:05 AM, Andrew Edwards<EMAIL_ADDRESS>wrote:
Yes merge until you only see your name on your graph.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Almost all of model projection section is complete but need someone to look at and fill in the values for the age comp projection part. @kellijohnson do you know where those numbers come from? Thanks

Also there is a DFO provisionary in-the-healthy-zone value of 96% which I'm unsure where to find or calculate. @andrew-edwards did you do this last year?

I will look.
Also, I think the DFO numbers are in base.model$risk
On Wed, Feb 6, 2019 at 9:40 AM Chris Grandin<EMAIL_ADDRESS>wrote:

Also there is a DFO provisionary in-the-healthy-zone value of 96% which
I'm unsure where to find or calculate. @andrew-edwards
https://github.com/andrew-edwards did you do this last year?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cgrandin/hake-assessment/issues/534#issuecomment-461116067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6xFFU71QfOJnkI1CuuXGofxBXWrRTCks5vKxOSgaJpZM4alcnJ
.

--
Kelli Faye Johnson, PhD
Research Fish Biologist
Northwest Fisheries Science Center
National Marine Fisheries Service
2725 Montlake Boulevard East
Seattle, Washington 98112
(206) 860-2465
<EMAIL_ADDRESS>

it's in the variable dfo2019 (I thought it says that in a comment by the text - this was done quickly last year).  I think there's ajoint probability value mentioned somewhere also, but the calculation is in a comment also.

Age comp in numbers is
setNames(round(apply(base.model$extra.mcmc$natsel.prop, 2, median)* 100, digits = 0), paste("Age", 0:20))

Okay, I lost a commit from yesterday also (maybe more). Please do a diff before commiting to double check what you've changed....

Working on 3.1 ...

diff is my standard routine as well as making sure everything I'm working on is saved before merging/committing.

Hmmm..... It's actually the re-editing of a file - see my comment on one of the recent commits.

I'll do the hardwired numbers at the end of 3.7 (DFO-related and others). @kellijohnson  you weren't doing any of this, correct?

@cgrandin nope, i am editing 3.1, so code away :)

Should I do 3.5 or 3.6?

NM is @cgrandin is, just realized what sections those were. What else is there that someone isn't working on?

Kelli, how about going through table/figure captions and updating those as needed?  I think you need to pay particular attention to those with '**"

I'm doing 3.6 DFO paragraph (it's related to the later one I was doing). Sorry for not mentioning. I'll do all of 3.6 then.

Be good to decide which MCMC appendices to keep (it's slowing down the build a bit). Without looking at the results (!) I think the ones that Chris mentioned once - Run 53 (last year's base) and 54 (this year's base with different assumption for 2018+ weight-at-age). They are the two closest to the 2019 base model.

I agree with those for now. We always have the others if they need to be seen. If nobody objects, I will comment the rest out and modify refs as required.

Could first upload the .current pdf to Google Drive so we have them built (and can look at when we have time....)

Haha too late

I saw! I'll do it before merging.
hake-assessment-all-fec-mcmcs.pdf

I'm done for the day. Couple of checkboxes in this issue didn't get checked (maybe carry over to Thursday?).
Also noticed we thank the SRG for a smoothly run meeting - a bit premature? I think we usually comment that bit out then put it in after the meeting....

I'm closing this and moving Model uncertainty section to Thursday tasks


[webview_flutter_wkwebview] Fix typo of a method name, setCookieForInsances

Just fixed a typo of a method name, from setCookieForInsances to setCookieForInstances
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hi @KosukeSaigusa, thanks for fixing this.
Could you updated the CHANGELOG by following: https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#updating-a-changelog-that-has-a-next.

Thank you for your message, @bparrishMines.
Now I updated the CHANGELOG.md in this commit: https://github.com/flutter/plugins/pull/6102/commits/cec0ebcbc33ce08a6a75c95c10edeb5ca7f9371b

@bparrishMines
Thank you. Resolved the conflict and updated the grammar.

Is the only thing remaining here the CHANGELOG issue?  @KosukeSaigusa can you rebase/merge onto top of tree and make sure your pubpsec and CHANGELOG version matches?

Friendly ping, @KosukeSaigusa, this is so close to being mergeable! 🙂


Add favicons

@geoRG77 This is not the way we should do things - it will be hard to keep this repo up to date with current Este. These custom things that we need should be distributed as npm packages and then inserted into the app when needed.
We have the awesome tool este-cli which can bootstrap the application without the TODO-MVC stuff (it now even supports removing semicolons!) – tha's the way to go for us.

Currently it's quite easy to keep this repo updated, I did 2 or 3 updates with git rebase upstream/master and never meet serious issues.
I consider this as a core feature as I'm sure this will be used in all of our webapps and by doing this not in core I ended up in solving same issues in multiple projects instead of doing it once and forever.

Keeping forks of open source projects with a few improvements/fixes is not the way I would like us to work in Blueberry. I am going to delete this fork, please back it up somewhere.


ProviderCredentials.UserId does not return the same value that the MobileAppUser.UserId did

MobileAppUser is gone (understood) and the replacement to get UserId, ProviderCredentials, returns an email address rather than the original UserId that the MobileAppuser did. This is with Microsoft.Azure.Mobile.Server.Authentication.<IP_ADDRESS>. This also affects the Mobile App UserId because it is still returning a "sid:value" which is now the same for users of different providers that have the same email address specified on each provider.

Is it possible for UserId to return the claim: nameidentifier, so we can grab the unique provider assigned id from UserId? If not, can we get a better understanding of how UserId is created and whether it will stay the same between versions (it has been changing from "Provider:someid" to "sid:somedifferentid" now to "email".

I've found that calling the following:
ClaimsPrincipal user = this.User as ClaimsPrincipal;
var userId = user.GetUserId();
returns the same UserId as the MobileAppUser used to: "sid:guid".
where the GetUserId extension method is as follows:
public static string GetUserId(this ClaimsPrincipal principal)
{
if (principal == null)
{
throw new ArgumentNullException(nameof(principal));
}
return principal.FindFirstValue(ClaimTypes.NameIdentifier);
}
public static string FindFirstValue(this ClaimsPrincipal principal, string claimType)
{
if (principal == null)
{
throw new ArgumentNullException(nameof(principal));
}
var claim = principal.FindFirst(claimType);
return claim != null ? claim.Value : null;
}

To clarify:
//
ClaimsPrincipal user = this.User as ClaimsPrincipal;
GetNameIdentifierClaim();
//NameIdentifier Claim returns the "sid:guid"
//
ProviderCredentials identity = await user.GetAppServiceIdentityAsync(request);
identity.UserId = "user email address"
//
MobileService.CurrentUser.UserId // returns the same "sid:guid" as the ClaimsPrincipal method
//
both the 1st and 2nd UserId values are the same for a Google Account and Facebook Account that have the same primary email address

In your last example, 1 and 2 are called on the server and 3 is called on the client, correct?
Yes, this has changed with the move to using the new App Service Authentication.
The NameIdentifier claim (sid:identifier) is a unique id that App Service Authentication creates that will identify this user for your application. As you've seen, each of these ids can map to one or more ProviderCredentials that has provider-specific data that you can get via GetAppServiceIdentityAsync.
The ProviderCredentials.UserId value depends on the provider, but it tries to use the email registered with the provider so it can automatically link the provider creds with a single sid on your service.
So if you want to identify a user within your app, using the 'sid:identifier' id is the way to do it.
We'll have some deeper docs coming out on this in the future, but let me know if you have any other immediate questions that I can help answer.

You are correct about the server and client question.
It was intentional then that a user who logs into my app using their Facebook and then their Google account, when the ProviderCredentials.UserId from both services is their email address and they match, will have the same "sid:identifier"?
It sounds like I should still store the unique provider user id as I've seen the "sid:identifier" change between versions and services. Storing it with the sid:identifier at least gives me a way to map up users if the "sid:identifier" ever changes in the future.
Also, what happens if the email address from one of the services changes? Does their "sid:identifier" now change?
On a side, but related note, in an ASP.NET 5 RC1 Web Application with the same service auth ClientID/AppID and ClientSecret/ClientID as my mobile app, the HttpContext.User.GetUserId() functionality returns a completely different id. Is there anyway to match these with my previous examples 1 and 3?
When creating a Mobile App, Azure SQL Backend, and an ASP.NET Web Application accessing the same data, and the UserId information doesn't match, it makes it so I need to resort to using the Provider Specific User ID for matching up records in the DB.
Is there a different recommended approach for doing a Mobile App/ASP.NET Web App/Single Azure SQL Backend for an application while getting all of the specific functionality per mobile and web?
Thanks for taking the time on this,
John

I use User.Identity.GetUserId(); from the IdentityExtensions of Microsoft.AspNet.Identity.Core.
No cast needed, works like a charm even with my custom auth. But I admit it's kind of weird to have the email address in ProviderCredentials' UserId.

Let me backtrack on what I said above (sorry!) -- as you mentioned, the registered email of a user with a provider may change, which means the generated 'sid:identifier' for that user would change. For example, I logged in with Facebook, looked at my sid, changed my primary email, and verified that my sid was now different.
The sid is unique to App Service Authentication and is used internally as an id to store the other claims from the provider in a token store. GetAppServiceIdentityAsync() pulls those claims from the token store and turns them into a ProviderCredentials object.
That being said, the best id to use to uniquely identify a user, is to use the provider's unique id (I misspoke when I said to use the sid above). Even if the email changes, the unique id will not. For Mobile Apps, that is available via the ClaimTypes.NameIdentifier claim from the ProviderCredentials.Claims array.
You're right that it does feel odd that we're surfacing the email now as the user id, when that may change. I'll see if we can address that.
As for how other backends surface their user ids, I'll have to investigate that. If the other backend is not using App Service Authentication, then what they surface as the user id will be different. However, any authentication using the same provider client id should contain that provider's unique id somewhere in their claims. I've not set this up in ASP.NET 5 yet -- what value does it return as the user id? Do you get the provider's unique id also?

@brettsam Thanks for looking into this further.
What you've stated sounds accurate to what I've seen from my tests. On the ASP.NET 5 side of things, it looks like the NameIdentifier claim returns the guid that is created in the database that it creates, however, I haven't had much time for testing to see if it's possible to find the provider unique id in those claims. I'll do some testing and report back if it's available.
Currently, it sounds like using the Provider Unique Id is the way to go. It adds a little bit of code to each call on the server side to make sure that we only return the records for that user, but it's doable. At least I shouldn't have to worry about losing the user info as long as that Provider Unique Id does not change.
On the Facebook side of things, the user id is per app, but they do have a means of using the business api to get the unique ids for a user to your apps, so you can "translate" between the ids based on the apps if using the same backend database between those apps.

@brettsam
In the ASP.NET 5 application I am able to get the Unique Provider Id using the following code:
'var info = await _signInManager.GetExternalLoginInfoAsync();
var uniqueProviderId = info.ExternalPrincipal.FindFirstValue(ClaimTypes.NameIdentifier);'

I recently migrated to Azure Mobile App from AMS - I am using custom authentication as well as Providers...I have Providers working fine but the custom auth is failing to work correctly.  I have verified that it generates a token via the AppServiceLoginHandler.CreateToken successfully and the token is in the client request X-ZUMO-AUTH header, however, the requests are failing with 401 unauthorized.  I have verified that my signingKey has what appears to be a valid value...I am convinced that something is wrong with the custom token since the providers are working which makes me thank it is claim/audience/issuer issue.  Any chance you could point me in correct direction to trouble shoot this further?  I am using the JwtRegisteredClaimNames.Sub claim per the few samples I have been able to find on the web and I am using my Azure Mobile App URL for audience and issuer - does all that sound correct?

I noticed audience and issuer need a / at the end of the address to work, could this solve your issue?

Thank you very much Paul - that was it!  added trailing / and it is working now.

Glad I could help :+1:

@PaulARoy - thanks for the tip with the trailing "/" - this solved my problem with debugging authentication locally. maybe this could be added in the documentation (https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-dotnet-backend-how-to-use-server-sdk/#how-to-debug-and-troubleshoot-the-net-server-sdk)

Perfect :)
I would be relevant yes.

Hi,
After reading through this, I still don't understand this:
How do you match provides ID when you are doing verification on Mobile devices (Windows, Xamarin.ios) as methods that are available on .net that are mentioned here are not available on mobile devices and we are still getting only SID that does not match what we already have in database.
We were using uniqueID from providers to identify our users in SQL database and it worked like charm on MobileServices. Now we want to migrate and have problem how our apps get to data stored in database.
I am unable to find anything about this and its major problem.

@messvk the user object on the client SDKs will only have the SID populated in it now.  If you need to get additional information about the user you can either:

Call a custom API / table API that will get the additional information for you from the server (and use the above logic) post login.
Use a client directed auth patten (get the id from fb/etc directly, and then pass the auth token to login to the app service app)

@phvannor

I am not sure if i follow, can i send SID to custom API hat will get from sid user ID through methods on top? Or we need to somehow login on server side instead client side?
what do you mean by ◦Use a client directed auth patten?  Do you mean implement it directly through providers API instead of Azure?

Whole point is to avoid updating client apps, because each update takes 2 weeks to certificate and its pain in the a** changing stuff like that in production environment without causing any disturbance in service and not mentioning cost of additional work that needs to be spend...

One you are authenticated on the client (via client.login, etc) any request you make to you mobile app (or service) will have a X-ZUMO-AUTH header.  That header will auto populate the user object mentioned above, so you can just stand up a custom API, hit it, and use the above code, no other actions should ne needed.
Option 2, is more invasive and yeah, would be using the provider's APIs directly.  The calling the login+token method on the client.
I agree on having to make client changes in a pain, there are a handful of client-server contract breaking changes in the service to apps migration that should be called out in the migrate docs and if not, need to be. (@mahender can you look?)
Is your SQL filtering happening locally on the device against a local SQL db, or on the server?  If the latter, there are additional options here.  Your table script can be the one adding the filter based on the logged in user, and avoid having the client care.

@phvannor
I understand the first part now, thank you.
Unfortunately its not that simple with us, as we are are providing heavily encrypted service with local encrypted database, asymetric encryption while communicating and than azure SQL, also encrypted where we have users and data.
problem is, that we are using this ID as part of generated security and communication, so we would have to change some of logic and it will add another unnecessary step, in order to provide access to locally stored data and communication with server, again cant be done without changing client apps...
Currently old mobile service that was migrated works as before, but we would like to use new features in full someday, so for me it would be great if we got at least info, if those data will be some day available in client or we have to do all this work ourselves.
We were very early adopters of azure, and spend lot of money and effort in building our service around it (that could be done on SAP HANA instead), and this feels like backstabbing changing crucial part of service in this radical way.

@mattchenderson can you comment on plans re: above?

Hi,
I have the same question as @renzska with two different Id for same user, ASP.NET 5 Web App and xamarin.iOS app
Setup:
Azure WebApp ASP.NET 5 with API Controllers
Xamarin iOS App with Microsoft.WindowsAzure.Mobile.Client Nuget
Azure B2C AAD
When the user has authenticated from Web App I get the objectId:
var userClaim = ClaimsPrincipal.Current.FindFirst("http://schemas.microsoft.com/identity/claims/objectidentifier").Value;
While from Mobile App there is no objectIdentifier, only nameidentifier
var mobileClaim = ClaimsPrincipal.Current.FindFirst("http://schemas.microsoft.com/identity/claims/nameidentifier").Value;
The id's are not the same while the user is the same in AAD, for know I need to store two id's for a user in my DB in order to identify the user.
How can I retrieve the same id and which Id is the correct to use ?

Closing this issue as the original issue has been answered.  If anyone on the thread has additional issues (e.g. @JanCB ), then please post another question.  Thanks,

I have UWP app backend is azure mobile app service. I have configured azure b2c as authnetication. from last six month it is working fine.
on my client  side  i am using  DefaultManager.CurrentClient.CurrentUser.UserId which give me userid {sid:value} format.
on server side  this code was also giving {sid:value} and provider was aad
var identity = User as ClaimsPrincipal;
var userClaim = identity?.Claims.FirstOrDefault(b => b.Type == ClaimTypes.NameIdentifier);
Now from yesterday it is giving directly from b2c.
when i send the same request to local code it works as expected. but if i  debug uisng attcahing to azure mobile app. i am getting the same different value.


bug: Press space is quitting neovim

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.1
Operating system/version
MacOS 14.5
Describe the bug
Everytime that I open lazyvim when I'm in the command mode and press space it's going back to the terminal.
Steps To Reproduce

Just open neovim

Expected Behavior
Space open the lazyvim options, and works as
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "LazyVim/LazyVim", import = "lazyvim.plugins" },
    -- add any other plugins here
  },
})

Can you show a video?

Also, since you mentioned it happens in the command mode what does :verbose cmap <space> show? I can't reproduce this with default LazyVim installation.

Here it's the video https://asciinema.org/a/LFm3WM4PBbKTeDuq67NanQcEJ
About the result of the command it returns 'no association found'

Recording of the :verbose cmap <space> result:  https://asciinema.org/a/jlpDlB2hLIxvsICverhcLEk2f

Can you try the following?
1. mkdir ~/.config/lazytest
2. git clone https://github.com/LazyVim/starter ~/.config/lazytest
3. NVIM_APPNAME=lazytest nvim and wait for the installation to complete
4. While Lazy UI is still open press `C` to check and `U` to make sure everything is updated
5. Restart Neovim with command from step 3

Do you observe the same behavior?
For cleanup do
rm -rf ~/.config/lazytest
rm -rf ~/.local/share/lazytest
rm -rf ~/.local/state/lazytest
rm -rf ~/.cache/lazytest

No the behaviour doesn't happen. The strange thing is that I use the same configuration in another machine and it works like a charm.

https://github.com/annacruz/nvim is the configuration that I'm using.

What you've just tried is a default Lazyvim installation with no user configuration present. That means there's something in your personal configuration causing this and it's not a Lazyvim bug. I don't know what is causing this, but you should try disabling some things until you find the culprit.

Yeah... I'll try to make the configuration manually one piece by one, it's the best. Thanks for your support!

I would suggest you to backup your current configuration and then start from scratch enabling one piece of your current configuration in the new configuration at a time. Essentially the installation steps mentioned on the website.

Quitting without a map on space tells me it is possibly a crash rather than a quit. To check if it is a quit vs a crash, if you run nvim && echo exited ok, press space, and "exited ok" prints to the terminal, that says nvim exited normally. If you run nvim || echo crashed and do the same, the print to terminal will say nvim crashed.
If it's a crash, might need to reinstall neovim. Also make sure treesitter parsers are up to date (:TSUpdate), I've had crashes from that in the past.

Just as an info it's crashing, I'm trying to check the reasons of the crash before close the issue

Reinstalled everything including putting again the configuration solve the issue. Might had passed some trash. Thanks for help me debugging.


Add remove W&B image to export_nbs

Currently, when we export the nbs, there's W&B images in the first cell of each notebook which breaks it integrating into docodile.
We need to remove that image from each during export so that the # title is the first cell. This is what determines the title in the docs.

Do you want me to remove the image, or move It down?


AndroidX的问题

AndroidAutoSize-v1.2.1.aar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.

https://github.com/JessYanCoding/AndroidAutoSize/issues/352#issuecomment-874418441


Fixes a few layout issues in lesson screens

Replacing grid with flex layout to fix a few issues. Also removing some unnecessary Tailwind tags.
Should fix issue #214 and the problem pointed out in this comment: https://github.com/saving-satoshi/saving-satoshi/pull/146#issuecomment-1450874989
I'd recommend avoiding grid in favor of flex box. I only saw it in a few places in the codebase and on those a grid wasn't even used (meaning multiple rows and columns), but it's either a row a column. Safari follows an older spec in regards to height calculation, which caused one of the layout issue mentioned above.
Overall I also see a lot of unnecessary layout tags that have no effect. I wonder if everyone is clear on exactly how flexbox works. If not, I recommend this guide.
Live site:

Preview:

Live site:

Preview:

tACK!


config is not loaded from $HOME/.config/shell-craft/config.json due to improper usage of ~ in path

https://github.com/JohnnyIrvin/shell-craft/blob/26a7af762f5eb905105b55d6c4b870946a2d577f/shell_craft/cli/main.py#L43
Needs to use os.path.expanduser

Fixed in https://github.com/JohnnyIrvin/shell-craft/releases/tag/v1.1.1


Installation in ubuntu not working: 404 not found

When i try to install hummingbot within ubuntu i get the following error: 404 not found
wget https://raw.githubusercontent.com/hummingbot/hummingbot/master/installation/docker-commands/create.sh
--2023-04-13 02:26:43--  https://raw.githubusercontent.com/hummingbot/hummingbot/master/installation/docker-commands/create.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-04-13 02:26:43 ERROR 404: Not Found.

Hey @cryptod6969 docker scripts deprecated in this PR https://github.com/hummingbot/hummingbot/pull/6160
You could use https://github.com/hummingbot/deploy-examples repo as reference for docker installation


Add snap prevention option: pedestrian_area

In order to avoid snapping to the "wrong side" of a long pedestrian area.
The typical pedestrian area (highway=pedestrian, area=true) that causes
problems is a long coastal esplanade: There are several connecting edges
from the land side, but none from the water side. If we snap to the water
side of the esplanade, the route will trackaround  the edges of the area
before getting to the connecting land side edges. This results in routes
that are way too long (a route that should be a few meters can become
several kilometers).
One example of such esplanade is Norra Hammarbyhamnen, Stockholm, Sweden.

I do not understand the use case as highway=pedestrian should not accessible for motor vehicles anyway and if it is accessible why would you want to avoid snapping and why only in combination with area=true? Can you post a GraphHopper Maps link of the situation?

Sorry, I was not being very clear. I'm talking about vehicle=foot here, not car. Given a set of objects, I want to find out which object that is closest to the user of my application. Through manual testing, I have found that the routed distance can be way too long when the user is located on these kind of coastal esplanades or quays. Some examples:

Dublin example
Gothenburg example.
Stockholm example (OSRM being used since GraphHopper hasn't yet updated the routing since the virtual paths that I tried to add were removed).

This can result in a far away object being reported as closest to the user.
By not snapping to these areas (but still allowing routing on them them), this problem goes away. The downside is of course that GraphHopper won't snap to regular plazas either, but in my experience this affects routed distances marginally compared to how badly these coastal esplanades/quays can mess the result up.

Thanks for the examples.
This is IMO not a viable solution and will fail for many situations and has nothing to do with a wrong snapping. See #82 for a proper solution.


Make syslog address and port properties optional

For .pivotal tiles that want to use this release and expose the syslog
address and port as optional properties, this is required for the
deployment to succeed.
[#130627651]
Signed-off-by: Gerhard Lazu<EMAIL_ADDRESS>

@gerhard why would someone enable syslog release if they dont want to forward logs to remote location?

In PCF RabbitMQ, the tile, syslog address & port are optional properties. Since we cannot optionally exclude a release from the deployment (Ops Mangler can't template handcraft.yml), this seemed like the next best option, even if it goes against the nature of the release.
Long-term, we would like the tile to support the syslog BOSH add-on, which is based on this release. In that context, syslog address and port are no longer optional and this PR becomes redundant. Until Ops Mangler figures out how to handle BOSH add-ons, we cannot recommend a viable upgrade path to that exciting new world.
Right now, I can see these options:

This PR gets accepted and we can go on our merry ways
We use syslog-release in our cf-rabbitmq-release and the legacy way in p-rabbitmq
We back-track and stick with the legacy way, no syslog-release

We are going with option 3 in @gerhard's list. You can close this PR.


Mangaholic changed to radiantscan org to https://tcbscans.cc/manga/

Source information
Mangaholic 1.4.40
Source language
English
Source new URL
https://tcbscans.cc/manga/
Other details

Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

It's not the real radiant  mangaholic website changes there url often and I think it's just temporarily down because they changed url yesterday only and it was working well till afternoon

Domain doesn't have any A records, so I'd say the extension should be removed instead.


⚠ Bofrost.de has degraded performance

In 04654d5, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1221 ms

Resolved: Bofrost.de performance has improved in 9d58459 after 6 minutes.


[SYCL] Update llama.cpp to latest commit for fixing currently broken SYCL backend

SYCL is currently broken on llama-cpp-python, version 0.2.78 because it lacks the fix.

Should be fixed in the latest version (0.2.79)


materia-theme: 20180928 -> 20181115

Motivation for this change
Update to version 20181115
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: materia-theme
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: materia-theme
Partial log (click to expand)

Done.
glibPreFixupPhase
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/mlb7pqj0xyz8g2brb3yk9n9s2wzzwm01-materia-theme-20181115
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/mlb7pqj0xyz8g2brb3yk9n9s2wzzwm01-materia-theme-20181115
checking for references to /build in /nix/store/mlb7pqj0xyz8g2brb3yk9n9s2wzzwm01-materia-theme-20181115...
/nix/store/mlb7pqj0xyz8g2brb3yk9n9s2wzzwm01-materia-theme-20181115

Success on x86_64-linux (full log)
Attempted: materia-theme
Partial log (click to expand)

Done.
glibPreFixupPhase
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/msnif9rnpmcbx0a64lg315k55mwy6l0s-materia-theme-20181115
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/msnif9rnpmcbx0a64lg315k55mwy6l0s-materia-theme-20181115
checking for references to /build in /nix/store/msnif9rnpmcbx0a64lg315k55mwy6l0s-materia-theme-20181115...
/nix/store/msnif9rnpmcbx0a64lg315k55mwy6l0s-materia-theme-20181115


Improve documentation v2

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

Project coverage is 99.24%. Comparing base (f47a43a) to head (6b9bf9c).
Report is 18 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##             main     #101    +/-   ##
========================================
  Coverage   99.23%   99.24%
========================================
  Files         175      183     +8
  Lines       39928    40412   +484
========================================
+ Hits        39623    40107   +484
  Misses        305      305

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


Item filter condition support when querying items

Ability to specify filter condition when performing queries

this is already released in 1.11.0, see here


chore(firebase_performance): migrate to depend on new firebase_core plugin

Description
Migration of current firebase_performance package to depend on new firebase_core as per #2582.
Depend on firebase_core pre-release versions and migrate plugin to use firebase_core native SDK versioning features;

Firebase iOS SDK versions are now locked to use the same version defined in firebase_core.
Firebase Android SDK versions are now using the Firebase Bill of Materials (BoM) to specify individual SDK versions. BoM version is also sourced from firebase_core.

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the [Flutter Style Guide].
[x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the [CLA].
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[x] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[ ] No, this is not a breaking change.

@googlebot I consent.


Add RadentscheidWordpressLocations to the list

Would that be a candidate for the list? https://github.com/steampixel/RadentscheidWordpressLocations

Yes sure. You want to create a PR for it?

This was my first idea :-) But can you give me some hint on where this project should appear in the list?

Good question. The list is lacking a structure but that is on my to do list.
So I’d say put it wherever you think it is best and I will work it in to structure in the next weeks. Under what section header would you put it if you could choose one?

Puh! That is not easy to answer. This software touches many topics such as "civic tech, data literacy, security, ...". I don't know how. But there is maybe a way to tag the projects with several keys instead of pushing them into static categories. But I have no idea on how to do this with a simple markdown document. I think it would be easier to sort the projects by a main category. For this project I would prefer "civic tech".

I like the idea of adding tags or badges.
Civic tech sounds like a good section name

#38


Link with Security Framework

I noticed that the current frida core devkit would not allow for frida-go to build with the error:
/usr/local/go/pkg/tool/darwin_arm64/link: running clang failed: exit status 1
Undefined symbols for architecture arm64:
  "_SecTaskCopyValueForEntitlement", referenced from:
      _darwin_detach_kernel_driver in libfrida-core.a[474](libusb_os_darwin_usb.c.o)
  "_SecTaskCreateFromSelf", referenced from:
      _darwin_detach_kernel_driver in libfrida-core.a[474](libusb_os_darwin_usb.c.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

After some research this is due to a change that now requires the Security framework. See https://github.com/frida/frida/issues/2910
Doing that change locally fixed my build issues.

Thanks @nilathedragon


Copy-Paste broken on Google docs

When I have the DFWP add-on enabled, I cannot copy or paste in google docs. I'm on a mac. Neither CMD+C nor CMD+V does anything. Happy to help debug, but not sure where to start looking.
This only happens when I add the Google Docs url as a rule. When I remove it, I can copy and paste in a google doc as usual.

Why do you want to add google docs as a rule? Google docs presumably isn't preventing you from copying and pasting.

It was mostly a mistake. This morning, I realized that copy-paste was broken in Google Docs. I narrowed it down to this extension. So, I raised this issue. Later on, I realized that I must have accidentally added a rule for google docs, so I edited this issue to add that tidbit.
Maybe this doesn't need to be fixed, but it would be nice if there were a warning if you tried to add google docs as a rule.

This is no longer an issue for me, so feel free to close.

I'm not likely to add in warnings for sites where you probably don't want to enable the add-on but I'll leave the issue open if someone wants to make a PR that does that.

Thanks...I may try a PR if I get some time.


Add options to refreshBoundingBox to improve performance

Before:
refreshBoundingInfo(applySkeleton: boolean, applyMorph: boolean)

After:
export interface IMeshDataOptions {
    applySkeleton?: boolean;
    applyMorph?: boolean;
    updatePositionsArray?: boolean;
    cache?: IMeshDataCache;
}

refreshBoundingInfo(options: IMeshDataOptions)

The updatePositionsArray flag will allow users to disable computing this array which isn't used in all situations.
The cache object will cache the allocations, reduce slice calls, etc.
On my machine:
Before: 2.81s
After: 1.67s

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15234/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15234/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15234/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15234/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15234/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15234/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGL 1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgpuplaywright/index.html

I factored out some functions so that native can override. It is much, much faster in native now.

Visualization tests for WebGL 1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15234/merge/testResults/webgl2playwright/index.html


Fix handling of URLs with special characters

Fixes #11
Added a new test to test this fix
The test passed.

Have you tested it with the actual Bitbar app that it works in practice?

Yes I verified by adding a plugin which uses a quote in the url. The quote gets encoded successfully.

Test passed:
bash-3.2$ npx ava -v

  ✔ main
  ✔ test_quotes_encoding_in_href
  ✔ `text` property validation

  3 tests passed

Ping


[Snyk] Security upgrade django from 2.2.5 to 2.2.13

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Issue
Upgrade
Breaking Change
Exploit Maturity

Information Exposure SNYK-PYTHON-DJANGO-571013
django:  2.2.5 -> 2.2.13
No
No Known Exploit

Cross-site Scripting (XSS) SNYK-PYTHON-DJANGO-571014
django:  2.2.5 -> 2.2.13
No
No Known Exploit

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Conflicting files exists. closing (Old PR)


Update font-inconsolata to new url

Use Google Web Font Directory as noted on the author's website.
Google Web Font Directory is now the official upstream for Inconsolata and the one directly linked from the author's website is now outdated.
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[ ] The commit message includes the cask’s name and version.
=> Include only cask name since the version is just 'latest' and the change is not related to the version number.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked that the cask was not already refused in closed issues.

Thank you for your contribution.


[Discussion] aspnetcore-ci-, aspnetcore-volatile- feeds being deprecated

As part of some of our infrastructural changes, we're discontinuing the use of the following feeds and may remove them entirely in the future:

https://dotnet.myget.org/f/aspnetcore-ci-dev
https://dotnet.myget.org/f/aspnetcore-ci-release
https://dotnet.myget.org/f/aspnetcore-volatile-dev
https://dotnet.myget.org/f/aspnetcore-volatile-release

If you're currently using one of these feeds in your projects to pick up our daily builds, we recommend migrating to https://dotnet.myget.org/f/aspnetcore-dev.

Closing as we have condensed even more, and recommend using https://dotnet.myget.org/gallery/dotnet-core for official daily builds.