Build and document 'dce upgrade' functionality

Add a flag to dce system deploy that specifies the version of dce to deploy.
Default is to deploy latest version
Add a quick start for updating dce given you have an old version deployed
Consider how to deal with incompatibilities between different versions of the cli and dce backend

To reduce risk, let's consider pinning the version as default behavior and instead provide a "--latest" or something flag to allow users you override the version if desired.


What is the recommended approach to create an annotated tag (instead of a lightweight tag) when merging a PR created by release-please?

My team just started using release-please (via GitHub Actions workflow utilizing https://github.com/google-github-actions/release-please-action) and we noticed that the first git tag created for our first merged release PR created a lightweight tag instead of an annotated tag. Our old release process used standard-version/commit-and-tag-version, which creates annotated tags, and I was hoping to continue that pattern with release-please.
When using a lightweight tag, git describe does not respect the latest tag (although git describe --tags does) and returns something like v1.81.1-10-gfb8b2220 instead of the expected v1.82.0. I'm not sure if this will cause problems downstream, but I thought there might be an easy way to tell release-please to create an annotated tag instead.
Is there a recommended way to accomplish this?
I have considered doing something like git tag -a -f <tagname> <tagname>^0 as a post-processing step in our GitHub Actions workflow, but I think that might cause problems for generated releases in GitHub.
I also briefly looked into the possibility of using a plugin to accomplish this, but it seems like plugins are mostly for working with monorepos (which my team is not using).
If necessary, I don't have a problem opening a PR to add a new configuration option to use annotated tags instead of lightweight tags, but I'm having difficulty finding where in the codebase the lightweight tag is actually created. I also don't want to assume that this necessitates a code change to release-please as it may be something easy I am just missing/haven't found yet.
Please advise, and thanks!

https://github.com/googleapis/release-please/blob/main/src/manifest.ts#L1194 eventually calls out to https://github.com/googleapis/release-please/blob/main/src/github.ts#L1355 which just makes a github release. Unfortuantely, github's release feature doesn't do annotated tags.
People have been complaining about this for a few years.

https://github.com/isaacs/github/issues/1916
https://github.com/orgs/community/discussions/4924

which just makes a github release.
Unfortuantely, github's release feature doesn't do annotated tags.

Thanks @justinabrahms. I realized this after I posted the question, but I appreciate the confirmation.
It looks like this is the GitHub API endpoint that can be used to create an annotated tag (before creating the tag reference): https://docs.github.com/en/rest/git/tags?apiVersion=2022-11-28#create-a-tag-object
I'm not sure if that endpoint/approach would cause any problems for (subsequently) creating a release in GH, but perhaps a PR for a new boolean configuration parameter for release-please/release-please-action (e.g. use-annotated-tag) is possible.

I have an initial attempt at code changes to add a new annotated boolean release option here, but I'm not quite sure it works or is the right approach: https://github.com/googleapis/release-please/compare/main...nexdrew:release-please:use_annotated_tag
Any feedback or guidance would be appreciated.

@nexdrew It'd probably be a little easier if that was a PR.
I don't think you need to specify the poster. Presumably octokit already has an authenticated session. That said, that looks approximately right w/o having tested it. I assume you'll want to write a test or something to get it merged.

@nexdrew I just ran into this issue and this looks pretty much like the fix I had in mind. It would be good to get this into a PR. Probably faster than Github fixing their releases.


[BEAM-10379] Add bit_and back into Calcite SQL.

The incorrect behavior when mixing null and non-null values is still present.
bit_and is still excluded from ZetaSQL.
R: @amaliujia

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

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

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Hi Kyle, do you want to enable bit_and in ZetaSQL? If so I guess you will also need to uncomment this line: https://github.com/apache/beam/blob/816017e44e3209d334f4f3b2bc3fa829663c530e/sdks/java/extensions/sql/zetasql/src/main/java/org/apache/beam/sdk/extensions/sql/zetasql/SupportedZetaSqlBuiltinFunctions.java#L416
Or do you just want to uncomment the code without turning on the feature?

Hi Kyle, do you want to enable bit_and in ZetaSQL?

I wanted to enable it in Calcite, but keep it out of ZetaSQL because it fails compliance tests.


Sync item state from ADO to Asana

As a user, I want the state of items to be synced from ADO to Asana, so items that are closed in ADO are closed in Asana.

Related to #24 - Ensure that we limit the sync to a fixed period.

Related to #85 - We need to use another call to get the closed items from ADO.


ReferenceError: Can't find variable: ResizeObserver

Our users that are on Safari 12 seem to be getting this error, but I can't find anything about ResizeObserver on here. We're using Wavesurfer 7.7.15. From googling, it sounds like this could be to do with polyfills but I don't really know what that is to be honest. Hoping someone can point me in the right direction!

I’m surprised there are still Safari 12 users. It came out in 2018. :)
It should be easy to fix though.

Yes, you can load a polyfill on your end but I was talking about adding an if in wavesurfer code.


Implementation: Multi-Class Backpropagation

The BackPropagationLearner can now learn for more than two classes. Previously, it was a binary learner, so NeuralNetworkLearner and PerceptronLearner were binary classifiers. I extended the functionality to classify into multiple classes.

Added a new function, init_examples, to initialize the inputs and outputs for the learner. The outputs need to be in an one-hot representation, where the 1 represents the class the item is classified in.

Added tests for the algorithms (unfortunately, the learners can sometimes be wrong, so the tests are a bit general).

Added a new function, find_max_node, which takes as input the output nodes and returns the index of the one with max value.

Moved the helper functions below the three main algorithms (Neural Network, BackPropagation and Perceptron).

Implemented multi-class functionality.

Note: The learning Notebook needs to be updated too, but I would prefer to do it after this is reviewed so we are certain this is the implementation we want to go with.

Cool work, just one suggestion, the function find_max_node could be rewritten to:
def find_max_node(nodes):
    return nodes.index(max(nodes, key=lambda node: node.value))

I was thinking of writing it like this, which is more pythonic, but I don't feel it's that needed. First, we are writing a lot of keywords (index, then max, then the lambda) all in one line which isn't that easy to the eye. Second, this is a simple helper function that everyone knows what it does by the name alone. The way I have currently written it is the way that everyone has been seeing it for a long, long time. I just imagine that if someone was skimming through the function, he wouldn't mind it the way it is written now, but if it was written in the pythonic way you mentioned, it might catch an eye or two.
Anyway, this was my reasoning behind this decision. Long story short, even though there is a more pythonic way to write it, the function itself is so commonly seen the way I wrote it that I think it balances out.
I don't have strong feelings on this though and I would change it if more people feel the same way. Thanks for the suggestion.

I too feel we need to change find_max_node function. The way it uses index as -1 and initial maximum as -10000 feels 'hackish'. Also use argmax instead of max. It is the standard notation used in the book.

Since you agree with @lucasmoura too, I will make the changes.
This is what I will use:
def find_max_node(nodes):
    return nodes.index(argmax(nodes, key=lambda node: node.value))

Unfortunately my PC burned down so I can't test this. Can someone confirm the above returns the index of the max element? Thanks.

@MrDupin I have made the following test and it works fine:
from collections import namedtuple
from utils import argmax
import pytest

def test_node():
    Node = namedtuple('Node', ['value'])

    nodes = [Node(value) for value in range(10)]

    assert 9 == nodes.index(argmax(nodes, key=lambda node: node.value))

I just thought of something else that maybe should be discussed.
I changed max_score to 0 (at least for now). If the values in the nodes don't exceed 0, something went terribly wrong. Since the BackPropLearner converges in values in the range [0,1], if the maximum value is negative, there is an issue. If max_score is initialized at 0, we will catch that issue but in the pythonic way we won't. In that case, a seemingly random index will be returned and the user will be none the wiser.
So, a new idea I want to throw on the table is this: We keep the traditional find max method that I wrote, but if the index at the end is -1, we raise an exception.
Another idea is to go the pythonic route, but in the end check if max_score is negative. If yes, we raise an exception. I don't feel though this is as pythonic and beats the purpose of that route.
I would like another opinion on this. Sorry for taking so long to decide, this is a pretty big PR and I wouldn't want to mess it up.

PS: The title of the second to last commit is wrong, I rushed it. 0 is better than -1.

@MrDupin Let's change it to the pythonic implementation and add the >0 check in test files. If there is something wrong in the implementation, it must ideally be caught in tests and fixed. I don't like the idea of performing runtime checks. They must be used only for debugging. Adding these checks makes the code hard to read and defeats the purpose of tests.


Database#transaction returns block result

Closes #113.

Awesome! Thank you so much for contributing this improvement.


Current default RAM seems to be 1024

As discussed with @NolanChan, the default value for RAM is total plan ram / total number of services
Could you please document this?


Any plans to implement RAG (retrieval augmented generation)?

I think this is a great project when it comes to data privacy and compliance for Organizations looking to adopt Gen AI with LLAMA 2. Adding capabilities for this private GPT to get ingested with Org specific data (like docs,confluence pages) as vectors would take this to next level. let me know if I can contribute. thank you!

This is the biggest thing I'm seeking out. I want to give a self-hosted LLM access to my own data that I've collected, so I can search and summarize through it.

This is a good idea. Any tools or post about this? I can take a look on how to implement this.

Maybe this https://gpt-index.readthedocs.io/en/latest/?

@edgar971 I'm having 2 ressources in mind :

https://python.langchain.com/docs/expression_language/cookbook/retrieval
https://github.com/imartinez/privateGPT


Best practise with vcpkg for multiple tool sets

Some while ago, there was a discussion about how to manage and develop code using different tool sets in visual studio. At the very least v140-v143. I contributed two scripts that, first generated triplets for these toolsets out of the default ones and then ensured that
vcpkg.bat install xxx:x64-windows etc. generated the full complex of libraries. (see better management of multiple builds #7932).
I am currently setting up a new machine, It has a clean version of the SDKs for 7.1, 8.0, 8.1, and 10 and the current version of vs2019. My question, 6 months on, is what is the best practice for making this work smoothly so one can build with any chosen toolset, and is there now an agreed documentation.
Visual studio 19 boasts knowledge of the following tool sets on my configuration:

Personally my current need is to easily support C++ python extensions with a small boost dependency back to python 2. You will see that an automated approach that is correct really is required. It does not need to support every toolset, in my case I need to ensure my code builds for toolkits: 142 140 100 90, debug and release, x86 and x64 for windows and (to create a manylinux package) on an old version of centos and also on the mac. (24 contexts in all! 12 if one ignores the debug versions).
So I am very interested indeed in cross platform tools for building code with dependencies. I would like to use vcpkg with best practise. I don't find the correct part of the documentation.
Thanks. I still think the whole idea is wonderful.

That's a good idea!
I think we need a management module and provide multi-version support for each compilation method. (It needs to support cmake at least)
So, please track issue #7923.
Thanks.


s3cmd does not work from nix-shell (even without --pure)

Issue description/Steps to reproduce
I have s3cmd installed globally via environment.systemPackages
[anders@gurney:~/devel/card-game]
$ s3cmd ls
[anders@gurney:~/devel/card-game]
$ nix-shell -p s3cmd

[nix-shell:~/devel/card-game]$ s3cmd ls
ERROR: SSL certificate verification failure: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)

Technical details
[anders@gurney:~/devel/card-game]
$ nixos-version
16.09.git.1ceb6ea (Flounder)
[anders@gurney:~/devel/card-game]
$ nix-env --version
nix-env (Nix) 1.11.2
[anders@gurney:~/devel/card-game]
$ nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"16.09.git.1ceb6ea"

hmm. This appears to be because nix shell is setting SSL_CERT_FILE
[anders@gurney:~/devel/card-game]
$ env | grep SSL
[anders@gurney:~/devel/card-game]
$ nix-shell -p s3cmd

[nix-shell:~/devel/card-game]$ env | grep SSL
SSL_CERT_FILE=/no-cert-file.crt

I'm not sure why that's done in a non --pure shell

Related are https://github.com/NixOS/nixpkgs/issues/13744, https://github.com/NixOS/nixpkgs/issues/15873 and https://github.com/NixOS/nixpkgs/pull/15571

Closing this since its a known issue and described in #13744.


Feature/jewish migration

Add a corpus definition for the dataset exposed by the Jewish Migration repo. Close #1276 : adds JSONCorpus, and ingests via a call to the requests library (in corpus.sources).
Also introduces a geo_field as a possible mapping type.

Can you include updates for these documentation pages?

https://github.com/UUDigitalHumanitieslab/I-analyzer/blob/develop/documentation/How-to-add-a-new-corpus-to-Ianalyzer.md
https://github.com/UUDigitalHumanitieslab/I-analyzer/blob/develop/documentation/Defining-corpus-fields.md

Also, heads-up that the JSON corpus should eventually be included in https://github.com/UUDigitalHumanitieslab/ianalyzer-readers - this is a bit inconvenient right now because it's an outfactor that that is almost ready to be integrated, so it should stay up to date.
Can you make a issue/PR to that package with your additions? You can do that after merging this PR, whatever order makes sense.


Core: NEW station map

About the PR

Nanotrasen has introduced a new station into the ranks! Core is a 40-70 medium population map featuring a singularity in the center along with an off-branching arrivals area and a singular solar panel array.
Station-exclusive jobs include:

Boxer
Zookeeper
Reporter

The evacuation shuttle used here is Rod, which is on another unapproved PR right now where the map Marathon needs to be tweaked by Emisse.
P.S. Before merging I would like a considerable amount of playtesting and player feedback from not just maintainers.
(these are the main points to be covered)

singularity
job spawns
power
firelocks and spacing
fax
air alarms/sensors
atmos
cameras
telecommunications
disposals
artifact room
warp points as ghost

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: Ubaser

add: Nanotrasen has hired a group of architects to change up their selection with the introduction of the new space station, Core!

What happens when Arrivals runs out of EVA suits?

What happens when Arrivals runs out of EVA suits?

i might add a small disposals section for people so they can return the suits to arrivals. Otherwise, just run through space you'll live :)

goofy ahh arrivals

the singulo window grilles arent shocked so singuloose will be ridiculously easy

A few things from a very brief look over:
That arrivals is unique but isn't going to work.  New players especially will be confused and punished by the forced spacewalk, etc.
The solar array is massive and boring, should split it into multiples and make them more interesting
Serious lack of maints: med and sci especially have none, and the maints that do exist are straight, narrow, and empty
Station specific jobs: these are station specific, meaning intended for their specific stations.
Looks like you've put in a good effort for it though so I can do a more in depth review when it's ready

this map has next to 0 maintenance of any kind, which is a major problem.
also, check is right about arrivals. neat concept, but you're really throwing new players to the wolves. Many people aren't going to be able to go spacewalk to the main station a few minutes after joining.

Also if you're including a custom evac shuttle, you should include the render of that as well since it will also need to be reviewed

reviewed minor things on discord, will do a more in depth design review later today or tomorrow after work
check cartography threads

no robotics?

 I suggest plasma glass to add a cool effect of being able to see a singulose from maints

Along with non electrified grills it doesn’t have plasma glass or shutters so you WILL die if you stay too long in maints with a singulose active. I suggest plasma glass to keep the cool effect of being able to see a singulose from maints

this is actually on purpose, i added a set of glass, plasma sheets and rods so that engineering can do it themselves :)

Also if you're including a custom evac shuttle, you should include the render of that as well since it will also need to be reviewed

i have a separate PR that should be accepted soon

Along with non electrified grills it doesn’t have plasma glass or shutters so you WILL die if you stay too long in maints with a singulose active. I suggest plasma glass to keep the cool effect of being able to see a singulose from maints

this is actually on purpose, i added a set of glass, plasma sheets and rods so that engineering can do it themselves :)

Radiation in its current implementation is really overly punishing, particularly since it is functionally undetectable unless you are an engineer.  It is incredibly frustrating for players who die to something they are not aware is even happening or not aware of what to do etc.  If radiation was better conveyed to players through like green glowy stuff or in some other way this wouldn't be an issue, but as it stands, you're just going to end up killing 1/4 of the crew every shift and the victims will probably not be very happy about it

Along with non electrified grills it doesn’t have plasma glass or shutters so you WILL die if you stay too long in maints with a singulose active. I suggest plasma glass to keep the cool effect of being able to see a singulose from maints

this is actually on purpose, i added a set of glass, plasma sheets and rods so that engineering can do it themselves :)

Radiation in its current implementation is really overly punishing, particularly since it is functionally undetectable unless you are an engineer. It is incredibly frustrating for players who die to something they are not aware is even happening or not aware of what to do etc. If radiation was better conveyed to players through like green glowy stuff or in some other way this wouldn't be an issue, but as it stands, you're just going to end up killing 1/4 of the crew every shift and the victims will probably not be very happy about it

Hm yeah that makes a lot of sense… i might add signs or something similar to warn anyone passing through

Im having a stroke and the ghost conflict is not going away

im confused i think i did something wrong

i was simply trying to update my map guh

i was simply trying to update my map, but im going to just reopen it real quickly

i was simply trying to update the thing, still new to github. Reopening now


CLI add support for array type

CLI: Add support for array type in ES visibility store.

Coverage increased (+0.4%) to 66.935% when pulling 9e234408004c8059455712f773a0dd04887571d6 on salist into d884315233b19f2992bdf49797ecae5c29f29a82 on master.


nextcloud-client: 3.3.6 -> 3.4.0

Motivation for this change
https://github.com/nextcloud/desktop/releases/tag/v3.4.0
Tested sync
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 148066 run on x86_64-linux 1

1 package built:

nextcloud-client


Load casks from the JSON API with HOMEBREW_INSTALL_FROM_API

This PR updates the method for loading casks when HOMEBREW_INSTALL_FROM_API is set. Now, casks are loaded directly from the JSON API in the same way that formulae are. I've started to test this out locally and haven't had any issues so far (outside of the ones listed below).
It's worth noting that the old cask-source API is still being used to write the cask source to the .metadata folder. This is similar to the way that formula bottles also contain the formula file, except that the source for casks are retrieved using the API rather than a bottle.
Also, a nice little side effect of this PR is that brew edit now works for casks with HOMEBREW_INSTALL_FROM_API (while the taps are installed, of course)

Here are some known issues:

Casks with {uninstall_,}{pre,post}flight stanzas will currently ignore those when installing and uninstalling. This can cause issues in casks like vlc which rely on these blocks to create files that will be referenced by the regular artifact stanzas. This is a relatively significant issue that is probably worth brainstorming about sooner rather than later since it does technically cause a regression from the old API-install behavior for casks.

Review period will end on 2022-12-30 at 08:06:20 UTC.

One possible way to solve the pre/postflight issue is just to use the cask-source API to get the ruby source for those methods and evaluate that.
This, of course, is not ideal since we're executing arbitrary code that was downloaded from the internet. We can probably improve this a bit by adding a hash of the source to the JSON API. This would help prevent corrupted downloads from causing issues since the hash wouldn't match, but isn't really any more secure against malicious actors.
Thoughts on this method?

One possible way to solve the pre/postflight issue is just to use the cask-source API to get the ruby source for those methods and evaluate that.

This seems reasonable, particularly if we can indicate somehow in the JSON the minority of cases where this is required.

This, of course, is not ideal since we're executing arbitrary code that was downloaded from the internet. We can probably improve this a bit by adding a hash of the source to the JSON API. This would help prevent corrupted downloads from causing issues since the hash wouldn't match, but isn't really any more secure against malicious actors.

I think if this is always over HTTPS: I'm not overly concerned. Ultimately, if you can MITM the formulae or cask JSON APIs: you can execute arbitrary code.
Any checksums here would have to be stored and generated in a different location to be useful (think like how bottles checksums are stored in Git).
The only way I can think to have a checksum involved here would be something like using the GitHub raw Git API/endpoints, specifying the URLs with the Git checksums (rather than branch checksums) embedded and using this instead of cask-source. This at least gets us some separation between formulae.brew.sh generation and the raw Ruby (stored in a Git repository) but I'm not sure if this is overkill.

Yeah, testing is definitely something we'll need to look at more before making this the default since we don't really have any HOMEBREW_INSTALL_FROM_API coverage yet.
My plan was to tackle testing in a future PR, but I can look into adding some basic tests for Homebrew::API for now

This seems reasonable, particularly if we can indicate somehow in the JSON the minority of cases where this is required.

Do you mean indicate the cases where a *flight block is around or the cases where the *flight block is crucial to the install process? We already list the flight blocks in the JSON. Doing the latter would probably require a maintainer to explicitly indicate that its the case
Re checksums, I was thinking about using them as a way to ensure that files aren't corrupted more than as a way to prevent MITM attacks. We already check the cask.json file for corrupted downloads by making sure it is valid JSON. To ensure that cask-source files are not corrupted before we try to execute them, I was thinking was more that we take a hash of the cask-source file and include that in the JSON API. Then, if we compare them and they don't match we know that at least one was corrupted somehow and we shouldn't try to execute it.
It might be that the file being valid ruby is good enough for us, though, and so the checksum thing is not necessary

Review period ended.

My plan was to tackle testing in a future PR

Fine with me 👍🏻

Do you mean indicate the cases where a *flight block is around or the cases where the *flight block is crucial to the install process? We already list the flight blocks in the JSON. Doing the latter would probably require a maintainer to explicitly indicate that its the case

Ok, cool, if we list them in the JSON then presumably we only need to fetch them when they are present there, right?

Then, if we compare them and they don't match we know that at least one was corrupted somehow and we shouldn't try to execute it.

I feel like we should just retry the download in this case and only fail if it fails more than the current number of retries.

It might be that the file being valid ruby is good enough for us, though, and so the checksum thing is not necessary

Yeh, I think that is good enough 👍🏻

Okay, *flight blocks can now be loaded from the API. However, I've found that this isn't always enough to solve the problem. Take vlc as an example:
cask "vlc" do
  # ...

  # shim script (https://github.com/Homebrew/homebrew-cask/issues/18809)
  shimscript = "#{staged_path}/vlc.wrapper.sh"
  binary shimscript, target: "vlc"

  preflight do
    File.write shimscript, <<~EOS
      #!/bin/sh
      exec '#{appdir}/VLC.app/Contents/MacOS/VLC' "$@"
    EOS
  end

  # ...

Executing the raw preflight block when loading from the API fails because there's no definition for the shimscript variable. We don't currently encode those in the API at all. This doesn't affect the binary artifact, though, since the string value of shimscript is what's returned to the API.
Any thoughts on how best to deal with this?

Something else to keep in mind is other configuration-specific strings that are fully expanded in the JSON. For example, the JSON expands appdir to the default /Applications and interpolates this wherever it's used. So, a user specifying their own value for appdir would not see that value respected when installing from the API.
We can probably filter out /Applications and replace it with a placeholder like we do with /opt/homebrew. This does make me wonder, though, what other similar issues I'm forgetting about

Any thoughts on how best to deal with this?

introduce cops/audits for these cases to ensure that preflight etc. works standalone
revert all this and just fall back to downloading the cask source from GitHub in these cases

I pretty strongly thing 2. is the best call here.

For example, the JSON expands appdir to the default /Applications and interpolates this wherever it's used.

Is this just in preflight or everywhere? Not a blocker for making this default, I think, but we will need to note this limitation. Feels like either we deprecate these sort of options or need to move away from interpolation in their implementation.

This does make me wonder, though, what other similar issues I'm forgetting about

We'll figure some out before we make this default and some after. It's a big change, there will be corner cases!

introduce cops/audits for these cases to ensure that preflight etc. works standalone
revert all this and just fall back to downloading the cask source from GitHub in these cases

I think 1 would be pretty difficult to do. For 2, are you suggesting that we always use the cask source or only for casks with *flight blocks?
Part of me thinks that if we're going to use the source in some cases, why not do it in all cases? It would also remove the appdir issue.
Note: there are currently 149 casks in homebrew/cask and 40 in other cask taps that use *flight blocks.

Is this just in preflight or everywhere? Not a blocker for making this default, I think, but we will need to note this limitation. Feels like either we deprecate these sort of options or need to move away from interpolation in their implementation.

This is an everywhere issue. For example, sdm:
cask "sdm" do
  # ...

  uninstall delete: "#{appdir}/SDM.app/Contents/Resources/sdm-socket"

  # ...
end

The JSON API looks like this:
{
  "artifacts": [
    {
      "uninstall": [
        {
          "delete": "/Applications/SDM.app/Contents/Resources/sdm-socket"
        }
      ]
    }
  ]
}

I'm in favor of just using the cask source for everything if we're not sure we've caught all of the edge cases.
If we're sure we know about all of the edge cases, we could just tag those casks, include the tag in the JSON returned from the API and download the source for them. It seems like between the *flight blocks and the appdir variable there are around 258 casks in homebrew-cask that fit those criteria. That's around 6% of the total.
/u/l/H/L/T/h/homebrew-cask (master|✔) $ git grep -l -E '#\{appdir\}|preflight|postflight' | wc -l
     258

I think 1 would be pretty difficult to do. For 2, are you suggesting that we always use the cask source or only for casks with *flight blocks?

Only for *flight blocks are other cases where we need them.

Part of me thinks that if we're going to use the source in some cases, why not do it in all cases? It would also remove the appdir issue.
Note: there are currently 149 casks in homebrew/cask and 40 in other cask taps that use *flight blocks.

There's >4000 casks in homebrew/cask alone. I think it's worth optimising for the most common case by not having to hit the network for that and fall back to the source only when we need it.

This is an everywhere issue. For example, sdm:

Ok. I think this would be fine to punt on for V1 of this being default and we just fail if people specify --appdir without HOMEBREW_NO_INSTALL_FROM_API set.
Later we'll have to change the JSON generation to output "delete": "${APPDIR}/Contents/Resources/sdm-socket" or similar and then replace it ourselves when we consume it.

Okay, this now loads casks using the JSON API when there are no *flight blocks, and from the cask source if there are.


Support REVISION migration into string/number union type

Do in tandem with #136
Scenarios:
Was string, now string/number
Do nothing - number will be stringly typed.
Was number, now number
Convert field from numeric to string.
Obviously this should interoperate correctly with nullability too

Migrated to https://github.com/snowplow/iglu/issues/243


25c Automation: Security

Before we close this section and move on to releasing, a short chapter on security.
First, let's extend test, our little test script to run tests, to also prompt the user to build and publish: [93198867ac8424d56c06a64587e940330fbc5540]

Build automation
Now the result of running test looks like this:
$ ./test
Success: no issues found in 8 source files
.........
----------------------------------------------------------------------
Ran 9 tests in 0.080s

OK
Build package (y/N)? y
venv/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
Building pseudo-9608 (0.3.4)
  - Building sdist
  - Built pseudo-9608-0.3.4.tar.gz
  - Building wheel
  - Built pseudo_9608-0.3.4-py3-none-any.whl
Publish package (y/N)? y
venv/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(

No suitable keyring backends were found
Using a plaintext file to store and retrieve credentials
Username: <username>
Password: <...>

It might be fine to keep keying in the username and password, especially if this is happening in a public setting and it is not safe to be storing credentials. But this chapter is about automation, and if we were in a more private setting (e.g. on a laptop or computer we control) we might wish to automate this section.

Storing credentials locally
The poetry documentation on repositories suggests using poetry config to configure credentials:

If you want to store your credentials for a specific repository, you can do so easily:
$ poetry config http-basic.foo username password

This is fine if we are writing the code on our own laptop; the credentials will be stored on the laptop, and used each time we run poetry publish.

Storing credentials in environment variables
I'm working on pseudo-9608 from a cloud environment (specifically Replit), which means it isn't safe to save credentials to a file in the project; if it ever becomes public, those files might be visible to others. Even if I delete those files, they may remain in the repository history, unless I erase that repository permanently!
The poetry documentation proposes an alternative:

Alternatively, you can use environment variables to provide the credentials:
$ export POETRY_PYPI_TOKEN_PYPI=my-token

Replit provides a way to configure environment variables without saving them to disk, so I'll use that instead.
And now poetry stops prompting me for a username and password for publishing:
$ ./test
Success: no issues found in 8 source files
.........
----------------------------------------------------------------------
Ran 9 tests in 0.020s

OK
Build package (y/N)? y
venv/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
Building pseudo-9608 (0.3.5)
  - Building sdist
  - Built pseudo-9608-0.3.5.tar.gz
  - Building wheel
  - Built pseudo_9608-0.3.5-py3-none-any.whl
Publish package (y/N)? y
venv/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(

No suitable keyring backends were found
Using a plaintext file to store and retrieve credentials
Publishing pseudo-9608 (0.3.5) to PyPI
 - Uploading pseudo-9608-0.3.5.tar.gz 100%
 - Uploading pseudo_9608-0.3.5-py3-none-any.whl 100%


Allow appending comments below documents in phriction like other applications

Any idea?

We're more likely to build inline commenting, see https://secure.phabricator.com/T1894


[Bug] Sometimes banner gets removed from the editor.

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Monaco Editor Playground Code
No response
Actual Behavior
We are using VueJs and tried to integrate the Monaco editor. When we set the banner to the original editor and modified editor, in some cases it gets removed from the modified editor.
I am attaching the screenshots and code snippets of the same.

(While rendering the editor, the banner is set)
After mounting the editor, the banner disappears from the editor and is removed from the DOM.

Expected Behavior
The banner should be preserved always in both the editor. (original and modified)
Additional Context

This is a code snippet, we have written in Vue to set the banner for both the editors.

Does this reproduce without Vue?


chore: add github actions for ci

Work ID W-11677914
Move CI to GitHub Actions and  off CircleCI.

@ryandagg I added in additional runners and removed the dep caching.


Immense appreciation and respect - plus a few technicalities

Hello dearest Craig Raw, you MAGNIFICENT Soul,
I am called to reach out to you to express my deepest, utmost, sincerest appreciation, honor and respect for the SERVICE TO HUMANITY that you have provided and continue to provide so selflessly, with or without support (we should ALL be supporting you / your team), for many years, in the development and continual support you provide in Sparrow Wallet.
You are undoubtedly, a unique and magnificent Soul on this planet and I so greatly admire this part of your Divine Purpose in contributing this incredible, consistently effective, beautiful, trustworthy software. I see men like you in nearly the same regard as Satoshi Nakamoto himself - which is extremely highly regarded.
I would love to share with you a donation today made on BTCPay on your website for about 55,000 sats, around $50 USD. I had to make it on the chain, despite trying three times to send it over lightning using my phoenix wallet. Each LN attempt failed. The error in phoenix says: "An error occurred on a node in the payment route. The payment may succeed if you try again." I should have tried with a different LN wallet but didn't think to, so I'm not sure what is causing the issue. I'll try again next time I donate :)
I have been using your software for many years as a tool for managing this incredibly important resource we all have access to on Earth now, called Bitcoin. I am so humbled by your dedication. Your work ethic. Your Love. To support this budding ecosystem that has immense potential to bring humanity into a completely new state of existence, one of freedom, abundance, and much of what we all deserve is Divine HUmans.
Another issue is just being able to contact you/your team. I was unable to join the Telegram group. Telegram gives me an error: "Sorry, this group is not accessible." Just thought I'd let you know. I also couldn't send you a message on Twitter because your account requires messengers to be "Verified", which I am not.
I hope you are having a brilliant, peaceful November, wherever you are in the world, and enjoying these face-melting actions in the bitcoin marketplace as well.
With greatest appreciation and respect,
Yuri

Thank you for the kind words Yuri.
Managing inbound liquidity is an ongoing task :) It should be better now - I appreciate your donation!

Telegram gives me an error: "Sorry, this group is not accessible."

Let me know your Telegram username (either here or on Telegram DM) and I'll take a look.


Estimote catch instance uuid

I am using estimote proximity beacon and i am trying to obtain the advertising UUID and i am having some difficulty.
So write now i have this code:
print("add : advertisementData : ", peripheral.advertisementData.advertisementData)

print("add : serviceUUIDs : ", peripheral.advertisementData.serviceUUIDs?[0].description ?? "zero")

that the result is:
add : just UUID :  AF471412-5AC5-47AA-AFEE-6B9E5495190F
add : advertisementData :  ["kCBAdvDataIsConnectable": 0, "kCBAdvDataServiceData": {
    FEAA = <00e1edd1 ebeac04e 5defa017 24267fd3 25bf0000>;
}, "kCBAdvDataServiceUUIDs": <__NSArrayM 0x170057a00>(
FEAA
)
]

add : serviceUUIDs :  FEAA

where the "edd1 ebeac04e 5defa017" is namespace and "24267fd3 25bf" is the instance.
how can i catch the instance ( "24267fd3 25bf") in code?

Hello @tnmendes
Sorry for the delay. If I understand you correctly you want to retrieve service data from advertisement.
You should retrieve whole data by using CBAdvertisementDataServiceDataKey
This looks something like:
let data = advertisementData[CBAdvertisementDataServiceDataKey][CBUUID(string: "FEAA")]

Data is collection beginning from Swift 3 so you should be able to easily retrieve wanted bytes from it.
Please write in case of any further questions.
Regards,
Kacper

Closing it for now - please feel free to reopen in case of any further concerns.
Regards,
Kacper


11 dependency injection

https://rostyslavhavuka.github.io/frontend-course-2020/homeworks/rostyslav.havuka_RostyslavHavuka/11-dependency-injection/vehicle/dist/vehicle/

Closed because another request is created


How Javascript Works Behind the Scene

It would be helpful to include a separate chapter that covers How Javascript works behind the scene.
adding a chapter on the inner workings of JavaScript equips developers with a deeper understanding of the language but also enhances their ability to write efficient, performant, and reliable code, making them more proficient and versatile in their roles.

It would be helpful to include a separate chapter that covers How Javascript works behind the scene.
adding a chapter on the inner workings of JavaScript equips developers with a deeper understanding of the language but also enhances their ability to write efficient, performant, and reliable code, making them more proficient and versatile in their roles.

Kindly assign this to me. Thank you.

@sumn2u you are welcome.

@sumn2u, Thank you so much for assigning the issue to me! I'm excited to contribute. Could you please provide some guidance on how to proceed with this? Are there any specific steps, guidelines, or preferences you have in mind for the content of the chapter? I want to make sure I align with your expectations.
Additionally, if there's a particular approach or outline you have in mind, I'd love to discuss it further. I'm open to collaboration and would appreciate any feedback you may have throughout the process.
Looking forward to your guidance.

Could you please provide some guidance on how to proceed with this? Are there any specific steps, guidelines, or preferences you have in mind for the content of the chapter? I want to make sure I align with your expectations.

Certainly, we can include a dedicated chapter that delves into the inner workings of JavaScript. This can cover important topics such as its engine, execution context, call stack, memory heap, runtime environment, and event loop. We have already covered other related topics such as its single-threaded, asynchronous nature, Promises, async/await, and debugging tools which we can reference.

Additionally, if there's a particular approach or outline you have in mind, I'd love to discuss it further. I'm open to collaboration and would appreciate any feedback you may have throughout the process.

The project's README.md defines the typographic conventions, project structure, and contributing guidelines used, you can follow it.

Hi @sumn2u . I added this chapter and submitted a pull request, please check :)


Use apiclient.New instead of mgr.GetClient

When a storageclassclaim CR is created, a Reconcile is triggered. We are using controller runtime client does GET operation which reads from the runtime cache. When a blockpool or subvolumegroup is created, a new reconcile request will be in the queue until the existing Reconcile completes. Once the existing Reconcile completes, we will get Reconcile request for the resource in the queue and try to get the storageclassclaim object here. We have a chance to get the object from the runtime cache instead of fetching it from the apiserver. Because of it, we get stale resources created for subvolumegroup and blockpool.
With this fix, use apiclient.New client for all operations in the storageclassclaim controller.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

/assign @nb-ohad

/lgtm


fix usages of mut interface methods

draft! don't merge yet , preparing for https://github.com/vlang/v/pull/11963

@nedpals is it ok to merge?

sure thing. :slight_smile:

thank you!


Make session loading lazy

Ideally we would not load sessions from stores until the moment we actually want to use them.
Currently we pay an overhead price of loading the session from the backing store on each request where this middleware is installed. This can be mitigated with caching techniques, for example by using Moka. That said, it's overhead that could be avoided altogether.
Consider that many applications will install this middleware at some lower point in their route graph where only a subset of those routes will use the session--this is an example of overhead we should strive to eliminate altogether.
To facilitate this, I'm working on strategy for loading sessions on demand. The current approach involves making the session generic over a store. This would allow us to defer the store load until we interact with the session in some way, say by explicitly loading or saving it.
These methods will be abstracted away such that as a user the interface remains the same, with the exception that the session takes a generic parameter. Internally, the session will manage a kind of cache which is hydrated lazily and sent back to the store when modifications have happened.
This should also simplify the design measurably and perhaps even enable other optimizations, such as a custom future type (i.e. eliminating the need for a boxed future).

cc @bikeshedder, this might be of interest to you. 🙂


Make sure that the native getAttribute method is invoked

We wrap setAttribute of the custom elements of our application. This produces unwanted side effects when running the code of the polyfill. This patch makes sure that the native setAttribute is called.

I'm thinking if there are cases where an element involved doesn't actually use the getAttribute inherited from HTMLElement.prototype ... which is why node.getAttribute at runtime is crucial.
IE8, for instance, works only thanks to that runtime. It looks like your code has problems, and you'd like to fix those here.
Can I please know more about the problematic case? Also a test case that shows the problem would be better.
Thanks

P.S. sorry I haven't seen this before for some reason.

We redefine the setAttribute/getAtrribute in A-Frame to add extra functionality:
https://github.com/aframevr/aframe/blob/master/src/core/a-entity.js#L540
We want to make sure that the polyfill invokes the native one instead of our custom version defined on the element.

digging a bit more, beside IE8 there are browsers that need an overwrite of the setAttribute at runtime.
https://github.com/WebReflection/document-register-element/blob/master/src/document-register-element.js#L463-L467
which is why I use node.setAttribute to be sure I use the eventually patched one.
I might try to change one bit and see how that goes but I need you to test this repo file before I publish such change on npm (it might take a while due necessary tests I need to do)

please check latest from this repo and tell me if it works.
There are still possible gotchas with setAttribute and removeAttribute and I'm thinking how to better patch these at runtime.
Patching the entirity of the HTMLElement prototype is too obtrusive and a suicide for performance reason (even non custom elements would need to pass through custom elements related steps)

re-asking about current repo version: does this fix the problem?
If the answer is yes, I can publish this and bump its version.


make-based: Update config files to RELEASE-0.13.0

How did you update them? Should they not be gitignored and autogenerated on setup or build?

The scripts in the make-based directory will copy the already generated .config files to the apps directories in order to be able to build without running make menuconfig or any kind of configuration step.
The updates were necessary since the last release introduces some new features and the build step was now waiting for user input on those new options before being able to start the actual building.

Yes, I'm saying rather than doing this manually on every new update, perhaps provide a Kraftfile or kraft.yaml that can generate these .config files
because you have hardcoded user directories in them, like /home/stefan/projects/.... which for me might be /root/projects/...

Yes, I'm saying rather than doing this manually on every new update, perhaps provide a Kraftfile or kraft.yaml that can generate these .config files because you have hardcoded user directories in them, like /home/stefan/projects/.... which for me might be /root/projects/...

We have the kraft.config versions here, but usually we do not want to be dependent on kraft or any other external tool, we want to do everything with the bare minimum available.
The directories are updated automatically when running the actual build, so they are not a problem.


[wip] Update 0.34.0

fix #276

Update from 0.34.0rc1 to 0.34.0
Link to release in mailing list<EMAIL_ADDRESS>Common ancestor between versions: sha-1 a04fad858644466219b7ea399aead110cb8ea655
(not from mailing list, but from git merge-base 0.34.0rc1 0.34.0)
Last split commit: sha-1 a04fad858644466219b7ea399aead110cb8ea655

Performed checks

[x] I updated Makefile with the new SUPERSET_VERSION
[x] I updated the CHANGELOG file
Migrations:

[ ] I merged migrations
[x] No migration merge was needed

I checked the config files (and ported if needed):

superset/contib/docker

[ ] changes merged
[x] nothing to be merged

superset/superset/config.py

[ ] changes merged
[x] nothing to be merged

superset/.travis.yml

[ ] changes merged
[x] nothing to be merged

[x] Tested the upgrade building & checking it with src-d/sourced-ce

notes
0.34.0rc1, its common ancestor with 0.34.0, and the split commit are equals because 0.34.0 release branch was created from 0.34.0rc1. Also, there is no revert commit to merge because there is no changes in 0.34.0rc1 which are not in 0.34.0.

I think we decided to close this one and update to 0.34.1 instead as soon as it's released.
(the vote process has started already<EMAIL_ADDRESS>)

Yes, forgot to close it. Done


[flutter_tools] The tool should prefer the JDK vendored with Android Studio

As seen in issue #56572, if a version of JDK greater than 8 is set as JAVA_HOME, the tool will fail to detect android licenses. Since Android Studio vendors JDK 8, we should prefer that version.

Hi @AmirGamilDev
I'm not sure that this is exactly the case;
keeping in mind that android set up goes through android studio inheriting openjdk8,
it is possible to use a different jdk, please see this SO answer.
Recommending one version is different from not supporting another one.
It is true that in some users have experienced issue with android licence
and, since isn't a procedure advised by the official docs,
imho those difficulties shouldn't fall under flutter repository scope;
nonetheless the same issue you shared offers a solution for the situation you described
Does this solve the issue for you?
Thank you

Hi @iapicca
While it's true that Android Studio itself comes bundled with Open JDK 8, a developer may already (or in the future) install a more recent version of the JDK.  I don't believe it's correct to assume that a developer will be using JDK 8.
In fact, this is what happened to me.  I did have JDK 8 running on my machine.  Then I upgraded to JDK 14 to get around another entirely separate issue with another development environment.  Later, running flutter doctor gave the error message.  After much online searching, trial and error, trying solutions around unchecking hide obsolete packages, uninstalling and re-installing Android SDK tools etc. etc., I was still no further along hours later.  Eventually, I saw mention of JDK versions and because I had recently upgraded Java, I thought to try this.
If part of the Flutter philosophy is to reduce barrier to entry then I believe highlighting categorically that a developer may have issues if they don't have JDK 8 is extremely important.  To be honest, even if the Flutter philosophy is not to reduce barrier to entry, out of respect for developers' time and sanity, I believe it's reasonable to expect that flutter doctor would flag this as an issue.  I don't believe developers should have to search online for hours to eventually find out that they either:
a) Have to use JDK 8 when using flutter
or
b) Have to download deprecated Java libraries and add them to the classpath in order to be able to use a more recent version of the JDK
One developer doing this is bad enough.  Countless developers doing this is worse.  And it's clear to see that a number of developers have come up against this issue.  If it's a developer's first experience of Flutter and they can't get it working after an hour or so of trying, they may just give up.  Is this what the Flutter team wants?

Recommending one version is different from not supporting another one.

I must respectfully disagree with this.  Clearly, flutter doctor does not work if JDK is > 8 out of the box.  This means it's not supported.  But there is no mention of this anywhere in the docs or in flutter doctor's output.
While it's true that the Android tools SDK could probably fix this since flutter is dependant on it, I don't see the harm in flutter doctor doing the right thing and at least warning a developer that they may run into issues since they are using JDK > 8.
What do you think?

Can we not update the tool to prefer the version vendored with Android Studio (which is an android development dependency) @jonahwilliams?

We should if it isn't already the case, I'm not quite sure though - that code is a bit of a mess :(

I'm going to update the action point on this issue to prefer version 8 vendored with android studio.

@christopherfujino
I'm not sure if preferring the JDK vendored with Android Studio is the way to go?  Perhaps just checking if the JDK version is greater than 8?  Or at least doesn't include the necessary classes to perform the Android licensing check.

I am also not sure that preferring the JDK vendored with Android Studio is the way to go. Developers might prefer to use the same JDK on command line and Android Studio.
For example, the integration_test package mentions to run gradle on the command line for Android device testing. To have command line gradle execution and Android studio gradle execution run on the same JDK, I'd have to set my JAVA_HOME to Android Studio's internal JDK which doesn't seem like good practice.
Rather, I'd like to go the opposite way and make flutter use my standard JDK. There are a few tickets on Stackoverflow (e.g. #1, #2) that indicate others have tried to go the same way.

Also, here is an issue showing exactly what I meant: a case where .gradlew build worked (because it used the system JDK) while flutter run didnt (because it used the Android Studio JDK).

I think this issue was addressed, and I hate it. flutter -v doctor will always show the Java in the embedded Android Studio resources, but in my case I have issues with the latest Java 17 that ships with Jellyfish. It can't launch.
I installed a newer Java 17 with sdkman-cli and now the build works in Android Studio, but Flutter will not respect my decision I made in Android Studio and it will also not respect JAVA_HOME.
I'm on MacOS, btw.


Remove (now-redundant) Dual Wield skill.

Remove reference to the Dual Wielding skill, which is no longer necessary for backwards compatibility following the 7th Plague Update.

@librarianmage not a particularly important update since all it's really doing is suppressing an error from being written to Player.log, so feel free to bundle it together with other changes at a later date.


Fix bug in unique task reference name validation

We hit an issue where I was expecting a validation error on workflow creation, but didnt get one. We had some tasks lower down some decision trees/forks that had the same taskReferenceName...... which shouldnt be allowed, but was.
The problem was that the Validation was just doing getTasks(), but really you need to be doing collectTasks().
Verified we get the correct validation error now.

Pull Request Test Coverage Report for Build 4675

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.042%

Totals

Change from base Build 4670:
0.0%

Covered Lines:
12969

Relevant Lines:
18516

💛  - Coveralls


Added Facade class for SSEData; added $event argument to ->update();

Hi @jiggo, I did not maintain this package for a long time so I am looking at your commit right now, I think I'll start maintaining it again. I'll definitely check it out and let you know about it's status. Thanks for your contribution :)


EXP requirements for Focal Manipulator unclear

Whenever I try to bind a spell to a focus, it always says that the EXP requirement for it is 1 level. It does not begin the process if I only have 1 EXP level, though it will if I have 10 levels and will drain me to level 9. Is there something I'm missing as to the exact amount of EXP I need?

Issue is reproduced with 1.12.2-6.1.BETA26


There is no way of downloading KSStudio Utility

Hello,
I am trying to install the KSStudio utility but on its intallation page the instructions are not correct. There is no "Tools for driver developers" element to choose from among the so described list of components. There isn't even a list of components when installing the WDK.
I am currently downloading the WDK from here: https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
Please update your docs asap.
Regards,
Christopher
[Enter feedback here]

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

ID: 0e3f34d2-a2bc-be65-21ff-a8febf1f1ace
Version Independent ID: f31caf08-8aa4-ac94-5fba-91845ce0e1db
Content: KsStudio Utility - Windows drivers
Content Source: windows-driver-docs-pr/audio/ksstudio-utility.md
Product: windows-hardware
Technology: audio
GitHub Login: @DOMARS
Microsoft Alias: domars

I found the location of the executable, it is in C:\Program Files (x86)\Windows Kits\10\Tools\x64 for the 64 bits version.
What happened is that the WDK installer installed KSUtility.exe regardless, so I basically had it installed the whole time.
Which is a good thing, I can work now, but the docs were not very clear on this aspect.

@christopherlacapra - Thanks for this useful documentation input. As you determined, the install directions were out of date. I updated the directions to reflect how the WDK install behaves currently. Thanks for pointing out this docs error, so that we can improve the docs for the next person who is working with the KSStudio utility.


Add benchmarks for simple topic subscription publishing scenarios

Superseeded by https://github.com/CihatAltiparmak/moveit_middleware_benchmark/pull/30
Closing


musikcube_win32_0.64.1 VCRRuntime140.dll not found.

Release : musikcube_win32_0.64.1
On a fresh new Windows 10
Cannot run the musikcube. VCRRuntime140.dll not found.

I got the same issue with musikcube_win32_0.64.0.

Installing v_redist.x86 did fix it

@benoit-pereira-da-silva thank you for bringing this to my attention. While your fix works, it is not my intention to require installation of the Visual C++ redist library. I'll try to remove this dependency in the next release of musikcube.
Re-opening this ticket for tracking purposes.

https://github.com/clangen/musikcube-bin/commit/b825e6066d88535aad8c27d9131632f88e90510c
https://github.com/clangen/musikcube-bin/commit/31cd7109785075fc18ddb6319440c5cbb305e702
https://github.com/clangen/musikcube/commit/34e383bb2cad38f195da8bac93fdfd372798426f
https://github.com/clangen/musikcube/commit/9bbd1f01405578d8fa73705aa22a88c7219f0856


Fix description of average growth rate statistic

The formula suggested growth over the entire week but description mentioned it as daily average growth rate

Seems okay to me. If we change the description to this, then dividing by 7 doesn't make sense

@shuklaayush
Dividing the weekly growth rate by 7 does not give daily average growth rate. Either the description or the formula should be fixed.
E.g. growth rate of 50% a week would mean 100 cases rose to 150.
A growth rate of (50/7)% i.e. 7.14% daily would mean cases rose to 100* (1.0714)^7 i.e. 162.
In the millions, these stats look misleading

@varunvora Ah, you're right. It's the simple vs compound interest thing. Let me fix it

Fixed via 60f2ac064c7f5cd7ce113697b0d6ab92877a5f1e


In local after running python run_first.py resumes and  job description are not being processed into json..

have resumes in data folder and run run_first.py
python run_first.py
below are logs for the above command
2023-10-03 18:34:05,089 (run_first.py:31) - INFO: Started to read from Data/Resumes
2023-10-03 18:34:05,089 (run_first.py:28) - INFO: Deleted old files from Data/Processed/Resumes
2023-10-03 18:34:05,089 (run_first.py:38) - INFO: Reading from Data/Resumes is now complete.
2023-10-03 18:34:05,089 (run_first.py:48) - INFO: Started parsing the resumes.
2023-10-03 18:34:09,600 (core.py:64) - INFO: loaded 'en_core_web_md' spaCy language pipeline
^[[15~^[[15~^[[15~^[[15~An error occurred: module 'networkx' has no attribute 'pagerank_scipy'
2023-10-03 18:36:03,071 (run_first.py:52) - INFO: Parsing of the resumes is now complete.
2023-10-03 18:36:03,072 (run_first.py:54) - INFO: Started to read from Data/JobDescription
2023-10-03 18:36:03,072 (run_first.py:28) - INFO: Deleted old files from Data/Processed/JobDescription
2023-10-03 18:36:03,072 (run_first.py:61) - INFO: Reading from Data/JobDescription is now complete.
2023-10-03 18:36:03,072 (run_first.py:72) - INFO: Started parsing the Job Descriptions.
An error occurred: module 'networkx' has no attribute 'pagerank_scipy'
2023-10-03 18:36:03,763 (run_first.py:76) - INFO: Parsing of the Job Descriptions is now complete.
2023-10-03 18:36:03,763 (run_first.py:77) - INFO: Success now run `streamlit run streamlit_second.py`

Hello @karthikeyakumar, please check if this is related to: https://github.com/srbhr/Resume-Matcher/issues/121

Please close the issue if the problem is resolved.
You can refer to #121

BTW we can try the en_core_web_lg and trf as well now.


Complete continuations and browsing for 0.23.0

https://github.com/sigma67/ytmusicapi/compare/0.22.0...0.23.0
Resolves #15

Merged even with failing tests. Will reevaluate tests after getting to 0.^25.0


Error is produced whenever k2s is started

Describe the bug
Whenever start of k2s is performed, the following error is logged in the console.

To Reproduce
Steps to reproduce the behavior:

start K2s using command k2s start -o

Expected behavior
No errors are produced during k2s start

The issues is not comming up anymore, will close it.


Improve handover descriptions

Changes:

Describe handover parameter negotiation properly
Clarify what should happen in case handover=false has been negotiated.
Minor description improvements in handover-related sections

Resolves #120 once merged. Will update the ORTC task once the changes have been approved by @dbrgn.

@dbrgn Be aware that the requirements have shifted slightly as the text now clearly states that a handover MUST be requested before offer/answer have been created. I don't know if you need to do any adjustments in the task implementations.

Mhh, looks like I never updated the ORTC task.


[Mac OS] No output from CPLEX after running optimize!(mymodel)

The following simple example has been tested but no output is returned.
julia> using JuMP, CPLEX
julia> mymodel = Model(with_optimizer(CPLEX.Optimizer))
julia> @variable(mymodel, 0 <= x <=2)
julia> @objective(mymodel, Max, x)
julia> optimize!(mymodel)

I am sure the model is been properly solved because I can get solution by calling JuMP.value.(x), or objective_value(mymodel).
I tried the same thing on my windows 10 machine and it returned the solving statement correctly.
I tried using another solver GUROBI, optimize(mymodel, with_optimizer(Gurobi.Optimizer)) and it did returned the solving statement from GUROBI, so I guess there might be something wrong with CPLEX.jl on Mac OS (macOS High Sierra Version 10.13.6 in my case).
I also tried Pkg.update() and rebuilt CPLEX by Pkg.build(CPLEX) but the issue (no output) still exists.

I experience the same (after updating to JuMP 0.19) which required me to  to change the command of creating a model to
model = Model(with_optimizer(CPLEX.Optimizer, CPX_PARAM_MIPDISPLAY = 2 )).
So, even if I force a screen output like that nothing is printed. Notice that I use Ubuntu 18.04, Julia 1.1, JuMP 0.19, MathOptInterface v0.8.2, CPLEX v0.4.3 to start CPLEX 12.8.

I experience the same (after updating to JuMP 0.19) which required me to to change the command of creating a model to
model = Model(with_optimizer(CPLEX.Optimizer, CPX_PARAM_MIPDISPLAY = 2 )).
So, even if I force a screen output like that nothing is printed. Notice that I use Ubuntu 18.04, Julia 1.1, JuMP 0.19, MathOptInterface v0.8.2, CPLEX v0.4.3 to start CPLEX 12.8.

Yes, this issue happened exactly after I updated JuMP to version 0.19.

What happens if you set CPX_PARAM_SCRIND=1?
It looks like we used to turn this on by default:
https://github.com/JuliaOpt/CPLEX.jl/blob/13d849b4ae3e34b276b4160f0cffe4954faac6cb/src/CplexSolverInterface.jl#L21
Not any more:
https://github.com/JuliaOpt/CPLEX.jl/blob/13d849b4ae3e34b276b4160f0cffe4954faac6cb/src/MOI_wrapper.jl#L44-L52

There is a bug: even if we pass in an existing environment, we create a new one...
https://github.com/JuliaOpt/CPLEX.jl/blob/a09be2e0fabc38dfaec75f67b9039a70d2b0c1e7/src/MOIWrapper.jl#L39-L42

What happens if you set CPX_PARAM_SCRIND=1?

Nothing happens. It is the same behaviour as before.

See #218

@odow Thanks very much for the help! I assume that you have figured out the problem so you could get an output form CPLEX in your local machine. Is that right? If so, I would close this issue and wait for your pull request #218 .


Half sem courses shows slot clashes

Course slot clashing warning don't differentiate between half sem and full sem courses. This is a problem while making freshie timetables because they have a lot of half sem courses. A solution to this could be to relax the slot clash check if there are two half sem courses in the same slot.

By relaxing the slot clashes, both courses have to appear on same place in the timetable. Have you planned any UI/layout to show such courses? @AdithyaKrishnaK


fallabck to blob type

Current dependencies on/for this PR:

main

PR #527   👈

This stack of pull requests is managed by Graphite.


GTFS-Vehicles (core)

Core version of the full GTFS-Vehicles proposal.

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

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

This should probably be moved to https://github.com/google/transit ?
cc: @scmcca


fix: update gpu driver image to support h100s

What type of PR is this?
/kind bug
What this PR does / why we need it:
Updating gpu driver image with fix for h100 fabric manager. PR in aks-gpu: https://github.com/Azure/aks-gpu/pull/23
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

assuming we don't need this anymore, feel free to reopen if I'm wrong


Imkc state machine policy

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Thanks for submitting a pull request 🚀 @rctatman will take a look at it as soon as possible ✨


Disable rules when fixing on save

Fix #89
Add a new config that allows to define rules that will not be automatically fixed when saving.
Set by default with capitalized-comments and no-only-test.
Errors will still be fixed when running the command XO:Fix.
The test currently fails because an issue with deep-assign in XO. When passing the fix as a function, deep-assign replaces it with {}.
Passing the option {fix: () => {...}} through deep-assign results in {fix: {}}.
This is fixed by 4f4de13, but this commit is not released yet. As soon a new version of XO is released the tests will work.

This is fixed by 4f4de13, but this commit is not released yet. As soon a new version of XO is released the tests will work.

Can you bump XO here?

Done !

It seems there is an issue on the Travis build: Xlib:  extension "RANDR" missing on display ":99".

It seems there is an issue on the Travis build: Xlib: extension "RANDR" missing on display ":99".

This can safely be ignored.
FYI, the officially recommended CI scripts are located in https://github.com/atom/ci, although nobody has bothered to fix it there because it doesn't actually change anything.
If you were curious, to fix this you need to add +extension RANDR to the Xvfb arguments.

Thanks for the info! Really helpful.
So I have to figure out why apm test fails on Travis but works locally...

Took a look at the build, generally when apm test has no output like that, it means that Atom encountered an error before the specs could start. Usually this is due to encountering syntax it doesn't understand, but it could be anything.
You can probably get this output to show by changing apm test to atom --enable-electron-logging --test spec.js. (I think that's the right syntax for a single file?)

Thanks!
For info I tried to use the official script from https://github.com/atom/ci. apm works but atom doesn't. After installing ~/atom/usr/bin/atom -v doesn't return anything.

Using the official scripts it seems to work. The test had to be put in the spec folder in order to be ran by the scripts.
Running the test from an npm script or directly in Travis doesn't work.

Hmmm, sorry, I just looked in detail at what you are doing here. The reason apm test failed before is that you have no Jasmine 1.3 specs, the only format that Atom understands by default. Atom does support alternative test runners, but I don't think anyone has written one for ava yet.
It seems the current setup works, though it just runs a "spec" of 0 tests within Atom. I'd say just leave it as is though since the script will install Atom for you and should be kept up to date for you with any changes needed.

Thanks for the help :)
The spec is written with Jasmine: https://github.com/xojs/atom-linter-xo/pull/90/files#diff-e1eba628503a5c40e269db41c03ec220
So I guess that spec should run?
There is some ava test files as well but they just test individual modules and they are run in Travis with npm test.

You're right the tests are not running: https://travis-ci.org/xojs/atom-linter-xo/builds/342197372#L1889
I don't know why. I looked at several of Atom Linter project and they all have their Jasmine specs in a spec folder and the CI script run them...

I've always named the file something-spec.js, I don't know how it would behave with just spec.js. Does it work locally?

No, but it seems that naming the file something-spec.js works.

It failed :( https://travis-ci.org/xojs/atom-linter-xo/builds/342209740#L1859
Unfortunately I can't run atom --enable-electron-logging --test spec.js in the CI because the atom bin is not found.

Fascinating, I can't get it to fail locally under any of the environments I have set up. The next step I would take would be to essentially stick the important parts of build-package.sh directly in the build script so I could insert the debugging version instead, or alternatively fork that script, insert it, and switch the build here to use the forked version temporarily.
I can work on that tomorrow if you don't figure it out before hand.

That's a good idea! I'll try that, but it's getting very late for me so it will have to wait until tomorrow as well. Any help is much appreciated!

language: generic in .travis.yml seems to fix the Atom spec.
I guess it's only because by default the generic image happen to come with a Node version compatible with Atom.
If you run with a Node image that specifies version 8 or 9 then you get:
[6797:0216/064237.292221:INFO:CONSOLE(109)] "Error: The module '/home/travis/build/xojs/atom-linter-xo/node_modules/pathwatcher/build/Release/pathwatcher.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 59. This version of Node.js requires
NODE_MODULE_VERSION 53. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or`npm install`).

I imagine the day Travis decide to update their default Node version on their generic image that will happen as well.

Actually, the issue with language: node is that unless you override it Travis automatically "helps" you by running npm install, which happens before the script step. In this case that is building the wrong version of the native modules.
If you want to use that image you just need to skip the install step.

Thanks for the info. So I guess I can use a Node image and if I override the install step to run what I have now it should work.

Looks like that did it!

Yep I noticed as well... It's really weird...

ah my bad, I renamed the test spec.js by mistake

Seems good now, the test are running now https://travis-ci.org/xojs/atom-linter-xo/builds/342474730#L540

Looks like a .DS_Store file snuck in there. 😆

Looks like a .DS_Store file snuck in there. 😆

Oops. It's fixed now.

This looks great. Thanks for helping us out @Arcanemagus :)


[New Port Request] libmodpbase64-dev

Library name:
libmodpbase64-dev
Library description:
collection of high performance c-string transformations
Source repository URL:
https://packages.debian.org/stretch/libmodpbase64-dev
B.R

The package ported as "modp-base64"


ui(#964): refine collections page

close #964
Also add edit this collections button https://github.com/pingcap/ossinsight/issues/964#issuecomment-1326182806

/LGTM
/merge


Unhandled Exception tcpservercomponent.cpp: Line 87

Unhandled exception
UE4Editor_TCPWrapper!<lambda_a8de54fa59a761fe631f44d43119327a>::operator()() [c:\users\robot\desktop\myproject\plugins\tcpwrapper\source\tcpwrapper\private\tcpservercomponent.cpp:87]
UE4Editor_TCPWrapper!SetPromise<TUniqueFunction<void __cdecl(void)> &>() [c:\program files\epic games\ue_4.23\engine\source\runtime\core\public\async\async.h:49]
UE4Editor_TCPWrapper!TAsyncRunnable::Run() [c:\program files\epic games\ue_4.23\engine\source\runtime\core\public\async\async.h:404]
UE4Editor_Core
UE4Editor_Core
kernel32
ntdll

Here is the line in question:
//Did we disconnect? Note that this almost never changed from connected due to engine bug, instead it will be caught when trying to send data 				ESocketConnectionState ConnectionState = Client->Socket->GetConnectionState();
Unfortunately, I have very little context for what action caused this exception. I think it happened either:

During tcp-ue4's built-in PING.
While a client was trying to reconnect to my tcp-ue4 server. (Note: The client program is a Windows executable I wrote in C#, and therefore is not written with tcp-ue4 or even UE4.)

I will do more tests, and I will post again if I can reproduce it.

Hi, I'm facing the same issue on my side. It's very ambiguous what produces the error so quite hard to reproduce

Is there any new progress on this issue?

Likely https://github.com/getnamo/tcp-ue4/blob/master/Source/TCPWrapper/Private/TCPServerComponent.cpp#L86 Client->Socket is nullptr/invalid when queried. This needs a barrier check probably.


LspInstall pyls_ms fails to report missing unzip command

What language server(If the problem is related to a specific language server):

pyls_ms

Operating system/version:
Ubuntu 20.04

How to reproduce the problem from neovim startup
On a system without the unzip command installed, run :LspInstall pyls_ms from nvim.
Actual behaviour
The LspInstall command fails silently, without output. Inspecting the nvim cache directory reveals that a pyls.nupkg file has been placed, but no further processing occurred.
Expected behaviour
The process should have given a clear error that the unzip command is not available. From examining the source, it appears this is already done for a few other requirements, but unzip has been skipped.

I wrote the original config/install, but I think generally the sentiment is that we're moving install actions out of the plugin, but it shouldn't be too hard to fix this (sorry for the oversight). Also microsoft's python language server is deprecated in favor of pyright, so I would be in favor of removing the config altogether.

@dutchgecko Do you want to test #405 for me?


"Builder is not in a fully completed state." when there are multiple objects with conditionals

I managed to boil to down to such an example:
"GameInfo"
{
	One
	{
		Key1 1 [$MOBILE]
	}

	Two
	{
		Key2 2 [$MOBILE]
	}

	Three
	{
		Key3 3 [$MOBILE]
	}
}

Removing one of these works, unsure why it happens yet.
Found in https://github.com/SteamDatabase/GameTracking-Underlords/blob/master/game/dac/gameinfo.gi

Actually adding new KVSerializerOptions {Conditions = new string[] { "MOBILE" } } parses it. So looks like there's an issue with skipping unmatched conditionals.


get points from ScatterPlotListDraggable

System Details
ScottPlot Version: 4.1.64
Operating System: Windows 11
Application Type: WinForms
Question:
If I have a:
var scatter = new ScottPlot.Plottable.ScatterPlotListDraggable();
scatter.AddRange(xs, ys);

How do I get the positions of the points after they have been dragged?

I think the issue is that, the Xs and Ys are set to be protected, so you cannot read out their values in your code:
protected readonly List<T> Xs = new();
protected readonly List<T> Ys = new();

Lets wait for Scott, if he suggest a proper solution, i can make a PR if you want to give option to read out X and Y values of the points.

I'm doing something like this now:

        private void formsPlot1_PlottableDragged(object sender, EventArgs e)
        {
            List<PointF> controlPointsTop = GetControlPoints(dataGridView1);
            List<PointF> controlPointsBottom = GetControlPoints(dataGridView2);

            (double mouseCoordX, double mouseCoordY) = formsPlot1.GetMouseCoordinates();
            richTextBox2.Text = $"Mouse coords ({mouseCoordX:N8}, {mouseCoordY:N8})" + System.Environment.NewLine;
            PointF mouse = new PointF(float.Parse(mouseCoordX.ToString()), float.Parse(mouseCoordY.ToString()));

            float lowestDistanceTop = float.PositiveInfinity;
            int indexLowestDistanceTop = 0;
            float lowestDistanceBottom = float.PositiveInfinity;
            int indexLowestDistanceBottom = 0;

            float lowestDistance = float.PositiveInfinity;
            int indexLowestDistance = 0;
            bool topOrBottom;

            for (int i = 0; i < controlPointsTop.Count; i++)
            {
                float currentDistance = GetDistanceBetweenPoints(mouse, controlPointsTop[i]);
                if (currentDistance < lowestDistanceTop)
                {
                    lowestDistanceTop = currentDistance;
                    indexLowestDistanceTop = i;
                }
            }
            for (int i = 0; i < controlPointsBottom.Count; i++)
            {
                float currentDistance = GetDistanceBetweenPoints(controlPointsBottom[i], mouse);
                if (currentDistance < lowestDistanceBottom)
                {
                    lowestDistanceBottom = currentDistance;
                    indexLowestDistanceBottom = i;
                }
            }

            if (lowestDistanceTop < lowestDistanceBottom)
            {
                lowestDistance = lowestDistanceTop;
                indexLowestDistance = indexLowestDistanceTop;
                topOrBottom = true;
            }
            else
            {
                lowestDistance = lowestDistanceBottom;
                indexLowestDistance = indexLowestDistanceBottom;
                topOrBottom = false;
            }

            richTextBox2.AppendText(lowestDistance.ToString() + System.Environment.NewLine);
            richTextBox2.AppendText(indexLowestDistance.ToString() + System.Environment.NewLine);
            richTextBox2.AppendText(topOrBottom.ToString() + System.Environment.NewLine);

            if (topOrBottom)
            {
                controlPointsTop[indexLowestDistance] = mouse;
                gridViewAddPoints(dataGridView1, controlPointsTop);
            }
            else
            {
                controlPointsBottom[indexLowestDistance] = mouse;
                gridViewAddPoints(dataGridView2, controlPointsBottom);
            }

            calculations();
        }

        private static float GetDistanceBetweenPoints(PointF pointA, PointF pointB)
        {
            double distanceX = pointA.X - pointB.X;
            double distanceY = pointA.Y - pointB.Y;
            float distance = float.Parse((Math.Sqrt(Math.Pow(distanceX, 2) + Math.Pow(distanceY, 2))).ToString());
            return distance;
        }

        private static List<PointF> GetControlPoints(DataGridView gridView)
        {
            List<PointF> controlPointsBottom = new();

            for (int i = 0; i < gridView.Rows.Count - 1; i++)
            {
                // Retrieve the values from the DataGridView
                float x = float.Parse(s: gridView.Rows[i].Cells[0].Value.ToString());
                float y = float.Parse(s: gridView.Rows[i].Cells[1].Value.ToString());
                // Create a PointF object
                PointF point = new(x, y);
                controlPointsBottom.Add(point);
            }

            return controlPointsBottom;
        }

I know, this code is horrible, but it works 😅
And it relies on the control points being stored in a dataGridView.
Would be much cooler if the points could be read directly from the formPlot.

https://github.com/ScottPlot/ScottPlot/pull/2711

Thanks for this idea and the PR! I'm merging now and it'll be in the next release 🚀


contextSensitiveHelpUrl does not work with locales in "About apps"

1. Describe the bug
It seems that property contextSensitiveHelpUrl does not work in all scenarios on the pages. It works correctly in the About this task or page section, but not in About apps on this page section.
2. To Reproduce

create new extension
use these properties in the app.json

"contextSensitiveHelpUrl":  "https://mysite.com/{0}/documentation/",
 "supportedLocales": [ "en-US", "cs-CZ],

create new Page
deploy the project
open new Page and Help
There are two sections  About this task or page and  About apps on this page

3. Expected behavior
When I use link in both section it opens the url https://mysite.com/en-US/documentation/ or https://mysite.com/cs-CZ/documentation/ depends on locales
4. Actual behavior
In the section About this task or page the logic works correctly.
In the section About apps on this page locales are not used and link keep as it is https://mysite.com/{0}/documentation/
5. Versions:
Business Central: 20

This seems like a web client issue. Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Problems copying from Files to Blob.

Which version of the AzCopy was used?
2021/05/27 02:13:02 AzcopyVersion  10.10.0
Which platform are you using? (ex: Windows, Mac, Linux)
2021/05/27 02:13:02 OS-Environment  windows
What command did you run?
azcopy copy "https://<storage-account>.file.core.windows.net/<file-share>/my-filename.txt?<sas-token-with-all-permissions>" "https://<same-storage-account>.blob.core.windows.net/<blob-share>/folder/my-filename.txt"
What problem was encountered?
INFO: Scanning...
INFO: Authenticating to destination using Azure AD

INFO: Failed to create one or more destination container(s). Your transfers may still succeed if the container already exists.
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

Job 5651b09b-a007-ce43-4235-2eb4287ac2ba has started
Log file is located at: C:\Users\my-name\.azcopy\5651b09b-a007-ce43-4235-2eb4287ac2ba.log

0.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,

Job 5651b09b-a007-ce43-4235-2eb4287ac2ba summary
Elapsed Time (Minutes): 0.0334
Number of File Transfers: 1
Number of Folder Property Transfers: 0
Total Number of Transfers: 1
Number of Transfers Completed: 0
Number of Transfers Failed: 1
Number of Transfers Skipped: 0
TotalBytesTransferred: 0
Final Job Status: Failed

In log file:
[lines 17-27]
===== RESPONSE ERROR (ServiceCode=ResourceNotFound) =====
Description=The specified resource does not exist.
RequestId:d8b94b38-801a-00f7-539d-520b02000000
Time:2021-05-27T02:13:03.5506526Z, Details:
   Code: ResourceNotFound
   GET https://<storage-account>.file.core.windows.net/<file-container>/my-filename.txt?restype=**directory**&<FILE-TOKEN>
   User-Agent: [AzCopy/10.10.0 Azure-Storage/0.8.0 (go1.15; Windows_NT)]
   X-Ms-Client-Request-Id: [8c459393-13ce-482d-6bb8-a558c6b79ae3]
   X-Ms-Version: [2019-12-12]
   --------------------------------------------------------------------------------
   RESPONSE Status: 404 The specified resource does not exist.

How can we reproduce the problem in the simplest way?
It's a simple example, just copy a file from one File account to another Blob account.
I have been able to do it, using my computer in the middle.
Have you found a mitigation/solution?
Using my computer in the middle, which I dislike, and I'm getting sidelooks from the security people.

Hi @Diego-MX, please search for the keyword COPYFAILED instead, it should show you the actual failure reason.
The quoted error is benign and didn't cause the failure.


question: Merge ClientFlowEvent::AuthenticateAccepted and ClientFlowEvent::AuthenticateRejected?

Currently, it's possible that we produce non-sensical events, e.g., AuthenticateAccepted that has a negative Status or AuthenticateRejected that has a positive Status.
We could merge them to AuthenticateStatusReceived and let users figure out what happened using the Status.kind.

I'm not 100% convinced, but let's do it.
We have a similar problem with other event types like CommandRejected, but in this case not all status types are allowed.

We could also add something like StatusNo, StatusBad, StatusNoOrBad to imap_flow::types, similar to CommandAuthenticate, and use them where appropriate. Would be very nice for setter methods like ServerFlow::idle_reject. What do you think?

These workarounds are quite easy to implement in imap-flow. Making the changes in imap-types requires more effort  and I'm not sure whether or when you will do it. So IMO let's add more stuff to imap_flow::types.

Fair enough. Proposal: Let's add to imap-flow first and open an issue to reevaluate if we want to merge it into imap-types close to some release.


fix: regex for matching blame dividers is broken

should be "|" no | (or)

Funny!  This worked because it was matching  -----------------, which worked out alright in every case I tested it.  Good catch.

Yes, in it's broken form it matches too much - so it will work in a lot of cases.


OpenMP error on PHP 8.2

System Info
Running on my Mac Mini (M2 chip) macOS Sonoma (14.6.1).
This occurs in PHP 8.2, but PHP 8.3 seems unaffected.
PHP Version
8.2.19
Environment/Platform

[X] Command-line application
[ ] Web application
[ ] Serverless
[ ] Other (please specify)

Description
OMP: Error #15: Initializing libomp.dylib, but found libomp.dylib already initialized.

OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://openmp.llvm.org/

Abort trap: 6

Reproduction
$e = Codewithkyrian\Transformers\Pipelines\pipeline (
    task: Codewithkyrian\Transformers\Pipelines\Task::Embeddings,
    modelName: 'Xenova/all-MiniLM-L6-v2',
);
$e( 'Hello World', normalize: true, pooling: 'mean');

Which version of the package are you running with?

Sorry, I should have said. I'm currently on 0.5.1, but I noticed it when upgrading from 0.4.4 (which seems unaffected) to 0.5.0 Also happens on current main branch.
It's possible there's some problem with the FFI extension in my PHP 8.2 setup. I'll try upgrading to 8.2.22 and see if it persists.
As mentioned, there's no problem under my PHP 8.3 setup, so the issue will go away for me. I thought it was worth reporting anyway.

I had the same problem but with php 8.3.
After some tests I found that disabling imagick extension fixed the problem.

I have tried for a couple of days now to reproduce the problem on my device and I haven't been able to. I have imagick installed and enabled for both PHP 8.2 and 8.3 and I still haven't been able to hit the error.
Is there any more relevant information you could give me to experiment further on my end like how you installed PHP and imagick?

I installed the extension from https://github.com/shivammathur/homebrew-extensions not with pecl

I installed the imagemagick library via Homebrew (7.1.1-38). I compiled the imagick PHP extension (3.7.0) from source (downloaded from PECL). These are all the latest versions.
I'm out of my depth here, but happy to provide any info you need, or try things / recompile things.


Do Not trust verify

Pls,
to avoid using bad source code, how to verify downloaded source code to build is that released?

Pls, to avoid using bad source code, how to verify downloaded source code to build is that released?

Could you please elaborate on what you are trying to achieve? This will help me guide you more effectively.

Sure, i refer to something like that:
https://raspibolt.org/guide/bitcoin/electrum-server.html#build-from-source-code
In second section when about to verify the signature.

I agree, this would be a really nice feature to have :)

some additional reference I found in GitHub to sign a commit https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

some additional reference I found in GitHub to sign a commit:
https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification

All commits need to be signed in order for PR to be merged in the repo. I think what the OP refers to is for the releases to be signed so we don't have to trust GH


Geometric-error based point cloud attenuation and eye dome lighting

This PR adds simple geometric-error-based attenuation and eye dome lighting for point clouds.
This trick only really works with replacement refinement point clouds right now, I'll follow up with some fixes for additive refinement.

@likangning93, thanks for the pull request! Maintainers, we have a signed CLA from @likangning93, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Awww who's a good bot? CHANGES.md updated.

Possible to have a shorter name? :smile:

Can the Sandcastle example use better default parameters (and maybe camera view); currently, you can't really see the point cloud after load.

For defaults, perhaps

decrease SSE
Set attenuation and EDL to true

Maybe this is OK, but I found it strange that decreasing the max SSE - which should increase detail - forces the attenuation to become smaller.

Maybe this is OK, but I found it strange that decreasing the max SSE - which should increase detail - forces the attenuation to become smaller.

Maybe the default max attenuation needs to be higher.

Maybe this is OK, but I found it strange that decreasing the max SSE - which should increase detail - forces the attenuation to become smaller.

In this case maximumAttenuation is the SSE instead of a constant, which was an attempt to reduce the amount of parameter tuning required. It also looks like there isn't any more detail getting called down, either the view is already of a leaf or server issues popped up while you were running the demo.
Maybe we could remove the link between maximumAttenuation and SSE and just add a note to recommend using the SSE as maximumAttenuation when tuning?

Maybe we could remove the link between maximumAttenuation and SSE and just add a note to recommend using the SSE as maximumAttenuation when tuning?

Whatever you and @lilleyse think.

@pjcozzi updated!

Thanks for the updates @likangning93!
@lilleyse please merge when ready.
No need for this to make the 1.41 release, but if it does, it should be merged on Jan 1 as I am starting the 1.41 release very early on Jan 2.


@typed/core link returns 404

The @typed/core link in the README returns 404. Looks like the package was moved?

That is correct. The package is removed. README needs to be updated. Thanks for the heads-up.

I've been lazy and didn't make this simple change for a long time - it's been removed from the main README


Add EasyRobotics

https://github.com/gotmachine/EasyRobotics

Does something for Breaking Ground robotics.
Fixes #10003.

Waiting for confirmation from @gotmachine on whether it's OK for BreakingGround to be a dependency.