Remappings example for brownie

Hi Juan!
Thank you so much for the remapping addition, this is huge!
So for a brownie project, in my contracts I have something like:
import<EMAIL_ADDRESS>
And the package is located at:
<EMAIL_ADDRESS>
I can't seem to get the settings write for Source<EMAIL_ADDRESS>not found: File import callback not supported to go away. Any thoughts?
The following doesn't seem to be working:
  "solidity.remappings": [
    "<EMAIL_ADDRESS>  ]

Ah.. @PatrickAlphaC all the mappings are setup to be relative to the folder. I need to change that when prefixed by "/" or "C:", thanks for pointing that out.

@PatrickAlphaC check the latest release and let me know how it goes, added the absolute support.

@juanfranblanco don't want to speak for Patrick, but I was running into this same issue and going insane trying to google it and figure out how to make this extension work better with brownie. finally came across this issue. the remappings setting you listed above worked for me and the infuriating "File import callback not supported" highlight has gone away. thank you very much.

@Brodan thank you very much for confirming this. I wanted to validate it before updating the Readme. Note that you can also add a remappings.txt file with each remapping included in a new line.

I was being a dunce, got it :D
Example:
"solidity.remappings": [
    "<EMAIL_ADDRESS>    "<EMAIL_ADDRESS>  ]

Hi @juanfranblanco, so found out another edge case though :(
"solidity.remappings": [
    "<EMAIL_ADDRESS>    "@openzeppelin/contracts-upgradeable/=/Users/patrick/.brownie/packages/OpenZeppelin/<EMAIL_ADDRESS>  ]

If I have 2 repos from the same org, the remappings settings file doesn't know how to handle this. Is this something we could fix too?

Additionally.... it would be great to add home directory functionality, ie:
~/

instead of absolute... Thanks again for taking a look!

@PatrickAlphaC let me check that, yes I can see the issue with matching the first element.
Also. yes the extension does not translate ~, only works with absolute / relative.
Note that there are two remappings, one for the compiler and one for the extension to find imports, autocomplete etc.

What ~ path? There's no ~ in these remappings. I don't understand the question.

@cameel oh I meant, if the ~ should be supported, and if it is currently supported.

Hi, is there any solution regarding this solidity.remappings path issue when developing on different platforms?
I cannot 'dupe' the remapping like so, because it doesn't support fallback behavior (or at least on Mac it works, and on Windows it does not):
"solidity.remappings": [
    "<EMAIL_ADDRESS>    "<EMAIL_ADDRESS>]

I also cannot use VS Code environment variables:
"solidity.remappings": [
    "<EMAIL_ADDRESS>]

And as far as I know, VS Code does not support platform specific settings.

Hey, that is an interesting thought! Having those env values.

Do you have a node example to quickly test it?


feat: get canonical id from group resource

Description of your changes
This PR adds option to reference the Group resource to get canonical id to create Group Alias.

Fixes #
I have:

[X] Read and followed Crossplane's contribution process.
[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

@ulucinar / @sergenyalcin - I don't know how to test it locally. I tried both make run and make reviewable test both unable to find the targets in Makefile. Could you please help?


Date picker RTL support

Bug, feature request, or proposal:
Bug
What is the expected behavior?
RTL support

What is the current behavior?

What is the use-case or motivation for changing an existing behavior?
It should look properly when dir="rtl" is set on the body element
Steps to reproduce
Add dir="rtl" to body element

Is there anything else we should know?
I was able to get the right look by adding dir="rtl" directly on the date picker element

From some quick testing it works for me. Are you adding/changing the dir dynamically after the datepicker has been created?

@crisbeto No, I sat it in the body in index.html

I don't think I can reproduce it in a stackblitz because it doesn't have index.html, so I made this repo (sorry I just pushed the project as it is) but it is straightforward. the date picker is defined in this file
Click on "file" button to see the date picker

Thanks, I see what you mean now. The issue comes from the fact that when Material opens an overlay (in your case a dialog and a datepicker), it defaults to the direction being ltr, unless you've passed in something different. I've submitted a PR that will default to the direction from the body, but until it gets released you can fix your issue by setting the direction explicitly in your dialog config:
dialog.open(DialogComponent, {
  direction: 'rtl'
  // some other dialog configuration...
});

@crisbeto Great! Thank you.


SIGPIPE killed prometheus and alertmanager (journald restart)

What did you do?
restarted systemd-journald.service
What did you expect to see?
prometheus should not bei killed
What did you see instead? Under which circumstances?
prometheus was killed, after I restarted the above service. Only prometheus, alertmanager, grafana and the prometheus mailexporter were killed on different servers.
Environment

System information:

Linux 3.16.0-4-amd64 x86_64

Prometheus version:

prometheus, version 0.20.0 (branch: master, revision: f8bb0ee)
build user:       johannes@local
build date:       20160710-00:19:46
go version:       go1.6.2

Alertmanager version:

alertmanager, version 0.3.0 (branch: master, revision: d263b7ab9aa8ae6213b45ba3c959d02c9600955c)
build user:       johannes@local
build date:       20160905-16:00:39
go version:       go1.7

Prometheus configuration file:
I think this is not relevant.

Alertmanager configuration file:
I think this is not relevant.

Logs:

Dec 01 17:54:40 hostname systemd[1]: prometheus.service holdoff time over, scheduling restart.
Dec 01 17:54:40 hostname systemd[1]: Stopping Prometheus Server Instance...
Dec 01 17:54:40 hostname systemd[1]: Starting Prometheus Server Instance...
Dec 01 17:54:40 hostname systemd[1]: Started Prometheus Server Instance.

Dec 01 18:03:35 hostname systemd[1]: Starting Prometheus Alertmanager Server Instance...
Dec 01 18:03:35 hostname systemd[1]: Started Prometheus Alertmanager Server Instance.

The difference between prometheus.service and prometheus-alertmanager.service is, that the following option is set in the prometheus config file:
Restart=always

Can't reproduce. Please reopen if you have evidence this is a bug in Prometheus.


NPC show as Unconscious and not dead

Hello When I apply dead to npc tokens it only show as unconscious and not dead. But is not the same for pc tokens
PC

NPC or creature

How can I make sure the npc also dies?

What system are you on?


multi day events - 1st day not showing after update

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Hi,
cool calendar at all, but after update to 7.7.1  the multi-day events are do not show the 1st day.
before, the 1st day was not shown as all-day event but as normal event from 12am to 12pm and the following events were shown as all-day event in calendar mode and in event mode.
Settings:
showMultiDayEventParts: true
showMultiDay: true
When I set showMultiDay: false, the second day is shown, but not the 1st day...
Expected behaviour
all days from multi-day events shown as all-day events on all days
Steps To Reproduce
No response
Mode
Both
Card Version
7.7.1
Home Assistant Version
2023.8.3
Configuration
type: custom:atomic-calendar-revive
name: Kalender
enableModeChange: false
entities:
...
showDate: true
showLocation: true
sortByStartTime: true
showAllDayEvents: true
calShowDescription: true
hideFinishedEvents: false
showRelativeTime: true
showMultiDayEventParts: false
showDeclined: false
compactMode: false
offsetHeaderDate: true
defaultMode: Calendar
showLastCalendarWeek: true
disableCalLink: true
disableCalLocationLink: false
disableCalEventLink: false
showMultiDay: false
showFullDayProgress: false
showEventIcon: false
hoursOnSameLine: true
linkTarget: _top
maxDaysToShow: 60
startDaysAhead: 0
view_layout:
  grid-area: header1
card_mod:
  style: >
    table.cal {
      height: 580px !important;
      }
    ha-card {
      background: rgb(17,18,23) !important;
      border-radius: 20px;
      font-size: 18px;
      font-weight: normal;
      border: solid 2px black;
      height: 825px !important;
        }
    .calIcon {
      --mdc-icon-size: 18px !important;
        }
    td.cal {
      vertical-align: top !important;
      }
    ha-card > div.cal-eventContainer > div.calTableContainer > table > tbody >
    td > div > div {
      padding-bottom: 5px !important;
      width: 60px !important;
      }
    .calDay {
      max-width: 60px !important;
      }

Relevant log output
No response
Code of Conduct

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

cardHeight: 100%
fullDayEventText: All Day
untilText: Until
maxDaysToShow: 6
maxEventCount: 0
showLoader: true
showLocation: false
showMonth: false
showWeekDay: true
fullTextTime: true
showCurrentEventLine: false
showDate: false
dateFormat: LL
startDaysAhead: 0
showLastCalendarWeek: false
sortByStartTime: false
disableEventLink: false
disableLocationLink: false
disableCalMonthLink: false
linkTarget: _blank
hideDeclined: false
showPrivate: true
showHiddenText: false
hiddenEventText: events are hidden
showCalendarName: false
nameColor: var(--primary-text-color)
dateColor: var(--primary-text-color)
dateSize: 90
descColor: var(--primary-text-color)
descSize: 80
showNoEventsForToday: false
noEventText: No events
noEventsForNextDaysText: No events in the next few days
showNoEventDays: false
timeColor: var(--primary-color)
timeSize: 90
showHours: true
showRelativeTime: true
eventTitleColor: var(--primary-text-color)
eventTitleSize: 100
locationIconColor: rgb(--primary-text-color)
locationLinkColor: var(--primary-text-color)
locationTextSize: 90
hideFinishedEvents: false
dimFinishedEvents: true
finishedEventOpacity: 0.6
finishedEventFilter: grayscale(80%)
dayWrapperLineColor: var(--primary-text-color)
eventBarColor: var(--primary-color)
eventCalNameColor: var(--primary-text-color)
eventCalNameSize: 90
showProgressBar: true
showFullDayProgress: false
progressBarColor: var(--primary-color)
progressBarBackgroundColor: '#555'
enableModeChange: true
defaultMode: Event
calGridColor: rgba(86, 86, 86, .35)
calDayColor: var(--primary-text-color)
calWeekDayColor: var(--primary-text-color)
calDateColor: var(--primary-text-color)
defaultCalColor: var(--primary-text-color)
calEventBackgroundColor: rgba(86, 100, 86, .35)
calActiveEventBackgroundColor: rgba(86, 128, 86, .35)
calEventSatColor: rgba(255, 255, 255, .05)
calEventSunColor: rgba(255, 255, 255, .15)
calEventTime: false
firstDayOfWeek: 1
refreshInterval: 60
showEventIcon: true
europeanDate: false
hideDuplicates: false
showMultiDay: true
showMultiDayEventParts: true
showWeekNumber: false
showDescription: false
showEventDate: true
showDatePerEvent: false
showAllDayHours: true
showAllDayEvents: true
offsetHeaderDate: false
titleLength: 0
descLength: 0
type: custom:atomic-calendar-revive
name: Termine
entities:
calShowDescription: false
showDeclined: false
compactMode: false
showTimeRemaining: false
view_layout:
grid-area: header2
card_mod:
style: |
ha-card {
background: rgb(17,18,23) !important;
border-radius: 20px;
font-size: 18px;
font-weight: normal;
border: solid 2px black;
height: 623px !important; overflow-y:scroll!important;
}

This is fixed in the release I'm working on, hopefully ready for release today.

thx


Htmlcompanysections

Current coverage is 54.47%

Merging #40 into master will decrease coverage by -1.36% as of 1e7d353

@@            master     #40   diff @@
======================================
  Files            9       9
  Stmts          120     123     +3
  Branches         0       0
  Methods          0       0
======================================
  Hit             67      67
  Partial          0       0
- Missed          53      56     +3

Review entire Coverage Diff as of 1e7d353

Powered by Codecov. Updated on successful CI builds.


Flash enhancements and fixes primarily for STM32 support

This PR includes a number of flash related fixes. The most important is making use of erase sector vs program page sizes for .FLM flash algos coming from CMSIS Packs. This fixes issues with STM32 devices that have such large sector sizes that sector buffer won't fit in RAM. Now pyOCD will use the page size declared in the algo for buffers. This also enabled double buffer support, increasing flash programming speed.
Other included changes.

The debug.log_flm_info user option will cause details of an .FLM flash algo to be logged when it is loaded.
Builtin STM32 targets with large sectors were updated to use different sector/page sizes and enable double buffering.
Fixed an issue with reported erased byte count for flash programming, if the sector size is not the same as the page size.
The commander show map command prints both sector and page sizes.
Fixed flash_loader_test.py for the case where the test binary and generated test data would overlap.
The most recently created Session object is available via Session.get_current(), which allows code that doesn't have a direct reference to a session to make use of user options. This will mostly be used for debug or similar purposes.

Closes #612

/morph test

/morph test


Complete basic cancer use case end-to-end test

Is your feature request related to a problem? Please describe.
We need to create a minimal cancer variant calling pipeline use case setup here

https://github.com/bihealth/snappy-use-case-cancer

Describe the solution you'd like
We should have the following steps

ngs_mapping
somatic_variant_calling

for two or three public cancer exome data sets This could come from public data (ideally) or access-restricted. We could use two germline exomes and use one as proxy cancer and one as proxy tumor. We need to get this done end-to-end and then can refine (refinement out of scope). Data and static data should be downloaded either directly public data or can be deposited on our public file servers.
Describe alternatives you've considered
N/A
Additional context
N/A

I would include RNA sequencing in the cancer use case as well. In addition, the following steps should be included

hla_typing
gene_expression_quantification
somatic_targeted_seq_cnv_calling
variant_annotation
variant_filtration
cbioportal_export (=variant-export)

I adjusted my text for copy-and-paste issues.
Let's define "micro milestones" and convert each into a ticket.
e.g.,

[ ] micro milestone: minimal

[ ] ngs_mapping
[ ] somatic_variant_calling

[ ] micro milestone: basic cBioPortal export

[ ] somatic_variant_annotation
[ ] somatic_variant_filtration
[ ] cbioportal_export

[ ] micro mileston: CNV calling

[ ] ...

etc.


nflgame-update-players socket timeout error

Sorry to keep opening issues with your projects (which are great btw thanks for all your hard work).  I got nflvid working now, but I can't seem to get nflgame-update-players to work properly.  I suspect a lot of my issues were related to hacking together old score data downloads, but I've since completely reinstalled all your programs with a fresh db.
$ nflgame-update-players
Loading games for REG 2015 week 1
Downloading team rosters...
/home/dan/.local/lib/python2.7/site-packages/bs4/__init__.py:166: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("lxml"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.

To get rid of this warning, change this:

 BeautifulSoup([your markup])

to this:

 BeautifulSoup([your markup], "lxml")

  markup_type=markup_type))
23/32 complete. (71.88%)Traceback (most recent call last):
  File "/usr/local/bin/nflgame-update-players", line 4, in <module>
    nflgame.update_players.run()
  File "/home/dan/.local/lib/python2.7/site-packages/nflgame/update_players.py", line 398, in run
    for i, (team, soup) in enumerate(pool.imap(fetch, teams), 1):
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 659, in next
    raise value
httplib2.ServerNotFoundError: Unable to find the server at www.nfl.com

Sometimes it ends in a socket.timeout instead of the unable to find nfl.com error
$ nflgame-update-players --full-scan
Loading players in games since 2009, this may take a while...
Traceback (most recent call last):
  File "/home/dan/.local/bin/nflgame-update-players", line 4, in <module>
    nflgame.update_players.run()
  File "/home/dan/.local/lib/python2.7/site-packages/nflgame/update_players.py", line 348, in run
    for _, schedule in nflgame.sched.games.itervalues():
ValueError: too many values to unpack

I've also tried $ nflgame-update-players --simultaneous-reqs 1 which gives the same error.  Sometimes it gets further in the download sometimes it gets not as far...
32/32 complete. (100.00%)
Done!
Fetching GSIS identifiers for players not in nflgame...
90/330 complete. (27.27%)Traceback (most recent call last):
  File "/home/dan/.local/bin/nflgame-update-players", line 4, in <module>
    nflgame.update_players.run()
  File "/home/dan/.local/lib/python2.7/site-packages/nflgame/update_players.py", line 426, in run
    for i, (purl, gid) in enumerate(pool.imap(fetch, purls), 1):
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 659, in next
    raise value
httplib2.ServerNotFoundError: Unable to find the server at www.nfl.com

I have no clue. It is working fine for me here. Can you access www.nfl.com in a browser? It looks like some kind of connectivity problem...

Yes.  Maybe I am being rate limited by nfl.com right now?  I'll try again this weekend from a different ip address.

FWIW, I've never seen nfl.com do rate limiting in the years I've been doing this. Specifically, as long as you're starting with an existing player database, the number of requests sent to nfl.com should be pretty small.

Good to know.  I did try running nfldb-update a few times already today with a much larger database compiled here https://github.com/BurntSushi/nfldb/issues/82 which I think may have been making WAY more requests than intended.

I was able to get this to work today after a few tries.  Maybe just need to catch the error and retry the GET if the first one fails.
$ nflgame-update-players
Loading games for REG 2015 week 1
Finding (profile id -> gsis id) mapping for players...
Traceback (most recent call last):
File "/home/dan/.local/bin/nflgame-update-players", line 4, in
nflgame.update_players.run()
File "/home/dan/.local/lib/python2.7/site-packages/nflgame/update_players.py", line 376, in run
for i, t in enumerate(pool.imap(fetch, players.items()), 1):
File "/usr/lib/python2.7/multiprocessing/pool.py", line 659, in next
raise value
httplib2.ServerNotFoundError: Unable to find the server at www.nfl.com
$ nflgame-update-players
Loading games for REG 2015 week 1
Finding (profile id -> gsis id) mapping for players...
83/101 complete. (82.18%)Traceback (most recent call last):
File "/home/dan/.local/bin/nflgame-update-players", line 4, in
nflgame.update_players.run()
File "/home/dan/.local/lib/python2.7/site-packages/nflgame/update_players.py", line 376, in run
for i, t in enumerate(pool.imap(fetch, players.items()), 1):
File "/usr/lib/python2.7/multiprocessing/pool.py", line 659, in next
raise value
httplib2.ServerNotFoundError: Unable to find the server at www.nfl.com
$ nflgame-update-players
Loading games for REG 2015 week 1
Finding (profile id -> gsis id) mapping for players...
101/101 complete. (100.00%)
Done!
Downloading team rosters...
/home/dan/.local/lib/python2.7/site-packages/bs4/init.py:166: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("lxml"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.
To get rid of this warning, change this:
BeautifulSoup([your markup])
to this:
BeautifulSoup([your markup], "lxml")
markup_type=markup_type))
32/32 complete. (100.00%)
Done!
Fetching GSIS identifiers for players not in nflgame...
222/222 complete. (100.00%)
Done!

I know this is an old issue but I found the source of the problem.  This is sort of unrelated to nflgame as I found the same issue with other scrapers and it was due to my poor wifi connection and lost packets.  The solution was to retry all get requests if the first one fails.  For a code sample I replace all
req = requests.get(url)

with
''' Get a url and return the request, try it up to 3 times if it fails initially'''
def retry_request(url):
    session = requests.Session()
    session.mount("http://", requests.adapters.HTTPAdapter(max_retries=3))
    return session.get(url=url)

req = retry_request(url)


feature: adding api_base option

Thanks for your PR. Can I ask why this dynamic api_base is needed? I did a search and did not find anything about this base url in the Intercom docs. Could you provide a link to your source?

This is a bug of Intercom, some Internet Service Providers in Vietnam are not connecting to Intercom. Intercom added api_base attribute to their config

I see, but I would like a url to some official documentation so I can confirm this. Could you add some tests to make sure there are no side effects?

@doankhoi Have you got any update on this? Otherwise I'm inclined to close this PR.

Saw another related issue for a simular Intercom solution: https://github.com/intercom/intercom-rails/pull/329/files

Hello ! Is this fix still up-to-date ? I tried to use the apiBase prop without success. It seems that the official API Doc has changed slightly, introducing a discrepancy between react-use-intercom, and Intercom.
The documentation ( https://developers.intercom.com/installing-intercom/docs/basic-javascript ) gives 3 possible values for api_base :
Regional Location | API Base to Set
US | https://api-iam.intercom.io
EU | https://api-iam.eu.intercom.io
Australia | https://api-iam.au.intercom.io
Hence I don't think the react-use-intercom feature is up-to-date. See current explanation about IntercomProvider's props apiBase :
"apiBase | If you need to route your Messenger requests through a different  endpoint than the default. Generally speaking, this is not needed. Format: https://${INTERCOM_APP_ID}.intercom-messenger.com"
I have tried both https://api-iam.eu.intercom.io and https://${INTERCOM_APP_ID}.intercom-messenger.com apiBase formats, without success.
To bypass that problem, I need to delete react-use-intercom and use the traditional HTML Intercom implementation.
Thanks !

Hi, indeed the according documentation is outdated, but the functionality hasn't changed. You can still set the apiBase if required

It does not work for me as well.
I tried to implement it for EU | https://api-iam.eu.intercom.io/
Removing the react-use-intercom package from my project.


bundle-gen.py: Set the url of the origin remote unconditionally

When opening PRs, bundle-gen will re-use one of the repositories cloned earlier to save a clone.  However, the origin of this repository points to the upstream reposistory instead of the fork repository.
/cc @lleshchi @2uasimojo
/assign @lleshchi

Ah. Maybe we should just make this clone from the fork repo instead. @lleshchi wdyt?

...except I guess we would have to be careful to fast-forward the fork in that case.
(This is all my fault -- I suggested DRYing the clone.)

@2uasimojo I'm in favor of the current solution as I think it is clearer to follow.

/lgtm


MarkdownV2 support?

At telegram api docs present parse_mode = MarkdownV2.
I tried to send some data and find, that needed new escape for support this format.
https://core.telegram.org/bots/api#markdownv2-style
    public static function escapeMarkdownV2($text)
    {
        $markdown = [
            '#',
            '*',
            '_',
            '=',
            '.',
            '[',
            ']',
            '(',
            ')',
            // ... rest of markdown entities
        ];
        //'_‘, ’*‘, , ’~‘, ’`‘, ’>‘, ’#‘, ’+‘, ’-‘, ’=‘, ’|‘, ’{‘, ’}‘, ’.‘, ’!‘
        $replacements = [
            '\#',
            '\*',
            '\_',
            '\\=',
            '\.',
            '\[',
            '\]',
            '\(',
            '\)',
            // ... rest of corresponding escaped markdown
        ];

        return str_replace($markdown, $replacements, $text);
    }

Something like this, as i think.

@asafov Have created a PR for you to review 👌

Are you planning to support auto escaping?
May be i create a PR for it?
I think it would be really convenient to pass second argument for markdownV2 for escaping

@devope THIS!


Convert check_pinned_packages & pfs-swift-load-plot to py3

Is it safe to assume I need to match some of these changes in SAIO et. al.?


Timeline scroll position is not preserved after navigating to a post and returning

When scrolling down the timeline and then clicking on a post to view or comment on it, upon returning to the timeline, the scroll position resets to near the top of the page. The previous scroll position is not preserved.
It seems like there might be a missing scrollPositionRestoration option in the route configuration. Implementing this would greatly improve the user experience by allowing users to continue from where they left off in the timeline after interacting with a post.

I think I manage to figure out solution also for user's profile.


[CH][HOTFIX] Fix compile error after merging PR#5308

What changes were proposed in this pull request?
Fix compile error after merging PR#5308
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_master_04_22_2024_time.csv
log/native_master_04_21_2024_b08258e51_time.csv
difference
percentage

q1
36.84
34.90
-1.936
94.75%

q2
26.10
24.06
-2.038
92.19%

q3
37.15
36.70
-0.446
98.80%

q4
40.55
40.96
0.408
101.01%

q5
71.41
69.60
-1.809
97.47%

q6
7.43
7.44
0.015
100.20%

q7
85.19
85.59
0.398
100.47%

q8
87.61
85.37
-2.241
97.44%

q9
125.61
125.78
0.171
100.14%

q10
44.30
43.35
-0.944
97.87%

q11
20.56
19.84
-0.717
96.51%

q12
25.45
25.80
0.347
101.36%

q13
57.20
54.10
-3.100
94.58%

q14
17.68
21.91
4.235
123.96%

q15
30.05
29.24
-0.809
97.31%

q16
12.69
14.28
1.592
112.54%

q17
100.75
101.35
0.597
100.59%

q18
144.04
145.10
1.058
100.73%

q19
14.98
13.61
-1.367
90.87%

q20
28.30
28.46
0.156
100.55%

q21
285.90
287.28
1.380
100.48%

q22
14.83
14.78
-0.052
99.65%

total
1314.62
1309.52
-5.100
99.61%


Upgrade Jinja2 to 2.8

Quick FYI – 2.8 hasn't actually been formally released yet – http://jinja.pocoo.org/docs/dev/changelog/#version-2-8


How to resync the node ?

@NauvalRizki
It looks like there is a typo in your command; the port should be 8545 (unless you changed it). If you changed it, please make sure the node is running and also that the port is open.


Right after cloning the project into Windows environment, a lot of files are being marked as deleted.

Right after cloning the project into Windows environment, a lot of files are being marked as deleted.
I presume that there might be some conflict in the way, where different environments set up the directory structure?
C:\Users\dmitrijsbalcers\Documents\GitHub\SpaceTalk>git status
On branch develop
Your branch is up-to-date with 'origin/develop'.

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

        deleted:    packages/useraccounts:core/.editorconfig
        deleted:    packages/useraccounts:core/.gitignore
        deleted:    packages/useraccounts:core/.jshintignore
        deleted:    packages/useraccounts:core/.jshintrc
        deleted:    packages/useraccounts:core/.travis.yml
        deleted:    packages/useraccounts:core/Guide.md
        deleted:    packages/useraccounts:core/History.md
        deleted:    packages/useraccounts:core/LICENSE.md
        deleted:    packages/useraccounts:core/README.md
        deleted:    packages/useraccounts:core/lib/client.js
        deleted:    packages/useraccounts:core/lib/core.js
        deleted:    packages/useraccounts:core/lib/field.js
        deleted:    packages/useraccounts:core/lib/methods.js
        deleted:    packages/useraccounts:core/lib/server.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_error.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_form.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_input.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_message.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_nav_button.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_oauth.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_pwd_form.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_pwd_form_btn.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_pwd_link.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_reCaptcha.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_result.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_sep.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_signin_link.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_signup_link.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_social.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_terms_link.js
        deleted:    packages/useraccounts:core/lib/templates_helpers/at_title.js
        deleted:    packages/useraccounts:core/lib/utils.js
        deleted:    packages/useraccounts:core/package.js
        deleted:    packages/useraccounts:core/tests/tests.js

Any suggestions how to solve this?

It's the colon in useraccounts:core directory. Windows doesn't support colons in dirnames.

@hellstad wow good one @rclai could you fix this maybe?

Try that.

This issue is resolved, thank you.


ClientError: An error occurred (InvalidParameterCombination) when calling the DeleteDBInstance operation: FinalDBSnapshotIdentifier can not be specified when deleting a cluster instance

2017-05-11 11:06:58,017: custodian.output:ERROR Error while executing policy
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/c7n/policy.py", line 241, in run
results = a.process(resources)
File "/usr/lib/python2.7/site-packages/c7n/resources/rds.py", line 607, in process
client.delete_db_instance(**params)
File "/usr/lib/python2.7/site-packages/botocore/client.py", line 253, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/usr/lib/python2.7/site-packages/botocore/client.py", line 557, in _make_api_call
raise error_class(parsed_response, operation_name)
ClientError: An error occurred (InvalidParameterCombination) when calling the DeleteDBInstance operation: FinalDBSnapshotIdentifier can not be specified when deleting a cluster instance

thanks for the bug report.
this should be getting filtered out by the _db_instance_eligible_for_final_snapshot but it looks like the condition using its output has a logic flaw.

Error appeared when I was trying to delete Aurora instances


Question about a MJCF element

Hello, I am a student who is studying pick and place of robot using Mujoco.
I have a question about a MJCF element.
Like the picture below, I would like to research that a robot gripper grasps a bottle placed on a shelf.
However, the problem is that the robots' arm doesn't move into the empty space even though there is an empty space on the shelf.
So, I thought that if i change any parameter in the mujoco XML reference, it will be recognized as an empty space.
I am wondering what parameters need to be changed so that the arm of the robot can move into empty space.

The robot's arm cannot move inward.

The xml file of the shelf that is currently set up is as follows.
<mujoco model="shelf">
  <asset>
    <mesh file="meshes/shelf.stl" name="shelf" scale="0.9 0.9 0.9"/>
    <texture file="../textures/yellow-plaster.png" name="dark-wood"/>
    <material name="wood" reflectance="1.0"  texture="dark-wood" texuniform="true"/>
  </asset>
  <worldbody>
    <body name="shelf">
      <body name="collision">
        <geom pos="0 0 0" mesh="shelf" type="mesh" solimp="0.998 0.998 0.001" solref="0.001 1" density="150" friction="0.95 0.3 0.1" material="wood" group="1" condim="4"/>
      </body>
      <body name="visual">
        <geom pos="0 0 0" mesh="shelf" type="mesh" rgba="0 1 0 1" conaffinity="0" contype="0" group="1" mass="0.0001"/>
      </body>
    </body>
  </worldbody>
</mujoco>

Please answer about my question.
Thank you.

In simulate, hit the 'H' key to see the convex hulls of your meshes. This is what you are actually colliding with. A concave shape needs to be composed of a union of convex shapes (mesh or primitive). Load the mug example to see how that can be dove with primitives. Note the collision geometry is in group 3, so you'll need to hit the '3' key to see it.


Binary cards don't flip back to white on chrome

A white card can be clicked on to flip it to black, but a black card cannot be clicked on to flip to white

The issue is the line backface-visibility: hidden; in binary-cards.scss. Without that line it works fine except in firefox where you can now see the numbers through the black cards


Calculation error!

with a large number of operations, it gives an incorrect result!

@yurikosan, thank you!


Adding managed policy schema to Chrome App and Extension to allow policy to be pushed down

I added this to both the app and extension since that seemed to be easier. If you feel strongly that it should be just one rather than both, then please let me know. I think I updated all associated build files as well.

This change is

I realize this won't make it until the next release, but I'm just double checking this is good now that I've removed the changes to the scraps.

:thumbsup:


Function event to go to a specific date in the calendar

I have a datetimepicker widget that is able to select a date, I'd like to know if there's a way to go to a specific date in the calendar and update the view. I know the you can do it at initialization time with the "day:" option, but how would you do it after initialization?
Thanks

Did you find a solution?


Support environment variables in DockerComposeEnvironment

You can do this for GenericContainer by using .withEnv, but there is nothing similar for a DockerComposeEnvironment

Hi @jmacmahon, any reason not to have the env variables defined in the docker-compose.yml file directly?

We would like to specify a temporary source directory for a bind mount defined in the docker-compose.yml file.
A snippet from the file therefore looks like:
    volumes:
      - type: bind
        source: ${BIND_SOURCE}
        target: /whatever

Our test code will create the temporary directory somewhere on the host, and pass it down to docker-compose by setting the appropriate environment variable.
For now, we have worked around this by setting process.env.BIND_SOURCE = cratedTemporaryDirectory before calling new DockerComposeEnvironment(), but this is not ideal.
From this issue: https://github.com/PDMLab/docker-compose/issues/7, it looks like one can simply pass the env parameter to the upAll function in the docker-compose npm package, which I see is what this project uses.

@jmacmahon Thanks for explaining.
Would something like this work? I've deliberately kept the API the same to that of the GenericContainer:
const environment = await new DockerComposeEnvironment(composeFilePath, composeFile)
  .withEnv("ENV_KEY_1", "ENV_VALUE")
  .withEnv("ENV_KEY_2", "ENV_VALUE")
  .up();

const environment = await new DockerComposeEnvironment(composeFilePath, composeFile)
  .withEnv("ENV_KEY_1", "ENV_VALUE")
  .withEnv("ENV_KEY_2", "ENV_VALUE")
  .up();

That looks great 👍

@jmacmahon Just to double check, here's an excerpt from the README in the PR, does it look good to you?

Bind environment variables to the docker-compose file. For example if we have the following docker-compose file:
services:
  redis:
    image: redis:${TAG}

Then we can set TAG as follows:
const { DockerComposeEnvironment } = require("testcontainers");

const environment = await new DockerComposeEnvironment(composeFilePath, composeFile)
  .withEnv("TAG", "value")
  .up();

If so I'll merge and release

@jmacmahon Just to double check, here's an excerpt from the README in the PR, does it look good to you?

Looks good to me, thanks for doing it so quick! Great package 😊

Great, thanks! Released in v7.3.0 🙂


Auto Commenting when a PR is merged

This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.
Could you please assign me this issue under GSSOC'24.

Please assign to me this i want to work on this @Yashshukla11
i am GSSoc Contributor


Fixing an issue with missing folder

If there are no prerendered pages, the build would throw a file not found error since staticDir is rimraf'ed on line 70. It's an odd corner case but I did end up hitting it.
Thank you for publishing this adapter!

Thanks for identifying the issue! I refactored your solution a bit -- instead of creating the directory, we can just move all code that writes to the static directory to after SvelteKit writes the static files. This let me remove another mkdirp call.


fmCheckMate: fmCheckMate > Convert and fmCheckMate > Replace All Again undo the last edit

When fmCheckMate is not available an erroneous undo command undoes the users last edit.

Fixed


Palette: Remember category open/close state across reloads.

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
If you are working on some custom nodes and have them in a new category at the bottom of the list, it's nice to have the others closed even after a page reload.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[ ] I have run grunt to verify the unit tests pass
They seem to fail, but not because of this change.
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 68.193% when pulling a11827222224432dd0fcdccf879cceb5d4eaee13 on dreamair:feature/remember-category-state into 30ea300f65c7bdb880339601461e4001d4fbc0df on node-red:dev.

Hi Bruno, thank you for your contribution.
@knolleary This PR is part of what was introduced in #4634. It can therefore be closed as superseded by #4634.


Add action pod lib lint

Add action pod lib lint

I checked the test result from CircleCI and found that:

Your build ran 1730 tests in RSpec with 0 failures

I don't What needs to be fixed in order to let the tests pass?


Feature: Additional Parser functionality needed for tentris

This PR adds two features to IStreamQuadIterator

The ability to provide custom prefixes during construction

std::istream is{...};
IStreamQuadIterator qit{is, ParsingFlags::none(), {{"xsd", "http://some_url.org"}, {"asd", "http://other.com"}}};

The ability to disable prefix parsing

std::istringstream iss{"@prefix xsd: <http://some_url.org#>"};
IStreamQuadIterator qit{is, ParsingFlag::NoParsePrefix, {{"xsd", "http://some_url.org"}, {"asd", "http://other.com"}}};
assert(qit->has_exception());

Note:
The interface to provide prefixes is not quite optimal since it suffers from two limitations:

The constructor cannot take template arguments since the type is pimpl. Therefore no ranges.
Something like qit.add_prefix("a", "b") wouldn't work since the iterator starts on the first triple, and therefore the prefix wouldnt work for the first triple. Fixing this would require breaking the interface and it would make it weird to use.

If you have a better idea for the prefix interface, feel free to suggest something :)

Do you still plan changes or is there another reason why this is still a draft?

No, I just thought the interface for passing prefixes was kinda ugly and was hoping for a better solution


Add manual mapping validation tests

What
Update mapping generation script with Ontology Mapper v4.2, which now has enhanced mapping validation. Correcting new invalid mappings.
Why
Ensure all manual mappings are valid to allow for Ontology Mapper to generate inferred mappings.

Hi @joebeernink, I've encountered several unexpected errors during the Willow validation tests. A significant number of these errors indicate invalid source and target DTMIs. However, after reviewing them, they appear to be correct. Could you please look into potential causes?


#705 : Fixed countDigits method

Closes #theRelatedIssueNumber

[x] Running yarn lint does not trigger any linter errors
[x] The test of the method you have fixed is passing
[x] You have written a new skeleton method for someone else to work on!
[x] You have written tests to accompany your skeleton method

Please review the Contributing Guide. Thanks!


Glow syntax highlighting for VS code

In GitLab by @plotnick on Aug 5, 2021, 06:03
We should have a VS Code extension that does basic syntax highlighting for Glow programs. This will make the language somewhat more accessible for developers who use that IDE; an Emacs major-mode and VIM plugin are obvious follow-ups.
Apart from the (fairly minimal) boilerplate to create the extension (and which we can also obviously augment in the future), this task involves writing a TextMate grammar file (JSON) that defines tokens as regular expressions; see https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide for details.

See https://github.com/reedjones/vsc-glow-lang for a start on this.

Working on this now
first time making vs code extension and slightly confused on how semantic highlights work https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide


No events for marpa_r_start_input()

The doc says "Events are generated by the marpa_g_precompute(), marpa_r_earleme_complete(), and marpa_r_start_input() methods." (18.1).
However, the doc for marpa_g_precompute() (11.8) and marpa_r_earleme_complete() (12.4) specifies their events as follows:
marpa_g_precompute():
  MARPA_EVENT_COUNTED_NULLABLE
  MARPA_EVENT_LOOP_RULES
  MARPA_EVENT_NULLING_TERMINAL

marpa_r_earleme_complete():
  MARPA_EVENT_EARLEY_ITEM_THRESHOLD
  MARPA_EVENT_EXHAUSTED

and the below events clearly belong to the recognizer (and thus marpa_r_earleme_complete()) only:
  MARPA_EVENT_SYMBOL_COMPLETED
  MARPA_EVENT_SYMBOL_EXPECTED
  MARPA_EVENT_SYMBOL_NULLED
  MARPA_EVENT_SYMBOL_PREDICTED

So, there is apparently no event left to be generated by marpa_r_start_input().

marpa_r_start_input() has the effect of "completing" Earley set 0, so many (most?) of the events that marpa_r_earleme_complete can return are returned by marpa_r_start_input().

Ok. Perhaps a note to that effect in marpa_r_start_input()'s doc (12.4)?

Fixed in the above referenced commit.


[keras example] AttributeError: 'NoneType' object has no attribute 'items'

Environment: Google Colab, Tensorflow 1.15.0
I was trying out one of the examples (examples/tensorflow/keras), and when I was running benchmark session, I got the following error:

Traceback (most recent call last):
File "main.py", line 76, in
evaluate_opt_graph.run()
File "main.py", line 63, in run
for mode, result in results.items():
AttributeError: 'NoneType' object has no attribute 'items'

So I opened the file main.py to inspect the code:
results = evaluator()
for mode, result in results.items():
It seems that results is a NoneType object, which caused the error.

On another note, I wanted to ask about how to setup config for the quantization:

How do I specify the type of quantization, e.g. full integer quantization or 16x8 integer quantization? I see the current method seems to employ the full integer method. So I opened that the sample config file to try to edit the method, but ended up seeing the following parameters
 model_wise:
activation:
algorithm: minmax
I'm not sure how this connects to the quantization method, any hints/help would be greatly appreciated.
Just to be sure, the benchmark statistic
FP32 baseline is: [0.1135, 138.3854]  list object refers to accuracy, and loss respectively right?

Thanks in advance. 😃

Hi, for the benchmark error, the results are printed automatically after running, line63~71 should be removed and we have fixed it in the next release.
Question 1: the algorithm is the way to calculate the scale of nodes during quantization
Question 2: the baseline lists [accuracy, latency] in order

Thanks for the answer, it worked fine now. I did encounter another problem though, I will open another issue for that.

@peiwenhuang27  pls use latest LPOT, in which we have improved logging message. you will see something like
FP32 baseline is: [accuracy: 0.1135, duration(second): 138.3854]
rather than
FP32 baseline is: [0.1135, 138.3854]

as for specifying quantization type, LPOT only supports u8/s8 quantization.


Update Dockerfile in .devcontainer.

Signed-off-by: Shubham Kuchhal<EMAIL_ADDRESS>As per discussion here #1610, I have Updated the golang version and OPERATOR_RELEASE_VERSION  in Dockerfile.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Changelog has been updated

Fixes #1610

Hi @zroubalik, @ahmelsayed
could yo please take a look.


SCTP tests dont execute due to unknown issue capturing netcat stdout

Describe the bug
SPDY executor doesnt return a sctp netcat servers stdout.
To Reproduce
Steps to reproduce the behavior:
Enable SCTP tests by setting environment variable ENABLE_SCTP=true. Ensure SCTP kernel modules are loaded on the affected worker nodes.
Run tests.
Expected behavior
SCTP tests pass.
**additional comments **
SCTP tests fail and SPDY executor returns blank stdout even though I can see the appropriate IP address was sent to the netcat server via tcpdump -i any -A -s0.
This only occurs for SCTP tests.

/assign

I dont have time to fix this right now so unassigning to let others jump on this in the meantime.

/reopen


chore:  ♿ add aria-current: page attribute to active link.

Fixes #41
Proposed Changes

add aria-current: page attribute to active link.

Sorry for having missed this @hussamkhatib 😅
I like this addition, can I reopen it?

Sure.
I closed it as I am not sure if it is the proper usage of that attribute.

No aria is better is than bad aria

When you have a group of related elements, such as several links in a breadcrumb or steps in a multi-step flow, with one element in the group styled differently from the others to indicate to the sighted user that this is the current element within its group, the aria-current should be used to inform the assistive technology user what has been indicated via styling.
mdn

I also created a post on Reddit, didn't get the answer I was expecting.

@hussamkhatib Hmmm, well first of all, thanks so much for going ahead and posting about this on Reddit 🙌 That's pretty impressive.
Secondly, I think this is a good addition and fits here with #41 — but we should also include a visual marker on the Navbar to indicate what the current page is. I can work on this, and then we can reopen and merge your PR here? What do you think?

Sounds good.


[Task][Before Each Release]: Ensure the Go version used for container builds is the latest available.

What needs to happen?
Go makes security patch releases of their tooling, so it's good to ensure we're up to date for each release.
This affects container bootloader security, WRT CVEs that are listed when the containers are scanned.
See if https://go.dev/doc/devel/release has a newer release. Go releases a new version every 6 months, but provides minor revision releases for security updates and bug fixes for the last two versions. It's important to be on the latest of these each release.
After creating the update PR, move this task to the next release.
TODO(lostluck): Automate making these updates.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[X] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Still at 1.12.1 and putting these instructions into the release guide.


Definition of exc_only in figure 9.1 is different from explanation above

description of exc_only in figure 9.1 only contains exception, and interrupt is not included.

Yes, that is a minor error in the diagram.  When the spec was initially being written, the term "exception" was used to cover both exceptions and interrupts.  Later this was replaced with the term "trap".  But it looks like this piece of text didn't get updated (likely because it's embedded in a diagram)
Iain
From: zhangdujiao @.>
Sent: 28 June 2024 10:20
To: riscv-non-isa/riscv-trace-spec @.>
Cc: Subscribed @.***>
Subject: [riscv-non-isa/riscv-trace-spec] Definition of exc_only in figure 9.1 is different from explanation above (Issue #127)
description of exc_only in figure 9.1 only contains exception, and interrupt is not included.

Reply to this email directly, view it on GitHubhttps://github.com/riscv-non-isa/riscv-trace-spec/issues/127, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALQOPSTYCQXFWPEA6ZWH76TZJUTCPAVCNFSM6AAAAABKBPNSCSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TSOJXHA2TANQ.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

Got it, great to know!


”Lunca Rateș”, ”Rediu”, ”Tufeștii de Sus” are listed in the drop-down menu

Description:
When user writes ”Lunca Rateș”, ”Rediu”, ”Tufeștii de Sus” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Rediu"

Expected results
The location appears in the drop-down menu as "Sat Rediu, IAȘI (Scânteia)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Tufeștii de Sus"

Expected results
The location appears in the drop-down menu as "Sat Tufeștii de Sus, IAȘI (Scânteia)".


Implement LayoutClass/LayoutClassPtr/AsAny marshalers

This is a couple marshallers that nobody should be using for anything, but WinForms and System.Drawing uses them for everything. Frankly, it feels like the designers of .NET 1.0 got too excited about marshalling everything with these and someone should have stopped them.
These marshallers are for marshalling abritrary reference types to native code.
This is enough to get basic WinForms apps running. E.g. the MatchingGame .NET Sample works with this. Serious WinForms apps will eventually hit missing COM support, but at least the basics work now and it's enough to get a read on things like startup time.

Mandatory screenshot:

Sigh, the Release test failures are because RyuJIT inlines Marshal.SizeOf<SequentialStruct> in the test and we then don't save the marshaling data. This would normally be saved by the reflection infrastructure (that makes sure Marshal.SizeOf<SequentialStruct> is reflection callable, and therefore has a standalone method body, and therefore interop sees the call), but for reasons I forgot, we turned on reflection blocking on the PInvoke test and nobody saves it.
The ultimate fix is to put interop infrastructure on the same plan as reflection (have a "usage based interop manager" that determines interop needs from code + an "analysis based interop manager" that uses data someone else provided - e.g. the scanner phase in optimized builds).
I'll meditate on this a bit, but I think I'll just make the type public and therefore not blocked.


feat(release): add assets info

Resolves #99.

@pi0 Just a friendly ping~

thanks. looks good but i want to locally check responses too before merging as it directly goes into production.
btw do you have specific usecase for this? (just curious)

btw do you have specific usecase for this? (just curious)

I am writing a custom build script for a Hackintosh project that required downloading several custom XNU kernel extensions from GitHub releases. I use both curl and jq to obtain the download URL. While I can use secrets.GITHUB_TOKEN inside GitHub Actions, it's possible to reach the api.github.com rate limit when running the script locally.


MonadAsk is over constrained

The law for MonadAsk ask >>= \_ -> ask = ask only requires Applicative ask *> ask = ask. You can't execute effects depending on the environment, but you can compute results depending on the environment.
example = f <$> ask <*> other

Would the class be renamed to ApplicativeAsk?

I think it would be ApplyAsk. Technically, only Apply is needed for the law.


Update CI from ubuntu 16.04 (EOL) to 19.04

Closes #1333 .

@gnzlbg: no appropriate reviewer found, use r? to override

SYS_syscalls error comes from: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2dba5ce7b8115d6a2789bf279892263621088e74;hp=5f3b183d198b39ca993a41aadb02bddd9fde078d

Let's see if including the bits/syscalls.h header fixes those!

So that did not work, that header cannot be included directly.

It seems SYS_syscalls is no longer generated, at least it's absent in 18.04 container with libc6-dev and linux-headers-5.0.0 installed.

That would happen if the kernel does not define __NR_syscalls, but AFAICT it does ? Or maybe syscalls is just missing from the list that glibc uses.

Yes, that appears to be the case: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2dba5ce7b8115d6a2789bf279892263621088e74;hp=5f3b183d198b39ca993a41aadb02bddd9fde078d
Shows that "pseudo-system calls" that define ranges, and unused / reserved system calls, are skipped.

AFAICT, that's a backwards incompatible breaking change from glibc.

cc @fweimer

Seems it's not present for every arch:

rg "__NR_syscalls" /usr/
/usr/include/asm-generic/unistd.h
736:#undef __NR_syscalls
737:#define __NR_syscalls 292
781:#undef __NR_syscalls
782:#define __NR_syscalls (__NR3264_lstat+1)
799:#undef __NR_syscalls
800:#define __NR_syscalls (__NR_signalfd+1)
834:#undef __NR_syscalls
835:#define __NR_syscalls (__NR_mmap+1)
897:#undef __NR_syscalls
898:#define __NR_syscalls (__NR_fork+1)

/usr/src/linux-headers-5.0.0-15/arch/arm/tools/syscallnr.sh
29:        echo "#define __NR_syscalls $nr"

/usr/src/linux-headers-5.0.0-15/include/uapi/asm-generic/unistd.h
744:#undef __NR_syscalls
745:#define __NR_syscalls 295

/usr/src/linux-headers-5.0.0-15/arch/alpha/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/alpha/include/asm/unistd.h
7:#define NR_SYSCALLS   __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/arm64/include/asm/unistd.h
56:#define NR_syscalls (__NR_syscalls)

/usr/src/linux-headers-5.0.0-15/arch/ia64/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/microblaze/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/m68k/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/parisc/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/ia64/include/asm/unistd.h
13:#define NR_syscalls          __NR_syscalls /* length of syscall table */

/usr/src/linux-headers-5.0.0-15/arch/riscv/include/asm/unistd.h
23:#define NR_syscalls (__NR_syscalls)

/usr/src/linux-headers-5.0.0-15/arch/parisc/include/asm/unistd.h
7:#define __NR_Linux_syscalls   __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/m68k/include/asm/unistd.h
7:#define NR_syscalls   __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/powerpc/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/arm/include/asm/syscall.h
18:#define NR_syscalls (__NR_syscalls)

/usr/src/linux-headers-5.0.0-15/arch/mips/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/sh/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/powerpc/include/asm/unistd.h
14:#define NR_syscalls  __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/sparc/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/xtensa/kernel/syscalls/syscallhdr.sh
32:     printf "#define __NR_syscalls\t%s\n" "${nxt}"

/usr/src/linux-headers-5.0.0-15/arch/sh/include/asm/unistd.h
8:#define NR_syscalls   __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/xtensa/include/asm/unistd.h
25:#define NR_syscalls                          __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/sparc/include/asm/unistd.h
20:#define NR_syscalls  __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/arc/include/uapi/asm/unistd.h
30:#define NR_syscalls  __NR_syscalls

/usr/src/linux-headers-5.0.0-15/arch/sh/include/uapi/asm/unistd_64.h
420:#define __NR_syscalls               394

/usr/src/linux-headers-5.0.0-15/arch/sh/include/uapi/asm/unistd_32.h
400:#define __NR_syscalls               383

@mati865 the error is (e.g. on aarch64):
error: 'SYS_arch_specific_syscall' undeclared here (not in a function); did you mean '__NR_arch_specific_syscall'?
cargo:warning=             static const  long __test_const_SYS_arch_specific_syscall_val = SYS_arch_specific_syscall;
cargo:warning=                                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~
cargo:warning=                                                                             __NR_arch_specific_syscall
cargo:warning=/checkout/target/aarch64-unknown-linux-gnu/debug/build/libc-test-bf57c51a205470a0/out/main.c:29556:64: error: 'SYS_syscalls' undeclared here (not in a function); did you mean '__NR_syscalls'?
cargo:warning=             static const  long __test_const_SYS_syscalls_val = SYS_syscalls;
cargo:warning=                                                                ^~~~~~~~~~~~
cargo:warning=                                                                __NR_syscalls

This means that SYS_syscalls is not defined in the headers, but __NR_syscalls is. Before glibc used to export SYS_syscalls for these targets. Now it does not, even though __NR_syscalls still exists.

The same happens in other targets with the reserved/unused syscalls.

So most build jobs are green now. I have no idea why s390x is failing, the error message is weird. For example, see:
cargo:warning=/checkout/target/s390x-unknown-linux-gnu/debug/build/libc-test-bf57c51a205470a0/out/main.c:24441:73: error: 'PTRACE_GETREGS' undeclared here (not in a function); did you mean 'PTRACE_GETREGSET'?
cargo:warning=             static const unsigned int __test_const_PTRACE_GETREGS_val = PTRACE_GETREGS;
cargo:warning=                                                                         ^~~~~~~~~~~~~~
cargo:warning=                                                                         PTRACE_GETREGSET
cargo:warning=/checkout/target/s390x-unknown-linux-gnu/debug/build/libc-test-bf57c51a205470a0/out/main.c:24447:73: error: 'PTRACE_SETREGS' undeclared here (not in a function); did you mean 'PTRACE_GETREGS'?
cargo:warning=             static const unsigned int __test_const_PTRACE_SETREGS_val = PTRACE_SETREGS;
cargo:warning=                                                                         ^~~~~~~~~~~~~~
cargo:warning=                                                                         PTRACE_GETREGS

Notice how the first error says that PTRACE_GETREGS is undeclared, but the suggestion of the second error does suggest using PTRACE_GETREGS, which can only happen if that has been declared somewhere =/

I was also puzzled by this one. Definitions seems to be absent though:

PPC: https://elixir.bootlin.com/linux/latest/source/arch/powerpc/include/uapi/asm/ptrace.h#L182
S390X: https://elixir.bootlin.com/linux/latest/source/arch/s390/include/uapi/asm/ptrace.h
architectures with the define: https://elixir.bootlin.com/linux/latest/ident/PTRACE_GETREGS

Most build jobs fail again with ubuntu 19.04, the errors are of the form:
bad ucontext_t size: rust: 936 (0x3a8) != c 968 (0x3c8)
bad fscanf function pointer: rust:<PHONE_NUMBER>26624 (0x7f5ca5ea7c20) != c<PHONE_NUMBER>30928 (0x7f5ca5ea8cf0)
bad scanf function pointer: rust:<PHONE_NUMBER>26816 (0x7f5ca5ea7ce0) != c<PHONE_NUMBER>30688 (0x7f5ca5ea8c00)
bad sscanf function pointer: rust:<PHONE_NUMBER>27024 (0x7f5ca5ea7db0) != c<PHONE_NUMBER>31136 (0x7f5ca5ea8dc0)
bad NFT_MSG_MAX value at byte 0: rust: 22 (0x16) != c 25 (0x19)

The incorrect const and field size are easily fixable, but the incorrect function pointers means that Rust points to a different function than C in our tests. Maybe a different version of glibc is being pulled via the rust standard library than the one C is using ? No idea yet.
Also, the s390x build job fails with:
/prog: /lib/libc.so.6: version `GLIBC_2.27' not found (required by /prog)

but AFAICT ubuntu 19.04 ships glibc 2.29 =/

From the 2.29 release notes:
An archaic GNU extension to scanf, under which '%as', '%aS', and
  '%a[...]' meant to scan a string and allocate space for it with
  malloc, is now restricted to programs compiled in C89 or C++98 mode
  with _GNU_SOURCE defined.  This extension conflicts with C99's use of
  '%a' to scan a hexadecimal floating-point number, which is now
  available to programs compiled as C99 or C++11 or higher, regardless
  of _GNU_SOURCE.

We do define _GNU_SOURCE in the tests.

So I've removed the switch to 19.04 since it doesn't seem straightforward.

Hopefully one of the last fixes:
cargo:warning=/checkout/target/sparc64-unknown-linux-gnu/debug/build/libc-test-bf57c51a205470a0/out/main.c:21088:28: error: return from incompatible pointer type [-Werror=incompatible-pointer-types]
cargo:warning=                     return &b->ut_session;
cargo:warning=                            ^~~~~~~~~~~~~~

Error on Ubuntu 19.04 was much more useful:
cargo:warning=/checkout/target/sparc64-unknown-linux-gnu/debug/build/libc-test-bf57c51a205470a0/out/main.c:21088:28: error: returning '__int32_t *' {aka 'int *'} from a function with incompatible return type 'long int *' [-Werror=incompatible-pointer-types]
cargo:warning=                     return &b->ut_session;
cargo:warning=                            ^~~~~~~~~~~~~~

https://github.com/rust-lang/libc/blob/11f30a8837d051741d0119078acabdb606fac14c/src/unix/notbsd/linux/other/mod.rs#L227-L246

So I think things are mostly green for 19.04 now. There is a breaking change where we callign _scanf and friends before, but are calling __isoc99_scanf now. These are available since glibc 2.7 (2007) so I hope this doesn't break anybody.

So everything is green now, except for the wasi build jobs which still fail with target not found (cc @alexcrichton @sunfishcode) and the android build jobs which are allowed to fail.

So I've pulled the renaming changes only from #1342 .

Now the documentation build job fails because bitrig was remove in the latest nightly, which was just released. Perfect timing.

@bors: r+

:pushpin: Commit 8eceb62a3e200c42ea2d6bbc4be93a1c2227b37e has been approved by gnzlbg

:hourglass: Testing commit 8eceb62a3e200c42ea2d6bbc4be93a1c2227b37e with merge 4ac8346b74f530d4573627fdd24b2fbe1018a3f2...

This was, by far, the largest game of code golf I've ever played.

:sunny: Test successful - checks-cirrus, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing 4ac8346b74f530d4573627fdd24b2fbe1018a3f2 to master...

Thank you @mati865 for the feedback and help with the changes!

@gnzlbg FWIW if this happens in the future I'd recommend simply disabling targets on CI. I think it's best to keep the wheels turning and the problems fixed here in general should be inconsequential because the current state of the crate isn't exactly full of bugs to the point that it's unusable. By enabling PRs to land quicker it can help reduce some stress from landing big changes/refactorings like this all at the same time.

@alexcrichton The Ubuntu version that was being used went end-of-life and the Docker images for it were removed, so all build jobs using it (almost all of them) started failing. That is, we would have had to turn off CI completely. I suppose we could have done that, to be able to continue merging PRs without any testing on CI, but I don't think we should have done a new release until CI was up again, and at that point, merged PRs might have introduced errors, that I would have had to fix in the PR updating CI, so... I don't know if that would have been better.

@gnzlbg oh sure yeah I understand but it probably wasn't too hard to get the major targets working again on CI and the main difficulty was getting everything working, right? I was mostly just saying that this could probably get staged where the main targets are brought back up and then the remaining targets would be follow-ups.

Well, maybe? The part that took most of the time here was getting x86_64 and aarch64 gnu Linux targets working. This PR did not fix Android (there is a PR open for this) nor Emscripten, but getting the tests to pass on the Linux gnu targets without breaking the other targets more required splitting the Linux bits from the libc-test/build.rs, which was done as simple as possible (there are a million fixmes, which are now being cleaned up in other PRs). The other Linux targets (e.g. the musl ones) kind of just worked, or were easy to fix.
The sparc64 and s390x fixes were probably unnecessary and could have been done later, but they weren't very time consuming either.
What costed most of the time is having to test this on travis-ci, which gives me a 30min iteration time, because the docker containers that we have do not work on MacOS X.

Ah ok, well whatever works works! Not being able to test locally I can also see would significantly complicate things...


Superusers shall always be staff users

Bug description
When a user is superuser but not staff user, they cannot access some functionality like listing and viewing users.
Expected behavior
Every superuser shall be staff user as well. The user interface and the API shall forbid otherwise.

Staff users will be deprecated soon


Fixed 2QB gate error depending on qubit order

Errors to two-qubit CZ gates were only applied for one specific order of the qubit arguments in the gate construction. But the error should be applied independent of this order since the gate is symmetric in control and target qubit.
Changes:

Added reverse qubit order in error construction in iqm_fake_backend.py.
Added assertion to test case test_noise_model_contains_all_errors in test_iqm_fake_backend.py.

Looks good, but you also need a Changelog entry to trigger a release 🙂

Looks good, but you also need a Changelog entry to trigger a release 🙂

Done.


setContainerView: parameter should be nullable

In 2.2 the UIView passed into + (void)setContainerView: changed its nullability specifier to nonnull. However, the containerView property is nullable:
@property (strong, nonatomic, nullable) UIView *containerView;
And a comment specifies // default is window level, indicating that it is valid to have a nil value here.
Proposal: change to
+ (void)setContainerView:(nullable UIView*)containerView;

Please submit a PR.

https://github.com/SVProgressHUD/SVProgressHUD/pull/803

Thanks.


how can i  use  your model to test

hello, i have gen_proposal_list  and then i want to test a video.
I do not know how to use your model.
In your yjxiong/tensorflow-model-zoo.torch/   I run the code pytorch_load.py in bninception  and inceptionresnetv2 and inceptionv4
the error  as follow:
(py2_ten1.6_torch3.1) ct@PowerEdge-T630:~/myfile/project/SSN/action-detection/model_z
oo/inceptionresnetv2$ python pytorch_load.py /home/ct/anaconda2/envs/py3/envs/py2_ten1.6_torch3.1/lib/python2.7/site-packages/h5py
/init.py:36: FutureWarning: Conversion of the second argument of issubdtype from float to np.floating is deprecated. In future, it will be treated as np.float64 == np.dtype(float).type.  from ._conv import register_converters as _register_converters
Traceback (most recent call last):
File "pytorch_load.py", line 521, in
state_dict = load()
File "pytorch_load.py", line 376, in load
load_conv2d(state_dict, name_pth='conv2d_1a', name_tf='Conv2d_1a_3x3')
File "pytorch_load.py", line 303, in load_conv2d
h5f = h5py.File('dump/InceptionResnetV2/'+name_tf+'.h5', 'r')
File "/home/ct/anaconda2/envs/py3/envs/py2_ten1.6_torch3.1/lib/python2.7/site-packa
ges/h5py/_hl/files.py", line 269, in init    fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
File "/home/ct/anaconda2/envs/py3/envs/py2_ten1.6_torch3.1/lib/python2.7/site-packa
ges/h5py/_hl/files.py", line 99, in make_fid    fid = h5f.open(name, flags, fapl=fapl)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5f.pyx", line 78, in h5py.h5f.open
IOError: Unable to open file (unable to open file: name = 'dump/InceptionResnetV2/Con
v2d_1a_3x3.h5', errno = 2, error message = 'No such file or directory', flags = 0, o_flags = 0)
could you help me.

Unable to open file (unable to open file: name = 'dump/InceptionResnetV2/Con
v2d_1a_3x3.h5', errno = 2, error message = 'No such file or directory', flags = 0, o_flags = 0)


Merge pull request #1 from duckduckgo/develop

updates from fork

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

@PIYUSH-MISHRA-00  can you check this PR? It doesn't follow the guidelines nor adds any change.


Fix thunk/deferred_codegen getting incorrect world age and segfaulting

Bug Found:
The following script will error out with a segfault in the current Enzyme implementation. This occurs because the generated functions for thunk and deferred_codegen do no retrigger GPUCompiler and instead use stale values. Simply dropping the generated tag fixes the segfault but we are no longer able to look up unique method instances as the returned world ages are incorrect. Instead we should switch to using GPUCompiler.methodinstance directly dropping the need to filter on world ages.
module EnzymeTest
using Enzyme

rosenbrock(x, y) = (1.0 - x)^2 + 100.0 * (y - x^2)^2
autodiff(Reverse, rosenbrock, Active, Active(1.0), Active(2.0))

function __init__()
    autodiff(Reverse, rosenbrock, Active, Active(1.0), Active(2.0))
end

end # module EnzymeTest

With the following segfault:
julia> using EnzymeTest
[ Info: Precompiling EnzymeTest [87ed9522-ec2b-4441-9f14-f86404eed9ba]

[1273377] signal (11.1): Segmentation fault
in expression starting at REPL[1]:1
unknown function (ip: 0x7f6f218d4050)
macro expansion at /home/collinw/.julia/dev/Enzyme/src/compiler.jl:8971 [inlined]
enzyme_call at /home/collinw/.julia/dev/Enzyme/src/compiler.jl:8663 [inlined]
CombinedAdjointThunk at /home/collinw/.julia/dev/Enzyme/src/compiler.jl:8626 [inlined]
autodiff at /home/collinw/.julia/dev/Enzyme/src/Enzyme.jl:205 [inlined]
autodiff at /home/collinw/.julia/dev/Enzyme/src/Enzyme.jl:214 [inlined]
runGradients at /home/collinw/julia_master/EnzymeTest/src/EnzymeTest.jl:9 [inlined]
__init__ at /home/collinw/julia_master/EnzymeTest/src/EnzymeTest.jl:30
Allocations: 7890557 (Pool: 7878530; Big: 12027); GC: 11
Segmentation fault (core dumped)

To fix the segfault the @generated tags are removed so that GPUCompilation can occur whenever this function is called. Previously precompilation caching was storing stale function pointers. With this change we no longer get segfaults but instead are unable to look up the correct methodinstance on initialization due to mismatching world ages. To fix this GPUCompiler.codegen_world_age() is no longer used infavor of calling GPUCompiler.methodinstance inside thunk/deferred_codgen. Tested on failing testcase and achieve desired results. No segfaults and run of both autodiff calls.

to deduplicate conversatoin channels cc @vtjnash @maleadt

Superceeded by https://github.com/EnzymeAD/Enzyme.jl/pull/1575


Broken css-link in usage.md

I read it in documentation page (usage.md)

Note: This package does note include any styling by default. You can use react-contextmenu.css from examples for quick setup.

But link is broken. I'm thinking right url is https://github.com/vkbansal/react-contextmenu/blob/master/examples/react-contextmenu.css.

Would you like to open PR?


expose amplify-meta.json to backend functions & apis

Is your feature request related to a problem? Please describe.
Multienv support generates new resource identifiers for resources like Cognito User Pools, DynamoDB table names, and ElasticSearch endpoints. This makes referencing those resources from backend functions (added via amplify add function or amplify add api) challenging (and in some cases impossible) with hardcoding per-environment configuration outside the context of Amplify.
Describe the solution you'd like

As part of the build process for Lambda functions, expose a copy of amplify-meta.json that the Lambda function can use to lookup desired resource identifiers.
DynamoDB table names created by the GraphQL transformer are not currently exposed in amplify-meta.json; add those, please.
No information about the ElasticSearch service provisioned by @searchable is currently included in amplify-meta.json; add that too, please.

Describe alternatives you've considered
Alternatively consider offering full support for the front-end functions included in the aws-amplify library, such as querying of GraphQL APIs, from back-end functions. FYI it currently "just works" if you include a fetch polyfill (e.g. cross-fetch/polyfill), but the authentication process is obviously geared toward use cases with a static user (as it stores a lot of data in global state).
Additional context
Ref: #621

Looking forward to this feature. For now we are creating a map per env with the dynamically generated api id.

This gonna be very helpful

Today we released an updated flow as a part of the functions category to pass resource identifiers like the cognito userpool ID  or graphql ID or any other resource - managed and generated by the Amplify CLI to a lambda function as environment variables and also populate the corresponding lambda execution role to access these resources. You can install the latest version of the CLI and go through the amplify update function flow to update your existing functions to access your Amplify generated resources in the project.

@kaustavghosh06 do you happen to have a sample for access the API from a lambda using something like graphqlOperation and API from 'aws-amplify' ? I'm assuming the user has to be an IAM role here, which is handled when updating the function.

@kaustavghosh06 Is there any documentation on how to use e.g. the AppSync API from your Lambda function?

how does one access environmental variables outside of those generated by amplify such as for third party services such that can be stored in the SSM parameter store? https://serverless.com/framework/docs/providers/aws/guide/variables/ is a good execution of what I hope is exposed by Amplify.

Today we released an updated flow as a part of the functions category to pass resource identifiers like the cognito userpool ID or graphql ID or any other resource - managed and generated by the Amplify CLI to a lambda function as environment variables and also populate the corresponding lambda execution role to access these resources. You can install the latest version of the CLI and go through the amplify update function flow to update your existing functions to access your Amplify generated resources in the project.

@kaustavghosh06, I just executed amplify update function and all I get is the amplify function menu: "
amplify function <subcommands>

  add                     Takes you through a CLI flow to add a function resource to your local backend
  push                    Provisions only function cloud resources with the latest local developments
  remove                  Removes function resource from your local backend which would be removed from the cloud on the next push command
  build                   Builds all the functions in the project (does an npm install on the functions src directory)
  invoke <resourcename>   Invokes a function locally for testing

Maybe that's because I've my amplify libraries up to date; but then, how can I access this IDs from within my function? I was hoping that the flow following this invocation would shed some light into this.

Is your feature request related to a problem? Please describe.
Multienv support generates new resource identifiers for resources like Cognito User Pools, DynamoDB table names, and ElasticSearch endpoints. This makes referencing those resources from backend functions (added via amplify add function or amplify add api) challenging (and in some cases impossible) with hardcoding per-environment configuration outside the context of Amplify.
Describe the solution you'd like

As part of the build process for Lambda functions, expose a copy of amplify-meta.json that the Lambda function can use to lookup desired resource identifiers.
DynamoDB table names created by the GraphQL transformer are not currently exposed in amplify-meta.json; add those, please.
No information about the ElasticSearch service provisioned by @searchable is currently included in amplify-meta.json; add that too, please.

Describe alternatives you've considered
Alternatively consider offering full support for the front-end functions included in the aws-amplify library, such as querying of GraphQL APIs, from back-end functions. FYI it currently "just works" if you include a fetch polyfill (e.g. cross-fetch/polyfill), but the authentication process is obviously geared toward use cases with a static user (as it stores a lot of data in global state).
Additional context
Ref: #621

@troygoode, could you give me some pointers on how to use cross-fetch library to archive this?
Thanks!

@kaustavghosh06

DynamoDB table names created by the GraphQL transformer are not currently exposed in amplify-meta.json; add those, please.
I this request also in the release? I don't see the dynamodb created for Appsync in the amplify-meta.json

I ran into a problem with my function going directly to DDB. I started using @key with composite sort keys and needed to go back to the function to duplicate what is being done in the mutation resolvers to construct the field.
If you're working on an app with a quickly changing schema it's going to be a headache to maintain.

Any update on this feature request?
I couldn't find how to access amplify-meta.json content in my backend python function
Using following hack for now but looking for best practice to do this
amplify/backend/function/FunctionName/src/index.py
with open("../../../amplify-meta.json") as f:
    meta_json = json.load(f)
    print(meta_json)

Any suggestions to improve this is really appreciated.
Please let me know if I am missing anything from my side.


All Day Events

separate all day events from the non-all day events 👍
closes #18
What's New

AllDayView layouts EventViews in a UIScrollView similar to Apple's Calendar app

Changes

Added allDay: Bool to EventDescriptor and Event

What to review

[ ] filtering method (separation of all day event)
[ ] Max height of AllDayView

What's left

[ ] Performance of updating the stationary view
[x] all-day label in the AllDayView
[x] Tapping an event needs to invoke the delegate

@richardtop I believe this is now complete :)

@richardtopI've completed styling. I believe now this was the last step before your review :)

I was able to reproduce a bug where the contentInset property is not being updated when the allDayTaskView is present:

Therefore, it's impossible to see the top part of the timeline.

Thank you for the detailed, and quick, feedback! I've committed the changes you've mentioned here

Congratulations with your first pull request to CalendarKit!


cctag: fix failing tests with gcc13

Since GCC13 the package does not build correctly, causing the tests to fail. This was not the case with GCC12. Instead of building it with an older version of GCC, we can build and test it successfully with Clang.
Description of changes
ZHF: #309482

failed build: https://hydra.nixos.org/build/259383428
fixes https://github.com/NixOS/nixpkgs/issues/289100

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 311609 run on x86_64-linux 1

3 packages built:

cctag
cctag.dev
cctag.lib


Can not build the project from docker file

OS version: Ubuntu 18.04 (Used in a Virtual Box)
Docker version: 19.03.6
docker-compose version: 1.17.1
I tried to build the Avalon project by using the docker-compose command for the SGX simulator mode. But it gives the following error. I can't find a solution for this. Is something wrong with my docker versions?

Could you please share your docker-compose file?

I never seen that error before and it works with me.
Apparently it is caused by this line in Docker-compose.yaml:
- DISPLAY=${DISPLAY:-}
It seems to be implying that the $ should be escaped.  That is:
- DISPLAY=$${DISPLAY:-}
But that should not be needed.
As a workaround you can delete that line unless you are running an app that uses X Windows (such as the Heart Disease Evaluation GUI).
I Googled the error and it could be caused by an old version of docker-compose. Mine is:
$ docker-compose version
docker-compose version 1.24.1, build 4667896b
Dan
From: Shehan Dhaleesha<EMAIL_ADDRESS>Sent: Saturday, April 25, 2020 8:39 AM
To: hyperledger/avalon<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [hyperledger/avalon] Can not build the project from docker file (#428)
OS version: Ubuntu 18.04 (Used in a Virtual Box)
Docker version: 19.03.6
docker-compose version: 1.17.1
I tried to build the Avalon project by using the docker-compose command for the SGX simulator mode. But it gives the following error. I can't find a solution for this. Is something wrong with my docker versions?
[image]https://user-images.githubusercontent.com/25993584/80283905-bef70700-8738-11ea-9852-7a4bf8b79619.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/hyperledger/avalon/issues/428, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH26URNCLCIHRGRLOWYFB6TROL7YLANCNFSM4MQZNATQ.

This is the docker-compose.yaml file content
# Copyright 2019 Intel Corporation
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

version: '3.5'

services:
  avalon-shell:
    container_name: avalon-shell
    image: avalon-shell-dev
    build:
      context: .
      dockerfile: ./docker/Dockerfile
      args:
        - DISPLAY=${DISPLAY:-}
        - XAUTHORITY=~/.Xauthority
        - http_proxy
        - https_proxy
        - no_proxy
    environment:
      - DISPLAY
      - http_proxy
      - https_proxy
      - no_proxy
    volumes:
      # Below volume mappings are required for DISPLAY settings by heart disease GUI client
      - /tmp/.X11-unix:/tmp/.X11-unix
      - ~/.Xauthority:/root/.Xauthority
    command: |
      bash -c "tail -f /dev/null"
    stop_signal: SIGKILL
    depends_on:
      - avalon-enclave-manager
      - avalon-listener

  avalon-enclave-manager:
    container_name: avalon-enclave-manager
    image: avalon-enclave-manager-dev
    build:
      context: .
      dockerfile: ./enclave_manager/Dockerfile
      args:
        - http_proxy
        - https_proxy
        - no_proxy
    environment:
      - http_proxy
      - https_proxy
      - no_proxy
    command: |
      bash -c "
        enclave_manager --lmdb_url http://avalon-lmdb:9090
        tail -f /dev/null
      "
    depends_on:
      - avalon-lmdb

  avalon-lmdb:
    container_name: avalon-lmdb
    image: avalon-lmdb-dev
    build:
      context: .
      dockerfile: ./shared_kv_storage/Dockerfile
      args:
        - http_proxy
        - https_proxy
        - no_proxy
    environment:
      - http_proxy
      - https_proxy
      - no_proxy
    expose:
      # Port is where lmdb server will listen for http request.
      # Port should be same as in bind parameter or lmdb_config.toml
      - 9090
    command: |
      bash -c "
        kv_storage --bind http://avalon-lmdb:9090
        tail -f /dev/null
      "

  avalon-listener:
    container_name: avalon-listener
    image: avalon-listener-dev
    build:
      context: .
      dockerfile: ./listener/Dockerfile
      args:
        - http_proxy
        - https_proxy
        - no_proxy
    environment:
      - http_proxy
      - https_proxy
      - no_proxy
    expose:
      - 1947
    command: |
      bash -c "
        avalon_listener --bind http://avalon-listener:1947 --lmdb_url http://avalon-lmdb:9090
        tail -f /dev/null
        "
    depends_on:
      - avalon-lmdb

Upgrading docker-compose to lates solved the issue. Thanks @danintel for the help.

You are welcome. I will add the error to the FAQ>


AppVeyor CI

It would be nice if all of the JDKs pre-installed on AppVeyor could be pre-registered so switching between them is cheap.
https://www.appveyor.com/docs/windows-images-software/#java

Also possibly helpful with Windows, https://github.com/shyiko/jabba/issues/478

Hi @jayvdb, it's not entirely clear what is your suggestion: do you believe we should be providing an alternative way, not going through jabba, or do you think jabba should do it?

Hi @DanySK , I was thinking that Jabba could detect AppVeyor, and do the configuration so those environments can be easily selected.
It was a while ago that I created this, so perhaps it is easier now, but I found it a bit cumbersome to do this in my CI - Windows CI can be troublesome to get working.  IIRC, I gave up and used a different approach.

@jayvdb this issue should probably belong to shyko/jabba than DanySK/Gravis-CI, then, if I understand what you mean.

Sorry, I mean that Gravis-CI should do it.  jabba itself is obviously aiming to be a raw tool, and Gravis-CI is a better layer on top to be doing voodoo to simplify using it in CI.
If you dont want to support AppVeyor, that is your choice.
If you just dont want to get it working, I would be keen to help with this, as I would like a cross-platform solution, and cross-platform-CI tools is a key component of that.

I am totally open, my only limit is that I never used AppVeyor and do not know it.
But pull requests are totally welcome, I got nothing against supporting multiple providers :)


ccdec: do not assume h264 as the default coded format

H.264 is very popular, but it is still not a good idea to simply assume it as a default.
Passing some random data as an h.264 stream crashes cros-codecs, or produces no useful output as no valid NALUs are parsed. This is the best-case scenario, but we should not rely on that.
Leave the responsibility of properly labelling the data to the user.

Yeah, that's very reasonable. I think I'll try to implement some kind of input format detection for the case where the input format is not explicitly specified. Differentiating between H.264 NALs, IVF and Matroska should not be hard.


feat(friendshipper): add "copy logs to clipboard" button

Added a button to the build logs page to copy the currently-displayed log to the clipboard.

Nice 🎉


feat: 🎸 add manual redirect settings to each page

📝 Changed routes:

/login
/my

(view full size)
(view full size)

/register

(view full size)

Commit 6fb4f41360db9105a40da70ad1d742b22579f235 (https://next-chat-app-v3-htvjfnlu8-personal-development-540bcc48.vercel.app).


Write batches atomically

This PR  ensures that when the nodes of a graph containing the result of an Altimeter scan are written, they are always linked to an snapshot vertex that, in turns, is linked with the current Altimeter Universe vertex.

Recreated in https://github.com/adevinta/graph-altimeter/pull/6 without conflicts


CSS file not generated when input is empty but when CSS should still be generated due to prefix being set

If SCSS source file is empty and prefix is set then the CSS file should still be generated:
const scssConfig = {
  processor: () => postcss(postCssConfig),

  output: "./static-dev/css/main.css",
  outputStyle: "compressed",
  sourceMap: isPreview,
  failOnError: true,

  prefix: `@import "./frontend/styles/base.scss";`,

  includePaths: [
    "./node_modules/prismjs/themes",
  ],
};

It probably makes sense to always generate the CSS file for repeatability purposes. Could you make a PR?


feat(editor): Support auto-close for ``

[x] Added an entry to CHANGELOG.md if this change could be valuable to users

This updates the bracket/quote auto-pairing behavior to include backticks and angle brackets. I find backtick matching really handy when writing markdown, and angle bracket matching is really nice when writing code with generics in all sorts of languages. Update: I've removed angle bracket matching from this PR; it now only matches/pairs backticks.
I expanded a test to cover this change; aside from that, I've been using this locally for several days and it has been working as expected. Thanks!

Codecov Report

Merging #1855 (eaaac9f) into master (1c7815b) will increase coverage by 0.06%.
The diff coverage is 80.95%.

@@            Coverage Diff            @@
##           master   #1855      +/-   ##
=========================================
+ Coverage    6.94%   7.00%   +0.06%
=========================================
  Files         128     128
  Lines       55532   55280     -252
=========================================
+ Hits         3857    3873      +16
+ Misses      51675   51407     -268

Impacted Files
Coverage Δ

lapce-core/src/syntax/util.rs
17.64% <50.00%> (+1.32%)
:arrow_up:

lapce-core/src/editor.rs
30.36% <88.23%> (+0.65%)
:arrow_up:

lapce-ui/src/app.rs
0.00% <0.00%> (ø)

lapce-ui/src/title.rs
0.00% <0.00%> (ø)

lapce-data/src/data.rs
0.00% <0.00%> (ø)

lapce-ui/src/window.rs
0.00% <0.00%> (ø)

lapce-data/src/update.rs
0.00% <0.00%> (ø)

lapce-proxy/src/terminal.rs
0.00% <0.00%> (ø)

lapce-proxy/src/plugin/wasi.rs
9.18% <0.00%> (+0.04%)
:arrow_up:

... and 2 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Test failure appears to be a false negative due to network timeouts. I think? I don't believe that I have access to rerun.

I think this feature should be improved.
It creates angle brackets when not needed:

Highlights "paired" characters "<" and ">":

I think this feature should be improved.

You're right; angle bracket pairing was half-baked. I've removed it from this PR. I checked several other editors (Doom Emacs, Helix, Typora) and none actually supported angle bracket pairing, but they all supported backtick pairing (which I've left in place in this PR)
Thank you!

Thanks for the feedback, @panekj. Which languages use backtick/grave as an escape (I admit that I'm drawing a blank)?
I'm going back to the drawing board to make this better and to make it more configurable by language. I'd like to make sure that I handle them correctly while also allowing pairing in appropriate langs (eg Markdown, JS, sh/bash, php, etc). Thanks!

powershell uses grave accent as a line continuation character (equivalent to sh \)
Remove-Item `
  -Recurse `
  -Force `
  .

I'm going back to the drawing board to make this better and to make it more configurable by language.

That's currently not possible

powershell uses grave accent as a line continuation/escape character (equivalent to sh \)

Cool, thank you. I don't see Powershell as a supported language in Lapce, though. I'll try to think about how that should work, because I assume there will be lots of "not officially supported" languages where current behaviors could also be annoying. Lisp comes to mind, because lists of symbols can be made via "single quoting" like '(a b c). These are fairly common in lisp.

That's currently not possible

I'm aware. I'm working on changing that.

Lisp comes to mind, because lists of symbols can be made via "single quoting" like '(a b c).

To add to that, we also have such rust syntax, where lifetimes are explicitly specified
fn func_name<'a, 'b>(arg1: 'a type1, arg2: 'b type2) -> (out1::<turbofish1>, out2::<turbofish2>) {


Two Sum Leetcode Problem with Python

Hi @Prem-Kumar-Dev,

I would like to contribute to this for a two sum problem using python. I’d love to help improve this repository as part of Hacktoberfest 2024. Please assign me this task and add the HacktoberFest label.

hey, @Prem-Kumar-Dev can I work on this issue?


Unable to find the script_client.proto file needed to build the Python client

I set-up docker running on a ubuntu VM and followed the commands to get the deployment of new script language (https://github.com/EXASOL/script-languages/tree/master/python_client).
When trying to build, I found that the wget call to https://raw.githubusercontent.com/EXASOL/script-languages/master/script_client.proto, included in the script, is not resolving the URL.
Is there a workaround for this procedure to work? Shouldn't the README be updated with the latest details?
Thanks a lot!

@kamon Hello.
I think this file is now available here: https://github.com/EXASOL/script-languages/blob/master/src/zmqcontainer.proto

Thanks, I've updated the path in the Makefile