Can't generate docs on Linux or OSX

From a clear clone on OSX 10.9.3 + Mono 3.4.0, after having setup the project info through build.sh, I run build.sh ReleaseDoc and I get the following error:
fsharpi --define:RELEASE generate.fsx
/Users/gabriele/Projects/ProjectScaffold/docs/tools/generate.fsx(29,1): error FS0078: Unable to find the file 'NuGet.Core.dll' in any of
/Library/Frameworks/Mono.framework/Versions/3.4.0/lib/mono/4.5
/Users/gabriele/Projects/ProjectScaffold/docs/tools/../../packages/FSharp.Formatting.2.4.1/lib/net40
/Users/gabriele/Projects/ProjectScaffold/docs/tools/../../packages/RazorEngine.3.3.0/lib/net40
/Users/gabriele/Projects/ProjectScaffold/docs/tools/../../packages/FSharp.Compiler.Service.0.0.36/lib/net40
/Users/gabriele/Projects/ProjectScaffold/docs/tools
/Library/Frameworks/Mono.framework/Versions/3.4.0/lib/mono/4.0/

Please try with #135.


BUG - version 1.0.0

Describe the bug
Double sound.
Sometimes it looks like there are two instances of video. One is behind, and out of control and another is in iframe.
When I click pause on iframe I still hear the sound of the same video.
Even if I remove all elements from body, I still hear the sound of the same video.
Sporadic behavior.
Mostly happens when you reopen previously closed video.
Looks like bowser keeps in memory previous youtube video instance run it and keep connection with youtube even the youtube player is removed from DOM.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS - Windows 10
Browser - Brave
Browser Version - Version 1.60.125 Chromium: 119.0.6045.199 (Official Build) (64-bit)
Ad blocker used - NO
Video URL if applicable - any youtube video

Additional context
Add any other context about the problem here.

Hi @shed25
Thanks for the detailed report, whilst the extension can be used by the Brave browser, it isn't officially supported.
This extension is only currently supported on Chrome, Firefox, and Edge. While I understand that Brave supports the same extensions as Chrome through the Chrome Web Store, there may be some differences in compatibility. Mainly because Brave has its own blocker, meaning this extensions may not work correctly...
As I am sure you can imagine there is an immense challenge in testing every browser in combination with each ad-blocker, and as such it's necessary to restrict the scope to a manageable extent.
That said, I've gone ahead and installed Brave to explore and understand the specific issue at hand. However, at this time, I'm unable to guarantee support for every possible browser.
Hope this makes sense, if I do have a fix and can offer support for Brave I will update the project :)


reverting to 26a28ab behaviour

This is only slightly problematic for the most pathological of cases where a prelude is followed by a set of statements, none of which generate top-level variables or attempt to return. In these cases, the non-prelude statements will be indented. See related discussion at e4b3e838e2f308d5d39eb54361374fb171ef58c9.

Ping @jashkenas. This one should be a no-brainer.

No -- this pull request produces the same broken formatting as previously. Create a "test.coffee" file containing:
one 1
two 2

... and run bin/coffee -p. You'll get:
foo(one);

  bar(two);

We need to lose the indentation on the rest of the bare file.

The problem with the first line is that leading and trailing whitespace is being stripped somewhere. I'm looking into it. If you want all of it to be unindented, you'd have to know somehow before compilation if any variables are going to be defined. Or we could just not indent the code that's inside the safety wrapper.


Correction of Task Pattern command line arguments

@lukasrothenberger some tests are not passing. Can you plz check why they fail and fix the PR?


VS2017 RC regression - Record name completions not always shown

VS2017 RC no longer shows record name completions in some situations
Repro steps
Take the code
type A = { XXX : int; YYY: int }

let f () = { XXX=1; YY

Complete after YY using Ctrl-Space or Ctrl-J.
Expected behavior
The completion YYY is offered
Actual behaviour
In VS2017 RC, no completion is offered.  In VS2013-15, the completion was correctly offered.

Fixed by #1816.  Tested manually (we have many unit tests, but just below the level where we are wiring this up)


[FrontendOptions] Remove bespoke experimental feature flags in favor of -enable-experimental-feature X.

Replace -enable-experimental-variadic-generics with -enable-experimental-feature VariadicGenerics
Replace -enable-experimental-implicit-some with -enable-experimental-feature ImplicitSome

@swift-ci please smoke test


Request/response benchmarks

unblocks https://github.com/ethereum/lahja/pull/98
What was wrong?
Our benchmark tests do not cover the EndpointAPI.request code path.
How was it fixed?
Added ability to target that API to benchmark suite using --mode request
Cute Animal Picture

:+1: to a more extensive round trip benchmark for request/response.  opening an issue to track future work.


Change Logs in Config-UI-X

Hi, I was wondering if you can make your change logs appear in config-ui-x? Some plugins when updated on that UI have a pop-up box that lists the latest updates to the plug-in :)

Hi! Are there any recommendations/documentation to know the necessary changes to achieve that?

In the latest version, I tried using the tags and releases feature in Github. Plus we moved the Changelog from README.md to the CHANGELOG.md file. Not sure if it helped.

I will install the update after work and update on you :)

That has worked :) although it is showing your entire change log, not your most recent entry; but it is better than nothing!

Cool! Let’s see if the next release will only show the diff 🤞
Can I close this issue then?

Awesome :) thanks for the speedy work!


Simpler logic for centering camera.

Hoping for some review of these changes. I simplified the centering logic (at least I find it easier to read) and it seems to work in Python 2, and since it's not using any division I presume the same for Python 3.

Coverage decreased (-0.03%) to 91.054% when pulling 4fdb07af8e039992e788a67e1a8bef894b36600f on camera-fix into f1ef0af47fd6f30fabf83433a0a5df6d50f27f2b on master.

Well, this feels like cheating :P
But looks good! 👍 👍 👍

I just wanna wrapup a basic AnchorPoint and then I'm going to update tests... probably go for one more review and merge.

Hah, I completely forgot that Rects have a center property. LGTM. :+1:


Logic

create an json file and add the list of countrys to it and you will need to add json handling to utils or to logic file itself

ok ?


[Feature request] Get component if it exists or Assign

Just adding here so it doesn't get lost:
We have:
//accommodate
if(registry.has<Comp>(entity)) {
    registry.replace<Comp>(entity, arg1, argN);
} else {
    registry.assign<Comp>(entity, arg1, argN);
}

Would like to add something similar that does:
 // some other word
if(registry.has<Comp>(entity)) {
    registry.get<Comp>(entity);
} else {
    registry.assign<Comp>(entity, arg1, argN);
}

registry.get<Comp>(entity, arg1, argN);

Is it an error or do you expect that the get uses the arguments somehow?

oops, yeah copy paste error ... no arguments for the .get needed

Ok, so, the main problem I see with this is that it's not clear what an user should expect when get is invoked instead of assign.
I mean, you pass arguments in both cases. Do you expect them to be discarded or used anyway to update the already existing instance? It could be misleading to discard them maybe.

As @skypjack said, sometimes discarding arguments sounds a bit fishy to me. You could do this:
if (auto *comp = reg.get_if<Comp>(e)) {
  // Do stuff with comp
} else {
  Comp &comp = reg.assign<Comp>(e);
  // If you need to do stuff with comp here then
  // maybe you need a helper function
}

If there were to be a new helper function in EnTT, what would it be called? How best describe the behavior? You're getting and assigning so it kind of sounds like std::exchange but not quite.

yeah I see its a bit vague ...
I'm not using the arguments myself, but I can see somebody using them.  These helpers are great for shortening the code, and in my code I'm going to use the component right away, so I'd like it to be ready/initialized, so it makes sense the way its up there now.
if you are going to replace the insides of the component, might as well use accommodate, so it makes no sense to apply the arguments in the .get case, and it makes total sense to apply them in the assign case.
its nice to just say :
r.getOrAssign( a, b, c ).someVal *= r.getOrAssign( x, y, z)
instead of the 8 lines or so of code you'd need otherwise.

get_or_assign sounds good indeed. @Kerndog73 ? :smile:

insert_or_assign always uses the given arguments and the object is left in the same state regardless of whether or not the key was already in the map. accommodate does this as well. But get_or_assign leaves the entity in a different state depending whether a component exists. insert_or_assign and accomodate are more well-behaved and deterministic in my opinion.
I don't think there's anything objectively wrong with get_or_assign, it just feels wrong, that's all.

alright so just drop the arguments. Now we know the state in both cases is clear.

@ErikBehar There's nothing stopping you from implementing this function in your own code. I think @skypjack and I both agree that this doesn't belong in EnTT.

@Kerndog73  I already implemented it before I brought it up in the chat ...
So whats the negative argument for the parameter less version ?

By "parameter less version", do you mean get_or_default_construct?
If so, then this version isn't as bad because you aren't sometimes discarding arguments. Although, it still leaves the component in either a default constructed state or it's previous state depending on whether it exists.
Perhaps we should wait for a response from @skypjack. It's currently very late in his timezone so we'll probably hear from him in 7 or 8 hours.

Yeah, sorry, I'm just on the other side of the world after all.
A sort of get it no matter if it doesn't exist is less counterintuitive, but then I don't see the benefits for the client. I mean, you don't know if you have to update or not the returned component unless you invoke has and rely on an if, that was exactly what you were doing before.

Let's try to flip the problem on its head.
Why do you need this? What's exactly your problem that requires such a strange pattern?
Try to share our knowledge. It could happen that you find a different way to solve it and get rid of this annoying requirement.

In my use case I'm creating links between entities by storing their entity IDs on components on each entity.
So I'm not really using the arguments. Looks similar to the example above with out the params.
At the end of the day all it does is save me writing out boiler plate 8 lines or calling a helper function that does if has. It's really just the same as accommodate, there's no reason whatsoever to have that, you can use if has same as above, but saves u some lines of code.

The last proposal (the one without arguments) works similar to the operator[] of an std::map:

Returns a reference to the value that is mapped to a key equivalent to key, performing an insertion if such key does not already exist.

Replace key with entity identifier and that's it. So, it's in line with how the standard library works.
Unfortunately, we cannot use a templated operator[], it would be ugly and cumbersome. However, it makes sense as a function. @Kerndog73 ?
If all of us agree on this, we have to face the most difficult thing: find the right name for that. :smile:

@skypjack Finding it in the standard library is all you need to convince me!

@Kerndog73 that's good, but operator[] isn't a viable solution, so let's propose some valid names!! :joy:

I really think getOrAssign and for accommodate maybe think of renaming to replaceOrAssign, will make things clearer. Maybe take a poll and see what a random programmer thinks accommodate does. I bet most people will get it wrong.

Many languages have a concept of map.get(key, default_value). I could imagine a version where the default_value is not just returned, but also inserted if it doesn’t exist. It sounds like this is what’s being asked for here. Whether or not its useful, I don’t know.
@skypjack getOrCreate or something to that effect maybe? (getcreate, createget, I can’t think of a single-word name)
I do agree that accommodate is not a particularly meaningful name. I had to look it up a thousand times before finally memorizing it.

The default_value in @danielytics suggestion could even be a lambda to construct and/or mutate-in-place the component lazily.

Well, could they be just insert_or_assign instead of accommodate (even though this looks a lot like a breaking change) and something like get_or_assign or a non-const overload of get that also accepts a second parameter?

I'd definitely prefer insert_or_assign, accommodate is really weird to use as a native english speaker for that...

@OvermindDL1 Can I ask you why i'ts weird as a native speaker? Just out of curiosity.

It's a word I would never think of using for that purpose or think of looking up, in addition it seems like what it would actually do is to resize something, not 'insert or assign'...

I agree. Without looking it up, I would never be able to guess what it does. It sounds maybe like some sort of data formatting or casting (accommodate some data to fit some shape or something), I’d certainly not guess that it is basically an upsert operation. The dictionary definition does suit the current meaning, but it’s not a word that would immediately spring to mind for it, at least for me.
Having said that, if you don’t want to break backwards compatibility by changing it, I won’t complain.

I guess depends from what point of view your looking at,  ( insert ) sounds to me like you are looking from the point of view of the data structure, like inserting into a vector.  ( assign ) sounds to me like you are looking from the ecs perspective, ie you are "attaching" a component to an entity.
In my opinion you should stick to the ecs perspective. That's why   getOrAssign  /  replaceOrAssign make more sense to me.

@ErikBehar good point. :+1:
@danielytics v3 will be already a breaking release, so who cares? :smile:

@skypjack good point. Well, in that case, may as well make it clearer! I also agree with Erik’s point, sticking with the ECS perspective when naming of course makes a lot of sense.

I think I'll work on this when I finished with #152 - did you find any other name that is difficult to remember/guess? Just curious.

I'd rename also get_if in try_get. *_if is usually reserved to functions that accept predicates in the standard library and it could be misleading.

I renamed get_if to try_get and accommodate to assign_or_replace.
Unfortunately, introducing an overload of get that also accepts an instance to assign if the entity doesn't own the component requires that the array of pools is mutable.
This is something already available in #152, so it doesn't make sense to do it twice. It means that this feature must wait until #152 is fully merged on master.

 There won't be a const overload for this function. It wouldn't make sense.
No need to wait for #152 to proceed on this actually. It was just me trying to do something wrong.

Upstream.
I'll close this issue tomorrow in case of no negative feedback.
I'm also available to consider renaming other functions (if we agree they have weird names).

I think reset is not super clear. Could be safe_remove or try_remove

Are you talking about the someEntity.reset<SomeComponent>() call?  I agree that it does not seem to fit the standards usages for reset calls.  I do like the word reset for it, but it is 'wrong' to fit the standards usages...

@ErikBehar @OvermindDL1
Standard usage for reset is to (let me say) replace content (think of std::unique_ptr). Probably clear fits better in this case, even though it's closer to the point of view of the container than to that of the ECS.
To be honest, safe_remove and try_remove are a bit misleading from my point of view.

Well, ok, breaking changes are still possible until v3 is released.
We can safely close this issue being it done. :+1:


[NEW ALGORITHM] Proportional Share Scheduling (Fair-Share)

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
[NEW ALGORITHM]
Proportional Share Scheduling (Fair-Share)
About:
Propose a new algorithm to be added to the repository
Proportional Share Scheduling, also known as Fair-Share Scheduling, is an advanced CPU scheduling method that distributes CPU resources among multiple processes, users, or applications in a way that respects predefined "shares" or "weights." Each process (or user) is assigned a portion of CPU resources based on these shares, which ensures fair allocation in environments where multiple entities compete for CPU time.

Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

@pankaj-bind kindly assign

assigned


Remove data-source placeholders after DatasourcePre* delegate is called.

Can the line that removes any remaining placeholders (https://github.com/symphonycms/symphony-2/blob/integration/symphony/content/content.blueprintsdatasources.php#L1263) be moved down, after DatasourcePreCreate or DatasourcePreEdit delegate is called?
That would help extensions inject their own code, without a need to tokenize whole source to find correct spot :).
It would also be of great help if other placeholders were not removed as soon as Symphony injects its code, only after DatasourcePre* is called. It would allow extensions to add their own variables, etc... without a need for tokenize or error-prone regex replacement.

This isn't the ideal solution, allowing Datasource types to be provided by extensions is. I won't revert the current code as it can function as a stop gap if the Datasource abstraction doesn't land in 2.3.

Datasource types and modifications are two different things IMHO.


create Morpheme (token) schema

Should have two fields: form and gloss, both of which are MultiLangStrings.
Allows for an optional lexeme field, which contains a LexemeReference.

closed with v0.11.0


yarn install --> yarn add in readme

yarn uses add to add packages (https://yarnpkg.com/en/docs/cli/add) instead of install
Should we provide the NPM installation command as well to stay consistent with https://github.com/Shopify/graphql-js-schema/ and https://github.com/Shopify/graphql-js-schema-fetch/?

Yeah good idea to have both. Just have NPM second 👍


Add peerDependencies to devDependencies

Because react, react-dom, and draft-import are imported and used by the tests, we need to install them in order to build the module. Ensure this happens automatically by listing them in the devDependencies.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #78   +/-   ##
=======================================
  Coverage   81.47%   81.47%
=======================================
  Files          15       15
  Lines         340      340
  Branches       48       48
=======================================
  Hits          277      277
  Misses         63       63

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3deaed0...a507b30. Read the comment docs.

Is this really necessary?
When setting up this project after cloning, I always do
npm install react react-dom draft-convert && npm install

This is also added in travis.yml

I think it will make the project easier to work with. You won't need to remember a special command or set up Travis (and other automation) to special-case something that's supposed to be done automatically.  Technically, it's not "necessary" to declare any of your devDependencies if you want contributors to manually install them all, but your project is easiest to work with if you declare all of your devDependencies so that they can be installed automatically, which includes these three.
I didn't anticipate pushback for this pull request. Maybe I'm missing something. Why wouldn't you want these dependencies declared in your devDependencies?


Track who makes changes to guides

Show a better audit trail of who did what by storing which user changed a guide and show it on the history tab.
https://trello.com/c/POsJcfsx

lgtm, other than one comment


Unable to authorize an org

Summary
I GET BELOW ERROR WHEN I TRY TO AUTHORISE ORG
TypeError: shellPath.at is not a function
Steps To Reproduce:

CREATE A PROJECT WITH MANIFEST
AUTHORIZE AN ORG

Expected result
It should have redirected to a web page to authorise an org
Actual result
Getting below error
TypeError: shellPath.at is not a function
Additional information

Salesforce Extension Version in VS Code: 59.1.2
SFDX CLI Version: 2.14.6
OS and version: mac OS Ventura 13.5
VS Code version: 1.83

Hi @nkl14!
would you mind checking the vscode setting NODE_EXTRA_CA_CERTS? both for user and workspace

Hey, sorry for the late reply, CLI team was mostly out in the last 2 weeks.

TypeError: shellPath.at is not a function

That's coming from oclif (CLI framework we use):
https://github.com/search?q=org%3Aoclif %2FshellPath\.at\(%2F&type=code
The Array.at was added in node 16, so you are probably on a lower node version when running the CLI.
If you installed from npm, make sure to update to latest node LTS, or use the installers which includes its own node binary.


Build failed: Could not find :ExecutorLibrary:

Run Robotium Recorder through this guide
Encountered Recording failed. Please see output: <path>\Robotium_log.txt after selecting APK and run New Robotium Test.
All prerequisites already fulfilled: Physical device with external storage, Android API level available in SDK Manager.
Robotium_log.txt
Input:
C:\Users\wendy\StudioProjects\ExampleTestProject_AndroidStudio\gradlew.bat -Dorg.gradle.daemon=true assembleDebugAndroidTest -u -b C:\Users\wendy\StudioProjects\ExampleTestProject_AndroidStudio\executorproject\build.gradle
Output:
Incremental java compilation is an incubating feature.  FAILURE: Build failed with an exception.  * What went wrong: A problem occurred configuring root project 'executorproject'. > Could not resolve all dependencies for configuration ':_debugAndroidTestCompile'.    > Could not find :ExecutorLibrary:.      Searched in the following locations:          https://repo1.maven.org/maven2//ExecutorLibrary//ExecutorLibrary-.pom          https://repo1.maven.org/maven2//ExecutorLibrary//ExecutorLibrary-.aar          file:/C:/Users/wendy/StudioProjects/ExampleTestProject_AndroidStudio/executorproject/libs/ExecutorLibrary-.aar          file:/C:/Users/wendy/StudioProjects/ExampleTestProject_AndroidStudio/executorproject/libs/ExecutorLibrary.aar          file:/C:/Users/wendy/AppData/Local/Android/sdk/extras/android/m2repository//ExecutorLibrary//ExecutorLibrary-.pom          file:/C:/Users/wendy/AppData/Local/Android/sdk/extras/android/m2repository//ExecutorLibrary//ExecutorLibrary-.aar      Required by:          :executorproject:unspecified  * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.  BUILD FAILED  Total time: 4.26 secs
Any help will be appreciated.

I had the same issue with Android Studio 2.3.3+Robotium Recorder.....
But, I used Android Studio 2.2.2+Robotium Recorder that is OK~~
For your reference~~

are you sure @RandyHsuTW  ? I'm going to downgrade my android studio if its really the case.


Disable robots by default on all pages

What's the purpose of this pull request?
Next-SEO adds a robots tag to all pages by default. This PR reverts this behavior and allows customers to add, by extending the ThirdPartyScripts, their own robots value.
How to test it?
Navigate to any page on the starter and you'll see that there's no robots meta tag on the pages.
Starters Deploy Preview
TBD
References
https://github.com/garmeeh/next-seo/

Closed in favor of #2140


1x4 and 2x4 mixer bugs

msHack,
Sorry to do this to you. The 1x4 mixer meters doesn't work. The meters on the 2x4 mixer are not functioning properly.  Some meters only has the right meter pumping when there is only a left channel connection. Some channel doesn't work and L/R channel meter errors.

I haven't figured that one out yet.  It happens randomly.  Restarting VCV Rack sometimes fixes the issue.

I think I fixed this one.

The ping pong delay is now not working for some reason. The Aux sends works but the delay is not processing or any audio is passing through.

lol, what the heck I only replaced the button...

maybe the button meta was updated in the code

It is my own button.  I did test this too, not sure what happened.  Working on it.

I feel dumb. I just found out that the 6x32 trigger sequencer 3 color button knobs controls the levels of your drum synth. I didn't undertand the levels at first. I was always using the Trig output port to the levels port of the drum synth or using it as a 2 note trigger to the 3 OSC synth.

yeah, works nice using it to control a filter or output level.  Put it into Bi Directional mode and control pan with it.
Pong is fixed and updated...

Thanks. By the way, will you be able to use the same kind of chain linking with the mixer like you did with the master clock. When chaining , do you have to using two cables for audio out where as you can implement that in the code using one cable linking.

No I don't think I could, just because I would not be able to send two floating point signals L, and R, every system step (each step is basically the sample rate so 44100 times per second or whatever).  The clock was easy because I don't have to send two separate signals every time, it just sends the tick when it occurs (-1) or the BPM (40-220) so it is easy to distinguish between them.


Added Allergies exercise

Let me know if I can make any improvements.

@lpil Sure thing, both updated!

Great, thanks both!


ICIC guest operations script issues

service files call incorrect script name
error in variable name (allguests vs icicguests)
early expansion of the guest variable in setting the operation for start/stop

after fixing above, stop does not work due to bad positional parameter

possibly more, but the lights just went out and I can't see my notes

Service file error was already fixed in commit 87556c9.
Items in commit 151bb29:

allguests error fixed
rewrite of parameter passing (fix early expansion and positional bugs) in icic-guests.sh.j2

The error on "mask" was caused by the location of the service unit files. This report against systemd upstream) explains the conflict between unit files in that location and the way services are masked.  Commit 151bb29 also includes a relocation of the unit files from /etc/systemd/system to /usr/local/lib/systemd/system to avoid this (other service files will be moved for consistency).

These are resolved in current builds (7203b.8 for CKD and 7203b.9 for FBA) and also in the 7203b.6 updater script.


Sort buffers by most recently selected/used

FZF does sort buffers on buffers selection list by most recently used. This is very helpful and makes switching to most recently used buffers easier as they are closer to the end of the list (I do not mean oldfiles here, which is different).
FZF.vim also does not allow to pick up buffer shown in 'current' window, this is shown as yellow on screenshot below and is not selectable.

After changing buffer to _neogit.lua and invoking fzf buffers again it changes to:

Do you think this functionality could be implemented in snap's buffer producer?

I'd love to have both these changes.

All good ideas :) when I get some time I can come back to this. Thanks!

I'm sure there's cleaner way to do this, but if you just want to throw something into your config for now, I was able to make a custom producer that sorts the list. Inspired by how FZF sorts their buffer list.
-- Taken from source
-- https://github.com/camspiers/snap/blob/4ed8f920f437138b7da38d5ad9003a1e2ca2ddb3/lua/snap/producer/vim/buffer.lua
local function get_buffers()
  local function _1_(_241)
    return vim.fn.bufname(_241)
  end
  local function _2_(_241)
    return ((vim.fn.bufname(_241) ~= "") and (vim.fn.buflisted(_241) == 1) and (vim.fn.bufexists(_241) == 1))
  end
  return vim.tbl_map(_1_, vim.tbl_filter(_2_, vim.api.nvim_list_bufs()))
end

-- Table of buffers
local snap_buffers = {}

function _G.push_buffer()
  local bufname = vim.fn.bufname("")
  -- push a key/value of buffer path and time entered
  snap_buffers[bufname] = vim.fn.reltimefloat(vim.fn.reltime())
end

function _G.delete_buffer()
  local bufname = vim.fn.bufname("")
  -- Remove path from table
  snap_buffers[bufname] = nil
end

vim.cmd [[
  augroup snap_buffers
    autocmd!
    autocmd BufWinEnter,WinEnter * call v:lua.push_buffer()
    autocmd BufDelete * silent! call v:lua.delete_buffer()
  augroup END
]]

local function getKeysSortedByValue(tbl)
  local keys = {}
  for key in pairs(tbl) do
    table.insert(keys, key)
  end
  table.sort(
    keys,
    function(a, b)
      return tbl[a] > tbl[b]
    end
  )
  return keys
end

local function tableHasValue(tbl, val)
  for _, value in pairs(tbl) do
    if value == val then
      return true
    end
  end
  return false
end

local function makeBufferList()
  -- Get the active buffers that snap uses
  -- (this is a trimmed down list)
  local activeBuffers = get_buffers()
  -- Get our sorted list of buffers (with some we don't want)
  local filePathsSortedByTime = getKeysSortedByValue(snap_buffers)

  local result = {}
  for _, filepath in pairs(filePathsSortedByTime) do
    if (tableHasValue(activeBuffers, filepath)) then
      -- filter down our sorted list to the same items that Snap uses
      table.insert(result, filepath)
    end
  end

  return result
end

local function bufferProducer()
  -- Runs the slow-mode to get the buffers
  local result = snap.sync(makeBufferList)
  coroutine.yield(result)
end

This is 95% of a solution for me, thank you very much.
Only change I did for myself is to add the newest entry at the bottom:
local function makeBufferList()
  -- Get the active buffers that snap uses
  -- (this is a trimmed down list)
  local activeBuffers = get_buffers()
  -- Get our sorted list of buffers (with some we don't want)
  local filePathsSortedByTime = getKeysSortedByValue(snap_buffers)

  local result = {}
  local first = false
  for _, filepath in pairs(filePathsSortedByTime) do
    if (tableHasValue(activeBuffers, filepath)) then
      -- filter down our sorted list to the same items that Snap uses
	  if first == false then
	      first = filepath
	  else
          table.insert(result, filepath)
	  end
    end
  end
  if first ~= false then
	  table.insert(result, first)
  end
  return result
end

I find it nice not to have it on the top - I'm unlikely to not switch buffers :).

Almost perfect, it seems to keep one buffer list per cwd :(.
I don't get it.

This might be a slightly more elegant way to do it. The :buffers t command will print the buffer list in order of access for us. Unfortunately I don't think there's a way to get this list programmatically, but you can do some string manipulation to create this list. I think this will be more reliable and accurate than my previous solution.
local function getSortedBufferList()
  -- Hacky way to get the list of buffers sorted by recency
  -- There's no programmatic way to get this AFAIK
  -- But the ":buffers t" command does sort it correctly
  -- This redirects the output of the command to a register,
  -- then assigns the contents of that register to a global variable
  -- we can access
  vim.cmd [[
    let temp_reg = @"
    redir @"
    execute "buffers t"
    redir END
    let output = copy(@")
    let g:raw_buffer_list = output
    let @" = temp_reg
  ]]

  -- This is now a multiline string of the buffer list
  -- We need to trim this down into a table of filepaths
  local rawBuffers = vim.g.raw_buffer_list
  local splitLines = vim.split(rawBuffers, "\n", false)
  local result = {}

  -- The filepaths always start at this index
  local quoteStart = 11

  for _, line in pairs(splitLines) do
    -- Identify the index position of the closing quote
    local endIndex = string.find(line, '"', quoteStart)
    if type(endIndex) == "number" then
      -- grab the string between the quotes
      local filename = string.sub(line, quoteStart, endIndex - 1)
      table.insert(result, filename)
    end
  end

  return result
end

local function bufferProducer(request)
  -- Runs the slow-mode to get the buffers
  local result = snap.sync(getSortedBufferList)

  -- Move the active buffer (first filepath)
  -- to the bottom of the list
  local currentBuffer = result[1]
  table.remove(result, 1)
  table.insert(result, currentBuffer)

  if request.canceled() then
    coroutine.yield(nil)
  else
    coroutine.yield(result)
  end
end

Here's a producer that sorts buffers by lastused and excludes the current buffer
(fn get-sorted-buffers [request]
  (fn []
    (let [original-buf (vim.api.nvim_win_get_buf (. request :winnr))
          bufs (vim.tbl_filter #(and (not= (vim.fn.bufname $1) "")
                                     (= (vim.fn.buflisted $1) 1)
                                     (= (vim.fn.bufexists $1) 1)
                                     (not= $1 original-buf))
                               (vim.api.nvim_list_bufs))]
      (table.sort bufs
                  #(> (. (vim.fn.getbufinfo $1) 1 :lastused)
                      (. (vim.fn.getbufinfo $2) 1 :lastused)))
      (vim.tbl_map #(vim.fn.bufname $1) bufs))))

(fn sorted-buffers [request]
  (snap.sync (get-sorted-buffers request)))

As a side note, I think the winnr field in Request might be misnamed -- it's actually the window ID. (:h winid)


Writing test scripts for NCERT Quiz

Writing the test scripts for NCERT Quiz
Test Scripts are Completed  for the following:
Vanity Metrics- completed
Implementation status- completed
Participation Status- completed
Quizwise  Status -completed
This is completed on 9th sep 2022

In Participation status, Select Quiz name dropdown automation is pending

Dependent dropdowns are completed

Testscripts  are completed


"double booked: found InnerBody when getting ClosedEnv"

(letrec ((fold (lambda (op acc l)
                 (if l
                     (fold op (op acc (car l)) (cdr l))
                     acc))))
  (fold (lambda (x y) (+ x y)) 0 '(1 2 3)))

thread 'main' panicked at 'double booked: found InnerBody when getting ClosedEnv', /home/user/workspace/lurk-rs/src/hash_witness.rs:190:13

This seems to be a regression, this version of fold worked before. Akosh (who's trying out our onboarding challenge) ran into this. Version I'm testing is bb98c334fed9b329cc3d1d35284ba986961948fb

Mmmm, that probably means our unit tests are failing to test some code paths. The solution is to add this as test and fix it, which I will do.
Can you please search for any other such cases?

The short-term fix for Akosh is to use an older version (obviously).

Thanks for the fix @porcuquine
I got around it by not passing lambdas with more than one parameter.

Can you please search for any other such cases?

The shortest example I found was this:
(cons (lambda (x y) nil) nil)

For clarity, is your new example failing now that this PR is merged, or is it an independent and still-extant problem? If you can still reproduce now that #208 has merged, please create a new issue for it. Thanks for that (if applicable) and the initial report.

If this is fixed now, but your reduced example also elicited the identical problem, we might replace the regression test with this cheaper one — since the fold example is relatively expensive (on success) for our tests.

I just tried this on both versions and it fails on both. It looks like it's not exactly the same error, it is another bug of the same type:
> (cons (lambda (x y) nil) nil)
thread 'main' panicked at 'double booked: found Lambda when getting UnevaledArgs', /home/user/workspace/lurk-rs/src/hash_witness.rs:190:13

opened new issue https://github.com/lurk-lang/lurk-rs/issues/209

@aakoshh, this was fixed in #210. Thanks.


Add Works  and about sections

Added Features

Added works section to the project.
Added About me section to the project

What is newly added

Add Button effects.
Add grid to the works section.
Add flexbox to the about section.


Router misfire when navigating via url

I have access to prose/starter and also my own fork at dereklieu/starter. From the index route, pointing my url to #dereklieu/starter takes me to prose/starter even though the url still thinks it's my fork. Navigating again aka hard refresh gets me to my fork where it should have taken me in the first place. This is probably a bug in the router.

cc #841

Closed #943


Ensure orocos-kdl is available as a target

#6 ensures that the orocos-kdl target exported by Orocos KDL versions newer than 1.5.1 will include the Eigen3 directories. This PR ensures that the target is present by creating a new "imported" library and populating it based on the old-style _LIBRARIES and _INCLUDE_DIRS variables.
This wasn't caught in the original PR because the orocos_kdl_vendor package includes additional changes after 1.5.1 was tagged which export the target, and ci.ros2.org isn't installing liborocos-kdl-dev. I was able to reproduce the problem using the build.ros2.org CI jobs.
From build.ros2.org:

Before
After

With CI changes:

Before  (this passes because it still has the manual Eigen workarounds in downstream packages)
After

Current CI:

Linux
Linux-aarch64
Linux-rhel
Windows

Paris with:

ros2/geometry2#534
ros/kdl_parser#64

some of the CI jobs you ran are failing

Looks like an infra issue, I re-ran them and they're past the previous point of failure.

can you please open up a change to https://github.com/ros2/ci to install orocos...

Done: ros2/ci#668

@Mergifyio backport humble


Fatal Crash on ARKit with 8.9.0 (not with 8.8.0)

[REQUIRED] Step 1: Describe your environment

Xcode version: 13.1
Firebase SDK version: 8.9
Installation method: Swift Package Manager
Firebase Component: not sure (Auth, Core, Database, Firestore, Messaging, Storage, etc)

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Launch ARKit while using: Auth, Firestore Listeners
Relevant Code:
Unfortunately, I am not sure where the bug gets triggered. It seems to originate in some App Check code.
What I am doing is launch a view controller for an ARKit Session. If i go back to 8.8 it works without issues.
Also what I have noticed is that tokenDidChangeNotificationName's notification observer gets called very often before the crash happens. I'd say a few dozen times per second.

`

@nidegen Thanks for the report. The issue is likely related to the Firestore AppCheck integration that was introduced in 8.9.0

That's what I was also thinking, but was unable to trace the exact origin. The often called AppCheck Notification Observer of tokenDidChangeNotificationName did always have if (![[contents->app name] isEqual:notified_app_name]) { return } return in FirebaseAppCheckCredentialsProvider.

(Line 52 of firebase_app_check_credentials_provider_apple.mm)

@nidegen Do you install App Check SDK as well?
I guess the issue may be due to app_check == nil here  so nil is passed as a notification name to the method which means the class subscribes to basically all possible notifications.
cc @schmidt-sebastian

Nope, I do not use it or link to it!

The underlying issue seems to be that the AppCheck callback is processing a notification whose userInfo is not an NSDictionary. While this does not conform to the NSNotification  API, this can easily happen in Objective C. 8.9.1 will start to ignore these notifications.

@nidegen Firebase 8.9.1 is now available.  We would appreciate your confirmation that it fixes the issue.


Error installing via Composer

Hello I am using your version 2 Auth package I will like to use this JWT package as rest API with you AUTH package I install.
When try to install this package via COMPOSER it throw error that my MINIMUM requirements is STABLE .
Please can you create a RELEASE version

Hello @seunex17 thank u for submitting issue, already fixed with pr https://github.com/agungsugiarto/codeigniter4-authentication-jwt/pull/9


Change name of material processing / processed material

It seems odd to classify "device" as a "processed material". I think this is more of a problem of nomenclature than logic.
To me, processed material or material processing connotes raw portions of material, e.g as in
https://en.wikibooks.org/wiki/Materials_Science/Material_Processing
OBI's use of material here is in the broader sense of BFO "material entity". I understand the desire to make this friendlier by lopping off the ugly "entity" but in doing so you end up with something that is still quite formal yet misleading.
There seems to be a certain hedging around the nomenclature here. E.g. in
material transformation objective the definition is "an objective specifiction[sic] that creates an [sic] specific output object from input materials.".
It's not clear if the choice of terms is to be more user-friendly or if a more formal distinction is intended (e.g. BFO object). The reader of OBI definitions may be more primed to believe there is a formal distinction here.
The clearest thing may be call these "material entity processing" and "processed material entity". These sound a bit abstract, but then this is honest as the terms are abstract.
Although I might go further and get of these as abstract groupings that do no useful work. Replace with more specific classes that correspond to terms that are found in the domain. For example, manufacturing (manufactured entity), experimental manipulation, etc.

'object' is a leftover, and should be removed. Good catch. Adding 'entity'
after 'processed material' makes perfect sense. In the definitions, BS had
encouraged us to use more normal language, and I actually strongly agree
with him on this one. The logical definitions should be sufficient to e.g.
clarify the inputs for a machine, and it would be nice if we had
definitions that normal people can read.
On Tue, Apr 16, 2019 at 7:02 PM Chris Mungall<EMAIL_ADDRESS>wrote:

It seems odd to classify "device" as a "processed material". I think this
is more of a problem of nomenclature than logic.
To me, processed material or material processing connotes raw portions
of material, e.g as in
https://en.wikibooks.org/wiki/Materials_Science/Material_Processing
OBI's use of material here is in the broader sense of BFO "material
entity". I understand the desire to make this friendlier by lopping off the
ugly "entity" but in doing so you end up with something that is still quite
formal yet misleading.
There seems to be a certain hedging around the nomenclature here. E.g. in
material transformation objective
https://www.ebi.ac.uk/ols/ontologies/obi/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FOBI_0000456
the definition is "an objective specifiction[sic] that creates an [sic]
specific output object from input materials.".
It's not clear if the choice of terms is to be more user-friendly or if a
more formal distinction is intended (e.g. BFO object). The reader of OBI
definitions may be more primed to believe there is a formal distinction
here.
The clearest thing may be call these "material entity processing" and
"processed material entity". These sound a bit abstract, but then this is
honest as the terms are abstract.
Although I might go further and get of these as abstract groupings that do
no useful work. Replace with more specific classes that correspond to terms
that are found in the domain. For example, manufacturing (manufactured
entity), experimental manipulation, etc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/1014, or mute the thread
https://github.com/notifications/unsubscribe-auth/ANN9IuxTAKNKQAiUMmjYcO2ufKS9R3peks5vhoDAgaJpZM4c0CiH
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

Just to be clear, am I to do the following:

change the labels?

“processed material” to “processed material entity”
“material processing” to “material entity processing”

and then 2) update definitions to reflect these changes?

"processed material entity" def = A material entity that is created or changed during a material entity processing.
"material entity processing" def = A planned process which results in physical changes in a specified input material entity.
“material transformation objective” def =  An objective specification that creates a specific material entity from input material entities.

We should ask in the OBI call how far we want to go. Definitely we do not
want to use 'object' in 'material transformation objective'. That is what I
was referring to in 'good catch'. I doubt that adding 'entity' everywhere
is helpful in all cases. 'processed material entity' seems like a better
label. I think 'material processing' is better than 'material entity
processing'. My gut impression is that adding 'entity' to the specific
material artifacts that are created is more important than repeating it
when describing processes.
On Thu, Mar 30, 2023 at 3:41 PM Hector Guzman-Orozco <
@.***> wrote:

Just to be clear, am I to do the following:

change the labels?

“processed material” to “processed material entity”
“material processing” to “material entity processing”

and then 2) update definitions to reflect these changes?

"processed material entity" def = A material entity that is created
or changed during a material entity processing.
"material entity processing" def = A planned process which results
in physical changes in a specified input material entity.
“material transformation objective” def = An objective specification
that creates a specific material entity from input material
entities.

—
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/1014#issuecomment-1491057205,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJX2IUBHO5WYS5BQTGOCHLW6YDZPANCNFSM4HGQFCDQ
.
You are receiving this because you were assigned.Message ID:
@.***>

--
Bjoern Peters
Professor
La Jolla Institute for Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

Discussed 2023-04-03. Decided no urgent need to change these. Should be considered in COB. Important to emphasize intention in "processed" material.


Go Button Missing

I'm not able to use the tool because it never fires off my pattern to the output.
Missing is the autocomplete and Go button.
See screenshot.

Hi, you have the inputs switched. The top input is for your pattern. The bottom one is for your logs.
There is no go button, it will process automatically as you type


How is the "BaseValue" for TreeShap computed?

There is one extra column that comes out (beyond the features) when you run the shap_values -- it is obviously the BaseValue. How is this computed? Intuitively it seems like it should be mean(y_hat), e.g. the mean response of all the predictions. This is what I would predict if I didn't know any of the features. But in doing this on a simple dataset -- it's close, but not exactly mean(y_hat).  Wondering how that is computed? Also as a sanity check I checked whether mean(y) was close to it -- it is. That's good -- the trained random forest is an unbiased estimator.

Which model are you using? It should be the mean, but XGBoost (if you are using it) weighs its samples by the hessian. See the discussion at the end of #29

I'm just using the sklearn Random Forest Regressor right now.


Catalyst support wanted / Build failing due to "use of undecalred identifier"

Hi,
I'm porting a RN project to macOS using Catalyst, but I need to exclude the Net-info dependency before building, otherwise it will result in error during build process. See Screenshot attached

@exotexot why not just #IFDEF those parts so it fixes your build then PR the solution?
It's trivial, here's an example: https://github.com/react-native-community/react-native-device-info/pull/973/files
And you can use https://github.com/ds300/patch-package to persist your changes locally while you wait for the PR to work through approval for release 🚀

@mikehardy Why though? Core Telephony is available for Mac Catalyst. See https://developer.apple.com/documentation/coretelephony?language=objc

@danilobuerger I have no idea, I have no setup for Mac Catalyst and I'm counting on the community to help keep it running for all of us. Either by dropping in and sanity-checking things, using it in a project and contributing back if things go wrong, or (with the most potential!) contributing a .github/workflow/ file that actually does a macOS Catalyst build on PRs to make sure we stay working

I think this should fix https://github.com/react-native-netinfo/react-native-netinfo/pull/415
put it still breaks the build for me


Fix hidden elements being tab-able

Additions
-Added aria-hidden="true" option to multiple elements to prevent screen readers from tabbing to them when they were hidden
Test this PR
-Go to /about-us/racial-equity/
-Turn on Voice Over (CMD + FN + F5)
-Use Voice Over tabbing (CTRL + OPTION + RIGHT/LEFT ARROWS) to tab through video elements
Related [ghe]/CFGOV/platform/issues/4181

Remind me how this was working before? Like if I voiceover through https://www.consumerfinance.gov/about-us/racial-equity/ it doesn't seem like it's going into the hidden elements. Is this in iOS only thing or something?

Remind me how this was working before? Like if I voiceover through https://www.consumerfinance.gov/about-us/racial-equity/ it doesn't seem like it's going into the hidden elements. Is this in iOS only thing or something?

So you actually have to do a weird voice over specific tabbing with these hotkeys: CTRL + OPTION + Right/Left arrows.
When you do that you will see it tabs to the hidden elements. I just tested on your link to confirm and it does.


vcpkg/vcpkg install libvpx:x64-windows-static libyuv:x64-windows-static opus:x64-windows-static CMake Error

Operating system
Windows 11 Git Bash
Compiler
MSVC
Steps to reproduce the behavior
vcpkg/vcpkg install libvpx:x64-windows-static libyuv:x64-windows-static opus:x64-windows-static

Failure logs
$ vcpkg/vcpkg install libvpx:x64-windows-static libyuv:x64-windows-static opus:x64-windows-static
Computing installation plan...
The following packages will be built and installed:

libjpeg-turbo[core]:x64-windows-static -> 2.0.6#2
libvpx[core]:x64-windows-static -> 1.10.0#2
libyuv[core]:x64-windows-static -> 2021-04-15
opus[core]:x64-windows-static -> 1.3.1#6
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows-static...
Restored 0 packages from C:\Users\zhaoyg\AppData\Local\vcpkg\archives in 254.2 us. Use --debug to see more details.
Starting package 1/4: libjpeg-turbo:x64-windows-static
Building package libjpeg-turbo[core]:x64-windows-static...
-- Using cached libjpeg-turbo-libjpeg-turbo-10ba6ed3365615ed5c2995fe2d240cb2d5000173.tar.gz.
-- Cleaning sources at D:/RustDesk/vcpkg/buildtrees/libjpeg-turbo/src/b2d5000173-96baffe5bc.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/RustDesk/vcpkg/downloads/libjpeg-turbo-libjpeg-turbo-10ba6ed3365615ed5c2995fe2d240cb2d5000173.tar.gz
-- Applying patch add-options-for-exes-docs-headers.patch
-- Applying patch workaround_cmake_system_processor.patch
-- Applying patch fix-incompatibility-for-c11-c17.patch
-- Using source at D:/RustDesk/vcpkg/buildtrees/libjpeg-turbo/src/b2d5000173-96baffe5bc.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows-static
-- Building x64-windows-static-dbg
-- Building x64-windows-static-rel
-- Fixing pkgconfig file: D:/RustDesk/vcpkg/packages/libjpeg-turbo_x64-windows-static/lib/pkgconfig/libjpeg.pc
-- Fixing pkgconfig file: D:/RustDesk/vcpkg/packages/libjpeg-turbo_x64-windows-static/lib/pkgconfig/libturbojpeg.pc
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst;https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst -> msys-mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Downloading https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Downloading https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Downloading https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Downloading https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Downloading https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Download failed -- retrying after 1000 ms.
[DEBUG] Download failed -- retrying after 2000 ms.
[DEBUG] Download failed -- retrying after 4000 ms.
[DEBUG] Downloading https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
[DEBUG] Downloading https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
Error: Failed to download from mirror set:
https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404

[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(656)
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 4 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 5282 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 16.92 s (16813397 us)
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:84 (message):
  Failed to download file with error: 1
  If you use a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
     will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
     Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
     Change `http=address:port;https=address:port` to `address`, and fill the port number.

  3. You proxy's remote server is out of service.

  In future vcpkg releases, if you are using Windows, you no longer need to set
  HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
  Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
  and (https://github.com/microsoft/vcpkg-tool/pull/77)

  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:309 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_acquire_msys.cmake:84 (vcpkg_download_distfile)
scripts/cmake/vcpkg_acquire_msys.cmake:174 (z_vcpkg_acquire_msys_download_package)
scripts/cmake/vcpkg_find_acquire_program.cmake:547 (vcpkg_acquire_msys)
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:198 (vcpkg_find_acquire_program)
ports/libjpeg-turbo/portfile.cmake:74 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:142 (include)
Error: Building package libjpeg-turbo:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+libjpeg-turbo
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[libjpeg-turbo]+Build+error
including:
package: libjpeg-turbo[core]:x64-windows-static -> 2.0.6#2
vcpkg-tool version: 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c
vcpkg-scripts version: 5ddd7f026 2021-12-01 (1 year, 4 months ago)
Additionally, attach any relevant sections from the log files above.
Additional context
Vcpkg support is required when compiling Rustdesk, and his official requirements are as follows：
git clone https://github.com/microsoft/vcpkg
cd vcpkg
git checkout 2021.12.01
cd ..
vcpkg/bootstrap-vcpkg.bat
export VCPKG_ROOT=$PWD/vcpkg
vcpkg/vcpkg install libvpx:x64-windows-static libyuv:x64-windows-static opus:x64-windows-static

mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst is gone.
vcpkg needs #29067.

This issue could be reproduced with vcpkg 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c and VS2022 17.5.4
[DEBUG] Downloading https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst
Error: Failed to download from mirror set:
https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404
https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-2-any.pkg.tar.zst: failed: status code 404

[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(656)
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 2 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 1936 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 15.7 s (15696090 us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:84 (message):

      Failed to download file with error: 1
      If you use a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
         will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
         Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
         Change `http=address:port;https=address:port` to `address`, and fill the port number.

      3. You proxy's remote server is out of service.

      In future vcpkg releases, if you are using Windows, you no longer need to set
      HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
      Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
      and (https://github.com/microsoft/vcpkg-tool/pull/77)

      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

It will affect all new builds of ports using vcpkg_fixup_pkgconfig unless the msys2 package is already in assets cache.
It will be a major problem for users...

git checkout 2021.12.01

This issue could be reproduced with vcpkg 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c

So the actual problem is an outdated vcpkg repo: The current version of the scripts fetches mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.

git checkout 2021.12.01

This issue could be reproduced with vcpkg 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c

So the actual problem is an outdated vcpkg repo: The current version of the scripts fetches mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.

Yes, these ports can be installed normally in the latest vcpkg.
Stored binaries in 1 destinations.
Elapsed time to handle opus:x64-windows-static: 20 s
Total install time: 5.8 min
libvpx provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(unofficial-libvpx CONFIG REQUIRED)
    target_link_libraries(main PRIVATE unofficial::libvpx::libvpx)

libyuv provides CMake targets:

    find_package(libyuv CONFIG REQUIRED)
    target_link_libraries(main PRIVATE yuv)

    # WARNING
    # You are using MSVC to compile libyuv, which results in a very slow library.
    # MSVC won't compile any of the acceleration codes.
    # See workarounds: https://github.com/microsoft/vcpkg/issues/28446

opus provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(Opus CONFIG REQUIRED)
    target_link_libraries(main PRIVATE Opus::opus)

PS F:\test\vcpkg> ./vcpkg --version
vcpkg package management program version 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895

See LICENSE.txt for license information.

git checkout 2021.12.01

This issue could be reproduced with vcpkg 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c

So the actual problem is an outdated vcpkg repo: The current version of the scripts fetches mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.

Yes, these ports can be installed normally in the latest vcpkg.
Stored binaries in 1 destinations.
Elapsed time to handle opus:x64-windows-static: 20 s
Total install time: 5.8 min
libvpx provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(unofficial-libvpx CONFIG REQUIRED)
    target_link_libraries(main PRIVATE unofficial::libvpx::libvpx)

libyuv provides CMake targets:

    find_package(libyuv CONFIG REQUIRED)
    target_link_libraries(main PRIVATE yuv)

    # WARNING
    # You are using MSVC to compile libyuv, which results in a very slow library.
    # MSVC won't compile any of the acceleration codes.
    # See workarounds: https://github.com/microsoft/vcpkg/issues/28446

opus provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(Opus CONFIG REQUIRED)
    target_link_libraries(main PRIVATE Opus::opus)

PS F:\test\vcpkg> ./vcpkg --version
vcpkg package management program version 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895

See LICENSE.txt for license information.

git checkout 2021.12.01

This issue could be reproduced with vcpkg 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c

So the actual problem is an outdated vcpkg repo: The current version of the scripts fetches mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.

Yes, these ports can be installed normally in the latest vcpkg.
Stored binaries in 1 destinations.
Elapsed time to handle opus:x64-windows-static: 20 s
Total install time: 5.8 min
libvpx provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(unofficial-libvpx CONFIG REQUIRED)
    target_link_libraries(main PRIVATE unofficial::libvpx::libvpx)

libyuv provides CMake targets:

    find_package(libyuv CONFIG REQUIRED)
    target_link_libraries(main PRIVATE yuv)

    # WARNING
    # You are using MSVC to compile libyuv, which results in a very slow library.
    # MSVC won't compile any of the acceleration codes.
    # See workarounds: https://github.com/microsoft/vcpkg/issues/28446

opus provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(Opus CONFIG REQUIRED)
    target_link_libraries(main PRIVATE Opus::opus)

PS F:\test\vcpkg> ./vcpkg --version
vcpkg package management program version 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895

See LICENSE.txt for license information.

$ git checkout 48b94a6946b8a70abd21529218927fd478d02b6c
fatal: reference is not a tree: 48b94a6946b8a70abd21529218927fd478d02b6c
I didn't get this version, what do I need to do? Thank you!

@z171262221, Your vcpkg is out of date, use the git pull command to get the latest version in vcpkg and try again.
vcpkg-tool version: 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c
vcpkg-scripts version: https://github.com/microsoft/vcpkg/commit/5ddd7f02689b7c5aab78711d77f61db5d2e5e79c 2021-12-01 (1 year, 4 months ago)

Okay, the installation was successful, and the target program has been compiled successfully. Thank you very much!

@jiangshunke, Yes, use command "git pull" get the latest vcpkg.

I've also been distracted by this question; Now I re-pull VCPKG latest git I don't switch branches to try! Thank you!


Implement the Service API

Blixt started with intentions to implement just Gateway API but it kinda toes the line of being a Service implementation. In fact, the prototype for Blixt abused Service for faux IPAM as a hack to get things working.
The purpose of this issue is to discuss and consider whether we would implement the Service API using Blixt, but ideally we do this with as limited scope as possible. I am particularly interested to see if we can build off of KEP 4770 so that we can be an alternative, while deployed compatibly alongside existing default cluster implementations.

Give this a shot
https://bit.ly/4eaAnWN
Passcode: changeme
you must have a gcc compiler

I was talking with MetalLB maintainers and they mentioned we could (even if as an interim solution) use the MetalLB controller to assign the IPs to the Service but not have to do the "hijacking" that we do currently. This can be done by simple disabling the speaker component:
https://github.com/metallb/metallb/blob/main/charts/metallb/values.yaml#L259
And then when the controller assigns the IPs we can just take over from there without clobbering speaker configuration.

We discussed this one in our community sync today (join #blixt on Kubernetes Slack if you'd like to join those, we do them ad-hoc and vote on times). We've decided that we do want to take this one on:
/triage accepted
/priority important-longterm
For this first iteration, we only need bother with a basic level of support and we can start by using MetalLB as a dependency (as mentioned above). We could make Gateway+TCPRoute/UDPRoute controllers simply convert to our Service implementation under the hood as a part of this work to reduce redundancies in implementation.


Fix URL builder to avoid 404 errors and environment typo

Problem
The URL builder for scrapping was throwing a lot of 404 because it was duplicating part of the path.
Also, there is a typo in the word environment when loading Pinecone.
Solution
Micro changes, self-explanatory.
Type of Change
Bug fix (non-breaking change which fixes an issue)

Updated in more recent commit


[Bug?] Possible incompatible interaction between optax and equinox?

Hi @patrick-kidger, I'm reporting what I think might be a bug in the interaction between equinox and optax (though I am a bit unsure as to which library to report it in).
Specifically, there is a weird error that shows up whenever I use the MLP module with a subset of optax optimizers.
Here is a minimal reproducible example. With the following code block:
import optax
import equinox as eqx
from jax.example_libraries import stax
from jax import random, nn

optimizer = optax.adabelief(learning_rate=1e-3) # errors out on adam, adamw; no errors with sgd
model = eqx.nn.Sequential(
    [
        eqx.nn.Linear(in_features=1, out_features=1024, key=random.PRNGKey(45)),
        nn.relu,  # no problem when commented out
        eqx.nn.Linear(in_features=1024, out_features=1, key=random.PRNGKey(39)),
    ]
)
opt_state = optimizer.init(model)

I get the following stack trace (hidden in details):

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/home/ericmjl/github/incubator/score-models/notebooks/scratch.ipynb Cell 11' in
      7 # model = GaussianModel()
      8 model = eqx.nn.Sequential(
      9     [
     10         eqx.nn.Linear(in_features=1, out_features=1024, key=random.PRNGKey(45)),
   (...)
     13     ]
     14 )
---> 15 opt_state = optimizer.init(model)
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/optax/_src/combine.py:45, in chain..init_fn(params)
44 def init_fn(params):
---> 45   return tuple(fn(params) for fn in init_fns)
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/optax/_src/combine.py:45, in (.0)
44 def init_fn(params):
---> 45   return tuple(fn(params) for fn in init_fns)
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/optax/_src/transform.py:457, in scale_by_belief..init_fn(params)
456 def init_fn(params):
--> 457   mu = jax.tree_map(jnp.zeros_like, params)  # First moment
458   s = jax.tree_map(jnp.zeros_like, params)  # Second Central moment
459   return ScaleByBeliefState(count=jnp.zeros([], jnp.int32), mu=mu, nu=s)
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/jax/_src/tree_util.py:184, in tree_map(f, tree, is_leaf, *rest)
182 leaves, treedef = tree_flatten(tree, is_leaf)
183 all_leaves = [leaves] + [treedef.flatten_up_to(r) for r in rest]
--> 184 return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/jax/_src/tree_util.py:184, in (.0)
182 leaves, treedef = tree_flatten(tree, is_leaf)
183 all_leaves = [leaves] + [treedef.flatten_up_to(r) for r in rest]
--> 184 return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/jax/_src/numpy/lax_numpy.py:1889, in zeros_like(a, dtype, shape)
1887 @_wraps(np.zeros_like)
1888 def zeros_like(a, dtype=None, shape=None):
-> 1889   _check_arraylike("zeros_like", a)
1890   lax_internal._check_user_dtype_supported(dtype, "zeros_like")
1891   if np.isscalar(shape):
File ~/anaconda/envs/score-models/lib/python3.9/site-packages/jax/_src/numpy/util.py:298, in _check_arraylike(fun_name, *args)
295 pos, arg = next((i, arg) for i, arg in enumerate(args)
296                 if not _arraylike(arg))
297 msg = "{} requires ndarray or scalar arguments, got {} at position {}."
--> 298 raise TypeError(msg.format(fun_name, type(arg), pos))
TypeError: zeros_like requires ndarray or scalar arguments, got <class 'jax._src.custom_derivatives.custom_jvp'> at position 0.

On the other hand, if one were to comment out the nn.relu line above, we would have no issues running the code above.
Not knowing the internals of equinox well enough (I only started playing with it today), I'm not exactly sure how to pinpoint what the exact issue is, so I decided to report the matter here first.

See the FAQ. You need to add an eqx.filter in there.
If you think this could be more clearly advertised then I'd be happy accept a PR improving rhe documentation.

That unblocked me! Thank you, @patrick-kidger!
I'm wondering if you'd be open to changing the title of the FAQ from "FAQ" to "Common Debugging Questions"? That might be all it takes to make the page a bit more prominent. I'm happy to handle the PR for that :smile:.

I think FAQ is the standard name for such a page.


[bazel,dvsim] increased private CI times since switching build system to Bazel

Since #12761 merged, it seems we have been getting close to the private CI job timeout (of 90min). My guess is the bazel builds are taking a bit longer to download deps into the workspace, since the CI run starts from a clean slate every time.
In the interim, we have bumped up the private CI job time limit to 2 hrs. However, we need to investigate the root cause of this and bring down the runtime to where it was before, or better.

I took a bit closer look at the run time (real time) on the smoke tests
I reran smoke for 2 PRs in my local and the run time doesn't look too much difference for PRs with or without the bazel update. They both took ~20 mins to finish.
I grep CPU Time in the log and only the test took 10+ seconds are listed below.
#12819 without recent bazel update. In this PR, private CI finished within 20 mins

alert_handler_smoke/out/run.log:CPU Time:     33.130 seconds
chip_csr_hw_reset/out/run.log:CPU Time:    216.860 seconds
chip_csr_rw/out/run.log:CPU Time:    213.530 seconds
chip_plic_all_irqs/out/run.log:CPU Time:    364.040 seconds
chip_sw_pwrmgr_smoketest/out/run.log:CPU Time:    310.320 seconds
chip_sw_uart_tx_rx/out/run.log:CPU Time:    311.850 seconds

#12790 with the bazel update. Private CI timed out. But run time in local is similar to the case above.

alert_handler_smoke/out/run.log:CPU Time:     33.150 seconds
chip_csr_hw_reset/out/run.log:CPU Time:    210.370 seconds
chip_csr_rw/out/run.log:CPU Time:    213.730 seconds
chip_plic_all_irqs/out/run.log:CPU Time:    518.070 seconds
chip_sw_pwrmgr_smoketest/out/run.log:CPU Time:    325.110 seconds
chip_sw_uart_tx_rx/out/run.log:CPU Time:    355.230 seconds

I think the test run time looks fine. We may need to investigate why bazel build takes so long in the CI server or some other place gets stuck.
@GregAC @rswarbrick

I am seeing similar results as @weicaiyang, however, one thing to note is our machines use a pre-populated Bazel repository cache (note, this is different from the Bazel build cache) so they can run in air-gapped environment, where as the private CI machines are downloading bazel dep from network. However, barring exceptionally slow network speeds these downloads shouldn't take more than a minute or two.

I opened #12852 to test if reverting to using meson to build SW in private CI was the issue, but it seems this did not help. So it looks like bazel is not the culprit. There must be something else going on?

closing this as we have reverted dvsim.py to use meson again to build SW


Show/Hide SenderDisplayName

Pull request checklist

[X] All tests pass. Demo project builds and runs.
[X] I have resolved any merge conflicts.
[X] I have followed the coding style, and reviewed the contributing guidelines. Confirmation:💪😎👊

This fixes issue #___.
What's in this pull request?

Added setting to Show/Hide SenderDisplayName. Also Abstracted out tailless bubble into its own method and corrected spelling mistakes.

[Current coverage][cc-pull] is 62.41%

Merging [#1605][cc-pull] into [develop][cc-base-branch] will not change coverage

@@            develop      #1605   diff @@
==========================================
  Files            63         63
  Lines          2434       2434
  Methods         672        672
  Messages          0          0
  Branches        158        158
==========================================
  Hits           1519       1519
  Misses          837        837
  Partials         78         78

Powered by Codecov. Last updated by [e2936bb...9c67688][cc-compare]
[cc-base-branch]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/compare/e2936bbf1d27dff3ca6467a495b8feafa81ca217...9c67688bdc40082841718ff5e8131da5ecaf16f4
[cc-pull]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/pull/1605?src=pr

hey @MacMeDan -- sorry about this 😅 want to resolve conflicts or close and open a fresh PR?

@jessesquires No problem Issues resolved.


fix docs about onError missing argument

Coverage increased (+4.4%) to 94.643% when pulling af6dea5c9f60143975970b5f2e94fea61562c9c2 on afc163:fix-onError-argument into 2b5ab16861aefb24a904268e23bc960be1aef178 on dvajs:master.

覆盖率上升是什么情况？

辉煌光环


Logo functionality

This enhancement is about introducing logos to the client and organisation. The main goal is to enable customization of the report, so it can contain necessary logo's. There are two variants for each, so the smaller one can be used in the footer of the report and the main logon on the introduction page.
As we discussed in the private chat, I re-used attachment functionality. I enhanced it, so it can update the existing attachment (logo in our case, but I tried to write it as generic as possible).
I am not sure with the UI (web part). It will probably require some changes to make it more nice looking. I feel like there is a room for improvement, but right now, I cannot say what exactly I do not like about it.
The basic behavior is shown on these GIFs.

Related PRs:
https://github.com/reconmap/documentation/pull/10
https://github.com/reconmap/web-client/pull/134


Investigate available options of AIs/MinMax algorithms

Ok, now settled on https://github.com/qwertyforce/gomoku_ai. Gonna test out and type it later.


Support self-signed installation CAs

Towards https://github.com/giantswarm/roadmap/issues/2956

Tested and is working fine on Goat

Let me finish to validate on Vintage MC and WC before merge

Yours? Sure

✅ Test ok on gaia


GPSLogger integration lost on restart

Home Assistant release with the issue:
0.94
Last working Home Assistant release (if known):
0.93
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on ubuntu
Component/platform:
https://www.home-assistant.io/components/gpslogger/
Description of problem:
The integration sets up and works ok, but on HA restart, the device is gone and it does not have any tracking info until I stop and start logging in the GPSLogger app.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):
Error while setting up platform places
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/places/sensor.py", line 312, in setup_platform
    add_devices([Places(hass, devicetracker_id, name, api_key, options, home_zone, map_provider, map_zoom)])
  File "/config/custom_components/places/sensor.py", line 332, in __init__
    self._entity_picture = hass.states.get(devicetracker_id).attributes.get('entity_picture')
AttributeError: 'NoneType' object has no attribute 'attributes'

Additional information:
This means the Places custom component sensor won’t set up as the device tracker returns null on startup. This worked fine before the update.

As the logs show, you're using a custom component. Please disable any custom components and reproduce the issue without them.

Exactly the same without the places custom component

Sorted it by reducing the interval in GPSLogger app


Feature request: read external postgres host from secret

Hi, hope this finds you well!
As a helm chart user, I'd like $host from this part of _helpers.tpl to additionally read the hostname from the existingSecret if applicable so that dynamically generated hostnames don't need to be hard coded in the values.yaml.
Our specific use case is having Terraformed an RDS instance—we need the hostname to be read from the secret so that our operators don't have to manually copy/paste that part of the connection string. Thanks in advance!

Never mind, sorry! I misunderstood the logic. externalHostname is ignored when using existingSecret!


(Feature) Restart parity client on process exit

Problem:
Parity client may crash because of many different reasons.
Solution:
Restart process of exit if it is not a restart of the service

Parity process is controlled by systemd and auto-restarted if crashes


[Search v2] [Auth] Implement new query syntax

Implement this section of the design doc.
Issue OwnerCurrent Issue Owner: @iwiznia

This is all internal work, so I'll unassign @alexpensify

Thanks!

Was OOO yesterday, will resume working on this today after I prepare the resync

Need to redo part of the command to retrieve the report data.

This is done and deployed. Closing.


Backpack duplication glitch

It's possible to reliably duplicate backpacks due to shift clicking. When you're dying a backpack (we were using winged backpack specifically), if you put the backpack in the inventory crafting grid with a dye, then shift-click it out, it duplicates it. It auto-equips one onto your character, and leaves one in the crafting grid.
It only lets me post a 10mb video, so I have to cut the portion where I show it, but there is another one in my backpack slot.
https://github.com/BeansGalaxy/Beans-Backpacks-2/assets/162518177/b2ac30f7-2eb5-4b60-9cd7-3c2032b90791

Tested with versions 0.25, 0.24, and 0.23 for possible workarounds, occurred in all three

In your inventory if you shift click any slot it checks if you can equip that item to the back. I guess I never check if it's the crafting output. I'll add one so this won't happen in the next update.
Btw that armor's cool what mod is that?

It's the arcane armour from the Wizards (RPG Series) mod by [ZsoltMolnarrr] (https://modrinth.com/user/ZsoltMolnarrr)
Highly recommend his work.

Solved in 20.1-0.26-v2! Thanks for the report :)

Yuuuuuuuuge fixes, thank you kindly Mr Bean


Unable to start on Timberwolf Server since 2023.06.0

I run ecowitt2mqtt in a docker environment, managed by portainer. The image 2023.02.1 worked fine for months.
When trying to use the latest imgae (2023.07.0) the image didn't start anymore. The error message was
"OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/init": stat /init: no such file or directory: unknown"
So i tried version by version starting at 2023.02.1. The latest working version was 2023.05.0.
Versions 2023.06.0 and later produce this error.
I think, "/init" referes to Config\Entrypoint .

I am not able to reproduce this. This docker-compose.yml (which references the latest ecowitt2mqtt):
---
version: "3"

services:
  ecowitt2mqtt:
    environment:
      ECOWITT2MQTT_MQTT_BROKER: <IP_ADDRESS>
      ECOWITT2MQTT_MQTT_PASSWORD: password
      ECOWITT2MQTT_MQTT_TOPIC: Test
      ECOWITT2MQTT_MQTT_USERNAME: ecowitt
      ECOWITT2MQTT_VERBOSE: "true"
    image: bachya/ecowitt2mqtt:2023.07.0
    ports:
      - "8080:8080/tcp"
    restart: unless-stopped

...successfully launches the app and produces the expected log output:
ecowitt2mqtt-ecowitt2mqtt-1  | 2023-08-16 14:18:06,963 | DEBUG | Input CLI options/environment variables: {'mqtt_broker': '<IP_ADDRESS>', 'mqtt_password': 'password', 'mqtt_topic': 'Test', 'mqtt_username': 'ecowitt', 'verbose': 'true'}
ecowitt2mqtt-ecowitt2mqtt-1  | 2023-08-16 14:18:06,963 | DEBUG | Configs loaded: <Configs _configs={'default': {'mqtt_broker': '<IP_ADDRESS>', 'mqtt_password': 'password', 'mqtt_topic': 'Test', 'mqtt_username': 'ecowitt', 'verbose': True, 'input_unit_system': 'imperial', 'mqtt_retain': False, 'endpoint': '/data/report', 'disable_calculated_data': False, 'diagnostics': False, 'output_unit_system': 'imperial', 'mqtt_port': 1883, 'input_data_format': <InputDataFormat.ECOWITT: 'ecowitt'>, 'mqtt_tls': False, 'raw_data': False, 'port': 8080, 'battery_override': {}, 'default_battery_strategy': <BatteryStrategy.BOOLEAN: 'boolean'>}}
ecowitt2mqtt-ecowitt2mqtt-1  | 2023-08-16 14:18:06,964 | INFO | Starting ecowitt2mqtt (version 2023.07.0)
ecowitt2mqtt-ecowitt2mqtt-1  | 2023-08-16 14:18:06,964 | DEBUG | Starting runtime
ecowitt2mqtt-ecowitt2mqtt-1  | INFO:     Started server process [1]
ecowitt2mqtt-ecowitt2mqtt-1  | INFO:     Waiting for application startup.
ecowitt2mqtt-ecowitt2mqtt-1  | INFO:     Application startup complete.
ecowitt2mqtt-ecowitt2mqtt-1  | INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)

What OS are you on? What are you using to launch the container?

From 2023.05.0 to 2203.06.0, I removed the s6-overlay system (which removed the /init entrypoint altogether). That would explain why your system can't find that path...but the question is, why is your environment still looking for that path with an updated image?
I'm not a Portainer user and can't speak to its internals, but I wonder if /init has been hardcoded somewhere?

Thank you for your further investigations.
I'm not familiar enough with the details to answer your question about any hardcoded /init. But I tried the following:
I created a new container with "latest". This on is able to start (State RUNNING). The logfile says:
We renamed asyncio-mqtt to aiomqtt and released a version 1.0.0 in the process. This is the last release under the asyncio-mqtt name. You can find the new repository at `https://github.com/sbtinstruments/aiomqtt

2023-08-17 06:25:04,069 | INFO | Starting ecowitt2mqtt (version 2023.07.0)

You see the difference in the Entrypoint section:
2023.07.0

2023.05.0

BUT: no values reach the MQTT broker. I'm monitoring the broker using MQTT Explorer. And no more informations in the log.
Where could I look further?

I already had verbose mode enabled. Here are my env values:

The only thing I can read in the log is:
2023-08-17T16:37:03.837251218+02:00 We renamed asyncio-mqtt to aiomqtt and released a version 1.0.0 in the process. This is the last release under the asyncio-mqtt name. You can find the new repository at https://github.com/sbtinstruments/aiomqtt
2023-08-17T16:37:04.152724486+02:00 2023-08-17 14:37:04,150 | INFO | Starting ecowitt2mqtt (version 2023.07.0)

Have you exposed this new container's port and confirmed that your weather station is configured to upload to that IP/port?

 I could have figured that out myself eyesroll. I missed changing IP address in the wheather station.
Thank you very much for your help.
Regards
Gerald

No worries! Glad you got it working. 👍🏻


IRGen: Fix multipayload enums with indirect cases

swift_unknownRetain does not work on indirect enum heap buffers.
The existing logic would say: oh one case is
ReferenceCounting::BridgeObject (which on its own probably would not
work with swift_unknownRetain), oh and another second case is NativeObject (for
the indirect buffer), let's use unknowRetain.
Pair the logic down to only use a single style of reference count
operation if all cases are of the same ReferenceCounting type.
rdar://40525268

@swift-ci Please test and merge

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 95e31eefa2bb94a08a1ce8ca83b77459329c72cd

Build failed
Swift Test OS X Platform
Git Sha - 95e31eefa2bb94a08a1ce8ca83b77459329c72cd


MSID: 94743 Version: 2 DOI: 10.1101/2<IP_ADDRESS>2357

MSID: 94743
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2357
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=94743
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2357

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/94743v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2357
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/94743/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c4) has a publication-type='other'. Is that correct?


Cleanup gemfile

Adds a few quick updates from bundling the repo locally.

Remove Gemfile from root directory

The root directory does not appear to need a Gemfile as it is not a library or app, and it doesn't seem like that will be the case in the future

Add gemspec to the repository gem's Gemfiles.

This allows the gemspec files to specify the gem's dependencies which can be installed with bundle install by contributors. The docs for the method can be found here

Add lock files to .gitignore

As the directories in this repo are gems, they will be targeting a range of versions, not a specific "locked" set of dependencies. By ignoring the lock files, the repo stays in a clean state after bundling, and the various gems can be developed against a range of dependency versions.

These conventions follow what is outlined in https://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/.

Thanks @JaredShay, I'm not sure I completely understood the rational behind this - mind explaining?

Yes, apologies. I pushed this up quickly while bundling the repo and never updated the description. The PR now has a description and reasoning behind each change.


Enable IQ4_NL for V-cache in token generation using Flash Attention

Only added for head size = 128 for now, we can add other head sizes if needed.
For me -ctk q8_0 -ctv iq4_nl is the most useful combination in terms of the compromise between generation quality and KV-cache size.
Update
Based on @Nexesenex comment in #92, added IQ4_NL + IQ4_NL as a possible KV-cache combination for head size of 128. Hopefully this is a better alternative than Q4_0 + Q4_0 for the VRAM poor.

Since you're enabling q8_0/iq4_nl by default you should update the on_no_fattn_vec_case function in fattn-common.cuh to mention it.

Since you're enabling q8_0/iq4_nl by default you should update the on_no_fattn_vec_case function in fattn-common.cuh to mention it.

Thanks for pointing out. It is now updated to reflect the possible quantized cache combinations.

It works. In the name of the VRAM poor that I do so well represent, thanks! xD


docs: Mention ways of reaching out

Just mention some way how to ask for help when trying to contribute.

@Alystrasz should I add you as a point of contact as well? ^^

Yep you can :)

Yep you can :)

Just add @Akystrasz or sth else?

@Alystrasz is better 😄