Partitioning data into two keys is taking more time (10x) than partitioning into one key.

I am trying to add second level of partition to my table instead of one level of partition but it is taking 10X time as compared to single level partition in hudi flink job.
I tried to ingest 1.8M record into one level of partition and it took around 12-15 Min to ingest all the data then with same configuration I just added another level of partition key with same data payload and it took around 1 hour 45 Min to complete the process.
To Reproduce
Steps to reproduce the behavior:
below is the configuration that I am using for table. You can add the table creation statement with below properties.
PARTITIONED BY (`client_id`,`hashed_server_id`)
WITH ('connector' = 'hudi','path' = '${table_location}',
'table.type' = 'COPY_ON_WRITE',
'hoodie.datasource.write.recordkey.field' = 'a,b',
'payload.class'='x.y.PartialUpdate',
'precombine.field'='ts',
'hoodie.clean.async'='true',
'hoodie.cleaner.policy' = 'KEEP_LATEST_COMMITS',
'hoodie.clean.automatic' = 'true',
'hoodie.clean.max.commits'='5',
'hoodie.clean.trigger.strategy'='NUM_COMMITS',
'hoodie.cleaner.parallelism'='100',
'hoodie.cleaner.commits.retained'='4',
'hoodie.index.type'= 'BUCKET',
'hoodie.index.bucket.engine' = 'SIMPLE',
'hoodie.bucket.index.num.buckets'='16',
'hoodie.bucket.index.hash.field'='a',
'hoodie.parquet.small.file.limit'='104857600',
'hoodie.parquet.compression.codec'='snappy')

Expected behavior
As it is just a partition addition to the storage it should not impact the performance much(I can understand if it takes 5-7 min extra as complexkey generation is bit slower than simplekey ).
Environment Description

Flink  1.17.1

Hudi version : 14

Spark version : NA

Hive version : NA

Hadoop version : 3.4.0

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) :Yes

Additional context
My table type is upsert and I have test the functionality and it is working fine and I cannot change the table type.
I also discussed with @ad1happy2go and he also suggested that it wont impact much as it just a another level of partition.
CC : @ad1happy2go @codope @danny0405 @yo

@xicm Yes I agree but it would not effect it to 10 times.
let say I have 100 partition and each partition has 10 sub-partition with 16 bucket then total task would be 1001016 at max whereas with single partition it has 100*16 right?
I understand it will take 5-7 min extra compared to single partition but not 10 times.
let me know your thoughts

not sure if this is the cause, can you check the number of file groups after partition field changed, and reduce the bucket number to see the time cost.

@xicm let me reduce the number of bucket and test it for same number of record to check process time.
can you tell me how to check number of filegroup?

@xicm I reduced the number of bucket( it makes sense to reduce the bucket size as we have second level partition) but it is still taking 45-50 min to execute which 5 times as compare to 1 level partition.

can you tell me how to check number of filegroup?
cli or spark sql, show_commits, pay attention to total_files_added and total_files_updated

it is still taking 45-50 min to execute which 5 times as compare to 1 level partition.
reduce the bucket num and increase write.tasks, test a few times to get a better performance

Yes I am trying to test the different combination with bucket number.

Hi @xicm,
I tried below combination with same number record.

Please find the below details related to filegroups

After testing it several times I noticed that 8,4 buckets looks good for data size which is <100M.
As we know once the number of buckets is set we cannot change it.
so I have question related to same.
Suppose I took 8 as buckets and the streaming data is constantly growing (100 million per ID), will it affect the performance (considering that the job is streaming)?
Thanks
Mahesh Gupta

I already had 20 task to write the data, please check in below screenshot. do you want me to increase it more?

Yes. it is 20. it start from 0 and ending with 19.

@xicm Let me try to increase the number write task and for load and test the performance.
thanks

@danny0405 I am asking about the number of file group added for particular commit. I am already implementing bucket index.
Number of filegroup is more than 2000 for a commit.

Hi @xicm and @danny0405,
I tried to increase the parallelism as @xicm suggested but it is trying to consume the data in a single commit
i.e. it accumulates the data into a single commit which causes a Heap OOM issue.

Commit size from .hoodie folder
Second commit is trying to consume the entire data in one commit i.e. it is creating 41MB .commit file.

Can we reduce/control the commit filesize?

Can you redesign the partitions? There are only 100M of data, but there are so many partitions.

@xicm The dataset is huge, around 100M. However, for performance evaluation, I have only ingested 1.78M.

Yeah, try to deduct the number of file groups per-commit, because for each file group, we have a in-memory buffer before flushing into disk.

@danny0405 can you please share the config to deduct the filegroup per-commit?

Discussed with @maheshguptags . Advised to explore flink Kafka stream configs to control number of records/bytes in one MicroBatch.
https://nightlies.apache.org/flink/flink-docs-release-1.13/docs/connectors/datastream/kafka/
cc @danny0405

@ad1happy2go I tried the below configuration for Kafka, but it didn't help.
source.kafka.max.poll.records=300
source.kafka.max.poll.interval.ms=300000

I tried different configurations for the above config.
cc : @danny0405

@danny0405 Can help with this plz?

@maheshguptags Lets get into a call to discuss this further.

@xicm @danny0405 Had a discussion with @maheshguptags . Let me try to summarise his issue.
He is having around 5000 partitions in total and using the bucket index. When he use parallelism(write.tasks) as 20 the job takes 1:45 mins and when it is 100 it takes 35 mins.
But with increase in parallelism, the number of file groups explodes as expected. This result in lot of small file groups with very few records each (~20) , which ultimately causing OOM due to 400MB commit files.

Hi @ad1happy2go,
There is little correction on the commit file size.

which ultimately causing OOM due to 400MB commit files.

its a 41 Mb commit file size @ad1happy2go.

@danny0405 still waiting for your response. can you please take look on this plz?


[1pt ] Setup Backend

Changes :

Setup kanban for the backend of the booking app project

Assign roles to team members

Setup Kanban for frontend

Assign roles to team members

Screenshot

Link to the Kanban Project

Hi Team,
While you made a great effort in this project, unfortunately, I cannot proceed to review your board.
Invalid Code Review Request
You have submitted a project, that does not contain a screenshot of the current state of the Kanban Board at the time of review request which is seen as a requirement here
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Please, do not open a new Issue for re-reviews. You should use the same Issue submitted for the first review, either valid or invalid unless it is requested otherwise.

Hi Team,
Great work so far👏
However there are some issues preventing me from giving the 👍
Highlights

All issues have description ✔
Weight for tasks seem appropriate ✔

Required Changes

Tasks assigned to team members should be  equitable and therefore there should not be more than a 5 pt difference in task assignments. In this case @tashisrael has way more tasks assigned than everyone else. Currently don't meet this requirement✖
Ideally this requirement would have made submission invalid, but I forgot to spot this originally so did not think it were fair to mark it as invalid again, so please address this: Info concerning the number of persons on your team should be in this issue description (Whether it means you mention the github users. their names or just the number memebers in the team (or all)).  You currently do not meet this requirement ✖

Optional suggestions

[OPTIONAL] Consider adding laels to your issues, it'd make it easier to among different tasks and even make it easier to filter different types of tasks. Do you think this is something you can do ❓

Every comment with the [OPTIONAL] prefix won't stop the approval of this issue. However, I strongly recommend you to take them into account as they can make your Kanban better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Please, do not open a new Issue for re-reviews. You should use the same Issue submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi Team,
In my opinion, you are ready to move on to the next step! ⏭
Good luck! 🎉
Highlights

You corrected inequitable distribution of tasks and all good now ✔
Representation of number of members in team is in the issue description ✔

Optional suggestions

[OPTIONAL] Consider adding laels to your issues, it'd make it easier to among different tasks and even make it easier to filter different types of tasks. ❓

Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Cheers and Happy coding!👏👏👏

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


sap.m.Table ListMode Delete for table cannot be used in drag and drop because selection of a row is not permitted

OpenUI5 version:  1.123
Browser/version (+device/version): chrome latest
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
https://openui5.hana.ondemand.com/entity/sap.m.Table/sample/sap.m.sample.TableDnD/code
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

https://openui5.hana.ondemand.com/entity/sap.m.Table/sample/sap.m.sample.TableDnD/code
Change the mode of tables to Delete
Select the row in table and try to move it up and down
It doesn't happen because rows cannot be selected during the delete mode

What is the expected result?
Expected result is that there should be a way to select the rows in the delete mode so that we can move the rows in the delete mode
What happens instead?
If we press the row then it wont get selected so I wont be able to move it up and down. There should be a way to trigger the press event in case we press the row when the table is in delete mode.
Any other information? (attach screenshot if possible)
https://experience.sap.com/fiori-design-web/responsive-table/
I went through this and its suggested that "Delete is a mode of the responsive table and therefore cannot be used together with single selection or multiselection."  but what if we want to select the row in the table during delete mode and move it up and down.

I am a bit confused by the problem to be honest.
As I've understood correctly, you're trying use "Delete" in combination with Drag & Drop, right?
When changing the mode of both tables to "Delete", you are still able to press on a row and drag it somewhere else, even though selection is not possible.
If you are solely referencing the buttons ("Move Up", etc.), that logic is completely custom. In this case there is a controller function moveUp and moveDown, which moves the items accordingly.
That logic is not part of the Drag & Drop API.
One could overcome this issue, by also providing another button, which switches Delete mode to selection.
But in the end, that is up to the application itself.
Drag & Drop API works as expected (dragging and dropping works) in combination with Delete. And if you'd want to enable the sample coding with Delete mode, to allow for button usage as well, the custom logic would need a modification.
Or am I missing your point?

@DonkeyCo Hi, You have understood it rightly, The problem is not with the drag and drop, like you said we can have a delete button which switches on the delete mode but lets say I want to use move up and move down when the table is in Delete mode then its not possible because I wont be able to select a row to move it up and down.
Issue: The table is in delete mode and I want to select a row to move it up and down, during delete mode this is not possible, is there a way this can be achieved without switching the mode of the table from delete to single select master.

Hello @albertbolt1,
Thank you for sharing this finding. I've created an internal incident DINC0203716. The status of the issue will be updated here in GitHub.
Regards,
Gergana

Hi @albertbolt1,
as already mentioned by @DonkeyCo this 'Move up / down' is a custom implementation.
Based on the API it is not possible to have multiple 'Modes' active at the same time.
This is how the ListBase / Table is actually designed.
What you could do is to add a separate column containing buttons with custom actions you need and leave the mode of the table to 'SingleSelectMaster'.
As there is either a real issue with D&D nor with the Table itself I'm closing this case.
Thank you best regards,
Marco
(SAPUI5 Development)


SUP-1665: v1.0.0 upgrade note on Administrator bound API access tokens & buildkite_pipeline_team resources

Docs(Pipeline/Pipeline Team resources): Upgrade note for v1.0.0 and pipeline.team -> buildkite_pipeline_team conversion with Admin bound API tokens
PR checklist:

[x] docs/ updated
[ ] tests added -> Docs amendment
[ ] an example added to examples/ (useful to demo new field/resource) -> Docs amendment
[x] CHANGELOG.md updated with pending release information

With the current requirement that the upgrade to v1.0.0 (with the intermediate v0.27.0 update) requiring Administrator bound API Access tokens in the process of switchover, amended the upgrade guide to outline this while longer term resolutions are triaged.
Per #445

Looks like I bypassed said template - adjusted with adding terraform-plugin-docs and its deps to mod/associated sum


ratio

i am ratioing your bot

You cant ratio an open src bot + u helped me made it

@XL84 Im gonna close this issue :trollface:


Incorrect Char array type number for portable serialization

Corrected the Type number at FieldType class to be the same as Java. Added read/writeBooleanArray to portable reader/writer.
Fixes https://github.com/hazelcast/hazelcast-cpp-client/issues/230
Fixes https://github.com/hazelcast/hazelcast-cpp-client/issues/236

verify

Test FAILed.

Test FAILed.

verify

verify

verify

Test FAILed.

Test FAILed.

Test PASSed.


Billy/1191 tx designs

Closes #1191
Description: Added the new transactions from tendermint/ui (updated it to fix a moniker bug and layout error: https://github.com/tendermint/ui/pull/63/commits/dd88c5d141a19e8b89771499405f64ffcf0787be)
Refactored modules/blockchain.js and added modules/transactions.js for all current transaction info and ready for future transaction formats.

I agree with removing the dead code. It bloats the files and we can get the code from history again. What do you think?

@fabo sounds good to me
thanks for all the js tips @NodeGuy !
this is still blocked by tendermint/ui PRs and npmjs.com updates
also unresolved how to handle the validator link. Should we just use vue-router in the component library?

sorry can you elaborate?
On Mon, Sep 3, 2018 at 11:05 AM Fabian<EMAIL_ADDRESS>wrote:

@faboweb commented on this pull request.
In app/src/renderer/vuex/modules/transactions.js
https://github.com/cosmos/voyager/pull/1223#discussion_r214620681:

@@ -0,0 +1,123 @@
+let { uniqBy } = require("lodash")

We didn't define a rule for this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cosmos/voyager/pull/1223#discussion_r214620681, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA611GAnNYqsaPx15MaWfEExYKPNT1n1ks5uXPDpgaJpZM4WVoNI
.

yup, they both go to  http://localhost:9080/localhost/staking/validators/{address}
On Mon, Sep 3, 2018 at 11:55 AM Fabian<EMAIL_ADDRESS>wrote:

@faboweb commented on this pull request.
In app/src/renderer/components/wallet/PageTransactions.vue
https://github.com/cosmos/voyager/pull/1223#discussion_r214634689:

@@ -85,7 +82,8 @@ export default {
sort: {
property: "height",
order: "desc"

}

},
validatorURL: "https://explorecosmos.network/validators"

How about ${window.location.hostname}/stake/validators? Will this also
open a new window?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cosmos/voyager/pull/1223#pullrequestreview-151731698,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA611L6QfnvxQ880Uwo26uyyD81XcvLcks5uXPybgaJpZM4WVoNI
.

Should we just use vue-router in the component library?

I would vote yet. The explorer also uses the vue-router.

Follow up #1275

Unbonding delegations are not shown correctly -> blocked on https://github.com/tendermint/ui/pull/64


How to create database using FMDB?

Hi, i want create database using FMDB, but i can't import FMDB in swift
error message : could not build objective-c module 'FMDB'
and how to update FMDB pods? this version its outdate
Thanks

@Koutenshidatshu, if you can't import FMDB in swift you'll have to make a specific module map file or a bridging header to be able to do so. This is not an issue related to this project, so I'm closing this.


Try to fix windows scipy Pyinstaller issue

@garrettmflynn Does this branch fix your specific scipy issue? Solution from: https://saturncloud.io/blog/troubleshooting-scipy-import-error-with-pyinstaller/#:~:text=This error typically occurs because,for PyInstaller to work properly.
You were right that I don't run into the same problem in my environment. Quite strange...

Solution 1 from the suggestion did not work for the deployment version - the file size of the release was also unchanged by the extra flags
Will continue trying other solutions later

When run locally, the configuration options specified here appear to error immediately—so the Pyinstaller command will not even run.
Can you tell if that's happening for the deployment version?


replace zebra-crossing by zxing-wasm

zxing-wasm has two main advantages:

does not rely on a jdk to be installed
handles binary data properly

Thank you so much. I've already searched for a JS based solution for a long time.  Do you know, why some tests are failing?


Meals coordinator role

Originally created by Tom Smyth at 2017-09-11 09:12, migrated from redmine-#7109

Version set to 4.5

By Tom Smyth at 2017-09-24 21:40


torchscript support for DCVv2

Hello!
Allow me to ask for your advice, please.
Situation description: I know that deformable convolution is supported natively in Pytorch since 1.4, but this does not mean DCN may be extracted to a static graph via jit. Moreover, DCN added to Pytorch is version 1, not this one (version two).
Question: Can you confirm I understand the situation correctly and how hard is to add DCNv2 support to torchscript from your point of view?

@IgorDavidyuk Have you added torchscript support?

Any updates?

It seems @IgorDavidyuk  found its answers elsewhere : https://discuss.pytorch.org/t/torchscript-support-for-deformable-convolution-v2/69372


Allow users of ODLM to specify OLM dependencies for the APIs

Summary
Today the ibm-common-service-operator bootstraps the operand-lifecycle-operator-manager as well as a supporting namespacescope operator, among other bootstrapping tasks.
It is told that the users of ODLM must include ibm-common-service-operator and must not include ODLM in their definitions.
This request is to allow the users of ODLM to declare their API and package requirements through OLM.
Details
There are at least two other operators who have adopted ODLM for their deployment architecture:

ibm-management-orchestrator
ibm-aiops-orchestrator

These operators include the ODLM golang library and directly interface with the ODLM APIs in kubernetes.
The deployment architecture for the operands of these operators is based on ODLM as a fundamental component.
If the ODLM APIs do not exist, or are not within the supported range, the operators will panic.
Further, these operators are not yet offered through a bundle format in OLM. What this means is that they are only specifying required APIs in the CSV and are not utilizing the bundle dependencies.yaml for GVK and package type specifications.

@taylormgeorge91
ibm-common-service-operator also gets and updates OperandConfig and OperandRegistry. Currently, we use api.Reader to avoid panic.
I believe we can't use customresourcedefinitions.required to explicitly claim the dependency since OLM will deploy an ODLM in the namespace of the operator, which is not expected.
Do you know if there is any mechanism from OLM to handle the operator in the pending status until the required CRD exists instead of just creating it?

@horis233 That is a good point but not something I think OLM supports

Do you know if there is any mechanism from OLM to handle the operator in the pending status until the required CRD exists instead of just creating it?

I can ask the OLM guild and see if that is of any consideration.
We could create an init container to validate, but we would really like to use the OLM dependency management for required APIs as that is the accepted norm.
I will get a log of the error.

@taylormgeorge91
Please check if the nativeAPI field in the CSV can fulfill the requirement.
https://olm.operatorframework.io/docs/tasks/creating-operator-manifests/#nativeapis-recommended

Thanks @horis233 ! I'll give it a go, looks like what we want.

Works well, thanks again.


[iOs] haptic feedback does not working if mic on

Hello,
Is there any solution to use haptic feedback when mic is active on iOs ?
React-Native: 0.63.4
expo: 42.0.1
`const options = {
enableVibrateFallback: true,
ignoreAndroidSystemSettings: false,
};
ReactNativeHapticFeedback.trigger("selection", options);
`
Thanks,

Will check for the circumstance

I had the same experience using in conjunction with react-native-audio-recorder-player, and found that wrapping my record function in a setTimeout resolved the issue:
            ReactNativeHapticFeedback.trigger('impactHeavy');

            setTimeout(() => {
              startRecording();
            });

In short: can be enabled, read below.
Natively on iOS haptic feedback is disabled during audio recording sessions not to interrupt it. Still, you can enable with
if #available(iOS 13, *) {                 do {                     try AVAudioSession.sharedInstance().setAllowHapticsAndSystemSoundsDuringRecording(true)                 } catch {}             }
inside the startRecording function of native RNAudioRecorderPlayer.swift file.


Powershell Instructions

Powershell Connection directions, or a link to them, would be appreciated.

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

ID: 187dd8b0-3b85-a09b-bdcc-dfbe8bef11a5
Version Independent ID: 187dd8b0-3b85-a09b-bdcc-dfbe8bef11a5
Content: Manage schedule owners for shift management - Microsoft 365 for frontline workers
Content Source: microsoft-365/frontline/schedule-owner-for-shift-management.md
Service: microsoft-365-frontline
GitHub Login: @LanaChin
Microsoft Alias: v-lanachin

@IdahoWill Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/12246
Once the author approves, the changes will be live.
Thanks
Sri


using fftconvolver for vst binary

hi!
i am trying to find a suitable partioned convolution library for usage in vst plugins.
gpl forbids to distribute vst binaries as they are compiled using the non-free steinberg vst sdk.
i wanted to ask if you are ok if somebody uses your code in a gpl project and offer vst binaries of this project.
thanks,
matthias

Hi matthias,
sorry for not answering earlier, but I was more in making music than in programming music software... ;-)
Yes, it's perfectly fine for me if you use FFTConvolver in your VST plugin and also distribute VST binaries of it. I was not aware of this limitation of this license.
Do you know of any more appropriate license for this use case? Basically it's no problem for me to switch to a slightly more liberal one regarding this.
I've seen that your from Regensburg. I'm from Munich and visiting Regensburg from time to time because quite some friends live there. :-)
Servus, Uli

Hi Uli,
thanks for the answer :) Musician and code writer.. nice :)
In the meantime I did reprogram the convolution engine so the question is not really relevant for me anymore.
Wanna meet in Regensburg? Let's get in contact via email<EMAIL_ADDRESS>Ciao, Matthias

Alright, so I leave the license for now as it is, and it's no problem for me if someone distributes VST (or other) binaries.
Please feel free to contact me if the license should be adapted somehow.
Regards, Uli

I've changed the license to MIT now... :-)


Access Management for Kubernetes operator

Hi,
Is there a way in clickhouse on Kubernetes operator to uncomment access_management in users.xml file?
And what is the best way to do that?

look to kubectl explain chi.spec.configuration.files and kubectl explain chi.spec.configuration.users
spec:
  configuration:
    files:
      users.d/access_management.xml: |
         <clickhouse><users><default><access_management>1</access_management></default></users></clickhouse>

you shall carry itself about move RBAC objects during change cluster layout (scale-up)

Thank you Slach it worked


ERROR - App matching query does not exist

Hello,
I was trying to install app 'cartoview_arcgis_feature_server' . While checking on try.cartoview.net , the new name is CartoServer. Both are the same I think.

hello @lolob
our apps installer is alpha version
to fix this error please create app object under APP_MANAGER/Apps section then click  add app app button    in admin panel like in screenshots open apps.yml and add record for cartoserver like this:
- active: true
  name: cartoview_arcgis_feature_server
  order: 10


Expose StencilObject

Description
Exposes StencilObject as gt4py.StencilObject for typing info.
Resolves #613.

bors try


Offset on uniform buffer?

Question / Feature request
Buffer.bind_to_uniform_block takes exactly one argument. Is there a way to bind it with an offset, like VertexArray.bind? The OpenGL docs seem to mention something in this direction should be possible:

If you bind a uniform buffer with glBindBufferRange, the offset field of that parameter...

Version info
python -m moderngl

moderngl 5.0.7
--------------
vendor: Intel
renderer: Intel(R) HD Graphics 4000
version: 4.0.0 - Build <IP_ADDRESS>85
python: 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:04:45) [MSC v.1900 32 bit (Intel)]
platform: win32
code: 400

Hi!
Thank you for the feature request!
Please take a look at this PR.
You can test it out as follows:
pip install -U https://github.com/cprogrammer1994/ModernGL/archive/ubo-offset.zip

I think Shader Storage Buffers Objects should be bound the same way.

Great! Tried it and it works wonders.

What is the moderngl way to read a value like GL_UNIFORM_BUFFER_OFFSET_ALIGNMENT ? I was trying to add some tests in tests/test_uniform_block.py but can only make it work if this number is known (which may differ per device).

There should be an entry in Context.info implemented here.
I will add it to the PR.

Added a new entry to Context.info
>>> import moderngl
>>> ctx = moderngl.create_standalone_context()
>>> ctx.info['GL_UNIFORM_BUFFER_OFFSET_ALIGNMENT']
16


fixed 2 issues

Fixed html for disabled colorize (issue #73)
Fixed timezone handling for events during change from daylight saving time back to standard time

travis test red, have restarted them ... mysterious

I think it was a timing issue, because the second run was successful. But nevertheless it founds a possible problem.

I will soon remove the file ".settings/.gitignore" from this PR and then merge ... just that you know ... maybe setting .settings in global gitignore is a good idea?
Thank you very much!!

Thank you, will go out now. I will also post in forum (hopefully I find all threads)


IntersectRay always returns shape_idx=0

Version: Godot 3.0 beta1
As can be seen here, ray casting implementation always sets shape index to 0, yielding incorrect results.

CC @AndreaCatania


false positive in no-unused-prop-types

I added a test case to show a false positive of the rule no-unused-prop-types.
It happens when using both nextProps and this.props in a lifecycle method.
The prop-types rule does complain (as it should) when not specifying a propType for foo.
I tried to dive into the code and find the difference (and understand why those 2 rules aren't based on the same "parser") but I got lost.

fixed in #1106


Unable to use Testnet

Following the steps in the readme, i've added wallet providers to app:
  const providers = useInitializeProviders({
    providers: [
      { id: PROVIDER_ID.DEFLY, clientStatic: DeflyWalletConnect },
      { id: PROVIDER_ID.PERA, clientStatic: PeraWalletConnect },
      { id: PROVIDER_ID.DAFFI, clientStatic: DaffiWalletConnect },
      { id: PROVIDER_ID.EXODUS }
    ],
    nodeConfig: {
      network: 'testnet',
      nodeServer: 'https://testnet-api.algonode.cloud/',
      nodeToken: '',
      nodePort: '443'
    }
  })
...
  return (
    <WalletProvider value={providers}>
      <RouterProvider router={router} />
    </WalletProvider>
  )

Then, on a page i have:
import { useWallet,
  DEFAULT_NODE_BASEURL,
  DEFAULT_NODE_TOKEN,
  DEFAULT_NODE_PORT } from '@txnlab/use-wallet'
const algodClient = new algosdk.Algodv2(DEFAULT_NODE_TOKEN, DEFAULT_NODE_BASEURL, DEFAULT_NODE_PORT)
...
const { activeAccount, activeAddress, signTransactions, sendTransactions } = useWallet()

const suggestedParams = await algodClient.getTransactionParams().do();
const ptxn = algosdk.makePaymentTxnWithSuggestedParamsFromObject({
        from: activeAddress,
        suggestedParams,
        to: constants.receiveWallet,
        amount: algosdk.algosToMicroalgos(total/algoInUsd/1000),
        note: new Uint8Array(Buffer.from(noteKey)),
      });
try {
      const encodedTransaction = algosdk.encodeUnsignedTransaction(ptxn)
      const signedTransactions = await signTransactions([encodedTransaction])
      const waitRoundsToConfirm = 4
      const { id } = await sendTransactions(signedTransactions, waitRoundsToConfirm)

      console.log('Successfully sent transaction. Transaction ID: ', id)
} catch (error) {
      console.log("Couldn't sign txn", error);
}

Testing with Pera connected using Pera Web, and when signing that tx i'm sent to Pera which shows TESTNET since i have the node set to testnet, i get:
Network mismatch
Your wallet is connected to a different network to this dApp. Update your wallet to the correct network (MainNet or TestNet) to continue.

Is there something i'm missing or overlooked?  I have connected to Pera using essentially the demo code (with ui formatting), with testnet set, and restarted the app a few times but i cannot gewt it to connect to testnet.
Any help is much appreciated.

More Info:
Your readme under 'Signing and Sending Transactions' states:
import {
  useWallet,
  DEFAULT_NODE_BASEURL,
  DEFAULT_NODE_TOKEN,
  DEFAULT_NODE_PORT
} from '@txnlab/use-wallet'

const algodClient = new algosdk.Algodv2(DEFAULT_NODE_TOKEN, DEFAULT_NODE_BASEURL, DEFAULT_NODE_PORT)

for signing txns, but those DEFAULT* comes from [index.ts] export * from './constants' which are the hard coded defaults, which default to mainnet!!!  If you want to use the network details from nodeConfig i.e. TESTNET, then you need to do something like:
  const algodClient = clients?.[activeAccount?.providerId]?.algodClient || null

to get a pre-initialised algod client loaded with the nodeConfig values.  Otherwise you get the default mainnet values!
Might be a good idea to complete the Node configuration section by stating that in order to use the values from nodeConfig, you need to grab the pre-loaded algod client from the provider in use, rather than the earlier example of using new algosdk.Algodv2() with the DEFAULT*s from @txnlab/use-wallet?

A simpler approach would be to define your own constants for NODE_TOKEN, NODE_BASEURL, and NODE_PORT and pass them to both nodeConfig and your app's algod client instance:
import algosdk from 'algosdk'
import {
  NODE_BASEURL,
  NODE_TOKEN,
  NODE_PORT
} from '@/constants'

const algodClient = new algosdk.Algodv2(NODE_TOKEN, NODE_BASEURL, NODE_PORT)

const providers = useInitializeProviders({
  providers: [...],
  nodeConfig: {
    network: 'testnet',
    nodeServer: NODE_BASEURL,
    nodeToken: NODE_TOKEN,
    nodePort: NODE_PORT
  }
  algosdkStatic: algosdk
})

Yes that is another option.  See i'm new to the project, and when integrating it as per the readme, i'm led to believe that setting nodeConfig will also set the network for the Signing and Sending Transactions section which i previously implemented.
Some kind of note in the readme docs would have helped me to understand this, and thus implement either of our suggestions.

I can see how the transaction example code could be confusing.
In the code examples prior to the transaction example, nodeConfig is not set and the default configuration is used. In that scenario, the library's DEFAULT_* variables can be used to instantiate your app's algod client. But that's not a very good way to demonstrate using the library, and there's no explanation about why that works.
The recommended approach would be the example I provided above: passing the same variables to your algod client instance and the nodeConfig. They should match. I'll update the README and transaction example code.
Thank you @Ataye, really appreciate your feedback!

No worries.  I was planning to put together something similar to this project ala Rainbowkit etc, but you have already done the hard work so appreciate it and happy to support :)
Also, just FYI, Exodus doesn't support testnet it seems!


Debugger is not stopping/showing at the breakpoint in node v6.1.0

VSCode Version: Alpha
OS Version: OSX 10.11.5

Steps to Reproduce:
Follow the steps in smoke test - Smoke Test Debugging Javascript section

Open VS code with VSCode-Smoketest-Express project
Go to debug view
Put a break point in index.js file at line 6
Start the application
In the browser open the application page http://localhost:3000/

Expected: Debugger should stop at the break point and show all necessary debug information like call stack etc
Actual: Debugger stops but there is no visual representation that it is actually stopping, and no necessary info is shown.
Additional Information:
See the attached movie
http://g.recordit.co/0UV4elT3Cq.gif

It worked when I tested first time and later it was breaking sometimes as above. I used keyboard short cuts to stop and start the server. I do not know if it is something to do with this

@weinand FYI

@sandy081 what version of node are you using?

@weinand its v6.1.0

@sandy081 I was not able to reproduce this on OS X 10.11 and node 6.1. The error that you see in the CALL STACK view is a V8 issue in node v6.x (https://github.com/node-inspector/node-inspector/issues/864).
VS Code has a workaround for it, but that does not seem to work as reliably for you as for me. We will have to wait until the real fix in V8 appears in node v6.

I am seeing this behavior and I am running node v 4.4.3.  I am seeing Code say "PAUSED ON BREAKPOINT" but I am not seeing any indication of the breakpoint or the data around it.  The strange thing is that on some endpoints (express endpoints), the breakpoints work fine, and others not.  I am on OSX 10.11.4.

@jnystrom what version of VS Code are you using?

I am using the latest Insiders version.

I just tested it in the latest released version and I still see the issue.  I can add breakpoints that hit, during the startup of my node app, but when I hit this express 'PUT' endpoint, I cannot see any breakpoints getting hit.  I do see them getting hit on a 'GET' endpoint.  I am possibly using a newer version of NPM that is newer than the version of node I am using.

I have that problem too since upgrading vscode to 1.0.
I use vscode on windows, linux and mac with node 5.x and I get that behaviour on each platform ever since upgrading to 1.0
In case of the linux machine I also tried node 4.x, 5.x and 6.x and it did not make any difference.
I then reverted vscode back to a 0.9x version with node 6.x and it worked again.
So there must be something wrong with the 1.0 release as opposed to a possible node 6.x incompatibility.
I also tried the 1.2.0 insider but the problem still persists there.

The original problem is a symptom of a specific v8/node v6 issue  (https://github.com/nodejs/node/pull/6928) which has been fixed in node 6.2.1.
The other problems occur in any version and unrelated to this issue (even if they show the same symptoms).
@sandy081 please verify that node 6.2.1 fixes your problem.

@weinand can I get a link to the Issue(s) that have to do with these same symptoms?

@jnystrom https://github.com/Microsoft/vscode/issues/6164

just fyi, I updated to node 6.2.1 but the debugger is still not showing the breakpoint.
I tried it with 1.1.1 and and the most recent insider as of today: 1.2.0 (7ccb21d7e7256a7d42f3dda8b2d3721b8e59724f)

@tmkn this bug is about that a breakpoint is hit but that the call stack view stays empty. Is this really the problem you are seeing?

Yes, I set a breakpoint but the stack view stays empty, I can press continue and by doing that the program then finishes correctly.
I just looked at the attached gif again and it behaves exactly the same however my call stack stays empty(there's no "No callstack available" message like in the gif).
Also certain breakpoints work, it's just those that in my case are set inside a handlebarsjs registerFunction won't show any information.
//breakpoints here work fine
hbs.registerHelper("include", () => {
    //any breakpoint here triggers this behaviour
});

If wanted I can try to isolate the behaviour to a short snippet for easy reproduction.
As I said it appeared ever since I upgraded to 1.0 regardless of os or node version.

I can confirm the same issue here. The breakpoint is hit and the application pauses, but the call stack view is empty with an error message: "No call stack available (Cannot read property 'indexOf' of undefined)."
I'm using node 6.2.1 and vscode 1.2.0

@tallakh do you have a (ideally small) reproducible case that I can investigate?

I'm experiencing the same issue. The debugger stops, but it doesn't look like it's connected to any breakpoint and the call stack view is empty. I have tried different node versions but the problem persists. Using Visual Studio Code 1.2.0
I have also verified that the same breakpoints works in other IDE's like JetBrains WebStorm for instance.

@jornki it would be great if you could provide a reproducible case that I can investigate.

@tallakh you are hitting https://github.com/Microsoft/vscode/issues/7481

@weinand Thanks, looking forward to a fix.

@tallakh the fix for #7481 is available in the next Insider build.

This bug still occurs to me with the latest Insiders builds and the latest Node.js

@rmagen so when hitting a breakpoint you are seeing this message in the CALL STACK view?

Yes.
I actually got it fixed just now by (I think) updating some babel libraries.
Thanks!

The latest release of VS Code on both Windows and Ubuntu (with latest nodeJS 7) is still having this issue. It is extremely hard to reproduce and only seems to happen once the code base exceeds some complexity.

I'm facing this issue, node version 6.9.3 and VS code version 1.10.2, When I put a breakpoint at the beginning of the code I can see the yellow bar and I can step into and over the code, however after using Promises and generators in different places in the code, the debugging stops to work. the application seems to pause where the breakpoint is set, but I can not inspect variables or step into or over the code

Please try the Insiders build.

Hi @weinand, I have installed the latest version of VS Code Insiders, but unfortunately it is still not working, worth mentioning that I'm not using Electron, and the debugging protocol that I'm using is "legacy", not "inspector".

I'm with the insider using inspector and this happens mostly when using bluebird. I'm in node 7.6.

@waelemara What is the exact problem you are seeing?

I have a very similar issue with a complex Promise chain
    {
      "type": "node",
      "request": "launch",
      "protocol": "inspector",
      "name": "Update Chains",
      "program": "${workspaceRoot}/scripts/updateChains.js"
    }

@shamoons do you have a reproducible snippet that you can share with us?

Was this ever resolved?

Yes, pls see: https://github.com/Microsoft/vscode/issues/6967#issuecomment-223572489


Update upgrade test post-CASSANDRA-12694

CASSANDRA-12694 did slightly change the behavior in that case (for the
better) and updated unit tests accordingly (see the end of
https://github.com/ifesdjeen/cassandra/commit/3b7a2f8479eaafa00d55466fe37e43318b8dadcf,
which is "exactly" the same case) but this upgrade test was missed and
currently fails
(http://cassci.datastax.com/job/cassandra-3.0_dtest_upgrade/lastBuild/testReport/junit/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_0_x_To_indev_3_0_x/static_columns_cas_test/).

I worry this will break earlier versions, but we'll see. +1


The plugin stop working

Hi all,
By April 18, 2017, Symantec will decommission the "Legacy" timestamping service.
(Legacy) RFC 3161 SHA128 Timestamp Service:
https://timestamp.geotrust.com/tsa
To support business continuity for our customers, we have provided the following replacement services.
(New) RFC 3161 Service SHA256:
http://sha256timestamp.ws.symantec.com/sha256/timestamp
In order for me to use it I will need to poin to the new location, otherwise the builds are failing.
Cheers,
Viktor

That link: https://timestamp.geotrust.com/tsa is probably set in adt.project and has nothing to do with your project. Marked as resolved

I believe this needs support for the -tsa option on the packager (I don't see it now)
This would allow us to either set it to the new value (http://sha256timestamp.ws.symantec.com/sha256/timestamp) or "none"

exactly, we needs something like:

com.yelbota.plugins
adt-maven-plugin
<IP_ADDRESS>

package

 THIS ONE
3.9
bundle

It is possible to pass parameter to command goal instead of using the package goal. But it is very fiddly and as Viktor mentioned above, the configuration is better option.
<execution>   <id>adtCommand</id>   <goals>     <goal>command</goal>   </goals>   <configuration>     <arguments>-package -tsa none -storetype pkcs12 -keystore ${basedir}\yourcertificate.p12 otherArgumentsAndParametersLikeCompilationFilesAndAssets</arguments>   </configuration> </execution>


Add BluetoothLeManager and BluetoothManager

As we are writing more and more apps that require Bluetooth functionality, it is better to write some standard Bluetooth(Le) Managers instead of always start writing them from scratch.

@SibertSchurmans What do you think, you want to take a look into this with me, as we both have written some sort of manager lately?

Yes! I'm curious on how our approaches differ and what the best implementation can be 😄
Let me know when you want to check it out! ( Maybe with the rest of circle android on an evening? )


Fix support of datadog exporter for krakend-opencensus

Even tho https://github.com/devopsfaith/krakend-opencensus support datadog, I couldn't use it from docker-CE.
We need the init() of datadog exporter to run to be able to use it.
Thus we need to import the exporter, as other exporter.

Hi @tgermain , and welcome to the KrakenD Community!
We are still pending of create a new krakend-opencensus release that includes the DataDog exporter and update the deps of KrakenD-CE to be able to add the import.
I'll leave this PR open until we tag a new opencensus version so you can update the deps.

+1 we need this feature for our project, when this will be added?

it's already included into the branch 1.2.0-dev, ready to be released


Add a transform that takes a Relation and clips the L2 or L1 norm of all protected entities of a column

Assume a column defines the protected entity for now

Find the relation(s) to clip: this can be the innest Relation::Reduce` that is not PEP. When we have joins, We may have several relations to clip.

Rescale the columns. Most of the estimators can then be rewritten as sums.

clipping_qrlew.pdf

For clipping, we want a primitive that calculates the norm of a column of values according to another column of group by and a column of PEID.

There is a base of the normed vector space: the groups of the group by.

A norm for each PEID.

The coordinates of each PEID on the base: the column of values.


mermaid installation on debian

hello community,
i have installation issue's with mermaid package.
I'ved worked through several stages of problems but doesn't have any ideas for the last error Invalid file descriptor to ICU data received..
any ideas?
Systeminfo
I'm using this docker image docker run --rm -it robie2011/gitlab-asciidoctor bash
root@f3216f0534e8:/# uname -a
Linux f3216f0534e8 4.9.87-linuxkit-aufs #1 SMP Wed Mar 14 15:12:16 UTC 2018 x86_64 GNU/Linux

Installation
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg |  apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
apt-get update
apt-get install -y nano yarn
yarn global add mermaid mermaid.cli
nano test.mmd
# todo: add sample diagram code

sample diagram code:
graph LR;
    Generate-->Sign;
    Sign-->Transfer;
    Transfer-->Validate;
    Validate --> Clean;

First Error - missing dependencies on system level
root@f3216f0534e8:/# mmdc -i test.mmd -o test.png
(node:933) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
/usr/local/share/.config/yarn/global/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/usr/local/share/.config/yarn/global/node_modules/puppeteer/lib/Launcher.js:255:14)
    at Interface.helper.addEventListener (/usr/local/share/.config/yarn/global/node_modules/puppeteer/lib/Launcher.js:244:50)
    at emitNone (events.js:111:20)
    at Interface.emit (events.js:208:7)
    at Interface.close (readline.js:370:8)
    at Socket.onend (readline.js:149:10)
    at emitNone (events.js:111:20)
    at Socket.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
(node:933) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:933) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Fixing + reinstall mermaid:
apt-get install -y gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget

Root-User Issue
root@f3216f0534e8:/# mmdc -i test.mmd -o test.png
(node:2843) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
[0413/071446.332564:ERROR:zygote_host_impl_linux.cc(88)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/usr/local/share/.config/yarn/global/node_modules/puppeteer/lib/Launcher.js:255:14)
    at Interface.helper.addEventListener (/usr/local/share/.config/yarn/global/node_modules/puppeteer/lib/Launcher.js:244:50)
    at emitNone (events.js:111:20)
    at Interface.emit (events.js:208:7)
    at Interface.close (readline.js:370:8)
    at Socket.onend (readline.js:149:10)
    at emitNone (events.js:111:20)
    at Socket.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
(node:2843) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2843) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code

Execute as non-root user
root@f3216f0534e8:/# useradd doc
root@f3216f0534e8:/# su doc
$ mmdc -i test.mmd -o test.png
(node:2862) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
[0413/071618.696488:ERROR:icu_util.cc(133)] Invalid file descriptor to ICU data received.
[0413/071618.696630:FATAL:content_main_delegate.cc(53)] Check failed: false.
#0 0x564e86baab0c base::debug::StackTrace::StackTrace()
#1 0x564e86bc3780 logging::LogMessage::~LogMessage()
#2 0x564e84f4cd23 content::ContentMainDelegate::TerminateForFatalInitializationError()
#3 0x564e868e5deb content::ContentMainRunnerImpl::Initialize()
#4 0x564e868efb72 service_manager::Main()
#5 0x564e868e4f14 content::ContentMain()
#6 0x564e8a9f49b9 headless::(anonymous namespace)::RunContentMain()
#7 0x564e8a9f4a42 headless::HeadlessBrowserMain()
#8 0x564e868ecf9d headless::HeadlessShellMain()
#9 0x564e84f4b1ac ChromeMain
#10 0x7f9fb78f72e1 __libc_start_main
#11 0x564e84f4b02a _start

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/usr/local/share/.config/yarn/global/node_modules/puppeteer/lib/Launcher.js:255:14)
    at Interface.helper.addEventListener (/usr/local/share/.config/yarn/global/node_modules/puppeteer/lib/Launcher.js:244:50)
    at emitNone (events.js:111:20)
    at Interface.emit (events.js:208:7)
    at Interface.close (readline.js:370:8)
    at Socket.onend (readline.js:149:10)
    at emitNone (events.js:111:20)
    at Socket.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
(node:2862) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2862) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This is a mermaid.cli issue, Since you have created an issue there, I want to close this one.


BUG: date parsers use different tz offsets

xref #12060
@jreback - my thought was to just convert the dateutil timezone offset (tzoffset) to a pytz offset?
# dateutil
In [1]: pd.Timestamp('2013/01/01 00:00:00+09:00')
Out[1]: Timestamp('2013-01-01 00:00:00+0900', tz='tzoffset(None, 32400)')

# C parser
In [2]: pd.Timestamp('2013-01-01 00:00:00+09:00')
Out[2]: Timestamp('2013-01-01 00:00:00+0900', tz='pytz.FixedOffset(540)')

In [3]: pd.date_range('2013-01-01 00:00:00+09:00', '2014/01/01 00:00:00+09:00')

TypeError                                 Traceback (most recent call last)
<ipython-input-3-d34c322923bc> in <module>()
----> 1 pd.date_range('2013-01-01 00:00:00+09:00', '2014/01/01 00:00:00+09:00')

...

TypeError: Start and end cannot both be tz-aware with different timezones

you might want to make a slightly different error message. But its still a TypeError (even if they mean exactly the same tz). We don't have anywhere where we allow mixing of timezones like this. (and I dont' think we should).

just to be clear I didn't think that date_range should work as is - question is on the parsing - if it falls back to dateutil should it really be a different tz offset?
This popped up in the tests in #12060 - if the iso8601 parser is more flexible, it's somewhat easy to have two similar looking dates, but only 1 hits the C parser.  There it was:
date_range('2013/1/1 0:00:00+9:00', '2016/1/1 23:59:59+09:00')

oh I c. so we fallback to dateutil to parse and thus it generates a dateutil tz offset.
is no leading 0 on the offset not ISO8601? (e.g. +9:00), while (+09:00) ISO?

Yeah, that's the issue.  Though looking at again, I suppose I could also have the ISO parser handle times without leading 0s, I think it's unambiguous as long as the : separators are present.

we can deal with issue separatly (e.g. parsing leading/lacking 0's for the tz's)


Test Issue

Summary:
Summarise your issue in one sentence (what goes wrong, what did you expect to happen).
Steps to reproduce:
How can we reproduce the issue?
Expected behaviour:
What did you expect the app to do?
Observed behaviour:
What did you see instead?  Describe your issue in detail here.
Logcat for the issue
Provide logs for the crash here
Device and Android version:
What make and model device (e.g., Samsung Galaxy S3) did you encounter this on?  What Android
version (e.g., Android 4.0 Ice Cream Sandwich or Android 6.0 Marshmallow) are you running?  Is it
the stock
version from the manufacturer or a custom ROM?
Screenshots:
Can be created by pressing the Volume Down and Power Button at the same time on Android 4.0 and higher.

I would like to work on this by opening a new issue for one of the tasks on the GCI portal but it is not opened here on the gtihub repo page @jddeep @SaumyaSingh1 @abhijitramesh @edcable

Here is the task - https://codein.withgoogle.com/dashboard/task-instances/6695551769247744/

@edcable @luckyman Why is this task not published on the GCI portal tasks section? If it is can you please share the link asap?

@PiyushSharma99 This is not a task, it was opened for other purposes.


Changes in the return type of the gRPC streaming error

In the gRPC standard library(v0.7.6), the return stream type was,
stream<anydata, error?>

Due to this(https://github.com/ballerina-platform/ballerina-lang/issues/27916) language change, it has now changed to,
stream<anydata, error>

Fixed in https://github.com/ballerina-platform/module-ballerina-grpc/pull/99/commits/3d1946640c9e5c758e0d97837774218c9d9c6524 and https://github.com/ballerina-platform/module-ballerina-grpc/pull/99/commits/106e94b05b82bbb2d8bf0ee08f414287d27eafe8

Fixed in https://github.com/ballerina-platform/module-ballerina-grpc/pull/99/commits/3d1946640c9e5c758e0d97837774218c9d9c6524 and https://github.com/ballerina-platform/module-ballerina-grpc/pull/99/commits/106e94b05b82bbb2d8bf0ee08f414287d27eafe8


fix(status): concurrent BasicStatus creation

This change adds concurrent BasicStatus creation, maintaining the order
of status output.

What does this do / why do we need it?
It reduces the time taken by status.
Before:
real    0m16.092s
user    0m0.408s
sys    0m0.394s

After:
real    0m1.777s
user    0m0.411s
sys    0m0.339s

What should your reviewer look out for in this PR?
Correctness of concurrency code.
Do you need help or clarification on anything?
~Some help with the detected race condition.~
Which issue(s) does this PR fix?
Related to https://github.com/golang/dep/issues/1008 , making status more verbose on failures.

Looks like you sorted out the concurrency.
Regarding error handling, would it still be worthwhile to output as much as possible in the event of an error, rather than only logging errors returning?  The work is still being done either way, and partial success can still be informative.

Regarding error handling, would it still be worthwhile to output as much as possible in the event of an error, rather than logging errors and suppressing results? The work is still being done either way, and partial success can still be informative.

Yeah, that sounds reasonable.

What if errored items were still displayed inline, but indicated error somehow? (probably in addition to separate logs, since we don't want to cram messages into the table). Then there would be no mistaking the tail of the output for a false positive, with the errors interleaved.
Or perhaps simplest is best, what if the error output just came last?

@jmank88  So I thought about it and even prototyped the idea.
Right now, if status is run offline, none of the network errors are logged. Or none of the errors are logged at all. I think it would be good to log the errors in verbose mode and let the user know that something failed in non-verbose mode.
 Run `dep status -v` to see the error messages.
failed to fetch updates

NOTE: the LATEST field is marked unknown, which is like an inline indication that something wrong happened. And a message at the bottom about how to view the errors.
I'll push the commit with these changes.
Could we link the final message with the unknown tag little more directly? Something like:
The statuses of %d projects are unknown due to errors. Rerun with `-v` to see details

So I added the unknown count too.
The status of 2 projects are unknown due to errors. Rerun with `-v` flag to see details.
failed to fetch updates

And created 2 different error channels for different error types. Error due to failure in listing packages (errListPkgCh) and error due to failure in listing versions(errListVerCh).
Added 3 errors errFailedUpdate, errFailedListPkg and errMultipleFailures. Only errFailedUpdate would print the result with unknown data.

@jmank88 thanks for spending so much time on this 😊


Bot is “resetting” every day

What's your nodejs Version.
17.7.1
What's the version you downloaded the bot?
10.3.
Desktop

• OS: Windows
• Version: Windows 11

Additional context, text and screenshots!

Every day the bot is someway “resetting”. So if I the other day make a welcoming channel or a fact of the day, the next day the setup system will be “gone”. The same happens to the ai chat, so every day I need to register it as an ai chat again.

Nope
Your databases are getting deleted every day.
make sure that ur host is not deleting sqlite files.
Note: Replit does that, so don't use replit.
There is a reason, why i don't suggest to use replit
if you want a good vps server hosting check out: https://bero.milrato.dev (--> SSD PACKETE) and use code milrato


Worker fails with exception if none of the new exposed environment variables are set

Checked out the most recent changes and attempted to run the worker without setting any of the new environmental variables such as ENV_VARS_URL (e.g. http://someUrl/config, default: null)
ENV_VARS_RELOAD_RATE (defaullt 15000), etc.
When worker is invoked, the following exception is raised:
java.lang.RuntimeException: Could not load variables from 'null': URI with undefined scheme
	at io.zeebe.http.EnvironmentVariableProvider.getVariables(EnvironmentVariableProvider.java:91) ~[classes/:na]
	at io.zeebe.http.HttpJobHandler.handle(HttpJobHandler.java:57) ~[classes/:na]
	at io.zeebe.http.ZeebeHttpWorkerApplication.handleFooJob(ZeebeHttpWorkerApplication.java:62) ~[classes/:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
	at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
	at io.zeebe.spring.client.bean.MethodInfo.invoke(MethodInfo.java:31) ~[spring-zeebe-0.7.1.jar:0.7.1]
	at io.zeebe.spring.client.config.processor.ZeebeWorkerPostProcessor.lambda$null$1(ZeebeWorkerPostProcessor.java:49) ~[spring-zeebe-0.7.1.jar:0.7.1]
	at io.zeebe.client.impl.worker.JobRunnableFactory.executeJob(JobRunnableFactory.java:44) ~[zeebe-client-java-0.21.1.jar:0.21.1]
	at io.zeebe.client.impl.worker.JobRunnableFactory.lambda$create$0(JobRunnableFactory.java:39) ~[zeebe-client-java-0.21.1.jar:0.21.1]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[na:na]
	at java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264) ~[na:na]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java) ~[na:na]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
Caused by: java.lang.IllegalArgumentException: URI with undefined scheme
	at java.net.http/jdk.internal.net.http.common.Utils.newIAE(Utils.java:244) ~[java.net.http:na]
	at java.net.http/jdk.internal.net.http.HttpRequestBuilderImpl.checkURI(HttpRequestBuilderImpl.java:79) ~[java.net.http:na]
	at java.net.http/jdk.internal.net.http.HttpRequestBuilderImpl.uri(HttpRequestBuilderImpl.java:71) ~[java.net.http:na]
	at java.net.http/jdk.internal.net.http.HttpRequestBuilderImpl.uri(HttpRequestBuilderImpl.java:43) ~[java.net.http:na]
	at io.zeebe.http.EnvironmentVariableProvider.refreshM2mToken(EnvironmentVariableProvider.java:132) ~[classes/:na]
	at io.zeebe.http.EnvironmentVariableProvider.createHttpRequest(EnvironmentVariableProvider.java:102) ~[classes/:na]
	at io.zeebe.http.EnvironmentVariableProvider.getVariables(EnvironmentVariableProvider.java:65) ~[classes/:na]

I am also able to duplicate the problem by commenting out these lines in the unit test:
@SpringBootTest(properties = {
    "ENV_VARS_URL=http://localhost:8089/config", "ENV_VARS_RELOAD_RATE=0",
    "ENV_VARS_M2M_BASE_URL:http://localhost:8089/token", "ENV_VARS_M2M_CLIENT_ID:someClientId", "ENV_VARS_M2M_CLIENT_SECRET:someSecret", "ENV_VARS_M2M_AUDIENCE:someAudience"})

If these are optional configuration parameters, the worker should not fail.
The purpose of these new environment variables is also not quite clear.

Thanks @Klaus-Nji-sp for reporting! Fixed

@berndruecker, thanks for the fix.  I do realize this PR is closed and will open a new issue if this is really an issue but here is a new behavior I have found with the new release.
I now have to create an output mapping with source defined as statusCode and target defined as statusCode to be able to use the value of statusCode returned from the http task in an exclusive gateway.  Did not have to do this before.  Is this desired behavior?

Hey @Klaus-Nji-sp: This is wired - it should actually be totally standard behavior: https://github.com/zeebe-io/zeebe-http-worker/blob/master/src/main/java/io/zeebe/http/HttpJobHandler.java#L69

Yes, it is weird.  I'll keep investigating.  In the meantime, I am ok with the mapping.... but perhaps this behavior should be well understood.

Yeah! Would be awesome if you could investigate a bit more. And also feel free to open an issue for it


Need "sleep 2" before arping otherwise it does not work

We're using pipework with docker and running it from our systemd service unit, which starts the container.
To get it work we had to add a sleep 2 before the arping is done, in this line:
https://github.com/jpetazzo/pipework/blob/ae42f1b5fef82b3bc23fe93c95c345e7af65fef3/pipework#L455

Closing old issues.


Text field's font style is incorrect

Inputs are using Arial font instead of acumen-pro-semi-condensed
https://ui-components-ui-components-dev.os99.gov.ab.ca/?path=/docs/components-form-item--basic

This has been assigned to be worked on during this sprint, Sprint 9.

@ambroseyau Closing this issue as being tested and found to be resolved.


LedgerService as a protocol.

By defining LedgerService as a protocol, secure testability and extensability.

Looks good.


Repository not Found

your HACS integration link seems not working

This is the same for me !!

Indeed it seems to require to this repository to be added in hacs first.
I'll work on this this evening but it might require some time to be fixed because it requires sequential PRs in https://github.com/home-assistant/brands and https://github.com/home-assistant/brands

https://github.com/hacs/default/pull/1529 has been opened, I think the issue will disappear after it will be merged.

Hello
Any update? Is there a link to be able to add the repository manually in HACS?

I'm still waiting for https://github.com/hacs/default/pull/1529. In the meantime you can follow instructions on https://hacs.xyz/docs/faq/custom_repositories/

Hello,
I installed rte-ecowatt with the described method above since hacs is not yet up to date but the interface is not prompting me anything to define client_id and client_secret, should I write it in configuration.yaml ?
Thanks.

You need to go in Settings-> "Devices & Services" as for any integration configured from the UI.

Oh that's right, sorry for the noise, it's configured now, thanks !

Repository has been added and will be published in next hacs version.

Confirmed ! Thanks :)


Example in testing section does not work

Hi!

I start echo server with: cargo r -p echo_server
Then I start the native example: cargo run -p example_app
I see the connection both on client:

and on server:
  Compiling echo_server v0.1.0 (/home/smfx/tmp/ewebsock/echo_server)
   Finished dev [unoptimized + debuginfo] target(s) in 0.34s
    Running `target/debug/echo_server`
Listening on: ws://<IP_ADDRESS>:9001
New client connected

When I send any message nothing happens. I don't see anything in server logs nor in client app.

I checked on rust 1.79 and 1.76.

Hi.
I can confirm this as well. I also tried connecting the example_app to a websocket server other than the echo_server provided in the examples, and it behaves the same. The connection is established, but then messages don't arrive to the server side. If I try an alternative client implementation and connect it to the example echo_server, messages do get through. So I presume something is wrong with the example_app.

This broke with the recent update to tungstenite 0.23:

https://github.com/rerun-io/ewebsock/pull/39

I currently see that the example is working
I guess the fix was https://github.com/rerun-io/ewebsock/pull/45
Conclusion: example_app is working now


files are not submitted in node 14

I see strange behaviour for attached files (both streams & Buffers). Those are ok in node.js up to 13, but ignored in node.js 14.
The same with .submit(), node-fech, got and so on.
Could you check?

Hello @puzrin  did you find any solution?
The same is happening with me, the files are not being submitted,
https://stackoverflow.com/questions/64360831/upload-multiple-images-from-nodejs-to-php-server

no

Seems node 14 fixed at some moment. Not a problem anymore (at least, supertest works).


SSL Conection String for Web App?

I enabled the forced use of SSL in my database server but at the time of backing up and including the connection string I got an error and I was asked to configure the ssl but I couldn't find any documentation on how to do it from the connection string.

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

ID: 77a94e6f-a799-494f-f2f9-171c1804e5f4
Version Independent ID: 0ca5e2ae-5889-61ef-3ce7-5c447f7519a6
Content: Configure SSL connectivity to securely connect to Azure Database for MySQL
Content Source: articles/mysql/howto-configure-ssl.md
Service: mysql-database
GitHub Login: @ajlam
Microsoft Alias: andrela

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

@jvdjeery Do any of these Sample Code snippets not work with your application implementation?
If not, can you please provide some detail on what language you require a connection string example.
Regards,
Mike

The problem is with the connection string that is in the web app.
When I enable SSL forcing on the MySQL server the backups cannot be made.
Using this connection string when creating a backup of the app including the database gives the following error.
String: Database={your_database}; Data Source={host_name}; User Id={your_username}; Password={your_password}
Error Screenshot: https://1drv.ms/u/s!AhxkJ8FhPn1KjIoZ7q0UfMdluLGJEg
How can I add SSL to this connection string for backup??

The App Service backup plan has the non-SSL connection string cached. You essentially need to refresh the backup plan cache with the SSL enabled connection string. This can be accomplished by deleting and recreating the App Service backup plan. This should resolve your issue. Please let me know if this works for you, or if you have additional questions.
Regards,
Mike

@jvdjeery We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
Regards,
Mike

Hi,
I have the same issue.
My web app connection string can't connect via SSL, none of the examples include SSL parameters for a web app connection string


Simplify RBAC

Rbac performs a number of functions.
now:

Builds queries, scopes and acts as a focal point to integrate filters.
Enhances a query to assist with security
Counts records for each of these scopes
Performs in memory filtering and in sql filtering.
Caches ids in the session for some use cases.
It uses empty? and fetches count(*) before performing most queries.

future:

Take a scope as input.
Return a scope as output.
Provide helpers that perform counts and other common methods
Don't use empty? as a flag.
Accept scopes as well as arrays as input
Don't perform rbac on a object_id[] that has already been filtered and stored in the session.

Impact:

Half the time spent in all report screens.
Remove 1/2 to 2/3 of the large queries from all report screens.

See also #5844 for a list of the queries that are targeted. over 1/2 of the queries are slated to go away. (I did not include queries like determine user identity.)

steps

[ ] deprecate filtered and search differences - to inform users

[ ] change filtered(nil) and search(:target => nil) to search all

[ ] change filtered([]) and search(:target => []) to always return empty results

[ ] change search(:target => Scope) to run query even when scope returns a nil

[ ] converge scope, klass, and targets.first.klass - internally just pass around scope

[ ] converge where into scope

[ ] transform id lookups into where clauses

[ ] short circuit object lookup and conversion into ids

[ ] remove :id return option, instead, support pluck(:id)


Spaceship::Tunes::Application latest_version not working anymore

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
We try to find out whether a certain app version has passed review, we read the app state by using Spaceship
Spaceship::Tunes.login(ENV["FASTLANE_USER"], ENV["FASTLANE_PASSWORD"])
Spaceship::Tunes.select_team(team_name: ENV["TEAM_NAME"])
app = Spaceship::Tunes::Application.find(ENV["BUNDLE_ID"])
...

and then got version information with
app.latest_version
That used to work fine - but since there are macOs Apps created automatically in AppStoreConnect when you setup a new app, it suddenly crashes with this message:
Spaceship::UnexpectedResponse: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Not Found"], "info"=>nil}, "statusCode"=>"ERROR"}
There now are versionSets (I can't remember seeing those before)...
Command executed
app.latest_version
Maybe this is connected to issue https://github.com/fastlane/fastlane/issues/17370, I don't know.
Please let me know if the Spaceship::Tunes code part is still in maintenance or if I will have to switch to using the Spaceship::ConnectAPI instead.

Even tried app.latest_version(platform:'iOS') instead of app.latest_version, but same outcome.

I am facing this issue. It worked well 2 days ago

Im getting the same error when using the command
Spaceship::Tunes::Application.create!(name: app_store_name, primary_language: primary_language, sku: sku, bundle_id: bundle_id, company_name: company_name)

Yikes! I'm facing this issue as well. I can't switch over to ConnectAPI as I use multiple development teams. I'm not sure how to get around this. All my builds are failing because I can't find the current version in the store/testflight.
Anyone know of a workaround, that doesn't involve ConnectAPI?

If you look at the spaceship logs in /tmp, the overview endpoint returns but when trying to get version specifics, that's where it fails:
INFO  [12:39:20]: >> GET ra/apps/1524418469/overview: [undefined body]
DEBUG [12:39:21]: << GET ra/apps/1524418469/overview: 200 {"data"=>{"sectionErrorKeys"=>[], "sectionInfoKeys"=>[], "sectionWarningKeys"=>[], "value"=>nil, "adamId"=>"1524418469", "primaryLocaleCode"=>"en-US", "features"=>["PRERELEASE", "PRICING", "GAMECENTER", "SALES_AND_TRENDS", "ANALYTICS", "ARCHIVE"], "appTransferState"=>nil, "localizedMetadata"=>[{"localeCode"=>"en-US", "name"=>"BEATS Barre + Bike"}], "platforms"=>[{"type"=>"APP", "platformString"=>"ios", "everBeenOnSale"=>true, "inFlightVersion"=>{"type"=>"APP", "id"=>"838930204", "version"=>"1.15.9", "state"=>"prepareForUpload", "stateKey"=>"prepareForUpload", "stateGroup"=>"preRelease", "largeAppIcon"=>{"size"=>nil, "width"=>nil, "height"=>nil, "checksum"=>nil, "assetToken"=>nil, "sortOrder"=>nil, "originalFileName"=>nil, "type"=>nil, "url"=>nil, "thumbNailUrl"=>nil}, "supportedHardware"=>["iphone"], "issuesCount"=>0, "hasGrievous"=>false, "isZulu"=>false, "isWatchCombo"=>false}, "deliverableVersion"=>{"type"=>"APP", "id"=>"836934244", "version"=>"1.15.0", "state"=>"readyForSale", "stateKey"=>"readyForSale", "stateGroup"=>"readyForSale", "largeAppIcon"=>{"size"=>117103, "width"=>1024, "height"=>1024, "checksum"=>"76e76c627e925d6457a53e1683a0a7f5", "assetToken"=>"Purple124/v4/a1/ab/39/a1ab3992-082c-3f4a-5ffd-9fe71a4daad7/contsched.juzdzcsg.png", "sortOrder"=>nil, "originalFileName"=>"AppIcon.BEATS-Barre-Bike-0-0-1x~marketing-0-0-0-10-0-0-sRGB-0-0-0-GLES2,0-512MB-85-220-0-0.png", "type"=>"LargeApplicationIcon", "url"=>"https://is1-ssl.mzstatic.com/image/thumb/Purple124/v4/a1/ab/39/a1ab3992-082c-3f4a-5ffd-9fe71a4daad7/contsched.juzdzcsg.png/1024x1024ss-80.png", "thumbNailUrl"=>"https://is3-ssl.mzstatic.com/image/thumb/Purple124/v4/a1/ab/39/a1ab3992-082c-3f4a-5ffd-9fe71a4daad7/contsched.juzdzcsg.png/340x340bb-80.png"}, "supportedHardware"=>["iphone"], "issuesCount"=>0, "hasGrievous"=>false, "isZulu"=>false, "isWatchCombo"=>false}}], "allowedNewVersionPlatforms"=>["osx", "appletvos"], "submittablePlatforms"=>["osx", "appletvos", "ios"], "deleteablePlatforms"=>[], "appStoreUrl"=>"https://apps.apple.com/us/app/beats-barre-bike/id1524418469?ls=1", "analyticsUrl"=>"https://analytics.itunes.apple.com/", "salesAndTrendsUrl"=>"/WebObjects/iTunesConnect.woa/da/jumpTo?page=salesReports", "salesAndTrendsBaseUrl"=>"https://reportingitc2.apple.com/", "isPreOrderLive"=>false, "requiresPreOrderRelease"=>false, "isAAG"=>false, "isFirstParty"=>false, "canCreateAddOn"=>true, "isIAPLimitExceeded"=>false, "hasAppTransferRequest"=>false, "hasValidContract"=>true, "archiveTimestamp"=>nil, "isOrEverWasAKidsApp"=>false, "recurringAddOnCount"=>0, "contractAnnouncements"=>[], "rcIssues"=>[], "everSubmittedAnAddon"=>false, "everSubmittedFreeSubscriptionAddon"=>true, "freeSubscriptionAddonCount"=>0}, "messages"=>{"warn"=>nil, "error"=>nil, "info"=>nil}, "statusCode"=>"SUCCESS"}
INFO  [12:39:21]: >> GET ra/apps/1524418469/platforms/ios/versions/838930204: [undefined body]
DEBUG [12:39:21]: << GET ra/apps/1524418469/platforms/ios/versions/838930204: 404 {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Not Found"], "info"=>nil}, "statusCode"=>"ERROR"}

Weird, this seems to be working fine for me now, nothing changed. Anyone else still experiencing the issue?

Sorry, no - problem still existing in my case!

still facing issue

Working for us again ¯_(ツ)_/¯

Working for us again ¯_(ツ)_/¯

can you please share the code you using for getting latest version?

Sure, in a nutshell

    UI.message "Fetching version numbers from App Store Connect"
    app_store_build_number
    live_version_number = lane_context[SharedValues::LATEST_VERSION]
    latest_testflight_build_number
    latest_testflight_version = lane_context[SharedValues::LATEST_TESTFLIGHT_VERSION]

    UI.message "Downloading live version dsyms"
    download_dsyms(version: live_version_number, username: username)
    if latest_testflight_version != live_version_number then
        UI.message "Downloading latest TestFlight dsyms"
        download_dsyms(version: latest_testflight_version, username: username)
    end

That was not working and then it started working again last night

It used to fail on app_store_build_number but its all good now for us

You should be able to login with the Spaceship::Tunes way and still be able to use the ConnectAPI without actually using an API key. There is no longer the concept of edit_version vs. live_version. You want to look into something like:
bundle exec irb
require "spaceship"
Spaceship::Tunes.login("*************", "("*************")
Spaceship::Tunes.select_team
5
app = Spaceship::ConnectAPI.get_app(app_id: "123456789")
versions = app.get_app_store_versions

Should be a good starting point to test out locally with irb

You should be able to login with the Spaceship::Tunes way and still be able to use the ConnectAPI without actually using an API key. There is no longer the concept of edit_version vs. live_version. You want to look into something like:
bundle exec irb
require "spaceship"
Spaceship::Tunes.login("*************", "("*************")
Spaceship::Tunes.select_team
5
app = Spaceship::ConnectAPI.get_app(app_id: "123456789")
versions = app.get_app_store_versions

Should be a good starting point to test out locally with irb
Spaceship::UnexpectedResponse (The specified resource does not exist - There is no resource of type 'AppsV1' with id ""
got the above error for the following line
app = Spaceship::ConnectAPI.get_app(app_id: "123456789")

Solved the issue I had with Spaceship::Tunes::Application.create! by switching to Spaceship::ConnectAPI

You should be able to login with the Spaceship::Tunes way and still be able to use the ConnectAPI without actually using an API key.

This was the hint that helped - it was a bit rough to get it working, but finally I can read the appstore version and status again. Many thanks!
after logging and team selection in via
Spaceship::Tunes.login("*************", "("*************") Spaceship::Tunes.select_team
I do the following
`app = Spaceship::ConnectAPI::App.find(bId)    #use the new way even if we logged in the old way
unless app.nil?
UI.message "App name #{app.name}, bundleId #{app.bundle_id} FOUND"
    platform = Spaceship::ConnectAPI::Platform::IOS
    filter   = {
      appStoreState: [
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::PREPARE_FOR_SUBMISSION,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::DEVELOPER_REJECTED,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::REJECTED,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::METADATA_REJECTED,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::WAITING_FOR_REVIEW,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::INVALID_BINARY,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::IN_REVIEW,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::READY_FOR_SALE,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::PENDING_APPLE_RELEASE,
        Spaceship::ConnectAPI::AppStoreVersion::AppStoreState::PENDING_DEVELOPER_RELEASE
      ].join(","),
      platform: platform
    }

    v = nil
    app.get_app_store_versions(filter: filter).collect do |version|
      v = version
      UI.message "having version: #{version.version_string} - status: #{version.app_store_state}"
    end

`
... and so on analysing what I got with "v". I do the filtering myself because I want the information about those status', too.
Perhaps this might help somebody later.


No 'step' key in Adam optimizer state when training on PyTorch 1.7

Hello,
I would like to ask a question (and possibly report a potential bug as well).
After upgrading to PyTorch 1.7, I frequently had a memory issue with my trainings:
File "/home/user/.local/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 943, in all_reduce
            work = group.allreduce([tensor], opts)work = group.allreduce([tensor], opts)work = group.allreduce([tensor], opts)
MemoryErrorMemoryErrorMemoryError: : : std::bad_allocstd::bad_allocstd::bad_alloc

This issue happened randomly: for an exact same configuration (same model, training data, and everything else) across different runs: sometimes the job runs well and sometimes there is a memory error or socket timeout error.
After downgrading back to 1.6, I no longer observed this issue. However, I was not able to resume trainings that I had started on 1.7 because of the following error:
File "/home/user/code/fairseq/fairseq/optim/adam.py", line 199, in step
    self.optimizer.step(closure)
  File "/home/user/code/fairseq/fairseq/optim/adam.py", line 199, in step
    state["step"] += 1
        state["step"] += 1KeyErrorstate["step"] += 1
:
'step'KeyError
: KeyError'step':
'step'
    state["step"] += 1
KeyError: 'step'

I have manually checked the checkpoints saved by 1.7 and found that their optimizer states indeed do not have the key step, while the 1.6 checkpoints do.
Could you please tell me how I can continue my trainings on PyTorch 1.6 by resuming from the checkpoints saved by PyTorch 1.7?
Thank you so much in advance for your help!
What's your environment?

fairseq Version (e.g., 1.0 or master): '1.0.0a0+65d88f1'
PyTorch Version (e.g., 1.0): 1.6 and 1.7
OS (e.g., Linux): Linux (RedHat 8)
How you installed fairseq (pip, source): source
Build command you used (if compiling from source): pip install --editable ./
Python version: 3.7.5
CUDA/cuDNN version: 10.1.2/7.6.5
GPU models and configuration: Tesla V100

What's the resolution to this issue?


XFA - Add back empty subforms (which can have a background)

It aims to fix issue #13579.

/botio test

/botio test

/botio makeref


Edit legal docs

Modifications I've made to the original docs generated from getterms.io

In some places it's referred to 'website and/or services' in other places only 'services'

Yea we could probably normalize to just "Services".

Is it 'Services' or 'services'

Should be capital given other examples I've seen.


Angular 14 support?

Is Angular 14 supported by this package?

Any news?

It should work just fine with the existing latest version. Let me know if you have any issue

I thought so since it's targeting "@angular/core": ">=13.0.0" and I can confirm after trying it that it's working just fine.

I just upgraded Angular from v13 to v14 and I'm getting the error: Error: NG0302: The pipe 'translate' could not be found in the 'the_component_name' component. Verify that it is declared or imported in this module. which kinda does not make any sense since the diff that I can see in my repo between v13 and v14 does not contain any changes to the module files. The majority is about UntypedFormGroup, UntypedFormControl and similar. The only other change is in my main tsconfig.json which have changed the "target": "es5" to "target": "es2020". Each of my modules contains TranslateModule in the imports section as it did with v13.
Maybe anybody seen something similar?

Same here. I updated to Angular v14.
    "@angular/core": "^14.2.3",
    "@ngx-translate/core": "^14.0.0",
    "@ngx-translate/http-loader": "^7.0.0",

I can compile and start the peoject. In the browser I see the same Error:
Error: NG0302: The pipe 'translate' could not be found in the 'LoginComponent' component.

Same Here core.mjs:7635 ERROR Error: NG0203: inject() must be called from an injection context such as a constructor, a factory function, a field initializer, or a function used with

Is Angular 14 supported by this package?

Yes, it is supported. Just update it to the latest version.

Yes, Angular 14 is supported.

This problem exists for me too.
@ocombe
Error: NG0302: The pipe 'translate' could not be found in the 'the_component_name' component. Verify that it is declared or imported in this module.

I am using Angular 14 and got the following error after adding ngx-translate:
Error: Module not found: Error: Package path ./public_api is not exported from package C:\Users...\node_modules@ngx-translate\core. Anybody knows how to fix it? Thanks.

Error: node_modules/@ngx-translate/core/dist/lib/translate.directive.d.ts:25:18 - error TS2707: Generic type ‘ɵɵDirectiveDeclaration’ requires between 6 and 8 type arguments.
25     static ɵdir: i0.ɵɵDirectiveDeclaration<TranslateDirective, “[translate],[ngx-translate]“, never, { “translate”: { “alias”: “translate”; “required”: false; }; “translateParams”: { “alias”: “translateParams”; “required”: false; }; }, {}, never, never, false, never>;
Error: Command “npm run build” exited with 1
Any idea? Deploy failed and this is error

For anyone having the same issue, you can solve it this way:
Navigate to -><EMAIL_ADDRESS>Replace line 25 with this code:
static ɵdir: i0.ɵɵDirectiveDeclaration<TranslateDirective, "[translate],[ngx-translate]", never, { 'translate': 'translate'; 'translateParams': 'translateParams'; }, {}, never, never, false, never>;

@martinabdulghni solution worked for me !

static ɵdir: i0.ɵɵDirectiveDeclaration<TranslateDirective, "[translate],[ngx-translate]", never, { 'translate': 'translate'; 'translateParams': 'translateParams'; }, {}, never, never, false, never>;

We require a solution for this issue that arises whenever I execute npm install. It should be a consistent fix that also addresses the need for replacement in the package, especially for automated deployment processes.


Feature Request: Upgrade Spyder's Environment Handling

Currently Spyder provides a way to select the iPython environment of new consoles in the preferences.
This works well as a "default" setting for new consoles but it would be very nice to be able to select environments for new consoles on the fly or change the environment of existing consoles.
I envision the following features:

In the preferences, the default iPython environment for new consoles will keep the existing mechanisms of "Default (i.e. the Same as Spyder's)" or "Use the following Python interpreter", but have an additional selection option "Use the following environment" which would be a drop-down list populated from environments automatically identified on the system. These environments could include the system Python, identified Conda environments, and identified Pyenv environments.
The status bar environment indicator, when clicked, will reveal the list of identified environments on the system (as in the preferences in the previous item). When selected, the current console will restart in the new environment.
The status bar environment indicator should indicate the environment of the current console, not necessarily the environment selected in Spyder's preferences.
The console widget settings dropdown menu item "New console (default settings)" will change to "New Console" with a submenu list of "Default" and the identified environments on the system.
The "Run configuration per file" console settings, in addition to selecting a current, dedicated, or external console, should should have a dropdown list of identified system environments to use. This would be greyed out if "current" console is selected.

Note that in order to properly handle Pyenv environments, the paths to identified python executables should not be resolved if they are symbolic links, or a different mechanism for identifying environments should be used.

This will be a very ambitious project; it is very interesting to me, though I don't know that I'll be very adept at it, since I have no experience (yet?) at GUI programming. I guess we'd be looking at this for version 5?

Actually, I've already created #12200, closing this issue


Compress button not scroll-able for screen less than 14 inch

My laptop is hp probook 440 G5. Its a 14inch Screen. I have installed Densify. However i cannot see the Compress now button. Its not scrollable. See attached screenshot.

Same issue here, but it seems to be an abandoned project, no updates for two years...

Hey guys,
Sorry for the late reply on this. "Life got in the way." It looks like what's happening is that you both are running on pretty low resolution? I am also on a 14" but doing 1080p so this does not happen.
After doing some testing, it seems that when I set the resolution to 1280x720 (16:9) resolution (or lower), I then finally experience the same issue as yourself. I don't have a device that runs lower than 1080p now-a-days so I never noticed that before.
In the latest release, I have put together a hack that basically doesn't show the logo and shrinks the app window upon detecting display height of below 720.
You can find that in the master branch now or https://github.com/hkdb/Densify/releases/tag/v0.3.0
Let me know if that fixes the problem for you.
Thanks!

Thanks for your work! But nothing changed for me with the new version. My screen resolution is 1366x768, and the logo still shows up

@TheNomad11 Thanks for the quick feedback! I have just released v0.3.1 that will launch in low resolution mode when it detects anything below x800 instead of x730. Can you give that a whirl?
Thanks!

Perfect now, thanks a lot!!!


Update rhods prometheus stack according the kfnbc migration

This PR cleans up the obsolete monitoring targets, alerts and recording rules from Prometheus configuration
Description
Applied the following changes:

Removed Traefik
Removed Jupyterhub and JupyterhubDB
Add monitoring target for Jupyter notebook spawner page (WIP)

How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message.
[x] JIRA link(s): https://issues.redhat.com/browse/RHODS-4765
[ ] The Jira story is acked.
[ ] Live build image:
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] QE contact acknowledges that this has been tested and is approved for merge.

Adding in /cc @Samu to be aware for the PRs that deal with the changes on the monitoring stack

Some notes and thoughts regarding the third point of this PR Add monitoring target for Jupyter notebook spawner page
Case 1:
Adding the URLs
- rhods-dashboard-redhat-ods-applications.apps.atheodor.dev.datahub.redhat.com/notebookController/spawner or
- rhods-dashboard-redhat-ods-applications.apps.atheodor.dev.datahub.redhat.com/notebookController
as targets into the job: user_facing_endpoints_status and alongside deleting the ServiceAccounts notebook-controller-service-account, odh-notebook-controller-manager and rhods-dashboard (Having the operator scaled down) I don't see any downtime on the targets via rhods_aggregate_availability metric. (The scraping of the targets is UP)
Case 2:
Adding the URLs
- rhods-dashboard-redhat-ods-applications.apps.atheodor.dev.datahub.redhat.com/notebookController/spawner or
- rhods-dashboard-redhat-ods-applications.apps.atheodor.dev.datahub.redhat.com/notebookController
as targets into the job: user_facing_endpoints_status and stop notebook server (via rhods dashboard) I don't see any downtime again through rhods_aggregate_availability metric.
I believe the reason that we don't see any downtime while we scrape these targets is that the kfnbc spawner is embedded on rhods dashboard.
Any alternative thoughts regarding how to scrape or not the notebook spawner?

@atheo89 these changes look good to me (other than the small whitespace nit). Do you have a live build I can test with?

@accorvin today, we had a discussion with @samuelvl about the live build. He is going to bunch all the monitoring changes together and he will provide a live build. Once it will be ready we will add the link for the live build.

@atheo89 the prometheus stack init container will also need to be updated to account for traefik proxy
https://github.com/red-hat-data-services/odh-deployer/blob/main/monitoring/prometheus/prometheus.yaml#L22-L35

@anishasthana, I should remove the command, right?

It would be better to update it so that prometheus is waiting for one of the notebook controller pods to come up.

Note: Added on this PR the changes for the fault firing of the kfnbc alerts, and I closed the old one.  https://github.com/red-hat-data-services/odh-deployer/pull/255

A new live build with these changes is available at quay.io/accorvin/rhods-operator-live-catalog:1.0.0-rhods-4765

@atheo89 I'm getting an error in the deployer init container:
sed: -e expression #1, char 101: unknown option to `s'

I believe I've found the problem that was causing the deploy script to fail. I've added https://github.com/red-hat-data-services/odh-deployer/pull/256/commits/b9eb01445121d4315bc2833829d65ae742d37be5 with a fix and am building a new live image now.

The issue with the odh deployer init container failing has been resolved by my latest change (this change is available in the live build, I pushed the new version to the same tag).
I'm seeing an issue now where the probes are getting 403 errors. I'm investigating why that is happening.

Update: I found that the opendatahub-operator container in my live build did not properly include the changes from https://github.com/red-hat-data-services/odh-manifests/pull/231
I'm generating a new live build that resolves that and will post with the status of my testing.

Update: this looks to be working correctly now with the latest version of my live build

Rhods livebuild for these changes with KFNBC and migration script: quay.io/llasmith/rhods-operator-live-catalog:1.16.0-dashboard-kfnbc

We've pulled Adriana's changes into #257

These changes have been pulled into https://github.com/red-hat-data-services/odh-deployer/pull/257


squirrel.exe and Update.exe, which one can be depended on by my app?

After installation, there are 2 files -- <installation_dir>\Update.exe and <installation_dir>\app-x.y.z\squirrel.exe -- installed, and seems the same.
Why both of them exist? which one can be executed by my app (I want to use it to create shortcuts)? Are they guaranteed to exist in future versions of grunt-electron-installer?

Update.exe is the version that is actually used to update and install your app and the one you should rely on. Squirrel.exe is the latest version of Update.exe - during update, <installation_dir>\Update.exe will look for that Squirrel.exe and use it to update itself (i.e. so your users don't get stuck on an old version of Squirrel).

I see, thank you very much！


nm/state: Discard IP stack when disabled for verification

When desire contain extra IP information when IP disabled,
the verification will fail.
For example:
desire:     {'enabled': False, 'dhcp': False}
current:    {'enabled': False}

The verification should pass on the above use case.
The fix is remove the whole IP stack before verification when disabled.
A unit test case has been added for this use case.

Coverage increased (+0.07%) to 72.894% when pulling ea24b010b40af2cadb622b6f86bb1c0e59210ad8 on cathay4t:fix_disable_ip_verification into e287866df6bed32b31cab8bda82825e72531f5b0 on nmstate:master.

Coverage increased (+0.07%) to 72.894% when pulling ea24b010b40af2cadb622b6f86bb1c0e59210ad8 on cathay4t:fix_disable_ip_verification into e287866df6bed32b31cab8bda82825e72531f5b0 on nmstate:master.

Coverage increased (+0.07%) to 72.894% when pulling ea24b010b40af2cadb622b6f86bb1c0e59210ad8 on cathay4t:fix_disable_ip_verification into e287866df6bed32b31cab8bda82825e72531f5b0 on nmstate:master.


chore(ci): move blockifier dep to root toml

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#258
#257
#256  👈
#255
main-v0.13.2

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dorimedini-starkware and the rest of your teammates on  Graphite


balena push  never completes

After following the instructions and getting to the balena push <appName> part. It all runs fine and I get:
[Info]            Uploading images
[Success]         Successfully uploaded images
[Success]         Release successfully created!
[Info]            Release: f632086f61288803fc1ea9efaaf59317 (id: 974470)
[Info]            ┌────────────────┬────────────┬────────────┐
[Info]            │ Service        │ Image Size │ Build Time │
[Info]            ├────────────────┼────────────┼────────────┤
[Info]            │ pihole         │ 275.84 MB  │ 11 seconds │
[Info]            ├────────────────┼────────────┼────────────┤
[Info]            │ dnscrypt-proxy │ 19.06 MB   │ < 1 second │
[Info]            └────────────────┴────────────┴────────────┘
[Info]            Build finished in 22 seconds
But it never returns to the command prompt. I can ctrl + c to cancel then I get
Received SIGINT, cleaning up. Please wait.
Then if I run balena push <appName> again it creates a new release version, even though nothing has changed.
I am using Windows 10 and Poweshell to run the commands.

Hey @craigusus , I've seen this behavior before too and it's related to the balena-cli rather than this specific app stack. I thought maybe I was using it wrong :)
I'm pretty sure @chrisys will see this and help you out, but you may want to submit an issue or post on the forums at https://forums.balena.io for a faster response.

Hey @craigusus yup as this is a balena-cli issue please post on the forums and the cli team will see it and be able to work out what's going on. If you share the version of the cli you're using too that'll help.


improve styling of team contact us box

this color is according to them (light sky blue) so it is not looking much better.
@mansiruhil13 please assigned this taskto me.

Changes are done and i created pull request please let me if it works or not.
@mansiruhil13 @4F24L
issue no:- #339