Use PECL uuid function

This PR replaces the RamserUUID object uuid_create.
Calls to the PECL library are faster and avoid storing complexe object for nothing.

I'm fine with this, the leaner the better.
I am wondering why you have chosen for UUID_TYPE_DCE over UUID_TYPE_RANDOM what we used before (which should be v4). I know those 2 are the same in the polyfill but I can't find any documentation on the PECL extension and if it makes a difference, but I prefer UUID_TYPE_RANDOM better since it's more recognizable for the uninformed reader.
Also the build is failing because you left some @throws comments and unused imports (check the Travis logs) :)

That is interesting... it seems like ramsey/uuid might not be so bad after all and might be best to keep that since it looks like it is quite a bit faster than the PECL extension.
The polyfill itself is even faster but it looks like with the PECL extension you get a big downgrade in performance (comparing against ramsey/uuid) but without the PECL extension there is a bit of a win.
Overal it might be better to keep ramsey/uuid to be honest.
Great find on the announcement, did not even question the "extension is faster" statement: https://symfony.com/blog/introducing-the-new-symfony-uuid-polyfill

Ramsey can use the PECL extension too, however by default its usage is disabled and must be manually enabled, even if it's available. Also I don't know how much this extension is installed, so I cannot comment on it. The downside of this change is that the polyfill automatically uses it if it finds that it's available and there is no way to prevent it

I agree, so if the consideration to make this change is speed I think this is going backwards when the PECL extension is actually installed and only slightly better if it's not :)
As far as I've gathered the PECL extension might be more secure/resistent to collisions since it uses a better random source, but that is not critically important in this case.

Ramsey should use the random_bytes feature of PHP as far as I saw, but I didn't look at the full source code. One of the reasons I chose it instead of keeping the custom function like in 1.x was because it's a battle-tested library with a strong and safe implementation. I really think that the only thing that should be taken in consideration here is if we want to depend on such 3rd party library just to generate a string (because we only do that) or if we are keen to slow down things for users having the PECL extension installed but make it faster, but probably less safe, for those who don't. One of the reasons the extension is slower is because it opens a file descriptor to /dev/urandom every time a UUID v4 is generated
https://jolicode.com/blog/uuid-generation-in-php
Given that this change is just an internal change and doesn't affect in any way the public API it makes sense in my opinion to merge it and accept the tradeoffs of slowing things down if the extension is enabled because I doubt that such extension is so commonly used

Thank for your review and comments. Yes PECL, is 3 micro seconds slower than Ramsey/polyfill.
But I think that Event are not instanciated that often, and we can afford it.
The purpose of this PR was more about removing a dependency to a package (that already have 3 major version and a 4th in dev) and removing the burdon of maintaing/updating the dependency while keep Backward Compatibility with old version.
Feel free to close the PR if you think we won't affort such performance drawback, I wouldn't be offended :wink:

The purpose of this PR was more about removing a dependency to a package

As I already said, I'm more than happy to drop a dependency if we can and it makes sense and in this case for what we are doing which is just generating a UUID and then converting it to a string it totally makes sense, so you have my approval for the change. There is just that small change on the test class that I requested, then for me LGTM

tests are green. (sorry @stayallive i force-pushed you commit).
Looks like Appveyor is out

Looks like Appveyor is out

I'm looking at the issue, since PHP 7.1 is not maintained anymore the link to download the Windows version is not working anymore 🤦♂

@jderusse looks like everything is here so no worries :)
Just some AppVeyor issues, but the PR is solid, thanks!

@jderusse can you please force push to retrigger the CI? Once all checks are green I will merge

@ste93cry Done. But this PR targets develop (changed by you 2 days ago) While #938 has been merged in master.

Yes sorry my bad, I didn't notice it! I will rebase master on develop as soon as possible and then we should be fine here too


[BUG] Download error when regenerating OpenMapTiles

Describe the bug
On Windows 10, when generating using scripts/regenerate-openmaptiles, an error is thrown during the download of omt yaml files.
Exception in thread "main" java.io.FileNotFoundException: https://raw.githubusercontent.com/openmaptiles/openmaptiles/v3.12.2/layers\water\mapping.yaml

Pasting the suspect URL into Chrome works fine. Turns out that accessing this URL through Java returns a 404 for this particular .yaml file.
This bug results from the forward-slash and backslash in the URL (probably due to windows file separator).
To fix this, I added url = url.replaceAll("\\\\", "/"); above line 108 of Generate.java  .
https://github.com/lokkelvin2/planetiler/blob/0214605799655c28f0a33a6714ebb0b19eaf38da/planetiler-basemap/src/main/java/com/onthegomap/planetiler/basemap/Generate.java#L108
Note that I have not tested the impact of this patch on non-windows machines.

Thanks for taking the time to submit this bug report. Probably it is best to solve this problem at the source, i.e., where mappingPath is generated. Would you like to submit a pull request with the following change?
         if ("imposm3".equals(datasource.type)) {
-          String mappingPath = Path.of(layerFile).resolveSibling(datasource.mapping_file).normalize().toString();
+          String mappingPath = Path.of(layerFile).resolveSibling(datasource.mapping_file).normalize().toString().replaceAll("\\\\", "/");
           imposm3MappingFiles.add(base + mappingPath);
         } else {

This works on my linux machine...

Before I make submit a PR, I am trying to fix another related bug.
It appears that the requests for .yaml files are getting cached, so the Generate script does not always pull the latest commits from github. This issue had me questioning why certain OMT changes were not being reflected on my planetiler output.
One workaround is to change the --"tag" every generation so that a new url is always used.

I also had the impression once that the requests get cached, but then later on this was not the case anymore...

Thanks for reaching out, I agree it's best to fix where @wipfli points out the local disk path gets converted to a URL.  The Path is just a list of parts that get joined by the platform-specific path separator (\ on windows) so I think we just want to change that code to explicitly join path parts with /.
Also, it would be good to run the "regenerate" workflow on windows too to catch this kind of issue. - or we could just add the steps it runs to the end of the build job.

For the cache issue, the URL gets created in this method:
https://github.com/onthegomap/planetiler/blob/cce51668f296745dea264cd1a3f4caea1ccc27b7/planetiler-core/src/main/java/com/onthegomap/planetiler/util/Downloader.java#L100-L107
You can also add connection.setUseCaches(false); to that to tell it not to cache anything.  That method gets used to download input files, the geofabrik index, AWS index to get latest planet file, and this generator so I'm not sure if would make sense to bypass the cache for all of those? Or if it should be a parameter that the caller sets...?

Talk to a Polygon Dev on the Live support page so that your issue can be looked into.


SOLR-7642: add opt-in support to create ZK chroot on startup

https://issues.apache.org/jira/browse/SOLR-7642
Converting the patches from Steve Molloy and Isabelle Giguere into a pull request.

Can we add this add an optional Env Var as well?

This will make life easier when I run mutliple versions of Solr on a single ZK cluster!    Out of curiosity, would you ever NOT want it to be autocreated?    Is adding a switch that opts in the right way?   What if it was a switch to opt out of autocreate?

Can we add this add an optional Env Var as well?

Replied on jira where there was already other non-code discussion history.

This will make life easier when I run mutliple versions of Solr on a single ZK cluster! Out of curiosity, would you ever NOT want it to be autocreated? Is adding a switch that opts in the right way? What if it was a switch to opt out of autocreate?

Replied on jira where there was already other non-code discussion history.


About  ModuleNotFoundError: No module named 'sgmllib'

Hello @alireza-nasiri  ，
Thank you for sharing such excellent code .
May I ask you a question？
‘ModuleNotFoundError: No module named 'sgmllib'’  error when I run code，Looking up the information, we know that the package above python3 is gone，How to solve this problem？

I am not using that library and I run the code in python 3.7 which doesn't have that library. Maybe if you can copy the error code here to see which line of the code causes it, I can help you better.

Error：C:\Users\52937\Anaconda3\python.exe "F:/123/Contrastive Learning/code/SoundCLR-main/SoundCLR-main/train_contrastiveLoss.py"
Traceback (most recent call last):
File "F:/123/Contrastive Learning/code/SoundCLR-main/SoundCLR-main/train_contrastiveLoss.py", line 21, in
import dataset_ESC50 as dataset
File "F:\123\Contrastive Learning\code\SoundCLR-main\SoundCLR-main\dataset_ESC50.py", line 5, in
import transforms
File "C:\Users\52937\Anaconda3\lib\site-packages\transforms_init_.py", line 1, in
from .safe_html import safe_html, bodyfinder
File "C:\Users\52937\Anaconda3\lib\site-packages\transforms\safe_html.py", line 1, in
from sgmllib import SGMLParser, SGMLParseError
ModuleNotFoundError: No module named 'sgmllib'
Process finished with exit code 1

import dataset_ESC50 as dataset
import transforms
from .safe_html import safe_html, bodyfinder
from sgmllib import SGMLParser, SGMLParseError
These are four lines of code that indicate errors.

I look forward to your reply

I updated couple of the lines including line 5 in dataset_ESC50.py. I changed "import transforms" to "from utils import transforms". I think this should solve the error that you are getting. I also made couple of updates in other import commands in the code.
Please let me know if changing the import commands take care of this issue.

Thank you very much. This problem has been solved ！

Great, thanks for noticing this issue.


Was there any recent change in the behavior of AlterRows?

I am using AlterRows in my data flows since last 6 months. Since the date on this article is 5/6/2020 can you highlight if there was any change in AlterRow behavior recently?

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

ID: 64a72e9e-1698-c866-e5c0-fb1d050c7878
Version Independent ID: 0b4069f1-c3f7-bc94-527f-ea5348835059
Content: Alter row transformation in mapping data flow - Azure Data Factory
Content Source: articles/data-factory/data-flow-alter-row.md
Service: data-factory
GitHub Login: @kromerm
Microsoft Alias: makromer

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

No behavior change. The doc update was an added section talking about handling updates against identity and distribution keys.
https://docs.microsoft.com/en-us/azure/data-factory/data-flow-alter-row#merges-and-upserts-with-azure-sql-database-and-synapse

@ramit-rulz  We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


SRT output

I seen the other, issue but this definitely needed i dont think json to srt conv will work good as pure as whisper's normal srt option

which issue are you referring to @toprak ? is this model not able to save SRT?

@SeeknnDestroy yeah it only gives json

have you tried using the writer from whisperx library? https://github.com/m-bain/whisperX/blob/main/whisperx/utils.py#L406C10-L406C10

Here is how they use their writer https://github.com/m-bain/whisperX/blob/main/whisperx/transcribe.py#L155C8-L155C8

Hey @toprak @SeeknnDestroy - That's a lovely suggestion, would either of you mind helping with this? I am currently quite swamped with work and would appreciate any help possible!

@toprak This API provides SRT output with Whisper-v3 - https://developer.monsterapi.ai/reference/post_generate-speech2text-v2
The output is same as that given by faster-whisper

Quick script to convert the json into srt format, courtesy of chatGPT. Tested with VLC.
import json

def convert_to_srt(chunks):
    """
    Convert the chunks of transcripts into .srt format with correct newline placements.
    """
    srt_format = []

    for index, chunk in enumerate(chunks, start=1):
        start_time = chunk['timestamp'][0]
        end_time = chunk['timestamp'][1]

        # Convert timestamp to SRT format: hours:minutes:seconds,milliseconds
        start_srt = f"{int(start_time // 3600):02d}:{int(start_time % 3600 // 60):02d}:{int(start_time % 60):02d},{int(start_time % 1 * 1000):03d}"
        end_srt = f"{int(end_time // 3600):02d}:{int(end_time % 3600 // 60):02d}:{int(end_time % 60):02d},{int(end_time % 1 * 1000):03d}"

        # Append the formatted string to the list, with correct newline placements
        srt_format.append(f"{index}\n{start_srt} --> {end_srt}\n{chunk['text'].strip()}\n\n")

    return srt_format

# Path to the JSON file
file_path = '/path/to/your/transcript.json'

# Load the JSON file
with open(file_path, 'r') as file:
    transcript_data = json.load(file)

# Convert the transcript data to .srt format
srt_data = convert_to_srt(transcript_data['chunks'])

# Path for the output .srt file
srt_file_path = '/path/to/save/converted_transcript.srt'

# Writing to a .srt file
with open(srt_file_path, 'w') as file:
    file.writelines(srt_data)

print(f"Converted .srt file saved at: {srt_file_path}")


VSTS Agent incorrectly handles MacOS Monterey version detection (GetDarwinOSVersionString)

Having issue with YAML?
Please log an issue at Azure-Pipelines-YAML. Over there we discuss YAML templates, samples for Azure Pipelines, and designs for upcoming YAML features. Also a place for the community to share best practices, ideas, and so on. File suggestions and issues here if they're specific to YAML pipelines.
Having issue with Tasks?
Log an issue at Azure-Pipelines-Tasks. It contains all of the in-box tasks we ship with Azure-Pipelines/VSTS/TFS. If you're having issues with tasks in Build/Release jobs (e.g. unreasonable task failure) please log an issue there.
Having issue with software on Hosted Agent?
Log an issue at Hosted Agent Image Repository. It contains the VM image used in the Azure Pipelines Hosted Agent Pool. If you're having Build/Release failures that seems like they are related to software installed on the Hosted Agent (e.g. the dotnet SDK is missing or the Azure SDK is not on the latest version) please log an issue there.
Having generic issue with Azure-Pipelines/VSTS/TFS?
Please report it on Developer Community
Have you tried troubleshooting?
Troubleshooting doc
Issue cause described below.
Agent Version and Platform
Version of your agent? 2.144.0/2.144.1/...
2.195.2
OS of the machine running the agent? OSX/Windows/Linux/...
MacOS Monterey 12.1
Darwin  21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server?
If on-premises, which release? 2015.0, 2017.1, 2019 RC2, etc.
If dev.azure.com, what is your organization name? https://dev.azure.com/{organization} or https://{organization}.visualstudio.com
digitalasset
What's not working?
Please include error messages and screenshots.
Darwin agent reports wrong OS version in capabilities on macOS Monterey. Issue is caused by version calculation in GetDarwinVersionStriing that only handles Big Sur.
private static string GetDarwinVersionString()
    {
        // from .net 5 onwards the runtime returns the product version instead of the darwin kernel version
        var version = Environment.OSVersion.Version;
        if (Environment.Version.Major >= 5)
        {
            return $“{version.Major}.{version.Minor}“;
        }
        if (version.Major < 5)
        {
            return “10.0”;
        }
        if (version.Major - 4 <= 15)
        {
            return $“10.{version.Major - 4}“;
        }
        else
        {
            return $“11.{version.Major - 20}“;
        }
    }

Note that Monterey 12.1 will show as 11.1
Agent and Worker's Diagnostic Logs
Logs are located in the agent's _diag folder. The agent logs are prefixed with Agent_ and the worker logs are prefixed with Worker_. All sensitive information should already be masked out, but please double-check before pasting here.
Not required as issue described above

Quick Update: Agent v2.198.3, which contains the fix for the issue, has been fully rolled out.


feature: added preferSwap property

Thanks for submitting a pull request to RGL!
https://github.com/react-grid-layout/react-grid-layout/issues/1525
this feature will allow to swap between two item if its possible

why was this closed and not merged? I'm looking for a swap functionality and dragging items in my grid.

@galr52 any update on this feature?


Optional Removal of "[KANKA]" from Journal entries

It's a great way to see which entries came from Kanka and which ones were made directly in Foundry. However, when an entire campaign is made in Kanka then it's kind of redundant.
Maybe have an option in settings to remove this, make it smaller (like [K]) or an icon (I don't think Foundry Allows this) to make it less intrusive would be nice.

Hi @Unikatze, thanks for your Feedback.
You can actually rename folders (and change any other options presented by Foundry like color etc.) after they were created by the module to whatever you like and it will keep using that folder for the specific type of entries. So if you rename "[KANKA] Characters" to "Awesome Characters" it will keep importing all future characters into that folder.
Please let me know if that's enough for your use case. Maybe I should add a paragraph to the readme regarding this. :)

Hi @Unikatze, thanks for your Feedback.
You can actually rename folders (and change any other options presented by Foundry like color etc.) after they were created by the module to whatever you like and it will keep using that folder for the specific type of entries. So if you rename "[KANKA] Characters" to "Awesome Characters" it will keep importing all future characters into that folder.
Please let me know if that's enough for your use case. Maybe I should add a paragraph to the readme regarding this. :)

I just updated the readme to add this info. Please let me know if more is needed to in this regard.

I just updated the readme to add this info. Please let me know if more is needed to in this regard.


How to start docker container using docker-compose

Question
I'm trying to start leon in docker mode but it seems to execute docker compose instead of docker-compose. Where can i change this?

`root@leonai:~# leon  start

<EMAIL_ADDRESS>docker:run
docker compose up

docker: 'compose' is not a docker command.
See 'docker --help'
Error: Command failed with exit code 1: npm run docker:run
root@leonai:~# docker-compose version
docker-compose version 1.29.2, build unknown
docker-py version: 5.0.3
CPython version: 3.11.1
OpenSSL version: OpenSSL 3.0.8 7 Feb 2023
`

nevermind, it turned out that i need docker-compose-plugin package


Can't set redirectUrl for localhost testing

I am no longer being forwarded back to localhost when running my app in development mode.  I use to be able to log in with Google and get the token back on the app.  Now it just redirects back to the authDomain instead of the domain that it came from.

Hi @megamindbrian ! We have a required issue template. I'm going to close this issue, but free to open a new one that follows the template. Also if you could provide a plnkr that demonstrates the problem that would help out tremendously!

Thanks for nothing. Good thing I don't need to use this anymore.
On Aug 16, 2017 6:07 AM, "David East"<EMAIL_ADDRESS>wrote:

Closed #933 https://github.com/firebase/angularfire/issues/933.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/angularfire/issues/933#event-1208236823, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX5XbgexjVFV4nbydsg0mDId_2_9MPpuks5sYumVgaJpZM4NlzwE
.


Restart Addon by Automation?

Hi,
thank you for your Addon
is it possible to restart Addon by Automation?

Yes, that's possible. You have to use the restart add-on from supervisor service.


Remove extra production build steps from frontend.sh

These are all now run in the default gulp scripts and gulp styles tasks.
Removals

Extra build steps for ondemand and nemo stuff in production in frontend.sh

Testing
🤷♂ I suppose we wait to see it get merged and deployed onto Build?
Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Yes, you're right! Ran that and confirmed that the subtasks still run.


Not able to post data(NSData) in body

Hi ,
Could anybody please tell me, using this library how can I send a custom data (NSData) through post request?
Thanks
Vishun

By NSData, I assume you mean uploading a file. See this:
https://github.com/daltoniam/SwiftHTTP#upload
https://github.com/daltoniam/SwiftHTTP/blob/master/Source/Upload.swift#L109
Simply follow the same upload example from the README and just change the Upload object to use the NSData file upload version instead of the fileURL one.
let yourData = //... your NSData object
do {
    let opt = try HTTP.POST("https://domain.com/new", parameters: ["aParam": "aValue", "file": Upload(data: yourData, fileName: "myFile", mimeType: "image/png")]) //your whatever your mime type is
    opt.start { response in
    //do things...
    }
} catch let error {
    print("got an error creating the request: \(error)")
}

mimeType list:
https://www.sitepoint.com/web-foundations/mime-types-complete-list/

I want to set a json string as nsdata into body. I did not find a way to set body like we do in case of NSMutableRequest httpBody

Ah, that adds context, thank you 😄. SwiftHTTP is built to serialize the parameters for you, so if you want to send the HTTP body as data yourself, you can do that with a bit more code:
https://github.com/daltoniam/SwiftHTTP/blob/master/Source/Operation.swift#L385
https://github.com/daltoniam/SwiftHTTP/blob/master/Source/Operation.swift#L243
do {
    guard let req = NSMutableURLRequest(urlString: yourURL) else { return }
    req.verb = .POST
    req.HTTPBody = //your data
    let opt = HTTP(req)
    opt.start { response in
        if let err = response.error {
            print("error: \(err.localizedDescription)")
            return //also notify app of failure as needed
        }
        print("opt finished: \(response.description)")
        //print("data is: \(response.data)") access the response of the data with response.data
    }
} catch let error {
    print("got an error creating the request: \(error)")
}


Add SetWindowKeepAspectRatio

This PR adds a new method that fixes the aspect ratio while resizing.
#1804

Well fuck.


Fix decoration of symfony scoped http clients

This MR Fixes #700 and resolves #701
I had a look how this bundle decorates the http-client. It iterates over all tagged http client services and creates new decorated services of them. This is not the intended decoration way and (see update 1) should also not be necessary (?).
Instead just the default http_client needs to be decorated which is put into all other (scoped) services.
This changes the Sentry\SentryBundle\Tracing\HttpClient\TraceableHttpClient not to be the first service in the decoration chain anymore, but this is hopefully not important.
Note:
I did not test the function of sentries TraceableHttpClient before or after my change, I just tested the decoration chain to be intact for the default http client or when used as a scoped service.
I tested it in Symfony 6.2 and can test this next week also in Symfony 5.4 which has no bigger internal changed behavior in this regard tho.
Update 1:
Removed the comment ragarding suggested way to decorate all different http client services because there actually ia none.

This is not the intended decoration way and should also not be necessary

Actually, it does it this way because Symfony does the exact same thing here...

Yeah, I know this had to be the source. First of all I am by far no decoration expert and just learned a lot of the container building in the last weeks.
I indeed cannot find something official the way we are doing it but to me it is simple, straight forward and I cannot see a "reasonable" scenario it fails. One could be self created services tagged by http_client.client which is no promoted tag in any way.
Symfony in the few extension descriptions it has, just points to a general decoration document which surely does not help here.

Would you mind checking if you are the same behavior you’re reporting for the TraceableHttpClient used by Symfony to collect the data for the profiler?

@ste93cry do you mean if the TraceableHttpClient is actively used / part of the decoration? As I wrote at the end of #700 it does not happen with TraceableHttpClient being part of the chain.
It happened on our servers and took me quiet some time to find the root cause in my environment where debugging and the webprofiler are active.

Another general problem you'll face when decorating every tagged client and being placed in front of the ScopingHttpClient is to not having the complete URL.
Depending on the type of the scoped client you'll often just receive the relative url and the base_uri is prefixed by the ScopingHttpClient which all later clients receive in the request.
I noticed that the URL is also handled by your client which does not work correctly then.

I am surprised this and more importantly the underlying bug is still open. IMO the current state of the http client
tracing implementation is error prone and can lead to various problems (as for me) which stay maybe undetected. Especially as it is activated by default.
Talking of this specific PR Iam relatively confident it does its job well but it needs some tests/confirmation.
I do not wait for it tho, because we decided to disable the tracing. At least for now.

I tested the changes and I'm still having issues. Symfony 6.3+ reworked the way the HTTP client the decoration is done, so it should be pretty easy to fix the issue we're having here by simply decorating the http_client.transport service. However, for older versions of the framework, I still have to find a way that works: the problem is that they're using some weird way to decorate the services based on referencing the *.inner service directly instead of using the classic decoration approach supported by the framework, and it's hardcoded which service is referenced as HTTP client 🤦

Can you tell the kind of problems?

Wasted enough energy trying to convince it is a problem necessary to fix and this likely the correct solution.

I'm sorry that you feel like you've wasted energy, the reported issue is clearly a bug and noone doubts that needs to be addressed. Unfortunately, this package is managed by a couple of volunteers and we often don't have all the time and resources to respond as quickly as expected. Regarding the issues that I have with your solution, I've observed that the decoration is not applied in all cases, depending on the configuration you have. Assuming a config like the one below, the http_client service is decorated, while the scoped clients are not.
http_client:
  default_options:
    retry_failed: true
  scoped_clients:
    noretry.client:
      retry_failed: false
      base_uri: https://example.com/
    example.client:
      retry_failed: true
      base_uri: https://example.com/

With older versions of the frameworks, I've observed even worse scenarios, e.g. other decorators disappearing from the chain. This is not to say that the proposed solution is the wrong way, but it needs a lot more work to be reliable, apparently.

@ste93cry this is indeed an issue that can be fixed by increasing the decoration priority to let's say 15. It needs to exceed the RetryableHttpClient which has priority 10.
I did not notice because we do not use this feature

Unfortunately, I tried to change the priority and it still didn't fix the issue, in particular on versions of the framework prior to 6.3. I suggest setting up a small project running those versions and trying for yourself these changes to see what I'm talking about

I tested the fix just an hour ago on Symfony 4 and 5 with and without retryable and on 5.4 with multiple decorations.
Did you look for the decoration in the whole chain? It comes after the scoped client.

I tried again, and I confirm what I already mentioned:
Symfony 6.3

Setting the http_client.mock_response_factory config option makes the decoration fail for the scoped clients: I tried setting both a negative and positive decoration priority, but it didn't matter.
Enabling the UriTemplateHttpClient by installing one of the supported and required packages, e.g. guzzlehttp/uri-template makes the decoration fail: it works for the default HTTP client, but not for the scoped clients, no matter the decoration priority.

Symfony 5.4

Setting the http_client.mock_response_factory config option makes the decoration fail: I tried setting both a negative and positive decoration priority, but it didn't matter.

@ste93cry I cannot follow all points, but I now first tested it in Symfony 6.3. The http_client.transport introduction brought a breaking change no longer have a working decoration when scoped clients come into play.
I didn't want to try to find a way around it directly or file a Symfony bug.
Instead I pushed a new commit to my branch which fixes the decoration for Symfony 6.3 by using the http_client.transport service from this version on.
I tested this change in Symfony 5.4, 6.2 and 6.3 without debug activated (only) and with active retryable.
I still don't know why you do not get it to work in versions prior to 6.3 if that should be the case.
Regarding mock_response_factory I did not test this. It probably is working in Symfony 6.3 now because of the transport service introduction. Not sure about earlier versions. I see no value in expecting the decoration there or is the http-client feature completely broken?

Instead I pushed a new commit to my branch which fixes the decoration for Symfony 6.3 by using the http_client.transport service from this version on

This is indeed a part of the fix that we need. Since 6.3, it looks like they finally got the decoration right, so that's one less problem we have to tackle.

The FrameworkBundle 6.3 feature detection was pretty tricky

It should be enough to just check that the http_client.transport service exists in the container. If it is, then we have to decorate it, otherwise, we have to fallback to another mechanism to get things right.

I tested this change in Symfony 5.4, 6.2 and 6.3 without debug activated (only)

I tested it using the dev environment, which adds yet another decorator to the chain. When using the http_client.mock_response_factory, there's no apparent way to make the decoration to work by using the standard decoration approach.

I see no value in expecting the decoration there or is the http-client feature completely broken?

We should get things right for all cases, otherwise, depending on which option you configured, you would see different behaviours which are hard to track and understand. I'm working on an improved solution, it seems to work but I need to polish it and find a meaningful way to test it.

It should be enough to just check that the http_client.transport service exists in the container.

You can try but as far as I saw the definitions are not there at this point and even they would I don't know how safe it is to rely on it.

We should get things right for all cases, otherwise, depending on which option you configured, you would see different behaviours which are hard to track and understand

The mock_response_factory is for testing purposes of the own project using the http-client to simulate some specific responses. I see no realistisch scenario they would care a sentry decoration is or isn't there.
Especially when it should work in never versions from this point on.

Since you pushed new commits after closing this PR, I cannot reopen it, hence I've submitted my solution in a new one. I tested it on all versions of the framework we support, both in development and production mode, with both the retryable and the mock client enabled/disabled. It seems to work fine, but if you could make some more tests on your own it would be great!


Check for github action updates using dependabot

This will use dependabot to check for any updates to the github action packages which this project uses and submit pull requests with version bumps in order to keep packages up-to-date on a monthly basis.
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot

This doesn't feel like it needs a CHANGELOG entry. Any objections @tmuxinator/tmuxinator?


Warning: componentWillMount has been renamed,

"react": "^16.12.0",
"react-dom": "^16.12.0",
"react-redux": "^7.2.0",
"react-router-dom": "^5.1.2",
"react-scripts": "3.4.0",
Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

Move code with side effects to componentDidMount, and set initial state in the constructor.
Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: BraftEditor

react_devtools_backend.js:6 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

 See https://fb.me/react-unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

 See https://fb.me/react-unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.


[v4] Preview error on some web browsers : No type for path

Hi @angeloashmore,
Thanks for your work on gatsby-source-prismic, it's a pleasure to work with :)
I've got a mysterious error on preview mode and would need your help to understand it:

Stack

Built and deployed on Gatsby Cloud + Gatsby Hosting,
gatsby-source-prismic is version 4.0.0-beta.15 (edit: updated to 4.0.0-beta.18, nothing changed),
We are using the Custom Types API integration to retrieve the types schemas automatically

Situation
This error only happens on the preview mode of the deployed version of our website (here if you need it) - I couldn't reproduce it locally (neither in a dev server, nor by building it locally).
I tried rebuilding and emptying cache with no success.
I've got some troubles understanding the meaning of this message, and am not comfortable enough with the functional programming style used in proxyDocumentSubtree.ts to understand this part of the code.

What is this mysterious "path" : 65835afba98d019db2da6746b47aaf07 ?
I understand that this error could happen if my code is not synced with the Prismic custom types, but by using the Custom Types API, everything should be in sync, right ?
I can't reproduce it locally ; do you see any reason for it ?

Update :
This error stops showing when we switch browsers for the preview (in my case, from Google Chrome to Firefox), so we're not blocked anymore.
For the record, I tried clearing the cache, cookies and everything with no success ; whereas my colleague didn't even have this problem in the first place.
Therefore this issue is now more of:

a feature request to add a more precise error message when this kind of error happens,
an information for you that this error can happen :)

Hey @benjaminwaterlot, thanks for the detailed report. This is very helpful!
For some background on the error: The preview plugin reads a file that contains a mapping between your Prismic custom type fields to their type (e.g. "RichText" or "Image"). It does this to re-shape documents from the Prismic API into something that matches the Gatsby GraphQL API. It MD5 hashes the field names to hide your Custom Type fields so it is not exposed to users.
The MD5 hashing only happens in production (i.e. process.env.NODE_ENV=production). In development, you will see a full path for the field (e.g. "page > data > title").
Since the error only appears in production for you, and intermittently, it's possible the MD5 function is not always returning the same result for a given field name. Or the plugin isn't downloading the types file correctly.

Can you perform the following test on your local machine (not Gatsby Cloud)?

Run NODE_ENV=development gatsby build to build the site without production mode.
Run gatsby serve.
Preview a document from Prismic (you may need to add another preview URL to Prismic for http://localhost:9000/preview).

Are you able to recreate the error using this version of the build?
Next, can you re-try these steps, but with NODE_ENV=production? This will enable the MD5 hashing (this is done by default on Gatsby Cloud)

Run NODE_ENV=production gatsby build to build the site with production mode.
Run gatsby serve.
Preview a document from Prismic.

Are you able to recreate the error using this version of the build?

Hey @angeloashmore, thanks a lot for your answer.
I already had tried to replicate the error locally (both in yarn dev and yarn build, and I verified that NODE_ENV changes had no impact). So it seems tied with the execution environment on Gatsby Cloud, as strange as it seems.
However, following your answer, I completely removed the MD5 hashing (using patch-package to remove the NODE_ENV check after the package is installed).
The error message then changed to No type for path: page.
page is the id of one of our Custom Types, and there is no clear reason why this error would happen - especially only when executed on Gatsby Cloud.
We fully use the "Custom Types API" (until now, I didn't even pass the schemas prop in gatsby-config).

Workaround
So I figured I would try to stop using this Custom Types API, and here's what I did :

Use the https://customtypes.prismic.io/customtypes endpoint to retrieve all my custom types,
Save them as .json files,
Feed them to the schemas prop,
Remove the customTypesApiToken to prevent the automatic use of the Custom Types API at build time.

It seems to work, as the preview is now functioning on all environments (I'm not fully confident given the randomness of the previous problem, but it really seems to be fixed).
Do you see a reason why the automatic retrieval of types may fail only in certain execution environments ?

I think I've got news :D
I found this line in the build :
verbose 11.748821172 gatsby-plugin-prismic-previews(shine) - Wrote type paths store to public/static/621f58b4cec4ad92fb044e46727a5683.json

So I went to see this JSON file on our deployed website:
https://shinestaging.gatsbyjs.io/static/621f58b4cec4ad92fb044e46727a5683.json
It was not up-to-date, and was missing my latest Custom Type, whether the one served on localhost:9000 was up-to-date.
I cleared the cache by doing a force-refresh on this particular URL (a simple refresh didn't change anything, I guess because of server-side caching ? The .json request was marked as 200, so I suppose it can't be browser caching).
After this cache clearing, the preview started working again.
Cache problem would explain browser inconsistencies and having the problem only on online environments.
@angeloashmore do you think setting up a correct cache policy can be done on the plugin side ?
I'm not very proficient on these subjects.

@benjaminwaterlot Sorry for the delayed reply. This is great insight!
Gatsby itself cannot manage how the web server provides cached content/headers, but we can make sure the filename changes anytime a schema is updated. It currently only uses the repository name which is a mistake due to the assumption that the server will properly invalidate the cache (I believe services like Netlify will do this automatically, but we should make a universal solution).
I have to think a bit on how it can be implemented but I will report back once a fix is published. Thank you for the detailed analysis!

Hey @benjaminwaterlot, can you try out the latest beta and test for this issue again<EMAIL_ADDRESS>I wish I had thought of this sooner, but I changed the fetch function for that JSON file to effectively skip the browser's cache. This should solve the issue. If it doesn't, there's an extra level of ignoring the cache that we can try, but I want to try this version first.

Hey @angeloashmore, I'm updating right now and will keep you updated (I think I should encounter this error in the next two days, when I add a new custom type, if the error is still there).
Thanks for your answers! :)

@benjaminwaterlot Thanks! I appreciate it!

I'm going to close this as it should be fixed, but I can reopen it if the issue persists. Thanks!

Indeed - I can confirm that the error didn't happen again after the upgrade, thanks ! 🎉


Get the BLE beacon name

I'm trying to understand if it is possible using this library to get (besides the information already there) the name of the bluetooth beacon.
I checked the code and didn't see any place where the information might be loaded. But I rather ask and be sure.

The name is not part of the standard beacon format. Usually it is fetched online from the backend of the beacon manufacturer (if you use their apps). So, no unfortunately this is not possible.


Correctly map Hs argument in jonswap_spectrum

This fixes a bug, described in #132, where the Hs argument input into the jonswap_spectrum function is not properly mapped to the corresponding mhkit.wave.resource.jonswap_spectrum function. This maps Hs into the 3rd argument of jonswap_spectrum when the gamma parameter is passed. Test failures are expected until this is rebased to include #131.

@rpauly18 and @hivanov-nrel, this is good to go. This is a simple fix and test for the jonswap_spectrum function. Prior to this addition we were not passing the Hs argument to MHKiT-Python. This fix passes Hs to MHKiT-Python when the number of inputs is 4.


Added MultiRtpDisplay

MultiRtpDisplay is based on Camera1 and Camera2 Multistream. It implements DisplayBase.

Look good, I will merge after test it.
Let me knoe if you have any error or idea to improve it.
About index error and special features of rtsp/rtmp I have plan to do exception for this cases and then release a new version.

I did a fix in this line for rtspSize:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/pull/873/files#diff-16c94abc4e51e45ac019de797047701769b2ebac38ad6079868058f99d75cd34R73
The rest all fine, merged


Rename Authchain to Intchain

Description of change
renamed authchain to Intchain
Links to any relevant issues
fixes issue #195 partly
like discussed in the weekly meeting, everything was renamed but the logic behind it wasnt changed.
Type of change
Add an x to the boxes that are relevant to your changes.

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] Enhancement (a non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Fix

How the change has been tested
Change checklist
Add an x to the boxes that are relevant to your changes.

[X] I have followed the contribution guidelines for this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation

every time I see IntChain I think of a chain of integers....
int is also a bit of a confusing variable name here (thankfully rust doesn't have the keyword int). maybe it would be less confusing to use IntegrationChain and not use the int variable name ?


input type="search" - the (x) button gets cut off in Safari

On an input with type search (e.g.The search box on the Foundation docs page) the padding on the search box partially obscures the (x) button which clears the content of the input (see screenshot)

Also if you have e.g. results=5 on the input element then a magnifying glass is rendered within the left side of the field - this is similarly obscured.
I guess Chrome implements these elements in a different way to Safari because they render fine in chrome.
Doesn't seem to be related to #5533

Looks like it's a webkit issue and the only way to solve it would be to completely remove that padding. I'll close this since thats something we're not going to be able to do. Looked into this for a while and seems like a pretty common issue.

OK thanks for looking :)

There's a bug for this issue on the Webkit bug tracker: https://bugs.webkit.org/show_bug.cgi?id=111843


Generate board/pin setup from user configuration files

Very rough sketch:
[board]
# could house multiple, but a build system would look for the
# one thing it can "run" on
mdbt1.part = "nrf52840qiaaf02242ed"

[[led]]
name = "D2"
color = "red"
drive = { gpio = "mdb1.p1.09", level = "active-high" }

[[sensor]]
part = "BMP280"
drive = { scl = "mdb1.p0.11", sda = "mdb1.p0.12" }

Tools this could also interact with:

KiCAD schematic symbol generation (e.g. kipart)
Nice board pin-outs (e.g. Pinion)
Board search (similar to drive-rs)


Add payment-info line to SignTransaction CheckoutLayout

Resolves #83.
Only problem remaining is how to hide the info-line when the user goes back or cancels the signing. The Keyguard shortly shows the loading animation again before redirecting back to the AccountsManager. In that time, the page is hidden because it is not a CSS target anymore, but the payment-info-line lives outside the page, so is not hidden. And CSS can only be written to affect later elements in the DOM, so the info-line cannot react to a page being hidden (the page comes after the info-line)...
Only possibility I see is instead of relying solely on the CSS target, to also add a loading class or similar to the body or #app element... @Bettelstab?

There are several possibilities how to handle this payment line:

Copy & Paste HTML ;(
Make it a component and add it at the start of each page
Place it after the page and use CSS (order property, #app is flex anyway) to make it appear before the page.
I thought about doing the flex reverse order as well. I don't like it too much as it is unexpected order, but I currently think it's still the cleanest solution.

And I also would agree with making it a component, although it's only needed once. But we'll never know.
I'll refactor it.


Unable to remove package-level annotations

Jurand does not remove annotations placed on whole packages.
For example, given package-info.java file:
@MyAnn
package mypkg;
import other.MyAnn;

Call Jurand like this:
jurand -s -n MyAnn package-info.java
Expected output:
package-info.java:
package mypkg;

Actual output:
package-info.java:
@MyAnn
package mypkg;

Some real-word examples of package-info.java with annotations on package-level:

https://github.com/jhy/jsoup/blob/master/src/main/java/org/jsoup/package-info.java
https://github.com/raphw/byte-buddy/blob/master/byte-buddy-dep/src/main/java/net/bytebuddy/package-info.java
https://github.com/testng-team/testng/blob/master/testng-core/src/test/java/test/ignore/ignorePackage/package-info.java

Reminder that for without -a flag, only imports are removed.
I added tests and looks like your exact case is handled fine.
https://github.com/fedora-java/jurand/commit/84f6867e40c12e796ff675941df91dcc1a600051

In that case the issue can be closed.
There is no manpage for jurand command, only for the RPM macros.
So I referred to macro manpage when running the command, which was a mistake.


Typo in documentation

Here it says session.xtoke instead of session.xtoken. I would file a pull request but you can't do that on github wikis

Changed


[Masthead v2]: Remove the suppression of the L0 menu items when L1 is present

Engineering info:

Innovation Team JIRA Ticket: https://jsw.ibm.com/browse/ADCMS-2538
DPO consulting engineer: N/A

Description

For the launch of the Masthead v2, the team is looking to bring back the menu items within the L0/Masthead when it's being stacked next to the L1 Nav.

Additional information

Overview and scope of the engineering work should be included in the linked epic (#9208)

Design Specs

Desktop - https://www.figma.com/file/35JfN0Sg4ltIIjM7jBDKMk/Navigation?node-id=1970%3A110816
Mobile - https://www.figma.com/file/35JfN0Sg4ltIIjM7jBDKMk/Navigation?node-id=1970%3A111059

Acceptance criteria

[ ] L0/Masthead menu items will be visible next to the L1 Nav.

Notes from the 08/23 "Navigation Stakeholder & Dev Weekly" meeting:

The visibility of the L1 Menu items within the hamburger menu on mobile is not a blocker for the end of the Q3 deadline.
We're going to be following up with a new solution for displaying the L1 Nav on mobile using the accordion behavior that @JaniceChristineM has been working on (see Figma Link). This work will most likely go out as part of phase 2 work, which includes changes in the L1 Nav.
The changes in this PR to remove the suppression of the L0 menu can continue on and be made available.


Color_spiral.py

Hi, I am Abhishek Dongre and have created a python project on color spiral.As you run the program the color spiral starts executing.
Plz accept my pull request and make it valid for hacktoberfest 2022

Please label it as hacktoberfest 2022 so it will be considered for hacktoberfest 2022


Survey fix

Motivation and Context
Restricting input fields to prevent HTML injection
What has changed
Added regex validators to survey editing and creation

How to test?
Local:

pipenv run python run_tests.py
make test

Dev:

Spin up cluster in dev with response-ops-ui image tagged "survey-fix", and port-forward to that on port 8080

Links
https://trello.com/c/ys4n60Jr

Screenshots (if appropriate):

Unit tests added, thanks.


Enable Link-Time Optimization (LTO)

Hi!
I noticed that in the Cargo.toml file Link-Time Optimization (LTO) for the project is not enabled. I suggest switching it on since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance a bit. If you want to read a bit more about LTO, I can recommend starting from this Rustc documentation.
I suggest enabling LTO only for the Release builds so as not to sacrifice the developers' experience while working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional dist or release-lto profile where in addition to regular release optimizations LTO will also be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most performant version of the application. If we enable it on the Cargo profile level, users, who install the application with cargo install will get the LTO-optimized version "automatically". E.g., check cargo-outdated Release profile.
Basically, it can be enabled with the following lines:
[profile.release]
lto = true

I have made quick tests (Fedora 41, Rustc 1.82) by adding lto = true to the Release profile. The binary size reduction is from 15 Mib to 12 Mib.
Also, you might be interested in enabling other optimizations to the Release profile like codegen-units = 1 and other things.
Thank you.

@zamazan4ik Thank you for your suggestion. I've enabled LTO in Cargo.toml. The next release of Paddler will use it.


Playground emojis

A Playground often features Slides, Swings, See-saws, Sand Pits (→ #177), Carousels and other large toys for children. They are points of interest on many maps, but currently there are only emojis for amusement parks or fairs 🎡🎢🎠.

Emoji 14.0 in 2021 added a draft Slide emoji.


rosette diameter

Diameter of rosette at maturity of main axis.
Reported by: dosza
Original Ticket: obo/plant-trait-ontology-to-requests/45

added the term using TermGenie


ICD11foundation x-ref

Added all the ICD11foundation x-ref that were reported in the exact lexical matching file.
File is here: https://raw.githubusercontent.com/monarch-initiative/mondo-ingest/main/src/ontology/lexmatch/unmapped_icd11foundation_lex_exact.tsv

FYI: @matentzn @joeflack4 @twhetzel

@joeflack4 I think it is part of the review. The lex matching is a suggestion, and we rarely realize that there is a proxy merge until the QC checks tell us.
As we move forward, this will happen less often because the ICD11 code will not be suggested anymore (since it is already in Mondo).
The very good thing (even though it is annoying to review-but it is my job :-) ) is that it unveil issues about the orphanet-ICD11 mappings. So it is all fine.

Use OAK to validate mappings rather than rely on waiting for a GH action
https://github.com/INCATools/ontology-access-kit/blob/main/notebooks/Commands/ValidateMappings.ipynb

@cmungall @matentzn @twhetzel If OAK has means to validate illegal proxy matches, shouldn't sssom-py also? I just checked and it did not detect.
I guess we could validate lexmatch files in mondo-ingest, but we'd have to do some refactoring. They're like half robot template / half SSSOM.
@cmungall I finagled the lexmatch file until it passed sssom-py validation, but when I ran runoak validate-mappings on it, I got a not-validation related error:

https://github.com/INCATools/ontology-access-kit/issues/742

@sabrinatoro I am looking over the mondo-edit.obo file, one question is why does MONDO:0009255 have both of these lines:
xref: icd11.foundation:1173858031 {source="MONDO:equivalentTo"}
xref: icd11.foundation:1173858031 {source="Orphanet:79237", source="MONDO:equivalentTo"}

This is correct, I think these lines are duplicated because they were added via the orphanet-icd11 mappings and via the exact lexical matching.
I agree, these lines should be merged. I wonder if a normalization step would do the trick...

I don't know if NORM will do that, but worth a try. If not, my next try would be a SPARQL query to find these and manually remove.

Definitely normalise this it will do the trick

+1 on most definitely adding 1 or more orcids

there seem to be a few xRefs that are mis-mapped based on the ICD11 structure

This is a very complex issue. We treat structure merely as evidence for the correctness of a mapping. The goal of determining exactness is to determine "intent" (whether or not explicitly reflected in the structure of the ontology) and approach mapping from a "practical POV" (nothing is truly an exact match, but if it "appears the same" and pretending it is the same does impact diagnostic tools adversely, we assert it).
I would break out the 85, make a new PR for these and otherwise merge it, but I understand from slack that you prefer to be more careful.


Language agnostic near-operation-file preset helpers

I've refactored near-operation-file to extract the fragment resolution logic into fragment-resolver.ts and the main document processing logic into resolve-document-imports.ts, which is then re-exported as resolveDocumentImports for use by other preset builders, thus satisfying #3091.
This cuts the main plugin logic down to the following, aside from prep and post processing:
function resolveImportPath(baseOutputDir: string, relativeOutputPath: string, sourcePath: string) {
  const shouldAbsolute = !sourcePath.startsWith('~');
  if (shouldAbsolute) {
    const absGeneratedFilePath = resolve(baseDir, relativeOutputPath);
    const absImportFilePath = resolve(baseDir, sourcePath);
    return resolveRelativeImport(absGeneratedFilePath, absImportFilePath);
  } else {
    return sourcePath.replace(`~`, '');
  }
}

const sources = resolveDocumentImports(options, schemaObject, {
  generateFilePath(filePath: string) {
    const newFilePath = defineFilepathSubfolder(filePath, folder);
    return appendExtensionToFilePath(newFilePath, extension);
  },
  fragmentSuffix: 'Fragment',
  generateImportStatement({ relativeOutputPath, importSource, baseOutputDir }) {
    const importPath = resolveImportPath(baseOutputDir, relativeOutputPath, importSource.path);
    const importNames = importSource.names && importSource.names.length ? `{ ${importSource.names} }` : '*';
    const importAlias = importSource.namespace ? ` as ${importSource.namespace}` : '';
    return `import ${importNames}${importAlias} from '${importPath}';${importAlias ? '\n' : ''}`;
  },

  schemaTypesSource: {
    path: shouldAbsolute ? join(options.baseOutputDir, baseTypesPath) : baseTypesPath,
    namespace: importTypesNamespace,
  },
});

Old Description
This is a first pass at #3091, but I'm not sure it's the right way to go. Really, it might be better to export a function that takes the arguments I added to the config here, to make it easier for plugin publishers to implement their own preset. That approach:

would actually be better for my use case
would allow for the usage of function arguments instead of the templates

I still like the idea of exposing the template strings in the end user config, as even with the "preset wrapper" approach end users might want to customize the import statements. However, the fact that we're already interpolating environment variables makes the API awkward (didn't this was the case at first)

@dotansimha could you take a look at this when you get the chance? I'm already using it in the latest https://github.com/micimize/graphql-to-dart beta

Looks great, thanks @micimize . can you please revert the version bump? Then I'll merge this.

@dotansimha reverted the version bump 👍


[2pts] Implement methods

Implement methods:

[x] add_item method in the Genre class

should take an instance of the Item class as an input
[x] should add the input item to the collection of items
[x] should add self as a property of the item object (by using the correct setter from the item object)

[x] can_be_archived?() in the MusicAlbum class

[x] should override the method from the parent class
[x] should return true if parent's method returns true AND if on_spotify equals true
[x] otherwise, it should return false

The above methods were implemented during class creation in both  MusicAlbum and Genre classes. It can be closed after the final review of both classes.

Yes.
We need to only implement things required for the the given task.
In this case I think these two issues could be merged into one issue. But not a big issue. We are good to go.
So I think this issue can be closed now.
Thanks


Update profile page layout

Change from a tab layout where you can only see one aspect a time to a vertical series of modules that each summarize and preview aspects. Design below is really rough.
The current layout is clean, but you just have to click through all the tabs to learn what this person is doing, and there's a lot of focus on the follow list. I think it's better to highlight more diverse activity right off the bat.

This affects a lot of things and also requires different sub-pages to people can click through to the individual aspects (e.g. see all badges, lists, etc), and then even further down (single list, etc).

This is done now. Profiles that only follow others but have no other activity are a bit short, but other profiles look nicer and are more interesting - really depends on how active the user is. I hope it encourages people to do more different activities.
There's some follow-up to do, I'll create issues for those:

Allow for clicking into individual lists to see their "contents"
Use a URL structure for profile sub-sections (/reports, /badges...). Tried it briefly, but Nuxt didn't play well, as it kept refreshing the top part of the profile when clicking around instead of keeping it static (even using layouts). Don't think this is super important though


CMake integration

work in progress
The objective is to create and install RobotDartConfig.cmake from waf, so that it is easy to call RobotDart from CMake projects (and still compile/install with waf as this is our prefered tool, which will handle options, etc.).
for now
I managed to use the INTERFACE IMPORTED system to create a working RobotDartConfig.
now
Copy information from dart to this (easy).

@jbmouret Nice! How can I try to see how it works?

You can try.
A `./waf install'
then:
export CMAKE_PREFIX_PATH=/Users/jmouret/lib/cmake/ (where you installed)
and you can try the example.

Apparently my last commit added many files that should be removed. I will clean up.

Apparently my last commit added many files that should be removed. I will clean up.

Indeed. It'd be better to revert the commit and only add the files that you want/need. Otherwise, I think it'll pollute the history quite a lot..

You can try.
A `./waf install'
then:
export CMAKE_PREFIX_PATH=/Users/jmouret/lib/cmake/ (where you installed)
and you can try the example.

It works after a small typo fix (RobotDartConfig.cmake->RobotDARTConfig.cmake) and only the no-graphics version.

I polluted the history (sorry) because it was already pushed... If you know how to revert the commit and put the files, I do not remember how to do this.
For the graphics version, I have this issue:
-- Found DART: /usr/local/include  found components: dart utils utils-urdf collision-bullet collision-ode dart
CMake Warning at /usr/local/share/cmake/Magnum/FindMagnum.cmake:646 (find_package):
  By not providing "FindGLFW.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "GLFW", but
  CMake did not find one.

  Could not find a package configuration file provided by "GLFW" with any of
  the following names:

    GLFWConfig.cmake
    glfw-config.cmake

  Add the installation prefix of "GLFW" to CMAKE_PREFIX_PATH or set
  "GLFW_DIR" to a directory containing one of the above files.  If "GLFW"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/local/share/cmake/Magnum/MagnumConfig.cmake:26 (include)
  /usr/local/Cellar/cmake/3.17.2/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
  /Users/jmouret/lib/cmake/RobotDART/RobotDARTConfig.cmake:32 (find_dependency)
  CMakeLists.txt:8 (find_package)

-- Found Magnum: /usr/local/include  found components: Trade GL MeshTools Primitives Shaders SceneGraph GlfwApplication WindowlessCglApplication
-- Found Magnum: /usr/local/include  found components: Trade GL SceneGraph Primitives MeshTools
-- Found DART: /usr/local/include (Required is at least version "6.0.0") found components: dart
-- Found Magnum: /usr/local/include  found components: Trade AnyImageImporter
-- Configuring done
CMake Error at CMakeLists.txt:17 (add_executable):
  Target "robot_dart_example_graphics" links to target "GLFW::GLFW" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

@costashatz do you have the same?

I guess this might be related to: https://github.com/mosra/magnum/pull/194/files

I polluted the history (sorry) because it was already pushed... If you know how to revert the commit and put the files, I do not remember how to do this.

I remember how, but now it'll be much more complicated. The pollution is not that big in the end :)

@costashatz do you have the same?

Yes.. This is a known issue with GLFW (they have a very stupid CMake and they do not want to change it). I remember that Magnum did something for this. Let me try to find the solution..

@jbmouret I fixed the issue with GLFW configuration.. Now I am getting linking errors with Magnum. Which makes a bit sense since: 1) we are mixing static and shared libraries together (I have to check how to say to CMake that they are static), and 2) I am not sure Magnum is exporting the targets as you are using them.

@jbmouret it should be fixed now. There were 2 issues: 1) the order of the libraries for linking matters (at least in gcc), and 2) you were not getting the proper variable for Magnum's libraries from waf (thus, they were a few libraries missing). It should be working now..

In my Ubuntu setup, I am getting the following:
CMake Error at /usr/share/cmake-3.10/Modules/CMakeFindDependencyMacro.cmake:48 (find_package):
  Could not find a package configuration file provided by "Boost" with any of
  the following names:

    BoostConfig.cmake
    boost-config.cmake

  Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
  "Boost_DIR" to a directory containing one of the above files.  If "Boost"
  provides a separate development package or SDK, be sure it has been
  installed

It works for me on my mac! (it compiles and run, except that there my example does not have access to the urdf).
I am quite sure that we are using targets in the correct ways. Do you have the BoostConfig.cmake somewhere?
/usr/local/Cellar/boost/1.72.0_1/lib/cmake/Boost-1.72.0/BoostConfig.cmake
/usr/local/Cellar/boost/1.72.0_1/lib/cmake/Boost-1.72.0/BoostConfigVersion.cmake

from brew.
Do you use the system boost or a special one?

Do you use the system boost or a special one?

The system boost. But the weird thing is the following:

There's no BoostConfig.cmake anywhere installed
FindBoost.cmake is available here: /usr/local/share/dart/cmake/DARTFindBoost.cmake and /usr/share/cmake-3.10/Modules/FindBoost.cmake

I am not sure if I have installed dev-all from Boost, but do we need this?
In my arch-linux system, everything was working properly for Boost.

According to the cmake documentation:"If Boost was built using the boost-cmake project or from Boost 1.70.0 on it provides a package configuration file for use with find_package’s config mode. "
https://cmake.org/cmake/help/v3.15/module/FindBoost.html
As this is for all boost (and not a specific component), this might be in some 'dev-all' package, but this would be surprising. This file (BoostConfig.cmake) is in no Ubuntu package?

This file (BoostConfig.cmake) is in no Ubuntu package?

I do not think that I installed dev-all. I think I only installed a few packages. Let me check when I find time.

from Boost 1.70.0

In Ubuntu 18.04, we have Boost 1.65.1 (in arch-linux, I have 1.72.0).. This might explain the issue. We might need to provide a configuration file if version of Boost is less than 1.70.0..
By the way, I think we should enable components for RobotDART. One for the Simu and one for GUI/Magnum. I do not like this CMake variable: maybe robot_dart is built with Magnum, but I do not want it. Why would CMake try to find it?

Yes, this is certainly because you are using an old boost...
I will have a look later at the components. It should not be hard.

Yes, this is certainly because you are using an old boost...

This is Ubuntu!

(it compiles and run, except that there my example does not have access to the urdf).

This is because I am assuming that there files are located next to the executable. We can fix that.

@jbmouret I fixed the issue with Boost easily as I realized that we only use Boost for unit tests (no reason for the user to use them in a client app) and in DART. DART finds on each own Boost, and thus I completely removed it and it works nicely both in archlinux and Ubuntu.
I, then, found another bug in Ubuntu and older versions of CMake that they were ignoring INTERFACE_LINK_DIRECTORIES, so I fixed that also.
Finally, I cleaned-up a few things and passed the flags from waf configuration to CMake.
Let me know if the latest commit works for you also. Btw, I like now the components! :smile:

It works for me! We should select an example that works (fixing the paths of the urdf... or not using any urdf).
I am glad you like the component.

@jbmouret I tested on my setups and it is working like a charm.. I will merge later today!


use 'Clear' instead of  'Drop' in rpn.cog

So you can stop the program without an error telling you have some n objects still on the stack.

The error is because an item is left on the stack if Error? is set. I've fixed this with a Drop in an if-else branch. This has the advantage of not having an arbitrary number of items on the stack, which could be considered a memory leak.

It shouldn't leak items onto the stack anymore, so this issue doesn't apply


Is any plan to develop 'utf8_slice_charunits' like existed 'utf8_slice_codeunits'

STOP! Are you reporting a bug, a possible bug, or requesting a
feature? If so, please report under the ARROW project on the ASF JIRA
server https://issues.apache.org/jira/browse/ARROW. This JIRA server
is free to use and open to the public, but you must create an account
if it is your first time.
See our contribution guidelines for more information:
http://arrow.apache.org/docs/developers/contributing.html
We have GitHub issues available as a way for new contributors and
passers-by who are unfamiliar with Apache Software Foundation projects
to ask questions and interact with the project. Do not be surprised if
the first response is to open a JIRA issue or to write an e-mail to
one of the public mailing lists:

Development discussions<EMAIL_ADDRESS>(first subscribe by
sending an e-mail to dev-subscribe@arrow.apache.org).
User discussions<EMAIL_ADDRESS>(first subscribe by
sending an e-mail to user-subscribe@arrow.apache.org).

Thank you!

like utf8_slice_codeunits, but start/end/step is in byte unit

Hi @chenbaggio, could you expand on what you refer to as a "byte unit". If you refer to char (signed integral), you should be able to use it (via casting) with the current int64_t type for start/end/step. Probably, I am misunderstanding your request, so could you give an example.
Also, are there other language implementations that have a similar operation?

Dears:
here, I can give one example to descirbe why need a function to extract binary in byte unit
             In distribute database, data has distribute policy and relatived hash algorithm for different data type,
              here we just discuss string-like and binary type, the hash algorithm need detach string-like or binary
              in bytes to calculating, for example , take 1-4 byte cast to integer and shift-left 16 bits, then take 5-6byte cast to
               integer and the result from last step, and so on, the  'utf8_slice_codeunits' function can partly meet the require if all
              are ascii,  but if the string-like contain chinese, one chinese may occupied three bytes,  start 1 to end 3, three utf8 character
              may take nine bytes, but it not meet the hash algorithm, it only need 3 bytes, so if provide a function but not cast, the same
              function arguments like 'utf8_slice_codeunits', it may called 'binary_slice_byteunit'

At 2022-07-27 11:23:12, "Eduardo Ponce Mojica" @.***> wrote:
Hi @chenbaggio, could you expand on what you refer to as a "byte unit". If you refer to char (signed integral), you should be able to use it (via casting) with the current int64_t type for start/end/step. Probably, I am misunderstanding your request, so could you give an example.
Also, are there other language implementations that have a similar operation?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks for explanation. I consider it is a reasonable compute function to add given that some string functions come in multiple variants (ascii, utf8, binary). For example, currently there are related functions binary_replace_slice and utf8_replace_slice that support both the byte-oriented and codeunit-oriented forms of data.
I searched in JIRA issues and did not find one related to this request. @chenbaggio would you be willing to open a JIRA issue to add this compute function and submit a PR? If not, let us know and we will help with this request.

Dears :
sorry, it seems I can not longin JIRA, not the user for it, would you help to do it or suggest me how to register,thank you!
At 2022-07-27 23:42:02, "Eduardo Ponce Mojica" @.***> wrote:
Thanks for explanation. I consider it is a reasonable compute function to add given that some string functions come in multiple variants (ascii, utf8, binary). For example, currently there are related functions binary_replace_slice and utf8_replace_slice that support both the byte-oriented and codeunit-oriented forms of data.
I searched in JIRA issues and did not find one related to this request. @chenbaggio would you be willing to open a JIRA issue to add this compute function and submit a PR? If not, let us know and we will help with this request.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
 Here is the documentation guide for creating Apache Arrow issues.

thank you for your help, created the issue ARROW-17301, but the assignee is still blank, please help finish it, thank you!
At 2022-08-04 11:26:27, "hero" @.***> wrote:
Dears :
sorry, it seems I can not longin JIRA, not the user for it, would you help to do it or suggest me how to register,thank you!
At 2022-07-27 23:42:02, "Eduardo Ponce Mojica" @.***> wrote:
Thanks for explanation. I consider it is a reasonable compute function to add given that some string functions come in multiple variants (ascii, utf8, binary). For example, currently there are related functions binary_replace_slice and utf8_replace_slice that support both the byte-oriented and codeunit-oriented forms of data.
I searched in JIRA issues and did not find one related to this request. @chenbaggio would you be willing to open a JIRA issue to add this compute function and submit a PR? If not, let us know and we will help with this request.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @chenbaggio, it seems that a simple binary slice function may not be the solution for your use case. Currently, Arrow only contains logical shifts, so no arithmetic nor rotational shifts. If you consider that a rotational shift will suffice for your hash algorithm, please submit a ticket for this other compute function.


configure.ac: supress OpenSSL deprecation warnings on OS X

I'm not familiar with autoconf so there may be a more correct way to do this.

I normally do this like this:
https://github.com/digitalbitbox/dbb-app/blob/fd5dc5568c9f49271093faeab55d90198be41db5/src/libbitpay-wallet-client/bpwalletclient.cpp#L36
Although not sure if my approach makes more sense.

The advantage of that approach is that we could potentially wrap just the openssl includes with a push/pop and still get deprecation warnings from other headers.  But it's a lot of pragmas to add.
How about this kind of thing:
https://github.com/dtebbs/picocoin/commit/6d614743c78f725ee57609b7e3e47d2a4a20ef93
Use openssl from brew if available, otherwise fall back to the (noisy) default version?

This fixes all of the OS X compile warnings for me.

Coverage increased (+0.02%) to 75.024% when pulling 22f8fc89dda661d043abc70fbd9e6221e87500ca on dtebbs:osx_warnings into c382202b25244025dfb5713a8ff7d1d8f4a531b6 on jgarzik:master.

Re-pushed based on @jgarzik comments.
Also, instead of globally disabling deprecation warnings I switched the build to favor the brew version of openssl, which seems to produce no warnings.  Neither solution is ideal, but if we eventually move away from openssl we can remove the workaround.


support pip install

This is to make the repo pip installable, locally or from the github.

[x] build wheel from source code
[x] pip install . from source code
[x] pip install frmo the git repo

changed the setup.py to use setuptools so you can build wheel from the repo
$ python setup.py bdist_wheel
/Users/robertwen/virtualenv/v1/lib/python2.7/site-packages/setuptools/dist.py:364: UserWarning: Normalizing '0.03' to '0.3'
  normalized_version,
running bdist_wheel
running build
running build_ext
skipping './python-lapjv/python_lapjv.cpp' Cython extension (up-to-date)
installing to build/bdist.macosx-10.11-x86_64/wheel
running install
running install_lib
creating build/bdist.macosx-10.11-x86_64/wheel
copying build/lib.macosx-10.11-x86_64-2.7/lapjv.so -> build/bdist.macosx-10.11-x86_64/wheel
running install_egg_info
running egg_info
writing python_lapjv.egg-info/PKG-INFO
writing top-level names to python_lapjv.egg-info/top_level.txt
writing dependency_links to python_lapjv.egg-info/dependency_links.txt
reading manifest file 'python_lapjv.egg-info/SOURCES.txt'
writing manifest file 'python_lapjv.egg-info/SOURCES.txt'
Copying python_lapjv.egg-info to build/bdist.macosx-10.11-x86_64/wheel/python_lapjv-0.3-py2.7.egg-info
running install_scripts
creating build/bdist.macosx-10.11-x86_64/wheel/python_lapjv-0.3.dist-info/WHEEL

moved the setup.py to the top repo level so you can pip install from git
$ pip install git+git://github.com/robertwenquan/lapjv.git

Hi Robert,
the patch works for me under Debian, but I have some compilation issues under MacOS. I should have some time later this week, so I'll try to patch it.
Thanks for contributing!
Best,
Tomas

Hi Tomas,
Glad to help.
The mac failure may not be contributed by this patch. Actually the python setup.py build failed on some of my colleagues mac with Xcode 7.3.1 while it works fine with Xcode 7.3
Let me know if I can help with troubleshooting the platform issue as we have a variety of os versions company wise.
Best,
Robert

I finally got some time to work on this. The current version seems to be ok on both linux and mac that I have access to. Could you give it a try on some of your systems?


CPP: Clean up PotentialBufferOverflow.ql, PotentiallyDangerousFunction.ql

Move the logic about gets from PotentialBufferOverflow.ql to PotentiallyDangerousFunction.ql.  One goal is to have LGTM report uses of gets, which would've caught one of the issues in https://github.com/gsingh93/lgtm-test/blob/master/test.cpp.  Also, this cleans up the identity of PotentialBufferOverflow.ql significantly.
Before:

PotentialBufferOverflow.ql (not on LGTM, CWE-242) - any use of gets, overflowing use of sprintf
PotentiallyDangerousFunction.ql (on LGTM, CWE-676) - any use of gmtime
( and DangerousUseOfCin.ql (on LGTM, CWE-242 and CWE-676) - potentially overflowing use of cin )

After:

PotentialBufferOverflow.ql (not on LGTM, CWE-676) - overflowing use of sprintf
PotentiallyDangerousFunction.ql (on LGTM, CWE-242) - any use of gmtime, any use of gets
( and DangerousUseOfCin.ql (on LGTM, CWE-676) - potentially overflowing use of cin )

Relevant CWEs:

CWE-242: Use of Inherently Dangerous Function (https://cwe.mitre.org/data/definitions/242.html)
- the example is gets; the samate tests are all about gets
CWE-676: Use of Potentially Dangerous Function (https://cwe.mitre.org/data/definitions/676.html)
- the example is strcpy; the samate tests are all about cin

16:32:54 Some tests failed!
16:32:54     semmlecode-cpp-tests/security-tests/CWE-242/CWE/examples/PotentialBufferOverflow.qlref: Test failure (Expected output does not match)
16:32:54     ql/cpp/ql/test/query-tests/Security/CWE/CWE-242/semmle/tests/PotentialBufferOverflow.qlref: Test failure (Expected output does not match)

semmlecode-cpp-tests/security-tests/CWE-242/CWE/examples/PotentialBufferOverflow.qlref: Test failure (Expected output does not match)

Fixed by adding a change to https://git.semmle.com/Semmle/code/pull/30297.

ql/cpp/ql/test/query-tests/Security/CWE/CWE-242/semmle/tests/PotentialBufferOverflow.qlref: Test failure (Expected output does not match)

Fixed here.


Excavator enchant not working

Just added excavator III to a netherite pick and it doesn't increase reach whatsoever. Am I missing something?

What version are you using? If you're on mod v1.1.7 for Minecraft version 1.20, then it's known that Excavator doesn't work properly on that version (the dependency hadn't been updated at the time but I still wanted to push out an update). So in that case update to the latest version, where Excavator does work when you're holding the pickaxe.

I am on version 1.1.10 for minecraft 1.20.1, all other enchantments work properly. I even upgraded to mod version 1.1.11 but to no avail.

What specific tool are you using (Diamond Pickaxe?) and what other enchantments are you using on the tool? Thank you!

Hi again, I am using a netherite pickaxe. On the pickaxe itself i only have excavator 3 and nothing else, but I do have life steal 3 on my sword and it works. I am on singleplayer.

Nevermind! Did a new minecraft installation and reinstalled the mod and it works now.

Great! It might have been something off with the config since I had to disable the enchantment in one version and then reenable it. Glad it's working


Agregando respuesta

con este PR agrego clase repuesta con sus respectivos test

Codecov Report

Merging #26 into V1.0 will decrease coverage by 3.66%.
The diff coverage is 73.33%.

@@             Coverage Diff              @@
##               V1.0      #26      +/-   ##
============================================
- Coverage     94.36%   90.69%   -3.67%
- Complexity       34       38       +4
============================================
  Files            11       12       +1
  Lines            71       86      +15
  Branches          2        2
============================================
+ Hits             67       78      +11
- Misses            4        8       +4

Impacted Files
Coverage Δ
Complexity Δ

...va/edu/fiuba/algo3/modelo/Respuesta/Respuesta.java
73.33% <73.33%> (ø)
4.00 <4.00> (?)

Continue to review full report at Codecov.

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


Contributing

Hello!
I hope you all are well. Our company is looking to adopt this library. Though everything appears to he maintained here, if we run into anything we feel is missing, what would your process look like in terms of process and timelines to merge a PR into main.
Thanks! And looking forward to diving into your library!
Jake

Hey, @wayjake  responded to your email 😉


[BUG]No login authentication by Container deployment in Azure with persistent storage

Describe the bug
No login authentication by Container deployment in Azure with persistent storage
To Reproduce
use the method in flowise docs for Azure
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Flow
If applicable, add exported flow in order to help replicating the problem.
Setup

Installation [e.g. docker, npx flowise start, yarn start]
Flowise Version [e.g. 1.2.11]
OS: [e.g. macOS, Windows, Linux]
Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

It used to have that by previous installation

have you set the env variables - FLOWISE_USERNAME and FLOWISE_PASSWORD? https://docs.flowiseai.com/deployment/azure
no changes were made there, it should works as before

have you set the env variables - FLOWISE_USERNAME and FLOWISE_PASSWORD? https://docs.flowiseai.com/deployment/azure no changes were made there, it should works as before

yes, here is the output:
{
"confidentialComputeProperties": null,
"containers": [
{
"command": [
"/bin/sh",
"-c",
"flowise start"
],
"environmentVariables": [
{
"name": "FLOWISEUSERNAME",
"secureValue": null,
"value": "fsafaf"
},
{
"name": "FLOWISEPASSWORD",
"secureValue": null,
"value": "afsafaf"
},
{
"name": "DATABASEPATH",
"secureValue": null,
"value": "/opt/flowise/.flowise"
},
{
"name": "APIKEYPATH",
"secureValue": null,
"value": "/opt/flowise/.flowise"
},
{
"name": "SECRETKEYPATH",
"secureValue": null,
"value": "/opt/flowise/.flowise"
},
{
"name": "LOGPATH",
"secureValue": null,
"value": "/opt/flowise/.flowise/logs"
}
],
"image": "flowiseai/flowise",
"instanceView": {
"currentState": {
"detailStatus": "",
"exitCode": null,
"finishTime": null,
"startTime": "2023-11-22T05:13:04.660000+00:00",
"state": "Running"
},
"events": [
{
"count": 1,
"firstTimestamp": "2023-11-22T05:11:40+00:00",
"lastTimestamp": "2023-11-22T05:11:40+00:00",
"message": "pulling image "flowiseai/flowise@sha256:36af2ea41f09d4a69b76babb43e88f582eda82d99235896ad3d9b17519ce860b"",
"name": "Pulling",
"type": "Normal"
},
{
"count": 1,
"firstTimestamp": "2023-11-22T05:12:48+00:00",
"lastTimestamp": "2023-11-22T05:12:48+00:00",
"message": "Successfully pulled image "flowiseai/flowise@sha256:36af2ea41f09d4a69b76babb43e88f582eda82d99235896ad3d9b17519ce860b"",
"name": "Pulled",
"type": "Normal"
},
{
"count": 1,
"firstTimestamp": "2023-11-22T05:13:04+00:00",
"lastTimestamp": "2023-11-22T05:13:04+00:00",
"message": "Started container",
"name": "Started",
"type": "Normal"
}
],
"previousState": null,
"restartCount": 0
},
"livenessProbe": null,
"name": "affassfa",
"ports": [
{
"port": 80,
"protocol": "TCP"
},
{
"port": 3000,
"protocol": "TCP"
}
],
"readinessProbe": null,
"resources": {
"limits": null,
"requests": {
"cpu": 1.0,
"gpu": null,
"memoryInGb": 1.5
}
},
"securityContext": null,
"volumeMounts": [
{
"mountPath": "/opt/flowise/.flowise",
"name": "azurefile",
"readOnly": null
}
]
}
],
"diagnostics": null,
"dnsConfig": null,
"encryptionProperties": null,
"extensions": null,
"id": "/subscriptions/fc69bb3a-a652-4352-a03a-942fc7651a81/resourceGroups/rg-linseasia/providers/Microsoft.ContainerInstance/containerGroups/flowiseproduction",
"identity": null,
"imageRegistryCredentials": null,
"initContainers": [],
"instanceView": {
"events": [
{
"count": 1,
"firstTimestamp": "2023-11-22T05:13:02.869000+00:00",
"lastTimestamp": "2023-11-22T05:13:02.869000+00:00",
"message": "Successfully mounted Azure File Volume.",
"name": "SuccessfulMountAzureFileVolume",
"type": "Normal"
}
],
"state": "Running"
},
"ipAddress": {
"autoGeneratedDomainNameLabelScope": "Unsecure",
"dnsNameLabel": "afafaf",
"fqdn": "afsafs.southeastasia.azurecontainer.io",
"ip": "afafafa",
"ports": [
{
"port": 80,
"protocol": "TCP"
},
{
"port": 3000,
"protocol": "TCP"
}
],
"type": "Public"
},
"location": "southeastasia",
"name": "asfsafa",
"osType": "Linux",
"priority": null,
"provisioningState": "Succeeded",
"resourceGroup": "fasfa",
"restartPolicy": "OnFailure",
"sku": "Standard",
"subnetIds": null,
"tags": {},
"type": "Microsoft.ContainerInstance/containerGroups",
"volumes": [
{
"azureFile": {
"readOnly": null,
"shareName": "fileflowise",
"storageAccountKey": null,
"storageAccountName": "storeflowise"
},
"emptyDir": null,
"gitRepo": null,
"name": "azurefile",
"secret": null
}
],
"zones": null
}

are you missing an underscore? FLOWISE_USERNAME

Just fix it by reinstall with another updated version and it works again. can be closed


BLOCKER: PSSA Errors Need to Be Fixed

Errors from PS script analyzer are causing the tests to fail like this.
This resource module cannot be released until these errors are fixed or suppressed and the tests are passing.

I have submitted a pr to the EditAppVeyorFile for this - the errors are for a sample file that gives an example of how to use the resource so added an ignore for them.

Closed by #25


Counter on polymorphic relationship

How to make counter on polymorphic relationship?

@deniskorobicyn thanks for the anti-pattern link. There are lot of useful information.

any updates on this, would love to have polymorphic capability, as i have used this extensively in my project.

Nothing new from my end, unfortunately.

Hi,
Are there any updates on this yet or newer forks with this capability? I used this gem extensively in a project and now need polymorphic support. Thanks!

No unfortunately not.

#154 is a new(ish) PR for single-level polymorphic counters (I think multi-level may be possible, I just haven't come up with a reasonable test case yet).
After a bit of too-ing and fro-ing I think this is working.
If anyone has a use-case for multi-level polymorphic counters can you add a simplified example here -- it would help motivate a subsequent multi-level polymorphic counter PR.

Closing this as one-level polymorphic relationships are supported now as of version 1.5.0. Thank you @timdiggins for making this happen.


Dart package listed under https://ml-algo.com/ , but no website there

Going to http://ml-algo.com, I get a Namecheap page saying the domain was recently registered.  The https version of that URL is registered at https://pub.dev/publishers/ml-algo.com/packages .  I'd recommend at least setting up a quick one-page website there with a link back to github - it helps with people like me, who try to look into a publisher before using a package off pub.dev :-)

@zathras hi, thank you for the suggestion :) The page is in progress right now


Consider additional context on AS / UMA

In the recently submitted iteration of the Solid-OIDC specfication  there are references made to an Authorization Server that SHOULD implement a UMA 2.0 Grant for OAuth 2.0 Authorization (UMA).
Specifically:
In Authorization Server Discovery:

Authorization Servers SHOULD implement User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization [UMA].

In Obtaining an Access Token:

For Authorization Servers that conform to [UMA], the http://openid.net/specs/openid-connect-core-1_0.html#IDToken profile MUST be supported. This profile MUST be advertised in the uma_profiles_supported metadata of the Authorization Server discovery document User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization § rfc.section.2.
When using the http://openid.net/specs/openid-connect-core-1_0.html#IDToken profile with an UMA-based Authorization Server, the Authorization Server MUST be capable of exchanging a valid Solid-OIDC ID Token § 8.1 DPoP-bound OIDC ID Token for an OAuth 2.0 Access Token.
Note: Clients can push additional claims by requesting an upgraded RPT User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization § rfc.section.3.3.1
Authorization Server MUST pefrom § 9.3 DPoP Validation and § 8.1.1 ID Token Validation

I don't believe any more normative detail needs to be added to the Solid-OIDC specification on this subject - but I do think that non-normative supplementary context should be provided to support adoption by developers of Solid-OIDC implementations and the users of those implementations, possibly in a separate document.
For example, Solid Community Server bundles in an existing OpenID Provider that conforms to Solid-OIDC. It would seem that to be fully conformant they would also need to bundle in an AS that implements UMA. Client-side authentication libraries would similarly need some adjustment. I'm sure an overview detailing these considerations would be useful and welcome.
Consequently, it would helpful to showcase the real benefits of a UMA flow in the primer, separately from a "classic" Solid-OIDC flow. I know that the Primer accurately reflects the changes in the specification, but it does little to demonstrate the benefit of them. A second "robust" flow that showcases those benefits could help motivate implementations to fully support this functionality.

I think a part of this issue is covered by specifying/clarifying conformances classes - in issue https://github.com/solid/solid-oidc/issues/20 .