Adjusting deviceSizes breaks srcSet

I ran into an issue when trying to adjust the image and device sizes in next.config.js.
For my specific use case I do not need all default imageSizes: [16, 32, 48, 64, 96, 128, 256, 384] and deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840], and as a way to speed up the build time tried to adjust the list of sizes to something more suitable, like deviceSizes: [640, 750, 1080, 1920].
It might also be that I do not understand the configuration properly. However, if they are not meant to be customised, then I also do not see the need to specify them in next.config.js🙂
Expected behaviour
The plugin only generates new, optimised images for the specified imageSizes and deviceSizes, and adjusts the srcSet of the image tag to make use of the new sizes.
Observed behaviour
The plugin indeed only generated the sizes specified, but does not adjust the image tag properly so that it includes non-existent files. This breaks the image when the browser window gets too wide or too small.

Ways to reproduce the bug
1. Change next.config.js
module.exports = {
  images: {
    loader: "custom",
    nextImageExportOptimizer: {
      imageFolderPath: "public/images",
      exportFolderPath: "out",
      imageSizes: [16, 32],
      deviceSizes: [1920, 2048],
      quality: 75,
    },
  },
  env: {
    storePicturesInWEBP: true,
  },
};

2. Run npm run export
3. Resulting out/images folder

4. Resulting img tag
<img id="test_image" alt="test_image" sizes="100vw"
srcset="images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-640.WEBP 640w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-750.WEBP 750w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-828.WEBP 828w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-1080.WEBP 1080w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-1200.WEBP 1200w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-1920.WEBP 1920w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-2048.WEBP 2048w,
images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-3840.WEBP 3840w"
src="images/nextImageExportOptimizer/chris-zhang-Jq8-3Bmh1pQ-unsplash-opt-3840.WEBP"
decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px; border: none; margin: auto; display: block; width: 0px; height: 0px; min-width: 100%; max-width: 100%; min-height: 100%; max-height: 100%; object-fit: cover;">

Hi @ueberf,
Thanks so much for noticing this bug. I made a mistake in the specification of the configuration keys imageSize and deviceSizes in the next.config.js.
The change should be the following so that Next.js automatically takes the keys and thus the widths into account when it generates the srcset for the image:
{
// next.config.js
module.exports = {
  images: {
    loader: "custom",
 imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
 deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
    nextImageExportOptimizer: {
      imageFolderPath: "public/images",
      exportFolderPath: "out",
-      imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
-     deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
      quality: 75,
    },
  },
  env: {
    storePicturesInWEBP: true,
  },
};
}

I will update the README to reflect the correct set-up.

Hey @ueberf,
Could you please confirm that v0.9.4 fixes the problem also on your side? (You have to change the nextjs.config.js keys yourself, as the library cannot change it)
Thanks a lot!!

Hey @Niels-IO,
Yes, that fixed the issue and the srcset adapts to the exported images now!
One thing that I do not understand 100% yet is why the specified imageSizes do not appear in the srcset, too.
If they do not get included, what is the point of generating them?
Thanks for all you work!!

Hey @ueberf,
Cool! Regarding the image sizes I found this in the docs:
https://nextjs.org/docs/api-reference/next/image#image-sizes

The reason there are two separate lists is that imageSizes is only used for images which provide a sizes prop, which indicates that the image is less than the full width of the screen.

I will have to test it the complete srcset will be generate with the sizes prop.

I did a little test by adding another image in the example pages/ index.js , giving it a parent with display: "block" based on next/image documentation  and setting some custom imageSizes & deviceSizes
{/* Added Image Element */}

  <ExportedImage
    src="images/subfolder/subfolder2/ollie-barker-jones-K52HVSPVvKI-unsplash.jpg"
    layout="responsive"
    width={400}
    height={600}
    alt="Responsive image"
  />

module.exports = {
  images: {
    loader: "custom",
    imageSizes: [16, 32],
    deviceSizes: [1920, 2048],
    nextImageExportOptimizer: {
      imageFolderPath: "public/images",
      exportFolderPath: "out",
      quality: 75,
    },
  },
  env: {
    storePicturesInWEBP: true,
  },
};

Images get optimised as WEBP in the four specified imageSizes and deviceSizes, but are not listed in the srcSet
The resulting img looks like this:
<img
alt="Fixed image"
src="images/subfolder/subfolder2/nextImageExportOptimizer/ollie-barker-jones-K52HVSPVvKI-unsplash-opt-2048.WEBP"
decoding="async"  data-nimg="responsive"
style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px; border: none; margin: auto; display: block; width: 0px; height: 0px; min-width: 100%; max-width: 100%; min-height: 100%; max-height: 100%;" sizes="100vw"
srcset=" images/subfolder/subfolder2/nextImageExportOptimizer/ollie-barker-jones-K52HVSPVvKI-unsplash-opt-1920.WEBP 1920w, images/subfolder/subfolder2/nextImageExportOptimizer/ollie-barker-jones-K52HVSPVvKI-unsplash-opt-2048.WEBP 2048w"
>

At least based on this test it does not seem like the imageSizes are taken into consideration?

Hi @ueberf,
According to the documentation, the Nextjs image component will use the imageSizes array on one of the following conditions:

The Image component has a fixed layout with specified width and height, like this:<ExportedImage
  src="images/chris-zhang-Jq8-3Bmh1pQ-unsplash.jpg"
  layout="fixed"
  width="100px"
  height="100px"
  objectFit="cover"
  priority={true}
  alt="test_image"
/>

The Image component has a sizes prop with media queries like this for example:sizes="(min-width: 1024px) 48px, (min-width: 475px) 32px, 16px"

I tested it for the first condition, and it does indeed use the imageSizes array to generate the srcset. I added some tests in the pull request #17 if you want to have a deeper look.

Hey @Niels-IO,
Thanks for the heads-up!
Seems like I haven't read the Next's image documentation properly enough, but then it is indeed working as intended.


✨ Add embed-pdf / project shortcode

Is your feature request related to a problem? Please describe.
I want to be able to use shortcode for embed pdf
Describe the solution you'd like
Add  embed-pdf for shortcode
Describe alternatives you've considered
Using pdfjs-dist and create embed-pdf.html for shortcode, I refer to hugo-embed-pdf-shortcode, and import  pdfjs-dist in package.json.
shortcode example:

{{< embed-pdf url="./xx.pdf"  renderPageNum="2">}}

Additional context
I built a small prototype locally and I took the following screenshot.

I would be willing to make a PR based on your feedback to add this functionality.

Sorry @Weaxs thanks for the effort. However, I am not accepting the PR for this just yet (heads-up will close it for now).


Options window doesn't close on its own after opening a markdown file

Workaround: Close the window yourself.
Should be a quick fix.

Fixed in 1.10

Update: this only sems to happen in the web version, not on standalone. It's not fixed yet....


New Client ID

I want to port this to Homey. Can we get our own Client ID?

You can go here to find your client ID in the project:
https://iot.tuya.com/cloud/?id=p1698667378563n9fdns


Bower Angular Appears to only have v1.5.9?????

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Unable to download any angular version not being 1.5.9
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).

All versions should be available?
What is the motivation / use case for changing the behavior?
My project stopped working when it updated to the v1.5.9-build.5059+sha.4f44e01
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
My application works with the 1.5.8 version as I still have the development server hosting that file.
Other information (e.g. stacktraces, related issues, suggestions how to fix)

https://github.com/angular/bower-angular-route#1.5.8
None of this appear to be available ??? I'm I missing something?

The tags are there, but apparently GitHub is only showing a limited number of tags. BTW, those v1.5.9-build.XYZ are not actually v1.5.9 - they are (sort of) nightly builds, built automatically from our CI (and will eventually become 1.6).
Anyway, if you want to access an older tag that is not shown in GitHub's dropdown, you can either checkout the repo (and tags) locally or use a URL in this format: https://github.com/angular/bower-angular-route/tree/v1.5.8

Why is bower getting the nightly builds?

Bower is getting angular from that repository. We add appropriate tags, so when doing bower install angular you will get the latest stable version. The nightlies are also available, but you won't get the nightlies unless you explicitly specify the tag name.

gkalpak, thank you for your response.
I know this isn't related to angular but I tried the following bower.json names to get the 1.5.8 angular version.

"angular": "=1.5.8"
"angular": "~1.5.8"
"angular": "^1.5.8"

I still get the nightly build version no matter which version I try to get.

I'm sorry I just looked in my ng-route dependencies and noticed it's set to
  "dependencies": {
    "angular": "1.5.9-build.5059+sha.4f44e01"
  }

Should I report this as a bug in the ng-route git?

This is the ngRoute repo :smiley: But everything seems fine on the 1.5.8 version of ngRoute: bower.json
It must be something on your build/process. Try removing bower_components/ and re-installing.


LoginView.get_response modified in order to respect rest_framework_jwt.JWT_AUTH_COOKIE setting

Coverage decreased (-0.3%) to 96.639% when pulling<PHONE_NUMBER>2db6c6a2fbb89f15a38dd45d9cacf7 on gbezyuk:master into 9d1f65eedcd437003f5bef13fdc1f27d0fb0ee1a on Tivix:master.

Coverage decreased (-0.4%) to 96.552% when pulling 46fd16700a9e64fc23d843a9c3ff8c1798d60cd0 on gbezyuk:master into 9d1f65eedcd437003f5bef13fdc1f27d0fb0ee1a on Tivix:master.

What's blocking this PR? This fixes a problem I have. Much safer than putting the token in the localstorage in my SPA

@mariodev anything blocking this?


feat: move ac_rfl to Std

[ ] depends on: https://github.com/leanprover/lean4/pull/3223
[ ] depends on: https://github.com/leanprover/std4/pull/573

See issue lean4#3198 for context.

Move canceled upstream.


Update Notes in Group transformation

updated Group transformation notes to call out clearly the usage of Regex which is restricted for transforming only one group at a time and cannot be used for transforming multiple groups from the UI.
#ATCP

@maathangik : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@billmath
Can you review the proposed changes? Note that the en-us must be removed from the link before merging.
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

@maathangik : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off. Proposed changes accepted. PR is ready for the review team to merge.

@maathangik: I'm sorry - only the author of this article, @billmath, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Noted, will wait for the author @billmath to approve and sign off.

Checking with engineering

@maathangik Thanks for submitting this.
I checked with engineering and this was the response:
•	The statement is not actually 100% true
•	You can't have more than one regex transformation on groups, but you can transform many groups with the same regex pattern
So we need to update the statement to make it more clear, currently it looks like you can transform only one group value not group claim.
Thanks.
#HOLD-OFF

There doesn't appear to be any updates and this can't be merged as is.
#please-close


Using ModPagespeedUrlValuedAttribute made a duplicate image load problem

Hi,
I opened a new issue that is related by issue #1297
That is by using the syntax :
ModPagespeedUrlValuedAttribute li data-thumb image
the image ended up duplicate in the html just like what Mr. @oschaaf  said in the original issue post
Thank you very much

Reproduced.  If you configure a site to be:

And you set in your config:
ModPagespeedUrlValuedAttribute li data-thumb image

Chrome gets:

That is,
 just gets cache-extended, while  gets fully optimized.  On the other hand, if you have:

Then you get the expected:

Going from memory, the problem is that any tag that has children isn't considered an acceptable target for image optimization, so it only gets cache-extension here.  I'm not sure why we have this limitation, but it should be fixable.
I've added this to the Work Prioritization sheet.


totem-pl-parser: 3.26.2 -> 3.26.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/totem-pl-parser/versions.
meta.description for totem-pl-parser is: '"Simple GObject-based library to parse and save a host of playlist formats"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.26.3 with grep in /nix/store/jb4rwyafzh8spllmii83mjr18xm28kja-totem-pl-parser-3.26.3

directory tree listing: https://gist.github.com/3ce9c7ef12653b003f684d35ead2e008

du listing: https://gist.github.com/af1b0971ec93c500e2f01b4c7061896a

Rebuild report (if merged into master) (click to expand)

93 total rebuild path(s)
31 package rebuild(s)
31 x86_64-linux rebuild(s)
31 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
31 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
deja-dup
empathy
gnome3.cheese
gnome3.empathy
gnome3.file-roller
gnome3.gnome-boxes
gnome3.gnome-contacts
gnome3.gnome-control-center
gnome3.gnome-documents
gnome3.gnome-music
gnome3.gnome-online-miners
gnome3.gnome-photos
gnome3.gnome-terminal
gnome3.gnome-tweak-tool
gnome3.gnome-tweaks
gnome3.gnome-user-share
gnome3.gnome_control_center
gnome3.gnome_terminal
gnome3.grilo
gnome3.grilo-plugins
gnome3.nautilus
gnome3.nautilus-python
gnome3.rhythmbox
gnome3.totem
gnome3.totem-pl-parser
gnome3.tracker-miners
gnomeExtensions.gsconnect
lollypop
pantheon.extra-elementary-contracts
rhythmbox
totem-pl-parser

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jb4rwyafzh8spllmii83mjr18xm28kja-totem-pl-parser-3.26.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A totem-pl-parser https://github.com/r-ryantm/nixpkgs/archive/2255a45808867aa3b3ac76c83f5e341120f8d186.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jb4rwyafzh8spllmii83mjr18xm28kja-totem-pl-parser-3.26.3
ls -la /nix/store/jb4rwyafzh8spllmii83mjr18xm28kja-totem-pl-parser-3.26.3/bin

cc @lethalman @jtojnar @hedning @worldofpeace for testing.

News


Error loading data for HeavySelect2MultipleWidget

Attempting to use HeavySelect2MultipleWidget in a form with a data_url, but I get a "Uncaught TypeError: Cannot read property 'results' of undefined" error on line 19 of django_select2.js.
The call in forms.py looks like this:
categories = forms.MultipleChoiceField(
        widget=HeavySelect2MultipleWidget(data_url = 'static/js/vendor/factual176.json'),
		required=False
	)

The format of the JSON data looks like this:
{ "results": [{ "id": 1,"label": "Factual Places","text": "Factual Places"}, {"id": 2,"label": "Automotive","text": "Automotive"}, {"id": 3,"label": "Car Appraisers","text": "Automotive/Car Appraisers"},...

I'm using this tag on the template to include select2:
{{ form.media.js }}
I get this in the console, so it looks to me like it's finding the JSON file, but I'm unclear what's failing, and why:
[31/Jan/2016 17:12:09]"GET /static/js/vendor/factual176.json?field_id=NDQwNzkzMzAwOA%3A1aPvXU%3AEnSmfECr2vFAB-hlQNMUS8SJD9E HTTP/1.1" 200 18453

Hi @garyhesse ,
is this a new problem, or are you just starting out to use django-select2.
I don't see an error, since you get a 200 from the JSON endpoint and the data seems correct.
Is your JSON dump the response body of the request from the browser?
Cheers,
Joe

Joe,
I'm just starting to implement django-select2 in a new project. I am seeing the JSON in the browser at that path.

Ok, so the problem seems to be javascript side. Do you use jQuery 1 or 2?

jQuery 2.2.0.

Update: I rolled back to jQuery 2.1.4 and the TypeError message disappeared. However, I'm still not getting the JSON elements to appear in the select. Using the data example above, typing 'Auto' in the widget leads to this in the console:
[03/Feb/2016 17:48:36]"GET /static/js/vendor/factual3.json?term=Auto&field_id=NDQwMzgzMjMzNg%3A1aR1Rf%3ABL9BxsKdEi3_WNSSeAq7IRSAKzY HTTP/1.1" 200 121
... but I still see the 'Searching' message and nothing loads in the widget.

Update 2: I rolled back even further to jQuery 1.12.0. The data now loads in the widget, but I expected that typing would filter the widget to matching elements and that's not happening. Should it be, or am I misunderstanding the widget's function?

@garyhesse no, please stay with jQuery 2. Select2v4 doesn't support jQuery 1

Joe,
Is there a version of jQuery you recommend that should work with the widget?

Screenshot with jQuery 1.12.0:

Screenshot with jQuery 2.0.0:

@garyhesse you should use the latest jQuery2 version. But the problem seems to be in you JSON response. You have label in there, where it should only by id and text.

I tested with this JSON response and jQuery 2.2.0 without success:
{"results": [{"id": 1,"text": "General"}, {"id": 2,"text": "Automotive"}, {"id": 3,"text": "Automotive/Car Appraisers"}]}

This is very strange, it works for tons of people. I don't know all your code. I'm afraid that is all I can do for you :(


[improve][broker]Ensure namespace deletion doesn't fail

Motivation
Deleting a namespace sometimes fails and leaves znodes around, especially the "bundle owner" nodes /namespace/NAMESPACE/xxxxxx
Modifications

ensure that all the children of /namespace/NAMESPACE are deleted, especially the ephemeral nodes for ownership
ensure that on the code path that handles the deletion of the namespace we make progress, the main fact is about not relying on "cache.exists" before using a "delete": the new code is more pessimistic that goes with "deleteIfExists", handling "NotFound" gracefully
add more logs about the delete namespace execution path

With this patch

delete namespace seems to consistently work
there are no more spammy logs about errors around the topic policies event reader (changelog_events...)
in case we see an error we log at which point the procedure was (because we log all the paths that are deleted from zk)

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/eolivelli/pulsar/pull/27

This script reproduces MANY problems with namespace deletions, just run it in a loop on a Pulsar cluster with a few brokers (like 6) and more than one ZK server (I am using 3 nodes)
reproduce.sh
#! /bin/bash
export PATH=$PATH:/pulsar/bin
set -x
pulsar-admin topics delete-partitioned-topic non-persistent://T1/N1/P1 -f
bin/pulsar zookeeper-shell -server pulsar-zookeeper-ca:2181 ls -R /T1/N1 | grep namespace
pulsar-admin namespaces delete T1/N1
pulsar-admin tenants delete T1

pulsar-admin tenants create T1
pulsar-admin namespaces create T1/N1 -b 64
pulsar-admin topics create-partitioned-topic non-persistent://T1/N1/P1 -p 20

exit 0

Execute it in a loop
while true ; do ./reproduce.sh ; done

@lhotari I think that it is worth to port this fix to all the active branches, maybe up to 3.0. Wdyt?

@lhotari I think that it is worth to port this fix to all the active branches, maybe up to 3.0. Wdyt?

@eolivelli makes sense. Btw. there's a rabbit hole in namespace deletion. Currently concurrency limits are missing and a namespace deletion will attempt to concurrency delete all possible topics in the namespace. This is something that would have to be addressed to improve the reliability of namespace deletion. More details in #22541 comments such as https://github.com/apache/pulsar/pull/22541#issuecomment-2071621213 and https://github.com/apache/pulsar/pull/22541#issuecomment-2071687995 .

Codecov Report
Attention: Patch coverage is 43.13725% with 29 lines in your changes are missing coverage. Please review.

Project coverage is 32.47%. Comparing base (bbc6224) to head (23c39c1).
Report is 261 commits behind head on master.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #22627       +/-   ##
=============================================
- Coverage     73.57%   32.47%   -41.10%
+ Complexity    32624       87    -32537
=============================================
  Files          1877     1745      -132
  Lines        139502   133886     -5616
  Branches      15299    14673      -626
=============================================
- Hits         102638    43482    -59156
- Misses        28908    84033    +55125
+ Partials       7956     6371     -1585

Flag
Coverage Δ

inttests
27.52% <43.13%> (+2.94%)
:arrow_up:

systests
24.80% <5.88%> (+0.47%)
:arrow_up:

unittests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

.../service/SystemTopicBasedTopicPoliciesService.java
52.26% <100.00%> (-21.93%)
:arrow_down:

...he/pulsar/metadata/impl/AbstractMetadataStore.java
55.31% <100.00%> (-29.25%)
:arrow_down:

...ulsar/broker/resources/LocalPoliciesResources.java
44.82% <0.00%> (-31.04%)
:arrow_down:

...he/pulsar/broker/resources/NamespaceResources.java
53.90% <25.00%> (-26.25%)
:arrow_down:

...apache/pulsar/broker/resources/TopicResources.java
39.58% <33.33%> (-57.03%)
:arrow_down:

.../org/apache/pulsar/metadata/api/MetadataStore.java
60.00% <50.00%> (-20.00%)
:arrow_down:

.../apache/pulsar/broker/resources/BaseResources.java
55.85% <50.00%> (-16.88%)
:arrow_down:

...pache/pulsar/broker/admin/impl/NamespacesBase.java
15.22% <0.00%> (-57.86%)
:arrow_down:

... and 1517 files with indirect coverage changes


Change unsigned to signed int for the loops to work correctly...

i and M should be signed int below otherwise M - 15 is a very large number when M is less than 15. Same applies in many other places...
https://github.com/hfp/libxsmm/blob/f8994bee45316343a3ef39ed796e7ad4920347ed/samples/eltwise/eltwise_dropout.c#L72-L77

M and i are per definition unsigned datatypes (they cannot be negative), I guess the condition needs a fix, something like, (M/16)*16 or so.

Either is fine. May be use i < (M & ~0xF). I feel M - 15 was more readable...

OK, feel free to change to what solution is most readable, while keeping the unsigned values as the dimensions cannot be negative.

you can look at several macros: https://github.com/hfp/libxsmm/blob/master/include/libxsmm_macros.h#L465

push was done to fix this.

push was done to fix this.


Add option to upload games to hotslogs

Contact Barrett and decide whether hotsapi will push selected replays to hotslogs or hotslogs will pull new replays

Released an update, testing


Zappi: incorrect L1 phase shown

My zappi is installed with phase rotation set to 312, so phase 3 connected to L1 on the zappi, but when running zappi show I see the following which is incorrect
Supply voltage: 231.0V
Line frequency: 49.97Hz
L1 phase: 2

Your over-thinking 3-phases, the Zappi has no-idea which phase is connected to which terminal, in fact it is irrelevant as long as the rotation direction is correct. It is far better and logical to set the Zappi as 123 if you have a CW rotation.
At any instance in time, any phase can be 3 in your instance.

There is a phase rotation setting (see https://support.myenergi.com/hc/en-gb/articles/360019643517-How-To-Change-Phase-Rotation) which is set on my device to 312. To the zappi L1 terminal phase 3 is connected. I assumed that the L1 phase would return 3 in my case, but it seems I am incorrectly assuming that, what is the meaning of the L1 phase, is that something else?

Phases are 120° apart and the Zappi setting for phase rotation will work the same for any CW combination, they are all CW notations. In a purist sense it’s easiest to fit the physical phase 1 (which doesn’t actually exist as 1 !) to Zappi terminal 1, then set the phase rotation to 123, however in reality your house phase-1 can be real world 1 or 2 or 3. Only if you could trace your phases back to the power station generator could you be really sure which phase is which. In practice it is almost certain that phases will have been swapped along the power distribution path from generic to your house. As long as the phase direction is correct it will all work.
if you monitored the L1 terminal at any instance of time it could be any phase that follows the sequence 123, 231, 312 it is literally irrelevant.
to further add to the possibility your installer could have swapped any two phases relative to your grid supply and it would still work but you’d never know. The reference is the Zappi terminals, but it’s never going to tell you which phase is connected to the Zappi. It will tell you that ‘some’ phase connected to Terminal 1 at that instance in time.

I don’t understand what the issue is, the integration merely displays what the API is returning, if there was an issue you’d need to be asking MyEnergi.


duplicate_counter issues

Describe the bug
During testing, duplicate_counter jumps from 0 -> 1 -> 3 -> 4 -> etc
Also, the implementation of message_duplicate_count means it looks like it is being called one message early. Further investigation required
To Reproduce
Steps to reproduce the behaviour:

Run the code, printing the return from propagate
Send at least 3 messages

Expected behaviour
duplicate_counter does not jump by 2 in one step
Screenshots
https://gyazo.com/b8b646ca725109265b8dfb847d236e2f
Additional context
These are not covered by unittests, hence why I don't think I saw them earlier

Added some unittests and the library appears to function as expected, except for the duplicate counter issue. Still investigating

Not sure whats happening, is working as expected. Will reopen if we no longer get expected behaviour


HELM-369: Flow datasource and histogram panel code improvements

A number of code improvements related to the Flow Datasource and Flow Histogram panel which were requested on PR #597 , including:

breaking functions down into smaller chunks
removing moment.js reference and eslint-disable clause
type annotations
other code cleanup and comments

External References

JIRA (Issue Tracker): https://opennms.atlassian.net/browse/HELM-369
Continuous Integration: CircleCI

Looks incredible. Great work. :)

Thank you! It was good to finally follow up on all your great suggestions :)


chore: update build script

created a dist folder with a .keep file in it

you will no longer need the mkdir dist; in the build scripts (breaking for window)

create build task for unminified source with source maps.
create meta-build task to execute both builds

Great idea.

:+1:
I think this should be submitted to develop?

in reality we should never be hitting the green merge button. The branch a PR is sent to really means nothing (aside from not cluttering the github interface)

landed as c669bdf


EditorImportPlugin throws errors when moving imported file that's saved as a custom resource.

Godot version
3.3.2.stable.mono.official
System information
Windows 10
Issue description
Custom EditorImportPlugins throw errors when moving the imported file, saved as a custom resource, into another location.
Note that the resource seems to get saved correctly but a few errors are thrown.
# import_plugin.gd
tool
extends EditorImportPlugin

...

func import(source_file, save_path, options, r_platform_variants, r_gen_files):
	var file = File.new()
	var err = file.open(source_file, File.READ)
	if err != OK:
		return err

	var res = CustomResource.new()

	file.close()

	return ResourceSaver.save("%s.%s" % [save_path, get_save_extension()], res)

# custom_resource.gd
class_name CustomResource
extends Resource

Steps to reproduce

Open up the reproduction project
Drag the .txt file into another folder.
Watch the editor print the error:

editor/editor_file_system.cpp:1782 - BUG: File queued for import, but can't be imported!
editor/editor_file_system.cpp:1783 - Method failed.
Another resource is loaded from path 'res://addons/plugin/custom_resource.gd' (possible cyclic resource inclusion).

Minimal reproduction project
ImportPluginBroken.zip

Possible duplicate of https://github.com/godotengine/godot/issues/46288
Not sure, though.


Initial draft of LIP-20

This PR is the initial draft for LIP-20. This is meant to provide both definitions for how currencies work on-chain (registration, minting, coin operations, SCS v.s. synthetic currencies, burning), and also some level of intuition at the same time provide some intuition and motivation for each these e.g., Preburn exists so that off-chain actions can be performed before burning the coins.

The biggest question I have is whether we want this to be a Libra-specific standard (in which case I think it is close to ready) or a more general standard that will be adopted by other blockchains that want to interop with Libra and/or use Move (in which case I think we have some thinking to do in a few key areas). Some of my comments are assuming we want the latter (especially given the "20"), but wasn't sure.

My thinking was that this would be more Libra specific, but I defer to your and @dahliamalkhi's view on this, and am happy to edit this either direction.

I believe all comments have been resolved. I've also updated to use Diem and XDX everywhere, with the exception of links at the moment.
@sblackshear let me know if this looks good to you.


Save my favorite filters

Issue opened with imdone.io from code comment on 9f751f1
BACKLOG  Save my favorite filters id:16

https://github.com/imdone/imdone-atom/blob/9f751f14f022fed15d90b360e4f50f43250dcb82/lib/views/menu-view.coffee#L22-L27

Issue closed with imdone.io by removing a comment.

https://github.com/imdone/imdone-atom/blob/b7251b7ccf00e69c484ae85d9668078cedb7152e/lib/views/menu-view.coffee#L21-L26


Use libssl3 for Ubuntu builds

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
SevenTV/chatterino7#172

That would only work on 22.04 iirc because it is still 1.1 on 20.04 iirc. Will check later when I left bed.
Also I almost fixed the build and got it to work by bundling Qt and adjusting LD_LIBRARY_PATH. Just need to get the postinst script to work to set the library path variable automatically.

The correct approach to distributing deb files is to be specific which version we're targeting. Right now, we're targeting Ubuntu 20.04 with our deb, only changing the libssl version is not the right approach, we need to check all dependencies for a 22.04 release

I'll be honest I was just taking a shot in the dark that this would resolve the issue, this isn't for me to fix as I do not have either env to test with. 🙂


Awesome PHP

Add to the list on Awesome PHP when library has been updated to PHP 7.1+.

Project already listed on Awesome PHP.


Add another job on openshift-ci to run integration tests

As of now e2e-crc calls the make e2e and we are not running the integration tests which are written to Ginko, It should be good that we have a upstream CI to test those changes so dev members can also play with it and update as needed.

PR https://github.com/openshift/release/pull/17726

It is now fixed, closing it.


Integrate the Darstellung block the History Graph

Selectors should filter the level of showing graph.

This are the elements the controls should contain:
First Control: (Vollständig should be default)

Second Control: (Alle Flurstücke should be default)


WASI network access example

Hello,
I am trying to use container2wasm to run a Linux VM inside wasmtime. Here is my code:
#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
    // Create a new Wasmtime engine and store with unit data.
    // Construct the wasm engine with async support enabled.
    let mut config = Config::new();
    config.async_support(true);
    let engine = Engine::new(&config)?;

    // Embed the WebAssembly module into the binary.
    let wasm_bytes = include_bytes!("../images/ubuntu:22.04.wasm");

    // Create a linker to link the WASI module.
    let mut linker: Linker<WasiP1Ctx> = Linker::new(&engine);
    preview1::add_to_linker_async(&mut linker, |t| t)?;

    // Create a WASI context and put it in a Store; all instances in the store
    // share this context. `WasiCtxBuilder` provides a number of ways to
    // configure what the target program will have access to.
    let wasi_ctx = WasiCtxBuilder::new()
        .inherit_stdio()
        .inherit_network()
        .socket_addr_check(|_, _| Box::pin(ready(true)))
        .allow_ip_name_lookup(true)
        .allow_tcp(true)
        .allow_udp(true)
        .build_p1();
    let mut store = Store::new(&engine, wasi_ctx);

    // Load the WebAssembly module from the embedded bytes.
    let module = Module::new(&engine, wasm_bytes)?;
    let func = linker
        .module_async(&mut store, "", &module)
        .await?
        .get_default(&mut store, "")?
        .typed::<(), ()>(&store)?;

    // Create an instance of the module with a mutable store.
    func.call_async(&mut store, ()).await?;

    Ok(())
}

It works great and I have access to a shell/prompt.   They have been ignored, or old ones used instead.
root@localhost:/#

What am I missing?

container2wasm only supports networking through the use of a helper program c2w-net running on the host as native program: https://github.com/ktock/container2wasm/tree/main/examples/networking/wasi It looks like container2wasm targets wasip1 which only supports exposing a server over the network listening at a wasm runtime defined port (which c2w-net seems to take advantage of). You need wasip2 to be able to actually connect to arbitrary servers without a proxy like c2w-net.

@bjorn3 thank you for your quick response!

You need wasip2 to be able to actually connect to arbitrary servers

How do I do that? I thought my code was already already targeting preview2

Container2wasm doesn't use wasip2. You did have to ask the maintainer of container2wasm to add wasip2 support.

You did have to ask the maintainer of container2wasm to add wasip2 support.

@bjorn3 so you mean my code is fine and supports preview 2, but the loaded WASM module produced by converter2wasm does not support preview2 ?

but the loaded WASM module produced by container2wasm does not support preview2 ?

Indeed. container2wasm produces wasip1 rather than wasip2 wasm modules.

so you mean my code is fine and supports preview 2

You need different code to load wasip1 and wasip2 modules. Your current code is correct for wasip1, but once container2wasm supports producing wasip2 modules, you will need some changes to load the wasip2 module.

you will need some changes to load the wasip2 module.

@bjorn3 are there any examples for wasip2?

This PR updates the WASI example in this repo to wasip2.

It looks like Wasmtime is performing as-expected here and while there's perhaps follow-up items with tools like container2wasm I'm going to close this as I don't think there's anything to track on the Wasmtime side of things. If I'm wrong though let me know!


Adjacent Difference Algorithm

Describe the solution you'd like
The adjacent_difference algo produces a new sequence in which each element is difference between adjacent elements in original sequence.
Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

Please assign this issue to me

I want to add solution to this in Java under LGMSOC.
@Ayush7614 @Amit366 please assign me this.

Hi I'm an LGM SOC participant and would like to work on this in C++ language. It would be great if this could be assigned to me.

@Yakshit310 it's already assigned . U can choose other language

@Amit366 can I try JavaScript?

@Yakshit310 no JS

@Amit366 Python ?


hubot fails to start on node 5.6.0

[Fri Mar 04 2016 09:06:18 GMT-0600 (CST)] ERROR Unable to load /home/bfosberry/workspace/captain/node_modules/papertrail-hubot/scripts/papertrail: TypeError: Cannot read property 'on' of undefined
at /home/bfosberry/workspace/captain/node_modules/hubot/node_modules/scoped-http-client/src/index.js:87:14
at Groups.fetch (/home/bfosberry/workspace/captain/node_modules/papertrail-hubot/scripts/papertrail.coffee:135:7)
at new Groups (/home/bfosberry/workspace/captain/node_modules/papertrail-hubot/scripts/papertrail.coffee:87:8)
at module.exports (/home/bfosberry/workspace/captain/node_modules/papertrail-hubot/scripts/papertrail.coffee:209:22)
at Robot.loadFile (/home/bfosberry/workspace/captain/node_modules/hubot/src/robot.coffee:358:11)
at /home/bfosberry/workspace/captain/node_modules/papertrail-hubot/index.coffee:8:13
at FSReqWrap.cb as oncomplete

The problem is that the script does not exits gracefully when the env variable is not set. I've already created a pull request to fix it:
https://github.com/papertrail/papertrail-hubot/pull/5


refactor term representation in the physical layer

rebased on top of #372, so should not be merged before that


SA VoNR docker won't start after setting up AMF ports

I'm trying to use the sa-vonr-deploy branch, in use with an external gNodeB (ORS68 from Rapidspace). Following the tutorial, i uncommented the below lines about ports on AMF and UPF:

Afterwards, the docker launch ends with a parsing error :
test@lab5G-open5GS:~/docker_open5gs$ sudo docker-compose -f sa-vonr-deploy.yaml up
ERROR: yaml.parser.ParserError: while parsing a block mapping
in "./sa-vonr-deploy.yaml", line 197, column 5
expected , but found ''
in "./sa-vonr-deploy.yaml", line 220, column 6
If I skip this part, the dockers will start, but it results in the AMF aborting all SCTP INIT attempts from the gNodeB :

Could someone give me a clue about how getting it to work ? Thanks in advance.

Can you post here the sa-vonr-deploy.yaml you modified ? Also, can you let me know the docker-ce and docker compose version you are running?

Hi @herlesupreeth. The requested docker version :
cogisys@lab5G-open5GS-fork:~/docker_open5gs$ docker --version
Docker version 24.0.7, build 24.0.7-0ubuntu2~22.04.1
cogisys@lab5G-open5GS-fork:~/docker_open5gs$ docker compose version
Docker Compose version v2.3.3
And the sa-vonr-deploy.yaml in attachment.
sa-vonr-deploy.yaml.txt

The indentation of "ports" section under amf and upf is wrong. Please align it (yaml files are very sensitive to spaces)

Thanks for the information, I didn't know it was space-senstive. I tried again with a copy/paste from the repo, and I had the same issue.
Howerver, I was able to make it work : there is an extra space between the sharp character and "ports" in the sa-vonr-deploy.yaml from the repo. I removed it and it starts.
Thanks again for your help.


fix: repoURL matching is case sensitive

this change is currently untested, I plan on conducting a full one soon
While testing this awesome project in my own repository, I found that using different casing in the application repoURL results in a confusing error message printing that the repoURL key was missing entirely. We may want to consider printing something more helpful in that case (for example, "Different 'repoURL' under spec.source in file {}")
Additionally, I fixed the debug message printing spec.sources[] as the source even when spec.source is used, which mislead me at the start. (=> rebase)

Ah, so that was why the CI failed. This issue reminded me once again of how complicated rust can be, foolish of me to think yolo-ing the change without a test compile would be a good idea :sweat_smile: thank you!
I think I may have to rebase + autosquash as GitHub can't do it during the merge, lmk when it's time to do so.

Ah, so that was why the CI failed. This issue reminded me once again of how complicated rust can be, foolish of me to think yolo-ing the change without a test compile would be a good idea 😅 thank you! I think I may have to rebase + autosquash as GitHub can't do it during the merge, lmk when it's time to do so.

Yes, Rust is a struggle sometimes 😄 It looks fine as it is — I’ll merge it, and it will be part of the next release ✌🏻
Thank you for the contribution! I didn’t consider that URLs could potentially include uppercase letters.

v0.0.24 is now released 🚀  This fix is live


Add fallback runfiles path for setting debug CWD.

There is a default workspace name __main__ that is used when none is
declared in a WORKSPACE file. This commit adds this as a fallback path
since the expected path derives the workspace name from the root
directory.
See Bazel change log at: https://github.com/bazelbuild/bazel/blob/master/CHANGELOG.md#release-023-2016-05-10

Note that __main__ is printed as main in markdown formatting in the Bazel changes.

Hello @mtsgrd,  Are you still looking to submit this PR? Could you please fix the buildkite checks, so that i can share it for review. Thanks!


"Go To Definition" navigates to the file's dedicated tab rather than staying within the diff's tab.

Version Information :

Visual Studio Version 17.5.4
Git Branch Differ Version 1.1.1

Describe the bug
Inside a diff's tab, right-clicking a variable or type defined in that file and selecting "Go To Definition" navigates to a new tab of the same file alone rather than staying within the diff's tab.
Expected behavior
If possible, the cursor should stay within the diff's tab so unnecessary, diff-less tabs aren't needlessly switched to instead. In contrast, using Find References on a type or variable within a diff tab already works as I'd expect, navigating to elsewhere within the tab if possible, or even to the associated diff tab of that reference's location (if that diff tab happens to already be open, anyway).

Hi, I reckon that's quite annoying. I'll look for a way to fix this bug.
I've also thought of adding a way to manage these diff-tabs created by the extension, somehow separate them from non-diff tabs for better UX, easier lookup.


Exposure Notification (Corona) Scanner Implementation

ROM:
lineage-14.1 unofficial build - Android 7.1.2
GmsCore:
dirty build, commit d641ca7e7e9a147f65120c5cb40216c11744b702
device:
Sony Z5 compact (E5823)
Corona app:
CWA <IP_ADDRESS>
Hi, I am having some issues running the EN API. First I noticed that after running EN for a while the preferences app did not show any collected IDs. So I debugged a bit. My device seems to scan for 30mins and then stops. It only continues scanning after disabling and re-enabling EN or rebooting (basically after the ScannerService is restarted). I added some debug output printing seenAdvertisements to the callback function onScanResult. I see those debug prints for 30min and then stopping. They only restart after restarting the ScannerService.
Since nobody else noticed while testing, it might be a problem with my device/bluetooth chip. Nonetheless, it might be worth finding the issue or changing the implementation in case it affects other people. Since there is no error message it might go unnoticed and basically breaking the EN scanning functionality.
While searching for the reason of the bug I also had a look on the Google implementation / description. Please correct me if I am wrong, but I think your current implementation constantly / all the time scans for other devices? The EN system, at least as envisioned from Google/Apple, should actually only scan for a couple of seconds in an interval of a couple of minutes (when the device is woken or every 5min). Do you have a reason for the continues scanning other than to have a quick first release? I guess it is also not very battery friendly (ok, there is a "battery optimization" item on your todo list). Probably my problem would also be solved with a system, which scans only every now and then (where the ScannerService is restarted).

Not sure about this, but I thought this is part of the battery optimization process mentioned here

I agree that scanning continuously is not optimal and that will certainly be optimized later on, however I also don't see a big battery impact on my device at least.
Do you have "battery optimizations" ignored for microG Services Core according to Self-Check?
When you are connected with adb shell, you can run dumpsys activity service com.google.android.gms/org.microg.gms.nearby.exposurenotification.ScannerService to let it print when it was started and when the last advertisement was recorded.

In general, do you mind PRs for this feature or EN? I am not really a Android developer and never used kotlin. But if I am bored in the next couple of weeks, I might give it a try.
No, all self checks are ticked
I did not know this dump feature (as I said, I am not a Android developer), its nice :). I was already wondering for what the dump function is for :D

time 9:36
SERVICE com.google.android.gms/org.microg.gms.nearby.exposurenotification.ScannerService 51a0247 pid=3207   Client:     Started: true     Since Mon Sep 07 09:35:19 GMT+02:00 2020     Seen advertisements: 23     Last advertisement: Mon Sep 07 09:36:39 GMT+02:00 2020
time 10:02
SERVICE com.google.android.gms/org.microg.gms.nearby.exposurenotification.ScannerService 51a0247 pid=3207   Client:     Started: true     Since Mon Sep 07 09:35:19 GMT+02:00 2020     Seen advertisements: 340     Last advertisement: Mon Sep 07 10:02:44 GMT+02:00 2020
time 10:10
SERVICE com.google.android.gms/org.microg.gms.nearby.exposurenotification.ScannerService 51a0247 pid=3207   Client:     Started: true     Since Mon Sep 07 09:35:19 GMT+02:00 2020     Seen advertisements: 379     Last advertisement: Mon Sep 07 10:05:19 GMT+02:00 2020
tine 10:48
SERVICE com.google.android.gms/org.microg.gms.nearby.exposurenotification.ScannerService 51a0247 pid=3207   Client:     Started: true     Since Mon Sep 07 09:35:19 GMT+02:00 2020     Seen advertisements: 379     Last advertisement: Mon Sep 07 10:05:19 GMT+02:00 2020
I also attached adb logcat *:S ExposureNotification:D (which also shows an other problem I have, CWA has a problem checking keys and shows an timeout error, but I will use the similar open issue for this)
2020-09-07_logcat_en-1.log

Can you test with 4663d61007060f7f42b8d91920571b1969a79b55?

I started testing it today in the morning (~3 hours ago) and until now it runs without any problem. I will close the issue if it continues running until tomorrow morning. Thank you for the quick fix

All looks well after a day, thanks again for fixing it and your work on EN in general :+1:


InputSource Error

Installed package through Cocoapods...
pod 'ImageSlideshow', '~> 1.8'
pod 'Kingfisher', '~> 5.0'
App couldn't resolve KingfisherSource so I manually put just the InputSource.swift and KingfisherSource.swift file into the project.
Error
Value of type 'KingfisherSource?' does not conform to expected element type 'InputSource'
If you insert "as! InputSource" as recommended by Swift there is another error
Error
Expression type 'InputSource' is ambiguous without more context

I fixed this by manually adding the folder and the podspec to the project and then installing the pods in the same way the Example project does... by pointing to the path manually


I saw you fixed the style, thx! I wonder why you switched from:
#include <utility> to #include "utility" it seems like the first one looks more correct?

Now the static check is complaining about the fact that the include should be the last one. We have a CLang formatter config that sorts the includes alphabetically. If you use it, it will just sort the includes for you, I suggest to change the include back to #include <utility> before sorting it using CLang formatter.


If no hostnames detected from bindings, allow hostname to be specified manually

I run my IIS sites without a hostname.
Your program is therefore unable to detect the hostname (understandably). It presents me with various different options, and I must select manual mode.
Instead, a better option would be to show the IIS site, and prompt manually for the hostname.
Thanks for your great program.

I'll look into this when refactoring the IIS plugins for the next release.

I've looked into this, but it's actually pretty difficult to implement, especially when properly matching the certificate to the binding during renewal. In my opinion it would require at least one extra field in the internal representation of a target and a bunch of logic changes in different places.
Perhaps at some point in the future this will become easier as we refactor the code to be more flexible, but right now I'm removing this from the v1.9.5 milestone.

You can do it in v1.9.7 by creating the certificate on another binding (might even be another website) and then link it to the hostless binding. After this initial manual step LEWS will keep the host-less binding updated after renewal.

@WouterTinus How would that work -- wouldn't LE issue to the certificate for the wrong hostname then?

You would have to create a binding on port 80 somewhere with the correct hostname configured. It's not the perfect solution yet, but it's at least a way to get auto-renewing certificates set up on hostless bindings :).

It has to be on port 80? But then that will conflict with the user's existing binding...

Yes it has to be port 80, but it can be on the same site as the hostless binding so that it doesn't conflict; all traffic would still go to the same site.


chore: bdd-spring-1587306773 to 0.0.1

chore: Promote bdd-spring-1587306773 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Wrong path for cache directory in offline mode

Describe the bug
Dear huggingfacers,
I'm trying to use a subset of the-stack dataset. When I run the command the first time
dataset = load_dataset(
    path='bigcode/the-stack',
    data_dir='data/fortran',
    split='train' )

It downloads the files and caches them normally.
Nevertheless, since my compute nodes are not online (HF_DATASETS_OFFLINE=1) . Whenever I try to run the command again, the library is passing the wrong cache path:
Cache directory for the-stack doesn't exist at /Users/user/.cache/huggingface/datasets/bigcode___the-stack/default-data_dir=data%2Ffortran-data_dir=data%2Ffortran
when the right path is:
'/Users/user/.cache/huggingface/datasets/bigcode___the-stack/default-data_dir=data\%2Ffortran
Not sure why those redundancies are included in the path.  If I try adding the correct path through the the cache_dir argument it throws an error:
ConnectionError: Couldn't reach the Hugging Face Hub for dataset 'bigcode/the-stack': Offline mode is enabled.
Your help with this issue is greatly appreciated. Thanks a lot for the great work.
Steps to reproduce the bug
1:
dataset = load_dataset(     path='bigcode/the-stack',     data_dir='data/fortran',     split='train' )
2:
HF_DATASETS_OFFLINE=1
3:
dataset = load_dataset(     path='bigcode/the-stack',     data_dir='data/fortran',     split='train' )
Expected behavior
being able to use the cached data
Environment info
several different systems

+1

same error in 2.16.1

@kongjiellx any luck with the issue?

I opened https://github.com/huggingface/datasets/pull/6632 to fix this issue. Once it's merged we'll do a new release of datasets

Thanks @lhoestq !


Updated example for Remove method

I have decided to propose a new example because existing not only is confusing (implicit variable type declarations and unused variable) but also does not compile because of dots and invalid use of Remove method; run time error 450: Wrong number of arguments or invalid property assignments.

Docs Build status updates of commit 2da6b32:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/remove-method-dictionary-object.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Ability to add payment methods and native Apple Pay outside of a component

Is your feature request related to a problem? Please describe.
If I'm understanding the documentation and examples correctly, right now the payment method flow (get/create setup intent, create payment method, submit payment method to API) all needs to happen within the same component as the calling component. Meaning, it all needs to happen within the same component as <CardField /> or <ApplePayButton />. However, this is currently breaking our coding norms as we were able to abstract most of it to methods living outside components and GraphQL mutations.
Describe the solution you'd like
We would like a way to do what I described or, if there's no way or plan, an answer here so that we know we've exhausted our options.
Describe alternatives you've considered
It's not the end of the world to keep all payment related actions in methods within components but, as I said, it does break our coding patterns.
Additional context
We are coming from tipsi-stripe, which allowed us to do this, albeit at the cost of possible lack of PCI compliance.

It does not need to be called within the same component, the requirement is rather that the CardField component needs to be mounted at the time of calling confirmPayment or createPaymentMethod etc.
We traverse the view stack and find the CardField, so as long as it is visible and filled in we are able to extract the card details.

@thorsten-stripe thanks! Would be great if a note about this could be added to the docs because right now it's not clear how it all works.


Fix #840 Migration of unique/index keys in PgSQL

My second try to fix issue #840.

Ok, thanks @xxdavid! I'm going to merge this and add some tests later on.


Human readable plugin names

Summary
Offer human-readable plugin names as the primary name of plugins, instead of the Python package name
Intended Outcome
Naming conventions of Python packages are not very user friendly & we've heard from users that they are confusing. We'll let plugin developers provide human-readable plugin names that aren't subject to the same constraints of PyPI package names.
How will it work?
Plugin developers will be able to provide human-readable plugin name which will supercede the Python package name if they choose to use it.
Assets

PRD (when ready)
Designs (when ready)
Tech Spec (when ready)

Job stories
napari hub

[x]  When I'm viewing a plugin's card, I can read the author's Display Name
[x]  When I'm viewing a plugin listing, I can read the plugin author's Display Name
[x] When I search, I get results that match the plugin's Display Name

Preview Page

[x]  When I'm viewing the Preview Page and I don't have a Display Name, I can be reminded that this metadata is missing and see how to add it

related: https://github.com/napari/napari/issues/3102

Here's a link to the final designs:
https://www.figma.com/file/YhYdskZzQuMQSsnPXEUElW/Human-readable-plugin-names?node-id=24%3A10

closing in favor of #434 as the primary epic for this work

frontend work done: https://github.com/chanzuckerberg/napari-hub/issues/434

When I'm viewing a plugin's card, I can read the author's Display Name

When I'm viewing a plugin listing, I can read the plugin author's Display Name

When I search, I get results that match the plugin's Display Name

When I'm viewing the Preview Page and I don't have a Display Name, I can be reminded that this metadata is missing and see how to add it


signature method returns a plain Object?

I'm trying to sign data items to bundle them into a single tx using ArBundles and i'm running into an issue using the signature method.  The return type of the method is Promise<string> but it's returning a plain Object.  I'm struggling to debug why :)
async sign(message: Uint8Array): Promise<Uint8Array> {
  const signature = await window.arweaveWallet.signature(message, {
    name: "RSA-PSS",
    saltLength: 32,
  })
  console.log('SIGNING WITH THIS SIGNATURE', signature)

  return Buffer.from(signature) // This line will fail as signature is not a string as expected
}

This is running in a browser environment (Brave Version 1.34.81 Chromium: 97.0.4692.99 (Official Build) (64-bit))
Buffer is provided by a dependency in the arbundles package and implements Uint8Array
The return line in the above method will error with the following:
TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.

Any pointers or advice?  Thanks!

Apologies, we currently do not support bundles, but this will be an upcoming feature. That function is not for bundle signing.

@martonlederer Well I got it to work anyway :P  Bundle successfully posted locally with arlocal using ANS-104 Binary format
async sign(message: Uint8Array): Promise<Uint8Array> {
  const signature = await window.arweaveWallet.signature(message, {
    name: "RSA-PSS",
    saltLength: 32,
  }) as any

  const signatureArray = []
  const keys = Object.keys(signature)

  for (let i = 0; i < keys.length; i++) {
    signatureArray.push(signature[keys[i]])
  }

  return Uint8Array.from(signatureArray)
}

I'm using arbundles and wrote a custom Signer and also re-implemented the bundleAndSignData method to use Buffer and it all works now
      class ArweaveWalletSigner implements Signer {
        signatureType: number = SignatureConfig.ARWEAVE
        ownerLength: number = SIG_CONFIG[SignatureConfig.ARWEAVE].pubLength
        signatureLength: number = SIG_CONFIG[SignatureConfig.ARWEAVE].sigLength

        // TODO
        publicKey: Buffer

        // TODO ?
        pem?: string | Buffer | undefined

        constructor(publicKey: Buffer) {
          this.publicKey = publicKey
        }

        async sign(message: Uint8Array): Promise<Uint8Array> {
          const signature = await window.arweaveWallet.signature(message, {
            name: "RSA-PSS",
            saltLength: 32,
          }) as any

          const signatureArray = []
          const keys = Object.keys(signature)

          for (let i = 0; i < keys.length; i++) {
            signatureArray.push(signature[keys[i]])
          }

          return Uint8Array.from(signatureArray)
        }

        static async verify(
          pk: string,
          message: Uint8Array,
          signature: Uint8Array,
        ): Promise<boolean> {
          return await Arweave.crypto.verify(pk, message, signature)
        }
      }

My guess is that signature is attempting to return a Uint8Array but it's been JSON stringified and parsed or something similar.  Possibly because of the call message format between the extension's environment

Wow nice job! This will also help us implementing a specialized api for bundles in the future

Wow nice job! This will also help us implementing a specialized api for bundles in the future

thanks!  Ultimately this issue is for the signature method returning a plain object instead of a string as suggested by the docs https://docs.th8ta.org/arconnect/functions#signature which is also reflected in the method's return type definition.
i'd like to move forward using the signature method as I outlined above but it seems to be a bug that it's returning a plain object.  I wouldn't want to run into breaking changes, although I could type check the return value for string for now

I will have to investigate why it's not consistent, I'll keep this issue open till then.

I will have to investigate why it's not consistent, I'll keep this issue open till then.

thanks!  I think it might be more useful to instead change the return type to Uint8Array as that's what the input is expected to be and, at least for my use case, what i'd like it to use it as
i think it is returning a Uint8Array it's just been erroneously converted to a plain object or never re-instantiated as Uint8Array after getting the result from the extension environment


Fix L7 ingress proxy in direct routing mode

Fix per-endpoint route mode with the cilium-health daemon, and configure
it such that the daemon prefers to connect over IPv4 rather than IPv6 when
both protocols are enabled in the daemon. Otherwise we hit CI issues in
the endpoint routes mode datapath configuration test (See #8956).
Fix routing from a host proxy towards local pods in endpoint routes mode:
When endpoint routes are enabled, we don't need to install the ip rules
or routes to ensure that the traffic from the ingress proxy goes into
cilium_host; Instead, we configure BPF programs attached to the TC
egress filter of the endpoint device to ensure that it implements the
policy logic.

Treat this case as datapath mode "routed", where we will now skip those
rules. All other datapath configuration should be equivalent to direct
mode.

If we don't do this, then when applying L7 ingress policy, the traffic
from the ingress proxy towards the pod is first directed towards the
cilium_host device, then subsequently passed to the stack and re-routed
towards the endpoint device, which causes the BPF to lose the context
that this traffic comes from the proxy and hence the BPF program treats
it as newly inbound traffic from the world. As a result, inbound HTTP
requests see a message like:

```
$ kubectl exec tiefighter -- curl -s -XPOST <IP_ADDRESS>/v1/request-landing
upstream connect error or disconnect/reset before headers. reset reason: connection failure
```

This fixes the following policy cases:

Ingress L7 policy in direct routing mode for traffic from the same node
Ingress L7 policy in direct routing mode for traffic from a remote node

This change is

This currently causes some havoc with cilium-health IPv6 connectivity which I'm still figuring out. It's easy to reproduce with enable-ipv6: true and enable-endpoint-routes: true, and may be something to do with the new routed mode in bpf/init.sh.

Coverage decreased (-0.04%) to 44.119% when pulling 1ef17f9a092e82a820c71afe2fa9a0ff1440197d on joestringer:submit/fix-l7-ingress-rules into 9c36f26c98f8201b8add3abe220ad574e9860f9e on cilium:master.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


Need Formula for CHEBI:38757

Dear ChEBI Curators;
Would it be possible to add back the formula C15O2R10 to CHEBI:38757 so that we can balance the RHEA reaction with ChEBI:28206 which has Formula:C15HO3R9?
Thanks in advance for your help,
Lucila

Now done.
Kind regards,
Gareth


Improve the style for small screens and smartphones: lots of small suggestions

For very narrow screens, I suggest the following changes.

[ ] remove the name of file, except if there are already two tab editors (so you win some vertical space) ;
[x] switch the [ editor | toplevel ] horizontal flex layout to a vertical layout, putting editor on bottom, toplevel on top ;
[ ] move the +/-/:wastebasket: button to vertical stack, and to the right of both editor and toplevel ;
[ ] increase default zoom by

    <meta name="viewport" content="width=device-width, initial-scale=1.75, maximum-scale=1.75">

[ ] add a "launch" button also on the editor pane, for easier access
[ ] if possible (I could find how to do it), change the flex between toplevel/editor from 50%/50% to 40%/60%, to allow a larger editor zone

Demo
I tried everything and it works fine on my local Firefox on Ubuntu, when asking a narrow screen, and it works fine on Firefox on my Android that has a narrow screen too.

Try it
If you want to try the current version, you can do so here.
However, as you can see, it displays poorly on large screens.
My changes are not so smart (yet) about being responsive, and it implements all these changes regardless of the size of the screen (ie, no use of CSS @media screen (max-width 650px), just manual modification of the HTML).
My main problem was that I don't how to dynamically switch from container horizontal to container vertical based on screen width. I'm not a very good CSS designer, sorry!

You can see on https://github.com/Naereen/BetterOCaml/commit/2380c51f6c738ac83efa9a728bc670ee90238a88 the changes.
Lots of them are just because I "beautified" the HTML and CSS using VSCode auto tools, but the rest of the changes are very sparse.

I also suggest to add these two lines in the HTML file:
    <meta name="viewport" content="width=device-width, initial-scale=1.75, maximum-scale=1.75">
    <meta name="theme-color" content="#263238">

Of course you can adapt the zoom, I hacked this the other day to try to have a quickly done mobile-aware responsive version, but your new branch is surely better!
Same for the theme.

I guess this can be closed safely.


Add configuration variable to force llvmlite memory manager on / off

Following the merge of numba/llvmlite#1009, it enables its built-in memory manager on 64-bit ARM platforms. However there are situations where it might be desirable to override the default, e.g.:

To check if it introduces a regression on a platform on which it's normally enabled
To debug / develop it on a platform where it's not (e.g. Linux on x86_64)

This PR adds a config / environment variable and the relevant documentation.

I've manually tested the use of NUMBA_USE_LLVMLITE_MEMORY_MANAGER and confirmed that it worked as intended

Great, thanks for doing that @sklam.


Make add_node() consistent w. add_input / add_output

For add_node() we have:
n = so.node(...)
g = so.add_node(g, n, ...)

while for add_input we have:
g = so.add_input(g, ...)

why not use:
g = so.add_node(g, ...)  # i.e., do not explicitly create a node first.

This was designed this way as nodes are often require more code to instantiate than inputs/outputs, and hence the code might become unwieldy when merging this all into a single call (and, additionally, one might create multiple nodes in sequence and use add_nodes to add them all ad once.
So, we are going to stick to this convention for now. However, we might add an append_node (or something like that) which does immediately add a note to a graph if that makes sense to users.
Feel free to add this. I am closing this issue for now.


bird hunter plugin

Bird Hunting Plugin mplementation
Description:
Implements a bird hunting script with dynamic trap handling.
Automatically sets a hunting area based on player location and configurable radius.
Manages trap interactions (setting, collecting, and replacing traps).
Automatically walks back to the center of the hunting area if outside.
Includes snare inventory checks based on player level.
AntiBan implementation

Thanks for contributing <3


KeyError: "Dataset 'coco_trainval_all' is not registered!

KeyError: "Dataset 'coco_trainval_all' is not registered! Available datasets are: coco_2014_train, coco_2014_val, coco_2014_minival, coco_2014_minival_100, coco_2014_valminusminival, coco_2017_train, coco_2017_val, coco_2017_test, coco_2017_test-dev, coco_2017_val_100, keypoints_coco_2014_train, keypoints_coco_2014_val, keypoints_coco_2014_minival, keypoints_coco_2014_valminusminival, keypoints_coco_2014_minival_100, keypoints_coco_2017_train, keypoints_coco_2017_val, keypoints_coco_2017_val_100, coco_2017_train_panoptic_separated, coco_2017_train_panoptic_stuffonly, coco_2017_train_panoptic, coco_2017_val_panoptic_separated, coco_2017_val_panoptic_stuffonly, coco_2017_val_panoptic, coco_2017_val_100_panoptic_separated, coco_2017_val_100_panoptic_stuffonly, coco_2017_val_100_panoptic, lvis_v1_train, lvis_v1_val, lvis_v1_test_dev, lvis_v1_test_challenge, lvis_v0.5_train, lvis_v0.5_val, lvis_v0.5_val_rand_100, lvis_v0.5_test, lvis_v0.5_train_cocofied, lvis_v0.5_val_cocofied, cityscapes_fine_instance_seg_train, cityscapes_fine_sem_seg_train, cityscapes_fine_instance_seg_val, cityscapes_fine_sem_seg_val, cityscapes_fine_instance_seg_test, cityscapes_fine_sem_seg_test, cityscapes_fine_panoptic_train, cityscapes_fine_panoptic_val, voc_2007_trainval, voc_2007_train, voc_2007_val, voc_2007_test, voc_2012_trainval, voc_2012_train, voc_2012_val, ade20k_sem_seg_train, ade20k_sem_seg_val"

KeyError: "Dataset 'coco_trainval_all' is not registered! Available datasets are: coco_2014_train, coco_2014_val, coco_2014_minival, coco_2014_minival_100, coco_2014_valminusminival, coco_2017_train, coco_2017_val, coco_2017_test, coco_2017_test-dev, coco_2017_val_100, keypoints_coco_2014_train, keypoints_coco_2014_val, keypoints_coco_2014_minival, keypoints_coco_2014_valminusminival, keypoints_coco_2014_minival_100, keypoints_coco_2017_train, keypoints_coco_2017_val, keypoints_coco_2017_val_100, coco_2017_train_panoptic_separated, coco_2017_train_panoptic_stuffonly, coco_2017_train_panoptic, coco_2017_val_panoptic_separated, coco_2017_val_panoptic_stuffonly, coco_2017_val_panoptic, coco_2017_val_100_panoptic_separated, coco_2017_val_100_panoptic_stuffonly, coco_2017_val_100_panoptic, lvis_v1_train, lvis_v1_val, lvis_v1_test_dev, lvis_v1_test_challenge, lvis_v0.5_train, lvis_v0.5_val, lvis_v0.5_val_rand_100, lvis_v0.5_test, lvis_v0.5_train_cocofied, lvis_v0.5_val_cocofied, cityscapes_fine_instance_seg_train, cityscapes_fine_sem_seg_train, cityscapes_fine_instance_seg_val, cityscapes_fine_sem_seg_val, cityscapes_fine_instance_seg_test, cityscapes_fine_sem_seg_test, cityscapes_fine_panoptic_train, cityscapes_fine_panoptic_val, voc_2007_trainval, voc_2007_train, voc_2007_val, voc_2007_test, voc_2012_trainval, voc_2012_train, voc_2012_val, ade20k_sem_seg_train, ade20k_sem_seg_val"

I also met this question, would you share your resolution? thank you very much!!!

I solved this question, by recompiling detectron2


Fix minor grammar issues

Line 30 -  "your query was sent" rather than "you query sent"
Line 37 - Off topic sub headings, "Your program must distinguish between 'transient errors' versus 'persistent errors.'  The paragraph is discussing   these two topics but the start of the next sentence refers back to a previous topic not the sub topic, - Transient faults. Optionally to avoid double wording to change to "Transient errors are fault conditions..."
Line 269 - Wrong word used - which rather than with

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

@PRMerger7 I like these changes, and I recommend #sign-off.
CC @KompotentKev Thanks Kevin.


ESP8266 Newb

I'm afraid that I am quite the newb when it comes to ESP devices and also the Arduino IDE. I have a history with more barebones uC like PIC.
I have a ESP8266MOD AI-THINKER chip on a CH340 USB UART board that I bought from China years ago. I have an arduino ide sketch that uses the DallasTemperature, and therefore OneWire, and also ESPAsyncWebServer -- and that is working correctly. However, I'd like to add Preferences to this setup so that I can configure the device without flashing it.
This Preferences library return false when I try to use this code (paraphrased):
Preferences prefs;
bool result = prefs.begin("tiger", true);
I don't know where to go from here. Is there some sort of debugging message I can catch? Is this chip not supported by this library? Do you know of any alternatives that might work? Is there some way I can help you support this chip if that's a possibility?
Thanks.

I'm embarrassed to admit that I tried this on some WEMOS D1 mini, and it worked perfectly. So I'm pretty convinced that the board I was working with just didn't have any flash available to the sketch.
Sorry for the noise!


[1.20.6] Item duplication when adding tools to belt

ver:utility-belt-neoforge-2.1.1+1.20.6.jar
Neoforge: 20.6.75
When I right-click to add tools to the belt, like you do with a bundle, the tool is duplicated in the belt.

And if the belt is full and I try to right-click to remove the items, it will delete two items.

Thanks for reporting. I started looking into this but decided I'll just work on it tomorrow, because I think the fix should involve some refactoring to make sure stuff like this can't happen

Weird thing: this does not happen in creative mode

Fixed, might not release for a while though as I want to do some intensive play testing to find any other issues


3.0 - (breaking) Reworking how validation error state is handled

The goal here is to allow for a way to "map" the error text used by the browser for different validity state so we can show different text (when not using native browser validation reporting). In my scenario here, I wanted more concise messaging for the error itself with more information coupled in the UI.  To allow this, I've added validity from the input to be stored with the FieldError, so when it changes, the input/select/textarea can determine what kind of error it is from state.
(Specifically so they can determine if it's a custom error or a non-custom error and in turn setCustomValidity when upstream errors are set).

This changes the onFieldError prop on Input, Select and TextArea and gives it additional arguments.
Instead of (field: string, message: string) => void it's now (field: string, message?: string, validity?: ValidityState) => void.
This also means that fieldError Prop is now treated as an object with a message: string prop (alongside validity to then indicate to the input component error details.
errorMapping argument has been added to the useFieldState hook and in the FieldManager component as a prop to enable a simple text mapping from error type to message. These are not variable driven yet, but I can look at that in the future.

A simple example of error mapping looks like this:
const mapping: ErrorMapping = {
	badInput: 'Invalid',
	customError: 'Invalid',
	patternMismatch: 'Invalid',
	rangeOverflow: 'Too high',
	rangeUnderflow: 'Too low',
	stepMismatch: 'Invalid',
	tooLong: 'Too long',
	tooShort: 'Too short',
	typeMismatch: 'Invalid',
	valueMissing: 'Required'
}

dogfooding this before merge.


Update the godoc format in connection_config.go file

Closing this PR in favour of https://github.com/turbot/steampipe-plugin-sdk/pull/411


Update/Add pipx to M1 runners

Tool name
pipx
Tool license
MIT
Add or update?

[X] Add
[ ] Update

Desired version
1.4.3
Approximate size
No response
Brief description of tool
This is available on all other images, and is the basis for the GitHub Actions for cibuildwheel, nox, and a lot of other Python tooling. It's also pre-installed in lots of other places too, like the manylinux images for Python.
I think it was supposed to be present in https://github.com/actions/runner-images/pull/7599 (given the name of the PR), but it is not present currently for M1.
URL for tool's homepage
https://pipx.pypa.io
Provide a basic test case to validate the tool's functionality.
pipx run cowsay

Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
Yes if that helps.

Notably, there is no Python present on the image either, usage of https://github.com/actions/setup-python seems to be required to run any kind of Python code since macOS no longer even ships with it. More so, according to https://github.com/actions/runner-images/blob/37a171e44de1f134793d7f0cbff137ca481942ab/images/macos/macos-14-arm64-Readme.md there's no tool cache anymore and setup-python always has to download it? Either way, at least one Python install, along with pipx, would be nice since pipx can then be used with any interpreter that's later installed with actions/setup-python.

Hey @henryiii
The macOS-14 image has been significantly streamlined compared to its predecessors. We removed some packages and programs that could be easily and quickly installed at runtime. Compatibility issues also influenced decisions of this nature. Regarding the stated need to add the 'pipx' package, we will explore what can be done and provide additional information later.

Okay, thanks for looking at it. Having pipx as a supported package manager was very important for composite actions (Python actually didn't matter, since that can be pulled by setup-python and targeted by any pipx, only having pipx actually mattered once activate-environment: false was supported by setup-python). Here's what an isolated action looks like with pipx:

Pipx installed isolated composite action:
runs:
  using: composite
  steps:
    # Set up a non-EOL, cibuildwheel & pipx supported Python version
    - uses: actions/setup-python@v5
      id: python
      with:
        python-version: "3.8 - 3.12"
        update-environment: false
    - run: >
        pipx run
        --python '${{ steps.python.outputs.python-path }}'
        --spec '${{ github.action_path }}'
        myapp
      shell: bash

Now, if pipx is not installed, the simple workaround initially seemed to be:

Pipx not installed incorrectly isolated composite action:
runs:
  using: composite
  steps:
    - uses: actions/setup-python@v5
      id: python
      with:
        python-version: "3.8 - 3.12"
        update-environment: false

    # macos-14 (M1) may be missing pipx (due to it not having CPython)
    - run: |
        "${{ steps.python.outputs.python-path }}" -m pip install pipx
      shell: bash

    # Note that different syntax is required for powershell
    - run: >
        "${{ steps.python.outputs.python-path }}" -m pipx run
        --spec '${{ github.action_path }}'
        myapp
      shell: bash

However, this permanently changes the setup-python provide environment. This makes the composite action surprising (if you try to install something later that is incompatible with pipx's dependencies after running a compatible setup-python call, it will break), and it can affect self hosted runner's environments. That's why you should use pipx instead of pip, but if you have to use pip to get pipx, you are still using pip!
Here's the correct workaround:

Pipx not installed isolated composite action:
runs:
  using: composite
  steps:
    - uses: actions/setup-python@v5
      id: python
      with:
        python-version: "3.8 - 3.12"
        update-environment: false

    - id: myapp
      run: |
        "${{ steps.python.outputs.python-path }}" -u << "EOF"
        import os
        import sys
        import venv
        from pathlib import Path
        from subprocess import run
        class EnvBuilder(venv.EnvBuilder):
            def __init__(self):
                super().__init__()
            def setup_scripts(self, context):
                pass
            def post_setup(self, context):
                super().post_setup(context)
                self.python_path = context.env_exe
                run([sys.executable, "-m", "pip", "--python", context.env_exe, "install", r"${{ github.action_path }}"], check=True)
        print("::group::Install cibuildwheel")
        builder = EnvBuilder()
        builder.create(Path(r"${{ runner.temp }}") / "cibw")
        with open(os.environ["GITHUB_OUTPUT"], "at") as f:
            f.write(f"python-path={builder.python_path}\n")
        print("::endgroup::")
        EOF

    # Note that even more different syntax is required for powershell
    # Also, this workaround requires a __main__ module to run it via -m
    - run: >
        "${{ steps.myapp.outputs.python-path }}" -m myapp
      shell: bash

cibuildwheel has to use powershell on Windows, which makes the workaround even a bit more messy.
Having pipx as a package manager alongside the native package managers like brew was very helpful! (if setup python included pipx by default or via an option, that would also work, but has different implications & effects).

Pipx is present now, but permissions aren'y set up correctly:
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 1311, in mkdir
    os.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/opt/pipx/venvs'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/homebrew/bin/pipx", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/opt/homebrew/Cellar/pipx/1.4.3/libexec/lib/python3.12/site-packages/pipx/main.py", line 916, in cli
    setup(parsed_pipx_args)
  File "/opt/homebrew/Cellar/pipx/1.4.3/libexec/lib/python3.12/site-packages/pipx/main.py", line 863, in setup
    mkdir(constants.PIPX_LOCAL_VENVS)
  File "/opt/homebrew/Cellar/pipx/1.4.3/libexec/lib/python3.12/site-packages/pipx/util.py", line 75, in mkdir
    path.mkdir(parents=True, exist_ok=True)
  File<EMAIL_ADDRESS>line 1315, in mkdir
    self.parent.mkdir(parents=True, exist_ok=True)
  File<EMAIL_ADDRESS>line 1311, in mkdir
    os.mkdir(self, mode)
PermissionError: [Errno 13] Permission denied: '/usr/local/opt/pipx'

While waiting for a fix for this, I was able to work around the permissions issue in my workflow just by adding sudo. Maybe it will work for others as well.

Pipix is added, permissions issue is tracked here: https://github.com/actions/runner-images/issues/9607 and should be rolled out soon too.

Thanks!


Active Edits Date Time Bug

There are inconsistent date/time formats that cause issues.
We save the dates as a timestamp sometimes and mysql other times. DB field type is mysql timestamp so update all time queries accordingly.

@oefada the is no need to use mysql unix format convert, we save the value $this->dateFactory->newStorageDate() (int - which is the timestamp already). So all we need is replace the use of time() with the same time value (see my commit)

this results in the same exact query...
$timestamp = $this->dateFactory->newStorageDate()->toUnix() - $this->expiry;
is equal to $timestamp = time() - $this->expiry;
The problem is that the table is not storing timestamps, it's mysql datetime so the query against an integer doesn't work.
the unit tests don't have coverage for the mysql repository and don't account for data that will exist that is older than the expiry.  if you load some old data, you'll see, all records are returned always.


python311Packages.fastai: 2.7.13 -> 2.7.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.fastai is: The fastai deep learning library
meta.homepage for python311Packages.fastai is: https://github.com/fastai/fastai
meta.changelog for python311Packages.fastai is: https://github.com/fastai/fastai/blob/2.7.14/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.7.14 with grep in /nix/store/yzxza9lm5chs6wcx0srmhhxqh0vvjfrm-python3.11-fastai-2.7.14
found 2.7.14 in filename of file in /nix/store/yzxza9lm5chs6wcx0srmhhxqh0vvjfrm-python3.11-fastai-2.7.14

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.fastai

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yzxza9lm5chs6wcx0srmhhxqh0vvjfrm-python3.11-fastai-2.7.14 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.fastai https://github.com/r-ryantm/nixpkgs/archive/999243158a0b86197ebbb5f930781563c44105e2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/999243158a0b86197ebbb5f930781563c44105e2#python311Packages.fastai

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yzxza9lm5chs6wcx0srmhhxqh0vvjfrm-python3.11-fastai-2.7.14
ls -la /nix/store/yzxza9lm5chs6wcx0srmhhxqh0vvjfrm-python3.11-fastai-2.7.14/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

python311Packages.fastai

Maintainer pings
cc @benxiao for testing.

@ofborg build python311Packages.fastai python311Packages.fastai.passthru.tests


Create a Butane configuration YAML file for the HHGW Flatcar Linux system.

Reference:
fabricator/pkg/fab/recipe/control_butane.tmpl.yaml


Executor can access the k8s apiserver with a out-of-cluster config file

Our production k8s cluster operators have banned accessing the k8s apiserver with an in-cluster strategy (using a service account). We have to configure the executor with a kube config file to access it in an out-of-cluster strategy. It may be helpful for other users.

@alexmt
Changes have been made for custom kubeconfig secret volume name & mount path, and controller config example.
But an irrelevent test always fails and I proposed a fix in #1221 which should be accepted before this  one.

LGTM!


Where can we see updated new of the coin?

I'm researching about it but I cannot find any relevant new on this year. Is this project dead?

No, it's not dead

How can I contribute?

No, it's not dead

its dead man.
the whitepaper is missed...why you lie
no news for a long time
you scammed early investors with atm + mining
so why you say its not dead??????

check whitepaper to see
https://ucacoin.com/#!/white
and also roadmap
https://unitedcryptoalliance.com/roadmap/

Thanks @madlord19
@ucacoin any feedback on those comments?

my friend this team has no idea about crypto....they will not answer.
Everyone has dissapeared, search for verway , try to find any leader of verway(in what ever country) ......to get answers.....
im afraid you wont find anyone...all are hiding....propably afraid
now verway is sold....
its funny

We are currently preparing a new release, please be patient one more time

Closing for now as 3.4.0 is released.


Dark mode modifier

Describe the bug
dark: modifier broken on the last version for native apps :
works fine with ios: android: :
To Reproduce
Steps to reproduce the behavior:

Start project
Run :

import * as React from 'react';
import { View } from 'react-native';

export default function Screen() {

  return (
    <View className='flex-1'>
      <View className="h-20 w-20 bg-primary dark:bg-destructive"/>
    </View>
  );
}

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Platform (please complete the following information):

Type: Browser, Simulator, Emulator, Device
OS: iOS, Android

Additional context

Expo : ~50.0.17
nativewind 4.0.36

Could you please try the canary version (4.0.36)? Several improvements have been made and maybe this issue has been fixed.

What version of Tailwind are you using? Try version 3.4.1; version 3.4.2 introduced some changes to how dark mode styles are generated. I believe it is not handled by NativeWind right now.

I was having problem with the dark mode functionality in my app as well and I found out that I by accident changed the .dark selector in global.css from .dark:root to .dark. Hopefully this can help someone else!


python kernel still up after closing VSCode if extension host is on a linux machine

Environment data

VS Code version: 1.54.3
Jupyter Extension version (available under the Extensions sidebar): v2021.3.619093157
Python Extension version (available under the Extensions sidebar): v2021.3.658691958
OS (Windows | Mac | Linux distro) and version: 20.04
Python and/or Anaconda version: Python 3.8.5 /conda 4.9.2
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local

Expected behaviour
Close python kernel.
Actual behaviour
Python kernel's still up.
Steps to Reproduce:

Open an ipython notebook
Type the following

import torch

a = torch.ones((1,)).cuda()

Close VSCode
Open terminal
nvidia-smi
Check if any python process is consuming GPU memory

Gif:

Logs
N/A

Thanks for the issue @goncamateus. This might either be exclusive to conda or to Linux. I tried it on windows with regular python and the process did disappear.
Tomorrow I'll spin up a VM to see if I can repro. In the mean time, I have a favor to ask you. Cloud you try to repro the same steps, but without conda? That would help a lot!

@IanMatthewHuff @DonJayamanne @joyceerhl Could any of you try this on a mac and see if you can repro?

I don't have an nvidia gpu, u don't need a mac, you need an nvidia gpu for this.
Or better yet, just check if the GPU is being used (i don't think it matters if its nvidia).
Basically the processes should be killed when you exit VSCode.

I tried it with conda, also doesn't repro on windows, this might be only on linux, maybe mac.

@goncamateus, we've made some significant changes to our notebook support. Can you try this scenario in VS Code insiders to see if it still repros?

@greazer yup! Still happening. The kernel does not close and so the process.
https://user-images.githubusercontent.com/9999972/120923997-e17f8180-c6a7-11eb-9ea5-9a578082c3ad.mp4

The same thing is happening on my machine (Ubuntu 21.04), but it's not limited to processes on the GPU.
I am only using interactive windows, but I suspect it's the same issue.
Right now, when you run an interactive window, there will be 5 python processes, 2 of them being related to the kernel and 3 helpers. If you exit VS Code, it will shut down the 3 helper processes, but the 2 kernel processes will remain open. However, if you close the interactive window, VS code will shut down the kernel processes just fine (while the 3 helper processes remain). So the current work around for me is to first close the interactive window and only then close VS code.

@Aleko2286, from what you're describing, this is actually by design. We have traditionally been starting two kernels instead of just one because at one point in our past, getting kernels started could take a long time. Having a second one waiting in the wings to be used on a kernel restart, was the rational for this.
That said, kernel startup times have improved and so starting with builds next week, there should only now only be one kernel process started.

The issue isn't 2 kernel processes being started though, but them not closing on VS code exit. They only close when closing the interactive window manually, but they do not close when youclose VS code right away when the interactive window is still open.

I'm reproing this with WSL.
Before shutdown:
/bin/python3 -m vscode_datascience_helper
/bin/python3 -m ipykernel_launcher --ip=1
After shutdown
/bin/python3 -m ipykernel_launcher --ip=1

I believe this has something to do with the daemon. When I forgot to install python jsonrpc, it didn't repro anymore.

Current guess - python daemon's kill signal is not getting handled by the time the daemon process itself is killed. Might be better to have the daemon kill itself on kill?

Another possibility is skip having the daemon launch the kernel and have raw kernels just launch from the typescript code. Then the daemon wouldn't own the lifetime of the kernel.

Basically we need to fix the daemon to actually kill the kernel on shutdown.

@rchiodo are you still able to repro this issue? I couldn't repro this.

Yes repros on linux machines. I can repro on WSL2

I'm trying with stable build and insiders, instead of the dev version.
Hmm

This should be fixed in the latest pre-release build of the Jupyter extension.


#564 fix documentation warnings

https://github.com/appsquickly/Typhoon/issues/564

Codecov Report

Merging #569 into master will decrease coverage by 2.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #569      +/-   ##
==========================================
- Coverage    89.1%   86.96%   -2.14%
==========================================
  Files         303      295       -8
  Lines        8653     7988     -665
  Branches      542      542
==========================================
- Hits         7710     6947     -763
+ Misses        898      762     -136
- Partials       45      279     +234

Impacted Files
Coverage Δ

Tests/iOS/Typhoon-iOS/main.m
0% <0%> (-100%)
:arrow_down:

...l/CircularDependencies/PrototypePropertyInjected.m
14.28% <0%> (-42.86%)
:arrow_down:

Source/Factory/Internal/TyphoonAssemblyBuilder.m
26.66% <0%> (-26.67%)
:arrow_down:

...ce/Factory/Internal/TyphoonMemoryManagementUtils.m
75% <0%> (-25%)
:arrow_down:

...nal/TyphoonParentReferenceHydratingPostProcessor.m
25% <0%> (-25%)
:arrow_down:

...hoonConfiguration/TyphoonPlistStyleConfiguration.m
65% <0%> (-20.19%)
:arrow_down:

Tests/Model/CROPrototypeA.m
80% <0%> (-20%)
:arrow_down:

Tests/Model/SingletonsChain/NotSingletonA.m
80% <0%> (-20%)
:arrow_down:

...Model/CircularDependencies/PrototypeInitInjected.m
80% <0%> (-20%)
:arrow_down:

...nConfiguration/TyphoonPropertyStyleConfiguration.m
81.25% <0%> (-18.75%)
:arrow_down:

... and 138 more

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 2e8c61b...18f839a. Read the comment docs.

thanks @Emailrus !


Q_CLUSTER is using the database for its broker

This change partially reverts the changes of redis as cache because Q_CLUSTER is not using redis as the broker and doesn't need to.

Q_CLUSTER is not using redis as the broker and doesn't need to.

This wording confuses me a bit..
Are you saying this PR changes the q-cluster broker from redis back to the database?

No, the broker for q-cluster was never changed from the database (even though I thought it was when redis was added as a cache).
This removes the configuration that half setup redis as the broker because there are advantages to keeping q-cluster using the Django ORM (such as the tasks appearing in the Django Admin) as the broker.  This just clarifies what q-cluster is using as the broker.

@nwns actually noticed that when deploying to Kubernetes. If your nodes are somewhat fast it is not a problem. You were talking about changes to InvenTree to enable easier deployment. I have a few instances running in a private RKE cluster rn and did not change anything but a few DB settings and the exchange backend (using something custom). Is there anything remaining that you wanted to change to make it more optimized?

@matmair Not that I know of right now.
I am working through documenting the process of deploying on K8s for dev so that I can verify the current master can be deployed to my liking.  My current production installs are so customised (and old) that I can't just change the image to verify the behaviour of the changes.

@nwns some k8s docs would be very nice. I am a novice in this area so i feel it would be a nad idea for me to do this.
Have you ever done ci - testing of kubernetes deployments? Would be interesting to add this to the release pipeline.

Also don't hesitate to open FRs for customisations you would like to see / options you miss. More ideas are always great!


Support - Upgrade EIP55 package

📝 Description
PR provided by @Tuditi
At the moment ledger apps depend on eip55 v2.1.0. This results in build errors in browser contexts, such as electron.
(https://github.com/iotaledger/firefly/actions/runs/5284776862/jobs/9562554148)
The root cause of this error is that eip55 relies on an old version of the keccak package. This has been fixed in v2.1.1.
This PR aims to update the eip55 dependency.
❓ Context

Impacted projects: @ledgerhq/live-common @ledgerhq/coin-evm @ledgerhq/domain-service
Linked resource(s): ``

✅ Checklist

[ ] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Merged, thanks @Tuditi