Olomouc Official Edge Data

David and I have been looking through the data on Cloudstor, and we are unable to find the official data for Olomouc's edges. For Olomouc's official data, we were only able to find supermarket destination data. Is anyone able to send the original official data for Olomouc?
@gboeing @carlhiggs

I see it on cloudstor...
Go to the URL for "Official Data for Phase II Validation" then browse to /edge validation/Olomouc/olomouc_edges.*

@gboeing It seems that is not the official data. From the OSM geopackage, we were unable to load the edges for some reason. We were able to load the sample points as a proxy to the edges.
When plotting the sample points and the data from  /edge validation/Olomouc/olomouc_edges.* , they still matched up perfectly, leading us to believe that  /edge validation/Olomouc/olomouc_edges.* is actually the OSM data.
If you would like, I am available to call until 3:30pm.
@gboeing

@nicholas-david ah, got it. Ok that's a question for @carlhiggs then...
Carl, the "official" Olomouc edges shapefile on cloudstor is a perfect 1:1 match with the OSM edges data. This leads us to believe that it is not the true official data, but is simply a mislabeled copy of the OSM edges data. Can you double-check this for us, and perhaps update the "official" edges on cloudstor with the correct official shapefile if this is indeed the problem?

Hi all,
I'm not sure what is up with the data that is there, but I have just uploaded the original zip file provided by the collaborator Jan Dygryn for Olomouc street network data.  I also uploaded the street network data which was uploaded for Hanoi --- there may be good reasons this wasn't used previously, but in case it was overlooked I thought it worth also locating this in the edges folder since it is an asset we have to hand.
As far as I can tell the olomouc_edges shape file is what was provided by Thu on Google Drive:

There was some back and forth regarding file names I recall, and perhaps things got mixed up then.  In any case, its best to have the original source file in the format and name as it was provided for posterity I think.
Hope this helps,
Carl

@nicholas-david can you check these new files from Carl? If the Olomouc edges still look wrong, we can follow-up with Thu to see if she has the originals and got things mixed up on her end.

@gboeing I'll take a look at the Olomouc data.

I can confirm that the collaborator provided data appears different to that provided in the olomouc_edges.shp file --- on cloudstor and google drive the file sizes of that shapefile are in accord; however, they are much larger than those of the official network data:

Without looking at the data, I think this makes sense that the network labelled as 'olomouc_edges' is the OSMnx derived all roads dataset --- in particular, because its file sizes matches this shape file:

@carlhiggs thanks for tracking this down. Given that you appear to have the correct official Olomouc edges shapefile on your hard drive, would you mind uploading to the cloudstor validation data folder and replacing the incorrect edges shapefile there?

Hi @gboeing , assuming you are refering to the zip file provided by Jan Dygryn, I posted it on Cloudstor before making my initial post above.

Please let me know if I'm misunderstanding what you mean, but I think this is what you are asking for and it is already there.  I assume Thu was using this file previously, but when changing file names / uploading to Google drive it must have been mixed up with the OSM data.  (I assume you don't want the OSM data re-uploaded, as I believe that is there too?)
Enjoy the weekend,
Carl

I didn't remove the previous file that appears incorrect 'olomouc_edges' - and I don't think its necessarily a good idea to rename the official data to match that name construct.  I or others can delete this once what you need is sorted (I believe you all have edit and upload privileges).

Ah yes thanks Carl. I missed that detail earlier in my haste. Sorry.
@DRosasMoctezuma can you check that data file on Monday (by running the edge validation script with all the correct data files now) and verify we're all good now?

Thank you @carlhiggs @gboeing I will check the data file prior to our Monday meeting.

@DRosasMoctezuma thanks. Remember we pushed our team meeting to Tuesday next week.


[master] fix: change jwk priorities

:id: I will add when I get it

Hey @MartyniakAndrii, thanks for the contribution! We've started to review your PR and will have an internal meeting on Monday (when some devs will be back from holidays 😁) to discuss it in depth. We will keep you posted on the progress!


Unsupported queries: column must appear in the GROUP BY clause or be used in an aggregate function

The query runs on PostgreSQL but cockroachdb v19.2.0-beta.20190930 gives an error:
SELECT "defer_simpleitem"."id", "defer_simpleitem"."value", COUNT("defer_feature"."id") AS "feature__count"
FROM "defer_simpleitem" LEFT OUTER JOIN "defer_feature" ON ("defer_simpleitem"."id" = "defer_feature"."item_id")
GROUP BY "defer_simpleitem"."id";

column "value" must appear in the GROUP BY clause or be used in an aggregate function

Schema:
CREATE TABLE public.defer_feature
(
  id integer NOT NULL DEFAULT nextval('defer_feature_id_seq'::regclass),
  item_id integer NOT NULL,
  CONSTRAINT defer_feature_pkey PRIMARY KEY (id),
  CONSTRAINT defer_feature_item_id_ea27b723_fk_defer_simpleitem_id FOREIGN KEY (item_id)
      REFERENCES public.defer_simpleitem (id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION DEFERRABLE INITIALLY DEFERRED
)
CREATE TABLE public.defer_simpleitem
(
  id integer NOT NULL DEFAULT nextval('defer_simpleitem_id_seq'::regclass),
  name character varying(15) NOT NULL,
  value integer NOT NULL,
  CONSTRAINT defer_simpleitem_pkey PRIMARY KEY (id)
)

There are a number of failing queries like this in Django's test suite but I suspect the root cause is the same.

https://github.com/cockroachdb/cockroach/issues/26709 is the issue in our DB repo. I believe the team is going to work on this issue soon.

Fixed on cockroachdb master and backported to 19.2.1.


Is there a roadmap for releasing a 1.0 version?

A stable 1.0 version is on the way anytime soon?
Many thanks in advance. This is an awesome library!

@matteosister generally, I do not plan to change significant APIs before 1.0, the package has been quite stable for a long time now and I am happy with most of the design choices. There are a couple of ideas I have, one of them being to remove the C extension as it doesn’t add that much value, esp. for PHP 5.6 where we can get rid of call_user_func() and the like. I would generally be interested in what my userbase thinks about the following questions:

How important is the C extension to you? Do you use it in production?
What PHP version are you on?
What do you wish to see in functional PHP?

I do not use the php extension. It's a pretty large codebase in Symfony2, and we are bringing as many functional approach as possible, but we don't have a pure sysadmin in the team, and composer is a no-brain solution for us.

we are on php 5.5, because we are using aws elastic beanstalk to deploy our app. We are evaluating a migration to ebs + docker, so we can upgrade immediatly to 5.6. It's a matter of weeks anyway.

This library works great for us. For me there is only one thing that I'd like to see. And it's not really important. I'd like to see an alias for reduce_ to fold_. But as I said who cares? It's just that I love haskell...
A stable release would be great. I like to keep my minimum-stability in "stable". And IMO this library deserves a 1.0.0 release! :+1:

I, personally, on my projects do not use the C extension just because I do not have a need for it. It seems to be working fine on small to medium size projects without any noticeable difference.
Use both PHP 5.5 and 5.6 now but will migrate all project's server base to PHP 5.6 rather soon.
So far Functional PHP fit my needs.

I don't use the C extension and don't plan on doing so.  The PHP library is as fast as a non-functional approach would be, and that's good enough for me.
I've used this library on 5.3, 5.4, and 5.5.
A stable release :)

I don't use the C extension
I use it on 5.3 for now, migration on 5.6 is planned
A sort function would be nice, like Ruby Array.sort. For now I use usort but it modifies the collection.

@msadouni interesting idea to add an F\sort() function. Thank you

Hi, is there anything blocking the release of an alpha? I would love the use some of the features that aren't in the latest release, but cannot since my build software forces me to use tagged releases.

1.0.0-alpha5 is released

:+1:

thanks a billion!

I plan on migrating existing functional style code over to this library as standardization process. I would have just rewrote a lot of the functions, which doesn't make any sense. I don't plan on using the PHP extension in the future and will be using composer.
If there aren't any sort functions, then I might do a pull request when I need to do collections or I guess monoids.

So, here is the plan: release a 1.0 as far as possible and start working on the following changes for 1.2:

Use variadics and callables and bump version requirement to 5.6
Use generators for sequences
Add partial application function

1.0.0 has landed, 1.2 has been merged in to master


Gets attribute as expected, but throws StateError too

Using findElements() works as expected, unless element contains href attribute with query string attached to it.
Like,  https:// example.com/example.jpg?aid=rss_feed
So for example, the following will throw StateError and still provide href as expected. It does both.
try {       final itunesImageElement = itemElement.findElements('itunes:image').first;       final itunesImageAttrib =           itunesImageElement.getAttribute('href') ?? 'No itunesImage Attribute';       itunesImage = itunesImageAttrib;     } on StateError {       print('StateError is thrown ');     }
However, if href attribute is  https:// example.com/example.jpg
You still get href value as expected and no StateError is thrown.

Hard to tell what is going on. Can you paste the full stack trace of the StateError?

Here is stack trace:
I/flutter ( 7708): StateError is thrown
I/chatty  ( 7708): uid=10146(com.example.part1) 1.ui identical 7 lines
I/flutter ( 7708): StateError is thrown
I/flutter ( 7708): itunesImage | https://image.simplecastcdn.com/images/8862bce3-8814-46a6-9b72-a533960bbd50/5dd1869a-dac7-4edc-acb6-f791663f6fd1/3000x3000/wim176-frisby-ep-01-v001.jpg?aid=rss_feed

I just added a finally after the StateError {} and it is showing in stack trace the expected itunesImage value. And then showing the initial value I declared in the begin of the factory. I have to create a minimal viable project for you that demos this behavior. Should have this for you within 24 hours.

I'd like to see where the full stack of where the StateError is thrown, not where it is handled :-)

I don't know how to do that. I took the time to make a MVP, it is 280MB, tried to paste it here and got file too big error. How do I get this to you?

Ok, just discovered on StateError catch (e, s) is this what you want?
I/flutter ( 7161): Unknown exceptions: Bad state: No element, with stack:
I/flutter ( 7161): #0      Iterable.first (dart:core/iterable.dart:624:7)
I/flutter ( 7161): #1      new RssItem.parse (package:fake_throw/models/rss_item.dart:21:75)
I/flutter ( 7161): #2      new RssFeed.parse. (package:fake_throw/models/rss_feed.dart:26:43)
I/flutter ( 7161): #3      MappedIterator.moveNext (dart:_internal/iterable.dart:391:20)
I/flutter ( 7161): #4      new List.from (dart:core-patch/array_patch.dart:41:17)
I/flutter ( 7161): #5      new RssFeed.parse (package:fake_throw/models/rss_feed.dart:24:17)
I/flutter ( 7161): #6      RssParser.loadAsset (package:fake_throw/services/rss_parser.dart:12:13)
I/flutter ( 7161):
I/flutter ( 7161): #7      RssFeedLogic.rssFeed (package:fake_throw/rss_feed_logic.dart:12:25)
I/flutter ( 7161):
I/chatty  ( 7161): uid=10146(com.example.fake_throw) 1.ui identical 7 lines
I/flutter ( 7161): Unknown exceptions: Bad state: No element, with stack:
I/flutter ( 7161): #0      Iterable.first (dart:core/iterable.dart:624:7)
I/flutter ( 7161): #1      new RssItem.parse (package:fake_throw/models/rss_item.dart:21:75)
I/flutter ( 7161): #2      new RssFeed.parse. (package:fake_throw/models/rss_feed.dart:26:43)
I/flutter ( 7161): #3      MappedIterator.moveNext (dart:_internal/iterable.dart:391:20)
I/flutter ( 7161): #4      new List.from (dart:core-patch/array_patch.dart:41:17)
I/flutter ( 7161): #5      new RssFeed.parse (package:fake_throw/models/rss_feed.dart:24:17)
I/flutter ( 7161): #6      RssParser.loadAsset (package:fake_throw/services/rss_parser.dart:12:13)
I/flutter ( 7161):
I/flutter ( 7161): #7      RssFeedLogic.rssFeed (package:fake_throw/rss_feed_logic.dart:12:25)
I/flutter ( 7161):

Yes, perfect: Looks like RssItem.parse calls first on an empty collection (package:fake_throw/models/rss_item.dart:21:75). Look for the bug there ...

Sorry for bothering you with this non-existent issue.


ci: Fix coverage report with travis CI

Because some permissions were missing, goveralls binary was not installed and we lost the coverage report.

Changes Unknown when pulling 3f09010d1feb5f13c877be0aea8a87f69ce0ef98 on sboeuf/fix_coverage into ** on master**.

LGTM


http to https in algorithm details view

Summary
After merging branch 'info_on_analysis_in_progress' staging server reported and error in algorith details view: Mixed Content: The page at 'https://ohtup-staging.cs.helsinki.fi/quantmark/algorithm/2?version_id=7&metrics_id=7' was loaded over HTTPS, but requested an insecure script 'http://code.jquery.com/jquery-latest.min.js'. This request has been blocked; the content must be served over HTTPS.
How to test
Check that algorithm details view shows list of running analysis and there is now errors in console.

Codecov Report

Merging #155 (dee1621) into main (00e06a6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #155   +/-   ##
=======================================
  Coverage   88.34%   88.34%
=======================================
  Files          33       33
  Lines        1055     1055
=======================================
  Hits          932      932
  Misses        123      123

Continue to review full report at Codecov.

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


Join node can not combine complete messages

If the following node properties are set, the join node can not combine complete messages.
Mode：manual
Combines each：complete message
to create：an Array or a key/value Object
Send the message: after a count or after a timeout
Example

In the above, the join node sends a msg after 3 messages are received.
msg.payload should be an array of these messages, but msg.payload [2]  refers to msg not third received message.
msg.payload[0] ---> first received message
^   payload[1] ---> second received message
|   payload[2] -+  <- circular reference!
|               |
+---------------+

When the join node combines complete message,in the following code,
'group.msg' is the last received message and 'group.payload' has a reference to the last received message.
https://github.com/node-red/node-red/blob/master/nodes/core/logic/17-split.js#L303
So setting 'group.payload' to a property of 'group.msg', a circular reference occurs.

Thanks, for finding and fixing, will review.


[#1793] Fixed focus order a11y issue with resources dialog.

#1793
===
Fixes focus order of Dialog controls while in browse mode so that it is aligned with how the dialog is laid out visually.
Previous order:
Dialog heading -> Close button -> Dialog content
New order:
Close button -> Dialog heading -> Dialog content

Coverage remained the same at 65.913% when pulling e7847bac44addb1027479b045e9254c41db8dc6f on toanzian/acc-#1793 into e73b856c286266bc13d8b675fd4c1d9e0e402a8b on master.


AutocompleteTemplate: Use modelfile template for granite3

granite3 is currently using the "hole filler" template since it lacks FIM support. This template is getting sent to ollama raw, so the template from the model file is not getting applied to it.
This commit ensures the proper format is fed to the model, by moving the hole filler system message to be a global constant, and using it in the existing holeFillerTemplate and a new granteHoleFillerTemplate that also applies the appropiate model specific formatting.

this is marked draft because i haven't tested it yet, so haven't confirmed it doesn't regress results.
I just sketched it out a few days ago after noticing the problem when looking at ollama debug output.
I will test eventually, but for now, I just want to get it off my machine so I don't lose track of it.


Add 'OpenAL' package

Hey guys
Why here is no OpenAL or any other libraries for playing sounds/music?

Because you haven't made a package yet :p

I got this one for you @NukeBird ;)

@isaachier you will help me very much! ^^

https://github.com/ruslo/hunter/pull/1128

@isaachier thank you!

No worries glad to help


Unsupported Rust: range patterns

fn f() {
    match 4 {
        1..10 => (),
        _ => ()
    }
}

Open this code snippet in the playground

@maximebuyse, that's probably something you will want to look at, that should be fairly simple to add on top of #878!


Truncated results

when I try to decode a polyline I get coordinates with just 3/4 decimal.
I don't get why the results are rounded up/truncated, how can I get a 5 decimal precision?

Hi,
Could you pleas bring an example?

sure,  I'll attach a file with the data.
decodePolyline.txt

Thanks. And can you show how do you print the output values? It might be that the values are correct, but your serialization routine truncates them.

sorry!!! you're right, the problem was with the output function. I was using std::cout and now with printf have no problem whatsoever so now I get the full results.
Thank you!

No problem. Thank you for your interest, anyways.


Update version: Rem0o.FanControl version 181

[X] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[X] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.6 schema?

Microsoft Reviewers: Open in CodeFlow

Hi @OfficialEsco,
This manifest adds Apps and Features entries that aren't present in previous PR versions. These entries should be added to the previous versions, or removed from this version.
(Automated response - build 870.)


Dev

Here's the current state including dynamic client-side in-doc outline navigation.
TODOs: there seems to be some bad interaction between the app shell in carbon and how anchors in the side nav work, so the page is always scrolled a bit below where the anchor is.

@bgins all done AFAICT


Add a test in isRTLValue method

Hello @knolleary
Following our Slack conversation I think the code is ready now
Could you please review ?
Thank you very much for your help and time

Hello @knolleary ,
This is the fix I told you about yesterday
Could you please review it ?
Thank you

Hi,
when we spoke about this yesterday, I pointed out what I believed was the root cause further up the stack trace.
This is where your code is getting the current value of the input using $(this).val() which gets passed to the isRTLValue function: https://github.com/node-red/node-red/blob/ee45d6b48ffe27fbb0de118ff308a7a573c79cb0/editor/js/text/bidi.js#L67
From a previous discussion, that is not always going to be the right way to access a field's value. If it is a contenteditable div, then you need to be using $(this).text() as you do here:
https://github.com/node-red/node-red/blob/ee45d6b48ffe27fbb0de118ff308a7a573c79cb0/editor/js/ui/editor.js#L167
I cannot confirm this as we still don't have any test cases for the bidi work to help verify these changes.

Coverage remained the same at 88.294% when pulling 380bc8ffd294563da3dd777e4d7c57f21491878c on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.1%) to 88.186% when pulling 3dbb2361a0ef8e052828e18024f56f19b0799005 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.1%) to 88.186% when pulling 3dbb2361a0ef8e052828e18024f56f19b0799005 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.09%) to 88.205% when pulling 1c9c85487c3b282955374e1343fc833ed2aca76f on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.09%) to 88.205% when pulling 1c9c85487c3b282955374e1343fc833ed2aca76f on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.09%) to 88.205% when pulling 591b5852c03ffaef38ec9dd78d0b8ac1970a65f7 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.2%) to 88.092% when pulling 83a69b39ae02542436c4cba351b1eaff12b147c7 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.2%) to 88.092% when pulling 83a69b39ae02542436c4cba351b1eaff12b147c7 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.2%) to 88.092% when pulling 83a69b39ae02542436c4cba351b1eaff12b147c7 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Coverage decreased (-0.2%) to 88.092% when pulling 83a69b39ae02542436c4cba351b1eaff12b147c7 on wajnberg:0.15.0 into ee45d6b48ffe27fbb0de118ff308a7a573c79cb0 on node-red:0.15.0.

Hi,
I spent some time looking at this and decided a different fix was needed - closer to what I'd suggested in slack. Have committed that change directly:
https://github.com/node-red/node-red/commit/c797073c05731a81adff36a6681f4e9ea8c89af3
In summary:

return quickly from preparePropertyEditor if there is no matching form element for the property
only add keyboard event handlers to Inputs and TextAreas; all other form elements are irrelevant here


How do binary installation on Ubuntu via APT?

I am using ROS Humble and Ignition Fortress on Ubuntu 22.04. Although the README says that the binaries of packages are hosted at https://packages.ros.org/, it seems that the "gz_ros2_control" package cannot be found and installed by APT command:
sudo apt install ros-humble-gz-ros2-control.

For Fortress the package is called ros-humble-ign-ros2-control, but I can't find it and it's available in rosdistro. I will check what is happening

For Fortress the package is called ros-humble-ign-ros2-control, but I can't find it and it's available in rosdistro. I will check what is happening

It's hard to identify the packages and plugins names between Gazebo and Gazebo Classic at present.

This is my tip:

For the "new" Gazebo: Packages below Fortress are called ign-<something>. From Fortress packages are called gz-<something>.
For Gazebo-classic we use the hole name gazebo-<something>.


Getting error to open about wrong workspace folder - 3.6.9 (Win x64)

Hi there,
This is an oldest bug (3.5+ i think), after install and trying to open it by second time, I got an exception before splash screen.
Looking up about this error, I realize that Dbeaver didn't create his .dbeaver for my Win user 'Carlos Spohr', instead, his created a folder 'Carlos%Sphor'. See it below:

But log file was created at 'Users/Carlos Spohr/.eclipse/', same folder that my Eclipse create his files.

However, here is log about exception talking about permissions that DBeaver doesn't have at 'Program Files' folder.
!ENTRY org.eclipse.equinox.preferences 4 2 2016-05-30 21:35:58.223
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.IllegalStateException: The platform metadata area could not be written: C:\Program Files\DBeaver\workspace\.metadata.  By default the platform writes its content
under the current working directory when the platform is launched.  Use the -data parameter to
specify a different content area for the platform.
	at org.eclipse.core.internal.runtime.DataArea.assertLocationInitialized(DataArea.java:61)
	at org.eclipse.core.internal.runtime.DataArea.getStateLocation(DataArea.java:129)

Here complete stack:
https://gist.github.com/carlosjrcabello/134c5c5e072c36d9e5322398e80b7392
Is there any mode to change current workspace as Eclipse, or, configure it to create inside User folder in .dbeaver folder ?
Appendix
I didn't any customization about system permissions, just default installation folder and checking 'Reset settings' before install. I've reinstalled by four or five times cleaning any residual files or configurations.

Update,
Using standalone versions (zip) it's OK, but still writes configurations inside .eclipse folder...previously versions was .dbeaver.

This looks like a conflict with running version of DBeaver. Sometimes Eclipse executable just hangs during shutdown and never finish.
Reboot should solve this problem. Or killing dbeaver.exe in Task Manager (or killall dbeaver).

Hi there,
So, I did what you said, and I still getting this same error. I'll try to install it in my standalone apps folders to test it.

OK, installing it in other folder (not Program Files), all seems working normally. I'll continue testing it on next releases to see this occurs again.
If anyone else report an issue like this, I think you can close it.
Thanks Serge.

I was able to reproduce that.
The problem is in space in the profile name.

Yep,
DBeaver puts a '%' between words of profile name, at least, on Windows.
On Wed, Jun 1, 2016 at 7:39 AM, Serge Rider<EMAIL_ADDRESS>wrote:

I was able to reproduce that.
The problem is in space in the profile name.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serge-rider/dbeaver/issues/495#issuecomment-222956148,
or mute the thread
https://github.com/notifications/unsubscribe/AAm7R-833Bepz344MEyFuqJUZanxTzcsks5qHWFigaJpZM4IqGOV
.

--
Atenciosamente,
Carlos Alberto Junior Spohr Poletto
carlos.inf.br

Please test EA version
http://dbeaver.jkiss.org/files/ea/

Worked Serge!

DBeaver got correctly user folder and not creating a new one with '%', and I not received an error about workspace permission.
Tested with dbeaver-ee-3.6.9-x86_64-setup.exe binary.

Ok, thanks for testing.
I'll release hotfix version 3.6.10 on the next week.


MINOR: document restriction against running multiple Streams apps on same state.dir

Running more than one Streams instance on the same physical state directory has never been supported, but until now it's also not really been enforced. Since we fixed Streams to fail fast in the case of this misconfiguration instead of offering vague symptoms, we will throw an exception on startup if it is detected. We should document this clearly as some users may have been using this setup for testing (note: there's no reason to do this in a real production app, as you should either scale up by adding more threads and/or scale out by adding new instances with their own storage)

This should be cherrypicked back to the 2.8 branch (it's just docs) -- cc/ 2.8 release manager @vvcephei

Call for review any of @cadonna @lct45 @wcarlson5 @rodesai @agavra

LGTM! Merged to trunk and cherry-picking to 2.8

Cherry-picked to 2.8 cc RM @vvcephei


MC-9497 ReferenceDataValue functional specs

There is a strange bug causing the failures in mdm-plugin-referencedata/ReferenceDataModelFunctionalSpec... All of its tests pass when you run the spec on its own. But when running all tests in the plugin altogether (gradle :mdm-plugin-referencedata:integrationTest) it sometimes fails by returning the referenceDataModel.authority.url as https://localhost instead of http://localhost.
Any idea as to the cause? (Flaky test perhaps?)
Regardless, I can't see at a glance how the bug is caused by this PR.

@a

There is a strange bug causing failures in mdm-plugin-referencedata/ReferenceDataModelFunctionalSpec... All of its tests pass when you run the spec on its own. But when running all tests in the plugin altogether (gradle :mdm-plugin-referencedata:integrationTest), it sometimes fails by returning the referenceDataModel.authority.url as https://localhost instead of http://localhost.
Any idea as to the cause? (Flaky test perhaps?)
Regardless, I can't see at a glance how the bug is caused by this PR.

You can't run all the integrationTests at the same time as that runs the IT and FT tests.
You either need to run them like the ./run-all-tests.sh does using gradle
or do as the README instructs and use grails CLI
then

test-app -Dgradle.integrationTest=true -integration runs the IT
test-app -Dgradle.functionalTest=true -integration runs the FT

this will probably solve the issue you're finding.


Mythic Metals compatability

Mythic metals compatability for Fabricae Ex Nihilo like renewable starrite from sifting endstone or unobtanium but an extremely low chance or even every material
-this issue was made by your server's pissposter

Done.


chore: french translation

Summary of Changes
Add missing translation in French
Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[ ] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[ ] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[ ] Updated documentation as needed for changed code and new or modified features;
[ ] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

You have multiple different AFJ error messages being merged into one single message. This will make AFJ errors more difficult to troubleshoot. I would rather you create entries for each different type of AFJ error

You have multiple different AFJ error messages being merged into one single message. This will make AFJ errors more difficult to troubleshoot. I would rather you create entries for each different type of AFJ error

Resolve

@agueye84 able to get this PR up to date with the base branch? Then I'll run the automated checks

@agueye84 Re. Brycen's comment above. Sorry for the delay but we were hoping someone with better French skills than ours would be able to review. Nudge nudge @jcdrouin21.

I reviewed the French localization changes with my limited French ability and suggested some changes and made comments. Not sure if it should be reviewed further by a native French speaker.

@bryce-mcmath Did your comment get addressed? If so you'll need to re-review and approve.


How do i change version or where do i get sourcecode for 1.8

Hello,
I want to know how to change the version to 1.8 or where i can download version 1.8

I believe the last commit for 1.8 was this one: https://github.com/Steveice10/MCProtocolLib/commit/4ccf753002a9666a259649061afffa785c0731d6
You can either build it yourself or, if you use jitpack, you can specify a commit hash as the dependency version.


Please elaborate on the use of scopes

Can you please elaborate on the usage of the scopes?
Are the given scopes somehow automagically required, even if the authentication call was made using less (or even different) scopes?
Or are those scopes only used when the authentication-redirect takes place?

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

ID: 47770286-78c2-00ac-b923-e03041d2c059
Version Independent ID: a0835218-8f50-4cfc-d927-c3d61b6202e0
Content: How to configure Microsoft Account authentication for your App Services application
Content Source: articles/app-service/app-service-mobile-how-to-configure-microsoft-authentication.md
Service: app-service
GitHub Login: @mattchenderson
Microsoft Alias: mahender

@nils-a Thanks for the feedback. We are actively investigating and will get back to you soon.

Hello @nils-a - Thank you for your question. Please take a look this documentation: Scopes, permissions, and consent in the Azure Active Directory v2.0 endpoint
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

I'm sorry. Maybe I missed something.
Doc's you linked explain scopes in general. How does that relate to the question?

Hi @nils-a - Apologies for closing to soon - I misunderstood your question. I'm still a little unclear as to what you're exactly looking for with respect to scopes. Were you more interested in how scopes are utilized in EasyAuth and how it works internally?

Sorry for being unclear. I was asking specifically "when" the in azure given scopes are being  used.
Let me make an example.

I define a function/app-service/whatever
I enable authentication as described by the article - here I select some scope.
I create an app/website/whatever to consume the function from point 1. For this (as described in https://docs.microsoft.com/en-us/azure/app-service/app-service-authentication-overview ) I'd need to:

Authenticate to the auth provider using the auth providers SDK (and using my own scopes, as defined by the providers SDK)
post the received auth token to /.auth/login/
use the returned app-service auth token (via X-ZUMO-AUTH header) for further, authenticated requests.

Now: Where in this process are the scopes I defined in the function/app-service (see step 2) being used. As far as I can ascertain they are never used. Only the given scopes from step 3.i. are being used...

@nils-a  Thank you for additional info. Since your scenario involves 2 apps establishing authentication & authorization between each other (apps in point 1 and 3), using Azure Managed Service Identity instead may be a better fit.
EasyAuth flow discussed on this documentation implements OAuth2.0 protocol where end-user has to review & approve consent screen and the corresponding scopes are enforced & verified at the time when resource server validates the access tokens.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

@mike-urnun-msft no, my example seems to be misleading. Sorry making it not clearer.
The question is when, if ever are the scopes used that are configured in the page?

Hi @nils-a Since this channels is for driving improvements towards content of this documentation, could you open a thread on MSDN forums instead?

@mike-urnun-msft Sorry - I don't get it.
The documentation is about "configuring [...] Microsoft Account login".
When you look at the (modified) screenshot below:

while everything in red is explaind (or at least "used") in the article, the green part is missing completely from the documentation.
My question was "can please someone update the docs, so it reflects the missing parts".
Are you now asking me to go to the forums and find out for myself if there is someone out there who knows the things that are currently not documented?


Need way to clear parents

As discovered in #43, we need a way to clear parents in addition to setting them

FYI if you write something like "fixes #44" in your commit message, it will automatically close the issue when the PR is merged, and will link the two. See https://github.blog/2013-01-22-closing-issues-via-commit-messages/


Update idc slim master

@pedrokohler lets wait for @fedorov to test recent upstream changes then we can update this PR. We might have other changes coming soon.


Crash in TagManagerQueue -[TAGHitStore buildPendingEventFromStatement:]

[READ] Step 1: Are you in the right place?
Crash in the Firebase SDK
[REQUIRED] Step 2: Describe your environment

Xcode version: 11.1
Firebase SDK version: 6.8
Firebase Component: Analytics
Component version: 6.8

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Crash happening in the wild, unable to reproduce locally. Stack trace:
Crashed: TagManagerQueue
0  libswiftCore.dylib             0x1bb3807e4 +[__SwiftValue allocWithZone:].cold.1 + 16
1  libswiftCore.dylib             0x1bb35d9f8 -[__SwiftValue copyWithZone:] + 14
2  libobjc.A.dylib                0x1ad88f458 objc_allocWithZone + 52
3  Foundation                     0x1adf16e7c _decodeObjectBinary + 2164
4  Foundation                     0x1ade655dc -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 868
5  Foundation                     0x1ade2e1a4 -[NSDictionary(NSDictionary) initWithCoder:] + 180
6  Foundation                     0x1adf16ed8 _decodeObjectBinary + 2256
7  Foundation                     0x1adf16354 _decodeObject + 344
8  Foundation                     0x1ade1e088 -[NSKeyedUnarchiver decodeObjectForKey:] + 172
9  Foundation                     0x1ade74244 +[NSKeyedUnarchiver unarchiveObjectWithData:] + 92
10 jobs                           0x102367874 -[TAGHitStore buildPendingEventFromStatement:] +<PHONE_NUMBER>
11 jobs                           0x102366fa0 __44-[TAGHitStore fetchPendingEventsToCallback:]_block_invoke +<PHONE_NUMBER>
12 libdispatch.dylib              0x1ad7ffbb0 _dispatch_call_block_and_release + 32
13 libdispatch.dylib              0x1ad80100c _dispatch_client_callout + 20
14 libdispatch.dylib              0x1ad807484 _dispatch_lane_serial_drain + 568
15 libdispatch.dylib              0x1ad807eb0 _dispatch_lane_invoke + 368
16 libdispatch.dylib              0x1ad810f20 _dispatch_workloop_worker_thread + 580
17 libsystem_pthread.dylib        0x1ad866aa0 _pthread_wqthread + 280
18 libsystem_pthread.dylib        0x1ad86cc78 start_wqthread + 8

Hm, based on my limited understanding of the Swift stdlib -[__SwiftValue copyWithZone:] should not call through to alloc. See these lines
Is this only occurring in older versions of iOS?
Also, based on the stack trace contents, you may be able to work around the issue by not passing Swift objects into Tag Manager (though this is hardly a practical workaround).

Predominantly happening on iOS 13 (85% of crashes) with the rest on iOS 12 and 11 evenly.
I can take a look at what objects we're passing through to Firebase Analytics but as you mention this might not be feasible.

Thanks for this insight @morganchen12 - I found an instance where a Swift Enum value was being sent as a parameter value in a Firebase event.

We should be able to prevent this sort of bug by re-typing the parameter, but afaik it's not idiomatic  and might result in weird casting requirements. What method in TagManager were you calling?

Looks like I spoke too soon - the issue is still happening, but as far as I can tell we're not sending anything but swift Strings through as parameter values.
We're calling this function from swift:
+ (void)logEventWithName:(NSString *)name
              parameters:(nullable NSDictionary<NSString *, id> *)parameters
    NS_SWIFT_NAME(logEvent(_:parameters:));

Looking through the tag manager codebase, it's trying to unarchive some Analytics events immediately after the app finishes launching. Can you try to repro the crash by logging some Swift values and then restarting the app?


WIP: gossip validation error handling refactoring

dependent on #1561
-integrates the BlockError and AttestationError into the respective gossip validations
-more to come

decided to not open this yet because it has changes from #1561 , which is still not finished, merged into it


Update logback-classic, logback-core to 1.2.10

Updates

ch.qos.logback:logback-classic
ch.qos.logback:logback-core

from 1.2.6 to 1.2.10.
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 = "ch.qos.logback" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #304.


Swift 3.0 Support

Hello,
I've been working on a Swift 3.0 update but have run into a gnarly crash I don't know how to fix. If anyone else wants to pick it up from here and fix it, or point me in the right direction, I'd greatly appreciate it!
I think I've tracked down the issue to objc_getAssociatedObject receiving an object that can't be turned into a ValidationRuleSet, but I'm not 100% sure on that. I am pretty sure that the bug is something in ValidatableInterfaceElement.swift though.

Closed pending #42


Default "unbounded" sequences to a value (100) in IDL to match what RTI's IDL compiler does

Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
RTI's IDL compiler defaults all unbounded sequences to 100. This means that all unbounded sequences in SNA, when using RTI, are really sequences bounded to 100. This should be reflected in CX to make it easier to understand by developers and to have the IDL just reflect this hidden default.

Please work this before the PATHMAP safeguard ticket (#191 ) if possible.

I will work on this first. To be clear, we need to treat unbounded sequences as if they have 100 as value when generating descriptor file?

Actually. I will set the default value of sequence bound to 100 when it is created if that’s ok.

@ysroh No, we don't want the default value set to 100. We want the value of "Unlimited" or "infinited" or whatever it is to default to 100 (more specifically, a configurable value) when IDL is generated. Descriptor files (CDP and CDD) do not contain or care about unbounded sequences.We are only concerned with IDL files.

@J17359 Got it. I have one more question. If unlimited translates to 100 then what about any value that is greater than 100 set by user?

@ysroh Two things:

We want unlimited to translate to 100 by default, but we want this value to be modifiable. In otherwords, a preference setting that is set to 100, but could be changed. When the user generates IDL, whatever value is in that preference setting is what is used to set sequence bounds. Additionally, this preference should allow a user to set the value to -1, or unlimited, in which case the sequences generated in the IDL would truly be unbounded. This is the current behavior, and while we do not want it to be the default, we should still provide it.
Values over 100 are fine. The issue that we are trying to resolve is the one where RTI sets all unbounded sequences to 100 by default. This causes issues when trading IDL between developers who may be using different DDS vendors. If the IDL specifies all sequence bounds, then the IDL would create the same DDS types in any DDS impelementation (theoretically)

@J17359 Thanks for the clarification. I will let you know when I have the fix ready. Thanks.

@ysroh I was able to test out your change today. I think there is a small miscommunication. We do not want to default a "null" bounds to the values specified in the preference page. This would be bad as it takes information out of the model and hides it in the generation step, which can make understanding the interface difficult.
What we would like is the value "CCM_DDS::UNLIMITED" modified to take the value specified in the preference page when generated to IDL. Either that, or a new bounds value, say "RTI_UNBOUNDED", that can be filled in with the value in that preference page. The issue is that when "CCM_DDS::UNLIMITED" is placed in the IDL file, RTI assumes 100 (unless the IDL is generated differently).

@j26151 I see. I will update the code to translate CCM_DDS::UNLIMITED to the value specified in the preference page. Thanks

@j26151
Here is the snapshot of the preference page.

The CCM_DDS::UNLIMITED will be translated to the value specified but if this field is empty or -1 then "CCM_DDS::UNLIMITED" will be the sequence bound like before.
Let me know if have any comments on this before I make final change.
Thanks.

That looks good to me.

Actually, can you give me a little bit of time to verify with some of our applications before making this change

Alright, so I think that we want to do what you have above (where CCM_DDS::UNLIMITED will be translated to the value), the only other fix that I want to state is that if the value is -1 or the field is empty, then the sequences generated should be
typedef sequence  testSeq;
and not
#include "CCM_DCPS.idl"
....
typedef sequence <long, CCM_DDS::UNLIMITED> testSeq;
CCM_DDS::UNLIMITED is defined in a file in axcioma (dds4ccm_base.idl), but as far as I can tell, it is not meant for us to use or include. Also, the include CCM_DCPS.idl does not exist in axcioma.

@j26151 Thanks. I will make that change.

This should be fixed now.

I have verified this on our end, thank you. You can close this issue whenever you want.


Fix: Data Race Vulnerability in ThreadedSeedGenerator Counter

This pull request makes the following changes

Fixes issue #1885

Checklist

[x] I have created an issue for the solution I am submitting
[x] I forked the base repository, created a new branch and made my changes in the new branch created
[x] My pull request is sent to the latest base branch in the original bc-java repository
[x] I have linked the issue I worked on to this pull request submitted by me
[x] File(s) now contain changes as specified in the issue I worked on

See #1885


App is failing to launch

React Native version:

0.59.9
Steps To Reproduce

When we are installing the app in the iPhone 6 (12.3.1), app is working properly on the first launch. But we close it and reopen it does not launch and it shows up in the tray as an active app.
If we close it and open it again same thing happens but we are not able to use the app. It just shows up in the tray.

Describe what you expected to happen:
The app should launch normally as it does on the first time.
Snack, code example, or link to a repository:

Console output -
2019-07-10 17:19:13.842669+0530 AppName[7829:2290393] - [I-ACS036002] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2019-07-10 17:19:14.360500+0530 AppName[7829:2290396] 6.3.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60002000 started
2019-07-10 17:19:14.403169+0530 AppName[7829:2290395] 6.3.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2019-07-10 17:19:14.671917+0530 AppName[7829:2290397] 6.3.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2019-07-10 17:19:14.674752+0530 AppName[7829:2290307] -[RNFirebaseNotifications init] [Line 46] Setting up RNFirebaseNotifications instance
2019-07-10 17:19:25.094653+0530 AppName[7829:2290397] [BoringSSL] nw_protocol_boringssl_input_finished(1543) [C3.1:2][0x1019191f0] Peer disconnected during the middle of a handshake. Sending errSSLClosedNoNotify(-9816) alert
2019-07-10 17:19:25.122485+0530 AppName[7829:2290397] TIC TCP Conn Failed [3:0x2836bef40]: 3:-9816 Err(-9816)
2019-07-10 17:19:35.433926+0530 AppName[7829:2290421] [BoringSSL] nw_protocol_boringssl_input_finished(1543) [C4.1:2][0x10192bf00] Peer disconnected during the middle of a handshake. Sending errSSLClosedNoNotify(-9816) alert
2019-07-10 17:19:35.436145+0530 AppName[7829:2290421] TIC TCP Conn Failed [4:0x2836b4f00]: 3:-9816 Err(-9816)
2019-07-10 17:19:35.506915+0530 AppName[7829:2290421] [BoringSSL] boringssl_context_alert_callback_handler(3724) [C5.1:2][0x101826390] Alert level: fatal, description: inappropriate fallback
2019-07-10 17:19:35.507113+0530 AppName[7829:2290421] [BoringSSL] boringssl_session_errorlog(224) [C5.1:2][0x101826390] [boringssl_session_handshake_incomplete] SSL_ERROR_SSL(1): operation failed within the library
2019-07-10 17:19:35.508381+0530 AppName[7829:2290421] [BoringSSL] boringssl_session_handshake_error_print(205) [C5.1:2][0x101826390]<PHONE_NUMBER>:error:1000043e:SSL routines:OPENSSL_internal:TLSV1_ALERT_INAPPROPRIATE_FALLBACK:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-109.250.2/ssl/tls_record.cc:586:SSL alert number 86
2019-07-10 17:19:35.509010+0530 AppName[7829:2290421] [BoringSSL] boringssl_context_get_error_code(3617) [C5.1:2][0x101826390] SSL_AD_INAPPROPRIATE_FALLBACK
2019-07-10 17:19:35.513114+0530 AppName[7829:2290421] TIC TCP Conn Failed [5:0x2836b5e00]: 3:-9860 Err(-9860)
2019-07-10 17:19:35.514880+0530 AppName[7829:2290421] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9860)
2019-07-10 17:19:35.514964+0530 AppName[7829:2290421] Task <7D486CE3-EF13-4511-8BC6-D1D617DC98D0>.<1> HTTP load failed (error code: -1200 [3:-9860])
2019-07-10 17:19:35.515311+0530 AppName[7829:2290422] Task <7D486CE3-EF13-4511-8BC6-D1D617DC98D0>.<1> finished with error - code: -1200

Having the exact same issue, any updates?

Gday
If this is still an issue could you try running it with yarn react-native start --reset-cache and let me know the result? It sounds like its broken from the get-go but you first load a cached version, then when you reload, it loads your broken version
Also, what's the result of adding these lines to your info.plist
<key>NSAppTransportSecurity</key>
<dict>
 <key>NSAllowsArbitraryLoads</key>
 <true/>
</dict>

Just a hunch based on your NSURLSession/NSURLConnection HTTP load failed  line in the log you pasted.


Remove Activation dependency

Related to #1388
According to https://github.com/dropwizard/dropwizard/issues/2318 the issue was fixed with DW 2.0, so we should not need this dependency anymore?
I couldn't see errors when starting the webserver locally.

Looks good - thanks!


implement bounded mpmc queue

#6
WIP:

[x] add more input check
[x] add more method
[x] performance optimization
[x] add more test cases

Has performance testing been done? (e.g. compare with the ordinary concurrent_queue).


Request: Print out the crop values for the active area offsets

Hello quietvoid,
when using the --crop/-c parameter when extracting the rpu data like so:
ffmpeg.exe -i "Hybrid HDR10Plus DV Sample.mkv" -an -sn -dn -c:v copy -bsf:v hevc_mp4toannexb -f hevc - | dovi_tool.exe -m 2 -c extract-rpu - -o "RPU.bin"
...the only information provided is:
Reordering metadata... Done.
It would be nice and useful to get information about the crop values, so they can be used for further processing.
Something like:
Reordering metadata...
Offsets were cropped by: left=0, right=0, top=276, bottom=276
Done.

In this context I have also a question:
Where does dovi_tool take the values, to crop the offsets, from or how are they calculated?

It's an extract operation and not meant to show any info.
Use the appropriate subcommand to get offsets info:
dovi_tool export -i RPU.bin -d level5

Okay, thanks anyway.

There's no calculation, --crop simply sets the L5 metadata to all zeros.

That was actually pretty helpful, thank you.


[BUG] Can not save quantized model to disk: "you shouldn't move a model that is dispatched using accelerate hooks."

Describe the bug
Hi all, recently when I do experiments with different quantization method,  I come through TheBloke repo in Huggingface but can't find my model on his quantized list. That why I decide to quantize myself.
I also looked at #291.
I was use GPTQ to quantize Llama-2-70B model with following setup:
Hardware details
4 x A100 (80GB each) = 320GB VRAM
32 core of CPU.
240 GB RAM
Software version
Cuda 12.2
pip install auto-gptq==0.7.1 --no-build-isolation

pip install transformers==4.38.2

To Reproduce
Steps to reproduce the behavior:
Use following config:
quantize_config = BaseQuantizeConfig(
    bits=4,  # quantize model to 4-bit
    group_size=32,  # 64, 128
    damp_percent=0.01,
    desc_act=True,  # set to False can significantly speed up inference but the perplexity may slightly bad
)

max_memory = {0: "40GIB", 1: "40GIB", 2: "40GIB", 3: "40GIB"}

num_samples = 2048
pretrained_model_dir = "/models/llama70b"
quantized_model_dir = "/models/gptq/llama70b_4bit_32_act"
quantize_dataset_path = "/Dataset/alpaca_data_cleaned.json"

tokenizer = AutoTokenizer.from_pretrained(pretrained_model_dir,
                                          #use_fast=True,
                                          trust_remote_code=True
                                         )

And then:
model = AutoGPTQForCausalLM.from_pretrained(pretrained_model_dir,
                                            quantize_config,
                                            trust_remote_code=True,
                                            torch_dtype=torch.float16,
                                            max_memory=max_memory,
                                           )

model.quantize(examples_for_quant,
               cache_examples_on_gpu=False,
               batch_size=8
              )

The error happen when
model.save_quantized(quantized_model_dir)

When I monitoring the process with top and  nvidia-smi command in Linux:

In the quantization phase, every thing seem normal:
In the beginning, because Llama-2-70b is 140GB in fp16, therefore 4 gpu each recieved 35GB. It seem correct and normal.
Then, each GPU is used consequently depend on which layer is in it. e.g: When it come to the layer in the particular GPU, the usage of this GPU will be high.
This take 4 hours long.

But after it finish with layer 80. I see that it copy all of the weight down to the CPU, I see the RAM usage is increasing slowly to 220GB RAM. It take about 1 hours just for copy from GPU to CPU.

In the end my process is killed with the reason:

...
INFO - Quantizing mlp.down_proj in layer 80/80...
You shouldn't move a model that is dispatched using accelerate hooks.
Killed

Lastly I would like to know the differences with the loading method of autoawq.
For reference, when I quantized with AutoAWQ, it take about 1 hours and its able to run on a instance with 90RAM + 80GB VRAM.
With GPTQ it is much slower (5 hours compare to 1 hours) and 4 time resource requirement VRAM or RAM.

Now Im trying to use the low_cpu_mem_usage=True and ignore the max_memory as @TheBloke mentioned https://github.com/AutoGPTQ/AutoGPTQ/issues/291#issuecomment-1695992421

I'm having the same problem. The warning appears to come from the accelerate library:

https://github.com/huggingface/accelerate/blob/main/src/accelerate/big_modeling.py


virus en el archivo zip

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System

Server OS: [e.g. Windows 10]
Client OS: [e.g. Windows 7]
Server installed .NET Framework version: [e.g. v4.8]
Client installed .NET Framework version: [e.g. v4.8]
Quasar Version: [e.g. 1.3.0 or commit-id]
Build configuration: [e.g. Debug/Release]

Additional context
Add any other context about the problem here.

no es un virus. creo que se arregla con presionar ctrl+j y click allow download.

smh.....

smh.....

this isn't even an issue about quasar

smh.....

this isn't even an issue about quasar
they also didn't fill the fields with information.

Yes, I agree


Circular imports

Remove all calls to the pypit package
to avoid circular imports.  This meant
duplicating a few of the methods in
pypit's arutils (e.g robust_polyfit).
It will be wise in the future to begin tagging
releases of arclines.

merging for now, but arclines is headed into PYPIT proper
before long.


Avoid the 404 error when generating javadoc, and actually show failed compilation results

When generating Javadoc, even if the Umple model is perfect, the documentation might not be generatable.
This can happen if a state machine refers to a non-existant attribute or method, or if there are any compilation errors in methods in the model. It is simply that javadoc generation actually attempts to compile, and fails.
Currently a page appears 'A page you requested was not found' ... in other words a 404 error page appears.
The solution would be to detect the failed compilation and actually show the javac error messages. It could look something like 'Unable to generate Javadoc because there is uncompilable Java code in the model. This can happen when methods cannot be compiled, or when state machine guards or constraints refer to non-existant attribiutes or methods. The following are the javac compilation results. You should try to correct the embedded Java that is resulting in these messages'. Ideally line number references would result in clickable items that could select the relevant line in the model.

New versions of javadoc seem less sensitive, so polishing this issue is not worth it. Once we update the main server to newer Java, this issue will not be a problem any more.


Add full instructions for elm-install

This is in the example but it's not obvious.
If you don't add "cmditch/elm-web3": "0.2.1 <= v < 1.0.0" then elm-install will just ignore it without throwing an error or message.

Thanks!


[Feature request] Keep original terminal colors

Would it be possible to keep the original terminal colors ? Depending of the combinations the miss-match of colors make working with mprocs impossible.
Usable but not very pretty

Not usable at all

Yeah, I didn't put much effort into colors. Will revise it.

I second this! I have a onedark colorscheme in my terminal, and it is unusable. I don't think being able to configure custom colors is necessary, just sane defaults picking up the colors from the terminal colorscheme.
Btw, fantastic product idea, thanks for the work! It's missing a few things and fixes but it looks super promising to add it to my workflow.

I switched to only basic 8 colors, which are defined by your terminal theme. It is now in master and I will release is today/tomorrow. Later I plan to add support to override the colors in the config.

I released mprocs 0.4.1 which uses basic 8 colors. All elements are visible on my light theme. Feel free to reopen if there are still issues with a light theme.


fix InsertExecutor afterImage

Ⅰ. Describe what this PR did
fix InsertExecutor afterImage
Ⅱ. Does this pull request fix one issue?

fixes #1500 #1430 #1516
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1512 into develop will increase coverage by 0.02%.
The diff coverage is 65.11%.

@@              Coverage Diff              @@
##             develop    #1512      +/-   ##
=============================================
+ Coverage      46.41%   46.44%   +0.02%
- Complexity      1691     1696       +5
=============================================
  Files            347      347
  Lines          12707    12738      +31
  Branches        1589     1598       +9
=============================================
+ Hits            5898     5916      +18
- Misses          6169     6177       +8
- Partials         640      645       +5

Impacted Files
Coverage Δ
Complexity Δ

...ource/sql/druid/oracle/OracleInsertRecognizer.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...rm/datasource/sql/druid/MySQLInsertRecognizer.java
68.42% <0%> (-8.05%)
7 <0> (ø)

...va/io/seata/rm/datasource/exec/InsertExecutor.java
84.09% <84.84%> (-0.99%)
25 <1> (+5)

.../io/seata/common/loader/EnhancedServiceLoader.java
62.29% <0%> (-0.21%)
24% <0%> (ø)

...n/java/io/seata/rm/datasource/ConnectionProxy.java
9.09% <0%> (ø)
4% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

mysql
create table test(
id int primary key auto_increment,
name varchar(45),
name2 varchar(45)
)

1. containsPK (preparedstatement)  pk is ?
insert into test(id, name, name2) values (?, ?, ?)
2. containsPK (preparedstatement) pk is null
insert into test(id, name, name2) values(null, ?, ?)
3. containsPK (statement) pk is null
insert into test(id, name, name2) values(null, '11', '111')
4. containsPK (preparedstatement) pk is null or ?
insert into test(id, name, name2) values(null, ?, ?), (?, ?, ?)
parameters: ['11', '111', null, '22', '222']
5. not containsPK (preparedstatement) pkvalue is null
insert into test values(null, ?, ?)
6. not containsPK (preparedstatement) pkvalue is ?
insert into test values(?, ?, ?)
7. not containsPK (preparedstatement)
insert into test(name, name2) values(?, ?)
8. not containsPK (statement)
insert into test(name, name3) values('11', '111')

mysql not support
1. insert into test(id, name, name2) values(fun(), ?, ?), (fun(), ?, ?)
2. insert into test(id, name, name2) values(null, '11', '111'), (null, '22', '222')
3. insert into test(id, name, name2) values(?, ?, ?), (1, ?, ?)

oracle
create table test(
id int primary key,
name varchar(45),
name2 varchar(45)
)
create sequence test_seq;

1. containsPK (preparedstatement) pk is seq
insert into test(id, name, name2) values(test_seq.nextval, ?, ?)
2. not containsPK (preparedstatement)
insert into test values(test.seq_nextval, ?, ?)

oracle not support
1. insert into test(id, name, name2) values(fun(), ?, ?), (fun(), ?, ?)
2. insert into test(id, name, name2) values(test_seq.nextval, '11', '111'), (test_seq.nextval, '22', '222')
3. insert into test(id, name, name2) values(test_seq.nextval, ?, ?), (1, ?, ?)


Add cancelable SQL api requests

Add cancelable mechanism to SQL api / datasets fetch requests + its application to:

[x] Formula widget
[x] Category widget
[x] Histogram widget
[x] Geocoding
[x] Isochrone
[x] User datasets

Allow the use of signal & AbortController to abort fetch requests, so they are correctly cleaned up in react components, and they don't throw errors on console like this one:

This adds cleanup functions to each component.

More work is required, either here or in a 2nd PR, for other widgets: Geocoder & Isochrones

I have decided to add more fixes into this PR, related to other models... WIP

Would be possible to have create the AbortController in the executeSQL?
I think that would be great returning an object as {'request': Promise, 'cancel': Function} instead to create it in each widget

Hi @Josmorsot, about your comments... I see your point.
I've been thinking about it but I'm not sure about making the change, because of the impact to the API. I would like to have more feedback from other mates before we decided:
Here it is the choice:
Option 1 (current: external abort)
client (react component)
useEffect(() => {
    const abortController = new AbortController();
    const signal = abortController.signal;

    const handleCalculateIsochrone = async () => {
      try {
        const isochrone = await getIsochrone(
          credentials,
          {
            geom: latLong,
            mode: selectedMode,
            range: selectedRange,
          },
          { signal }
        );
        updateIsochrone(isochrone);
      } catch (error) {
        if (error.name === 'AbortError') return;

        dispatch(setError(`Isochrone error: ${error.message}`));
      }
    };

    return function cleanup() {
      abortController.abort();
    };
  });

Option 2 (internal abort)
 useEffect(() => {
    let getIsochroneRequest;
    const handleCalculateIsochrone = async () => {
      try {
        getIsochroneRequest = await getIsochrone(
          credentials,
          {
            geom: latLong,
            mode: selectedMode,
            range: selectedRange,
          }
        );

        const isochroneResult = await getIsochroneRequest.result;
        updateIsochrone(isochroneResult);
      } catch (error) {
        if (error.name === 'AbortError') return;

        dispatch(setError(`Isochrone error: ${error.message}`));
      }
    };

    return function cleanup() {
      getIsochroneRequest.cancel();
    };
  });

On the one hand, option 1 (current) keeps the abort mechanism as something optional, and controlled by the client, keeping the api responses more simple for non cancelable use cases...
On the other hand, option 2 works probably better as an abstraction for cancelable use cases, but at the cost of adding always this kind of response object for all api requests:
// made-up, not real SQL api
export const apiRequest = async (opts) => {
    const abortController = new AbortController();
    const signal = abortController.signal;

    let promise = fetch(request, { signal } );

    return {
          result: promise,
          cancel: () => { abortController.abort() }
    }
};

I'd go with something like this:
useEffect(() => {
    const abortController = new AbortController();

    const handleCalculateIsochrone = async () => {
      try {
        const isochrone = await getIsochrone(
          credentials,
          {
            geom: latLong,
            mode: selectedMode,
            range: selectedRange,
          },
          { abortController }
        );
        updateIsochrone(isochrone);
      } catch (error) {
        if (error.name === 'AbortError') return;

        dispatch(setError(`Isochrone error: ${error.message}`));
      }
    };

    return function cleanup() {
      abortController.abort();
    };
  });

Need to reopen, as I forced reset with develop for the sync

Need to create a different PR with same branch


live_from date not showing for scheduled changes

How are you running Flagsmith

[ ] Self Hosted with Docker
[ ] Self Hosted with Kubernetes
[X] SaaS at flagsmith.com
[ ] Some other way (add details in description below)

Describe the bug
When creating a scheduled change and viewing it from the Scheduling page, the go-live date is never shown.
We do have logic for this already but the banner is not being shown: https://github.com/Flagsmith/flagsmith/blob/8e2db7c24d8c0268fc53e2275778c6a2d86b19e0/frontend/web/components/pages/ChangeRequestPage.js#L403-L418

Steps To Reproduce
Create any scheduled change for the future and open it from the Scheduling page.
Expected behavior
Show the go-live date on both the details page, and on each scheduled change in the list page.
Screenshots
No response

This is resolved in #4852 according to @kyle-ssg


Ticking Entity

Whenever a mob walks on Thaumcraft crystals it causes the following server crash.
This happens on Windows and Linux servers but not in single player even if open to LAN.
http://pastebin.com/bCcDCe3a

Nice to see this is solved already. When will you release the next alpha containing the fix?


HV-1440 Some additional fixes for incontainer mode and JDK 9

@gsmet we can close this one as I've merged #822, right?

Yes.


Fix xDiskAccessPath issue when reattaching volume - Fixes #66

This PR:

Fixes #66
Fixes #67
Fixes #68

These are some PSSA violations still in xDisk and xDiskAccessPath:
- MSFT_xDisk.psm1 (Line 96): File 'MSFT_xDisk.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.
- MSFT_xDisk.psm1 (Line 533): File 'MSFT_xDisk.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.
- MSFT_xDiskAccessPath.psm1 (Line 98): File 'MSFT_xDiskAccessPath.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.
- MSFT_xDiskAccessPath.psm1 (Line 570): File 'MSFT_xDiskAccessPath.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.

The WMI cmdlets should be able to be removed because they are fallback cmdlets if CIM does not work. Removing these may prevent older the resources from working in older OS's though. Unfortunately there were no code comments stating why the WMI cmdlets were included. @kwirkykat , @mbreakey3 - what is the thinking of the DSC Team on this?
This change contains the following fixes:
- Updated readme.md to remove markdown best practice rule violations.
- Updated readme.md to match DSCResources/DscResource.Template/README.md.
- xDiskAccessPath:
  - Fix bug when re-attaching disk after mount point removed or detatched.
  - Additional log entries added for improved diagnostics.
  - Additional integration tests added.
- Converted integration tests to use ```$TestDrive``` as working folder or ```temp``` folder when persistence across tests is required.
- Suppress ```PSUseShouldProcessForStateChangingFunctions``` rule violations in resources.
- Rename ```Test-AccessPath``` function to ```Assert-AccessPathValid```.
- Rename ```Test-DriveLetter``` function to ```Assert-DriveLetterValid```.
- Added ```CommonResourceHelper.psm1``` module (based on PSDscResources).
- Added ```CommonTestsHelper.psm1``` module  (based on PSDscResources).
- Converted all modules to load localization data using ```Get-LocalizedData``` from CommonResourceHelper.
- Converted all exception calls and tests to use functions in ```CommonResourceHelper.psm1``` and ```CommonTestsHelper.psm1``` respectively.
- Fixed examples:
  - Sample_InitializeDataDisk.ps1
  - Sample_InitializeDataDiskWithAccessPath.ps1
  - Sample_xMountImage_DismountISO.ps1

The changes made to xDiskAccessPath could be also ported to xDisk and it would resolve #25 . I'll raise a separate issue to address this.

This change is

Doh! Of course! Thanks @TravisEz13 - fixed.

build failed due to AppVeyor issue.  Triggered rebuild.

Thanks @TravisEz13 - I didn't notice this.

@PlagueHO To answer your question about the PSSA issues, my preference would be to update to CIM cmdlets, but if the WMI cmdlets are really needed, then you can suppress the PSSA rule, and I will move this rule to the 'flagged' category and list this as an exception.

@kwirkykat - TBH, I think the WMI cmdlets are only there to support legacy systems. I think they were added in Windows Server 2012/Windows 8. So dropping the WMI cmdlets will prevent this resource working on Windows Server 2008R2 and Windows 7.
My feeling is that if people do really want to use this resource with these legacy OS's then they can use earlier versions of this module. Going forward I'd much rather drop the WMI cmdlets and just define a minimum requirement in the Readme.md . What do you reckon?

@PlagueHO I agree with this 100% with that last paragraph. Drop the WMI cmdlets and those who aren't upgrading to newer OS's can continue to use the older module versions.


Calculated Policy - AWS EC2 Instance Approved based on Image tags #504

closes #504

Please ignore this comment! Testing slack!


Write the docs

No need for some fancy multi-paged documentation. Just a simple tutorial on:

how to set up,
how to use this package.

Docs maintained in GitHub Wiki.


NATS Streaming support

nats-streaming is getting clustering support and so it's about time to support it.

Has there been any progress on this in the recent months, or anything planned for the foreseeable future? It would definitely be great to see the operator support NATS Streaming.

Hi @JeanMertz yes looking at NATS Streaming support would be next in the list along with prometheus support.

Alpha version of a NATS Streaming Operator built using the Operator SDK is also available here for now: https://github.com/nats-io/nats-streaming-operator
Will look at refactoring current version of NATS Operator so that a single operator is responsible of the multiple CRDs as well as that might be more convenient.

As mentioned to @wallyqs privately, I think it's best for everybody if we keep both NATS and NATS-Streaming operators as one. After all, NATS needs to be in place for NATS-Streaming to work. Breaking them apart would mean more operations and more code to maintain.

I'm very interested in keeping the the two together as well.

Are there any updates on this ? We're very keen to use it in our pipeline. Appreciate all the work you guys have been doing 👍

@sirajmansour I'll resume on this next week, can also try the nats streaming operator built with operator sdk:  https://github.com/nats-io/nats-streaming-operator

There has been a lot of work on the structure of the code, so we can have one operator to rule them all, instead of maintaining separate repos. I'll be working on this over the coming weeks.

@pires does that mean that the nats-streaming-operator will be deprecated in favor of this nats-opertor that will support both altogether?

@diogogmt we would continue to support the nats-streaming-operator too since some may like the separation of responsibilities and streaming operator fairly lightweight anyhow.

OK so it seems we are misaligned and I'm stopping any work to support NATS Streaming in this repo.

In the context of user experience, development, and contributions, what are the advantages and disadvantages of one operator for NATS versus having multiple operators?
For longer term planning, how would each approach unfold as we add new components (e.g. JetStream,  Leaf Nodes), or deprecate parts of NATS?

From the top of my head here's my pov on having two operators.
Pros

Existing users of the nats-streaming-operator use the operator as is today.

Cons

There are two codebases to maintain, including two different, non-integrated APIs.
Their design is different, and quality is as well. For instance, nats-streaming-operator has some basic e2e tests when compared to nats-operator, which provides a more complete e2e test suite, covering functionality that is only available based on feature-gates.

OK from the pov of maintenance:

The streaming operator is fairly straightforward as it is right now, with main controller logic is around 700 loc, technically does not block already from being able to import it and have it be embedded into this operator as a goroutine for example to have two controllers running if needed.

nats-operator tests take 30 min to run so using separate repos could decouple the testing and improve in separate for the nats streaming operator to only test the stateful aspects required for nats
streaming might be good too.

The NATS Streaming Server also supports embedded mode which requires configuring the NATS transport itself that the nats-operator could be well suited for.  Besides logistics around maintenance, I think  this could be were nats-operator support could come in handy, since
the other alternative is for streaming nodes to be able to set soft affinity to nats nodes.

For longer term planning, I think newer features related to NATS transport would be a good addition for the nats-operator.

I think we should fold the NATS streaming operator functionality into this operator. test will run longer, but one stop shopping for users would be good imo.  Flags could enable which components are installed - would it be feasible to have a streaming.enabled flag, disabled by default, to determine if streaming features are installed?

@ColinSullivan1 I don't think we even need flags. Just a different API resource (maybe the one from the other operator impl) or changes to NatsCluster resource, and adapt the operator to understand those.


Error: Cannot find module 'chalk' when using graphql-shield in production

My Node.js app runs perfectly fine in development mode.
On running the app in production (by setting NODE_ENV to production or using npm install --production), it throws the following error:
Error: Cannot find module 'chalk'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/example/app/node_modules/graphql-shield/dist/src/index.js:56:15)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/example/app/src/graphql/index.js:1:82)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)

If I do just npm install on my production server without the --production flag, all works well but I suppose that's not a solution since I don't want to take up space installing devDependencies on my production server.

It seems chalk should be listed in a peer dependency in this library.
Workaround until that is done is to install chalk as a dependency in your own project.

This is also done in the 2.x branch.

Thank you all so much for fixing this!

Thanks for building this! 👍 : )


Better text replacement

Description
Adds in the ability to replace a sentence with multiple of the same word. Also will throw if you attempt to replace text in a node that does not have the text.

@ShaunOssa yeah I think in the future of this we probably want the option to replace at an index or replace multiple. Not sure quite how that would work though haha.

@ShaunOssa also this does not replace multiple it actually allows for multiple instances of the same word in a sentence not to clobber then end of the sentence from the split. For example:
With this text node: "112 co-sponsors of Medicare for All were on the ballot. All of them won."
if I did a replace of All it would replace the text with.
"112 co-sponsors of Medicare for  were on the ballot."
Because the second All would split but the rest of the content after that would not be retained.


fix: write file to be sync

options.cache
while writeFfile is not sync,  cache.json will be messy.

Can you share more context? I think we are awaiting them, it shouldn't affect much

Can you share more context? I think we are awaiting them, it shouldn't affect much

if i dont use async write cache file

or write a new function, only write file sync on cache

Can you share more context? I think we are awaiting them, it shouldn't affect much

or write a new function, only sync write file on cache

i have an another idea, beat performance!


[STORM-1206] Reduce logviewer memory usage through directory stream

Using DirectoryStream to replace File.listFiles will save logviewer memory usage since it does not require loading all files' metadata into memory. This avoids potential memory usage problem in extreme case (e.g., you have millions of small files in your log directory).
Also, a multi-phase PQ-based sorting and cleaning scheme is introduced in DirectoryCleaner for replacing the global in-memory sorting.

These changes look rather large, but the tests pass and the code looks good.  I assume you have done some manual testing so I am +1.


linearization: properly check out the temp branch

First of all, I'm a moron. local_project.create_branch only creates the
branch, and does not check it out. We now have a test case to verify
this - that we end up in the same branch after the SRPM creation when
linearization is triggered.
The second change is that we explicitly check out the former branch
instead of naively doing git checkout -.

@csomh the code indeed looks cleaner now, that was a great suggestion to do branch operations in a single method; please re-review


Hiding splash screen after being inactive or put on backround

I have very simple react-native application - all it does is to hide splash screen in render method and then shows Rendering component text.
My app:
import React from 'react'
import {View, AppState, Text} from 'react-native'
import SplashScreen from 'rn-splash-screen'

class App extends React.Component {

  constructor(props) {
    super(props)
  }

  hideSplash() {
    SplashScreen.hide()
  }

  render() {
    this.hideSplash()

    return (
      <Text>Rendering component</Text>
    )
  }
}

module.exports = App

Right after install, everything works:

I install and start the app - splash screen appears.
Splash screen disappears and I see white screen with Rendering component text on it.

Then I put the app to the background and open it again via icon on home screen:

Splash screen appears and stays there. It hasRendering component text on top of it.

I think that splash screen should disappear.
Then I lock the device via power button and unlock it again (while the app is open):

Splash screen appears and stays there. It hasRendering component text on top of it.

I think that splash screen should disappear too in this case too.
I am using Samsung S5.

I did another experiment, since splash screen hiding does not belong to the render method anyway. This time, I call hideSplash method in componentWillMount and also in AppState event listener. The method counts how many times it was called during component life:
class App extends React.Component {

  constructor(props) {
    super(props)
    this.state = {splashHidden: false, splashHiddenTimes: 0}
  }

  hideSplash() {
    this.setState({splashHidden: true, splashHiddenTimes: (this.state.splashHiddenTimes || 0) + 1})
    SplashScreen.hide()
  }

  componentWillMount() {
    this.hideSplash()

    AppState.addEventListener('change', (currentAppState) => {
      if (currentAppState === 'active') {
        this.hideSplash()
        this.setState({currentAppState})
      }
    })
  }

  render() {
      return (
        <Text>{this.state.currentAppState} at {this.state.splashHidden ? 'it is hidden' : 'nope'} times {`${this.state.splashHiddenTimes}`}</Text>
      )
  }
}

module.exports = App

Right after install, everything works:

I install and start the app - splash screen appears.
Splash screen disappears and I see white screen with at it is hidden times 0 text on it.

Then I put the app to the background and open it again via icon on home screen:

Splash screen appears and stays there. It hasat it is hidden times 0 text on top of it.

Lock the device again via power button and unlock it again a couple of times:

Splash screen appears and stays there. It hasactive at it is hidden times 2 text on top of it.
Splash screen appears and stays there. It hasactive at it is hidden times 3 text on top of it.
Splash screen appears and stays there. It hasactive at it is hidden times 4 text on top of it.
etc

I think that splash screen should disappear. The hideSplash method is being called after each unlock, because the number is raising.
Is there something else I can do to make the splash disappear?

Is this same issue? https://github.com/mehcode/rn-splash-screen/issues/26

Probably not, we are using react-native 0.31.0 and his problem started with 0.34.0.

This was fixed as well in v4.0.0


[Service] common log util

Use common log util in model-dbus impl.

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #282. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/282-202304031246440.41638088226318-6eb73363f0ad67d15012011082922c428d4dfc81/.


"flutter build apk" doesn't run implicitly pub get

If the first thing you do in a flutter project directory is "flutter build", you get all kinds of weird messages because we don't imply a "pub get" for you like we do for "flutter run".

cc @HansMuller

Yes, we should fix this!. @Hixie why the gradle label?

Sorry, overzealous labeling there!

Moving out of bucket5 since there is no committed assignee; please don't hesitate to move these to a specific milestone if there is someone who is committed to working on it by that milestone.

I think this is fixed already: I tried creating a new flutter project (flutter create hello), and running flutter build apk from there had no errors.  Similarly, if I delete that project and creat a new project, and even if the first thing I do is edit the pubspec.yaml, it produces the following output:
(home/gspencer:master) -- hello > vi pubspec.yaml
# add a dependency
(home/gspencer:master) -- hello > flutter build apk
Running "flutter packages get" in hello...                   0.7s
Initializing gradle...                                       0.9s
Resolving dependencies...                                    1.0s
Running 'gradlew assembleRelease'...                        25.4s
Built build/app/outputs/apk/release/app-release.apk (7.3MB).

Please reopen with your repro if you disagree.


Restore tests lost in commit 03e65a.

Some of the newer tests in test_scale got lost in the reconciliation of the
tests.

Restored lost test_scale.lua tests
Ensured that tests still run (with a warning) if graphicsmagick is missing.

@albanD could you please check whether any other tests were introduced after your last sync?

@jagapiou thanks a lot for the test_scale. I am really sorry (I though this would have been caught in the rebase). I double checked, no other test got forgotten.

No problem, @albanD. Thanks.

@jagapiou don't you think your version of assertTensorEq  should be used by all tests that call tester:assertTensorEq  ?

:+1: for soft requirement on graphicsmagick (test.CompareLoadAndDecompress())

@albanD actually, I've pushed it down to just be assertByteTensorEq and to use tester:assertTensorEq() after conversion to double. Less reinvention that way.

@jagapiou looks good to me.


Add FooterComponent prop

Hello, first thank you for this library is amazing.
Can you create a prop like HeaderComponent but to the footer?
In the footer for example I can add a text for the image.
Thank you so much,
Greetings

Hi, thank you for using my library.
I think I will try to add it at the end of this week

Hi, just came out version 1.1.3. in which I added "OverlayComponent" props. OverlayComponent is no different from HeaderComponent but the name itself illustrates more what you can put in it. I also added an example with a footer so that it might make it easier for you to implement.
In the next releases I will probably also add "goNext" and "goPrev" methods which will allow, for example, to create physical buttons to move between photos
I didn't decide to create a typical FooterComponent, because from the beginning the idea was to make the library focus mainly on the photo interaction part, and leave the visual part, such as headers and footers, to developers who will use this library.
If you have any more questions go ahead ;)


[Sema] Don't warn on trailing closures in closure conditions

Add ClosureExpr to the list of expressions we don't walk into for the purposes of diagnosing trailing closures in conditional initializers.
rdar://92521618

@swift-ci please test


remove collect tones from recognize complete

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


xhrStripeTokenToMyServer is not defined

It just be me but I keep getting this error when using the example code.

I'm having the same issue.

@noabyuna That function is just an example. It means 'sending ajax (xhr) request to my server' it can be your $.ajax code. That's a sample handling once you get a token.

Ah i see.. Thanks for the reply :)

This can be closed


add alerts to kube-burner dash

Description
add alerts to kube-burner dash

/rerun all

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_kubeburner
Pass
0
00:22:23


mc_mros_reasoner package release

(from https://github.com/MROS-RobMoSys-ITP/metacontroller/issues/4)
metacontroller depends on owlready2 python package

[x] we need to contribute the rule to rosdep:
https://github.com/ros/rosdistro/blob/master/CONTRIBUTING.md
http://docs.ros.org/independent/api/rosdep/html/contributing_rules.html

Note: since owlready2 is not available through the Debian/Ubuntu apt repositories, you'll have to contribute a pip rule (ie: pip-owlready2).
This will immediately mean you cannot release mc_mros_reasoner through the ROS buildfarm (as that only supports apt dependencies), but I guess that's not really an issue here.

I've created the PR to contribute the python3-owlready2-pip rule  https://github.com/ros/rosdistro/pull/27418

Edit: and actually, if you're still using catkin_virtualenv, I believe adding the dependency to rosdep is not necessary. pip (via catkin_virtualenv) will take care of this.

We're using both, catkin_virtualenv is used for melodic, but for foxy we don't need that anymore.

We're using both, catkin_virtualenv is used for melodic, but for foxy we don't need that anymore.

could still be nice to avoid polluting people's machines, but that may be not too important.

could still be nice to avoid polluting people's machines, but that may be not too important.

In any case, I guess the rosdep rule is still useful.
I'm closing this as the contribution has been merged already https://github.com/ros/rosdistro/pull/27418#event-4029472094


Allow to reuse the same cluster

This is particularly useful for local iteration, so there is no need to re-pull images all the times
Still wip, teardown of deps ain't that easy as expected
Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>

I really dont think this is very useful. Maybe we should change the e2e-tests script to be e2e-setup which setups the cluster with the pre-reqs instead so you can have a cluster setup with the dependencies? The you can run the e2e tests only or drop the clsuter or manually install the rancheros-operator instead? Kind of setting up a vm with ann the needed stuff then running the tests on that vm or letting the user interact with it?

I really dont think this is very useful.

I do need a way to store the images locally, trashing the cluster each time is not optimal at all for local development, just sharing my setup here

Maybe we should change the e2e-tests script to be e2e-setup which setups the cluster with the pre-reqs instead so you can have a cluster setup with the dependencies? The you can run the e2e tests only or drop the clsuter or manually install the rancheros-operator instead? Kind of setting up a vm with ann the needed stuff then running the tests on that vm or letting the user interact with it?

good point, maybe I can make it the other way around and make the setup optional instead of the teardown

I do need a way to store the images locally, trashing the cluster each time is not optimal at all for local development, just sharing my setup here

mmmh, I didnt think of that, maybe my internet speed is too fast to notice LOL
Isnt some kind of local proxy registry that we can reuse for local deployment so it picks the images from there instead of grabbing them from the internet?

I do need a way to store the images locally, trashing the cluster each time is not optimal at all for local development, just sharing my setup here

mmmh, I didnt think of that, maybe my internet speed is too fast to notice LOL

You wouldn't notice now that we aren't touching much and using tests, but if you need to run them sequentially it eventually becomes cumbersome

Isnt some kind of local proxy registry that we can reuse for local deployment so it picks the images from there instead of grabbing them from the internet?

kind actually supports to side load image from the host, but that way we have to pull all images from the docker daemon beforeahead and it is too much convoluted imho
anyhow.. need to implement some proper cleanup logic that takes care of the tests resources that gets created during the timeframe so you wouldn't get into false positive by rerunning the test suite twice, will have a look at it later

can confirm that the proxy methods works and its kind of cool. Seems something that we could implement for local development as its simple enough!


Missing info regarding moving log analytics workspace

Wondering whether a log analytics workspace can be moved from one resource group to another.  Thanks.

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

ID: 23df5354-6833-a5da-0eb3-d860150c8b78
Version Independent ID: 682ec206-0fda-3e0b-5841-543860a87e34
Content: Move operation support by resource type - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/move-support-resources.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

Hello @pamstat ,
Yes, Log Analytics workspaces can be moved across resource groups - ref here
This is also included in the above doc under "next step" section.

Hope this helps.
Cheers.


There is a memory leak defect at line 312 in the file openssl/test/v3ext.c.

At line 233 in the file openssl/test/v3ext.c, a pointer named f1 is defined. This pointer allocates a dynamic memory region at line 262 through the function IPAddressFamily_new. When the if statement at line 262 returns false, it indicates successful allocation of dynamic memory for f1. Subsequently, at line 265, the program allocates a dynamic memory region for the ipAddressChoice member of pointer f1 through the function IPAddressChoice_new. If the if statement at line 265 returns true, the program will jump to the end label at line 308 from line 266, thereby bypassing the IPAddressFamily_free(f1) operation at line 281. The end label does not release the dynamic memory region pointed to by f1, thus constituting a memory leak defect. The diagram below illustrates the detailed path of the defect:https://github.com/LuMingYinDetect/openssl_defects/blob/main/openssl_2.png

Note: there are two proposed fixes to this, #23906 which seemingly has a potential for double-free, and #23991 which appears quite complicated for what it's trying to do.


Fix parameter passed to list clients endpoint

This fixes the behavior observed in the test.
This now uses the correct parameter, as seen in ClientsResouce:
    public Stream<ClientRepresentation> getClients(@QueryParam("clientId") String clientId,
                                                 @QueryParam("viewableOnly") @DefaultValue("false") boolean viewableOnly,
                                                 @QueryParam("search") @DefaultValue("false") boolean search,
                                                 @QueryParam("q") String searchQuery,
                                                 @QueryParam("first") Integer firstResult,
                                                 @QueryParam("max") Integer maxResults) {

Closes #51

Hi @kami619 - this should fix the problem with the increasing list() times.
Could you please review it an comment/approve here once you have the time? Thanks!

@pedroigor - as @kami619 has reviewed it, could you please merge it? Thanks!

the changes works as expected on my local. the response times are now constant aligning to the max parameter value specified in the test for listing the clients


Corrects variable name in use

Corrects neutron_venv_bin to use the correct neutron variable. This
has no change in functionality and is instead used to match previous
variable convention and use correct variable name.
Backport pull requests already include this change.
Connects rcbops/u-suk-dev#857

Looks like there's a merge conflict now, @dankolbrs.

Got it fixed up @major


NuGet package Microsoft.TypeScript.MSBuild is incompatible with .NET Framework 4.0

TypeScript Version:  1.8.11
Trying to build a .NET 4.0 project that references Microsoft.TypeScript.MSBuild 1.8.11 on a computer that only has .NET Framework 4.0 (not .NET Framework 4.5) fails.
Expected behavior:
Package should indicate a dependency on .NET 4.5 because an included .targets file makes use of the KeepDuplicates attribute (which was only introduced in .NET Framework 4.5)
Actual behavior:
Error:
packages\Microsoft.TypeScript.MSBuild.1.8.11\tools\Microsoft.TypeScript.targets (159,44): error MSB4066: The attribute "KeepDuplicates" in element <ConfigFiles> is unrecognized.

Duplicate of https://github.com/Microsoft/TypeScript/issues/12739