x_CostCenter not populated

Where are you getting "x_CostCenter" data? I am unable to find anything in the report.
Within Power BI, I select "Transform data", select the table "CostDetails" and then I scroll over to the far right to find the X_CostCenter column. When I drop down on the column name and select "load more", I am unable to find any Cost Center data.
In the portal, I know I have cost center defined at the subscription level and it's inherited via a policy to resources under each subscription.
Any suggestions?

I had a similar issue where only 20% of my cost centers were being populated. I sent an email to<EMAIL_ADDRESS>since they're the team that handle the exports.

We discovered a bug in the FOCUS transform for x_CostCenter. The fix is ready and should be part of the next release. I'll keep this open to track it and update you here when I hear back on the timeline.

This is fixed on the newly released version 0.3


Need to construct a DocumentWriteOperation

DocumentWriteOperation is a convenient way to represent all the pieces of a document write.  In scenarios like an integration with Spring Batch it's convenient to batch writes in a list.  Let's provide users a way to construct a DocumentWriteOperation so they don't need to use DocumentWriteOperationImpl.

It turns out DocumentWriteSet works fine as-is.  I recommended changing this code:
List<DocumentWriteOperation> newItems = new ArrayList<>();
for (DocumentWriteOperation op : items) {
    String newUri = uriTransformer.transform(op.getUri());
    newItems.add(new DocumentWriteOperationImpl(DocumentWriteOperation.OperationType.DOCUMENT_WRITE,
        newUri, op.getMetadata(), op.getContent()));
}
batchWriter.write(newItems);

to this
DocumentWriteSet newItems = client.newDocumentManager().newWriteSet();
for (DocumentWriteOperation op : items) {
    String newUri = uriTransformer.transform(op.getUri());
    newItems.add(newUri, op.getMetadata(), op.getContent()));
}
batchWriter.write(newItems);


chore: add discussion issue type

Which problem is this PR solving?

Issues like #591 create feature requests where they would prefer to open discussions

Codecov Report

Merging #592 into master will increase coverage by 0.1%.
The diff coverage is n/a.


sap.ui.core.util.MockServer: set up against a JSONModel

Dear UI5-Team,
in my OpenUI5 application I use the JSONModel, so no ODataModel.
In order to do the CRUD operations to the backend you can find statements like
return jQuery.ajax({ url : "https://some.domain.de/path-to/entity"
Then the result is set to the JSONModel:
this.getComponent().getModel().setProperty(sPath, oResult);
I tried to set up the MockServer as describe under
Mock Server Configuration
Do I need a localService/metadata.xml file for a MockServer running with a JSONModel?
There is no "sap.app.dataSources" definition and no "sap.ui5.models."".dataSource" definition in my manifest.json. Is this required for the MockServer?
I wonder whether this MockServer can run with a JSONModel at all.
OpenUI5 version 1.58.4

Hello @born2dev ,
I've created an internal record<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Lidiya


split pane's height wouldn't be changed after close another split pane.

After I closing one of split panes,  another split pane's height can not adjust the new height


Fixes #33

Drop support for older Python versions
Add support for testing with tox
Migrate setup.py to pyproject.toml
Add support to Python 3.12, replacing the deprecated function pkg_resources.resource_stream with importlib.resources.files

I need to spend some time setting up github actions and friends to ease publishing the package. Will likely just reuse what I did for babelfish https://github.com/Diaoul/babelfish

Do you know when you will be able to release a new version with this fix? It would be great if this is fixed before the new subliminal release 😄


Question: How to restore data from directory from another crate.io host.

Hi,
am testing drive Crate.io here, very glad to have such great product to use.
I deployed one crate cluster with 2 nodes in docker container successfully,
and also have 5 GB test data to create a table and query function pretty well.
And then I destroyed the two containers, and the data directories are kept.
Question is:
Could the existing data directories /path/data/0,1 be used to used in the new crate cluster directly?
As I tried to reconfigure one new container with -v path to data pointed to the existing ones, the 5 GB table just could not be seen. If so, how to make it?
Any help would be appreciated. Thank you! : )

Hi, yes - usually the data directories can and will be re-used and CrateDB. Can you check the logs and maybe if the directory was mounted correctly?
Cheers, Claus

Thanks @celaus for you tips very much. Problem solved.
JUST FOR FUTURE REFERENCE.
By checking the mounted directory, I logged into the docker and found this:
/data mount only in default crate.yml
In the manual/doc, it used /data as container data directory, how it seems only functions when you use the default crate.yml, so if any one would like to set a self-defined crate.yml out of the container, may have to redefine the path:"path.data: /data" in crate.yml and then do some mount job :/data to container configuration.


随机种子没有效果

每次出的都是同一张图为啥呀大佬？

I've encountered the same issues as well. Additionally, I've found that making slight changes to the prompt can have the effect of changing the seed, whereas manually changing the seed without altering the prompt does not result in any changes to the final output image.


refactor(enharmonic_note): remove redirecting method on enharmonicIntervalDistance

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
481

Relevant Lines:
481

💛  - Coveralls


Draft: add container_run_and_save rule

Overview
Adds container_run_and_save rule. This rule is meant to be a mediocre "replacement" for the container_run_and_commit rule out of rules_docker.
Why?

Few/no replacements exist for container_run_and_* rules offered by rules_docker
rules_docker is not actively maintained
Updating a base image such as Ubuntu may not be as easy as decompressing debs in the event of widespread dependency requirements (glibc/etc)

Concessions/Caveats

Uses similar exec fallback as oci_tarball

Attempts to find a binary via loader parameter, falls back to $PATH if missing

Must pass a tarfile as a base image to the container_run_and_save rule.

Ideally this would just be passing in a label to an oci_image like other rules

There are probably other/better ways to do this

This works ™
This provides an option for people coming from rules_docker who need to execute commands in their containers
This provides a workaround for a well-known issues in rules_oci which is the lack of this and similar rules matching rules_docker functionality

This probably does less than rules_docker implementation

Something is better than nothing

Other thoughts

If this is something that the maintainers would like to avoid the overhead on maintaining and supporting, I would ask to then consider creating these files as a patch which can then be optionally applied in a WORKSPACE file. This would allow for the feature to exist but obviate the need to support it as a GA feature.
gazelle did it's thing and touched a few more corners of this than I was intending. I can revert these changes if desired.

Usage
oci_image(
    name = "example_ubuntu_base",
    base = "@ubuntu",
    entrypoint = ["/bin/bash", "-c"],
    env = {
        "TZDATA": "Etc/Utc",
        "DEBIAN_FRONTEND": "noninteractive",
    },
)

oci_tarball(
    name = "example_ubuntu_base_tarball",
    image = ":example_ubuntu_base",
    repo_tags = ["example-ubuntu-base:latest"]
)

container_run_and_save(
    name = "update_packages",
    base_tarball = ":example_ubuntu_base_tarball",
    cmd = "apt update; apt upgrade -y"
)

oci_image(
    name = "image",
    base = ":example_ubuntu_base",
    tars = [
        ":update_packages",
    ]
)

oci_tarball(
    name = "tarball",
    image = ":image",
    repo_tags = ["updated-ubuntu-base:latest"]
)

Produces an image which is up to date and compliant with basic security scans:
$ docker run --rm -it  updated-debian-base:latest "sh -c 'apt update; apt upgrade'"
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Hit:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:5 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1370 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2035 kB]
Fetched 3634 kB in 8s (444 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thanks for putting this together,  however our position on this rule is clear here: https://github.com/bazel-contrib/rules_oci?tab=readme-ov-file#comparison-with-rules_docker
It's not likely we will commit this to our public api, especially for use cases such as apt-get install, as rules such as rules_distroless and rules_apko exist.
That said, to make it easier for people coming from rules_docker, we could accept this as an example here that is not exported as public api.

@thesayyn is there any way in which this PR could be tagged/labeled "better" such that it'd catch more eyes? A few hundred browser tabs of searching later, something with the right visibility might save some weary engineers.
I would say further to that point, while rules_distroless and rules_apko are pretty awesome - they don't solve the entirety of the problem. The problem statement is: "I need to provide $engineer with an Ubuntu image that is up-to-date" and I don't know that the industry response of "use Alpine instead" is appropriate.
I'd love to use Alpine/Distroless for all of the things, but some organizations have adopted policies which guide what and how distributions can be used, be it for licensing or other reasons. Other organizations just simply don't have the engineering capacity to say "I know we used to use Ubuntu, but if we want Bazel to keep working - now we have to use Alpine."
Thank you for the quick response on this! Hopefully it prompts useful conversation around real-world usage of these rules and can save some folks some time when searching for a solution.

rules_distroless naming is a bit unfortunate, but it's more than just distroless, it supports any Debian based distribution, it's a partial replacement for apt-get install.
As for building base image, using a non-reproducible Dockerfile to build base image is a bad make things go south really quickly.

I don't know that the industry response of "use Alpine instead" is appropriate.

I agree with you on that, I am simply pointing out that these two alternatives cover i want to install some system packages, whether it's alpine or debian.
Reason that such rule doesn't exist here is that it's the wrong thing to do under Bazel, instead of encouraging it, we should tell people to do right thing.
Our readme mentions this use case here: https://github.com/bazel-contrib/rules_oci?tab=readme-ov-file#install-system-packages

It's not likely we will ever implement a rule like container_run_and_save. Now that we have an example of how to this in genrule using buildx, it's less pressing for us to introduce this as an first-class rule here.
Closing in favor of https://github.com/bazel-contrib/rules_oci/pull/570.


Not found en iOS 11

In android I'm perfect but instead I opened the camera and did not read any type of QR code. to what is due?? I do not see any error in the log, I have given it camera permissions and installed the extension
http://cordobo.com/2269-cordova-plugin-for-nscamerausagedescription-in-ios-10/ç
any ideas?

Please, when creating issues fill the template and provide all the requested information.


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld : Thanks for your contribution! The author, @gregvanl, has been notified to review your proposed change.

Verified the updates.
@changeworld Thanks!


Remove unused local typedefs

Hi, thank you for the work.
remove unused local typedefs to fix the following werror.
/opt/ros/humble/include/lanelet2_core/geometry/impl/LineString.h: In function ‘std::pair<double, lanelet::geometry::internal::ProjectedPointInfo<typename lanelet::traits::PointTraits<PointT>::BasicPoint> > lanelet::geometry::internal::signedDistanceImpl(LineStringT, const PointT&)’:
/opt/ros/humble/include/lanelet2_core/geometry/impl/LineString.h:130:9: error: typedef ‘using BasicPoint = PointT’ locally defined but not used [-Werror=unused-local-typedefs]
  130 |   using BasicPoint = PointT;
      |         ^~~~~~~~~~

related: https://github.com/fzi-forschungszentrum-informatik/Lanelet2/pull/300

@poggenhans I appreciate it if you could release this fix as 1.2.2.


[dashboard, time-series bar chart] scrollbars always visible, regardless of slice dimensions

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
superset 0.18.5, but the issue exists at least since 0.18.2.
Expected results
By defining a slice area large enough to accommodate the entire plot, the scroll bars dissappear.
This worked in superset 0.15.4.
Actual results
Regardness how large the slice dimensions are chosen, there are always scrollbars shown, when a Time-series bar chart is included into a dashboard. The Bottom margin parameter doesn't seem to influence this behavior.

Steps to reproduce
Create a Time-series bar chart slice and add it to a dashboard. Then try to resize it until the scrollbars are gone. This is futile...

Browser? OS?

Dup of #3124, which already a dup...

OS: Windows 7
Browsers:

Vivaldi 1.10.867.38: both scrollbars
Firefox 52.1.1 (32-Bit): both scrollbars
IE 11.0.9600: no vertical scrollbar, but horizontal is never gone, even if slice is expanded over two screens

@xrmx: I am eagerly following the github pulse and employed the search function before submitting the issue. However, it seems that I failed with both attempts. Sorry…

Notice: this issue has been closed because it has been inactive for 279 days. Feel free to comment and request for this issue to be reopened.

@mistercrunch please reopen unless reported to be solved. I cannot evaluate the latest version at the moment, though...

This is still a problem on 0.26.3.


[Feature/NiFiDataflow] Stop dataflow

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
-

License
Apache 2.0

What's in this PR?

Add ability to stop dataflow
Why?

To stop dataflow even with syncMode at once or always.
Checklist

[ ] Implementation tested
[ ] Error handling code meets the guideline
[ ] Logging code meets the guideline
[ ] User guide and development docs updated (if needed)
[ ] Append changelog with changes

Do you think is it a bit of mis-use of labels to use them for some action? Aren't they meant to be purely metadata about the resource?
Do you think a spec configuration makes more sense to take action (or inaction, in this case) on? Perhaps the following:
spec:
   syncMode: always
   stopFlow: true

Then you can express the fact that you want the flow to stop, but you want it to remain in sync. This would be useful for maintenance periods or something like that.

Here's an example in a Deployment. The .spec.pause field:
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#paused


Create Waypoint mission

Hi, Thanks for share end build this library.
I am using this library but is it possible create a waypoint mission and send to my PIXHAWK ?

Hi @guicolares, this library does not contain any higher-level wrapper that can help you with this specific task, but you still can use set of MAVLink commands to do that. More information you could find here. Also you can check how this functionality is implemented in Mission Planner Sources.


Always move in the right direction for PageUp/PageDown

Closes #4213

If it clipped to 0, a page up would have no effect. I was clipping to 1, but I noticed you used 3 below so I switched to that. I added a test.

Let me know if there's anything else you'd like me to tweak.

Looks great. Merged as e59d75a


Use prebuild for binaries

The CI job should call the prebuild script to build+package and then the prebuild-upload script to upload attach the binary to a GitHub release (https://github.com/prebuild/prebuild#uploading). (I have no idea how to tell Azure that)
#10

I guess yarn install on CI should always --build-from-source ?

hmm, weird. re-ran and it passed.

Interesting. I kind of assumed it would just publish the pre-built binaries as part of the npm package but that seems not to be the case. Instead, it downloads it dynamically at install time. Wonder why...

Interesting. I kind of assumed it would just publish the pre-built binaries as part of the npm package but that seems not to be the case. Instead, it downloads it dynamically at install time. Wonder why...

Publishing to S3 or GItHub is the common way to do this, though there are libraries to publish to npm as well: https://github.com/prebuild/prebuildify
Advantage of publishing every prebuilt binary in the npm tarball:

install speed
would also work if user disabled npm scripts

Major Disadvantage:

Size

Yeah makes sense. I'm close to getting things to upload to GitHub via azure pipelines.


Announce Squeezebox players with multiple accounts

Hello,
first of all thank you for this great plugin!
I'm experiencing some issues with the announcement of the Squeezebox players for the second (out of two) Spotify account. The first account sees all players, but the second account sees only the first player in the list. In this case Don't announce Squeezebox players running in Spotify Connect mode in your network. Check this option if you don't want your Spotify Connect enabled Squeezebox player to show up in all Spotify apps in your network. is checked. If I uncheck it, then obviously it works.
I'm using a Spotify Client ID and the second user is added on the User Management page for the inserted key. Both accounts have premium.
Does also someone else have this issue?
I put the log to debug, but I found no data that could help me. Any tips for what to search for?

I don't understand your question: you tell Spotty not to announce the players in your network. Why would you expect them still to be seen?
The one account seeing it is not seeing it on the network, but through Spotify's servers. But the other accounts don't see it, because it's connected to the first account. If one of them is seeing both then this probably is some caching, and would go away after a while?

Somehow I thought that this option shows the player only to connected accounts and not for other accounts, e.g. when friends are in my WiFi.
Now I understood this better thanks. It happened now to me, that the flag for this option Don't accounce Squeezebox players... was set again already two times, always after a LMS update. I'm using the MS4H system.
Have you a hint on how to troubleshoot that? Other settings are preserved from the plugin, so this is very odd.

Sorry, MS4H is Music Server 4 Home which is a bundle to integrate the LMS with Loxone.

I think this can happen if the helper crashes repeatedly, as there are some incompatibilities on some systems. Please check your server.log: there would be a hint about the daemon crashing (Settings/Information).

In the logs there are no crashes. Today the setting was again lost, even without update. I tried to set it again, made an update, but the setting is still correct. Has to be something other. Now I selected the Spotty Helper Application manually instead of automatic. Maybe that helps.
disableDiscovery is correctly set to ~ in /var/lib/squeezeboxserver/prefs/plugin/spotty.prefs when disabled and to on when enabled.
This are the services from the GUI:

This from the command line:
root@ms4h:~# systemctl --type=service --state=running
  UNIT                      LOAD   ACTIVE SUB     DESCRIPTION
  acpi-fakekey.service      loaded active running ACPI fakekey daemon
  acpid.service             loaded active running ACPI event daemon
  apache2.service           loaded active running The Apache HTTP Server
  autofs.service            loaded active running Automounts filesystems on demand
  avahi-daemon.service      loaded active running Avahi mDNS/DNS-SD Stack
  cron.service              loaded active running Regular background program processing daemon
  dbus.service              loaded active running D-Bus System Message Bus
<EMAIL_ADDRESS>      loaded active running Getty on tty1
  nmbd.service              loaded active running Samba NMB Daemon
  qemu-guest-agent.service  loaded active running QEMU Guest Agent
  rc-local.service          loaded active running /etc/rc.local Compatibility
  rpcbind.service           loaded active running RPC bind portmap service
  rsyslog.service           loaded active running System Logging Service
  smbd.service              loaded active running Samba SMB Daemon
  ssh.service               loaded active running OpenBSD Secure Shell server
  systemd-journald.service  loaded active running Journal Service
  systemd-logind.service    loaded active running User Login Management
  systemd-timesyncd.service loaded active running Network Time Synchronization
  systemd-udevd.service     loaded active running Rule-based Manager for Device Events and Files
  telegraf.service          loaded active running Telegraf
<EMAIL_ADDRESS>          loaded active running User Manager for UID 0

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
21 loaded units listed.

Yes. I wrote a script now, that notifies me, when the option gets changed. This way I can check what happens at this moment.

Seems that this was a LMS bug. Since the latest LMS update this did not happen again.


When provide netty4 compares the performance test with the netty3.

Do you mean the performance benchmark testing report between Dubbo with Netty3 and Netty4?

yes


Script for creating scaling plots/tables

This will most likely be some added functionality in the generic plotting script (see #107), plus a custom config file for scaling plots specifically.

In particular, we want to do point 3 of #183 as part of this issue:

scale y values by the value of the first point (usually the serial performance point in a scaling plot)


Enable logger for application layer

Description
The current solution for logging uses Serilog. Specifically class Serilog.Log and its static methods.
Usage of static methods is not ideal from a testing perspective and it would go against defined architecture in terms of dependency flow.
To enable logging in other layers, if needed, we need to create an interface on the application level and through dependency injection pass logger when desired.
AC

[ ] Interface representation of logger is created and registered by Serilog
[ ] Experimental usage has been tested and documented in PR
[ ] All tests are passing

After discussion with @robertstriz  we found that the current state already provides a solution for this.
Serilog usage already registered instance for an interface ILogger so we are able to inject that anywhere we need.
Marking as Done.


Netfilm

Source name
Netfilm
Source link
https://netfilm.app
Source language
English
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Pleace Sorurce Code


update linuxptp daemon image to fetch from redhat-cne

Signed-off-by: Aneesh Puttur<EMAIL_ADDRESS>Update the env file to fetch linuxptp daemon image from redhat-cne repo

/lgtm
/approved


add completion for greek letters

Closes #157

This looks great! I’m not really seeing much benefit in adding the phf dependency though and would somewhat prefer keeping the code dependency-free if possible.

This looks great! I’m not really seeing much benefit in adding the phf dependency though and would somewhat prefer keeping the code dependency-free if possible.

phf is generally preferred for this use case because a perfect hash map is what you need in this case


Investigate the risk of recording all evaluations under the 10.1099 doi prefix

As of today we record 1661 evaluations:
https://api.crossref.org/works?filter=prefix:10.1099,type:peer-review,relation.type:is-review-of
The relation filter is for robustness, but does not exclude anything:
https://api.crossref.org/works?filter=prefix:10.1099,type:peer-review
The publisher has 72718 items on crossref, initial sample shows journal-article:
https://api.crossref.org/works?filter=prefix:10.1099

Running the below commands confirms that all ingested evaluations have Microbiology Society as publisher:
$ curl -v "https://api.crossref.org/works?filter=prefix:10.1099,type:peer-review,relation.type:is-review-of&sort=published&order=asc&rows=1000" > acmi-page-1.txt
$ curl -v "https://api.crossref.org/works?filter=prefix:10.1099,type:peer-review,relation.type:is-review-of&sort=published&order=asc&rows=1000&offset=1000" > acmi-page-2.txt
$ cat acmi-page-* | jq . | grep publisher | sort | uniq -c
   1661         "publisher": "Microbiology Society",

Filtering by doi partial suffix shows all items have strong relationship with acmi.
$ cat acmi-page-* | jq . | grep DOI | grep 10.1099/acmi | wc -l
1661

Querying by publisher-name Microbiology Society produced 72718 items, which is the same as filtering by DOI prefix:
https://api.crossref.org/works?filter=prefix:10.1099&query.publisher-name=Microbiology Society

Facets can give us the total number of items matching each type:
curl "https://api.crossref.org/works?filter=prefix:10.1099&facet=type-name:*" | jq .message.facets

{
  "type-name": {
    "value-count": 5,
    "values": {
      "Journal Article": 69192,
      "Peer Review": 1661,
      "Report": 1004,
      "Posted Content": 856,
      "Journal": 5
    }
  }
}

This investigation shows that there are 1004 report type items available on Crossref under the 10.1099 prefix. We believe they correspond to machine-generated reports rather than peer review.
$ curl -v "https://api.crossref.org/works?filter=prefix:10.1099,type:report&sort=published&order=asc&rows=1000" > acmi-reports-page-1.txt
$ curl -v "https://api.crossref.org/works?filter=prefix:10.1099,type:report&sort=published&order=asc&rows=1000&offset=1000" > acmi-reports-page-2.txt
$ cat acmi-reports-page-* | jq . | grep DOI | head
        "DOI": "10.1099/acmi.0.000459.v1.2",
        "DOI": "10.1099/acmi.0.000459.v1.1",
        "DOI": "10.1099/acmi.0.000460.v1.1",
        "DOI": "10.1099/acmi.0.000460.v1.2",
        "DOI": "10.1099/acmi.0.000463.v1.1",
        "DOI": "10.1099/acmi.0.000463.v1.2",
        "DOI": "10.1099/acmi.0.000462.v1.1",
        "DOI": "10.1099/acmi.0.000462.v1.2",
        "DOI": "10.1099/acmi.0.000464.v1.2",
        "DOI": "10.1099/acmi.0.000464.v1.1",

All posted-content items (typically preprints) are part of acmi.
$ curl -v "https://api.crossref.org/works?filter=prefix:10.1099,type:posted-content&sort=published&order=asc&rows=1000" > acmi-posted-content-page-1.txt

$ cat acmi-posted-content-page-* | jq '.message.items[].DOI' | grep acmi | wc -l
856

According to Crossref journal records, this publisher has 5 journals.
curl "https://api.crossref.org/works?filter=prefix:10.1099,type:jou
rnal" | jq '.message.items[].title'
[
  "Journal of General Virology"
]
[
  "Microbiology"
]
[
  "International Journal of Systematics and Evolutionary Microbiology"
]
[
  "Journal of Medical Microbiology"
]
[
  "JMM Case Reports"
]

However, 2 more publications are listed on the website:

Access Microbiology, an open research platform (not to be confused with Microbiology)
Microbial Genomics

We are testing hypothetical scenarios against the current product, to find out:

whether they could trigger undesirable consequences
if we can identify the relevant places to intervene in the code if that happens.

We have investigated this hypothetical scenario:

the Microbiology Society adds another journal with public peer reviews which appear on Crossref, and they don't want it on Sciety. What do we do?
We inspected our ACMI ingestion and it will start to record these peer reviews, assuming they are under the same DOI prefix.

Therefore, we will need to:

introduce an ingestion filter that targets DOIs of the form 10.1099/acmi.*
erase the incorrectly recorded evaluations

Another hypothetical scenario:

Mark asks us to include machine-generated reports as well as peer reviews. What do we do?

Therefore, we will need to:

change or add Crossref URL and codecs in the ingestion
the DOIs use the same prefix so we will ensure the evaluation fetcher for the digest fails cleanly, and provides only a link to the original URL in the paper activity page
we won't be able to guarantee any machine readable digest

We are testing hypothetical scenarios against the current product, to find out:

whether they could trigger undesirable consequences
if we can identify the relevant places to intervene in the code if that happens.

We have investigated this hypothetical scenario:

the Microbiology Society adds another journal with public peer reviews which appear on Crossref, and they want it on Sciety. What do we do?
We inspected our ACMI ingestion and it will start to record these peer reviews, assuming they are under the same DOI prefix.

Therefore, we will need to:

introduce ingestion filters that targets DOIs of the form 10.1099/acmi.* and whatever we need for the new journal
erase the incorrectly recorded evaluations

Another hypothetical scenario:

the society changes their domain name (or path), where they host the XML for machine readable digests

We will need to:

if the domain / path is changed for all hosted machine readable digests, then we will need to update the hardcoded URL root to the new value
if the hosting is split between original and new locations, more investigation will be needed


Use an oauth credential for GCS that supports refresh tokens

fixes #1673

@patflynn adding some logging around error conditions: https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1684/commits/405e85d60aba9ebe74cc6c4c2c17be2d414d4612


Simplify the protVer arguments

Without loss of generality, focus on Allegra. Start from the binding of protVerAllegra in protocolInfoCardano. EG at https://github.com/input-output-hk/ouroboros-consensus/blob/0079ee65f6c49d1c05a8d30ffa492b20c46b12b8/ouroboros-consensus-cardano/src/ouroboros-consensus-cardano/Ouroboros/Consensus/Cardano/Node.hs#L658
There, protVerAllegra:

(A) is passed to mkShelleyBlockConfig
(B) influences maxMajorProtVer

Also, maxMajorProtVer:

(C) is passed to tpraosParams and used to construct praosParams, to eventually be an upper bound in the ProtocolHeaderSupportsEnvelope envelopeChecks method (to throw the "obsolete node" errors).
(D) is passed to mkPartialLedgerConfigShelley which eventually uses it to constructor SL.Globals

mkShelleyBlockConfig ::
     ShelleyBasedEra era
  => SL.ProtVer
  -> SL.ShelleyGenesis (EraCrypto era)
  -> [SL.VKey 'SL.BlockIssuer (EraCrypto era)]
  -> BlockConfig (ShelleyBlock proto era)
mkShelleyBlockConfig protVer genesis blockIssuerVKeys = ShelleyConfig {
      shelleyProtocolVersion  = protVer
    , shelleySystemStart      = SystemStart  $ SL.sgSystemStart  genesis
    , shelleyNetworkMagic     = NetworkMagic $ SL.sgNetworkMagic genesis
    , shelleyBlockIssuerVKeys = Map.fromList
        [ (SL.hashKey k, k)
        | k <- blockIssuerVKeys
        ]
    }

data instance BlockConfig (ShelleyBlock proto era) = ShelleyConfig {
      -- | The highest protocol version this node supports. It will be stored
      -- the headers of produced blocks.
      shelleyProtocolVersion  :: !SL.ProtVer

-- | Praos parameters that are node independent
data PraosParams = PraosParams
    ...
    -- | All blocks invalid after this protocol version, see
    -- 'Globals.maxMajorPV'.
    praosMaxMajorPV        :: !MaxMajorProtVer,

data Globals = Globals
  ...
  , maxMajorPV :: !Version
  -- ^ All blocks invalid after this protocol version

(D) I just opened https://github.com/input-output-hk/cardano-ledger/issues/3682, which would eliminate this use.

(A) ultimately enables the node to write this version to a header field that is never scrutinized by the entire Cardano node code base. It is only used for SPOs to indicate in their blocks that they have upgraded their software in preparation for an imminent transition to the next ledger era.

(C) This use is motivated in a short paragraph in the the ledger spec, here: https://github.com/input-output-hk/cardano-ledger/blob/63d98c3f8e9eb2878cec3ab71c54fc40c798ac01/eras/shelley/formal-spec/protocol-parameters.tex#L162-L165 It is worth noting that the value scrutinized here doesn't come from the header, it instead comes from the ledger state (view). And most crucially: it is not the header from (A).

(B) The influence of allegraProtVer on maxMajorProtVer is via the latter's definition:

https://github.com/input-output-hk/ouroboros-consensus/blob/0079ee65f6c49d1c05a8d30ffa492b20c46b12b8/ouroboros-consensus-cardano/src/ouroboros-consensus-cardano/Ouroboros/Consensus/Cardano/Node.hs#L754-L775
Note that this use is exactly contrary to the warning comments where allegraProtVer is actually set, such as:
https://github.com/input-output-hk/cardano-node/blob/70dde196367e86c977fbe72167f4eb303b3ffa88/cardano-node/src/Cardano/Node/Protocol/Cardano.hs#L185-L194
        Consensus.ProtocolParamsAllegra {
          -- This is /not/ the Allegra protocol version. It is the protocol
          -- version that this node will declare that it understands, when it
          -- is in the Allegra era. That is, it is the version of protocol
          -- /after/ Allegra, i.e. Mary.
          allegraProtVer =
            ProtVer (natVersion @4) 0,
          allegraMaxTxCapacityOverrides =
            TxLimits.mkOverrides TxLimits.noOverridesMeasure
        }

It is currently my suspicion that all of these per-era *ProtVer arguments should be removed (thereby eliminating (B)), and replaced by some logic that defines maxMajorProtVer by analyzing the last given transitionIntraShelleyTrigger. And the per-era values used in (A) should instead all simply use maxMajorProtVer.

Minor comments:

Note that this use is exactly contrary to the warning comments where allegraProtVer is actually set, such as:
https://github.com/input-output-hk/cardano-node/blob/70dde196367e86c977fbe72167f4eb303b3ffa88/cardano-node/src/Cardano/Node/Protocol/Cardano.hs#L185-L194

Yeah, I think this is a case where we actually loose generality by only considering Allegra: Ignoring experimental eras for now (this just changes what the "last era" is), protVerXXX has the following meaning ATM:

For all but the last era, it is the lowest major protocol version of the next era, ie if YYY is the successor of XXX, it is eraProtVerLow @YYY
For the last era, it is the highest major protocol of this last era, ie eraProtVerHigh @XXX.

Also see https://github.com/input-output-hk/ouroboros-consensus/pull/294#discussion_r1304111224
So in fact, we can safely use the protVer entry for the last era as the max major protocol version, despite the fact that protVerXXX is not a protocol version of the XXX era for all but the last era.

It is currently my suspicion that all of these per-era *ProtVer arguments should be removed (thereby eliminating (B)), and replaced by some logic that defines maxMajorProtVer by analyzing the last given transitionIntraShelleyTrigger.

That specific approach won't work directly:

TriggerHardFork does not necessarily contain a protocol version:
https://github.com/input-output-hk/ouroboros-consensus/blob/0079ee65f6c49d1c05a8d30ffa492b20c46b12b8/ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/HardFork/Simple.hs#L11-L24
Even if it did, it does not contain any information on whether the last era already sustained an intra-era HF. Eg Babbage had an intra-era HF (from 7 -> 8, "Valentine HF"), so the latest TriggerHardForkAtVersion (ignoring Conway, which is experimental and should hence not be considered unless enabled explicitly via a flag) will only be 7, but we need to set the max major protocol version to at least 8 to avoid considering all blocks after the Valentine HF as invalid.

The general approach can of course still work, we just have to pass in more stuff ("worst-case", just the max major protocol version directly).

And the per-era values used in (A) should instead all simply use maxMajorProtVer.

Intuitively, that sounds like a good plan; main question is: do we ever want forging nodes to put different versions in their header for different eras? Maybe a statistical use case similar to https://github.com/input-output-hk/cardano-node/blob/70dde196367e86c977fbe72167f4eb303b3ffa88/cardano-node/src/Cardano/Node/Protocol/Cardano.hs#L210-L213 could arise?

protVerXXX has the following meaning ATM

The changing semantics of the field---especially in a way dependent on the --experimental flag---is confusing for a "configuration data" data structure😬.

That specific approach won't work directly.

Yeah, I figured there isn't quite enough information/it wasn't accessible right now. But this still seems right to me as a high-level design target.

do we ever want forging nodes to put different versions in their header for different eras?

In general, sounds useful. And indeed you linked to a former example use (which correctly comments itself as a "HACK" :/).
But it also sounds not strictly necessary. So at the very least, I think it should be provided in a separate "overrides" argument, eg (perhaps limited to the minor version?). More directly: I think we should remove it now and add something like that back when it's next actually needed.

PR #294 is definitely related. For context: I hadn't looked over that PR before drafting this Issue.

The MaxMajorPV was added in this commit https://github.com/input-output-hk/cardano-ledger/commit/441e23bc7541ab0a535e9d24cda1d836c04b64ed

Esgen and I just discussed this all during a call. There are several overlapping concerns, sadly.
Testing overrides
For testing, we let config override the version-based triggers in the HFC.
Experimental flags
There are two "experimental" flags in the node: ExperimentalHardForksEnabled (<-> npcExperimentalHardForksEnabled) (formerly TestEnableDevelopmentHardForkEras) and ExperimentalProtocolsEnabled (<-> pncExperimentalProtocolsEnabled) (formerly TestEnableDevelopmentNetworkProtocols).
The node ultimately passes ExperimentalProtocolsEnabled to Consensus as srnEnableInDevelopmentVersions.
  , srnEnableInDevelopmentVersions  :: Bool
    -- ^ If @False@, then the node will limit the negotiated NTN and NTC
    -- versions to the latest " official " release (as chosen by Network and
    -- Consensus Team, with input from Node Team)

The node uses ExperimentalHardForksEnabled to alter the upper bounds on the *ProtVer arguments it passes to Consensus. Re-read the Issue description to understand the consequences this flag has. For example:
          Praos.babbageProtVer =
            if npcExperimentalHardForksEnabled
              then ProtVer (natVersion @9) 0
              else ProtVer (natVersion @8) 0,

It is not obvious to me how these two flags interact in general. In particular, suppose we have an experimental era, such as Conway right now. Is it necessarily the case that ExperimentalProtocolsEnabled enables (at least) the NTN and NTC versions that Conway requires? And so we should require that ExperimentalProtocolsEnabled implies ExperimentalHardForksEnabled?
When we instead don't have an experimental era, ExperimentalHardForksEnabled has no effect and so that implication wouldn't be necessary? For example, without an experimental era, ExperimentalProtocolsEnabled could be guarding merely new queries.
The Obsolete Node Checks
The MaxMajorPV mechanism introduced here https://github.com/input-output-hk/cardano-ledger/commit/441e23bc7541ab0a535e9d24cda1d836c04b64ed is older than the HFC. At a high-level, the HFC renders MaxMajorPV unnecessary: if the node doesn't yet know about the Nth ledger era, then it won't be able to even parse a header in that era. However, because of "intra-era hard forks", it may be that MaxMajorPV is necessary even in the presence of the HFC.
It seems possible that we could ban intra-era hard forks in the future. Or maybe even implement them as duplicates in the HFC type-level list (but that would be inconvenient in terms of performance, and Issue https://github.com/input-output-hk/ouroboros-consensus/issues/328, eg).
Type-level ledger era major version intervals
The ledger statically assigns intervals of the major version to each era. For example:
https://github.com/input-output-hk/cardano-ledger/blob/a90833107aa98f359dbb839991582b397c1c4bc8/eras/allegra/impl/src/Cardano/Ledger/Allegra/Era.hs#L20-L26
-- | The Allegra era
data AllegraEra c

instance Crypto c => Era (AllegraEra c) where
  type PreviousEra (AllegraEra c) = ShelleyEra c
  type EraCrypto (AllegraEra c) = c
  type ProtVerLow (AllegraEra c) = 3

Alonzo is different because it contains a so-called "intra-era hard fork" (ie a hard fork that does not change the ledger era, and so does not involve the HFC).
https://github.com/input-output-hk/cardano-ledger/blob/a90833107aa98f359dbb839991582b397c1c4bc8/eras/alonzo/impl/src/Cardano/Ledger/Alonzo/Era.hs#L21-L28
-- | The Alonzo era
data AlonzoEra c

instance Crypto c => Era (AlonzoEra c) where
  type EraCrypto (AlonzoEra c) = c
  type PreviousEra (AlonzoEra c) = MaryEra c
  type ProtVerLow (AlonzoEra c) = 5
  type ProtVerHigh (AlonzoEra c) = 6

If it weren't for the testing overrides and the experimental flags, I think all of the node's use of protocol versions would be determined by those ProtVerLow and ProtVerHigh instances---even intra-era hardforks, since ProvVerHigh captures those. Sounds appealing.

I think so too.
Right now Handshake assumes that all versions are linearly (/ totally) ordered.  But we could relax it to be a partial order, which would allow things like:
graph TD;
  1'-->0;
  1-->0;
  2-->1;
  2-->1';

where 1 and 1' are the non comparable two different experimental version.  Consensus could peak it's own max network version, the same with network.  Assume that 1 contains some consensus feature while 1' some network features, and we don't want to publish both (e.g. 2).  Then the network team would pick 1 as it's max version, and consensus would peak 1' as its max version.
Our picking algorithm would need to pick the smallest sub-partial order which is closed under supremum.  This way if one enables only consensus experimental features one would end with versions smaller or equal to 1; if one only enables network experimental features one would end with versions smaller or equal to 1' and if one picks both then all versions smaller or equal 2.
Handshake would do the same as now: pick the largest version which belongs to both own supported versions and the presented one.


issues bizgenerator 2

branch: development_fixoct8b

employees need to be put in same collection under employees/...

see introduced name in employee object
uses name (with only _ and underscore) as name of page of employee
only generate if it doesn't exist yet

we should have more checks, if errors then we should not generate mdbook, just show the errors

see if we can do a trick where we serve the mdbook over v webserver,
we use https://modules.vlang.io/os.notify.html to see if change of file at source
then use some injected javascript trick (when serving mdbook) to reload the open page when there is change of file at source, this would hugely help the development time.


Changing sort order or page on the search screen resets filters

Reproduction steps:

Go to the search screen
Change the category filter to "Fern" and click "Apply Filters"
Scroll down and click "Next"

Alternatively, click "Genus" or "Species" to apply a sort

Notice the category filter (and all other filters that could be applied) are now blank.

Closed as duplicate of #22


Update Set-TenantProperties.ps1

Correction of a small typo in the PowerShell script

thx @Tomatokun13, appreciated.


Render Markdown of JSDoc

VSCode Version: 1.7.1
OS Version: macOS

I'm expecting
/**
 * This is foo
 * Foo is great! Use it like this:
 *
 * ```ts
 * const foo = new Foo();
 * ```
 */
function Foo() {

}

var f = new Fo

I was expecting my Markdown to be rendered here:

the code above works fine and the jsdoc displayed as markdown in a .ts file on insiders build :
Version 1.8.0-insider
Commit ce6d57875ab53309204cf12dc54d74956221cfc1
Date 2016-11-09T08:48:03.700Z
Shell 1.3.8
Renderer 52.0.2743.82
Node 6.5.0
OS Windows 10 14393.447

I am seeing the issue.

This is a good feature request.

This issue was moved to Microsoft/TypeScript#12185


Feature/rabbit specific vhost for queue and binding

While developing with the RabbitMQ module I figured out that there was no possibility to start with a queue or binding on a specific virtual host. Since my test setup should be as realistic as possible I created a workaround within my project. To make it easier for others who need queues and bindings on specific virtual hosts I've created this pull-request.
I've also added some basic usage examples inside the documentation to let others know about the valuable features which are already builtin the module.

Hi @StefanHufschmidt,
Could you please use runnable examples? See other docs pages for examples of runnable examples 😅

Oh, missed that comment. I'll change that.

@bsideup I've added some tests for the running documentation examples. I did not want to change the whole tests inside the RabbitMQ module so I've added some basic ones for the documentation to ensure that the documentation works. I hope I've included everything correctly.

Hi Guys,
May I know any updates on this topic?
Thanks.

Hello @bsideup @kiview @rnorth, is there anything else that prevent this pull request to be merged?
Can I help?

@StefanHufschmidt thanks for the PR! After some lessons learned on our side, we consider that testcontainers should only have the responsibility to start and provide the right attributes so the client can connect to it. We are not considering coupling with the CLI tools provided by each image.

@eddumelendez since the basic functions already used the cmd interface of the container I thought to keep it consistent. Should the existing function for the RabbitMQContainer also be changed?

Hey @StefanHufschmidt, long time no see ;)
Yes, we were indeed wondering if they should be deprecated.
Can't you normally also use a client library (admin client?) to do such things?

@kiview yes you can configure the RabbitMQ via the management API. Springs AmqpAdmin or better its implementation RabbitAdmin uses this API and already allows the configuration remotely. Therefore I'd say that it is possible.
I've noticed that there are some issues regarding latest version of the RabbitMQContainer:

#5599
#4312

Maybe it's time to overhaul the whole container in a way the API might not change but the function is provided via other ways than using the CLI inside the container.

In general, what we currently envision for Testcontainers container modules going forward is that Testcontianers takes care of the following:

Starting up the container and ensuring its readiness in a stable manner
Providing a connection mechanism (often just a URL, or host and port combination) that allows other client libraries to connect to the container and let them do what they do best.

E.g. for databases, we mostly should just expose the mapped JDBC-URL and let others tools such as Flyway/Liquibase handle schema creation and migrations. Ultimately, I think other modules should also move in this direction.

From my point of view the helper methods for declaring exchanges, queues and bindings where always very helpful. Maybe even with the methods withPublishedMessages(List<Message>, Exchange) and withPublishedMessages(List<Message>, Queue) the testing is speed up massively.
I've found a way to declare exchanges, queues and bindings (see https://github.com/testcontainers/testcontainers-java/compare/master...StefanHufschmidt:testcontainers-java:feature/rabbitmq_without_cli). I also know a way to implement those publish methods. This way the declaration is way faster than executing the command inside the container but it also requires the official RabbitMQ client lib.
The whole user configuration stuff, policy stuff is only offered by the HTTP API of the management plugin or the CLI tool (as it currently is). Ofc you could build some kind of advanced configuration file and map it into the container but the format is pretty annoying. One way could be to use https://github.com/rabbitmq/hop. This library offers the API usage of the management plugin.
I'd suggest to add the basic exchange, queue, binding and message configuration extension as well as the more complicated management configuration into a separate module so that everyone can decide by themselves how much and what to use.
Maybe most of the time a container is enough. Sometimes you could need some help declaring exchanges, queues, bindings and publish messages for your tests and the use-case for the other stuff might be very rare I'd assume.
Then we'd have:

rabbitmq-basic module containing the BasicRabbitMQContainer which just spins up a container and checks it for being ready
rabbitmq module containing the RabbitMQContainer which simply extends the BasicRabbitMQContainer and offers the configuration methods as it currently is

That is indeed a general concept I was thinking about, but I am not sure if and how we would maintain those extended APIs in the context of Testcontainers.
I somehow think, configuring a RabbitMQ started by Testcontainers for testing is technically and conceptually not different than configuring any other kind of RabbitMQ instance. This means if you just have this e.g. RabbitMQTestSupportClient class, that provides you all the APIs you were mentioning, it would be enough if this class would connect to the instance via the URL Testcontainers can provide. And this class would be independent from the mechanism by which the instance was started, as long as it interacts with it over the official external protocols, e.g. some admin client or HTTP. The only situation, where such a support class would need to be aware of Testcontainers is, when it can only do its task by executing commands inside the container, but I would hope this is rare.
I also think internally using an official client (or something like hop) to interact with the instance is completely fine, especially if it's shaded.
Note that these are some personal unstructured thoughts of mine and they don't necessarily reflect the thoughts of the Testcontainers Maintainers team on this issue. We will also discuss this internally, to come up with some clearer guidelines 🙂

From my point of view a Testcontainer should at least provide the basic function for a module which it is representing. A database container also allows to create a specific database. Therefore I'd expect at least the following things for a RabbitMQContainer:

Create a queue with a specific name
Create an exchange with a specific name and type
Create a binding from an exchange to a queue with specific routing key
Publish a message to an exchange with specific routing key
Publish a message to a specific queue
Read n messages from a queue

For my personal taste we can discard most of the convenience functions such as "using special SSL certificate", "use policy", "use vhost", "create user" and leave it for specific customization for each individual use-case.
The mentioned basic functions will cover the common use-cases for:

testing a consumer which listens on a queue
testing a publisher which publishes messages to an exchange

This would also reduce all of our methods to a hand full and might reduce the maintenance massively without loosing most of the convenience for most of our use-cases.
Since it should not be based on the container itself, it can use the APIs and default client library instead to avoid having to adjust to changes of the CLI.
Another benefit would be that we can also run with regular rabbitmq images instead of using those with management plugin enabled. This would also reduce resources and startup time.

Thanks for the detailed input @StefanHufschmidt, I think it makes a lot of sense from a DX and usage perspective to have these kinds of functionalities provided. I think we will need a bit of time to internally decide how we see the focus going into the future, we will keep you in the loop 👍


[WIP] Validate IngressRoutes and update their status

Updates #490
Pending on #469

Thanks @davecheney. Writing the status from within DAG.recompute also gave me a gut feeling that something was out of place, but I wasn't sure exactly what/where. I think your comments and suggestions crystallized the issue for me. I am going to close this PR and work on a new one.

I think a good way forward would be to change recompute to return a slice of failed  validation types, I don’t know exactly goes inside that type, but some error value or string as a start as well as a reference to the original object. That should be enough of a toehold for a separate process to do status patches after the run.

On 3 Jul 2018, at 18:11, Alexander Brand<EMAIL_ADDRESS>wrote:
Closed #491.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Remove double quotes in awesomplete.min.js title

Quote causes an error in the console.

Huh, that's super odd. Pull request to remove the quotes?

@JonathanDcstr You can close this issue, it's already being solved and merged in https://github.com/LeaVerou/awesomplete/commit/66837d556b2927ac5c156d890c13165291ab9b25#diff-7b5ed85343ecac61d1197e3f969efe51L1


fractal(-next): init unstable rewritten version

Motivation for this change
Have a useable matrix-client: with not every functions yet.

crypto

multi-account

...

[ ] does it build?

[ ] clean up if old library really needed

Things done
this PR also updates:

pango
gtk4

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] 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

[ ] Fits CONTRIBUTING.md.

Note that GTK 4.5 is a development version and unless something changed, still contains significant regressions.

@jtojnar it is not an development branch, it is a developer release/tag
but yes this PR should not be merged till a gtk4 in version 4.5.x is official released.

FYI I just merged #176259 so fractal will be the last package that use libhandy_0.

https://github.com/NixOS/nixpkgs/pull/192935 updated to latest release.
@genofire can this get closed?


[Bug] Incorrect Gen 1 Hue Dimmer Switch Button Mapping in HomebridgeZ2M (DOWN-OFF-ON-UP)

Please use the template and fill in all the data requested below!
Describe the bug
Hi, I'm trying to use the Gen 1 Hue Dimmer (Philips<PHONE_NUMBER>21) with a CC2652p-based Zigbee Gateway on Homebridge in hopes of getting the LONG PRESS functionality that isn't provided by the Hue Bridge itself in Homekit.
The Dimmer Switch successfully paired (with the "legacy: true" default config) was able to be seen and operated in Homekit. However, I realized quickly that the button mapping of the Dimmer when recognized by the HomebridgeZ2M plugin was as follows:
Button 1 (down):
SINGLE: down-press
LONG : down-hold
Button 2 (off):
SINGLE: off-press
LONG : off-hold
Button 3 (on):
SINGLE: on-press
LONG : on-hold
Button 4 (up):
SINGLE: up-press
LONG : up-hold
This seems odd to me, since the actual button placement on the remote from top to bottom is ON - UP - DOWN - OFF. I understand the support of this device was added a long time ago, but is there anyway I can change the button mapping when it is brought into Homebridge?
p.s. From Zigbee2MQTT's frontend, the button mapping is correct, it is only after it's brought into Homekit that the mapping changes.
Thank you very much!
Related devices
Gen 1 Philips Hue Dimmer Switch (Philips<PHONE_NUMBER>21)
To Reproduce
Standard install with Device type specific configuration set to "legacy: true" or just leave it blank as default.
Expected behavior
The actual button mapping from top to bottom should be: ON - UP - DOWN - OFF.

Does it match this mapping or not?
The reason it might not map to the physical position on the device (or even the buttons on the device), is because this information is not known in Zigbee2MQTT and therefor not known in this Homebridge plugin.
In reality without this information being provided by Zigbee2MQTT, the plugin cannot do this "correctly" without a lot of configuration (which is what I want to avoid).

Hi, yes, the button mapping is exactly as shown in the homebridge log as button 1 (down) / button 2 (off) / button 3 (on) / button 4 (up) and it's how it was presented in Homekit as a result.
I see, I guess since ZigBee2MQTT has no idea that the ON button stands for Button 1 and the UP button stands for Button 2 and so on, I guess it's not possible to have it at the correct physical positions at this point?

It is not possible. We could potentially create a configuration for this, but I personally don't see a use case for it and it would only complicate the usability. If you really want this, please open up a feature request issue describing what this feature should look like.
Functionally, it doesn't change a thing and HomeKit still won't show labels that directly relate to what's on the physical device (numbers as opposed to "On", "Off", "Up" and "Down").
Next to that, HomeKit will still show which event was triggered when you are in the screen to configure the actions in the Home app.
In other words, if you perform the action on the remote for which you want to configure the action in HomeKit, it should give you an indication of that in the Home app.
Closing this issue, as the device is working as defined.


Investigate non-deterministic CI failures

Travis CI is failing non-deterministically for some reason.
Usually it takes me 2-3 attempts of retriggering CI for tests to pass.

From my observations, error messages differed from run to run. Here's one example:
[info] - add_broadcast4 *** FAILED ***
[info]   java.io.IOException: Cannot run program "/tmp/snippet": error=2, No such file or directory
[info]   at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
[info]   at scala.sys.process.ProcessBuilderImpl$Simple.run(ProcessBuilderImpl.scala:71)
[info]   at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.lineStream(ProcessBuilderImpl.scala:143)
[info]   at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.lineStream(ProcessBuilderImpl.scala:109)
[info]   at scala.sys.process.ProcessBuilder.lines(ProcessBuilder.scala:178)
[info]   at scala.sys.process.ProcessBuilder.lines$(ProcessBuilder.scala:178)
[info]   at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.lines(ProcessBuilderImpl.scala:87)
[info]   at lantern.DslDriverC.eval(dslapi.scala:501)
[info]   at lantern.BroadCastingTest.$anonfun$new$5(test_broadcast.scala:85)
[info]   at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)

Perhaps randomizing snippet filenames fixes this issue. I'll observe and close this issue if that is the case.

Yep. That was the same problem. My recent push should have used random name now.

One downside to randomizing snippet filenames is that each test invocation generates a new file in /tmp. If tests are run many times, there'll be an explosion in the number of snippet files.
A better strategy may be to use the testcase name as the snippet filename, e.g. test("vector-vector-dot") -> /tmp/vector-vector-dot.cpp.

I think it's better to run tests sequentially anyways (for reproducibility) so let's just turn parallelism off (there's an sbt flag to do that, check LMS repo).
But let's also name files according to test names, as you suggest @dan-zheng.

Parallel test execution disabled.
Reverted snippet filename randomization.

The root of the CI failures was parallel testing, not the shared snippet filename. Use a single deterministic filename is better for clarity.


Create gammux3.py (Python3 Version)

Translated code to Python3. This still doesn't create gAMA chunks, but at least its Python3

@Feriixu Looks good, merged!
(also thanks)


update from Studio Classic styles ahead of deprecation

referencing new styles via L.tilelayer with url template because Mapbox.js 2.2.2 does not support L.mapbox.styleLayer, and attempt at updating led to further complications

Hi, did those changes affect the zoom level ?

@woodElec yes it did, indirectly. We've fixed the regression in #667 and re-deployed.


Cabrillo Fix

There was an bug in the modes of cabrillo exports.
Additionally we had no possibility to include the gridsquares in the cabrillo file. Since Wavelog does not know that the grid was chosen as exchange type (we do not store this yet...), I had to add a little option in the export form. (Default: No)

This affects for example the DARC FT4 contest.
The sequence is
QSO: [QRG in kHz]  [MODE*]   [DATE]   [TIME]  [MY_CALL]  [RSTs]  [SERIAL]  [GRID]  [EXCH]  [RSTr]  [SERIAL]  [GRID]  [EXCH]
Serial, Grid and Exchange: Each if not null / empty  and grid if option is true
*Modes based on the official cabrillo documentation: https://wwrof.org/cabrillo/cabrillo-qso-data/

@dg9vh confirmed that this is the correct cabrillo syntax


Uncaught Error: The specified module could not be found./?~\AppData\Local\atom\app-1.52.0\res...

[Enter steps to reproduce:]

...
...

Atom: 1.52.0 x64
Electron: 6.1.12
OS: Microsoft Windows 10 Home Single Language
Thrown From: Atom Core
Stack Trace
Uncaught Error: The specified module could not be found.
\?\C:\Users\nisha\AppData\Local\atom\app-1.52.0\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
At electron/js2c/asar.js:138

Error: The specified module could not be found.
\\?\C:\Users\nisha\AppData\Local\atom\app-1.52.0\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:147:18)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:16:16)
    at customRequire (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:1:735077)
    at get_KeyboardLayoutManager (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:14:2716464)
    at get_manager (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:14:2716566)
    at Object.getCurrentKeyboardLayout (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:14:2716692)
    at e.keystrokeForKeyboardEvent (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:14:1047827)
    at KeymapManager.keystrokeForKeyboardEvent (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:11:1228394)
    at KeymapManager.handleKeyboardEvent (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:11:1226379)
    at WindowEventHandler.handleDocumentKeyEvent (~/AppData/Local/atom/app-1.52.0/resources/app/static/<embedded>:11:284820)

Commands

Non-Core Packages

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀


TAJO-1644: When inserting empty data into a partitioned table, existing data would be removed.

When inserting empty data into a partitioned table, existing data would be removed. Tajo provides column value partition which is hive-style partition. In hive, when inserting empty data into a partition, there are two cases. If you use dynamic partitions, existing data never would be removed. But if you don't use dynamic partitions, existing data would be removed. When inserting a data to partition, tajo user don't specify each column and each column value. So, it is similar to dynamic partition of hive. It seems to update deletion logic of partitioned table.

Thanks @hyunsik
I've just updated the patch using your comments. :)

Hi @blrunner,
Thank you for your work. How about the insert overwrite behavior for not partitioned table? Does that the same semantic?

Hi @hyunsik
Thank you for your review. I also agree with you. But when inserting empty data into a non partitioned table in hive, existing data would be removed always. I'm a bit anxious about user's confusion between hive and tajo.

@hyunsik
Thank you for your detailed review.
I've just updated the patch using your comments.

+1
Looks good to me. I leaved one trivial comment.


base64

Hi.
I have been testing Nesbox with loading ROMs from websites. I have successfully used code that will get a rom, convert it into base 64, and convert the base 64 into a Data URI. Unfortunately, Nesbox does not support Data URIs. Is there another way to load roms from different websites, or use the base 64 with Nesbox?
Thanks!
http://colt05.github.io/nesbox/test3

Unfortunately, there is no way to load base64 roms.
But if you want to load roms from different websites you have to add crossdomain.xml policy file to them.
http://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html

thanks!!
do you have to use crossdomain.xml even while using a cross-origin resource sharing proxy?

I think it's a bad way to use base64 in URL address, maximum length of url is ~2000 characters

is there another way to display it on a webpage using php? github pages does not support php so I can't use that. is there cross origin local storage (use one website to set the local storage of another website)?

pls read how to use crossdomain.xml for adobe flash.
you just have to put the crossdomain.xml file on a website with roms and then load roms from website with the emulator

ok. can the emulator load raw roms as text?


Microscopy techniques - new instance (and maybe a clean-up)

@ingrre asked if we could add "confocal light-sheet microscopy" and I think that it would make sense to do so. @tgbugs I checked the method ontology but couldn't find it there. Would it make sense to add it?
Additionally, I'm kind of wondering where we draw the line for the microscopy related terms? Below is a list of all microscopy term that we added so far:

Brightfield microscopy
Confocal microscopy
Dual View Inverted Selective Plane Illumination microscopy
Electron microscopy
Epifluorescent microscopy
Fluorescence microscopy
Focused Ion Beam Scanning Electron microscopy
Light microscopy
Light Sheet Fluorescence microscopy
Microscopy
Polarized Light microscopy
Scanning Electron microscopy
Serial Section Transmission Electron microscopy
Transmission Electron microscopy
Two-Photon Excitation Fluorescence microscopy
Widefield Fluorescence microscopy
Widefield microscopy

The easy one first: "microscopy" needs to be removed. This is a duplication since it exists as an experimental approach (which obviously makes most sense anyway).
Then, I think widefield fluorescence microscopy & epifluorescent microscopy might be synonym (see here: https://oni.bio/nanoimager/super-resolution-microscopy/epifluorescence-microscopy/).
So, in short, my questions are:

Add "confocal light-sheet microscopy" - yes or no?
Remove "microscopy" (actual not a question)
"widefield fluorescence microscopy" same as "epifluorescent microscopy" - yes or no?
If 3. is answers with no, rename "epifluorescent microscopy" to "epifluorescence microscopy" to be consistent with the other fluorescence techniques?

@lzehl feel free to comment as well :)

@UlrikeS91 I agree to removing "microscopy" but maybe next year (if this is already in use in EBRAINS) I don't want to do another mapping right now for migration. But I will check how far this term is in use.
The rest I leave to @tgbugs

@UlrikeS91 @lzehl, "microscopy" is not in use so can be removed

@lzehl Sure I can make a PR. Do you mean, remove the file? Or are there some intricate details I am not aware of?

@MaaikevS yes. just remove the jsonld file. the rest has to happen in the EBRAINS KG.

Done! See PR #145

Result of discussion with @tgbugs :
Let's add definitions to see what we might want to merge, but I think besides the widefield fluorescence microscopy & epifluorescent microscopy these can be all considered as different techniques

Thanks to everybody for all the discussion (online and offline) and the PRs to make first fixes! To see where we are with this issue, I'd like to sumnmarize and identify the parts that are still open.
During the discussion, we pretty much agreed that all of the listed microscopy techniques will remain (except for microscopy which is captured as an experimental approach in openMINDS).
I've copied in the list of techniques from above here again with comments about their status:

(previously) existing technique
definition added?
other notes

Microscopy
-
deleted

Brightfield microscopy
yes

Confocal microscopy
yes

Electron microscopy
yes

Fluorescence microscopy
yes

Light microscopy
yes

Light Sheet Fluorescence microscopy
yes

Polarized Light microscopy
yes

Widefield microscopy
yes

Electron tomography
yes
wasn't in my original list

Dual View Inverted Selective Plane Illumination microscopy
no

Epifluorescent microscopy
no
this is the same as widefield fluorescence microscopy, delete one and add other as synonym

Focused Ion Beam Scanning Electron microscopy
no

Scanning Electron microscopy
no

Serial Section Transmission Electron microscopy
no

Transmission Electron microscopy
had one already

Two-Photon Excitation Fluorescence microscopy
had one already

Widefield Fluorescence microscopy
had one already
this is the same as epifluorescence microscopy, delete one and add other as synonym

This means that the ones without a definition should get one and we should also have a look at the ones that already had a definition again just to check that we are happy with them.
All of these should also get ontology IDs if possible, so we could fix those in parallel when adding the definitions and/or check the existing definitions.
Here the questions when I opened the issue:

So, in short, my questions are:

Add "confocal light-sheet microscopy" - yes or no?
Remove "microscopy" (actual not a question)
"widefield fluorescence microscopy" same as "epifluorescent microscopy" - yes or no?
If 3. is answers with no, rename "epifluorescent microscopy" to "epifluorescence microscopy" to be consistent with the other fluorescence techniques?

Still needs an answer, but based on the previous discussions, I would say that we should add it unless one of the existing ones would already cover it. I will look into it and either comment again or make a PR for it.
done
I looked into it and they are the same. I will check which one of the two has been mostly used in the KG and do the mapping if necessary, and of course delete one of them.
We talked about this in a way before and concluded to stick to the term that is used more by the community. I'll check but I assume that it will remain "epifluorescent" (if we use this one and not widefield fl. microscopy).

To-Do:

[ ] add definitions (and ontology ID, etc.) for

[ ] Dual View Inverted Selective Plane Illumination microscopy
[ ] Focused Ion Beam Scanning Electron microscopy
[ ] Scanning Electron microscopy
[ ] Serial Section Transmission Electron microscopy

[ ] review/revise definitions (and add ontology ID, etc.) for

[ ] Transmission Electron microscopy
[ ] Two-Photon Excitation Fluorescence microscopy

[ ] "Widefield Fluorescence microscopy" and "Epifluorescent microscopy"

[ ] review/revise definition for "Widefield Fluorescence microscopy"
[ ] merge the terms (based on which is more commonly used) and add other as synonym
[ ] add "epifluorescence microscopy" as synonym (or new name and add all other ones as synonyms)

[ ] "confocal light-sheet microscopy":

[ ] check if any other term covers this technique, if not add it as a technique

I think this is it ☺ Once we fixed the to-do list items, we should be able to close this ticket! I'll work on this today.


Switching between subdomains, requires re-login

If you are logged into mydomain.com and then change the url to www.mydomain.com, you are asked to re-login when navigating to a protected page.

You can change the domain of the session cookie in the php.ini file, in the session.cookie_domain setting. If you set it to ".example.com", then it'll be valid for all subdomains of that domain, including "www". If you don't have access to the php.ini file, then you can achieve the same using the session_set_cookie_params function.


Secret scanning detects secrets leaked in pull requests and discussions

Summary
Secret scanning currently scans commit content for all supported patterns. We're extending the breadth of our scans for Advanced Security customers to cover pull requests and discussions, plus all related comments.
Intended Outcome
While most secret leaks occur in code content, a portion do also leak in other content types, including pull requests and discussions. We're expanding the scope of our scans for more exhaustive coverage to better protect our users across GitHub.
How will it work?
Advanced Security customers will be able to view detections found in private and public repositories for these content types within the secret scanning UI and REST API.

🚢 This has shipped: https://github.blog/changelog/2023-12-04-secret-scanning-now-detects-new-secrets-in-github-discussion-content.
Leaving open to track for GHES.

This shipped with GHES 3.14<EMAIL_ADDRESS>


[Feature Request] Metric for outstanding updates

Hey, thanks for writting this exporter. I was wondering if there is a possibility to have a metric for nextcloud updates as I want to alert with prometheus if there are any updates.

Apparently statistics about the apps have been added to the serverinfo response. :tada:
I've added these metrics in the linked PR. Please check if that works for you...

Apparently statistics about the apps have been added to the serverinfo response. :tada:
I've added these metrics in the linked PR. Please check if that works for you...

Thanks for the quick PR. I've tested it and it works perfect.
# HELP nextcloud_apps_updates_available_total Number of apps that have available updates
# TYPE nextcloud_apps_updates_available_total gauge
nextcloud_apps_updates_available_total 0

Thanks for the quick PR. I've tested it and it works perfect.
# HELP nextcloud_apps_updates_available_total Number of apps that have available updates
# TYPE nextcloud_apps_updates_available_total gauge
nextcloud_apps_updates_available_total 0


Expose Integration Flow Endpoint as API and Test the Flow

Tutorials: https://developers.sap.com/tutorials/cp-starter-isuite-api-management.html
Step 3 : Define the API : point 12:-- Screenshot needs to be updated. After opening an API in API Designer editor, there is a 'Download' option displaying in actual result as below.
Expected :

Actual :

@NidhiMurkute - fixed this, will send a PR very soon.


Update to Azure DevOps

Last line in the document should refer to Azure DevOps instead of VSTS.

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

ID: 113ca148-4ba7-2330-eff1-ae88af26b910
Version Independent ID: d05063b5-ffbf-23eb-a8ad-1dddf53e874a
Content: Agile Culture - Azure DevOps
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fagile%2fagile-culture.md&version=GBlive&_a=contents
Product: devops
Git Login: samgu
Microsoft Alias: abjork

@trickpatty Thanks for letting us know, I fixed this and it should be live shortly, and I'm doing another sweep to make sure no other ones slipped through.


add description and default for "custom-hadoop-binary-path"

add description and default for "custom-hadoop-binary-path"

Coverage increased (+9.09%) to 72.451% when pulling 046dd6e43f560abc0f9e664f8979085ccb9b3b10 on yuan/fix_hadoop_binary_path into 9655bed1ebcc28c2577157e588393ecd110ccfbb on master.


Suppress host restart for hostingstart.html

This should mitigate an obscure issue that is impacting a small number of apps where the host gets stuck in a restart loop that somehow relates to file change events happening for hostingstart.html

Verified to suppress the restart for hostingstart.html by testing with a private site extension


[BUG] Mac M2 arch reporting as M1

AWS offers support for mac M2, when trying crc on an M2 the INFO message is identifying the CPU as a M1:
INFO Checking if running emulated on a M1 CPU

Checking the arch we can see the M2
ec2-user@Mac-mini ~ % sysctl machdep.cpu.brand_string
machdep.cpu.brand_string: Apple M2 Pro

When we added this message, the M2 didn't exist. We check for arch64 on an Apple computer. Perhaps we just change this to 'Apple silicon' instead.

Or use the output from that macro?

Or use the output from that macro?

In some  instances, it would not be correct, for example CRC can only run on AMD64/Intel64 CPUs and Apple silicon. This cannot be changed to CRC can only run on AMD64/Intel64 CPUs and M2 Pro

I meant the output from sysctl machdep.cpu.brand_string


Docks change size when tabbing in/out

Godot 3.1 alpha 4
I opened an empty project, and clicked on the Import and Scene tabs alternatively, and noticed that the size of the left dock changed size as I did this. Same for the right dock, for which tabs also move as a result.
This didn't happen in 3.0.6. It keeps happening even if I change the size using the vertical split.

possibly related to https://github.com/godotengine/godot/issues/23289

@girng no, this is not about alt-tabbing, but just clicking dock tabs alternatively.

@Zylann It is actually related, but more to the fix I made than the issue itself.
I suspect the Import and Scene dock not having the same minimum width, which could cause the split offset to be calculated differently depending on the dock.

It doesn't seem reproducible in the current master branch (at least on Import and Scene).


Add brief but explicit directions for creating the upstream Git rep

Section 8 tells the user to create an upstream Git repo but does not include explicit instructions.  Our audience may include people who do not set up Git repos all the time and might struggle with this.  A few brief instructions about how to do this, with perhaps a screenshot or two would solve the problem.
This could be partially solved if we provided a video to accompany this section and had the video show how to create the Git repo but the better solution is to include both text and video.

stale


error in code

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/hello-world-tutorial/run
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
The tutorial tells to use dotnet watch to start the application, instead of dotnet watch run

I need to change the tutorial to be more clear that it needs .NET 6 SDK in order for it to work as written. So, you can use dotnet watch run if you're using .NET 5 or download .NET 6 SDK for the tutorial to work as-is.


prefer standard functions over external dependencies

This PR fixes three issues, two happens to be related to generator functions middleware.
While this functionality will be removed completely in Koa 3.0, the next major version is not on the radar yet (unfortunately), but these small changes will make Koa a little bit faster and safer today.

Use util.types.isGeneratorFunction when available (Node >= 10) instead of loading external dependency.

Remove depd dependency and use process.emitWarning. depd is huge for the purpose  - it's 500+ lines of code (twice as big as Koa' application.js) and used just once - to deprecate generator middleware. process.emitWarning coupled with --no-deprecation and --trace-deprecation command-line flags resulting in the same functionality while having one less external dependency to load.

Use standard (since Node >= 10), Stream.finished instead of external on-finished module when supported. This required small change in context mocking to actually create stream (I think that was necessary anyway for correctness)

i think it is ok, please merge. when to merge?

closed by https://github.com/koajs/koa/commit/b747e16d75554203a28e55d87296e81f68b992f5


[OSSALifetimeCompletion] Handle unavailable blocks in dead-end regions.

Not every block in a region which begins with the non-lifetime-ending boundary of a value and ending with unreachable-terminated blocks has the value available.  If the unreachable-terminated blocks in this boundary are not available, it is incorrect to insert destroys of the value in them: it is an overconsume on some paths.  Previously, however, destroys were simply being inserted at the unreachable.
Here, this is fixed by finding the boundary of availability within that region and inserting destroys before the terminators of the blocks on that boundary.
rdar://116255254

@swift-ci please test

thank you!


Log major function calls to improve logfile readability

We should log each function call and the args that were passed. All are strings/ints so should be easy to read in the log itself. Something like:
# Connect("...", "...")
TYPE I
200 Command okay.

# UploadFile("...", "...", FtpExists.Overwrite)
SIZE FlashDisk/TestStand/EthNamedPipeConnector.exe
500 Syntax error, command unrecognized.
EPSV
229 Entering extended passive mode (|||49461|).
STOR FlashDisk/TestStand/EthNamedPipeConnector.exe
125 Data connection already open; transfer starting.
226 Closing data connection.

# DeleteDirectory("....", true, false, FtpVerify.None)
PWD
257 "/".
TYPE I
200 Command okay.
EPSV
229 Entering extended passive mode (|||49465|).
LIST /FlashDisk/TestStand
125 Data connection already open; transfer starting.
05-19-17  13:03                32768 EthComConnector.exe
05-19-17  13:03                23040 EthComLib.dll
05-19-17  13:03               461312 EthNamedPipeConnector.exe
226 Closing data connection.
Disposing FtpSocketStream...
Confirmed format Windows
DELE /FlashDisk/TestStand/EthComConnector.exe
250 Requested file action okay, completed.
Disposing FtpSocketStream...
DELE /FlashDisk/TestStand/EthComLib.dll
250 Requested file action okay, completed.
DELE /FlashDisk/TestStand/EthNamedPipeConnector.exe
250 Requested file action okay, completed.

Done as of 17.4.3. Sample logs:
# Connect()
Status:   Connecting to <IP_ADDRESS>:21
Response: 220 You will be disconnected after 15 minutes of inactivity.
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 2 of 150 allowed.
Response: 220-Local time is now 03:19. Server port: 21.
Response: 220-IPv6 connections are also welcome on this server.
Command:  USER ***
Response: 331 User *** OK. Password required
Command:  PASS <omitted>
Response: 230 OK. Current restricted directory is /
Command:  FEAT
Response: 211 End.
Response: 211-Extensions supported:
Response: EPRT
Response: IDLE
Response: MDTM
Response: SIZE
Response: MFMT
Response: REST STREAM
Response: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response: MLSD
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: UTF8
Response: TVFS
Response: ESTA
Response: PASV
Response: EPSV
Response: SPSV
Response: ESTP
Status:   Text encoding: System.Text.UTF8Encoding
Command:  OPTS UTF8 ON
Response: 200 OK, UTF-8 enabled
Command:  SYST
Response: 215 UNIX Type: L8
Status:   Auto-detected UNIX listing parser

# UploadFile("D:\Github\hgupta\FluentFTP\README.md", "/public_html/temp/README.md", Overwrite, False, None)

# FileExists("/public_html/temp/README.md")
Command:  SIZE /public_html/temp/README.md
Response: 213 56985

# DeleteFile("/public_html/temp/README.md")
Command:  DELE /public_html/temp/README.md
Response: 250 Deleted /public_html/temp/README.md

# OpenWrite("/public_html/temp/README.md", Binary)
Command:  TYPE I
Response: 200 TYPE is now 8-bit binary

# GetFileSize("/public_html/temp/README.md")
Command:  SIZE /public_html/temp/README.md
Response: 550 Can't check for file existence
Command:  EPSV
Response: 229 Extended Passive mode OK (|||31852|)
Status:   Connecting to <IP_ADDRESS>:31852
Command:  STOR /public_html/temp/README.md
Response: 150 Accepted data connection
Response: 226 1.265 seconds (measured here), 43.98 Kbytes per second
Response: 226-File successfully transferred

# DownloadFile("D:\Github\hgupta\FluentFTP\README2.md", "/public_html/temp/README.md", True, None)

# OpenRead("/public_html/temp/README.md", Binary, 0)
Command:  TYPE I
Response: 200 TYPE is now 8-bit binary

# GetFileSize("/public_html/temp/README.md")
Command:  SIZE /public_html/temp/README.md
Response: 213 56985
Command:  EPSV
Response: 229 Extended Passive mode OK (|||41233|)
Status:   Connecting to <IP_ADDRESS>:41233
Command:  RETR /public_html/temp/README.md
Response: 150 55.6 kbytes to download
Response: 150-Accepted data connection
Response: 226 0.547 seconds (measured here), 101.75 Kbytes per second
Response: 226-File successfully transferred

# Dispose()
Status:   Disposing FtpClient object...
Command:  QUIT
Response: 221 Logout.
Response: 221-Goodbye. You uploaded 56 and downloaded 56 kbytes.
Status:   Disposing FtpSocketStream...

Implemented in https://github.com/hgupta9/FluentFTP/commit/8c9bd881a33bc99eb61d45528898e1ca24cfbe63


Model arguments

Is there no way of passing arguments that configure the temperature, tokens, and even the model to be used?

It's a chatGPT wrapper not a GPT3 api wrapper...


Add state estimation methods

I've been looking a little bit into this and it would include the eigen C++ library for stuff like kalman filters or controller-observers for motor control.. this would work for the arm motors (I think)
I'm not sure if these tools are commercial off the shelf already

For anyone who's interested, these links are a good starting point
https://forum.kde.org/viewtopic.php?f=74&t=129652
https://github.com/bminerd/Kalman/blob/master/KalmanFilter.h

No longer needed with the RMD-X7 motors as they have a PID and state estimation system built in.


new release needed

Several changes have been made since the last release that has been more than one year ago.
A new release should be made and released to hex.pm. Right now is not possible to push software that depends on this library on hex.pm due to this reason.

Here, I just finished changing all dependencies to be from the hex registry. Tell me if it works well with you: https://hex.pm/packages/cqerl


README: Needs updating

This is basically a constant state of affairs as changes get made.  This issue is a reminder to adjust the README before a public-ish release.

Brought the README up to date with the current state of the repo (or how it will be in a couple days).  Others should check it for mistakes and omissions.


x/text: case folding differs from ICU

What version of Go are you using (go version)?
1.16.6
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using?
linux/amd64
What did you do?
Given this string: "Ꮖ-Ꮩ-Ꭺ-Ꮹ-Ꭼ-Ꮮ", convert it to lower case via x/text/cases.Fold().Bytes(...). This produces a valid but unexpected result (and many common fonts don't contain characters for the output).
What did you expect to see?
I expected the characters to go through unchanged. That's because x/text/cases claims to comply with Unicode version 13. ICU (I tested v63.2 and v66.1), which include Unicode 13 and below, leave the text unchanged when passed to ICU's u_strFoldCase.

Duplicate of #46101


Respect the actual line indent size instead of the defined indent_size

I'm not sure if this is a bug or a feature, but right now instead of using the defined indent_size if you are typing in a line that is already indented the indent size used is the one of the actual ones and not the one in the configuration.
Steps to reproduce:

Create a file like this one

def foo():
    print('hello world')

Pressing enter with the cursor in the line 1 the new line will have 2 spaces.
Pressing enter with the cursor in the line 2 the new line will have 4 spaces.

Involved .editorconfig-files
root = true
[*]
indent_size=2

Directory structure
.edittorconfig
foo.py

Hi @fpuga - thanks for getting in touch. I will take a look at this (i guess next week), but i fear this isn't anything we can handle in this package. The reason is that we're setting the buffer's indentation in a general setting and Atom is applying the settings to the newlines independently.

Thanks for sharing your thoughts. As I say, this can be the expected behaviour for some users. Maybe is just a matter of taste. For example, emacs, also have some weird behaviours in this topic. If the electric-indent-mode is enabled (and it is by default), when you press enter on a line, the current line and the next line are both indented. So I understand that it does not have an easy fix.

Thanks for that hint @fpuga - this sounds pretty interesting. I think editorconfig doesn't cover that feature in general but i'll have a look.

Closing as Atom is abandoned.


travis-ci breaks on dump

when testing the dump api function the build breaks very often.

must have been something with the docker test. but rspec uses only vcr. so dropped the docker stuff.


Source-build patch removal for SDK.

@crummel commented on Mon Jun 10 2019
Source-build has some patches that we are currently applying to your repo.  This issue tracks removing the patches.  These patches can be found at https://github.com/dotnet/source-build/tree/release/3.0/patches/sdk.
Patches that have the responsibility "Repo" and the Disposition "Incorporate" are patches that we believe are valid source-build fixes that should be moved into your repo.  Please let us know if these don't seem like good patches.  Any changes with the responsibility "source-build" is something that we plan to keep going forward or integrate in another way - please also let us know if you think there may be problems with those patches.

Patch name
Type
Disposition
Responsibility
Notes

sdk/0001-Upgrade-to-netcoreapp2.1.patch
ToolCompat
Incorporate
source-build
May go away with SDK uptake.  Otherwise needs investigation similar to   nuget-client/0001

sdk/0002-Add-missing-PlatformAbstractions-reference.patch
Bug
Incorporate
source-build

sdk/0003-Consolidate-versions.patch
Coherence
Incorporate
source-build

@nguerrera commented on Tue Jun 25 2019

sdk/0002-Add-missing-PlatformAbstractions-reference.patch

Not really sure why this is necessary. It is a transitive dependency. If the packs coming in are source built, they should point to the right source built version as a dependency. But it's harmless, so I'll accept it.

@nguerrera commented on Tue Jun 25 2019

sdk/0003-Consolidate-versions.patch

This has to be done carefully, the version used by other components must match. Particularly Microsoft.NET.HostModel and some razor tooling as well I believe. This is due to binding redirect issues with msbuild tasks on desktop.

@nguerrera commented on Tue Jun 25 2019

But it's harmless, so I'll accept it.

I take that back, picking a specific version adds more binding redirect risk for netfx build. Also, it would need to be changed to prevent copying for netcoreapp case. I don't think it is necessary.
@crummel Can you give me steps to validate these changes. I want to understand why these were done better. The comments in the patches do not tell the whole story.

@crummel commented on Tue Jun 25 2019
0003 I'll switch to our responsibility, it was a coherence issue so I'll look into that further.  If 0002 is a transitive dependency then it's probably a similar issue - should we be using the built version of PlatformAbstractions or is that something that should be constant?

@nguerrera commented on Tue Jun 25 2019
It needs to be the built version because it appears in the output of the build for net4x case. I would expect that the source-built DependencyModel would pull in the source-build PlatformAbstractions transitively. S.R.M also needs to be source built and we need to make sure that core-setup and the web sdk(s) get pushed the same version.

@crummel commented on Tue Jun 25 2019
Ok, I will check on what DependencyModel and S.R.M are doing, I'll probably be pestering you about this shortly.  I'll move this issue to source-build since these are all our patches now.

Being done as part of #1141.


Get user profile information from cognito id token

Describe the task
Think maybe we could start try to get the user profile information from the Cognito id token. So far we only have the IDIR userID in the id token, maybe we could see if we could grab the display name and the email by adjust the Cognito config in the terraform for FAM.
Acceptance Criteria

[x] Remove the hardcode data in the profile
[ ] Add display name and email to the id token return by Cognito
[ ] Display the userID and display name and email get from the id token to the profile section
[ ] Test and confirm with IDIR only at this time

Additional Info

Frontend only

Hi @OlgaLiber2 not sure what avatar we should use for the user, I just use the first two letter in the IDIR username and shows as an avatar for now. Background color and text color are hardcoded to use the blue and white we use for the header.
Private Zenhub Image

Works in DEV:
Private Zenhub Image


add contributors images to readme

Closes #3

Thanks for the hint. It has been added

Congratulations on the HacktoberFest contribution


Publish to Maven Central

https://blog.gradle.org/jcenter-shutdown

yeah please publish this library to mavenCentral so that we can continue using it.


upgrading to development fails

You're probably already aware of it? Otherwise, see below:
(base) [pela09@vs476 ~]$ bcbio_nextgen.py upgrade -u development --tools --data
Upgrading bcbio
Collecting package metadata: ...working... done
Solving environment: ...working... done

## Package Plan ##

  environment location: /usr/local/share/bcbio/anaconda

  added / updated specs:
    - bcbio-nextgen[version='>=1.1.5']

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    bcbio-nextgen-1.1.6a       |           py36_0         2.1 MB  bioconda
    ------------------------------------------------------------
                                           Total:         2.1 MB

The following packages will be UPDATED:

  bcbio-nextgen                                1.1.5-py36_0 --> 1.1.6a-py36_0

CondaFileIOError: '/usr/local/share/bcbio/anaconda/pkgs/bcbio-nextgen-1.1.6a-py36_0.tar.bz2'. contains unsafe path: bin/bcbio_nextgen.py

Traceback (most recent call last):
  File "/usr/local/share/bcbio/tools/bin/bcbio_nextgen.py", line 221, in <module>
    install.upgrade_bcbio(kwargs["args"])
  File "/usr/local/share/bcbio/anaconda/lib/python3.6/site-packages/bcbio/install.py", line 60, in upgrade_bcbio
    anaconda_dir = _update_conda_devel()
  File "/usr/local/share/bcbio/anaconda/lib/python3.6/site-packages/bcbio/install.py", line 297, in _update_conda_devel
    ["bcbio-nextgen>=%s" % version.__version__.replace("a0", "a")])
  File "/usr/local/share/bcbio/anaconda/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/local/share/bcbio/anaconda/bin/conda', 'install', '--quiet', '--yes', '-c', 'bioconda', '-c', 'conda-forge', 'bcbio-nextgen>=1.1.5']' returned non-zero exit status 1.

Heya-- I can't reproduce this error on our installation. Does this give you any clues: https://github.com/conda/conda/issues/8423 in particular this comment? https://github.com/conda/conda/issues/8423#issuecomment-475702893


Move WithInterFont to the global Avalonia namespace

To keep it in line with other AppBuilder extensions, keeping Program.cs file simpler

You can test this PR using the following package version. 11.0.999-cibuild0032742-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]