Optional Consola

What problem does this feature solve?
Hi,
I have an issue with the latest Nuxt version(2.8.0), especially with "consola".
Our team is using a custom console style something like this: https://hackernoon.com/styling-logs-in-browser-console-2ec0807dc91a
However, because of wrapConsole(), our team's custom console style is not displayed.
Could you get wrapConsole() optional? 👉 https://github.com/nuxt/nuxt.js/pull/5810/commits/7be2f7805389af7f0388c174b788165efbfca993
something like add an option, devConsola = false, in nuxt.config.js?
I can make a PR if you want (devConsola=false or with some nuxt option property name like this),
or could you fix it for our team's console log😭?
or is there any other solution for this situation?
Thanks!

This feature request is available on Nuxt community (#c9289)

Hi, @nh0627. Sure we can make it optional for development mode :)

@pi0 Thank you👏👏👏

@nh0627 What do you think if we just don't override console.log? (But other console log levels). Also as a workaround for now you can try console.__log

Thanks @pi0!
I think if consola.wrapConsole() doesn't override the default console.log, it would be fine. We just basically need default console.log and customize it.

Also as a workaround for now you can try console.__log

BTW, what this means?
I was trying to change our console.log, e.g. console.log("%cHello", "color: blue; font-size: 20px");, to console.__log("%cHello", "color: blue; font-size: 20px");, but still it's broken.
Thank you again!

Nuxt no longer override console.log in 2.8.1: https://github.com/nuxt/nuxt.js/releases/tag/v2.8.1

@pi0 Grate! Thanks a lot


variable explorer not showing some variables

File "C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\spyder\widgets\variableexplorer\collectionseditor.py", line 449, in createEditor
if not editor.setup_and_check(value, title=key, readonly=readonly):
File "C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\spyder\widgets\variableexplorer\arrayeditor.py", line 619, in setup_and_check
self.data.flags.writeable = True
ValueError: cannot set WRITEABLE flag to True of this array

This is fixed in our latest version. Please update by opening the Anaconda Prompt and running there
conda update spyder


The password "Dax???????" is incorrect when creating an advanced windows VM

OS: Win10
Build Version: 20210609.1
Repro Steps:

F1 -> Create Virtual Machine...(Advanced) -> Enter a name -> Windows -> Select a Windows image -> Enter a username
-> Enter an admin password which entered the special character is "?" (e.g. Dxe???????).
Check whether the password is correct.

Expect:
The password is correct.
Actual:
The password is incorrect.

More Info:

This issue doesn't reproduce when creating a Windows VM in portal.

This issue doesn't reproduce when entering the !, @, #, $, %, ^, &, * special characters.
This issue also reproduces when entering the ., =,  +, <, > special characters.

I need to update this special character array to reflect whatever the portal is using: https://github.com/microsoft/vscode-azurevirtualmachines/blob/main/src/commands/createVirtualMachine/PassphrasePromptStep.ts#L78


vendor: OCI Image Spec v1.0.0-rc6

Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master     #928   +/-   ##
=======================================
  Coverage   59.55%   59.55%
=======================================
  Files           5        5
  Lines         759      759
=======================================
  Hits          452      452
  Misses        199      199
  Partials      108      108

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 7fc91b0...f903909. Read the comment docs.

LGTM


doc : suggest shell env var mechanism

It is not clear where and how user-defined environment var should be handled.
I would expect using a dedicated (using prefix MY_ ?) sections in the .env file, so I would find my vars when running 'set' after ./shell.sh
Currently it is not the case (you only export what you know and expect from .env), and I am not in apache/php shell to manually perform export env vars. So I am doing an hugly hack :
in .env I am defining my var like MY_APPLICATION_ENV=development
and in docker-compose.yml I had this under php/environment :
-MY_APPLICATION_ENV
I would like not having to modifiy your docker-compose.yml but at least i see my vars when i run     set | grep MY_  (after ./shell.sh)
Those env vars are expected by my application, for instance, in my index.php I have:
defined('APPLICATION_ENV') || define('APPLICATION_ENV', getenv('MY_APPLICATION_ENV') );
cfg/*.ini are related to third parties applications with specific version
while those vars are related to the application itself and do not change between php versions
As a workaround, .htaccess can be used to declare such var like
SetEnv MY_APPLICATION_ENV development
but I would have to manage different .htaccess for development and production in my github and this file is  #ignored in CLI context :(
Note that my PAAS provider is using environment variables injection, so my bootstrap use more and more getenv()

@normance I made a few tests and it seems pretty simple to accomplish that.
Do the following in docker-compose.yml under the php section:
Just add env_file: pointing to the local .env file:
  php:
    ...
    env_file:
      - ./.env
    ...

Now you will be able to have any value specified in .env to be avilable in each php container.
Can you give this a try and let me know if it works as expected for you,

It works fine, thanks for the support 👍
because of the priority of  environment: over env-file: you could even make this mechanism as default behaviour in docker-compose.yml ?
The reference you provide deserve to be added in your doc, it is very usefull.

@normance glad it works. I will add this to master as well as to the documentation. Let's keep this issue open until its been merged.

It's up for the next release: https://github.com/cytopia/devilbox/pull/130

@normance could you please confirm that it works for you in the upcoming relase: #130 (Detailed Instructions for how to check it out in the comment)

tested with success on REL-012 branch :)

Merged and ready in v0.12


Upgrade Apache Commons Collections to v3.2.2

Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of
vulnerability that exists. By merely existing on the classpath, this
library causes the Java serialization parser for the entire JVM process
to go from being a state machine to a turing machine. A turing machine
with an exec() function!
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103
https://commons.apache.org/proper/commons-collections/security-reports.html
http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/

Thank you for update!

As you can tell by the dates of the checkins, we don't really keep this project up-to-date. We had a customer a while back that commissioned the work. One issue is that the openid connect client libraries are old. However if we update them, they may break it. Then again, without updating the client libraries, this code may not work against the current version of the Gluu Server. If we update the client code, are you willing to test it?

@nynymike - are you asking me if I am willing to test it?  The answer is no. I'm updating ~1000 repositories.

I realized that after I saw your profile on github! Good luck with your mission!


change the JSON parser to the native one

as disucssed with @weefuzzy we had a pre 3.6 home-made parser. we could implement it as a fall back with try like in FluidSound, or just remove it and replace by the following code which is much faster for large DS to dump to dict for instance (via the tempfile)
(
~parse = {
    var str = File.readAllString("zepath");
    var d = str.parseJSON;
    d
};
~dic = ~parse.value;
~dic.postln;
)

Looks like it was changed to the handrolled thing in c1f7725d71748d9c3807f0d8ed607adf78f4f31b because the native parsing was enforcing a change of types somewhere undesirable.

@g-roma do you happen to remember what parseYAMLFie was doing that was undesirable?

I can't remember, but there was some problem.

The problem seems to be that parseYAML and friends make everything a String, e.g.
d = "{\"foo\":[1.0,2.0,3,4,5]}".parseJSON
d["foo"].do{|x| x.class.postln}

-> Dictionary[ (foo -> [ 1.0, 2.0, 3, 4, 5 ]) ]
String
String
String
String
String

🤦
So, I guess the alternative to what we're doing now is to walk the whole Stringified Dictionary after faster parsing and coerce values back to float where appropriate. That may or may not be faster than the current implementation.

see https://github.com/supercollider/supercollider/issues/1154 which has been open since 2014
looks like yaml-cpp doesn't provide a nice way to determine whether a scalar is a string, int or float (see https://stackoverflow.com/questions/19994312/obtain-type-of-value-stored-in-yamlnode-for-yaml-cpp)

Indeed @weefuzzy at the moment I can read faster but I cannot use any of it without converting to float the strings... not super useful :) Slow it stays then, until we find a way around this.

actually, running
i["cols"] = i["cols"].asInteger;

)

(
x = Main.elapsedTime;
i["data"].keysValuesDo{|a,b|i["data"][a] = b.asFloat};
(Main.elapsedTime - x).postln;
)

takes 100% cpu for quite some time. So I don't know what the answer to

That may or may not be faster than the current implementation.

is yet...

ok our version is faster than parsing the dict to itself - although it suddenly occured to me that maybe I'm making an infinite loop by parsing over itself - another test is needed.


fix: update dev scripts and add missing deps

Contains the following changes:

revised development scripts in response to changed dependencies
added missing development dependencies
updated webchat
added DOM.iterable types to support modern iteration methods for various Browser APIs

Coverage: 67.69%. Remained the same when pulling 0f932bd26985361e1df9f33eff58fc97ad9af4c8 on OEvgeny:fix/dev into fa8607a0a1a261fd0d7e7eff1e01b8f3b0d0a734 on microsoft:main.

@cwhitten updated the PR description with the changes made. Let me know if anything is blocking this (I see from Azure the latest PR build got passed)


GraphicsCapturePicker UI needs updating to Windows 11 styling

Proposal: [GraphicsCapturePicker UI needs updating to Windows 11 styling]

Summary

The UI shown by GraphicsCapturePicker hasn’t been significantly updated since introduction, and now looks quite out of place on Windows 11. This UI should be updated to use the new WinUI 2.6 styles
Rationale

Make the OS consistent with all its apps and components (in this case an app might be using this API and would look ugly with it)

Important Notes
Screenshot of what I am referring to

Open Questions

This feedback isn't directly Windows App SDK related. We've reached out to the appropriate team internally so they're aware of the issue 😊


Add Additional Dexcom Functionality

Currently, the only Dexcom vendor/device functions available are
glucose
iter_glucose
iter_glucose_hours
which all obtain glucose values, trend arrow direction, system times, and display times.
There are several other functions exposed by dexcom_reader, including device settings, battery status, and I believe calibration entries. It would be great to add this functionality to openaps.

Happy new year, I think this shipped earlier today.

Looks like the version that shipped has a reversion of some sort. iter_calibrations and iter_calibrations_hours somehow (they both return []), while calibrations returns a truncated list (missing the most recent handful of calibrations). This is what we fixed before, but I'm not sure how it went backward in this release.

@bewest Wondering if the issue is related to https://github.com/openaps/openaps/blob/master/setup.py#L23; should the dependency version be incremented? The issue is fixed when I switch back to https://github.com/channemann/dexcom_reader/tree/wip/fix-pages, which is apparently current with the most recent version of openaps/dexcom_reader, so I'm guessing that updating openaps and running develop installed an earlier version?

How's this:
bewest@bewest-MacBookPro:~/Documents/openaps$ openaps use share -h
usage: openaps-use share [-h] USAGE ...

optional arguments:
  -h, --help            show this help message and exit

## Device share:
  vendor openxshareble

  openxshareble - pure python driver to communicate with Dexcom G4+Share
  over ble.  Allows openaps to use ble to talk to Dexcom G4+Share.

  Examples:

add vendor to openaps
openaps vendor add openxshareble
create device called share to use the new vendor
openaps device add share openxshareble
use it, eg:
openaps use share iter_glucose 2

USAGE                 Usage Details
  GetFirmwareHeader
  ReadBatteryLevel
  ReadBatteryState
  ReadManufacturingData
  ReadTransmitterId
  battery
  calibrations        read calibration entry records
  configure           Configure DEXCOMRX serial number.
  glucose             glucose
  insertion_time      Fetch INSERTION_TIME records from the Dexcom receiver.
  iter_calibrations   read last <count> calibration records, default 10, eg:
  iter_calibrations_hours
                      read last <hours> of calibration records, default 1,
                      eg:
  iter_glucose        read last <count> glucose records, default 100, eg:
  iter_glucose_hours  read last <hours> of glucose records, default 1, eg:
  iter_insertion_time
  iter_insertion_time_hours
  iter_meter_data
  iter_meter_data_hours
  iter_sensor
  iter_sensor_hours
  iter_sensor_insertions
                      read last <count> sensor insertion, removal, and
                      expiration records, default 10, eg:
  iter_sensor_insertions_hours
                      read last <hours> of sensor insertion, removal, and
                      expiration records, default 1, eg:
  iter_user_event_data
  iter_user_event_data_hours
  list_dexcom         Scan the environment looking for Dexcom devices.
                      Returns a list of scanned devices.
  meter_data          Fetch METER_DATA records from the Dexcom receiver.
  scan                scan for usb stick
  sensor              Fetch Sensor (raw) records from Dexcom receiver.
  sensor_insertions   read sensor insertion, removal, and expiration records
                      of sensors
  user_event_data     Fetch USER_EVENT_DATA records from the Dexcom
                      receiver.
bewest@bewest-MacBookPro:~/Documents/openaps$

+1
Awesome stuff; would love to be able to not have my Dexcom receiver physically attached for a variety of reasons. That's all being done on your laptop at the moment, right? Have you tried it with a BT dongle in the RPi?

It's possible to get openaps running on OSX laptop (everything except carelink, if using yardstick1, RL, or similar everything can be done from laptop).
I'm missing a BLE dongle for rpi :-(.  Believe it works out of box for edison, but not sure.

calibrations and sensor readings just shipped, there are now a ton of uses, along with integrated G5 usb support.  Closing for now, many thanks.


Incorrect wavelet plots (scales do not match with build ttf plots)

Seems there is an incorrect implementation of wavelets matlab integration as rendered plots do not match with fft results (which are correct)

to add also ability to use radians instead of cycles


added cram. re-added blastxml and maf

after bcbio-gff pr merged
fixed some new bugs and turned the bam into a cram for testing - works fine now.
Now have 9 track types working with blastxml, bam, bed, cram, gff3, hic, maf, paf and vcf

And I forgot to count bigwig so 10 track types working now.
Got any uses for any of those track types? This could do with some testing.

@bgruening - good timezone!  Can merge please so you can try it out...?


Make the “.” operator work properly in lvalues

This PR adds tests that specify behavior of the . operator in lvalues and adjusts the implementation to match. Specifically, it extends the Juttle grammar and removes incorrect checks in the semantic pass.
Note that member assignment in put/reduce still isn't allowed. Making it work requires more substantial changes which will be done later.
Part of work on #419.

@bkutil

+1


Clean up some documentation around shader warm-up.

Based on recent public discussions.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I signed the CLA.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

cc @liyuqian @chinmaygarde


Trouble with Zoomify Tiles

I am trying to convert from Zoomify to openseadragon. I would like to use my existing Zoomify tile files. I am not getting an image (the page is blank except for the pan/zoom controls from openseadragon). I have tried to implement the "in line" parameters since the zoomify "Image Properties .XML file is non standard for openseadragon. I am pretty sure I am getting something wrong in the code or folder paths.
Here is a link to my zoomify image:
https://jthommes.com/Astro/Zoom/NGC6823_FSQ_PI1_AF2.htm
Here is a link to the openseadragon (non) image:
https://jthommes.com/Astro/Zoom/NGC6823_FSQ_PI1_AF2x.htm
I have attached a snipped image of my file folders.
Can you spot what I am doing wrong? Maybe I just need to collapse the TileGroup_n (0, 1, 2) into one folder?? Any help you can provide would be a great help. Also, let me know if it is not possible for some reason to use my zoomify tiles. If that is the case, I need a desktop App to convert full size images to tiles that are compatible with openseadragon.
You can get source code from the (non) image openseadragon page, but I have included it below:
=========================================

===========================================

Hello,
It seems to me that the tiles url should be like this :
tilesUrl:   "https://jthommes.com/Astro/Zoom/NGC6823_FSQ_PI1_AF2/",
as it should point to the folder of the tiles.

Hello, It seems to me that the tiles url should be like this :
tilesUrl: "https://jthommes.com/Astro/Zoom/NGC6823_FSQ_PI1_AF2/",
as it should point to the folder of the tiles.

That did it! (Sometimes I can be a real klutz). Thanks for the help!


Add Make Target for Downloading Trace Dataset

The ./pkg/tests/end_to_end_tests/ingest_trace_test.go tests require
a dataset file. This file is fairly large, and is stored out-of-band
in a second GitHub repo. This commit adds a make target to make it
easy for folks to download this file into the correct place in the
code tree.

bors r+


Updated Local Development Environment documentation.

Description
Hi,
I have resturctured the Local Development Environment document to have clear instructions. We can consider this is not final draft as the description of the #677 says there are some vital information that needs to be added. I am expecting a review and suggestion list on what needs to be added apart from the existing content here.
I have hosted this documentation here for testing and showing the changes: https://dhivaversion-nearbeach.readthedocs.io/en/latest/002-local-development-environment-setup/index.html
Here are the list of changes made at a high level:

Pushed the below text box to the end and merged with "Start contributing section"

Removed Django reference from docs as these dependencies are already present in the requirements.txt and automatically gets installed. Please let me know if this should be added back

Removed the below warnings and as these are covered in prerequsities

Added a short description

Added prerequities section

Modified setting up the project section

Added whats next section.

Added Dependency :
Added extension: sphinx.ext.intersphinx in /docs/conf.py file
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Database change that requires a migration
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Local manual testing via "./manage runserver"
[ ] Local Python Unit Testing via "./manage test"
[ ] Local Cypress E2E Testing
[ ] Tested on virtual box
[ ] Tested on server

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Sorry. Just done :D


Create HTTP-client from Armeria-annotated interface

Currently, there is no way to create a HTTP-client from the annotations used to create an AnnotatedService. It would be useful to be able to do that to create a client by simply feeding an interface to Clients.newClient().
We would use them in tests, but also in tools talking to the production service. Usage would probably be very similar to armeria-retrofit, but as it would not use the retrofit annotations, the internals may become completely different.
The only framework I know that has this feature(e.g. same interface with annotations can be used for both server and client) is Jaxrs(Jersey), but I don't doubt Spring has it.

https://app.slack.com/client/T1NH00FK9/C1NGPBUH2/thread/C1NGPBUH2-1616066728.020600

Closing this as there are no watchers and not even I would use the functionality anymore.


Make CI builds respect govendor

The latest Viper commit breaks Hugo, but it shouldn't concern the CI builds, but it did.
/cc @moorereason and I guess @spf13 would have to fix AppV.

@moorereason `govendor?´s sync seems to not handle internal packages, which seems like a bug -- but it renders the tool kind of not perfect for Hugo. I assume it is a bug, but I don't have time to investigate it.

I'll try to find time to investigate today.
cf. https://github.com/kardianos/govendor/issues/231

https://github.com/kardianos/govendor/issues/137

OK, now travis seems to "get it" -- so now we have to make the Windows build use govendor => @spf13

This issue has been automatically marked as stale because it has not been commented on for at least four months.
The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still valuable, please open a proposal at https://discuss.gohugo.io/.
This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions.

This is fixed.


eslint plugin exhaustive deps objects false positive

Describe the bug
After upgrade to v4.26.2 eslint considers some internal variables inside queryFn as dependencies.
export function useApi() {
  return useQuery({
    queryKey: ["api"], // Error: The following dependencies are missing in your queryKey: data[0].name
    queryFn: async () => {
      const response = await fetch(
        `https://jsonplaceholder.typicode.com/users`
      );
      const data = await response.json();
      return data[0].name;
    },
  });
}

Your minimal, reproducible example
https://codesandbox.io/p/sandbox/loving-wildflower-7h6sz3?file=%2Fsrc%2FuseApi.ts&selection=[{"endColumn"%3A2%2C"endLineNumber"%3A14%2C"startColumn"%3A1%2C"startLineNumber"%3A3}]
Steps to reproduce

Open codesandbox exaple
See the error

Expected behavior
No error for scoped variables
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
eslint: 8.35.0
@tanstack/react-query: 4.26.1
@tanstack/eslint-plugin-query: 4.26.2
TanStack Query version
4.26.1
TypeScript version
4.9.5
Additional context
Maybe, related: #5069 #5079

@Newbie012 FYI


Switch over to triangle

Meshpy creates a lot of issues for users - will triangle work?

It seems that some users are having issues with meshpy (#42, among others).  This seems to be one of the reasons to switch to triangle.  But, since meshpy is using triangle anyway, why do we think that using triangle would actually fix the random crash issue?  Meshpy does indicate that the triangle it includes has some minor changes, but I doubt it makes a minor change that would cause the issue.
Do we have a minimum working example that causes issues for multiple people?  If it crashes for me, I can try to dig a little deeper and see if I can debug it closer.  Perhaps the issue is about some poor input geometry that we can add a check/correction for in sectionproperties.
This said, I'm not opposed to switching to triangle at all.  But I'm not sure that it will magically fix the random crashes that some people have experienced.
@connorferster - maybe you have a minimum working example that regularly crashes?  Ideally one that works with current master, but one that works with your shapely changes is fine too.

It seems that some users are having issues with meshpy (#42, among others).  This seems to be one of the reasons to switch to triangle.  But, since meshpy is using triangle anyway, why do we think that using triangle would actually fix the random crash issue?  Meshpy does indicate that the triangle it includes has some minor changes, but I doubt it makes a minor change that would cause the issue.
Do we have a minimum working example that causes issues for multiple people?  If it crashes for me, I can try to dig a little deeper and see if I can debug it closer.  Perhaps the issue is about some poor input geometry that we can add a check/correction for in sectionproperties.
This said, I'm not opposed to switching to triangle at all.  But I'm not sure that it will magically fix the random crashes that some people have experienced.
@connorferster - maybe you have a minimum working example that regularly crashes?  Ideally one that works with current master, but one that works with your shapely changes is fine too.

As an example, I see that the mesh is built using the code below.  Maybe the min_angle or mesh_order used here isn't good for some geometries?  At the least, I think these should probably be keyword arguments so that a user could change them.  Probably just accept **kwargs and pass that to the build method.
mesh = triangle.build(
    mesh, min_angle=30, mesh_order=2, quality_meshing=True,
    attributes=True, volume_constraints=True)

As an example, I see that the mesh is built using the code below.  Maybe the min_angle or mesh_order used here isn't good for some geometries?  At the least, I think these should probably be keyword arguments so that a user could change them.  Probably just accept **kwargs and pass that to the build method.
mesh = triangle.build(
    mesh, min_angle=30, mesh_order=2, quality_meshing=True,
    attributes=True, volume_constraints=True)

Hi all,
Have taken a break from sectionproperties this week. Will try and get back into it this weekend. Have been developing an application at work and it has taken a lot of my brain.
I will take a look at the geometry and see if how that contributes to the problem. I found it odd because I was getting this result off of the rectangular section test, which I thought would be predictable. Will investigate further and see what I can find out.
Agreed, if both meshpy and triangle are wrapping Triangle, then I don't know what the difference will be, unless, as @Spectre5 points out, the call to triangle itself may require some tweaking. I think it would be nice if we can make meshpy work but I think I will need to learn more about how Triangle works.
Part of my ambition for working on a shapely interface is to have the geometry "just work" and not require detailed clean-up prior to meshing. I just had a read of the "Troubleshooting" page on the Triangle site and it seems helpful. I will review the problems I am having in more detail and report back: http://www.cs.cmu.edu/~quake/triangle.trouble.html.

Hi all,
Have taken a break from sectionproperties this week. Will try and get back into it this weekend. Have been developing an application at work and it has taken a lot of my brain.
I will take a look at the geometry and see if how that contributes to the problem. I found it odd because I was getting this result off of the rectangular section test, which I thought would be predictable. Will investigate further and see what I can find out.
Agreed, if both meshpy and triangle are wrapping Triangle, then I don't know what the difference will be, unless, as @Spectre5 points out, the call to triangle itself may require some tweaking. I think it would be nice if we can make meshpy work but I think I will need to learn more about how Triangle works.
Part of my ambition for working on a shapely interface is to have the geometry "just work" and not require detailed clean-up prior to meshing. I just had a read of the "Troubleshooting" page on the Triangle site and it seems helpful. I will review the problems I am having in more detail and report back: http://www.cs.cmu.edu/~quake/triangle.trouble.html.

Very weird that you would see the issue with the rectangle test!  That makes me think that it must be something related to the computer setup or the triangle library.  Maybe the wrong binary for you system gets installed from pypi or something?
I think using the triangle binary directly with an input file that causes issues is a very good idea.  Just submit it to the triangle binary many times and see if it crashes.  If so, use the troubleshooting page to debug.  That removes sectionproperties, meshpy, and the python interface to triangle all out of the equation.
I agree that removing all/most of the section clean-up is a huge upside to using shapely!

Very weird that you would see the issue with the rectangle test!  That makes me think that it must be something related to the computer setup or the triangle library.  Maybe the wrong binary for you system gets installed from pypi or something?
I think using the triangle binary directly with an input file that causes issues is a very good idea.  Just submit it to the triangle binary many times and see if it crashes.  If so, use the troubleshooting page to debug.  That removes sectionproperties, meshpy, and the python interface to triangle all out of the equation.
I agree that removing all/most of the section clean-up is a huge upside to using shapely!

https://github.com/PyMesh/PyMesh/issues/115#issuecomment-412429474
PyMesh author describes here how to debug C++ parts of PyMesh, for an issue which seems quite similar. Somewhat fearful of diving into C++ meshing code but will try and give it a go and report in due course (since it is a bit of a show-stopper on what I am trying to do ;) )

https://github.com/PyMesh/PyMesh/issues/115#issuecomment-412429474
PyMesh author describes here how to debug C++ parts of PyMesh, for an issue which seems quite similar. Somewhat fearful of diving into C++ meshing code but will try and give it a go and report in due course (since it is a bit of a show-stopper on what I am trying to do ;) )

PyMesh? Meshpy? What is real life?!?!

PyMesh? Meshpy? What is real life?!?!

@connorferster Ha. Dammit. Sorry, my bad. And I was going to spend tomorrow 'trying' to fix the wrong meshing library. Phew!

@connorferster Ha. Dammit. Sorry, my bad. And I was going to spend tomorrow 'trying' to fix the wrong meshing library. Phew!

Yup, probably the same root cause!  I'm guessing that there is certain inputs or features that triangle doesn't like and are making their way to it.  I still think using triangle directly with an input that fails is the best place to start.

Yup, probably the same root cause!  I'm guessing that there is certain inputs or features that triangle doesn't like and are making their way to it.  I still think using triangle directly with an input that fails is the best place to start.

I haven't had these issues, and I've been running and meshing rectangular geometry in my Hypothesis testing setup repeatedly. Sometimes I will lock up all system resources, but I was assuming that was because it tried to mesh at too small a size (as a result of Hypothesis bounds). It's never errored out when I ran, and since limiting the hypothesis bounds I have no issues.

I haven't had these issues, and I've been running and meshing rectangular geometry in my Hypothesis testing setup repeatedly. Sometimes I will lock up all system resources, but I was assuming that was because it tried to mesh at too small a size (as a result of Hypothesis bounds). It's never errored out when I ran, and since limiting the hypothesis bounds I have no issues.

I haven't either, although I really haven't used it extensively yet.  Again, maybe it is something related to computer setup.
What system are people running?  I'm on Ubuntu 20.04.

I haven't either, although I really haven't used it extensively yet.  Again, maybe it is something related to computer setup.
What system are people running?  I'm on Ubuntu 20.04.

Windows 10
Sent from my iPhone

On Jan 11, 2021, at 11:33, Spectre5<EMAIL_ADDRESS>wrote:

I haven't either, although I really haven't used it extensively yet. Again, maybe it is something related to computer setup.
What system are people running? I'm on Ubuntu 20.04.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Windows 10
Sent from my iPhone

On Jan 11, 2021, at 11:33, Spectre5<EMAIL_ADDRESS>wrote:

I haven't either, although I really haven't used it extensively yet. Again, maybe it is something related to computer setup.
What system are people running? I'm on Ubuntu 20.04.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Will giving this a look once I fix up the doc strings on the new classes and functions (next!)
Sent from my iPhone

On Jan 11, 2021, at 11:33, Spectre5<EMAIL_ADDRESS>wrote:

I haven't either, although I really haven't used it extensively yet. Again, maybe it is something related to computer setup.
What system are people running? I'm on Ubuntu 20.04.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Will giving this a look once I fix up the doc strings on the new classes and functions (next!)
Sent from my iPhone

On Jan 11, 2021, at 11:33, Spectre5<EMAIL_ADDRESS>wrote:

I haven't either, although I really haven't used it extensively yet. Again, maybe it is something related to computer setup.
What system are people running? I'm on Ubuntu 20.04.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi all,
A bit late to the party here, but will try to clarify a few things:

The desire to switch to the python library triangle, is solely to address the installation issues a lot of users face (largely windows users, but here have also been issues experienced on unix systems as well).
I believe the segmentation errors some users are getting are due to corrupt geometry being passed to the c++ triangle routine, but it could also be related to faulty installation issues of meshpy (maybe this is what @connorferster is experiencing with the rectangle test?)
In essence both python libraries triangle and meshpy do exactly the same thing and use the same algorithm, but I believe triangle is more desirable because of the following (discussed in #22):

fewer end-user installation issues (meshpy windows installation cannot easily be automated; requires c++ compiler)
lighter weight dependency (meshpy also handles gmsh & some 3d mesh tools)
more actively maintained

Robbie

Hi all,
A bit late to the party here, but will try to clarify a few things:

The desire to switch to the python library triangle, is solely to address the installation issues a lot of users face (largely windows users, but here have also been issues experienced on unix systems as well).
I believe the segmentation errors some users are getting are due to corrupt geometry being passed to the c++ triangle routine, but it could also be related to faulty installation issues of meshpy (maybe this is what @connorferster is experiencing with the rectangle test?)
In essence both python libraries triangle and meshpy do exactly the same thing and use the same algorithm, but I believe triangle is more desirable because of the following (discussed in #22):

fewer end-user installation issues (meshpy windows installation cannot easily be automated; requires c++ compiler)
lighter weight dependency (meshpy also handles gmsh & some 3d mesh tools)
more actively maintained

Robbie

Have been mulling over & playing around with the Triangle issue. Technically, the particular issues I was having meshing relatively complex imported DXFs (aluminium extrusions with screw flutes etc) can be addressed by tinkering with geometry and meshing settings. (Python) Triangle gives a more accessible way of doing this and throws a python exception so you can go around again with different settings. MeshPy just spits a dummy.
Frankly, though I am a little reluctant to spend more time on it, because of the 'license' on the original C++ Shewchuk Triangle code, which does not quite marry up with the MIT one on this repo:
Please note that although Triangle is freely available, it is copyrighted by the author and may not be sold or included in commercial products without a license.

I was not going to be just calculating section properties for fun ;) Pretty sure I speak for other end users...
I have has a look around for alternatives with no luck yet.
Thoughts? Am I just being a kill-joy?

Have been mulling over & playing around with the Triangle issue. Technically, the particular issues I was having meshing relatively complex imported DXFs (aluminium extrusions with screw flutes etc) can be addressed by tinkering with geometry and meshing settings. (Python) Triangle gives a more accessible way of doing this and throws a python exception so you can go around again with different settings. MeshPy just spits a dummy.
Frankly, though I am a little reluctant to spend more time on it, because of the 'license' on the original C++ Shewchuk Triangle code, which does not quite marry up with the MIT one on this repo:
Please note that although Triangle is freely available, it is copyrighted by the author and may not be sold or included in commercial products without a license.

I was not going to be just calculating section properties for fun ;) Pretty sure I speak for other end users...
I have has a look around for alternatives with no luck yet.
Thoughts? Am I just being a kill-joy?

I believe that the "sold or included in commercial products" would only cause a problem if sectionproperties had an option for a "paid" version or someone used sectionproperties in their paid version of something else. Internal corporate use does not generally trigger a breach of license in these instances. This is similar to the Qt license, I believe.

I believe that the "sold or included in commercial products" would only cause a problem if sectionproperties had an option for a "paid" version or someone used sectionproperties in their paid version of something else. Internal corporate use does not generally trigger a breach of license in these instances. This is similar to the Qt license, I believe.

From the license in the source of triangle.c:
Private, research, and institutional use is free.
Also:
If you are not directly supplying this code to a   customer, and you are instead telling them how they can obtain it for free, then you are not required to make any arrangement with me.

From the license in the source of triangle.c:
Private, research, and institutional use is free.
Also:
If you are not directly supplying this code to a   customer, and you are instead telling them how they can obtain it for free, then you are not required to make any arrangement with me.

Thanks for looking into it, that is my understanding too.  It would be illegal, I believe, to use triangle (and thus sectionproperties) in your own "cross section analysis" tool that you then sold to customers.  At least doing so without the caveat that Connor mentions above.
And whatever licenses issues there are or are not with triangle, that applies to the current code base since it uses meshpy, which uses triangle anyway.

Thanks for looking into it, that is my understanding too.  It would be illegal, I believe, to use triangle (and thus sectionproperties) in your own "cross section analysis" tool that you then sold to customers.  At least doing so without the caveat that Connor mentions above.
And whatever licenses issues there are or are not with triangle, that applies to the current code base since it uses meshpy, which uses triangle anyway.

Are people still having issues with Triangle crashes?  If so, please indicate what system you use.  Maybe it is only any issues on Windows, which might provide some information to consider when debugging.  It can't be only a geometry issue since @connorferster has had issues even using a simple rectangle.

Are people still having issues with Triangle crashes?  If so, please indicate what system you use.  Maybe it is only any issues on Windows, which might provide some information to consider when debugging.  It can't be only a geometry issue since @connorferster has had issues even using a simple rectangle.

The only reports that I have personally received related to installation issues (only windows platforms) & geometry errors. I would be interested to see if @connorferster got the same issues if the python package triangle was used in place of meshpy.

The only reports that I have personally received related to installation issues (only windows platforms) & geometry errors. I would be interested to see if @connorferster got the same issues if the python package triangle was used in place of meshpy.

@"everybody" (not a tag, but still)
It seems that the problem I was having may have been connected to the way I generated the points and facets. I had the first point in the perimeter also as the last point in the perimeter. I fixed this and the problem seems to have gone away.
Now, I am able to get test_rectangle.py to consistently run in pytest and I no longer have my issues when creating the mesh in Jupyter when also using matplotlib to .plot_geometry(). Great news.
Additionally, my tests were crashing because of PlasticSection: I had not reviewed it or updated it yet to see if there were inconsistencies with the new pre-processor. However, my intention is to fit the new pre-processor into the existing CrossSection and analysis interface so it should not require updating.
I am however getting some funny values when calculating g

@"everybody" (not a tag, but still)
It seems that the problem I was having may have been connected to the way I generated the points and facets. I had the first point in the perimeter also as the last point in the perimeter. I fixed this and the problem seems to have gone away.
Now, I am able to get test_rectangle.py to consistently run in pytest and I no longer have my issues when creating the mesh in Jupyter when also using matplotlib to .plot_geometry(). Great news.
Additionally, my tests were crashing because of PlasticSection: I had not reviewed it or updated it yet to see if there were inconsistencies with the new pre-processor. However, my intention is to fit the new pre-processor into the existing CrossSection and analysis interface so it should not require updating.
I am however getting some funny values when calculating g

awesome, good to hear!

Completed in #153.
For casual interest, I did a quick "benchmark" test between triangle and meshpy. I performed the test by first running the test code in one cell (while on the "triangle..." branch), I switched branches, reloaded the imports (with autoreload enabled), and re-ran the same code in a separate cell.
Comparison can be viewed here: https://gist.github.com/connorferster/74c39da3da2710315921d95bc67eb03d
Seems to be a slightly improvement in meshing by using triangle!


"Something went wrong while connecting to instagram" error keeps popping up no matter what

I've tried to use this plugin with different settings, but no matter what I do I end up with the error Something went wrong while connecting to instagram: Throttled by Instagram because of too many API requests.
The only way I can produce the error is by editing the Wordpress post and clicking Update. The plugin doesn't automatically try to post to IG by itself.

This is what I get on the Posts dashboard when it doesn't autopost:
Instagram Status : Never published
Posted : Unknown
Upload info :
When I try to Update, this is what I get:
Instagram Status : Never published
Posted : Unknown
Upload info : Something went wrong while connecting to instagram: Throttled by Instagram because of too many API requests.

I came across those 2 options as well @egozalor. Any other option I've managed to see either scrapped IG auto-publish or just recently pushed it to premium packages.
Sadly, I don't have any hope either. Buffer is about the closest thing I can get to automation, but of course it comes with the manual part of queuing up the posts.


Add node labels option in the plan file to label nodes when they register

Fixes #133
Example, either format will work as the are both map[string]string
worker:
  expected_count: 1
  nodes:
  - host: worker001
    ip: <IP_ADDRESS>
    labels: {"com.koshkin/worker" : "", "com.koshkin/foo": "bar"}
  - host: worker002
    ip: <IP_ADDRESS>
    labels:
      com.koshkin/foo: bar
      com.koshkin/ssd: true

We should have test coverage in our integration suite. My inclination is to add a new subtest to the large clusters we currently deploy, instead of adding a new cluster deployment for testing this.

@alexbrand @dkoshkin was looking at the tests for this and I don't seem to see any negative tests such as if the user enters the following what happens:

labels: {"com.koshkin/worker" : ""}
labels: {"" : "com.koshkin/worker"}
labels: {"" : ""}
labels: {"node-type:test" : ":test"}

Nice, LGTM!


add collectd::plugin::ceph

Class to manage ceph plugin for collectd

Please update the README with docs and add a quick spec test.

added basic test and docs

Great, thanks for all the work!


Release 0.25

Version 0.2.0 being the previous release. The master branch is quite behind of the develop branch. Many useful features have been implemented since then. Perhaps it's time for a half-release, version 0.2.5. Let's use this issue to discuss what's to be include in this version.

What do you think of the version number? We might want to include CNN support in version 0.3.

Dont forget to add unified testing structure.

lol  guys
@dboyliao All there's missing is dropout, then, you'd have a full-blown CNN. Should we add it in?
@mbartling yeah  that's going into the release note

I just finish the dropout name scope parsing thing tonight.
I think dropout is working but I need more tests to be sure.


Navigator.lua broken

Plugin Broken on commit 0d29116b18a0b8321d4c4023e0c96ce014f56b65
jumping back to 7514fa9f works fine for me
Lsp does not startup on loading filetype
update
git bisect good 7514fa9f
You need to start by "git bisect start"

Do you want me to do it for you [Y/n]? Y
git bisect good 7514fa9f
git bisect bad 0d29116b18a0b8321d4c4023e0c96ce014f56b65
Bisecting: 6 revisions left to test after this (roughly 3 steps)
[baad5112d87d61a9d5a07941c6a24a15ce80de40] optimize jump to position
git bisect good
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[05e51f2e7404cea4413baf03231a7de577c4887d] postphone the treesitter loading
git bisect good
Bisecting: 1 revision left to test after this (roughly 1 step)
[f30e5a290d2f1eb4e04c61051808b255488e6650] gopls flags->allow_incremental_sync/debounce update                                                                                git bisect good
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[b08bfd68396b4f0afe6bffe6939760d876e487ea] improve launching time
git bisect bad
b08bfd68396b4f0afe6bffe6939760d876e487ea is the first bad commit
commit b08bfd68396b4f0afe6bffe6939760d876e487ea
Author: ray-x<EMAIL_ADDRESS>Date:   Fri Jul 2 19:32:19 2021 +1000

    improve launching time

 lua/navigator/lspclient/clients.lua | 74 ++++++++++++++++++-------------------
 lua/navigator/lspclient/mapping.lua |  3 +-
 lua/navigator/lspwrapper.lua        |  2 +-
 3 files changed, 38 insertions(+), 41 deletions(-)

the breaking commit is b08bfd68396b4f0afe6bffe6939760d876e487ea
tested with

typescript
rust

The commit reverted. I will check what is wrong with that one.
Thanks!

Should have been fixed

still a lua issue with illuminate
error occurs on d62b03c39419e08edfaa11866555b09acbb514c0
errror does not occur on 7514fa9f7095d7d3c67d033735072af6eab78153
Error executing vim.schedule lua callback: /home/dnehrig/.config/nvim/lua/plugins/lspconfig/init.lua:249: attempt to index field 'illuminate' (a nil value)
config:
local single = {"╭", "─", "╮", "│", "╯", "─", "╰", "│"}
require("navigator").setup(
    {
        default_mapping = false,
        border = single,
        code_action_prompt = {enable = false, sign = true, sign_priority = 40, virtual_text = true},
        lsp = {
            format_on_save = false,
            sumneko_lua = {
                sumneko_root_path = sumneko_root_path,
                sumneko_binary = sumneko_binary,
                settings = luadev.settings,
                on_attach = function(client, bufnr)
                    custom_attach(client, bufnr)
                end
            },
            rust_analyzer = {
                on_attach = function(client, bufnr)
                    custom_attach(client, bufnr)
                end
            },
            tsserver = {
                filetypes = {"typescript", "typescriptreact"},
                on_attach = function(client, bufnr)
                    vim.cmd [[packadd nvim-lsp-ts-utils]]
                    local ts_utils = require("nvim-lsp-ts-utils")

                    -- disable TS formatting since we use efm
                    client.resolved_capabilities.document_formatting = false

                    -- ts utils code action and file import update
                    ts_utils.setup {
                        debug = false,
                        disable_commands = false,
                        enable_import_on_completion = false,
                        import_on_completion_timeout = 5000,
                        -- eslint
                        eslint_enable_code_actions = true,
                        eslint_bin = "eslint_d",
                        eslint_args = {"-f", "json", "--stdin", "--stdin-filename", "$FILENAME"},
                        eslint_enable_disable_comments = true,
                        -- experimental settings!
                        -- eslint diagnostics
                        eslint_enable_diagnostics = false,
                        eslint_diagnostics_debounce = 250,
                        -- formatting
                        enable_formatting = false,
                        formatter = "prettier_d_slim",
                        formatter_args = {"--stdin-filepath", "$FILENAME"},
                        format_on_save = true,
                        no_save_after_format = false,
                        -- parentheses completion
                        complete_parens = false,
                        signature_help_in_parens = false,
                        -- update imports on file move
                        update_imports_on_move = true,
                        require_confirmation_on_move = false,
                        watch_dir = "/domain"
                    }

                    ts_utils.setup_client(client)
                    vim.api.nvim_buf_set_keymap(bufnr, "n", "<space>gi", ":TSLspImportAll<CR>", {silent = true})
                    vim.api.nvim_buf_set_keymap(bufnr, "n", "<space>ae", ":TSLspRenameFile<CR>", {silent = true})
                    custom_attach(client, bufnr)
                end
            }
        },
        on_attach = function(client, _)
            -- float
            if not packer_plugins["illuminate"].loaded then
                vim.cmd [[packadd illuminate]]
            end
            require "illuminate".on_attach(client)
        end
    }
)

I think the early version is incorrect and which cause your code
        on_attach = function(client, _)
            -- float
            if not packer_plugins["illuminate"].loaded then
                vim.cmd [[packadd illuminate]]
            end
            require "illuminate".on_attach(client)
        end

did not been called.
In fact

It is not packer_plugins["illuminate"].loaded ,  it should be packer_plugins["vim-illuminate"].loaded. You did not see the error because in old version of navigator only custom_attach was called. This piece of code was not called. (my mistake)

You do not need vim-illuminate plugin. Navigator provides similar features and in addition, it provides multiple references highlight with k.  I think as navigator works almost same way as  illuminate. You did not notice that the plugin was not attached.

@ray-x i though illuminate was a required dependency for some reason
and yeah should have double checked that code
sorry about that my mistake :b


centralize currencies, collations and calendars

Currently, the proposal focuses on enumerating currencies, collations, calendars, numbering systems, units and time zones.
Out of these, the last three are well-specified: the list of available numbering systems and units is present in the spec, and time zones are specified as all the IANA time zones, which works pretty well.
Unlike the latter, however, the former three are not well specified. If I understand correctly, in the last TC39 meeting, @codehag expressed a concern that this may allow an implementation to return only a subset of the supported values, which I do not think is intended here. Also, as I mentioned above, this is also not internally consistent within the proposal.
I feel that this points to a larger problem in ECMA-402: because we deal with each new proposal one at a time, we may sometimes lose sight of the bigger picture. Let's take currencies as an example: including this proposal, there will be three places where currencies are used in ECMA-402, with both NumberFormat and DisplayNames. While I'm sure all implementations would like to (and infact do) support the same set of currencies in all three places, it is not mandated by the spec IIUC and I think it should be.
One way to solve this (that I managed to come up with, there might be better ones) would be to store lists of these values in internal slots of the Intl object, and normatively require all present (and future) Intl functions to support the entire list from that slot. Mind you, the contents of these lists would still be implementation-defined, but it would ensure that supporting a different set of currencies, for example, in NumberFormat than in DisplayNames would be a spec violation.
@FrankYFTang @sffc what do you folks think?

I agree that it makes sense for all Intl objects to support exactly the same set of identifiers that come out of Intl Enumeration.
We have a section toward the end of the spec that contains a centralized list of identifiers or algorithms for determining that list. Could we put this language in there somehow?

I agree that it makes sense for all Intl objects to support exactly the same set of identifiers that come out of Intl Enumeration.

Good to know that we're all on the exact same page with this.
As I mentioned in the OP, the issue is not new with Enumeration, it just increases the number of redundant lists. I think we can easily do this as a normative (or editorial, since it just potentially changes the result of locale-dependent operations) PR for ECMA-402. But since that would still happen before stage 4, I suppose there will be some changes to enumeration as well.

I believe this might be appropriate to record as an invariant, which will be a way to note the rationale for aspects of the spec and why they shouldn't be changed. https://github.com/codehag/documenting-invariants/ -- I will think a bit about how that may look.

Thanks @codehag, I agree that this would be a good invariant on the 402 side!

This should be a ECMA402 editorial issue, not an issue in this proposal


Add initializers

This PR adds two new initializers: init(uniquingWith:) and init(discardingConflicts:). Closes #19.

The CI workflow for Swift 6 failed to run since Xcode 16 is no longer in beta. I have implemented a quick fix for this.

Here's my feedback for init(discardConflicting:): https://github.com/ladvoc/BijectiveDictionary/commit/dc62d25163c32bb76614d797dec6df5eb581d88d

I suspect that the uniquing problem is more complex than I realize, and that there is a consideration that I'm unaware of. Please let me know if there's something that I'm missing.

Sorry, this review had a lot of feedback. Hope it's not overwhelming. The tl;dr; is I suspect that if we shift the responsibility of resolving conflict to the user, then we can probably eliminate a lot of the complexity elsewhere.
This conversation is probably a good starting point for the review: https://github.com/ladvoc/BijectiveDictionary/pull/24/files#r1759825272

@DandyLyons. Not a problem at all. It is best to get it right the first time—especially for public API. I am reviewing your feedback now.

Not conflicting but related, I made a PR for another possible approach to fixing the uniquing problem: https://github.com/ladvoc/BijectiveDictionary/pull/26


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/47461

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61934


Gradient checkpointing: Wrap tf.keras.Model or tf.keras.layers.Layer in tf.recompute_gradients()

I'm implementing gradient checkpointing with my Tensorflow 2.1 project, following the doc here: https://www.tensorflow.org/api_docs/python/tf/recompute_grad
When I try
model = tf.recompute_grad(model)

it fails, and likewise with
model.layer = tf.recompute_grad(model.layer)

I see that Keras acts differently because tf.recompute_grad() wraps the function with an inner() call, but what should I do to get it working?

+1 to this question, I'm doing something similar with tf-nightly==2.2.0.dev20200119 with custom layers inherited from Keras layers and the docs could use some clarification on "keep a reference to the underlying object around for the purpose of accessing these variables"

+1 to this. would be great to know how to make use of both keras layers and the gradient checkpointing functionality.

no reply.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


sokol_nuklear zig bindings

Hello!
I was looking to add sokol_nuklear bindings to this repository for usage inside of my project, but I noticed that the bindings were all machine-generated. I couldn't find a tool anywhere that would let me generate these bindings, but I did see your blog post.
Could you shed some light on how I can make these bindings please?
Thank you

The important stuff is here:
https://github.com/floooh/sokol/tree/master/bindgen
(I just notice that the readme is incomplete, you'll also need to clone the new D bindings into the bindgen directory: git clone https://github.com/floooh/sokol-d
I think it's best to do roughly the same as sokol_imgui.h (which is a bit special in that there's no example in sokol-zig, because it would require a cimgui+Dear ImGui dependency, instead the example is in a separate repository:
https://github.com/floooh/sokol-zig-imgui-sample
If you get stuck, let me know. Also if you get it working let me also know because then we can add it to the official bindings ;)

Basically:

add a new line here, similar to the sokol_imgui.h entry: https://github.com/floooh/sokol/blob/7b20c1936229370277d1c61bde950bce194de584/bindgen/gen_all.py#L31
add a new line here: https://github.com/floooh/sokol/blob/7b20c1936229370277d1c61bde950bce194de584/bindgen/gen_zig.py#L25
...and here: https://github.com/floooh/sokol/blob/7b20c1936229370277d1c61bde950bce194de584/bindgen/gen_zig.py#L39
...in the cloned sokol-zig subdirectory, add a sokol_nuklear.c file here, with content similar to sokol_imgui.h, don't worry about the Nuklear header dependency yet, this is only needed for building the sokol C library later, not for generating the bindings

Back in the bindgen directory, try running python3 gen_all.py and look for errors. If it works, the sokol_nuklear.h header should have been copied to sokol-zig/src/sokol/c/, and a file `sokol-zig/src/sokol/nuklear.zig should have been created.

Hello, I did the following steps, and I got something simpler than I imagined.
// machine generated, do not edit

const builtin = @import("builtin");
const sg = @import("gfx.zig");
const sapp = @import("app.zig");

// helper function to convert a C string to a Zig string slice
fn cStrToZig(c_str: [*c]const u8) [:0]const u8 {
    return @import("std").mem.span(c_str);
}

So, none of the actual bindings are there. Very strange.

Hmm, I get a different problem which I didn't anticipate:
In file included from sokol-zig/src/sokol/c/sokol_nuklear.c:6:
sokol-zig/src/sokol/c/sokol_nuklear.h:322:2: error: "Please include nuklear.h before sokol_nuklear.h"
#error "Please include nuklear.h before sokol_nuklear.h"
 ^
sokol-zig/src/sokol/c/sokol_nuklear.h:440:24: error: unknown type name 'nk_handle'
SOKOL_NUKLEAR_API_DECL nk_handle snk_nkhandle(snk_image_t img);
                       ^
sokol-zig/src/sokol/c/sokol_nuklear.h:441:60: error: unknown type name 'nk_handle'
SOKOL_NUKLEAR_API_DECL snk_image_t snk_image_from_nkhandle(nk_handle handle);

Problem is that sokol_nuklear.h needs the nuklear.h header even for the declarations, because of the use of nk_handle here:
https://github.com/floooh/sokol/blob/7b20c1936229370277d1c61bde950bce194de584/util/sokol_nuklear.h#L440
...this is actually tricky to solve because requiring the nuklear.h header for bindings generation is a no-go.
I don't have a quick solution to offer, we basically need to get rid somehow of all nuklear.h dependencies (like nk_handle). Maybe with a preprocessor define somewhere...

I don't have a quick solution to offer, we basically need to get rid somehow of all nuklear.h dependencies (like nk_handle). Maybe with a preprocessor define somewhere...

would it be possible to activate the preprocessor ifs from the command line at compile time? and only when building for bindings?

Yep, cleanest solution would be to add a define in the clang call here:
https://github.com/floooh/sokol/blob/7b20c1936229370277d1c61bde950bce194de584/bindgen/gen_ir.py#L102
...maybe this works:
cmd = ['clang', '-Xclang', '-ast-dump=json', '-D', 'SOKOL_BINDGEN', '-c' ]
...and then in the sokol_nuklear.c file we can check for SOKOL_BINDGEN and provide the required Nuklear types directly before sokol_nuklear.h is included, e.g.:
#if defined SOKOL_BINDGEN
typedef union {void *ptr; int id;} nk_handle;
#endif

if the nuklear types have a snuklear_ prefix instead of a nk_ prefix that would work right?
after that, well it's a matter of redefining the nk_ type to snk_ if !SOKOL_BINDGEN.

been working on this for a little while, i have some basic types.
#if defined(IMPL)
#define SOKOL_NUKLEAR_IMPL
#define NK_IMPLEMENTATION
#include "nuklear.h"
#endif
#include "sokol_defines.h"
#include "sokol_app.h"
#include "sokol_gfx.h"
#ifdef SOKOL_BINDGEN
struct nk_context;
typedef union {void *ptr; int id;} nk_handle;
typedef unsigned int nk_flags;
typedef int(*nk_plugin_filter)(const struct nk_context*, nk_handle, int*, int);
#endif
#include "sokol_nuklear.h"

generations go until it reaches a struct nk_context * type. it outputs
Error as_c_arg_type(): struct nk_context *

I believe that the nk_context struct is not being included in the AST dump, and that's why it cannot be found. So, i'm trying to get the nk_ prefix included in the gen_zig.py/gen_ir.py scripts, and I think i'm stuck.
Thanks again.

Hi @chakany, do you have a work-in-progress published somewhere? I'm interested in hacking on this a bit myself as well.
– Dylan

Ah... looks like nk_context is used inside _snk_state_t[1], so its layout actually has to be known. That would seem to preclude the usual opaque pointer tricks without some more significant rewriting of sokol_nuklear.h.
[1] As is nk_font_atlas for that matter...


[DRAFT] PAYMENTS-6796 How we will localise payment error messages

What?
Currently, error messages coming from BigPay are displayed without being translated. Instead, we want to use translated messages based on the error codes.
Open question: How shall we handle non-existing error code?
Why?
So shoppers read payment error messages in their own languages.
Testing / Proof

@bigcommerce/checkout @bigcommerce/payments

I wonder if it's better to perform the translation at the API level. Not sure what's our approach as a platform, but most of our Checkout Storefront APIs are localized.
The problem with this approach is that if a new error code is added in BigPay, it will require a checkout-js release as well. This will make the whole cycle lengthier in order to provide with a translation.
The advantage of having it checkout-js is that merchants could decide to customize the error message in whatever way they wanted.
In saying so, I think both approaches are compatible and complementary. However, if we had to choose one, I think localizing the error messages at the API level might be a better start.

Thanks for the review @capsula4
My understanding in that translations cannot be done in BigPay (I guess it's unaware of the store language). Moreover, we do want  merchants to be able to customise the error messages as well.

We'll probably want to put this behind an experiment to control the rollout (I know, it's still a draft)


return the same function from useRPC

I couldn't figure out how to make useEffect work, so hopefully this seems ok, it does the same thing.


Compared to yolo

Please tell me, which effect is better compared to mmd and yolov5

Kindly ping @hhaAndroid

Kindly ping @hhaAndroid

What do you mean?

@zcswdt This should be determined according to your own needs.


add SR_7270 driver with example notebook

This PR adds a driver for the SR7270 lock-in from Ametek.
Thanks to Elyjah Kiyooka for the work!

Codecov Report

Merging #243 (a8425a6) into main (27b73cc) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #243      +/-   ##
==========================================
- Coverage   19.93%   19.87%   -0.06%
==========================================
  Files         139      140       +1
  Lines       17405    17450      +45
==========================================
  Hits         3469     3469
- Misses      13936    13981      +45

Files Changed
Coverage Δ

qcodes_contrib_drivers/drivers/Ametek/SR_7270.py
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Could you check quick setup script with Cloudsmith mirror?

Describe the bug
I want to install rabbitmq 3.13 with cloudsmith mirror but it is not working.
Maybe mirror server is broken.
Reproduction steps
computer env: amd64 ubuntu 22.04 LTS

copy and paste quick setup script
rabbitmq-server 3.9 installed
after running script, apt update fails with many IGN

E: Failed to fetch https://ppa1.novemberain.com/rabbitmq/rabbitmq-server/deb/ubuntu/dists/jammy/main/binary-i386/Packages  404  Not Found [IP: <IP_ADDRESS> 443]

Expected behavior
After running quick setup script...

apt update is working well
rabbitmq-server 3.13 is installed

Additional context
No response

After creating the issue, I noticed the above statements.

The Cloudsmith repository has a monthly traffic quota that can be exhausted. For this reason, examples below use a Cloudsmith repository mirror. All packages in the mirror repository are signed using the same signing key.

But right now, the time is '2024-04-01T23:08:55.326Z', so... it is hard to think used all of quota.


[Bug]: The object view is missing a locator key.

ODC version
4.2.4
OB version
All
What happened?
When viewing information about tables, views, and other such objects, the ability to locate their position within the resource tree of the target database is not available.

What did you expect to happen?
Supplemental locator keys
How can we reproduce it (as minimally and precisely as possible)?
open a table or other objects.
Anything else we need to know?
No response
Cloud
No response

not bug


Mysql Connections - Can't configure Databases/Catalog Filters

System information:

Operating system (distribution) and version: MacOSX Mojave
DBeaver version: Version <IP_ADDRESS>010041557
Additional extensions

Connection specification:

Database name and version: Mysql
Driver name: Mysql
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
The filter Databases/Catalogs is gray/disabled for Mysql Connections:

Steps to reproduce, if exist:
Edit Connection and go to General Tab and try to create a filter.
I wanted to filter tables like sys, tmp, innodb, etc.
Include any warning/errors/backtraces from the logs

thanks for the bug report.
As a workaround you could use filters, that are available in context menu in DB Navigator

Fixed in 7.3.1.
Ability to choose Database/Catalogs in Connection page added, and tab Schemas/Users disabled.
Also ability to choose Database/Catalogs in Connection page added to Snowflake connection.

filter applying has no effect. Excluded databases are still shown. Also, there is no sync with a filter in DB Navigator

filters aren't applied if the database wasn't reconnected after applying in settings

verified


Initial setup

Created the initial setup for the widget.

Also I think the dist folder can be in .gitignore

investigate


drivers: uart: stm32: Power management is broken after recent commit

Power management for UART is broken after merging PR #63158 made by @erwango .
The code on line 1272 in drivers/serial/uart_stm32.c is actually never called if you don't use  CONFIG_UART_ASYNC_API.
if (pm_device_runtime_is_enabled(dev)) {
	(void)pm_device_runtime_put(dev);
}

I believe that this code should be somewhere around line 1233.
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using?
STM32L4R5
What have you tried to diagnose or workaround this issue?
Measured power consumption and checked clocks for all used peripherals.

To Reproduce
Steps to reproduce the behavior:

use UART with CONFIG_UART_INTERRUPT_DRIVEN and without CONFIG_UART_ASYNC_API

Expected behavior
The power consumption of my system will be the same as before merging this PR.
Impact
UART clock runs all the time and power consumption is about 0.5mA higher
Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows) :  Linux
Toolchain (e.g Zephyr SDK, ...)  :  Zephyr SDK
Commit SHA or Version used :  3.5.0

Are these changes actually tested by someone?

@fabiobaltieri FYI, working on a fix, but might be required to revert

Unfortunately, today I'll miss time and HW to find a proper solution which fixes both issues.
Considering the release timeline, I'm pushing #63907 (revert of https://github.com/zephyrproject-rtos/zephyr/pull/63158) as a lesser evil, which can be merged once confirmed by @coran21 that it is fixing his issue.
I'll work on a follow up fix, but I can't commit it can be fixed in due time for the release


Android - Attachment – Unable to zoom image in preview when upload it after password protected PDF

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.52-0
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: Applause - Internal Team
Action Performed:

Open New Expensify app.
Log in
On a conversation, click on the + button in the compose box
Click on add attachment
Upload a password protected PDF (Attachment 1)
Enter a password (Test12345), confirm and send
Upload an image (Attachment 2)
Verify a preview of the image is displayed before uploading to the conversation
Try to zoom the image in a preview

Expected Result:
Able to zoom image in preview
Actual Result:
Unable to zoom image in preview when upload it after password protected PDF
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/e3c637e8-5909-4212-bde3-3f02fb402224
View all open jobs on GitHub

@twisterdotcom I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

I cannot recreate this and it is also very niche: https://drive.google.com/file/d/13hO6rM3yKW7GSq2Qc7YwLAmgAgJI7nr2/view?usp=sharing


[WM-2140] Allow scrolling in Submission Config

Jira Ticket: https://broadworkbench.atlassian.net/browse/WM-2140

Summary of changes:

What

Set minimum height for table container in Submission Config

Why

Users on smaller computers should be able to scroll inputs and outputs easily

Testing strategy

Tested with different screen sizes

Small screen before and after:
https://github.com/DataBiosphere/terra-ui/assets/67511512/9b610a4f-5053-44bd-bea5-fb71f2e58492
Monitor before and after:
https://github.com/DataBiosphere/terra-ui/assets/67511512/cfb0e349-e516-4c09-80ff-de2f6c663090

@dillydally414 is it possible to completely unfix the top section of Submission config and let the inputs table fill remaining of the page, similar to what we have in GCP?

@dillydally414 is it possible to completely unfix the top section of Submission config and let the inputs table fill remaining of the page, similar to what we have in GCP?

@salonishah11 I will look into what GCP does tomorrow. I think the problem is that the inputs table is filling in the remainder of the page but the remainder is very small.


Add display: none; to remove-diff-signs.css

I have found that running v19.6.26 in Chrome 75.0.3770.100 on our GitHub Enterprise instance running 2.16, content: none; does not work to remove the diff marker, but display: none; does. Also, it appears to throw off the indentation wildly and inconsistently, so for now I've disabled that feature.
An addition line looks like this on GHE 2.16:

Whereas it's a span on Github.com:

The element being span or td doesn't matter, and this PR specifically fixes just diff markers issue.
What you are experiencing on GitHub Enterprise is #2174. It is currently being fixed in #2181.

Please test #2181 and provide feedback there.

Sorry for the trouble and thanks for the PR, but indeed there has a been a bug on GHE. It'll be fixed in the next release

Thanks! I'll wait for the next release, as I noticed the other issues in #2174 as well.


High Sierra: update expected CLT/libcurl pkgconfig file.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Various changes per DP/Xcode/CLT updates released a couple days back.

Holding off on this for a bit to give folks time to upgrade.

Thanks again @DomT4!

Thanks Mike. My VMWare trial license only has 6 days to run, so after that I guess I'll have to make a decision on whether to upgrade my main machine or let someone else take over these PRs.


There is possible to skip login?

Just a question, skip login, or maybe do an autologin?
Thanks!

Currently there are no plans to bypass login.  It is part of the access control system.  Although I wouldn't be necessarily against a pull request ;)

Nice, we need this features and I volunteer myself to make this change and send a pull request. =]
I believe the best place to do this change is in the shipyard v3.
Do you have some code pointers? Which do you think is the best approach, do some kind of auto login where the authenticated user is always the default user or allow Shipyard to run without authenticate user? I think the second option is the better...

:+1:


When the decoder is used together with the canvas, it causes a segmentation fault.

Since the raw_sjpeg_data field is not detected in the decoder_info function, calling strncmp will cause a segmentation fault.

@vinodstanur Could you take a look?

@vinodstanur Could you take a look?


Flickering

I've mentioned this before, but formatting the number causes a weird flicker on iOS.
https://user-images.githubusercontent.com/13172299/150595203-a85a3e13-e433-47a1-8f01-7b844f20c835.mp4
It appears that this is a known RN issue (https://github.com/facebook/react-native/issues/24585).
Interestingly, on Web, there is no flicker:
https://user-images.githubusercontent.com/13172299/150594706-a694fa7c-1405-4f21-9309-79fcfc61bd7e.mp4
This comment says that it can be solved by using defaultValue instead of value. Although it doesn't have many upvotes, so I'm not sure.
Are there any possible alternatives to fix this? Perhaps setNativeProps or something?

Sorry the first video wasn't working at first, I just uploaded a new one.

For example, I wonder if we can setNativeProps inside of onChangeText or onChange directly.

Any updates on this issue?

The flickering happens because of how the TextInput works on React Native. The onChangeText is asynchronous with the native event. Nothing we can do about that


Update runtimes to 1.0.10, 1.1.7 and 2.0.6

This also reverts changes back from ubuntu to debian.  This is temporary until the ubuntu release is ready.

@amanda-tarafa  thanks! I'm going to merge for now to get a release started.  I pinged Ivan and he said he will give it a double check tomorrow (before we push it out)

Let me know when you have push the release, I can test it first (it was failing for me also) and then update the SO thread.


feat(DockerFileLoad): Enable actor file load for docker

Feature or Problem

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Hey @ritesh089 thanks for getting on fixing this -- would you mind setting up sign off for your commits?

Thank you for your contribution @ritesh089 !
This docker compose file doesn't mount a volume where locally built actors are likely to be. Do you anticipate building actors from within the host's container?

Yes . I was mounting a local volume for actors. But I  didnt want to commit that in this PR because I wanted to enable file load first .

@ritesh089 yeah, I'm not sure what the "right" volume mount would look like. But agreed this PR is a nice step in the right direction!

Looks like the checks have passed @connorsmith256 . can we merge this PR ?

Thanks once again @ritesh089 !


Feature Request - Round Alert

Hello!
My previous issues were all discovered while attempting to make a simple "Round X" alert appear in chat at the top of each round.
I can now do that as of 1.5.1, but I have to keep remaking it each combat as alerts are cleared when combat ends.
So I created a macro to help in creating the alert each combat which is pretty good:
const alertData = {
    round: 1,
    roundAbsolute: false,
    repeating: {
        frequency: 1,
    },
    macro: "AnnounceRound",
};

TurnAlert.create(alertData);

The macro "AnnounceRound":
const messageContent = `<hr><div style="color: black; font-size: 1.75em; font-weight: bold;">ROUND ${game.combat.round} START</div><hr>`
ChatMessage.create({ content: messageContent });

This works just fine, but still requires that I run this macro at the start of combat.  I started wondering if, in addition to announcing each player's turn, this module could also optionally announce the round start or end by default?  It would be very useful for using chat log as combat history.
Either that or maybe allow "pinning" an alert so that it won't clear between combats. (not sure how that would operate outside of "top of round" section)
I realize this is a very specific use-case, and I'm not sure if this fits with your vision for the module, but I figured I'd suggest it. Thanks.

Hi! Thank you for the earlier bug reports and your interest in Turn Alert. I'm sorry to say I don't plan on implementing something like this directly. My preference for Turn Alert would be to be as minimal as possible while giving users the tools they need to make their own alerts, rather than adding it's own opinionated alerts by default.
That being said, as I mentioned, I want to make sure the tools are available for you to do what you want. There is a way to achieve the results you want, albeit it does require a bit of initial setup. Essentially we'll create a "world script", which will add a new alert to any combat when it is created.
First, you'll need to create a new file in your world's directory (i.e. in <your foundry user data>\Data\worlds\<your world>) called roundAlert.js. In this file, paste the following code:
Hooks.on("createCombat", (combat) => {
    const alertData = {
        combatId: combat.id,
        round: 1,
        roundAbsolute: false,
        repeating: {
            frequency: 1,
        },
        label: "Announce Round",
        macro: "AnnounceRound",
    };

    TurnAlert.create(alertData);
});

Finally, open the world.json file in the same folder and add the script to the "esmodules" array. It should look like this: "esmodules": ["roundAlert.js"],. The "esmodules" key should already exist, but if it does not, you can add it in just after "compatibleCoreVersion".
This is unfortunately more difficult to edit, although you can of course change your "AnnounceRound" macro to do whatever you wish at the top of the round.
I hope this solution is sufficient for your purposes, if somewhat less convenient than what you were hoping for.

I'm new to scripting in Foundry but I can definitely work with this!
Thanks a lot for the quick and detailed response.


Error when doing undo after toggling comment

Please see the GIF:

Please upload the BCEditor.Highlighter.Comments.pas file.
Thx

Fixed a few bugs.
I don't agree with this:
//// Hello World in Pascal <= wrong

Does not make a sense to comment comments.


add to download all reports

to resolve this issue: https://github.com/kasunkv/owasp-zap-vsts-task/issues/57
I am a C# programmer. I don't know much about Typescript. Can someone please review it and try it?
With this option all reports could be downloaded.

@kasunkv , are you continuing with the development?
There are several things to do. I uploaded one here, but someone has to test it and approve it.

Puedo confirmar que se compila bien y se genera el vsix correctamente:


Heading colors instead of vertical bar

Would it be possible to have headings with different font color instead of (or as an option to) the vertical bars?

If I understand correctly, you should be able to set in style settings

oh i hadn't seen that, thanks a lot!


Make onclick trigger for both mouse and keyboard

Description
Currently, the onclick command for buttons is only executed when the button is clicked using the left mouse button. This pull request changes the behavior of the onclick handler to also be executed if the button is activated using the keyboard (with enter or space).
Usage
Here is a simple example button:
(defwindow example
  :monitor 0
  :focusable true
  (button :onclick "notify-send 'Hello'"
    "Test button")
)

Add the snippet to your eww.yuck and open the widget using
eww open example

You will see a notification for both a left click as well as enter and space.
Additional Notes
Currently, the onclick command is activated as soon as the button is pressed. A side effect of the new implementation is that the command is now executed after the button is released.
Furthermore I was not able to find an equivalent signal handler for the event box widget, hence the keyboard support is only present for the button widget.
Checklist
Please make sure you can check all the boxes that apply to this PR.

[ ] All widgets I've added are correctly documented.
[x] I added my changes to CHANGELOG.md, if appropriate.
[ ] The documentation in the docs/content/main directory has been adjusted to reflect my changes.
[x] I used cargo fmt to automatically format all code before committing

#1187 supersedes this pr which can therefore be closed.
you have been attributed, thank you for your work!


Support for sticky session with kubernetes ingress as backend

Hi
Can anyone suggest if sticky session(cookie based) is supported in traefik with kuebernetes ingress as backend.
I tried the below annotations in my ingress resource but this doesn't work. The request is being routed to multiple pod
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: node-web-app-ingress
annotations:
traefik.stickysession: "true"
Please advise

This PR looks promising but apparently it has not (yet) been implemented for Kubernetes Ingress, but only for Docker and Marathon (see Backend Configurations and search for traefik.backend.loadbalancer.sticky). Any Go volunteers?

Fixed in #1068


Add building of containers using Pipelines-as-code

Build containers automatically using hacbs pipeline. Using docker-build
pipeline, we should switch to java-pipeline in future.

/retest


AwaitExpression.precedence => 14

Fixes #34597

https://dart-review.googlesource.com/c/sdk/+/76880


refactor(context): adjust the usage of throttle

Description
for details, please see the associated PR：https://github.com/antfu/unplugin-auto-import/pull/289
Linked Issues
https://github.com/antfu/unplugin-vue-components/issues/537
Additional context

Thank you. This was a regression, reverted throttle-debounce


⚠ Bofrost.be has degraded performance

In 7bdb1d4, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1354 ms

Resolved: Bofrost.be performance has improved in 6bce0eb after 32 minutes.


Rayon support

Hi! How to use shuttle to test packages based on Rayon? My understanding is that shuttle has no direct support for Rayon primitives, so we need to change source code of Rayon. Is it true? Or is there any existing code base of Rayon adapted for shuttle?
Also, it will be great to add direct Rayon support.

Hi, your understanding is correct, Shuttle has no direct support for Rayon primitives. There is as far as I am aware no existing code base which has a model of Rayon / no fork of Rayon adapted for Shuttle. If you want to exercise code using Rayon under Shuttle you would need to either extend Shuttle to offer the APIs you need, or have a fork / model of Rayon which uses Shuttle's primitives. This would mean swapping out imports of things like Mutexes, Atomics, Rand etc. to use the Shuttle equivalent version.
A few general tips if you want to do this:

See if there is some common primitive(s) you can add, make that "Shuttle-aware", and then model things as usages of that /those primitive(s)
Make a wrapper crate around Rayon which conditionally enables either the regular Rayon or the Shuttle-aware version, depending on some flag (ie #[cfg(feature = "shuttle")]).
Only model the subset of Rayon you are actually using.

Hope that helps, and thanks for your interest :)


Animal Crossing:Wild World

Hi,
I've tried to patch wild world w/ the AR code, yet it's still using HTTPS for connection (packet dumps show). Do you know why?

I don't have this game. Can someone corroborate this issue?

I'm running into this issue as well

I took a closer look at this game and it looks like it copies part of the arm9 binary to ITCM, the hook in particular gets copied to 01FFA3C4. Unfortunately this memory region cannot be addressed directly from ARM7 which is what the Action Replay code engine runs on. And the data seems to be copied so early in boot that the ARDS doesn't get a chance to patch the hook while it's still in WRAM.
Long story short, this game will probably require a game-specific code to be written for it. In the meantime I'd suggest using WfcPatcher if you can.


add a favicon

the site currently doesn't have one, and it's a nice bump in lighthouse.
I very quickly made one up, that's just the "H" in the Belgian flag colors, but really anything would be better than nothing.
the PR with the updates to test out is here:
https://github.com/HackYourFutureBelgium/hackyourfuture.be/pull/37

It doesn't look very good, but maybe this issue could be a good place to add ideas, and we can go from there.

@iLienstAr @colevandersWands Could you validate the favicon proposed by @lpmi-13 ?

Personally, I would suggest something more squared.

We could use the favicon from Amsterdam or Copenhagen.
Otherwise maybe just the letters HYF in Belgian colors? That can be squared and could be recognizable at favicon size

I would go for the same as Copenhagen and Amsterdam, which is the logo in
small (without the Belgian flag in it).
Our original logo is not squared, so I'll ask them for a .png.
Kind regards,
Lien Arits
Community & Communications Manager
Hack Your Future Belgium http://hackyourfuture.be/
+32 (0)492 89 88 19
<EMAIL_ADDRESS>Connect with us on Facebook https://www.facebook.com/HackYFutureBE/ or
Twitter https://twitter.com/HackYFutureBE
Op wo 28 okt. 2020 om 12:41 schreef Evan Cole<EMAIL_ADDRESS>
We could use the favicon from Amsterdam
https://www.hackyourfuture.net/assets/img/favicon/favicon.ico or
Copenhagen https://www.hackyourfuture.dk/static/favicon.ico.
Otherwise maybe just the letters HYF in Belgian colors? That can be
squared and could be recognizable at favicon size
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HackYourFutureBelgium/hackyourfuture.be/issues/38#issuecomment-717878220,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO6RLXJZDOP6P73SNBNOHYLSM77PNANCNFSM4TBBIDBQ
.


feat: add chiado testnet

PR Description
Adds the Chiado network, which is Gnosis' testnet.
Fixed Issue(s)
None
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[ ] I thought about adding a changelog entry, and added one if I deemed necessary.

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


Display current values in secret appearance settings

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem

I have to click on the pencil individually to see the settings of the different secrets.

Describe your ideal solution
As admin, I want to see all secrets' settings without need to go into edit mode individually, to get a better and faster overview of the different settings.
When I open the Secret Appearance settings,
Then I see all the configured settings of each Secret.
When I click on the pencil (edit),
Then I can edit the configuration
Ideally we use the same pattern to read/edit configuration as in the other setting pages.
Version
No response
Environment
ZITADEL Cloud
Additional Context
No response

Hei @mffap, @hifabienne and @peintnermax do you agree that this would be the desired look and feel or do you need something different?

Hei @mffap, @hifabienne and @peintnermax do you agree that this would be the desired look and feel or do you need something different?

Thanks! For me this looks more in line with the other settings.


[Live-Site] 🛑Fixes Tracker

List of issues found uptil now

[x] #859
[x] #864
[x] #865
[x] #860
[x] #855
[ ] Do not check roles from frontend instead add middleware in backend.
[ ] #861
[ ] #754
[ ] Add different icon instead of call one to exit the event(since it's not kind of call)

Extending this issue for further improvements

Check pagination for logs if not present add.
Check all error/normal response messages from server and add proper one's if not added.
Remove more section, not needed as of now
Improve room code modal and get the initial data for this with API. (create ticket and fill all the requirements)
Improve sidebar(placeholder No Mavens in the stream getting not visible and text is also large, do not highlight self user instead show You placeholder maybe('research and implement`))
Add PIP(picture in picture mode) and full screen mode in controls panel (also when pressing F key it should go to full screen and vice versa)
[Bug] When sharing screen and moving to logs tab the screen share doesn't get shown to the self user, ideally it should show the screenshare after that too.


Training and Validation Data as Part of Model Data Structure

Why are the training and validation data put into the model data structure when model.fit is run?  This substantially increases the space, and these parts of the data structure never seem to be referenced.  Thanks!

There are not part of the "model data structure", we just add a pointer to
the current data as a Model attribute. There is not added cost to doing so,
and it's useful to reference the training data from various parts of the
code.
If you need to store the model, you should do it via the canonical way
(refer to the documentation).
On 9 February 2016 at 14:19, Irene Kaplow<EMAIL_ADDRESS>wrote:

Why are the training and validation data put into the model data structure
when model.fit is run? This substantially increases the space, and these
parts of the data structure never seem to be referenced. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/1676.

Thanks for the clarification.


Disable IAM user checks for STS

When a customer intends on using ROSA for clusters with STS
authentication, we do not need the 'osdCcsAdmin' user. We skip those
checks entirely, as well as the cluster simulation.

LGTM