Can't pair/add devices properly anymore

Hey!
For some reason I can't properly pair/add anything anymore, despite it working pretty flawlessly the past few months. I mostly use aqara motion and temp sensors, as well as some ikea tradfri spotlights, all of these have worked great, up until now when I noticed that one motion sensor wasn't updating so I decided to repair it, and all hell broke lose.
I keep getting the message
Device with modelID 'undefined' is not supported.
after I get the "device connected" etc, it just becomes a "unknown" device when restarting the addon. It doesn't properly pair it, even if it's literally next to the coordinator.
What I tried doing to troubleshoot was:
Tried basic restart of the addon/reset stick, plug stick in plug out and then restart etc, but it keeps giving same messages. I also removed the device with the mqtt command, removed it from database, but still same issues upon re-pairing.
I then went the complete remove/reset route:

Remove devices/entities in hassio entity registry (even removed mqtt broker setup altogether after removing in entity registry) to get a clean slate, all traces of all my zigbee2mqtt devices were gone in hassio when fully rebooting the system.
uninstalled addon as well and entirely deleted all traces off it like the folders etc, then re-installed it, and I tried with both regular and dev versions.

Running latest hassio as well.
But it keeps giving the same results, I get the "device connected" message with its device id number but it then spams with the Device with modelID 'undefined' is not supported. messages, even when just pairing one simple device such as the aqara motion sensor, a aqara temperature sensor, or a cc2531 router. I never had this issue before, after several pairings/re/pairings.
I don't know what to do or try now anymore, any suggestions/tips?
Thanks in advance!

Well I went as far as reinstalling my entire hassos from scratch, and only adding zigbee2mqtt, starting simple with adding one device, and still same thing, devices gets "added/connected" quickly but not fully, the neverending Device with modelID 'undefined' is not supported keeps spaming the log. Don't know what else I can do now :/

Can you try reflashing the original coordinator stick?

I'd try that next time there is a need to redo stuff, all the troubleshooting took pretty much entire day, and re pairing everything is a bit tedious, so I'd rather not touch anything for now since it's working :)
It was just weird since the original stick was flashed with the same firmware and had worked so well this far.

I've the same problem only with Ikea Tradfri lamps, any other devices work.
Solution?
I don't have the possibility of reflash the firmware...


SKIA rendering not support HDPI

When the BUILD_SKIA option is enabled, the rendering quality degrades significantly on high-DPI displays, leading to noticeable aliasing or jagged edges in the rendered graphics.

Which branch (openmath/master) do you use?

master currently.
I'm attempting to work with the "openmath" branch, but I'm unable to successfully compile it. Skia requires support for SkParagraph, which cannot be directly built using vcpkg. I'm still in the process of trying to compile it.


invalid school name

the schoolname from the webite is: OSZ+IMT
i think the + in the schoolname is not working here?
Fehler beim Login: Failed to login. {"jsonrpc":"2.0","id":"error","error":{"message":"invalid schoolname","code":-8500}}

Use spaces instead of plus. That worked for me


Wrong culture on 404 page

CurrentUICulture, CurrentCulture and PreferredCulture is the wrong language when rendering the 404 page. The main language on our sites are norwegian. When being on the english verison of the page and going to a page that doesn't exist (www.oursite.no/en/asdasd/) the various culture variables change to norwegian somehow. It doesn't work to manually set these to english in the error controller either as it seems to be overritten at a later stage.
The NotFoundPage is loaded correctly in english with an english 404 message, but the header, menu-links and footer is in norwegian. This seems to be due to @Html.Translate using CurrentUICulture to pick lang file.
On www.oursite.no/en/:

On www.oursite.no/en/asdasd (404):

Is your 404 page an Episerver page or just ASP.NET?

The correct english page created in Episerver is fetched in the error controller, stored in a view model which is returned like this:
return View("~/Views/Error/Error404.cshtml", viewModel);

Is this intended behavior? If not, do you get the same result if you write code for displaying the cultures? Also, do you know how to fix this? In some solutions, overwriting the cultures works, but for some other sites it does not, as it gets overwritten back again.


[WIP] UI Test suits

Describe your changes :

I worked on the ..... because ...

Type of change :

+- [x] Bug fix
+- [x] New feature
+- [x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [x] Documentation

Frontend Preview (Screenshots) :

For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] All new and existing tests passed.

Reviewers

+
+

Closing as unable to track. Creating another PR


How do I synchronize objects of the same Array , with the index on different pages?

Hi,
I put the images on different pages using the ng-repeat and the custom filter | filterBy : [ 'id '] , ' ' " , only just the image of the first object in the array of the list is expanded correctly , the other I need go adding +1 , +2 , +3 and successively. The third object in the array only magnifies the image properly if I add ($index+2) , eg .
 $scope.Images =
[
   { id="1", url: "/images/img-1.jpg", src: "/images/img-1.jpg" },
   { id="2", url: "/images/img-2.jpg", src: "/images/img-2.jpg" },
   { id="3", url: "/images/img-3.jpg", src: "/images/img-3.jpg" }
];

The object that is the first in Array $ scope.images list functions normally

The object that is second on the list of Array $ scope.images only works if I add +1 to $ index

The object that is third on the list of Array $ scope.images only works if I add +2 at $ index

I wonder if this directive works by placing the images (objects) , the same array, in different pages , if so, how could do it ?
Thanks.

In each ng-repeat, the $index starts at 0. To get the correct index in your images array, you can use the image id instead:

This assumes your ids are always ordered like 1, 2, 3, 4, 5, ...

I use in decreasing order 5 , 4, 3 , 2, 1 .Organizei in ascending order to facilitate understanding. 're Almost working, need your help to complete this task.

Try changing your controller method to find the array index based on the given image object:
$scope.openLightboxModal = function (image) {
  Lightbox.openModal($scope.images, $scope.images.indexOf(image));
};

Pass in the image:

It worked perfectly fine. Thank you for excellent help , I will be promoting his work. hug!


Invoking AL from control add-in does not work if there is a Message call during system initialization

Symptoms
If there is a Message call inside an OnAfterInitialization event subscriber, any control add-ins on the page that was loading won't call AL during InvokeExtensibilityMethod invocations.
More info
I've created a repo that illustrates the problems with minimum code. The README.md file there explains the entire setup and how to repeat:
https://github.com/vjekob/bc170ctrladdinbug

I don't mean to be rude, but did anyone even take a look at this? This has been a very breaking change for our customers.

I am investigating the issue, but is not clear to me from the bug report what version this used to work in?

I am investigating the issue, but is not clear to me from the bug report what version this used to work in?

I am investigating the issue, but is not clear to me from the bug report what version this used to work in?

It's BC170, Business Central 2020 Release Wave 2 Update.

I am investigating the issue, but is not clear to me from the bug report what version this used to work in?

It's BC170, Business Central 2020 Release Wave 2 Update.

I think Jesper's question is: did this work in any version of Business Central before 17.0?

I think Jesper's question is: did this work in any version of Business Central before 17.0?

Yes :) It was broken in BC 17.0.

Yes :) It was broken in BC 17.0.

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 21747 and VS Code Extension Version .
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/

Thanks, Jesper and the team!


[DO NOT MERGE] Emitter Framework

Very Experimental emitter framework

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@typespec/compiler
:x:@typespec/efnext-cli-sketch
:x:@typespec/http

Show changes

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


pass in events as an array of strings

Events should be passed in so it's easy to customise what events will reset the timer


feat(client/api): validate ms users

These are suggested changes from MS team.
Adds a way to link (and unlink) Microsoft usernames to freeCodeCamp accounts.

adds a new collection to store the MS usernames
adds two new endpoints, POST /user/ms-username (link) and DELETE /user/ms-username (unlink)

Adds a new view type for the trophy challenges, and a new way to submit them

Once a user account is linked, they just click the verify trophy button and it checks the MS API to see if they've earned it.
adds new endpoint POST /ms-trophy-challenge-completed to submit trophy challenges

And some other suggested fixes from MS team
TODO: Add all this to API project board.
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Quick Question:
Are we sure we want to allow multiple Microsoft usernames per account?

Not this PRs fault, but I failed the exam, and still have the tick:

Refreshing the page removes the tick, but it should not be put there.
Cannot claim certification, though

Lets go with this then. I will look at the exam tick issue on the next PR.


Legacy FCM APIs will be removed in June 2024

These endpoints will stop working next month:
const FCM_SUBSCRIBE = 'https://fcm.googleapis.com/fcm/connect/subscribe'
const FCM_ENDPOINT = 'https://fcm.googleapis.com/fcm/send'
https://firebase.google.com/support/faq#fcm-23-deprecation
https://firebase.google.com/docs/cloud-messaging/migrate-v1

Thanks for bringing it up. I'll check out the upgrade posibility.
In mean time, feel free to add whatever you find. Thanks :)

I found this. It is an upgraded version of MatthieuLemoine/push-receiver with the new endpoints.
https://github.com/MatthieuLemoine/push-receiver/compare/master...javajuice1337:push-receiver-v2:master

Thanks for the detective. I'll attempt to transplant the changes within a few days and see if it works. Help is always appreciated :)

It's looking good. Got a working version.
There are some new requests and token refreshing that needs to be done before releasing.
Also there are gonna be data changes so old tokens are probably gonna need to be re-generated

@juangvega I've created a new version. Can you please double check form that is's working as expected?
<EMAIL_ADDRESS>

Hi there! This is great news. I will try later and let you know. Thanks

Seems to be working well

@Eneris Thanks for your work on updating the FCM API.  I'm preparing to update ring-client-api which heavily depends on push-receiver, however, it's not clear to me what the upgrade/migration process from older versions might be.  Do I need to generate an FCM project for my specific project?
I'll try to look through the source code to get a better clue, but just doesn't feel very clear to me right now what firebase property should contain so if you have any hints it would be appreciated.

@Eneris Thanks for your work on updating the FCM API. I'm preparing to update ring-client-api which heavily depends on push-receiver, however, it's not clear to me what the upgrade/migration process from older versions might be. Do I need to generate an FCM project for my specific project?
I'll try to look through the source code to get a better clue, but just doesn't feel very clear to me right now what firebase property should contain so if you have any hints it would be appreciated.

Hi. Yea. The firebase project is required now (the free tier will do fine). Yasyest way is to copy-paste the config that firebase gives you for the web apps.
https://github.com/Eneris/push-receiver/blob/master/src/types.ts#L119-L128
These parts of the config are required
{
    projectId: string
    appId: string
    apiKey: string
    messagingSenderId: string
}

As for migration steps:

All that is required from your part is to supply new config properties
PushReceiver will generate new credentials and tokens for each device automatically so save the new ones. The old ones will stop working since they are registered to old endpoints

Web credentials for firebase are public so don't worry about compiling them into the code


Add high-level API examples.

Code can be simplified when using TensorFlow's high-level APIs. This commit
adds 2 additional examples: (1) using TensorFlow layers to create our fully-
connected layers in our MNIST network, and (2) wrap our model in an Estimator
which then drives the training of our model. Additionally, in the estimator
code, I've converted to using the new Datasets API for higher-performance
input pipelines.
This code is first presented at the Deep Learning Summer School in Montreal
2017.

Thank you very much! Appreciated.


Digital channels should somehow be protected against getting values other than 0/1

This might be handled by ADwin correctly (everything that is non-0 is 1?), or if not, we can handle it in the ADwin script.
However, it hurts also the operational level if other values appear, e.g. when plotting the timeline.

Basic sanitizing functions for ADwin-specific things have been extended in the adwin module. Just need to add another function.


vm.tiktok.com/{ID} links no longer working?

Changing
from https://vm.tiktok.com/ZT8WXquk6/
to https://vm.dstn.to/ZT8WXquk6/ is now giving a "invalid_match_for_video" error
However, changing:
https://www.tiktok.com/@mikecakez/video/7329968713464073518
to
https://vm.dstn.to/@mikecakez/video/7329968713464073518
is working just fine

Fixed, at latest for now, we'll see if it works for everything and for how long. https://github.com/dustinrouillard/tiktok-embeds/commit/5f2bda85585a16e4e162aaa29eb11c5ffc66b836


re-activating support for win-32?

I noticed that iminuit-1.2 was also build for the win-32 platform, while iminuit-1.3.2 is only build for *-64 platforms. Should we still support win-32?

Suggest to drop win 32.There's already close to no downloads at https://anaconda.org/conda-forge/iminuit/files , the number of users that want that now might be zero.

Ok, that's fine with me.


 If parsing user input, this may be used as a denial",
            + 	"    of service vector.",
            + 	"  More info: https://pkg.go.dev/vuln/GO-2021-0054",
            + 	"  Module: github.com/tidwall/gjson",
            + 	"    Found in<EMAIL_ADDRESS>            + 	"    Fixed in<EMAIL_ADDRESS>            + 	"    Example traces found:",
[...]
            /Users/gopher/go/src/golang.org/x/vuln/cmd/govulncheck/testdata/testfiles/source-call/source_vuln_text.ct:71: want=-, got=+
            $ govulncheck -C ${moddir}/vuln -show=traces ./... --> FAIL 3
[...]

FAIL
FAIL	golang.org/x/vuln/cmd/govulncheck	7.890s
FAIL

(full details are on the post-submit dashboard here)
CL 555515 is a change generated by the automated tagging workflow, that updates to the latest versions of golang.org/x dependencies. This test runs only on longtest builders, and x/vuln trybots only has short builders by default, so it wasn't caught in pre-submit.
A short term fix is to revert the CL, or fix forward. @golang/vulndb What would you prefer?
That said, these kinds of CLs are expected to happen continuously, so there might be more to do to make the test okay with continuous golang.org/x dependency updates. If that's not viable, then let's discuss if something should change on the side of the monthly tagging workflow or the builder configuration. Thanks.

I think CL 555655 should fix the immediate problem.

This is fixed now.


Error with installing plugin

Current Behavior
The plugin does not work on version 1.14.4 Spigot
Expected Behavior
Plugin operation
Steps To Reproduce

Start Server
Yeeees error!

Version and Log
1.14.4 Spigot
Plugin version: WeaponMechanics-2.2.6, MechanicsCore-2.2.4, protocollib latest
Logs:
logs.txt
Anything else?
No response

Update to java 16 or newer


Make sure on-exit-leak-free is run on node >=14

Since it uses WeakRef and FinalizationRegistry available only from Node v14. It would otherwise give errors like
ReferenceError: FinalizationRegistry is not defined
    at Object.<anonymous> (node_modules/on-exit-leak-free/index.js:11:18)

I have nothing against adding this metadata, but neither Node.js or npm are enforcing them.


Can't host the SwaggerUi on a nested endpoint with axum

I have an axum service that is made to support multiple versions of the API.  Each version of the API is contained in its own module and then a router it returned from the only public  method from the module, so like:
pub fn build_router<DAO: Dao>() -> Router<DAO, Body> {
    Router::new()
        .route("/message", get(get_messages::get_messages::<DAO>))
       ....
}

This is done to keep the implementation of each version well isolated from each other since they often have similar named structs and methods.
This module is then nested to the larger app by nesting it, so:
let app = Router::new()
        .nest("/api/v1", handlers::v1::build_router::<DAO>())
        .nest("/api/v2", handlers::v2::build_router::<DAO>())
        .with_state(dao)

The problem comes up when I want to add a swagger UI.  I want to add it to the build_router method. So something like:
pub fn build_router<DAO: Dao>() -> Router<DAO, Body> {
    Router::new()
        .merge(SwaggerUi::new("/swagger-ui").url("/openapi.json", ApiDoc::openapi()))
        .route("/message", get(get_messages::get_messages::<DAO>))
}

The swagger UI would then be served at "/api/v1/swagger-ui" and by default try to load the openapi.json from "/openapi.json" but it is actually being served from "/api/v1/openapi.json".  I can't find a way to make this work.
As a work around I'm making the ApiDoc public from the module, added directly to the root router like this:
    let app = Router::new()
        .merge(SwaggerUi::new("/api/v1/swagger-ui").url("api/v1/openapi.json", handlers::v1::ApiDoc::openapi()))
        .merge(SwaggerUi::new("/api/v2/swagger-ui").url("api/v2/openapi.json", handlers::v2::ApiDoc::openapi()))
        .nest("/api/v1", handlers::v1::build_router::<DAO>())
        .nest("/api/v2", handlers::v2::build_router::<DAO>())
        .with_state(dao)

This works and isn't the end of the world, but it would nice to be able to use nest on SwaggerUi

The utopia is now able to work on nested routers already, you need to provide a correct config.
eg.
let config = Config::from("/v1/api-docs/openapi.json");
let mut router = Router::new()
        .merge(SwaggerUi::new("/swagger-ui")
            .url("/api-docs/openapi.json", ApiDoc::openapi())
            .config(config)
        )

Yup thats the way to solve this.


Bug in QInputBase

In QInputBase, the attributes slots[] and evaluate_prop[] are defined as class members, while IMHO they have to be instance members. I stumbled into it when I created a webpage containing a QDate component which has a JS function assigned to its 'options' attribute. And also containing a QSelect component the 'options' attribute of which is a string. Very strange things happened...
I solved the problem by changing the source code of QInputBase.
I deleted line 56 evaluate_prop = []
I added a line at the end of the__init__() method, line 66 self.evaluate_prop = []
Looking at the source code of QInputBase, I believe the same kind of issue exists with the slots[] property. As I am not using it in my project, I didn't touch it though.

Yes, good point, thank you. I will change it.

The lines are not at the positions mentioned any more.
class _QInputBase(Input):

    slots = []
    evaluate_prop = []

    def __init__(self, **kwargs):
        self.disable_input_event = False
        super().__init__(**kwargs)
        self.vue_type = 'quasar_component'
        self.directives = quasar_directives
        self.disable_events = False
        self.prop_list = []
        self.attributes = []

Has the code such as quasarcomponents been written completely manual or has there been some kind of (semi-) automation/generator technology to so?

It was written manually using the copy and paste technique.

@elimintz that is good to know. My background is in model driven development and generator technology. It was a big hype between 1996 and 2008 and is not much applied in the industry any more. At least it will be worthwhile to do an analysis how systematic the problem ist and what the rules are. Automation requires systematization.
@docm64  since a systematic/general solution will take it's time could you provide a pull request for this?


Use compression on output file to save space

This could also be an option for the user to choose.

Needs a port of #99 to pyro

Is covered by https://github.com/advancedtelematic/meta-updater/pull/101


[DS-3938] Use JDK7-compatible PostgreSQL JDBC driver in DSpace 5.x

#1970 updated the PostgreSQL JDBC driver. However, the default version in the Maven repositories require JDBC4.2 (JDK 8). This PR specifies to require JDK7-compatible version of the driver.

@jmarton : thanks for that note! I missed that this is solved dynamically both in dspace-6_x and in master:

https://github.com/DSpace/DSpace/blob/dspace-6_x/pom.xml#L550
https://github.com/DSpace/DSpace/blob/master/pom.xml#L661

I'll remove the "port to 6.x" tag as it's definitely not necessary. This only needs merger into dspace-5_x

@tdonohue My instance is built on the release distribution rather than the full source distribution.  Even if I incorporate the pom.xml file change from this commit, the unwanted jar file is still getting built into the rdf and rest webapps files.
Have we seen reports from others having trouble upgrading to 5.9?
Would this commit justify the publishing of a new release?


Clear output window previous syntax error(s) or compile messages when re-saving and there are no more errors

Just an annoyance, if I previously had syntax error(s) in my snakemake file and there's message output from those, when I've fixed them and I save the file the previous messages are still there in the output window and I'm no certain that the syntax or compile errors are gone.

Moved https://github.com/tfehlmann/vscode-snakefmt-provider/issues/8


⚠ Fortnite has degraded performance

In c12fd58, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1585 ms

Resolved: Fortnite performance has improved in 1337b8b.


MINOR: Drop enable.metadata.quorum config

The primary purpose of this patch is to remove the internal enable.metadata.quorum configuration. Instead, we rely on process.roles to determine if the self-managed quorum has been enabled. As a part of this, I've done the following:

Replace the notion of "disabled" APIs with "controller-only" APIs. We previously marked some APIs which were intended only for the KIP-500 as "disabled" so that they would not be unintentionally exposed. For example, the Raft quorum APIs were disabled. Marking them as "controller-only" carries the same effect, but makes the intent that they should be only exposed by the KIP-500 controller clearer.
Make ForwardingManager optional in KafkaServer and KafkaApis. Previously we used null if forwarding was enabled and relied on the metadata quorum check.
Make zookeeper.connect an optional configuration if process.roles is defined.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji Do we still need this PR since Colin already did one?

@hachikuji Do we still need this PR since Colin already did one?

@hachikuji Do we still need this PR since Colin already did one?

That PR was for the KIP-500 branch, not for trunk.  It also didn't refactor the "disabled" APIs concept, which I think is useful.

Replace the notion of "disabled" APIs with "controller-only" APIs. We previously marked some APIs which were intended only for the KIP-500 as "disabled" so that they would not be unintentionally exposed

That seems reasonable.  I guess the idea is that the broker will not include those APIs in its ApiVersionsResponse.  However, the controller always will (not that clients will talk directly to the controller anyway...)

@hachikuji Do we still need this PR since Colin already did one?

That PR was for the KIP-500 branch, not for trunk.  It also didn't refactor the "disabled" APIs concept, which I think is useful.

Replace the notion of "disabled" APIs with "controller-only" APIs. We previously marked some APIs which were intended only for the KIP-500 as "disabled" so that they would not be unintentionally exposed

That seems reasonable.  I guess the idea is that the broker will not include those APIs in its ApiVersionsResponse.  However, the controller always will (not that clients will talk directly to the controller anyway...)

@cmccabe Yeah, that's right. Let me see if I can improve this a little bit to make the intent clearer. We have some APIs which will be exposed by both the broker and the controller, so I think this should probably be a set rather than a flag.

@cmccabe Yeah, that's right. Let me see if I can improve this a little bit to make the intent clearer. We have some APIs which will be exposed by both the broker and the controller, so I think this should probably be a set rather than a flag.

I decided to leave the controller-only flag as it is. I think there are further improvements here to make the scope of the API clearer, but the implications for compatibility are subtle enough that we should consider it separately.

I decided to leave the controller-only flag as it is. I think there are further improvements here to make the scope of the API clearer, but the implications for compatibility are subtle enough that we should consider it separately.


[SPARK-18661] [SQL] Creating a partitioned datasource table should not scan all files for table

What changes were proposed in this pull request?
Even though in 2.1 creating a partitioned datasource table will not populate the partition data by default (until the user issues MSCK REPAIR TABLE), it seems we still scan the filesystem for no good reason.
We should avoid doing this when the user specifies a schema.
How was this patch tested?
Perf stat tests.

@rxin

Test build #69435 has started for PR 16090 at commit 51d2a41.

Test build #69435 has finished for PR 16090 at commit 51d2a41.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69435/
Test FAILed.

Test build #69437 has started for PR 16090 at commit 275f6b9.

Test build #69437 has finished for PR 16090 at commit 275f6b9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69437/
Test FAILed.

Test build #69514 has started for PR 16090 at commit 89b0a64.

Test build #69514 has finished for PR 16090 at commit 89b0a64.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69514/
Test FAILed.

Merged build finished. Test FAILed.

Test build #69534 has started for PR 16090 at commit 2940d55.

Test build #69536 has started for PR 16090 at commit b405635.

Test build #69534 has finished for PR 16090 at commit 2940d55.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69534/
Test FAILed.

Test build #69536 has finished for PR 16090 at commit b405635.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69536/
Test PASSed.

Merged build finished. Test PASSed.

My main concern is that, in CreateDataSourceTableCommand, we call DataSource.resolveRelation to infer the schema and partition columns. At that time, the table is not created yet, so logically we should not pass a CatalogTable to DataSource and create CatalogFileIndex inside it, which looks like a hack.
It seems to me that it's more logical to tweak the InMemoryFileIndex to scan the files lazily, to avoid unnecessary file scan for cases like this one.

I looked at avoiding the creation of a CatalogFileIndex, but the way table resolution works right now, the only way is to create some sort of dummy file index class that does not support scans. It's not clear to me that is any better than just creating a CatalogFileIndex, which seems better than incorrectly creating an InMemoryFileIndex.

Seems like we also create InMemoryFileIndex twice for non-catalog tables. Let me try to fix that too.

Fixed by adding a private cache to Datasource, which is used to avoid the duplicate file reads with InMemoryIndex.

Test build #69600 has started for PR 16090 at commit 5a250ad.

cc @rxin please merge unless wenchen gets to it first

Test build #69600 has finished for PR 16090 at commit 5a250ad.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69600/
Test FAILed.

 I'll take a look at this
again tomorrow.
On Fri, Dec 2, 2016, 7:49 PM UCB AMPLab<EMAIL_ADDRESS>wrote:

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69600/
Test FAILed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/16090#issuecomment-264614120, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA6SoVLnj_xZMTNgUpQo0THN8Z2LRvDks5rEOa2gaJpZM4LA1GX
.

If we are going to hack it, how about this?
val dataSource = DataSource(...)
if (classOf[FileFormat].isAssignableFrom(dataSource.providingClass)) {
  dataSource.getOrInferFileFormatSchema()
} else {
  dataSoure.resolveRelation().schema -> new StructType
}

Then we don't need to create FileIndex and scan files.

Not sure I follow - could you explain more on why that would resolve the issue?
Btw, I reverted this pr to b405635, which passes all tests.

Test build #69630 has started for PR 16090 at commit b405635.

Test build #69630 has finished for PR 16090 at commit b405635.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69630/
Test PASSed.

After looking more at the code, now I agree with your approach. One question, seems we still scan the files when creating a unpartitioned external data source table?

Yeah I was wondering if we should also try to fix that. It seems maybe not
as bad since unpartitioned tables usually aren't that big.
We can create separate tickets for investigating that, and also the
duplicate file scan issue (that might not be a regression).
On Sun, Dec 4, 2016, 12:05 AM Wenchen Fan<EMAIL_ADDRESS>wrote:

After looking more at the code, now I agree with your approach. One
question, seems we still scan the files when creating a unpartitioned
external data source table?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/16090#issuecomment-264690256, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA6Ska3bJklmhoUUWIaS1Tlg0ha1JsHks5rEnRigaJpZM4LA1GX
.

LGTM, merging to master/2.1!
@ericl please create tickets for the other 2 issues

Filed
https://issues.apache.org/jira/browse/SPARK-18725
https://issues.apache.org/jira/browse/SPARK-18726


Push latest tag of our images during nightly build

Today, the nightly build only pushes a named tag as specified here. This is problematic because our deployment has configuration settings such as GIT_CONTAINER_IMAGE or MUTATE_IMAGE_CONTAINER_IMAGE which default to use the latest tag. Normally, when you use a yaml of a version or nightly release, then you get a named tag and that is present in quay. But if you for some reason remove this environment variable - or run make local, then it might fallback to the default.
Two ideas to fix this:
(1) Add tag to ko command
ko supports multiple tags. If we change above referenced with ,latest as suffix, then it will push a latest tag. But, it seems that it then will not include a tag anymore in the resolved yaml. That's okayish. The only caveat is that by looking at our controller deployment, or a BuildRun pod, one cannot anymore determine which nightly one has installed. Workaround could be some annotation or label which would require some programming logic to get this into a BuildRun pod.
(2) Copy images after ko
We can copy the images to the latest tag. docker pull, docker tag, docker push. Or maybe crane copy or skopeo copy. Caveat here is that we must not forget to extend the list once there is a newer image unless ko extract is available.

I personally prefer option (2).

@imjasonh feeling a little too busy and would rather not re-read enough of https://kubernetes.slack.com/archives/C019ZRGUEJC/p1632745313022800 to answer the following question :-) ...
what if anything does https://github.com/google/ko/pull/448 and https://github.com/google/ko/releases/tag/v0.9.2 do to help with this issue and our recent experience ?
I think it is orthogonal, right?
thanks

v0.9.2 doesn't fix the specific problem, but should make it so commands
don't have to start with /ko-app/, that's all.
On Thu, Sep 30, 2021 at 1:36 PM Gabe Montero @.***>
wrote:

@imjasonh https://github.com/imjasonh feeling a little too busy and
would rather not re-read enough of
https://kubernetes.slack.com/archives/C019ZRGUEJC/p1632745313022800 to
answer the following question :-) ...
what if anything does google/ko#448
https://github.com/google/ko/pull/448 and
https://github.com/google/ko/releases/tag/v0.9.2 do to help with this
issue and our recent experience ?
I think it is orthogonal, right?
thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shipwright-io/build/issues/877#issuecomment-931526324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABTOMPHAAHLTGKXULOCDIDUESNZVANCNFSM5E2SWO4Q
.

v0.9.2 doesn't fix the specific problem, but should make it so commands don't have to start with /ko-app/, that's all.

great thanks for the confirmation @imjasonh :-)

fwiw I'm +1 for @SaschaSchwarze0 's preference for 2)
I think it helps confine the use latest to the local dev / make local path by not involving it in the ko interactions wrt the nightlies


Team Calendar extension does not work with Azure DevOps Server 2022

Team Calendar extension does not work with Azure DevOps Server 2022.
Here is an error:
VSS.SDK.js:105 TypeError: $.uniqueSort is not a function
    at processClassString (widget.js:528:36)
    at $.<computed>.<computed>._classes (widget.js:541:13)
    at $.<computed>.<computed>._toggleClass (widget.js:578:43)
    at $.<computed>.<computed>._addClass (widget.js:566:21)
    at $.<computed>.<computed>._createWrapper (dialog.js:361:14)
    at $.<computed>.<computed>._createWrapper (widget.js:132:37)
    at $.<computed>.<computed>._super (widget.js:117:47)
    at $.<computed>.<computed>._createWrapper (dialog.js:938:18)
    at $.<computed>.<computed>._createWrapper (widget.js:132:37)
    at $.<computed>.<computed>._create (dialog.js:140:14)

jQuery.unique() was renamed to uniqueSort in jQuery version 3.0:
https://api.jquery.com/jQuery.uniqueSort/#:~:text=The %24.,not considered to be duplicates.
Adding the following would fix the issue:
if ( !$.uniqueSort ) {
    $.uniqueSort = $.unique;
}

Thanks for reporting it will be fixed in an upcoming release.

Hello @AminTi can you please provide a date for the release to fix this issue? Thanks in advance.

I too am having an issue with the calendar. Below is a screenshot of the error I am getting:

the same here. any prevision?

At this moment, we are actively working on the Team Calendar, and once we have resolved it, we will proceed with the release. appreciate your patience.

Hello @AminTi   would you have any news on this? Is there any plan to get it fixed?


[feature request] publish sink connector artifact to maven central

Hey,
In order to be able to create a projet with one or more postProcessor, I think that It would be a good idea to publish the current connector project to the central nexus.

@zthulj yes you are right in case you want to write a project containing any custom code this would be helpful. till today nobody ever asked for it but I'll try to look into this soonish. THX for reporting this improvement suggestion!

Fixed with release 1.3.0 -> find it on maven central as of now. Enjoy!


Ajax spit out data emoji string expression how to change

emoji expressions?

Hello,
is this issue still relevant? If so, could please specify your problem more close?

in this demo i can send emoji name it's good but how can i send emoji image in this demo.?

can you please help me...

@socialinfotech215 do you mean that the final string is something like Hello :smile:? instead of Hello 😄? If you would like the image to be in the string you will have the parse the string and replace :*: with the according image.


[🐞 BUG]: In appropriate alert message when username or password is invalid

Description 📝
when the user tries to sign-in in Sign-In page, if the username or password is invalid and if we have selected ENGLISH as the languagethen also the alert message is not in the ENGLISH
Link 🔗
https://retlab-dev.firebaseapp.com/signin
Steps to Reproduce 🔄

Go to https://retlab-dev.firebaseapp.com/signin link
fill username and password and select English as the langauge
see the alert message

Screenshots 📸

Expected Behavior 🤔
The alert message must be in the the language selected by the user
Actual Behavior 😱
the alert message is not in  user selected language
Environment 🌍
windows 11
web browser : ms edge.
Additional Information ℹ
No response

please assign this issue to me .

please assign this issue to me .

@Tufailahmed-Bargir pull the develop branch, your branch is outdated.

Noted...


AzureOptimizationEngine installation failed.

During the installation process of the AOE the script throws the below issue. Also when running the script locally, the script gets stuck (I've waited more than 10 minutes) and didn't create any of the resources in the given subscription.

Hi, @PostelnicuAlin . Thank you for reporting this issue. I am working on a PR that is going to fix this issue very soon. The issue will be automatically closed when the PR is merged.


server output in ansi (windows-1252) only

Description
I tryed my best - even with tips from this source here - to get all outputs in dbeaver to utf8 (like all my databases do). This works well in all cases but not in the server output window (SQL editor bottom toolbar, console like), where still windows-1252 is used. Did I miss something (all my dbeaver/eclipse preferences seem to be configured as utf8)?

these cryptic letters should be the euro sign.
(https://github.com/orgs/dbeaver/discussions/20579)
DBeaver Version
23.1.3 on Eclipse Version: 2023-06 (4.28.0)
Operating System
MS Windows 10 V22H2 (Build 19045.3208)
Database and driver
PostGreSQL 15
MySQL 10.4.28-MariaDB
Steps to reproduce
In PostGreSQL for example use 'raise notice 'öäüß' in any function of your choice and call it or try to get some server outputs with non ansi unicodes ("create table if not exists public.t_öäüß (test_id serial)" two times for example).
Additional context
No response

Hello @NotSignificant,
Can you please open Help -> Installation Information -> Configuration, search for .encoding and send the results?
You might try adding the following line to the end of the dbeaver.ini file (located next to the DBeaver's executable):
-Dfile.encoding=UTF-8

Since I'm working with Eclipse the path seems to be Help -> About Eclipse IDE -> Installation Details -> Configuration and it's output is
`*** Date: Donnerstag, 3. August 2023, 17:23:56 Mitteleuropäische Sommerzeit
*** Platform Details:
*** System properties:
file.encoding=UTF-8
native.encoding=Cp1252
stderr.encoding=Cp1252
stdout.encoding=Cp1252
sun.io.unicode.encoding=UnicodeLittle
sun.jnu.encoding=Cp1252
*** System environment variables:
*** Features:
*** Plug-in Registry:
*** User Preferences:
/instance/org.jkiss.dbeaver.core/pg.export.all.encoding=UTF-8
*** Current Install Configuration:
*** Security Configuration:
`
-Dfile.encoding=UTF-8 helps although file.encoding already was UTF-8 encoded. I don't know if this is a bug in eclipse or a bug in dbeaver now. But I think it's in eclipse, because the configuration details are part of eclipse, even if dbeaver isn't there. Or could it be, that you use -Dfile.encoding instead of file.encoding somewhere?
after modifying the configuration looks like this
`*** Date: Donnerstag, 3. August 2023, 18:33:08 Mitteleuropäische Sommerzeit
*** Platform Details:
*** System properties:
-Dfile.encoding=UTF-8
file.encoding=UTF-8
native.encoding=Cp1252
stderr.encoding=Cp1252
stdout.encoding=Cp1252
sun.io.unicode.encoding=UnicodeLittle
sun.jnu.encoding=Cp1252
*** System environment variables:
*** Features:
*** Plug-in Registry:
*** User Preferences:
/instance/org.jkiss.dbeaver.core/pg.export.all.encoding=UTF-8
*** Current Install Configuration:
*** Security Configuration:
`

Although we both are confused, I'm glad I was able to help you. I believe the ticket can be closed now.


Simplify enums

While reviewing a Cadl for a service team today, I was surprised by the verbosity of extensible enums:
enum ThingKindValues {
  A;
  B;
}
@knownValues(ThingKindValues)
model ThingKind is string {};
model Thing {
  kind: ThingKind;
}

Seems that could be simplified, but how really depends on whether Cadl wants to follow Azure guidelines by default or not (seems not).
If we say that enums are extensible by default, for example, we could simply declare the enum as, say, @fixed and just use it:
@fixed
enum ThingKind {
  A;
  B;
}
model Thing {
  kind: ThingKind;
}

Conversely, if enums are fixed by default, we could come up with something like @extensible and treat them, effectively as is string {} now.
The syntax is more concise for authors, and this also seems like less guesswork for generators. Take the C# generator, since .NET doesn't support unions nor string-based enums - either of which other languages do: we have to now look at two different models to determine if something should be a regular, fixed enum or an enum-like readonly struct per our current guidelines.

I think there are two parallel questions here:

What should Cadl's opinions about enums be, if any?
How should you specify the other way around?

Tackling #2 first, one nice aspect of the present solution is that it is much less error prone. Emitters are not required to interrogate enums to see if they are extensible or not. If they do the simple thing, an extensible enum will just appear as a string or number to them, and they will generate a client that works (albeit with less type system help). I believe that's why we went with the present approach over the @extensible annotation, but perhaps others remember more of the discussion.
Regarding #1, pinging @KrzysztofCwalina who I know also has opinions! While Cadl doesn't presently expose enum strictness in any way you can detect, my opinion is that Cadl enums are fixed because this is the stricter semantics that I think aligns most conceptually with how folks around industry would want to use Cadl. Calling something an enum and then making it just a hint over its base type feels surprising for an API description language, to me.
KC pointed out that, in C#, enums are "by default" extensible in the sense that a method which takes an enum parameter can take any int. It is likely very common for integer enums to behave this way across languages for performance reasons and because it makes using bitflags more ergonomic. But this feels much less justifiable with string enums, and indeed in TypeScript at least string enums are "fixed" and do not allow any string, and I wouldn't be surprised if C# string enums follow a similar pattern. Being fixed is perhaps better for performance for string enums as well.

Yes, it's true that enums in .NET can take any int, but the predominant use case is for strings. In fact, of all the swaggers I've reviewed the past few years, I don't think I've once seen any use besides strings. It's certainly possible and should be allowed, but seems better to focus on the main use case.
I appreciate that Cadl starts off with a strict interpretation and don't argue it's wrong, but I do think that OpenAPI has enums wrong. It doesn't seem version compatibility has been - or is - top of mind. At the very list, enums as a "hint" of possible values provide a better UX for both REST and client libraries. As merely a string - if generators didn't interrogate for more information - it's a worse UX. Besides, couldn't generators just as easily ignore any defined enum values and treat it as a string, while not making generators that want to do the better UX figure out what types to define and which not? As written today, I wouldn't want to see ThingKindValues defined at all and ThingKind to be an enum instead of a model class (or struct), which doesn't really model the Cadl as written.

KC pointed out that, in C#, enums are "by default" extensible in the sense that a method which takes an enum parameter

This is true, but it's also a bit like saying every TypeScript type is extensible because you can force the compiler to let you pass any value in its place.

A few things that would/could simplify this
Inline enums
We have plan to allow specifying enum inline which would make the known value pattern
@knownValues(enum {
  A,
  B,
})
model ThingKind is string;

Also looks pretty good with decorators after (Not something you can do now but we have discussed it)
model ThingKind is string @knownValues(enum {
  A,
  B,
})

String union
Should we allow
@knownValues("A" | "B")
model ThingKind is string

How would authors document string unions in this case? I think that's somewhat important. Too many swaggers already don't do a great job of documenting enum values.

I knew there was a reason string union wasn't that great of an alternative :) but couldn't remember, you cannot document options.

However, if we forget documentation from a language completeness this feels like we should allow it.

I don't think we should. We should be encouraging better documentation, which is what the stewardship board wants to do by asking that default documentation not be generated and have validation to make sure everything is @doc'd.

Though this is an Azure opinion for Azure SDK and is enforced by the cadl-azure-core linter, the Cadl language doesn't force and shouldn't force documentation.

I think the concept (a union of known values and unknown values) exists in the modeling space. We are now trying to decide how to express this concept in CADL. We can express it as a string with annotations (as it's done today) or as some first-class syntax. I think the latter would be more readable without concrete negatives I can see. If there are concrete negatives, I would love to understand them. I have to say the arguments above read a bit too philosophical to me and I am having problems distilling it to concrete negative implications.

We can express it as a string with annotations (as it's done today) or as some first-class syntax.

Or as an enum with annotations as is proposed at the top of the issue. Without expressing a very strong opinion in either direction, I don't think we should add more syntax to the language for this scenario.

I think @extensible enum { A, B, C } is OK if people feel really strongly against the string + knownValues approach. I think it is perfectly concrete that an emitter than doesn't do anything with extensible will emit something more restricitive than it should, but I think it is probably OKto trade that small negative for the gained readability in what is a very common scenario in our own API.

I think it is probably OK to trade that small negative for the gained readability in what is a very common scenario in our own API.

I think this philosophy should be applied to other concepts in services/libraries. i.e. I love the extensibility CADL offers, but I think we should use these extensibility mechanisms for non-common concepts/scenarios. Core scenarios should be expressible using super readable built-in syntax. I really think there is an opportunity to obsolete API view (and do reviews of CADL files in github) if we simplify the syntax.

@extensible enum would still be using Cadl's extensibility via decorators. It's just a more readable thing. I think we often debate first-class vs. via-extension too much instead of just looking for good readability, which doesn't have to exclude decoration.

I really think there is an opportunity to obsolete API view (and do reviews of CADL files in github) if we simplify the syntax.

I'm behind this 100%. I don't want to have to switch context to APIView and not have the back and forth experience of conversing over a PR. I'm already in the notification page reviewing notifications, why have to switch to something separate? And the more concise the language, the easier that is to do. Already, I find reviewing Cadl files so much easier than swagger because they are concise and you can get a better overview of the API.

@extensible enum Foo {One: 1, Two:2, Three: 3}

azure-core?
dpg
core?
openapi?

do we need a concept of fixed enums?
option 1: enums are interpreted as 'extensible' by Azure
//option 2: @extensible
option 3: @fixed  (***azure-core, dpg, openapi)

fix cadl-autorest and specs

Yes, there are cases for fixed enums. Personally, I don't really care which the default is - given pure Cadl, perhaps fixed - but we need a keyword to "reverse" it either way. If we default to fixed, I think @extensible might be more of an azure-core thing since x-ms-enum.modelAsString is an autorest extension. Or would that classify it more as a DPG thing?


Reader callback in constant readers list changed loop.

Hello,
I am having the issue with your demo reader program for Delphi that this is in a constant readers list changed loop.
I do have to say that I am using Delphi 5. This is used in house for all our development for years which is why this has not been updated before you ask why we are still on that version.
I have been reading the issues for the non delphi Swelio repository and something was mentioned about Sd card readers being one of the issues. If I disable this SD Card reader in my system then the demo reader program stops with it's loop. The strange thing though is that the demo reader program has only detected 1 card reader. I made an adjustment to use the GetReadersCount to update the found readers since I was curious if another reader was found.
I have made sure too use the latest version of the delphi repository and also the most up to date Swelio32.dll of 18-9-2023 (the one in the delphi repository is a 2022 version)
Could you help me with this? or is their another way to handle this then disabling a device?

This issue is fixed in v1.18.30
Additionally 2 procedures added IgnoreHardwareEvents and IgnoreServiceEvents. By defaults this kind of events is ignored now, but you can switch it on by using new procedures, if necessary


Draft roadmap as of Dec 2018

Codecov Report

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

@@          Coverage Diff           @@
##           master   #3617   +/-   ##
======================================
  Coverage    80.5%   80.5%
======================================
  Files         395     395
  Lines       81012   81012
  Branches     9215    9215
======================================
  Hits        65216   65216
  Misses      14373   14373
  Partials     1423    1423

Thanks for the fix up, can be merged as convenient.


Support new shared components as an alternative to the indy-sdk

Includes support for

[ ] Indy VDR
[ ] Indy CredX
[ ] Aries Askar

Proudly closing it (althought we are using anoncreds instead of indy-credx)


Update xlf files with new string

New string appeared between xlf creation and when localization team translated them. This commit syncs the xlf against the latest resource state on master.

LGTM, but I have some process questions.
What keeps these up to date going forward? Do we need to do anything special when we add a new string? What about changing an existing one?

Here is an overview of the localization process so far. I'll write a more detailed wiki on it.
When sufficient changes have accumulated, and\or before a VS release, we update the loc team to perform localization. While the loc team is translating, we should not update our xlf since that might lead to races and missed updates (they translate a string that updates while translating).
So here's the process on our end:

CI does localized builds all the time
We only do a localized build and commit the xlf file changes before notifying the loc team.
We do not do localized builds and commit the xlf while the loc team did not return from our last notification. Synchronous process :)

You can view this commit as step 2.

@dotnet-bot test Windows_NT Build please


Updated docker to latest ubuntu

This PR updates the docker file and fixes compilation problems in docker

Thanks!


TestEventsFilterContainerID is racy

fix racy TestEventsFilterContainerID it has to do with events

--- FAIL: TestEventsFilterContainerID (0.94s)
    docker_cli_events_test.go:355: Expected 3 events, got 2: [2015-03-31T17:36:02.000000000Z ab26eddbd0f26fad7fb1263785e701e23d5f5021afbb196a94d4c31c06a97de9: (from busybox:latest) create 2015-03-31T17:36:02.000000000Z ab26eddbd0f26fad7fb1263785e701e23d5f5021afbb196a94d4c31c06a97de9: (from busybox:latest) start]


Fix StackOverflowException when calling ItemStackInventory#IsEmpty

When isEmpty is called on a Farmer's Delight inventory, it recursively calls itself, leading to a StackOverflowException.
This can be reproduced by attaching a hopper to a Cooking Pot and attempting to insert items using it.
This PR fixes the bug by properly delegating to ItemStack#isEmpty instead of the ItemStackInventory's own isEmpty.

Hello @unilock,
Thanks you for the help.


Release/3.0.26

I'm working on a full russian translation, about 1/4th way through the guide book, and i've rewrote the ru_ru.lang existing. It's a lot less "google translate" now, and a lot more vanilla minecraft-named like.
ru_RU.zip

Unfortunately your attached ZIP file is invalid. If you can fork the repository and add your changes there and commit it to a different branch on your fork, (GitHub desktop should help you there), you should be able to push that and then request a pull from your branch to the main branch.


How styled-components interact with inline styles created by dangerouslySetInnerHTML?

It's a question, but not the usage one, rather the "how does it work" type. It might be a bug report.
I pass a html with inline styles string to dangerouslySetInnerHTML inside the jsx element. Later on that component is used as a descendant of a several styled components and the inline styles vanish. Does in any point during creating a styled component, inline styles may be overwritten? How can I keep these styles?

Yea, this is more of a question, so may be better for Stackoverflow / Spectrum in the future. But I recognise that you weren't sure whether it was related to styled-components, so no worries :+1:
Basically, styled-components has nothing to do with this. If you have children / parents that are rendered then a StyledComponent like usual in React's paradigms doesn't control or know anything about them. So it's not possible for this problem to be directly related to our components.
I don't obviously know why you're doing this and injecting CSS this way, but I'd start at looking whether the element actually has the styles you expect it to have (I assume it's just a style tag with dangerouslySetInnerHTML?) and then check if the rules are there whether you've introduced some specificity issues.


Export Log levels in util/log

Without knowledge about log levels impossible to set log level programmatically.

pr in #666

Closing as https://github.com/micro/go-micro/pull/666 was merged in


ADD: Oluwaseun Abiola

Hey
Can you help 3 people update their PR. I like to address it from the earlier PR like #6, #5 and upward.
I will add you as administrator to help me.


fix(sync): fill auto fields with nil

Summary
bump go-kong to 0.59.0
use go-kong utils to fill auto fields with nil in the config sent to the CP.
The rest of the default values are still not filled in the configuration that is sent out, as they are meant to be filled by the CP itself.
Full changelog

[Implement ...]
[Fix ...]

Issues resolved
https://konghq.atlassian.net/browse/KAG-5317
Documentation

[ ] Link to the website documentation PR

Testing

[ ] Unit tests
[ ] E2E tests
[ ] Manual testing on Universal
[ ] Manual testing on Kubernetes

Codecov Report
Attention: Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Project coverage is 29.96%. Comparing base (0b1b75f) to head (fdbf4dc).

Files with missing lines
Patch %
Lines

pkg/diff/diff.go
0.00%
8 Missing :warning:

pkg/types/plugin.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
- Coverage   29.97%   29.96%   -0.01%
==========================================
  Files         106      106
  Lines       12581    12583       +2
==========================================
  Hits         3771     3771
- Misses       8350     8352       +2
  Partials      460      460

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Xslt transformer

This is an XSLT transformer module that uses SI XsltPayloadTransform transformer. It is developed using SI DSL. The project has an integration and module configuration unit tests, as well as one sample xslt file and an xml payload file. Readme has all instructions.

I'm not if this repository or the spring-xd-samples repository is the right place for such contributions. I though this simple module can be useful for someone who wants to ingest xml payloads to any sink after running it through an XSLT. The sample shows how to convert XML to CSV using XSLT. I am not sure if that can be achieved with transformer/splitter oob modules.

I think this is right repo

Thank you for the contribution! Many of the modules in the spring-xd-samples repo include both maven and gradle builds. This is mainly to illustrate how modules can be built either way. In practice, it's difficult to maintain both so I would choose one and simplify the README accordingly.  Note that you have different versions of XD declared (1.1.1.RELEASE for maven and 1.2.0.M1 for gradle) here. I am seeing a difference in the contents of the jars and the test fails for the gradle build for me (looking into the cause).  Note that Spring XD 1.2.x includes spring-integration-xml already. I recommend maven since as of 1.2.0.RC1 the parent pom includes dependency management. In cases like this, where you have compile time dependencies on such libraries, you do not need to specify the version.  This raises another point about this repo and which version of XD each module is targeted for. We don't have any policy on that at this point but I will discuss with the team. Meanwhile, I'll look for another commit on this PR to make the recommended changes before merging it. Thanks again!

One more thing - we will need you to sign the contributor's agreement, and select the Spring XD project.  This does not grant you commit rights to the repository, but it does mean that we can accept your contributions, and you will get an author credit if we do.  Active contributors might be asked to join the core team, and given the ability to merge pull requests.  Thanks!

I have signed the agreement.
The confirmation number is -<PHONE_NUMBER>01074425
Thanks,
Muhammad Ali
On Mon, Jun 1, 2015 at 9:47 PM, David Turanski<EMAIL_ADDRESS>wrote:

One more thing - we will need you to sign the contributor's agreement
https://support.springsource.com/spring_committer_signup, and select
the Spring XD project. This does not grant you commit rights to the
repository, but it does mean that we can accept your contributions, and you
will get an author credit if we do. Active contributors might be asked to
join the core team, and given the ability to merge pull requests. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/spring-projects/spring-xd-modules/pull/13#issuecomment-107652391
.

--
Muhammad Ali
Advisory Consultant
Pivotal Services @ EMC | +971551259736 |<EMAIL_ADDRESS>www.pivotal.io

Rebased and merged.


create a cheat sheet on chrome developer tools

perhaps demo at the meeting and then have someone take notes. it would be a good start

to get you started. here is a screenshot

.

I added a video on youtube [here](https://www.youtube.com/watch?v=RRuaG0_W7B4


Can't send message to Rabbitmq

Hello everyone,
I'm trying to make a simple console application on windows. I have installed AMQP-CPP  and included the library on my Visual Studio project. My task is to create the simple communication with the rabbitmq server. The main function is:
#include <amqpcpp.h>
#include "rabbitmqModels.h"

int main(){

    string msg = "hello world";
    string queueName = "message_queue";
    string exchangeName = "myexchange";
    string routingKey = "hello";

    Address address("amqp://guest:guest@localhost:15672");
    MyConnectionHandler myHandler;
    Connection connection(&myHandler, address);
    Channel channel(&connection);

    channel.declareQueue(queueName);
    channel.declareExchange(exchangeName, direct).onSuccess([]();
    channel.bindQueue(exchangeName, queueName, routingKey);
    channel.publish(exchangeName, routingKey, msg, msg.size());

    return 0;
}

where rabbitmqModels.h code is:
using namespace AMQP;
class MyConnectionHandler : public ConnectionHandler
{
private:
	/**
	 *  Method that is called by the AMQP library every time it has data
	 *  available that should be sent to RabbitMQ.
	 *  @param  connection  pointer to the main connection object
	 *  @param  data        memory buffer with the data that should be sent to RabbitMQ
	 *  @param  size        size of the buffer
	 */
	virtual void onData(Connection* connection, const char* data, size_t size)
	{
		// @todo
		//  Add your own implementation, for example by doing a call to the
		//  send() system call. But be aware that the send() call may not
		//  send all data at once, so you also need to take care of buffering
		//  the bytes that could not immediately be sent, and try to send
		//  them again when the socket becomes writable again
	}

	virtual void onReady(Connection* connection) override
	{
		// @todo
		//  add your own implementation, for example by creating a channel
		//  instance, and start publishing or consuming
		std::cout << "Connection is established...\n";

	}

	virtual void onError(Connection* connection, const char* message)
	{
		// report error
		std::cout << "Connection Error: " << message << std::endl;
	}

	virtual void onClosed(Connection* connection)
	{
		std::cout << "closed" << std::endl;

	}

	virtual void onConnected(Connection* connection)
	{
		std::cout << "connected" << std::endl;
	}
};

The code builds without errors. Note that my rabbitmq server runs on localhost:5672 and I have defined both the queue and the exchange/routing key.
The thing is that I cannot see any message coming to my defined queue.  Do I have to use only TCPHandler? I can't find any implementation of TCPHandler for windows.
Can you please tell me why?
Thanks in advance

Hi there,
This question is not that new but I thought I'd still answer it.
If I understand it correctly the use case by the original library developer is for a UNIX/Linux environment.
There is no out of the box TCP handler implementation for windows provided with the library.
With that in mind, you can with little effort implement your own TCP handler, inheriting from ConnectionHandler.
It is up to you which networking library/event loop you want to use.
If you are interested, I don't mind sharing some knowledge and examples of my own with you.
Cheers

The above answer is correct. In your MyConnectionHandler you still have a lot of empty functions that you must implement to set up the connection to the RabbitMQ server.

Hi @EmielBruijntjes ,
Do you have an example MyConnectionHandler for Windows.
Thanks

No, I'm sorry


License

Hi
Great app!
Does it released under BSD license?
Regards
Israel

Thanks,
I thought about adding GPL V3 license but if BSD fits for you i will add it.

Great, thanks you.
On Tue, Jan 5, 2016, 21:20 RealGame (Tomer Zait<EMAIL_ADDRESS>wrote:

Thanks,
I thought about adding GPL V3 license but if BSD fits for you i will add
it.
—
Reply to this email directly or view it on GitHub
https://github.com/realgam3/hackmecredit/issues/1#issuecomment-169102716
.

Done,
You can close your issue :+1:


Update simapp

Let's follow Cosmos SDK development step by step, adapting our code as needed along the way.

[x] to nightly-2020-08-11 and REF=20c80cfd44a068a592148d648c50de3459fd6295 #381
[ ] to nightly-2020-08-12 and REF=7ea64676788f2d550a65d86cd6b4cdfe89e9a49b (blocked by https://github.com/cosmos/cosmos-sdk/issues/7026)
[ ] to nightly-2020-08-13 (blocked by https://github.com/cosmos/cosmos-sdk/issues/7026)
[ ] to nightly-2020-08-14 (blocked by https://github.com/cosmos/cosmos-sdk/issues/7026)
[ ] to nightly-2020-08-15 (blocked by https://github.com/cosmos/cosmos-sdk/issues/7026) (requires Tendermint 0.34)
[ ] to nightly-2020-08-16 (requires Tendermint 0.34)
[ ] to nightly-2020-08-17 (requires Tendermint 0.34)
[ ] to nightly-2020-08-18 (requires Tendermint 0.34)
[ ] to nightly-2020-08-19 (requires Tendermint 0.34)

@webmaster128 Is this checklist still accurate?

I think there is nothing wrong with the existing entries but we should try to fast-forward to today's simapp version.

Blocked by #451


My Brunch

I added only my contacts but, if I have free time, I try to add dark and light mode. So, firstly, I must customize color styles and create dark color styles which is pretty annoying, but I will do it.

Hello, @azick99. That will be a wonderful feature to have, so if you can accomplish it, that would be fantastic.
In the main time, PR MERGED! Thanks for contributing.


Join Chat API

Is there available option for join group chat via invite link?

Just found it, check this:
'messages.importChatInvite'


Move ffmpeg-installer to optional packages

What kind of change does this PR introduce?

Security improvement

What is the current behavior? (You can also link to an open issue here)

ffmpeg-installer is installed as a direct dependency of this library

What is the new behavior (if this is a feature change)?

ffmpeg-installer is moved to optionalDependencies from dependencies

Other information:

ffmpeg installer has optional dependencies for each cpu architecture, each ships with postinstall scripts that could be used as an attack vector
By moving ffmpeg-installer to an optional dependency, we can hopefully mitigate this effect. This also appears to match the intent of how the library is used.
If there's something I can do to help improve this PR or land this change, please let me know. Happy to help where I can!

Hi @benschwarz,
Thanks for pointing out the security risk and PR. I appreciate it.
It would be great, if you could update your PR against latest changes, Please.

@prasanaworld I've rolled back the version bump and merged the updates from main. Thanks!

@prasanaworld Is there anything else you'd like to see on this PR? LMK. I'm keen to have this released!  🚀

Looks good to me. Thanks for your contribution

Thanks @prasanaworld. As far as I can see, the build tool hasn't automatically released an updated npm package. Could you give it a nudge?

Thanks @prasanaworld. As far as I can see, the build tool hasn't automatically released an updated npm package. Could you give it a nudge?


[Package Issue]: UweSieber.UsbTreeView wrong InstallerUrl

Please confirm these before moving forward

[x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[x] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Other
Brief description of your issue
The InstallerUrl for the UweSieber.UsbTreeView package always points to the latest release. However, this behavior is not desired because if the version in the winget repository has not been updated, attempting to install it will result in the error message: "Installer hash does not match."
Currently, the latest version of the package in the winget repository is 4.4.2, while the actual latest release is 4.4.3.
To resolve this issue, you can download the specific version of the package directly from the following URL format:
https://www.uwe-sieber.de/files/UsbTreeViewNNN_ARCH.zip
For example, to download version 4.4.2 for the x64 platform, use the following URL instead of the current one:
https://www.uwe-sieber.de/files/UsbTreeView442_x64.zip
Something like this:
--- UweSieber.UsbTreeView.installer.yaml	2024-11-25 21:24:23.381081238 +0100
+++ UweSieber.UsbTreeView.installer.yaml	2024-11-25 21:24:13.191084794 +0100
@@ -10,7 +10,7 @@
 UpgradeBehavior: install
 Installers:
 - Architecture: x64
-  InstallerUrl: https://www.uwe-sieber.de/files/UsbTreeView_x64.zip
+  InstallerUrl: https://www.uwe-sieber.de/files/UsbTreeView442_x64.zip
   InstallerSha256: 092EA02051DCE0274EEBCA943E630EEF6E0B79C3C1087621580315DA4227175C
 ManifestType: installer
 ManifestVersion: 1.6.0

Steps to reproduce
Trying to install the current version:
winget install --source winget --id UweSieber.UsbTreeView
> Installer hash does not match.

Trying to install the latest version of the package, not yet in the winget repository
winget install --source winget --version 4.4.3 --id UweSieber.UsbTreeView
> No version found matching: 4.4.3

Trying to manually install the latest version available in the winget repository
winget install --source winget --version 4.4.2 --id UweSieber.UsbTreeView
> Installer hash does not match.

Actual behavior
Unable to install the UweSieber.UsbTreeView package because the current InstallerUrl always points to the latest release, which does not match the version available in the winget repository.
Expected behavior
Ensure the ability to install the UweSieber.UsbTreeView package using Winget by downloading the installer that matches the repository version.
Environment
Windows Package Manager v1.9.25200
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.2314
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.24.25200.0

Screenshots and Logs
No response

Under the UsbTreeViewXXX_x64.zip name I keep previous version for download only.
Would it help to have the latest release available with its version in the file name too?

Done:
https://www.uwe-sieber.de/files/UsbTreeView443_x64.zip
And I'll do it for further releases.
Just in case: Some other popular tools
https://www.uwe-sieber.de/files/UsbDriveInfo563_x64.zip
https://www.uwe-sieber.de/files/ComPortInfo121_x64.zip
https://www.uwe-sieber.de/files/DeviceCleanup131_x64.zip
All x64 only.

Done: https://www.uwe-sieber.de/files/UsbTreeView443_x64.zip
And I'll do it for further releases.
Just in case: Some other popular tools
https://www.uwe-sieber.de/files/UsbDriveInfo563_x64.zip https://www.uwe-sieber.de/files/ComPortInfo121_x64.zip https://www.uwe-sieber.de/files/DeviceCleanup131_x64.zip
All x64 only.

Thanks 😃


Download link is broken

The link to the latest version of the Closure Compiler is broken: https://dl.google.com/closure-compiler/compiler-latest.zip

It has been fixed. Thanks!


FormattedName field value incorrect

The FormattedName field in the vCard seems to be an unparsed N field rather than the FN field

@richardhauer I have released an update with a fix


fix: fix font rendering issue under HiDPI

fix the following issue:
https://github.com/horsicq/Detect-It-Easy/issues/176

Thanks a lot! :)


Can't prompt for custom background-size, and display error in vscode and vue3

Current environment

"vite-plugin-windicss": "^1.4.12",
"vue": "^3.2.16",
"windicss": "^3.2.1"
windicss IntelliSense: v0.21.4

Current config

custom background-size

do not prompt bg-full

But it actually worked

in style prompt error

But it actually worked

After restarting the computer/restarting vsocde, it resumes itself


Skip filter state update when composite filter is in upstream

This is to address issue: https://github.com/envoyproxy/envoy/issues/33343

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @htuch @juanmolle

envoy 1.30 was released. does this PR got sens now? if it does and get merged in 1.31, then eventually will break compatibility right?

envoy 1.30 was released. does this PR got sens now? if it does and get merged in 1.31, then eventually will break compatibility right?

composite filter status_upstream is alpha : https://github.com/envoyproxy/envoy/blob/313b6fb7cf0f806e74a2d42c93e7c1fcccce2391/source/extensions/extensions_metadata.yaml#L284
This gives us flexibility to make some upstream specific changes.

Doesn't the issue suggest we could support upstream filter state? Or is this "we'll implement it when needed"?

Doesn't the issue suggest we could support upstream filter state? Or is this "we'll implement it when needed"?

This PR implements the latter.


Google Maps

BEFORE YOU BEGIN
I have attempted the following troubleshooting suggestions:

[ ] The issue persists when using Firefox in Troubleshoot Mode.
[ ] Disabled DNS-level content blocking (AdGuard Home, NextDNS, Control D, RethinkDNS, PiHole, etc), cleared my DNS cache, and used my ISP's DNS resolver (if applicable).
[ ] Cleared website data, restarted Firefox, and my issue persists.
[x] I have created a new profile. The issue persists when using the current user.js file on GitHub. (Must be in a new profile and a new user.js!)

REPORT
Describe the bug
on google maps site "globe mode" is not available and zooming is intermittent
To Reproduce
I go to google maps and observe the inability to turn on "globe mode" and intermittent zooming
1. Go to google maps
2. Click on layers
3. Scaling the map
4. See error

Expected behavior
globe mode on google maps and smooth zooming
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/yokoffing/Betterfox/assets/97912016/18031d5b-e705-4ab8-b8d5-991287f3071d
Desktop (please complete the following information):

Windows 10 22H2 x64
Firefox
116.0

Additional context
Add any other context about the problem here.

I cannot reproduce on Firefox Stable using a new profile or when using the current user.js.
I can reproduce on my build with Firefox Nightly.
There are many bug reports across various browsers reporting this issue in the past 5 years, but none of them I've found post what the solution was. Many seem to point to the browser not being able to use WebGL. You can test if Firefox can use WebGL with this site: https://get.webgl.org/
On Stable (with or without user.js):

On Nightly w/ user.js:

Indeed, the essence of the problem is in the enabled parameter about:config webgl.disabled. After disabling it, the problem is solved. The only remaining question is whether this parameter is in user.js or related to something else?

webgl.disabled is not in the user.js. It's stated in the README that we don't break user experiences like this.
Most issues are due to users toggling prefs outside the user.js, which is why the BEFORE YOU BEGIN section exists for bug reports...
In the future, bug reports not following through with self-troubleshooting will be auto-closed.


display not detected in docker container

[ubuntu 22.04 with nvidia gpu]
I tried to run the toy example with the rendering option genesis.Scene(show_viewer=True) but screeninfo could not detect my display on docker.
Solution:

allow all local process to the x server before running a docker container: xhost +Local:*
add following options when running a docker container: -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix

Then the following error occurred:
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) libGL error: failed to load driver: swrast
Solution:
there is swrast_dri.so in /usr/lib/x86_64-linux-gnu/dri/
so I make a link to the path mentioned above:
ln -s /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so /usr/lib/dri/swrast_dri.so
(reference: https://forum.step.esa.int/t/snap9-error-libegl-warning-mesa-loader-failed-to-open-swrast/36702/5)
Then the following error occurred:
libGL error: MESA-LOADER: failed to open swrast: /home/miniconda3/envs/genesis/bin/../lib/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/x86_64-linux-gnu/libLLVM-15.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) libGL error: failed to load driver: swrast
Solution:
there was libstdc++.so.6 in /usr/lib/x86_64-linux-gnu/, so I created a link to the path with
ln  -s /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30 /home/miniconda3/envs/genesis/lib/libstdc++.so.6.0.30
and set LD_LIBRARY_PATH in conda with
export LD_LIBRARY_PATH=/home/miniconda3/envs/genesis/lib:$LD_LIBRARY_PATH
Then it worked for me.

thanks


vcs: difftest checks on negedge

Difftest is essentially a producer-consumer framework, where various DPI-C functions in SimTop.v act as producers, and functions like simv_nstep serve as consumers. Currently, in the difftest framework based on vcs / tb_top, both producers and consumers operate on the rising edge, leading to a race and hazard issue, namely: before all the DPI-C functions of the producer have executed, the consumer starts comparing with incomplete content, thereby triggering errors. This issue has already occurred in vcs.
As shown in the figure below, when the commit in the ROB is enabled, the mstatus in the CSR also changes synchronously.

However, judging from the printed content (printf in the DPI-C functions in ROB commit and CSR), the actual execution order is: the commit DPI-C function in the ROB -> the difftest comparison process (comparison fails, the producer function of the CSR has not yet been executed) -> (the DPI-C function of the CSR may be executed at this time).

It appears that a simple solution is for the producer to produce on the rising edge, while the consumer consumes on the falling edge.
Feel free to discuss whether this solution is reasonable, whether the modifications in the PR are complete, and whether there are better solutions.

Let @klin02 have a review.
I remembered he told me about similar race issues before.

In Gateway.scala, we delay step one cycle to make sure consume after produce. And we can set ping-pong buffer for consumer and producer by enable difftest-config Z.
Just try pass “--difftest-config Z” or EZ to mill. See detail in Makefile of XS.

Related discussion #283

Seems that --difftest-config Z can resolve this issue. I think it may be set as default option when we use tb_top.

Seems that --difftest-config Z can resolve this issue. I think it may be set as default option when we use tb_top.

Are we required to built different Verilog for VCS and Verilator? @klin02
If so, it looks strange. Are there any alternative approaches to fix the issue?


fix(license) replace boilerplate

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

https://github.com/bytecodealliance/wasmtime/issues/4064


add japanese translation

Tests are failing because you appear to have used dist/js/i18n/en.js instead of src/js/select2/i18n/en.js.
That should also help to fix the JSHint errors that are being triggered.

@kevin-brown   sorry for late reply. I fixed it

I forgot to close this off when https://github.com/select2/select2/pull/3477 was merged. That pull request also added Japanese translations.
If there are any discrepancies between the two translations, feel free to note them in the other pull request.


scipy.weave.inline can be excessively slow on windows 7

See numpy/numpy#3713

weave support will be removed in PySB 2.0, see #434


Added mutator to AND and OR in logic block

#797
Added mutator to AND and OR in logic blocks. But, I made AND and OR into separate blocks, without having the dropdown.
@halatmit @afmckinney @jisqyv

@candicefan You should remove the commented out code. You also need to provide an "upgrader" to upgrade existing projects to use your new block.

@candicefan @jisqyv @afmckinney
Candice:  Doing the upgrader might be a little tricky.   Ask Andrew or Jeff or me for help.   See versioning.js, but that might not tell you enough.

@candicefan @jisqyv
Candice:
This doesn't seem to bee handing the upgrading correctly.   Doing what's required is a little tricky.  Please sit down with Jeff and/or me in person, and we can go over in detail what needs to be done.

This is going to be merged as part of the Blockly update.

@ewpatton that pretty much means that this PR should be closed?

@moliata It will need to be rebased and some minor things will need to be fixed given the extent of the changes in the Blockly update, but I don't expect it to be too much work. I would be hesitant to close the PR given that 90% of the work has been done.

Blocked by #989

Merged as part of #2184


That about environment teams?

More detailed is needed to learn how environment teams can help assign security roles to groups of users. Also how the roles assigned through environment teams can be verified.
Also how can you assing security roles directly to the user and by default on the team.
There are several types of teams too. I tried adding an AAD team, but for some reason only three of the 2600`users are shown.
also when the group type associated with the team is AAD the search for team members does not seem to work.
Quite frustrating
### Tasks
- [ ] Add a draft title or issue reference here

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

ID: 04be5f13-5b10-de80-5c9f-66632bcb8918
Version Independent ID: 41fc9e53-ea77-ea3d-d4d3-3be63cbbebd4
Content: Assign security roles - Power Platform
Content Source: power-platform/admin/assign-security-roles.md
Service: power-platform
Sub-service: admin
GitHub Login: @sericks007
Microsoft Alias: sericks

Thanks for your comment, @bernatagulloesbrina. This issue has been assigned to the doc author for review.


[BUG] toast.promise error callback

Describe the bug
In original sonner, the error callback of a promise can also take a function with the rejected error as parameter.
To Reproduce
toast.promise(
  new Promise((resolve, reject) => {
    setTimeout(() => {
      reject(new Error('Nah'));
   }, 1000);
  }),
  {
    loading: 'Loading..',
    success: (result: string) => `Resolved:  ${result}`,
    error: (error: Error) => `Rejected: ${error.message}`,
  }

Expected behavior
Types should allow this, as well as functionality should mimic original sonner
Environment info

Library
Version

sonner-native
latest

react-native
latest

react-native-reanimated
latest

react-native-gesture-handler
latest

hello! i've opened a PR that should cover that feature

Releasing the fix in an hour or so, closed


Add startup flag to specify functions that should be favorably selected by fuzzer

This adds a startup flag "assign_function_tickets" to the fuzzer that takes
a comma separated list of function names and their tickets in the format
<function_name>=. Every ticket represents an opportunity for
a function to be chosen from a pool of candidates. By default, every
function has one ticket, and the likelihood of a function being picked
can be increased by allotting it more tickets. Note that in practice,
increasing the number of tickets does not proportionally increase the
likelihood of selection, as the selection process involves filtering
the pool of candidates by a required return type so not all functions
may compete against the same number of functions at every instance.
Number of tickets must be a positive integer.
Example:
--assign_function_tickets "eq=3,floor=5"
Test Plan:
Ran fuzzer for 60 secs with:
Case 1:
--assign_function_tickets "reverse=1"
functionName numTimesSelected proportionOfTimesSelected numProcessedRows
subscript 4698 6.24% 50935
array_min 3039 4.04% 31115
array_max 3027 4.02% 34004
least 1830 2.43% 10932
greatest 1749 2.32% 9115
clamp 1492 1.98% 13815
floor 1416 1.88% 20626
divide 1404 1.87% 18279
negate 1399 1.86% 19363
sign 1367 1.82% 16842
multiply 1362 1.81% 19842
ceil 1346 1.79% 16744
minus 1341 1.78% 17084
mod 1335 1.77% 18587
abs 1324 1.76% 17189
round 1315 1.75% 17258
ceiling 1310 1.74% 19120
plus 1299 1.73% 18900
reverse 1100 1.46% 11350
Case 2:
--assign_function_tickets "reverse=6"
subscript 4914 6.17% 56986
reverse 3209 4.03% 35340
array_max 3180 3.99% 38363
array_min 3171 3.98% 35746
greatest 1787 2.24% 9678
least 1763 2.21% 10213
multiply 1533 1.93% 24829
ceil 1518 1.91% 21930
round 1517 1.91% 19357
abs 1499 1.88% 20086
plus 1489 1.87% 19672
mod 1487 1.87% 19735
minus 1466 1.84% 19829
ceiling 1443 1.81% 22217
negate 1438 1.81% 21344
clamp 1433 1.80% 14652
sign 1432 1.80% 20460
floor 1423 1.79% 18669
divide 1408 1.77% 19904
date_add 1062 1.33% 4755
date_trunc 1021 1.28% 8358
slice 777 0.98% 7429

This is a follow-up PR after #3695 that leverages it to enable this feature.
Fixes #3388

@kgpai @kagamiori Can you please take a look when you get a chance? Thanks!


Failed to deploy web package to App Service using ZIP Deploy

I have encountered an error while using the azure/webapps-deploy@v2
beta-deploy.yaml:
name: Develop - Build and deploy to Azure Web App

on:
  push:
    branches: ["develop"]
  workflow_dispatch:

jobs:
  build:
    runs-on: windows-latest

    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v3
        with:
          node-version: 16
      - name: Set up .NET Core
        uses: actions/setup-dotnet@v1
        with:
          dotnet-version: '6.0.x'
          include-prerelease: true

      - name: Install npm
        run: |
          cd src/Web/
          npm install
      - name: Build WEB
        run: dotnet build ./src/Web --configuration Debug

      - name: Upload artifact for deployment job WEB
        uses: actions/upload-artifact@v2
        with:
          name: .net-app-web
          path: ${{env.DOTNET_ROOT}}/web

      - name: Publish API
        run: dotnet publish  ./src/PublicApi/ -c Release -o ${{env.DOTNET_ROOT}}/api

      - name: Upload artifact for deployment job API
        uses: actions/upload-artifact@v2
        with:
          name: .net-app-api
          path: ${{env.DOTNET_ROOT}}/api

  deploy:
    runs-on: windows-latest
    needs: build
    environment:
      name: 'Production'
      url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}

    steps:
      - name: Download artifact from build job - WEB
        uses: actions/download-artifact@v2
        with:
          name: .net-app-web

      - name: Deploy to Azure Web App
        id: deploy-to-webapp-web
        uses: azure/webapps-deploy@v2
        with:
          app-name: 'webapp-XXXXXXXXX'
          slot-name: 'Production'
          publish-profile: ${{ secrets.AZUREAPPSERVICE_PUBLISHPROFILE_DEF5E7EC3B4649958EFAF575DDB49C91 }}
          package: .

And the main issue happens in the deploy part where once the build is complete and it tries to do the deploy the output looks like this
Output
Using the following command to generate deployment script: 'azure site deploymentscript -y --no-dot-deployment -r "C:\local\Temp\zipdeploy\extracted" -o "C:\home\site\deployments\tools" --basic --sitePath "C:\local\Temp\zipdeploy\extracted"'.
C:\PROGRA~2\SITEEX~1\NODEAP~1\296456~1.8\nodejs\build\src\Loader.js:153
                ...StatusLogger.DEFAULT_STATUS,
                ^^^

SyntaxError: Unexpected token ...
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:[12](https://github.com/vacha/nanosun-systems/actions/runs/4701623399/jobs/8338345568#step:3:13))
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at module.js:669:12
    at Array.forEach (native)
C:\PROGRA~2\SITEEX~1\NODEAP~1\296456~1.8\nodejs\build\src\Loader.js:[15](https://github.com/vacha/nanosun-systems/actions/runs/4701623399/jobs/8338345568#step:3:16)3\r\n                ...StatusLogger.DEFAULT_STATUS,\r\n                ^^^\r\n\r\nSyntaxError: Unexpected token ...\r\n    at createScript (vm.js:56:10)\r\n    at Object.runInThisContext (vm.js:97:10)\r\n    at Module._compile (module.js:542:28)\r\n    at Object.Module._extensions..js (module.js:579:10)\r\n    at Module.load (module.js:487:32)\r\n    at tryModuleLoad (module.js:446:12)\r\n    at Function.Module._load (module.js:438:3)\r\n    at Module.require (module.js:497:[17](https://github.com/vacha/nanosun-systems/actions/runs/4701623399/jobs/8338345568#step:3:18))\r\n    at module.js:669:12\r\n    at Array.forEach (native)\r\nC:\Program Files (x86)\SiteExtensions\Kudu\100.50331.6[20](https://github.com/vacha/nanosun-systems/actions/runs/4701623399/jobs/8338345568#step:3:21)4\bin\Scripts\starter.cmd "C:\Program Files (x86)\SiteExtensions\Kudu\100.50331.6204\bin\node_modules\.bin\kuduscript.cmd" -y --no-dot-deployment -r "C:\local\Temp\zipdeploy\extracted" -o "C:\home\site\deployments\tools" --basic --sitePath "C:\local\Temp\zipdeploy\extracted"
Deployment Failed.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed, Package deployment using ZIP Deploy failed. Refer logs for more details.

I have no idea what the cause is. If it is on the action part or if it is on our side. Am I missing something?

Any chance this can be looked into please? We are also facing this issue.

We are also experiencing this issue as of today.

Hello, Can we look into this? We are experiencing this as well.

Just started experiencing this issue as well. Preventing us from deploying to production. Would love some guidance if possible. Thank you!

Just tried, this is still an issue and is preventing our team from publishing critical fixes. Please help!

Any updates anyone? We have experienced this issue since Monday and we desperately need to deploy.

This issue is preventing us from making any deployments to Azure.

@Ortieez have you had any responses yet on this issue?

@Ortieez have you had any responses yet on this issue?

Nothing yet. We managed to fix this by creating a new instance and just moving our stuff there. But I think the issue still persists.

We have tried using earlier versions v2.2.7 , v2.2.6 , v2.2.5 but they also give errors.

Any advice would be super welcome @Ortieez as Graham said we have tried using earlier versions v2.2.7 , v2.2.6 , v2.2.5 but they also give errors. Much appreciated.

Any advice would be super welcome @Ortieez as Graham said we have tried using earlier versions v2.2.7 , v2.2.6 , v2.2.5 but they also give errors. Much appreciated.

As I mentioned before, we also tried multiple versions on the currently old azure web app instance and everything failed there. So we created a new instance and using the latest version of the deploy action it suddenly started to work.

@Graham-getOptimal @danfellows605 @curtiswmcmillin
I had the same issue and the solution I found on SO helped me.
In short, setting WEBSITE_NODE_DEFAULT_VERSION in App Service -> Configuration -> Application Settings to 16.9.1 helped (I also checked Deployment slot setting - don't know if this is required)

I have tried setting WEBSITE_NODE_DEFAULT_VERSION in App Service -> Configuration -> Application Settings to 16.9.1
I am still getting the same error

@iskeld That fixed it, thank you so much!

Still ongoing on projects I'm inolved in.
In my case I removed the WEBSITE_NODE_DEFAULT_VERSION setting from azure entirely on the deployment slot I was having trouble deploying to. Application Insights might add this setting, and swapping slots might move it to a slot you don't expect too.

So it's happened for me again on a different project. On my previous project, setting WEBSITE_NODE_DEFAULT_VERSION to 16.9.1 helped - but on this project it hasn't. Any other ideas?

As mentioned above, for us helped just moving the project to different Azure App. That is all I can provide. @brooklynDev

We are also experiencing this issue as of today.

Just adding that updating AppService's WEBSITE_NODE_DEFAULT_VERSION setting to 16.9.1 took care of this issue.

Yep we struck this today and can confirm that updating WEBSITE_NODE_DEFAULT_VERSION to 16.9.1 fixed it. Frustrating that this wasn't part of a major version bump and affected v2 of the action.

Can confirm this issue persists. I noticed the apps we have the are having this issue the offending config item was set to 6.9.1 I was able to get it running by removing the WEBSITE_NODE_DEFAULT_VERSION setting completely or by changing it to 16.9.1

Hi everyone,
As we can see from the supported NodeJS versions by running this, only "NODE:18LTS",   "NODE:16LTS",   "NODE:14LTS" are supported. If you're using the legacy versions of the Nodejs this issue persists. This can be mitigated by setting the WEBSITE_NODE_DEFAULT_VERSION app setting in your app to the latest version of NodeJS. (Currently ~18, you should use a tilde (~) to have the runtime use the latest available version of the targeted major version. For example, when set to ~18, the latest version of Node.js 18 is used. When a major version is targeted with a tilde, you don't have to manually update the minor version.)

For me the issue was solved by reviewing all parameters on WebApp configuration section.  Someone setup the Application Insights in my resource group, and it generated a lot of parameters there that were making my deploy fail.

solved by reviewing all parameters on WebApp configuratio

Hey, did you remove them all?


docs(README): Include a POSIX-compliant wget example

It might be better to use POSIX-only syntax with wget, which is included by default in Alpine Linux, considering portability.

LGTM, thanks!


I Can not work rollbackto.

Your Question
Hi everyone,
I use testify and gorm in my project. I've created a testsuite which can be seen below. I've debugged the code many times and I am pretty sure that SetupTest and TearDownTest works as expected. But RollbackTo function does not work as expected. The inserts are not reverted after the tests.
func (s *ToDoTestSuite) SetupSuite() {
	s.config = config.Init()
	s.config.Database.Name = fmt.Sprintf("test_%s", s.config.Database.Name)
	database.SetupTestDatabase(s.config.Database)
}

func (s *ToDoTestSuite) TearDownSuite() {
	db, _ := s.db.DBConn.DB()
	err := db.Close()
	if err != nil {
		panic(err)
	}

	database.DropTestDatabase(s.config.Database)
}

func (s *ToDoTestSuite) SetupTest() {
	s.db = database.New(&s.config.Database)
	s.tx = s.db.DBConn.Begin()
	s.tx.SavePoint("sp")
}

func (s *ToDoTestSuite) TearDownTest() {
	s.tx.RollbackTo("sp") // Did NOT WORK
	s.tx.Commit()
	db, _ := s.db.DBConn.DB()
	_ = db.Close()
}

func TestTestSuite(t *testing.T) {
	suite.Run(t, new(ToDoTestSuite))
}

The document you expected this should be explained
https://gorm.io/docs/transactions.html#SavePoint-RollbackTo
Expected answer
By the way, my repository can be checked here for those want to get more information.

Resolved by using s.tx instead of s.db