Backwards-compatability tests

#503 broke the backwards-compatability tests and since we don't guarantee backwards-compatability we kinda disabled them by just running with the current decoder.
My question is now if we should just remove these tests all together since we don't guarantee it anyways, or if we should pin it to the current version of the decoder?
I am fine with both with a slight preference for removing.

While thinking about it again I thought that it is already valuable to know how backwards-comaptible our output is. So keeping the tests around gives us this certainty if someone ever comes around and wants to know this.

@jonas-schievink what are your thoughts?

The purpose of those tests was to make sure that the earliest semver-compatible defmt release can still decode what the current git version produces. The result here does not necessarily have to match 1-to-1 (so the changes to the output were fine), but I can see that that does fail the tests at the moment. Not totally sure how to do this better, maybe we just have to check that the decoder didn't fail?

So I think it would work if we just always install probe-run from main and check that the decoding doesn't fail? Thereby we make sure we don't loose decoding functionality, but enable PR authors to alter the output.

I think we'll need to revise those backcompat tests after #287 is implemented because after that the behavior is going to be:
breaking changes in the encoding / decoding are allowed in patch versions (but breaking API changes are not); using defmt 0.3.x anywhere in the dep graph = you use the latest patch version of defmt = no breakage in code because of the 'no breaking API changes'; probe-run will error (or maybe it will work but not print any logs?) and tell you to upgrade it if it sees a defmt patch version newer than what it supports.
so using the v0.3.x encoder with the 0.3.0 decoder (which the backcompat tests tested) is not something that's going to be part of  the workflow anymore

After #287 we should additionally to the output-format also check backwards-incompatible changes to (quoted from the PR): "the symbol naming scheme, the symbol and section layout, the data encoding / wire format".

I think what we need to do here to test for changes that break backwards compatibility (after #540) is, at a high level:

add a new xtask, say test-backcompat
this xtask will run the same set of firmware examples as test-snapshot BUT

it will use an "old version" of qemu-run
it will not check the output (stdout/stderr) of qemu-run
it will check the exit code of qemu-run; it should be 0 (success) in all cases
if qemu-run fails, the xtask must indicate which test failed and print whatever qemu-run printed -- so we can figure out where decoding failed

By "old version" of qemu-run I mean a version that uses the oldest git commit of defmt that last bumped this version number.
how to install an "old version" of qemu-run? The easiest way is to run cargo install --git https://github.com/knurling-rs/defmt --rev $git_hash but this is not great for running CI locally because it will override any local qemu-run (though it's unlikely people have that tool installed). An alternative that does not do that would be nice but not a deal breaker.
how to use an "old version" of qemu-run? in the firmware/qemu directory, cargo run is configured (see .cargo/config.toml) to use the local, i.e. latest version, of qemu-run. To override this one can set the CARGO_TARGET_${target_triple}_RUNNER env var. Like this:
$ CARGO_TARGET_THUMBV7M_NONE_EABIHF_RUNNER=path/to/binary cargo run --bin hello

Note that you need to specify the target triple in UPPERCASE letters.
What do we when this test-backcompat test breaks in a pull request?

temporarily disable the test-backcompat test to land the PR
in a follow-up defmt PR

bump the defmt version number in src/lib.rs
update xtask to use the commit hash of the pull request merge that broke backcompat


Update outputs for foundations/environments example

Outputs have been uncommented and updated

Nice catch, this completely slipped my radar. :)


xcode error profile doesn't match the entitlements file's value for the application-identifier entitlement.

I must say RNUC is the easiest and neatest env config for React Native as right now. Thank you @maxkomarychev for this great package!
Everything works like a charm for me after closely following the instructions except XCode wouldn't treat my qa and prod env configs as different apps even though they have different bundle identifiers and display name. Whenever I switch the env, Xcode always tries to upgrade the previous install on the device and then with the failed installation error message: profile doesn't match the entitlements file's value for the application-identifier entitlement.

hey, thanks for kind feedback :)
regarding you problem: could you please share more information?
what exactly is your setup? do you use CLI to switch environments or did bind env to schemes? what does "tries to upgrade the previous install" exactly? does that mean it overwrites app in previous environment? do you keep xcode open when executing command (in case if switching with command line)?

Hi @maxkomarychev, I used CLI to switch environment before I build the app in Xcode. After running the npm run runc .env.qa, I do see bundle IDs and display names are being changed correctly in the general tab.
Yes, Xcode is trying to overwrite the app in the previous environment. It would not install a new app. Eg. If I switch from prod to qa, it will try to overwrite the prod app but with the error I mentioned. And the same if I switch from prod to qa.
Yes, I kept Xcode open when switching. Let me try running the config with xcode closed.

Just tried running the config with xcode closed. Still getting the same error in Xcode.
"This application’s application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed."

do you have both apps installed when running build in xcode?
what kind of entitlements do you have? (push? keychain? etc)
if you do have entitlements file you might need to have different file per environment, this is possible to configure with this lib
can you try running app via react-native CLI?

any chance you can share screenshot of your entitlements file with masked data?
btw, maybe this helps https://developer.apple.com/library/archive/qa/qa1710/_index.html ?
xcode does not play well if xconfig is regenerated on the fly so its best to reopen it when switching environments

Nope. Only one app can be installed at a time. Cannot install both from Xcode. The goal is to install both apps on the same device.
I have push notification entitlement and background modes/remote notifications entitlement.
I do see something weird about my entitlement file: myapp.entitlements. It has none of the push notification capabilities I added under signing and capabilities tab.  Does this look correct to you? If it is, how do I make a different file per environment. Btw, I'm using the latest XCode 11.5 and React-Nave 0.60.6

aps-environment
development

Running the CLI I didn't receive the error, but the app is upgraded from prod to qa instead of installing a separate app.

Does this look correct to you?

	<key>aps-environment</key>
	<string>development</string>

this is related to push notifications, looks good to me

Running the CLI I didn't receive the error, but the app is upgraded from prod to qa instead of installing a separate app.

are you running app with CLI on the device or simulator?
have you enabled push capabilities for both qa and prod apps?

The issue is now gone. I revoked the QA identifier, and created a new identifier and provisioning profile in my Apple dev account. And now XCode builds QA and Prod as separate apps now. I suspect it has to do with the automatic signing. The old QA identifier had exactly the same setup, but it didn't recognize it as a different identifier.
Indeed there's nothing wrong with RNUC, but Xcode settings and configuration issues.
Thanks for your help and patience @maxkomarychev !


Missing icons

Describe the bug
There are a bunch of new google icons missing, would be lovely if you could add them.
Reproduction
Like Trophy
https://fonts.google.com/icons?selected=Material+Symbols+Outlined:trophy:FILL@1;wght@400;GRAD<EMAIL_ADDRESS>import Trophy from 'svelte-google-materialdesign-icons/Trophy.svelte';
Version and System Info
System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1
    Memory: 97.00 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
    pnpm: 8.8.0 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 128.0.6613.120
    Safari: 17.5
  npmPackages:
    @sveltejs/kit: ^2.0.0 => 2.5.24
    svelte: ^4.0.5 => 4.2.19
    svelte-google-materialdesign-icons: ^1.0.5 => 1.0.5
    vite: ^5.0.0 => 5.4.2

Ah, maybe a hassle, but possible to switch to the newer lib?
https://github.com/google/material-design-icons/tree/master/symbols/web

Thank you for the link. The problem is that there are too many files. When I publish an npm package, more than 4000 files fails to process it.


⚠ SkyfallMC Minecraft Server has degraded performance

In e7c2593, SkyfallMC Minecraft Server (play.skyfallmc.ga) experienced degraded performance:

HTTP code: 200
Response time: 3603 ms

Resolved: SkyfallMC Minecraft Server performance has improved in 66773e2.


Duplicate MutatingWebhookConfiguration

Describe the bug
There are currently two MutatingWebhookConfiguration resources in the chart (defined here), but they have the same name. While helm ignores this, k8s will (probably) apply only the second one, overwriting the first. But, crucially for me, when trying to inflate the helm chart using kustomize it (properly) fails saying that a resource with that ID already exists.
Expected behavior
The two webhook configurations should have unique names.
To reproduce

Create a folder connaisseur and place these two files inside:

a kustomization.yml file:
namespace: connaisseur
resources:
  - namespace.yml
helmCharts:
  - name: connaisseur
    repo: https://sse-secure-systems.github.io/connaisseur/charts
    namespace: connaisseur
    version: 2.5.0

a namespace.yml file:
apiVersion: v1
kind: Namespace
metadata:
  name: connaisseur

Run kustomize build connaisseur --enable-helm and get the following error:
Error: could not parse rnode slice into resource map: may not add resource with an already registered id:
MutatingWebhookConfiguration.v1.admissionregistration.k8s.io/connaisseur-webhook.[noNs]

Versions:

OS: Ubuntu 24.04
Connaisseur: 3.5.0
Connaisseur Helm chart: 2.5.0
Helm: v3.15.0-rc.2
Kustomize: v5.4.2

Additional context
The two webhook configurations do differ in their annotations, but that is not enough to make them unique.
Currently they are defined as:
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  name: {{ include "connaisseur.webhookName" . }}
  labels:
    {{- include "connaisseur.labels" . | nindent 4 }}
  annotations:
    "helm.sh/hook": post-delete
    "helm.sh/hook-delete-policy": before-hook-creation, hook-succeeded, hook-failed
...
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  name: {{ include "connaisseur.webhookName" . }}
  labels:
    {{- include "connaisseur.labels" . | nindent 4 }}
  annotations:
    "helm.sh/hook": post-install, post-upgrade, post-rollback
...

Hoy @graipher. The two webhooks with the same name are intended. The reason for that is a bit complicated:
Connaisseur is a admission controller that runs inside the k8s cluster and is hooked up into k8s with a so called mutatingwebhookconfiguration. When this configuration is applied, k8s expects Connaisseur to up and running and do its job. Should that not be the case, e.g. Connaisseur is not yet installed, then k8s will block all resources that Connaisseur would handle. This includes all workloads with image references. Essentially you brick your whole cluster with an active mutatingwebhookconfiguration and no running Connaisseur (you need to manually delte the mutatingwebhookconfiguration).
In order to avoid this situation, we set up the Connaisseur installation, so that the mutatingwebhookconfiguration is only applied after Connaisseur was successfully installed (if we do it during Connaisseur installation, we might run into race conditions, where Connaisseur needs to be applied faster then the mutatingwebhookconfiguration, because the mutatingwebhookconfiguration could block Connaisseur itself). Applying it after the Connaisseur installation is achieved with the helm hooks (e.g. post-install or post-upgrade). Now we run into the next problem: since the mutatingwebhookconfiguration isn't part of the regular helm installation step (this is because its defined as a helm hook), it won't be uninstalled when running helm uninstall, thus yet again creating the situation where we have a mutatingwebhookconfiguration without Connaisseur running -> clusters broken until the mutatingwebhookconfiguration is manually deleted.
How do we solve this problem? The helm hooks have so called delete policies, that automatically delete the given resource in configurable circumstances. We can't set those policies for the regular mutatingwebhookconfiguration, because otherwise the mutatingwebhookconfiguration would be delete after installing Connaisseur, redering the admission controller useless (Connaisseur needs to be hookup into k8s to function). Instead we overwrite the mutatingwebhookconfiguration with another one, but only on the post-delete helm hook (so after someone tries to run helm uninstall). This one has the delete policy set, so it deletes the resource afterwards.
With this setup we achieve our two main goals:

the mutatingwebhookconfiguration is applied only after Connaisseur is successfully installed
the mutatingwebhookconfiguration is removed once Connaisseur gets deleted with helm uninstall

We also aechive all of this without any users needing to manually apply/delete the mutatingwebhookconfiguration.

Now for your problem .. maybe there is still a solution. Does kustomize alle overwritting the values of the helm chart?

Hey @phbelitz, thanks for the explanation! When I saw that helm hooks are involved, I knew there might be a reason for it, but I was hoping it was just an oversight that the names are actually identical.
Yes, kustomize does allow the values of the helm chart to be overwritten by supplying a values.yml file. Here is the not stripped down version of my kustomization.yml:
namespace: connaisseur
resources:
  - namespace.yml
helmCharts:
  - name: connaisseur
    repo: https://sse-secure-systems.github.io/connaisseur/charts
    releaseName: connaisseur
    namespace: connaisseur
    valuesFile: values.yml
    version: 2.5.0
    includeCRDs: true

Currently I only configure the application.validators list to include my own public key for the private images.


Flamingos at Minecon?

I installed the Flamingos mod but cannot find any flamingos at minecon - is this a known bug or have they just been removed from worldgen?

They, in fact, have never been added. Blame Minecraft.


Option to search only in personal/organisation repositories

Hello there,
It would be useful to be able to disable Github-wide repository searches in the settings, so when you search only personal/organisation repositories are shown.
Another observation: when searching for repositories of my organisation, the results are incomplete: some repositories that satisfy the search query are displayed, but not all of them. Even when I detalise the search query, some repositories are not displayed. I am not sure if it is a bug or not, I don't know if there's some kind of condition that makes a repo to show up.
Thank you for your hard work.

We'll have to look more into the feasibility of searching personal/organization repos (given the GitHub search apis), but I think it's a good idea to have that option.
As for missing results, we are kind of a the mercy of the GitHub search apis -- and depending on the number of results they can be truncated (and the order is seemingly unstable). If you search for <user-or-org>/<repo> we will limit the results to that user/org so that might help in getting better results.

We'll have to look more into the feasibility of searching personal/organization repos (given the GitHub search apis), but I think it's a good idea to have that option.

Great, thank you!

If you search for / we will limit the results to that user/org so that might help in getting better results

I did exactly this and it didn't work. Suppose, I am part of the organisation called TheRoundTable and I have 5 repositores: trt-logger, trt-plugin, trt-engine, etc. When I searched for TheRoundTable/trt- I only saw two results instead of five. Weird, huh?
I understand that you're relying on Github API and there might be no way to address it in Remote Repositories extensions, so I guess my main point is about disabling Github-wide search.

@arsinclair If you go to https://github.com/search/advanced, and set From these owners box to TheRoundTable and set the Advanced search box to trt- do you see the same issue?

@arsinclair If you go to https://github.com/search/advanced, and set From these owners box to TheRoundTable and set the Advanced search box to trt- do you see the same issue?

No, all results are displayed.


[FLINK-29888][streaming] Reimplement checkNotAllowedConfigurations using refactored CheckpointConfig and ExecutionConfig

This PR depends on FLINK-29379, so please ignore a couple of first commits that are being reviewed in https://github.com/apache/flink/pull/21245
After FLINK-29379 we can re-implement checkNotAllowedConfigurations to produce better exception messages.
Instead of a generic "Configuration object ExecutionConfig changed", without a hint of what has been modified,
we can report what ConfigOption has been changed.
Verifying this change
This change is partially covered by existing tests but also expands StreamContextEnvironmentTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure


[extractor/bandcamp] Add album_artist metadata (#5536)

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

This patch adds an album_artist metadata field in the BandcampIE extractor class by scraping the track's webpage for the name of the artist who owns the album. This makes it easier to download albums into an artist/album/track.mp3 directory structure when downloading compilation albums (tracks of varying artists).
Fixes #5536
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

No. I will squash everything before merge. So commit messages don't really matter

@pukkandan Oh jeez I committed the wrong bit. That's embarrassing. Fixed!

Added myself to the contributors doc too if that's alright.

@pukkandan ping - just letting you know PR is ready for review again

Pls update tests

Updated to include tests in the BandcampIE class. Running python test/test_download.py TestDownload.test_Bandcamp locally gave me errors for pretty much every other test in the _TESTS list.  Confusing but I just commented them out and wrote a test that covers a track with a differing artist/album_artist that passes.

The test suite wasn't as strict till recently. So many of the tests are incomplete by current standards. It's expected to be fixed when we work on the extractor. Also, due to the nature of extractors, tests often break due to factors outside our control. In that case, we have to manually check and fix the test definitions.


pageSize not updating

I believe it's happening because of https://github.com/tannerlinsley/react-table/blob/master/src/index.js#L146-L150
We have new pageSize in state variable, but it's overwritten by this.props with old pageSize value. Because of that following shouldComponentUpdate returns false, so despite new pageSize in state component is not re-rendered.

How are you setting/changing pageSize exactly? Can you post your component here?

I've developed custom pagination and this behaviour appeared after update from 3.2.1 to 4.4.1.
This is how I'm updating pageSize — https://gist.github.com/DimitryDushkin/ff76572d5f1efe2b642206171a5290fb#file-reacttablepagination-jsx-L78
I'm sure that correct number is passed to this function.

That's strange. This should work from what I saw in your gist. What props are you sending the table when you render it?

@tannerlinsley sorry for worry.
I've set pageSize prop by myself instead of defaultPageSize that's why changing it via pagination component didn't have effect.


I am missing an example library

Issue description
The documentation on creating an OSS library is absolutely amazing and inspiring! However, 1 thing that would make this even better would be an example library/libraries using all these features!
My suggestions:

a library that uses the strategy described by the articles.
A great readme that can be used as a template by others. Include some badges, etc.
github templates for easy issue creation.
git flow (or another good, recommended branching strategy) with pull requests and CI/CD that builds and tests your code. Adding things like dependency checker bots would be even better. Perhaps on a main/master PR completion it would create a new version as a github release, tag, nuget version, etc.. Perhaps add pre release version support

Add automatic/easy versioning support.

I would love multiple example libraries, including one that uses an asp.net core feature.
Target framework
None

This is a good idea @sander1095
Tagging @tdykstra @IEvangelist
Let's discuss this for .NET 6. and guidance for open source developers. We could probably use one of the .NET Foundation projects as a example case study.


Multiselect: drop-down arrow is not clickable to close drop-down when max selections is showing

To Reproduce
Steps to reproduce the behavior:

Go to https://www.consumerfinance.gov/about-us/blog/
Click on five items in the "topics" drop-down so the "Reached the maximum of five selections" message.
Click the down arrow icon and see that the drop-down is not closed, as it is before the max is reached.

We talked about making the multiselect a web component, this could be addressed as part of that work


Feat checksum merge to Develope

This is mainly open to troubleshoot Gitstats for now

Ok, that sounds like it might have been related to the anonymizer thread safety. I'll hold off my approval til we get the refactor PR merged as it will, I think, resolve your nonreproducible bug (probably just difficult to reproduce)

I don't understand this one..
W0301 15:05:36.155704 PluginsManager.cpp:258] Registering plugin 'data-anonymizer' (version 0.5)
 Failure during '[PREPARE UpdateChecksum]': ERROR:  relation "attachedfiles" does not exist
 LINE 1: UPDATE attachedfiles SET uncompressedsize = $1, compressedsi...

The last commit doesn't touch any SQL.. and the one before passed..

I'll update the docker-compose.yml for github tonight to utilize a pre-built image. Then we can merge this PR.


AttributeError: 'HTML' object has no attribute 'next'

I try these codes from document online:
>>> r = session.get('https://reddit.com')
>>> r.html.next()

catch exception error like the title says:

AttributeError: 'HTML' object has no attribute 'next'

OS: Ubuntu17.10 Python: 3.6.2 IDE: ipython
Is it a up-to-date feature?

@zhang-win This code works perfectly fine with me. Please double check at your end!
from requests_html import HTMLSession session = HTMLSession() r = session.get('https://reddit.com') r.html.next()
Result:
'https://www.reddit.com/?count=25&after=t3_86l0nt'

I fixed this on #146; while it gets merged you can use r.html._next().

This was already solved, you can install from the repository or wait for the new release.

v0.10.0 was released yesterday fixing this bug.


Object owntracks.0.locations.home.timestamp

"owntracks.0.locations.xxx.timestamp" is too short.
When converting this date comes: "1970.01.19 01: 46: 29.535".
If you add 3 zeros to the timestamp, it will work correctly.

Timestamp is 10 digits long (seconds since Jan 01 1970). Adding 3 digits turns it to milli-seconds.

With the new release (see https://github.com/iobroker-community-adapters/ioBroker.owntracks/issues/18) all timestamps and milli-seconds will be converted to date-time as well.


Mapzen problem

Dear Jonatawalker,
Thank you so much for the job done.
It works well for me using Nominatim / OSM service, but when I try to use Mapzen / Pelias, I have a message saying I have no connection.
After a short investigation, the problem comes from the fact the api keyword expected by mapzen is 'api_key', while ol-geocoder only use 'key'.
I modified the local code on my server, but you should update the source code to prevent such a problem.
Regards.
Rémi

Thanks @rbonnefoi for reporting. Fixed with #142.


Unnecessary import and Code Duplication in core/log.py

I think that the core/log.py has some unnecessary import from the core.config and core.config_builder
from core.config_builder import default_paths
from core.config import _paths
from core.config_builder import _builder`

also, there is a repeat in the first nested if condition violating the DRY principle
    if version() == 2:
        if isinstance(data, str):
            try:
                log = json.loads(data)
            except ValueError:
                log = ''

        if isinstance(log, dict):
            if final:
                with open(filename, mode) as save:
                    save.write(data + '\n')
            else:
                submit_logs_to_db(language, data)
        else:
            if not final:
                flock = lockfile.FileLock(filename)
                flock.acquire()
            with open(filename, mode) as save:
                save.write(data + '\n')
            if not final:
                flock.release()
    else:

        if isinstance(data, str):
            try:
                log = json.loads(data)
            except ValueError:
                log = ''

OS: Ubuntu
OS Version: 18.04
Python Version: 3.6.9

closed by PR #349

closed by PR #349


Not seeing console messages when pushing puck.js button

puck-remote installs for me (Mac OS X Mojave) but running node index.js does not log battery values like the github page says it should.
I did npm install and see the warning:
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/bluetooth-hci-socket):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux,android,win32","arch":"any"} (current: {"os":"darwin","arch":"x64"})

Running on my Mac, not a Raspberry Pi.
I did disconnect from the espruino web ide after deploying the sketch.
Using node v8.15.0 because npm install reported a build failure otherwise. I am using nvm to manage node.js installs.
The LEDs glow the right colors after the button pushes (1, 2, 3) but no advertisement messages appear in the console.

I came back to my puck.js, re-deployed the sketch, disconnected and ran node index.js. Now the LEDs no longer illuminate. Could I have a low battery already?

I am using 2v01 firmware on the Puck in case that matters.

I'm not an expert on the Puck. I got this working on the Pi. I simply can't remember if I ever tried it on my Mac, so I can't give any particular guidance until I have some spare time to dig it out and try. That isn't going to be for a while as I'm on vacation.

Thanks for the update. I will try on my Pi and then see if I have the same experience there.
I will have to perhaps add some bluetooth support to the Pi with apt-get installs?
Enjoy your vacation -- didn't mean to interrupt.
Jim
On Feb 19, 2019, at 5:10 PM, knolleary <notifications<EMAIL_ADDRESS>wrote:
I'm not an expert on the Puck. I got this working on the Pi. I simply can't remember if I ever tried it on my Mac, so I can't give any particular guidance until I have some spare time to dig it out and try. That isn't going to be for a while as I'm on vacation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fknolleary%2Fpuck-remote%2Fissues%2F1%23issuecomment-465331677&data=02|01|james.j.solderitsch%40villanova.edu|7f89de622f8446517fba08d696b71d0b|765a8de5cf9444f09cafae5bf8cfa366|0|0|636862110539611370&sdata=HpocNrZeE3AGvpeONa8DSeALUQjtZnjmejL5oqag8NE%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWBYJEXQNf-dkTCrBzgrgakzgfFL5RjIks5vPHZsgaJpZM4bDklo&data=02|01|james.j.solderitsch%40villanova.edu|7f89de622f8446517fba08d696b71d0b|765a8de5cf9444f09cafae5bf8cfa366|0|0|636862110539611370&sdata=pyXFcW9lVrpap6HBdOo6rdjMDifScY9TX9mlSLNh9ZY%3D&reserved=0.

Turns out that noble is broken for Mac running the latest OS X Mojave. There are open issues reported in the githib project.
But there is a parallel project noble-mac:
https://github.com/Timeular/noble-mac
and if you make the dependency for this project be noble-mac instead of noble then things mostly work.

I also tried this on my Pi using a fresh install of Raspbian Stretch and the original code works there.


Bug: Loading plugin fails

Type (choose one):

Bug

NPE version:  <IP_ADDRESS>
Installed from: ClickOnce
In case of a BUG:
Loading a plugin fails. Works with <IP_ADDRESS>.
Error: Could not load file or assembly 'NuGetPackageExplorer.Types, Version=<IP_ADDRESS>, ...'

To reproduce just open the plugin dialog and try to add a feed plugin.
No workaround possible.

could you check which dlls are present in the installation directory/

Can confirm this one.

@Sam13 could you test it by changing
in NuGetPackageExplorer.exe.config
change 3.10 -> 3.12 (twice) in <bindingRedirect >
from:
So
           <dependentAssembly>
                <assemblyIdentity name="NuGetPackageExplorer.Types" publicKeyToken="b33e3c54f0b885e9" culture="neutral"/>
                <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
            </dependentAssembly>

to:
           <dependentAssembly>
                <assemblyIdentity name="NuGetPackageExplorer.Types" publicKeyToken="b33e3c54f0b885e9" culture="neutral"/>
                <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
            </dependentAssembly>

@304NotModified Not able to load any plugin, different errors for each plugin. Also unable to load my own plugin which worked with 3.19 (loading all plugins worked there)...

I'll close this one then for now, but aside from getting ILSpy to work, we ought to think of what the plugin model should be going forward. Maybe what we have is fine, maybe it needs work.


kubeconfig file saved in JSON format

Don't know if it's an issue as other tools seems to work but online documentations mention YAML format

This issue was fixed using @kubernetes/client-node and js-yaml modules.


Add library to create test report manifest

Description
Add groovy library to trigger report workflow to create test report manifest. Upload the generated test-report.yml to the S3 test results bucket.
Issues Resolved
Part of https://github.com/opensearch-project/opensearch-build/issues/1274
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Just had a new commit to accommodate your suggestions. Please help take a look again. Thanks! @gaiksaya @rishabh6788


has no existing object, this might lead to an error in future versions

Node.js: v14.17.1
NPM: 6.14.13
JS-Controller: 3.3.15
Admin: 5.1.25
Linux-Control: 1.1.2
linux-control.0 | 2021-09-13 08:35:26.331 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions
linux-control.0 | 2021-09-13 08:35:26.329 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions
linux-control.0 | 2021-09-13 08:35:26.327 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions
linux-control.0 | 2021-09-13 08:35:26.324 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions
linux-control.0 | 2021-09-13 08:35:26.322 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions
linux-control.0 | 2021-09-13 08:35:26.319 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions
linux-control.0 | 2021-09-13 08:35:26.274 | warn | State<EMAIL_ADDRESS>has no existing object, this might lead to an error in future versions

Please delete all datapoints and restart the adapter


Cannot execute one-line installation as root

I got return Don't run this as root! when execute one-line installation as root, do I need to execute as other users instead of root?
$ sh -c "$(curl -fsSL https://raw.githubusercontent.com/Linuxbrew/install/master/install.sh)"
Don't run this as root!

Yes, that's correct. Run it as a different user than run, preferably a user with sudo access. One option is to create a linuxbrew user.


Prepare for simultaneous application rounds

This month, LargeLots will launch another call for applications, while the LargeLots team continues to review applications from the previous round. The app is not set-up to handle concurrent rounds. @evz and I talked about ways forward.
Option 1: Multiple deployment
Set up round-specific deployments. This solution entails:

create new Nginx and Supervisor configs (we'd have three of each, now!)
update deployment scripts
handle redirects for PPF submissions

Option 2: Name-spacing applications (Recommended)
Because a multi-deployment solution would complicate the PPF submission process, it seems more straightforward to namespace applications, allowing the site host one or more application rounds concurrently. Here's what it entails:

add a field to the Application model that indicates the pilot (could be a foreign key relation with a freshly created Pilot model)
write a migration that updates the current applications with the 2018 pilot, i.e., set the default value in the migration to whatever is in the settings
adjust the admin interface: allow logged-in users to toggle between pilots
adjust query for map on Index page: add a filter for the "sale pending" query

Timeline
I am going to start implementation on December 14 (tomorrow) and hand-off remaining tasks to @evz on Monday, if needed.
We plan to have this completed before the end of the day on Tuesday.
@hancush @derekeder - feedback welcome!

Checklist
Good news! The Application model had a field for saving the pilot all along.  I only need to modify the public and admin UI:

[ ] adjust the admin interface: allow logged-in users to toggle between pilots
[ ] adjust query for map on Index page: add a filter for the "sale pending" query


Feature/batch call filter

Description
Adding CallFilter to pallet-utility.
Motivation
The current form of the pallet uses frame_system::Config::BaseCallFilter, which does not allow to disable calls, which should not be used in this particular pallet.
Behavior
This PR adds call filtering at the pallet level. Filtering rules are similar to frame_system::Config::BaseCallFilter:

For Root Origin, filtering is disabled.
For Signed Origin, the frame_support::traits::Contains::contains method is used. If the result is true, then sp_runtime::traits::Dispatchable::dispatch is called, otherwise the error frame_system::Error::CallFiltered returned.

Only one nitpick: otherwise, the error frame_system::Error::CallFiltered is returned


Add Travis-CI configuration

Checks syntax of playbooks
Runs ansible-lint on playbooks

That's great!  I'm curious to try the lint command independently, but this should be good to merge.

ansible-lint mostly raises warnings AFAIK - I don't think it raises an error otherwise.

:+1: Any objections to my :merge: ?

No objections.  I just wanted to try out the ansible-lint command myself before merging, to verify how it behaves when there's a serious parsing issue.

Ah, I see.  I'll let you go ahead and do that.

This looks great.  If there's an actual parse error, ansible-playbook --syntax-check will obviously catch it, but ansible-lint will do the same.  It's good as it is, though, with the --syntax-check run distinguishing a parse error from other issues.  I will rebase this and merge it.

Actually, one final thing.  I think we want to add the travis build-status badge to the README.  I'll look into that, as well.


build on node 18

fix #149580
work in progress ...

[x] build/

[ ] build/lib/nls.ts - handle position not found error

downgrade to avoid "pure ESM" modules, to avoid dynamic import

got
node-fetch
p-all

use alternative to avoid "pure async" modules, to avoid API change to async

source-map-sync

@microsoft-github-policy-service agree


在window10下能运行吗，，感谢百度！

Hi, yongcong. I'm also a big fan for windows 10. It would be wonderful if MDL could be run on this marvelous platform. However, as of today our primary concern is still android and iOS. We may add a support for windows 10 in the future since the c++ codebase could be compiled across different platforms.


Error during draft up

Configured the repo to use docker hub.   Saw image pushed over.
Hit this error:
--> Deploying to Kubernetes
Release "bald-newt" does not exist. Installing it now.
Could not install release: rpc error: code = Unknown desc = error converting YAML to JSON: yaml: did not find expected alphabetic or numeric character

Can you provide a few more details such as which type of application you were building?
Thanks for the bug report. We'll look into this!

sorry, it is the app used in the tutorial:  draft/examples/python

So to confirm, can you provide a few more details?

your output of helm version
your output of draft version
your kubernetes cluster version
the steps you followed to deploy the python example. Were you using the "Getting Started" guide?

That yaml error means that somewhere in the chart/ directory, one of the yaml manifests is not proper YAML (usually indentation errors). Have you made any changes to the example, or perhaps do you have an editor open that automatically changes tabs to spaces or vice versa? Those are the first things that come off the top of my head.

→ helm version
Client: &version.Version{SemVer:"v2.4.1", GitCommit:"46d9ea82e2c925186e1fc620a8320ce1314cbb02", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.4.1", GitCommit:"46d9ea82e2c925186e1fc620a8320ce1314cbb02", GitTreeState:"clean"}
linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python on git:master ✖ [15:51:50]
→ /Users/linsun/Downloads/darwin-amd64/draft version
Client: &version.Version{SemVer:"canary", GitCommit:"8520032ef117cbbd64eff6f7e513c7cf8cd323f9", GitTreeState:"clean"}
Server: &version.Version{SemVer:"canary", GitCommit:"ed93463b23f1ebb5ee6f670b6dbbb51df11aa46e", GitTreeState:"clean"}
linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python on git:master ✖ [15:52:08]
→ kubectl version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.6-4+abe34653415733", GitCommit:"abe346534157336e6bd5a70702756cff19d43a49", GitTreeState:"clean", BuildDate:"2017-05-18T16:52:50Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

I didn't make any changes and was just following through the tutorial.   These are 2 of my yaml files:
→ cat chart/Chart.yaml
apiVersion: v1
description: A Helm chart for Kubernetes
name: bald-newt
version: 0.1.0
linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python on git:master ✖ [15:52:41]
→ cat chart/values.yaml
Default values for python.
This is a YAML-formatted file.
Declare variables to be passed into your templates.
replicaCount: 2
image:
registry: docker.io
org: library
name: python
tag: onbuild
pullPolicy: IfNotPresent
service:
name: python
type: ClusterIP
externalPort: 80
internalPort: 8080
resources:
limits:
cpu: 100m
memory: 128Mi
requests:
cpu: 100m
memory: 128Mi

I just repeated the steps (by ensuring the python example dir is clean) and used draft create to recreate all the yamls.  Still hit the same error.
I'm also relatively new to helm.   I tried to install the generated chart:
→ helm install chart
Error: release womping-kitten failed: Ingress.extensions "womping-kitten-awesome-kangaroo" is invalid: spec.rules[0].host: Invalid value: "womping-kitten.": must match the regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* (e.g. 'example.com')```

Could someone shed some insight on how to install the generated chart manually?
→ helm lint
==> Linting .
[ERROR] Chart.yaml: directory name (chart) and chart name (awesome-kangaroo) must be the same
[INFO] Chart.yaml: icon is recommended

Error: 1 chart(s) linted, 1 chart(s) failed

# linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python/chart on git:master ● [18:01:12]
→ cd ..

# linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python on git:master ● [18:02:33]
→ mv chart awesome-kangaroo

# linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python/awesome-kangaroo on git:master ✖ [18:02:46]
→ helm lint
==> Linting .
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, no failures

# linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python/awesome-kangaroo on git:master ✖ [18:05:14]
→ cd ..

# linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python on git:master ✖ [18:05:50]
→ helm package awesome-kangaroo --debug
[debug] Saved /Users/linsun/go/src/github.com/Azure/draft/examples/python/awesome-kangaroo-0.1.0.tgz to current directory

[debug] Saved /Users/linsun/go/src/github.com/Azure/draft/examples/python/awesome-kangaroo-0.1.0.tgz to /Users/linsun/.helm/repository/local

# linsun at linsun in ~/go/src/github.com/Azure/draft/examples/python on git:master ✖ [18:05:57]
→ helm install awesome-kangaroo-0.1.0.tgz
Error: release cranky-fish failed: Ingress.extensions "cranky-fish-awesome-kangaroo" is invalid: spec.rules[0].host: Invalid value: "cranky-fish.": must match the regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* (e.g. 'example.com')```

ok, i got the python example chart installed manually via calling helm directly:
NAME:   wanton-elephant
LAST DEPLOYED: Thu Jun  1 18:36:29 2017
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1beta1/Deployment
NAME                   DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
wanton-elephant-chart  2        2        2           0          3s

==> v1beta1/Ingress
NAME                   HOSTS                              ADDRESS      PORTS  AGE
wanton-elephant-chart  wanton-elephant.draft.example.com  <IP_ADDRESS>  80     3s

==> v1/Service
NAME                   CLUSTER-IP    EXTERNAL-IP  PORT(S)  AGE
wanton-elephant-chart  <IP_ADDRESS>  <none>       80/TCP   3s

NOTES:

  http://wanton-elephant.draft.example.com to access your application

Woo! Yeah! Makin' progress!
What I don't quite understand is that you're able to install the chart with helm but not with draft which is really just shipping the files over to Tiller (server portion of Helm) and having Tiller do the same work that you just saw done with wanton-elephant.
Shot in the dark - but are you still having problems with draft up now that you're seeing success with a helm install of the same chart?

Still have probs.... in fact, tonight, I tried draft with mini kube and failed with the same error.
Could you provide what version of kube, helm, draft that works for you?  I'm on a MacOS.
I've updated my helm to latest version.  See my versions:
Client: &version.Version{SemVer:"v2.4.2", GitCommit:"82d8e9498d96535cc6787a6a9194a76161d29b4c", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.4.2", GitCommit:"82d8e9498d96535cc6787a6a9194a76161d29b4c", GitTreeState:"clean"}
bash-3.2$ kubectl version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0", GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37", GitTreeState:"dirty", BuildDate:"2017-04-07T20:46:46Z", GoVersion:"go1.7.3", Compiler:"gc", Platform:"linux/amd64"}
bash-3.2$ ~/Downloads/darwin-amd64/draft version
Client: &version.Version{SemVer:"canary", GitCommit:"8520032ef117cbbd64eff6f7e513c7cf8cd323f9", GitTreeState:"clean"}
Server: &version.Version{SemVer:"canary", GitCommit:"3fad7ef57ce9ed198649bef38023be3860792d24", GitTreeState:"clean"}```

one thing may be helpful to debugging, is this expected?
bash-3.2$ cd examples/python/
bash-3.2$ ls
Dockerfile		app.py			chart			draft.toml		requirements.txt
bash-3.2$ cd chart/
bash-3.2$ helm lint
==> Linting .
[ERROR] Chart.yaml: directory name (chart) and chart name (billowing-cow) must be the same
[INFO] Chart.yaml: icon is recommended
Error: 1 chart(s) linted, 1 chart(s) failed
When I deploy helm chart, I had to get this error fixed (plus ensure it is the right registry, image name, tag, etc) before I can deploy.

Oh, one more thing.  I tried to update the chart.yaml file, and noticed the draft up console has connection refused error:
E0602 23:28:32.695890   15285 portforward.go:332] an error occurred forwarding 51188 -> 44135: error forwarding port 44135 to pod 5ef95025a31fc67f869192beeb93ac089d6096cf64324b0b6e0d5d31da98ce63, uid : exit status 1: 2017/06/03 03:28:32 socat[26457.140211455952640] E connect(5, AF=2 <IP_ADDRESS>:44135, 16): Connection refused
Error: there was an error running 'draft up': there was an error while dialing the server: unexpected EOF

I found the following in the tilt log (e.g. kubectl logs tiller-deploy-3354596499-kwxrz  --namespace=kube-system):
2017/06/05 14:54:40 storage.go:43: Getting release "bunking-butterfly" (v1) from storage
2017/06/05 14:54:40 storage.go:139: Getting release history for 'bunking-butterfly'
2017/06/05 14:54:40 release_server.go:660: Failed install prepare step: error converting YAML to JSON: yaml: did not find expected alphabetic or numeric character
Is there a way I can check out the release in the storage to see if it looks correct?  Given that I can use helm to deploy the chart, I think there may be an issue with uploading the chart to tiller via draft?

is there a online chat forum or slack that i can discuss this issue?

Hi @linsun! Sorry for not getting back to you sooner. I have been away for 2 weeks on vacation while the announcement was going on. I am just getting back on my own two feet (and reading hundreds of emails/github notifications), but I will definitely take a look at this once I am back on my own two feet again. Sorry about the delayed response! I promise I haven't forgotten you. :)

thank you @bacongobbler!  would appreciate any insight from you on this.  I hit this pretty consistent on two kubernetes envs and 2 clients envs.

So after debugging with @linsun over Slack, we found that it was due to a misconfigured base domain. When @linsun installed draft, she used *.example.com as the basedomain instead of example.com. This caused the helm chart to freak out due to the misconfigured ingress rule and raise the error seen above.
So, our action items for this ticket is to

improve the draft init experience, tracked in #49
document what exactly should be under the basedomain field as a crutch for now.
potentially look into how we can better improve helm template errors to show where the helm chart is failing to work. Being shown that the ingress template was failing to be parsed would have made debugging significantly easier.

closing in favour of #152 as we are going to drastically simplify the draft init workflow there which will also address @linsun's issue with suggesting a base domain which draft will accept.


todo-show throwing errors

atom.workspaceView is no longer available. In most cases you will not need the view. See the Workspace docs for alternatives: https://atom.io/docs/api/latest/Workspace. If you do need the view, please use atom.views.getView(atom.workspace), which returns an HTMLElement.
Called 9 timesCreate Issue on todo-show repo
Atom.Object.defineProperty.get - /Applications/Development/Atom.app/Contents/Resources/app/src/atom.js:54:11
ShowTodoView.openPath - /Users/jb259/.atom/packages/todo-show/lib/show-todo-view.coffee:260:9
atom.workspaceView is no longer available. In most cases you will not need the view. See the Workspace docs for alternatives: https://atom.io/docs/api/latest/Workspace. If you do need the view, please use atom.views.getView(atom.workspace), which returns an HTMLElement.
Called 9 timesCreate Issue on todo-show repo
Atom.Object.defineProperty.get - /Applications/Development/Atom.app/Contents/Resources/app/src/atom.js:54:11
ShowTodoView.moveCursorTo - /Users/jb259/.atom/packages/todo-show/lib/show-todo-view.coffee:269:25

Getting the same thing


String interpolation updates

Review and fix open issues on the string interpolation tutorial
Fixes #27209

Remove stray comment.
Ensure parameters are ordered consistently across all snippet versions.

Fixes #27271

A little refactoring and explanation.

ping @adegeo
Once again, each fix is in a separate commit for easier review.

Fine new paragraph, @BillWagner

That change means you can remove the enabled field. Then, you can change the return type of AppendLiteral and AppendFormattable to void.

but there is little typo – AppendFormattable should be AppendFormatted.

@Uzivatel919 these comments in completed PRs may easily go unnoticed. It's best to open a new issue or edit the file and open a PR.

@Uzivatel919 these comments in completed PRs may easily go unnoticed. It's best to open a new issue or edit the file and open a PR.

It’s fixed anyway.


Release 0.13.0

Maybe we could specify in the README.d that before version 0.13.0 we didn't follow the semver?

@kbogtob

Maybe we could specify in the README.d that before version 0.13.0 we didn't follow the semver?
Well, we do follow semver (https://semver.org/#spec-item-4) since this is version 0, do I don't think the note is needed in the end (contrary to what I initially thought).


IO::Socket::Async::SSL fails tests with OpenSSL 3

I tried to install this module and failed on an Ubuntu 24.04 x64 system, which uses OpenSSL3 (3.0.2).  The P12 file cannot be read by OpenSSL on this system.
I believe the problem is that the RC2 cipher is no longer usable by default in OpenSSL3.
I get the following test failure:
jmaslak@resolver2:~/p6-io-socket-async-ssl$ PERL6LIB=lib raku t/client-server.t
ok 1 - listen method returns a Supply
ok 2 - Server not listening until Supply is tapped
ok 3 - Server listens after Supply is tapped
ok 4 - Can establish and SSL connection to the SSL server
ok 5 - Can write to the SSL server
ok 6 - Can get a Supply of incoming data
ok 7 - SSL echo server got back expected data
ok 8 - Can close the SSL server connection
# Subtest: Without specifying a CA, our self-signed server fails verification
    1..2
    ok 1 - code dies
    ok 2 - right exception type (X::IO::Socket::Async::SSL::Verification)
ok 9 - Without specifying a CA, our self-signed server fails verification
ok 10 - Server not listening after tap is closed
# Subtest: When we connect to <IP_ADDRESS>, certificate for localhost will not do
    1..2
    ok 1 - code dies
    ok 2 - right exception type (X::IO::Socket::Async::SSL::Verification)
ok 11 - When we connect to <IP_ADDRESS>, certificate for localhost will not do
ok 12 - socket-host works
ok 13 - Simple server-side ALPN works
ok 14 - Passed protocols are correct
ok 15 - Server-side ALPN with a subroutine works
ok 16 - ALPN on server-side is set
ok 17 - ALPN on server-side is set
ok 18 - Multiple clients with ALPN work
ok 19 - Multiple clients with ALPN work
ok 20 - Negotiation is correct (1)
ok 21 - Negotiation is correct (2)
ok 22 - listen method returns a Supply with PKCS12 bundle
Failed to parse t/certs-and-keys/server-bundle.p12 as PKCS12
  in block  at /home/jmaslak/p6-io-socket-async-ssl/lib/IO/Socket/Async/SSL.pm6 (IO::Socket::Async::SSL) line 508
  in block  at /home/jmaslak/p6-io-socket-async-ssl/lib/IO/Socket/Async/SSL.pm6 (IO::Socket::Async::SSL) line 481
  in block <unit> at t/client-server.t line 171

OpenSSL3 on Ubuntu from the command line cannot open the file either.
jmaslak@resolver2:~/p6-io-socket-async-ssl$ openssl pkcs12 -info -in t/certs-and-keys/server-bundle.p12
Enter Import Password:
MAC: sha1, Iteration 2048
MAC length: 20, salt length: 8
PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 2048
Error outputting keys and certificates
403741A2587F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()

The problem seems to be the deprecated RC2 cipher.
I believe this problem similar to one seen with a module from our sister language: https://github.com/dsully/perl-crypt-openssl-pkcs12/issues/40

I guess if the cipher is deprecated, the easiest way forward is to remove the test?

Update to my previous update: OpenSSL is installed on the newer machine with openssl@3 but fails to install on my machine with openssl@1.
I'm pretty clueless on ssl libraries except to know it's a mess I keep having for a number of years now. Any specific suggestion on what I should do? Safe to do a --force install?

[OpenSSL] WARNING: /Users/sean/.rakubrew/versions/moar-2022.06/bin/rakudo is loading libcrypto in an unsafe way

That's tracked in https://github.com/sergot/openssl/issues/81, fwiw.

Having read https://github.com/dsully/perl-crypt-openssl-pkcs12/issues/40#issuecomment-1153148185 it looks like all we may need to do is run t/certs-and-keys/gencert.sh on a system with a newer openssl; if anybody experiencing this issue has a chance to clone the module and try that (and even prepare a PR if it works), that would be much appreciated. Otherwise I'll use an Ubuntu 24 container to do it next week.

Yes, running that script from within the t/cert-and-keys fixed one of the failed tests. However, another test is failing: sh-ciphers.t. The test just silently dies and returns (Any). Here is the contents of the test file:
use Test;
use IO::Socket::Async::SSL;

my constant TEST_PORT = 54335;

my $server = IO::Socket::Async::SSL.listen(
    'localhost', TEST_PORT,
    private-key-file => 't/certs-and-keys/server.key',
    certificate-file => 't/certs-and-keys/server-bundle.crt',
    ciphers => 'DHE-RSA-AES256-GCM-SHA384'
);
my $echo-server-tap = $server.tap: -> $conn {
    $conn.Supply(:bin).tap: -> $data {
        $conn.write($data);
    }
}
END $echo-server-tap.close;

lives-ok
    {
        my $s = await IO::Socket::Async::SSL.connect('localhost', TEST_PORT,
            ca-file => 't/certs-and-keys/ca.crt',
            ciphers => 'DHE-RSA-AES256-GCM-SHA384');
        $s.close;
    },
    'Connection with cipher doing key exchange works';

done-testing;

I'm guessing it's the same issue as this one: https://github.com/jnthn/p6-io-socket-async-ssl/issues/68

Regenerated the certificates using an Ubuntu 22.04 container; will make a release.


Uncaught ReferenceError: module is not defined

I try to add the theme to my project and I get:
@catppuccin_daisyui.js?v=348caec0:1762 Uncaught ReferenceError: module is not defined
    at @catppuccin_daisyui.js?v=348caec0:1762:1
(anonymous) @ @catppuccin_daisyui.js?v=348caec0:1762

@catppuccin_daisyui.js?v=348caec0:1762 Uncaught (in promise) ReferenceError: module is not defined
    at @catppuccin_daisyui.js?v=348caec0:1762:1

Hi @pkpg,
To help me better understand your issue, could you provide a minimal reproduction of this problem? It will make it easier for me to investigate and identify a solution.
I’ve put together a sample project with a workable configuration. I hope it’s helpful for you!

After these past few weeks of my practice, I feel that it may be because you directly imported the file into the browser environment. However, browsers do not have a module variable, which causes this error. I've adjusted the build configuration to avoid this issue; but, you still should not directly import this file into the browser.

Given that you have not responded for a long time, I have closed this issue. Hopefully, your problem has been resolved.


TicTacToe Game

Fixes #442
Created a TicTacToe game using HTML, CSS and JS.
Hope this solves the issue.
Looking forward for merging this PR.
Screenshot:

Screen Recording:
https://github.com/DhanushNehru/Ultimate-Web-Development-Resources/assets/143169520/e9d96df9-8b80-4d10-b23a-d122d0b045f6

Sure @selemondev would add it soon:)

Hey @selemondev do I have to add the project in your readme file and create a PR for that?

Hey @selemondev if you liked the changes can you please merge the PR. :)


Test test23unionMultiMaps is failed

Trying to run only this test in the latest snapshot of scalan-ce I got the following exception:
An exception or error caused a run to abort: scala.tools.nsc.Global.LiftedAssign()Lscala/reflect/internal/Trees$LiftedAssign$;
java.lang.NoSuchMethodError: scala.tools.nsc.Global.LiftedAssign()Lscala/reflect/internal/Trees$LiftedAssign$;

Looks like incompatible scala-reflect or scala-compiler versions somewhere. Try using sbt clean first.

Works for me:
> lms-backend/it:testOnly *SmokeItTests -- -z test23unionMultiMaps
[info] Compiling 2 Scala sources to /home/aromanov/IdeaProjects/scalan-lite/common/target/scala-2.10/test-classes...
[info] Compiling 19 Scala sources to /home/aromanov/IdeaProjects/scalan-lite/core/target/scala-2.10/test-classes...
[info] Compiling 6 Scala sources to /home/aromanov/IdeaProjects/scalan-lite/community-edition/target/scala-2.10/test-classes...
[info] Compiling 3 Scala sources to /home/aromanov/IdeaProjects/scalan-lite/lms-backend/target/scala-2.10/test-classes...
[info] LmsSmokeItTests:
error: write to non-mutable Sym(2) -> Some(TP(Sym(2),FieldApply(Sym(1),_1)))
at Sym(6)=Reflect(ArrayBuilderAppend(Sym(2),Sym(5)),Summary(false,false,false,false,false,false,List(),List(),List(Sym(2)),List(Sym(2))),List())
... other LMS errors
[info] - test23unionMultiMaps
[info] ScalaTest
[info] Run completed in 14 seconds, 130 milliseconds.
[info] Total number of tests run: 1
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[info] Passed: Total 1, Failed 0, Errors 0, Passed 1

We can try to reproduce it when you come in tomorrow.

Sorry, It was my problem - it is necessary now to move scala-lang.virtualized.* above core and community-edition projects in dependencies. Before it was enough just to place them before scala-lang.* libraries.


cuelang.org: redirect from tip.cuelang.org to cuelang.org on go-live

https://tip.cuelang.org is currently an entirely different site, generated against the tip version of CUE (https://cuelang.org is generated against the latest non-pre-release version of CUE).
When we go-live, we will not immediately have support for https://tip.cuelang.org.
We should non-permanently redirect to https://cuelang.org on go-live, until #2538 is supported in some way shape or form.

We did this on go-live so closing.
https://github.com/cue-lang/cue/issues/2538 tracks adding a proper tip.cuelang.org


Required Attributes Section - Version

"•	MUST have a version , which SHOULD be a semantic version like 1.2.3. "

How are non-individually-versioned EDK 2 PE binaries handled?
Companies employ large variety of versioning schemes. Oftentimes version format cannot be changes easily due to dependency of the tooling and internal processes on established version format. Should we consider softening or removing semantic version requirement?

non-individually-versioned EDK 2 PE binaries handled

Version 1.0?

Should we consider softening or removing semantic version requirement

What do you use now? How would vex work without semantic versions?

okay, I will give you an example.
EDK2 code is released every quarter and the versioning is literally done by git release which looks something like:
edk2-stable202311
That label covers everything from EDK2 release.  This is not a "semantic version"  But it is a versioning system.
That code can be taken by the next level vendor and be broken down and versioned in any way that they want and I would doubt that it will be in the same way that EDK2 releases.  On top of that, the way that Company A versions is most likely different from Company B, or Company C.
What we are asking here is that we don't specifically spell out "Semantic" versioning.  We read this to defined as
Major.Minor.Build
We just want this to be versioning.  There will be a versioning system.  Just not a Semantic one.

This is not a "semantic version"

I think 2023.11 is a semantic version FWIW.

Good description of semver: https://www.baeldung.com/cs/semantic-versioning
I'm in favor of a hash for binary versioning. This could be a hash of the binary itself to ensure it is unique. The hash can be used as a key in VEX server to get vuln status.


Token 'H' doesn't match specifier '%d'

I have several logs being already monitored, however, these logs are being a pain...I'm sure it's something simple.
time-format %H:%M:%S
date-format %d/%b/%Y
log-format %h %^ %^ [%d:%t %^] "%r" %s %b
Log format:
<IP_ADDRESS> - - [26/Jul/2019:20:26:54 -0700] "GET /profile/upload/server/php/ HTTP/1.1" 404 224
<IP_ADDRESS> - - [26/Jul/2019:20:28:34 -0700] "GET /robots.txt HTTP/1.0" 404 208

The common log format should it:
goaccess access.log --log-format=COMMON

Closing this. Feel free to reopen it if needed.


Update sbt-mima-plugin to 0.6.1

Updates com.typesafe:sbt-mima-plugin from 0.6.0 to 0.6.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe", artifactId = "sbt-mima-plugin" } ]

labels: semver-patch

Coverage decreased (-0.3%) to 94.737% when pulling 9530d25b8937d8ca86192eaba9c052775330115c on scala-steward:update/sbt-mima-plugin-0.6.1 into 5f72dc378fc2f3cf36c73954216272d9a8291020 on iheartradio:master.


Close Window specification

Expected Behaviour
I have just written an acceptance test for Close Window. It needs review as behaviour is different across operating systems.
Current Behaviour
The current behaviour does not match the test
Like Quit (#116, #117), the Save function doesn't work. I don't think offering to save one unsaved tab makes sense, hence the test says to just warn about unsaved work.
Your Environment

Data Curator version 0.3.3
Operating System macOS Sierra 10.12.6

see https://github.com/ODIQueensland/data-curator/blob/master/test/features/data_curator/quit.feature


Internal/Public Reports show question results out of order

Description: The Survey Results section of both the Internal and Public reports show results to question, but the questions appear in a different order than sequenced in the survey
Summary: If a staff or public user would view the report, they would likely expect to view Results in an order similar to how they answered them on the original survey.
Steps to Reproduce:

Engagements > look to Coyote Hydrogen - Early Engagement
Hit Actions dropdown > select View Report - Public or Internal
Scroll to Survey Results > notice that the first question displayed is actually part of a Likert Matrix from Q4 ['Outreach' page 2], the next result displayed is from a question which is actually Q15ish? [from 'Project Location' page 4] on the survey, etc.

Expected Result: The results should display in the same order they're listed on the survey, including the sub questions in Likert matrixes
Actual Result: The results are in an apparent random order
Environment: PROD
OS: Windows
Device/Model: Lenovo ThinkPad Laptop
Browser (if applicable): Edge
Attachments:
Results

First Page of Survey

Rectified data inconsistencies in existing survey results and deployed a code fix to address the underlying issue for future survey instances.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1643 ms

Resolved: Bofrost.de performance has improved in 08effff after 6 minutes.


Error is reported sporadically during k2s start: failed to start service flanneld

⏳ Write-Log : [11:01:36] Start-Service : Failed to start service 'flanneld (flanneld)'.  At C:\k2s\smallsetup\common\GlobalFunctions.ps1:1025 char:9  +         Start-Service $Name -WarningAction SilentlyContinue  +
⏳ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~      + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service], ServiceCommandException      + FullyQualifiedErrorId :
⏳ StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand
⏳ At C:\k2s\lib\scripts\k2s\base\Invoke-ExecScript.ps1:44 char:9
⏳ +         Write-Log $($_ | Out-String) -Error
⏳ +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
⏳     + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
⏳     + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

Nevertheless, after start flanneld service is running.
  get-service flanneld

Status   Name               DisplayName
------   ----               -----------
Running  flanneld           flanneld

since this only occurs for flannel service on windows side, one approach is to ignore error with -ErrorAction SilentlyContinue and check afterwards if the service is in running state


Add type-checking and fix type errors

Closing issues
closes #1447
Description
Type-checking has been added to the code, and existing type errors have been addressed.
Changes

Add typecheck script
Add npm run typecheck to test.yml
Fix type errors

Hello @simkasss ,
I ran typecheck and got the following errors. Can you please take a look?
><EMAIL_ADDRESS>typecheck
> tsc --noEmit

src/config/sidebar.ts:2:19 - error TS2307: Cannot find module 'astro:content' or its corresponding type declarations.

2 import { z } from "astro:content"
                    ~~~~~~~~~~~~~~~

src/content/config.ts:1:37 - error TS2307: Cannot find module 'astro:content' or its corresponding type declarations.

1 import { z, defineCollection } from "astro:content"
                                      ~~~~~~~~~~~~~~~

Found 2 errors in 2 files.

Errors  Files
     1  src/config/sidebar.ts:2
     1  src/content/config.ts:1

This is because the .astro directory is not generated until you run the server.


exception occuring in sendReminders

[2021-06-15T17:10:02.341Z] [shrd:0] sendReminders TypeError: Cannot read property 'slice' of undefined     at Function.idToBinary (/usr/src/bot/node_modules/discord.js/src/util/Util.js:503:29)     at Function.deconstruct (/usr/src/bot/node_modules/discord.js/src/util/Snowflake.js:66:25)     at Message._patch (/usr/src/bot/node_modules/discord.js/src/structures/Message.js:140:43)     at new Message (/usr/src/bot/node_modules/discord.js/src/structures/Message.js:44:20)     at Object.sendReminders (/usr/src/bot/handlers/events.js:1020:23)     at runMicrotasks (<anonymous>)     at processTicksAndRejections (node:internal/process/task_queues:94:5)

somehow an event doesn't have a messageID:
_id : 60c11b2b1cfc4700138f733d guildID : "852266636765298709" userID : "679140275733659669" attendees : date_time : 2021-06-15T18:00:00.000+00:00 title : "Session" dm : "679140275733659669" duration_hours : 3 number_player_slots : 8 description : "Regular Session" recurEvery : 7 __v : 1 reminderSent : 2021-06-15T17:10:02.226+00:00

avoiding the race condition that most likely caused the messageID not to be saved.  avoiding it 'double time' now that sendMessages, recurEvents, removeOldSessionPlanningChannels, removeOldSessionVoiceChannels are all 'awaited' from bot.js


ProfileCard: implement business logic to get and save ProfileCard model

create repository
create in-memory repository

https://github.com/DroidKaigi/conference-app-2024/pull/361
implemented


fix: return type of Compiler.shouldEmit should be boolean

Summary

Test Plan

Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

Thank you!


AWS + CoreOS + k8s 1.0.1 Documentation

Hello,
Is there more documentation on how to run a Kubernetes cluster using CoreOS on AWS ??
I tried the script for AWS specifying KUBE_OS_DISTRIBUTION=coreos, it started a master on ubuntu, and then tried to launch my minions but they all crashed.
I first had to modify the cluster/aws/coreos/util.sh script and delete those lines to make the script go this far:
i=$1
TODO(bakins): Is this actually used?
MINION_PRIVATE_IP=$INTERNAL_IP_BASE.1${i}
MINION_IP=$(yaml-quote ${MINION_PRIVATE_IP})
That crashed because you dont use a loop anymore to create the minions.
Do you have a solution to use the script to start a cluster automatically, like create credentials and give me access to the cluster directly. I dont want to use the other guide in the multi-node coreos page, because it is basically useless as is. What do i do once the masters and minions are running ?  SSH to get the credentials ?
I would love to be able to use the autoscaling group approach from the other script :)
I am on kubernetes version 1.0.1.

@kelseyhightower

I had the same issue. Not exactly knowing if it would help, I just updated i=$1 to i=${i:-0} and it at least launched the minions in.  This doesn't make much sense since it sets MINION_IP in user-data to the same IP for all minions created, but this didn't actually affect the internal IPs of my instances.  I had another issue after my cluster was up and running where dns-service resolution was only working in containers in 1 of the 2 minions I launched.  Not sure if that is related, but this has been a big blocker for me in getting kubernetes up and running on AWS with coreos.

I ha ve at the same stage as you @joshm1, when trying to access the UI I get this error:
Error: 'dial tcp <IP_ADDRESS>:8080: no route to host'
Trying to reach: 'http://<IP_ADDRESS>:8080/'
It seems the network stack is missing something ?

You should be accessing it through the apiserver proxy. Run:
kubectl proxy

Then go to http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/user-guide/connecting-to-applications-proxy.md

I tried to access it using address like https://xx.xx.xx.xx/api/v1/proxy/namespaces/kube-system/services/kube-ui on the IP of the master, which used to work when not using coreos as kube distribution.
Also I cant ping from one container to another.

Have you guys tried https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/coreos/coreos_multinode_cluster.md?

yes I tried I am using that currently but it is not a hand key version, like authentication you need a ssh tunnel, you dont have all the addons, the UI doesnt work.

I had the same problem with @mcadam on 1.0.3.

@mcadam there is no UI nor secure API access, indeed. But it's better than not having a cluster, am I right? Joke aside, it would be great if the alternative CoreOS documentation would include this.  I will be adding it to #9178

I suggest checking out https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/debugging-services.md

CoreOS is now maintaining official "Kubernetes on CoreOS" documentation. See the AWS guide here: https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws.html

I would suspect this is hideously out of date. Please reopen if it's still an issue.


Typo Fixes (Confrim -> Confirm)

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

This file has moved to another repo. You can open a PR there.

@oldnewthing, doesn't hurt to fix a simple typo here for anyone who finds it here, but if they're supposed to be the truth in the other repo, should the directory be removed from these samples with a pointer there instead?

Yup, the directory is already gone from this repo.


URI_TEMPLATE_ATTRIBUTE used when available with feature flag. Fixes g…

Fixes gh-1302.

@OlgaMaciaszek
I've added a feature flag.
TBH Now it doesn't look very neat now. getPath is very low as private method in utility class.
I do not think that somebody really needs old behaviour. Metrics are aggregated usually on path and IMO this is a memory leak rather than a feature.

Thanks @JaroslawDembek, the idea would be to remove the old behaviour completely from the new release. I agree this is bug rather than a feature, and normally we would just change the behaviour, but I think when it comes to metric tags, it might be better to be very conservative with any changes, but I'm going to request @marcingrzejszczak to weigh in on this.

@marcingrzejszczak  FYI this is a continuation of this: https://github.com/spring-cloud/spring-cloud-commons/pull/1327#issuecomment-1911913665.

Hi @JaroslawDembek, after some team chat, we think we can go forward with this fix without the flag after all, since there will bo no changes in the actual tag names; sorry for the confusion. Will you update the PR?

Hello @JaroslawDembek  - have you seen my last comment? Are those tests what you were looking for? Do you need more help or just need some more time?

Hello @JaroslawDembek - have you seen my last comment? Are those tests what you were looking for? Do you need more help or just need some more time?

Hints were ok. It was a good starting point. I was able to work it out for reactive scenario, but unfortunatelly I hit a wall with RestClient + BlockingLoadbalancingClient - no easy access to uriTemplate field.
TBH I believe the old way should be abandoned and the whole thing should be moved to Observation API - low/high cardinality aspect is perfect for this.
Wdyt?
I've started this (looking as great learning oportunity), but definetely I need more time.

Hi @JaroslawDembek - thanks a lot. Yes, it definitely makes sense to switch to Observation API - if you'd like to work on it, that sounds great. Also looking at the blocking implementation. In fact, since we're operating at the level of interceptor, we only get to work with org.springframework.http.HttpRequest, and specifically org.springframework.http.client.InterceptingClientHttpRequest, and we do not have access from the uriTemplate from there, as it doesn't pass it on.

Hi @JaroslawDembek, I guess you do not have time to finish this up. I'd like to get this into our upcoming RC-1, so I'm going to cherry-pick your commits and add the remaining changes.

I have also discussed using the Observation with @marcingrzejszczak and it seems that unless we want to create spans, it's better to stick with Meter and using  URI templates, as a high cardinality tag will not really give us any additional insight.

Closing in favour of https://github.com/spring-cloud/spring-cloud-commons/pull/1422.


Add cool PlebFM branded image to the readme file

Add cool PlebFM branded image to the readme file

This can also be used as the social preview image for this repo.

@nickatee this might be a good issue for us to pair on


Feat update score calculate

更新 jscpd 参数
支持设置检测重复度最大行数
更新评分计算方式，最低分改为10，总分改为加权平均计算。（最低分增加 0.1 权重）

Codecov Report

Merging #696 (bbff2b3) into release/0.15.0 (5435911) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release/0.15.0     #696   +/-   ##
===============================================
  Coverage           57.14%   57.14%
===============================================
  Files                   1        1
  Lines                  70       70
  Branches               15       15
===============================================
  Hits                   40       40
  Misses                 30       30

Continue to review full report at Codecov.

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


Background image on dashboard

I'm not sure if this is possible, but is there a way to make the background of the whole dashboard an image and not one solid color?

I am getting pretty good with Dashing and I have managed to add a background image quite easily, however, I have a dilemma.
I have two dashboards with different widgets. On one of them, I simply have a lot of "text" widgets displaying targets. I am trying to add a custom background to just some of those widgets, but not all. I have tried adding my own class in the scss file and binding it which I have included in the widget html file as normal and then added the data-backimage="backimage" hookup to the div in the erb file, however, I cannot see the image.
Any help would be appreciated, even if it is to tell me it cannot be done, which I doubt! :-)

My background never shows if i try to use a local image file as my background - regardless of whether i use the absolute or relative path. It works perfectly if i use on online-url of an image, though. Has anyone an explanation for this problem?

Serve the image from Dashing via HTTP. file://  is flaky at best.
https://en.wikipedia.org/wiki/File_URI_scheme


How to test a new WSDL ?

Hi there, I'm having issues using ShipService_v13.wsdl and I want to test the v15. I did replaced the content in these files:

fedex/wsdl/ShipService_v13.wsdl
fedex/wsdl/test_server_wsdl/ShipService_v13.wsdl

But is not taking any changes I make, how can I test a different WSDL file ?

Best bet is to drop some altogether new files in there (don't replace v13) and adjust the names here:
https://github.com/gtaylor/python-fedex/blob/master/fedex/services/ship_service.py


jabref: 5.10 -> 5.11

Description of changes
https://github.com/JabRef/jabref/releases/tag/v5.11

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg build jabref

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2949

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

1 package built:

jabref

Seems to work, thanks


[Issue] Icons not centred when on the right hand side of the screen.

My wife loves this module, she has almost forgiven me for building a MM in the first place :)
We noticed that the letters in the coloured icons where not centred when we moved the module to the right hand size (bottom_right).
Hope you don't mind but the easiest way I found to fix this, was adding text-align: center; to .icon section of the CSS.
.icon {
color: black;
display: inline-block;
font-style: normal;
height: 2.5em;
margin: 0 auto;
overflow: hidden;
text-indent: 0px;
white-space: nowrap;
width: 2.5em;
border-radius: 50%;
text-align: center;
}
BTW may thanks for the module @szech
Carl

Thanks for commenting! Glad you like the module.
Will look at incorporating your change soon 👍

Hi @szech,  think I found a better solution. If we add
.pollen-container td {
text-align: center;
}
to pollen-container.css, it centres the days as well.
Carl

hi @carlywarly, the latest update addresses this.
please update your local installation and config and report back.

perfect, again many thanks :)
Carl


Data drift: Usage of all the reference data instead of a mean (?

Hi, i hope you're doing well. I'm having a trouble related to the data drift plots.

As you can see, the reference data is counting all of the data took in the dataframe associated to the reference data, and as a consequence, the distribution looks a little odd. There's any way to workaround this??
I was thinking using the mean, but for boolean values, doesn't work very well.
Thanks in advance!

Hi @benja20029, do you refer to the fact that the absolute object count is much higher in reference, which makes the plot harder to interpret? If yes, you can toggle the "perc" button in the top right corner to switch from absolute to percentage view, which will be more convenient. Let me know if you meant something else.

I tried that, thanks!
The only problem i have now is that the information shown in the data drift plot is not agreeing with information shown in the data distribution (as you can see here):

As you can see, the first plot shows aproximately 5 or 6 points in 240 M but the data distribution plot says that are 61 points and seems to be weird. There's any reason to why is this happening??
In the other hand, i want to know how the data is ordered through the index binned, there's any way to sort it from higher value to lower value??
Thanks in advance!

Hi @benja20029, the first plot splits your data into 150 bins - there is currently no way to parametrize it. This aggregation helps reduce the overall size of the Report since users often run it for thousands or millions of data points at once.
You can consider the following.
1/ Inlcude the DateTime
If you have a timestamp (DateTime) for each prediction, I would recommend referring to it in Column Mapping. This way, your plot will not just use the binned numbered index but organize values by time to make it more interpretable.
2/ Turn the aggregation off (use raw data)
If you have a small number of data points, it might make sense to turn the raw data on when generating the Report. This way, you will see individual data points instead of binned index. Docs: https://docs.evidentlyai.com/user-guide/customization/report-data-aggregation
3/ Generate additional visualizations for specific columns outside of the DataDriftTable().
If you want to explore your data after you identified columns of interest (e.g. drifted columns), you can use other metrics to visualize them - e.g. ColumnDriftMetric(), ColumnValuePlot() (with raw data on), or ColumnSummaryMetric() for feature stats.

Thanks for the first two suggestions, they helped me a lot!
I don't understood quite well the third though :(, I would really to change the tooltip when i hover over a data point in the data drift plot, or if that's not possible, generate a new visualization, but i don't know if i should just create a new method or if there's any workaround (because I only want to change a small thing). 😢


Add substitution support for Info.plist and XCConfigs

Summary
This PR adds support for substituting values in xcconfig into infoplists and xcconfig_by_build_setting in to infoplists_by_build_setting.
In the current rules we have most of what is required to allow substitution of xcconfigs into the plist files but users must create their own macros to do this. Since this is a very common use-case for xcconfigs, and given that rules_ios directly supports xcconfig and xcconfig_by_build_setting it would be a better user experience to automatically performing this variable substitution for users of rules_ios
Problem
Given an Info.plist:
<plist version="1.0">
<dict>
    <key>CFBundleIdentifier</key>
    <string>${PRODUCT_BUNDLE_IDENTIFIER}</string>
    ...
    <key>CustonXCConfig1</key>
    <string>${CUSTOM_XCCONFIG_1}</string>
    <key>CustonXCConfig2</key>
    <string>$(CUSTOM_XCCONFIG_2)</string>
</dict>
</plist>

Given a BUILD.bazel:
ios_application(
    name = "App",
    xcconfig = {
      "CUSTOM_XCCONFIG_1": "VALUE_1",
      "CUSTOM_XCCONFIG_2": "VALUE_2",
    },
    ...
)

It would be expected that we end up with a final Info.plist:
<plist version="1.0">
<dict>
    <key>CFBundleIdentifier</key>
    <string>${PRODUCT_BUNDLE_IDENTIFIER}</string>
    ...
    <key>CustonXCConfig1</key>
    <string>VALUE_1</string>
    <key>CustonXCConfig2</key>
    <string>VALUE_2</string>
</dict>
</plist>

However, we currently receive an Info.plist merge error:
ERROR: In target "//tests/ios/xcconfig:App"; unknown variable reference "${CUSTOM_XCCONFIG_1}" while merging plists (key: "CustonXCConfig1", value: "${CUSTOM_XCCONFIG_1}").
ERROR: /Users/lpadron/Development/rules_ios/tests/ios/xcconfig/BUILD.bazel:81:16 Bundling App failed: (Exit 1): plisttool failed: error executing command
  (cd /private/var/tmp/_bazel_lpadron/7c5e30dd733c097d91026d4bca2f7997/sandbox/darwin-sandbox/1137/execroot/build_bazel_rules_ios && \
  exec env - \
    APPLE_SDK_PLATFORM=iPhoneSimulator \
    APPLE_SDK_VERSION_OVERRIDE=15.5 \
    XCODE_VERSION_OVERRIDE=<IP_ADDRESS>F100 \
  bazel-out/darwin_arm64-opt-exec-2B5CBBC6-ST-dedf359489b7/bin/external/build_bazel_rules_apple/tools/plisttool/plisttool bazel-out/applebin_ios-ios_sim_arm64-dbg-ST-2dd91a95bcfe/bin/tests/ios/xcconfig/App-intermediates/Info.plist-root-control)
# Configuration: ee2650817cf108ae590de90e920dc3ebc71f739bfdb185cc497e135b023391fc
# Execution platform: @local_config_platform//:host

Solution
The solution to the above is to use the existing tools in rules to perform variable substitution into the infoplists and infoplists_by_build_setting.
We use write_info_plist_if_needed and substitute_build_setting along with the xcconfig and xcconfig_by_build_setting attributes provided to the rules to construct a dict of infoplists_by_build_setting. This dict is then selected and passed as the infoplists attribute the relevant rules_apple rules which handle merging the plists.
Depends on

https://github.com/bazel-ios/rules_ios/pull/590

Related

https://github.com/bazelbuild/rules_apple/issues/226

What should people do here that already have the macros: it looks like this code is backwards compatible?

@jerrymarino yeah, should continue to work you'll just have extra info plists to merge (since they'd be substituting and so would rules_ios) but this shouldn't be an issue.
Thanks for filing the issue! Definitely agree that doing this during loading phase makes it difficult to use since macros have to handle the select via dict APIs.

@luispadron sure, I'll give this another run through this morning - thanks again for the improvement!

Spoke too soon, looks like PR is still modifying some fixtures which is unexpected I think. Looking into it!

I've resolved the issues where it was creating an extra plist, and thus failing the Xcode project tests. This should be ready now

Will follow up adding analysis time support for this


EXP: For big cube, be a minimalist

Companion to:

https://github.com/spacetelescope/jdaviz/pull/2839

Seems a little more performant when using https://github.com/spacetelescope/jdaviz/pull/2827 instead of main with these changes, but slider still too laggy to be usable (but not as laggy as main). Subset creation at least possible (not possible on main).
🐱

this skip parsing the hdulist if the cube is over 8 million spaxels?

It skips parsing uncert and mask but flux should still be loaded.

My diff here is only exploratory. It didn't complete fix the lag in loading and slice. I tried profiling the code on main but Snakeviz crashed. I ran out of time so I didn't try Snakeviz here. See the ticket comments for a full report. Thanks!

My diff here is only exploratory.

Gotcha 👍

Follow up tickets created. This is no longer necessary.


Autohashtag

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- src/main/java/brv/notifier/packt/services/hashtags/RiteKitHashtagService.java  4

Complexity decreasing per file
==============================
+ src/main/java/brv/notifier/packt/notifications/TwitterNotificationListener.java  -3

See the complete overview on Codacy


Broken dependency since #574 - incorrect use of provider source for 0.12 versions of Terraform

Hi,
#574
This commit: https://github.com/terraform-aws-modules/terraform-aws-vpc/pull/574/files#diff-7a675c670d75c5377fab042389a1c31e147037138af03515f2d455e357aaef60
The above commit is fundamentally flawed. A provider source (in this case for AWS) cannot be supplied for versions of Terraform < 0.13 yet the constraint for the required version of Terraform still permits 0.12 versions of Terraform.
Anyone who depends on this resource who is still running a 0.12 version of Terraform will now find themselves with a broken implementation.
I suspect this was tested using a 0.13 version of Terraform. Try again with a 0.12 version to reproduce.
Thanks.

According to the CHANGELOG for Terraform, this has became available since v0.12.20 - https://github.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md#01220-january-22-2020 (related PR: https://github.com/hashicorp/terraform/pull/23843)
I ran the examples using the minimum required version of Terraform (0.12.21) before releasing it to verify that it was valid syntax.
Can somebody verify this also?

Take a look at this: https://www.terraform.io/docs/language/providers/requirements.html
Also this: https://www.terraform.io/docs/language/providers/requirements.html#v0-12-compatible-provider-requirements
The latter suggests the minimum Terraform version of v0.12.26 so that should probably be the minimum required_version, not v0.12.21 as per the commit.
After pushing our Terraform version up to v0.12.29 which overcame the above issue we hit another issue. For reasons of general local compatibility we had AWS provider pinned to >~ 3.0.0 in our root module - this was incompatible with ~> 3.1.0 as specified in your latest commit as these 2 constraints are mutually exclusive.
Yes we should probably be more up to date with our AWS Provider versioning but it is worth noting here.


No support for relative server_port overrides

haproxy supports relative port addresses, prefixed by a "+" or "-".
If this is set the server port is determined by adding the value to the client's port. In the base service_watcher there is currently a check to verify that the override port is an integer which breaks existing configurations.
I assume nginx doesn't support a similar behaviour, would you accept a patch or should we just maintain our own version?

@udangel-r7
Since backend_port_override is provided by the user I've got no problem loosening the regex in the base watcher. If you all have a fork with a patch PR it and I can merge it.


Missing reference for JavaScriptServices

ASP.NET Core API Reference page missing namespaces from packages Microsoft.AspNetCore.SpaServices and Microsoft.AspNetCore.NodeServices

Making this repository Ready Only.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 2157 ms

Resolved: Bofrost.de performance has improved in b6d55a1.


[jest] it.each type conflict

Hi @NetanelBasal,
thank you for providing spectator I am a big fan of the API you have created.
I tried your library and it seems that some type-definitions of spectator still override jest's type definitions.
Importing @netbasal/spector/jest causes a compiler error when it.each is used.
I prepared a repository reproducing this behaviour:

git clone https://github.com/GregOnNet/spectator-jest-playground
cd spectator-jest-playground
yarn
visit src/app/app.component.spec.ts

Please let me know if I can provide further information
Thanks in advance
Gregor

@dirkluijk thoughts?

I missed to mention, that test.each works fine.
Only it.each causes problems.


not valid a selectbox

Hi,
I have a form' all the elements in divs with class "form-group"
but the selecbox not validation,
how I valid it?
Thanks you

I have this issue too, the  is supposed to be required but I get no validation and the submit-button is always enabled. I have no problem with any other form-element.

                                     Välj konto                                     <select class="form-control"                                         id="chooseAccount"                                         aria-describedby="selectValidationMessage"                                         data-error="Välj ett konto"                                         required>                                         <option>Välj</option>                                         <option value="konto #1">Konto #2</option>                                         <option value="konto #2">Konto #3</option>                                         <option value="konto #3">Konto #4</option>                                         <option value="konto #4">Konto #5</option>                                     </select>

Glad you got it worked out! Closing this ticket now.

I have the same problem. I have this option as prompt and and
<select class="form-control" required="required" name="user[gender]" id="user_gender">
<option value="">Gender*</option>
<option value="Male">Male</option>
<option value="Female">Female</option>
</select>

It does work with chrome, firefox ... ONLY iphone eg. has problems.

Any solution on this already? I have the same problem.
I have to choose the  element 2 times (only iPhone)

Edad
< 1 año
1 año
2 años
3 años
4 años
5 años

Works fine for me when I test it using iOS 9.3.2
http://output.jsbin.com/kebuqagewu [source]

I updated from version 0.10.2 to 0.11.5 version and now it works fine on iPhone. @1000hz Thank you very much!


Upgrade Tests and make them pass

https://github.com/html5lib/html5lib-tests use that in tests/data/libhtml5-tests and make the tests pass

Testing
git submodule update --init
git submodule update --recursive
11c3216 and master of old branch do work

  11140 passing (3s)
  4070 failing

  1) Tree adapter: default - ParserStream(tree-construction) - 0.adoption01 - `<a><p></a></p>` (line 1):

      AssertionError [ERR_ASSERTION]: Expected values to be loosely deep-equal:

[
  '(1:1) missing-doctype'
]

should loosely deep-equal

[]
      + expected - actual

      -[
      -  "(1:1) missing-doctype"
      -]
      +[]

      at Context.<anonymous> (test/utils/generate-parsing-tests.js:85:20)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)

old once with master
 14831 passing (3s)


Add support for np.conj/np.conjugate.

As title.
Fixes #2972

Looks good!  Will merge once CI passes.

Azure passes.  Merging now.


Trajectory of Crimes in West Bengal

Trajectory of crimes in west bengal has been visualized with the help of bar chart
Solution to #3
@souvikg544

Great @dhruvkej9