Django SAML: saml2.sigver.SigverError: Can't find ['xmlsec1']

Context
Python 3.6, zappa 0.47.1:
I am trying to setup django_saml2_auth and running into some issues with xmlsec1
saml2.sigver.SigverError: Can't find ['xmlsec1']
The setup works locally, but there are some issues with xmlsec1 running in the AWS Lambda environment. I have tried to build it a number of different ways in docker (using both the Amazonlinux image and lambci python 3.6), but no luck. Steps I've tried:

Build and deploy in docker
Manually copy library files to /var/task/myenv/lib/python3.6/site-packages/lib/ as well as `/var/task/lib/
Manually update PySAML2 xmlsec_binary path
I've also tried to follow: https://github.com/Miserlou/Zappa/issues/1029 and https://github.com/Miserlou/Zappa/issues/1374 with no luck

Expected Behavior
Redirection to SAML login page
Actual Behavior
Traceback (most recent call last):
  File "/var/task/django/core/handlers/exception.py", line 35, in inner
  response = get_response(request)
  File "/var/task/django/core/handlers/base.py", line 128, in _get_response
  response = self.process_exception_by_middleware(e, request)
  File "/var/task/django/core/handlers/base.py", line 126, in _get_response
  response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/var/task/django_saml2_auth/views.py", line 207, in signin
  saml_client = _get_saml_client(get_current_domain(r))
  File "/var/task/django_saml2_auth/views.py", line 99, in _get_saml_client
  spConfig.load(saml_settings)
  File "/var/task/saml2/config.py", line 356, in load
  self.load_complex(cnf, metadata_construction=metadata_construction)
  File "/var/task/saml2/config.py", line 296, in load_complex
  self.load_metadata(cnf["metadata"]))
  File "/var/task/saml2/config.py", line 398, in load_metadata
  disable_ssl_certificate_validation=disable_validation)
  File "/var/task/saml2/mdstore.py", line 850, in __init__
  self.security = security_context(config)
  File "/var/task/saml2/sigver.py", line 1103, in security_context
  xmlsec_binary = get_xmlsec_binary(_path)
  File "/var/task/saml2/sigver.py", line 203, in get_xmlsec_binary
  raise SigverError("Can't find %s" % bin_name)
saml2.sigver.SigverError: Can't find ['xmlsec1']

Steps to Reproduce

Install django_saml2_auth
Setup required configuration steps to connect to SAML
Deploy to Lambda environment
Navigate to SAML login page (django_saml2_auth.views.signin)
Should get the error

Your Environment

Python 3.6, zappa 0.47.1:
Dockerfile:
FROM lambci/lambda:build-python3.6

RUN yum groupinstall -y 'Development Tools' && \
    yum install -y xmlsec1 libxslt-devel libxml2-devel xmlsec1-devel xmlsec1-openssl-devel libtool-ltdl-devel

ARG environment
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8
WORKDIR /var/task

RUN virtualenv dev && source dev/bin/activate && \
    pip install -r requirements.txt

CMD ["bash"]

Have you found any solution?

Unfortunately I was not able to find a solution for this, so went a different route..but still interested in how to solve this

Are you using the slim handler? I am, and noticed that the path to the xmlsec binary was different to what I expected.
I've got XMLSEC_BINARY=/tmp/myapp/lib/xmlsec1 in settings.py.
I also had to set the LD_LIBRARY_PATH environment variable on the lambda to /tmp/myapp/lib in order to get xmlsec1 to find the libraries it's linked against.

Some update?

My solution to making it work in Zappa/Django

Create an AWS EC2 instance, The image have to be identical to the AMI you are going to use for the Zappa/Django. Install xmlsec1 and related packages.
Copy xmlsec1, libxmlsec1.so.1, libxmlsec1.so.1.2.20 to /site-packages/lib in your virtualenv
Install libxmlsec1-openssl and copy lbixmlsec1-openssl.so, lbixmlsec1-openssl.so.1, lbixmlsec1-openssl.so.1.20 to /site-packages/lib
Set xmlsec_binary to "/var/task/lib/xmlsec1" for saml_settings

saml_settings["xmlsec_binary"] = "/var/task/lib/xmlsec1"

I hope it helps.

@weasteam did you run into any permission issue ? I followed all the above steps and worked fine until I run into Permission issue
check_sig: [Errno 13] Permission denied: 'lib/xmlsec1'
Any idea ?


Unify String and Char to integer/float conversion API

Add Char#to_i*, Char#to_i*?, Char#to_u* and Char#to_u*?
Add Char#to_f, Char#to_f?, Char#to_f* and Char#to_f*?
Add String#to_f? and String#to_f*?
Make to_f behaviour consistent with to_i behaviour
Remove Char#to_i with a block and second argument

The char integer and all float stuff still lacks the amount of options the string integer stuff has, but this should be a good first step and unify for the common usages.
Closes #3024

@jhass So much ❤ for this!!
I didn't know how to make to_f raise, because with atof it seemed a bit hard/impossible. I didn't know there was strtof in libc.

In the interest of not blocking this PR on this discussion, I added the whitespace option to String#to_f and companions.


DataSpreadsheet: add column re-ordering

What will this achieve?
This will allow users to re-order the columns within the spreadsheet to a custom order. To achieve this, the user would click and drag the column header cell to a new placement.

How will success be measured?
When columns can be reordered through the interaction described above. See screenshot below for dragging state example:

Additional information

Designs
Existing code
etc

https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/1954 has been opened which adds a selected state to row/column headers. Now that there is a selected state, we know when to add a drag event because column headers can only be dragged if they are in a selected state.


Debug 1668 CI

Debugging CI fail on the (seemingly innocuous!!) #1668.
This PR is not to be reviewed. Please do not review it.

Codecov Report
Patch has no changes to coverable lines.

:exclamation: Current head f643f52 differs from pull request most recent head fd5af19. Consider uploading reports for the commit fd5af19 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:loudspeaker: Thoughts on this report? Let us know!.


Change perm index to correspond to the index in the complete list (;lp)

That was a difficult one xD

ty


Permissions

BkCommonLib version:
TrainCarts version:
Spigot version:

Problem or bug:
Any public permissions? Is it possible to set different permissions for different ranks?
Expected behaviour:
permissions eg: - traincarts.speedlimit
Steps to reproduce:

I like to believe that there are (PermissionDefaults.yml), but after so many years it got outdated/superseded a bit. The big problem is that there are so many ways to change properties: through signs, through applying defaults, through a spawner and through commands. Commands are handled well, and all these properties have permissions for those, but you can quite easily bypass it with a properties sign.
I'd say probably the best way is to revoke permissions for using the property sign and then tailor the command permissions based on rank.


Renamed access instructions to usage notes on shared output page

During refinement we were talking about migrating this fields in squidex


Unable to edit any game stats - aborting store error

When attempting to edit any game and any stat, I receive error stating "An error occurred while setting the value for GMA_X_MINUTES_STAT, aborting store."
Just wondering if this is a known issue or just happening for me.

Are you attempting to reduce the value on an increment only stat?

Are you attempting to reduce the value on an increment only stat?

I am trying to increase the value on it, so similar I suppose yes.

I have the same error, but I don't know if it is possible to change it.


TCPRoute CRD missing on clean install

Welcome!

[x] Yes, I've searched similar issues on GitHub and didn't find any.
[x] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
33.0.0
What version of Traefik are you using?
3.2.0
What did you do?
I'm installing Traefik with Argo CD with following config:
# Chart.yaml
apiVersion: v2
name: traefik
type: application
version: 1.0.0
appVersion: "3.2.0"
dependencies:
  - name: traefik
    version: 33.0.0
    repository: https://traefik.github.io/charts

# values.yaml
traefik:
  providers:
    kubernetesIngress:
      enabled: false
    kubernetesGateway:
      enabled: true
      experimentalChannel: true
  gateway:
    enabled: true
    annotations:
      cert-manager.io/issuer: selfsigned-issuer
    listeners:
      websecure:
        port: 8443
        hostname: "*.bioapp.internal"
        protocol: HTTPS
        namespacePolicy: All
        certificateRefs:
          - name: bioapp-tls
      mqtt:
        port: 1883
        protocol: TCP
        namespacePolicy: All
  ports:
    mqtt:
      port: 1883
      protocol: TCP

And trying to create a TCPRoute as follows:
# tcproute.yaml
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: TCPRoute
metadata:
  name: mqtt
spec:
  parentRefs:
    - name: traefik-gateway
      namespace: traefik
  hostnames:
    - {{ .Values.tcproute.mqtt }}
  rules:
    - backendRefs:
        - name: emqx
          namespace: bioapp
          port: 1883

What did you see instead?
Argo CD fails to create the TCPRoute resource with the error The Kubernetes API could not find gateway.networking.k8s.io/TCPRoute for requested resource bioapp/mqtt. Make sure the "TCPRoute" CRD is installed on the destination cluster.
Traefik logs the following errors:
W1115 15:44:20.132037       1 reflector.go:561] k8s.io/client-go@v0.31.1/tools/cache/reflector.go:243: failed to list *v1alpha3.BackendTLSPolicy: the server could not find the requested resource (get backendtlspolicies.gateway.networking.k8s.io)
E1115 15:44:20.132251       1 reflector.go:158] "Unhandled Error" err="k8s.io/client-go@v0.31.1/tools/cache/reflector.go:243: Failed to watch *v1alpha3.BackendTLSPolicy: failed to list *v1alpha3.BackendTLSPolicy: the server could not find the requested resource (get backendtlspolicies.gateway.networking.k8s.io)" logger="UnhandledError"
W1115 15:44:28.457977       1 reflector.go:561] k8s.io/client-go@v0.31.1/tools/cache/reflector.go:243: failed to list *v1alpha2.TLSRoute: the server could not find the requested resource (get tlsroutes.gateway.networking.k8s.io)
E1115 15:44:28.458046       1 reflector.go:158] "Unhandled Error" err="k8s.io/client-go@v0.31.1/tools/cache/reflector.go:243: Failed to watch *v1alpha2.TLSRoute: failed to list *v1alpha2.TLSRoute: the server could not find the requested resource (get tlsroutes.gateway.networking.k8s.io)" logger="UnhandledError"

The following CRDs seem to have been installed:
$ kubectl get crds | grep 'traefik\|networking\|gateway'
accesscontrolpolicies.hub.traefik.io                    2024-10-29T10:17:40Z
apiaccesses.hub.traefik.io                              2024-10-29T10:17:41Z
apibundles.hub.traefik.io                               2024-10-29T10:17:41Z
apiplans.hub.traefik.io                                 2024-10-29T10:17:41Z
apiportals.hub.traefik.io                               2024-10-29T10:17:40Z
apiratelimits.hub.traefik.io                            2024-10-29T10:17:41Z
apis.hub.traefik.io                                     2024-10-29T10:17:40Z
apiversions.hub.traefik.io                              2024-10-29T10:17:40Z
gatewayclasses.gateway.networking.k8s.io                2024-10-29T10:17:41Z
gateways.gateway.networking.k8s.io                      2024-10-29T10:17:41Z
grpcroutes.gateway.networking.k8s.io                    2024-10-29T10:17:41Z
httproutes.gateway.networking.k8s.io                    2024-10-29T10:17:41Z
ingressroutes.traefik.io                                2024-10-29T10:17:40Z
ingressroutetcps.traefik.io                             2024-10-29T10:17:41Z
ingressrouteudps.traefik.io                             2024-10-29T10:17:40Z
middlewares.traefik.io                                  2024-10-29T10:17:41Z
middlewaretcps.traefik.io                               2024-10-29T10:17:40Z
referencegrants.gateway.networking.k8s.io               2024-10-29T10:17:40Z
serverstransports.traefik.io                            2024-10-29T10:17:40Z
serverstransporttcps.traefik.io                         2024-10-29T10:17:40Z
tlsoptions.traefik.io                                   2024-10-29T10:17:40Z
tlsstores.traefik.io                                    2024-10-29T10:17:41Z
traefikservices.traefik.io                              2024-10-29T10:17:41Z

What is your environment & configuration?
k3s v1.30.6+k3s1
Argo CD v2.12.6
Additional Information
I have read several similar issues, but they seem mostly related to difficulty when upgrading, but this is a clean deployment on a new cluster. It seems strange to me that the grpcroutes.gateway.networking.k8s.io CRD is created but tcproutes is not, since they are both experimental channel. The error logged by the Traefik container seems related to missing TLSRoutes, and again similar issues seemed to mention some missing RBAC, but if I am reading the other issues correctly this should have been resolved in the 33.0.0 release. Thanks for any help, I'm new to this so expect I've made a mistake somewhere.

I did indeed make a mistake, the solution is in the documentation. It is necessary to separately installed CRDs for experimental channel resources as follows:
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.0/experimental-install.yaml


[Question] Is there a way to add Click, Mouseover, MouseOut event to link between two nodes?

[Question] Is there a way to add Click, Mouseover, MouseOut event to link between two nodes?

This can help to show info about the link between two nodes.

Hi @karanbajaj2209,
This isn't currently possible, but I'll convert this into a feature request so others have an opportunity to request it too and/or submit a PR adding the functionality :)


Directly opening DEMOS.sln in 'C:\VulkanSDK\1.3.290.0\Demos' has some issues with the include hierarchy.

The
https://github.com/KhronosGroup/Vulkan-Tools/blob/4c63e845962ff3b197855f3ae4907a47d0863f5a/cube/cube.c#L56
Should be
#include "Volk/volk.h"
And
https://github.com/KhronosGroup/Vulkan-Tools/blob/4c63e845962ff3b197855f3ae4907a47d0863f5a/cube/cube.cpp#L50
Also

This is ultimately an SDK packaging issue, and has already gotten an open issue:
https://vulkan.lunarg.com/issue/home?limit=10;q=;mine=false;org=false;khronos=false;lunarg=false;indie=false;status=new,open
While I could modify vkcube.c/vkcube.cpp to include volk in the 'right' place for the Windows SDK, I'd have to work around that for the local build (eg, this repo on its own). That is very un-fun and brittle. I would much rather the SDK be consistent across platforms so that this repo can use that single location.
Because this is a packaging issue (plus, demo's come the SDK), I am going to close the issue.


Wrong repo link as example?

Under this section https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/use-gitops-connected-cluster#create-a-configuration, there is the mention of this repo https://github.com/slack/cluster-config, should it be replaced by this one https://github.com/Azure/arc-k8s-demo instead? The latter is the one used in the examples right after.

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

ID: d85632de-0573-dbcf-8f25-756b449e58d0
Version Independent ID: d19bfd06-ee59-5198-4820-d436fc6c0ff1
Content: Use GitOps for an Azure Arc-enabled cluster configuration (Preview)
Content Source: articles/azure-arc/kubernetes/use-gitops-connected-cluster.md
Service: azure-arc
GitHub Login: @mlearned
Microsoft Alias: mlearned

Yes, good catch this should point to https://github.com/Azure/arc-k8s-demo

PR approved, do changes will go live soon. Hence closing the issue.


Fixed typo

Changed ContinuosCollisionDetection to ContinuousCollisionDetection in PhysicsEngineFlags.cs and Simulation.cs
See https://github.com/xenko3d/xenko/issues/152

 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.Tehnikumi Opilane seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks! However this a duplicate of PR #293 (which wasn't merged yet because we need an upgrader).

Just realized you also did the other PR!
Sorry I didn't get around writing the upgrader yet.
If you think you can do it yourself, feel free to give it a try!
I can give you some details of what's needed exactly if you want.


Prevent leftover artifacts of TSB breaking builds

Several projects like traffic_monitor will break presently if you build
ATS with the optional build in pkg due to tsb leaving its source code
behind which then gets picked up by the main go mod calls.

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

ATS
Build

What is the best way to verify this PR?

./pkg -v traffic_monitor_build
./pkg -v -o ats
./pkg -v traffic_monitor_build

If this is a bug fix, what versions of Traffic Control are affected?

master

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

@jhg03a TSB no longer breaks builds after #5639 was merged. Can #5635 be closed?


O(1) buffer next capacity computation

Motivation:
Enlarging buffers approaching 4 MiB size requires n iterations
Modification:
Use a single instruction to compute the next buffer capacity
Result:
Faster/Simpler calculateNewCapacity

@franz1981 thanks a lot!


Arc-length State Initialization

Hi @alexliniger ,
If I understand the paper referenced in this repository correctly, arc-length of the parameterized path acts as one of the states for MPCC. And at each time step all states need to be initialized using the actual current states of the vehicle to predict over the prediction horizon. What is the best way to initialize arc-length (theta)? Is it advisable to just take the previous time step predicted arc-length, or should one calculate the exact optimal arc-length by projecting the current vehicle position on to the parameterized reference path i.e. solve Eq. 8 at each MPCC time step just for initialization of one state? Please let me know.
Kind Regards
Pranjal Biswas

You can see in the code that I used the findTheta function to compute the arc length of the current position (theta_0), however, all the other thetas are taken from the previous solution (which is shifted in the function augState)
I hope this helps,
Alex


Add Makefile with publish and dnslink tasks

This publishes to the dmca.denylists.lists.refs.ipfs.io subdomain, which nginx will map to.

This works great so far btw, I largely copied it from the website's Makefile

hahahahha gotta love that subdomain.

yeah, i really should make a resolver that reverses DNS and uses paths.
cat /dns/ipfs.io/refs/lists/denylists/dmca
curl fs://dns/ipfs.io/refs/lists/denylists/dmca

Heh took me a bit to understand ;)
For now I thought of making this a convention at the nginx layer:
https://ipfs.io/refs/*
=> /ipns/*.refs.ipfs.io

@lgierth convention SGTM.
For the future: https://github.com/jbenet/random-ideas/issues/36

@lgierth this LGTM -- lmk when i should merge (or go for it) as i saw you just pushed something else


VyprVPN 5.1.2 Crack + Serial Key Free Download 2024

[VyprVPN 5.1.2 is a Swiss-based VPN company that’s experienced major changes and enhancements over the past couple of years. In this up-to-date and fresh VyprVPN review, we’ll look at how the service does and how it compares against rivals. Although it may not wow you with its marketing or exaggerated assertions, VyprVPN can make your life easier by allowing the unblocking from Netflix or other services streaming, as well as providing users with fast speeds and also allowing access to streaming services safely. Through this program, you will be able to connect to more than 70 sites worldwide. It lets you join the Internet from anywhere in the globe, no matter whether you’re in Germany or the United States, or somewhere in between, and surf as if you were there.
Download Here

✅▶▶DOWNLOAD VyprVPN Software Pro
✅▶▶MIRROR VyprVPN Software Crack


Uncaught Exception: Attempting to call a function in a renderer window that has been closed or released. Function provid

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.1
Time: Tue Apr 12 2016 12:31:06 GMT-0500 (Central Daylight Time)
Error:
Attempting to call a function in a renderer window that has been closed or released. Function provid
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: Object.<anonymous> (C:\Users\DiGriz\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\inject\GPMInject\interface\mouseButtonNavigation.js:8:8.
    at BrowserWindow.callIntoRenderer (C:\Users\DiGriz\AppData\Local\GPMDP_3\app-3.0.1\resources\atom.asar\browser\lib\rpc-server.js:201:19)
    at emitTwo (events.js:92:20)
    at BrowserWindow.emit (events.js:172:7)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #470

You are running an outdated version if the program.
Please can you upload your squirrel log found at %LOCALAPPDATA%/GPMDP_3 so I can figure out why you aren't updating


Always use benchmark-operator for service account

The service account name is hard coded in some of the workload
roles, ie:
https://github.com/cloud-bulldozer/benchmark-operator/blob/master/roles/fio_distributed/templates/servers.yaml#L48
If someone were to change the fullnameOverride in values.yaml the
workload would fail.

Can one of the admins verify this patch?


Add testnet (Whatsonchain still in the process of building it out)

This API is still in active development at https://developers.whatsonchain.com/#introduction
and so currently only has a limited feature set. Nevertheless it is a start!
The most difficult aspect will be that there is no way currently to update the UTXO set... so the only way to send on testnet at the moment will be to manually create Unspents. Be patient...
BitIndex have plans to include Testnet and STN support in the near future
There is also a possible plan in the near future for a "Bitcoin node as a service" (via RPC)
--> Which in theory would be the most amenable to use in some kind of RegTest setup (#16 ).

Hey! Busy now, let me get back to you on this.

@AustEcon I wanted to let you know that BitIndex now supports Testnet and STN!
The new v3 endpoints are now available and you can select the chain.
Examples: http://github.com/bitindex/bitindex-sdk
Thanks again!

@attilaaf Oh wow! This is amazing news! Can't wait to wire that all up! :) I'm sure users of bitsv will be stoked as well!
Thanks for all of the hard work!

Thank you ! :)

I'm sorry for missing this. Lots of little things going on over here. Feel free to ping me if you need anything.
Also, thank you @attilaaf, this sounds great.

Thanks again guys!
I wanted to follow up quick on the 502's recently.
Basically we've been experiencing a lot of growth in traffic and one of our servers disks were slow and causing a backlog of requests and then timing out other upstream links.
I've upgraded and fixed the problem and also added a caching layer on the backend to mitigate the problem and have a new architecture in the works to be more resilient too.
Thanks again and looking forward to seeing this library evolve.


Cannot run cli magento-installer

Trying on latest W10. Is it trying to create a folder with ':' in it?
`PS C:\laragon\www\docker\meanbee-magento2-01> docker-compose run cli magento-installer
Starting meanbee-magento2-01_appdata_1 ...
Starting meanbee-magento2-01_dbdata_1  ... done
Starting meanbee-magento2-01_db_1      ... error
Starting meanbee-magento2-01_appdata_1 ... done
ERROR: for meanbee-magento2-01_db_1  Cannot start service db: b'driver failed programming external connectivity on endpoint meanbee-magento2-01_db_1 (f28f7150288a8a38e7f5d03d74c0e9f20383a97b1043a4c3e3126c01e877b14b): Error starting userland proxy: mkdir /port/tcp:<IP_ADDRESS>:32827:tcp:<IP_ADDRESS>:3306: input/output error'
ERROR: for db  Cannot start service db: b'driver failed programming external connectivity on endpoint meanbee-magento2-01_db_1 (f28f7150288a8a38e7f5d03d74c0e9f20383a97b1043a4c3e3126c01e877b14b): Error starting userland proxy: mkdir /port/tcp:<IP_ADDRESS>:32827:tcp:<IP_ADDRESS>:3306: input/output error'
ERROR: Encountered errors while bringing up the project.`

Edit: seems that the docker installation has common issues not related to this project.


Greytide Virus bolts open all department doors it targets, including doors that are a part of different grids

Description
PR #33547 introduced the Greytide Virus, an event that bolts open doors and unlocks lockers of the department it targets, depending on severity.
Unfortunately it appears that the event targets doors/lockers on entirely different grids, so grids like the Evac Shuttle and CC are affected by the virus as well.
Reproduction

Experience the Greytide Virus event
Go to CC or Evac Shuttle
Witness doors bolted open, lockers unlocked on those grids

Screenshots

Feature? :trollface:
Greytide worldwide memes and all that I mean.


Auto increment does not work in mysql

Setting auto increment field in entity framework does not work with mysql. I found this issue when I was trying to save a basic model with two properties:
public class User
{
    [DatabaseGenerated(DatabaseGeneratedOption.Identity)]
    [Key]
    public int Id { get; set; }
    [Required]
    public string Name { get; set; }
}

When I wanted to save a new user to mysql database I got an exception

Field 'Id' doesn't have a default value

private TetrominoContext _dbContext;

public HomeController(TetrominoContext dbContext)
{
    _dbContext = dbContext;
}
public IActionResult Index()
{
    var user = new User {
        Name = "Whatever"
    };

    _dbContext.Users.Add(user);
    _dbContext.SaveChanges(); // Throws exception
}

InnerException  {MySql.Data.MySqlClient.MySqlException: Field 'Id' doesn't have a default value
at MySql.Data.MySqlClient.MySqlDataReader.ActivateResultSet(ResultSet resultSet)
at MySql.Data.MySqlClient.MySqlDataReader.d__62.MoveNext()

I tried different combinations of [DatabaseGenerated(DatabaseGeneratedOption.Identity)] and [Key], but with no luck.
These are all of my packages:
 <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.2" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.3" />
    <PackageReference Include="Microsoft.AspNetCore.NodeServices" Version="1.1.1" />
    <PackageReference Include="Microsoft.AspNetCore.StaticFiles" Version="1.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="1.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="1.1.1" />
    <PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="1.1.2" />
    <PackageReference Include="Microsoft.VisualStudio.Web.BrowserLink" Version="1.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="1.1.2" />
    <PackageReference Include="Pomelo.EntityFrameworkCore.MySql" Version="1.1.2" />
  </ItemGroup>

And my migration:
    [DbContext(typeof(TetrominoContext))]
    [Migration("20170625090637_SixthMigration")]
    partial class SixthMigration
    {
        protected override void BuildTargetModel(ModelBuilder modelBuilder)
        {
            modelBuilder
                .HasAnnotation("ProductVersion", "1.1.2");

            modelBuilder.Entity("Tetromino.Models.User", b =>
                {
                    b.Property<int>("Id")
                        .ValueGeneratedOnAdd();

                    b.Property<string>("Name")
                        .IsRequired();

                    b.HasKey("Id");

                    b.ToTable("Users");
                });
        }
    }

My Startup.cs:
public class Startup
    {

        public Startup(IHostingEnvironment env)
        {
            var builder = new ConfigurationBuilder()
                .SetBasePath(env.ContentRootPath)
                .AddJsonFile("appsettings.json", optional: false, reloadOnChange: true)
                .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
                .AddEnvironmentVariables();
            Configuration = builder.Build();
        }

        public IConfigurationRoot Configuration { get; }

        // This method gets called by the runtime. Use this method to add services to the container.
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddMvc();

            //services.AddEntityFrameworkMySql().AddDbContext<TetrominoContext>(options => options.UseMySql(Configuration.GetConnectionString("MySqlConnection")));
            services.AddEntityFrameworkMySql().AddDbContext<TetrominoContext>(options => options.UseMySql(Configuration.GetConnectionString("LocalTestDbConnection")));
        }

        // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
        public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {
            loggerFactory.AddConsole(Configuration.GetSection("Logging"));
            loggerFactory.AddDebug();

            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
                app.UseBrowserLink();
            }
            else
            {
                app.UseExceptionHandler("/Home/Error");
            }

            app.UseDefaultFiles();
            app.UseStaticFiles();

            app.UseMvcWithDefaultRoute();
        }
    }

This is an issue with the MySQL provider. Their issue tracker is here: https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/issues

Fixed in 2.0

I checked my migrations. When was developing it in Development mode was using Sqlite, so added annotations for MySql also, but missed on some other columns, then created the database.
This error came up, and have figured out that on some other Id columns I missed MySql annotations, then added for those also. Still was getting the same error, because after final fix have to drop the database and run again.
Now works fine!


HIP: PoC Distance Limit

rendered

Distance limitation is a huge step towards my proposal for "HIP 100" Currently the SINR levels in the network are unmanageable.  The distance limitation should be dynamically assigned similar to the Transmit scale based on the the HEX structure and whether neighbor HEXes are empty or populated

@evandiewald you were going to add that extra commentary here right?

@abhay see #383

Hi @abhay,
Could you please clarify something on Discord?
BigBarki#6528
Much appreciated.

Could you please clarify something on Discord?
BigBarki#6528

Sure ping me in the channel

Could you please clarify something on Discord?
BigBarki#6528

Sure ping me in the channel

Thanks for your quick response Abhay. I can't find you on Discord, is there a possibility that you add me, we'll talk there.


HAWKULAR-985 - Removed direct dependency on secret store.

@jpkrohling you can't upgrade Metrics right away. There are too many impacts (UI, Pinger, AvailCreator, Charts) which I have started to analyze (I will send an email today).

Alright, I'll remove the change to metrics then.

@jpkrohling just restarted the build, it seems something weird happened with npm install


Correctly set appID in builtin app

Summary
Correctly set appID when the state is read.
I also added some more error wrapping to make debugging easier.
Ticket Link
Fixes https://github.com/mattermost/mattermost-plugin-apps/issues/306

@DHaussermann I suggest merging this ASAP since the master is broken without it?


webhooks/gitlab: Stop filtering comments when description is null.

We filter out hidden comments out of Issue descriptions but this
breaks when description is null (which is unusual). So this commit
just checks to see if the description is None and if so, not to
filter anything out.
@timabbott: FYI :)

Tested locally and merged, thanks @eeshangarg!
I'm not sure what's up with CircleCI hanging on this one.


single-file version?

Is there a single-file version of this - I was going to translate it to a single file c/c++ module but the multi-file distribution in the git is a pain. It's interesting the scale of this - as I wouldn't have thought generating NHS numbers would have been a complex task...

My general feeling is that this somewhat out of scope for this project. There are, as they say, lots of ways to skin a cat (why do they say that?), and I think in this project we are throwing our collective weight behind python. There is no imperative to do this, except that python is very accessible, is a language familiar to the health tech and academic community, and we have PyPi which is a great resource for packages. We want colleagues engaging in health systems research, or potentially delivering clinical care, to be able to focus on building the thing, not wrangling with esoteric modulus 11 algorithms and the vaguaries of regional number ranges and so. And as with discussions elsewhere - it is built with simplicity in mind, but with complexity available if you want it. I think if there is a different use case that requires binaries/another language, that should be another project. It could for sure inherit from this one, but my view is that it is hard to maintain in the same repo and I am not that clear what the end product would look like.

Not a focus for this project. The Python code here is freely available; if others want to generate a parallel C/C++ implementation then they can use this as a template if they so wish.

Not a focus for this project. The Python code here is freely available; if others want to generate a parallel C/C++ implementation then they can use this as a template if they so wish.


refactor: optimizeDeps back to top level

Description
In the current Environment API design, we made every top-level option act as a default for all environments. To make that happen in a backward compatible way, and because deps optimization is dev only, we moved optimizeDeps (only applies to client) to dev.optimizeDeps (default for all environments).
Even if consistency is improved, this also brings issues. In https://github.com/vitejs/vite/pull/18397/files, we had to use:
  environments: {
    client: {
      dev: {
        optimizeDeps: {
          include: [ 'gsap' ],
        },
      },
    },
  },

instead of
  optimizeDeps: {
    include: [ 'gsap' ],
  },

to avoid gsap to also be optimized during SSR. Apart from the three extra levels of nesting environments.client.dev., this is bad because we now need to explain what environments are for users that are building a simple SPA/MPA. The config for them, should still works configuring the whole app at top level.
This triggered @bluwy into exploring some design changes to the Environment API: https://github.com/vitejs/vite/discussions/18415. We explored reducing the needed nesting and exposing environments with https://github.com/vitejs/vite/pull/18439. But the design gets more complex and the user still needs to understand environments in the case above even if using a top level client.
This PR starts some changes discussed in this thread. The idea is that we are going to change the concept of top-level props from being "defaults" to "app configuration". Environments will in general inherit from these options, but some top-level options will only affect the client because they don't make sense as a general default for all environments (optimizeDeps is a good example, also dev.warmup will probably be client only). This means that a user building a SPA/MPA can configure their app (that has a single environment, the client) using only top-level keys. And when other environments are added later (if SSR is introduced), it can configure them with environments.ssr. But until then, there is no need to know what an environment is. environments.client will not get much use in general after this PR.
This change will also avoid needing to ask users to move from optimizeDeps, that would have resulted in a lot of config changes and churn.

Honestly, I thought it already works like this 🫣

Ok, let's go with this approach then


Fix azure terraform

What this PR does / why we need it:
Fresh versions of azurerm provider require those changes, so keeping up to date config.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

keep azure terraform config up2date

/retest

/retest


WIP: lazy attribute support

Implements #10345
This is very much not the poise-derived solution.
This allows the user to store procs/lazy-evaluators into the attribute tree.  Those are saved into the merged view of the node object.  On access, the proc is evaluated before the value is given back to the user.
This allows the user to lazy derived attributes:
default['user'] = "Avasarala"
default['homedir'] = lazy { "/home/#{node['user']}" }

Since the proc is saved in the deep merge cache rather than the evaluated value, the result is truly lazy:
default['user'] = "Avasarala"
default['homedir'] = lazy { "/home/#{node['user']}" }

# prints "/home/Avasarala"
puts node['homedir']

override['user'] = "Amos"

# prints "/home/Amos"
puts node['homedir']

The user can arbitrarily mess with the dependent variable in recipe code and the lazied attribute should change accordingly.
The access through the precedence level is still the proc (this is pretty much a feature not a bug and trying to change this behavior would cache the lazy evaluation on first access):
default['user'] = "Holden"
default['homedir'] = lazy { "/home/#{node['user']}" }

# prints something about being a proc defined on some source line
puts default['homedir']
# prints "/home/Holden"
puts default['homedir'].call

It also supports recursive laziness
default["program"] = "ganymede"
default["program_var"] = lazy { "/var/#{node["program"}" }
default["program_cache"] = lazy { "#{node["program_var"]}/cache" }

default["program"] = "phoebe"

# prints "/var/phoebe/cache"
puts node["program_cache"]

This will not work with poise-derived, users will get poise-derived behavior (which I suspect has been broken for several major releases of chef-client now)
Note that since it returns a real value on access, that means it does not lazy the value all the way to converge time in the recipe context, it will still be necessary to lazy the access in recipe code as well.  There is technically a breaking change issue here, because users may have figured out that they can already pass a lazy proc into an attribute and pass it to a property which will lazy the evaluation (and lazy it all the way to converge time).  This change enhances the former behavior -- any user that was trying to work around the derived attribute issue will have found that it fails when passed into e.g. template variables without littering their templates with ".call" modifiers and such, which this PR fixes.  However it necessarily breaks lazy procs in attributes from being lazied all the way to converge time, which uses may have abused as a feature, or may have just accidentally become dependent upon.  This is actually better behavior since having the contents of the attribute control the evaluation at converge time is going to surprise people who overwrite the attribute and lose the behavior as well.  There is no good way to deprecate this behavior since it requires very, very spooky action at a distance (the evaluation of the proc by the property does not have any information about the proc being declared immediately in the recipe code or distantly from the attributes file, and a lazy proc in the attributes file might not require the behavior of lazying to compile time so some very distant coordination would be required to accurately emit a deprecation -- and doing this with cookstyle would be impossible).  At the same time the amount of cookbooks using this trick that will break should be very, very low.
It looks like there's only two groups of cookbooks on the supermarket that have discovered this trick:
alfresco-appserver/attributes/default.rb
alfresco-appserver/attributes/tomcat.rb
alfresco-db/attributes/mysql_local.rb
alfresco-transformations/attributes/default.rb
kafka/attributes/default.rb
kkafka/attributes/default.rb

Those seem to be using lazy {} in order to do derived attributes so presumably would still work okay, but no other cookbooks should be affected.
BONUS FIX:
The deep merge code was calling ImmutableMash#[] while merging arrays which was incurring additional expense and complexity in invoking all the decorated state_tracking stuff and other calls in the inheritance heirarchy on those.  Similarly to how we use the Mash#internal_set API in that routine to set values without going through convert_value this introduces a change to use the new Mash#internal_get API which directly gets the value from the underlying Hash without any magic associated with it.  This should provide at least a little bit of perf boost to the deep merge caching routines, and it eliminates an infinite loop that I created here.

Just to be clear, does the proc converge on first-read, or will it be re-evaluated on every read? In other words if I do:
file 'whatever' do
  owner node['user']
end

file 'whatever2' do
  owner lazy { node['user'] }
end

and assuming user is lazy, per your example, does the second file get screwed by the value already being resolved in the first file?
Your description implies so, but that doesn't seem super bad. I'm not familiar enough with the code to know for sure at a quick glance without paging in the attribute code.

Just to be clear, does the proc converge on first-read, or will it be re-evaluated on every read? In other words if I do:
file 'whatever' do
  owner node['user']
end

file 'whatever2' do
  owner lazy { node['user'] }
end

and assuming user is lazy, per your example, does the second file get screwed by the value already being resolved in the first file?
Your description implies so, but that doesn't seem super bad. I'm not familiar enough with the code to know for sure at a quick glance without paging in the attribute code.

Yeah that's the second example, it is truly lazy on every read rather than caching the first evaluated return value.
node['user'] = lazy { node['real_user'] }

node['real_user'] = "phil"

file 'whatever' do
  owner node['user'] # this would have magically been "lazied" to converge time before this change and would be "dibowitz", but now is "phil"
end

file 'whatever2' do
  owner lazy { node['user'] } # this will be "dibowitz"
end

ruby_block "print it" do
 block do
   puts node['user'] # this will now print "dibowitz" (before it would print out something about it being a Proc)
end

node['real_user'] = "dibowitz"

Note that in the new behavior only the second property is evaluated lazily at converge time.
In the old behavior node['user'] was implicitly lazied all the way to converge time because the attribute carried a lazy block which was presented directly to the property.
In the new behavior the laziness is more directly exactly what is written and the first property will not have a lazy value.  When ruby parses the attribute at compile time the lazy proc will be evaluated and a string will be presented into the property.
This seems more correct to me, since if you want lazy properties at converge time you should have lazy {} around the value in the property and relying on a lazy proc being shoved into the node attribute is SUPER confusing spooky-action-at-a-distance and overwriting it with node['user'] = "phil" will unlazy the use of the attribute and pass the string to the first file property at compile time.  So breaking that seemed okay.

Yeah that's the second example, it is truly lazy on every read rather than caching the first evaluated return value.
node['user'] = lazy { node['real_user'] }

node['real_user'] = "phil"

file 'whatever' do
  owner node['user'] # this would have magically been "lazied" to converge time before this change and would be "dibowitz", but now is "phil"
end

file 'whatever2' do
  owner lazy { node['user'] } # this will be "dibowitz"
end

ruby_block "print it" do
 block do
   puts node['user'] # this will now print "dibowitz" (before it would print out something about it being a Proc)
end

node['real_user'] = "dibowitz"

Note that in the new behavior only the second property is evaluated lazily at converge time.
In the old behavior node['user'] was implicitly lazied all the way to converge time because the attribute carried a lazy block which was presented directly to the property.
In the new behavior the laziness is more directly exactly what is written and the first property will not have a lazy value.  When ruby parses the attribute at compile time the lazy proc will be evaluated and a string will be presented into the property.
This seems more correct to me, since if you want lazy properties at converge time you should have lazy {} around the value in the property and relying on a lazy proc being shoved into the node attribute is SUPER confusing spooky-action-at-a-distance and overwriting it with node['user'] = "phil" will unlazy the use of the attribute and pass the string to the first file property at compile time.  So breaking that seemed okay.

OK that makes sense to me.
If I use proc instead of lazy, does that change things? We have a bunch of latterns where we do node.default['foo'] = proc { bla } and then we want to eval that proc at a specific time, are we going to try to read node['foo'] and get it eval'd for us? Or is this only for "lazy"?

OK that makes sense to me.
If I use proc instead of lazy, does that change things? We have a bunch of latterns where we do node.default['foo'] = proc { bla } and then we want to eval that proc at a specific time, are we going to try to read node['foo'] and get it eval'd for us? Or is this only for "lazy"?

oh interesting.  no its not just for lazy, and it does procs as well.
that would be easily fixable though.  in fact it sounds like i should fix that.

oh interesting.  no its not just for lazy, and it does procs as well.
that would be easily fixable though.  in fact it sounds like i should fix that.

[4] pry(main)> a = Chef::DelayedEvaluator.new { puts "foo" }
=> #<Chef::DelayedEvaluator:0x00007ffe0c03a4c8 (pry):4>
[5] pry(main)> a.dup
=> #<Proc:0x00007ffe0c058e28 (pry):4>

ruby just trolling me now.

[4] pry(main)> a = Chef::DelayedEvaluator.new { puts "foo" }
=> #<Chef::DelayedEvaluator:0x00007ffe0c03a4c8 (pry):4>
[5] pry(main)> a.dup
=> #<Proc:0x00007ffe0c058e28 (pry):4>

ruby just trolling me now.

Okay, fixed.

Okay, fixed.

Ruby bug report also submitted: https://bugs.ruby-lang.org/issues/17545

Ruby bug report also submitted: https://bugs.ruby-lang.org/issues/17545


cmd/celestia: dev mode should be a flag on each node type (full | light) rather than a separate mode

We have a dev mode option in the CLI right now, but what it does is it basically runs an embedded dummy Tendermint node with a dummy app that generates blocks and feeds them to the celestia Full node. What we need is a --dev flag that can be called with the full node type. Keep in mind, the light node does not need a dev mode because it will work once connected to a bootstrap peer.
For the full --dev mode, it can work the same as the current dev mode option, but just with the celestia app rather than the dummy kvstore that is currently used. Evan has a PR open (https://github.com/celestiaorg/celestia-node/pull/176) to replace the dummy kvstore app with celestia-app, so that can be merged / used for reference.
For light, we need to be able to feed the light node a bootstrap peer that is already started (ideally another full --dev node) so that the light node can start syncing headers from the dummy full node. So basically, you should use the following command:
./celestia light init --bootstrap=<IP:PORT> and then start the node.
For example:
./celestia light init --bootstrap=a5b96b333f698eddfb08db6507e801651738c9ca@<IP_ADDRESS>:26656

./celestia light start

where a5b96b333f698eddfb08db6507e801651738c9ca@<IP_ADDRESS>:26656 is the address of the full node.
Basically, a dummy light node cannot run without being connected to something, but it doesn't really matter if the light node is connected to a bootstrap peer that is a dummy as long as the blocks are "valid".
Questions:

[ ] Do we have a method to generate a dummy valid chain? If so, we need to integrate that with full --dev mode / celestia-app. This means we don't really need to have a --dev mode for light node as the headers will technically be valid.

cc @Wondertan

Alternatively, full --dev mode can take a --remote=<remote core node address> in order to run the celestia-app.
cc @evan-forbes

Blockers to running a full / light node with celestia-app:

[ ] https://github.com/celestiaorg/celestia-node/pull/196 needs to be merged or this https://github.com/celestiaorg/celestia-node/pull/176
[ ] we need --bootstrap flag that's able to take a bootstrap node and feed it to light node p2p config

Anything else? @Wondertan

After talking with @Wondertan, we will close this issue as it is no longer necessary given new testing architecture plans.


Update launcher v0.1

Applies the same logic for the launcher for development to staging and Ari.

argh


Folder with examples

Description
Please include a summary of the change and what type of change it is (new feature, bug fix, refactoring, documentation).
Please also include relevant motivation and context.
List any dependencies that are required for this change.
Fixes # (issue)
Quick checks:

[ ] I have followed the Code Guidelines.
[ ] There is no other pull request for the same update/change.
[ ] I have written unit tests.
[ ] I have made sure that the PR is of reasonable size and can be easily reviewed.

Closing this for now, as we're currently focusing on other roadmap items.


[BUG] Different CultureInfo can cause wrong URL query in AppendQueryDelimited() in RequestUriBuilderExtensions.cs

Library name and version
Azure.Core latest
Describe the bug
Recently, we were reported a bug that our query is malformed in uri.AppendQueryDelimited() function
After digging deeper, it seems our AppendQueryDelimited() in RequestUriBuilderExtensions.cs should also applies value.ToString(TypeFormatters.DefaultNumberFormat, CultureInfo.InvariantCulture) to value otherwise, some culture will incorrectly delimit comma for specific region users.
The original discussion thread: https://learn.microsoft.com/en-us/answers/questions/1193753/azure-maps-routerange-api-invalid-coordinates-or-o?page=1&orderby=Helpful&comment=answer-1193064#newest-answer-comment
An example code snippet looks like below:
using Azure;
using Azure.Maps.Routing;
using Azure.Maps.Routing.Models;
using System.Globalization;
using System.Text.Json;

namespace Program
{
    internal class Program
    {
        static void Main(string[] args)
        {
            // Comment out the line below to repro the correct scenario
            Thread.CurrentThread.CurrentCulture = new CultureInfo("fr-FR");
            var credential = new AzureKeyCredential("<Azure Maps Credential>");
            var _routeClient = new MapsRoutingClient(credential);

            var options = new RouteRangeOptions(10.752276, 45.521535)
            {
                TimeBudget = new TimeSpan(0, 100, 0)
            };

            try
            {
                //Using the options and the route client, get route range result and serialize it as JSON.

                Response<RouteRangeResult> result = _routeClient.GetRouteRange(options);
                //Write the result to the console as JSON.
                Console.WriteLine("Route Range Result:");
                Console.WriteLine(JsonSerializer.Serialize(result.Value));
            }
            catch (Exception ex)
            {
                Console.WriteLine(ex.Message);
            }
        }
    }
}

Note: To make the program runnable, please install Azure.Maps.Routing nuget package:
dotnet add package Azure.Maps.Routing --prerelease

Note 2: Create an Azure Maps account and replace line 15 "<Azure Maps Credential>" to your Azure Maps credential. See the instruction in the C# Developer Guide
Expected behavior
A json that contains some map route result like:
{
  "FormatVersion":"0.0.1",
  "ReachableRange": { ... }
}

Actual behavior
It will return 400 error code and shows:
{
  "error":
  {
    "code":"400 BadRequest",
    "message":"The provided coordinates in query are invalid, out of range, or not in the expected format"
  }
}

Reproduction Steps
Comment line 15: Thread.CurrentThread.CurrentCulture = new CultureInfo("fr-FR"); to see the correct behavior.
Uncomment line 15 will show error (400 error code)
Environment
dotnet 6.0 (or above)
IDE: Visual Studio Code (or Visual Studio)

I'm able to repro this locally (using CultureInfo("fr-FR") first, my local culture second):
- GET https://atlas.microsoft.com/route/range/json?api-version=1.0&query=45%2C521535%2C10%2C752276&timeBudgetInSec=6000 HTTP/1.1
+ GET https://atlas.microsoft.com/route/range/json?api-version=1.0&query=45.521535%2C10.752276&timeBudgetInSec=6000 HTTP/1.1

I agree with @ArcturusZhang that it would make sense to add overloads to AppendQueryDelimited() in RequestUriBuilderExtensions that take IEnumerable<> of the different number types we have AppendQuery() methods for, and call value.ToString(..., CultureInfo.InvariantCulture) on them prior to joining the values.  It looks like this was missed in this PR.
It would also be good to cost what it would take to move these extensions into Core (i.e. to put them on RequestUriBuilder directly), and consider addressing https://github.com/Azure/azure-sdk-for-net/issues/26534 as part of this work.

This issue should have been resolved by https://github.com/Azure/autorest.csharp/pull/3311
but the SDK need to release a new version to make the fix to take effect.
@annelo-msft do you know who will take the release work of the new version?

Hi @jsquire  and @annelo-msft , the PR is merged. I'd like to know it is shipped to the latest Core library? Should I release a new version for our SDK? Thank you so much!

Hi @dubiety,
This change actually went into the "Microsoft.Azure.AutoRest.CSharp library, and not Azure.Core.  The latest version referenced by Packages.Data.props should have the fix, so I believe whenever you release a new version of Azure.Maps.Routing it should pick up the change.
Please reach out if you find that for some reason the problem has not been fixed!  Once you have confirmed it is resolved, we can close this issue.
Thanks!

The bug is fixed in Azure.Maps.Routing v1.0.0-beta.2. Close the issue.


Avoid reporting about unmatched pattern

https://github.com/ember-template-lint/ember-template-lint/pull/2435

Hi @taltcher, I see that you haven't attached any Trello card, let me help you with that...

 reviewdog-action-ember-template-lint - Avoid reporting about unmatched pattern


Recompact blocks with large number of tombstones

Carried over #91 as it diverged too much from master.

👍


Alert on invalid logo URL

Our data contains a logo field. Some of these URLs are hot-linked from the merchant's website and have the risk of going down.
We should spin up a GitHub actions job that will notify us if any of these logo URLs do not respond with a 2XX.
On a unrelated note, all logo should be CDN'ed to help resolve this issue as well as potential CORs problems.

On a unrelated note, all logo should be CDN'ed to help resolve this issue as well as potential CORs problems.

Opened an issue for this: https://github.com/hackclub/yellow_pages/issues/6

We should vendor the logos instead. https://github.com/hackclub/yellow_pages/issues/10

Yup!


Set framework location and remove unnecessary steps in ReadMe

Hard code the framework location so the user only needs to build in carthage and does not need to find the framework.

[x] Save framework location(s) in the XCode project to Carthage/Build/iOS
[x] Remove readme instructions Importing the frameworks from the SDK

Complete in https://github.com/watson-developer-cloud/visual-recognition-coreml/pull/13


Upgrade org.pitest:pitest-junit5-plugin 1.2.0 -> 1.2.1

This PR contains the following updates:

Package
Type
Update
Change

org.pitest:pitest-junit5-plugin (source)
build
patch
1.2.0 -> 1.2.1

Release Notes

pitest/pitest-junit5-plugin (org.pitest:pitest-junit5-plugin)
v1.2.1
Compare Source

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade pitest-junit5-plugin 1.2.0 -> 1.2.1

See https://github.com/pitest/pitest-junit5-plugin/compare/1.2.0...1.2.1


Fix cumulative and density function

deviance function is not supported.
Compare to multibugs: multibugs doesn't seem to support cumulative and density, but provide individual cdf and pdf functions. We can also stop supporting these two functions, and direct user to use cdf and pdf.
For now, a new member distributions is added to BUGSModel to track all the distributions: using Dict right now because non-scalar rv is problematic if we store distributions in the same way we store values.  cumulative and density are handled in special way in _eval function to allow access to distribution info at run time. Maybe this can be generalized, the distribution can be helpful introspect info

Fix: https://github.com/TuringLang/JuliaBUGS.jl/issues/137

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

126 of 143 (88.11%)  changed or added relevant lines in 5 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.3%) to 82.118%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/model.jl
14
15
93.33%

src/utils.jl
40
42
95.24%

src/compiler_pass.jl
50
56
89.29%

src/parser/bugs_macro.jl
21
29
72.41%

Files with Coverage Reduction
New Missed Lines
%

src/utils.jl
1
85.78%

src/model.jl
1
89.33%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1621

Relevant Lines:
1974

💛  - Coveralls


Do not reorder side effect nodes #110

This PR resolves #110

The relative order of side effect and non side effect imports is now preseverd by default. See the readme and issue for more info.
I renamed the getSortedNodes method to getSortedNodesByImportOrder; and added a new implementation for getSortedNodes that first splits the imports at each side effect node, then sorts each chunk via the original getSortedNodesByImportOrder. I also moved the logic for adjusting comments and inserting new lines to the new getSortedNodes method.
With the exception of one test case (imports-with-comments-and-third-party has a side effect import import "./commands"), all existing tests still pass without any modifications.  This leads me to believe you haven't considered these kind of import statements yet and how they should be treated. So this PR could be thought of as defining the behavior for that scenario.
I also added a few additional tests for the new behavior with side effect imports.

The way this PR is implemented (only performing less sorting in case of side effect imports) means that all source files that were considered formatted correctly before this PR are still considered to be formatted correctly. So this change should not require a new major version (assuming you are following semver). Also,  prettier recommends users to use an exact version, so the same should also apply to plugins.
That only leaves the question of whether (a) we should introduce an option that can turn side effect import sorting on and off, and (b) if so, what  should be the default. My opinion is no, following the philosophy of prettier, which is to be an opinionated code formatter without many options. Not sorting side effects should also be the default, as having side effects is the only purpose of those imports and changing their order is more likely to break the code.

@ayusharma @byara what do you think of this idea?  I'd really love to have this merged and released, as without it I'm not able to use this excellent-looking plugin.  Thanks!

Hey @blutorange @IanVS thanks for the PR. This seems like a really good idea. But I have to say that we have to take a look into it and at the moment both @ayusharma and I are on holiday 😅  As soon as we get back, we will take care of this 👍

No problem, take your time and enjoy your holidays, I can wait a little while. Let me know what you think when get back : )

Yeah I'm all set for now, using patch-package to apply it to my node_modules.  I'll report back if I see anything funky, but in the meantime, enjoy your time off!

@byara @ayusharma do you have new about this PR ? ... it is okayish ?  because it solves 1 of the 3 issues that prevents us from using the plugin.
if this one moves on, I will give it a try to the others too.

Yeah, if there's anything I can do to improve this PR, let me know. I have some index files too that need side effect imports where getting this merged would help greatly.

@byara  Should be good now, but let me now if you find anything else.

Hey @ayusharma, would be great if you could leave a review as well so we can go forward with this PR.
Maybe we should merge this to v3.2.x branch?

I'll recommend merging it to the 3.2.x branch and release from that branch.

Hi, We have to revert the PR as it fails the basic idea of the plugin.
For example:
Input
import React, {
    FC,
    useEffect,
    useRef,
    ChangeEvent,
    KeyboardEvent,
} from 'react';
import { logger } from '@core/logger';
import { reduce, debounce } from 'lodash';
import { Message } from '../Message';
import { createServer } from '@server/node';
import { Alert } from '@ui/Alert';
import 'lodash';
import { repeat, filter, add } from './utils';
import { initializeApp } from '@core/app';
import { Popup } from '@ui/Popup';
import 'styles.css';
import something from 'rx';
import { createConnection } from '@server/database';

With your PR we produce the following output:
import { debounce, reduce } from 'lodash';
import React, {
    ChangeEvent,
    FC,
    KeyboardEvent,
    useEffect,
    useRef,
} from 'react';
import { createServer } from '@server/node';
import { logger } from '@core/logger';
import { Alert } from '@ui/Alert';
import { Message } from '../Message'; // this should be just after import { add, filter, repeat } from './utils';
import 'lodash'; // this should be on the top with the 3rd party imports.
import { initializeApp } from '@core/app';
import { Popup } from '@ui/Popup';
import { add, filter, repeat } from './utils';
import 'styles.css';
import something from 'rx'; // this should be on the top with the 3rd party imports.
import { createConnection } from '@server/database';

The new sorting breaks the general principle of the 3rd party modules and local modules.

Hmm, the PR is correct in the sense that it implements the solution described in #110
Whether or not that solution is appropriate is something I'm open to discuss. There are three point I had in mind when I suggested the solution:

Err on the side of correctness. Having pretty formatted code is great, but only if it does not break it (which I think agrees with prettier's philosophy)
Keep the number of options to a minimum (also following prettier's philosophy here). We could add several options for people to configure how side effect imports are treated, but in my opinion that adds complexity, and I think it should just work out of the box.
An import like import "..." does not import anything, the only reason for it to exist is for side effects. We do not know what those side effects will be -- they could change or prepare the runtime environment in a way that will effect other imports. So to be safe, other imports before a side effect import must stay before it, and other imports after a side effect import must stay after it.  The example from artola above with the polyfill ilustrates this.

Hi @ayusharma, I don't agree that introducing this change would be distracting or breaking for your users. Currently, the plugin handles side-effect imports improperly, reordering them and potentially breaking any code this plugin is applied to. This makes the plugin completely unusable for any folks (like me) who have side effect imports.
From what I can tell, this change just makes the plugin usable for any files with side effect imports, with the downside of not totally sorting the imports in files with side-effect imports.
I don't understand what the use-case would be for a config value to disable this feature. Who would disable it?

@ayusharma This is not a breaking change, it is a just bug fix. Former behaviour is just improper. Furthermore, it does not break previous saved code because it will keep any side-effect in place.
At most it makes sense to release this change as v4 to "shout" the change.

I can understand your point of view, but let me share my on thoughts on this:

imports can be distracting and breaking for our users
Not sure about distracting, but regarding the breaking: It should not be breaking change in the sense that every file that was recognized by prettier as properly formatted will still be recognized formatted properly. So users won't get any build failures from updating the plugin. It's just that files that weren't formatted properly before are now not sorted as much.

File-based API detection
Personally I don't like non-standard magic comments that are used only by a one of the many dependencies of a project. I'm not totally opposed to it, but every feature adds complexity and I'm not sure if configuring it per file is really needed. Especially since the main reason for not making this the default behavior is for people who are used to the old behavior.

Side effects import soring using prettier config
That I think sounds much better. I'd still like if it were be enabled by default so the plugin would not break code out of the box with the default options -- but perhaps we could make the option disabled by default for versions 3.x and make it enabled by default with 4.x ?

I'll just chime in that I tried out this sorting plugin, thought everything was great, and then later realized that my app was broken because side effect imports were re-arranged.  Luckily I did notice before I pushed to production, but it was definitely unfortunate.  I wouldn't be able to use this plugin at all, if it weren't for this PR.  So, because of that, I agree that this should be treated as a bugfix and made the default.  It doesn't really make sense to me to have a default behavior which has a good potential to break the code it is run on.  Honestly I don't even think that should be an option.  Just my $0.02.  Thanks for the robust discussion, everyone!

@ayusharma What's your current opinion on this? Should this still be an option? Should be enabled or disabled by default?

Hi @blutorange, @byara and I would like to keep it disabled by default.

Hi @blutorange, @byara and I would like to keep it disabled by default.

Is there a config value to enable using side-effect imports?
Automatically rewriting side-effect imports is similar to sorting imperative commands in alphabetical order. It's nice but it can break things

I think this PR is an important bugfix, and have published https://www.npmjs.com/package/@ianvs/prettier-plugin-sort-imports which is a fork of this project, but includes this PR without reverting it.  Maybe those of you with side-effect imports will find it useful.

Question about @trivago/prettier-plugin-sort-imports v3.2.0:
This PR has been merged. But it seems it's not included in v3.2.0?

This PR has been merged. But it seems it's not included in v3.2.0?

After reading the messages above, I see that this PR has been reverted 😞:
https://github.com/trivago/prettier-plugin-sort-imports/pull/111#issuecomment-1016310310

@ayusharma / @byara why are you shipping buggy code and wasting time of so many users, when community contributes bug fixes alleviating these problems?

Time to change cya, gl hf

This is a huge shame, is there any plans to have this at least configurable in prettier as mentioned above? It's a deal breaker for us.

This is a huge shame, is there any plans to have this at least configurable in prettier as mentioned above? It's a deal breaker for us.

@missbruni, my sincere thanks to the original authors for initiating this project. However, when I faced this issue, I found a solution by switching to @IanVS 's fork.
I highly recommend taking a look at Ian's package: https://www.npmjs.com/package/@ianvs/prettier-plugin-sort-imports.

Ditched for @IanVS as well, Mantine React requires CSS imports in a specific order without having to dump to PostCSS, and Vite supports it just fine, so to have this tool mess it up wasted an hour of my time figuring out what went wrong and going to a better plugin.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/401 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit a552f42:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-02-10-05-08-32 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-02-10-05-08-32

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


BUG: image preview doesn't work

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
0.9.5
Operating System / Version
MacOS 14.3.1
Describe the Bug
I have the image.nvim dependency installed, and the setting for image_preview is also explicitly specified, but image doesn't render
Screenshots, Traceback

Steps to Reproduce

Install neo-tree with image.nvim dependency
Open neo-tree
Open preview of any image

Expected Behavior
Rendered image in preview
Your Configuration
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}

local neotree_config = {
  "nvim-neo-tree/neo-tree.nvim",
  dependencies = { "MunifTanjim/nui.nvim", "nvim-tree/nvim-web-devicons", "nvim-lua/plenary.nvim", "3rd/image.nvim" },
  cmd = { "Neotree" },
  opts = {
    window = {
      mappings = {
        ["P"] = { "toggle_preview", config = { use_float = true, use_image_nvim = true } },
      }
    }
  },
}

table.insert(plugins, neotree_config)
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Could you double check if image.nvim itself indeed works but only fails with neo-tree?
https://github.com/3rd/image.nvim#try-it-out-with-a-minimal-setup

I have the exact same issue on macOS. I did the minimal setup and it works. Yet Neotree previews doesn't :(

I have:
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.6 LTS
Release:	20.04
Codename:	focal
and have the same issue.


Reapply Phinx migrations on a source code deployment rollback

Hi,
Is there any way to rollback the migrations that are missing? (that are deleted by a deployment rollback, for example).
In that case, we could rollback the deployment code safely, having added the phinx migrate command to always run automatically after deployment, code & db schema would always match. Any idea/workaround would be appreciated.

So, don't know if a good idea but, what if we save the php migration code in the phinxlog table for each migration, and we restore the file and perform the rollback when the migration is missing.

Not all phinx migrations would be feasible to be stored in any meaningful way. Data fixing migrations that have to run through multiple steps and/or rely on external sources, for example, could result in significant complexity.
As a further example, our migrations files tend to be stubs with the main behaviour abstracted away in other files. Rolling back code would delete the ancillary files.
There are a couple of features being discussed and are specifically about automated deployment and rollback.
https://github.com/robmorgan/phinx/issues/1044 and https://github.com/robmorgan/phinx/issues/1046
Both are about my organisations use of Phinx and hopefully will be defined well enough to be of real use to a large number of people.
Take a look at these, if you think you have anything to contribute to the specific ideas, please do. Getting more feedback from users will allow us to add the appropriate functionality.

Discussion can then continue in those linked issues.


Wasn't able to get the docker image running (Illegal instruction (core dumped)) (no AVX support?)

main: seed =<PHONE_NUMBER>

Illegal instruction (core dumped)

Wasn't able to get the docker image running.
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "4"
    field.cattle.io/publicEndpoints: '[{"addresses":["<IP_ADDRESS>"],"port":32435,"protocol":"TCP","serviceName":"serge:turbopilot-nodeport","allNodes":true}]'
  labels:
    workload.user.cattle.io/workloadselector: apps.deployment-serge-turbopilot
  name: turbopilot
  namespace: serge
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      workload.user.cattle.io/workloadselector: apps.deployment-serge-turbopilot
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        workload.user.cattle.io/workloadselector: apps.deployment-serge-turbopilot
    spec:
      containers:
      - env:
        - name: MODEL
          value: /models/codegen-2B-multi-ggml-4bit-quant.bin
        image: ghcr.io/ravenscroftj/turbopilot/turbopilot:latest
        imagePullPolicy: IfNotPresent
        name: container-0
        ports:
        - containerPort: 18080
          name: turbopilot
          protocol: TCP
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /models
          name: turbopilot
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      terminationGracePeriodSeconds: 30
      volumes:
      - name: turbopilot
        persistentVolumeClaim:
          claimName: turbopilot

Hi there thanks for your ticket. Can I ask what operating system and processor architecture you are running your k8s cluster on?

Hi there thanks for your ticket. Can I ask what operating system and processor architecture you are running your k8s cluster on?

I am running Ubuntu 22.04 LTS.
Kubernetes V1.23
The CPU's support AVX (not AVX2) (48 x Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz (2 Sockets), 32 x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (2 Sockets)) - I haven't tried the container on my Ryzen system that has AVX2 support..... will try that now......

It happened to me, too
when i run docker run --rm -it -v /home/yang/models:/models -e MODEL="/models/codegen-2B-multi-ggml-4bit-quant.bin" -p 80:18080 ghcr.io/ravenscroftj/turbopilot/turbopilot:latest
terminal output
main: seed =<PHONE_NUMBER> gptj_model_load: loading model from '/models/codegen-2B-multi-ggml-4bit-quant.bin' - please wait ... gptj_model_load: n_vocab = 51200 gptj_model_load: n_ctx   = 2048 gptj_model_load: n_embd  = 2560 gptj_model_load: n_head  = 32 gptj_model_load: n_layer = 32 gptj_model_load: n_rot   = 64 gptj_model_load: f16     = 3 Illegal instruction (core dumped)
My Operating Environment :
docker 20.10.18 Community
Ubuntu 22.04.1 LTS
Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz
I pulled the docker image directly

Great thanks for looking into the AVX thing - in hindsight that was the obvious problem - I should have known :facepalm:
So I think the short term solution would be to build the image on the system you're targetting and the C preprocessor should pick up what instructionsets are supported. The slightly longer term solution is for me to add CI builds that build with different sets of CPU instructions and make them available as part of the release

docker run --rm -it -v ./models:/models -e THREADS=6 -e MODEL="/models/codegen-6B-multi-ggml-4bit-quant.bin" -p 18080:18080 ghcr.io/ravenscroftj/turbopilot/turbopilot:latest

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

main: seed =<PHONE_NUMBER>
gptj_model_load: loading model from '/models/codegen-6B-multi-ggml-4bit-quant.bin' - please wait ...
gptj_model_load: n_vocab = 51200
gptj_model_load: n_ctx   = 2048
gptj_model_load: n_embd  = 4096
gptj_model_load: n_head  = 16
gptj_model_load: n_layer = 33
gptj_model_load: n_rot   = 64
gptj_model_load: f16     = 2
gptj_model_load: ggml ctx size = 6325.92 MB
Illegal instruction (core dumped)

Apple M1 Pro
Mac 13.2

hi @oshanz - please try changing the image uri to ghcr.io/ravenscroftj/turbopilot:latest - the path from your log above is the old build.

@ravenscroftj same issue with that image on mac m1.

hi @4j4y  - just to clarify when you say image above you are referring to ghcr.io/ravenscroftj/turbopilot:latest (as opposed to the old image with /turbopilot/turbopilot in it)?
I don't have an apple silicon device so I'm struggling to work out what is working and what isn't. Are you running docker desktop on your m1 in order to run the image? Don't suppose you can share the output from your docker pull or docker run command (I'm after the image hash that you are using).

support for older instruction sets is provided in release 0.0.5


Contribute "Round" Naming Convention

update the naming convention for the contribute changes to: ergopad.io/contribute/paideia/seed

duplicate #115


What is the minimum hardware requirement to fine-tune I3D on new dataset?

Dear Sir/Madam,
Can the pre-trained model run in a PC of i7 and GTX1080 for fine-tuning?  The size of the new dataset will be about 100.
Thanks.
Regards,
Stephen

Thanks.

Hi @salmedina and @stephencheung16 . I am trying to replicate the experiment of finetuning i3d trained on Kinetics, for ucf-101, as per the methods specified in the paper, but getting unsuccessful in achieving any significant accuracy (not even on training data) even after several iterations. Could you please give any guidance?
To simplify, I just used 10 classes from ucf-101,
extracted 64 contiguous frames from each video, from any (feasible) random begin point for each epoch,
spatially cropped 224x224 from video resized to 256,
used Adam optimiser with initial learning rate(1e-4),
and mean subtarction and division by 255 from data.


QR code not showing with value from state

QR code is not showing with value from state
Also disappears when state value changes

is there any update regarding this issue? Have you found the cause?

My issue was because the bundling process is not correct, it doesnt 'generate' the image correctly and after cleaning and rebuild, it runs perfectly.


fix receicing of DHCP vendor info

Test Setup
DHCP-Server sends forced vendor option
host devbrd-dhcptest    {
 hardware ethernet cc:db:a7:1d:XX:XX; fixed-address 10.X.X.X;
 option dhcp-parameter-request-list 1,3,28,6,43; # default + vendor
 option vendor-encapsulated-options "hallo test 1234";
}

with current master
this source
 char vendor_buf[128];
 bzero(&vendor_buf[0], sizeof(vendor_buf));
 esp_netif_dhcpc_option(wifi_device, ESP_NETIF_OP_GET, ESP_NETIF_VENDOR_SPECIFIC_INFO, &vendor_buf[0], sizeof(vendor_buf)-1);
 ESP_LOGI(TAG, "vendor string:%s:", &vendor_buf[0]);

logs
vendor string:llahllahllahllah:
what is obviously wrong
Bugs in lwip_default_hooks.c

the vendor option of the DHCP response is treated as multiple of 32-bit (what is an invalid assumption, see RFC 2132)
the response is converted from network to host byte order (for no reason)
the current loop will always duplicate the first 4 bytes because offset is not adjusted
not checked: the 32-bit handling will produce garbage when the last read is shorter than 2 bytes

Hints for everyone who would like to use vendor stuff in DHCP

query for vendor response in DHCP request: CMakeLists.txt ->  add_definitions(-DLWIP_HOOK_DHCP_EXTRA_REQUEST_OPTIONS=,43)

send custom vendor with request: after WIFI_EVENT_STA_START -> esp_netif_dhcpc_option(wifi_device, ESP_NETIF_OP_SET, ESP_NETIF_VENDOR_CLASS_IDENTIFIER, vendor_string, strlen(vendor_string))

 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.Leif Jakob seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Optimize performance

Closes #11

[Current coverage][cc-pull] is 100%

Merging [#18][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #18   diff @@
===================================
  Files           1     1
  Lines          52    87    +35
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
+ Hits           52    87    +35
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last updated by [758d956...f6743d9][cc-compare]
[cc-base-branch]: https://codecov.io/gh/safareli/free/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/safareli/free/compare/758d956b4e0613827c2bd56429007c64ad723aa9...f6743d960c0e1210e39f310f8722e1867c677d15?src=pr
[cc-pull]: https://codecov.io/gh/safareli/free/pull/18?src=pr


need to update README.md because the line 21 and 24 are repeated.

Sorry, because I changed the README of the project last time, so 21 and 24 are repeated.

ok @Xlgd I have fixed it.

Thank you!


Mod 1 - user can add an application when they shouldn't be able to

Module: 01
Lab/Demo: 01
Task: 2
Step: 6
Description of issue
User CAN add an application here......the notes say they would not be able to....
Repro steps:

Turns out yes they do see "+ New Application", but when they select an item from the gallery the final 'Create' button is unavailable.

Thanks for the feedback. we will tweak this to show the UI change.  I am sure that when I built the lab originally, the + New was greyed out; but Azure changes so often .


Create strings.js

Hi, @ovk
I translated into Italian your extension. I apologize for all these PR I did. In this file I could help settle the symbol ( ' ), I think I made a mistake. Thanks in advance!

Thank you, @Denisov21. I'll include your contribution in the next version.


Safari/iPad OS shows No device to connect when trying to host a session

There are issues initiating new sessions from safari in iPad OS, although joining an existing session works fine.

Could not reproduce it again during manual testing. Closing it now until it surfaces again.

This was caused by content blocker in Safari on iPad. A fix was deployed https://github.com/mustakimali/just-an-email/commit/b6e39f97b32e804ebf197c5616b65af5e3536fc7


Cannot Calcinate and get Minium Dust

Hi Pahimar,
I have tried blocks of emerald, blocks of diamond, and several other things. The last release on curse <IP_ADDRESS>7 is what I am using, and I still do not get any red dust. So, basically, I can not use EE3 at all. Can you offer a suggestion?

What is the value of minium dust/diamonds/emeralds/etc in your world? The probability of you getting minium dust is dependent on the values of objects.

Hello,
I am having the same problem. I am using <IP_ADDRESS>7, and all items simply turn to ash in the calcinater. Diamond exchange energy is 8192. Any ideas?

Hey!
I just wanted to say hi and show  you something  really interesting, here take a look http://ignazio.drhart.org/e8rji/586
Kind regards, SHoCKYCooKIE

I am having the same issue.  The following are some values of items as shown in my game:
Minium Dust: "No Exchange Energy value"
Diamond: 8192
Emeralds: 8192
Coal: 32
Iron Ingot: 256

Closing due to age


Fix errors / warnings related to pandas 1.3.0

Fixes #40

Huh - from scanning the pandas changelog it isn't entirely clear to me what caused this change, but given all the user facing issues I'm going to:

Merge this (I've manually confirmed that the behavior is the same is between versions).
Cut a release
Bump the CI to actually use new pandas/numpy
See if dependabot can keep requirements_locked.txt updated more frequently. I want to keep the old compatibilities locked to test backwards compatibility, but we should definitely be triggering CI on new versions of core dependencies.

Thanks for taking this @maread99 - much appreciated!


Fix redirect logic when Retry-After is given with a 301 redirect

Fixes #337
This is confusing and takes a while to figure out, but I think I've got it fixed.
There is a stack of libraries (requests->urllib3->httplib) handling HTTP requests.

urllib3.connectionpool.HTTPConnectionPool.urlopen has a (recursive) loop for handling retries for error responses (this is what urllib3.util.retry.Retry/max_retries configures).
urllib3 also has code in this function for handling redirects; however, when used through requests, this logic is disabled.
Instead, the logic in requests.sessions.SessionRedirectMixin.resolve_redirects is used.

When I first configured this, I erroneously assumed that the logic in urllib3 was used, and thought that adding the redirect status code to Retry.RETRY_AFTER_STATUS_CODES would cause it to wait for Retry-After, then redirect. Instead this resulted in waiting for Retry-After, then retrying the original request, all in the inner loop, without popping up to let requests reconfigure the request for a redirect.
With this change, we patch into the requests redirect handling logic instead, forcing it to sleep if a Retry-After header is present, then follow the redirect as normal.
I've tested this on a dummy test server sending normal, error and 301 Retry-After responses, and can probably make a simple unit test for it, but open to other ideas.

Codecov Report

Merging #341 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #341      +/-   ##
==========================================
- Coverage    84.8%   84.78%   -0.03%
==========================================
  Files          37       37
  Lines        1764     1761       -3
==========================================
- Hits         1496     1493       -3
  Misses        268      268

Impacted Files
Coverage Δ

hca/util/__init__.py
85.9% <100%> (-0.12%)
:arrow_down:

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 cc5c7e3...ce2f529. Read the comment docs.

@xbrianh I added a test in the copy of this code in https://github.com/HumanCellAtlas/dcplib/pull/23.
I will be changing this PR to import the relevant code from dcplib.


VSCode should follow .lnk

VSCode should be able to resolve .lnk files, if this link leads to a file on the users hard drive.
Thus the user can open the file right away by clicking on the link file in the sidebar.

VSCode should be able to resolve .lnk files, if this link leads to a file on the users hard drive.
Thus the user can open the file right away by clicking on the link file in the sidebar.

I would like this functionality as well, is it possible to reconsider this?

VSCode should be able to resolve .lnk files, if this link leads to a file on the users hard drive.
Thus the user can open the file right away by clicking on the link file in the sidebar.

I would like this functionality as well, is it possible to reconsider this?

Hi guys,
I was having difficulties opening files from some shortcuts in VS Code so did some searching but have to admit I was quite surprised to find this page, essentially saying it's a known issue and there are no plans to fix it. 🙁
I understand you have a lot of issues to triage, but do think this one may be worth re-considering...

.lnk files have been part of Windows for 25 years (since Win95) and are used by users every day
They are handled (resolved) by pretty much every other application (I literally can't think of another app that has tried to open the shortcut file itself, rather than the target)
(rhetorical) Is this feature/fix really going to be that hard to implement?... I don't know the code/effort involved, but would like to think this would be a fairly straight-forward fix (<5 lines) by a simple if check on the file extension, or something similar(?)

I appreciate the issue is currently closed, but hope the above outlines the case for implementing this feature. Thanks!

reopen please

To work around it, try mklink with cmd.
.lnk is created by right-clicking the file / folder and select create shortcut. It is not exactly a symlink but a file with pointer to the actual file and other details. If you run dir from cmd, you'll see it has no difference with other files except with the file extension being .lnk.
To create an actual symlink, you can run mklink from cmd or New-Item from Powershell. Both methods require privilege escalation.
CMD
mklink [/D] <new_symlink_name> <source_of_symlink>

where the /D flag is needed for symlink-ing a folder.
PowerShell
New-Item -Path <new_symlink_name> -ItemType SymbolicLink -Value <source_of_symlink>

Now when you dir the directory, you will see <SYMLINK> or <SYMLINKD> property in CMD or the l mode flag in PowerShell.
Back to VSCode, you'll see the nice drop-down button on the new symlink folder with the little arrow symbol!

image from VSCode update notice

Thanks @henryfung3a27 -- your workaround should hopefully help a few people out! 👍🏼
Side note: Unfortunately, it doesn't work for me (I did already consider this option) as my code directories are inside OneDrive and .symlinks aren't supported / synced with OneDrive... Once again, I would ask the VS Code Team to re-open/re-assess this issue -- thanks guys!

reopen, please.


DNS - test more passes in GlobalOptimization phase

64179.446 (vs. 7.679, 835645.50%↑)
🤯 is that a new record??