Chinese Display Error, unreadable code, how ?

pg = Spinner('中文')
pg.finish()

Seems to work for me. Can you try this example and let me know if it works?
from progress.spinner import Spinner
import time

pg = Spinner('中文')
for i in range(20):
    time.sleep(0.1)
    pg.next()
pg.finish()

I am so sorry for no replay for a long time,  thanks for you reply.  I have tested the code above, the error is still on.

This has nothing to do with the progress module. The python parser cannot parse your test.py file because it has Non-ASCII characters inside (namely '中文') and there is no encoding declared. Try adding something like this:
# -*- coding: utf-8 -*-

in the beginning of the file. Check PEP 263 (https://www.python.org/dev/peps/pep-0263/) for more info.

I add the coding, but the output is unreadable code.

I have no experience with Windows and I don't know if your file's encoding is actually UFT-8 but if I had to guess about your problem I would say that the software is using ANSI escape characters, that from what I read here: https://en.wikipedia.org/wiki/ANSI_escape_code are not working on Windows:

Although hardware text terminals have become increasingly rare in the 21st century, the relevance of the ANSI standard persists because most terminal emulators interpret at least some of the ANSI escape sequences in the output text. One notable exception was the Win32 console component of Microsoft Windows before Windows 10 update TH2.

Maybe check this thread: http://stackoverflow.com/questions/16755142/how-to-make-win32-console-recognize-ansi-vt100-escape-sequences


Adding Placeholder Logout Button Functionality

Clicking on the logout button should probably fire a redux action / reducer so that we can clear the stored user information in the future and redirect the user to the login page.  This work involves making some redux actions which can be dispatched when clicking the logout button to redirect the user to the login page.

I'll take this one


[Bug] Analytics URL not applying correctly

Bug Report
Describe the bug
Code Example:
<CldImage
	width="600"
	height="600"
	src="images/turtle"
	alt="turtle"
	overlays={[{
		publicId: `images/earth`,
		position: {
			x: 10,
			y: 10,
			gravity: 'north_west',
		},
		effects: [
			{
				crop: 'fill',
				gravity: 'auto',
				width: 200,
				height: 200
			}
		]
	}]}
/>

Resulting URL:
https://res.cloudinary.com/colbycloud-next-cloudinary/image/upload/e_background_removal/c_limit,w_600/e_tint:equalize:80:blue:blueviolet/u_images:earth,c_fill,w_1.0,h_1.0,fl_relative/fl_layer_apply,fl_no_overflow/f_auto/q_auto/v1/images/turtle?_a=E
The analytics parameter is not applying correctly:
_a=E

~I suspect the issue is that you didn't update the url loader package when applying the updated paramters:~
		"@cloudinary-util/url-loader": "3.5.1",

Thinking updating taht to latest will fix it
seems like thast not the only issue

im pretty confused as to why this isn't working, ive been trying to debug... it seems like everything is right

okay i figured it out there aer 2 issues
passing in a non "numerical" semver value 1.0.0-beta.9 breaks it
passing in a 2-digit value like 3.58.0 breaks it
the first one doesnt matter in dev most, but the 2nd one is definitely a bug with the URL Gen library if im not mistaken
flagging it there

okay - for the techVersion apparently only accepts a minor range of 1-10
so im thinking maybe what we need to do is just limit the techVersion to major
can just use something like this:
`${SVELTE_VERSION.split('.')[0]}.0.0`


Fix network nicknames

Explanation

NetworkClientConfiguration does not have the required information to make switch ethereum chaini word properly. The details required are actually inside of NetworkConfigurations, or if the network is an infura one, we fall back to using the networkClientConfiguration.
References

Changelog

@metamask/queued-request-controller

FIXED: NetworkConfigurations wiill be used in place of NetworkClientConfgurations when possible.

Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

@metamaskbot publish-preview

@metamaskbot publish-preview


Created Fibonacci sequence demo

Created a new demo for the Fibonacci sequence
Demonstrates using PyBryt w/ multiple references, providing helpful hints, checking time complexity.
Also includes some updates to functionality including not tracking annotations inside the time complexity context manager and updating the regex using in tracing to accept slices and attributes in assignment statements.

Codecov Report

Merging #56 (33ff1bc) into main (7be7a63) will decrease coverage by 0.36%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##             main      #56      +/-   ##
==========================================
- Coverage   95.05%   94.69%   -0.37%
==========================================
  Files          24       24
  Lines        1294     1300       +6
==========================================
+ Hits         1230     1231       +1
- Misses         64       69       +5

Impacted Files
Coverage Δ

pybryt/annotations/annotation.py
99.21% <66.66%> (-0.79%)
:arrow_down:

pybryt/annotations/complexity/complexities.py
93.54% <88.88%> (-6.46%)
:arrow_down:

pybryt/execution/tracing.py
100.00% <100.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 7be7a63...33ff1bc. Read the comment docs.


Update to OpenWeatherMap API v3

The app currently uses v2.5.
See https://openweathermap.org/api/one-call-3 for the new data shape

Upon further investigation, I learned this is a paid upgrade.


'yarn' is not recognized as an internal or external command

Hello,
While running npm run build task, I get an error the following error
'yarn' is not recognized as an internal or external command
The problem is that the prebuild task(which is called before the build task) has a clean  task in it which uses yarn --version command. As my machine didnt have yarn installed I was unable to build the project.
Although the documentation mentions that yarn is optional, I could only build the project after running the following command
npm install yarn -g
So is yarn mandatory or is it some bug ? Please suggest what should I do.
Thanks

oh, good point. I will fix this.

Fixed in the develop branch, many thanks for reporting!!


About the data format

What is the required data format for the code? Could you please provide any examples or documentation?
Thanks for your help!

We have uploaded the training data of OREO with Qwen2.5-Math-1.5B here: https://huggingface.co/datasets/jwhj/OREO-Qwen2.5-Math-1.5B-Train.

Hello, thank you for sharing the excellent document.
Is this dataset the one to be specified as --train_file for training Oreo?
Also, regarding data collection for Oreo, it is mentioned that both Oreo
and SFT are required. Could you please explain in detail what kind of data
is needed?
best, kazuya
2024年12月31日(火) 19:02 jwhj @.***>:

We have uploaded the training data of OREO with Qwen2.5-Math-1.5B here:
https://huggingface.co/datasets/jwhj/OREO-Qwen2.5-Math-1.5B-Train.
—
Reply to this email directly, view it on GitHub
https://github.com/jwhj/OREO/issues/3#issuecomment-2566305372, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGDRG4ZSDJEIDBUDJ6NIRD2IJTS3AVCNFSM6AAAAABULWED6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGMYDKMZXGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


little fix OPStackProver.sol

The error says the block should have 16 fields, but the condition checks for 15, which might be a typo. Fixing the condition matches it with the error.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for jackchuma @ 2024-11-21 21:27:56 UTC
User failed mfa authentication, see go/mfa-help

Addressed in a separate PR


Minecraft Authentication Error An internal server error occured

im getting this error when i try to link my  patreon

I first click the connect button

then the allow button

and then this shows up

Has since been fixed


Option to generate getter and setter methods for everything; setters should update both objects.

Clearly can see it will be needed as I do the validation I need to do given there aren't validator callbacks.   Specifically, I'm having to add this code to SAMI that should be at most one simple call:
  if config.defaultCmd.isSome() and not config.defaultCmd in allowedCmds:
    warn(fmt"Default command {config.defaultCmd} not recognized (ignored)")

    # This dance needs to be automated by con4m.  Note that we are
    # only making a copy of the entry here, so after we edit we need
    # to re-set it.
    var entry = ctxSamiConf.st.entries["default_command"]
    entry.value = none(Box)
    ctxSamiConf.st.entries = entry
    config.defaultCmd = none(string)

  if not config.logLevel in validLogLevels:
    warn(fmt"Log level {config.logLevel} not recognized. Defaulting to 'warn'")

    var entry = ctxSamiConf.st.entries["log_level"]
    entry.value = some(Box("warn"))
    ctxSamiConf.st.entries = entry
    config.logLevel = "warn"


ci: Push Sonar scan results when pushing to main

Closes #2042
Description
Start pushing the results of Sonar scan for projects that implement the task sonar to SonarCloud.
New OC image service SonarCloud project: https://sonarcloud.io/project/overview?id=openchallenges-image-service
Changelog

Update the Sonar config of OC image service to push to its new project
Add step to the CI workflow to generate and push the results of Sonar scans
Pass the environment variables SONAR_TOKEN to the dev container

Notes

note
This PR modifies devcontainer.json, which will prompt users to rebuild their dev container.

How to scan a Sage Monorepo project and publish the results with Sonar?

Ask @tschaffter to create a corresponding projects on SonarCloud.io
Search Sage Monorepo for a project that already implement the task sonar and that use the same programming language as your project.

If you found at least one project, use it as example.
If no such project exists, contact @tschaffter for help to create the task sonar

Preview
https://sonarcloud.io/project/overview?id=openchallenges-image-service

Badges

Cc

Schematic: @andrewelamb
Agora: @sagely1
Synapse (API client): @thomasyu888

Moving ahead to test that the CI workflow can indeed push scan results when pushing to the branch main.


BC issue with sortBy "isRefined"

I have implementations where:
sortBy: 'isRefined'
Previously this would make active refinements go to the top of the list.
Now this is no longer the case and I have to use sortBy: 'isRefined:desc'
Any clue on this?

This feature relies on the Helper. I opened an issue there.

The regression has been introduced with 1.8.

This is fixed in 2.13.0 of the helper.

released

Thx @bobylito


Out of Topic

sorry if this question goes off topic, I just wanted to ask how selenium makes it possible to enable third party cookies?
thanks

I don't think any additional arguments need to be added. It should accept third party cookies automatically.


Error: Program type already present: com.google.android.libraries.places.api.internal.impl.net.pablo.AutocompletePredictionResult$StructuredFormatting" after adding new libraries

I just added:
   implementation ('com.google.android.libraries.places:places:1.0.0') {
        exclude module: 'support-v4'
    }
    implementation ('com.google.android.libraries.places:places-compat:1.0.0') {
        exclude module: 'support-v4'
    }

And I got the following error:
AGPBI: {"kind":"error","text":"Program type already present: com.google.android.libraries.places.api.internal.impl.net.pablo.AutocompletePredictionResult$StructuredFormatting","sources":[{}],"tool":"D8"}

Any help will be appreciated.
Thanks in advance.
the only one related thing that I've found on entirely internet (using google of course) was:
http://qaru.site/questions/17030061/google-places-api-program-type-already-present-autocompletepredictionresult
and it is also answered.

This is because you are including both places and places-compat. You must remove one of them.

If you remove the second one: com.google.android.libraries.places:places-compat:1.0.0 the project doesn't compile.
Any idea??
@eriknyk , could you resolve it ?

I have the same problem and removing one of them doesn't solve the problem.
I left the com.google.android.libraries.places:places:1.0.0 and the error is exactly the same.
What should I do?
@eriknyk

i am having the same problem
Error: Program type already present: com.google.android.libraries.places.api.internal.impl.net.pablo.AutocompletePredictionResult$StructuredFormatting
what should i do?

@kamilwyszynski @dharmeshrathore Can you provide a link to your gradle file?

Same problem here

@McKabue can you provide a link to your gradle file?

I have the same issue,  what was the solution?

Same problem any solution found?

It was a library issue. Google is confusing with their new Places SDK migration description.
But I fixed the issue doing the following:
In Gradle App dependencies
implementation 'com.google.android.libraries.places:places:1.1.0'  // Remove
implementation 'com.google.android.libraries.places:places-compat:1.1.0'  // Add
*** In activity
import com.google.android.libraries.places.api.net.PlacesClient; // Remove
import com.google.android.libraries.places.api.Places;  // Remove
*** Remove all com.google.android.gms.location.places and replace with:
import com.google.android.libraries.places.compat.AutocompletePredictionBufferResponse;  // New
import com.google.android.libraries.places.compat.AutocompletePrediction; //New
import com.google.android.libraries.places.compat.AutocompleteFilter;  //New
import com.google.android.libraries.places.compat.GeoDataClient;  //New
import com.google.android.libraries.places.compat.Place;  //New
import com.google.android.libraries.places.compat.Places;  //New
import com.google.android.libraries.places.compat.PlaceBufferResponse;  //New

thanks for the info @jwilly12!

@kamilwyszynski  nope, I have not look to get com.google.android.libraries.places.compat working,
I spend about middle day trying to get this working, and after that I decided to rewrite the implementation with using new api so get rid of places.compat, and rewrite the code took in my case half hour.

Duplicate class com.google.android.libraries.places.api.internal.impl.net.pablo.AutocompletePredictionResult found in modules classes.jar (com.google.android.libraries.places:places-compat:1.1.0) and classes.jar (com.google.android.libraries.places:places:1.1.0)
It's impossible to solve this duplicity until a solution to this problem appears, I'll continue using 'com.google.android.gms: play-services-places: 16.1.0'

Just comment this 'com.google.android.libraries.places:places:1.0.0' use only this 'com.google.android.libraries.places:places-compat:1.0.0'  issue will resolved.


Ecto.Adapters.ClickHouse.structure_load: not implemented

Can we support this? I am currently migrating my old clickhouse schema files over and would like to have my old schema in a structure.sql.
Can we not just split on ; and execute every query step by step with the caveat there is no option for a rollback and that it can fail while executing? I feel like this is reasonable for a load operation since one expects the structure.sql to only be loaded once or during ci jobs on clean fresh databases

I will look into this then soonish!

@ruslandoga I wanted to work on this. How do you set up your dev environement to run command line things such as mix ecto.load?
Do you create a separate app and then just reference your local ecto_ch as dependency?

I don't remember exactly what I did during development, I think I tested the callbacks directly: https://github.com/plausible/ecto_ch/blob/master/test/ecto/adapters/clickhouse/structure_test.exs, and once the tests pass did a manual test in a separate app (plausible/analytics).

Ah perfect, I am doing the same right now

History shows that I already had "working" code when adding tests.
https://github.com/plausible/ecto_ch/pull/17/files
Maybe I used the dev repo: https://github.com/plausible/ecto_ch/blob/master/dev/repo.ex


only include transactions that are real donations

Coverage remained the same at 81.149% when pulling af3787e058bc8e94cd88d61e8220caf7c0188d00 on slack-report into f930cf7ec073259eaffbddf22c0a18c15b8276ed on master.


todo

revisit the "routing" and "dynamic pages" chapters and then do a chapter on DB handling

I've had to use a markdown parser (I used Parsedown) to actually pass md files through twig in a way that they would render correctly in the browser. Was that left as an exercise for the reader? Should there be a section on how to integrate that markdown parser to the FilePageReader?

It could be a new PageReader implementation with a simple PDO object passed in (which could obviously be an implementation and concrete...) Or abstracted classes for the various tables...  But the way you build on things from chapter to chapter I feel like it could be started with a simple implementation and piled on later.
<?php

namespace Example\Page;
// use stuff ...

class DbPageReader implements PageReader {
    private $db;

    public function __construct(Database $db)
    {
        $this->db = $db;
    }

    public function __readBySlug(string $slug) : string
    {
        $page = $this->db->query('SELECT * FROM pages WHERE slug = ?', ['slug' => $slug]);
        return $page->body;
    }
}

I've been using "my own" wrapper: https://github.com/ellisgl/GeekLab-GLPDO
The structure I use is as follows:
src
Db
Connect
{databasename}.php
Model
---Models are data that are manipulated---
Query\ ---Query files only have single queries---
{tablename}.php


Add library publishing and update Gradle/Kotlin versions

This will allow SVG non-stop to be used as a project dependency via JitPack as explained in the updated README. It will take effect after tagging the pulled commit with "1.1.2" and then opening this Jitpack link to give JitPack a chance to build and publish it.
I tested Gradle assemble and the built application to confirm none of the Gradle changes affect current use of the app.
I updated the Gradle and Kotlin versions to help future-proof it.

*will take effect after creating a release named "1.1.2" before opening that Jitpack link.
By the way, I created this PR after I realized the project could easily be both an application and library based on how you already structured your code. No need for me to maintain a fork to be able to use it in a Gradle plugin.

The two follow-up commits:

I realized this couldn't be used from Java without a package declared, in case anyone wants to use it in a Java project.
I discovered you're supposed to use io.github rather than com.github as your prefix. [details here](gradle.publish.key=SEIevDdET3uh4lv2361DQjwOvPDEirRd
gradle.publish.secret=cvNdnuog9vFxS7e1R7C3akLR3q0q6gId)


TextureProgressBar has always visible Gizmo when setting Fill Mode to 4, 5 or 8

Tested versions
Reproducible in: v4.3.stable.mono.official [77dcf97d8] (Latest)
System information
Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; <IP_ADDRESS>94) - AMD Ryzen 7 5800X 8-Core Processor (16 Threads)
Issue description
When selecting either "Clockwise", "Counter Clockwise" or "Clockwise and Counter Clockwise" as the FillMode, a cross is displayed in the center of the rect. This does not disappear, even when selecting another node or left clicking somewhere else in the scene view. Additionally, the crosshair is also visible when the TextureProgressBar node is used in an EditorPlugin.

Steps to reproduce

Add a TextureProgressBar to your scene.
Set it's Fill Mode to either "Clockwise", "Counter Clockwise" or "Clockwise and Counter Clockwise"
A crosshair will show up in the center. If you now click somewhere else or select another node, it will not disappear.

Minimal reproduction project (MRP)
Mrp.zip

This is done by design, but should probably be something you can configure, and not do when used in plugins etc:
https://github.com/godotengine/godot/blob/4788f54d9767425bf5435b1cc940885d357795c5/scene/gui/texture_progress_bar.cpp#L538-L553

A few questions:

What is the purpose of that reference cross?
Should Plugins be handled like if the node was in an actual "game scene"?
Would it make sense if it was more an option to enable the reference cross independent from what FillMode is selected?

It's to help you align things I'd say
That would be hard, though we could use is_part_of_edited_scene, will see if I can test that out some
I'd say that'd be the most useful solution

I think this maybe could be reworked to use Marker2D as internal node.

I made dirty but working prototype (this was actually easy) and this is how it may look:
Current master, big 1024x1024 TextureProgressBar:

4.4dev2
Prototype

And you should be able to access crosshair from code as internal Marker2D child node.

Another possible solution - add editor-only metadata to set crosshair visibility.

Sorry for not answering for so long I got distracted again. Does your prototype allow for disabling the crosshair even in the normal editor (without having to attatch a tool script or something to the node)?

Sorry for not answering for so long I got distracted again. Does your prototype allow for disabling the crosshair even in the normal editor (without having to attatch a tool script or something to the node)?

No, I did not add/change any methods. You still should change visibility of internal Marker2D node using script. Having additional parameters or methods for this looks like overkill.
Also there is controversial moment - should it be always added (for consistency) or only for editor?
Moreover, Marker2D is Node2D and TextureProgressBar is Control.
So this is not an ideal solution at the moment, and the implementation details should be discussed in more detail.

Oh, it looks like this problem was reported a few years ago.
See https://github.com/godotengine/godot/issues/46266


Add validation in Release Planner that service/product is using Typespec

Follow up from https://github.com/Azure/azure-sdk-tools/issues/6932 we should validate that if the service/product is new, that the API Spec definition type is TypeSpec. If not, either show error, send them to talk to someone, or etc. => process to be defined

This has been covered in the specs repo themselves so there isn't much for us to do here


CBAPI-2018 Process and Process Event Query Methods

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Tests have been added that prove the fix is effective or that the feature works.
[x] New and existing tests pass locally with the changes.
[x] Code follows the style guidelines of this project (PEP8, clean code, linter).
[x] A self-review of the code has been done.

What is the ticket or issue number?

https://jira.carbonblack.local/browse/CBAPI-2018
Pull Request Description

Adds the ability to set criteria, exclusions, fields, sort, start, rows, and time_range for Process and Event searches
Moved the sort method up from the AsyncProcessQuery object into Query
Does this introduce a breaking change?

[ ] Yes
[x] No

How Has This Been Tested?

Pytests added

Documentation updates needed for RTD, specifically the Criteria section of concepts.rst


Try to only run dwarfdump on executables

Changes Unknown when pulling 2d3c285d9c92c622c4b3723b6b7212e4b116f56a on philipc:travis into ** on gimli-rs:master**.

Changes Unknown when pulling 705cce43cbb7340834b73dde4a790f13194d8f45 on philipc:travis into ** on gimli-rs:master**.

The 'cargo clean' is because it was caching lots of target/debug/gimli-*, so we weren't running dwarfdump on the latest. Doesn't seem to have affected build time.


Don't require Numba to run

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Having Numba in the run section of the recipe forces Numba to be installed with ptxcompiler. Although ptxcompiler can patch Numba to use it, Numba isn't required for ptxcompiler to be used itself. Additionally, having ptxcompiler depend on Numba makes it hard to use ptxcompiler from Numba (e.g. for https://github.com/numba/numba/pull/8180).
This PR moves it to run_constrained, so that its installation is not required, but if it is present then only versions that can be correctly patched to use ptxcompiler are allowed.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I'd imagine it's not worth it to patch old versions, as I don't expect people are sticking with older versions.

Ok. We can always follow up later if needed

Thanks Graham! Also thanks Bradley for the review 🙏

Many thanks for the reviews and merge!


Extend rogue agent logs/events with VM id

Rogue agent events/logs need the VM id. In case of a rogue agent the VM should most probably be killed. It's very hard at the moment to figure out the VM of the rogue agent.

possible solution: could heartbeats contain the CID of the VM and the HM could also contain it in the alert? Currently, it is really hard to figure this out youself.

only thing that we can really trust from the agent is agent id. all other
info should be pulled in from the director if necessary so that it's coming
from an authoritative source.
On Mon, Nov 20, 2017 at 2:46 AM, Marco Voelz<EMAIL_ADDRESS>wrote:

possible solution: could heartbeats contain the CID of the VM and the HM
could also contain it in the alert? Currently, it is really hard to figure
this out youself.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/bosh/issues/1837#issuecomment-345615651,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALV901KtTEIX6mBTgFqByfjrIupHbaJks5s4S5fgaJpZM4QiRqR
.

@cppforlife so how would you propose to find out the VM to a rogue agent? All this is about is making that process easier somehow.

Hey @beyhan @voelzmo is this an issue you're still interested in discussing?

Yes, we're still interested in making it easier to follow-up on rogue agent alerts for operators or automation.


Problems using it on ControlNet workflow

I have 2 controlNet before the prompt (one tile, one Hed), when I add the hook between prompt (which is null, I don't use any to test) and 1st controlnet (positive) it gives me 0 differente or even an error message. Did you try to use with a loaded image on img2img to see the effect?

Seems to work for me?
Disabled

Enabled

Sample Workflow:

Ensure that:

The node is actually executed
You're not using an Ancestral sampler

Ei hi, totally right, My comfyUI was bugged, reinstall and updated and works. Thanks!


[Amazon AWS] Fix resource names for Step Function Command Actions

Description
Fix resource names for Step Function Command Actions. Plus, minor refactors and added the state machine type as an accessory.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

This closes https://github.com/raycast/extensions/issues/12353


Tests with Forwarding (Status 307) behave different than Postman

I have some tests in Postman that I wanted to move to Visual Studio Code, using your plugin.
One of my tests access an access point that forwards to another location via HTML status 307. I verify the response with the following tests:
pm.test("Status code is 307", function () {
     pm.response.to.have.status(307);
});
pm.test("Location is present", function () {
    pm.response.to.have.header("Location");
});
tests["Location is correct"] = (/^https:\/\/my-awesome-dummy-address.com/.test(pm.response.headers.get('Location')));

This is working successfully with the "original" Postman. However, using your Plugin, I receive a code 200, so I assume that the tests run on the forwarded address and thus fail. It would be nice if the Postman program and VSC plugin would behave consistently here.

Please verify if the new version solved your issue.

Unfortunately, it does not. I just installed the newest version in Visual Studio Code 2.0.0 and still get the mentioned status 200.
Is it the correct version? Or do I need to download a beta version or something someplace else?


Support getting token from path

This solves issue #3
Summary
What this PR aims to achieve is to make it possible to use the library in a GKE container that uses workload identity, instead of a credentials json file.
Here is the outline of the solution:

Add a configurable option to use workload identity (detect presence of config)
If enabled, use the following strategy to get a bearer token:
a. Perform an HTTP GET request to http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token with the header "Metadata-Flavor: Google"
b. Retrieve token and expiry from the response : { "access_token": "...", "expires_in":3090,"token_type":"Bearer" }
c. Update the oauth dict

The cleanest way to achieve this is probably to create a new module called "workload_identity_client", along with a new configuration table for it. The client can have the same "get_oauth_token", perhaps renamed to just "get_token", so either client can be passed in to request constructor from producer.

Everything seems to be working as expected locally - I still need to test it in GKE, I will do that on Monday.

Another issue I am seeing now is quite a few of these in my logs:
producer.lua:149: _timer_flush(): failed to create timer at _timer_flush, err: too many pending timers

I have not seen them before, so therefore suspecting it's something with my code. Trying to investigate.

Update: Seems like the fix of reverting to default settings only postponed the problem. It now runs for about 20-30 minutes without issues before starting to issue the same warnings (too many pending timers).

Update: Issue resolved, it was a silly mistake during testing where I used dofile instead of require on the producer, which resultet in an increasing number of producer instances with runaway timers.
This PR is now ready for review 🎉

@Vasu7052 Is this something you are interested in as a feature?


feat: add exception handling logic

Also included

feat: distinguish request failure from request success with no content
refactor: turn module into utility function
chore: standardize RubyGem require entrypoint

@barelyknown since introducing this gem, we've been raising more errors to rollbar since it doesn't have the same 'what kind of failure am i' logic.  If this looks ok to you, I'll test it in our app and write some tests here.

Yeah definitely fine with me. I just spiked it.


Multiple SparklinesLine color on a guideline

Hey 👋 It's great that you created this wonderful plugin. Is there a possibility to have a centered guideline sparkline that also generate SparklineLine that is green when above this guideline and red if it is below. See my attached image.

Would be happy to have this option as well.

@borisyankov - any comment on this functionality? would be fantastic to be able to have positive/negative values and colors to match.


No visible @interface for 'Twitter' declares the selector 'logInWithMethods::'

When building I get this error:
No visible @interface for 'Twitter' declares the selector 'logInWithMethods::'
I'm using RN 0.4 and Twitter Kit 3.0.3

With that version of twitter kit I had that problem, now I am using these versions and runs without problem
   - Fabric (1.6.11)
   - TwitterCore (2.8.0):
   - TwitterKit (2.8.1):

it was updated to use TwitterKit 3.0, so this should work fine now


@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/42233
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.7 -m "<description of version>" 34496981f208b9c9f39254c381169a7ac69bf722
git push origin v0.9.7


refactor(authz): use a struct for user access control info operations

fix(authz): fix isAdmin not using groups to determine if a user is admin.

What type of PR is this?
bug && refactor

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I re-reviewed the PR in current state, and don't have additional comments.


Next.js RSC error: It's currently unsupported to use "export *" in a client boundary

Which package has an issue?
@yamada-ui/react
Package Version
0.9.1
Description
When I use Yamada UI component in a Next.js RSC, I get an error: It's currently unsupported to use "export *" in a client boundary
./node_modules/.pnpm/@yamada-ui+react@0.9.1_@emotion+react@11.11.0_@emotion+styled@11.11.0_@types+react<EMAIL_ADDRESS>Error: It's currently unsupported to use "export *" in a client boundary. Please use named exports instead.

Link to Reproduction
No response
Steps to Reproduce

use a Yamada UI component directly in a server component
see compilation error

Browser
Chrome
Operating System

[X] macOS
[X] Windows
[X] Linux

Do you know how to fix the issue?
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix?
Yes
Additional Information
No response

Done #455


Webview scrolls when content does not exceed viewport

Hi, so I've noticed on all my screens the that the webview is scrollable. This caused an issue when using a floating action button with materializecss.css as it's hidden until you scroll to it.
Is there something special I need to do to prevent the scrolling or only scroll when content is long enough?
In the first screenshot, I'm able to scroll down further
In the second screenshot, the starting position which is unscrolled shows that it's already scrolled down. I believe this is the issue that I have as the floating action button positions itself with a fixed position bottom right of screen-based e.g
.fixed-action-btn {
    position: fixed;
    right: 23px;
    bottom: 23px;
    padding-top: 15px;
    margin-bottom: 0;
    z-index: 997;
}

I added a floating action button from the materializecss lib to the example app. Heres a better demonstration of the issue:
I added this to the layout.erb  section
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/materialize/1.0.0/css/materialize.min.css">

and this to index.erb

    mode_edit

insert_chart

format_quote

publish

attach_file

It is not supported by turbolink-ios, since scroll provides refresh for pages too.. If you want this kind of button it should be implemented with native view maybe using https://github.com/santomegonzalo/react-native-floating-action

thanks @lazaronixon, I'll look into that.


handling non-standard django app configs

This is a bug that I have a working fix for. I will open an PR shortly for @adamghill to review 😃
Summary of bug
The utility at components.unicorn_view.get_locations incorrectly assumes the python path for django apps follows the format of path.to.apps.ExampleConfig. This is not always the case because some django teams choose to store configs elsewhere.
Example
Here are some example configs where the bug exists: https://github.com/jacksund/simmate/blob/main/src/simmate/apps/configs.py
You'll see the configs are located at simmate.apps.configs and each config points to a different location for where the django app lives. Thus, unicorn is crashing because it incorrectly handles the a string such as simmate.apps.configs.WarrenLabConfig that is in INSTALLED_APPS.
Suggested fix
This issue can be fixed by using django's official recommendations on how to interact with configs:

django cautions against interacting with INSTALLED_APPS, but instead recommends loading configs via django.apps.apps (source)
the get_locations is really after the python import path for the app. This is stored as name on the app's config object (source)

Implementing the fix
The following code will be replaced:
https://github.com/adamghill/django-unicorn/blob/7097b6315ff96e399719c1dee028bcab2ca33988/django_unicorn/components/unicorn_view.py#L109-L137
The new implementation will be as follows:
from django.apps import apps as django_apps

# note: app_config.name gives the python path
all_django_apps = [app_config.name for app_config in django_apps.get_app_configs()]
unicorn_apps = get_setting("APPS", all_django_apps)

if not is_non_string_sequence(unicorn_apps):
    raise AssertionError("APPS is expected to be a list, tuple or set")

locations += [(f"{app}.components.{module_name}", class_name) for app in unicorn_apps]
return locations

Thanks for fixing this for real. I knew when I wrote this code, it wasn't the right way, so I'm really appreciative you cleaned this up. I will look at the PR soon!

The PR looks good, so I merged it in. Will let you know when the version is released.


Fixes #36

Updates Get-GitForWindows to return correct version number

@aaronparker Not sure why the Atom tests are failing, but I don't think it's anything I've broken!?


Update CONTRIBUTING.md

/sig multicluster
The contribution file should have links to the dev documentation, and an indication that contributions are being solicited.

Fixed in #103.


Code

Thank you for your excellent work, when will you release the training code?

Thank you for your interest in our work! The release time is expected before Feb. 2024 if things work all the best :).
Thanks,
Yiming

Thank you for your excellent work! I note that the code for your project is currently unpublished, and I understand that it may not be immediately available. However, I would very much like to have access to your dataset if possible.

Hello, I am very happy to see your work. It seems that your training code has not been released. When could we see your training code?


ImportError: No module named absl.flags #mnist_spark.py

Hello,
I was trying to run the mnist_spark.py with following inputs:
/root/spark-2.2.0-bin-hadoop2.6/bin/spark-submit --master yarn --deploy-mode cluster  --py-files /root/TensorFlowOnSpark/tfspark.zip,/root/TensorFlowOnSpark/examples/mnist/spark/mnist_dist.py --conf spark.dynamicAllocation.enabled=false --conf spark.yarn.maxAppAttempts=1  /root/TensorFlowOnSpark/examples/mnist/spark/mnist_spark.py --images examples/mnist/csv/train/images --labels examples/mnist/csv/train/labels --cluster_size 2 --mode train --model mnist_model
However, I got an error which says:
18/05/24 21:00:33 ERROR executor.Executor: Exception in task 1.0 in stage 0.0 (TID 1)
org.apache.spark.api.python.PythonException: Traceback (most recent call last):
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/worker.py", line 177, in main
process()
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/worker.py", line 172, in process
serializer.dump_stream(func(split_index, iterator), outfile)
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/rdd.py", line 2423, in pipeline_func
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/rdd.py", line 2423, in pipeline_func
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/rdd.py", line 2423, in pipeline_func
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/rdd.py", line 346, in func
File "/root/spark-2.2.0-bin-hadoop2.6/python/lib/pyspark.zip/pyspark/rdd.py", line 794, in func
File "/home/data2/nm-local-dirs/usercache/root/appcache/application_1527165162039_0004/container_1527165162039_0004_01_000001/tfspark.zip/tensorflowonspark/TFSparkNode.py", line 136, in _mapfn
File "/usr/lib/python2.7/site-packages/tensorflow/init.py", line 24, in
from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
File "/usr/lib/python2.7/site-packages/tensorflow/python/init.py", line 63, in
from tensorflow.python.framework.framework_lib import *  # pylint: disable=redefined-builtin
File "/usr/lib/python2.7/site-packages/tensorflow/python/framework/framework_lib.py", line 25, in
from tensorflow.python.framework.ops import Graph
File "/usr/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 55, in
from tensorflow.python.platform import app
File "/usr/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 24, in
from tensorflow.python.platform import flags
File "/usr/lib/python2.7/site-packages/tensorflow/python/platform/flags.py", line 25, in
from absl.flags import *  # pylint: disable=wildcard-import
ImportError: No module named absl.flags
at org.apache.spark.api.python.PythonRunner$$anon$1.read(PythonRDD.scala:193)
at org.apache.spark.api.python.PythonRunner$$anon$1.(PythonRDD.scala:234)
at org.apache.spark.api.python.PythonRunner.compute(PythonRDD.scala:152)
at org.apache.spark.api.python.PythonRDD.compute(PythonRDD.scala:63)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
at org.apache.spark.scheduler.Task.run(Task.scala:108)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:335)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
is there any suggestion about this conflicts please?

I'm assuming that you've installed tensorflow onto each of your grid nodes, and that you've been able to run a quick test on each as well?
This looks like a TF installation issue, e.g. this stack overflow.

Hi, I used the pip install -upgrade tensorflow and the error about missing import absl has gone. thanks.
however, I have another error about running mnist_spark.py  which says:
2018-05-27 21:33:05,881 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:06,882 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:07,883 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:08,885 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:09,886 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:10,887 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:11,889 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:12,890 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:13,891 INFO (MainThread-21278) waiting for 3 reservations
2018-05-27 21:33:14,893 INFO (MainThread-21278) waiting for 3 reservations
Traceback (most recent call last):
File "mnist_spark.py", line 68, in
cluster = TFCluster.run(sc, mnist_dist.map_fun, args, args.cluster_size, num_ps, args.tensorboard, TFCluster.InputMode.SPARK, log_dir=args.model)
File "/usr/lib/python2.7/site-packages/tensorflowonspark/TFCluster.py", line 306, in run
cluster_info = server.await_reservations(sc, tf_status, reservation_timeout)
File "/usr/lib/python2.7/site-packages/tensorflowonspark/reservation.py", line 121, in await_reservations
raise Exception("timed out waiting for reservations to complete")
Exception: timed out waiting for reservations to complete

Hi,
Please find the log file in the attachment.
yarnlog.txt

Interesting, it looks like you started a 2 node cluster (1 PS + 1 worker), but the logs only show the driver and the PS logs, but no worker log.  If you can view the executor logs while the job is running, it MIGHT show more information (not sure).  Otherwise, figure out the node which is failing to start, and then ssh into that box and run a local python/tensorflow test to see if it's working at least locally.

Closing due to inactivity.  Feel free to reopen if still an issue.

2018-10-25 15:35:58,881 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:35:59,882 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:00,884 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:01,885 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:02,886 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:03,888 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:04,889 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:05,890 INFO (MainThread-10731) waiting for 2 reservations
Traceback (most recent call last):
File "mnist_spark.py", line 69, in
cluster = TFCluster.run(sc, mnist_dist.map_fun, args, args.cluster_size, num_ps, args.tensorboard, TFCluster.InputMode.SPARK, log_dir=args.model)
File "/usr/local/hadoop-2.7.1/tmp/nm-local-dir/usercache/honglingwang/appcache/application_1540289919087_0021/container_1540289919087_0021_01_000001/tfspark.zip/tensorflowonspark/TFCluster.py", line 297, in run
File "/usr/local/hadoop-2.7.1/tmp/nm-local-dir/usercache/honglingwang/appcache/application_1540289919087_0021/container_1540289919087_0021_01_000001/tfspark.zip/tensorflowonspark/reservation.py", line 121, in await_reservations
Exception: timed out waiting for reservations to complete
End of LogType:stdout

Hi,after running for a while,I have an error about running mnist_spark.py as follows:
2018-10-25 15:35:58,881 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:35:59,882 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:00,884 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:01,885 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:02,886 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:03,888 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:04,889 INFO (MainThread-10731) waiting for 2 reservations
2018-10-25 15:36:05,890 INFO (MainThread-10731) waiting for 2 reservations
Traceback (most recent call last):
File "mnist_spark.py", line 69, in
cluster = TFCluster.run(sc, mnist_dist.map_fun, args, args.cluster_size, num_ps, args.tensorboard, TFCluster.InputMode.SPARK, log_dir=args.model)
File "/usr/local/hadoop-2.7.1/tmp/nm-local-dir/usercache/honglingwang/appcache/application_1540289919087_0021/container_1540289919087_0021_01_000001/tfspark.zip/tensorflowonspark/TFCluster.py", line 297, in run
File "/usr/local/hadoop-2.7.1/tmp/nm-local-dir/usercache/honglingwang/appcache/application_1540289919087_0021/container_1540289919087_0021_01_000001/tfspark.zip/tensorflowonspark/reservation.py", line 121, in await_reservations
Exception: timed out waiting for reservations to complete
End of LogType:stdout

@wanghongling123 Please file a new issue (unless you are seeing the "ImportError: No module named absl.flags" issue in your logs).


Replace build time in binary with commit time

- What I did
Replace build time in binary with commit time
- How I did it
By changing the date by the git commiter date in the Makefile
- How to verify it
$ docker app --version

- Description for the changelog
Replace build time in binary with commit time
- A picture of a cute animal (not mandatory)

Why do we need such date?
Commit Sha is enough to track code matching binary. IMHO binary from commit should be fully reproducible.

@ndeloof I see this more as a user feature to know from when is the commit of the current binary and not a dev/debug information. Maybe we need to confirm with @chris-crone before merging.

The only real use of the build time is when you're testing your local build between commits and want to make sure you're using the latest version. We can:

Remove the build time completely
Only store the build time when building with uncommitted changes (i.e.: git describe --always shows <sha>-dirty)

I'm happy with either of the above solutions.

Was having a chat with @chris-crone (not related to this PR) Just recalled there's a "standard" env-var to use for commit-time; SOURCE_DATE_EPOCH (see https://reproducible-builds.org/specs/source-date-epoch/). Same variable was added in the "engine" in https://github.com/moby/moby/pull/34176

I've chosen approach 1, removing build time.

Windows CI is failing (not clear what on though)

@thaJeztah I just rerun the tests in the CI. Windows machines are a bit unstable

All green now; @chris-crone PTAL


persist year attribute for source_sets

This persists a year attribute for source_sets.  It adds a column to the source_sets table.  The model validates that year is an integer.  It provides an interface for admins to add, view, and edit the year.
This addresses ticket #8204.

Is this year the date of creation of the source resource? Is it possible it would ever be BCE, for instance, for a picture of some sculpture from a museum?
Other than that, and my question about validating the range, I don't have any other observations, and this looks good to me.

The year is a subject related to the items in the set.  It could be BCE, but its very unlikely.  If it were, I image that we could use a negative number to represent a BCE date.  This year is not going to be shown the end user, it's just going to be used to sort source_sets behind-the-scenes.
It would probably be helpful to put at least a maximum cap on the date range, say 2100.  I'm not sure about a minimum cap because I can picture a world in which someone wants to make a set about fossils or something.

I guess that, in that case, it's a matter of documentation and the perceived needs of future admins. If the maintainers grows to a group larger than a few internal users, they might be prone to forget that the year is just a sort-order key; but I'm not sure how important this is to the project. Maybe a tooltip or label would help to clarify that it's just for sort order.
Another thing is that ranges like "2014-5" or phrases like "1920s" would be invalid, and I could see new  admins trying to enter those -- without a tooltip or label for guidance.

@markbreedlove I added a validation and test to ensure that the year can't be greater in value than the current year.

@markbreedlove I just saw your latest comment about adding instructions to the admin interface - doing that now.

@markbreedlove instructions have been added to the view: https://github.com/dpla/primary-source-sets/pull/85/files#diff-8b5366e103d161b9136995d3c47ea222R32

Thanks! Good to go ...


Unable to get version without being root

Is this a BUG REPORT or FEATURE REQUEST?:

kind bug

Description
I don't think I should need to be root to read the podman version.
Steps to reproduce the issue:
[core@crawford-libvirt-master-0 ~]$ podman --version
ERRO[0000] cannot re-exec process
[core@crawford-libvirt-master-0 ~]$ sudo !!
sudo podman --version
podman version 0.7.3

Fixed somewhere in 0.8.x - I want to say 0.8.4?

What distro are you on?

i think it went into 0.8.3

@mheon:
$ cat /etc/os-release
NAME="Red Hat CoreOS"
VERSION="4.0.5470"
ID="rhcos"
ID_LIKE="rhel fedora"
VERSION_ID="4.0"
PRETTY_NAME="Red Hat CoreOS 4.0.5470"
ANSI_COLOR="0;31"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat 7"
REDHAT_BUGZILLA_PRODUCT_VERSION="4.0"
REDHAT_SUPPORT_PRODUCT="Red Hat"
REDHAT_SUPPORT_PRODUCT_VERSION="4.0"
OSTREE_VERSION=4.0.5470

CoreOS should be getting a newer version soon - there were some questions as to where to get Podman from.


ClamAV Image Moved to GHCR

As of a recent release (https://github.com/Mailu/Mailu/releases/tag/2.0.0), the mailu/clamav image is no longer available in DockerHub. It's moved to ghcr.io.
I tried just setting these in values.yaml as a workaround for the moment, but there are some additional changes needed to upgrade to 2.x.
image.repository: ghcr.io/mailu/clamav
image.tag: 2.0.4

https://mailu.io/2.0/releases.html#upgrading

1.9.50 is in GHCR, so this worked for me.
image.repository: ghcr.io.mailu/clamav
image.tag: 1.9.50

Thanks for the report, i have done it here:

https://github.com/wiremind/wiremind-helm-charts/pull/258


CompletionVisionMessage format

Discussed in https://github.com/johniwasz/whetstone.chatgpt/discussions/218

Originally posted by philbags June 13, 2024
Hi There,
I'm trying to get a description of an image using a ChatGPTCompletionVisionRequest.
I'm struggling to get the format correct for a CompletionVisionMessage.  Intellisense is telling me the content should be a list(of object). Would anyone be able to provide sample code for this?
Many thanks in advance!

Worked it out myself:
   ```

var dictType = new Dictionary<string, string>
{
{ "type", "text" },
{ "text", "What is in this image?." }
};
    var dictImage = new Dictionary<string, string>

{
{ "type", "image_url" },
{ "image_url", url }
};
    var yourObjects = new List<object>

{
dictType,
dictImage
};
    var msglist = new List<ChatGPTCompletionVisionMessage>

{
new ChatGPTCompletionVisionMessage { Role = "user", Content = yourObjects }
};


Crashing

Game crashed if i leave console open for 1 minute

Still crashing with newest update

and also to add it crashes when im not closing console and getting game minimised i think its only cause it crashing game

Closing as this doesn't seem related to the mod, make sure you don't have other mods with issues.

I have only this mod... only use console

Closing as this doesn't seem related to the mod, make sure you don't have other mods with issues.

I have only this mod only use console...

To reproduce issue open console and minimise game and after 10 seconds or more it will crash

We have tried to reproduce the bug and have never been able to...

Ant way to find out why it's crashing any logs for it ?


Feature/jvisenti/extensible sequence

Added the ability to extend RZViewAction sequences after they have been created. This addresses issue #8
This change will be released in version 0.3.0
NOTE: This branch was off of master, so a podspec change that was never merged back into develop is lumped in with the changes.

Will be merging this today and pushing v0.3.0 if there are no objections.

Merging...


Failed to load resource: .../iron-component-page/iron-component-page.html

Hello,
I have this error in both browser, but with IE,Edge and firefox, this error break my app angular2.
This error apear on my application since I use your component vaadin.
But works with chrome.
I have any solution?
Thx
Yvan

I believe you can install this element with bower:
$ bower install PolymerElements/iron-component-page

But seriously, normally it should not be required. It’s an element that renders documentation pages for Polymer elements, probably not directly useful for your app.
Please try to find, what tries to load it. Looking for a Referrer header for the request of iron-component-page in the network log inside browser developer tools might help.

Hello @platosha,
Yesterday, I have installed icon-component and was worst,
I find the referrers :

inside index.html from vaadin-data-picker, vaadin-combo-box ...

@platosha
My mistake, i have imported   <link rel="import" href="lib/paper-button/index.html" />  instead of     <link rel="import" href="lib/paper-button/paper-button.html" />
Sorry for the distrub !
thx again


Azure 3.0.0

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1980   +/-   ##
=======================================
  Coverage   53.17%   53.17%
=======================================
  Files        4714     4714
  Lines      117148   117148
=======================================
  Hits        62295    62295
  Misses      54853    54853

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 80fc6f0...02a2c37. Read the comment docs.

@zezha-msft to give you an idea of why I don't do it every day :p
Especially this one is subtle, since upgrading from azure 2.0 to 3.0 will try to upgrade from azure-storage 0.x to azure-storage-blob/page/queue 1.x, which is problematic...
I expect issues in the next days on failed upgrade from 2.0 to 3.0....

Hi @lmazuel, thanks for the insight!
I do not foresee any breaking structural change for the Storage SDK, hopefully this will not happen again! 😃


Update javadocs for all project and code coverage.

Coverage decreased (-1.1%) to 78.06% when pulling 8e58d0a9ea0b87003c81bf06300d47f0c4c8515b on bogdandrutu:ocall into 0b4f14a7135d24e60f47718d844a85b29a4bf3db on census-instrumentation:master.

Codecov Report

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

@@             Coverage Diff              @@
##             master     #735      +/-   ##
============================================
- Coverage     77.32%   76.12%   -1.21%
- Complexity      772      782      +10
============================================
  Files           142      144       +2
  Lines          3520     3619      +99
  Branches        331      345      +14
============================================
+ Hits           2722     2755      +33
- Misses          733      794      +61
- Partials         65       70       +5

Impacted Files
Coverage Δ
Complexity Δ

...encensus/exporter/trace/zipkin/ZipkinExporter.java
31.81% <0%> (ø)
3% <0%> (?)

...s/exporter/trace/zipkin/ZipkinExporterHandler.java
33.76% <0%> (ø)
7% <0%> (?)

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 0b4f14a...8e58d0a. Read the comment docs.


DOC: Add examples to scipy.cluster.hierarchy

Additionally, many small changes are applied according to PEP8

Thanks @MartinThoma, examples look good. Just a few minor things to fix that I commented on.

CI failure was a 50 min timeout, unrelated to this PR.
LGTM now, merging. Thanks @MartinThoma


Updating material.opacity does not work as expected

https://playcanvas.com/project/633316/overview/mattest
There are two 2D Screens, one is enabled by default, another one is disabled.
First one works as expected, the opacity will be set to 0.5.
The second element does not work properly, it will be enabled by Root/delayedEnable after 1 sec. but opacity won't be changed.
This only happens with texture, So I made 2 elements for each 2D Screen to explain it.

How about this?

in your Test.js
var Test = pc.createScript('test');

Test.prototype.initialize = function() {

    this.entity.element.material = this.entity.element.material.clone();
    this.entity.element.material.opacity = 0.5;

    if(this.entity.name === 'Tex (BUG)') {
        var material = new pc.StandardMaterial();
        var blood = pc.app.assets.find('bear.gif', 'texture');

        material.diffuseMap = blood.resource;
        material.opacityMap = blood.resource;
        console.log(material.opacityMap);
        material.blendType = pc.BLEND_NORMAL;
        // material.opacityMapChannel = 'r';
        material.update();
        this.entity.element.material = material;

    }

    this.entity.element.material.update();

};

@velbi
Thank you for the solution, but I think your code is a workaround. I wrote the issue to request them to fix it.
And, here's a code how I solved it.
setTimeout(() => {
  this.entity.element.material = this.entity.element.material.clone();
  this.entity.element.material.opacity = 0.1;
  this.entity.element.material.update();
}, 1);

#6721 most likely fixed this issue, closing.


Fix project social Profiles displaying in adminbro show view

Simplified the show view with a custom function that modifies the response object. That way no weird db or columns need to be added.
If a social profile is removed it will be reflected in both the project and projectVerificationForm.

@MoeNick
Now we show social profiles in admin-bro, ( this was missed in weekly demo)


Base settings erroneously added when only setting for configs

I have a spec that sets CODE_SIGN_IDENTITY separately for a few configs, and does not set it at the base level.
We previously had a compiled version of xcodegen checked into our repository, which was version 2.7.0. The project generated successfully with this version with the expected settings:

I just upgraded our repo to use homebrew to manage installing xcodegen, and removed that compiled version we had checked in. Now, with version 2.18.0, we get a bogus base value set for this setting, which breaks our deploys at the code sign step:

I've verified this by feeding the same spec into both versions. You can see where the new unexpected settings are added at the target level. I expect this setting only to be set at the project level, and only for the configurations, not at the base level.

I just tried bisecting between 2.7.0 and 2.18.0 in your history, but everything always produces a result like my second screenshot, so the 2.7.0 build we have in our repo history is probably a red herring. I will try to create a simple example that reproduces the problem.

OK, I'm not able to reproduce the original case any longer with any build. There must have been other changes somewhere in the process with how we define our settings per configuration. I'm not able to figure out why these are being set on the app target instead of just the project, which is where we define them in our spec.
I wound up fixing this for us by defining the per-config settings on the app target directly instead of at the project level.

Here's a sample json that reproduces the settings in the second screenshot, where I expected it to be like the first screenshot. I pared this down from the actual spec we use:
{
    "configs": {
        "debug": "debug",
        "dev": "release",
        "prod": "release",
        "profile": "release"
    },
    "fileGroups": [],
    "name": "MyApp",
    "options": {
        "bundleIdPrefix": "my.prefix",
        "createIntermediateGroups": true,
        "indentWidth": 4
    },
    "settings": {
        "base": {
            "CLANG_ENABLE_OBJC_WEAK": true,
        },
        "configs": {
            "debug": {
                "CODE_SIGN_IDENTITY": "Apple Development: MyCompany Fastlane (<redacted>)",
            },
            "dev": {
                "CODE_SIGN_IDENTITY": "Apple Distribution: MyCompany Inc. (<redacted>)",
            },
            "prod": {
                "CODE_SIGN_IDENTITY": "Apple Distribution: MyCompany Inc. (<redacted>)",
            },
            "profile": {
                "CODE_SIGN_IDENTITY": "Apple Development: MyCompany Fastlane (<redacted>)",
            }
        }
    },
    "targets": {
        "MyApp": {
            "platform": "iOS",
            "settings": {
                "base": {
                    "ASSETCATALOG_COMPILER_APPICON_NAME": "AppIcon",
                    "DEVELOPMENT_TEAM": "<redacted>",
                    "ENABLE_BITCODE": false,
                    "PRODUCT_NAME": "MyApp"
                }
            },
            "sources": [],
            "type": "application"
        }
    }
}

Ah, I just reread some docs and found settingPresets. When I set it to "none" I get the desired result. We never had this set before, the only thing we changed was adding the "configs" dict to the spec, both the root level and under "settings".


Heroes heroesxp "add"

heroes command to add experience seems to be broken
it does not add more experience working as a set
If I run this command several times does not change the experience
"- heroesxp add Vampiro quantity:10"
Srry for my bad english
http://mcmonkey.org/paste/28708

I'm looking into this! :)

It would seem that the XP is being set. Going to try figure out why.

Fixed :D


Use feature detection instead of platform detection if possible

The dart-sass filter is currently non-functional on some PCs due to a problem with the tty-platform gem that we use to detect whether we are on Windows. (https://github.com/nanoc/nanoc/issues/1703, https://github.com/piotrmurach/tty-platform/issues/1)
While this will probably resolve itself in time, it's a bit brittle to rely on a platform string that might break as new versions of ruby are released. Instead I think it would be better to feature detect that we are on a Windows file system, like this:
    def windows_fs?
      ::File::ALT_SEPARATOR == "\\"
    end

At the moment the dart-sass filter seems to be the only place in nanoc we use this windows detection, I think? For detecting other windows related properties we may need to add additional helper functions, but in general I think this would be preferable to depending on a platform to be reliably detected and to infer functionality from that.

There is a possible fix in #1718. Can you check whether this works for you?

Thanks, looks good to me. I don't have access to a PC with git on it though, so can only verify it after release I'm afraid.


Type elimination and CFA/Type Guards

It probably was discussed in the past - but couldn't find.

Could TS not eliminate types and information about original type?

type EncryptedToken = 'TokenA' | 'TokenB' | string

function generateToken():EncryptedToken { ... }

// In some other module:
const token = generateToken() {} // Type: string

so TS (even if its 'working as intended' from compiler point of view) not only eliminated important information for developer that generateToken function can return 'TokenA' | 'TokenB' | string but also removed original type name EncryptedToken which could be also important for developer to understand the code - leaving user with just string
so
1a: Could TS keep the type: 'TokenA' | 'TokenB' | string  as 'TokenA' | 'TokenB' | string  and not downgrade to string?
Theoretically equivalent (from user point of view) code:
enum Test { a, b, c }
type B = Test.a | Test.B | number // Type: Test.a | Test.B | number

retains the type
but
type C = 0 | 1 | number // Type: number

does not
1b: Could TS show the original type as well?
const token = generateToken() {}

Instead of showing type as string could it show:
type: EncryptedToken or
type: EncryptedToken = string (if 1a is not possible) or
type: EncryptedToken = 'TokenA' | 'TokenB' | string (if 1a possible)

Now because of 1a the following code will not work:
type A = 0 | 1 | number
function test(a:0|1) {}
let a:A
if (a == 0 || a == 1) {
  test(a) // Error: number is not assignable to 0 | 1
}

But this code will work:
EDIT: This code works because enum is pretty much treated as number (https://github.com/Microsoft/TypeScript/issues/11559):
const enum Enum { a0, a1, a2 }
type A = Enum.a0 | Enum.a1 | number
function test(a: Enum.a0|Enum.a1) {}
let a:A
if (a == 0 || a == 1) {
  test(a)
}

Problem is that I want to use the same pattern for strings - but there are no enum strings (yet https://github.com/Microsoft/TypeScript/issues/1206#issuecomment-240581743)

I guess I'm not understanding what additional information is conveyed in a type "foo" | "bar" | string vs. just string. Either way, any string is a possible value, and "foo" | "bar" | string does not in any way provide more type safety than string.

@ahejlsberg
Here is an example - I know that I could write that piece of code in different way (or to use as) to avoid errors) -  it's just an example:
// Just an alias
type UserGuid = string
type FindBy = 'cost' | 'size' | UserId

function getUserInputFromCommandLine():FindBy {
  console.log("Type: cost | size | {UserGuid}")
  return 'cost' // user input taken from command line
}

const by = getUserInputFromCommandLine()

function findBySpecificKind(kind: 'cost' | 'size') {

}

function findByUserId(userId: UserGuid) {

}

if (by == 'cost' || by == 'size') {
  findBySpecificKind(by) // ERROR - string not assignable to 'cost' | 'size'
}
else {
  findByUserId(by)
}

So I was hoping to improve user experience in 2 ways:

Even if for compiler: "foo" | "bar" | string is the same as string - for user seeing that by or getUserInputFromCommandLine() returns type 'cost' | 'size' | UserGuid gives much much more information - than the current string. So kind of like self-documentation of the code

If 'foo' | 'bar' | string wouldn't be simplified to string then I guess the following would allow user to work: (kind of like 'foo' | 'bar' gets priority over string)

if (by == 'cost' || by == 'size') {
  findBySpecificKind(by) // ERROR - string not assignable to 'cost' | 'size', but CFA could figure out that it matched string literals in (non simplified) type definition
}

But if you feel like this makes no sense - feel free to close it

Ok, I think we should investigate is having equality comparison operations narrow from type string. For example:
const by: string = ...
if (by == 'cost' || by == 'size') {
  findBySpecificKind(by);  // by should narrow to "cost" | "size" here
}

This was already proposed in #11306, so I will close this one as a duplicate.


Update spago's run command

spago run currently depends on a file that requires Main, however this leads to the following error:
require('/Users/mark/code/working-group-purescript-es.github.io/output/Main').main()
^

Error [ERR_REQUIRE_ESM]: require() of ES Module ./output/Main/index.js from ./.spago/run.js not supported.
Instead change the require of index.js in ./.spago/run.js to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (..spago/run.js:3:1) {
  code: 'ERR_REQUIRE_ESM'
}

Node.js v17.2.0

The file ./.spago/run.js currently looks like this:
#!/usr/bin/env node

require('/Users/mark/code/working-group-purescript-es.github.io/output/Main').main()

The following replacement works as long as its filename ends in .mjs:
import { main } from "/Users/mark/code/working-group-purescript-es.github.io/output/Main/index.js"
main();

Note that it's required to specifically specify /index.js at the end.

Per Node 14 docs:

Node.js treats JavaScript code as CommonJS modules by default. Authors can tell Node.js to treat JavaScript code as ECMAScript modules via the .mjs file extension, the package.json "type" field, or the --input-type flag. See Modules: Packages for more details.

The --input-type is only for node --eval or inputs from stdin. Is there a reason why Spago creates a run.js file in the first place?

For example, this works:
$ spago build
$ node --input-type=module --eval "import * as Main from \"./output/Main/index.js\"; Main.main();"
🍝

I have updated the current branch with this proposal. We can close this issue now I think


Retain RGB case when editing

Editing e.g. RGB(11,22,33) in an XML file produces rgb(11 22 33). Is it possible to retain case or could a switch be provided? Thanks.

Duplicated https://github.com/jeronimoek/color-picker-universal/issues/103

Duplicated #103

This isn't a duplicate. Note the case change above - RGB -> rgb.
I'm editing an XML file which only accepts RGB so the fact this extension outputs rgb is breaking it.

My bad
In this case, this is not handled yet by the extension, so this will require some development involved. At the moment, I don't have much time available, but eventually, I might develop this

No problem - I can see why it looked like a dupe.
I thought it might be on the VS Code side but hoped it might be in the scope of your extension. Thanks for considering it.
And thanks for your time and help. All the best.


Cannot open right click settings

I think what is happening is that whenever I right click in command prompt it automatically copies (I am using windows 11 if that helps) and I can't seem to turn this feature off. If there is another way of opening the settings that would be really helpful because I can't use flm right now which is really annoying. Thanks!

Thank you very much I will try this later today, this is under dev settings in windows right?

Lol, I was expecting you solved the issue by yourself, but I’ll help you out!
If you’re using the Windows Store Terminal, you can’t open the settings directly via right-click. To access them, you need the legacy terminal. Another way to open the legacy terminal is by running flm.exe as an administrator.

Thank you! Your original message solved the problem.


function ref to static method/constructor of generic type not marked as type function

For this class:
class Box<Element> {
    shared static Box<Element>[2] pair(Element x, Element y)
            => [create(x), create(y)];
    shared new create(Element element) {}
}

I can write a ref to its constructor or static method like this:
value fun = Box.pair;
value fun = Box.create;

But these get assigned rubbish types.

Fixed.

@gavinking I think this is causing an SDK build failure with an error referencing a static member of a Java type - https://github.com/ceylon/ceylon-sdk/blob/358ad350376c8fac961375d8b51310a746996e75/source/ceylon/http/server/internal/DefaultServer.ceylon#L134
See also http://docs.jboss.org/xnio/3.0.4.GA/api/org/xnio/class-use/BufferAllocator.html
[ceylon-compile] /Users/jvasileff/Dropbox/Repos/ceylon/ceylon-sdk/source/ceylon/http/server/internal/DefaultServer.ceylon:134: error: argument must be assignable to parameter 'arg0' of 'ByteBufferSlicePool': '<B> given B satisfies Buffer => BufferAllocator<ByteBuffer>' is not assignable to 'BufferAllocator<ByteBuffer>?'
[ceylon-compile]                         ByteBufferSlicePool(BufferAllocator.directByteBufferAllocator,
[ceylon-compile]                                             ^
[ceylon-compile] /Users/jvasileff/Dropbox/Repos/ceylon/ceylon-sdk/source/ceylon/http/server/internal/DefaultServer.ceylon:134: error: type functions are not supported on the JVM: 'BufferAllocator' is generic (specify explicit type arguments)
[ceylon-compile]                         ByteBufferSlicePool(BufferAllocator.directByteBufferAllocator,
[ceylon-compile]                                                             ^
[ceylon-compile] /Users/jvasileff/Dropbox/Repos/ceylon/ceylon-sdk/source/ceylon/http/server/internal/DefaultServer.ceylon:134: error: type functions are not supported on the JVM: 'BufferAllocator' is generic (specify explicit type arguments)
[ceylon-compile]                         ByteBufferSlicePool(BufferAllocator.directByteBufferAllocator,
[ceylon-compile]                                                             ^


Add edpm_reboot_strategy to reboot role

Add edpm_reboot_strategy to reboot role that defines if reboot should be started or not. There are three modes: auto, never and force. The default is auto.
Add also more generic check for existence of openstack configs for already
deployed nodes, both old tripleo and new edpm node.

/lgtm

/lgtm

/approve

What is Tide waiting for here in terms of approval? Does it need to be approved by @SeanMooney specifically as the comment above suggests? :)

Ah i guess Mikolaj or i would have to be on the approvers list.

no it just requries approval form anyone in the owners file
https://github.com/openstack-k8s-operators/edpm-ansible/blob/main/OWNERS
or OWNERS_ALIASES
https://github.com/openstack-k8s-operators/edpm-ansible/blob/main/OWNERS_ALIASES

/approve

If there are concerns how this change works for adoption I link change that tests the change in pre-adoption phase.
https://github.com/openstack-k8s-operators/data-plane-adoption/pull/459/files

So that pr is not depending on this pr so it's not testing it and it's also failing ci which is not very encouraging
I'll remove the requested change to allow others to approve but I'm still unsure that how reboot are being done are correct

the os-reboot will be used for kernel updates or other changes that require a host reboot as part of day two maintenance.
it feels wrong to require force to be used in that case
auto should work asuimg a prior task has marked the node as needing reboot.
the intended workflow is that you would do a separate deployment including the os-reboot service with --limit to reboot subsets of host that you have drained of workloads in batches.
in that workflow we should not need to update the ansible_vars on the nodeset to force.
if we cant support that usecase we cant do minor updates properly.

i will file a jira bug for the fips issue

So that pr is not depending on this pr so it's not testing it and it's also failing ci which is not very encouraging
Yes, the pr wasn't testing it. I made a patch, but there was missing depends-on. I fixed it and new results are https://github.com/openstack-k8s-operators/data-plane-adoption/pull/459#issuecomment-2133562264
A non-ceph job failed during adoption, it passed pre-adoption validation with reboot.

filed OSPRH-7301


Add links to relevant documenation

please add links to help us get started on these idea, e.g., integrating PowerApps sound cool, but i'm not really sure what is meant by this. Providing links to articles about the various examples would be useful.

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

ID: ffb71344-2497-490c-8670-d5e9b6b3421b
Version Independent ID: 1e01ad06-e508-44ef-43a2-c60d969d89fa
Content: Why Microsoft Search
Content Source: MicrosoftSearch/why-microsoft-search.md
Service: mssearch
GitHub Login: @dawholl
Microsoft Alias: dawholl

@DeanGross Thank you for your feedback. Please see the PowerApps section in Manage Bookmarks page:


Revert latest OpenAPI updates

This is causing a live site issue because DevX API reads OpenAPI document directly from GitHub for snippet generation. Reverting to last known good state, i.e. last week's update. We will hit this issue again tomorrow when the generation schedule kicks in.

Revert "Update clean metadata file with 78287 [skip ci]"
Revert "Update clean metadata file with 78287 [skip ci]"
Revert "Update clean metadata file with 78287 [skip ci]"
Revert "Update clean metadata file with 78287 [skip ci]"
Revert "Updated v1.0_metadata.xml"
Revert "Updated beta_metadata.xml"
Revert "Update clean metadata file with 78286 [skip ci]"

cc: @andrueastman @irvinesunday @baywet to double check if reverting causes any issues for stuff that rely on OpenAPI document. At the moment, parsing of the document seems to be failing.
cc: @nikithauc @rkodev @fey101

mitigates https://github.com/microsoft/kiota/issues/1668

kiota command mentioned in the original issue works with the OpenAPI document from this branch:
C:\github\kiota\src\kiota\bin\Debug\net6.0\kiota.exe -d https://raw.githubusercontent.com/microsoftgraph/msgraph-metadata/zengin/revert/openapi/v1.0/openapi.yaml --language typescript -o C:\test_typescript -c GraphBaseServiceClient -n MicrosoftGraph

Thanks for the quick revert, I've been root causing this, have updated all the related issues (tactical) and I'll be posting a recap here (strategic)


keybindings stopped working.

Applied recent update and keybindings have stopped working.  They do open a terminal, but not at the root of the project.  I didn't realize how convenient this tool was until it stopped working.  Any help would be greatly appreciated.  Thank you.

see #54 and possibly #55

Thank you for the quick reply. Issue #55 above work brilliantly.  Thanks again!!


upgrade docker image for changed dependencies …

… and add a simple docker file which builds PDO code during build (in simulator mode only, though, see comments at end)

works for me


Pagination /Back/Previous buttons also have problems on modifier page

Issues
Also getting the same problem with the Back/Next, and pagination errors in modifers page. Must hit refresh to fix, and seems it happens as much as with slots and actions.

No errors in  console or git
0.25 release
local
win 10 pro

@dcalvom I was seeing this as well when on master. Have you been able to reproduce?

seems to be fixed for 27.1, but still testing

not fixed for 27.1 after retesting, error occurs deleting keywords, and it going back to dialouge page

Closed by 3adc7cbd57433d4a79e16569249406e39543ba3b


[BUG] band-solidity package isn't updated with mainnet oracle addresses

band-solidity currently in development phase. All function work well in mainnet. Please used Oracle(0xD5D2b9e9bcd172D5fC8521AFd2C98Dd239F5b607) instead of FINANCIAL. The new version of band-solidity that check network will publish soon.

band-solidity is currently in development phase. However all function work well in mainnet, just used Oracle(0xD5D2b9e9bcd172D5fC8521AFd2C98Dd239F5b607) instead of FINANCIAL. The new version of band-solidity that check network will publish soon.


A request for evaluation script

Hello,
Could you please share the script used for evaluation? The obtained results may differ with different evaluation scripts.
Thanks a lot!
Best wishes,
Lei

Hi,
The evaluation code should be very straightforward: For topic coherence evaluation, you could pass the output topics to the evaluation pipeline of the gensim library. For document clustering, you could refer to the README file. I hope these help!
Best,
Yu

Hello,
Thanks for your reply.
I wrote a function using gensim library as you mentioned, which was put into TopClusUtils class:
from gensim.models.coherencemodel import CoherenceModel
from gensim.corpora import Dictionary

def compute_coherence(self, data_dir, res_dir):
    topics = []
    with open(os.path.join(res_dir, 'topics_final.txt'), encoding='utf-8') as f:
        for line in f.readlines():
            topic = line.split()[2].split(',')
            topics.append(topic)

    docs = []
    with open(os.path.join(data_dir, 'texts.txt'), encoding="utf-8") as f:
        for line in f.readlines():
            doc = self.tokenizer.tokenize(line)
            docs.append(doc)

    dct = Dictionary(docs)
    corpus = [dct.doc2bow(doc) for doc in docs]
    UMass_cm = CoherenceModel(topics=topics, corpus=corpus, dictionary=dct, coherence='u_mass')
    umass = UMass_cm.get_coherence()

    UCI_cm = CoherenceModel(topics=topics, texts=docs, dictionary=dct, coherence='c_uci')
    uci = UCI_cm.get_coherence()
    print('UMass: ', umass, 'UCI: ', uci)

And I called it using trainer.utils.compute_coherence(trainer.data_dir, trainer.res_dir), but got results UMass:  -5.8793029613305725 UCI:  -3.1203332131498644.
I wonder if there is any issue within the code. Thanks in advance.
Best wishes,
Lei

Hi,
The results look quite off from those reported in the paper, and I believe there are a few points you could double check:

Check the output topics of TopClus; if they do not make sense, it's likely to be a problem during model training;
UCI is an extrinsic metric which evaluates the topics on an external general corpus such as Wikipedia instead of the training corpus, so you'll need to pass in a general corpus;
We evaluated the results with the top-5 words of each topic, and you'll need to specify this in the gensim function call.

I hope these are helpful.
Best,
Yu

Hello,
Thanks for your quick reply.
Um, I used the training corpus for evaluating UCI score and top-10 words of the topics. I will fix this and see the results.
Thanks for your tips again.
Best,
Lei

Hello,
I have fixed the issue by evaluating topic coherence with top-5 words, but the UMass score dropped to -6.49. As for the UCI score, I cannot find out how to evaluate the topics on Wikipedia with gensim library. Should I pass the whole Wiki data into the texts parameter of CoherenceModel?
Looking forward to your reply. Thank you very much!
Best,
Lei


chore(deps): :arrow_up: update dependency postcss-import to v16

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

postcss-import
~15.1.0 -> ~16.0.0

Release Notes

postcss/postcss-import (postcss-import)
v16.0.0
Compare Source

BREAKING: Require Node.js v18+ (#550, #551)
BREAKING: Signifigant rewrite, with small behavioral tweaks in a number of edge cases
Support for @supports conditional imports added (#532, #548)
When skipDuplicates is false, handles import cycles correctly (#462, #535)
Add warnOnEmpty option to allow disabling warnings for empty files (#84, #541)
Use proper node.errors (#518, #540)

Huge thanks to @romainmenke for all the hard work he put into this release.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN cli npm v10.2.5 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@angular/platform-browser
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@angular/forms
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     2 more (@angular/platform-browser-dynamic, @angular/router)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-01-03T02_59_06_807Z-eresolve-report.txt

npm ERR!


Add an option to get defaults from a configuration file

See this comment
Can we add an option to the api that takes a list of filenames and loads options from that, which can then be overridden by the commandline provided.
example API; function setconfigfiles(filenames)
Provide a list of filenames as;

.\my_app_name.settings     --> project settings, overrides user settings
%USERNAME%\my_app_name\user_config.settings   --> user overrides system
%ALLUSERS%\my_app_name\system_config.settings     --> system wide config

Highest level priority would be the options on the commandline

Closing this since it's been implemented. :)


Update extensions to Node 14

[x] storage-resize-images (https://github.com/firebase/extensions/pull/657)
[ ] delete-user-data (https://github.com/firebase/extensions/pull/661)
[ ] firestore-bigquery-export (https://github.com/firebase/extensions/pull/662)
[ ] firestore-counter (https://github.com/firebase/extensions/pull/664)
[ ] firestore-send-email (https://github.com/firebase/extensions/pull/665)
[ ] firestore-shortern-urls-bitly (https://github.com/firebase/extensions/pull/667)
[ ] firestore-translate-text (https://github.com/firebase/extensions/pull/668)
[ ] rtdb-limit-child-nodes (https://github.com/firebase/extensions/pull/669)

Once this migration is done, it would also help to merge https://github.com/firebase/extensions/pull/663, which adds a new Cloud Functions region

Completed


Name is really generic

Can we name this something more identifiable?

Bumping this again.

Bumping again.

Hi!  Sorry for the late response.  I was feeling some name fatigue at the time, having just changed the name from Crazytown due to the fact that some people felt uncomfortable spreading that name around, for some reason :)
This is an experimental cookbook meant to show this stuff, and will go away soon (as we will soon make core Chef resources easier to write and read), at which point I'll deprecate it.  Also, I don't know if you got that impression or not, but the name "resource" is not intended to imply that this is a Chef official position on resources, or anything like that (sorry if it gave that impression).
Given a few more days I should have a few RFCs up that we can chew on.  (I've been trying to break it up as much as possible rather than submitting a single massive one.)  The RFC process will involve bits from Poise and Crazytown, and we'll go 'round and try to reach something that makes sense for everyone.
Is that OK for now?  If I can avoid changing the name and inconveniencing the people using it for a few months, I'd like to :)

It is both unhelpful for communication to have something named "the Chef resource cookbook" and is definitely a shot across the bow for me as someone that both has an actively used competitor and has zero plans to participate in any core merge of their code. If your reason to put off renaming it is "I'm going to write an RFC to make Poise obsolete" I find that even more presumptuous, even if you think you are doing it with the best of intentions I prefer to keep my code out of Chef core for my own benefit. If you want to keep the name, at a minimum please move this repo to your personal GitHub account instead of the Official™ chef-cookbooks.

Just as it's logical and natural to name a cookbook "apache2" that manages Apache, it makes sense to me that @jkeiser would simply be inclined to name a cookbook "resource" that manages resources.
@coderanger, to whatever degree @jkeiser's work is a perceived or real threat to the success of Poise, it's not intended to create that harm. Your "shot across the bow" comment sounds like you're accusing @jkeiser of malice, which I think is both unreasonable and unkind.
The goal of this cookbook would appear to be solely making it easier for users of Chef to extend Chef by making it easier to create resources, and thus get more benefit from Chef. If you feel you can create the best solution for this by maintaining full control, and don't want to work with others to come up with an open source solution in core, you are of course entitled to do so. And keep your code, of course. But it would be absurd to intentionally not write good features into Chef that everyone would want to use to support that effort.
It's often inconvenient that the company goes by the same name as the project, but it does. This cookbook isn't presented at all as being an official thing that everyone should use, it's presented as an experimental cookbook written by a Chef Software employee, and development occurs in the company github repository for cookbook development. I'm not convinced the situation merits @jkeiser moving or renaming this cookbook, especially given its development status.

This name has previously been justified to me as correct because this cookbook seeks to be the default way to write Chef resources. I hope you can see how I would take that as a pretty direct challenge. Conflict for the greater good is totally a thing I support, but the "Chef" name brings with it a lot of implicit authority and as such it is a battle I am unlikely to make any headway in. If I know in advance I'm going to make little to no headway in improving the, let's be honest, abysmal state of most cookbooks I'm certainly disinclined from smashing my head against that wall indefinitely. Comparing this cookbook to "apache2" implies they cover similar amounts of their respective problem space and I would say that is demonstrably false. This cookbook does not represent any kind of communal "best practices" for writing resources, it is an experiment by one person in much the same way Poise is, the difference being that I specifically try to not oversell my code as anything more than one dude's helper library.

Or to be tl;dr-ish, the way we talk about things is important and naming this "chef-cookbooks/resource" certainly feels like it is to the exclusion of others.

I hear ya. The apache2 comparison was trying to visualize what I think @jkeiser was thinking when he was sitting at his computer. "So, chef generate cookbook... uhhh....... resource. yeah." I think he's been good in the past about coming up with unique names, but then they have a history of getting changed for various reasons and he's probably feeling some fatigue from the name bikeshed. There's apparently no way for @jkeiser to ever name something and have it been free from complications. :)
There's a constant push-pull to find the right balance with what gets implied by the chef name being associated with something. I personally dislike twitter bios that say things like "thoughts are my own" because I think "duh. of course they are. corporations aren't people." but not everyone thinks that way and we've dealt with that one in a big way recently. What's really important is there wasn't any intentional abuse/misuse of the chef name here, we just fell into it in the course of getting work done.

Closing this as this repository is now deprecated


net/http/httputil: DumpResponse return error when ContentLength=2 with Body length 0, but it's a response for http.MethodHead request

What version of Go are you using (go version)?

$ go version
go version go1.15.4 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/root/go/pkg/mod"
GONOPROXY="*.ucloudadmin.com"
GONOSUMDB="*.ucloudadmin.com"
GOOS="linux"
GOPATH="/root/go"
GOPRIVATE="*.ucloudadmin.com"
GOPROXY="https://goproxy.cn,direct"
GOROOT="/root/sdk/go1.15.4"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/root/sdk/go1.15.4/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build737726766=/tmp/go-build -gno-record-gcc-switches"

What did you do?

package main

import (
	"net/http"
	"net/http/httptest"
	"net/http/httputil"
	"testing"
)

func serveHTTP(w http.ResponseWriter, r *http.Request) {
	w.Header().Add("Content-Length", "2")
	switch r.Method {
	case http.MethodHead:
	default:
		w.Write([]byte("{}"))
	}
}

func TestDumpResponse(t *testing.T) {
	t.Run("Get", func(t *testing.T) {
		rw := httptest.NewRecorder()
		r := httptest.NewRequest(http.MethodGet, "/", nil)

		serveHTTP(rw, r)
		raw, err := httputil.DumpResponse(rw.Result(), true)
		if err != nil {
			t.Errorf("DumpResponse: (%v)\nRaw: %s", err, string(raw))
		}

	})
	t.Run("Head", func(t *testing.T) {
		rw := httptest.NewRecorder()
		r := httptest.NewRequest(http.MethodHead, "/", nil)

		serveHTTP(rw, r)
		raw, err := httputil.DumpResponse(rw.Result(), true)
		if err != nil {
			t.Errorf("DumpResponse: (%v)\nRaw: %s", err, string(raw))
		}

	})
}

go test main_test.go

What did you expect to see?

--- FAIL: TestDumpResponse (0.00s)
    --- FAIL: TestDumpResponse/Head (0.00s)
        main_test.go:38: DumpResponse: (http: ContentLength=2 with Body length 0)
            Raw:
FAIL
FAIL    command-line-arguments  0.003s
FAIL

What did you see instead?
ok      command-line-arguments  0.003s

i think you may change httputil.DumpResponse(rw.Result(), true) to httputil.DumpResponse(rw.Result(), false)

/cc @bradfitz @empijei

It's not clear to me what you're trying to convey.
You wrote
What did you expect to see?

--- FAIL: TestDumpResponse (0.00s)
    --- FAIL: TestDumpResponse/Head (0.00s)
        main_test.go:38: DumpResponse: (http: ContentLength=2 with Body length 0)
            Raw:
FAIL
FAIL    command-line-arguments  0.003s
FAIL

What did you see instead?
ok      command-line-arguments  0.003s

But if I run the tests myself I obtain the exact opposite result. I guess you meant to say that you expected "ok" and got the error instead.
Assuming my guess is right, your bug is saying that DumpResponse is erroring on an invalid response (CL mismatch with body) and you didn't expect it to?
Why did you expect httputil to work on inconsistent responses?


View behind the FloatingActionMenu is not clickable|scrollable

DETAILS - I have placed FloatingActionMenu over RecyclerView, I have set the width and height of FloatingActionMenu both to wrap_content, I have 2 FloatingActionButton inside FloatingActionMenu.
PROBLEM- The area behind the FloatingActionMenu is not scrollable due to which I'm unable to scroll my RecyclerView from the area covered by FloatingActionMenu.

Why this is issue is closed while there is no solution provided?


add sayo beatmap mirror site support

add the support for https://osu.sayobot.cn/
The beatmap mirror site in China
Direct search function not implemented yet

[x] Ranked status
[x] keyword search
[ ] download
[ ] diff

I will try to finish it soon
Thanks for attention

hey - i'm going to close this for the time being
if you'd like to give this another shot, feel free to re-open a pr!


dependencies in @types/styled-system

Why in @types/styled-system dependence on styled-components ? :confused:

That package isn’t part of this repo, you should ask the authors of the package