401 error on UI when login with wrong user or password

Issue
When an user enters wrong credentialls on ui, a 401 error appears
Steps to reproduce

Deploy latest Epinio server version (v1.10.0-15-g47ee6f4e) and  either of these ui images: ghcr.io/epinio/epinio-ui:v1.10.0-0.0.1 or ghcr.io/epinio/epinio-ui:latest-next
Enter a wrong username / password and login

Observed behavior
The user is taken to an 401 error screen and then returned to the login screen
https://github.com/epinio/epinio/assets/37271841/ae769e7f-5698-4cc5-99ab-2fe72e8f8ca7
Error:
xhr.js:178     GET https://epinio.<IP_ADDRESS>.omg.howdoi.website/pp/v1/direct/r/ZThhPrryoUeUuimbk4Gb-G3-I9A/api/v1/namespaces 401 (Unauthorized)

Note: CLI handles correctly the message:
Ξ epinio-repos/epinio git:(main) ▶ epinio login -u admin https://epinio.<IP_ADDRESS>.omg.howdoi.website

🚢  Login to your Epinio cluster [https://epinio.<IP_ADDRESS>.omg.howdoi.website]
Password:

⚠  Certificate signed by unknown authority

|     KEY     |      VALUE      |
|-------------|-----------------|
| Issuer Name | CN=epinio-ca    |
| Common Name | epinio-ca       |
| Expiry      | 2024-January-04 |

Do you want to trust it (y/n): y

✔  Trusting certificate for address https://epinio.<IP_ADDRESS>.omg.howdoi.website...

❌  error verifying credentials: error while connecting to the Epinio server: wrong password

Expected behavior
UI should handle it correctly not redirecting the user and displaying an error in the login page as before: Invalid username or password. Please try again.

Setup
Kubernetes Version: v1.25.4+k3s1
Epinio Server Version: v1.10.0-15-g47ee6f4e
Browser: Brave v1.58.135
UI Image:   ghcr.io/epinio/epinio-ui:v1.10.0-0.0.1 or ghcr.io/epinio/epinio-ui:latest-next

From a talk in slack we are theorizing that the issue is as follows:

We assume that the ui uses the /info endpoint after login to check if the entered credentials are correct or not.
Before the recent changes in the server the /info endpoint was authenticated and served that purpose well.
With the recent changes (#2604) the /info is not authenticated any longer.
To the UI this change means it comes to believe that even bad credentials are ok.
It then goes forward with actual work  (like listing the namespaces), and then fails there with the bad credentials.
And was not prepared for that, hence the 401.


feature request: species name in SimulationResult.all()

I'm using version 1.9.0
Right now in the source code of SimulationResult.all() the species names are given by
sp_names = ['__s%d' % i for i in range(len(self._model.species))]
(link), which then propagates to SimulationResult.dataframe() as column names. Would it be possible to incorporate more informative species names here, like Component name?

Hi, thanks for your suggestion. Our original reason for choosing species names like __s1 was for ease of reference. Species can be large complexes of molecules, which would mean their names could run into hundreds of characters, which is not ideal for referencing individual species. That said, I get that there are times when it would be useful to have more meaningful species names, so maybe some kind of user-selected naming option would work. In the meantime, here's how you can achieve what you describe manually:
# Run your simulation, e.g. res = ScipyOdeSimulator(model, ...), then:
new_names = list(res.all.dtype.names)
new_names[:len(model.species)] = [str(s) for s in model.species]
res.all.dtype.names = new_names

Thank you for the clarification and example! I did not realize the problem with large complexes, and now that design totally makes sense.
I suggest we add this example to the tutorial in the documentation (link) and then close this issue. User-selected naming option doesn't seem to be urgent or essential.


[e2e] Setup selenoid for parallel running tests

Set up selenoid
add parallel running tests

https://github.com/testcontainers/testcontainers-java/pull/3220
https://github.com/testcontainers/testcontainers-java/issues/1495
https://github.com/testcontainers/testcontainers-java/issues/5037


Note: already working mapbox/leaflet implementation for react

Hi.
I came acros an already working implementation of mapbox in react:
https://github.com/PaulLeCam/react-leaflet
This works with mapbox too, you just need to configure the tile layer for mapbox and you are done..
Maybe use this instead of doing double work ? ^^

Yes I know react-leaflet but this project is based on mapbox-gl-js which
render the map in a canvas instead of using the DOM it make the rendering
more efficient because if is using webgl.
On Monday, 18 April 2016, JonathanBergers<EMAIL_ADDRESS>wrote:

Hi.
I came acros an already working implementation of mapbox in react:
https://github.com/PaulLeCam/react-leaflet
This works with mapbox too, you just need to configure the tile layer for
mapbox and you are done..
Maybe use this instead of doing double work ? ^^
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/alex3165/react-mapbox-gl/issues/3

Ah okay, cool!


Put New Version of EtasonJB

I still hold that the name of this jailbreak is terrible. Thanks for the updated version.


Api first pass

Here's a first pass at cleaning up the public API so we can push a release to pypi @astheeggeggs
The idea is that users won't need (or shouldn't have access to, really) the internal namespace and will just use the functions lshmm.forward() etc.
All seems to be working OK, except for the viterbi sub-package. Can't get that to work, but have to go now. I'll pick this up again when I get a chance.
Did you hit issues like this?

Aha! Figured it out. The viterbi package was conflicting with the viterbi function. Took me ages to figure that one out!
That should be the main API surface picked out now, so how about we make an alpha package for pypi and push it up there?

Some updates here

I removed pydocstyle. I couldn't figure out what it wants and it seems really very overly proscriptive and unhelpful
I disabled the docs build for now as it's a bit tricky
Did a bit of a refresh on the nox config and the CI.

Hopefully this will get the build completing successfully on CI.

How's it looking @astheeggeggs? I'm assuming a lot of this stuff came from cookiecutter and you didn't hand craft these configs?

Yep, you're exactly right - lots of this stuff is from cookiecutter and I left well alone!

Aha! Figured it out. The viterbi package was conflicting with the viterbi function. Took me ages to figure that one out!
That should be the main API surface picked out now, so how about we make an alpha package for pypi and push it up there?

oh, whoa - sorry about the viterbi pain!


Rose/cylc log files from raijin are not being copied to accessdev

resolution_fixed   |    by ibc599

Normally the hook "rose suite-hook" would grab remote log files from raijin and copy them to accessdev. For some unknown reason this is failing.
People can manually update remote log files via the commands
rose suite-log --update ''
chmod a+r ~/cylc-run//log/*
The chmod is to allow people view them from the web.

Issue migrated from trac:19 at 2024-01-31 17:09:17 +1100

ibc599 commented

The commands for a manual update should be
rose suite-log --update --name SUITE ''
chmod a+r ~/cylc-run/SUITE/log/job/
where SUITE is the name of the suite

<EMAIL_ADDRESS>changed priority from major to critical

ibc599 commented

MET office tried to fixed this bug https://github.com/metomi/rose/issues/719 But the issue still occurs under heavy load?

ibc599 commented

Pulling of log files is done by the rose hook command. Need to checkout whether a timeout can be added to ensure files are completed before calling rose hook.

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>changed owner from `` to ibc599

ibc599 changed reviews which not transferred by tractive

ibc599 commented

Created a new hook "rose task-hook2" which is a wrapper for the rose task hook. Checks to see if any log files are created before calling rose task-hook.

<EMAIL_ADDRESS>changed component from accessdev server to Rose

ibc599 commented

Adding a sleep command on the event hook ensures "rose suite-hook" grabs the correct log file. 30-60 seconds seems to be enough time.
eg
succeeded handler = "sleep 60;chmod a+r $CYLC_TASK_LOG_ROOT*;rose suite-hook"
permission is still causing an issue?????

<EMAIL_ADDRESS>commented

Milestone Future deleted

<EMAIL_ADDRESS>removed milestone (was Future)

ibc599 changed resolution from `` to fixed

ibc599 changed status from assigned to closed


feat: add BYOP (bring your own phase) logic

This will allow consumers of operator-builder to bring their own controller phases, thereby extending the controller into any customizable format.
This relates to #84 by extending the concept of stub-phases into custom logic (e.g. I need a backup phase to my controller).

This was fixed with #217


chore: fix max gas for slashing transactions

Purpose

How does the solution address the problem

Changes made

prnet cleaned-up successfully


LIS_writeModelOutput '[INFO] Writing surface model output to:  ' produces garbage

The message '[INFO] Writing surface model output to:  ' in routine LIS_writeModelOutput in file lis/core/LIS_historyMod.F90 produces garbage for all non masterproc processes.
Only the master process sets lsmoutfile.  Either all calls to LIS_writeModelOutput should initial the output file name to some clean value or only the master process should issue this message.

lislog.0000:
 [INFO] Writing surface model output to:
 OUTPUT/SURFACEMODEL/200210/LIS_HIST_200210290300.d01.gs4r

lisle.0001:
[INFO] Writing surface model output to:
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@


WIP apply PP manually

Stack from ghstack (oldest at bottom):

-> #308
#161

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

squashed


Fixes some issues with 64x1D test.

Trailing commas are not standard, remove them.
error checker is assuming registered RAM, add register to LUT-RAM.

CI failure?

CI failure?

We've been having unrelated intermittent CI failures due to what appears to be VM disk failures.  The failure in http://sponge.corp.google.com/acee5057-e70f-4847-b9b9-e5cf8860a789 is hard to explain as anything other than the GCS VM disk failing to behave correctly.  I've been attempting replication of the failures without success on my local machine.  I've started trying to replicate on the large symbiflow VM.


Fifo delay queue is delivering messages immediately instead of delaying them

Hello!
I have a queue configured in the .conf file as follows:
  MyQueue {
    fifo = true
    delay = 60 seconds
    defaultVisibilityTimeout = 60 seconds
    deadLettersQueue {
      name = "MyDLQueue"
      maxReceiveCount = 3
    }
  }

As you may see, the queue has a delay of 60 seconds. The queue seems to have been created correctly. I checked using the CLI:

The problem is that regardless of the configuration, the messages get delivered immediately. I am using serverless-framework and I have configured a function to have the queue as an event source. As soon as a message is sent to the queue, the function get triggered immediately without the delay of 60 seconds.
Am I doing something wrong?
Thank you!

@jcelmeta14 I can't reproduce the issue.
I'm using softwaremill/elasticmq-native:1.4.7 and the following configuration:
include classpath("application.conf")

queues {
  main {
    defaultVisibilityTimeout = 10 seconds
    delay = 2 seconds
    receiveMessageWait = 0 seconds
    deadLettersQueue {
      name = "retry"
      maxReceiveCount = 1
    }
  }
  retry {
    defaultVisibilityTimeout = 10 seconds
    delay = 2 seconds
    receiveMessageWait = 0 seconds
  }
  delayed {
    fifo = true
    delay = 10 seconds
    defaultVisibilityTimeout = 10 seconds
    deadLettersQueue {
      name = "retry"
      maxReceiveCount = 3
    }
  }
}

and this is my test code:
queue = self.sqs.get_queue_by_name(QueueName='delayed.fifo')
queue.send_message(MessageBody='some test message to be delayed', MessageGroupId='group123', MessageDeduplicationId='dedup123')
messages = queue.receive_messages()
print(messages)
time.sleep(5)
messages = queue.receive_messages()
print(messages)
time.sleep(5)
messages = queue.receive_messages()
print(messages)

and this is the output:
[]
[]
[sqs.Message(queue_url='http://localhost:9324/000000000000/delayed.fifo', receipt_handle='b5edfb66-0106-43b7-beb4-e7ab211a82f0#c732fdcd-aa1c-4d78-af5c-00a7b2878ce1')]

If you still observe the issue with the latest version, please provide an application or test reproducing it.

Thank your for your reply! I will try to create a repo in the following days, and I will post another comment here.

The issue happens when the "DelaySeconds" is set to 0 within the message. If you modify your test code like this:
queue.send_message(MessageBody='some test message to be delayed', MessageGroupId='group123', MessageDeduplicationId='dedup123',DelaySeconds=0)
You would observe in src/main/scala/org/elasticmq/rest/sqs/SendMessageDirectives.scala line 131:
val delaySecondsOption = parameters.DelaySeconds match {
      case Some(v) if v < 0 || v > 900 =>
        // Messages can at most be delayed for 15 minutes
        throw SQSException.invalidParameter("DelaySeconds must be >= 0 and <= 900")
      case Some(v) if v > 0 && queueData.isFifo =>
        // FIFO queues don't support delays
        throw SQSException.invalidQueueTypeParameter(DelaySecondsParameter)
      case d => d
}

that delaySecondsOption is set as 0, and this causes nextDelivery in line 142 to be assigned to AfterMillisNextDelivery(0), and that will cause the sender to send the message immediately instead of waiting for the queue-wide DelaySeconds configuration.
I prepared this PR to fix this: https://github.com/softwaremill/elasticmq/pull/1009


Refactor triggers to use typed enums

Changes
Just small refactoring of the triggers to use typed enums

I'm sorry I didn't notice the pull request! Thank you!


Some machines do not respect loss of power

Fully functional when depowered:

Chemical Disperser
Cargo Shuttle Console
Vending Machines
Medical Scanner

If you open the UI before it depowers you can still use:

R&D Computer

If you open the UI before it depowers you can look around in the UI and open new windows:

Autolathe
Protolathe

Eh probably gonna be remedied when someone gets around to implementing the power rewrite that's on the hackmd. For now I think they're powered by default just to not give devs headaches.


Markdown Image (link to a blogpost)

I have a doubt, we linked a photo with markdown so that when people click in the image they can go to a blogpost. The issue is that when we are in the post and we pass with the mousse through the photo, a zoom + icon appears so it doesn't look like a clickable image, do you know if we can change that so that it's more obvious that you have to click on it?

I will close this issue since this bug was already reported some time ago, please download the latest version in order to fix it.

Hi Eduardo
Thanks for the reply.
How can I do to update the new version? Attached is an image of what I see in ghost: do I have to click on "upload a theme" as if it was a new one?
In case I have to do that, eoes it modify anything in my bloghttps://blog.jampp.com/?
For example a developer has added a few things like to open the links in a new page or a search bar.. If I change the theme/updated it will I loose those things?
Thanks!

From: Eduardo Gómez<EMAIL_ADDRESS>Sent: Tuesday, July 28, 2020 5:43 AM
To: eddiesigner/liebling<EMAIL_ADDRESS>Cc: vikiivalle<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [eddiesigner/liebling] Markdown Image (link to a blogpost) (#240)
I will close this issue since this bug was already reportedhttps://github.com/eddiesigner/liebling/issues/206 some time ago, please download the latest versionhttps://github.com/eddiesigner/liebling/releases/tag/v.0.8.1 in order to fix it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/eddiesigner/liebling/issues/240#issuecomment-664872184, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APLVEBHIWJLLWILAXAM5H43R52FUZANCNFSM4PIWNBIA.

Hi,
If you've made changes in the theme then you might need to implement those again in this new version, it depends of the changes really. If he made the changes through the Ghost Admin then you can just upload the new version and that's it, but if he modified some theme files, then those changes have to be done again in the new version.
I know it's not optimal but that's how it works at the moment, that would happen with this theme or with any other theme.

Hi Eduardo,
Thanks for your reply!
I have an issue with the markdown image link. I was able to add an image and link it without problem but when I add a gif and link it I don't know why it appears twice (attached) and below de image a text appears.
Do you know what can I do?
Thanks!

From: Eduardo Gómez<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 11:08 AM
To: eddiesigner/liebling<EMAIL_ADDRESS>Cc: vikiivalle<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [eddiesigner/liebling] Markdown Image (link to a blogpost) (#240)
Hi,
If you've made changes in the theme then you might need to implement those again in this new version, it depends of the changes really. If he made the changes through the Ghost Admin then you can just upload the new version and that's it, but if he modified some theme files, then those changes have to be done again in the new version.
I know it's not optimal but that's how it works at the moment, that would happen with this theme or with any other theme.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/eddiesigner/liebling/issues/240#issuecomment-665686241, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APLVEBA4BQDOV3U2SAB2FQDR6AUMXANCNFSM4PIWNBIA.

I was able to solve it by doing it with html!

From: vicky valle<EMAIL_ADDRESS>Sent: Tuesday, August 4, 2020 7:48 PM
To: eddiesigner/liebling<EMAIL_ADDRESS>eddiesigner/liebling<EMAIL_ADDRESS>Cc: Author<EMAIL_ADDRESS>Subject: Re: [eddiesigner/liebling] Markdown Image (link to a blogpost) (#240)
Hi Eduardo,
Thanks for your reply!
I have an issue with the markdown image link. I was able to add an image and link it without problem but when I add a gif and link it I don't know why it appears twice (attached) and below de image a text appears.
Do you know what can I do?
Thanks!

From: Eduardo Gómez<EMAIL_ADDRESS>Sent: Wednesday, July 29, 2020 11:08 AM
To: eddiesigner/liebling<EMAIL_ADDRESS>Cc: vikiivalle<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [eddiesigner/liebling] Markdown Image (link to a blogpost) (#240)
Hi,
If you've made changes in the theme then you might need to implement those again in this new version, it depends of the changes really. If he made the changes through the Ghost Admin then you can just upload the new version and that's it, but if he modified some theme files, then those changes have to be done again in the new version.
I know it's not optimal but that's how it works at the moment, that would happen with this theme or with any other theme.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/eddiesigner/liebling/issues/240#issuecomment-665686241, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APLVEBA4BQDOV3U2SAB2FQDR6AUMXANCNFSM4PIWNBIA.


Jewish Shabbath Times Sensor

Description:
Jewish Shabbath Times .
This Sensor got the times from hebcal.com in json and parsing into HA.
This sensor has also sensor that tell the HA if is Shabbath or Not..(this is for Jewish people)
its very useful for us..
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):
- platform: jewish_shabbath
  havdalah_calc: 42
  time_before_check: 10
  time_after_check: 10
  scan_interval: 60
  latitude: 00.000 # need to be change
  longitude: 00.000 # need to be change
  geoid: 00000 # need to be change
  resources:
    - in
    - out
    - parasha
    - hebrew_date
    - is_shabbat

Checklist:

[X] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Hi @rt400,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Where is the difference to the jewish_calendar? Or could that be integrated in that sensor as additional condition?

Where is the difference to the jewish_calendar? Or could that be integrated in that sensor as additional condition?

Hi ,
Our sensors are completely different, it will not be possible to merge them
It displays only the name of the holiday and special times of that day only.
There is no information for Shabbat that is every week, which for me presents them a week ahead so it is possible to automate them with HA
My sensor contains time data constantly updated with correct information
In addition, I have a sensor that checks whether it is time for Shabbat. If it does, it turns into TRUE and when it returns it becomes FALSE.

Our sensors are completely different, it will not be possible to merge them

No, they are not different. Both are covering the same topic.

It displays only the name of the holiday and special times of that day only.

That seems already covered by holiday_name in the jewish_calendar sensor.

There is no information for Shabbat that is every week, which for me presents them a week ahead so it is possible to automate them with HA
My sensor contains time data constantly updated with correct information

You need to extract the data retrieval logic to a separate Python Module anyway. I suggest that incorporate the missing into hdate if possible and add the your additional sensors to jewish_calendar sensor.

In addition, I have a sensor that checks whether it is time for Shabbat. If it does, it turns into TRUE and when it returns it becomes FALSE.

This should be a binary sensor. If you want to go that route then you need to create a component with a binary sensor and sensor platform.

Our sensors are completely different, it will not be possible to merge them

No, they are not different. Both are covering the same topic.

It displays only the name of the holiday and special times of that day only.

That seems already covered by holiday_name in the jewish_calendar sensor.

There is no information for Shabbat that is every week, which for me presents them a week ahead so it is possible to automate them with HA
My sensor contains time data constantly updated with correct information

You need to extract the data retrieval logic to a separate Python Module anyway. I suggest that incorporate the missing into hdate if possible and add the your additional sensors to jewish_calendar sensor.

In addition, I have a sensor that checks whether it is time for Shabbat. If it does, it turns into TRUE and when it returns it becomes FALSE.

This should be a binary sensor. If you want to go that route then you need to create a component with a binary sensor and sensor platform.

HI ,
How do you determine they are not different?
Sorry I ask ... But do you understand the difference between a Jewish Sabbath and a Jewish holiday?
I checked that sensor is completely different from what I wrote, I do not use the library that he wrote HDATE. I take the information through the HEBCAL website.
In any case, the information he provides is incomplete. For example, a PARASHAT sensor works only on Saturday and throughout the week it prepares incorrect information, in addition there are no times for Shabbat.
I think that if you understood the difference between what he did and what I did, you would see that there is a huge difference. Without prejudice to the aforesaid.
I'd be happy to provide you with additional information to clarify your changes.

How do you determine they are not different?

Both are covering Jewish events which happen on a date or time.

Sorry I ask ... But do you understand the difference between a Jewish Sabbath and a Jewish holiday?

Obvious I don't. I look at the code and see that both contain the hebrew_date.

I checked that sensor is completely different from what I wrote, I do not use the library that he wrote HDATE. I take the information through the HEBCAL website.

He didn't wrote it as far as I remember but contributed massive amount of code to it to make it usable for  the existing sensor.

In any case, the information he provides is incomplete. For example, a PARASHAT sensor works only on Saturday and throughout the week it prepares incorrect information, in addition there are no times for Shabbat.

This may be true. If there is an issue then the issue should be addressed and a new integration proposed that is working around it.

I think that if you understood the difference between what he did and what I did, you would see that there is a huge difference. Without prejudice to the aforesaid.

The existing sensor is calculate the occurrence of an event, you are grabbing the data from the third-party source.
Let's get @tsvi in the loop because he is the author of the jewish_calendar sensor and can assist with his expertise.
You need to extract the logic to retrieve the data in a Python module anyway. Thus let's see that @tsvi is thinking about a possible integration in to hdate.

@rt400 @fabaff I suggest asking @tsvi

How do you determine they are not different?

Both are covering Jewish events which happen on a date or time.

Sorry I ask ... But do you understand the difference between a Jewish Sabbath and a Jewish holiday?

Obvious I don't. I look at the code and see that both contain the hebrew_date.

I checked that sensor is completely different from what I wrote, I do not use the library that he wrote HDATE. I take the information through the HEBCAL website.

He didn't wrote it as far as I remember but contributed massive amount of code to it to make it usable for the existing sensor.

In any case, the information he provides is incomplete. For example, a PARASHAT sensor works only on Saturday and throughout the week it prepares incorrect information, in addition there are no times for Shabbat.

This may be true. If there is an issue then the issue should be addressed and a new integration proposed that is working around it.

I think that if you understood the difference between what he did and what I did, you would see that there is a huge difference. Without prejudice to the aforesaid.

The existing sensor is calculate the occurrence of an event, you are grabbing the data from the third-party source.
Let's get @tsvi in the loop because he is the author of the jewish_calendar sensor and can assist with his expertise.
You need to extract the logic to retrieve the data in a Python module anyway. Thus let's see that @tsvi is thinking about a possible integration in to hdate.
I'm sorry...
I worked on my code enough days and hours to work properly without anyone's help!
Today this sensor works for me and some other members of our group and we all enjoy it.
I do not think you understand the difference between the two sensors.
I do not understand why I have to go down at the level of my sensor because someone did something similar to mine (the only similarity that exists only on the Hebrew date).
If that's the way I'm not willing to be part of it.
All in all I want to share what I've built with other friends through HA.

I do not understand your insistence on this ...

Thank you for bringing me in the loop.

As @fabaff mentioned I didn't write the hdate module. It was written by
@royi1000, I mainly made it more "pythonic", brought it up to speed to
python 3 added some tests and prepared it for inclusion to homeassistant.
@rt400 is correct that a. the parasha isn't shown correctly during the
week. This is on my "never-ending to-do list". b. The shabbat times are not
shown. Both of these issues can be fixed by fixing the sensor. c. There's
no boolean sensor that turns true/false based on whether it is shabbat.
This would be a nice addition.
In any case both sensors are supposed to provide the same type of
information. So I don't see the reason for duplicating the effort.
Personally, I feel the existing sensor is more in-line with @balloob
statements of keeping the information as much as possible local. There
should be no reason for pulling this type of information from a
third-party. All of it can be calculated locally without to much trouble.
I invite you to contribute to the existing sensor. Although the
implementations are completely different, I think our contributed efforts
might provide a better user experience.

Thanks,
Tsvi Mostovicz
<EMAIL_ADDRESS>www.linkedin.com/in/tsvim
On Tue, Oct 2, 2018 at 1:30 PM Yuval<EMAIL_ADDRESS>wrote:

How do you determine they are not different?
Both are covering Jewish events which happen on a date or time.
Sorry I ask ... But do you understand the difference between a Jewish
Sabbath and a Jewish holiday?
Obvious I don't. I look at the code and see that both contain the
hebrew_date.
I checked that sensor is completely different from what I wrote, I do not
use the library that he wrote HDATE. I take the information through the
HEBCAL website.
He didn't wrote it as far as I remember but contributed massive amount of
code to it to make it usable for the existing sensor.
In any case, the information he provides is incomplete. For example, a
PARASHAT sensor works only on Saturday and throughout the week it prepares
incorrect information, in addition there are no times for Shabbat.
This may be true. If there is an issue then the issue should be addressed
and a new integration proposed that is working around it.
I think that if you understood the difference between what he did and what
I did, you would see that there is a huge difference. Without prejudice to
the aforesaid.
The existing sensor is calculate the occurrence of an event, you are
grabbing the data from the third-party source.
Let's get @tsvi https://github.com/tsvi in the loop because he is the
author of the jewish_calendar sensor and can assist with his expertise.
You need to extract the logic to retrieve the data in a Python module
anyway. Thus let's see that @tsvi https://github.com/tsvi is thinking
about a possible integration in to hdate.
I'm sorry...
I worked on my code enough days and hours to work properly without
anyone's help!
Today this sensor works for me and some other members of our group and we
all enjoy it.
I do not think you understand the difference between the two sensors.
I do not understand why I have to go down at the level of my sensor
because someone did something similar to mine (the only similarity that
exists only on the Hebrew date).
If that's the way I'm not willing to be part of it.
All in all I want to share what I've built with other friends through HA.
I do not understand your insistence on this ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/17053#issuecomment-426225641,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTZcGxz0d_9NSwB5J2AG0QZA12RTzURks5ug0BKgaJpZM4XC3Ie
.

Thank you for bringing me in the loop. 1. As @fabaff mentioned I didn't write the hdate module. It was written by @royi1000, I mainly made it more "pythonic", brought it up to speed to python 3 added some tests and prepared it for inclusion to homeassistant. 2. @rt400 is correct that a. the parasha isn't shown correctly during the week. This is on my "never-ending to-do list". b. The shabbat times are not shown. Both of these issues can be fixed by fixing the sensor. c. There's no boolean sensor that turns true/false based on whether it is shabbat. This would be a nice addition. 3. In any case both sensors are supposed to provide the same type of information. So I don't see the reason for duplicating the effort. 4. Personally, I feel the existing sensor is more in-line with @balloob statements of keeping the information as much as possible local. There should be no reason for pulling this type of information from a third-party. All of it can be calculated locally without to much trouble. 5. I invite you to contribute to the existing sensor. Although the implementations are completely different, I think our contributed efforts might provide a better user experience. Thanks, Tsvi Mostovicz<EMAIL_ADDRESS>www.linkedin.com/in/tsvim
…
On Tue, Oct 2, 2018 at 1:30 PM Yuval @.***> wrote: How do you determine they are not different? Both are covering Jewish events which happen on a date or time. Sorry I ask ... But do you understand the difference between a Jewish Sabbath and a Jewish holiday? Obvious I don't. I look at the code and see that both contain the hebrew_date. I checked that sensor is completely different from what I wrote, I do not use the library that he wrote HDATE. I take the information through the HEBCAL website. He didn't wrote it as far as I remember but contributed massive amount of code to it to make it usable for the existing sensor. In any case, the information he provides is incomplete. For example, a PARASHAT sensor works only on Saturday and throughout the week it prepares incorrect information, in addition there are no times for Shabbat. This may be true. If there is an issue then the issue should be addressed and a new integration proposed that is working around it. I think that if you understood the difference between what he did and what I did, you would see that there is a huge difference. Without prejudice to the aforesaid. The existing sensor is calculate the occurrence of an event, you are grabbing the data from the third-party source. Let's get @tsvi https://github.com/tsvi in the loop because he is the author of the jewish_calendar sensor and can assist with his expertise. You need to extract the logic to retrieve the data in a Python module anyway. Thus let's see that @tsvi https://github.com/tsvi is thinking about a possible integration in to hdate. I'm sorry... I worked on my code enough days and hours to work properly without anyone's help! Today this sensor works for me and some other members of our group and we all enjoy it. I do not think you understand the difference between the two sensors. I do not understand why I have to go down at the level of my sensor because someone did something similar to mine (the only similarity that exists only on the Hebrew date). If that's the way I'm not willing to be part of it. All in all I want to share what I've built with other friends through HA. I do not understand your insistence on this ... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17053 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABTZcGxz0d_9NSwB5J2AG0QZA12RTzURks5ug0BKgaJpZM4XC3Ie .

@tsvi did you see my code ?
My sensor pulls the information for the current week.
So I get future information and every week start has new information.
This is what we are actually looking for (we = smart house group) for HA.
My sensor gets a full date and according to it compares whether it is Shabbat or not.
Is your able to do this?
For example: 2018-10-05T18: 02: 00 It's Saturday time. And is updated every week since the beginning of the week. I do not use points of reference but only GEOID.
I also do not think you should load all the sensors in one. It is always better to separate what is Shabbat and what is a holiday.

I've taken a look at your code. It is trivial to add the functionality
you're looking for. As I mentioned, it is on my to-do list.
Getting the info for the coming shabbat, requires calculating another
property for the HDate object. Let's call it "next shabbat".
Getting the info whether now is shabbat is even easier. Again I think we'd
be much better served with a local calculation then pulling the info from
another site.
Regarding multiple sensors, I disagree with you. My point with the Jewish
calendar sensor is to provide of all the information that can be derived
about a given Jewish date. This includes zmanim, daily learning and more.
The more I think of this I think this info should be local, especially as
you don't want your shabbes automations to behave like a regular weekday
because your connection to the internet has been disrupted.
It also allows for home assistant to be used as a "smart" shabbes clock
without an internet connection.
On Tue, Oct 2, 2018 at 2:31 PM Yuval<EMAIL_ADDRESS>wrote:

Thank you for bringing me in the loop. 1. As @fabaff
https://github.com/fabaff mentioned I didn't write the hdate module. It
was written by @royi1000 https://github.com/royi1000, I mainly made it
more "pythonic", brought it up to speed to python 3 added some tests and
prepared it for inclusion to homeassistant. 2. @rt400
https://github.com/rt400 is correct that a. the parasha isn't shown
correctly during the week. This is on my "never-ending to-do list". b. The
shabbat times are not shown. Both of these issues can be fixed by fixing
the sensor. c. There's no boolean sensor that turns true/false based on
whether it is shabbat. This would be a nice addition. 3. In any case both
sensors are supposed to provide the same type of information. So I don't
see the reason for duplicating the effort. 4. Personally, I feel the
existing sensor is more in-line with @balloob https://github.com/balloob
statements of keeping the information as much as possible local. There
should be no reason for pulling this type of information from a
third-party. All of it can be calculated locally without to much trouble.
5. I invite you to contribute to the existing sensor. Although the
implementations are completely different, I think our contributed efforts
might provide a better user experience. Thanks, Tsvi Mostovicz
<EMAIL_ADDRESS>www.linkedin.com/in/tsvim
… <#m_3048515686272623726_>
On Tue, Oct 2, 2018 at 1:30 PM Yuval @.***> wrote: How do you
determine they are not different? Both are covering Jewish events which
happen on a date or time. Sorry I ask ... But do you understand the
difference between a Jewish Sabbath and a Jewish holiday? Obvious I don't.
I look at the code and see that both contain the hebrew_date. I checked
that sensor is completely different from what I wrote, I do not use the
library that he wrote HDATE. I take the information through the HEBCAL
website. He didn't wrote it as far as I remember but contributed massive
amount of code to it to make it usable for the existing sensor. In any
case, the information he provides is incomplete. For example, a PARASHAT
sensor works only on Saturday and throughout the week it prepares incorrect
information, in addition there are no times for Shabbat. This may be true.
If there is an issue then the issue should be addressed and a new
integration proposed that is working around it. I think that if you
understood the difference between what he did and what I did, you would see
that there is a huge difference. Without prejudice to the aforesaid. The
existing sensor is calculate the occurrence of an event, you are grabbing
the data from the third-party source. Let's get @tsvi
https://github.com/tsvi https://github.com/tsvi in the loop because he
is the author of the jewish_calendar sensor and can assist with his
expertise. You need to extract the logic to retrieve the data in a Python
module anyway. Thus let's see that @tsvi https://github.com/tsvi
https://github.com/tsvi is thinking about a possible integration in to
hdate. I'm sorry... I worked on my code enough days and hours to work
properly without anyone's help! Today this sensor works for me and some
other members of our group and we all enjoy it. I do not think you
understand the difference between the two sensors. I do not understand why
I have to go down at the level of my sensor because someone did something
similar to mine (the only similarity that exists only on the Hebrew date).
If that's the way I'm not willing to be part of it. All in all I want to
share what I've built with other friends through HA. I do not understand
your insistence on this ... — You are receiving this because you were
mentioned. Reply to this email directly, view it on GitHub <#17053
(comment)
https://github.com/home-assistant/home-assistant/pull/17053#issuecomment-426225641>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTZcGxz0d_9NSwB5J2AG0QZA12RTzURks5ug0BKgaJpZM4XC3Ie
.
@tsvi https://github.com/tsvi did you see my code ?
My sensor pulls the information for the current week.
So I get future information and every week start has new information.
This is what we are actually looking for (we = smart house group) for HA.
My sensor gets a full date and according to it compares whether it is
Shabbat or not.
Is your able to do this?
For example: 2018-10-05T18: 02: 00 It's Saturday time. And is updated
every week since the beginning of the week. I do not use points of
reference but only GEOID.
I also do not think you should load all the sensors in one. It is always
better to separate what is Shabbat and what is a holiday.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/17053#issuecomment-426239854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTZcLgiOFqoeS1bkTIsgVZCAqJGCZ4Jks5ug06ogaJpZM4XC3Ie
.

@rt400 wrote:

If that's the way I'm not willing to be part of it.

Well I guess that's case closed.
The existing sensor works 100% local, offline and is based off an external lib. As the author has indicated the missing features covered by this integration can be added to the other one, and that's how it is supposed to be done. We're not going to have two integrations that do similar things.


Simple walker class which outputs XML

I created a simple walker class (ostream_walker) which outputs the XML (e.g. to std::cout) starting with a pugi::xml_node object at https://github.com/awsteiner/o2scl/blob/3962b8e9ee69a634ac0457bae21017efd8c56e62/src/other/xml.h . Let me know if it's useful to someone, e.g. if you want to use it for the documentation. I'm sure it's not perfect, but it may be helpful for others.

Is this substantially different from calling xml_node::print with the stream as the argument?

It's simpler, i.e. it doesn't include attribute information. I shared it not because the functionality was particularly interesting, but rather because seeing a slightly more complex walker might be helpful for users who would like to design their own walkers.

In either case thank you for your excellent work.

I shared it not because the functionality was particularly interesting

It should not be an issue, but a feature? Or moving it to Discussions may be a better fit?

I'm going to convert to a discussion since the documentation already has a simple example of a walker implementation.


Greedy : Add Coin change problem using greedy algorithm in C++

I will take this up. Please grant me

May I do this one?


Edited the story.txt and madlib.txt

Edited the story.txt and madlib.txt

Looks good, will merge this.


extending to aggregation

This is not an issue, but an exploration.
I have been gaining a working understanding of the sift.js framework, and it seems like it might be fairly straightforward to adapt this same (expression) framework for emulating other parts of the Mongo aggregation framework.  I am most interested in the $group operations and expressions for now, and was wondering how far off I might be on this.
Any feedback is appreciated.  I would certainly be interested in collaborating on such a project.

This definitely seems useful, and it lines up a bit with another project I'm working on: mesh.
I'd love to work on this sort of thing, but right now I'm hosed with other stuff. Great idea though!

Craig

Thanks for passing along the link to mesh!  Seems very useful for structuring interfaces and API in my current project as well.  I like the simplicity and embedding bus concept.
I have a good start on the aggregate lib, and hope to post after I do some cleanup and add a few more operations.
BTW, I notice you are using a lot of ES6 (and a little ES7) in your mesh examples.  What toolset (or polyfills) are you using for these?

On Oct 29, 2015, at 6:29 PM, Craig Condon<EMAIL_ADDRESS>wrote:
This definitely seems useful, and it lines up a bit with another project I'm working on: mesh.
I'd love to work on this sort of thing, but right now I'm hosed with other stuff. Great idea though!
Craig
—
Reply to this email directly or view it on GitHub.

I'm using babel right now for other projects, but any other toolset should working so long as it has promises.


Adding Math Equations on Readme

http://latex.codecogs.com/
Markdown does not work properly

Html tags works as expected

for backslash \, need to escape in markdown as \\ ref

Thus <img /> tag is preferred instead.

However, codecogs is not suitable for Retina display.


Python bindings build fail on Ubuntu 24.04

This is a preliminary issue that needs to be resolved before we add support for Ubuntu 24.
Libpointmatcher relies on pybind 2.5.0, which was released over 4 years ago. In Ubuntu 24, this dependency started to break. There are two issues I have encountered so far:

pybind 2.5.0 depends on distutils, which was marked deprecated in Python3.10 and was removed in Python3.12 that comes with Ubuntu 24.
After installing the dependency manually (it is part of setuptools), building pybind 2.5.0 fails in multiple places; see some examples below

/libraries/pybind11/include/pybind11/cast.h: In function 'std::string pybind11::detail::error_string()':
/libraries/pybind11/include/pybind11/cast.h:446:36: error: invalid use of incomplete type 'PyFrameObject' {aka 'struct _frame'}
  446 |                 "  " + handle(frame->f_code->co_filename).cast<std::string>() +
      |                                    ^~
/libraries/pybind11/include/pybind11/cast.h:446:75: error: expected primary-expression before '>' token
  446 |                 "  " + handle(frame->f_code->co_filename).cast<std::string>() +
      |                                                                           ^

Overall, I think now would be a good time to investigate and migrate to newer releases of pybind.

Fixed in https://github.com/norlab-ulaval/libpointmatcher/pull/595.


Crash

crash.txt
Almost immediately crashes. Are there any mods, like Forgero that Mythic Upgrades is not compatible with?

Fixed in #44

Actually, not fully, Origins' dev is required to rename old ModToolMaterials in his compat class

Does that mean I need to reach out to the Origins dev to loop them in? Or is that being handled on your end?

@linaraincalzando I have already told them in their bug report channel in discord, so it's on their end now

Oops, crash with origins was on our side, the fix will be available in next update

fixed


ADBDEV-4938-47: Add assertions to return from dynamic_cast.

Add assertions to return from dynamic_cast.
dynamic_cast may return NULL, so I added assertions.

https://github.com/arenadata/gpdb/pull/806


Add CodSpeed for HACV

synced local file(s) with worgarside/github-config-files.

This PR was created automatically by the repo-file-sync-action workflow run #8140531014

This PR is empty, closing it. :no_good:


Unable to run any command on Spark Notebook

Hi
I just installed Spark Notebook on Windows 10. I can open it alright but I can't run any commands on it. Error flashed is : "value sc not found" or "globalscope not found". Looking through the logs, I also found "invalid escape character".  Am I going wrong somewhere?

check if you are using newest version (from master). I remember there was a problem with character escapes in windows.
also make sure the path/directory where you've put the spark-notebook  (SN) do not contain any special characters
if this doesn't help, please post more info about the issue (SN version, spark version, error log...)

I think the problem is that for some strange reason spark notebook uses
sparkContext variable instead of the standard sc one. I also was confused
when opened sparknotebook the first time and sc did not work
On Jan 31, 2017 13:03, "vidma"<EMAIL_ADDRESS>wrote:

check if you are using newest version (from master). I remember
there was a problem with character escapes in windows.
also make sure the path/directory where you've put the
spark-notebook (SN) do not contain any special characters
if this doesn't help, please post more info about the issue (SN
version, spark version, error log...)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/andypetrella/spark-notebook/issues/806#issuecomment-276334847,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAzaxHmE4axys9oxx-zLBblqkUy3B54Uks5rXxUDgaJpZM4LybbR
.

@vidma

The version I am using is: notebook: 0.7.0; scala: 2.10.6; spark: 2.0.1; hadoop: 2.7.2. Do you remember if there was a way to solve the escape character problem?
The path is: D:\Rutgers\spark-notebook-0.7.0-scala-2.10.6-spark-2.0.1-hadoop-2.7.2\bin\spark-notebook. (hyphen - or period , aren't a special characters, right?)
Steps in Spark Notebook and Error Shown:

val rdd = sparkContext.parallelize(1 to 10000)
rdd.count
:15: error: not found: value sparkContext
val rdd = sparkContext.parallelize(1 to 10000)
^
:14: error: not found: value sparkContext
sparkContext.setJobGroup("cell-0102999565EE445393937605144EAAED", "run-1485884145556: val rdd = sparkContext.parallelize(1 to 10000)rdd.count")

@antonkulaga Could you tell me how to get rid of the problem? Also, it seems as if the program doesn't even recognize "sparkContext".

Further, attached is the log file of the session.
sn-session-e8fe939f-ee2c-49f7-8796-2335cab4569e-new.snb.txt

It seems like #740 has some resolution by using master branch from spark.notebook.io but I can't download the master branch from spark.notebook.io . Any ideas?

@andypetrella Requesting some help.

but I can't download the master branch from spark.notebook.io .

what do you mean? downloading master from http://spark-notebook.io/ should work, just select "notebook version" = "master"...
I got Build not available, but launched!. And In few minutes I got an email with download link.

Any update on this one?
I am using Spark notebook in a docker container that comes along https://github.com/big-data-europe/docker-hadoop-spark-workbench
Facing the same error.
error: not found: value globalScope
globalScope.sparkContext.setJobGroup(....)

Try to set variable SPARK_LOCAL_IP with value "localhost"

Try to set variable SPARK_LOCAL_IP with value "localhost"

P.S. localhost for spark local mode only. for cluster mode, you'd need IP address I assume.


Bitcore Constantly Crashing

It’ll go strong downloading the blockchain, but will unexpectedly crash.
[2018-09-22T10:13:41.081Z] info: Bitcoin Height: 8864 Percentage: 0.02
[2018-09-22T10:13:56.670Z] info: Bitcoin Height: 8864 Percentage: 0.02
[2018-09-22T10:14:11.957Z] info: Bitcoin Height: 10413 Percentage: 0.03
[2018-09-22T10:14:25.991Z] info: Bitcoin Height: 11758 Percentage: 0.03
[2018-09-22T10:14:41.287Z] info: Bitcoin Height: 13089 Percentage: 0.04
[2018-09-22T10:14:56.052Z] info: Bitcoin Height: 13089 Percentage: 0.05
[2018-09-22T10:15:04.845Z] warn: Bitcoin process unexpectedly exited with code:
null
[2018-09-22T10:15:04.845Z] warn: Restarting bitcoin child process in 5000ms
[2018-09-22T10:15:05.168Z] warn: ZMQ disconnect: tcp://<IP_ADDRESS>:29332
[2018-09-22T10:15:05.168Z] warn: ZMQ connection delay: tcp://<IP_ADDRESS>:29332
[2018-09-22T10:15:05.168Z] warn: ZMQ connection delay: tcp://<IP_ADDRESS>:29332
[2018-09-22T10:15:05.667Z] warn: ZMQ connection delay: tcp://<IP_ADDRESS>:29332
[2018-09-22T10:15:05.668Z] warn: ZMQ connection delay: tcp://<IP_ADDRESS>:29332
Any thoughts?

Are you querying insight/ doing anything other than letting the blockchain
sync?
On Sat, 22 Sep 2018 at 21:52, James<EMAIL_ADDRESS>wrote:

It’ll go strong downloading the blockchain, but will unexpectedly crash.
[2018-09-22T10:13:41.081Z] info: Bitcoin Height: 8864 Percentage: 0.02
[2018-09-22T10:13:56.670Z] info: Bitcoin Height: 8864 Percentage: 0.02
[2018-09-22T10:14:11.957Z] info: Bitcoin Height: 10413 Percentage: 0.03
[2018-09-22T10:14:25.991Z] info: Bitcoin Height: 11758 Percentage: 0.03
[2018-09-22T10:14:41.287Z] info: Bitcoin Height: 13089 Percentage: 0.04
[2018-09-22T10:14:56.052Z] info: Bitcoin Height: 13089 Percentage: 0.05
[2018-09-22T10:15:04.845Z] warn: Bitcoin process unexpectedly exited with
code:
null
[2018-09-22T10:15:04.845Z] warn: Restarting bitcoin child process in 5000ms
[2018-09-22T10:15:05.168Z] warn: ZMQ disconnect: tcp://<IP_ADDRESS>:29332
[2018-09-22T10:15:05.168Z] warn: ZMQ connection delay: tcp://
<IP_ADDRESS>:29332
[2018-09-22T10:15:05.168Z] warn: ZMQ connection delay: tcp://
<IP_ADDRESS>:29332
[2018-09-22T10:15:05.667Z] warn: ZMQ connection delay: tcp://
<IP_ADDRESS>:29332
[2018-09-22T10:15:05.668Z] warn: ZMQ connection delay: tcp://
<IP_ADDRESS>:29332
Any thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/litecoin-project/litecore/issues/9, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACfNujSc3zVGTt00mA_bGnDp__lUr0GRks5udqMJgaJpZM4W1cEx
.

Just letting the blockchain sync.

Issue resolved. Problem was low server memory. Upgrading server RAM from 2 GB to 4 GB resolved the issue. Thank you!


Workaround for phpseclib.

These changes have been published! View these changes here.

We had a offline discussion about this and we concluded that this workaround should be in our client library. Can I close this?

Closing in favor of https://github.com/google/google-api-php-client/pull/848


Add language links to docs index

Update the docs index page with links to other language docs.

Thanks @leocross, I just merged the changes.
As a follow-up, I think we can remove the "Other Supported Languages" page now (/cc @eddumelendez).


RTL property names don’t work without explicit name?

I’m not sure why this is happening, but this does not work (resulting in "unexpected property"):
#[derive(knuffel::Decode)]
pub struct الطاب {
    #[knuffel(property)]
    pub الطاب: i64,
}

… but this, with an explicit name, does:
#[derive(knuffel::Decode)]
pub struct الطاب {
    #[knuffel(property(name = "الطاب"))]
    pub الطاب: i64,
}

What do you mean by doesn't work? We do case folding of the names. So probably that name have a different representation when case-folded so it doesn't match the property you expect.
If case folding is wrong, you should report the issue into heck crate.
Other that that, feel free to reopen the issue providing more details.

@tailhook here is a repro.
This works as expected:
fn main() {
    knuffel::parse::<Vec<Foo>>("example.kdl", r#"foo prop=123"#).unwrap();
}

#[derive(knuffel::Decode)]
pub struct Foo {
    #[knuffel(property)]
    pub prop: i64,
}

This works (node with RTL name):
fn main() {
    knuffel::parse::<Vec<الطاب>>("example.kdl", r#"الطاب prop=123"#).unwrap();
}

#[derive(knuffel::Decode)]
pub struct الطاب {
    #[knuffel(property)]
    pub prop: i64,
}

This doesn't work (property with RTL name):
fn main() {
    knuffel::parse::<Vec<Foo>>("example.kdl", r#"foo الطاب=123"#).unwrap();
}

#[derive(knuffel::Decode)]
pub struct Foo {
    #[knuffel(property)]
    pub الطاب: i64,
}

The error is:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { source_code: NamedSource { name: "example.kdl", source: "<redacted>", errors: [Diagnostic { message: "unexpected property `\\u{627}\\u{644}\\u{637}\\u{627}\\u{628}`", labels: "[LabeledSpan { label: Some(\"unexpected property\"), span: SourceSpan { offset: SourceOffset(4), length: SourceOffset(10) } }]" }

This works (property with RTL name with explicit name set):
fn main() {
    knuffel::parse::<Vec<Foo>>("example.kdl", r#"foo الطاب=123"#).unwrap();
}

#[derive(knuffel::Decode)]
pub struct Foo {
    #[knuffel(property(name = "الطاب"))]
    pub الطاب: i64,
}

Case folding shouldn't be the problem here; Arabic has no case.

It looks like heck is a bit broken here: "الطاب".to_kebab_case() returns the empty string.

Actually, this does work properly in heck if the unicode feature is turned on. knuffel-derive might need to expose that.

Oh, sure. Let's enable the feature.


Don't overwrite rubySass setting when upgrading theme

I have sent this in a different PR because it seemed that the rubySass overwrite was made on purpose, so I'm not sure if this will break some other thing.
If unsure, just don't merge this PR but only this one

Hey @natecavanaugh, do you remember if this was indeed intentional? It seems indeed a bit intrusive and counter-intuitive, but seems to signal that we wanted to remove rubySass usage.
Still, this might be necessary in Windows environments... 🤔
I'm going to be merging, for now, we can always revert back if necessary if we figure out this as an error.
Thanks!

Still, this might be necessary in Windows environments...

AFAIK libsass support for Windows should be considered stable now. @GianBe could you confirm this?


error when pulling blocks for Puerto Rico MSA

This error occurs when attempting to instantiate a community using the from_lodes constructor for any Puerto Rico MSA. In this case, it was 10380.
KeyError                                  Traceback (most recent call last)
~/anaconda3/envs/harmonization/lib/python3.7/site-packages/geosnap/_data.py in blocks_2010(self, states, convert, fips)
    269             try:
--> 270                 blks[state] = pd.read_parquet(blocks_2010[f"{state}.parquet"].get_cached_path())
    271             except:

~/anaconda3/envs/harmonization/lib/python3.7/site-packages/quilt3/packages.py in __getitem__(self, logical_key)
    646         for key_fragment in self._split_key(logical_key):
--> 647             pkg = pkg._children[key_fragment]
    648         return pkg

KeyError: '72.parquet'

During handling of the above exception, another exception occurred:

KeyError                                  Traceback (most recent call last)
<ipython-input-27-509238f4e555> in <module>
----> 1 temp = transform_all(msa = '10380', intensive_variables = ['median_home_value'])

<ipython-input-18-13084b7691d1> in transform_all(msa, intensive_variables, extensive_variables)
     26     twentycomm = Community.from_census(msa_fips = msa, years=[2000])
     27     twentytencomm = Community.from_census(msa_fips = msa, years=[2010])
---> 28     blocks = Community.from_lodes(msa_fips = msa, years = [2010])
     29
     30     all_comms = [ninetycomm,

~/anaconda3/envs/harmonization/lib/python3.7/site-packages/geosnap/_community.py in from_lodes(cls, state_fips, county_fips, msa_fips, fips, boundary, years, dataset)
   1800                 ]
   1801
-> 1802         gdf = datasets.blocks_2010(states=states, fips=(tuple(allfips)))
   1803         gdf = gdf.drop(columns=["year"])
   1804         gdf = _fips_filter(

~/anaconda3/envs/harmonization/lib/python3.7/site-packages/geosnap/_data.py in blocks_2010(self, states, convert, fips)
    270                 blks[state] = pd.read_parquet(blocks_2010[f"{state}.parquet"].get_cached_path())
    271             except:
--> 272                 blks[state] = blocks_2010[f"{state}.parquet"]()
    273             if fips:
    274                 blks[state] = blks[state][blks[state]["geoid"].str.startswith(fips)]

~/anaconda3/envs/harmonization/lib/python3.7/site-packages/quilt3/packages.py in __getitem__(self, logical_key)
    645         pkg = self
    646         for key_fragment in self._split_key(logical_key):
--> 647             pkg = pkg._children[key_fragment]
    648         return pkg
    649

KeyError: '72.parquet'

we need to make it clear that we don't have PR geodata, so these queries will always fail. Can you provide the actual code  you're using?

I've modified the issue with your requested changes.
I've also tried fetching Puerto Rico data from the census, like this:
blocks = Community.from_census(msa_fips = '10380')
and this just results in an empty GeoDataFrame:

right, we dont have PR data so these will always fail, but i'll add an informative warning


fix: handle more complex expressions in sort-objects

Description

3e987ae7e6fa9fc21caa7e23fb8b17d9ece027f0 fixes references to dependencies/earlier params (#9), but not in some more complex cases. Examples are provided in tests.
Additional context

Do you think this is a good approach? I think we should try to search all of the nested nodes for Identifiers, which would be pushed to the dependencies array. I'm not sure I covered all the possible cases with this approach.
The tests also probably need some more work on the semantics :)

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.
[x] Read contribution guidelines.

@azat-io Wow, that was fast :) I'll try to follow up with a PR adding the missing test cases and possibly doing something about making this auto fixable.


Remove duplicated string descriptions in distributable-web extension

These are already defined on lines 15-17.

@pferraro for merge.


getting error in mautic 3.2

Class "Mautic\CoreBundle\EventListener\CommonSubscriber" not found while loading "MauticPlugin\MauticInfoBipSmsBundle\EventListener\CampaignSubscriber".
This is the error I am facing

The codebase is no longer being updated for Mautic versions later than 2.8.2.  No new fixes will be made by myself, but contributions could be evaluated/integrated to the code.


Things defined with deftype dont have docs

Gotta fix that

Ok they have docstrings now, just not appearing in the staple output..hmm

fixed


Remove error return value from NewUUID func

I see NewUUID internally call GetTime which returns error as a return value but this value will always be nil (https://github.com/google/uuid/blob/master/time.go#L45-L67).
So, it doesn't make any sense to return error from NewUUID when the value is always nil.

Changing this will break existing code.
When the UUID package was first implemented, in 2011, GetTime called os.Time which could return an os.Error and GetTime passed that error to its caller, NewUUID, which in turn passes it back to its caller.   When changed to use time.Now() there was no longer a path that would return an error, however, the signature could not be changed without breaking backwards compatibility.
If, someday, someone decides to fully follow the standard then a host wide persistent mechanism would need to be used to assure no two processes would ever return the same time value and it would always be monotonically increasing, even across reboots.  In that case I guess an error could be returned again, but the real reason is what I said above.
You can see the checkin at https://github.com/pborman/uuid/commit/e130d97558da97862b63559fa31be05c88ce3cc7#diff-9087329ff82d586a2f2e2393b726e00312bbd94506e54899e2012b93041bd698


UX is not that nice for viewing files in some repos

This depends on the repo but for VS Code the extension is pretty bad as displaying the files. This screenshot shows that for this PR I don't know what files are and opt to click each of the files to discover what they are (hover takes too long):

Note that this is after double clicking the sash which is meant to set the viewlet to the "optimal" size.
The viewlet takes almost half the width of my macbook's monitor to show the files fully:

This is how that problem was solved for disambiguating tabs:

I'm not sure what the best way to improve this is as putting the file names at the start would degrade the experience when the PR has mostly short paths, due to the folders not being lined up.

Have you considered a nested tree for the changed files? Like a subset of the explorer files tree, showing only the changed files. It would expand the list vertically, but make it easier to fit the entire thing horizontally.
I build rubberduck, a browser extension for GitHub pull requests, and I've gotten consistent feedback that the nested view gives an instant overview of the changes (case in point). One downside is that it needs additional clicks to expand a deeply nested file, but I've found that to be a worthwhile tradeoff (and can auto-expand multiple levels maybe?)

As an idea, what do you think about viewing the file extension icons on the left side and badges (M for merged) on the right side?

Thinking about this more and reading the comments we should probably try and match what we do in the explorer and search. Search for example will show the file name first and the folder slightly greyed out:

The icon could be on the right could also help and then we could move the change state over the the right just like in the explorer:

I'm sure this would need more ext API to get right.

The tree items have already been changed to display the file name, and then the full path as a description after it the same way the explorer and search show.
Additionally, we just merged a PR that will add a setting for toggling between a tree and a flat view of these files - by default it's set to tree.


NestedScrollView does not scroll unless a minimum number of children are added to the CustomScrollView

Steps to Reproduce

Create a project using the command below (from the official documentation)
flutter create --sample=widgets.NestedScrollView.1 mysample
Change the value of the childCount to 7
Remove the expandedHeight: 150.0 from the SliverAppBar
Set the extent to be 120
Build the App on Android or iOS

Expected results:
The List should be scrolled without any issues as there are a couple of items off the screen.
Actual results:
The List is not scrolled.

Change the item count to 10 or more (depending on the device screen) => The list is scrolling.
Code sample
Use the sample code for NestedScrollView and adjust it as in the "Steps to reproduce"

Logs

https://user-images.githubusercontent.com/5802728/188334536-2c8bbc23-5ac3-4703-bf36-01c88ad0543f.mov
https://user-images.githubusercontent.com/5802728/188334541-56b546f4-b12d-43e9-a9fa-d350ae33959c.mov

Issue is reproducible following the steps outlined above.
Code sample has been attached below for easy repro.
Labeling for further investigation from the team.

code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: _title,
      home: MyStatelessWidget(),
    );
  }
}

class MyStatelessWidget extends StatelessWidget {
  const MyStatelessWidget({super.key});

  @override
  Widget build(BuildContext context) {
    final List<String> tabs = <String>['Tab 1', 'Tab 2'];
    return DefaultTabController(
      length: tabs.length,
      child: Scaffold(
        body: NestedScrollView(
          headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
            return <Widget>[
              SliverOverlapAbsorber(
                handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                sliver: SliverAppBar(
                  title: const Text('Books'),
                  pinned: true,
                  forceElevated: innerBoxIsScrolled,
                  // expandedHeight: 150,
                  bottom: TabBar(
                    tabs: tabs.map((String name) => Tab(text: name)).toList(),
                  ),
                ),
              ),
            ];
          },
          body: TabBarView(
            children: tabs.map((String name) {
              return SafeArea(
                top: false,
                bottom: false,
                child: Builder(
                  builder: (BuildContext context) {
                    return CustomScrollView(
                      key: PageStorageKey<String>(name),
                      slivers: <Widget>[
                        SliverOverlapInjector(
                          handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                        ),
                        SliverPadding(
                          padding: const EdgeInsets.all(8.0),
                          sliver: SliverFixedExtentList(
                            itemExtent: 120.0,
                            delegate: SliverChildBuilderDelegate(
                              (BuildContext context, int index) {
                                return ListTile(
                                  title: Text('Item $index'),
                                );
                              },
                              childCount: 7,
                            ),
                          ),
                        ),
                      ],
                    );
                  },
                ),
              );
            }).toList(),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 3.3.0, on macOS 12.5 21G72 darwin-arm, locale en-GB)
    • Flutter version 3.3.0 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ffccd96b62 (6 days ago), 2022-08-29 17:28:57 -0700
    • Engine revision 5e9e0e0aa8
    • Dart version 2.18.0
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.71.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.48.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 13 (API 33) (emulator)
    • iPhone 13 Pro (mobile)      • 6E074BA5-191C-47D4-892F-FD96AFC34148 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 12.5 21G72 darwin-arm
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 104.0.5112.101

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.4.0-19.0.pre.72, on macOS 12.5 21G72 darwin-arm64, locale en-GB)
    • Flutter version 3.4.0-19.0.pre.72 on channel master at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 202f5771f4 (9 hours ago), 2022-09-04 20:28:23 -0400
    • Engine revision b94120dfe9
    • Dart version 2.19.0 (build 2.19.0-168.0.dev)
    • DevTools version 2.17.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.71.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.48.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 13 (API 33) (emulator)
    • iPhone 13 Pro (mobile)      • 6E074BA5-191C-47D4-892F-FD96AFC34148 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 12.5 21G72 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 104.0.5112.101

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

I have a small update on this.
The issue can't be reproduced if the change between tabs is made via a "Swipe" left/right gesture and is reproducible only on Tab Selection events via click actions.
I've also noticed that even after a Tab Selection via clicking if a small swipe gesture (left/right) is made the issue can't be reproduced.

It seems quite similar to this issue https://github.com/flutter/flutter/issues/32563
Possible workarounds could be https://github.com/flutter/flutter/issues/32563#issuecomment-1107640958 or https://github.com/flutter/flutter/issues/32563#issuecomment-808783908

@Piinks


warzone_rat2

Details

[x] windows_bypass_uac_via_pkgmgr_tool.yml
[x] windows_modify_registry_maxconnectionperserver.yml
[x] windows_unsigned_dll_side_loading.yml
[x] windows_mark_of_the_web_bypass.yml

What does this PR have in it? Screenshots are worth 1000 words 😄
Checklist

[ ] Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
[ ] CI/CD jobs passed ✔
[ ] Validated SPL logic.
[ ] Validated tags, description, and how to implement.
[ ] Verified references match analytic.

Reviewed and fixed up minor things!


Directional links are placed on top of each other

Directional links are placed on top of each other where Link1 (from Node1 to Node2) is placed on top of Link2 (from Node2 to Node1). It would be nice with a bend so it is distinguishable on the interface

Hi @larsbuch thanks for the feedback this is a good addition to the directional graphs feature. It's a work in progress.

I will look foreward to the change and test it when ready. Would you please note it here when it is checked in?

Sure thing @larsbuch

Hello @larsbuch! Coming back with some progress, a working version of bending links is available at this branch https://github.com/danielcaldas/react-d3-graph/tree/feature/bend-links you can already check it out. To make links bend you just need to pass down a config value for link.type it can be one of the following "STRAIGHT", "CURVE_SMOOTH", "CURVE_FULL".

I will test it in the weekend

Closing this with #91


feat: ensure hub networks match when syncing with peers

Motivation
Fixes: https://github.com/farcasterxyz/hub-monorepo/issues/835. Prevents testnet hubs from accidentally syncing mainnet and vice versa
Change Summary
Check the peer hubs network and make sure it matches ours before syncing
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[x] PR title adheres to the conventional commits standard
[x] PR has a changeset
[x] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
[x] PR does not require changes to the protocol

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers

Shouldn't we set the network when gossiping out in getContactInfoContent ?

Whoops, good point. Was in too much of a hurry.

Also, there's too much logic in hubble.ts. We really need to make it more easily testable.

Looks good!


<EMAIL_ADDRESS>on build #108: When leaving call feedback on iPad, it's not possible to…

Feedback from<EMAIL_ADDRESS>: When leaving call feedback on iPad, it's not possible to navigate back to the issue detail (in order to choose a different candidate. Also, when you finish making your calls, the issue list isn't updated to reflect the check mark.
CreatedMon Feb 20 2017 02:09:09 GMT+0000 (UTC)CFBundleShortVersion1.1CFBundleVersion11App uptime142.9053Build108Device typeiPad Air 2Device nameBen’s iPadScreen size1024Screen size1024px by 768pxBattery54% UnpluggedMemory free44 MB / 1588 MBDisk free9344 MB / 116397 MBNetwork IP<IP_ADDRESS>
Link to buddybuild feedback from build 108

Yeah, I wasn't sure how we wanted to handle this. I can add a fake back button to the 'navigation bar'-like image at the top, but if we maintain the full-screen image header, we don't want to use a traditional navigation style.

okay, added a Back button next to the Share button.

working in #93


support setting IP_TRANSPARENT on sockets

This allows you to set IP_TRANSPARENT on sockets for linux.
To setup for a local proxy you can use the following:
ref: https://powerdns.org/tproxydoc/tproxy.md.html
    export OUTBOUND_PORT=3100
    export PROXY_PORT=3000
    # move anything marked with a 1 --> table #100
    sudo ip rule add fwmark 1 lookup 100
    # table 100, treat all addrs as local loopback
    sudo ip route add local <IP_ADDRESS>/0 dev lo table 100

    # all inbound traffic on $OUTBOUND_PORT should forward to localhost $PROXY_PORT transparently
    sudo iptables -t mangle -I POSTROUTING -p tcp --dport $OUTBOUND_PORT -j TPROXY --tproxy-mark 0x1/0x1 --on-port=$PROXY_PORT --on-ip=<IP_ADDRESS>

    # all output traffic for $OUTBOUND_PORT will get marked and sent to table #100 (loopback)
    sudo iptables -t mangle -A OUTPUT -p tcp -m tcp --dport $OUTBOUND_PORT -j MARK --set-mark 1

Once done, then newly accept()'ed sockets will have the local_addr() set to the originally requested address and not the currently bound listening address.

Thanks @pepinns!


Remap Shortcut Menu Closing

Microsoft PowerToys version
0.69.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
Open the shortcuts menu under keyboard manager, click add shortcut remapping, type "shift(left)" and "caps lock" and then for mapped to, type "shift(left)" and "backspace," click OK. Now attempting to open it again, the menu freezes and then closes.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response


3D Descriptors Dragons

for review
This is the second iteration of #1145

Dear Greg,
I try to correct AUTOCORR3D, RDF, MORSE and simplify GETAWAY & WHIM computations.

AUTOCORR is not equal to Dragon (even the article is the same)
RDF & MORSE are equal to Dragon except for the weigthed States (Istate are not the same in Dragon & RDkit?)
GETAWAY is equal or close to Dragon except for the weigthed States, I fix RCON computation, I have issues with clustering ITH, ISH values in some cases no sure why.
WHIM is close to Dragon  except for the weigthed States (again).

GETAWAY and WHIM not converted to void but still std:vector of double
Tell me If we can do better,
BR
Guillaume

In order to detect memory problems, I've run valgrind across:

testRDF: no problems
testMORSE: no problems
testWHIM: problems
testGETAWAY: major memory leak
testAUTOCORR3D: major memory leak
testAUTOCORR2D: memory corruption

more details coming

Here's the type of error message (there are a bunch of them) that show up for testWHIM:
==21982== Invalid read of size 8
==21982==    at 0x4E9D928: RDKit::Descriptors::(anonymous namespace)::getWhimD(std::vector<double, std::allocator<double> >, Eigen::Matrix<double, -1, -1, 0, -1, -1>, int, double) [clone .constprop.546] (WHIM.cpp:147)
==21982==    by 0x4E9FB59: GetWHIMs (WHIM.cpp:279)
==21982==    by 0x4E9FB59: getWHIM (WHIM.cpp:332)
==21982==    by 0x4E9FB59: RDKit::Descriptors::WHIM(RDKit::ROMol const&, std::vector<double, std::allocator<double> >&, int, double) (WHIM.cpp:365)
==21982==    by 0x406365: testWHIM() (testWHIM.cpp:155)
==21982==    by 0x40324D: main (testWHIM.cpp:194)
==21982==  Address 0x87e0c10 is 0 bytes inside a block of size 24 free'd
==21982==    at 0x4C2EDEB: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21982==    by 0x4E9D7B2: aligned_free (Memory.h:243)
==21982==    by 0x4E9D7B2: conditional_aligned_free<true> (Memory.h:317)
==21982==    by 0x4E9D7B2: conditional_aligned_delete_auto<double, true> (Memory.h:445)
==21982==    by 0x4E9D7B2: ~DenseStorage (DenseStorage.h:403)
==21982==    by 0x4E9D7B2: ~PlainObjectBase (PlainObjectBase.h:88)
==21982==    by 0x4E9D7B2: ~Matrix (Matrix.h:127)
==21982==    by 0x4E9D7B2: RDKit::Descriptors::(anonymous namespace)::getWhimD(std::vector<double, std::allocator<double> >, Eigen::Matrix<double, -1, -1, 0, -1, -1>, int, double) [clone .constprop.546] (WHIM.cpp:143)
==21982==    by 0x4E9FB59: GetWHIMs (WHIM.cpp:279)
==21982==    by 0x4E9FB59: getWHIM (WHIM.cpp:332)
==21982==    by 0x4E9FB59: RDKit::Descriptors::WHIM(RDKit::ROMol const&, std::vector<double, std::allocator<double> >&, int, double) (WHIM.cpp:365)
==21982==    by 0x406365: testWHIM() (testWHIM.cpp:155)
==21982==    by 0x40324D: main (testWHIM.cpp:194)
==21982==  Block was alloc'd at
==21982==    at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21982==    by 0x4E9D740: aligned_malloc (Memory.h:220)
==21982==    by 0x4E9D740: conditional_aligned_malloc<true> (Memory.h:301)
==21982==    by 0x4E9D740: conditional_aligned_new_auto<long int, true> (Memory.h:423)
==21982==    by 0x4E9D740: DenseStorage (DenseStorage.h:386)
==21982==    by 0x4E9D740: PlainObjectBase (PlainObjectBase.h:471)
==21982==    by 0x4E9D740: Matrix (Matrix.h:300)
==21982==    by 0x4E9D740: RDKit::Descriptors::(anonymous namespace)::getWhimD(std::vector<double, std::allocator<double> >, Eigen::Matrix<double, -1, -1, 0, -1, -1>, int, double) [clone .constprop.546] (WHIM.cpp:143)
==21982==    by 0x4E9FB59: GetWHIMs (WHIM.cpp:279)
==21982==    by 0x4E9FB59: getWHIM (WHIM.cpp:332)
==21982==    by 0x4E9FB59: RDKit::Descriptors::WHIM(RDKit::ROMol const&, std::vector<double, std::allocator<double> >&, int, double) (WHIM.cpp:365)
==21982==    by 0x406365: testWHIM() (testWHIM.cpp:155)
==21982==    by 0x40324D: main (testWHIM.cpp:194)

How to solve the issues on WHIM ?
How can I compile with valgrind to check by myself?

The error messages indicate that memory that has already been freed is being used. I would guess that there's something wrong with the way the eigen code is being used.
To use valgrind: you just need to compile the code with debug symbols turned on. You can do this by telling cmake to build the code in Debug mode (instead of Release mode, which is the default). After rebuilding you'll have the symbols and you can do: valgrind testWHIM

No luck valgrid is not compatible with sierra
Envoyé de mon iPhone

Le 19 mars 2017 à 12:40, Greg Landrum<EMAIL_ADDRESS>a écrit :
The error messages indicate that memory that has already been freed is being used. I would guess that there's something wrong with the way the eigen code is being used.
To use valgrind: you just need to compile the code with debug symbols turned on. You can do this by telling cmake to build the code in Debug mode (instead of Release mode, which is the default). After rebuilding you'll have the symbols and you can do: valgrind testWHIM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ww can close this pull request.


Update documentation site to reflect Halogen 5 changes

#38 introduces lots of changes to Select, including a fix for #36. The component is now used a bit differently and the documentation site is horribly out of date. (As a side note: it would be nice if the docs site could be browsed at a particular tag; as it stands, it will only show the latest branch).
Some major changes that will need to happen:

The tutorials will all need to be rewritten
The QueryF documentation should be removed
We should introduce a short example of how to embed parent queries like the old-style Select for those who were relying on that behavior (some people used Select to directly hook in to parent state -- for example, using a selection change to update the page header)
We should add a description of the various ways to extend Select (when should you extend state? when should you extend the query algebra?)
We should describe some new best practices: exporting a spec + a default input for your component; handling messages output by the component but providing your own new message interface for your spec; etc.

Made some partial progress with this:

Updated template to halogen5
Edited the getting-started section and some of the dropdown tutorial

Editing the dropdown tutorial requires working backwards from the completed dropdown example, and this is more involved than I expected.
I think updating the remaining chapters of the purescript book would be a better use of time with my current understanding of the language. Might circle back to this task later.
I'm also hoping to consolidate some of the web framework templates. Basing this tutorial on a more widely used template might reduce maintenance effort.

Thanks for getting started on this, @milesfrain!
Now that purescript-templates/halogen exists and after reading the 'Featured Templates' discussion on Discourse I think it's sensible for the CitizenNet template to be archived and for the tutorial here to be based on the purescript-templates version. That's up to @davezuch, though.
I agree that editing the dropdown tutorial will be involved; the new version of Select is quite different from v1 and I rewrote both examples as part of that update. Thanks for getting started, though, and this is a nice reminder for me to update the relevant documentation on my side.

@thomashoneyman Not sure when you read through that Discourse thread, but Harry brought up some good points at the end of the thread. So, I'm not sure whether this is the best approach still.

With #53 in mind, I’ll move straight to updating the documentation specifically for the Hooks implementation. With that in mind I’m going to close this issue.


Invalid argument(s): Invalid return from platform getLocalTimezone()

Relevant code
final timezone = await FlutterTimezone.getLocalTimezone();

Getting this error in web on Chrome (Version 117.0.5938.132 (Official Build) (arm64)) using MacOS 14.0..
Any idea? Thanks for your effort!

Hey there, thanks for the report.
Without knowing what was actually returned by the plugin, it pretty hard to offer any insight. Maybe you could put a breakpoint inside flutter_timezone_web and see what the call to Intl.DateTimeFormat actually results in?

Hello @tjarvstrand ,
I have this issue as well.
This only happens on MacOS 14 Ventura.
I tried on several Mac's and all the Ventura ones are broken using any browser.
For example, my timezone used to be Europe/Brussels on 13.5, but now since 14.0 it says it's CET.

Meanwhile I'm getting undefined for the value.. (not sure if this is what you're looking for)

Meanwhile I'm getting undefined for the value..

It seems like this is a browser/system problem. We rely on Intl.DateTimeFormat.resolvedOptions() to provide the timezone.

timeZone
The value provided for this property in the options argument; defaults to the runtime's default time zone. Should never be undefined.

If this is not correct, I'm not sure what to do about it?
Could you try calling Intl.DateTimeFormat().resolvedOptions().timeZone; in the browser console?

For example, my timezone used to be Europe/Brussels on 13.5, but now since 14.0 it says it's CET

Though I understand how it can be problematic that this has changed, CET is a valid time zone. Even if you don't use it, you'll still have to take into account the fact that a lot of systems use abbreviated time zones rather than full names.

BTW, @vixez

This only happens on MacOS 14 Ventura.

This version does not exist :) Do you mean MacOS 13 Ventura or MacOS 14 Sonoma?

@tjarvstrand
Oops you are right, I meant Sonoma 😄

I agree that this is a tough one to fix, I don't really know where to start looking to get it back to Europe/Brussels.
In my app I do more calculations with timezones, and for this I use the flutter_timezone package in combination with the timezone package.
The issue is that the timezone package does not accept CET as a valid timezone.
Since pretty much every user using my app is in the Europe/Brussels timezone, for now I catch it like this
  static Future updateLocalTimeZone() async {
    localTimeZone = await getLocalTimeZone();
    if (localTimeZone == 'CET' || localTimeZone == 'undefined') {
      //TODO: This is a MacOS 14 Sonoma issue
      //Ticket: https://github.com/tjarvstrand/flutter_timezone/issues/18
      localTimeZone = 'Europe/Brussels';
    }
  }

But of course this is far from ideal, or futureproof.

Seems like it's a system/browser issue then like you said... On chrome (even after latest update on Version 118.0.5993.70 (Official Build) (arm64)) it is still returning undefined .. On firefox it at least returns something .. I guess you can close this issue if you want...?

But of course this is far from ideal, or futureproof.

Yeah, dealing with time is a PITA. If you're in a position to do so, I'd recommend you to do all your storage and calculations in UTC and only deal with time zones as close to the user as possible.

I guess you can close this issue if you want...?

Thanks. Given how thin this library is, I don't think there's much that can, or should be done about it here so I'll close this for now. Sorry I couldn't be of more help.


Small typo in ModuleVersion = '<IP_ADDRESS>'

We have tag <IP_ADDRESS>, but when you download code with this tag, you end up with record in xNetworking.psd1 : ModuleVersion = '<IP_ADDRESS>'. As a result, when you put code to the directory XNetworkking\<IP_ADDRESS>... you can't load it.

Are you downloading the code directly from the master branch or the dev branch? Or are you using Install-Module to get this from the PowerShell Gallery?
I've tried using:
Install-module xnetworking

and it seems to install the xNetworking module to the correct <IP_ADDRESS> folder as expected.
Or am I misunderstanding the issue?

I've used tag.
Tag -> <IP_ADDRESS> and then Download zip.
On 8/2/2016 8:12, Daniel Scott-Raynsford wrote:

Are you downloading the code directly from the master branch or the dev
branch? Or are you using Install-Module to get this from the PowerShell
Gallery?
I've tried using:
Install-module  xnetworking
and it seems to install the xNetworking module to the correct <IP_ADDRESS>
folder as expected.
Or am I misunderstanding the issue?
—
Reply to this email directly or view it on GitHub
https://github.com/PowerShell/xNetworking/issues/92#issuecomment-181213418.

Oh, I see. The issue here is that the Tag <IP_ADDRESS> is linked to the wrong commit/branch (the <IP_ADDRESS> release commit). @tysonjhayes - are you able to resolve this?
In the mean time, can you download the Master branch instead? The master branch is currently at <IP_ADDRESS>.

Excellent. Thanks.
On 8/2/2016 10:25, Daniel Scott-Raynsford wrote:

Oh, I see. The issue here is that the Tag <IP_ADDRESS> is linked to the wrong
commit/branch (the <IP_ADDRESS> release commit). @tysonjhayes
https://github.com/tysonjhayes - are you able to resolve this?
In the mean time, can you download the Master branch instead? The master
branch is currently at <IP_ADDRESS>.
—
Reply to this email directly or view it on GitHub
https://github.com/PowerShell/xNetworking/issues/92#issuecomment-181252555.

Not something I can fix - @KarolKaczmarek could you lend a hand?

Should be fixed now


Update sql-database-develop-direct-route-ports-adonet-v12.md

Fixes #25822

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

@Potapy4 Hello Nikita, I love this fix!  My team has to figure out what to do with all these links to MSDN blogs that are being retired.  Given the info available to my team, the task of updating all these links turns out to be rather difficult for us.
I am curious to know - How did you know the new updated Https URL to techcommunity.microsoft.com/ etc? Please @ message me with another Comment in this PR 25827, even after this PR is merged the @ still works.  Thanks.  GeneMi
#sign-off

@MightyPen Hey Gene! I just google the article title 😏:


Enhanced typescript.preferences.quoteStyle

Since #49653, it's possible to set a preference for auto-imports and generated code to either single, double or auto.
auto means "infer from other imports in the file" which is a sensible behavior but doesn't quite work if the current auto-import is the first one in the file. On a project that uses single quotes, I get double quotes with auto. Not sure if this has an elegant solution, I imagine values like autoOrSingle and autoOrDouble but it is a big ugly.

Yes, sorry, it's indeed a duplicate.


Fix a typo

Another one is in https://crate-ci.github.io/pr/clippy.html:

frustrating and possibly alienating the,.

Thanks! And I just pushed a fix for those additional typos.


Update builder.py

create "logger" variable of "logging" class
replace method self.info() to logger.info() #because of "Builder" class has no method info()

Awesome job - thanks for fixing this :-)


net/unbound REST plugin - merge into /plugins?

I am running https://github.com/EugenMayer/opnsense-unbound-plugin for about 1 year in production now and recently migrated it to 19.1, too - so it's at least a little battle proven
It does offer a part of Unbound as a MVC based plugin in term to offer a REST api to create / remove DNS entries. It does not cover any UI, it just uses the current core plugin as the core and offers a REST interface for some parts (to be extended).
Surely the plugin might need clarification in its name or it confuses the user with the core plugin ( its rather a companion yet, not a replacement).
Also this plugin could be a starting point for a migration of the "Unbound legacy plugin" to an MVC plugin.
Let me know if there is any interest in merging it into the community plugin repository, i am happy to do so

I will take a look what we could do about it...

Is there any way to contribute without the sidetone? This is nothing for me - still you obviously took it that way.
So if that is a burden, just close the issue and we are good to go. I have it running, i keep it running. I was just sharing, but it seems, there is simply no way to do that without stepping on whoever toes why ever.
I guess once a tone is set, you cannot get rid of it - well we are all humans after all.

@EugenMayer we review everything to ensure that there are not many bugs inside and to see if it fits into the product.
For example, your code needs some changes as it contains some bugs / coding errors:

when it is not called via POST, you respond with 500, which is an internal server error but the server responds correctly as this is a client error. In this case use 405 or the generic 400.
the library code should not be in the controller directory (move to library).
the xml configuration very likely can be encapsulated in a model for new and old style classes to work with the OPNsense interal MVC components.
you are printing data and exit with 0 instead of just returning an associative array, in which case all the encapsulation is done for you by the framework.
and probably some more

Eugen, I added a unbound-plus Plugin to insert mvc code via config includes. Are you still using this feature? Adding a domain section for creating A records should be quite easy, just like overrides


Is it necessary to create a helpers or utils package?

For example, export all the auxiliary methods of prosemirror-utils and provide some custom convenient methods for operating PM.

I exported some more utils in https://github.com/prosekit/prosekit/pull/721. Let me know if you have something more that want me to add.


The build.sh does not work on OSX

It looks like the Docker image build process handled by the docker-build.sh is not working on OSX.
Fix proposed by @chamilad (see the if condition):
image_exists=$(docker images $image_id | wc -l)
if [ ${image_exists} == "2" ]; then
    askBold "Docker image \"${image_id}\" already exists? Overwrite? (y/n): "
    read -r overwrite_v
fi

Fixed in commit https://github.com/wso2/dockerfiles/commit/7902c91db53d1e1dd57a2f5ddee93fd7856f1c42