Set Frame Delay according to Monitor Refresh Rate

This is a simple PR that changes FilamentApp to delay its rendering to be roughly in line with the monitor framerate.
This helps all the samples look temporally smooth on higher refresh rate monitors, while still leaving it clear how to decouple rendering from vsync for new programmers.
Alternative techniques (with finer than 1ms granularity) like using SDL_GL_SetSwapInterval or SDL_RENDERER_PRESENTVSYNC might be preferable, but I'm still too new to SDL to figure out how to integrate them.    Even with integer milliseconds, the beat-frequency (rate of frame stutters) will never exceed ~1hz~ 0.5hz, so the incremental improvement will be minimal.

That makes sense; though I’m not sure what the best way to add them in SDL is.
It also just occurred to me that this change doesn’t take into account the time it takes for the application to run/render.  Might need to add some extra timing logic…


Added CheckList and CheckItem creation API calls

Update the Rest API. Card removal is WIP.

hi @benemon
don't have committer's rights here so I'll defer to @julienvey / @haklop for final merge decision but here are my views on this change:
On the plus side it seems straightforward enough and good to have :white_check_mark:
On the down side, formatting. Generally speaking you shouldn't apply "organize imports" type of refactorings to sources that you didn't actually otherwise modify.
Also WIP don't belong to a pull request. The commit text associated to "card removal" is misguiding and should be reworked and made part of a second PR later on when it's not wip anymore.
I found that for me the best way to go and separate such concerns is to fork the repo and create a branch dedicated to a particular problem in my fork. This way I can work on two features in parallel and each can have its own PR.
Unfortunately, in this case it means you have a little work to do to resync everything with upstream without losing your change (maybe you can export the changes as patches to be on the safe side, or create a branch that contains them), put each change in its own branch, then close this PR and open a new one.

Hi @simonbasle
Many thanks for the feedback. I'm glad that the feature for CheckLists and CheckItems is deemed good to have.
I must apologise for the presence of the WIP commit. I ended up in the situation where my deletion use case evaporated and I probably won't visit it again. I'm happy to close off this pull request and open another one for just the CheckLists.


Appium-docker for iOS

Can we run the appium -docker test in iOS test ? If so please share the steps for the same

No, docker is not supported natively on Mac OS. Appium needs XCode for iOS and it is not possible to create XCode docker image for now.


Rounding in resize is wrong

example:
image.shape == (500, 1000, 3)
resize(image, width=2018)
wil return an image of dimensions(1008, 2018)
The reason is the lines
r = width / float(w)
dim = (width, int(h * r))
which should round the dimension instead of flooring it

It's perfectly normal to simply cast the floating point value as an integer. I don't see this as a bug. Please feel free to create your own resize function and round if you would like.


EDC extension - retrieve data reference

Hi and sorry that it took so long to do the review.
First of all thanks for the contribution. We have taken a look at the code and would like to provide you with some general feedback.

The Copyright claims are not updated yet. As the extension is provided by you, feel free to add them for your company :)
For code coverage currently it's necessary to add your extension to this pom file
To include your extension in the SonarQube anaylsis add your extension to the parent pom.
After your project is incuded in the SonarQube analysis, there are probably some steps you can take to pass the quality gate.
We always add a README.md to new extensions. Normally we add stuff like summary, configuration and if possible a small example how to the extension is used. Its totally fine if it's not perfect on the first try, as we update most of the README.md regulary.
There are still some TODOs in the code. Would it possible to resolve them before we merge the branch?

The idea is to have the code on the develop branch as complete as possible (features, documentation, tests).
Dominik Pinsel<EMAIL_ADDRESS>Mercedes-Benz Tech Innovation GmbH, legal info/Impressum

Hi and sorry that it took so long to do the review.
First of all thanks for the contribution. We have taken a look at the code and would like to provide you with some general feedback.

The Copyright claims are not updated yet. As the extension is provided by you, feel free to add them for your company :)
For code coverage currently it's necessary to add your extension to this pom file
To include your extension in the SonarQube anaylsis add your extension to the parent pom.
After your project is incuded in the SonarQube analysis, there are probably some steps you can take to pass the quality gate.
We always add a README.md to new extensions. Normally we add stuff like summary, configuration and if possible a small example how to the extension is used. Its totally fine if it's not perfect on the first try, as we update most of the README.md regulary.
There are still some TODOs in the code. Would it possible to resolve them before we merge the branch?

The idea is to have the code on the develop branch as complete as possible (features, documentation, tests).
Dominik Pinsel<EMAIL_ADDRESS>Mercedes-Benz Tech Innovation GmbH, legal info/Impressum


[GP-3106] bigint ids

jooq maps these to Long. postgres already set up the sequence behind the auto-increment as bigint for some reason so only the surface level types need to be changed.

Docker is broken on my laptop to the point where i can't fully build vidarr because the tests crash so i need to push to github just to pull on desktop. I know the checks are failing it's fine I'll fix it :+1:


useCsrfFetch is not working after running "npm run build" in production

Environment
Nuxt project info:
------------------------------
- Operating System: Windows_NT
- Node Version:     v23.0.0
- Nuxt Version:     3.14.1592
- CLI Version:      3.16.0
- Nitro Version:    2.10.4
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      default
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Nuxt Security Version
v2.1.5
Default setup used?
Yes, the bug happens even if the security option is not customized
Security options
security: {
    csrf: true,
    headers: {
      xXSSProtection: '0'
    },
    rateLimiter: {
      tokensPerInterval: 5,
      interval: 30000,
      headers: true
    },
  },

Reproduction
Github:
https://github.com/raliclo/Nuxt_Security_PrimeVue_Pinia
Bug page
http://localhost:3000/about
Description
Bug page
http://localhost:3000/about
-What happens ?
When I use "npm run dev" to view the bug page, the {{time}} called by nuxt server api is successfuly rendered.
But if I use "npm run build" and run production version. The api call was not called.
It seems to be "useCsrfFetch" not calling the nuxt server api in the production page.
-What is expected to happen ?
useCsrfFetch is working and the about page call the nuxt server api.
Additional context
No response
Logs

@Morgbn
Would you be able to help here? :)

I have the same problem. I suppose it's linked to this #bug.


Different sizes for enums

Is your feature request related to a problem? Please describe.
Ghidra's enum types have a set size, but programs sometimes stick enum values into larger-sized variables. For example within the same program, the values of a State enum are sometimes stored/passed as uint8_t, uint16_t or uint32_t, especially when passed as a register parameter. Currently, Ghidra seems to assume an enum value is always stored as its exact size.
Describe the solution you'd like
Provide some way to set the type of a variable to an enum whose size is smaller than the variable's own type.
Describe alternatives you've considered
I end up creating copies State8, State16, State32, but this is suboptimal because they're three separate types (so searching for uses of one won't find the others) and can get out of sync (must remember to make the same changes to all three).

Could you please indicate the specific failures or impact such a single-size enum has for you.   Are you seeing type casts in the decompiler that differs from the enum (e.g., unsigned4, int, etc.)?

If I assign the register a smaller type, I usually see an automatic concatenation. Eg:
MapDirIdx32 mapGetDirIdx(MapId8 id)
{
  undefined3 in_register_0000000c;

  if (0x4a < CONCAT31(in_register_0000000c,id)) {
    return animtest_05;
  }
  return mapIdXltnTbl[CONCAT31(in_register_0000000c,id)];
}

versus:
MapDirIdx32 mapGetDirIdx(MapId32 id)
{
  if (0x4a < id) {
    return animtest_05;
  }
  return mapIdXltnTbl[id];
}

Especially in cases like this where it doesn't assign to a temporary variable, the concats make it harder to read.
The bigger problem is with structures. Some store a map ID in a uint8_t, some store it in a uint16_t, and so on. There doesn't seem to be a way to have a structure field that's "uint16_t but using the values of this 1-byte enum", so I have to either duplicate the enums or have wrong-sized structure fields.
It gets even hairier when the structure contains negative values, since they're represented differently depending on size (eg 0xFF vs 0xFFFF).

I would think that the CONCAT could be avoided but I will defer to @caheckman

This issue is still present on Ghidra 10.2. Unfortunately due to this, you either to manually create multiple copies of the same enum with different sizes and retype based on the context of the enum usage. This workaround fails though when your enum is packed in a struct and its size matters. In the decompiler view, there will be a cast from one type to the next, eliding the enum's actual type, preventing equates from being displayed properly.
The "double enum" approach also suffers from cross referencing, where you'd like to be able to see all usages of an enum, without having to check a narrowed or widened version.


Working Criteria for MongoDB 4.0 with ReplicaSet

This is a Great Script, I've done some modifications according to the following environment:

AWS
Ubuntu 16.04
Zabbix Agent 3.4
MongoDB 4
Python3

Below are my configuration:

Installing PyMongo
sudo apt-get install build-essential python-dev python3-pip
sudo pip3 install pymongo
Installing Zabbix_Sender
sudo apt-get install zabbix-sender
Change python to python3 in mongodb-stats.sh
python /usr/local/bin/zabbix-mongodb.py -- to --> python3 /usr/local/bin/zabbix-mongodb.py
Change Parameters under class MongoDB(object), in case of ReplicaSet
self.mongo_host = "hostname"
Provide Credentials if you have enabled Security
self.mongo_user = "username"
self.mongo_password = "password"

Appriciate your effort ...

Boa tarde,
No meu mongo que é um replica set ele apresenta esse erro [gandalf@node10-mongodb bin]$ sudo vim zabbix-mongodb.py
[gandalf@node10-mongodb bin]$ sudo sh -x mongodb-stats.sh
++ get_MongoDB_metrics
++ python3 /usr/local/bin/zabbix-mongodb.py
++ /usr/bin/zabbix_sender -c /etc/zabbix/zabbix_agentd.conf -i -
Traceback (most recent call last):
File "/usr/local/bin/zabbix-mongodb.py", line 245, in
mongodb.get_oplog()
File "/usr/local/bin/zabbix-mongodb.py", line 118, in get_oplog
if op_first.count() > 0 and op_last.count() > 0:
File "/usr/local/lib64/python3.6/site-packages/pymongo/cursor.py", line 787, in count
cmd, self.__collation, session=self.__session)
File "/usr/local/lib64/python3.6/site-packages/pymongo/collection.py", line 1600, in _count
_cmd, self._read_preference_for(session), session)
File "/usr/local/lib64/python3.6/site-packages/pymongo/mongo_client.py", line 1464, in _retryable_read
return func(session, server, sock_info, slave_ok)
File "/usr/local/lib64/python3.6/site-packages/pymongo/collection.py", line 1594, in _cmd
session=session)
File "/usr/local/lib64/python3.6/site-packages/pymongo/collection.py", line 250, in _command
user_fields=user_fields)
File "/usr/local/lib64/python3.6/site-packages/pymongo/pool.py", line 613, in command
user_fields=user_fields)
File "/usr/local/lib64/python3.6/site-packages/pymongo/network.py", line 159, in command
codec_options=codec_options, user_fields=user_fields)
File "/usr/local/lib64/python3.6/site-packages/pymongo/message.py", line 1534, in unpack_response
self.raw_response(cursor_id)
File "/usr/local/lib64/python3.6/site-packages/pymongo/message.py", line 1513, in raw_response
error_object)
pymongo.errors.OperationFailure: database error: Can't use 'local' database through mongos

result='sent: 0; skipped: 0; total: 0'
++ echo 'sent: 0; skipped: 0; total: 0'
++ awk -F ';' '$1 ~ /^info/ && match($1,/[0-9].*$/) {sum+=substr($1,RSTART,RLENGTH)} END {print sum}'
response=
'[' -n '' ']'
echo 'sent: 0; skipped: 0; total: 0'
sent: 0; skipped: 0; total: 0


Add AccuracySection

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (f93a3fa) to head (57283d0).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #72   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           27        28    +1
  Lines          469       500   +31
  Branches        41        42    +1
=========================================
+ Hits           469       500   +31

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix edge-api PR check

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes
[ ] I run make lint to prints out coding style mistakes and fix them

Test results are available in Ibutsu. The test run IDs are:
235eb8bc-3a5c-4301-b8f0-9bf1c7298425
41b9c551-0838-4908-a84e-88ff45137180

Missing check for thirdpartyrepo in routes


Strange behaviour with overlay network and AWS

I seem to be having a weird issue with my overlay network on AWS. I created an overlay network with the range <IP_ADDRESS>/16, which is working great! But for some reason when a container gets assigned the IP <IP_ADDRESS> nothing can communicate with it, it doesn't seem to make a difference what server its on in the docker swarm. I'll be honest I don't really know here to begin debugging this or how to replicate this. Can anyone help? This could be fixed on 1.10 but AWS are still on 1.9.1 😢
Output of docker version:
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5/1.9.1
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5/1.9.1
 Built:
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 6
Images: 112
Server Version: 1.9.1
Storage Driver: devicemapper
 Pool Name: docker-202:1-263652-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem:
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 5.876 GB
 Data Space Total: 107.4 GB
 Data Space Available: 44.78 GB
 Metadata Space Used: 8.409 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.139 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.17-22.30.amzn1.x86_64
Operating System: Amazon Linux AMI 2016.03
CPUs: 2
Total Memory: 3.862 GiB
Name: swarm-node-eu-west1-1c-1
ID: F5EH:BZNO:6HR5:MSTB:EYE3:MPBD:GKRX:RM7J:OSIB:ALF7:C4YU:C3RR
Cluster store: consul://<IP_ADDRESS>:8500
Cluster advertise: <IP_ADDRESS>:2375

Additional environment details (AWS, VirtualBox, physical, etc.):
We're on an AWS VPC in EU-West1

But for some reason when a container gets assigned the IP <IP_ADDRESS>

So it only fails for that IP address?

@thaJeztah weirdly yes!

My hunch is it's iptable rules or routing entries being wrong. Can you double check these?

Thanks for the suggest, unfortunately there doesn't seem to be anything in iptables. If I have some time later I'll go through some of the logs and see if I can figure it out. This is on a production cluster so I don't want to tinker too much!
[ec2-user@swarm-node-eu-west1-1a-1 ~]$ sudo iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Closing because we probably need more info to look into this, but let me know if you're still having this issue, or found the cause

@thaJeztah sorry I didn't close this. I actually recreated the network and not had the problem since 😄

Good to hear, thanks!


Diverse types of ontologies

Are existing ontologies sufficient? Clear statement needed

Relevant Section: 3.1.2

see #38

Wir könnten natürlich auch hier bei der Section "Challenges" ansetzen und dort ein kritisches Statement zu Ontologien platzieren. Würde wahrscheinlich hier sogar mehr Sinn ergeben, was denkst du?

In addition, dealing with data and schema heterogeneity and inherent un- certainty is another relevant field of research that BigGIS addresses. Preconditions for meaningful findings in GIS are accurate, consistent and complete data as input for analytical processes. However, sources of spatio-temporal data are distributed and quality of the data is varying, especially when considering uncertain data such as VGI. We intend to address this challenge by a smart data integration approach which is based on semantically described data sources and data transformation services as discussed in [3]. Smart web services dynamically compose workflows of data sources and data transformation services adopted to the requirements of different GISs based on the semantic metadata [4].

Challenges in Section 3.2.1:

We intend to address this challenge by a smart data integration approach which is based on semantically described data sources leveraging existing ontologies such as NeoGeo Spatial Ontology, or NeoGeo Geometry Ontology and data transformation services according to the requirements of different analytical goals as discussed in [3, 4].

see PR #49


Cow: Watch zuccherocanada.ca

Cow requests the watch of the watch_keyword zuccherocanada\.ca. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

zuccherocanada\.ca has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


Fix asref diagnostic macro call

Closes #172
I would like to ask @TheNeikos for review as well here, as #165 was developed with them.

This is done way better with #169 IMO. I guess this one should be closed in favour of #169!

Maybe 0b32574 can be added to #169, so the error from #172 is covered there explicitely as well.

Closing in favor of #169 which I just merged :)


Release Community meeting recording (August)

Acceptance criteria

[ ] Upload the recording on our youtube channel
To double check:

[ ] Recording is ordered (should be last one)
[ ] Recording has description

Description:
This meeting’s agenda:
This meeting’s agenda:

* 1.15 release
  * Enhanced PolicyServer CRD with tolerations
  * Centralised Management of tolerations, affinity and anti-affinity
  * Improve codebase of Kubewarden controller
  * PolicyGroup: implementation done inside of PolicyServer, what’s next
  * MatchConditions added to our policy CRDs
* Policies changes and fixes
  * User-group-policy updates
  * CEL policy: new capabilities added
* [Livestream fence io](https://www.youtube.com/watch?v=s1qVJT4i2-A)
* What’s coming next:
  * Removal of cert-manager dependency

Recording link
https://zoom.us/rec/share/m7boZp_IVjUBXO_1iHa-E9BqleBtox8dcd7V5GdtbXG_YIsCs9KH5GB_mC_XN1ew.X5sbM4JvVSwYUHhG

This is done.


Histogram performance improvement

In the histogram SQL query, the __cdb_iqrange table is declared as a CTE but only used once. A quick  test show a query time reduced from 1.3 s to 1.0 when inlining it instead (obviously this depends on the data)
cc/ @CartoDB/rt-managers

Removing this from RT. This is not urgent. If you feel this is important, let's do a project for it.


fix: render external imports as reference directives

me neither! let's hope it doesn't break anything else. released 0.1.9


Test the review build for LU-9725

This change is

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Everything good in here has either landed elsewhere or been made obsolete by better solutions.


fzf history not filtered by what user has already typed before invoking (Ctrl + R)

Hi! Amazing work on clink-fzf and clink. I discovered your work yesterday and think it's all empowering as a Windows user. 🙏
While this plugin works great, it seems to not initialize the history command with what the user has typed so far in their terminal. Here are examples comparing my Powershell setup with Clink.
Here is Powershell using PSFzf:
https://user-images.githubusercontent.com/4752973/220920970-5c1f9fe9-34e1-40ff-a2c8-0dbba18c23bd.mp4
Here is clink v<IP_ADDRESS>e404:
https://user-images.githubusercontent.com/4752973/220921453-9abe05b6-31f3-4e7b-8bff-9fe9eb0eb841.mp4
Not sure if this is a bug or not implemented yet. I noticed this line, but I believe this is intended to capture what the user has typed in the fzf prompt:
local r = io.popen(history..' 2>nul | '..get_fzf('FZF_CTRL_R_OPTS')..' -i --tac')

EDIT: I just now understood this comment. If I'm reading this correctly, this functionality is intentional:
This intentionally does not use '--query' because that isn't safe:
    -- Depending on what the user has typed so far, passing it as an argument
    -- may cause the command to interpreted differently than expected.

Doing this does seem to get the result I want, but at the risk of what you mention in the comment. I noticed this also breaks if I do something like node - and then hit Ctrl + R:
local line = line_state:getline()
local r = io.popen(history..' 2>nul | '..get_fzf('FZF_CTRL_R_OPTS')..' -i --tac --query ' .. line)

@kevinfiol Correct. It can result in a what is effectively an accidentally "friendly fire" injection attack. Various severe unexpected side effects are possible with flags like --query, so I'm a little surprised fzf uses that approach (a safer approach could be to read the query from an input file).
Certain kinds of input line text can be escaped and made possible to pass to --query, and some kinds of text cannot be escaped successfully.  And in some cases the act of escaping text can result in fzf doing a lookup on a different string than the user intended, resulting in a different set of results than the user was trying to find.
I could make it so that when the text doesn't need to be escaped, then clink-fzf could be pass it to --query.  But then the behavior will be inconsistent depending on the input line.  So far, I preferred to have consistent behavior.
Is that something you'd like?
Some especially troublesome characters are ", -, <, >, |, &, and some others.

Thank you for the clarification. It's a tough one, but I agree with you that it's better to keep the behavior consistent. May be worth just noting the caveat in the README.

I pushed an update that should be a safe way to use the --query flag.
However, as of this writing, fzf with bash and other shells has a code injection bug in how --query is used.

Opened https://github.com/junegunn/fzf/issues/3185 to alert in the fzf repo about this code injection issue, and a potential approach for fixing it.

The latest fzf.lua (in both clink-fzf and clink-gizmos) now performs as much escaping as possible of the query string, while following the 2N rule for backslashes when escaping quotes.  Now the only thing that can't be passed in the query string is just % because there's no way to prevent cmd from parsing % as part of environment variable expansion.


docs: cleanup markdown warnings

This will clean the markdown warnings in the docs:

Lists should be surrounded by blank lines.
Fenced code blocks should have a language specified.
Multiple consecutive blank lines.
No trailing punctuation in heading
Headings should be surrounded by blank lines.
Fenced code blocks should be surrounded by blank lines.

Love it! Running CI.
I also wonder if it's possible to add eslint config for this, so that they're automatically kept clean from these sorts of things.

It might get a bit challenging since some warnings like inline HTML are still there and I didn't want to touch them (do we want to remove them all?) but it would be interesting.


Scheduler: Trigger weekday not working if phone language is not english

In Scheduler.java the now.getDisplayName(Calendar.DAY_OF_WEEK, Calendar.LONG, Locale.getDefault()) returns locale specific name e.g Montag for Monday in german.
AWARE::Scheduler com.aware.phone D Weekday MONDAY vs now MONTAG in trigger weekdays: ["monday","tuesday","wednesday","thursday","friday","saturday","sunday"]
Workaround: modify the weekday array in studyConfig.json to the language you expect
A fix would be to change
now.getDisplayName(Calendar.DAY_OF_WEEK, Calendar.LONG, Locale.getDefault())
to
now.getDisplayName(Calendar.DAY_OF_WEEK, Calendar.LONG, Locale.ENGLISH)

Thank you very much. This is super helpful.


[Docs] Improve README

Description of your changes
Improve README file with prerequisites section and version improvement.
People will copy paste the v0.1.0 examples all the time, people copy paste examples, people wants the lastest version of the provider :).
I have:

[x] Read and followed Crossplane's [contribution process].

Thank you @scraly 🎉


chore: Move WithZero material depending on GroupWithZero

Everything under Algebra.Group should be additivisable. Therefore I move the GroupWithZero instances for WithZero from Algebra.Group.WithOne.Defs and the whole of Algebra.Group.WithOne.Units to a new file Algebra.GroupWithZero.WithZero. I credit Mario for https://github.com/leanprover-community/mathlib/commit/ad92a9ba47f417916aab365d13db653fa8991a84 and Johan for https://github.com/leanprover-community/mathlib/pull/762.
Use the opportunity to slightly clean up the code:

Replace := by where in instance declarations
Add missing explicit arguments to coe lemmas
Add missing section ... end

On the assumption that you did more than just moves (eg, replacing {} with where), can you summarize the changes you made in the PR description?

Done

bors d+
Thanks!

bors merge


TextEdit in correct "onChange/onTextChange"

Description
TextEdit if value and editable are fired at or near the same time. onChangeText fires twice with the OLD value the 2nd time not the new value.
React Native Version
0.71.7
Output of npx react-native info
System:
OS: macOS 13.3.1
CPU: (12) arm64 Apple M2 Max
Memory: 1.53 GB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.16.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 9.6.6 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: ^0.71.7 => 0.71.7
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

Preset value to "VALUE1" via a useState - [value, setValue] = useState('VALUE1')
set TextEdit value={value}
Present value of editable to try via a useState - [editable, setEditable] = useState(true)
set TextEdit editable={editable}
Manually type/set contents of TextEdit to "VALUE2"
Use a button that will fire this code:
setValue("VALUE1");
setEditable(false);

The "value" of the TextEdit initially changes to 'VALUE1' as observed by onChangeText, however onChangeText fires a second time (why?) with the previous value ('VALUE2').
Snack, code example, screenshot, or link to a repository
unable to provide

https://snack.expo.dev/@xpario/textedit---react-native-bug?platform=web
the issue started with 0.71.7 - i understand there is a newer version - ill have to wait until expo updates it. I am not able to test on <IP_ADDRESS>

our observation is that this issue happens only on IOS 16.4
we didn't test it on IOS 16.5 as it is still beta
we have also tried this fix  <IP_ADDRESS>  and it doesn't work
this issue is related to the IOS version not react native version

I have retested this issue on IOS 16.4.1 and working fine


Fix typo mismatch in field trial string for delay bwe weight

Discovered this problem while debugging today.

@taste1981, please review.


[ARTEMIS-1259] Log messages without prefixed id code in artemis-serve…

…r-osgi
JIRA: https://issues.apache.org/jira/browse/ARTEMIS-1259

..checkstyle... also make sure ArtemisFeatureTest is working

[main] 17:49:10,023 ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure in initialisation: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use


Use boxed slice for blocks in memory

Boxed slice is cheaper than Vec (2 words vs. 3 words in-place) since its length is never going to change, and thus it doesn't need to maintain a capacity.
This commit also simplifies the code to generate the blocks.

I like the code simplification. I'll merge it. Thanks.


Grounding zhengzhong readytomerge 20200407

Changes:
0, All changes are for the compositional grounding.
1, Use the all mention tokens to ground the concept when the syntactic head does not contain "NN" POS tag. The weights of the tokens are determined by their POS tags, NN, NNS, NNP get 5 and others get 1 (values are tuned to the best performance). The composited vector is normalized.
2, Use competing grounding for the concept branch and the process branch.
3, The results are: concept MRR=0.5635, process MRR=0.675, property MRR=0.7875.
4, This uses the localPublish version of the processor of branch "localPublish_makeVector_20200415", I will also make a pull request of that branch of processor. The publish version is "8.0.2-SNAPSHOT". The "procVer" value in build.sbt of eidos should match that.

I reran the evaluation and got the same results as Zhengzhong. I also did two quick experiments.
First, Zhengzhong's branch is using an older copy of the gold groundings, which has only 80 entities evaluated. I tried the newest version, which has 130 entities evaluated and some of the gold groundings fixed. Here are the results:
130 entities evaluated
flat grounding accuracy:	0.72397435
concept grounding accuracy:	0.5878205
process grounding accuracy:	0.6615385
property grounding accuracy:	0.8769231

Second, in my earlier error analysis I found a few areas where the ontology needed some changes. These mostly helped Property, but also gave some small boosts to Concept and Process. Running Zhengzhong's branch with the updated ontology yields the following results:
130 entities evaluated
flat grounding accuracy:	0.72397435
concept grounding accuracy:	0.5955128
process grounding accuracy:	0.66923076
property grounding accuracy:	0.9076923

Comparing these results (even just with Zhengzhong's additions, not including the updated ontology) to my current branch, we see a ~4 point improvement in Concept and a whopping 16 point improvement in Process.
Other than whatever merge conflicts there were, these updates look good, and the results are definitely an improvement, especially for Process, which was our biggest problem before.

The conflicts are resolved.

I released processors 8.0.2, which should be available on maven in a couple of hours. As soon as it does, and the unit tests pass, we can merge this!
Good job @zhengzhongliang and @zupon !

processors 8.0.2 is now on maven so this should work now. Maybe we need another commit to this branch to force tests to run again? @kwalcock ?

One thing that has to happen is that
  val      procVer = "8.0.2-SNAPSHOT"

needs to change.  Would @zhengzhongliang like to do the honors?  It should force another test.

The diff shows that this has been changed to 8.0.2 already, no?

Yes, sorry.  I was looking at stale data.  I'll kick it then.

It has all green lights now  I'm just going to double check before merging.

Yay!!
On Fri, Apr 17, 2020 at 8:14 AM Keith Alcock<EMAIL_ADDRESS>wrote:

It has all green lights now I'm just going to double check before merging.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/826#issuecomment-615301242, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TVYBD46DWUZJGUYZWTRNBW4ZANCNFSM4MI5MT2Q
.

Thanks, someone, for fixing my typo in allSimiliarities!
Here are a couple of questions/comments to make sure I understand this.
Is m.text.split(" ") here intentionally different from m.words.toArray?  m.text is actually a method that has to do substantial work to reconstitute a mention's text from the individual words and might even insert multiple spaces.  It looks like this is all immediately undone by splitting on the same spaces.  Are the words good enough?  I wish toArray was not necessary, but that's a different project.
Could the lines
      val mentionHeadTag = mentionHeadOpt.map(m=>m.tags.head.head).getOrElse("None")
      val conceptSimilarities = {
        if (!mentionHeadTag.startsWith("NN")) {

be combined into something like
      val mentionHeadTagIsNN = mentionHeadOpt.map(m=>m.tags.head.head.startsWith("NN")).getOrElse(false)
      val conceptSimilarities = {
        if (!mentionHeadTagIsNN) {

mostly so this temporary use of "None" can be avoided?
That SingleOntologyGrounding of mine isn't very transparent and should probably change.  It is hiding the fact that a Namer tries to keep track of the ontology branch.  So in
          .filter(_._1.name.startsWith("wm/"+branch))

if it's safe to assume that "wm" is already a given and that there are branches because compositional grounding is being used, then something closer to
            .filter(_._1.branch.get == branch)

would be preferable.
I just want to confirm that the take comes before filter because you want each branch to compete with the others for the top places.  (I should have paid more attention to your reports.)
          .take(effectiveTopN)
          .filter(_._1.name.startsWith("wm/"+branch))

For strings like "property", can constants like CompositionalGrounder.PROPERTY be used?
Thanks for putting up with the nitpicky critique.

Oops, one more.  In calculateSimilaritiesWeighted, the 1.0.toFloat can probably just be 1f or 1.0f.

@zhengzhongliang, do you have time to look at the small issues above?  I can make changes if need be.

Hi Keith,
Thanks for the review, here are the responses:
1, m.words.toArray is indeed better than m.text.plit(" "), I changed to m.words.toArray.
2, I changed the way to get the tag of the syntactic head to the method you suggested.
3, The filter branch method is changed to what you suggested .
4, Yes the current order is correct. The filter should be applied after take because I want the branches to compete with each other.
5, strings like "property" are replaced with what you suggested.
6, 1.0.toFloat is changed to 1.0f
I made these changes and tested the new code, and the result does not change, so I think this is ready to merge.

Please let me know if anything else I need to do to merge this. Thanks.

This is excellent and oh so close.  Can @zhengzhongliang  and @zupon look at the merge conflict with evaluation_results.tsv and decide what needs to happen?  Perhaps the file even needs to be regenerated to match whatever master would output.  I haven't followed it closely enough to know.  Thanks!

I left a message to Andrew on slack, should be able to fix this soon.

Conflict is resolved. @kwalcock

Thanks for everyone's hard work on this.


⚠ Bofrost.lu has degraded performance

In e5baa7b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 871 ms

Resolved: Bofrost.lu performance has improved in 6581590.


Leak on parceler compiler (org.parceler.ParcelAnnotationProcessor$$Bootstrap)

Hi,
Our build got memory leak on org.parceler.ParcelAnnotationProcessor$$Bootstrap. It causing stuck on our build when JVM (daemon) memory full, and cannot perform any GC. Then the heap dump showing leak and dominator object from org.parceler.ParcelAnnotationProcessor$$Bootstrap.
It takes around 50 % of our heap size (around 2GB).
The image below shows the dominator and leak object when compiling our project.

This is the screenshot of our main daemon when it got full because of parceler leak. At this point the build will hanging and won't complete (not even causing OOM).

It seems coming from this file.
https://github.com/johncarl81/parceler/blob/master/parceler/src/main/java/org/parceler/ParcelAnnotationProcessor.java#L4
Do you have clue what might be wrong ? We suspect transfuse as DI manager creating static variable that will contains reference to that class. But i am not really sure which part causing this issue.
We have like 50+ modules implement parceler_api (annotation processor), and using lot of @Parcel class.
Let me know if you have additional information, Thanks.

Hmm, this is certainly concerning.  Could you help me reproduce @doniwinata0309 ?

This is sample to repro the leak:
https://github.com/doniwinata0309/build-perf-test/tree/test/parceler

Go to test/parceler branch
build "./gradlew androidAppModule0:aFD --rerun-tasks" 2 times
Use visualVM to generate heap dump of gradleDaemon
Open with MAT and there should be leak on parceler.

I also attached the result of leak on the branch https://github.com/doniwinata0309/build-perf-test/tree/test/parceler
one with kapt incremental enable, one kapt incremental disable.

The REPOSITORY object being references on the tree view:
https://github.com/johncarl81/transfuse/blob/master/transfuse-bootstrap/src/main/java/org/androidtransfuse/bootstrap/Bootstraps.java
It seems alway add new object new GeneratedCodeRepository and causing leak there ?
The object also getting huge as we add more @parcel class i guess, and also multiple instance found on the leak.

Hmm, maybe im out of touch with gradle these days, but I cant get ./gradlew androidAppModule0:aFD --rerun-tasks to run, I get the following:
./gradlew androidAppModule0:aFD --rerun-tasks

FAILURE: Build failed with an exception.

* What went wrong:
Task 'aFD' not found in project ':androidAppModule0'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 546ms

Is aFD an acronym for some build task?

yes it is from ./gradlew androidAppModule0:assembleFlavDebug --rerun-tasks
let me know if this command works or not.

Ok, I'm up and running.  I haven't been able to pinpoint the URLClassLoader memory leak you're referring to.
If you perform a GC after the build is memory cleared up back to normal?
The point of the BootStraps class is to look up by reflection a generated code class.  Any idea what's holding on to the reference to keep it from being GC'd (if that's truely the case)?

Did you using MAT analyzer and  dump the gradle daemon ? mine will have like 1.2 gb of hprof file after 2 build with --rerun-tasks.
If you perform a GC after the build is memory cleared up back to normal?
No it is  still leak after i pressed GC. This is the detailed leak i just capturing.

I think
scoped org.parceler.ParcelAnnotationProcessor$$Bootstrap @ 0x76521f2d0
and REPOSITORY  class org.parceler.transfuse.bootstrap.Bootstraps @ 0x76521e9f8
cannot be GC ? because seems they are static  object

is it because scoped with @bootstrap causing ParcelAnotationProcessor cannot be GC'd. ParcelAnnnotationProcessor itself become really huge because it contains and refer to Bootstraps  which also hold REPOSITORY object.  Does the Bootstraps will getting huge as more class using @parcel  ? wondering if somehow we can  destroy the bootstraps/REPOSITORY object, so even though parcelAnotation cannot be  GC'd at least it only leaking very less amount of memory.

This should be easy to fix then.. just need to remove the cache located here.

it should be worth if it safe to remove that field. I would love to try that, can you give me advice how to try that on some branches or patch ?
https://github.com/google/dagger/commit/2902519e0b2128047c53f1c36574a6ac36bd8c85
Dagger also got similar issue with cache holding huge object on memory, and they remove the cache  entirely.

This should do the trick: https://github.com/johncarl81/transfuse/tree/remove_bootstraps_repo.  To test, you build Transfuse and install it into your local maven repo.  Next, you'll need to change this in Parceler: to 0.3.0-SNAPSHOT, built it and install it into your local maven repo.  Finally, in your project, reference your local maven repository to build in gradle (mavenLocal())

Thanks @johncarl81 , i already build the maven and tried it on our project. The leak has gone and daemon not stuck anymore, it certainly giving huge impact into our full  build.
Would very love to use this fix version very soon 👍

Awesome!  Thanks for testing it out.
We do use a similar technique in the Parcels utility here.  I imagine that the Bootstraps issue is more prevalent because new keys are used for each run, vs the same class keys used in the Parcels class.  But, Parcels is used during runtime, which would be a much larger issue for users.  Do you see any memory issues around the Parcels utility class for your project?

So the generatedMap will hold all generated all at once, or load it one by one depends on which page we opened ? so far i don't see any issue with this. I do a quick check on our app and that object seems only around 1.4kb in runtime memory.  this is the object of generatedMap on runtime:

Parcels loads the generatedMap lazily, and holds it for the lifetime of the application.  It really shouldn't load much and mitigate some runtime overhead of loading class definitions using reflection.

I see, I think it is fine to our apps with current behaviour on Parcels class. As it  not load much memory and can mitigate runtime overhead as you said.

Ok, ill look at making a release shortly with this update.

Hi @johncarl81, I hope you are doing well. Any chance this Bugfix will be deployed soon ? Thanks

Shoot, I've been meaning to do a release, just been backed up with other priorities.  Keep bugging me if I don't get to it.

Understood, thank you for letting me know your situation. I will remind you again in weeks :)

Released to maven central under 1.1.13.

Thank you for the release and fix this issue, greatly appreciate your time.

@doniwinata0309, just to be doubly sure, is this release working 100% for you now?

I did benchmark today at my CI, so far i did not see any significant improvement on build speed as i expected. But from visual VM using very less memory footprint compared to previous one.  Does the change https://github.com/johncarl81/transfuse/commit/a5ec966d19463a66fb1090e49f5f5fb0c2d9083a possibly will causing more cpu usage because it removing static classes that hold generated code ?   I will give more info after checking the cpu usage on this release comparing to the previous one.

Perhaps.  It will have to stand up the environment fresh for each run of the processor, but that's what we want here.  Curious to see your results.

Hi @johncarl81 , i analysed parceler 1.1.12 and 1.1.13 to our build in this doc:
Parceler 1.1.13-2.pdf
I think the profiler showing no huge differences on cpu activity and number of threads. The memory footprint on 1.1.13 is much better and causing less major GC (which is very good). So we decide to update it later. I am not sure yet what causing memory spike when processing application module, probably not related to parceler.
Let me know what do you think about the doc.

Good stuff @doniwinata0309.  Is this analyzed against https://github.com/doniwinata0309/build-perf-test/tree/test/parceler ?

No, it is the test result from my real project actually 😄

Sure, i will let you know if i find some similar problem again, so far it looks good on the newest Android Gradle Plugin. I really appreciate your time on fixing this issue. Thanks for your help   🙏 🙏


reveal a subset of TypeScript that is 100% guaranteed type-safe

this is ridiculous: https://github.com/Microsoft/TypeScript/issues/13002
my problem is that when i see  something claimed  done "we have readonly properties" i trust this statement and i am eager to use them, it turns out i should have not tried, because well they are not done
there is no reason to lie about what TypeScript can and cannot do
please be honest to your users
there is a sub-set of typescript that works 100% typesafe guaranteed, few people know what it is
the design team can and should be open and explicit about it, hence the request

Not happening. PureScript, Haskell -> JS, etc are all options if you want to go down this route.

Not happening what? You can't add to the release notes a side note in a fine font saying:
* - overdramatization, not for real use

Why not?

Why can't you be honest about what your features can and cannot do?

If you just want to vent, please install https://chrome.google.com/webstore/detail/complain-on-twitter-for-g/ionkpikblpmdnbakeihghkmgbchcfeii

i am just asking you a simple fair question, why can't you be honest about know limitations?

We don't lie about what things do and don't do, so please don't accuse us of that. I'm sorry that readonly doesn't meet your expectations, but we made the intentional decision to make it work that way so that it could find real usage in many common scenarios. Given a magic wand to release the first version with built-in readonly support we probably would have gone a different way, but these things are path-dependent.
100% soundness continues to be an explicitly-documented non-goal. I get that you don't agree with that goal - it's understandable - but it's always been the case and asking for two years for the language to move in a 90 degree turn from its explicit goals is not productive.

readonly means only reading, TS did lie (see #13000) or is horrible at
giving names, I understand I can't have all, I don't understand loud
statements proved to be wrong
On Dec 17, 2016 4:21 PM, "Ryan Cavanaugh"<EMAIL_ADDRESS>wrote:

We don't lie about what things do and don't do, so please don't accuse us
of that. I'm sorry that readonly doesn't meet your expectations, but we
made the intentional decision to make it work that way so that it could
find real usage in many common scenarios. Given a magic wand to release the
first version with built-in readonly support we probably would have gone
a different way, but these things are path-dependent.
100% soundness continues to be an explicitly-documented non-goal. I get
that you don't agree with that goal - it's understandable - but it's always
been the case and asking for two years for the language to move in a 90
degree turn from its explicit goals is not productive.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/TypeScript/issues/13003#issuecomment-267787568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5PzS_h57qOerOGdfmaDGMo2XcxE8CBks5rJFJVgaJpZM4LP-cL
.

Adopting the binary position that a feature is either 100% sound or "useless" would lead to us adding approximately 0 features ever.
readonly prevents direct mutation of the declared property through that reference. That's it. Doesn't go far enough? Fair criticism. A lie? No. It's still useful, e.g. #10097.

Much better

Can't see foe it is useful in #10097 or anywhere at all. Truth is you are either readonly or you are not. Anything in between doesn't make any sense, no matter how you put it. It's like saying that a boolean can in facT be true false or something else. Thus there was no single reason to go this way. Especially for a brand new feature that is by definition an opt in thing. It cannot break anything unless you deliberately write damn readonly I from of your otherwise perfectly valid code. So nothing you said makes sense. Let alone you didn't answer the fair and simplement question as too why TS can't be honest about limits of their features. You just closed it without consideting to makr an effort to answet it or give explanations.

And for the record I said no single word about going 100% sound or any binary position you mention, the request reads: please make an effort to label your imperfect features as safe and unsafe, please be explicit what unsafe is. That's all. Why does it deserve closing?

@aleksey-bykov You want people to discuss things with you when you make accusations and respect no one but yourself? I'd suggest you to watch your tone if you want them to take you seriously or even listen to your feedback.

Quote any of my word being disrespectful for start.

@aleksey-bykov Just because something isn't written or someone fail to describe something, doesn't mean he/she lie about it, accusing them for lying is not something you would do out of respect.


A PIN is a password

It doesn't matter what happens after a PIN is used, you still enter it exactly like a password. So it's not even a password replacement, it is a password - the bar to entry is exactly the same. I don't know why MS insists on trying to sell the PIN like it's somehow more secure. A keylogger will record a PIN just the same as it would a password; writing a PIN down on a slip of paper is exactly the same as writing a password on a piece of paper; hiding a camera to record the entry of a PIN is exactly the same as recording a password.
To the end user it doesn't matter how tied to a device a PIN is, because the typical user isn't going to use a different PIN on every device, they're just going to use the same PIN on everything because people are fed up with having to remember so many passwords. Instead of pretending PIN somehow makes Windows more secure, why not actually improve security by making two-factor authentication the norm in Windows?

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

ID: c34dbafa-df3c-a5a5-32d5-2ce152893534
Version Independent ID: cebdd9a6-45d7-6306-373c-7d31121f9e16
Content: Why a PIN is better than a password (Windows 10)
Content Source: windows/security/identity-protection/hello-for-business/hello-why-pin-is-better-than-password.md
Product: w10
GitHub Login: @DaniHalfin
Microsoft Alias: daniha

@bertfw - thank you for engaging with the community here for the docs.
I know the product teams are always looking for user feedback on how to make Windows 10 better. They keep a close tab on user feedback and it would be awesome if you could add your voice in
User Voice https://support.microsoft.com/en-za/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub
You might find others have made a similar request that you can add to, or you can open a new one. Let us know here if you do so we can up-vote your request.

@AndreaBarr - This issue can be closed.


Add proxy option for HTTP client to fetch content

In some environments, self-host server network can not access feed content directly. To support optional proxy option is useful for special feed .
In this commit, add Fetch via proxy function for add/edit feed UI, also api payload.

Why only some feeds would need the proxy? Why not use the proxy for all HTTP requests?

The feature fetch_via_proxy should be available in the web ui and API only if the global config option HTTP_CLIENT_PROXY is configured.

That because the network will filter some of websites, and if we are using proxy for all sites, will cause another sites fetch slow. e.g.: In China, we can’t access twitter.com directly, so we are using a proxy for access it, but we don’t use a proxy for access weibo.com.

Yes, that will be better. Thanks

The feature fetch_via_proxy should be available in the web ui and API only if the global config option HTTP_CLIENT_PROXY is configured.

I have reconsider this suggest. This option should always available in web ui and API, but it's only useful when the global config option HTTP_CLIENT_PROXY is configured.
There are two cases:

subscribe feed, to hide fetch_via_proxy option web ui is ok if the HTTP_CLIENT_PROXY is not configured.
edit feed, to hide fetch_via_proxy option may be confusion for the feed which already enable proxy.

hi @fguillot, do you have any suggestions on this PR ?

My comment still the same. Think about other people use case and the user experience with the default settings. The proxy feature should be visible/available only when HTTP_CLIENT_PROXY is configured.

My comment still the same. Think about other people use case and the user experience with the default settings. The proxy feature should be visible/available only when HTTP_CLIENT_PROXY is configured.

Now it's ready.
When HTTP_CLIENT_PROXY not present, Fetch via proxy option not visible from web UI.

Adding new subscription still problematic. Try by yourself.
When you select "Fetch via Proxy" on this screen:

It doesn't get saved into the database. Look at the edit feed page:

Same thing applies when the user have to choose between multiple subscriptions:

Just fix that

The 2nd scenario is not covered. Try with a website that propose more than one feed: https://daringfireball.net/

Now, fetch_via_proxy state will be take to choose subscription page, also submitted from choose subscription page.

Good improvements, Thanks!


Message type "apollo.planning.ADCTrajectory" has no field named "adc_trajectory_point".

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Linux Ubuntu 18.04
Apollo installed from (source or binary): binary
Apollo version (3.5, 5.0, 5.5, 6.0): 5.0

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

I am running the python example in modules/tools/planning/plot_trajectory, and I ran the main function by the following command in docker:
python main.py 1_planning.pb.txt 1_localization.pb.txt

And the error message is below:

I checked the eror message, i thought it was the message type is wrongly defined, i located the ADCTrajectory message in modules/planning/proto, and i modify trajectory_point to adc_trajectory_point and re-ran the command. But i sitll output the error message as before

Anyone know what's the problem? I am using Apollo 5.0, is this a bug in this version?

I think it's outdated now. Both the python code and "1_planning.pb.txt" need to be modified. As you can see, the following code cannot match any messages. It replaced by apollo.common.TrajectoryPoint.
adc_trajectory_point {
  x: -124.367072419
  y:<PHONE_NUMBER>42
  z: -31.332377322

  speed: 1.62222218513
  acceleration_s: 0.786162598236
  curvature: -0.00252617800322
  curvature_change_rate: 0
  relative_time: -0.089999914169311523
  theta: -1.81237826921
  accumulated_s: 0
}

I think it needs to be updated before it can work

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


New article: Interact with private AKS cluster using Azure Bastion and Azure DevOps

Proposing a PR for an additional guidance on interacting with private AKS cluster through Azure Bastion and Azure DevOps. This guidance will enable developers to be productive with private AKS cluster without needing setup such as vnet peering or hub and spoke network implementation.

Hi @Mahesh-MSFT
Contributors who work in the Product Manager role should work in the private repository for advanced quality validations and staging. New content, in particular, needs the benefits of the quality checks that are available in the private repo.
For details, see Should I work in a private or a public repo? and Tutorial: Make changes to an article published on docs.microsoft.com.
Would you make the updates in the private repo? We'll close this PR. Thanks!


this.setOverflow("hidden");

在执行react-native是报了这个错误

Task :react-native-maps:compileDebugJavaWithJavac
/Users/wenkui/Documents/gator-work/codes/Gatorand/node_modules/react-native-maps/lib/android/src/main/java/com/airbnb/android/react/maps/ViewAttacherGroup.java:23: 错误: 找不到符号
this.setOverflow("hidden"); // Change to ViewProps.HIDDEN until RN 0.57 is base
^
符号: 方法 setOverflow(String)
注: 某些输入文件使用或覆盖了已过时的 API。
注: 有关详细信息, 请使用 -Xlint:deprecation 重新编译。
注: 某些输入文件使用了未经检查或不安全的操作。
注: 有关详细信息, 请使用 -Xlint:unchecked 重新编译。
1 个错误

react-native：0.48.0
react:16.0.0-alpha.12
react-native-maps:0.21.0
How do I compile the past?

I am also getting this error. What is the solution?

me too , can you help me ?  What is the solution? @GoodCloudRepair and @sankalpgoibibo , thanks

@andikare This is due to compatibilty issue between the particular version of react-native and react-native-maps that you are using.
From the docs:

Due to the rapid changes being made in the React Native ecosystem, we are not officially going to support this module on anything but the latest version of React Native. With that said, we will do our best to stay compatible with older versions as much that is practical, and the peer dependency of this requirement is set to "react-native": "*" explicitly for this reason. If you are using an older version of React Native with this module though, some features may be buggy.
So go to the releases tab of react-native-maps, figure out the release date of your react-native version and try versions of maps released within the next one month. This fixed it for me. I was using 0.19.0 and downgraded myself to 0.18.3(RN version 0.49.3) to fix it.
Also you can comment out that particular line that is throwing exception and it seemed to work fine. You never know what breaks, so I would recommend the former method.

thankyou for the response @sankalpgoibibo , but still not work on my project,
this is my Environment
react-native: 0.48.2
react: 16.0.0-alpha.12
android:
compileSdkVersion: 27
buildToolsVersion: 27.0.1
minSdkVersion 16
targetSdkVersion 22
and my package.json
"dependencies": {
"multer": "^1.4.1",
"native-base": "^2.3.1",
"react": "16.0.0-alpha.12",
"react-native": "0.48.2",
"react-native-camera-roll-picker": "^1.2.3",
"react-native-contacts": "^2.2.2",
"react-native-encrypt-decrypt": "^1.0.0",
"react-native-firebase": "^4.3.8",
"react-native-fs": "^2.12.0",
"react-native-gifted-chat": "^0.2.7",
"react-native-google-places-autocomplete": "^1.3.9",
"react-native-maps": "^0.22.1",
thank you

Ok, so I downgraded to npm install<EMAIL_ADDRESS>and it finally compiled for me.

But thanks @harshitsaamu


Numcodecs 0.7.0 fails with Zarr package

Minimal, reproducible code sample, a copy-pastable example if possible
from zarr import Blosc

Problem description
I installed numcodecs latest 0.7.0 version, but found that zarr did not work properly with it. Downgrading numcodecs to version 0.6.4 resolved this issue.
Moreover, I had to install a bunch of dependency head files in Ubuntu to make the installation of numcodecs v0.7.0 succeed (see below):
sudo apt install libblosc-dev libzstd-dev liblz4-dev
conda activate pegasus-python37
pip install zarr

Then the code sample above gives the following error message:
>>> from zarr import Blosc
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'Blosc' from 'zarr' (/opt/miniconda3/envs/pegasus-python37/lib/python3.7/site-packages/zarr/__init__.py)

Version and installation information
Please provide the following:

Value of numcodecs.__version__: 0.7.0
Version of Python interpreter: 3.7.9
Operating system (Linux/Windows/Mac): Ubuntu Linux 20.04
How NumCodecs was installed (e.g., "using pip into virtual environment", or "using conda"): In conda environment, use pip install numcodecs.

My zarr version is 2.4.0.
Also, if you think it might be relevant, please provide the output from pip list or
conda list depending on which was used to install NumCodecs.

Probably related to my issue. Seems like the 0.7.0 distros are missing some components (like blosc):
https://github.com/zarr-developers/numcodecs/issues/242

Duplicate of https://github.com/zarr-developers/numcodecs/issues/242

Closing to consolidate conversation. Please follow along in issue ( https://github.com/zarr-developers/numcodecs/issues/242 ). Thanks!

@yihming, I just pushed out 0.7.1 which appears to work in a fresh ubuntu:16.04 docker image:
    1  apt-get install libblosc-dev libzstd-dev liblz4-dev # Likely
    2  apt-get update
    4  apt-get install python3
    9  apt-get install python3-venv
   10  python3 -m venv /tmp/z
   12  /tmp/z/bin/pip install -U pip
   14  /tmp/z/bin/pip install -U setuptools
   15  /tmp/z/bin/pip install zarr
   16  /tmp/z/bin/python -c "from zarr import Blosc"

Thank you so much for your quick response. I'll try it later and let you know.

Version 0.7.1 works properly with zarr now. Thank you again for your work!