Some symbols are not exported

Some symbols are not exported
After build it and check symbols inside, something is wrong because symbols is not there. Example:
nm -C build/ios/release/libpdfium.a | grep FPDF_CloseDocument

Output:
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols

But with an old but working version i got:
                 U _FPDF_CloseDocument
0000000000000e69 T _FPDF_CloseDocument
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols
no symbols

Can anyone help me?

It looks like you're just not linking everything that's required, e.g. you're leaving out everything in out/core. Really you're only linking third_party/pdfium_core (which seems to be some helpers) and third_party/skia_shared right now, along with the 4 .a files present (third_party/icu/libicuuc.a, third_party/libjpeg_turbo/libjpeg.a, third_party/libjpeg_turbo/libsimd.a, third_party/zlib/libchrome_zlib.a).

Yes, I already fixed it. It is working on device now.
The only problem now is on simulator. After load pdf document it crash, but on device works.
Can you help me with it?

Why has this been close ? @paulo-coutinho

It has now everything.
Before current version i made the link process manually, but now im calling default pdfium tools that generate final file with all linked.
We are using on mobile, desktop and wasm.
You have any problem with current version?

Hi @paulo-coutinho, Yes the fat static library is missing symbols
https://github.com/dart-lang/sdk/issues/44328

the fat library used is the one from this build https://github.com/paulo-coutinho/pdfium-lib/actions/runs/845371947

So, i will reopen this to understand better.

Thanks, please let me know if i can be of any help

Hi,
I have download your reference libraries compilation on github action and used in my simple sample here. It compile and work without problems on iOS:

Could you show how you added the library to your sample ?
because adding it to iOS project using the following configuration does not compile
s.vendored_libraries = 'Frameworks/libpdfium.a'  s.pod_target_xcconfig = { "OTHER_LDFLAGS" => "-force_load $(PODS_TARGET_SRCROOT)/Frameworks/libpdfium.a" }
Also could you try the binary from this project
https://github.com/bitsydarel/dart_ffi_static_link_issue/tree/main/pdfium

Hi,
You see here here:
https://www.dropbox.com/s/3b1sbqcl7kp9svs/pdfiumtest.zip?dl=1

It's seems like this project was not created with latest tools and i think the issue is because you have bundle or noted in the docs that the iOS app need additional libraries expect the pdfium one.
Also there's no podfile in the project you provided.
Here are the additional libraries you're building the project with

Could you try to add the library to a new project with the latest xcode tool ?

Hi,
I put a sample here.
https://github.com/paulo-coutinho/pdfium-test
This is the most basic example with xcode that i can make.

Hi @bitsydarel,
It was solved?

@paulo-coutinho  not really, every new project created on xcode static library fail to build.

That sample is a new project. Is something related on your machine.

The other devs on my team also have the same issue, but we will check and get back to you asap.

Also the tester on Google dart team have the same issue as you can see on the issue comments dart-lang/sdk#44328

Hi
Can you send me a sample?
Em qua., 9 de jun. de 2021 às 06:30, Darel Bitsy @.***>
escreveu:

Also the tester on Google dart team have the same issue as you can see on
the issue comments dart-lang/sdk#44328
https://github.com/dart-lang/sdk/issues/44328
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/paulo-coutinho/pdfium-lib/issues/4#issuecomment-857540989,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADAOWA3PSYSSULTUVTPKVDTR4YBVANCNFSM4JOOUGPQ
.

--
Atenciosamente,
Paulo Coutinho.
PRS - Soluções Inteligentes
Site: www.prsolucoes.com
Blog: www.pcoutinho.com
Skype: paulo.prsolucoes
Telefone: +55 21 99386-0010

This is a valid sample, the libraries are under the pdfium
https://github.com/bitsydarel/dart_ffi_static_link_issue/
If you have no knowledge of flutter it's fine, just open using xcode the ios folder in the example folder.

This is simple. Add on "OTHER_LDFLAGS" the link to "c++" as i showed before in xcode sample.
File: dart_ffii_static_link_issue.podspec
s.pod_target_xcconfig = { "OTHER_LDFLAGS" => "-force_load $(PODS_TARGET_SRCROOT)/Frameworks/libpdfium.a -lc++" }

Hi @bitsydarel,
Any update about this problem?
Thanks.

There is other files/lines with:
"-fvisibility=hidden",

And:
"-fvisibility-inlines-hidden",

Maybe you will need remove these too.
If works, i can make a patch to solve this.

Here have a solution that work with Dart/Flutter:
https://github.com/paulo-coutinho/pdfium-lib/issues/41

The solution is in other issue (https://github.com/paulo-coutinho/pdfium-lib/issues/41). Thanks.


兼容zone及usable参数

这个 PR 实现什么功能/修复什么问题:
兼容zone及usable参数
是否需要 backport 到之前的 release 分支:

release/2.11.0
release/2.10.0
release/2.9.0
release/2.8.0

/area region
/cc @swordqiu @yousong @tb365

Codecov Report

Merging #1622 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1622      +/-   ##
=========================================
- Coverage    7.67%   7.67%   -0.01%
=========================================
  Files         411     411
  Lines       63033   63043      +10
=========================================
  Hits         4839    4839
- Misses      57785   57795      +10
  Partials      409     409

Flag
Coverage Δ

#aFlag
7.67% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/networks.go
0.92% <0%> (-0.01%)
:arrow_down:

pkg/compute/guestdrivers/managedvirtual.go
0% <0%> (ø)
:arrow_up:

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 0f0a090...52bd952. Read the comment docs.

/lgtm
/approve

/lgtm
/approve


"Class"-ify weatherflow2mqtt

This is my initial attempt to help convert the main running program to an easier to manage class structure to ease future support.

Removes the option ADD_FORECAST and relies on data populated in both STATION_ID and STATION_TOKEN instead, since ADD_FORECAST, by itself, doesn't do anything.
Automatically determines ELEVATION and UNIT_SYSTEM in HA Supervisor installs

Removes UNIT_SYSTEM from config in supervisor

Also, I'd be interested in helping to maintain https://github.com/briis/pysmartweatherudp and https://github.com/briis/smartweatherudp

Perfect Nathan. I am actually in the process of doing that with three other Integrations I have, so if you can do this one, I would be happy.
Yes as you can see the UDP versions of the integration have not been touched for a while, my biggest issue was the pysmartweatherudp module. Even though it works, it really needs to be rewritten from scratch. I will put you on both these projects so you can merge PR's yourself.

You are now invited to both the above repositories.
Is this ready to merge?

And I added you to this repository also

Yes as you can see the UDP versions of the integration have not been touched for a while, my biggest issue was the pysmartweatherudp module. Even though it works, it really needs to be rewritten from scratch. I will put you on both these projects so you can merge PR's yourself.

Awesome, my hope with pysmartweatherudp is to get it so that this project can also utilize the same module for reading the UDP data, and then adding the additional smarts on top of it.

Is this ready to merge?

I've been running it on my box and haven't run into any issues. But it might be helpful to just peruse it first and make sure it looks kosher!

OK, I will merge now, and then test it tomorrow before I do the builds.
Would be great if there could be a shared UDP module - why didn't I think of that :)
I have just rewritten the smartweather integration using the pysmartweatherio. I decided I wanted to do so many changes, that I started from scratch and renamed it to the domain weatherflow. You can look at what I did there in these two repositories: pyweatherflowrest and weatherflow

We might actually be able to use pyweatherflowrest to pull the Weather data in to this, so this code can then be removed.

We might actually be able to use pyweatherflowrest to pull the Weather data in to this, so this code can then be removed.

My thoughts as well!

It looks like you may have previously started work on a separate package for the udp (https://pypi.org/project/pyweatherflowudp), but it doesn't look like that repository exists anymore. Did you cancel that initial endeavor?

No, I made it private. But it is very early stages, and I gave up on it again. But we can use this repository, to make a new, that will then stay within the same naming. I reset it to Public. https://github.com/briis/pyweatherflowudp and added you to it.
Feel free to delete and overwrite all that is in there

No, I made it private. But it is very early stages, and I gave up on it again. But we can use this repository, to make a new, that will then stay within the same naming. I reset it to Public. https://github.com/briis/pyweatherflowudp and added you to it. Feel free to delete and overwrite all that is in there

Sounds good!

Just another though, as your are making changes anyway:

We should remove all the historic attributes, as these are now covered by Home Assistant using the state_class parameter. So statistic information is accumulated here, and we don't need to do it in the database. That means the only thing we will still need the database for, are the values that are not persistent upon restart - like rain today, lightning today etc.


Prepend custom toolbar items before built-in editor toolbar items

thanks for a great project...
From the examples it seems that any custom toolbar items are appended after the editor toolbar items... is it possible to prepend?

@TheMashupApp I will have a look into this.


rocm-smi reporting a non-existant GPU 0?

On my system with ROCm 1.9, I see the following output from rocm-smi:
====================    ROCm System Management Interface    ====================
================================================================================
 GPU  Temp    AvgPwr   SCLK     MCLK     Fan      Perf    SCLK OD    MCLK OD
  0   N/A     N/A      N/A      N/A      0%       N/A       N/A        N/A
  1   55c     15.0W    852Mhz   167Mhz   10.98%   auto      0%         0%
================================================================================
====================           End of ROCm SMI Log          ====================

Is the non-existent GPU 0 an artifact of the CPU being enumerated as an HSA agent?  Might be less confusing to filter it out of rocm-smi output.

rocm-smi walks through all of the GPUs in the system shown in, for example, /sys/class/drm/#/. The DRM system can include non-AMD GPUs. For example, d you have an integrated GPU in your laptop or server motherboard?

Thanks @jlgreathouse , that's exactly what we do. I have been working forever on trying to only report GPUs that actually matter and have topology loaded, but it hasn't been done yet. For now, we just go through /sys/class/drm/cardX , and X is the GPU that we use. So in your case, it would be an integrated graphics card, or some other non-AMD display device, I would assume.

Fixed in 2.2


Backup and DR using Veeam and Zerto

Hi Team,
Do we have any option to enable Backup using Veeam and DR using Zerto? This is the feature request. Thanks in advance.

@thulasi39 you can use Veeman as documented here: https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_veeam or Zerto as documented here: https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_zerto-portal
Does that address your question, if not can you describe what you would like to see.

Hi @dprosper - Thanks for the link. But this can be included in the Terraform as part of the VM Provision?


Add contributors section to the README.md file.

There is no Contributors section in readme file .
As we know Contributions are what make the open-source community such an amazing place to learn, inspire, and create.
The Contributors section in a README.md file is important as it acknowledges and gives credit to those who have contributed to a project, fosters community and collaboration, adds transparency and accountability, and helps document the project's history for current and future maintainers. It also serves as a form of recognition, motivating contributors to continue their efforts.

@staoxiao  kindly assign me this #218 this issue, i want to work on it. Thank You!!

Good advice! Feel free to pull a request.


star-slash

Describe the requested icon
An outlined star with a slash. Sometimes you use star icons to indicate actions such as adding something to your favorites. In that case it would be nice to have a star-slash to remove an item from your favorites.
Screenshots

We'll think about it. Is it possible for you to use filled and outlined variants for favorite / not? That seems to be a much more common pattern.


docs: add placeholder query to playground

To address #757.
Tested locally and worked fine.
Placeholder query is currently btcPriceList since it doesn't require authentication. This query also uses a variable, which may be useful for people to see. But let me know if you would prefer a different query.

tests are not passing @moksha256 . you'll need to run prettier. yarn prettier-write should do it.

yarn prettier-write should do it.

Thanks, all checks now passed.

Let's put the query text in a variable using a template string (using backticks and dropping the \n).  Define it in src/graphql/playground.ts and import it in graphql-server.ts

@samerbuna @vindard thanks for the feedback. I added a tab name and defined all 3 query-related strings in src/graphql/playground.ts since it seemed like they should be together.

Not sure if anyone else has feedback for vindard's changes so I just committed them and tested...looks good from my end.

Let's put the query text in a variable using a template string (using backticks and dropping the \n).

@samerbuna how would you drop the \n from the query string here?


Add PushNotificationsLongRunningTask.ProxyStub pdb to symbols dir

The PushNotificationsLongRunningTask.ProxyStub.pdb was not being sent to the symbols folder in the pipeline. This PR addresses the issue.

/azp run

Seems like this is something good, but please explain in the description what is the problem being addressed here.

Seems like this is something good, but please explain in the description what is the problem being addressed here.

Sorry. I was testing pipeline to make sure the change was correct 😄 . Will update description.

/azp run

The foundation pipeline run is blocking this from merging. Unrelated to change but cannot move to main because of it


Please verify that the package.json has a valid "main" entry

Describe the bug
When I'm trying to use it on some project React+Webpack+TypeScript, I'm getting an error:
Error: Cannot find module<EMAIL_ADDRESS>Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:303:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:516:18)

Input code
webpack config:
{
        test:/\.(js|jsx|ts|tsx)$/,
        loader: 'swc-loader',
        exclude: /node_modules/
},

Config
{
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": true,
      "decorators": true
    }
  }
}

Expected behavior
no error happens
Version
The version of @swc/core: v1.2.52 (master branch)

ah, sorry for that. seems I installed sources from master but not the builded package


Support discovery with other tags besides clusterName

Currently we are basing discovery on the kubernetes.io/cluster/{clusterName} tag.
We should probably:

support wildcards in cluster names
support discovery via other tags other than cluster name (clusters can be renamed)

Closed via #8


Crossed entity names on smart meter

Hi!
I noticed the entities "Active energy (forward active energy)" and "Reverse active energy" have their names crossed. I can confirm this by comparing the actual values from the meter display.
HA entity reports the energy value I pulled from the grid as Reverse active energy. Shouldn't this be the amount I returned to grid from PV?

@pretor2113 first of all: thx
I did a quick check and the names are matching the attributes. The names and attributes are coming from the documentation. But to be honest I don’t understand all terminology.
Could you check the ID of your entity?

Both IDs correspond to their names.

as the attributes are matching I don’t think they are crossed in the code. But maybe something is wrong in Huawei Fusion Solar, or in the wiring, or in the terminology?
Would you be willing to contact Fusion Solar, and ask them to explain the terminology, or check if something is wrong at their end?

@pretor2113 any update on this? Or can this issue be closed?

Sorry, no reply yet. As a workaround, I will use the appropriate entity in my automation. I will get back to this when I learn more.


Sort out half-float support

Currently .NET lacks support for half-float, so we do not surface these data types in the API.
We should figure out if we should at least provide some interop APIs, even if we can not operate directly on the half values.

The CoreFX API proposal for adding a Half interchange type is here: https://github.com/dotnet/corefx/issues/25702
It has not gone to API review yet, as we determined it may need a dedicated review session.

This is done, for now.  We can move to depend on Merkli.Half or another until the point the Corefx Half becomes available


Upgrade error handling to use new primitives for 1.13

When go 1.13 becomes available, we will need to update our error handling code to make use of the new features such as error wraping. This should make the code considerably easier to debug / inspect.

This is being fixed in touch-ups to most packages. Closing the issue.


fix nip42 handling

Currently, filters for kind 4 events are not allowed for unathenticated clients.  However, when a filter does not specify kind 4, (e.g. just asks for recent events) kind 4 events are still returned.
This defeats the point of nip42 since it reveals message metadata to anyone willing to construct the right filters.
This fix is simple, just copies the same nip42 logic used to forbid certain filters and applies it to every event from every filter.

Still needs testing.  Will reopen when ready.

Added a test and a dummy Storage implementation that makes tests like these easier.

 Good catch, but this is looking very complicated.

The eight line change in handlers.go is all you need, the rest is just to test that it works as expected,


Add sticky navbar functionality

Fixed #232
Checkpoints

Added a sticky navbar.
Ensured that when users switch pages, the page scrolls to the top automatically.
Added test cases for all functionalities.

*Demo
https://github.com/user-attachments/assets/aecf23a7-e1ec-4a2d-9bb9-aace92187da1

@kasya  @arkid15r  can we merge it !


[Bug][Dashboard] The "next" button of the data synchronization module is invalid

What happened
After creating a data synchronization task in the inlong dashboard, do not submit it directly, return and enter again, then the next button will be invalid.
What you expected to happen
I got the err msg in browser console:
4577.97fb8884.chunk.js:1
 Uncaught (in promise) TypeError: n.join is not a function
    at 4577.97fb8884.chunk.js:1:7112
    at d (main.3841acf9.js:2:1653059)
    at Generator._invoke (main.3841acf9.js:2:1652812)
    at Generator.next (main.3841acf9.js:2:1653422)
    at r (main.3841acf9.js:2:1646506)
    at c (main.3841acf9.js:2:1646709)

How to reproduce

Create a data synchronization task

Don't submit, just return

Re-enter the task you just created

Click the Next button, you will find the button is invalid

Environment
No response
InLong version
master
InLong Component
InLong Dashboard
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

It has been solved in this PR https://github.com/apache/inlong/pull/11486


UI Freeze on Cancel

I tried to cancel Image Downloads because the number increased to 12.000 but the UI froze.
After looking at the Code I believe the problem is of more general nature and can happen with all cancel operations inside JMM Server.
Have a look at this method:
void btnImagesClear_Click(object sender, RoutedEventArgs e)
{
try
{
this.Cursor = Cursors.Wait;
JMMService.CmdProcessorImages.Stop();
	// wait until the queue stops
	while (JMMService.CmdProcessorImages.ProcessingCommands)
	{
		Thread.Sleep(200);
	}
	Thread.Sleep(200);

	CommandRequestRepository repCR = new CommandRequestRepository();
	foreach (CommandRequest cr in repCR.GetAllCommandRequestImages())
		repCR.Delete(cr.CommandRequestID);

	JMMService.CmdProcessorImages.Init();
}
catch (Exception ex)
{
	Utils.ShowErrorMessage(ex.Message);
}
this.Cursor = Cursors.Arrow;

}
The problem is within "wait until the queue stops" routine, because it can happen that between the Stop() and the next Iteration of the while Loop the workercommand again gets started from its cancel state.
In my case the JMMService.CmdProcessorImages.NotifyOfNewCommand(); method inside CommandRequestImplementation gets kicked off again, and so the bool ProcessingCommands again gets true.
To fix the problem I think there are 2 solutions:
1.) while loop a boolean that says true to the workercommand that actually got canceled, no matter if a "new" workercommand starts
2.) try to not only cancel the current workercommand but also the routine that is in the middle off notifing new commands
I think the 2nd one is the better one, since with the first one the user would have to hit the cancel button again and again if the software is in the middle of adding commands to the queue.

Another approach could be to redesign the start of JMM Server so that it starts it work AFTER it queued up all commands so that you can cancel them only after they are initialized.

Just love the close and comment button. :)

I would say submit the commit with the change you think would work best. I'm sure lwerndly wouldn't mind as the whole reason JMM was moved to GitHub was to allow others to help out.

agreed, if you have the skills and know-how then just do it, our creator and savior will review it and if its good then its great :P

Good to have people with programmation skill :)

can't agree more, after following this project for years now and have made hundreds of issues on here and the code.google site i do really miss out actually helping out on things, i dont even know where to start TBH XD

Download Visual Studio Express for Desktop (https://go.microsoft.com/fwlink/?LinkId=615464&clcid=0x409) and start messing around with JMM Desktop and JMM Server. I'm on my phone so I don't have the links but Google C# tutorials, WPF tutorials and Visual Studio tutorials. For me the vide tutorials work best as you can follow along.

There are a couple of things I will probably look at.
1 - Change the image queue to an in-memory queue instead of a database queue, it is not important if these commands get lost because it does a reconciliation every time JMM server starts
2 - Instead of iterating through the database and deleting one by one, issue a single sql delete statement.

After my Internet disconnected hasher stopped working and can't cancel the queue.
Are there any suggestions?

restart server?

I have already tried restarting, pausing and resuming each queue and all together and starting another job. Nothing worked.

Is queue full ? or empty ? can you force hash some small folder in the folder list?

There are 1443 items in queue but appears idle.
Could you explain how I can force hash?

in Server, on "import folder" tab, click on "Scan", yellow icon on left of folder name. Make new folder, copy 1-2 files there. add that folder. It should add it to queue automaticly.
Also maybe you have really big file that is taking so long to scan ?

Thank you!
I changed the import folder to a new one with 2 files and the queue went down.
Then I changed back to the old folder and everything seems fine.
The file was ~300MB and hasher was stuck for over 12 hours.

Hopefully we can get the solution @rand-random mentioned implemented.

I've fixed it in a  way that now it waits until the running command is finished and then removes everything. Feel free to reopen if you feel fix is incomplete.


Enhancement/improve-error-messaging-for-role-forbidden

Description

Closes #<issue_number>
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Refactor (change restructuring the codebase without changing functionality)
Improvement (change adding some improvement to an existing functionality)
Documentation update

How Has This Been Tested

Checklist

I added relevant documentation
I followed the style guidelines of this project
I did a self-review of my code
I made corresponding changes to the documentation
I confirm My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

I think this works great. I believe this is specifically for dataset creation but shouldn't we be covering the basic scenario of rg.Argilla(api_url="correct", api_key="wrong") as well?

I've improved that with changes to the message in argilla/src/argilla/_exceptions/_api.py . We also already have a validation message in argilla/src/argilla/_exceptions/_client.py that says:  ""Credentials (api_key and/or api_url) are invalid"".

I think this works great. I believe this is specifically for dataset creation but shouldn't we be covering the basic scenario of rg.Argilla(api_url="correct", api_key="wrong") as well?

I've improved that with changes to the message in argilla/src/argilla/_exceptions/_api.py . We also already have a validation message in argilla/src/argilla/_exceptions/_client.py that says: ""Credentials (api_key and/or api_url) are invalid"".

but perhaps it would be nice if we could also share a similar message, urging the user to go to my-settings with their owner account?


Locale dependent uppercase of schema prevents db from uploading data with turkish locale

OrientDB Version: 2.2.20
Java Version: 1.8.0_112
OS: Macos 10.12.5
Expected behavior
File should be uploaded without an error
Actual behavior
Error occurs
ETL process has problem: java.lang.IllegalArgumentException: No enum constant com.orientechnologies.orient.core.metadata.schema.OType.İNTEGER
Steps to reproduce
According to the tutorial at https://orientdb.com/docs/2.2/Import-the-Database-of-Beers.html

With turkish region set operating system

Download orient db

Extract the compressed file

Execute the command below with appropriate files

oetl.sh categories.json
Work around
add the jvm parameters in oetl.bat to ORIENTDB_SETTINGS variable
 -Duser.language=en -Duser.region=EN
Check for similar bugs and the solutions
http://mattryall.net/blog/2009/02/the-infamous-turkish-locale-bug
https://issues.apache.org/jira/browse/SPARK-20156
https://jira.atlassian.com/browse/CONFSERVER-5931
https://issues.apache.org/jira/browse/AVRO-1493
Thanks to @vezir for reporting the issue

I've patched the code on 2.2.x and develop branches.
If you want to check with a snapshot you can find them at this location:
https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/

Hi Roberto,
I checked case against version orientdb-community-2.2.22-SNAPSHOT and it is OK.
Result :
../bin/oetl.sh categories.json
OrientDB etl v.2.2.22-SNAPSHOT (build f9ac8ea1c90235d6f454484206d2523e07abc300) https://www.orientdb.com
[file] INFO Load from file categories.csv
BEGIN ETL PROCESSOR
[file] INFO Reading from file categories.csv with encoding UTF-8
Started execution with 1 worker threads
[orientdb] INFO committing
END ETL PROCESSOR

extracted 11 rows (0 rows/sec) - 11 rows -> loaded 11 vertices (0 vertices/sec) Total time: 299ms [0 warnings, 0 errors]

Should have look for version 3.0.0 ?

Roberto Franchini<EMAIL_ADDRESS>şunları yazdı (6 Haz 2017 20:24):
I've patched the code on 2.2.x and develop branches.
If you want to check with a snapshot you can find them at this location:
https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/ https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/7464#issuecomment-306557949, or mute the thread https://github.com/notifications/unsubscribe-auth/AFtOSvI8a3R03Fk6q-fzyibGXrH-S8x3ks5sBYtngaJpZM4NrTpt.

Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
www.likyateknoloji.com http://www.likyateknoloji.com/

Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul etmez.
This electronic mail and any files transmitted with it are intended for the private use of  the persons named above. If you received this message in error, forwarding, copying or use of any of the information is strictly prohibited. Please immediately notify the sender and delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. does not accept legal responsibility for the contents of this message.
P
Bu e-postayı yazdırmadan önce, çevreye olan sorumluluğunuzu tekrar düşünün.
Please consider your environmental responsibility before printing this e-mail.

I fixed 3.0 before, should be ok.
But, for sure, if you want/need/have time, check 3.0.0 too.


SearchInRotatedSortedArray Invalid Solution

Doen's work for below Input:
[1,1,3,1]
3
Expected: 2
Actual: -1

i think you have not realize the premise：
“an array sorted in ascending order”.

It is said in the first line of the code that, yoy may assume no duplicates occur in the array. So i guess the code does not work for duplicates.

your arr should be : [1, 1, 1, 3],   while you search "1", it may not the right position what you want.

You are right, no duplicates are allowed :)


Update azure-pipelines-task-lib to latest

Please update the azure-pipelines-task-lib to i think 4.10.0 as this resolves a lot of security issues.
That would at least fix mockery which is like 7 years old ;p work in a big company and alert bells go off etc ;)

Inside:

I think if you change this to something like ^2.0.0 then we are all good again, thats the source from what i can tell that calls the old one.

@jason-johnson any update on this? Happy to do a PR but is there anything else holding this back?

A PR would certainly speed up the process. I just need to make sure the PR doesn’t break anything. I’m in the process of moving more of the pipeline to GitHub so you get immediate feedback on errors.

Fixed by #459


(RE-5032) fully qualify the label in the osx mco plist

This commit fully qualifies the label in the osx mco plist using the
identifier plus service name.

CLA signed by all contributors.

puppet-agent currently ships with 2.8.2, should this be backported to 2.8.x or stable (I'm not sure if/how those are different)?

@joshcooper until your comment nobody had expressed the need for any form of timely release with this change incorporated and we currently have no releases planned.
What time pressure do we have to get this released?

@richardc we're planning on releasing OSX in PE real soon now, and if there are simple things we can do to improve the OSX experience that'd be great. But at the same time, it's not worth a new mcollective release just for this one thing. So I'd say if we are planning an mco release to coincide with the next PE .z release that'd be great, but otherwise let's wait.
Btw, we made a similar change in to puppet in https://github.com/puppetlabs/puppet/pull/4095


Handle hard failures (eg. kernel panic) during bootstrap

This change configures cloud-init to run the bootstrap script on every boot so that we can check for previous failed attempts and mark the instance as unhealthy.
This caters for the scenario where the kernel panics during a bootstrap attempt which leaves the instance non-operational on reboot but marked healthy.

Having said that, kernel panics causing the startup scripts to fail is not something we encounter regularly, so we haven't seen the need to make these scripts resilient to them. Do you have any insight into why they may be happening?

The issue that led to this is that we were seeing relatively frequent occurences of the kernel watchdog detecting soft lockups during installation of gcloud as part of our bootstrap. I'm unsure what the true underlying cause is.
We don't currently run with instance storage enabled, but my understanding is that the boothooks will run on every boot so you're probably correct that at least some portion of them should also be skipped if they have previously completed successfully.


Question about target speaker reproduction/transfer

About how long into training did the voice conversion effect start to be noticeable for you?
I ask because so far in my experiments training from scratch, audio reproduction for the source speaker seems to be pretty good, but passing a different speaker as the conversion target doesn't change the voice much. It did work better when I fine-tuned your pretrained model on my dataset, so I'm wondering how long I should let new experiments run before I deem them failures.

it depends. for vctk 300k steps are enough.

Gotcha—thanks for the response!

@space-pope hi, I wonder how big your new dataset is, how many epoch or iters (and the batch_size is?) have you fintuned till get good results?


For some custom fields if the value was made blank in JIRA then it shows the previous revision in ADO

Describe the problem
For a few custom fields when migrating in ADO its showing the prev value before it was made blank. Also in export logs I can see an null reference exception for some fields.
for eg, for below field this happens
{
"source": "Resolution Version(s)",
"source-type": "name",
"target": "Custom.tFResolutionVersion",
"mapper": "MapTags",
"for":"User Story,Bug"
},
Tool version

3.0.266

Attachments
Please attach the following files:
jira-export-log-231206-160727.txt
wi-import-log-231206-164312.txt
config-agile.json
Screenshots
If applicable, add screenshots to help explain your problem.

Wondering if this is maybe related to the MapTags mapper. I will try to replicate the scenario where the tags are unset.
What type is the field "Resolution Version(s)"? Is it a built-in or custom field?

@Alexander-Hjelm it may be taking None as a value, when I check the history I get it like below -

"Resolution Version(s)" is a custom field we are using.
MapTags I am using as we run some custom code on that field and we want that to be delimited by some proper character that can be checked, initially it was coming space separated, so by MapTags it made it semicolon separated

@shweta22992 Why not just use MapArray instead?

I was initially using MapArray but that was giving space delimited which we think may not be a robust option to go with for processing later.
Also I tried removing the MapTags mapper and still it was giving me the issue.

That shouldn't be possible. The MapArray mapper will take the value, split by comma and delimit the result by semicolon. You can refer to the source code here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/src/WorkItemMigrator/JiraExport/RevisionUtils/FieldMapperUtils.cs#L149

@Alexander-Hjelm I will take a look at this and again try to change, but if you can suggest something for the data issue after getting blank, as that is the more problematic thing for us currently

@Alexander-Hjelm I have raised a PR for this
https://github.com/shweta22992/fix-nulldatanotmapped/pull/1
do let me know if this looks fine or any suggestions you have

@shweta22992 Ah! That could indeed be an issue. My bad. Thanks for sniffing this one out.
I think a safer way would be to store (value || "") in an interim variable, so that we don't accidentally edit something outside of the current block.
I will create a fix for this asap.

@shweta22992 Nevermind, upon closer inspection I think your PR looks good enough as it is.
It seems like you have raised a PR to the main line of your own fork. I'm not sure if this was on purpose or not?
If you want credit for you fix, please edit the PR so that it merges into the main repo! Let me know otherwise and I'll apply the fix.

@Alexander-Hjelm no that got by mistake I think. was truing to raise to the main repo. I will check where I have to make change for pointing it to main repo

https://github.com/solidify/jira-azuredevops-migrator/pull/940


Could not find method google() for arguments [] on repository container.

Question
Building and installing the app on the device (cd android && ./gradlew installDebug)...
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Repository https://jcenter.bintray.com/ replaced by https://maven.aliyun.com/repository/jcenter.
Incremental java compilation is an incubating feature.
Repository https://repo1.maven.org/maven2/ replaced by https://maven.aliyun.com/repository/jcenter.

FAILURE: Build failed with an exception.

* Where:
Build file<EMAIL_ADDRESS>line: 3

* What went wrong:
A problem occurred evaluating project ':react-native-device-info'.
> Could not find method google() for arguments [] on repository container.

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

BUILD FAILED

Total time: 9.715 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

Environment
Environment:
  OS: macOS 10.14
  Node: 10.6.0
  Yarn: 1.12.1
  npm: 6.4.1
  Watchman: 4.9.0
  Xcode: Xcode 10.1 Build version 10B61
  Android Studio: 3.1 AI-173.4907809

Packages: (wanted => installed)
  react: ^16.0.0 => 16.5.2
  react-native: ^0.50.1 => 0.50.4

react-native-device-info: ^2.3.0

I need help.
How to fix it ?

#Old Version
react-native-device-info: ^0.11.0
Problem
:react-native-device-info:preBuild UP-TO-DATE
:react-native-device-info:preReleaseBuild UP-TO-DATE
:react-native-device-info:checkReleaseManifest
:react-native-device-info:preDebugAndroidTestBuild UP-TO-DATE
:react-native-device-info:preDebugBuild UP-TO-DATE
:react-native-device-info:preDebugUnitTestBuild UP-TO-DATE
:react-native-device-info:preReleaseUnitTestBuild UP-TO-DATE
:react-native-device-info:prepareAndroidxArchCoreCoreRuntime200Library
:react-native-device-info:prepareAndroidxAsynclayoutinflaterAsynclayoutinflater100Library
:react-native-device-info:prepareAndroidxCoordinatorlayoutCoordinatorlayout100Library
:react-native-device-info:prepareAndroidxCoreCore100Library
:react-native-device-info:prepareAndroidxCursoradapterCursoradapter100Library
:react-native-device-info:prepareAndroidxCustomviewCustomview100Library
:react-native-device-info:prepareAndroidxDocumentfileDocumentfile100Library
:react-native-device-info:prepareAndroidxDrawerlayoutDrawerlayout100Library
:react-native-device-info:prepareAndroidxFragmentFragment100Library
:react-native-device-info:prepareAndroidxInterpolatorInterpolator100Library
:react-native-device-info:prepareAndroidxLegacyLegacySupportCoreUi100Library
:react-native-device-info:prepareAndroidxLegacyLegacySupportCoreUtils100Library
:react-native-device-info:prepareAndroidxLifecycleLifecycleLivedata200Library
:react-native-device-info:prepareAndroidxLifecycleLifecycleLivedataCore200Library
:react-native-device-info:prepareAndroidxLifecycleLifecycleRuntime200Library
:react-native-device-info:prepareAndroidxLifecycleLifecycleViewmodel200Library
:react-native-device-info:prepareAndroidxLoaderLoader100Library
:react-native-device-info:prepareAndroidxLocalbroadcastmanagerLocalbroadcastmanager100Library
:react-native-device-info:prepareAndroidxPrintPrint100Library
:react-native-device-info:prepareAndroidxSlidingpanelayoutSlidingpanelayout100Library
:react-native-device-info:prepareAndroidxSwiperefreshlayoutSwiperefreshlayout100Library
:react-native-device-info:prepareAndroidxVersionedparcelableVersionedparcelable100Library
:react-native-device-info:prepareAndroidxViewpagerViewpager100Library
:react-native-device-info:prepareComAndroidSupportAppcompatV72301Library
:react-native-device-info:prepareComAndroidSupportSupportV42301Library
:react-native-device-info:prepareComFacebookFbuiTextlayoutbuilderTextlayoutbuilder100Library
:react-native-device-info:prepareComFacebookFrescoDrawee130Library
:react-native-device-info:prepareComFacebookFrescoFbcore130Library
:react-native-device-info:prepareComFacebookFrescoFresco130Library
:react-native-device-info:prepareComFacebookFrescoImagepipeline130Library
:react-native-device-info:prepareComFacebookFrescoImagepipelineBase130Library
:react-native-device-info:prepareComFacebookFrescoImagepipelineOkhttp3130Library
:react-native-device-info:prepareComFacebookReactReactNative0504Library
:react-native-device-info:prepareComFacebookSoloaderSoloader010Library
:react-native-device-info:prepareComGoogleAndroidGmsPlayServicesBase1700Library
:react-native-device-info:prepareComGoogleAndroidGmsPlayServicesBasement1700Library
:react-native-device-info:prepareComGoogleAndroidGmsPlayServicesGcm1700Library
:react-native-device-info:prepareComGoogleAndroidGmsPlayServicesIid1700Library
:react-native-device-info:prepareComGoogleAndroidGmsPlayServicesStats1700Library
:react-native-device-info:prepareComGoogleAndroidGmsPlayServicesTasks1700Library
:react-native-device-info:prepareOrgWebkitAndroidJscR174650Library
:react-native-device-info:prepareReleaseDependencies
:react-native-device-info:compileReleaseAidl
:react-native-device-info:compileReleaseNdk UP-TO-DATE
:react-native-device-info:compileLint
:react-native-device-info:copyReleaseLint UP-TO-DATE
:react-native-device-info:compileReleaseRenderscript
:react-native-device-info:generateReleaseBuildConfig
:react-native-device-info:generateReleaseResValues
:react-native-device-info:generateReleaseResources
:react-native-device-info:mergeReleaseResources
:react-native-device-info:processReleaseManifest
:react-native-device-info:processReleaseResources
ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:font
ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontStyle
ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontVariationSettings
ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontWeight
ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:ttcIndex
ERROR: In <declare-styleable> GradientColor, unable to find attribute android:endX
ERROR: In <declare-styleable> GradientColor, unable to find attribute android:endY
ERROR: In <declare-styleable> GradientColor, unable to find attribute android:startX
ERROR: In <declare-styleable> GradientColor, unable to find attribute android:startY
ERROR: In <declare-styleable> GradientColorItem, unable to find attribute android:offset

:react-native-device-info:processReleaseResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-device-info:processReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

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

BUILD FAILED

Total time: 21.884 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

Hi there!
I will make no effort to fix old versions, sorry. Feel free to fork and patch and maintain a stable branch but I work on master and release new versions
For the original error, I can find no information on the internet about a move like that. I believe you are behind a corporate proxy or something and this has nothing to do with this library


Incorporate VPC

At the moment we've not provisioned a VPC (which is by default what happens if you use the ECS wizard)
We should incorporate the VPC setup into here similar to the UI launch wizard

:+1: nice


narrow the promtail k8s pod discovery to kube-system only

How to categorize this PR?

/area logging
/kind enhancement
What this PR does / why we need it:
With this PR when the promtail agent installed on each shoot node is trying to discover a pod, it narrows it only to the kube-system namespace.
Also the request and limits of the loki's kube-RBAC-proxy are increased to meet the increased load.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Logs from shoot components can beretrieved only from pods running in the shoot `kube-system` namespace

/cherrypick release-v1.43

/cherrypick release-v1.42

I had to check that https://github.com/gardener/gardener/pull/5600 is available only in >=v1.43


music_drflac.c: Fixed the crash on looped file loading

Fixed the crash because of a null-pointer access attempt, and make the proper loading of meta-data (sample-rate can't be accessed if not handled via DRFLAC_METADATA_BLOCK_TYPE_STREAMINFO block separately).

Thanks.


Update README.md

using logo prometheus in readme that looks nicer
Before

After

Signed-off-by: Raihan Nismara<EMAIL_ADDRESS>

my first pr hack22 @codesome wdyt 🙏

Just made the file smaller to use, link to the file is here

Sounds like a good idea, but I would very much prefer the orange logo here. I found this with a quick search that we can use. Maybe reduce the size.

alright, thanks for the feedback!

Just made the file smaller to use, link to the file is here

done, please take a look

Can you download that pic and store it in the repo and point to it like you did for the grey logo?

Can you download that pic and store it in the repo and point to it like you did for the grey logo?

ok, but where the path should I store it? same path as the grey one?

Can you download that pic and store it in the repo and point to it like you did for the grey logo?

ok, but where the path should I store it? same path as the grey one?

Yes

finished

:+1: Thanks :)


Enhancement: Add a dummy energy meter class

If possible, please add a dummy energy meter class.
Currently, "hwmon"/"AEP"/"ACME" can be used for physical power consumption.
If the target board doesn't have any hardware energy meter ( e.g. hwmon/AEP/ACME), it's better for us to set a dummy energy meter module ( let's assume it "dummy_emeter" ), which can function as if it is a physical energy meter.
Of course, all the test results reported by the dummy emeter are only for simulation and we don't care about the result validity.  It's perfect if the dummy emeter reports lower power consumption for LITTLE cpu and higher power consumption for big cpu.
Benefit: With this new module, we can easily demo some notebooks for energy analysis because in customer site, it is difficult to set up a workable AEP/ACME environment in demo time!
Please consider this enhancement.  Thanks.

Setting up an ACME in demo mode is pretty fast: you just need a USB connection to the ACME, which is used both to power it up as well as to reach it via the USB Ethernet interface it provides.
You can of course avoid connecting the ACME to the target, which will make you read random/noise samples... but still I consider this a better / more realistic setup to demo.
Can you consider this option and, in case you agree and don't have other more specific needs for a dummy EM, close this issue?


Nargo execute should not panic if an invalid JSON-RPC resolver url is passed

Problem
Nargo panics if an invalid URL is passed to the oracle-resolver arg.
Happy Case
If the user passes in an invalid oracle resolver url, we likely don't want to panic since its a user error.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response

I'm working on this but I can't reproduce a panic.
I applied this diff to master:
index baef0c378..4eb7cfff0 100644
--- a/examples/prove_and_verify/src/main.nr
+++ b/examples/prove_and_verify/src/main.nr
@@ -1,3 +1,7 @@
-fn main(x: Field, y: pub Field) {
+#[oracle(custom_getter)]
+unconstrained fn custom_getter() -> Field {}
+
+unconstrained fn main(x: Field, y: pub Field) {
+    custom_getter();
     assert(x != y);
 }
\ No newline at end of file

Then, after compiling nargo_cli, went to examples/prove_and_verify and ran this:
$ ✗ nargo execute --oracle-resolver foo
warning: Unused expression result of type Field
  ┌─ /Users/asterite/Projects/noir/examples/prove_and_verify/src/main.nr:5:5
  │
5 │     custom_getter();
  │     ---------------
  │

Failed calling external resolver. transport error: minreq: was redirected to an absolute url with an invalid protocol

So, I get an error but it doesn't look like a Rust panic. Maybe this is already fixed? 🤔

Looks like it has! Thanks, we can just close this in that case.


database/sql: run prepare & execute commands on the same conn from DB pool

Try to find the connection for executing on the prepared statement from the free connections in the DB pool even if it's not the first free connection.
Fixes #32298

I signed it!


MFRC522-python not working after running mfrc522-rpi

Hello,
I have just installed mfrc522-rpi on my raspberry pi 3, and it I ran the read test example successfully. However, after exiting the app (Ctrl+c), I  noticed that my other python program which uses  MFRC522-python library, now is not detecting that rfid tag unless I reboot and run it before the mfrc522-rpi example.
in other words, if I run the python example first it works. On exit I call GPIO.cleanup(), so when I run node node /node_modules/mfrc522-rpi/test/read.js it works fine, but if I run python3 mypythonapp.py after it it doesn't detect the tag and output is:
/usr/local/lib/python3.7/dist-packages/mfrc522/MFRC522.py:151: RuntimeWarning: This channel is already in use, continuing anyway.  Use GPIO.setwarnings(False) to disable warnings.
GPIO.setup(pin_rst, GPIO.OUT)
I think this has to do with gpio cleanup?
P.S I tried to call rpio.close(22); and this.spi.close() in /node_modules/mfrc522-rpi/index.js, the warning above is gone, but still can't detect the tag.
Can anyone help with this please?
Ta
Hardware: raspberry pi 3 running raspbian buster
Node v12.8.0 (using nvm)

could you fix the problem?


How to render performance of agent visually

It would be nice to show how the agent is performing inside the game, but in the meantime here's some imperfect but functional code.
Note: This dramatically slows the throughput of the model. Only render after the model has finished training. May require additional dependencies (like matplotlib) if not already present.
Inside dopamine/atari/run_experiment.py:
  def _run_one_step(self, action):
    """Executes a single step in the environment.

    Args:
      action: int, the action to perform in the environment.

    Returns:
      The observation, reward, and is_terminal values returned from the
        environment.
    """
    self._environment.render(mode='human') #Shows game in progress. Note: Slows down training tremendously.
    time.sleep(1/60)
    observation, reward, is_terminal, _ = self._environment.step(action)
    return observation, reward, is_terminal

I think there is a simpler way to do this (without having to edit dopamine source code). You could simply wrap your environment with https://github.com/google/dopamine/blob/76cdae1f858233a8501e2b61095cde54c6f8a214/dopamine/discrete_domains/gym_lib.py#L306
Then you can put the render code in the step function.

hey everyone, just pushed some utilities to allow you to render the agent interacting with the environment (as well as other plots alongside it).
check out this colab for an example on how to use it: https://colab.research.google.com/github/google/dopamine/blob/master/dopamine/colab/agent_visualizer.ipynb


Item does not disappear with Glowsilk Bow charging state

Describe the Bug
When you are charging a Glowsilk bow, the item that you are holding in your other hand does not disappear compared to charging with a regular bow.
Reproduction Steps

Obtain a Glowsilk Bow in the offhand slot/main slot
Hold any item in the offhand slot/main slot
Charge the Glowsilk Bow
Compare the difference with a regular bow

Expected Result
The item in the opposite hand should lower to the bottom of the screen and disappear.
Screenshots and Videos

Operating System
Windows 10
Mod Version
Beta 2.5.0-1
Minecraft Version
1.18.2
Forge Version
40.1.31
Other Mods
N/A
Additional Context
No response

Present on 1.17


HUM-567 : cant overwrite obj in EC

when the object got stabilized the ETag got sent over as a Meta-Etag
header. I'm special casing it to be saved as ETag in db. this is
basically in line with what is done on whole objects

Works!


Update docs to clarify the versions supported, and mark calls that are only for "new" InfluxDb API versions

We can explain that there are basically two "versions" that this library supports: 0.9 and 1.0 (which is unreleased and basically means: everything that is not present in 0.9). Maybe we can even consolidate KAPACITOR_VERSION and INFLUX_VERSION enums as the later versions of the TICK-stack require all components to be of the same version?

Yes, that's a good idea. Anyway, just installed the latest influx in a VM, ran the tests and 15 failed :D

Oh, that's a shame. Were the failing tests kapacitor related?
On Sun, 26 Jun 2016, 19:23 Tihomir Kit<EMAIL_ADDRESS>wrote:

Yes, that's a good idea. Anyway, just installed the latest influx in a VM,
ran the tests and 15 failed :D
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pootzko/InfluxData.Net/issues/10#issuecomment-228612018,
or mute the thread
https://github.com/notifications/unsubscribe/AFPhtTfdAv3q7spgnxYs2e-ig0-D1yktks5qPrWUgaJpZM4I2Ivq
.

Most of them yes, but I guess it should all be fairly easy to fix. Working on it!

Updated everything, all tests pass finally, deployed to nuget.org, and updated some things in the README. Didn't add documentation for the latest stuff you added most recently yet. If you want, you could add it, or I'll do it in the next few days.


Initial implementation of row count estimates in cost-based optimizer

Signed-off-by: Andy Grove<EMAIL_ADDRESS>First pass at making estimated row counts available to the cost-based optimizer.
Closes https://github.com/NVIDIA/spark-rapids/issues/2090

build

@revans2 Could you review this when you get a chance

build


🐛 Bug Report: Login failed; caused by Error: Authentication failed, Failed to obtain access token, Error for Gitlab integration

📜 Description
I am implementing Organizational Gitlab Sign in on my fresh backstage application. The documentation only provides a limited amount of information on how to troubleshoot things.
👍 Expected behavior
Easy-Peasy Sign-in
👎 Actual Behavior with Screenshots
My organisation's Gitlab (signedin with my enterprise account)
[image]
The response/issue:

👟 Reproduction steps
app-config.yaml (This contains other boilerplate as well, I am just mentioning the changes I made)
integrations:
  gitlab:
    - host: gitlab.com
      token: ${GITLAB_TOKEN}

auth:
  providers:
    guest: {}

app-config.local.yaml (This contains other boilerplate as well, I am just mentioning the changes I made)
auth:
  environment: development
  providers:
    gitlab:
      development:
        clientId: [redacted]
        clientSecret: [redacted]
        audience: https://git.[redacted].dev/
        enableExperimentalRedirectFlow: true

index.ts (This contains other boilerplate as well, I am just mentioning the changes I made)
import { createBackendModule } from '@backstage/backend-plugin-api';
import { gitlabAuthenticator } from '@backstage/plugin-auth-backend-module-gitlab-provider';
import {
  authProvidersExtensionPoint,
  createOAuthProviderFactory,
} from '@backstage/plugin-auth-node';
import { stringifyEntityRef } from '@backstage/catalog-model';

backend.add(import('@backstage/plugin-auth-backend-module-gitlab-provider'));

const customAuth = createBackendModule({
  pluginId: 'auth',
  moduleId: 'custom-auth-provider',
  register(reg) {
    reg.registerInit({
      deps: { providers: authProvidersExtensionPoint },
      async init({ providers }) {
        console.log('lol');
        providers.registerProvider({
          providerId: 'gitlab',
          factory: createOAuthProviderFactory({
            authenticator: gitlabAuthenticator,
            async signInResolver(info, ctx) {
              console.log('bali', info);
              const {
                profile: { email },
              } = info;
              if (!email) {
                throw new Error('User profile contained no email');
              }
              // myEmailValidator(email);
              const [name] = email.split('@');
              const userEntity = stringifyEntityRef({
                kind: 'User',
                name: name,
                namespace: 'default',
              });

              return ctx.issueToken({
                claims: {
                  sub: userEntity,
                  ent: [userEntity],
                },
              });
            },
          }),
        });
      },
    });
  },
});

backend.add(customAuth);

App.tsx (This contains other boilerplate as well, I am just mentioning the changes I made)
components: {
    SignInPage: props => (
      <SignInPage
        {...props}
        auto
        providers={[
          'guest',
          {
            id: 'gitlab-auth-provider',
            title: 'Gitlab',
            message: 'Sign in using Gitlab',
            apiRef: gitlabAuthApiRef,
          },
        ]}
      />
    ),
  },

📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

Could you try the following docs to see if there's any additional information that could be relevant here? https://backstage.io/docs/auth/troubleshooting/#general-troubleshooting


Cut track branches on all repos for CKF 1.8

What needs to get done
We'll need to make sure we have created the corresponding tracks for all components used currently in our bundle
https://github.com/canonical/bundle-kubeflow/blob/main/releases/latest/edge/bundle.yaml
This will need to happen after we've first merged

[x] https://github.com/canonical/kserve-operators/pull/191
[x] https://github.com/canonical/katib-operators/pull/151
[x] https://github.com/canonical/kubeflow-tensorboards-operator/pull/98
[x] https://github.com/canonical/kubeflow-volumes-operator/pull/119
[x] https://github.com/canonical/istio-operators/pull/348
[x] https://github.com/canonical/minio-operator/pull/154
[x] Merge KFP PRs

https://github.com/canonical/kfp-operators/pull/362
https://github.com/canonical/kfp-operators/pull/385
https://github.com/canonical/kfp-operators/pull/386
https://github.com/canonical/kfp-operators/pull/387

[x] https://github.com/canonical/envoy-operator/issues/66

Why it needs to get done
In order for us to update the bundle for the 1.8 release, and have automations just for 1.8

Closing since all branches were cut


Update view-licensed-and-unlicensed-users-with-microsoft-365-powershe…

…ll.md
I think that in the example code for getting licensed users, it should be $licensed = $False in the declaration instead of $licensed = $True. Otherwise there is never an exception case.
Currently the list returns users with or without assigned licenses. In the submitted PR, it returns a list only of users with assigned licenses.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


support unicode and update related tests

support unicode ("測試" means "test" in Traditional Chinese)
make sure it's backward-compatible
include related tests
reference: http://erlang.org/doc/apps/stdlib/unicode_usage.html#id69524

Thanks and sorry being late to merge.


Move away from Jetty or downgrade its version due to crashes on Android

W/System.err: Defaulting Uptime to NOIMPL due to (java.lang.UnsupportedOperationException) Implementation not available in this environment
E/WireMockManager: Unable to start server
com.github.tomakehurst.wiremock.common.FatalStartupException: java.lang.RuntimeException: java.net.BindException: bind failed: EADDRINUSE (Address already in use)
at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:148)

this page - https://bugs.eclipse.org/bugs/show_bug.cgi?id=443652
suggests last version of jetty 9.x that worked on android (api level 19) was 9.1.2.v20140210
while your project uses 9.4.30.v20200611 of jetty

Caused by: java.lang.RuntimeException: java.net.BindException: bind failed: EADDRINUSE (Address already in use)
at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:184)
at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:146)

Caused by: java.net.BindException: bind failed: EADDRINUSE (Address already in use)
at libcore.io.IoBridge.bind(IoBridge.java:99)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:132)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at wiremock.org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at wiremock.org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at wiremock.org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at wiremock.org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at wiremock.org.eclipse.jetty.server.Server.doStart(Server.java:366)
at wiremock.org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:182)

#815 is another example of a jetty 9 crash on android

Going to have a major rethink about Android support in 3.x. See https://github.com/tomakehurst/wiremock/issues/1345#issuecomment-829341603


what's expected buffer clearing behaviour of perfetto trigger mode

Hi Perfetto team,
I am using perfetto to try to collect some traces from device. What I am expected is continious tracing and spliting traces into multiple  splitted ones, to tracing&profiling for several days to reproduce one issue. I noticed there's a trigger mode in perfetto config. However when I am using this feature, seems the traces generated , which has .NUMBER as its suffix, keeps increasing from KB to even hundreds MB. Where does these data resides in? Does the buffer used by perfetto not cleared?

Here's the config I am using.
adb shell perfetto \
  -c - --txt \
  -o /data/misc/perfetto-traces/encrypt_trigger_01.trace \
<<EOF

buffers: {
    size_kb: 129024
    fill_policy: DISCARD
}
buffers: {
    size_kb: 2048
    fill_policy: DISCARD
}
data_sources: {
    config {
        name: "android.packages_list"
        target_buffer: 1
    }
}
data_sources: {
    config {
        name: "linux.system_info"
        target_buffer: 1
    }
}
data_sources: {
    config {
        name: "linux.process_stats"
        target_buffer: 1
        process_stats_config {
            scan_all_processes_on_start: true
        }
    }
}
data_sources: {
    config {
        name: "linux.sys_stats"
        sys_stats_config {
            cpufreq_period_ms: 1000
        }
    }
}
data_sources: {
    config {
        name: "linux.ftrace"
        ftrace_config {
            ftrace_events: "sched/sched_switch"
            ftrace_events: "power/suspend_resume"
            ftrace_events: "sched/sched_wakeup"
            ftrace_events: "sched/sched_wakeup_new"
            ftrace_events: "sched/sched_waking"
            ftrace_events: "power/cpu_frequency"
            ftrace_events: "power/cpu_idle"
            ftrace_events: "sched/sched_process_exit"
            ftrace_events: "sched/sched_process_free"
            ftrace_events: "task/task_newtask"
            ftrace_events: "task/task_rename"

            atrace_categories: "am"
            atrace_categories: "aidl"
            atrace_categories: "binder_lock"
            atrace_categories: "binder_driver"
            atrace_categories: "database"
            atrace_categories: "input"
            atrace_categories: "pm"
            atrace_categories: "ss"
            atrace_categories: "view"
            atrace_categories: "wm"
            atrace_apps: "*"
        }
    }
}

data_sources: {
    config {
        name: "linux.perf"
        perf_event_config {
            timebase {
                frequency: 1000
                timestamp_clock: PERF_CLOCK_BOOTTIME
            }
            callstack_sampling {
                scope {
                    target_cmdline: "com.example"
                }
            }
        }
    }
}

data_sources: {
    config {
        name: "android.log"
        android_log_config {
            log_ids: LID_EVENTS
            log_ids: LID_CRASH
            log_ids: LID_KERNEL
            log_ids: LID_DEFAULT
            log_ids: LID_RADIO
            log_ids: LID_SECURITY
            log_ids: LID_STATS
            log_ids: LID_SYSTEM
        }
    }
}
data_sources: {
    config {
        name: "linux.ftrace"
        ftrace_config {
            ftrace_events: "ftrace/print"
            atrace_categories: "binder_driver"
            atrace_apps: "*"
        }
    }
}

# write_into_file: true
# output_path: "/data/misc/perfetto-traces/trigger_test_001.trace"

trigger_config: {
    trigger_mode: CLONE_SNAPSHOT
    trigger_timeout_ms: 86400000
    triggers: {
        name: "high_cpu"
    }
}

compression_type: COMPRESSION_TYPE_DEFLATE

EOF

There's a deep misunderstanding of triggers: please first read https://perfetto.dev/docs/concepts/config#triggers.
CLONE_SNAPSHOT triggers are a very advanced mode of triggering: it snapshots the state of the buffer every time the trigger is received and saves it to a file. It does not clear the state of the buffer when the snapshot is taken, just "clones" and takes a snapshot.
You are also using DISCARD mode of the buffers which makes zero sense for CLONE_SNAPSHOT triggers. RING_BUFFER is the only thing which makes sense for CLONE_SHAPSHOT tracing.
The traces will increase in size until they hit your buffer size and then they will stay at that size, always dumping the most recent snapshot into the trace.

You are correct. I noticed I set a pretty large buffer and result in takes a long time to fill it up.


Scheduler IntervalAction Returns 413 (200 is expected)

On master, blackbox test for intervalaction returns 413 where 200 is expected.  Not sure if this an issue with the test or the scheduler service implementation.
 Status code is 200
  Pass  Response time is less than 800ms

Sub-folder 361 http://localhost:48085/api/v1/intervalaction/:id
  POST http://localhost:48085/api/v1/intervalaction [200 OK, 153B, 12ms]
  GET http://localhost:48085/api/v1/intervalaction/4300eb62-e4ee-49a4-a30d-8e4219f66f2b [200 OK, 346B, 6ms]
  -
  | 'Validation failed: ', null
  -
  Pass  Status code is 200
  Pass  Response time is less than 800ms
  Pass  Has Content-Type
  Pass  Content-Type is application/json
  Pass  Is Valid Response Schema

Sub-folder 362 http://localhost:48085/api/v1/intervalaction
  POST http://localhost:48085/api/v1/intervalaction [200 OK, 153B, 10ms]
  PUT http://localhost:48085/api/v1/intervalaction [200 OK, 111B, 7ms]
  Pass  Status code is 200
  Pass  Response time is less than 800ms
  Pass  Has Content-Type
  Pass  Content-Type is application/json
  Pass  Body has True

Sub-folder 363 http://localhost:48085/api/v1/intervalation
  POST http://localhost:48085/api/v1/intervalaction [200 OK, 153B, 10ms]
  DELETE http://localhost:48085/api/v1/intervalaction/0a043911-05c4-4f6f-b2a4-2a81bd8698d9 [200 OK, 111B, 7ms]
  Pass  Status code is 200
  Pass  Response time is less than 800ms
  Pass  Has Content-Type
  Pass  Content-Type is application/json
  Pass  Body has True

Sub-folder 364 http://localhsot:48085/api/v1/intervalaction
  POST http://localhost:48085/api/v1/intervalaction [200 OK, 153B, 11ms]
  Pass  Status code is 200
  Pass  Response time is less than 800ms
  Pass  Has Content-Type
  Pass  Content-Type is text/plain

-------------------------------------------------------------------
|                         |          executed |            failed |
--------------------------+-------------------+--------------------
|              iterations |                 1 |                 0 |
--------------------------+-------------------+--------------------
|                requests |                 8 |                 0 |
--------------------------+-------------------+--------------------
|            test-scripts |                10 |                 0 |
--------------------------+-------------------+--------------------
|      prerequest-scripts |                 8 |                 0 |
--------------------------+-------------------+--------------------
|              assertions |                21 |                 1 |
-------------------------------------------------------------------
| total run duration: 859ms                                       |
-------------------------------------------------------------------
| total data received: 408B (approx)                              |
-------------------------------------------------------------------
| average response time: 77ms [min: 6ms, max: 554ms, s.d.: 180ms] |
-------------------------------------------------------------------

  #  failure         detail

 1.  AssertionError  Status code is 200
                     expected false to be truthy
                     at assertion:0 in test-script
                     inside "intervalAction / 360 http://localhost:48085/api/v1/intervalaction"

Process finished with exit code 1

Found when working https://github.com/edgexfoundry/edgex-go/issues/1809 (PR https://github.com/edgexfoundry/edgex-go/pull/1844).

I have a fix for this particular issue with PR#1883.  There was an issue in the parseFrequency function in the Scheduler schedulerContext call when ingesting new IntervalAction(s).  Although the Interval Frequency field was being validated it was not actually being converted correctly.  I have added back in the functionality "legacy functions" which converted the old style format to a time.Duration.   Only the utils file and the parseFrequency() function have been modified so just one file utils.go.   I validated this buy running the Black Box Tests after the fix was implemented locally.


Yeah, that's possible. Keep in mind though that IO-related tasks could then block execution of tasks not related to IO.

Mhhh what I meant is more like is this library to tool for that ?


Master

Fix for issue #2

Thanks for contributing!
I think it makes sense to delete an existing file first to prevent merging with a previous result.
grunt.file.delete(coverageFilePath)

Yeah, but probably that needs to be done before qunit is launched. Otherwise you'd be overwriting the previous url's result again :)

probably that needs to be done before qunit is launched

Sure. But there's already grunt.file.delete(dest); at the beginning of coverageInstrument task.


[BUG] fo.Dataset.from_dir for fo.types.CVATImageDataset not work for this structure folder

Instructions
Thank you for submitting an issue. Please refer to our issue policy for information on what types of issues we address.

Please fill in this template to ensure a timely and thorough response
Place an "x" between the brackets next to an option if it applies. For example:

[x] Selected option

Please delete everything above this line before submitting the issue

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): PopOS 22.04
Python version (python --version): 3.7
FiftyOne version (fiftyone --version): 0.18.0, 0.17.2
FiftyOne installed from (pip or source): pip

Commands to reproduce
if  structure folder like this:
dataset_dir/
   ├── annotations.xml
   └── data/x/x/
            ├── 1b0a16a7d2724a8d83c976749078f7db.jpg
            ├── 22ba24c163734b83a466f89e61e89ca6.jpg
            ...
            ├── day1_set3_side1_20220715123323_20f141053d594bab9400d354acef2956.jpg
            └── day1_set3_side1_20220715123323_85a343c3d5b84a26b4123169967460d2.jpg

test.py:
import fiftyone as fo

# Create the dataset
dataset = fo.Dataset.from_dir(
    dataset_dir='dataset_dir/',
    labels_path='dataset_dir/annotations.xml',
    dataset_type=fo.types.CVATImageDataset,
)

# commands here
python test.py

Describe the problem
if the structure like this, the path for labels_path will not_found based on this:
https://github.com/voxel51/fiftyone/blob/23451799fe43fe14772823b23657eba4e8ea43f2/fiftyone/utils/data/importers.py#L738
the impact cannot load and show annotations from cvat.
lets say the abs.path for dataset_dir is /x/x/x/dataset_dir
the output for labels_path will merge abs.path from dataset_dir and labels_path. so the output for label_path will be like this:
/x/x/x/dataset_dir/dataset_dir/annotations.xml

so i hardcode that line to became:
labels_path = fou.normalize_path(labels_path)

and it works for that structure folder
What areas of FiftyOne does this bug affect?

[x] App: FiftyOne application issue
[ ] Core: Core Python library issue
[ ] Server: FiftyOne server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently
[x] Yes. I would be willing to contribute a fix for this bug with guidance from the FiftyOne community
[ ] No. I cannot contribute a bug fix at this time

or we can just make it like this, but need to add it to documentation.
import fiftyone as fo

# Create the dataset
dataset = fo.Dataset.from_dir(
    dataset_dir='dataset_dir/',
    labels_path='annotations.xml',
    dataset_type=fo.types.CVATImageDataset,
)


Check elm.json summary for forbidden words

This is currently very picky about the whitespace in the json, expecting exactly "summary": " but no other whitespace flavours. I would rather not change to using RegExp or a full blown Parser for this, so that means only specific strings can be checked for. I think these variations should be sufficient for any hand-editing problems:

"summary": "
"summary":"
"summary" : "
"summary" :"

Adding a fallback range is probably sensible incase these can't be found, pointing at the top of the elm.json file.


code

When will the code be released? Very much looking forward to your work.

looking forward to your work!


No Presets Loaded yet

Companion (2.3.0+4608-v2-3.0-2994a6d0) doesn't receive presets from Event Master 9.05.65399.  Drop-down menus only list "no presets loaded yet"
Buttons created via the drag + drop Presets menu display " ?? (X)", where X is the preset number.
Microsoft Surface 8
Windows 10

Seems like a network issue to me, did you check Port available to your machine, no firewalls etc?

There was an update on the text of preset. Please check on which build you are

I've put in a fix for this


submit_chain.sh: Allow multiple versions of a single case

In the version of Keith Oleson's csh script that he sent me, there was a case that ran for a while with minimal output, ended, and then was resubmitted with additional output. This is a very useful idea—you might only need daily outputs for the last few years of a case. However, it's not how I have historically thought of things, so I wrote submit_chain.sh assuming that such segmentation would happen via different cases for each segment.
There's no reason this functionality couldn't be added, but it would be a lot of work. If you think it's worth it, comment here—or better yet, fork the repo and submit a pull request.

I've done some thinking about how this might be accomplished.
Maybe in the chainspec file, each case could have multiple lines, distinguished by elements of new vectors list_runnames (e.g., runA_1850_1969 and runA_1970_2010) and list_presub_scripts (which would refer to scripts that apply the segment-specific properties). Then list_deps would need to refer to runnames instead of cases. (And of course submit_chain.sh would have to be reworked to handle these.)

One tricky thing about this functionality is that calling case.submit for two different versions of the same run means that they will all see and use the configuration of the last run, because case.submit sets up the run directory. I solved this by adding a new flag to case.submit that makes it set up the run directory but not actually submit the run. The idea is to call case.submit --no-submit as part of the prerun script of secondary run versions (in the example above, runA_1970_2010).
The next tricky thing to figure out: The prerun script is called before every segment in a run with RESUBMIT>0. This is a problem if secondary run versions need to specify the RESUBMIT value—it would just keep getting reset, and the resubmits would go on forever.
I think I can make this work by having case.submit --no-submit only called if file NO_SUBMIT_ALREADY_CALLED_THIS_RUNNAME (or something) does not exist, and create that file as soon as case.submit --no-submit is called the first time.

This will also, of course, require another case.submit option: --only-submit.


Add generation from template

This works, however, because the device files are added at runtime, references to them are considered errors by VS Code intellisense. This could make development more difficult as we can't view source code or method names before compile time.

That's fixed now.

This works, however, because the device files are added at runtime, references to them are considered errors by VS Code intellisense. This could make development more difficult as we can't view source code or method names before compile time.

That's fixed now.


Send message to a Slack channel when a milestone number of virtual visits

What
Send a message to a Slack channel when a milestone number of virtual visits by:

Adding a Slack gateway with a postMessage using Slack's web-api package
Adding a sendVisitsMilestoneNotification usecase
Updating updateWardVisitTotals usecase to call new usecase

Why
To notify us when we've reached milestone and allow us to celebrate how far we've come from those first 48 hours.
Screenshots

Notes
Next steps:

Add a Slack bot to workspace
Add environment variables to live

Closing the PR so it's not noisy amongst other PRs. Need to figure how else to do this after https://github.com/madetech/nhs-virtual-visit/pull/292#discussion_r426734395. 🤔


flutter_gallery_sksl_warmup__transition_perf_e2e_ios32 flakes, flutter_01.sksl.json does not exist

Test is already marked flaky, so this isn't making the tree red.
flutter build ios --profile --bundle-sksl-path /Users/flutter/.cocoon/flutter/dev/integration_tests/flutter_gallery/flutter_01.sksl.json -t test_driver/transitions_perf_e2e.dart in /Users/flutter/.cocoon/flutter/dev/integration_tests/flutter_gallery

** BUILD FAILED **
/Users/flutter/.cocoon/flutter/dev/integration_tests/flutter_gallery/flutter_01.sksl.json does not exist.

flutter_gallery_sksl_warmup__transition_perf_e2e_ios32_1a9ea39_1.log

@liyuqian I didn't see an open issue for making flutter_gallery_sksl_warmup__transition_perf_e2e_ios32 not flaky.

Yes, the old one https://github.com/flutter/flutter/issues/65258 was closed before. The same error message seem to appear again. I'll investigate and track the progress here.


Positional arguments in __init__

Looking at the following class:
@attr.s
class A:
    x: int
    y: int
    z: int = attr.ib(default=4)

I see it generates the following __init__:
def __init__(x: int, y: int, *, z: int) -> None

Thus, I can not create an instance using the following A(x=3, y=4, z=5).
Why are the first arguments are positional arguments and not regular one?
I would expect the signature to be:
def __init__(x: int, y: int, z: int) -> None

Thanks

Class A is not an attrs class. The way it's written attrs does nothing at all.

i forgot adding the decorator in the question, did it now

This will result in
Revealed type is 'def (self: t.A, z: builtins.int =)'

because attr.s doesn't look at types by default.
If you use define or dataclass, you get:
Revealed type is 'def (self: t.A, x: builtins.int, y: builtins.int, z: builtins.int =)'

which is correct AFAICT.

Ok i found my mistake, it happens when there is a kw_only argument
For example in the following:
@attr.dataclass
class A:
    x: int
    y: int
    z: int = attr.ib(kw_only=True)

gives Signature: A.__init__(self, x: int, y: int, *, z: int) -> None
Why is x and y positional?

I think you might be mixing up "positional" and the new "positional-only" arguments (/)?

i mean both directions. Both A(3, 4, 5) doesn't work and A(x=3, y=4, z=5) doesn't work

A(x=3, y=4, z=5) totally works, I've just tested it with your example.
A(3, 4, 5) doesn't work, because z is kw_only=True.


Correct #21 so targetHeatingCoolingState works properly

I guess I'm still a little confused.  You said that both:

apiroute + "/off"
apiroute + "/targetHeatingCoolingState/0"

worked previously, but I don't see how that's possible.  In any case, I'm not sure how to support both without an additional option passed in by the application.  Is this what you were looking for?

Thx @paullj1 for your work :)


[CP Staging] Fix useResponsiveLayout bugs

cc @getusha
Details

Fixed Issues

$ https://github.com/Expensify/App/issues/48675
$ https://github.com/Expensify/App/issues/48724
Tests

Precondition: Workspace is connected to QBO, or have multi tags set up.

Click on any main tag.
Click Select all checkbox.
Expected Result: App will not freeze.

Test 2:

Go to staging.new.expensify.com
Go to workspace settings > Report fields
Click Add field
Select List from Type field
Click List values
Click Add value
Add some list values
Expected Result: There will be checkbox next to each list value

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

Same as tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

https://github.com/user-attachments/assets/5b15cc59-c119-4e1f-883d-60ee21b9fba6

iOS: Native

https://github.com/user-attachments/assets/7130c21e-832b-4ba6-a3ca-30c1f4ad3a92

iOS: mWeb Safari

https://github.com/user-attachments/assets/0394de98-df5d-41a6-8916-8328f94692a9

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/af87a148-0af7-425e-83dd-f3f225d8dc3e

MacOS: Desktop

https://github.com/user-attachments/assets/8239e4cd-e18e-4a83-afc1-88b6511b8857

Looks like this fixes regressions caused by https://github.com/Expensify/App/pull/46788, eh?

Report Fields fix working well on Chrome & Desktop 👍
https://github.com/user-attachments/assets/0e98be6c-fbfc-49ee-83c7-73853642433c
https://github.com/user-attachments/assets/c6e32c7b-384d-4473-b884-9d4bdea78eb2

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

This should get CP'd on Monday 🙏

This was CP'd last Friday - https://github.com/Expensify/App/actions/runs/10748576364 - failed in Desktop build but made it on a subsequent CP


fix: solve the restart caused by kong not starting

Added retry when getting data returned by Kong Admin API.
fixes #761
fixes #766

Thank you for your contribution. Please fill out the following form to claim your contributor swag:
https://github.com/Kong/kong/blob/master/CONTRIBUTING.md#contributor-t-shirt.