Cypress e2e tests for the About Us page

What does this pull request aim to achieve? 💯

Cover the About Us page with end-to-end tests

[x] I have checked that no one else is working on similar changes.

[x] I have read the latest README and understand the development workflow.

[x] The name of this branch is: feature/<branch_name>, or hotfix/<branch_name> if this is a hotfix, where <branch_name> briefly describes the issue(s) resolved and is prefixed with the issue number(s) (e.g. 1127-1130-update-git-branching-model). The branch is created in a cloned version of this repo, not a forked repo.

[x] This branch is rebased/merged with the latest staging (or the latest production if it is a hotfix).

[x] There are no merge conflicts.

[x] There are no console warnings and errors.

[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".

[x] The title describes the issue(s) being addressed using format: <issue_numbers> - <brief_issue_description> (e.g. #1127/#1130 - Update Git Branching Model)

Hi everyone,
this is my first test ever, could you please give me some feedback on it? Appreciate your help!

@TimeaKovacs86 , 1-so far I see you have the function call to get element out of the class.  the class AboutUs has only data, it seem like a JSON data file to me. 2- I am not sure if we should check the the links of supporters (life-time, current and past)

Thank you for your suggestions @jessica-lau , @adorapham . The check of the email and the  exit button on the modal window are good catches! I asked @galeza before I started this test suit if I should check the supporter links or not...and we agreed in not to test them. ( "no, it doesn't work with cypress. you won't be able to verify that. It will open in a new window and cypress will not allow you to switch") Also It would be difficult cause as I checked there are no selectors for those links which means I would have to write xpath localization, and the tests would be fragile. I will correct the code where you suggested! And write the missing ones. Thank you again!

@TimeaKovacs86 thanks for making the changes! All tests passed 👍.
I noticed the format of the code is single quoted vs double quoted. Just sent you a DM.

Hi @TimeaKovacs86
One test needs to be updated. We changed value in the href ContactUs:

In the POM we have:
  contactEmailHref =<EMAIL_ADDRESS>PR #1811 has been merged recently.

@TimeaKovacs86 @jessica-lau
For supporters'  links - maybe we can check  lifetime, current and past supporters containers exist:
main > div > div > div:nth-child(4)
main > div > div > div:nth-child(7)
main > div > div> div:nth-child(10)

and check their visibility. There is a possibility to call children() method and check number of children () but this number will change (I think it will be updated).
cy.get('.left-nav>.nav').children().should('have.length', 8)

Regarding to @jessica-lau's question about the supporter links test, could someone confirm it for me if we need those tests or not? Either way, I am ok with the team's decision. Let me know what you think. @galeza @adorapham @nivetheatha @idjevm

@jessica-lau @TimeaKovacs86
One thing is interesting for me. We used to use cy.get(selector) methods in the POM file like in the joinNow.js:
  getEmailField() {
    return cy.get(this.emailField);
  }

Here we have only selectors in the POM aboutUs.js and operations on page were moved to test spec file.
I always put all operations and searching for elements in the POM file. Maybe this is selenium inheritance but maybe all operations on elements should we put in POM? What do you think @jessica-lau ?

Hi everyone! I took out those test that checked the members of each supporter group. As far as I know the tests are running and passing. Let me know if I can do something else to make it better... Thank you for all the help!

Hi everyone! I took out those test that checked the members of each supporter group. As far as I know the tests are running and passing. Let me know if I can do something else to make it better... Thank you for all the help!

@TimeaKovacs86 , i make a quick run and get error , please take a look

@TimeaKovacs86 , I run local and see all the test passed  but let wait for confirmation if you need to move the functions to POM files :)

@jessica-lau @TimeaKovacs86
One thing is interesting for me. We used to use cy.get(selector) methods in the POM file like in the joinNow.js:
  getEmailField() {
    return cy.get(this.emailField);
  }

Here we have only selectors in the POM aboutUs.js and operations on page were moved to test spec file like:
  function closeGetInvolvedModalWindow() {
    **cy.get(aboutUs.getInvolvedCloseButton)**.click();
  }

I always put all operations and searching for elements in the POM file. Maybe this is selenium inheritance but maybe all operations on elements should we put in POM? What do you think @jessica-lau ?
Sorry, I didn't see this comment before I committed the last changes on the code. So, do you prefer if I move the getInvolvedCloseButton as a function in the POM aboutUs.js and in the spec there will be:
 function closeGetInvolvedModalWindow() {
    getInvolvedCloseButton().click()
}

And if I understand good this is the only thing what I should move to aboutUs.js, the last two functions written in the spec (checkEmailWorks ()and supporterContainerVisible()) are good where they are? Or should I move the one with the cy.xpath to the POM as well?

@TimeaKovacs86 yea I do agree with @galeza . Getter methods should be moved to the POM file so that it's more object oriented and it'll also be consistent with how all the other POM files are written. You can take a look at the other POM files as an example - methods are created on the selectors and then the methods are used in the test specs instead of directly referencing the selector.

I moved the cy.get and cy.xpath methods to the POM file. Please have a look, and let me know if I there is anything else I can do to make this test better.

Thank you all, for the help! @idjevm Please merge!

@idjevm please merge : ) Thanks.

I see that Merge option is enabled for me so I'm merging this PR


React 19 Support

Could you please consider upgrading to support React 19? Thank you!

{
  "peerDependencies": {
    "immer": ">=8.0.0",
    "react": "^16.8.0 || ^17.0.1 || ^18.0.0 || ^19.0.0"
  },
}

hi @chioio , I will update zustand-mutative later to support React 19.

I have released zustand-mutative v1.2.0. Feel free to use it.


Removing code samples from core app

And adding it to the install template.  I don't think this belongs in the main app.  This commit will add it to the install template so that when you get a new handoff proejct, it'll come with a sample page, but deleting it will remove it.

I also added some html to the installed sample page to show how you could do that.


Seeking help about seata error "service.vgroupMapping.default_tx_group"

Windows
jdk1.8.0
nacos 2.1.2
seata-server-1.7.0
These days I want to use seata in my project, but occured an error which could not solve it even though I try to find the solution on www.baidu.com, so I want to seek help here, could you please help me?

my config are as follows:
1. seata\script\config-center\config.txt, all config in this file has been uploaded to nacos, I just modify store.mode=db and db config, and service.default.grouplist=<IP_ADDRESS>:8091
2. seata\conf\application.yml

seata:
config:
type: nacos
nacos:
server-addr: <IP_ADDRESS>:8848
namespace:
group: SEATA_GROUP
username: nacos
password: nacos
context-path:
registry:
type: nacos
nacos:
application: seata-server
server-addr: <IP_ADDRESS>:8848
group: SEATA_GROUP
namespace:
cluster: default
username:
password:
context-path:

3. my project application.properties

seata.data-source-proxy-mode=AT
seata.tx-service-group=default_tx_group
seata.registry.type=nacos
seata.registry.nacos.server-addr=<IP_ADDRESS>:8848
seata.registry.nacos.group=SEATA_GROUP
seata.registry.nacos.cluster=default
seata.config.type=nacos
seata.config.nacos.server-addr=<IP_ADDRESS>:8848
seata.config.nacos.group=SEATA_GROUP
seata.config.nacos.username=nacos
seata.config.nacos.password=nacos

When I start my project, occured error:
main] .s.s.a.d.SeataAutoDataSourceProxyCreator: Auto proxy of [druid]
main] com.alibaba.druid.pool.DruidDataSource: {dataSource-1} inited
main] i.s.c.r.netty.NettyClientChannelManager: can not get cluster name in registry config 'service.vgroupMapping.default_tx_group', please make sure registry config correct
Could you please give me some suggestions?

In nacos service. vgroupMapping. default_tx_group configuration value is what?

In nacos service. vgroupMapping. default_tx_group configuration value is what?

service.vgroupMapping.default_tx_group=default

In nacos service. vgroupMapping. default_tx_group configuration value is what?

oh , I make a mistake when I upload seata/srcipt/config-center/config.txt, what my command is :
[root@localhost nacos]# sh nacos-config.sh -h <IP_ADDRESS> -p 8848 -g SEATA_GROUP -u nacos -w nacos
set nacosAddr=<IP_ADDRESS>:8848
set group=SEATA_GROUP
Set transport.type=TCP successfully
Set transport.server=NIO successfully
nacos host should be <IP_ADDRESS>, although it will sync config from db which uploaded by <IP_ADDRESS>
Anyway,thanks !

service.vgroupMapping.default_tx_group=default放到nacos上


Add instructions for Spresense  on each examples

Add Spresense instruction in README.mds of hello_world, micro_speach and person_detection in lite/micro/examples.
Please review it.

I have added issue as #50429


Resolve timer trigger not getting correctly catched in Gradle Check

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
Resolve timer trigger not getting correctly catched in Gradle Check
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/2966
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2970 (da31fe7) into main (f0477c2) will decrease coverage by 0.30%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2970      +/-   ##
==========================================
- Coverage   93.17%   92.87%   -0.31%
==========================================
  Files         167      167
  Lines        4602     4602
==========================================
- Hits         4288     4274      -14
- Misses        314      328      +14

Impacted Files
Coverage Δ

src/system/temporary_directory.py
64.44% <0.00%> (-28.89%)
:arrow_down:

src/system/os.py
94.73% <0.00%> (-5.27%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add the main README

Type

Documentation

Related JIRA Issue(s)
ENSWBSITES-534
Importance
Our repo needs a proper README!
Description
Initial draft of top-level README, plus minor changes to the more technical README in the ensemb/src directory.
Views affected
None.
Other effects
None.
Possible complications
None, apart from the fact that this is the first page any visitor sees!

Changes made as per Andy's request.


Outline best practices for sharing Kuzu databases

I'm wondering whether and how Kuzu databases may be shared to others. For example, after creating a Kuzu database, one ends up with a directory of files associated with the database. May this set of files be safely shared to others with the intention of enabling reproducible graph data science work? Mostly here I wonder: would it work at all from system to system, and separately, is it secure to do this openly/publicly (no "invisible" sensitive data included which wasn't a part of data ingest or creation)?
If Kuzu databases themselves shouldn't be shared, what is the best way of "exporting/converting" the entire database so it may be reused elsewhere?
Apologies if this is already outlined somewhere, I tried to find this and may not have been using the correct keywords. Thanks in advance for any thoughts you have on this!

Thank you @prrao87 , very much appreciate the guidance on this!


AlongRizal

__Originally posted by @AlongRizaL in https://github.com/Join-Now/mega888/AlongRizal

__Originally posted by @AlongRizaL in https://github.com/Join-Now/mega888/AlongRizal


zmqserver can cache objects

If the zmqserver gets a set_object command that sets precisely the same object data on precisely the same path that already exists, then do not forward it to the connected websockets.
This makes a dramatic improvement in the workflow of using meshcat on colab (at least as we use it in drake), because we don't have to repeatedly download large meshfiles from repeated simulations.

Codecov Report

Merging #75 into master will decrease coverage by 1.62%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
- Coverage   75.98%   74.35%   -1.63%
==========================================
  Files          11       11
  Lines        1012     1014       +2
==========================================
- Hits          769      754      -15
- Misses        243      260      +17

Impacted Files
Coverage Δ

src/meshcat/servers/zmqserver.py
31.95% <0.00%> (-1.11%)
:arrow_down:

src/meshcat/path.py
95.23% <0.00%> (-4.77%)
:arrow_down:

src/meshcat/geometry.py
88.54% <0.00%> (-3.44%)
:arrow_down:

src/meshcat/commands.py
92.59% <0.00%> (-1.86%)
:arrow_down:

src/meshcat/animation.py
77.77% <0.00%> (-1.02%)
:arrow_down:

src/meshcat/tests/test_drawing.py
97.14% <0.00%> (-0.58%)
:arrow_down:

Continue to review full report at Codecov.

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


Why i can't use the involution directly?

Very Nice work.

I'm so sorry. I have set the error channels and reduction ration so that i made the outputchannel=0

Sry to bother. I also want to insert involution block to my network. How did you deal with it? Did it mean that I need to train from scratch without pre-train model?


Pr3 parser

What does this PR do?
This PR continues to extend this application to parse metadata records from a completed crawl.
Helpful background context
As noted throughout the README, the motivating factor for wrapping the browsertrix-crawler in a container was so that we could perform actions after the crawl was to parse metadata records representing websites from that crawl.
As noted in documentation about metadata parsing, the creation of metadata records is an opinionated process.  This harvester was built to support crawling of the library websites and producing records for TIMDEX.
While this CrawlParser class could be extended in a number of ways to generate meaningful metadata records about non-library websites, and technically it would work for non-library websites, the additional metadata it extracts from the actual HTML content is geared towards our Library WordPress websites.
How can a reviewer manually see the effects of these changes?
Update the docker image and run a test harvest via a Make command:
make dist-local
make test-harvest-local

Once the crawl is complete, a single XML should be available locally on the host machine (as the harvest was performed via a docker container) at output/crawls/collections/homepage/homepage.xml.
Reviewing this XML file will reveal what kind of data is parsed from the websites crawled.
Includes new or updated dependencies?
NO
What are the relevant tickets?
https://mitlibraries.atlassian.net/browse/TIMX-247
Developer

[X] All new ENV is documented in README (or there is none)
[X] Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

[ ] The commit message is clear and follows our guidelines
(not just this pull request message)
[ ] There are appropriate tests covering any new functionality
[ ] The documentation has been updated or is unnecessary
[ ] The changes have been verified
[ ] New dependencies are appropriate or there were no changes

@ghukill Thank you so much for taking the time to carefully document important classes and methods! I would definitely need more time understand it on a much deeper level (which I aim to do via attempt to create a diagram for this application) and will probably have more feedback then. However, from a high-level perspective, I think the codebase is well-organized, documented, and it's apparent that a lot of care and thought has been put into it. :) I just have three clarifying questions above!


add scripts to make mass generation easier

these files currently assume they're placed in the root Archipelago directory but make mass world generation/testing easier

Mind adding to the readme a blurb what each batch file does?


[bug] production build not working

I'm submitting a ...  (check one with "x")
[x] bug report => check the README and search github for a similar issue or PR before submitting
[ ] support request => check the README and search github for a similar issue or PR before submitting
[ ] feature request

Current behavior

After a fresh git clone / npm install, I run npm run build:universal-prod

I get this issue 4 times.

Then :

Expected/desired behavior

Build files ready for universal production server.
Minimal reproduction of the problem with instructions
npm run build:universal-prod
Please tell us about your environment:

Mac OS, yarn.

Angular version: 4.1.0

Node (for AoT issues): node --version =  6.9.1

Thanks !
PS : it might be that I don't completely understand how to run production. If so, I can create a PR modifying the readme.

It's a known issue which arises today, this repo depends on the harmony branch of UglifyJs2 and it got somehow broken. If you visit the latest issues on that repo, you'll notice how everyone's builds are failing.
Commenting Uglify plugin from webpack config will help the prod build to be successful. Tomorrow, I'll have a look at the UglifyJs2 repo and try to solve this.

Cool, thanks !
👍

(internal note)
here's a list of links referencing the major crash on UglifyJS:

https://github.com/webpack-contrib/uglifyjs-webpack-plugin/issues/32
https://github.com/webpack-contrib/uglifyjs-webpack-plugin/issues/31
https://github.com/mishoo/UglifyJS2/issues/448#issuecomment-300403182

i have same issue

@Mahmoud-hassan87 i'm still collecting information on this topic, seems like the new of UglifyJS broke many things.
Stay tuned.

@theomathieubhvr @Mahmoud-hassan87 get the latest version and try to build. I temporarily commented the UglifyJs and it should run without a problem now.

Thanks ! That's working now.
I don't know what to do with this issue, renaming it or closing it ?
I'll let you decide.

Let's leave it because I could not reproduce it (using fulls1z3/webpack as a dependency). Let's keep this open for a few more days, and let's see.

I solved this by forcing the uglify-js deps to use version git://github.com/mishoo/UglifyJS2#harmony-v2.8.22.
Get the latest version of this repository, and remove webpack and uglify-js dirs from node_modules and run npm install/yarn et voila!


Merck dl patch SSO

As SSO is default variant a generation of secrets has been updated.

Reviewed. We are closing this PR as not relevant anymore.


Polyline crashes iOS App

Summary
When apply lineDashPattern in Polyline, iOS App not responding.
Reproducible sample code
<MapView
  provider={PROVIDER_GOOGLE}
  style={{
      ...StyleSheet.absoluteFillObject,
  }}
  initialRegion={initialRegion}
  onRegionChangeComplete={handleRegionChange}
  zoomEnabled={true}
  maxZoomLevel={18}
  minZoomLevel={0}
  rotateEnabled={false}
>
    <Polyline
        coordinates={plannedRoutePoints.map((item)=>({longitude:item.lng, latitude:item.lat}))}
        strokeColor={Colors.BRIGHT_BLUE}
        strokeWidth={2}
        lineDashPattern={[10,10]}
    />
</MapView>

Steps to reproduce
Add linDashPattern to polyline
Expected result
Render dash line
Actual result
iOS App stop responding
React Native Maps Version
1.3.2
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.70.1
What version of Expo are you using?
Not using Expo
Device(s)
Simulator iPhone 14 Pro
Additional information
No response

Same for me

+1
Same here after user gives the permission.

Getting this as well

I am facing the same problem, the App is crashed while using Polyline. is there any solution? @shawarmaz  @harisraza123  @christopherldo @yeesiang95

Was anyone able to resolve this issue? @logan0900 @shawarmaz @harisraza123 @christopherldo @yeesiang95

I'm unable to reproduce this with the sample code provided. Can anoyone experiencing this please provide a minimal sample repo or expo snack?

Hi, here is the example of polyline  https://snack.expo.dev/2lhxoVu-y
When I set the lineDashPattern property for the Polyline, and the iOS simulator crashed.

I'm unable to reproduce this with the sample code provided. Can anoyone experiencing this please provide a minimal sample repo or expo snack?

I solved removing the parameter lineDashPattern from the <Polyline> definition

I'm having this exact same issue.
react-native: 0.68.5
react-native-maps: 1.6.0
iPhone: 14 Pro (simulator)
iOS: 16.2
The app freezes when rendering a Polyline with the parameter lineDashPattern on iOS with Google Maps. It also happens with a 'LineString' Geojson (i assume it works the same as a Polyline).
This is my polyline:
<Polyline
   coordinates={[
     {latitude: -34.992509, longitude: -63.580034},
     {latitude: -36.825394, longitude: -65.824174},
   ]}
   lineDashPattern={[1, 20]}
/>

It works perfectly on Android

SAme problem here, the only solution i am using right now is to remove lineDashPattern prop from polyline

Same here. I am just using PolyLine with coordinates props, and I am crashing immediately when the map loads:
  <Polyline
    coordinates={[
      {latitude: 40.7128, longitude: 74.0060},
      {latitude: 40.8128, longitude: 74.0060},
    ]}
  />


panic on missed argument

Expected behavior
error: unable to find "Kptfile" in package "image-tag"

Actual behavior
✦ ❯ kpt cfg set image-tag v0.1.11
panic: runtime error: index out of range [2] with length 2

goroutine 1 [running]:
sigs.k8s.io/kustomize/cmd/config/internal/commands.(*SetRunner).preRunE(0xc0007d2780, 0xc000839600, 0xc0001c2640, 0x2, 0x2, 0x0, 0x0)
	sigs.k8s.io/kustomize/cmd/config@v0.9.9/internal/commands/cmdset.go:78 +0x331
github.com/spf13/cobra.(*Command).execute(0xc000839600, 0xc0001c2600, 0x2, 0x2, 0xc000839600, 0xc0001c2600)
	github.com/spf13/cobra@v1.1.1/command.go:839 +0x523
github.com/spf13/cobra.(*Command).ExecuteC(0xc000028b00, 0x200000003, 0xc000000180, 0xc00082ff78)
	github.com/spf13/cobra@v1.1.1/command.go:958 +0x375
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.1.1/command.go:895
main.main()
	github.com/GoogleContainerTools/kpt/main.go:37 +0x65

Information
Accidentally missed directory argument and got panic
Kpt 0.39.1

Steps to reproduce the behavior
Just as is
kpt cfg set please explode

Hi, thanks for reporting this. Could you try running this with kpt v0.39.2 and let us know if this is still occurring? I no longer see this behavior in that version. This is what I am seeing on version 0.39.2:
$ kpt cfg set image-tag v0.1.11
error: value must be provided either from flag or arg


[Access Request] Table 7321- Warehouse Shipment Line

Hi Al team,
I would like to access the following variables from the extension object
    protected var
        WhseShptHeader: Record "Warehouse Shipment Header";

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Is it available for Python Version 3.x ??

Hi, I found your package. It's looking amazing but it's not available for python 3.x I have Question that when It will be available for Python 3.x. When the new update is coming??

First:
Please read this: https://github.com/Skype4Py/Skype4Py#new-style-cloud-chats-dont-work---must-use-old-type-p2p-chats
It is not all new chats that are possible to use with skype and python
Second:
There is a python3-beta branch. You are more than welcome to try it and please contribute to the branch
Third:
Microsoft have discontinued the old skype api, with the old clients and introduced a new api. See https://dev.skype.com/ for how to use the api.

First:
Please read this: https://github.com/Skype4Py/Skype4Py#new-style-cloud-chats-dont-work---must-use-old-type-p2p-chats
It is not all new chats that are possible to use with skype and python
Second:
There is a python3-beta branch. You are more than welcome to try it and please contribute to the branch
Third:
Microsoft have discontinued the old skype api, with the old clients and introduced a new api. See https://dev.skype.com/ for how to use the api.

Just use '2to3' python module It will change the syntax of this code fron python 2 to 3 in few seconds Here is the link

Just use '2to3' python module It will change the syntax of this code fron python 2 to 3 in few seconds Here is the link


CLOUDSTACK-9404 Fixed ordering of network ACL rules being sent to the VR.

The comparator was inverted.
Issue: https://issues.apache.org/jira/browse/CLOUDSTACK-9404
In this example, I created rules with the port numbers the same as the rule numbers.
Chain ACL_INBOUND_eth2 (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             <IP_ADDRESS>
ACCEPT     all  --  anywhere             vrrp.mcast.net
DROP       tcp  --  anywhere             anywhere             tcp dpt:netstat
DROP       tcp  --  anywhere             anywhere             tcp dpt:10
DROP       tcp  --  anywhere             anywhere             tcp dpt:5
DROP       tcp  --  anywhere             anywhere             tcp dpt:3
DROP       tcp  --  anywhere             anywhere             tcp dpt:2
DROP       all  --  anywhere             anywhere
We can see above that the rules are inverted.
After the fix:
Chain ACL_INBOUND_eth2 (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             <IP_ADDRESS>
ACCEPT     all  --  anywhere             vrrp.mcast.net
DROP       tcp  --  anywhere             anywhere             tcp dpt:2
DROP       tcp  --  anywhere             anywhere             tcp dpt:3
DROP       tcp  --  anywhere             anywhere             tcp dpt:5
DROP       tcp  --  anywhere             anywhere             tcp dpt:10
DROP       tcp  --  anywhere             anywhere             tcp dpt:netstat
DROP       all  --  anywhere             anywhere

the changes look good to me

@pdube Travis timed out, you may want to try the Travis Lottery again ;-)
Is this ready for testing?

@remibergsma Yes, the rules should appear in the right order now.

@pdube Thanks, will give it a try soon

The Travis build has timed out 3 times now. Is there any known issue with Travis right now @swill ?

Looks clean and the added test case should prevent this from happening again.  According to the "git blame" the comparator was switched back in 2013 and has been broken since.

The only known issue is that it this periodically happens.  I have not had a chance to dig deeper...

I just kicked off a build that includes this PR.  I'm going to push this to our lab for testing and report back.

I tested this in our lab with advanced networking verified the patch is working as expected.  I used the following test process.

In short, LGTM based on testing.

Thanks @dmabry

@pdube No problem.  Think you could kick this off again and see if Travis comes back green?

@pdube can you close and reopen this one?  thx...

CI RESULTS
Tests Run: 85
  Skipped: 0
   Failed: 0
   Errors: 0
 Duration: 4h 01m 52s

Associated Uploads
/tmp/MarvinLogs/DeployDataCenter__Jun_13_2016_17_06_42_SFRV4J:

dc_entries.obj
failed_plus_exceptions.txt
runinfo.txt

/tmp/MarvinLogs/test_network_8S1TLA:

failed_plus_exceptions.txt
results.txt
runinfo.txt

/tmp/MarvinLogs/test_vpc_routers_SYNGX8:

failed_plus_exceptions.txt
results.txt
runinfo.txt

Uploads will be available until 2016-08-14 02:00:00 +0200 CEST
Comment created by upr comment.

@pdube though the fix looks good, the root of the issue is different.
Earlier when bash scripts were used to configure rules on VR, iptable rules for ACLs were inserted (-I option).
This changed to add (-A option) after VR refactor, resulting in rules being applied in the reverse order.

I'm not sure what to make of this comment @kishankavala. Is that a LGTM?

@swill This is a regression caused by VR refactor. There could be more such issues. I would prefer a fix in the VR script. Current fix is more like reversing the order twice to make it correct.

@pdube can you review @kishankavala's comments.  I want to cut an RC soon, but we have other pending issues in the VR right now which @kiwiflyer, @dmabry and team are working on...

Looking through the git blame for this section of code it appears the operator and the ordering of the list was the same as this patch prior to 2013 when the operator was switched.

@kishankavala I think that the ultimate fix will be in the VR. However, the inversion of the list is fixed with this patch, and does not require a VR update. This is a good enough fix for now, as the ordering inversion is a critical security bug, since the rule numbers you are giving are not being applied as expected.

@leprechau ACL rule ordering was introduced in 2013 in ACS 4.2. Since 4.2 release, the order was never changed.
 I'm only concerned about more such issues in VR.
can you please create a tracking bug for VR fix and make a note that this is a regression?

@kishankavala Understood, thank you for the explanation.  The long history of the project makes digging into some of these things difficult.

ACS CI BVT Run
Sumarry:
Build Number 207
Hypervisor xenserver
NetworkType Advanced
Passed=68
Failed=5
Skipped=3
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_vpc_vpn.py

ContextSuite context=TestRVPCSite2SiteVpn>:setup Failing since 24 runs

ContextSuite context=TestVpcRemoteAccessVpn>:setup Failing since 23 runs

ContextSuite context=TestVpcSite2SiteVpn>:setup Failing since 22 runs

test_volumes.py

test_06_download_detached_volume Failed

test_vm_life_cycle.py

test_10_attachAndDetach_iso Failed

Skipped tests:
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_disk_offerings.py


Are there any docs for custom LBs yet?

As I can't find any reference anywhere about that topic I am opening an issue here :)
So the question is really about everything that is essential when going to build own load balancers that use e.g. NGINX. I know there is a API doc, but there does seem to be no docs at all about stuff like how a custom LB should handle the service discovery.
Am I just overseeing those docs, if so please post me a link to it :), if not are there some docs in work? I guess for now I will fight through the source of the default lb.
Thank you!

As Ic right now, it is intended to really build upon the lb-controller and add a provider to it. I guess there really aren't any docs there yet?

The information you need is available in metadata, so you basically watch for changes and apply the relevant configuration.  Implementing a new provider in lb-controller manages the watching part for you so you just have to implement a few methods to configure, reload, etc.
The UI doesn't show a field to change the balancer image but you can update /v2-beta/settings/  lb.instance.image to point somewhere else.


i18n is not working with domains

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Next.js
Amplify APIs
Not applicable
Amplify Categories
hosting
Environment information

# Put output below this line
 System:
    OS: macOS 11.3.1
    CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
    Memory: 278.45 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.5 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.24.0 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 94.0.4606.81
    Edge: 94.0.992.50
    Firefox: 93.0
    Safari: 14.1
  npmPackages:
    @ampproject/toolbox-optimizer:  undefined ()
    @babel/core:  undefined ()
    @headlessui/react: ^1.4.1 => 1.4.1
    @heroicons/react: ^1.0.4 => 1.0.4
    @testing-library/jest-dom: ^5.14.1 => 5.14.1
    @testing-library/react: ^12.1.2 => 12.1.2
    @types/jest: ^27.0.2 => 27.0.2
    @types/node: ^16.10.3 => 16.10.3
    @types/react: 17.0.27 => 17.0.27
    @types/react-copy-to-clipboard: ^5.0.2 => 5.0.2
    @types/smoothscroll-polyfill: ^0.3.1 => 0.3.1
    @vercel/nft:  undefined ()
    amphtml-validator:  undefined ()
    arg:  undefined ()
    async-retry:  undefined ()
    async-sema:  undefined ()
    autoprefixer: ^10.3.7 => 10.3.7
    axios: ^0.21.4 => 0.21.4
    babel-jest: ^27.2.4 => 27.2.4
    bfj:  undefined ()
    cacache:  undefined ()
    ci-info:  undefined ()
    classnames: ^2.3.1 => 2.3.1 (2.2.6)
    cli-select:  undefined ()
    comment-json:  undefined ()
    compression:  undefined ()
    conf:  undefined ()
    content-type:  undefined ()
    cookie:  undefined ()
    cross-spawn:  undefined ()
    css-loader:  undefined ()
    debug:  undefined ()
    devalue:  undefined ()
    escape-string-regexp:  undefined ()
    eslint: 7.32.0 => 7.32.0
    eslint-config-next: 11.1.2 => 11.1.2
    eslint-config-prettier: ^8.3.0 => 8.3.0
    file-loader:  undefined ()
    find-cache-dir:  undefined ()
    find-up:  undefined ()
    framer-motion: ^4.1.17 => 4.1.17
    fresh:  undefined ()
    glob:  undefined ()
    gzip-size:  undefined ()
    http-proxy:  undefined ()
    identity-obj-proxy: ^3.0.0 => 3.0.0
    ignore-loader:  undefined ()
    is-animated:  undefined ()
    is-docker:  undefined ()
    is-wsl:  undefined ()
    jest: ^27.2.4 => 27.2.4
    json5:  undefined ()
    jsonwebtoken:  undefined ()
    loader-utils:  undefined ()
    lodash.curry:  undefined ()
    lru-cache:  undefined ()
    mini-css-extract-plugin:  undefined ()
    nanoid:  undefined ()
    neo-async:  undefined ()
    next: 11.1.2 => 11.1.2
    ora:  undefined ()
    popmotion: ^10.0.1 => 10.0.1 (9.3.6)
    postcss: ^8.3.11 => 8.3.11 (8.2.15)
    postcss-flexbugs-fixes:  undefined ()
    postcss-loader:  undefined ()
    postcss-nested: ^5.0.6 => 5.0.6
    postcss-preset-env:  undefined ()
    postcss-scss:  undefined ()
    prettier: 2.4.1 => 2.4.1
    react: 17.0.2 => 17.0.2
    react-copy-to-clipboard: ^5.0.4 => 5.0.4
    react-dom: 17.0.2 => 17.0.2
    react-horizontal-scrolling-menu: ^2.5.0 => 2.5.0
    react-share: ^4.4.0 => 4.4.0
    react-share-social: ^0.1.48 => 0.1.48
    react-test-renderer: ^17.0.2 => 17.0.2
    recast:  undefined ()
    resolve-url-loader:  undefined ()
    sass-loader:  undefined ()
    schema-utils:  undefined ()
    semver:  undefined ()
    send:  undefined ()
    smoothscroll-polyfill: ^0.4.4 => 0.4.4
    source-map:  undefined ()
    storyblok-js-client: ^4.1.5 => 4.1.5
    storyblok-react: ^0.1.2 => 0.1.2
    string-hash:  undefined ()
    strip-ansi:  undefined ()
    swiper: ^7.0.9 => 7.0.9
    swiper_angular:  0.0.1
    tailwindcss: ^2.2.16 => 2.2.16
    terser:  undefined ()
    text-table:  undefined ()
    typescript: 4.4.3 => 4.4.3
    unistore:  undefined ()
    web-vitals:  undefined ()
    webpack:  undefined ()
    webpack-sources:  undefined ()
    zen-observable:  undefined ()
  npmGlobalPackages:
    @angular/cli: 9.1.4
    @azure/static-web-apps-cli: 0.6.1
    @nestjs/cli: 6.8.4
    bower: 1.8.8
    create-next-app: 10.2.3
    gulp: 4.0.2
    n: 2.1.12
    npm: 7.24.0
    serverless: 1.50.0
    yarn: 1.22.10

Describe the bug
When using domain based i18n in Nextjs, the hosted version always returns the global default language regardless of the configuration specified for a domain.
It works locally, so I assume it has something todo with the lambda edge functions that are being deployed alongside the files for SSR support.
Expected behavior
Deliver correct defaultLanguage according to next.config.js configuration based on the domain.
Reproduction steps
Deploy an nextjs app with domain specific i18n configuration.
Code Snippet
// Put your code below this line.
module.exports = {
  reactStrictMode: true,

  i18n: {
    localeDetection: false,
    locales: ['en', 'de'],
    defaultLocale: 'en',

    domains: [
      {
        domain: 'example.com',
        defaultLocale: 'en',
      },
      {
        domain: 'example.de',
        defaultLocale: 'de',
      }
    ],
  },
}

Log output

// Put your logs below this line

aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response

@SebastianSchenk
Hi!
I have the same issue.
I have running my app with Vercel and Amplify.
Domain routing didn't works with the Amplify only.
region=us-east-1
arn:aws:amplify:us-east-1:479336677459:apps/d2617fmgdtfzyf

@dqunbp thanks for verifying with Vercel!

@SebastianSchenk any updates?

No, nothing new here. I ended up not using the i18n domain feature and instead, changed the default language based on the brunch in CI/CD. This means I have one prod branch for each language. This workaround is quite tedious, but it helped me passing by this problem.

@SebastianSchenk @chrisbonifacio
I looks like that issue is gone, my app renders correctly for each language

@chrisbonifacio, Wondering if there have been any updates to this issue. I am running into the same problem when hosting with Amplify and using Next.js' i18n functionality for locale switching between domains. I tested the functionality on Vercel, where it works as intended but not on Amplify it is serving the wrong locale.
The issue seems related to pages that share the same path for different locales

Is there any update on this? I would love to use AWS Amplify to host nextjs, but I can't make the switch without support for domain based routing 😅

Hey @hloriana, any news here? Some other folks have been waiting for domain routing to work for a while now:
https://github.com/aws-amplify/amplify-hosting/issues/2340
Looks like theres an issue with Cloudfront ommitting headers needed for the redirect to work, yet you explicitly list you support domain routing here: Internationalized (i18n) domain routing
Am I missing something here? I'm reproducing the same bug in app d1jx07rvivs0st

Hey @hloriana, @chrisbonifacio any news here? Some other folks have been waiting for domain routing to work for a while now: #2340 Looks like theres an issue with Cloudfront ommitting headers needed for the redirect to work, yet you explicitly list you support domain routing here: Internationalized (i18n) domain routing
Am I missing something here? I'm reproducing the same bug in app d1jx07rvivs0st us-east-1

Actually it is not the first time they add an unsupported feature into supported feature here 😄
Also that is related to auto locale detection.
I want to know is this issue is exist for you guys ? because I couldn't setup domain routing.

No, nothing new here. I ended up not using the i18n domain feature and instead, changed the default language based on the brunch in CI/CD. This means I have one prod branch for each language. This workaround is quite tedious, but it helped me passing by this problem.

It is a good workaround. as we have a amplify app for each domain I added default lcoale in env variable and use that directly in i18n.defaultLocale

Does anyone have a workaround for this issue?
Is there an option to set forwarded header for Amplify App?
Amplify apps doesn't appear in CloudFront so it is not possible to make any configurations at that level.

This feature has just been supported with our latest launch! I'm closing this issue as it's been resolved.
Check out the details here: https://aws.amazon.com/blogs/mobile/cdn-caching-improvements-for-better-app-performance-with-aws-amplify-hosting/


Fixed cli tool for windows

Summary of Changes
This PR corrects an issue in the getPluginsPath function where the path was incorrectly formatted on Windows systems. Previously, the path looked like C:\Users\user\AppData\Roaming Elgato/StreamDeck/Plugins, and this has been fixed to use the correct path separators.
Additionally, the changes include a try-catch block to handle potential errors when checking for existing plugins by UUID. This prevents the TypeError [ERR_INVALID_ARG_TYPE] from propagating if encountered.
Before
Previously, the path on Windows looked like: C:\Users\user\AppData\Roaming Elgato/StreamDeck/Plugins
After
Now, the corrected path is used: C:\Users\user\AppData\Roaming\Elgato\StreamDeck\Plugins
Testing

Tested on Windows to ensure the corrected path is generated successfully. Now creating a plugin with the cli works

Thanks @sohneg, the new path construction looks good!
The empty catches mask errors, so we should remove / handle these better. Couple of questions;

With the path resolution changes, are you still encountering ERR_INVALID_ARG_TYPE?
What version of Node and NPM are you using?

I agree, it's just a fast resolution I found. If you like I can improve it a bit more.

Yes the error still appears. It is because if the getPlugins() doesn't find any objects and it's a empty [] then it crashes. That's why I add the try catch. So if it doesn't find any plugins in the Plugins folder it is catched so it won't crash.

npm version 8.19.3,
node version v18.13.0


UI Error Messages

Can anyone explain to me when does this "ver_fail_server" message is displayed (found it in Localization )?We can't seem to display it on our end (this is for testing scenario). Thanks!
And if you don't mind, can you also explain how the other messages do mean (this is for reference)?

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

ID: 986c1f85-07c7-ec91-d4fb-d5da5676c6f1
Version Independent ID: 98782e9a-7697-52a3-754c-e1c6527401bb
Content: Localization string IDs - Azure Active Directory B2C
Content Source: articles/active-directory-b2c/localization-string-ids.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@leon8154 Thank you for your query. We will investigate and update the thread .

@msmimart, Can you please take a look at this.

In our experience, ver_fail_server is shown if an email can't be sent to the supplied email address.
For example, the default regex for the email claim will allow emails such as firstname.lastname@outlook, but this will result in a ver_fail_server message

#reassign:JasSuri

This error is issued when our mail server (Self Service Password Reset Service), deems the email to be invalid/unreachable/or itself fails for any reason to send the SMTP request to the inbox.

Thanks for your feedback @leon8154. Please also see Error codes: Azure Active Directory B2C. Hopefully this helps - I'll go ahead and close this issue for now but let us know if you have other feedback on the docs. #please-close


Add note to README about lint failing on first run without having changed module name

This trolled me for a while (being relatively new to both puppet and ruby). I think the edit is correct in terms of the necessary order things must be done in, but it's entirely possible I have got the wrong end of the stick here!

This is definitely a gotcha that I've noticed more than a few times. Thanks @jen20!


Add raylib as a Git submodule

This way, there is only one folder for raylib and we don't need to clone it every time we configure a CMake build in a new folder. Also, it should make it easier to automatically generate s7 to C binding code using raylib parser.
This PR also disables raylib's compilation warnings.
Note: I don't know if "libs" is the best name for this folder, maybe "3rdparty" would be a nice one as well (or it may doesn't matter at all).
Also, maybe it makes sense moving s7 to this folder, since it's a third-party library as well.

Merging on Master! An important note:  I'm not particularly fan of using submodules, but I investigated some options using CMake (e.g. using FETCHCONTENT_BASE_DIR) and there is a problem of caching just dependencies source code (but not binaries) between different builds. The problem is better described here: https://www.reddit.com/r/cmake/comments/pcs4zj/question_avoiding_multiple_downloads_with/. Having said that, submodules does work well for this case, but ideally I'd still prefer to have a CMake only solution.

You know, CMake have a Git module that could be used to clone the dependencies' source repository in a generic enough way. I do think it wouldn't make much of a difference between using CMake this way and using Git submodules though. If your concern is people forgetting to clone the submodules, we could also use this module to clone the submodules during the build if necessary.


Update opensearch build name in releases

Signed-off-by: Junqiu Lei<EMAIL_ADDRESS>Description
Update opensearch build name in releases to 2.2 branch, it was merged to main by #119.
Test
(base) ➜  geospatial-junqiu git:(update_os_name_2.2) ./gradlew assemble --no-daemon --refresh-dependencies -DskipTests=true
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.4.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 7.4.1
  OS Info               : Mac OS X 12.3.1 (x86_64)
  JDK Version           : 11 (Eclipse Temurin JDK)
  JAVA_HOME             : /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home
  Random Testing Seed   : C24973C818C88780
  In FIPS 140 mode      : false
=======================================

BUILD SUCCESSFUL in 30s
11 actionable tasks: 11 executed

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #120 (fa2dae3) into 2.2 (d440c44) will increase coverage by 0.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                2.2     #120      +/-   ##
============================================
+ Coverage     86.22%   86.38%   +0.16%
- Complexity      160      161       +1
============================================
  Files            28       28
  Lines           617      617
  Branches         42       42
============================================
+ Hits            532      533       +1
  Misses           78       78
+ Partials          7        6       -1

Impacted Files
Coverage Δ

...ospatial/action/upload/geojson/ContentBuilder.java
92.00% <0.00%> (+4.00%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


pnpm and Parsing error: Cannot find module

After migrating from yarn to pnpm I'm getting Parsing error: Cannot find module '@babel/plugin-proposal-decorators' error, but only in vscode,
pnpm eslint index.js in the terminal (even a terminal inside vscode) works fine.

Repro
see https://github.com/discourse/mass-merge – main branch for the working yarn setup and pnpm branch to get the error.
The full error (w/ truncated paths)
Parsing error: Cannot find module '@babel/plugin-proposal-decorators'
Require stack:
- node_modules/.pnpm/@babel+core<EMAIL_ADDRESS>- node_modules/.pnpm/@babel+core<EMAIL_ADDRESS>- node_modules/.pnpm/@babel+core<EMAIL_ADDRESS>- node_modules/.pnpm/@babel+eslint-parser@7.22.15_@babel+core@7.23.2_eslint<EMAIL_ADDRESS>- node_modules/.pnpm/@babel+eslint-parser@7.22.15_@babel+core@7.23.2_eslint<EMAIL_ADDRESS>- node_modules/.pnpm/@babel+eslint-parser@7.22.15_@babel+core@7.23.2_eslint<EMAIL_ADDRESS>- node_modules/.pnpm/@babel+eslint-parser@7.22.15_@babel+core@7.23.2_eslint<EMAIL_ADDRESS>- node_modules/.pnpm/@eslint+eslintrc<EMAIL_ADDRESS>
Make sure that all the Babel plugins and presets you are using
are defined as dependencies or devDependencies in your package.json
file. It's possible that the missing plugin is loaded by a preset
you are using that forgot to add the plugin to its dependencies: you
can workaround this problem by explicitly adding the missing package
to your top-level package.json.

I'm guessing that vscode-eslint (and/or eslint's API it uses) tries to resolve node_modules paths on its own, and those are different under pnpm? @babel/plugin-proposal-decorators in this particular case is a sub-dependency (i.e. not declared in the package.json of the project) so w/ pnpm it's not present directly in node_modules directory.

I test it with npm as well and your setup works there as well. So this seems to be something special with pnpm which I first need to understand. All I can recommend for now is to add @babel/plugin-proposal-decorators to your dev dependencies which I tested and it works.

The reason for this is that pnpm tweaks the eslint script that is put into the ./node_modules/.bin folder and adds some NODEPATH settings to is. In your case mainly:
/workspaces/mass-merge/node_modules/.pnpm/eslint@8.51.0/node_modules/eslint/bin/node_modules:/workspaces/mass-merge/node_modules/.pnpm/eslint@8.51.0/node_modules/eslint/node_modules:/workspaces/mass-merge/node_modules/.pnpm/eslint@8.51.0/node_modules:/workspaces/mass-merge/node_modules/.pnpm/node_modules
which actually hard codes paths
yarn does something similar but yarn provides a tools that lets VS Code know about this (e.g. yarn dlx @yarnpkg/sdks vscode) SInce I don't know what the purpose of that tweaking is all I can recommend is to open an issue against pnpm to ask them to provide a similar tools as yarn does


Issue: https://github.com/hypertrace/document-store/issues/48

Add bulk update API implementation for Mongo. This PR does not provide an implementation for postgresql and can be added in a follow up PR

I wonder when Postgres will be added. It makes sense we add it in a
separate PR but I would say we shouldn't release without having parity on
this. Otherwise it will be a never ending story of lack of parity. Does it
make sense?
On Wed, 14 Apr 2021, 10:47 github-actions[bot], @.***>
wrote:

Unit Test Results
11 files ±0 11 suites ±0 4s ⏱ ±0s
90 tests +2 90 ✔ +2 0 💤 ±0 0 ❌ ±0
Results for commit 7ccdf64
https://github.com/hypertrace/document-store/commit/7ccdf646b69dde519a38f2fe2bb5defadbfcaab0.
± Comparison against base commit 2cdb9d3
https://github.com/hypertrace/document-store/commit/2cdb9d3a037bcba5e17f30dcc45ec7a588420b2f
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hypertrace/document-store/pull/49#issuecomment-819348509,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAULJCYBUVNBGE4GXJ3TIVJDTANCNFSM424SLRMQ
.

I wonder when Postgres will be added. It makes sense we add it in a separate PR but I would say we shouldn't release without having parity on this. Otherwise it will be a never ending story of lack of parity. Does it make sense?
…
On Wed, 14 Apr 2021, 10:47 github-actions[bot], @.***> wrote: Unit Test Results 11 files ±0 11 suites ±0 4s ⏱ ±0s 90 tests +2 90 ✔ +2 0 💤 ±0 0 ❌ ±0 Results for commit 7ccdf64 <7ccdf64>. ± Comparison against base commit 2cdb9d3 <2cdb9d3> . — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXOYAULJCYBUVNBGE4GXJ3TIVJDTANCNFSM424SLRMQ .

This was needed as part of a fix for a RAF ticket. I can pick this up once the RAF ticket is completed. So likely next week


Relations API

The GET /relations route doesn't have a (documented) filter for the actual relation id...
The id filter currently refers to the resource, where it's either the subject or object.  That filter should be renamed to resourceId, and id should be the Relation id.

@evillemez Could we add a PUT route for editing relations? As far as I can tell, the only way to do that at the moment is deleting the original relation and recreating a new one with the updated data.
This isn't a huge issues, since there's only so much data in a relation that you could possibly edit, but it does come up when people want to change the kind of their text tracks.

@gliese1337 Sorry for the delay...
Doable - but I'm not at AC anymore and can't really devote any time to the project, unfortunately... I'd bet that @DavidMikeSimon would accept a PR if anyone were to add it, though.


Sort radars alphabetically per country

This needs to be done manually in config.ts. Ideally sorting is done on radar code (cf. https://aloftdata.eu/radars/) but that only makes sense if the radar code is also shown. So this issue is blocked by https://github.com/inbo/crow/issues/195

Note that changing the order will also affect how radars are shown on the map: the latest in the order is shown on top.


Cadvisor: update and fix test

Motivation for this change
Fixing the cadvisor test.
The cadvisor version was updated to match influxdb version.
@offlinehacker: Please review and test the PR. I know pretty much nothing about cadvisor, so I might have missed some important things. Also, I guess the cadvisor module should be updated to match the new version and features.
cc @domenkozar @offlinehacker
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Tnx!
On Fri, Sep 16, 2016, 09:10 Domen Kožar<EMAIL_ADDRESS>wrote:

Merged #18624 https://github.com/NixOS/nixpkgs/pull/18624.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/18624#event-791738417, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAjvSzaJCFCRDExhKjlBPKCnGNiUoOFyks5qqkDVgaJpZM4J90IN
.

Hmm, it's still failing, maybe it takes so long time to get up? http://hydra.nixos.org/build/40712097/nixlog/17/raw

#18671 should hopefully fix that.


Insert gesture to recognize video intro

I need to recognize the open hand when inserting the video intro.

It would be more efficient to compute gestures only once, but I don't do that because after cutting video, timestamps would change.


provide a homebrew-tap recipe

Hi!
Proposal
Do you have any plans to provide a homebrew-tap recipe? I saw you have integration with goreleaser, it provides that possibility.
For example, golangci-lint does that: https://github.com/golangci/golangci-lint/blob/6a689074bf17fd4ae1db779a74dba821a162b6c8/.goreleaser.yml#L82-L97
Background
It will be great to have the easiest way to install the binary on a local machine.
Workarounds
Now I used go mod to fetch new release and build a binary.

Thanks for your proposal. We would happily get a pull request to provide a solution as you mentioned. Would you agree to submit one ?

Yes, sure.

submit is here #786

Closed by #786


SAK-33098 add bulk edit for gradebook items

Ref https://jira.sakaiproject.org/browse/SAK-33098
Screenshot:

@steveswinsburg can you add the changes requested by accesslint and lets keep the whitespace changes to a minimum while that conversation happens in the email list?

This was discussed in the Core Meeting
see https://etherpad.nightly.sakaiproject.org/p/core-2018-10-16
and a consensus was reached that it doesn't make sense to accept a PR with large amounts of non functional changes.

I am in the middle of updating. Please do not close my PRs without consulting me first.

Codacy issues unrelated to this change.


UpstashError: Unauthorized

Using the latest, I've copied the code directly from Connect to your database, section
import { Redis } from '@upstash/redis'

const redis = new Redis({
  url: 'https://*****.upstash.io',
  token: '********',

})

const data = await redis.set('foo', 'bar');

My token was copied directly from

and verified to be loaded.
However this immediately fails with Unauthorized and no other information.
I noticed the node redis and ioredis versions use the port in the url where the @upstash/redis doe not. Is that the issue? If not more detail in the error message or anything to point as to why a valid token with your quick start code would fail.

Ok so apparently password is not what the API is wanting in token. I think the UI in the dashboard makes this very confusing because the REST API sections and Connect to your database are completely separate. In addition the langue UPSTASH_REDIS_REST_TOKEN has no indication that is to be use as token property in the connnect to your db code. I think there are lot of opportunities to make this more clear.

is here:

is here:

Wow, why is this critical button so tiny?


Recurring ValueError when refreshing TensorBoard

I'm often seeing the following ValueError:
  File "/persist/git/flambe/flambe/experiment/progress.py", line 66, in refresh
    k, v = h.split('=')
ValueError: not enough values to unpack (expected 2, got 1)

This happens when viewing TensorBoard in browser, and refreshing the page; the above error is logged to console by the server. This doesn't break anything, but it seems like a bug all the same.

Are you doing : !g with a single value inside?

@williamabrwolf I think jeremy could be right

Are you doing : !g with a single value inside?

Closing for now.


Typechecking fails for some numpy functions

Environment data

Language Server version: 2020.11.1
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): Miniconda Python 3.9

Expected behaviour
Correctly handle numpy typechecking
Actual behaviour
Assuming the following code:
import numpy as np
res = np.full_like(arr1, np.nan)
res[i] = np.max(arr2)

Pylance complains:
"__setitem__" method not defined on type "Tuple[Unknown]"

This seems to be caused by a mis-interpretation of the numpy source code which contains the idiom return (a, ) but in fact somehow returns a numpy ndarray object, not a tuple as understood by Pylance. The modified return type could be because of the operation of the decorator of the relevant function.
See numpy code here and here

Duplicate of #150. Numpy isn't typed, so it's a bit of a difficult time to try and work on.


QueryHelpers.AddQueryString should support # in the URL

Currently, if you try to add a query string like foo=bar to http://someurl.com/hello#world it returns http://someurl.com/hello#world?foo=bar which should actually be http://someurl.com/hello?foo=bar#world

Feel free to assign to @sornaks when triaging.

@sornaks are you working on this for Beta 6?

@muratg - yes. sent a PR.

Checked in. https://github.com/aspnet/HttpAbstractions/commit/25ea93de9e03f1b0be8922bf727163f8ac3be499

Would it make more sense to have a separate API called AddHashFragment?

@brockallen We're not trying to add a hash, we're trying to append query params to a url that may already have a hash.

Ah, got ya.


Tail do no consume input

On tail -f
Everything you type is not consumed and executed after stop command

Solved on #1048

Can you provide a list of steps to reproduce this? Here's what I came up with, but maybe I'm just misunderstanding the issue.

In one terminal, run the following:
$ echo hello | ( tail -f /etc/rc.local ; md5sum )

In another shell, kill the tail:
# Find out the PID
$ ps aux | grep 'tail -f /etc/resolv.conf' | grep -v grep
minoru   13808  0.0  0.0 124800   460 pts/11   S+   15:37   0:00 tail -f /etc/resolv.conf
$ kill 13808

In the first shell, observe the output. Mine is:
# Generated by resolvconf
nameserver <IP_ADDRESS>
options edns0

b1946ac92492d2347c6235b4d2611184  -

Note the last line. This is an MD5 hashsum of string "hello\n". This means tail didn't consume that "hello", and it went on to md5sum.

This is with tail (GNU coreutils) 8.26. Running the same experiment with previous master commit, ee9013215bed626fd14bfbcf73d3d90cc65afade, yields the same result, so uutils implementation is correct in this regard.
Am I missing or misunderstanding something?

I can reproduce tail consuming input this way:
$ tail -f /etc/rc.local; cat -A

from another terminal:
$ TAIL_PID=$(ps -ef | grep tai[l] | awk '{print $2}')
$ echo -e 'rm\n\nmv\n\n\n\n' > /proc/$TAIL_PID/fd/0
$ kill -2 $TAIL_PID

I guess those explains by itself, anyway it doesn't hurt little explanation:

$TAIL_PID grabs pid for running tail
echo -e send harming commands to stdin of running tail
kill -2 send a SIGINT (Ctrl+C) to tail
cat -A echo output with special symbols for special characters like $ = \n

I can see input echoed while tail is running
rm

mv

but those lines are not passed to next command cat
I can dig into tail implementation to see if this consumption is really done or not anyway
What I'm looking for is a tail implementation that support this workflow:

tail -f on a bunch of log files
press Enter several times (to clean screen)
write some text as note ("looking to find here blablabla that is failing when blablabla"
stop tail with Ctrl+C
do not see command line executing several Enter and my random notes as commands, specially if they become harming commands

I ran your commands and indeed it all works as you describe. But running them with uutils ee9013215bed626fd14bfbcf73d3d90cc65afade works the same way, too!
It looks like comparing GNU and uutils implementations will be necessary after all.

I replaced tail in your examples with rev (which reverses the strings in the input, e.g. turns "hello" into "olleh"), and sure enough, doing echo "hello\n\n\nworld resulted in the following output from rev:
hello

world

This StackOverflow answer explains why this happens. Indeed, when I replaced rev with cat | rev and echoed into rev's FD 0, I got a reversed output:
olleh

dlrow

In other words, your example doesn't really reproduce the workflow you describe at the end; you should be doing cat | ( tail -f /etc/rc.local; cat -A) instead.
This doesn't explain why uutils and GNU tail behave differently for you, though. The only suggestion I have is to run cargo clean && cargo build to ensure you have a clean build, and ensuring you've build the latest commit (which is ee9013215bed626fd14bfbcf73d3d90cc65afade).

I should say this problem arises on windows, and other tail versions suffer that too. My patch fixes that, behaving like *nix systems. Maybe check if it is running under windows is an option to apply.
Will try your hints and look for causes, but is true that using it, rust tail will be ahead of the command it tries to mimic, so maybe it should not be merged until a that fix is applied on upstream projects

Oh, Windows! This might depend on the shell as well; what are you running? (I've tested on Linux with ZSH and Bash.)
I don't have Windows, so I won't be able to help you there.
I'd also like to note that the tests in #1048 failed, even on Windows, and testing that PR locally, I can confirm that tail -f doesn't follow the file at all—it seems like it simply hangs until killed.

I use MINGW (from git bash for windows) Tested every possible tail implementation for windows and all of them keeps input for next command
Humm, seems it breaks *nix systems, so a check for OS running makes sense.
I will close this as it is clearly a new feature of windows OS. Any hint about how to implement Ok(_) so it uses datum but do not print anything? i read that result is annotated with must_use but don't know how to use it without doing nothing


Having trouble using the bridge plug-in

Hi.
I am working on a project using Touch Designer & we want to send data using OSC from a Node.js app.
I am getting the following error at run-time when trying to use the bridge plug-in:
"Error: BridgePlugin can not be used in browser context"
	BridgePlugin
osc.js:1073
require<[5]<
camera_osc.js:34:30
newRequire
http://localhost:1234/dist/904f316f53e694a9253efea39d6a5f51.js:42:7
require<
http://localhost:1234/dist/904f316f53e694a9253efea39d6a5f51.js:69:5
<anonymous>
http://localhost:1234/dist/904f316f53e694a9253efea39d6a5f51.js:10:12

@ManjitBedi How do you use the library in your code? Do you use the BridgePlugin on the client-side? Its only meant to be used on the server-side, the client would make use of the default WebsocketClientPlugin.

We are using UDP with Touch Designer.   I have tested sending UDP packets with other apps & it is working.  I changed the code to the following based on the Wiki page.
const dgram = require('dgram')
const OSC = require('osc-js')

const options = {
  send: {
      host: '<IP_ADDRESS>',   // @param {string} Hostname of udp client for messaging
      port: 3333           // @param {number} Port of udp client for messaging
    }
}

const osc = new OSC({ plugin: new OSC.DatagramPlugin(options) })
osc.open()

// send a messsage via udp
osc.send(new OSC.Message('/test'))

I now get a different error:
TypeError: dgram.createSocket is not a function[Learn More] osc.js:973
DatagramPlugin
osc.js:973
require<[7]<
camera_osc.js:39:30
newRequire
http://localhost:1234/dist/904f316f53e694a9253efea39d6a5f51.js:42:7
require<
http://localhost:1234/dist/904f316f53e694a9253efea39d6a5f51.js:69:5
<anonymous>
http://localhost:1234/dist/904f316f53e694a9253efea39d6a5f51.js:10:12

I see that UDP is not possible with Javascript in a browser app.

@ManjitBedi Yes! You will need to have a middleman between the browser and your UDP server application. This could be a Node.JS server for example, here is something: https://github.com/adzialocha/osc-js/wiki/PureData-&-MaxMSP

I see;  I get what you are saying;  thanks for the suggestion.


UnsatisfiedLinkError on ARM CORTEX A9 (soft float) at DB.open

I used sqlite-jdbc-3.8.11.jar to compile a jar that tries to open a connection to a database.
This is the error I get on a ARM CORTEX A9 (soft float).
The same jar is working fine on Ubuntu on x86. I think that working on ARM is quite important for a library like this.
zynq> java -jar sqlite-3.8.11.jar
Exception in thread "main" java.lang.UnsatisfiedLinkError: org.sqlite.core.NativeDB._open(Ljava/lang/String;I)V
at org.sqlite.core.NativeDB._open(Native Method)
at org.sqlite.core.DB.open(DB.java:161)
at org.sqlite.core.CoreConnection.open(CoreConnection.java:220)
at org.sqlite.core.CoreConnection.(CoreConnection.java:76)
at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:24)
at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:23)
at org.sqlite.SQLiteConnection.(SQLiteConnection.java:45)
at org.sqlite.JDBC.createConnection(JDBC.java:114)
at org.sqlite.JDBC.connect(JDBC.java:88)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.argonnetech.sqlite.SQLite.main(SQLite.java:14)

Could you try make native and mvn test command? If it works, please send the generated native library src/main/resources/org/sqlite/native/Linux/arm/libsqlitejdbc.so so that we can properly support ARM CPU.
Thanks.

Dear Taro,
I tried:
make ARCH=arm CC=arm-xilinx-linux-gnueabi-gcc native
but I get the following. Could you suggest the right way to cross compile
your lib?
#make ARCH=arm CC=arm-xilinx-linux-gnueabi-gcc native
*perl -p -e "s/sqlite3_api;/sqlite3_api = 0;/g" *

target/sqlite-amalgamation-3081100/sqlite3ext.h >
target/sqlite-3.8.11-Linux-x86_64/sqlite3ext.h*
*perl -p -e "s/^opendb_out:/  if(!db->mallocFailed && rc==SQLITE_OK){ rc =
RegisterExtensionFunctions(db); }\nopendb_out:/;" *
target/sqlite-amalgamation-3081100/sqlite3.c >
target/sqlite-3.8.11-Linux-x86_64/sqlite3.c*
cat src/main/ext/.c >> target/sqlite-3.8.11-Linux-x86_64/sqlite3.c*
*arm-xilinx-linux-gnueabi-gcc -o
target/sqlite-3.8.11-Linux-x86_64/sqlite3.o -c
-Itarget/sqlite-3.8.11-Linux-x86_64 -Itarget/sqlite-amalgamation-3081100
-Ilib/inc_linux -I/usr/lib/jvm/java-8-oracle/include -O2 -fPIC -m64
-fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include"
-I"/usr/lib/jvm/java-8-oracle/include/linux" *
-DSQLITE_ENABLE_LOAD_EXTENSION=1 *
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT *
-DSQLITE_ENABLE_COLUMN_METADATA *
-DSQLITE_CORE *
-DSQLITE_ENABLE_FTS3 *
-DSQLITE_ENABLE_FTS3_PARENTHESIS *
-DSQLITE_ENABLE_RTREE *
-DSQLITE_ENABLE_STAT2 *

\*

target/sqlite-3.8.11-Linux-x86_64/sqlite3.c*
arm-xilinx-linux-gnueabi-gcc: error: unrecognized command line option
'-m64'
make: *** [target/sqlite-3.8.11-Linux-x86_64/sqlite3.o] Error 1

On 3 August 2015 at 17:17, Taro L. Saito<EMAIL_ADDRESS>wrote:

Could you try make native and mvn test command? If it works, please send
the generated native library
src/main/resources/org/sqlite/native/Linux/arm/libsqlitejdbc.so so that
we can properly support ARM CPU.
Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/xerial/sqlite-jdbc/issues/45#issuecomment-127274576.

parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ make native CROSS_PREFIX=arm-linux-gnueabi- OS_NAME=Linux OS_ARCH=arm
perl -p -e "s/sqlite3_api;/sqlite3_api = 0;/g"
target/sqlite-amalgamation-3081100/sqlite3ext.h > target/sqlite-3.8.11-Linux-arm/sqlite3ext.h
perl -p -e "s/^opendb_out:/  if(!db->mallocFailed && rc==SQLITE_OK){ rc = RegisterExtensionFunctions(db); }\nopendb_out:/;"
target/sqlite-amalgamation-3081100/sqlite3.c > target/sqlite-3.8.11-Linux-arm/sqlite3.c
cat src/main/ext/.c >> target/sqlite-3.8.11-Linux-arm/sqlite3.c
arm-linux-gnueabi-gcc -o target/sqlite-3.8.11-Linux-arm/sqlite3.o -c -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux"
-DSQLITE_ENABLE_LOAD_EXTENSION=1
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT
-DSQLITE_ENABLE_COLUMN_METADATA
-DSQLITE_CORE
-DSQLITE_ENABLE_FTS3
-DSQLITE_ENABLE_FTS3_PARENTHESIS
-DSQLITE_ENABLE_RTREE
-DSQLITE_ENABLE_STAT2

target/sqlite-3.8.11-Linux-arm/sqlite3.c
/bin/sh: 1: arm-linux-gnueabi-gcc: not found
make: *** [target/sqlite-3.8.11-Linux-arm/sqlite3.o] Error 127
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ make native CROSS_PREFIX=arm-linux-gnueabi- OS_NAME=Linux OS_ARCH=arm^C
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ make native CROSS_PREFIX=arm-xilinx-linux-gnueabi OS_NAME=Linux OS_ARCH=arm
perl -p -e "s/sqlite3_api;/sqlite3_api = 0;/g"
target/sqlite-amalgamation-3081100/sqlite3ext.h > target/sqlite-3.8.11-Linux-arm/sqlite3ext.h
perl -p -e "s/^opendb_out:/  if(!db->mallocFailed && rc==SQLITE_OK){ rc = RegisterExtensionFunctions(db); }\nopendb_out:/;"
target/sqlite-amalgamation-3081100/sqlite3.c > target/sqlite-3.8.11-Linux-arm/sqlite3.c
cat src/main/ext/.c >> target/sqlite-3.8.11-Linux-arm/sqlite3.c
arm-xilinx-linux-gnueabigcc -o target/sqlite-3.8.11-Linux-arm/sqlite3.o -c -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux"
-DSQLITE_ENABLE_LOAD_EXTENSION=1
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT
-DSQLITE_ENABLE_COLUMN_METADATA
-DSQLITE_CORE
-DSQLITE_ENABLE_FTS3
-DSQLITE_ENABLE_FTS3_PARENTHESIS
-DSQLITE_ENABLE_RTREE
-DSQLITE_ENABLE_STAT2

target/sqlite-3.8.11-Linux-arm/sqlite3.c
/bin/sh: 1: arm-xilinx-linux-gnueabigcc: not found
make: *** [target/sqlite-3.8.11-Linux-arm/sqlite3.o] Error 127
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ make native CROSS_PREFIX=arm-xilinx-linux-gnueabi- OS_NAME=Linux OS_ARCH=arm
perl -p -e "s/sqlite3_api;/sqlite3_api = 0;/g"
target/sqlite-amalgamation-3081100/sqlite3ext.h > target/sqlite-3.8.11-Linux-arm/sqlite3ext.h
perl -p -e "s/^opendb_out:/  if(!db->mallocFailed && rc==SQLITE_OK){ rc = RegisterExtensionFunctions(db); }\nopendb_out:/;"
target/sqlite-amalgamation-3081100/sqlite3.c > target/sqlite-3.8.11-Linux-arm/sqlite3.c
cat src/main/ext/.c >> target/sqlite-3.8.11-Linux-arm/sqlite3.c
arm-xilinx-linux-gnueabi-gcc -o target/sqlite-3.8.11-Linux-arm/sqlite3.o -c -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux"
-DSQLITE_ENABLE_LOAD_EXTENSION=1
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT
-DSQLITE_ENABLE_COLUMN_METADATA
-DSQLITE_CORE
-DSQLITE_ENABLE_FTS3
-DSQLITE_ENABLE_FTS3_PARENTHESIS
-DSQLITE_ENABLE_RTREE
-DSQLITE_ENABLE_STAT2

target/sqlite-3.8.11-Linux-arm/sqlite3.c
"$JAVA_HOME/bin/javac"  -source 1.5 -target 1.5 -sourcepath src/main/java -d target/sqlite-3.8.11-Linux-arm src/main/java/org/sqlite/core/NativeDB.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
4 warnings
"$JAVA_HOME/bin/javah" -classpath target/sqlite-3.8.11-Linux-arm -jni -o target/sqlite-3.8.11-Linux-arm/NativeDB.h org.sqlite.core.NativeDB
arm-xilinx-linux-gnueabi-gcc -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux" -c -o target/sqlite-3.8.11-Linux-arm/NativeDB.o src/main/java/org/sqlite/core/NativeDB.c
arm-xilinx-linux-gnueabi-gcc -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux" -o target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so target/sqlite-3.8.11-Linux-arm/.o -shared -static-libgcc
arm-xilinx-linux-gnueabi-strip target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so
cp target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so src/main/resources/org/sqlite/native/Linux/arm/libsqlitejdbc.so
cp target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so target/classes/org/sqlite/native/Linux/arm/libsqlitejdbc.so
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ mvn test
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building SQLite JDBC
[INFO]    task-segment: [test]
[INFO] ------------------------------------------------------------------------
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 44 resources
[INFO] Copying 10 resources
[INFO] Copying 1 resource to META-INF/services
[INFO] Copying 3 resources to META-INF/maven/org.xerial/sqlite-jdbc
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 43 source files to /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/target/classes
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/main/java/org/sqlite/jdbc4/JDBC4PreparedStatement.java: Some input files use or override a deprecated API.
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/main/java/org/sqlite/jdbc4/JDBC4PreparedStatement.java: Recompile with -Xlint:deprecation for details.
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 23 source files to /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/target/test-classes
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/java/org/sqlite/PrepStmtTest.java: /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/java/org/sqlite/PrepStmtTest.java uses or overrides a deprecated API.
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/java/org/sqlite/PrepStmtTest.java: Recompile with -Xlint:deprecation for details.
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/target/surefire-reports

T E S T S
Running org.sqlite.SQLiteConnectionPoolDataSourceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.13 sec
Running org.sqlite.StatementTest
Tests run: 32, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.047 sec
Running org.sqlite.JDBCTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.sqlite.UDFTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.203 sec
Running org.sqlite.SQLiteDataSourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.sqlite.ConnectionTest
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec
Running org.sqlite.DBMetaDataTest
Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
Running org.sqlite.SQLiteJDBCLoaderTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.ResultSetTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.sqlite.FetchSizeTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running org.sqlite.BackupTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec
Running org.sqlite.ExtensionTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.util.OSInfoTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
Running org.sqlite.ExtendedCommandTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.sqlite.SQLiteConfigTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.sqlite.QueryTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.SavepointTest
running in native mode
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec
Running org.sqlite.PrepStmtTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
Running org.sqlite.ReadUncommittedTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.RSMetaDataTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.sqlite.TransactionTest
running in native mode
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.085 sec
Running org.sqlite.InsertQueryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec
Results :
Tests run: 194, Failures: 0, Errors: 0, Skipped: 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Mon Aug 03 08:49:58 PDT 2015
[INFO] Final Memory: 33M/300M
[INFO] ------------------------------------------------------------------------
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$

parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ make native CROSS_PREFIX=arm-xilinx-linux-gnueabi- OS_NAME=Linux OS_ARCH=arm
perl -p -e "s/sqlite3_api;/sqlite3_api = 0;/g"
target/sqlite-amalgamation-3081100/sqlite3ext.h > target/sqlite-3.8.11-Linux-arm/sqlite3ext.h
perl -p -e "s/^opendb_out:/  if(!db->mallocFailed && rc==SQLITE_OK){ rc = RegisterExtensionFunctions(db); }\nopendb_out:/;"
target/sqlite-amalgamation-3081100/sqlite3.c > target/sqlite-3.8.11-Linux-arm/sqlite3.c
cat src/main/ext/.c >> target/sqlite-3.8.11-Linux-arm/sqlite3.c
arm-xilinx-linux-gnueabi-gcc -o target/sqlite-3.8.11-Linux-arm/sqlite3.o -c -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux"
-DSQLITE_ENABLE_LOAD_EXTENSION=1
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT
-DSQLITE_ENABLE_COLUMN_METADATA
-DSQLITE_CORE
-DSQLITE_ENABLE_FTS3
-DSQLITE_ENABLE_FTS3_PARENTHESIS
-DSQLITE_ENABLE_RTREE
-DSQLITE_ENABLE_STAT2

target/sqlite-3.8.11-Linux-arm/sqlite3.c
"$JAVA_HOME/bin/javac"  -source 1.5 -target 1.5 -sourcepath src/main/java -d target/sqlite-3.8.11-Linux-arm src/main/java/org/sqlite/core/NativeDB.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
4 warnings
"$JAVA_HOME/bin/javah" -classpath target/sqlite-3.8.11-Linux-arm -jni -o target/sqlite-3.8.11-Linux-arm/NativeDB.h org.sqlite.core.NativeDB
arm-xilinx-linux-gnueabi-gcc -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux" -c -o target/sqlite-3.8.11-Linux-arm/NativeDB.o src/main/java/org/sqlite/core/NativeDB.c
arm-xilinx-linux-gnueabi-gcc -Itarget/sqlite-3.8.11-Linux-arm -Itarget/sqlite-amalgamation-3081100 -I/usr/lib/jvm/java-8-oracle/include -Ilib/inc_linux -O2 -mfloat-abi=softfp -mfpu=vfp -fPIC -fvisibility=hidden   -I"/usr/lib/jvm/java-8-oracle/include" -I"/usr/lib/jvm/java-8-oracle/include/linux" -o target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so target/sqlite-3.8.11-Linux-arm/.o -shared -static-libgcc
arm-xilinx-linux-gnueabi-strip target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so
cp target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so src/main/resources/org/sqlite/native/Linux/arm/libsqlitejdbc.so
cp target/sqlite-3.8.11-Linux-arm/libsqlitejdbc.so target/classes/org/sqlite/native/Linux/arm/libsqlitejdbc.so
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$ mvn test
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building SQLite JDBC
[INFO]    task-segment: [test]
[INFO] ------------------------------------------------------------------------
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 44 resources
[INFO] Copying 10 resources
[INFO] Copying 1 resource to META-INF/services
[INFO] Copying 3 resources to META-INF/maven/org.xerial/sqlite-jdbc
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 43 source files to /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/target/classes
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/main/java/org/sqlite/jdbc4/JDBC4PreparedStatement.java: Some input files use or override a deprecated API.
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/main/java/org/sqlite/jdbc4/JDBC4PreparedStatement.java: Recompile with -Xlint:deprecation for details.
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 23 source files to /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/target/test-classes
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/java/org/sqlite/PrepStmtTest.java: /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/java/org/sqlite/PrepStmtTest.java uses or overrides a deprecated API.
[WARNING] /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/src/test/java/org/sqlite/PrepStmtTest.java: Recompile with -Xlint:deprecation for details.
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /home/parallels/ypacket2/rootfs/packages/sqlite-jdbc/target/surefire-reports

T E S T S
Running org.sqlite.SQLiteConnectionPoolDataSourceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.13 sec
Running org.sqlite.StatementTest
Tests run: 32, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.047 sec
Running org.sqlite.JDBCTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.sqlite.UDFTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.203 sec
Running org.sqlite.SQLiteDataSourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.sqlite.ConnectionTest
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec
Running org.sqlite.DBMetaDataTest
Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
Running org.sqlite.SQLiteJDBCLoaderTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.ResultSetTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.sqlite.FetchSizeTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running org.sqlite.BackupTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec
Running org.sqlite.ExtensionTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.util.OSInfoTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
Running org.sqlite.ExtendedCommandTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.sqlite.SQLiteConfigTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.sqlite.QueryTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.SavepointTest
running in native mode
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec
Running org.sqlite.PrepStmtTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
Running org.sqlite.ReadUncommittedTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.sqlite.RSMetaDataTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.sqlite.TransactionTest
running in native mode
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.085 sec
Running org.sqlite.InsertQueryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec
Results :
Tests run: 194, Failures: 0, Errors: 0, Skipped: 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Mon Aug 03 08:49:58 PDT 2015
[INFO] Final Memory: 33M/300M
[INFO] ------------------------------------------------------------------------
parallels@ubuntu:~/ypacket2/rootfs/packages/sqlite-jdbc$

I did it, you can find the library attached.
Going to try this native lib. I will simply update the lib in the jar and
let you know.
Thx.
On 3 August 2015 at 17:17, Taro L. Saito<EMAIL_ADDRESS>wrote:

Could you try make native and mvn test command? If it works, please send
the generated native library
src/main/resources/org/sqlite/native/Linux/arm/libsqlitejdbc.so so that
we can properly support ARM CPU.
Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/xerial/sqlite-jdbc/issues/45#issuecomment-127274576.

I replaced the native arm lib into the jar with the one I compiled.
I can open the database, now I will do other tests as well.
Thx very much.

@antonio-dibacco
It looks like GitHub does not accept attachment via e-mail.
Could you create a pull request with the native library you built, or directly send an e-mail to me (leo at xerial.org)?
Thanks.

Added your binary here:
https://github.com/xerial/sqlite-jdbc/commit/3ee51f9b4db5ecfe56d75e7bd963c3d40c8112b8
Thanks for the contribution.

@antonio-dibacco Released <IP_ADDRESS> with your binary. Could you check whether this works or not?
Thanks

It works.
On 4 August 2015 at 05:02, Taro L. Saito<EMAIL_ADDRESS>wrote:

@antonio-dibacco https://github.com/antonio-dibacco Released <IP_ADDRESS>
with your binary. Could you check whether this works or not?
Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/xerial/sqlite-jdbc/issues/45#issuecomment-127461858.

Great. Thanks!

Thanks to you for your wonderful work. Count on me for any test in the
future.
Regards,
Antonio.
On 4 August 2015 at 09:47, Taro L. Saito<EMAIL_ADDRESS>wrote:

Great. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/xerial/sqlite-jdbc/issues/45#issuecomment-127509619.

hello , I have the same problem but with a ARMv5 , may you help me?

I tried to compile with "make native".
perl -p -e "s/sqlite3_api;/sqlite3_api = 0;/g"
target/sqlite-amalgamation-3081100/sqlite3ext.h > target/sqlite-3.8.11--/sqlite3ext.h
perl -p -e "s/^opendb_out:/  if(!db->mallocFailed && rc==SQLITE_OK){ rc = RegisterExtensionFunctions(db); }\nopendb_out:/;"
target/sqlite-amalgamation-3081100/sqlite3.c > target/sqlite-3.8.11--/sqlite3.c
cat src/main/ext/*.c >> target/sqlite-3.8.11--/sqlite3.c
o target/sqlite-3.8.11--/sqlite3.o -c -Itarget/sqlite-3.8.11-- -Itarget/sqlite-amalgamation-3081100
-DSQLITE_ENABLE_LOAD_EXTENSION=1
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT
-DSQLITE_ENABLE_COLUMN_METADATA
-DSQLITE_CORE
-DSQLITE_ENABLE_FTS3
-DSQLITE_ENABLE_FTS3_PARENTHESIS
-DSQLITE_ENABLE_RTREE
-DSQLITE_ENABLE_STAT2

target/sqlite-3.8.11--/sqlite3.c
make: o: Command not found
Makefile:49: recipe for target 'target/sqlite-3.8.11--/sqlite3.o' failed
make: [target/sqlite-3.8.11--/sqlite3.o] Error 127 (ignored)
"$JAVA_HOME/bin/javac"  -source 1.5 -target 1.5 -sourcepath src/main/java -d target/sqlite-3.8.11-- src/main/java/org/sqlite/core/NativeDB.java
/bin/sh: 1: /home/stefano/jre/bin/java/bin/javac: not found
Makefile:34: recipe for target 'target/sqlite-3.8.11--/org/sqlite/core/NativeDB.class' failed
make: *** [target/sqlite-3.8.11--/org/sqlite/core/NativeDB.class] Error 2

This error message says javac is not found. Please set:
export JAVA_HOME=(your jdk installation path)/bin

ejdk (soft float) does not include javac and this is the only available for ARMv5.

I'm not familiar with embedded jdk. Could you tell me how do you compile java programs in ARMv5 machine?

the problem is just that. I do not know if you can do and how to do it

OK I have compiled, but I have this error.

A fatal error has been detected by the Java Runtime Environment:

Internal Error (os_linux_zero.cpp:285), pid=3078, tid=3060642912
fatal error: caught unhandled signal 4

JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
Java VM: OpenJDK Zero VM (24.79-b02 mixed mode linux-arm )
Derivative: IcedTea 2.5.6
Distribution: Debian GNU/Linux 8.1 (jessie), package 7u79-2.5.6-1~deb8u1
Core dump written. Default location: /home/stefano/isaac/core or core.3078

An error report file with more information is saved as:
/home/stefano/isaac/hs_err_pid3078.log

If you would like to submit a bug report, please include
instructions on how to reproduce the bug and visit:
http://icedtea.classpath.org/bugzilla
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

Aborted (core dumped)

OK I have compiled, but I have this error

A fatal error has been detected by the Java Runtime Environment:

Internal Error (os_linux_zero.cpp:285), pid=3078, tid=3060642912
fatal error: caught unhandled signal 4

JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
Java VM: OpenJDK Zero VM (24.79-b02 mixed mode linux-arm )
Derivative: IcedTea 2.5.6
Distribution: Debian GNU/Linux 8.1 (jessie), package 7u79-2.5.6-1~deb8u1
Core dump written. Default location: /home/core or core.3078

An error report file with more information is saved as:
/home/hs_err_pid3078.log

If you would like to submit a bug report, please include
instructions on how to reproduce the bug and visit:
http://icedtea.classpath.org/bugzilla
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

Aborted (core dumped)

Hello, have the above arm questions been released on a version?


Update to CodePen URL

Updating to CodePen's official documented format for starting Pens with prefilled content. There is also a Prefill API, but that requires a POST, so this URL format is easier to use. But it does require that there is already an existing Pen that it copies the content out of. The Pen in this PR is this one owned by me. I can promise I'll never update that Pen, but if you want to go with this approach, you might wanna update the "slug" to a Pen owned by React on CodePen. Let me know there are any questions!

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Done.

Just checking in here.
The link to CodePen on this page 500 errors because of the invalid usage so it would be nice to fix. We have users writing in to tell us they are getting stuck by this.

@rickhanlonii @harish-sethuraman @jackpope :  Sorry for pinging you here, but I believe you three have recently merged PRs in this repo...? (Let me know if I have that wrong). I'm hoping one of you can provide some insight on what else we need to do to get this merged.
To be clear, we (CodePen) are trying to fix this user experience:


RASCIL 0.7.1

Setup of RASCIL new release
For this I have to build conda packages for

seqfile: https://github.com/musically-ut/seqfile
ska-sdp-func: https://github.com/ska-telescope/ska-sdp-func

Another, not fixed package is "radler", but it doesn't seem to be important.

The seqfile package is now available at: https://anaconda.org/i4ds/seqfile

This issue is depends on #164 . As soon as an anaconda package of ska-sdp-func is available, I can try to rebuild and run the Unittest afterwards.

@Lukas113 will give @fschramka access to the repository in which Lukas is working right now.

@fschramka I've added you and Simon as Admins to https://github.com/i4Ds/ska-sdp-func-build
As mentioned in the meeting the build with the python bindings doesn't work yet and I haven't tested anything with mac.

[...] and I haven't tested anything with mac.

FYI: We will drop macOS support (i.e. stop trying to support macOS). Cost/reward is unfortunately not looking good enough.

ska-sdp-func 0.0.3 is now available at Anaconda registry. Thus as soon as @fschramka finished refactoring the RASCIL build (see #216 ) RASCIL 0.7.1 should be ready to build.

@Lukas113 go for it :)

I've tried to build a 0.7.dev1 version on the according branch and got the following error:

Currently I'm not sure how to solve or approach it since I haven't found something useful on the internet. However, this issue must be related to ska-sdp-func (maybe also the build? Not sure, but conda install conda install -c i4ds -c conda-forge ska-sdp-funcitself works) since it occurs only after adding this specific dependency (e.g. RASCIL build0.7.0` still works in the same environment).

we will directly go to https://github.com/i4Ds/Karabo-Pipeline/issues/233


add WriteBytesAsString()

I have a situation where I'm constructing key names, and I want to avoid an allocation; I can do this cast in my code, but I thought I'd see if there's interest in accepting this so it's obvious for other people how to do this?

I prefer to keep the casting in user code.


Support probe option for MCP client

This patch supports probe option for MCP client.
mixer supports readiness probe for config store currently, but MCP
client does not update probe. Hence, readinessProbe always does not
work when MCP is enabled. This patch fixes it.
Fixes https://github.com/istio/istio/issues/19290

Hi @nak3. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/reopen
https://github.com/istio/istio/issues/19290 is a bug which 100% happens.


[WIP] Linting

WIP, applies a collection of rules to JSON data, is similar in structure to the CocoaPods QIs.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

          1 Warning

:warning:
Tests were not updated

  Generated by :no_entry_sign: danger

Danger went to sleep

OK, the windows build failing is fine 👍