Update mc_att_control_main.cpp

feed forward before constrain

@DrTon Could you have a look at the change? It seems to make sense to me.

Not sure if users will like this. If MC_MAN_Y_MAX > MC_YAWRATE_MAX then yaw rate will be limited in manual mode (bad! controller works in non linear mode and user gets not what he commanded). Note, that such settings are NOT wrong, user may want to have fast yaw in manual modes but slow yaw in AUTO.
Now for manual control limit only applied to additional yaw rate caused by yaw position error (outer loop controller). So with normal setting in manual mode controller should never reach saturation (good!), only way to reach saturation is to apply strong external forces (e.g. hand), then after releasing the forces yaw will be returned to setpoint with limited rate (good and safe, especially on takeoff), and in auto mode sp_move_rate is 0 anyway, so no difference, controller will just limit yaw rate.
It's better to not touch this, I thought about it :) Or, @ziyangli, show please which problems solved for the price of adding another problem?

@DrTon, thank you for your explanation, it's very clear. I was reading the code and thought logically we should constrain only at the last step. Obviously there are more practically reasons for not doing that.


Missing flag of Northern Ireland (sport)

Short information: https://en.wikipedia.org/wiki/Flag_of_Northern_Ireland.
The main point is "In sport, the Ulster Banner is carried by the Northern Ireland team in the Commonwealth Games. It is also regularly displayed by supporters of the Northern Ireland national football team and is displayed by FIFA as the flag of Northern Ireland"

https://github.com/lipis/flag-icon-css/commit/ba44a8a974ff4b0d9c4815c51f30b57cdfb6e26a
https://github.com/lipis/flag-icon-css/blob/master/flags/4x3/gb-nir.svg
https://github.com/lipis/flag-icon-css/blob/master/flags/1x1/gb-nir.svg


Update chart reloader to 1.0.84

This PR contains the following updates:

Package
Update
Change

reloader
patch
1.0.83 -> 1.0.84

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


feat(learn): add full stack certificate markdown

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #18128
Also partially addresses https://github.com/freeCodeCamp/freeCodeCamp/issues/38934.

Currently this just adds a full stack certification markdown file and makes it so the front 3, data viz, API and microservices, and new QA certification all you need to claim it. This doesn't rename the certification to "Legacy Full Stack Certification" yet.
@ahmadabdolsaheb and I were discussing whether this legacy full stack cert should require the new QA certification mentioned in https://github.com/freeCodeCamp/freeCodeCamp/issues/38934#issuecomment-636374471, or the Legacy Information Security and Quality Assurance certification (isInfosecQaCert in the db).

I didn't read all the comments here but..

@ahmadabdolsaheb and I were discussing whether this legacy full stack cert should require the new QA certification mentioned in #38934 (comment), or the Legacy Information Security and Quality Assurance certification (isInfosecQaCert in the db).

I would think it's only fair to have the legacy full stack cert include the exact same projects needed to currently get the full stack. What if someone is like one project away, and all of a sudden there's 5 new projects before it can be claimed.

@ahmadabdolsaheb, that's right, I forgot to add this in after our session last night.
There are some messages already in the file that we can send using Observable.just(typeOfMessage(certName)) like
const notCertifiedMessage = name => dedent`
  It looks like you have not completed the necessary steps.
  Please complete the required projects to claim the
  ${name} Certification
  `;

That or we could use a more generic error message for those cases. If there's no challenge/cert object at this point, it's likely that there's a connection issue or the new challenges/cert weren't seeded to the challenge collection in the db for some reason.

I would think it's only fair to have the legacy full stack cert include the exact same projects needed to currently get the full stack. What if someone is like one project away, and all of a sudden there's 5 new projects before it can be claimed.

@moT01, I can relate to your point. We could discuss this further in #38934.
If we arrive to a different conclusion there we could modify this implementation in the future accordingly.

@raisedadead, sounds great. In the meantime I'll implement the error checking and message like @ahmadabdolsaheb pointed out above.


Unable to view generators on yeoman.io

traced back to generator.js:25 Uncaught TypeError: a.sort is not a function(…) according to my console.

It works over here. Using Chrome 54.

There is something in the making to fix the current behavior of the generator list over here btw: https://github.com/yeoman/yeoman-generator-list/pull/51

Generators showing up for me now. Also on Chrome 54


Sorry, I can't assist with that.

Every other thing I ask GitHub Copilot in VS Code, I get "Sorry, I can't assist with that."
No idea, WHY it cannot assist? No feedback on how to ask the question differently.
Beyond frustrating and wasting time and tokens trying to "guess" how to get a helpful response.
Can you add a simple extension to the prompt to make the Copilot more helpful, adaptative, and responsive when it (apparently) cannot handle a prompt.

Can you please share the queries that lead to this response, so we can try to reproduce the error?

Maybe this is already intented but annoying because you cannot chat about other than directly coding questions. It always tend to write code and this is breaking the natural flow of the Sonnet. This characterization should only be in the Edit mode. (I dont actually prefer that too)


Bf gets smaller everytime I do anything

Describe your bug here.
I tried to reload in an image and my sprite got smaller for some reason
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

weird bug. hopefully it will get fixed soon.

Video? Files? Anything that helps reproduce the bug?? Sometimes scaling is just weird

If something like a file is missing the image will do what it knows and load the first image at 0.5x scale...
Unless it's arrow strums then the game will crash lol...

Like there is an image path
and I couldn't fix it so its fine


Scheduler with angular bootstrap calendar

Is there any example for implementation for scheduler of resources using this plugin?
i was looking for something that can scheduled calendar appt for a doctors office, where there can be multiple drs or multiple rooms etc.

Sorry there's no support for anything like this in this component.

I don't think it is possible with this package. I'd rather try with sth like this


placement and header of the notifications menu

Hi, I am working with Modus in Angular, and I'm trying to insert my own component for the notifications menu, but there is a static header that is not possible to remove.
It would be nice if the header for the notifications menu was optional or editable.

Also, as required by the UX design of my project, it would be great if the menu can be displayed on the right side of the screen as well:

Similar to the side navigation component.
Thanks :)

hi@rubie9816, we will be able to fix the static header in the notifications pop-up and regarding displaying the menu on the right side, we believe it is a use case and it could be achieved by a Side panel component (not Modus Side Navigation).

Thanks for your answer,
I have tried activating the notificationsMenuOpen event, but as the name suggests, it only detects the "open" action but not the close one, so if I want to hide the side panel I have no way to detect that action (maybe a Click event ?)
I also can't find a way to "hide" the default notification menu.
It would be great if you could give me an example of how to implement our own component (side panel) instead of the default notification menu  component (pop-up menu).

This is to reaffirm that Modus has approved the functionality for development.
cc @rubie9816
Note: Modus team tag the approved issues with modus-approved

Team Notes: We can proceed with the removal of the Notification Header.  We will need to split the ticket for the second request.
As for the side panel/utility panel, how much of a priority is this @rubie9816?


CoffeeScript Strings, Comments and String Interpolation

# this is a comment with a "string" inside
str = "an #{expression} is interpolated in this string"

Githubs Linguist gets this right (see above).
Prism doesn't.
Changing the order of the tokens will probably not be enough due to the nature of being able to embed any expression in #{} in double-quoted strings.

This looks fixed with the current version of the component.


Tooltip UX issues

(1) If you have the tooltip open and scroll before you move your mouse the tooltip stays open for a few seconds, and if you are focused on the info icon which opens the tooltip it stays open for the whole time you scroll
https://images.zenhubusercontent.com/360584111/e5e45f03-1828-4bf7-9a0f-d8176686fd5a/scroll_tooltip.mov
(2) If you click on a tag on the image card on the directory page the tooltip flashes before you are redirected to the details page

QA Notes:


remove psathyan from OWNERS file

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve
/lgtm


Corosync vs Pacemaker: wrong usage of "Corosync"

Corosync doesn't manage resources. Corosync provides reliable communication between nodes, manages cluster membership and determines quorum. Pacemaker is a cluster resource manager (CRM) that manages the resources that make up the cluster, such as IP addresses, mount points, file systems, DRBD devices, services such as MySQL or Apache and so on. Basically everything that can be monitored, stopped, started and moved around between nodes.
Pacemaker does not depend on Corosync, it could use Heartbeat (v3) for communication, membership and quorum instead. Corosync could also work without Pacemaker, for example with Red Hat's CMAN.
This is a documentation problem but also reflected in the names of the types this module provides. The Linux HA stack and its history as well as various cluster components are already confusing enough so it is important to not mix up terms.
I'll submit a PR for the Readme but I don't think it will be possible to rename the types this module provides at this point.

Just stumbled into this module and whole-hartedly concur. Pacemaker management is out of scope, should be a separate module.

Much of what hunner is discussing applies now that the module is under puppet-community. http://planck.nibalizer.com:5000/modules/puppet-community/puppet-corosync is even janky CI for it

Concerning crm_ vs. pm_ I disagree, by the way.
Yes, crm is a shell and as such not an integral part of pacemaker. But the Cluster Resource Manager is a thing that exists in any case and crmd is one of the components that make pacemaker tick (or beat?)
A pm prefix would be counter-intuitive because as far as I know, nothing in the LinuxHA ecosystem uses it to refer to pacemaker.

Is this still an issue?

yes

@kbon @bitglue @antaflos @hunner @ffrank
I want to give us the ability to rename this module for v6.0.0.

[ ] puppet-corosync
[ ] puppet-pacemaker
[ ] puppet-cluster
[ ] puppet-clustering
[ ] puppet-clusterlabs
[ ] puppet-ha

Also, what do we want for types?

[ ] cs_*
[ ] crm_*
[ ] cluster_*
[ ] pm_*
[ ] pacemaker_*
[ ] ha_*

Hi @roidelapluie, of course I'd gladly give my bike-shedding input, though I haven't been actively contributing here in a long time anymore ;-)
As for naming in general: in our internal infrastructure we made the historical error of introducing the "ha" term for a wrapper module, which just like "cluster" is awfully generic. In the meanwhile we've introduced Monit, not for clustering but for high availability regardless, and someday yet another HA or clustering tool will come along, doesn't align on all concepts (do they ever), and your module just doesn't make sense anymore: I'd avoid that path.
In that regard, I'd rename this module to puppet-pacemaker, as that's what this thing manages (both installation and configuration). If needed, split out corosync-specific stuff to a puppet-corosync module.
As for type names, @ffrank has a good point, crm_ still fits: even the Pacemaker RPM delivers many crm_ prefixed binaries. An alternative would be cib_ as everything ends up editing the cluster information base, but that could give the wrong impression this module edits the cib directly (who knows, someday). Though "pacemaker" isn't as short as "pm", "pm" makes me think of power management. Additionally the pm abbreviation isn't used anywhere else in the Pacemaker tooling afaik. A worthy alternative could be pcmk.
My vote gets shared between the crm, pcmk or pacemaker prefixes.

@kbon https://github.com/openstack/puppet-pacemaker that modules edits the CIB directly.

I am in favour of keeping puppet-corosync as corosync is always there in any stack. Me might rename to crm_ that might make sense. Like crm_resource instead of cs_primitive

@kbon's comments sound very reasonable to me. A cib_ prefix would be kind of neat, but crm_ is likely the better choice.
Renaming (essentially forking in the classic sense) to puppet-pacemaker could be done, but agree that puppet-corosync is close enough.

current status is: keep puppet-corosync -- move resources from cs_ to crm_
What about changing cs_primitive to crm_resource ?

Hmm, what's the reasoning here? I'm mostly impartial, leaning slightly towards sticking with "primitive".

Well primitive is not in the clusterlabs wording, is it?

@roidelapluie Primitive is indeed in the Clusterlabs wording, at least when using CRM.  Non-primitive resources are things like clone, location, colocation and group. You can see this in http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/ which is an older version of Clusters from Scratch that uses CRM, but also in the current edition http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Clusters_from_Scratch/ (search the page for primitive).
I believe the distinction has been abstracted away now that PCS seems to be the official CRM shell but since this module does not use PCS I think the type should be named crm_primitive, no?

@antaflos this modules uses both pcs and crm depending on the os. You are right, let's keep primitive.


Add first class support for setting timeouts via Hystrix.

Mentioned in #291, fixes #281

Codecov Report

Merging #295 into master will increase coverage by 0.02%.
The diff coverage is 83.33%.

@@           Coverage Diff            @@
##           master   #295      +/-   ##
========================================
+ Coverage   72.98%    73%   +0.02%
========================================
  Files         114    114
  Lines        2946   2952       +6
  Branches      208    209       +1
========================================
+ Hits         2150   2155       +5
- Misses        687    688       +1
  Partials      109    109

Impacted Files
Coverage Δ

...ay/filter/factory/HystrixGatewayFilterFactory.java
85.5% <83.33%> (-0.21%)
:arrow_down:

Continue to review full report at Codecov.

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

Good stuff @Fitzoh - just curious though, it is possible to set timeout by attaching configuration to a hystrix command this way:
hystrix:
  command:
    somecommand:
      execution:
        isolation:
          thread:
            timeoutInMilliseconds: 10000

Is this thought here that it is customized inline to where the circuitbreaker is defined.

Yep, that should way should still work fine @bijukunjummen...
@spencergibb should I maybe add another test configuration so we reference for both the DSL timeout configuration and Hystrix/Archaius configuration?

Now that I've had sleep, I don't think I want to start down this road. I'd rather the default Hystrix way be the only way rather than what we had to support in zuul.

Fair enough, I can probably get something together for #291 so it's at least documented


Corrected forward operations order

Fixes #ISSUE_NUMBER
Proposed Changes

the comment states [input -- > in --> lrelu --> ConvDS --> output] but the operation that happens in the code is [input --> ConvDS --> activation --> in --> output], which is inconsistent
this PR makes the code consistent with the comment

Checklist

[ ] CONTRIBUTING guide has been followed.
[ ] PR is based on the current GaNDLF master .
[ ] Non-breaking change (does not break existing functionality): provide as many details as possible for any breaking change.
[ ] Function/class source code documentation added/updated (ensure typing is used to provide type hints, including and not limited to using Optional if a variable has a pre-defined value).
[ ] Code has been blacked for style consistency and linting.
[ ] If applicable, version information has been updated in GANDLF/version.py.
[ ] If adding a git submodule, add to list of exceptions for black styling in pyproject.toml file.
[ ] Usage documentation has been updated, if appropriate.
[ ] Tests added or modified to cover the changes; if coverage is reduced, please give explanation.
[ ] If customized dependency installation is required (i.e., a separate pip install step is needed for PR to be functional), please ensure it is reflected in all the files that control the CI, namely: python-test.yml, and all docker files [1,2,3].

Since @Geeks-Sid wrote the initial module, I am requesting the review from him.

⚠ ⚠ ⚠
This PR is going to break all backward compatibility with unet and derived classes with trained models. Thus, it needs detailed discussion.

Also, if the operation order is changed to [input -- > in --> lrelu --> ConvDS --> output], the initialization for norm layer in __init__
self.in_0 = norm(output_channels, **norm_kwargs)

should be
self.in_0 = norm(input_channels, **norm_kwargs)

since norm now becomes the first layer.

Ah, I understand. So, there is going to be a breaking of backward compatibility regardless of the direction. Anyway, I will wait for @Geeks-Sid to comment on this.

Ah, I understand. So there is going to be a breaking backward compatibility regardless...
Anyway, @hongbozheng, you might need to take a look at the errors coming from the CI:

https://github.com/mlcommons/GaNDLF/actions/runs/9863809854/job/27237387798?pr=897
https://github.com/mlcommons/GaNDLF/actions/runs/9863809860/job/27237387817?pr=897

Ah, I understand. So there is going to be a breaking backward compatibility regardless...
Anyway, @hongbozheng, you might need to take a look at the errors coming from the CI:

https://github.com/mlcommons/GaNDLF/actions/runs/9863809854/job/27237387798?pr=897
https://github.com/mlcommons/GaNDLF/actions/runs/9863809860/job/27237387817?pr=897

I think the errors are caused by the issue I mentioned before, the norm layer initialization needs to be changed from
self.in_0 = norm(output_channels, **norm_kwargs)
                 ^^^^^^^^^^^^^^^

to
self.in_0 = norm(input_channels, **norm_kwargs)
                 ^^^^^^^^^^^^^^

as the error says ValueError: expected input's size at dim=1 to match num_features (64), but got: 32. which is exactly caused by the initialization of norm layer above.
The norm layer was initially the 3rd layer which performs norm after ConvDS (32 -> 64) that produces num_features=64, but it's now moved to the 1st layer which takes the num_features = 32 directly from the Input.
I'm not sure if I can still change the code in this PR.

Hey there, jumping in with the few notes from my side - now the implementation indeed looks correct in terms of compatibility with the ones in the comment, also the errors were caused by what @hongbozheng correctly shows - wrong input dimension in the norm layer, as now it is applied at different stage.
Overall LGTM.

Awesome, thank you for your comments, @Geeks-Sid and @szmazurek!
@hongbozheng - have you already signed the MLCommons CLA?

Awesome, thank you for your comments, @Geeks-Sid and @szmazurek!
@hongbozheng - have you already signed the MLCommons CLA?

I did yesterday, but I got the below email reply.
Thank you for submitting your request to contribute code to MLCommons GitHub repositories with the GitHub ID "hongbozheng." You are not currently listed in the designated employees section of the CLA for University of Illinois. We have reached out to our primary contact for University of Illinois regarding adding you to the CLA and will follow up with you once we hear back.

@hongbozheng - have you already signed the MLCommons CLA?

I did yesterday, but I got the below email reply.
Thank you for submitting your request to contribute code to MLCommons GitHub repositories with the GitHub ID "hongbozheng." You are not currently listed in the designated employees section of the CLA for University of Illinois. We have reached out to our primary contact for University of Illinois regarding adding you to the CLA and will follow up with you once we hear back.

Unless you are a paid employee of UI, you might need to ask them to updated this an "individual contributor"...

@hongbozheng - have you already signed the MLCommons CLA?

I signed the CLA and joined the MLCommons GitHub organization. I'm not sure what to do next to pass the cla-check.

@hongbozheng - have you already signed the MLCommons CLA?

I signed the CLA and joined the MLCommons GitHub organization. I'm not sure what to do next to pass the cla-check.

Thanks! I re-triggered the job and it passed. Welcome to the community! 😄


slides counter

Hello,
I want a slider counter callback, like "4 of 6".
is this possible?

oh sure. we have event callback. that is currently selected item index.
$('#myCarousel').on('select', function (evt, index) {
console.log('item selected : ' + index);
});
and you will know total count already.


developmemt

If you need to use this in the browser, you need to package it to do so. ANSI doesn't do much in the browser normally, not sure why you'd need it there.

If you need to use this in the browser, you need to package it to do so. ANSI doesn't do much in the browser normally, not sure why you'd need it there.

This component is installed with the webpack-cli installation package. In the development environment, this code will not be compiled by Babel, and the compiled code will show the arrow function, which cannot be opened in ie (the production environment has not been tested yet).

Why are you running webpack-cli in the browser?


Please remove "any subsequent sets were disturbed by newly bound pipelineLayout" warning

We - among many other Vulkan developers - are getting this warning in our code:

DescriptorSet 0x9dfc6 previously bound as set #0 is incompatible with set 0x392e9478 newly bound as set #0 so set #1 and any subsequent sets were disturbed by newly bound pipelineLayout (0x275)

It happens when we use a pipeline/pipeline layout with two sets, and then switch to a different pipeline layout that just uses set #0. The layers complain about the incompatibility and the fact that set #1 is disturbed by the new binding, however I don't intend to actually use set #1 anyway.
From what I understand, this issue could be solved if there was a way to call vkCmdBindDescriptorSets and say "I don't care about any other sets - this is a complete binding". This requires spec changes.
I believe this warning in its current state is actively harmful - it raises questions among Vulkan developers ("am I doing something wrong?"), followed by finding information that suggests that it's a false positive in validation layers (for example https://stackoverflow.com/questions/38679060/vkdescriptorset-from-previous-pipeline-giving-performance-warning) followed by either living with a stream of validation warnings, or disabling this specific warning in some hacky way in the validation report callback. As such, it seems strictly better to me to just remove this code from validation layers until a better solution for reporting whatever this warning is trying to report (which I must admit I don't fully understand) is found.

+1 to remove - this warning is pretty useless (at least for us).

+1, I find the warning more harmful than the problem it tries to warn about.

+1 kill with fire please.

Thank you!


blender water shader

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

I made the changes suggested by camperBot on your behalf.
LGTM

Congrats @Anutosh1 on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Remove --harmony flag from index.js shebang

The --harmony flag in the index.js file's shebang is causing issues in RDEs. Remove it as its not needed anymore (or maybe never was).
Change:
#!/usr/bin/env node --harmony

To:
#!/usr/bin/env node

Fixed in 1.3.0


Decorator flow errors: Covariant property getPropsForKey incompatible with invariant use

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Getting a flow error:

CompositeDraftDecorator
This type is incompatible with the expected param type of object type
Property getPropsForKey is incompatible:
Covariant property getComponentForKey  incompatible with invariant use in object type
.../node_modules/draft-js/lib/EditorState.js.flow:71

I'm getting the above error for getDecorations and getPropsForKey as well, essentially every method in CompositeDraftDecorator.
Here's my code. I also tried changing all the types to any, but the error persisted.
const findLinkEntities = (block: ContentBlock, callback: (number, number) => void, content: ContentState) => {
  block.findEntityRanges(
    (char: CharacterMetadata) => {
      const entityKey = char.getEntity();
      return entityKey ? content.getEntity(entityKey).getType() === "LINK" : false;
    },
    callback,
  );
};

type PropsT = { contentState: ContentState, entityKey: string, children: Node };

const Link = ({ contentState, entityKey, children }: PropsT) => {
  const { url } = contentState.getEntity(entityKey).getData();
  const style = {
    textDecoration: "underline",
    color: "#39a26f",
    cursor: "pointer",
  };
  return {children};
};

const linkDecoratorConfig = { strategy: findLinkEntities, component: Link };
const compositeDecorator = new CompositeDecorator([linkDecoratorConfig]);
const state = EditorState.createEmpty(compositeDecorator); // FLOW ERROR HERE

What is the expected behavior?
No flow error.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
DraftJS v0.10.4
Chrome Mac v63.0.3239.84

Same issue


Default folder when getting objects

When using the "get object" command, a file with a random identifier is created in the temp folder.
It often results on the same steps:

Copy path of the target folder
Go to file "temp" file and save as
Paste the folder
Remove the random id for clean file name

It should be possible to define folders within the workspace.
An idea is to have an additional settings for a pattern. For instance:
%x/%e/%o/%o-%n-%y%M%d-%h%m%s.xml

Where:

%x : workspace folder
%e: name of the environment (as the one display in the status bar)
%o: name of the object type (Rule, Form, etc.)
%n: name of the object
%y,  %M, %d, etc.: parts of the date

Please take a look at "Export Object" session at
https://marketplace.visualstudio.com/items?itemName=AndreiStebakov.sailpoint-iiq-dev-accelerator
It should get all objects in one folder, see if it works for you.
For your scenario it would probably be easier to just copy the content of
the object that you got and paste it in any target file with the name that
you need.
On Thu, Mar 16, 2023 at 9:26 AM yannick-beot-sp @.***>
wrote:

When using the "get object" command, a file with a random identifier is
created in the temp folder.
It often results on the same steps:

Copy path of the target folder
Go to file "temp" file and save as
Paste the folder
Remove the random id for clean file name

It should be possible to define folders within the workspace.
An idea is to have an additional settings for a pattern. For instance:
%x/%e/%o/%o-%n-%y%M%d-%h%m%s.xml
Where:

%x : workspace folder
%e: name of the environment (as the one display in the status bar)
%o: name of the object type (Rule, Form, etc.)
%n: name of the object
%y, %M, %d, etc.: parts of the date

—
Reply to this email directly, view it on GitHub
https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/41,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCZB6GAXAT4FXRBJ6BUO3W4MIILANCNFSM6AAAAAAV5GXNOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This is only available for all objects of the chosen object types

You can check the top check button which will select all object types so
you'll get them all.
On Thu, Mar 16, 2023 at 9:59 AM yannick-beot-sp @.***>
wrote:

This is only available for all objects of the chosen object types
—
Reply to this email directly, view it on GitHub
https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/41#issuecomment-1472031898,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCZBZHNVJLTIXLR275D7LW4MMERANCNFSM6AAAAAAV5GXNOA
.
You are receiving this because you commented.Message ID:
@.***>

Merged


🔹[EPIC] Github-pages for all examples

Description
All of our examples would benefit from having a github page wehre to showcase then

### Related Issues
- [ ] https://github.com/near/docs/issues/1883
- [ ] https://github.com/near/docs/issues/1884
- [ ] https://github.com/near/docs/issues/1885
- [ ] https://github.com/near/docs/issues/1886
- [ ] https://github.com/near/docs/issues/1887

All examples now have a github page

https://near-examples.github.io/hello-near-examples/
https://near-examples.github.io/counters/
https://near-examples.github.io/guest-book-examples/
https://near-examples.github.io/donation-examples/
https://near-examples.github.io/coin-flip-examples/


[Enhancement] Add more unit test for SNGAN_PROJ

add more unit test
fix bugs inSNGANGenResBlock and SNGANDiscResBlock with upsample (or downsample) is False
support pretrained argument

Codecov Report

Merging #53 (ca0200d) into master (2b89ebf) will increase coverage by 0.73%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage   75.06%   75.80%   +0.73%
==========================================
  Files         117      117
  Lines        7505     7507       +2
  Branches     1366     1366
==========================================
+ Hits         5634     5691      +57
+ Misses       1469     1443      -26
+ Partials      402      373      -29

Flag
Coverage Δ

unittests
75.80% <100.00%> (+0.73%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...rchitectures/sngan_proj/generator_discriminator.py
92.18% <100.00%> (+10.51%)
:arrow_up:

mmgen/models/architectures/sngan_proj/modules.py
98.87% <100.00%> (+19.78%)
:arrow_up:

...chitectures/stylegan/generator_discriminator_v1.py
89.83% <0.00%> (ø)

Continue to review full report at Codecov.

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


build/showMessage that shouldn't be a build/showMessage when using Mill BSP

Using Mill as a BSP server (version 0.10.7) I am often getting this message shown to me when using Metals. I don't believe this is a message that should be shown to the user. I see this is marked as debug in https://github.com/com-lihaoyi/mill/blob/main/scalalib/src/mill/scalalib/SemanticDbJavaModule.scala#L87, so I wouldn't expect this to be a build/showMessage from the build server.
[Trace - 08:32:57 pm] Received notification 'build/showMessage'
Params: {
  "type": 4,
  "message": "effective scalac options: List(-Xplugin:/Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scalameta/semanticdb-scalac_2.13.8/4.5.9/semanticdb-scalac_2.13.8-4.5.9.jar, -encoding, utf8, -Xsource:3, -explaintypes, -feature, -language:existentials, -language:experimental.macros, -language:higherKinds, -language:implicitConversions, -unchecked, -Xcheckinit, -Xlint:adapted-args, -Xlint:constant, -Xlint:delayedinit-select, -Xlint:deprecation, -Xlint:doc-detached, -Xlint:inaccessible, -Xlint:infer-any, -Xlint:missing-interpolator, -Xlint:nullary-unit, -Xlint:option-implicit, -Xlint:package-object-classes, -Xlint:poly-implicit-overload, -Xlint:private-shadow, -Xlint:stars-align, -Xlint:type-parameter-shadow, -Wunused:nowarn, -Wdead-code, -Wextra-implicit, -Wnumeric-widen, -Xlint:implicit-recursion, -Wunused:implicits, -Wunused:explicits, -Wunused:imports, -Wunused:locals, -Wunused:params, -Wunused:patvars, -Wunused:privates, -Wvalue-discard, -Vimplicits, -Vtype-diffs, -Xplugin:/Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scalameta/semanticdb-scalac_2.13.8/4.5.11/semanticdb-scalac_2.13.8-4.5.11.jar, -Yrangepos, -P:semanticdb:sourceroot:/Users/ckipp/Documents/scala-workspace/mill-scip, -Ystop-after:semanticdb-typer)"
}

Ahh, I think I found the issue here:
https://github.com/com-lihaoyi/mill/blob/876e2ac4e781640eedd1a4fe17bf7604002ebdb6/bsp/src/mill/bsp/MillBspLogger.scala#L53-L56
This probably shouldn't be directing debug messages to showMessage as these are meant to be helpful messages shown to the user.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.11 to before v5.15.5",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d1c263a031e876ac3ca5223c728e4d98ed50b3c0",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=10c22d9519f3f5939de61a1500aa3a926b778d3a"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d1c263a031e876ac3ca5223c728e4d98ed50b3c0",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "10c22d9519f3f5939de61a1500aa3a926b778d3a",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "NFSD: Fix exposure in nfsd4_decode_bitmap()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.5 by commit 10c22d9519f3f5939de61a1500aa3a926b778d3a, it was introduced in version v5.11 by commit d1c263a031e876ac3ca5223c728e4d98ed50b3c0. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002325


[🐞] When try to load component dinamically via import I get error

Which component is affected?
Qwik Rollup / Vite plugin
Describe the bug
Hi 😊
Currently, I can import any component by this way, the normal way:
import { $, component$, useClientEffect$, useStore } from<EMAIL_ADDRESS>import ComponentA from "~/components/component-a";
import ComponentB from "~/components/component-b";
import ComponentC from "~/components/component-c";

export default component$(() => {
  const tree = useStore(
    [
      { tag: "ComponentA", type: 1 },
      { tag: "ComponentB", type: 1 },
      { tag: "div", type: 0, class: "bg-green-400", content: "Hello" },
    ],
    {
      recursive: true,
    }
  );

  const changeComponent = $(() => {
    tree[0].tag = "ComponentC";
  });

  useClientEffect$(() => {
    // @ts-ignore
    window.changeComponent = changeComponent;
  });

  const components: Record<string, any> = {
    ComponentA: ComponentA,
    ComponentB: ComponentB,
    ComponentC: ComponentC,
  };

  return (
    <>

          {tree.map((element) => {
            if (element.type === 0) {
              const Tag = element.tag as any;
              return <Tag class={element.class}>{element.content}</Tag>;
            }

            if (element.type === 1) {
              // Works fine
              // const Component = components[element.tag];

              // Works fine
              // const Component = await import(`~/components/component-a`)

              // Fail
              const Component = await import(`~/components/${element.tag}`)

              return <Component key={element.tag} />;
            }
          })}

        <button onMouseDown$={changeComponent}>Click me</button>

    </>
  );
});

I tried it with success:
const Component  = await import(`~/components/component-a`)

But, if I wanna import some component dynamically (async) like:
const Component  = await import(`~/components/${element.tag}`)

It fails 😪 with error:
[plugin:vite-plugin-qwik] Dynamic import() inside Qrl($) scope is not a string, relative paths might break

In Vite, you can pass it with /* @vite-ignore */ comment, but I tried it too with no success.
Is there some way to achieve successfully this?
Reproduction
https://stackblitz.com/edit/qwik-starter-qnzpvu?file=src%2Fcomponents%2Fcomponent-b.tsx,src%2Fcomponents%2Fcomponent-c.tsx,src%2Froutes%2Flayout.tsx
Steps to reproduce
npm install && npm start
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @builder.io/qwik: ^0.15.2 => 0.15.2
    @builder.io/qwik-city: ^0.0.128 => 0.0.128
    vite: 3.2.4 => 3.2.4

Additional Information
No response

It's my understanding that if you build Qwik components correctly, there's no reason to use dynamic import(). The in-browser runtime loads everything on-demand already.

@mrclay  If the dynamicity is not about the on-demand loading but the programable loading by name as here, then I think it is still relevant

Same issue here. I want to load components (images as with .jsx ) dynamically as the data for loading is represented as a string in the database.
How am I able to load those based on this key dynamically? This is a fundamental requirement for larger projects.
@EggDice @oceangravity did one of you guys had any success with this?

This error happens even with no dynamic content. As long as you've got a back quote in the import() function, vite throw the error:
[vite] Internal server error: Dynamic import() inside Qrl($) scope is not a string, relative paths might break
  Plugin: vite-plugin-qwik
  File: <...>/icon.tsx:24:21
  24 |    const res = await import(`./icons/material/zoom_in.txt?raw`);
     |                       ^
  25 |    return res.default;
  26 |  });

All components are already loaded dynamically. So there is nothing to do here and no reason to lazy load them.
Any imports that are NOT relative should already work. (Import starting with ./ or ../ will not work (and can't work))
Imports such as icons/material/zoom_in.txt?raw can not work because they are vite tricks and only exist during build/dev time, not once the application is in production.

Same issue here. I want to load components (images as with .jsx ) dynamically, as the data for loading is represented as a string in the database.

I don't understand. If it is in the database, then import() will not help you, and you need to use some other RPC mechanism.
I am going to close this issue because this is either not needed or is working as intended. If you want to lazy load and you don't fall into categories 1, 2, or 3 above, please create a new issue.

@mhevery hey I mean the path or name of a component is read dynamically for the current user or page and I need to load it dynamically. So like mentioned by @oceangravity:
const Component  = await import(`~/components/${nameFromDatabase}`)

Is this possible with Qwik? I find that issue a lot, like if everyone is just building static sites but In big apps you need to load components dynamically based on information related to the user or a product.

Yes, the above is possible with caveats.

During build time, the qwik build system needs to have access to all components so that it can generate symbol IDs for it.
There needs to be a hashmap (could be on the server) that maps the name to a component.

Here is one way to do in Qwik: https://stackblitz.com/edit/qwik-starter-j55lca (but depending on your requirements it may be done differently)
import { Component, component$, useSignal, useTask$ } from<EMAIL_ADDRESS>import { server$ } from<EMAIL_ADDRESS>
export const getComponentFromDB = server$((name: string) => {
  return {
    cmpA: CompA,
    cmpB: CompB,
  }[name];
});

export const CompA = component$(() => A);
export const CompB = component$(() => B);

export default component$(() => {
  const Comp = useSignal<Component<any>>();
  const name = useSignal('cmpA');
  useTask$(async ({ track }) => {
    const compName = track(() => name.value);
    Comp.value = await getComponentFromDB(compName);
  });
  return (

      <input type="text" bind:value={name} />

dynamic component: {Comp.value && <Comp.value />}

  );
});

Ahh, that's interesting, thank you Miško.
But when you have a lot of components, would there be a possibility to get all components under a specific directory? That's how Vite solves it as far as I remember, so when Vite (or was it webpack?) detects a variable in an import statement, it does that hash map for you at build/dev time.
But manually maintaining the registry probably takes less time than writing and maintaining the plugin

In order to support resumability, the code has to go through an optimizer and each function needs to get a hash both on server and client. So there is more to it than just "loading"
So in general all lazy loaded code needs to be available to the optimizer at the time of compilation.

In order to support resumability, the code has to go through an optimizer and each function needs to get a hash both on server and client. So there is more to it than just "loading"
So in general all lazy loaded code needs to be available to the optimizer at the time of compilation.

That's out of question, just wondered if the imports could be generated from items like SVGs, images or components inside a specific directory by pointing to a path + var without the need of creating an index file containing all assets by hand.
But that is possible is already perfectly fine, just a bit cumbersome maybe to work with in case of updates, aka "Developer Experience" or "DRY" but it's more flexible I guess.
Thanks for clarifying though 🙏

Hi all
I'm trying to implement let's say something similar.
The project where I'm currently working uses a server-driven UI architecture but for a "regular website" and not for a mobile app using Vue 3.
This means that we don't build pages, only components, and then the page is built based on JSON returned from the server.
E.g:
{
  "name": "New Dashboard",
  "appearance": "Scene",
  "data": {
    "id": "unique-page-id-123",
    "layout": "MasterLayout",
    "title": "Dasboard",
    "description": "",
    "keywords": "",
    "components": [
      {
        "name": "counter",
        "appearance": "counter",
        "data": {
          "id": "unique-stage-1"
        }
      },
      {
        "name": "work",
        "appearance": "work",
        "data": {
          "id": "1",
          "type": null,
          "client": "Ficaat",
          "project": "Layout and Responsive HTML catalogue made to run on tablets (2013)",
          "description": "Layout and Responsive HTML catalogue made to run on tablets (2013)",
          "slug": "ficaat-tablet",
          "image": "ficaat_app.jpg"
        }
      }
    ]
  }
}

I already have it working when running dev mode but the problem comes when running the preview as it tries to load the TSX files and not a built js module.
Is there any way to make it work, or what I'm trying to do is not possible with Qwik?
https://stackblitz.com/edit/github-zlgpzh-2safe5?file=src%2Froutes%2Fdynamic%2F[slug]%2Findex.tsx,src%2Futils%2Fload-component.ts
To see it working in dev mode, just click on the hamburger menu and then click on "Dynamic Scene"
Thanks

@victorlmneves Make your dynamic component into a switch that imports each component separately

@appinteractive

But when you have a lot of components, would there be a possibility to get all components under a specific directory?

Something like import.meta.glob might be what you're looking for. It works both for importing components and their ?raw value.
Example :
const components = import.meta.glob("/src/registry/new-york/examples/*", {
  import: "default",
  eager: true,
});
const componentsCodes = import.meta.glob("/src/registry/new-york/examples/*", {
  as: "raw",
  eager: true,
});

type ComponentPreviewProps = QwikIntrinsicElements["div"] & {
  name: string;
  align?: "center" | "start" | "end";
  code?: string;
  language?: "tsx" | "html" | "css";
};

export const ComponentPreview = component$<ComponentPreviewProps>(
  ({ name, align = "center", language = "tsx", ...props }) => {
    const config = useConfig();
    const highlighterSignal = useSignal<string>();

    const componentPath = `/src/registry/${config.value.style}/examples/${name}.tsx`;
    const Component = components[componentPath] as Component<any>;

    useTask$(async () => {
      const highlighter = await setHighlighter();
      const code = componentsCodes[componentPath];

      highlighterSignal.value = highlighter.codeToHtml(code, {
        lang: language,
      });
    });

    return (

          ...
          <Component />

    )
  }
)

Benefits:

I don't have to import those components files by hand -> +1 for the DX since I have a lot of components (~80) and I expect to have more in the future.

Drawbacks:

It seems to take quite a toll on the dev server. ~40 components roughly add 7 seconds for the components and 7 seconds for their ?raw value for the dev server to show the page. I expect this to increase as the number of components increases. -> -1 for the DX.

This doesn't seem to affect performance once the dev server is up and running. I haven't had the ability/time to test this in production yet (because of a qwik-ui bug).
For my use case the drawbacks outweigh the benefits. +15 seconds or more every time I run pnpm dev is not worth it for me. I think I'll be better off by importing the components where they're needed and passing them through with a Slot. I think you should be able to do the same even with your user config coming from the database.

@victorlmneves Make your dynamic component into a switch that imports each component separately

@wmertens not sure if I got it. Can you detail?
Thanks

@appinteractive
Sorry for the oversight, it's actually possible to import.meta.glob without eager:true
Rectified example:
type ComponentPreviewProps = QwikIntrinsicElements["div"] & {
  name: string;
  align?: "center" | "start" | "end";
  language?: "tsx" | "html" | "css";
};

export const ComponentPreview = component$<ComponentPreviewProps>(
  ({ name, align = "center", language = "tsx", ...props }) => {
    const config = useConfig();
    const highlighterSignal = useSignal<string>();

    const componentPath = `/src/registry/${config.value.style}/examples/${name}.tsx`;

    const Component = useSignal<Component<any>>();
    const ComponentRaw = useSignal<string>();

    useTask$(async () => {
      const highlighter = await setHighlighter();

      Component.value = (await components[componentPath]()) as Component<any>;
      ComponentRaw.value = (await componentsRaw[componentPath]()) as string;

      highlighterSignal.value = highlighter.codeToHtml(
        ComponentRaw.value || "",
        {
          lang: language,
        }
      );
    });

    return (

          ...
          {Component.value && <Component.value />}

    );
  }
);

This doesn't seem to add much to dev server starting time and it does allow me to improve my mdx editing DX quite a lot.
So in my .mdx files,
instead of doing
import CardWithFormPreview from "~/registry/new-york/examples/card-with-form";
import CardWithFormCode from "~/registry/new-york/examples/card-with-form?raw";

<ComponentPreview code={CardWithFormCode}>
  <CardWithFormPreview q:slot="preview" />
</ComponentPreview>

where I have to add weird conditional logic with Slots if I want to pass different components (in my case I also have /registry/default, so I would have to find a way to display the right components based on user config).
I can simply do
<ComponentPreview name="card-with-form" />

And let my component handle everything for me :ok_hand: .

I think this is a great alternative to dynamic import. If it's not an issue for the optimizer I think it should be presented in the docs as it can significantly improve the DX for some use cases (especially in .mdx where there's no typescript auto-complete).
This would require a bit more testing (especially in prod), but I can work on a docs PR if you like the idea.

Let's say I am using Qwik's Responsive Images^1. I have a number of images I want to optimize, and instead of manually importing each of them:
import Image1 from "./image1.jpg?jsx"
import Image2 from "./image2.jpg?jsx"
import Image3 from "./image3.jpg?jsx"
// etc.

I would like to do it in a bit more concise way with import(), eg.:
const images = imagePaths.map(path => import(path).then(module => module.default))

I can't think of any alternative ways of doing this currently.

Hi!
The last example suggested by @maiieul in this issue seems not to be working anymore, just as the example in the documentation https://qwik.dev/docs/cookbook/glob-import/ does not work as well.
As @dhnm mentioned, we need the tool to dynamically load the images. I have data structures containing image file names and would really like to use the Qwik way to import those images, instead of manually specifying each.
I've made it work, but I still have a bug.
Please advise how to handle the error:
(index):366 QWIK ERROR Code(30): QRLs can not be resolved because it does not have
an attached container. This means that the QRL does not know where it belongs inside the DOM,
so it cant dynamically import() from a relative path.
/src/components/slides/tools/getlazyimagecomponent_server_metacomponent_yoh0mayxono.js?_qrl_parent=tools-icon.tsx GetLazyImageComponent_server_MetaComponent_Yoh0mAyxono Error:
Code(30): QRLs can not be resolved because it does not have an attached container. This means that the QRL does not know where it belongs inside the DOM, so it cant dynamically import() from a relative path.
    at createAndLogError (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:159:54)
    at logErrorAndStop (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:108:17)
    at qError (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:315:12)
    at Object.importSymbol (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:333:23)
    at resolve (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:8667:44)
    at resolveLazy (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:8674:49)
    at http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:8678:39
    at qrl (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:8606:30)
    at invokeApply (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:4536:26)
    at invoke (http://localhost:5174/node_modules/@builder.io/qwik/dist/core.mjs?v=faddbb96:4528:24)

Steps to reproduce (maybe there are other ways if you know the nature of the problem):

Start with any other page
Navigate through the website
Click on the to the link to the page with the images
The next page loads for a few seconds and stops loading and reacting to user interaction, leaving the user on the previous page.

Images are loaded fine if you start with the page with images.
Here is my code.
The error appears somewhere outside the component.
import {
  $,
  type Component,
  component$,
  useSignal,
  useTask$,
} from<EMAIL_ADDRESS>import { server$ } from<EMAIL_ADDRESS>
/*
This based on
https://qwik.dev/docs/cookbook/glob-import/
https://github.com/QwikDev/qwik/issues/2643
*/

const metaGlobComponents: Record<string, any> = import.meta.glob(
  '/src/media/**/**.*',
  {
    import: 'default',
    query: 'jsx',
    eager: true,
  }
);

export const GetLazyImageComponent = server$((path: string) => {
  // possible paths:
  // 'file.png'
  // /images/technologies/svg/react_clean.svg
  const brokenDownPath = path.split('/').filter(pathPart => !!pathPart);
  let fullPath = `/src/media/images/technologies/active/${path}`;

  if (brokenDownPath[0]==='images') {
    fullPath = `/src/media/${brokenDownPath.join('/')}`
  }

  if (!metaGlobComponents[fullPath]) {
    return;
  }
  const val = metaGlobComponents[fullPath]();
  const MetaComponent = $(()=>val);
  return MetaComponent;
});

export default component$((props: any) => {
  const MetaComponent = useSignal<Component<any>>();

  useTask$(async () => {
    const qrlAsyncFunction = await GetLazyImageComponent(props.path)
    if (!qrlAsyncFunction) {
      return;
    }

    // eslint-disable-next-line qwik/valid-lexical-scope
    MetaComponent.value = (await qrlAsyncFunction) as unknown as Component<any>;
  });

  return <>{MetaComponent.value && <MetaComponent.value />}</>;
});

Thank you!

Hi @tgskiv 👋 I assume it stops working for you in 1.8.0?

Hi @maiieul thanks for the response and sorry for not specifying it in the comment.
It was 1.7.2, now 1.8.0 but it still can be reproduced.

@tgskiv can you try with eager false?

@vmertens I'm currently proceeding the same task. With eager false it just doesn't load images, with eager true everything seems ok. BUT I have a usecase where I show the same images on 2 pages, 1 carousel, other is tiles.
Carousel is static and images load normally, but tiles are dynamically paginated and if I switch to this kind of import and try to navigate to the second page I receive "[vite] Internal server error: Dynamic import() inside Qrl($) scope is not a string, relative paths might break"


use local Docker credential to login private registry

Is your feature request related to a problem? Please describe.
Hi, I want to use local Docker credential to login private registry,
Describe the solution you'd like
I can choose to use local Docker credential or using WithRegistryAuthentication to login docker.
Describe alternatives you've considered
I use 1.5 version Currently  , login by WithRegistryAuthentication
Additional context
None
Thank you very much.

Do you get any error? My test case works fine with docker.io:
.WithImage("<account_name>/<image>")
.WithRegistryAuthentication("https://index.docker.io/v1", "<account_name>", "<account_password>")
.Build();

The Docker credential store, is not supported yet. If you would like to contribute, your help is more than welcome.

I want to use Docker credential store so I can use docker login on CI.

I want to use Docker credential store so I can use docker login on CI.

Sorry, I got that wrong. I thought, you're saying WithRegistryAuthentication does not work. As I said, the Docker credential store is not implemented yet. Would you like to contribute? Help is much appreciated.

Thank you very much!
have some example can give me reference XD?

Just run docker login. You can check the type of the credential store in your Docker config. Usually, at ~/. docker/config.json.


Update indexing plug-in to version 2.0

Description
Update org.dita.index plug-in to version 2.0.
Motivation and Context
Fix compatibility with DITA-OT classes.
How Has This Been Tested?

Type of Changes

Bug fix (non-breaking change which fixes an issue)

Documentation and Compatibility
No user facing changes.

Thanks @jelovirt!


KeyError: 'USD_BTC'

Lending EUR in Bitfinex, sometimes this error comes up. Any idea what it is about? Lending does seem to work fine though (atm I'm only lending EUR, not USD or BTC).
Traceback (most recent call last):
File "lendingbot.py", line 114, in
Lending.lend_all()
File "/home/pi/poloniexlendingbot/modules/Lending.py", line 252, in lend_all
usable_currencies += lend_cur(cur, total_lent, lending_balances, ticker)
File "/home/pi/poloniexlendingbot/modules/Lending.py", line 475, in lend_cur
raise msg
KeyError: 'USD_BTC'
v327
Unhandled error, please open a Github issue so we can fix it!

It seems that this issue was due to the minloansize being less than what is accepted by the exchange. After setting it to 50 the issue has not come up again.


Examples and Docs on using GPT-vision Models with structured extraction,

using images to extradt structured data would be cool, i bet it works well with json mode

Is json mode supported by gpt-4-vision-preview?. The docs only mention support for gpt-4-1106-preview  and gpt-3.5-turbo-1106. Though an example chaining a call from gpt-4-vision-preview to a model that supports structured output like json mode or function calling would be helpful to people

Hey @jxnl. I think this would be a great idea.
I started working on this repo: Object Detection using OpenAI GPT4-V
In the main.py file you can see the long system instructions and where I am doing string manipulating and casting to JSON:
content = response.choices[0].message.content
json_str = content.strip('`json\n') # Extract the JSON part from the string (remove the ```json and ``` at both ends)
coordinates = json.loads(json_str) # Convert the JSON string into a Python dictionary

I've been getting good results...
but lets say you try to ask a question like "Detect balloons" and there are no balloons in an image - you get an error trying to grab the data.
The response can be predictable, if the prompt is predictable.
This is where instructor would be awesome. You could have default values, cleaner prompt messages in the docstring and field annotations etc etc.
Tried a basic example with instructor here. But as @shanktt said gpt-4-vision-preview does not support functions and response_format.
  File "/Users/waseemh/Projects/image-detection-openai/venv/lib/python3.11/site-packages/openai/_base_client.py", line 842, in request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/Users/waseemh/Projects/image-detection-openai/venv/lib/python3.11/site-packages/openai/_base_client.py", line 885, in _request
    raise self._make_status_error_from_response(err.response) from None
openai.BadRequestError: Error code: 400 - {'error': {'message': '2 validation errors for Request\nbody -> function_call\n  extra fields not permitted (type=value_error.extra)\nbody -> functions\n  extra fields not permitted (type=value_error.extra)', 'type': 'invalid_request_error', 'param': None, 'code': None}}

I assume gpt-4-vision-preview will allow functions and response_format in the near future - but do you have any thoughts on how we can have it supported in the mean time.
Maybe this "patch" could be helpful for other future features OpenAI releases.

Looks like need to support something else like code block mode.

Beat me to it @Anmol6. Looking forward to this fix.

Is json mode supported by gpt-4-vision-preview?. The docs only mention support for gpt-4-1106-preview  and gpt-3.5-turbo-1106. Though an example chaining a call from gpt-4-vision-preview to a model that supports structured output like json mode or function calling would be helpful to people

Unfortunately not a planned feature as of yet: https://github.com/openai/openai-node/issues/469#issuecomment-1804985848

@jxnl can we close?


[DONT MERGE] Add dummy file just to check if CI is green

This PR is just to check whether there the CI is green or not

We already have a PR for that: #5009. Closing this to avoid duplicates.

Re-opening, because I missed that it uses the release branch as base.

@pmeier I think we can be a bit more lenient to allow people create dummy PRs to check the CI, as long as they close it in due time.

I agree with the sentiment. If this PR was using main as base, I felt it was justified to close and simultaneously to inform that we already have something like that (no changes and just checking CI). Basically the same what I did on your PR in https://github.com/pytorch/vision/pull/6017#issuecomment-1127284180.
Of course I blundered and base is not main making the other PR irrelevant. The same were true if a test PR introduces any changes.

@pmeier I like the proactiveness to keep things clean. We should remain proactive and perhaps eliminate some of the hundreds of stale PRs from years ago.
But for the CI case, I don't think it adds any value closing the PRs like that. While on-call, we often need to indicate to the Release Engineering team that the main branch is broken and provide proof. Redirecting them to a PR with 10+ commits adds unnecessary complexity as they need to confirm that this is indeed a dummy commit on top of main. For all these reasons, I suggest to leave people close their own dummy PRs, provided they haven't left them there forever.


Standard format for Enumeration

Would it be useful to provide a standard format for values of an arbitrary Enumeration type?
I have a working implementation, though it relies on an implicit type evidence of the specific enum type provided by the user. I could use reflection instead, but that seems less desirable.

I'd like to see said implementation, even if it's not part of the project, I could use it :)

Since I ended up finding this after digging around on the internet for an example, I'll paste the example I found
import spray.json.{DeserializationException, JsString, JsValue, RootJsonFormat}

/**
  * Based on the code found: https://groups.google.com/forum/#!topic/spray-user/RkIwRIXzDDc
  */
class EnumJsonConverter[T <: scala.Enumeration](enu: T) extends RootJsonFormat[T#Value] {
  override def write(obj: T#Value): JsValue = JsString(obj.toString)

  override def read(json: JsValue): T#Value = {
    json match {
      case JsString(txt) => enu.withName(txt)
      case somethingElse => throw DeserializationException(s"Expected a value from enum $enu instead of $somethingElse")
    }
  }
}

Use like:
implicit val enumConverter = new EnumJsonConverter(YourEnum)

@dkowis I have created a PR, #336, based on your code to add it as an example.

@dkowis I have created a PR, #336, based on your code to add it as an example.

But it's not PR to code itself, it's just PR to README.md :)
Can collaborators introduce this feature (support for Enumeration formats) in future updates?


If a quay repo is manually added, but it doesn't use automated builds, then none of the build information can be found and populated in the database

Currently the code will iterate over quay builds, but instead it must iterate through the quay tags.  Then it will be able to pull information such as the size if the container.

https://quay.io/api/v1/repository/dockstoretestuser/quayandgithub/tag/

Also consider the problem where you don't have any auto builds or manual builds.  There won't be any tags that exist, so the container should not be added.  Use the Quay API to check if such a tag exists for the given namespace and container, and if so deny manual register.  This will solve the issue of someone trying to manually register a quay container that has no auto builds.

Actually it seems that when you first push a docker image to Quay, it will generate the latest tag even if there are no autobuilds. However you can delete this tag.

Really this issue is about solving a few problems:

If you try and manually register a quay container which has no tags (thus associated image), then the image can't be added (UI and CLI).
If you try and manually register a quay container which has at least one tag, but no builds, then the image can be added, though the user will have to give the git branch for the given tag.

The second issue is already solved, so just the first one needs to be looked at.
Also there is no need to iterate through quay tags if there is no auto build, as this is already implemented.


Could not find module ember-infinity/mixins/route

I am trying to Implement infinite-scrolling using ember-infinity. I have followed the documentation only but I am getting error "Could not find module ember-infinity/mixins/route"
Below is my code:
`
import Ember from 'ember';
import InfinityRoute from 'ember-infinity/mixins/route';
     export default Ember.Route.extend(InfinityRoute,{
     store: Ember.inject.service(),

model(){
    var inflector = Ember.Inflector.inflector;

    inflector.irregular('feed', 'feeds.php');
    inflector.uncountable('advice');
    let user = JSON.parse(localStorage.getItem('user'));
    let token = localStorage.getItem('token');
    if(user != null){
        //return this.get('store').query('feed',{page:1,userid:user.id,token:token});
        return this.infinityModel("feed", { perPage: 12, startingPage: 1,userid:user.id,token:token });
    }
} ,
actions:{
  getDetails(feed){
    console.log("Getting details of "+feed.id);
  }
}
 });

`
Version I am using 0.2.8
EMber-js version 2.0+

hi @kgcorner - the only reason this would happen is if ember-infinity is not properly installed.  (Perhaps someone npm installed it but didn't persist it to package.json)
try ember install ember-infinity from the root of your app.


Allow Gradle to export CopySpec as map

Feature Request Description
Please add support for exporting a CopySpec object (from War, Jar, etc.) to a map or text. This is a great feature that allows us to deploy exploded packages without actual copying, right from Gradle's:

static resources folders (src/main/webapp, etc.)
cached libraries (~/.gradle/caches/modules-2/files-2.1/...)
output folder (build/classes, etc.)

I've asked how to do this on stackoverflow some time ago and it seems there is no evident way until this is implemented as a Gradle feature.
Example
Incoming file build.gradle
war {
  destinationDir temporaryDir
  into 'META-INF/resources', { from 'src/html/index.html' }
  into 'META-INF/resources/static', { from 'src/css' }
  into 'META-INF/resources/static', { from 'src/images' }
}

Desired build mapping for Tomcat 7 - $CATALINA_HOME/Catalina/localhost/myapp.xml
<Context docBase="">
  <Resources className="org.apache.naming.resources.VirtualDirContext" extraResourcePaths="
    /META-INF/resources/index.html=C:/myapp/src/html/index.html,
    /META-INF/resources/static=C:/myapp/src/css,
    /META-INF/resources/static=C:/myapp/src/images
  "/>
</Context>

Desired build mapping for Weblogic - .beabuild.txt
C\:/myapp/src/html/index.html=META-INF/resources/index.html
C\:/myapp/src/css=/META-INF/resources/static
C\:/myapp/src/images=/META-INF/resources/static

Could someone at least add labels for the issue?
It seems to me that this feature request can speed up development build a lot.

Why don't you just use the convention and store everything under src/main/webapp instead of copying from various non standard locations? Then you could have a single mapping from / to C:/myapp/src/main/webapp

Hello @uklance . I've update my question on StackOverflow too. I can't just restructure a project because (just an example):

I have some excluded files that I don't want to bring to the output folder.
I want to map several source folders to one output folder (e.g. build/classes and build/resorces both should be added to the one virtual JAR).
I want to map existing gradle caches to the virtual JAR.

Example for EAR file (.beabuild.txt mapping file used by Weblogic):
G\:/gradlehome/.gradle/caches/modules-2/files-2.1/org.springframework/spring-aspects/4.2.1.RELEASE/1ccea288d056d6b71839b07f09c5d663f9d98104/spring-aspects-4.2.1.RELEASE.jar = APP-INF/lib/spring-aspects-4.2.1.RELEASE.jar
G\:/gradlehome/.gradle/caches/modules-2/files-2.1/org.springframework/spring-instrument/4.2.1.RELEASE/88ae98a6ca8439e118807f8a3db8af2f1b8b1b65/spring-instrument-4.2.1.RELEASE.jar = APP-INF/lib/spring-instrument-4.2.1.RELEASE.jar
G\:/gradlehome/.gradle/caches/modules-2/files-2.1/org.springframework/spring-oxm/4.2.1.RELEASE/327df2a0b268a838492d9a15d015f0495debf42b/spring-oxm-4.2.1.RELEASE.jar = APP-INF/lib/spring-oxm-4.2.1.RELEASE.jar
G\:/gradlehome/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-web/4.0.2.RELEASE/86f6306aa201a69d37e84fa556bd15cf79752591/spring-security-web-4.0.2.RELEASE.jar = APP-INF/lib/spring-security-web-4.0.2.RELEASE.jar
C\:/repo/subprojects/wi/src/main/webapp = wi.war
C\:/repo/subprojects/wi/build/classes/main = wi.war/WEB-INF/classes
C\:/repo/subprojects/wi/build/resources/main = wi.war/WEB-INF/classes


Creating ANYTHING in GB Studio 2 Beta 1 Breaks

Please fix this in Beta 2, it's so broken that i can't even make my own project or force myself to use GB Studio 1, as it says "Creating", but it's not actually creating
Windows 10/NT 10.0

Hi @WindowsXP2001 This issue is fixed in the latest developer release, I'm going to be putting out a second beta very soon that fixes this and a number of other issues spotted in beta1.
The issue is with the path picker button choosing a random file in the folder you picked rather than just the folder. If you look in your screenshot if you deleted the desktop.ini\ from the end of that field so it only contained C:\Users\lt876\OneDrive\OneDrive\Documents\ I think you'll be able to make a project as expected.


Don't work on ContentView, Grid, StackLayout in C#

Don't work on this(ContentView), layout(Grid or StackLayout). Work only on text (Label)
My code:
public class TabbarButton : ContentView
{
public TabbarButton()
{
BackgroundColor = Color.LightGray;
        var text = new Label { VerticalOptions = LayoutOptions.Fill, HorizontalOptions = LayoutOptions.FillAndExpand };

        var layout = new Grid
        {
            HorizontalOptions =LayoutOptions.FillAndExpand,
            Children =
            {
                text
            }

        };
        HorizontalOptions = LayoutOptions.FillAndExpand;
        Content = layout;

        TouchEffect.Init();
        TouchEffect.SetColor(text, Color.Red);

        Commands.SetTap(text, new Command(() => Debug.WriteLine("ELO")));

    }
}

You have to call Init method in native projects, not in XF.
Show me pls how you use these effects in ContentView, Grid, StackLayout.

public class TabbarButton : ContentView
{
public TabbarButton()
{
BackgroundColor = Color.LightGray;
HorizontalOptions = LayoutOptions.FillAndExpand;
        var layout = new StackLayout
                {
                    Children =
                    {
                        new Label {Text = "Test"}
                    }
                };

        Content = layout;

        TouchEffect.SetColor(layout, Color.Red);

        Commands.SetTap(layout, new Command(() => Debug.WriteLine("ELO")));

    }
}

What version of XF?

XF <IP_ADDRESS>635

Ah, yes I still not add support latest XF version...
If you strongly need now use this lib then be patient and change XF version to 2.3.4.*

Ok, thank you. Some approximate release date?

This week for solve this

Same problem here

@gaffkins, @luismts pls try new version 1.4.0-pre for Xamarin.Forms 2.5+
Nuget package should be available in hour.


test-branch/execute-job/comment-from-wrong-user-on-pr/f56155ac-f953-49f4-8373-e77986cc8ae1

PR for testing dc9b0c1325ff1c9793a27511e1b0bddd062608c6

/canonical/self-hosted-runners/run-workflows dc9b0c1325ff1c9793a27511e1b0bddd062608c6


Access to parent repeater item in update event

Hey,
I got the follow scenario:

                             {{product.name}}

Is it somehow possible to access the shelf property of my outer repeater, inside the update event of the sortableOptionsList[0] setting? Update event supplies me the list of UL-Elements but I have to access the element above.
Hope it's understandable :-/
Thanks for great support!

Unfortunately, this has to be done in the controller, by having it assigned to a local var. In case you have multiple lists, you should probably also check which one contains the moved item.
A hacky way that will not work on DisabledDebugInfo invironment would look like this:
ui.item.source.scope().shelf

PS : Didn't actually tested the above code, but it demonstrates the concept of this hacky approach.


Derived Column support in Refinery

Is your feature request related to a problem? Please describe.
Some customers have created some great derived columns within honeycomb to pull useful information out of their data, but sometimes they'd like to be able to use those columns within their Sampling rules and field lists.  It would be super cool if we could put Derived Columns into the config of Refinery to be able to reference them, or maybe use an API key to pull the derived column logic from honeycomb and use it in Refinery.
Describe the solution you'd like

Be able to define derived columns in the configuration, or point to derived columns defined in honeycomb
Use those derived columns in Refinery's rule conditions and/or field lists

Describe alternatives you've considered
Obviously, doing these transformations in the collector or doing them in the instrumentation is doable, and would not require any work in Refinery.
Additional context

We have thought about giving refinery a rules configuration model that allows for greater freedom.
It wouldn't be THAT big a deal to support expression-based conditions with AND and OR, plus math -- could be done with an alternate field in the existing YAML structure for conditions, maybe something like Expression: "duration_ms > 1000 OR span_count > 5000"
The problem with that is that it isn't the DC format. We could implement the DC language, but I've resisted that because it's very user-unfriendly without infix operators -- IMO, it's harder to read than the existing YAML.
That said, it's a really interesting idea to think about being able to read DCs from the API and make them available in Refinery. Do you think it would be enough to allow someone to reference a DC by name, without also giving them the ability to define one in Refinery? (Not having to deal with parsing errors would save implementation time.)
We'd probably check them at configuration load time and cache them locally, and most likely only invalidate them once an hour or so.


NPM lockfile versions do not match

For context:
So I have a little different of a use case to the main 'firebase' one that others seem to have but it seems to mostly need to achieve the same things. In effect what I want to be able to do is take a package from my monorepo with all its dependencies (as in, able to be npm instaled later) and place its built artefacts into a docker image.
The issue I'm having is that the lockfile is re-generated from scratch in the isolated package and it pays no attention to the current lock file at the workspace root. This means if one of the dependencies are not pinned correctly it could cause a difference in execution between running any code inside my isolated package vs my monorepo itself.
Of course, ideally my package files would be well defined and any dependencies should be pinned or at least specify a proper version range, but this isn't always the case and I think the default behaviour of effectively ignoring the workspace lockfile could be dangerous to those not aware of this.
This is why I believe this may be a bug. I did some testing myself and managed to get it to work if I copied the workspace package-lock.json to the isolateDir in generate-npm-lockfile.ts and then await arborist.loadVirtual() before building the ideal tree. I'm not too well versed in using the arborist package (so that last step may be unnecessary) but this seemed to generate a lockfile as I expected with the same dependencies as were defined in the workspace itself.
Please let me know if you need any more information.

@TomCaserta Thanks for reporting. We might have messed this up along the way... I'm surprised that you are the first to report it. Maybe not a lot of people use NPM anymore with this package.
Having the versions in the isolate output the same as the original lockfile is one of the fundamental things that you'd use this for. In that sense your use-case is no different from the others. If you deploy to Firebase you'd still want to make sure your deployed code is using the original lockfile versions.
Initially, I could only get NPM to work by moving the entire node_modules folder to isolate and then moving it back after isolation was done, which was or course both fragile and hacky.
Later someone reported that it also works fine without moving the folder, and maybe I didn't properly verify that, but then we removed that step...
I'm not familiar with Arborist either.
In your workaround, does the process still generate a pruned lockfile, or does the lockfile contain everything? Having locked versions is more important so if you want to submit a PR I would be willing to accept it.
I don't have much time to work on this but I'll try to verify this problem myself in the coming weeks.

@TomCaserta I can see the issue, but unfortunately I am not able to reproduce your solution.
I've published 1.20.0-2 under @next, so you could try that. It calls loadVirtual but I don't see it working. I tested it in mono-ts in the use-npm branch. The root lockfile has firebase-admin locked to 12.1, but the resulting lockfile still shows 12.7 for me.

Thanks for your response!
Looking at the code there it doesn't look different to the patch I applied to the built libraries dist (besides naming and the fact I wasn't using path join ofc):
+++ b/node_modules/isolate-package/dist/isolate-bin.mjs
@@ -1,5 +1,3 @@
-#!/usr/bin/env node
-
 // src/isolate-bin.ts
 import console2 from "node:console";
 import sourceMaps from "source-map-support";
@@ -406,6 +404,8 @@ async function generateNpmLockfile({
       throw new Error(`Failed to find node_modules at ${nodeModulesPath}`);
     }
     const arborist = new Arborist({ path: isolateDir });
+    await fs9.copy(workspaceRootDir +'/package-lock.json', isolateDir + '/package-lock.json')
+    await arborist.loadVirtual();
     const { meta } = await arborist.buildIdealTree();
     meta?.commit();
     const lockfilePath = path7.join(isolateDir, "package-lock.json");```

One thing I do notice is that I was patching version `1.19.0` so could be the other changes in `1.20.0+` that makes this not function (or perhaps it's only working in my repo due to some other configuration or pure coincidence).

In any case, I will give your fix a test in my repo and see if it has different behaviour to the patched version that has been working and debug further.

Hi Tom, Thanks for diving deeper. That seems plausible.
To be honest I am not willing to spend a lot of time on this. This library already cost me way more time than I initially imagined. I'm happy that PNPM support is solid at least, because that covers my personal needs.
I tried reading the Arborist code, but I find it hard to read, so I'm putting my hopes on other people like you to figure this out  if you care enough about NPM.
In the meantime, I would recommend anyone to use PNPM, especially for monorepos. I think the transition was painless and I'm enjoying things like recursive interactive dependency upgrades and Node version managing.
But with loadVirtual we are at least one step closer to the desired behavior. If it makes things work for only a part of the use-cases I still think it's worth merging.


After Update nothing work and no style transfer, but before Update it work perfectly !!! and I get cool results !!! please help me...

this is my old workflow before update look at the result:

but after update it just didn't work even with the same settings :

and here is the reference image :

model: dreamshaper_8LCM
please help me :(

Me three :(
Would be super appreciative to see this fixed!

While we await our awesome developer friend to make the new version work I was able to retrieve the previous one from a backup and it's working for me, I hope this helps!
https://drive.google.com/file/d/1kuYcOtfCDGVgK5xe7_3HcxsAnAdh4Pve/view?usp=sharing

HI Mr Developer, can you please investigate and fix this please?

Same here. Not working at all, with any settings.


turbo-geth: 2020.11.03 -> 2020.11.04

Motivation for this change
new version
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

hash mismatch in fixed-output derivation '/nix/store/88ci4b5hviz0r3qxcsslb9226mcw22fi-source':
  wanted: sha256:1d7nxxrf53yv3dsm88p5n947sdzz7sq4h7nm3kshm9124z5ilvby
  got:    sha256:1iidj7cvpazk2v419l6k7h67rkx0mni3fcxfjpwrp0815fy1c2ri
cannot build derivation '/nix/store/9skz88f1n2chwnwghlmcn4snnwngxkp7-turbo-geth-2020.11.04-go-modules.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/6qh1whbbf5cxrkvk3kfjdfijsk6v3g9x-turbo-geth-2020.11.04.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/zbyi1d7vywng9iccsfcxvagsq05cb2f5-env.drv': 1 dependencies couldn't be built

oh wow, no idea how this happened, I definately had working 2020.11.04 binaries with the previous derivation. Thanks for the catch!

Result of nixpkgs-review pr 105032 1

1 package built:

turbo-geth


Error: unrecognized command line option ‘-Wno-covered-switch-default’

When compiling version 2.0。0, this error occurred：
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'TritonRelBuildWithAsserts', '-j128']' returned non-zero exit status 2.
Looks like it's caused by this：
cc1plus: error: unrecognized command line option ‘-Wno-covered-switch-default’ [-Werror].
how to deal with this

Did you solve this problem? I got same error


chore(deps): update deps

Update dependencies, why because:

Most of these include bug fixes
Some of these are performance improvements (next v13.1)
Nothing breaks, but if don't update dependencies regularly then everything will soon.

I think this PR might not be needed anymore. I did a bunch of updates in my testing PR which got merged today.

@dan-mba I'm kind of still trying to merge the changes because it isn't the easier. I'm marking this PR as draft for right now

I understand, but wanted to make sure this didn't get accidentally merged by someone trying to keep up with the flood of PRs

Thanks for updating the dependencies 👍 it is good to do these often 💯

I do not know what just happened. I synced the forks

@dan-mba, now this PR only updates the other two dependencies that haven't been updated 👍

If there are changes in the package file, we need to include changes to the lock file as well in this PR

Yes @eddiejaoude, actually I'm waiting for this PR to approved (ready to merge or something) and then I can package-lock.json so it's merged in quick succession and that there aren't any conflicts

Conflict, we proabaly need to merge this soon after it is recreated. Let's try tomorrow
Btw don't resolve the conflicts, just regenerated the file


Migrate ApprovalController to BaseControllerV2

This PR migrates the ApprovalController to BaseControllerV2. Its functionality is exactly the same as before, with the exception of some name changes for clarity, and the addition of controller messenger actions.
The method resolve has been renamed to accept, which is a breaking change.

I added events to be emitted when requests are approved or reject in the latest commit (4d5be86 at the time of writing). I'm not certain that we'll actually use them in practice, so I'm down to move them to a separate PR, or whatever we may desire.


Running detektBaseline generates too general exceptions, disabling rules

Expected Behavior
When generating a baseline for a code base, only the existing issues should be ignored when using it.
Observed Behavior
Running detektBaseline via gradle generates files that contains lines such as
<ID>NoBlankLineBeforeRbrace:</ID> which have no reference to a specific instance of the violation. This results in the rule being ignored entirely in the module when using the baseline file.
Steps to Reproduce
Steps to reproduce is uncertain. This issue was seen when running detektBaseline on a multiple module android project with many (~1000) issues in existing code.
Context
When trying to add detekt to a project and generate a baseline to avoid failing builds on old issues, it ends up disabling rules for new code as well.
Your Environment

Version of detekt used: 1.6.0
Version of Gradle used (if applicable): 5.4.1
Operating System and version: OSX
Link to your project (if it's a public repository):

@BraisGabin Also probably important to note that it wasn't just formatting rules. Here's the rules that I'm seeing the issue with

CommentSpacing
Indentation
MaximumLineLength
MultilineIfElse
*NoConsecutiveBlankLines
NoEmptyClassBody
NoWildCardImports
ParameterListWrapping
SpacingAroundColon
SpacingAroundComma
StringTemplate

All of Those are formatting rules related with the integration with ktlint. But thanks for the list!

Related to https://github.com/arturbosch/detekt/issues/1906.
All rules which report at KtFile have this problem. We should improve the signature generation for issues reported at the file level maybe with the line number.


DataSetAsyncCallback refactor

Consolidate error handling behaviour
Add internationalization to user messages
Add unit test

@manstis would you mind having a look on this :)

@cristianonicolai Hi, other than the above, looks OK to me.

@cristianonicolai Thanks
+1 to merge.

master: dde6aba4815bf90580445a25e6a903ea7b422582


constraint for addr % 32 == 0 for memory word address

Describe the feature you would like
after memory word read/write padding to 32 bytes,  need to constraint memory word addr is divide by 32.
after chat with @naure, Aurel will do it .
Additional context
No response

https://github.com/scroll-tech/zkevm-circuits/pull/634 merged into memory_opt close this issue now.


Please support KiwiBrowser(3rd Chrome support Extension) or Firefox Android Extension

Please support KiwiBrowser(3rd Chrome support Extension) or Firefox Android Extension

duplicated


(draft) Simpler spawner

This is just a demo on how we could simplify the spawner to keep all within the same file

I pushed some changes that fix a scenario with spawner + async function, I added tapexp which is the expected variable after being standardized.
However, I added after-end-assert.js but I noticed there is some differences between tapout and tapexp, so it doesn't pass:

The stdout of the inverted test doesn't return the first line like TAP version 13.
Now I added some colors so it's easier to read between all the random tap texts. I will remove chalk lib after reaching some stable point.
Previous brittle t.end() returned a Promise, and next brittle doesn't. I like that it doesn't but that is a breaking change as the rare t.end().then(...) is not valid anymore, although all tests done with await t.end() should mostly continue working.
Is it okay to have classic + inverted (regarding the same test) in a single file? Like the one I pushed: after-end-assert.js.
If you still prefer a single test per file, then it could be a test folder with test files + classic folder + inverted folder.

It would be cool to try merge this, so it doesn't become a too crazy PR and I can continue working on top with smaller changes, i.e. for now we could just deal with passing t to tester/spawner, later I could improve that. Improvements to standardizeTap function, adding more tests over multiple PRs, etc.


Remote system flag on user creation

Codecov Report

Merging #51 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #51      +/-   ##
==========================================
- Coverage   86.77%   86.75%   -0.02%
==========================================
  Files          41       41
  Lines         771      770       -1
  Branches       70       69       -1
==========================================
- Hits          669      668       -1
  Misses        102      102

Impacted Files
Coverage Δ

...ck/proxy/handler/radosgw/RadosGatewayHandler.scala
94.11% <100%> (-0.17%)
:arrow_down:

Continue to review full report at Codecov.

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


Added bitness for Python download

@kulkarnisonia16 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This is the first reference to an x64 that I've ever seen. Does this refer to the machine, func.exe, or the Python installation?

#sign-off


Translations?

Translations will be needed in the future, this is not the focus for now and I'm waiting to have a good idea of how much needs to be translated before asking for translations, but if you want to start translating already you can translate the extension description.

Ok


Crash when running in Unity on M2 MacBook

Hi,
I'm using DryWetMIDI to process inputs from MIDI devices like an electric keyboard in a Unity project. I'm using the Unity asset available to do this.
Things work on a Windows machine, however when I try running on a MacBook it crashes fairly quickly with the following stacktrace:
NullReferenceException: Object reference not set to an instance of an object
Melanchall.DryWetMidi.Multimedia.InputDevice.OnMessage_Mac (System.IntPtr pktlist, System.IntPtr readProcRefCon, System.IntPtr srcConnRefCon) (at <aa425ed4de0e44068f897ec3718f60da>:0)
(wrapper native-to-managed) Melanchall.DryWetMidi.Multimedia.InputDevice.OnMessage_Mac(intptr,intptr,intptr)
UnityEngine.<>c:<RegisterUECatcher>b__0_0(Object, UnhandledExceptionEventArgs) (at /Users/bokken/build/output/unity/unity/Runtime/Export/Scripting/UnhandledExceptionHandler.bindings.cs:46)

I was wondering if you have encountered this before and if there is a solution for this?
I'm getting the connected device using the following code:
List<InputDevice> inputDevices = InputDevice.GetAll().ToList();
if (inputDevices.Count > 0)
{
      InputDevice _inputDevice = inputDevices.First();
      _inputDevice.EventReceived += OnEventReceived;
      _inputDevice.StartEventsListening();
}

Then I'm handling the events in a method with the signature:
private void OnEventReceived(object sender, MidiEventReceivedEventArgs e)
{
}

If you need more information please let me know, I can perhaps create a minimal project and share it on GitHub.

Hi,
Unfortunately I have no Apple devices, so I won't be able to do tests on my side. So I really need your help with the issue.
Well, first of all, download please the ReceiveMidiData utility for macOS from here. Run it (in Terminal for example), select the same device and tell me please if the same error occurs.
Also what if you try to receive data from another MIDI device? Do you see the same error?
Thanks,
Max

Oh wait, I've just noticed a problem in your code:
if (inputDevices.Count > 0)
{
      InputDevice _inputDevice = inputDevices.First();

You create local variable here which will be collected by GC when the method exits. So in OnEventReceived the _inputDevice is probably deleted. You need to declare _inputDevice as a class field, not as a local variable. And I suppose the problem will gone. See an example here: https://melanchall.github.io/drywetmidi/articles/devices/Input-device.html.

Ah such a silly mistake - thanks for pointing that out!
Confirmed when I use a class field the issue doesn't occur. Odd it worked on Windows, maybe the GC behavior is different there.


Sometimes very wrong values for "Aktuelle Leistungsaufnahme Wärmepumpe"

´From time to time I have spikes in the graph and the reason is a very wrong value for "IDM_Wärmepumpe: Aktuelle Leistungsaufnahme Wärmepumpe". It jumps for one read (60sec on my integration) to the wrong value and jumps immediately afterwards back to the correct one. I saw it jumps to 20,64kW(!) Input Power for my heatpump and return immediately afterwards to 0,20 (which is the off state).
I think there a a locking issue, when reading a float value with two source values. This could be done of course wrong on the IDM_heatpump as well. So there might be nothing wrong with the integration. However it always corrupts the graphs and make the interesting part hard to see, since HA automatically adjusts the scaling to the biggest value, even there are wrong....
An easy fix could be to read the value again, if it changes too much from last reading (with this extrem example we could even allow an increase of 100% and any growth below 1kW. Or we do the reread based on plausability. A input power more than 10kW seems wrong and should be checked via re-read.

Hm, yes that is weird. Now that I look at it, it happens with my set up as well... I've even got values as high as 32 kW and it also happens when the heat pump is actually running.
Seems like an issue on the heat pump side. At least I have no idea how the integration would be at fault here. The raw 32-bit value is read via Modbus and then interpreted as a floating point number. The process is always the same so, if the error only occurs sometimes I don't think the integration is at fault...

An easy fix could be to read the value again, if it changes too much from last reading

What is "too much"? I have legit jumps from 0 to 3 kW (and maybe even more) when the heat pump starts. A percentage won't work (division by zero). Even limiting the growth in kW is hard, because the integration would have to remember previous values without giving them to Home Assistant to track the growth properly.
Best thing I could to is add a field to the integration configuration, where you can set the maximum input power of your heat pump model. Any value above that would be reported as "Unavailable". Then Home Assistant would just show a gap in the graph instead of the spike.

As long as your integration reads the 32bit value in one go, there is nothing wrong in your integration, the issue is in the heatpump, since they probably set it together from two 16bit values with might be not aligned.
The solution is easy. I propose following algorithm:
If a change more than 3kW from previous reading is detected it reads the value again from heatpump.
So it is the difference from previous reading not a percentage, that avoids any divison by 0 issue when the heatpump starts.
In case, as you told the change is actually real nothing harmful would happen. What is the result not trusting the value, correct it is just reading it again. So if the change is actually so high, it would read again the same value and the second time it is trusted.
The drawback for this algorithm is, it might read a value twice when the change is too big. If that happens only a few times a day, no real issue.

Just a quick question. Have checked the implementation, so you do a simple compare to max. power.
Is the reading again not an option, since it would take too long? That would prevent gaps, and would no need for configuration.
I am just curious, I am OK with this implementation as well.

In v0.7.0 the integration tries to read a second time, not sure if it will help, but it should cause any harm.


sdk 33 , permission BLUETOOTH_SCAN  on startScanning

Hello,
@nativescript-community/ble": "3.1.15" also trying with 3.0.33
@nativescript/core": "~8.2.0"
On Android, SDK 33 i have an issue on startScanning:
SecurityException: Need android permission BLUETOOTH_SCAN ,
but i'm already added this permission to manifest file

@eblomyac you need to ask the user at runtime (you can use @nativescript-community/perms).
I always advice to read android /iOS documentation for bluetooth.