Move package.json to top level removing the "explorer" directory

Need
Now that the Angular implementation has been deleted, we can move the React implementation to the top level. This gives a more standard repository structure and is in line with the expectations of release-please.
Check for dependencies on the /explorer directory structure

GitHub Actions
.gitlab build config

Completed.


short dump upon deserialization (insert)

I have an object whose name is case sensitive, so the method get_where_clause [0] generates a where clause which does not find the object entries and deserialization dies on duplicate insert error.
I can see that the only place where the object name is stored in case sensitive format is the serialized table contents in the corresponding object xml file.
I am currently pondering how to fix this problem.
0: https://github.com/abapGit/abapGit-Plugins/blob/master/src/zcl_abapgitp_object_by_sobj.clas.locals_imp.abap#L375

I thought object names (DB keys) are usually all upper case. I wrote a little program to check all keys for tables in OBJSL. There are 122 logical object types in NW 7.5 that allow lower-case keys (for the corresponding data element). It is more common and the generic serializer (here and in abapGit) should work with it properly.
I don't see any upper or lower case conversion in the plug-in. Do you have an example of the where-clause that doesn't work?


Nonlinear Regression and Logistic Regression Examples

Do you have any documentation or examples of how to use nonlinear regression and logistic regression?

The source files for the test modules show how to use the classes.  Look in the AIToolboxTests directory for the LogisticRegressionTests.swift and NonLinearRegressionTests.swift files.

Much appreciated...I was looking for documentation in the manual. Thanks for the help, the library is great.


Add external subtitle tracks to sample apps

This should solve issue #75.

I also cleaned up a few things in the samples (remove unneccessary null checks).


Feedback Wanted: Anyone find that sometimes the RM Mini doesn't trigger properly?

I'm finding that sometimes it won't trigger properly.  Usually if it hasn't been used for a while.  For example, The TV was on for a while then when I turned it off  (Switch multi, 1 for the tv one for the receiver) the tv didn't trigger but the receiver did.  It's like it missed the first hex as it didn't have time to connect it then it just carried on and triggered the second hex.
How do I find the logs for this?
Every device (homebridge server, apple tv 4 and rm mini) has a static internal IP address, the RM mini 3 firmware is up to date.
Here is my config:
{
"name":"TV",
"type":"switch-multi",
"interval":0.9,
"disableAutomaticOff":true,
"data":{
"on": ["TV ON hex code",
"RECEIVER ON hex code"
],
"off": ["TV OFF hex code",
"RECEIVER OFF hex code"
]

Anyone?

@lprhodes would be good if you could chime in.  I've finding that if the rm mini hasn't been used for a while when I go to trigger the above, it only turns on the the 2nd Hex Code (receiver) missing the first which is the TV.  I have to manually turn the TV.
Looking at the RM Mini led light it only lights up once (for the 2nd code) showing me that it definitely doesn't trigger the 1st hex code.
What would be causing this?  Should I put a dummy hex code in first to make it 3 so it "wakes it up" and gives it time to trigger the other 2??
Any help from anyone would be appreciated.
Also I find it does this with other devices I use to control with it (turning on and off the heat pump).  Sometimes it won't trigger first time.
Thanks!

In my case some times broadlink look like in standby and don't respond.
When I open the official app "e-control" they informe connecting and the homebridge back to work.
I don't know why. Maybe need send a request to start the broadlink.

That makes sense to me now.  Is there anyway to keep the rm mini 3 out of "standby"  ot keep it connected?

A workaround for this which seems to work most of the time now is doubling up the IR codes so use switch-repeat or switch-multi (inputing the IR code twice in your config) and this seems to "wake up" the RM Mini then fires the 2nd one off.  If it is "awake" having the code sent twice doesn't do hinder anything.


Update sbt-giter8 to 0.14.0

Updates org.foundweekends.giter8:sbt-giter8 from 0.13.1 to 0.14.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.foundweekends.giter8", artifactId = "sbt-giter8" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, commit-count:1

Incompatible dependencies with sbt-native-packager. We need to wait for a new release the packager (current is 1.9.9).

Superseded by #90.


Example DoH query is invalid

Existing documentation URL(s)

https://github.com/cloudflare/cloudflare-docs/blob/production/content/<IP_ADDRESS>/encryption/dns-over-https/make-api-requests/dns-json.md

Section that requires update
Example request:
What needs to change?
The example command curl -H 'accept: application/dns-json' 'https://cloudflare-dns.com/dns-query?name=example.com&type=AAAA' does not work. The server returns 'no 'dns' query parameter found

The example command works for me.
➜  ~ curl -H 'accept: application/dns-json' 'https://cloudflare-dns.com/dns-query?name=example.com&type=AAAA'
{"Status":0,"TC":false,"RD":true,"RA":true,"AD":true,"CD":false,"Question":[{"name":"example.com","type":28}],"Answer":[{"name":"example.com","type":28,"TTL":84769,"data":"2606:2800:220:1:248:1893:25c8:1946"}]}

➜  ~ curl -H 'accept: application/dns-json' 'https://cloudflare-dns.com/dns-query?name=example.com&type=AAAA' | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   210  100   210    0     0   5526      0 --:--:-- --:--:-- --:--:--  5526
{
  "Status": 0,
  "TC": false,
  "RD": true,
  "RA": true,
  "AD": true,
  "CD": false,
  "Question": [
    {
      "name": "example.com",
      "type": 28
    }
  ],
  "Answer": [
    {
      "name": "example.com",
      "type": 28,
      "TTL": 77242,
      "data": "2606:2800:220:1:248:1893:25c8:1946"
    }
  ]
}

Might be a platform/curl related bug - what OS & terminal are you running?

@ag-michael the example command seems correct to me, could you post your entire curl output? The 'dns' parameter is expected for the application/dns-message media type, not application/dns-json.

Any comment on this @ag-michael? I'll be closing this issue in a few days if not. Thanks! :)

Closing as there are no updates. Can reopen if needed. Thanks!

@marciocloudflare  apologies for the long delay. I was still having the problem but I found out the root cause, it was a middlebox intercepting DoH and attempting to resolve/mitm/proxy the request.
Thanks anyways.


Error with using TabBarController

If I added TabBarController to the ViewController with Pager
I will got error in PagerController.swift Line 270 "var frame: CGRect = self.tabsView!.frame"
fatal error: unexpectedly found nil while unwrapping an Optional value (lldb)
Is it not support using TabBar??

@nschucky can you help on this?

@wayne1203 i added a tab bar to the example project, can you check if this is helpful? #33

@nschucky Thanks and I will check it after work. 😁

I checked #33 it's not problem.
Thank you for your help.

@wayne1203 I'm having the same problem. Could you share your solution, please?

For what it's worth, it helped me to call self.defaultSetup() after self.setupPager().


Contradictory Instructions - Quality Assurance and Testing with Chai - Run Functional Tests using a Headless Browser

Hiya,
Reporting that there are contradictory instructions in the challenge "Quality Assurance and Testing with Chai - Run Functional Tests using a Headless Browser".
Link to challenge: https://learn.freecodecamp.org/information-security-and-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser/
Towards the top of the exercise, the instructions ask the user to test submitting for Cristoforo Colombo:
test('submit "surname" : "Colombo" - write your e2e test...', function(done) {
  // fill the form...
  // then submit it pressing 'submit' button.
  //
  // in the callback...
  // assert that status is OK 200
  // assert that the text inside the element 'span#name' is 'Cristoforo'
  // assert that the text inside the element 'span#surname' is 'Colombo'
  // assert that the element(s) 'span#dates' exist and their count is 1

However, in the area where the user/student is supposed to add their assertions, the "inline" instructions ask the user to test against Marco Polo:
// assert that the text inside the element 'span#name' is 'Marco'  <== BUG: This should say, 'Cristoforo'

// assert that the text inside the element 'span#surname' is 'Polo'  <== BUG: This should say, 'Colombo'

Let me know if there is anything else I can do.

I guess this PR adds to #35694 . A PR has been made on #35724, please make this comment there and request changes

Thanks thecodingaviator - will cross-post there as well.

Thanks thecodingaviator

Thanks thecodingaviator

Thanks thecodingaviator

Thanks thecodingaviator

Thanks thecodingaviator

Thanks thecodingaviator

Thanks thecodingaviator

guess this PR adds to #35694

After looking at this and #35694 it seemed the error referenced here was in the 'boilerplate-mochachai' repo and not the curriculum repo so submitted a PR on the 'boilerplate-mochachai' repo with a fix.

Closing as the issue has been resolved via https://github.com/freeCodeCamp/boilerplate-mochachai/pull/13

suite('Headless browser', function () {
    test('should have a working "site" property', function() {
      assert.isNotNull(browser.site);
    });
  });

  suite('"Famous Italian Explorers" form', function () {
    // #5
    test('submit "surname" : "Colombo" - write your e2e test...', function(done) {
      browser.fill("surname", "Colombo").then(
        browser.pressButton("submit", function() {
          browser.assert.success();
          browser.assert.text('span#name', 'Cristoforo');
          browser.assert.text('span#surname', 'Colombo');
          browser.assert.elements('span#dates', 1);
          done();
        })
      );
    });


Wrong limit of loop, in cpl_ini_vars.F

Hi,
in the file MITgcm/pkg/ocn_compon_interf/cpl_ini_vars.F, line 45
DO bi=myBxLo(myThid),myByLo(myThid)
should be
DO bi=myBxLo(myThid),myBxHi(myThid)
Regards,
EDIT: same in files
pkg/ocn_compon_interf/ocn_import_atmconfig.F, line 40
pkg/atm_compon_interf/cpl_ini_vars.F, line 45
pkg/atm_compon_interf/atm_import_ocnconfig.F, line 41

@Jiesseb Thanks for the report. Will submit a PR with this fixed.
Also found a couple of other places were we have the same problem

egrep -i 'bi.*myByLo' *.F
that I will fix too.

fixed by PR #271 which has just been merged

closed


Add error badge or/and error filter

Describe your suggested feature
An error badge/filter for when an update fails
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.11.2.
[X] I will fill out all of the requested information in this form.

https://github.com/mihonapp/mihon/pull/757

I have same opinion with Ansylich on this.

I have same opinion with Ansylich on this.

Okay, no problem. Would it be possible to know which entries have errors even if the automatic update didn't ended?

I have same opinion with Ansylich on this.

Okay, no problem. Would it be possible to know which entries have errors even if the automatic update didn't ended?

It should be possible to know the error status right after each entry update, no need to wait till the end


Add method to get functional representation of engine

Currently, the engines are all statefull classes.  This is useful for many things, but the final use case is an operation that looks much like a pure function:
func(url) = source
It is possible to add a method into the base engine class that will return a purely functional equivalent of the get_page_source method such that if you do (in pseudocode):
foo = Engine()
a = foo.get_page_source_as_func()
foo.set_state(bar='baz')
b = foo.get_page_source_as_func()

a != b

Further, the functions returned, a and b here, would take just one argument, url, and have all of the state of the parent object baked in.  This allows us to do some interesting things more performantly, like:
source_generator = (a(url) for url in urls)
or
from joblib import Parallel
Parallel(n_jobs=10, backend="threading")(delayed(a)(url) for url in urls)

:+1: This is a great idea. Definitely agree with the E:hard label though :smile:

Could we do it with a simple implementation like [this] (https://github.com/geezhawk/rasp/blob/interface/rasp/base.py#L19-L25)?

I think that might work, I think we would need a test similar to the pseudocode outlined above.  You're basically currying the function Engine.get_source(self, url) with the instance of self at that point in time.  If self gets modified after, does it also modify the previously returned function? If so, it will be a little bit more involved, using something like functools or toolz to actually curry the method with a copy of the instance that won't get modified.

Ah yeah you're right - any modifications to that instance of the class would also modify the function itself. I'll read up on functools and work on currying the function with a copy of all the instance variables. Good catch.

This idea works as-is under the assumption that at no point during the execution of the get_page_source method will the state of the engine will change.
To answer this

If self gets modified after, does it also modify the previously returned function?

It will, since it is still bound to that engine object, even though we no longer have to explicitly define it when we call the get_page_source method/fake function.
If we can't guarantee this, we should be able to accomplish what we want by implementing __deepcopy__ and performing that before the functional currying.  This won't guarantee a run-to-run lack of state changes within a thread, but each instance will now be threadsafe (assuming one copy per thread).

Assigned to @geezhawk


feat: sequence diagram background rect

Posting this a bit early to get some feedback. I still need to add unit tests and move some code around.
What does this pr do?
Adds a new language statement "rect" to sequence diagrams.
The rect statement applies a background color behind the contained statements.
Use case
Provides the ability to emphasize/group a selected part of the sequence diagram based on a desired condition.
Important Features

Nested backgrounds

Use Case example:
Currently, I am writing up documentation for a new feature that requires a change to one of our workflows. These workflows/diagrams are extremely complicated, and I would like to highlight endpoint calls are new.
Screenshots
sequenceDiagram
participant Alice
participant Bob
participant John as John
Second Line
rect rgb(200, 220, 100)
rect rgb(200, 255, 200)
Alice ->> Bob: Hello Bob, how are you?
Bob-->>John: How about you John?
end
Bob--x Alice: I am good thanks!
Bob-x John: I am good thanks!
Note right of John: Bob thinks a long
long time, so long
that the text does
not fit on a row.
Bob-->Alice: Checking with John...
end
alt either this
Alice->>John: Yes
else or this
Alice->>John: No
else or this will happen
Alice->John: Maybe
end
par this happens in parallel
Alice -->> Bob: Parallel message 1
and
Alice -->> John: Parallel message 2
end
loop awesome
A -> B: foo
end

Pull Request Test Coverage Report for Build 858

47 of 65 (72.31%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 53.145%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/diagrams/sequence/svgDraw.js
2
3
66.67%

src/diagrams/sequence/parser/sequenceDiagram.js
41
47
87.23%

src/diagrams/sequence/sequenceRenderer.js
0
11
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/diagrams/sequence/parser/sequenceDiagram.js
1
67.59%

Totals

Change from base Build 857:
-0.07%

Covered Lines:
2399

Relevant Lines:
4471

💛  - Coveralls


Stops after importing one item in category setup.

When setup to import to a category:

an item is imported but that is all.
importing stops after first import.

Same thing here.

I found the bug: https://meta.discourse.org/t/autobot-automatic-content-creator/71756/32

Thank you 👍. A PR related to this issue is now Merged https://github.com/vinkashq/discourse-autobot/pull/8


Blog Art : Deploying FlowFuse with Docker on the Ubuntu server

Related Issue
No response
Description
Considerations:

Blog tile

Content reference:

https://github.com/FlowFuse/website/pull/2300

Hi @sumitshinde-84 here it is


Cannot generate Reducers or effects with the Angular CLI (15.1.2)

Command
generate
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
15.1.1
Description
Cannot generate reducers or effects with the angular .
When using the command ng generate reducer (or ng g reducer) or ng generate @ngrx/schematics:reducer I get the following error:
An unhandled exception occurred: Cannot destructure property 'aliases' of 'collection.description.schematics[schematicName]' as it is undefined.
See "/private/var/folders/8r/0_dt1j351932ppgt33f60yfh0000gn/T/ng-IBPnCP/angular-errors.log" for further details.
Minimal Reproduction

ng new sample
ng add @ngrx/store@latest --no-minimal
ng config cli.defaultCollection @ngrx/schematics
ng g reducer
error

I can fix it with the following:

go to @angular/cli/src/commands/generate/cli.js
add if (collection.description.schematics[schematicName] !== undefined) in
async getSchematics() {
const seenNames = new Set();
for (const collectionName of await this.getCollectionNames()) {
const workflow = this.getOrCreateWorkflowForBuilder(collectionName);
const collection = workflow.engine.createCollection(collectionName);
for (const schematicName of collection.listSchematicNames(true /* includeHidden */)) {
// If a schematic with this same name is already registered skip.
if (!seenNames.has(schematicName)) {
seenNames.add(schematicName);
if (collection.description.schematics[schematicName] !== undefined){
const { aliases } = collection.description.schematics[schematicName];
const schematicAliases = aliases && new Set(aliases);
yield { schematicName, schematicAliases, collectionName };
}
}
}
}
}

Exception or Error
An unhandled exception occurred: Cannot destructure property 'aliases' of 'collection.description.schematics[schematicName]' as it is undefined.
See "/private/var/folders/8r/0_dt1j351932ppgt33f60yfh0000gn/T/ng-IBPnCP/angular-errors.log" for further details.

Your Environment
Angular CLI: 15.1.2
Node: 18.12.1
Package Manager: npm 9.2.0
OS: darwin arm64

Angular: 15.1.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1501.2
@angular-devkit/build-angular   15.1.2
@angular-devkit/core            15.1.2
@angular-devkit/schematics      15.1.2
@angular/cli                    15.1.2
@schematics/angular             15.1.2
rxjs                            7.8.0
typescript                      4.9.4

Anything else relevant?
I can fix it with the following:

go to @angular/cli/src/commands/generate/cli.js
add if (collection.description.schematics[schematicName] !== undefined) in
async getSchematics() {
const seenNames = new Set();
for (const collectionName of await this.getCollectionNames()) {
const workflow = this.getOrCreateWorkflowForBuilder(collectionName);
const collection = workflow.engine.createCollection(collectionName);
for (const schematicName of collection.listSchematicNames(true /* includeHidden */)) {
// If a schematic with this same name is already registered skip.
if (!seenNames.has(schematicName)) {
seenNames.add(schematicName);
if (collection.description.schematics[schematicName] !== undefined){
const { aliases } = collection.description.schematics[schematicName];
const schematicAliases = aliases && new Set(aliases);
yield { schematicName, schematicAliases, collectionName };
}
}
}
}
}

Duplicate of https://github.com/angular/angular-cli/issues/24586 and https://github.com/angular/angular-cli/issues/24600


MS Teams - Full Screen Button

Layout of the main screen with the Fullscreen button at the bottom of the screen. Users may not notice this straight away and be aware it is available, so may be more accessible if it were at the top of the screen or somewhere where it doesn't 'fall off' the screen and you have to scroll to see it.
Ticket 4047 - Tomasina Collier, Worcestershire NHS Commissioning and Primary Care
There was overwhelming feedback from the MS Teams testers that the Fullscreen button should be moved to a more prominent position near the top of the screen.

This has been done.


Support closer integration with Sublime Text

@lspitzner in https://github.com/ndmitchell/ghcid/issues/76#issuecomment-230036093 points at his Sublime setup at https://gist.github.com/lspitzner/5ae6638554f9e7457dccb462cb415987. That should be documented as is, or improved. Having Sublime integration would be great, as I use Sublime and ghcid most of the time.

Does anyone still use Sublime? I certainly drifted away from that and towards VS Code, so I'll let someone document/improve it as required, but it's unlikely to be me.


asap-data | OpenEye Toolkits version 2024.2.3 breaks on lilac

Not currently an issue, but may become so soon, which is that our GLIBC version on Lilac is not up to date enough to handle the newest OE versions.
Version 2023.1.1 still works just fine.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/__init__.py", line 142, in __getattr__
    obj = self._find_attr(name)
  File "/home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/__init__.py", line 132, in _find_attr
    return self._get_openeye_module(name)
  File "/home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/__init__.py", line 108, in _get_openeye_module
    spec.loader.exec_module(mod)
  File "/home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/oespruce.py", line 47, in <module>
    _oespruce = swig_import_helper()
  File "/home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/oespruce.py", line 44, in swig_import_helper
    _oespruce = libs.OEGetModule('_oespruce1533')
  File "/home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/libs/__init__.py", line 109, in OEGetModule
    mod = importlib.util.module_from_spec(spec)
ImportError: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/paynea/miniforge3/envs/asapdiscovery/lib/python3.10/site-packages/openeye/libs/python3-linux-x64-g++10.x/liboespruce-<IP_ADDRESS>.so)

Idk why they didn't statically link it, but this is a bit of a problem, AFAIK we can't really work around old GLIBC.

Without updating lilac system libs itself.

Yah an older version of openeye toolkits will be needed (we could ask them to statically link it, they might not like the larger binary).
I know you can install  sysroot_linux-64=2.28, that might work, but only if tha glibc gets picked up before the one that is on lilac

We can just add a pin, I don't think we will lose a lot.


Contributing Guide?

Hey! I absolutely love this library and want to help out. Not sure where the best place to start is. What are your standards for contributing, and what areas could I have the most impact in right now.

Hey! I absolutely love this library and want to help out. Not sure where the best place to start is. What are your standards for contributing, and what areas could I have the most impact in right now.

Contributions are welcome! There currently is no guide sadly, but a running theme is to just pick an issue from the backlog and work on it. Or if there is something you want changed/fixed open up a PR.
I'm pretty selective about large PR's or very opinionated PR's, but I've worked in the past with people to get stuff merged in. 👍
As far as future goals right now I think a big one is to:

Fix existing bugs
Re-write renderer to support:
a. Custom shaders
b. Feature locked rendering modes(Vertex pulling or regular mesh rendering).


Update docs in app template to see wireframe for VSCode

I updated the docs in App Template to open DevTools in VSCode, as guided by this stackoverflow link, because current documentation is outdated
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

可以拉取合併嗎?謝謝

可以拉取合併嗎?謝謝

I created another PR here, somehow the file changes here is 0


bug: singleton reported state return does not play nice with create-only

Describe the bug
For a workload object marked create-only, singleton reported state return does not work. That is because the singleton reported state return mechanism involves a label being applied to the workload object in the WDS and this label propagating to the workload object in the WEC (and later to the WorkStatus in the ITS). With create-only engaged, the label does not propagate to the workload object in the WEC if, for any reason, the object was already present, without the label, in the WEC.
Steps To Reproduce
Outlined above.
Expected Behavior
Singleton reported state return should work even for an object marked create-only.
Want to contribute?

[ ] I would like to work on this issue.

Additional Context
No response

@cwiklik
@waltforme


image_picker: ^0.6.2+1 image rotation issue

It appears that on devices android and ios when using the image_picker: ^0.6.2+1 portrait images are rotated by 90 degrees. If I use version 0.6.2 it works fine.

Hi @rlee1990
could you please provide your updated  flutter doctor -v?
Thank you

`[√] Flutter (Channel master, v1.12.12-pre.2, on Microsoft Windows [Version 10.0.18362.476], locale en-US)
• Flutter version 1.12.12-pre.2 at D:\nexttech\flutter_windows_v1.5.4-hotfix.2-stable\flutter
• Framework revision 033b897be5 (9 days ago), 2019-11-23 04:05:54 -0500
• Engine revision b6b54fd606
• Dart version 2.7.0
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\king3\AppData\Local\Android\sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 3.5)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 41.0.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] VS Code (version 1.40.1)
• VS Code at C:\Users\king3\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.6.0
[√] Connected device (3 available)
• SM N950U   • ce061716d1923703017e • android-arm64  • Android 9 (API 28)
• Chrome     • chrome               • web-javascript • Google Chrome 78.0.3904.108
• Web Server • web-server           • web-javascript • Flutter Tools
• No issues found!`

@iapicca Not sure what was changed in the version but going back to 0.6.2 works without an issue.

Even I experienced the same issue.
Future getImage(String source) async {
    if (source == "camera") {
      File image = await ImagePicker.pickImage(source: ImageSource.camera);
      if (image != null) {
        return image;
      }
    }
    return null;
  }

I suspect something wrong with bitmap scaling.

@iapicca
Hey there,
I managed to work around the rotation issue by changing the following method in ImageResizer.java
import android.media.ExifInterface;
import android.graphics.Matrix;

String resizeImageIfNeeded(
      String imagePath,
      @Nullable Double maxWidth,
      @Nullable Double maxHeight,
      @Nullable Integer imageQuality) {
//    return imagePath;
    boolean shouldScale =
        maxWidth != null || maxHeight != null || isImageQualityValid(imageQuality);
    String[] pathParts = imagePath.split("/");
    String imageName = pathParts[pathParts.length - 1];
    File file;
    Bitmap bmp = decodeFile(imagePath);
    if (bmp == null) {
      return null;
    }

    try {
      ExifInterface exif = new ExifInterface(imagePath);
      int orientation = exif.getAttributeInt(ExifInterface.TAG_ORIENTATION, 1);
      Log.d("EXIF", "Exif: " + orientation);
      Matrix matrix = new Matrix();
      if (orientation == 6) {
        matrix.postRotate(90);
      }
      else if (orientation == 3) {
        matrix.postRotate(180);
      }
      else if (orientation == 8) {
        matrix.postRotate(270);
      }
      bmp = Bitmap.createBitmap(bmp, 0, 0, bmp.getWidth(), bmp.getHeight(), matrix, true); // rotating bitmap
      file = createImageOnExternalDirectory(imageName, bmp, 100);
      copyExif(imagePath, file.getPath());

      if (!shouldScale) {
        file = createImageOnExternalDirectory(imageName, bmp, 100);
      } else {
        file = resizedImage(bmp, maxWidth, maxHeight, imageQuality, imageName);
      }
      copyExif(imagePath, file.getPath());
      return file.getPath();
    } catch (IOException e) {
      throw new RuntimeException(e);
    }
  }

Basically I checked the EXIF data of the image at imagePath and re-oriented the image if it was rotated. I am sure there is a better approach which fits within the plugin flow. But as a quick solution, this might help. Thanks :)

Although resizing the image takes time and is a lot of computation. I personally am avoiding resizing the image by returning the imagePath as it is

import android.media.ExifInterface;
import android.graphics.Matrix;

String resizeImageIfNeeded(
      String imagePath,
      @Nullable Double maxWidth,
      @Nullable Double maxHeight,
      @Nullable Integer imageQuality) {
    return imagePath;
}

Fixed in https://github.com/flutter/plugins/pull/2362, closing the issue


Fix dev vulnerabilities in testcafe and testcafe-hammerhead

[ ] Move from outdated webmake
[ ] Fix npm auditor dependencies

https://github.com/DevExpress/testcafe-hammerhead/commit/6532595694e6743bd491207ce9c046c939404250


Trying to parse invalid object

Hi I am encountering this error while loading the pdf document. I am using version 1.10.0. Have attached the file and error message

PDFDocument.load(docBuffer).then(() => {
        passwordProtected = false;
      }).catch(() => {
        passwordProtected = true;
      });

UserManual.pdf

Hello @rtrachelteng! Looks like the PDF you're trying to open is encrypted. Note the message of the error that is thrown:
Error: Input document to `PDFDocument.load` is encrypted.

pdf-lib does not support encrypted documents (see here). https://github.com/Hopding/pdf-lib/issues/233 and https://github.com/Hopding/pdf-lib/issues/243 are tracking support for this feature.


grammar corrector support in WWB

This PR introduces support for AutoForSeq2SeqLM models in WWB.
Previously, WWB only supported AutoForCasualLM, assuming that the generate method copies the prompt to the output.
But AutoForSeq2SeqLM generates output differently: there is no copy of the prompt, and it directly generates output.
The fix was checked on the example. It evaluates grammar correction with Seq2Seq model using WWB.

@AlexKoff88 @andreyanufr

@eaidova, please merge


[Feature Suggestion] Create Small Separators Between Actors

I think it could be cool if we could create small headbars between actors to allow for better visibility when having conversations between many separate parties in the same conversation.

That is a nice suggestion, I will be looking into adding something like this in the future. I don't know if it will be under the form of a separator (as that might make things look awkward when you will also have the option to re-order participants) which is why I am thinking of something more like a faction banner or symbol near the portrait itself. But who knows, I will try some things out and see what works and looks best.

So with the v5 release of the module, I have introduced the option of configuring and attaching a faction to each participant. This feature, combined with the ability to re-order participants should help to create a visible distinction between multiple parties present in the same conversation.
I have also played around with the idea of adding separators, I think I have found an option that might work (I need to test it further), but for now I think the addition of factions should help you achieve what you have suggested (until that separator is also implemented).
If you have any questions or additional requests/suggestions, feel free to contact me and I will answer as best as I can.


Relevant for the following modules: Odiglet, Autoscaler, Scheduler, Instrumentor, Frontend
I had a good experience using: https://github.com/golangci/golangci-lint

Opentelemetry repos can be used as a reference for how it can be achieved:
https://github.com/open-telemetry/opentelemetry-go/blob/c7f53cc973726dd51222f670acc539e563e6a631/Makefile#L192

@edeNFed @blumamir I want to work on this issue.


'nonempty' mount option does not work

Summary
Hello
I'm trying to use rexray s3fs driver for my docker swarm service but facing some troubles using 'nonempty' option. I've googled many threads using this option the same way, but can't make this work for me. Please help me to understand how to use it properly.
Thanks in advance.
Bug Reports
Version
$ lsb_release -d
Description:    Ubuntu 18.04 LTS

$ rexray version
REX-Ray
-------
Binary: /usr/bin/rexray
Flavor: client+agent+controller
SemVer: 0.11.4
OsArch: Linux-x86_64
Commit: e7414eaa971b27977d2283f2882825393493179d
Formed: Tue, 15 Jan 2019 19:03:57 MSK

Expected Behavior
rexray mounts s3fs non-empty bucket
Actual Behavior
Bucket is not empty. if you are sure this is safe, can use the 'nonempty' mount option.
Steps To Reproduce

Start minio S3 server:

docker run -d --restart=always -p 9000:9000 -e "MINIO_ACCESS_KEY=myaccesskey" -e "MINIO_SECRET_KEY=mysecretkey" -v /var/data/s3/data:/data -v /var/data/s3/config:/root/.minio minio/minio:RELEASE.2020-06-03T22-13-49Z server /data

Install s3fs (1.82-1), rexray (0.11.4-1)
Create docker stack on swarm node with service using s3fs volume
When container started with successfully created new bucket (container must write something in new bucket), force remove container
Watch another container instance not starting, because bucket is not empty

Configuration Files
/etc/rexray/config.yml:
rexray:
  logLevel: debug
libstorage:
  logging:
    level:         debug
    httpRequests:  true
    httpResponses: true
    stdout: '/var/log/rexray/rexray.log'
  service: s3fs
  server:
    services:
      s3fs:
        driver: s3fs
        s3fs:
          endpoint: http://minio-server:9000
          accessKey: myaccesskey
          secretKey: mysecretkey
          options:
            - nonempty
            - uri=http://minio-server:9000
            - use_path_request_style

/etc/docker/stack.yml:
version: '3.7'
volumes:
  portainer.bucket:
    name: portainer.bucket
    driver: rexray
services:
  portainer:
    image: portainer/portainer:1.23.2
    command: "-H tcp://tasks.agent:9001 --tlsskipverify"
    volumes:
    - portainer.bucket:/data

Logs
Service Log
rexray-service.log and
Syslog
Jun  5 20:54:01 master04 s3fs[3386889]: s3fs: MOUNTPOINT directory /var/lib/rexray/volumes/portainer.bucket is not empty. if you are sure this is safe, can use the 'nonempty' mount option.
Jun  5 20:54:01 master04 rexray[3378221]: time="2020-06-05T20:54:01+03:00" level=error msg="docker-legacy: Mount: portainer.bucket: failed: error mounting s3fs bucket" host="unix:///var/run/rexray/378211813.sock" integrationDriver=linux osDriver=linux service=s3fs storageDriver=libstorage time=1591379641990
Jun  5 20:54:02 master04 dockerd[1315]: time="2020-06-05T20:54:02.444687026+03:00" level=error msg="fatal task error" error="starting container failed: error while mounting volume '': VolumeDriver.Mount: docker-legacy: Mount: portainer.bucket: failed: error mounting s3fs bucket" module=node/agent/taskmanager node.id=nj611i50738hph6q0ak3wz4kv service.id=ttg2k8dejru02u1gzuxdmwmhl task.id=loznnevmfwpqhwx9bmpx0yrq

I have found through a lot of testing that the "options" field only seems to work if you put it at the root of your config file like this:
rexray:
  logLevel: debug
libstorage:
  logging:
    level:         debug
    httpRequests:  true
    httpResponses: true
    stdout: '/var/log/rexray/rexray.log'
  server:
    services:
      s3fs:
        driver: s3fs
s3fs:
  accessKey: ****
  secretKey: ****
  endpoint: http://****
  options:
  - url=http://****
  - use_path_request_style
  - allow_other
  - nonempty

Also you either need:
service: s3fs
or
  server:
    services:
      s3fs:
        driver: s3fs

you only need to use the second form if you are including multiple services

Yep, that works! Thank you so much for the help!
Another thing I forgot to mention is /etc/passwd-s3fs:
<Your_accessKey>:<Your_secretKey>

And it seems like s3fs doesn't have uri option, so here's my config that works, in case someone needs it:
/etc/rexray/config.yml
libstorage:
  service: s3fs

s3fs:
  endpoint: http://minio-server:9000
  accessKey: myaccesskey
  secretKey: mysecretkey
  options: 'use_path_request_style,nonempty'


[669] Update the buildx action

What
It was pinned to 0.9.1 for compatibility with GOV.UK PaaS. Now that we run on AKS, this limitations does not apply and we can use the default version.

 GIT-API: Decommission paas environments and code


Add Annual Security Reports

[[Insert URL to the list here]]
(https://github.com/jacobdjwilson/awesome-annual-security-reports)
[Explain what this list is about and why it should be included here]
A curated list of annual cyber security reports.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

[X] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
[X] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
[X] You have to review at least 2 other open pull requests.
#2503,#2498
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
[X] You have read and understood the instructions for creating a list.
[X] This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

[X] Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

[X] Your entry should be added at the bottom of the appropriate category.
Security
This PR should add the entry to the readme.md
[X] The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

[X] The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

[X] Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
[X] Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Can someone help me with this?
[X] The default branch should be named main, not master.
[X] Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

[X] It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
[X] The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

[X] The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

[X] Non-generated Markdown file in a GitHub repo.
[X] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[X] Not a duplicate. Please search for existing submissions.
[X] Only has awesome items. Awesome lists are curations of the best, not everything.
[X] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
How long does the group suggest aging out reports?
[X] Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

[X] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[X] Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

[X] Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

[X] Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

[X] Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

[X] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
[X] Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[X] Does not use hard-wrapping.
[X] Does not include a CI (e.g. GitHub Actions) badge.You can still use a CI for linting, but the badge has no value in the readme.
[X] Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.
I put other non-awesome inspirational people, does that count?

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

To my knowledge the only requirement not fulfilled is linting. Is there someone that can help lint this? I don't see a clear set of directions here. Also this awesome list has existed for well over a year.

Thank you @roj1512 !! I think i've fixed the output of the lint run and your feedback on the contribution and title

@jacobdjwilson The title of this pull request is still not in the suggested format.

Gotcha, I've modified the PR title as well.
The one thing I can't seem to fix in awesome-lint is remark-lint:double-link
Some items in the list will link to the same vendor and may cause double links in this case.

@jacobdjwilson Above the line that is unreasonably failing, you can put this comment:
<!-- lint ignore double-link -->

Okay perfect, I put the ignore rule on line 1. We should be good to go now! I appreciate all the help!

The description starts with an uppercase character and ends with a period.

For each item in the Analysis and Survey section, it would be useful with a one-sentence summary for each item. You can use ChatGPT for this.
I also think the report name column should be first.

@sindresorhus Is there any way to get this to pass the final failing lint check?

This review feedback is not addressed. You are also not following all the guidelines.

This review feedback is not addressed. You are also not following all the guidelines.

It's been over 6 months since this PR was opened and unfortunately I am unable to get the context to pass the linting checks for guidelines.
Respectfully, the feedback in your last post was not helpful in moving this PR forward. I disagree that the report title should be listed in the first column, if you review the dataset you'll see that a vast majority of reports have the name "Annual Threat Report" and the Provider column not only is more unique, but also allows users to quickly find multiple reports by relevant suppliers to their security program. Additionally, the use of generic ChatGPT sentence summaries degrades the usefulness of the list in my opinion. The most useful context in that sentence summary is already contained within the Data Type column.
I've put alot of thought into the structure and usability of this particular list, as I see that you have put alot of thought into the Awesome project as a whole. It would be great to get this PR merged.

@sindresorhus Okay I've reformatted all the data in list format and addressed your comments. Could you please review, thanks!

<EMAIL_ADDRESS>

@sindresorhus Could you please review the latest main branch of awesome-annual-security-reports? Thanks

@rojvv I have changed the format of the main branch and moved the old format to a legacy branch. You were super helpful in previous comments helping with lint checks and I appreciate that, could you help with re-running the checks? Thank you!

I helped because I had a PR of mine open back then, to fulfill its requirements. It is closed now and for the same reason I don't have a reason to help anymore. Sorry about that.

There are several linting issues noted here. You can also run the lint command locally to check.
For example, the error List item description must start with valid casing means that your description should start with an uppercase letter, which isn't the case in your README for those specific lines.

@sindresorhus Can this PR be merged please? Thanks

Mandiant - MTrends Special Report (2024) - The MTrends Special Report offers insights into advanced persistent threats, emerging attack techniques, and strategies for improving organizational cyber defense.

The description should not start with the title. Applies in multiple places.

Mandiant - MTrends Special Report (2024) - The MTrends Special Report offers insights into advanced persistent threats, emerging attack techniques, and strategies for improving organizational cyber defense.

The description should not start with the title. Applies in multiple places.

I have removed all mention of report titles in the description and any references to "the report" or other circular references.

Tweet: https://x.com/awesome__re/status/1859890268746756201


Add trove classifiers to setup.py

This provides some metadata about the package for tools such as pyup.io
https://pypi.python.org/pypi?%3Aaction=list_classifiers

@kavdev Can you please create PR?

Sure!


BUG: scipy.interplate.griddata states wrong shape of xi input in documentation

Describe your issue.
For scipy.interpolate.griddata the documentation states that the shape requirements of the input are:

points: (n, D)
values: (n, )
xi: (m, D)

However xi needs to be in the same shape as points if passed in as an array
This is referenced in: https://github.com/scipy/scipy/blob/acac27527df9c8723647512361c581f714fb473a/scipy/interpolate/_ndgriddata.py#L129
Reproducing Code Example
N.A.

Error message
N.A.

SciPy/NumPy/Python version information
1.9.0 1.23.2 sys.version_info(major=3, minor=10, micro=4, releaselevel='final', serial=0)

Can you provide some example code showing this, I am not sure I follow your argument at this point.

@aoerder, it is not required that xi and points have the same length.  The arrays points and values are the known function values of the function.  xi is the set of points at which new function values are to be interpolated.
In the following example, there are 5 known values at 5 points (n is 5), and we interpolate the values at the 3 locations given in xi (m is 3):
In [34]: from scipy.interpolate import griddata

In [35]: points = np.array([[0, 0], [1, 0], [1.25, 1], [0, 2], [2, 2]])

In [36]: values = np.array([5, 2.5, 2, 4, 7.5])

In [37]: xi = np.array([[0.5, 0.5], [0.5, 1.5], [1, 1.5]])

In [38]: griddata(points, values, xi)
Out[38]: array([3.75   , 3.25   , 3.65625])

I'm closing the issue, but if you have an example that demonstrates a problem, please include it here.


fixing unity server clearing and clipping plane

Oops! 😞
There was a bug in the unity server sample where-in the cameras weren't configured as recommended by the hololens team! Now they follow the advice as documented. 🚀

i want to change the lighting to be brighter here. labeling as invaliduntil i make that change tomorrow am

LGTM! Merging


Update Rust Implementation

I wasn't getting it to compile, due to some errors. It is likely caused by the Cargo.toml file not specifying a specific version of euclid, so it is giving errors with the updated version. This should compile now. With gdscript I was able to get 11,713, and in rust I was able to get 24,291if that tells you the performance delta.

Closing in favor of #21. Sorry for the delay. I haven't been giving this repo (and its contributors) the attention they deserve.


'my-popover' is not a known element

I have imported the NgWormholeModule to providers in app.module.ts,but failed to compile

<my-popover> was just an example in the README, this could be any element like <div>. This module does not define an actual my-popover component.

👍


Feature Request - Validate - parameter to indicate temp folder for WhatIf output

As a follow-up to #678 and the related fix in #679 to generalize temp pathing - I recently had to support a scenario that involved running the AzOps pipelines on a self-hosted Windows VM.
I have a working setup but thought I'd share some observations anyway:

In case of multiple pipeline agents on the same machine ensure you lock the Validate (and Push) pipeline to one of the agents (e.g. using demands with Azure Pipelines)
Upon pipeline startup - remove any previous OUTPUT.md / OUTPUT.json files left from past runs
Update the pipeline code as follows:

# Expected path to WhatIf output to match the AzOps internals
$whatIfOutputPath = Join-Path -Path ([System.IO.Path]::GetTempPath()) -ChildPath "OUTPUT.md"

Preferably, I would like to indicate something like Agent.TempDirectory (if using Azure Pipelines) as an argument to the Invoke-AzOpsPush call.
I realise this is an edge case as opposed to running the pipeline on a short-lived temporary agent. Alternatively, this might go into the wiki if at all.

Thank you for raising this. I do agree it is an edge case when not using short-lived agents/runners.
Perhaps a note or two in this https://github.com/azure/azops/wiki/self-hosted would be enough as a starting point? What do you think?


Feat/icon channel connection method impl

3 files in this PR, will be pushed first to IBC Integrations repo ,and will be imported in this repo and then it'll be merged.


Update to use FormsAppCompatActivity

@nosami Why was FormsAppCompatActivity helpful here? Just for my education, thanks

@dsyme: It's needed to make the OSX and Android apps look as similar as possible.


Support Ternary Operator

For example: foo ? bar : baz

I thought you wouldn't adopt ternary operators in Goby 😲

Yep I didn’t want to support this, but this is kind of a basic component to programming language I think

Is this something people have complained about not having?

Not yet, just I think it would be. But it might also because we don't really have much users for now.

Just a thought, do you want to do something like in Python style (although Goby is referenced to Ruby style syntax):
hello = 'world' if created? else 'nothing'

But this style is kind of like inline conditional which is addressed in #580

@Maxwell-Alexius I prefer using Ruby style because python style might confuse users

Would you guys let me try to attack this in my free time? I love Ruby and Go, and have tried working with compilers/interpreters before, so I feel like it wouldn't be such an idea to attempt something like this.

@spavikevik sure, feel free to work on it 😄


New package: Fortran90Namelists v0.1.0

Registering package: Fortran90Namelists
Repository: https://github.com/anchal-physics/Fortran90Namelists.jl
Created by: @anchal-physics
Version: v0.1.0
Commit: cd0bbfd96a4bab8230259ee310766838f05eb701
Reviewed by: @anchal-physics
Reference: https://github.com/anchal-physics/Fortran90Namelists.jl/commit/cd0bbfd96a4bab8230259ee310766838f05eb701#commitcomment-147598934
Description: A pure Julia implementation of Python f90nml package.

[noblock] Requesting override of package name similarity. This package is indeed supposed to provide same functionality as PyFortran90Namelists but without using the python modules in the backend. This is a pure julia implementation and thus it makes sense for it to have same name without the Py suffix.

Hi @anchal-physics, I really appreciate the work you've done in forking and modifying Fortran90Namelists.jl. It's great to see that others find the package useful and are contributing to the ecosystem.
I wanted to ask if you'd consider giving your fork a different name. The main reason is that I may implement a new version of the parser with some structural changes in the future, and I’d like to keep the original name available for that. Additionally, since your package is intended to be minimally maintained, a new name would help distinguish between our versions and avoid any potential confusion for users.
One suggestion could be FortranNamelistsParser.jl, which reflects the purpose of the package while differentiating it from the original. Let me know your thoughts, and thanks again for your contributions!

@singularitti Thanks for your comment and suggestion. I agree with you and will wait for your improved Fortran90Namelists.jl package. For now, I've renamed this package to FortranNamelistParser.jl and it has been accepted as new package in Julia Registry on this pull request: https://github.com/JuliaRegistries/General/pull/116786 . This merge request can be ignored and closed now without merging. Thanks.

That's great! Thank you! @anchal-physics


Latest version of automatic1111 wont start with this extension installed.

Reproduction.

Install this extension using automatic1111 built in extension installer.
Apply and reload ui.
Watch it crash.
Try to start web-ui-user.py and it won't start.

Expectation.
It shouldn't brick your install of automatic1111. Deleting this extension from the extensions folder solves the problem.

Still getting this issue. I installed all the packages mentioned in install.py but automatic1111 still doesn't start.


[GHSA-rxhx-9fj6-6h2m] enum_map macro can cause UB when Enum trait is incorrectly implemented

Updates

Affected products
Description
References
Source code location

Hi @xfix,
I am merging the fix commits but want to have more of a conversation about CVSS before merging that particular change. I discussed the CVSS you provided with my colleagues alongside the RUSTSEC advisory, and we can see where your assessment of critical and the advisory's assessment of high both come from. There are two factors which affect whether this vulnerability is high or critical:

Attack complexity. Per the RUSTSEC advisory, "This problem can only occur with a manual implementation of the Enum trait, it will never occur for enums that use #[derive(Enum)]." If this manual manipulation is not a standard part of the software configuration, this indicates a high-complexity attack.
Changed vs. unchanged scope. The RUSTSEC advisory does not indicate the vulnerability affecting systems outside the security scope of the system running enum_map, which would lead me to choose unchanged.

The advisory curators understand that, as the maintainer, you have insight into the code that those outside the project do not have. We appreciate your input and want to offer our perspective as people who work with CVSS assessments daily. If you have information that you believe would help improve our understanding of the situation, we would be interested in learning about it.


Any way to apply logic to show the confidence in search results?

Great work on this project, works beautifully most of the time. Quick question, not an issue, more of an enhancement.
Do you think it would be possible to add a feature that shows the confidence for each method? Method 2 never works for me, but 1 and 3 works great. So typically I'm seeing that they give the same responses, but especially in later questions they give different responses. And if I had more than 3 seconds to read and interpret the scores I could see this bot being 95% accurate.
For example, I don't know if this makes sense, you could calculate confidence like this:
Method 1:
Answer 1 score: 35, answer 2 score: 0, answer 3 score: 40
Let's say question does not include 'NOT'. so method 1 would return answer 3
Method 3:
Answer 1 score: 3, answer 2 score: 0, answer 3 score: 1
So this would return answer 1.
Now, confidence:
Take the top 2 answers, calculate the percentage between them
Hi: 40 Lo: 35 so 40-35/40=13% difference, so give it a confidence score of 13%
Hi: 3 Lo: 1 so 3-1/3=66% difference, so give it a confidence score of 66%
If the second largest score is a 0, it would return a score of 100%
I know there is a better way to calculate this, but I would go with method 3 as my answer, and I feel it gives me a better chance than the 50% chance I have right now to pick either one or the other.

Here's a real life example:
Q: What is the inner most planet in our solar system
A: Jupiter, B: Mercury, C: Saturn
M1: A:13, B:322, C:11
Best answer: B: Mercury (322-13)/322=96% Confidence
M3: A:284, B:239, C: 161
Best answer A: Jupiter (284-239)/284=16% Confidence
Two different answers but I would definitely pick the 96% confidence answer, which happens to actually be the correct answer.

pl help me i am unable to install it


[Schema] Separate input types for query fields and mutation fields

Currently only a single input type is generated for each model and this is used for queries and mutations. This assumes all fields are non-required to be able to cater for both cases.
We need to generate a separate <ModelName>Fields input type specifically for queries, and update the <ModelName>Input input type to map the required constraint from the model.

We should have input types that actual match the require fields etc. to enable better validation
We should have 2 input types:
Used for filtering (without required fields)
Used for mutations (with required fields same as in original type)
Closing https://github.com/aerogear/graphback/issues/844 as duplicate

type Note {
  id: ID!
  title: String
  description: String!
}

Two input types are generated:
type NoteData {
  id: ID # not required as this can be auto-generated
  title: String
  description: String!
}

type NoteFilter {
  id: ID
  title: String
  description: String
}

NoteData respects the required level of the fields - except for ID. This is because ID can be an auto-generated field and the input type is used for both update and create mutations. Updates require the ID for updating an item by its ID. Creates do not require IDs as they can be auto-generated by the database.
One solution for this is to have a separate input type for create and update mutations, but when we action https://github.com/aerogear/graphback/issues/1031 the CRUD Spec will change again anyway, so that update mutations would accept two types:
updateNote(filter: NoteFilter!, data: NoteData!)
At this point ID can be commpletely removed from NoteData as it would no longer be used.

Outdated by https://github.com/aerogear/graphback/issues/1031


Refactor login component

DocumentTitle should be always set only on top most (pages) components. In case of login form, it just seems to be defined twice.

THAT WAS MY ISSUE :-1:


Python Program based on DSA

Can I add some program based on DSA? Will you assign the issue to me or shall I create an issue and create a pr?

@varun6996  Can I do some program on DSA and create a PR?

Hie @varun6996, please review the PR and let me know if there are any changes required from my end.


Update Issue - 55217499

default description
URL tested: http://ci.bsstag.com/welcome
Open URL on Browserstack

Property
Value

Browser
Chrome 75.0

Operating System
Windows 10

Resolution
1024x612

Screenshot Attached
Screenshot URL

Click here to reproduce the issue on Browserstack

Updated Screenshot Attached


ComboBox.SelectedItem lost on control generated in a template

Copy this XAML into any window and run:
<StackPanel Classes="Hello World">
	<StackPanel.Resources>
		<ControlTemplate x:Key="MyTemplate">
			<ComboBox SelectedItem="World" ItemsSource="{Binding $parent[StackPanel].Classes}"/>
		</ControlTemplate>
	</StackPanel.Resources>
	<ComboBox SelectedItem="World" ItemsSource="{Binding $parent[StackPanel].Classes}"/>
	<TemplatedControl Template="{StaticResource MyTemplate}"/>
</StackPanel>

You will see something like this:

The ComboBox which was created as a direct child has kept its SelectedItem, as expected. But the one generated from the template, despite having the exact same XAML declaration, has lost its selection.
ComboBox.ItemsSource is correct for both items. The bug is reproducible with any ItemsSource; I only used Classes to keep the repro case as small as possible.
Expected behavior
Both ComboBoxes should display "World" as their selected item.
Environment

OS: Windows
Avalonia-Version: 11.0.9

Possibly the same issue: when the templated ComboBox disconnects from the logical tree, it loses its ItemsSource value and resets any selected value to null.

I had a deeper look at this issue and it looks like this is not easy to solve by Avalonia itself.
The moment the template is built the initial selected value is properly applied but at that moment the ItemsSource is not bound yet because there is no parent. So the selection gets reset.
I suggest moving the selected value state to some external state so you will be binding SelectedValue and ItemsSource.

We've dodged the issue by moving the affected control out of a template. It's duplicated in a few locations now, but works correctly.

Can we close this issue?

I don't think so. It's still a nasty bug that can strike at any time.

Another possible solution may be to not reset SelectedItem on a change to ItemsSource, even if the SelectedItem is not in the ItemsSource. The idea is that maintaining valid state should be the responsibility of the ViewModel, not the View. The View should not be making changes unless these changes are due to user interaction. The current behavior is that loading and unloading of the View can result in changes.
But such a change to behavior is probably a breaking change.

This bug just bit me too.
The suggestion by Gillibald to bind the SelectedIndex of the ComboBox works. It does not look too dirty but feels a bit like fixing something which should just work, so i'd agree that a fix would be welcome.

@DimNightStar can you translate also to English?


Remove RHACM references

Per request of @dhaiducek to check the PR guards
/cc @dhaiducek

/approve

/approve cancel

/ok-to-test

/ok-to-test cancel

Closing because GitHub seems to have lost a commit or something


⚠ Bofrost.es has degraded performance

In 19ba5eb, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1727 ms

Resolved: Bofrost.es performance has improved in ef4ff2c after 8 minutes.


#18 and #19 Fix to include filters for designs and extention to create AEM 6.2 Editable Templates folders structure

Fixed, please merge.

I reverted the last 2 commits in the readme due to closing the issue #21 .
Please merge.

coming to the party a little late... WDYT of creating a separate content package ui.content for artifacts like editable templates under /conf but also maybe a base /content structure. Filters would default to merge. Would be more inline with the We.Retail reference implementation...

@godanny86 I think that is an OK suggestion, except that /conf/<appname>/settings/wcm/template-types needs to be in ui.apps, not ui.content since template-types is under developer control.

good point @justinedelson that template-types would be under developer control. What about a filter.xml that defaults to:
<filter root='/conf/<appname>/settings/wcm/template-types' />
<filter root='/conf/<appname>/settings/wcm/templates' mode='merge' />
<filter root='/conf/<appname>/settings/wcm/policies' mode='merge' />
I feel like there will be other filters under /conf like metadata-schemas, customized search facets that fall into a 'gray' area that can be updated via the UI by power users but also many projects may wish to manage under source control. Maybe ui.content isn't the correct name, could do ui.conf ?

@godanny86 I think just the merge on the top-level will suffice. I think @mtstv already said he was going to add this.

cool, that works

Fixed issues form review.

One thing more, I think the file is unnecessary and can be deleted, because it will be not used by content-package-maven-plugin during the package generation.
/example-project.ui.apps/src/main/content/META-INF/vault/definition/.content.xml

@justinedelson so can @mtstv updates be merged?

yeah, I'll try to get to that this week

sweet!


Build fails in Cordova

Including this plugin with this in my config.xml:
<plugin name="cordova-plugin-volume-control" version="0.1.8" />
Getting this error when building with cordova:
Error: cmd: Command failed with exit code 1 Error output:
C:\Projects\gogyup-literacy-app\litapp-source\builds\build-cordova-litapp2\platforms\android\src\com\lorentech\plugins\vo
lumeControl\VolumeControl.java:42: error: ';' expected
                                int volumeToSet = (int) Math.round(args.getDouble(0) * 100.0f)
                                                                                ^
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

I suspect the latest github version is not uploaded to npm, as the semi-colon looks ok in latest github source.  But the VolumeControl.java in my local plugins/cordova-plugin-volume-control/src/android folder is missing the semi-colon, like the error message indicates.

You are right. I have published it now. Thanks for the warning.


feat: gradle e2e at repo root

Adds gradle e2e tests where the project root is also the repository root, to confirm the new fixes in
https://github.com/slsa-framework/slsa-github-generator/pull/3250
The same gradle files at e2e/gradle/workflow_dispatch have been copied tot he repository root.
Testing
I could not get this new Action to work on my own fork. It , but I believe we would followup with a fix to the test or revert this PR if it fails.
Verifying artifact build/libs/example-package-0.1.87.jar: FAILED: invalid ref: "refs/heads/main": unexpected ref type: "heads"
FAILED: SLSA verification failed: invalid ref: "refs/heads/main": unexpected ref type: "heads"
✖ 1 == 0 :: not main default parameters (annotated_tags)

@laurentsimon @ianlewis

seems to be working https://github.com/slsa-framework/example-package/actions/runs/7961521799. thanks!


Use and expose the ignore option in mapWorkspaces()

Needed to ignore duplicate workspaces that can happen at build time and which pnpm allows but which systems like npm doesn't: https://github.com/webdriverio/webdriverio/issues/11868#issuecomment-2038272842

Fixed in https://github.com/voxpelli/read-workspaces/commit/1a51e809a24214b0d6e71a6a0fb1fa489e126dea


pythonPackages.zeep: Enable test suite for Python 3

Motivation for this change
Using pytest with Python 3 is possible now.
See also #57469.
Things done

Enabled tests for the zeep package.

Added the airoresponses package which was a dependency of the test suite.

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

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 nix-review --run "nix-review wip"

[ ] 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)

[ ] Assured whether relevant documentation is up to date

[x] Fits CONTRIBUTING.md.

I have better things to do than waste my time talking to you @dotlambda.

@rvl I'm sorry if it felt like that. Did

You're not the only being on this planet.

offend you? If so, I'm sorry. I just meant to express "other people might be interested in Python 2 support" in a non-standard non-boring way. I'm genuinely interested to learn what you think I did wrong.


MPU+QMC Details, BMI Fix, and Defines.h Generator Update

Added MPU6050+QMC5883L tracker schematic, as well as relevant instructions for flashing the experimental firmware it requires.
The BMI160 schematic previously had an extraneous detail which has been corrected.
The defines.h generator has been updated to allow selecting the BMI160 and ICM20948 as options. The note that the MPU9250 is experimental has been removed and replaced with a notice about requiring a stable magnetic environment. Likewise, I attempted to make a similar warning for the ICM20948 which notes that to run it in 9DoF mode requires changing a line in debug.h, with another warning about requiring a stable magnetic environment. I'm slightly unsure of whether the ICM20948 warning is functional, but I think it should work.

Just double checking, you have done a local check on the image / code changes and everything looks peachy?


Barcodes visible in app bar

The barcode should be visible for shorter names, right?

Yes that's correct, we should open an issue for this one (really easy to fix
Originally posted by @g123k in https://github.com/openfoodfacts/smooth-app/pull/3805#issuecomment-1487592128

A small improvement would be to prevent the barcode bottom line to be shrunk (the kind of small detail I like 😅)

Actually it's OK for the initial bug. Because at the top of the screen, the barcode isn't visible, hence the fact that it can be on 2 lines


Bump postgres to fix zenith_test_utils linkage on macOS.

Perhaps we should merge 'contrib/zenith' and 'contrib/zenith_test_utils' into a single module. We can still provide a separate .sql file to create the debugging functions, so that they're not created out of the box.

Perhaps we should merge 'contrib/zenith' and 'contrib/zenith_test_utils' into a single module

+1
I've already merged corresponding PR into postgres main, so probably makes sense to merge this in it's current form and deal with function move in a separate PR -- will do as well.


Add GetConfig and GetState

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 16 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 87.382%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ygnmi/ygnmi.go
0
16
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
1572

Relevant Lines:
1799

💛  - Coveralls


Merge development into master branch

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Coverage decreased (-3.8%) to 57.42% when pulling c2752c8dec61585d1457537055d5170efbfed3cd on development into 71aa2568c1a9c104054f39c77382e0bddc84d2af on master.

Coverage decreased (-3.8%) to 57.42% when pulling c2752c8dec61585d1457537055d5170efbfed3cd on development into 71aa2568c1a9c104054f39c77382e0bddc84d2af on master.

Coverage decreased (-3.8%) to 57.42% when pulling c2752c8dec61585d1457537055d5170efbfed3cd on development into 71aa2568c1a9c104054f39c77382e0bddc84d2af on master.

Coverage decreased (-3.8%) to 57.42% when pulling c2752c8dec61585d1457537055d5170efbfed3cd on development into 71aa2568c1a9c104054f39c77382e0bddc84d2af on master.


bug(material/select): Material 3 mat-selects use the secondary color for selected item backgrounds (when the component is styled to primary)

Is this a regression?

[x] Yes, this behavior used to work in the previous version

Material 2 uses a static color for this highlight.
The previous version in which this bug was not present was
No response
Description
The styling of a select (mat-select) highlights the background of a selected element. However even when you are using the default 'primary' styling of a select (as documented https://material.angular.io/guide/theming#using-component-color-variants) the background highlighting of the selected option in the select uses the secondary palette.

Reproduction
This is a stackblitz forked from the mat-select documentation. It has been adjusted to use custom styles as produced by the output of ng generate @angular/material:m3-theme with the following colors: primary: ff0000, secondary: 00ff00, tertiary: 0000ff. The generated m3-theme.scss was copied over into that stack blitz and m3-theme.$light-theme was then used for @include mat.all-component-themes(m3-theme.$light-theme) in styles.scss
StackBlitz link: https://stackblitz.com/edit/nngoxu-ggvcsg?file=src%2Fstyles.scss
Steps to reproduce:

click to select element to open up the options list; note the background of the selected element is miscolored

Expected Behavior
I would expect that the selected background color of a given palette to either be static (as in M2's rgba(0, 0, 0, 0.04)) or to be based on the colors in the palette chosen to style that component.
Possible work arounds:

Use material provided palettes (ie mat.$red-palette).
Use a secondary color / palette that is produced as a variant the primary color / palette.
Set the css variable --mat-option-selected-state-layer-color.

For my code I went with option 3; --mat-option-selected-state-layer-color: rgba(0, 0, 0, 0.04);. Note for option 3, as this is styling something in a cdk-overlay-container you have to make sure that your override still applies.
Actual Behavior
The background color of a 'primary' (default) styled select appears to be using the color as specified in the secondary palette at the '90' level. This 'works' when you use the included scss material palettes because the 'secondary' palette is bundled as a subelement of that palette. A trimmed version of the 'rose' palette (rose/red is one of the styling options on the angular material page), as found in @angular/material/core/themeing/_palettes.scss looks like
/// Rose color palette to be used as primary or tertiary palette.
$rose-palette: _apply-patches((
  0: #000000,
  10: #3f001b,
  <... color levels ...>
  secondary: (
    <... color levels ...>
    90: #ffd9e1, // this is what the selected element actually uses on material.angular.io when using the 'Rose and Red' theme
    <... more color levels>
  ),
  neutral: (
    <... color levels...>
  ),
  neutral-variant: (
     <... color levels ...>
  ),
));

So even for the documentation stylings all of the secondary palettes are mutated forms of the primary palettes and so the selected element's background looks good. When using the ng generate @angular/material:m3-theme no such binding between the primary palette & secondary palette is implied or generated. So when it selects a secondary.90 for styling the background of a primary styled mat-select component it looks wrong.
Environment

Angular: 18.0.1
CDK/Material: 18.1.3
Browser(s): chrome
Operating System (e.g. Windows, macOS, Ubuntu): macOs

@amysorto Thanks for the response; but I don't think this is completely resolved.
The M3 docs you linked don't talk about color theming variants at all. However when we look at the colors chosen its all 'secondary' colors. So for example Menu list item with trailing icon - icon color (ie the red checkmark next to pizza in the original image) is specified as md.sys.color.on-secondary-container.  I split the colors in this demo into rgb as an easier way to track what color palette stuff comes from; red is the primary palette (green secondary & blue tertiary). So even though the M3 docs are specifying on-secondary-container we end up using on-primary-container for that checkmark; and other elements of the component also use the primary palette; such as for non-selected background etc.
This inconsistency of 'secondary' vs 'primary' I believe is due to the introduction of component color variants as via https://material.angular.io/guide/theming#using-component-color-variants .  The docs for M3 menu (https://m3.material.io/components/menus/specs) seem to be using variants of the 'secondary' (or neutral) color for everything.  Thus when using a 'select' styled to use the 'primary' component color variant, all of these 'secondary' colors have been shifted to instead be 'primary' colors.
Thus I'd argue that if configuring select to be 'primary' color variant updates the Menu list item with trailing icon - icon color from md.sys.color.on-secondary-container to md.sys.color.on-primary-container then configuring the select to be the 'primary' color variant should also update Menu list item selected container color from md.sys.color.secondary-container to md.sys.color.primary-container.

The M3 docs have a table with color roles, thats what I was referring to initially for where these color roles are coming from.
Ahh I see what you mean. It seems the checkmark should be on-surface-variant from the spec. It may just be an incorrect mapping rather than related to having the color variants support.
I'll reopen this issue and take a closer look! Thanks!


I do add repo-svn command,but nothing happend

@clarkda

Hey @xiaozi4624 thanks for the bug report, could you pod --version and let me know what version of cocoapods you are using?

The version is 0.36.3

@xiaozi4624 i've found a issue in cocoapods core and i'm working on a patch. going to try to finish the unit tests this weekend and hopefully it'll be a little easier to see breaks between new versions of cocoapods

Thanks for the work!

在 2015年4月24日，下午12:47，Dustin Clark<EMAIL_ADDRESS>写道：
@xiaozi4624 https://github.com/xiaozi4624 i've found a issue in cocoapods core and i'm working on a patch. going to try to finish the unit tests this weekend and hopefully it'll be a little easier to see breaks between new versions of cocoapods
—
Reply to this email directly or view it on GitHub https://github.com/clarkda/cocoapods-repo-svn/issues/6#issuecomment-95799741.

my pods version is 0.38.2 and i also found the issue,is my usage wrong?

@TimeSkyBlack I've just released a new version of the plugin at 2.0.0 .. you'll need this + the very latest from master for https://github.com/cocoapods/cocoapods
Having done that your Podfile will end up looking something like
chunk:test-svn-project dusty$ cat Podfile
plugin 'cocoapods-repo-svn', :sources => [
  'http://<IP_ADDRESS>/svn/repo/master-svn/'
]

pod 'LoL-svn'

you'll have to use master until cocoapods does a release that includes @amorde's changes :cake:
i'm sure that will happen very soon? :pray:

@clarkda yeah!!! i build the latest cocoapods and 2.0.0  ,and it work as usual~！！！thanks a lot😊

@TimeSkyBlack awesome! sorry for the crazy delay!

@TimeSkyBlack glad to hear it's working for you! :)


Use both Inpainting and Canny edges

Hi,
Can I use your script with multiple controlnet conditioning?
e.g. inpaint the face conditioning on canny-edges or depth?
Thanks for your response

can you please guide me of where the extra condition should be added and where do I need to add the controlnet model?

Something like that should work.
controlnet = ControlNetModel.from_pretrained(controlnet_path, torch_dtype=torch.float16)
controlnet2 = ... # second controlnet

pipe = StableDiffusionXLInstantIDInpaintPipeline.from_pretrained(
  ...
  controlnet=[controlnet, controlnet2],
  ...
)
...
control_image2 = ...  # second control image

image = pipe(
  ...
  control_image=[control_image, control_image2],
  controlnet_conditioning_scale=[1.0,  0.8],
  ...
)


Updated version of downloaded bin from 0.1.1 to 0.1.2 (current latest).

I'm working on refactoring the way that testing is done. The refactoring will use the latest Vault release.


How to add new control buttons after create mixer?

Hello, thanks a lot for this! I am just learning how to use it.
I want to create the control buttons on the fly after a backend server query, asking for the items to add to the container. The idea is to show only the buttons (that represent tag names) that the answer of listed items contains. (And not all the tags in all items on the server)
I tried to create the mixer without the control buttons first, and then to add the items to the container and the control filter buttons after. But the buttons aren't working, no filtering at all.
What can I try?
Maybe to add all the items tags on the server at first, and just hide the not required buttons on the query request answer?
(Also I have to disable animations before I add the container items, to avoid the error about queue is full...There is some better solution to this?)
Thanks!

If you're going to be adding removing/buttons at runtime, you need to set the controls.live configuration option to true. Otherwise controls will be bound on instantiation only.
var mixer = mixitup(containerEl, {
    controls: {
        live: true
    }
});

Regarding, the queue full error when adding items, could you show me what your insertion code looks like?

Thanks Patrick for your reply!
it worked! with:
controls: {
        live: true
}

I am adding the items like this: It's on a loop sometimes with 400 or 10 items... And after the third item i can see the queue errors on the console.
/```
/ NEW DIV:
var newHtmlBox = ''+ seedName +''+ seedOwner +''+ seedTags +''+ seedCounter +'';
var newDiv = ''+ newHtmlBox +'';
mixer.insert(newDiv);

I have another doubt if you don't mind. I want to erase and empty all the container and mixer elements to perform new query searches to the server. Do you think thats a good way:

// DESTROY GRID:
mixer.destroy();
$(".container").empty();
// CLEAR FILTER BUTTONS:
$("#filterTags").empty();
$("#filterUsers").empty();
// RECREATE MIXITUP GRID:
mixer = mixitup(containerEl, {...
On your demo example the remove example iterates item by item...

You can insert an infinite number of items in one go using the .insert() method. So you don't need to insert them one at a time.
You should change your loop to something like the following:
var $itemsToInsert = $();

for (... your loop logic here ...) {
    $itemsToInsert = $itemsToInsert.add('<div...></div>');
}

// We now have a list of all new elements to insert, which
// we can pass to the insert method in one operation:

mixer.insert($itemsToInsert);

This example uses a jQuery collection, but you could do the same with vanilla JavaScript by creating in memory DOM elements for each element, and appending to an array or document fragment before passing to MixItUp (jQuery makes this a bit easier by automatically converting your HTML strings into in-memory DOM).
Regarding removing the mixer, yes that is the correct way if you want an completely new mixer. If you want to keep the same mixer running, but remove all its items before re-adding new ones, you can follow exactly the same pattern as above, but using the .remove() method instead of .insert().


nested sequence item parsing to fix issue with IconImageSequence

When parsing a DICOM file with IconImageSequence, the parser stumbles over the PixelData inside the sequence, because of calling pixeldata_parse with the root DICOMData as an argument. Using the item as the DICOMData argument in reading the items elements solves this.

LGTM! Thanks for fixing this.


filtering stats api for hidden model

Description
[filtering stats api for hidden model hieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Why does this pr merge to 2.x, not main?

Why does this pr merge to 2.x, not main?

Do you see any concern? I will backport to main eventually? In 2.x it's easy to test with injecting the code in cluster. For super admin, that's how I need to test.


Represent filter

Hi, thank you for your work on this! I'm looking to use igv-reports to highlight certain variants of interest from a background set of variants.
I use the "FILTER" column in the VCF for this and in the desktop version of IGV the variants are greyed out as shown:

However with igv-report the filter information doesn't seem to be visually displayed (although it is still there if manually inspecting the variant):

Would there be a way of having the FILTER column be able to be used to adjust opacity/colour? Or should I look to have that information as part of the INFO column? If so, any quick advice for colouring things by the INFO column?
Thank you!

This would be an issue for igv.js, I'm transferring the issue to that project.


dynamic change columns, item will overlap

Expected Behavior
dynamic change columns and it should calculate new item's position correctly.
Current Behavior
item will overlap
Steps to Reproduce

dynamic change columns
the item which is overflow will change to position 1 and overlap the first item

I will try to fix it, plz let me know if the overflow item is static, how would you want it to behave

Hi there,
I think this is a side effect after we fixed your previous bug.
Rgds
Geirr
On Tue, 8 Aug 2023 at 03:45, UTing1119 @.***> wrote:

Expected Behavior
dynamic change columns and it should calculate new item's position
correctly.
Current Behavior
item will overlap
Steps to Reproduce

dynamic change columns
the item which is overflow will change to position 1 and overlap
the first item

[image: wcvb9-ws07f]
https://user-images.githubusercontent.com/74576629/258960891-b1388ff2-55c3-424e-970b-71ce02b715f6.gif
I will try to fix it, plz let me know if the overflow item is static, how
would you want it to behave
—
Reply to this email directly, view it on GitHub
https://github.com/gwinnem/vue-responsive-grid-layout/issues/12, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRBD4ACHUC27OQYITX2PQ3XUGK3DANCNFSM6AAAAAA3HYBRX4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, did you manage to make a fix for this ?

yes, I was tryna find the reason why the resize event will be triggered when col number is set by user.
do you have any plans to refactor?

Hi @UTing1119
I am doing some work on the component right now, and will look into this issue to. Just wanted to check up on your progress on this issue.

@UTing1119 may I ask what you are using the component for ?
Regards
Geirr

@gwinnem if you're referring to dragging items, that's because I'm tryna set up a template item that will be added to the GridLayout correctly.
and maybe provide slots for users to customize its appearance.
but unfortunately I have no time to fix it or refactor it.
if any idea, plz let me know

still not work in version 1.2.2/1.2.4/1.2.5

@UTing1119
I'll try to fix this asap.
Currently working on the Resize enhancement issue
But will pause this and start working on this issue.

Hi @UTing1119
If im correct, it  is alway the top left GridItem which have this issue ?

I think it's more like the item overflows right side of the layout.
I guess it's because in src/core/helpers/responsiveUtils.ts, both moveToCorrectPlace and correctBounds function only consider about whether to collide with static items or not.

I think it's more like the item overflows right side of the layout.
I guess it's because in src/core/helpers/responsiveUtils.ts, both moveToCorrectPlace and correctBounds function only consider about whether to collide with static items or not.

It is strange the behavior, but with multiple statics the result is a lot of overflows when dynamically changes the max col value.
I am looking into it now and will release a new version asap.

Should be fixed in 1.2.9